Known Issues › Known Configuration Issues › Configuration Failure on 64-bit Oracle

Configuration Failure on 64-bit Oracle

Valid on 64-bit Oracle 11g R1 and 11g R2

Symptom:

The configuration fails and the following error messages appear on 64-bit Oracle:

• In the stdlog: "Unable to connect to Oracle database mdbadmin on server"
• In the checkdb.0 log: “Unable to load the OCI library or DLL. Cannot continue!”

Solution:

Install the latest 32-bit Oracle client, and do the following:

• On Windows, verify that the path includes the directory for the 32-bit Oracle libraries.
• On UNIX, set the library path variable so it points to the 32-bit Oracle library.

Note: The problem can also occur when migrating from a previous release of CA SDM. If the error occurs during migration, install the client and run the migration.

bopauth_nxd Does not Run When Moved from Background Server

Symptom:

I have setup advanced availability configuration for the CA SDM environment. I logged in to the background server and navigated to Options Manager, Security from the Administration tab. I changed the bopauth_host value from default to point to an application server. I restarted all the CA SDM servers. bopauth_nxd is not running on the application server.

Solution:

When bopauth_nxd is moved from background server to any other server (such as the application server) complete the following steps:

1. Restart the background server after changing the default value of bopauth_host.
2. Start version control as a client on the application server using the following command:

   pdm_ver_nxd -c
   

3. Restart the application server.

LDAP Virtual Database Does not Run When Moved from Background Server

Symptom:

I have setup advanced availability configuration for the CA SDM environment. I logged in to the background server and navigated to Options Manager, Security from the Administration tab. I changed the ldap_virtdb_host value from default to point to an application server. I restarted all the CA SDM servers. LDAP Virtual Database is not running on the application server.

Solution:

When LDAP Virtual Database is moved from background server to any other server (such as the application server) complete the following steps:

1. Restart the background server after changing the default value of ldap_virtdb_host.
2. Start version control as a client on the application server using the following command:

   pdm_ver_nxd -c
   

3. Restart the application server.