This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.
TrueSight App Visibility Agent
App Visibility Agent for Java
App Visibility Agent for Java - All versions
When the App Visibility Agent for Java is installed and running on a WebLogic application server, the “ORA-01000: maximum open cursors exceeded” messages appears.
This message is caused by an outdated driver in the App Visibility Agent for Java
There were some database-related transactions failing with "stack overflow" errors in the Java Agent log and this could cause leak cursors because of this exception.
One possible cause for this is that the stack size, which has been explicitly set for the Java Virtual Machine (JVM) to a small value of 256KB (via "-Xss256k"), is not enough when running with the Java agent. So the first attempt would to increase the stack size configuration for the JVM to 1MB or more and restart the application server to see if the issue disappears.
Unfortunately, if this does not work, then there is no workaround for this issue to allow monitoring of the Java application and Oracle database without the ORA-01000 message. So below are the options to workaround this issue:
Options 1) Use the Light policy, which does not monitor the Oracle database, for the App Visibility Agent for Java
Option 2) Use the Medium policy for the App Visibility Agent for Java, but remove the variable that caused the ORA-01000 message. However, this modified Medium policy does not monitor the Oracle database.
Note: If the JDBC recordings are turned off in the Medium policy, then it will not monitor the database and there will not be any more ORA-01000 errors. If the JDBC recordings is turned on in the Medium policy, then the database will be captured, but the system will also report the ORA-01000 errors.
Below are instructions to turn on JDBC recordings in the Medium Policy:
1. Open the Agent Policies screen in the TrueSight Presentation Server (TSPS_ Console
2. Click on the 3 dots next to the agent policy that and choose to clone it.
3. On the next screen and give the new policy a name
4. Locate the property 'snapin.collect.extended.data.jdbc'.
5. Change the value to 'false'
6. Save the Policy
7. Apply the new policy to the agent
Option 3) Use Option 1 or Option 2 above and do not use the App Visibility Agent for Java to monitor the Oracle database. Instead use the Oracle KM to monitor the Oracle database.