cdn007
作者cdn007·2010-05-10 20:48
软件架构设计师·CA

【原创】直击Cognos CM-CFG-5063 (Cognos 启动异常)

字数 4911阅读 5786评论 1赞 0

问题描述:
今天重新安装了一台Cognos的测试机,启动Cognos时居然报CM-CFG-5063,启动异常(具体log参见附1),网上搜索解决方案未果,现对这一问题做一小结,并提供本人的解决方案,供后来者参考!

可能的原因(Cognos CM-CFG-5063 ):
1、Content Manager 没有配置或配置不正确
2、表空间问题或者用户权限问题
3、字符集问题,字符集应该为UTF-8
4、内容库的其他问题,建议重建内容库
5、数据库问题,建议重装数据库
6、其他的可能(参见附2)

解决方案:
因本人使用的数据库为DB2,所以如果你也使用DB2做Cognos内容库,那么以下方案便是不错的选择,具体操作如下(为最快的解决你的问题,请严格遵守以下步骤):
1、重建Cognos内容库(详细命令参见附3)
    a、删除原来的数据库实例
    b、创建content DB , the codeset must be UTF-8 for DB2.
    c、更新heap size
    d、创建buffer pool,页大小为32K
    e、创建系统临时表空间,页大小为32K
   f、创建用户临时表空间,页大小为4K
    g、创建一个常规的用户表空间,页大小为4K
2、停止数据库
3、拷贝数据库连接驱动db2java 到 cognos path
4、启动数据库
5、开始cognos configuration
6、测试content manager-->OK
7、启动cognos server-->OK

附1(log):
[Launching a JVM using 'Maximum memory in MB']
1. Successfully launched a test JVM with the memory setting of '768'. Note that this does not guarantee that Cognos 8 will start and run successfully.

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

[Archive Local File System Root]
1. Since the value is empty, the feature is disabled. There is nothing to test.

[Start Service]
1. 10:54:12, 'LogService', 'StartService', 'Success'.
2. 10:54:19, CM-CFG-5063 A Content Manager configuration error was detected while connecting to the content store.
CM-CFG-5063 A Content Manager configuration error was detected while connecting to the content store.
CM-CFG-5137 Content Manager was unable to complete the initialization of the content store. For more information, review the log file. Before you restart Content Manager, you may need to recreate the content store database or clean it using dbClean_*.sql.
3. 10:54:19, 'ContentManager', 'getActiveContentManager', 'Failure'.
DPR-CMI-4006 Unable to determine the active Content Manager. Will retry periodically.
4. 10:54:19, 'com.cognos.pogo.contentmanager.coordinator.ActiveCMControl', 'pogo', 'Failure'.
DPR-DPR-1035 Dispatcher detected an error.

5. 10:54:45, 'ContentManagerService', 'StopService', 'Success'.
6. 10:54:45, 'ContentManagerService', 'StopService', 'Success'.
7. 10:54:45, 'CPS Producer Registration Service', 'StopService', 'Success'.
8. 10:54:45, 'CPS Producer Registration Service', 'StopService', 'Success'.
9. 10:54:45, 'MonitorService', 'StopService', 'Success'.
10. 10:54:45, 'MonitorService', 'StopService', 'Success'.
11. 10:54:45, 'DeliveryService', 'StopService', 'Success'.
12. 10:54:45, 'DeliveryService', 'StopService', 'Success'.
13. 10:54:46, 'EventService', 'StopService', 'Success'.
14. 10:54:46, 'EventService', 'StopService', 'Success'.
15. 10:54:46, 'JobService', 'StopService', 'Success'.
16. 10:54:46, 'JobService', 'StopService', 'Success'.
17. 10:54:46, 'com.cognos.pogo.services.DefaultHandlerService', 'pogo', 'Failure'.
DPR-DPR-1035 Dispatcher detected an error.

