Mark a startup error of Cognos

I saw someone in the Technical Group asking for help due to a startup error of Cognos:

 

The error message is as follows:

========================================================== ========================================================== ======================================

Launching a JVM using 'maximum memory in mb']
Successfully launched a test JVM with the memory setting of '000000'. Note that this does not guarantee that the IBM Cognos service will start and run successfully.

To see which JVM options are based on this setting, view ibmcognos_location/bin/Bootstrap _ <OS>. xml and see your JVM documentation for an explanation of those options.

[Archive local file system root]
Since the value is empty, the feature is disabled. There is nothing to test.

[Validate Mail Server properties.]
[Error] The Mail Server cannot be reached.

[Archive local file system root]
Since the value is empty, the feature is disabled. There is nothing to test.

[Start Service]
04:35:15, 'logservice', 'startservice', 'success '.
04:35:18, CAF-WRN-0010 caf Input Validation enabled.
04:35:18, CAF-WRN-0021 caf third party XSS checking disabled.
04:35:43, CM-SYS-2057 creating content store tables (schema version 7.0019 ).
04:36:04, CM-CFG-5063 a Content Manager configuration error was detected while connecting to the content store. CM-CFG-5023 Content Manager is unable to initialize the content store by using the initialization file "/Cognos/configuration/schemas/content/Oracle/dbinitscript_oracle. SQL ". review the configuration for the content store database in IBM Cognos configuration to ensure that the settings are correct. verify that the account used to access the content store is still valid by checking the status of the password and account permissions. verify that the account that Content Manager uses has sufficient permissions to create, to connect to, and to initialize the file contents in the database. cause: ORA-00955: Name is already used by an existing object stack trace: Java. SQL. sqlexception: ORA-00955: Name is already used by an existing object at oracle. JDBC. dbaccess. dberror. throwsqlexception (dberror. java: 189) at oracle. JDBC. ttc7.ttioer. processerror (ttioer. java: 242) at oracle. JDBC. ttc7.oall7. receive (oall7.java: 554) at oracle. JDBC. ttc7.ttc7protocol. dooall7 (ttc7protocol. java: 1478) at oracle. JDBC. ttc7.ttc7protocol. parseexecutefetch (ttc7protocol. java: 888) at oracle.jdbc.driver.oraclestatement.exe cutenonquery (oraclestatement. java: 2076) at oracle. JDBC. driver. oraclestatement. doexecuteother (oraclestatement. java: 1986) at oracle. JDBC. driver. oraclestatement. doexecutewithtimeout (oraclestatement. java: 2697) at oracle.jdbc.driver.oraclestatement.exe cute (oraclestatement. java: 1100) at com.cognos.cm.dbstore.cmpreparedstatementbase.exe cute (cmpreparedstatementbase. java: 59) at com.cognos.cm.dbstore.statementproxy.exe cute (statementproxy. java: 276) at com.cognos.cm.dbstore.cmdbstorefactory.exe cutescript (cmdbstorefactory. java: 438) at com.cognos.cm.dbstore.cmdbstorefactory.exe cutescript (cmdbstorefactory. java: 290) at com. cognos. cm. dbstore. cmdbstorefactory. initdatabasecontentdependent (cmdbstorefactory. java: 1449) at com. cognos. cm. dbstore. cmdbstorefactory. initcontentdependent (cmdbstorefactory. java: 2129) at com. cognos. cm. dbstore. cmdbstore. initializecontentdependent (cmdbstore. java: 4432) at com. cognos. cm. server. cmservlet. initializecontentstoreforactive (cmservlet. java: 2192) at com. cognos. cm. server. cmservlet. init (cmservlet. java: 1892) at com. cognos. cm. server. contentmanager. start (contentmanager. java: 436) at com. cognos. cm. server. contentmanagerlifecyclehandler. start (contentmanagerlifecyclehandler. java: 65) at com. cognos. pogo. services. defaulthandlerservice. start (defaulthandlerservice. java: 88) at com. cognos. pogo. services. dispatcherservices. startinitialservice (dispatcherservices. java: 418) at com. cognos. pogo. services. dispatcherservices. startinititalservices (dispatcherservices. java: 404) at com. cognos. pogo. transport. pogoservlet $ pogostartup. run (pogoservlet. java: 803) at com. cognos. pogo. util. threads. safethread. saferun (safethread. java: 70) at com. cognos. pogo. util. threads. safethread. run (safethread. java: 61)
04:36:04, 'contentmanagerservice', 'startservice', 'failed '.

========================================================== ========================================================== ======================================

 

I probably got an error message.

There is such an ibmcognos_location/bin/Bootstrap _ <OS>. xml

I thought it was a previous user error case, but it was caused by the fact that the database character set was not UTF-8 (I would like to remind Cognos users again that the Cognos content library must be a UTF-8 database)

However, the error message is as follows:

A Content Manager configuration error was detected while connecting to the content store. CM-CFG-5023 Content Manager is unable to initialize the content store by using the initialization file "/Cognos/configuration/schemas/content/Oracle/dbinitscript_oracle. SQL ". review the configuration for the content store database in IBM Cognos configuration to ensure that the settings are correct. verify that the account used to access the content store is still valid by checking the status of the password and account permissions.

 

If you understand a little English, you can see that the initialization SQL of dbinitscript_oracle. SQL has a problem.

Generally, this problem should not occur.

According to the description of the questioner, the user creates a content library using the Oracle system user.

The problem is that dbinitscript_oracle. SQL does not support system execution for SQL writing? (Haha, not the best excavator Technology)

With questions, I tested the system in this machine and directly used the System user to execute dbinitscript_oracle. SQL

Then an error is displayed.

The original root cause of the error was the Oracle ORA-04089 error.

This error occurs when sys is used, and trigger created by system occurs.

This is an oracle limitation. Why do users such as sys need to be restricted from creating triggers?

 

Okay, the error is clear.

Therefore, to configure the Cognos content library, you can create a common user.

However, it is easy for some people to create new users and grant the DBA permission directly.

In fact, the user of the Cognos content Library only needs the following four permissions.

 

Okay. This article is complete !~

Mark a startup error of Cognos