IBM Cognos 8.4 异常的搜集与解决

8244

　　一、CAM-CRP-1085 验证是否已载入安全提供程序类时发生错误。 原因：java.lang.ClassNotFoundException: org.bouncycastle134.jce.provider.BouncyCastleProvider：
　　


 

 

解决方法：在D:\Program Files\cognos\c8\CS7Gateways\目录下添加cognos.ini文件，写入以下字符串：

[Databases]

MyProjectDB=^User ID:^?Password:;LOCAL;OR;ORACLE@%s@orcl/%s@COLSEQ=





其中"MyProjectDB"为数据源名称，绿色部分为连接字符串，可以在配置数据源的时候得到，复制下来就可以了。







三、启动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：

[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'