The following items are known limitations when you retrieve performance data from an Optim Performance Manager repository database and view the data in Optim Development Studio or IBM Data Studio.
Performance issues when retrieving SQL performance data from an Optim Performance Manager repository database
The amount of time required to retrieve SQL performance data from a repository database is directly related to the amount of data in the repository database. When Optim Development Studio retrieves performance data from a repository database to be displayed in the SQL Outline view, Optim Development Studio retrieves all the performance data from the repository database for the time frame that you specified.
For a repository database that contains a large amount of performance data, it will take a significant amount of time to retrieve all the requested from the repository database. For example, when a repository database is monitoring a database in a production environment, the repository database might contain a large number of rows of performance data (tens of thousands or millions of rows of data). Retrieving the data from the repository will take a significant amount of time.
Performance data for some SQL statements run on a DB2 for z/OS database cannot be displayed
When Optim Development Studio displays SQL performance data in the SQL Outline view, data from some SQL statements that are run on a DB2 for z/OS database are not displayed. If the DB2 for z/OS database is monitored by Optim Performance Manager, Optim Development Studio retrieves the data from the Optim Performance Manager repository database, but the SQL performance data is not displayed in the SQL Outline view for SQL statements the following cases:
- The SQL statement that is run on the DB2 for z/OS database ends with one or more space characters
- An application uses the pureQuery API and the SQL statement that the application runs on the monitored DB2 for z/OS database ends in a host variable
Workaround: To display the SQL performance data in the SQL outline view, modify the SQL statements that are run on the DB2 for z/OS database.
- If the SQL statement ends with one or more space characters, remove the trailing space characters from SQL statement.
- If the SQL statement ends with a host variable, add an SQL comment "--" to the end of SQL statement.
Performance data for SQL statements might not be not retrieved from a DB2 database when the value for the DB2 parameter STMT_CONC is set to LITERALS
If the value of of the DB2 database configuration parameter STMT_CONC is set to LITERALS, data might not be retrieved if you use the Performance metrics tab of the SQL editor view to run SQL statements against a database to collect database performance data.
The DB2 configuration parameter STMT_CONC enables SQL statement concentration for dynamic statements. SQL statement concentration alters statement text for statements that contain SQL literals.
If the statement is altered, Optim performance Manager gathers the performance data for the altered statement, not the original statement. The performance data for the altered statement is not retrieved and displayed in the Performance metrics view.
Workaround: Set the value of the parameter STMT_CONC to OFF.
Performance data for SQL statements is not retrieved when the application name is masked in Optim Performance Manager
If a monitored database in Optim Performance Manager is configured to mask the client application name, data is not retrieved if you use the Performance metrics tab of the SQL editor view to run SQL statements against the database to collect database performance data.
Workaround: In Optim Performance Manager, change the configuration of the monitored database to not mask the client application name.
|Information Management||Data Studio||Linux, Windows||3.1||IBM Data Studio Developer|