Reports Integration Guide › Troubleshooting › CA Business Intelligence: I Cannot Choose an Existing Database Server

CA Business Intelligence: I Cannot Choose an Existing Database Server

Symptom:

You want to use an existing database server. You do not want to install a new MySQL database server.

But when you run the CA Business Intelligence Setup wizard, the ODBC System DSN for your existing database server is not listed in the CMS Database Information screen.

Reason:

There are several possible reasons:

• There is no ODBC connection to your DBMS. You must specify a 32-bit ODBC System DSN to connect to your DBMS before you install CA Business Intelligence.
• The ODBC connection is using the default 64-bit ODBC, not a 32-bit ODBC.
• The ODBC connection is not defined as a System DSN.

Solution: 1

Specify a 32-bit ODBC System DSN to connect to your DBMS.

If you not running the CA Business Intelligence Setup wizard, create a new ODBC System DSN on your BusinessObjects reports server. This ODBC connection connects to the database server that you want to use. Then rerun the CA Business Intelligence Setup wizard.

If you already running the CA Business Intelligence Setup wizard:

1. Pause in the CMS Database Information screen.
2. Create a ODBC System DSN on your BusinessObjects reports server. This ODBC connection connects to the database server that you want to use.

   Note: For SQL Server, your ODBC connection must point to a new database, typically named BOE120. BusinessObjects Enterprise must connect to this database as the owner.

3. Force a refresh of the CMS Database Information screen so that it includes the ODBC connection you want.

   To refresh the screen, go back to the previous wizard screen (the Server Intelligence Agent screen). Then return to the CMS Database Information screen.

   The ODBC connection to your DBMS is now listed on the CMS Database Information screen.

4. Specify the ODBC connection to your DBMS and continue with the CA Business Intelligence installation.

Solution: 2

Verify the ODBC connection is correctly defined. On a 64-bit server:

• Verify that the ODBC connection is using a 32-bit ODBC, not the default 64-bit ODBC.

  The 32-bit ODBC is typically located in %SystemRoot%\SysWOW64\odbcad32.exe,

• Verify that the ODBC connection is defined as a System DSN.

Solution: 3

An Oracle CA Data Protection CMS must use a 32-bit ODBC System DNS to connect to your BusinessObjects CMS. To allow the CA Data Protection CMS to connect using 32-bit Oracle client software, the tnsnames.ora file must include an entry for the CA Data Protection CMS database. You must also specify the location of tnsnames.ora in the registry.

Details about tnsnames.ora are included in the Requirements section for CA Business Intelligence.

More information:

Add a CA Data Protection CMS Entry to Tnsnames.ora