89_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 BMC Network Automation application server database:

  • Refresh Status action with Configuration Profiling turned on fails with PersistenceException in the Job transcript.
  • The server log indicates deadlock errors.

To fix these problems, configure the isolation level to READ COMMITTED SNAPSHOT, as described in Configuring databases for Windows or Configuring databases for Linux.

Note

If you want to establish an encrypted connection with the SQL Server database engine, you must run one of the following SQL Server versions. Otherwise, the connection will fail.

  • SQL Server 2014
  • SQL Server 2012
  • SQL Server 2008 R2 Service Pack 1 and later
  • SQL Server 2008 Service Pack 3 and later

The service packs for SQL Server 2008 and SQL Server 2008 R2 address the BEAST vulnerability.

Troubleshooting an Oracle server

When you upgrade a BMC 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

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*