This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.
BladeLogic Decision Support for Server Automation (5 Report Viewers, 1 Query Studio)
BMC BladeLogic Decision Support for Server Automation (5 Report Viewers, 1 Query Studio)
This problem can surface in a number of ways with BDSSA:
1) When attempting to run reports:
QE-DEF-0285 The logon failed
DPR-ERR-2082 An error has occurred. Please contact your administrator. The complete error has been logged by CAF with SecureErrorID:2010-09-15-13:37:21.672-#49
The cogserver.log file located in reports/logs contains the following exception from the same time as the attempted report run:
Original Error: QE-DEF-0285 The logon failed.
QE-DEF-0325 The logon failed for the following reason:
RQP-DEF-0068 Unable to connect to at least one database during a multi-database attach to 1 database(s) in: ORA75
UDA-SQL-0432 Unable to locate the gateway "libcogudaor".
In Windows environments, the library is named "cogudaor", so the UDA-SQL-0432 message reads:
UDA-SQL-0432 Unable to locate the gateway "cogudaor".)
2) When installing the product:
[java] Importing archive blreports_basic_content_store_1337716455862... Please wait...
[java] Successfully imported ::blreports_basic_content_store
[java] Assigned system admin role successfully...
[java] Trying again to create datasource ...
3) When running the 4_UPDATE_COGNOS step of ETL (nsh update_cognos_model_properties.nsh).
In this case, the error is the following in reports/logs/update_cognos_model_properties.log:
############# Script Player #############
Transaction count: 21
SetActiveLocale successful, continuing...
BME-SP-0007 An unknown error occurred during execution.
BME-SP-0028 All applied changes will be saved.
4) During Cognos Startup. In this case, the following will be displayed in the cogserver.log
Audit.RTUsage.RSVP Response ReportService Failure QE-DEF-0285 The logon failed.QE-DEF-0325 The logon failed for the following reason:RQP-DEF-0068 Unable to connect to at least one database during a multi-database attach to 1 database(s) in: testDataSourceConnection UDA-SQL-0031 Unable to access the "testDataSourceConnection" database.UDA-SQL-0107 A general exception has occurred during the operation "attach".
Legacy ID:KA312975This error can have many root causes as it usually means that something has gone wrong with communication between the BDSSA Server and the Portal DB. This article attempts to provide a solution to the most common cause and also links to an IBM Cognos article on other causes.
If this error suddenly begins occurring in a previously-functioning environment, or is otherwise intermittent in nature, there may be an issue with db-connectivity such as the maximum number of Oracle processes being exceeded, a problem with the Oracle listener or a db-password change etc. In this case, the BDSSA services should be restarted and the issue retested. If the issue persists after the restart, attempt to login to the Portal DB instance from sqlplus on the BDSSA Server as the BSARA_PORTAL DB user. If this fails, it proves there is an issue connecting to the PORTAL DB instance and this issue is also affecting the viewing of reports. The site DBA should be consulted to assist with the sqlplus issue. If the issue is resolved after the restart but reoccurs after a period of time, ask the site DBA whether there are any alerts on the DB side regarding any DB resource thresholds being exceeded.
If this issue occurs in a new BDSSA environment where no reports have ever been run successfully, then this suggests a problem with the Oracle Client setup on the BDSSA Server.
The most common Oracle Client configuration issue which causes this problem in a new environment is the attempted use of a 64-bit Oracle client installation. The following note is from the BDSSA 8.1 installation guide for Oracle:
IBM Cognos 8.4 BI 64-bit application requires third party 32-bit libraries. The 64-bit Oracle database client must provide 32-bit libraries.
Unix/Linux BDSSA Servers:
To determine if this is the issue on a Linux/Solaris BDSSA Server, perform the following steps:
cd <reports install dir>/portal/bin
ldd libcogudaor10.so (or libcogudaor11.so)
Check for any errors or missing/broken links. The most common problem is "libclntsh.so.10.1 => not found" e.g.
[root@bsaraserv1 bin]# ldd libcogudaor10.so
libCCLCFGAPI.so => ./libCCLCFGAPI.so (0x00dfe000)
libCAM_Crypto_Interface.so => ./libCAM_Crypto_Interface.so (0x0020e000)
libcogudasql.so => ./libcogudasql.so (0x00387000)
libCCLCore.so => ./libCCLCore.so (0x0071f000)
libQEGeneral.so => ./libQEGeneral.so (0x00e95000)
libCCLIDOM.so => ./libCCLIDOM.so (0x008ff000)
libxerces-c.so.27 => ./libxerces-c.so.27 (0x00f79000)
libclntsh.so.10.1 => not found
libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00111000)
In this case, the first thing to check is that the library reported as "not found" actually exists on the BDSSA Server and is the 32 bit version e.g.
[root@bsaraserv1 /]# cd $ORACLE_HOME/lib
[root@bsaraserv1 lib]# ls -l libclntsh*
lrwxrwxrwx 1 oracle oinstall 40 Nov 13 2009 libclntsh.so -> /opt/oracle/oracle/lib/libclntsh.so.10.1
-rwxrwx--- 1 oracle oinstall 18435772 Nov 13 2009 libclntsh.so.10.1
[root@bsaraserv1 lib]# file libclntsh.so.10.1
libclntsh.so.10.1: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), not stripped
If the library or its link are missing or only the 64 bit version is installed, the 32 bit version must be installed. A few options exist here:
1) If the 64 bit Oracle client is installed, either uninstall it and install the 32 bit version or reinstall it in such a way that it installs both the 32 bit libraries ( in $ORACLE_CLIENT/lib32) as well as the 64 bit libraries (in $ORACLE_CLIENT/lib). The site DBA can usually assist with this.
2) If the 64 bit and 32 bit Oracle client libraries are both already installed, make sure the $BLREPORTS_HOME/Environment file's LD_LIBRARY_PATH references the 32 bit versions of the Oracle Client libraries before the 64 bit versions. e.g.
If changes are made to this file, restart the BDSSA services before retesting so they are picked up.
Note: Before Reports will work, the "ldd libcogudaor10.so" command run above must succeed with no errors.
Windows BDSSA Servers:
If it has is suspected that the 64 bit Oracle Client has been installed on the Windows BDSSA Server, run through the following steps:
1. Logon to Portal DB via SQl*Plus from BDSSA Server as BSARA_PORTAL user. This will confirm whether the Oracle client is 64-bit Production or 32-bit Production;
2. Uninstall 64-bit Oracle client;
3. Install 32-bit Oracle Client.
If both the 64-bit and 32 bit client exist on the BDSSA Server, make sure the 32 bit client's directories appear in the PATH before the 64 bit directories and that ORACLE_HOME points to the 32 bit client location..
The Dependency Walker tool is very useful for tracking this issue down in a Windows environment. Download and install Dependency Walker and point it to the following dll: Reports\portal\bin\cogudaor.dll. One of the dlls which cogudaor.dll depends on is the Oracle Client OCI.DLL file. In Dependency Walker make sure the copy of OCI.DLL being loaded is the one in the expected Oracle Client directory and not a stray dll in locations such as c:\windows\. c:\windows\system32 or c:\
Other possible causes of Cognos Error: QE-DEF-0285:
Aside from the use of 64-bit libraries, there are other reasons this error may occur. Please see the following IBM Cognos article for further details:
- BMC BladeLogic Decision Support for Server Automation (5 Report Viewers, 1 Query Studio)
- BMC BladeLogic Reporting and Analytics Manager