Troubleshooting database servers

This page describes issues that you might encounter with database servers, and contains the following topics:

Troubleshooting an SQL server

When you are using Microsoft SQL Server, the following problems might occur if you use the default isolation level READ COMMITTED for the TrueSight Network Automation application server database:

• Issue 1: Refresh Status action with Configuration Profiling turned on fails with PersistenceException in the Job transcript. 
  Solution 1: Set the READ COMMITTED SNAPSHOT isolation level of the TrueSight Network Automation database to ON, as described in Configuring databases for Windows or Configuring databases for Linux.
• Issue 2: The server log indicates deadlock errors.
  Solution 2: Set the READ COMMITTED SNAPSHOT isolation level of the TrueSight Network Automation database to ON, as described in Configuring databases for Windows or Configuring databases for Linux.
• Issue 3: TrueSight Network Automation upgrade is successful, however, the TrueSight Network Automation services do not start and the BCA-Networks.log file shows the following error message: MSSQL Database isolation level is incorrect. 
  Solution 3: Set the READ COMMITTED SNAPSHOT isolation level of the TrueSight Network Automation database to ON, as described in Configuring databases for Windows or Configuring databases for Linux and start the TrueSight Network Automation services.

Troubleshooting an Oracle server

When you upgrade a TrueSight Network Automation application server with an Oracle database, you might see the following error message if the maximum open cursor value in the database settings is not sufficient to allow the upgrade, and the upgrade might fail:

ORA-01000 maximum open cursors exceeded

To resolve this issue, contact your Oracle database administrator to increase the maximum open cursor value and then, retry the upgrade procedure.

Back to top