Common Cognos errors

L FAQs:

UCM-CFG-5137: Content Manager was unable to complete the initialization of

Content store.

Solution:

1. Ensure that all Cognos 8 Services are stopped.

2. Have the DBA make a backup the Content Store.

3. Have the DBA runInstall_path\ Configuration \ schemas \ content \DbVendor\ DbClean _DbVendor. SQL script on the Content Store database.

4. Start the Cognos 8 with Cognos Configuration.

 

UCM-CFG-5063: The Database User Configuration permissions are insufficient.

Solution:

Must ensure that Oracle database has the following permissions set:

A) connect to the database
B) create, alter, and drop tables

C) create, alter and drop triggers

D) create, alter and drop views

E) create, alter and drop procedures

F) create, alter and drop sequences

Also, addUnlimited QuotasPermission to oracle content store

Schema if the above steps do not work

 

UCM-SYS-5124: Database encoding method must be UTF-8

Solution: You need to modify the character set of the database in the database. You need the DBA permission to execute the following statement:

Sqlplus/nolog
Conn/as sysdba
Shutdown immediate;
Startup mount;
Alter session set SQL _TRACE = TRUE;
Alter system enable restricted session;
Alter system set JOB_QUEUE_PROCESSES = 0;
Alter system set AQ_TM_PROCESSES = 0;
Alter database open;
Set linesize 120;
Alter database character set INTERNAL_USE UTF8;

Alter session set SQL _TRACE = FALSE;

Shutdown immediate;

STARTUP;

 

UCFG-ERR-0106: IBM Cognos Configuration did not receive a response from the IBM Cognos 8

Service in the time allotted. Check that IBM Cognos 8 service is available and properly configured

Description: The error is returned when the cognos service is started.

 

Solution 1: the connection to the Cognos content database may fail.

Check whether the built-in content database of Cognos is installed in Cognos

If a third-party database is used, check whether the connection string information and driver file are normal.

 

Solution 2: Increase the timeout value.

When neither cogserver. log nor tomcat. log reports an error message

Add
Servicwaitinterval = 1000

ServiceMaxTries = 500

 

UCFG-ERR-0103:

Cause: the main application of Cognos cannot be started. The possible causes are as follows:
1. The Cognos database does not use the character set of UTF-8 (common in Oracle)
2. The Cognos service in the system service is disabled or cannot be started due to restrictions of other third-party software.

UCAM-AAA-0027:

The error is encountered when developing SSO using the Cognos SDK. Use the example TrustedSignonSample program in the SDk.
What I encountered when implementing SSO. According to the Google search results, 0027 may be a Cognos8.3 BUG.
The running Cognos application may suddenly appear. But The error message is different from what I encountered: The function call
'Cam _ AAA_Authenticate 'failed. Reason: "solution to this problem (Baidu searched ):
1. Memory leakage (most likely cause)
If this error is reported suddenly after the server runs normally for a period of time, most of the reasons are memory leakage.
2. configuration error (less likely)
For example, if you configure resources beyond the capabilities of the server for Cognos, this error occurs.
However, it does not conform to our current situation. It is estimated that the cause of this error should be the problem of the SSO interface, but the same error generation is encountered.
Code.
Later, we found that this SDK example is actually a proxy-like method, passing parameters through cookies to log on to another Cognos authentication.
Such as NTLM.
As we thought earlier, TrustedSignonSample is considered as an independent authentication.

Therefore, After configuring a namespace for ts ntlm authentication, it is actually very simple, it should be authentication.
The specified namespace cannot be found, and the number of retries reaches 10.

UCAM-AAA-0064

['Cognosjavaprovider']
1. [ERROR] CAM-AAA-0064 The function 'cam _ AAA_JniAuthProvider: Configure 'failed.
CAM-AAA-0154 Unable to load the Java authentication provider class 'trustedsignonsample '.
TrustedSignonSample (Unsupported major. minor version 49.0)
After 0027 problems were encountered in SDK implementation in 83, I considered switching to the Cognos8.2 production system for trial. The result was 0064,

The version problem cannot be solved.
The JniAuthProvider jar package may be updated to solve this problem.