Log and Trace Analyzer v6.0.1 Large Log support - Readme

Known Problems and workarounds

1.0 Large Log support in the Log and Trace Analyzer
1.1 Simultaneous clients access using the same database account is not supported
1.2 Mixed log persistence is not supported
1.3 Resource path collision
1.4 Large Resource Support preferences remain disabled despite valid selection
1.5 Improving performance of large log support
1.6 Restart DB2 after creating database and tables
1.7 Intermittent SQL exception
1.8 Test connection returns an error if you haven't applied preferences

1.0 Large Log support in the Log and Trace Analyzer

1.1 Simultaneous clients access using the same database account is not supported

Concurrent client access to a database might lock some tables. To unlock the tables, restart the Workbench and the database server.

1.2 Mixed log persistence is not supported

Mixed log persistence (XMI- and database-based) in the same workspace is not supported. Use each persistence mechanism in different workspaces.

1.3 Resource path collision

If you use the same database and database account for multiple workspaces, resource path collisions may result and resource will not be persisted into the database.

To work around this problem, use different project and monitor names in each workspace to avoid resource path collisions.

1.4 Large Resource Support preferences remain disabled despite valid selection

In Linux/GTK, on the Large Resource Support preferences page, the database settings fields will remain disabled even when a valid database type is selected.

To work around this problem, select DB2 as the database type, and apply the settings. Close and reopen the preferences dialog; the fields will be enabled.

1.5 Improving performance of large log support

To improve the performance of large log support, run the following command after you have imported large logs or created correlations using large logs:

db2 -tvf plugins/com.ibm.etools.ac.resources.database_6.0.0
/scripts/runStatsForAllHyadesTablesDB2-8.1.sql

1.6 Restart DB2 after creating database and tables

After running the database and tables creation script, CreateDatabaseAndTablesDB2-8.1.sql, you must restart DB2. From a DB2 command window run db2stop and then db2start in order to apply the changes to the configuration parameters made by the script.

1.7 Intermittent SQL exception

Occasionally, the following SQL exception may occur:

com.ibm.db2.jcc.b.SQLException: NULLID.SYSSH203 0X5359534C564C3031

When this problem occurs, restart the workbench and the database, if using DB2 or Cloudscape in network mode. Logs imported when this exception occurs will not be valid and will have to be re-imported.

1.8 Test connection returns an error if you haven't applied preferences

In the Large Log Support page of the Profiling and Logging section of the Preferences dialog, if you click Test connection before you have applied changes to settings, you may get a connection error. To avoid this, click Apply after making any setting changes and then click Test connection.

(C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.

Return to the main readme file

Copyright and notices