18. 10:54:46, 'com.cognos.pogo.services.DefaultHandlerService', 'pogo', 'Failure'.
DPR-DPR-1035 Dispatcher detected an error.

19. 10:54:46, 'SystemService', 'StopService', 'Success'.
20. 10:54:46, 'SystemService', 'StopService', 'Success'.
21. 10:54:46, 'BatchReportService', 'StopService', 'Success'.
22. 10:54:46, 'BatchReportService', 'StopService', 'Success'.
23. 10:54:46, 'ReportService', 'StopService', 'Success'.
24. 10:54:46, 'ReportService', 'StopService', 'Success'.
25. 10:54:46, 'ReportDataService', 'StopService', 'Success'.
26. 10:54:46, 'ReportDataService', 'StopService', 'Success'.
27. 10:54:46, 'LogService', 'StopService', 'Success'.
28. 10:54:46, 'LogService', 'StopService', 'Success'.

附2(其他的可能原因):
1、在测试中发现用SQL Server也会报这个错,怀疑有两个可能:1.数据库中未创建ContentStore所需的那些表,如果是这种情况,需要按cognos文档中的方法运行创建表的script命令;2.数据库使用的是Express版本,这种可能性较小,但如果是这种情况换用标准版就能解决
2、如果是针对Oracle,可以再试一下下面这种建议:表空间问题(设置为自动增长)或者用户权限问题
3、数据库的端口跟C8配置的端口号不一致
4、Cognos数据库没有采用UTF-8的字符集(Oracle下常见)
5、系统服务中的Cognos服务被禁用,或受到其他第三方软件限制无法启动

遇到类似问题建议处理步骤如下:
1、在安装目录的logs文件夹(...c8logs)中查看相关日志,如“cbs_start.log”,通常在日志文件中会有出错的较详细信息;
2、若能够在日志中直接获知错误原因,解决;否则在IBM官方站点搜索日志文件中的相关错误码,大多数问题都能找到解决方案;
3、由于出错诱因可能有多个,最好采用一一排除的解决思路。

附3(Detail cmd):
type DB2CMD in command line

setp:
---------------------
db2 CREATE DATABASE cognos AUTOMATIC STORAGE YES ON 'C:' DBPATH ON 'C:' USING CODESET UTF-8 TERRITORY US COLLATE USING SYSTEM PAGESIZE 32768

db2 connect to cognos user db2admin using root

db2 UPDATE DATABASE CONFIGURATION USING APPLHEAPSZ 1024 AUTOMATIC IMMEDIATE
db2 UPDATE DATABASE CONFIGURATION USING LOCKTIMEOUT 240 DEFERRED

db2 CREATE BUFFERPOOL COGBUF IMMEDIATE SIZE 250 PAGESIZE 32 K

db2 CREATE SYSTEM TEMPORARY TABLESPACE COGSTEMP PAGESIZE 32 K MANAGED BY AUTOMATIC STORAGE EXTENTSIZE 32 OVERHEAD 10.5 PREFETCHSIZE 32 TRANSFERRATE 0.14 BUFFERPOOL COGBUF

db2 CREATE USER TEMPORARY TABLESPACE COGUTEMP PAGESIZE 32 K MANAGED BY AUTOMATIC STORAGE EXTENTSIZE 32 OVERHEAD 10.5 PREFETCHSIZE 32 TRANSFERRATE 0.14 BUFFERPOOL COGBUF
----------------
The end.

如果觉得我的文章对您有用,请点赞。您的支持将鼓励我继续创作!

0

添加新评论1 条评论

housheng33housheng33软件开发工程师农行软件开发中心
2013-07-22 09:07
[Launching a JVM using 'Maximum memory in MB']

本来运行了好久的cognos ,用不了了!
重新启动,也报上面那个错。
后来发现是db2库被停了。
启动DB2,db2start
再启动COGNOS,OK
Ctrl+Enter 发表

作者其他文章

相关问题

相关资料

X社区推广