Skip to Content

Troubleshooting data warehouse database issues

This section describes issues that you might encounter when working with the data warehouse database.

32-bit application error in Oracle RAC environments

An error message similar to the following might appear when using the product in Oracle RAC environments.

Database error: (CS) "DBDriver failed to load: C:\Program Files (x86)\SAP BusinessObjects\SAP BusinnessObjects Enterprise XI 4.0\dataAccess\connectionServer\drivers\lib64\dbd_oci.lll (%1 is not a valid Win32 application.)". (IES 10901)

This error occurs if you have a 32-bit Oracle client installed on the computer on which the BusinessObjects BI server exists in your environment. You must have a 64-bit Oracle client installed.

To resolve this issue, complete the following procedure:

  1. Uninstall the 32-bit Oracle client from the computer on which the BusinessObjects BI server is installed.
  2. Install a 64-bit Oracle client on the computer with the Administrator option selected.
  3. Restart the BusinessObjects BI services by using the instructions in Restarting-the-BusinessObjects-services.

JDBC driver error occurs while running a report

If the JDBC drivers are not configured correctly, an error message similar to the following one appears while running a report .

Database error: No suitable driver found for jdbc: <database_specific_label> (IES 10901)

If the class path for the driver file is not correctly defined, an error message similar to the following one appears while running a report .

Database error: "Java class not found in classpath: <database_specific_driver>." (IES 10901)

See Configuring-the-BusinessObjects-server-JDBC-drivers for the correct procedure.

Schema changes

BMC does not recommend, nor does it support database schema changes for the data warehouse database.

 

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

BMC Decision Support - Database Automation 8.3