CogKnowHow

Product:

Cognos BI 10.1.1

Framework Manager

Oracle 11g

 

Symptom:

Data source connection in Cognos Connection is working.

Framework Manager is installed on a workstation.

But when you connect to a Oracle data source you get a error message.

Error Message:

QE-DEF-0285 The logon failed.
QE-DEF-0323 The DSN(ODBC)/ServiceName is invalid. Either the DSN is missing or the host is inaccessible.
RQP-DEF-0068 Unable to connect to at least one database during a multi-database attach to 1 database(s) in:
FM1
UDA-SQL-0031 Unable to access the “FM1” database.
UDA-SQL-0532 Data Source is not accessible: “DRPDB”.
ORA-12154: TNS:could not resolve the connect identifier specified

 

Above is when tnsnames.ora is missing.

 

Other error message:

QE-DEF-0285 The logon failed.
QE-DEF-0323 The DSN(ODBC)/ServiceName is invalid. Either the DSN is missing or the host is inaccessible.
RQP-DEF-0068 Unable to connect to at least one database during a multi-database attach to 1 database(s) in:
FM1

UDA-SQL-0432 Unable to locate the gateway “cogudaor”.

Above is when oracle client folder is not in windows path.

 

Solution:

Ensure you have installed the full 32 bit Oracle 11g administrator client on the computer where Cognos FrameWork Manager is installed. Framework Manager only works with the 32 bit Oracle client.

 

Ensure that you have the added the path to the bin folder of the Oracle client to windows system path e.g. \oracle\product\11.2.0\client_1\bin.

The path can be pointing to a old Oracle client installation, ensure the BIN folder exist in the path.

 

Ensure that the tnsnames.ora file is updated and contain the reference to the oracle database that is used in cognos connection. Best is to copy the tnsnames.ora file from the Cognos BI server to workstation where you have Cognos Framework manager installed. Place the tnsnames.ora file in folder \oracle\product\11.2.0\client_1\network\admin\.  Ensure that tnsnames.ora file is in the oracle client folder that is in use, and that are referenced from the path variable.

 

Exit Framework manager program before you test again, to ensure the changes have taken affect.

 

More information:

http://www-01.ibm.com/support/docview.wss?uid=swg21341734

Product:

IBM Cognos BI 10.1.1

Windows 2008 R2 server

Microsoft SQL 2008 database server

 

Symptom:

Error when you run a report or test data source in Cognos connection.

Query Mode

Microsoft SQL server (SQL 2005 Native Client) /Compatible…. Failed

Microsoft SQL server (JDBC) / Dynamic………………………………. Succeeded

 

Error message:

QE-DEF-0322 The connection string is invalid.RQP-DEF-0068 Unable to connect to at least one database during a multi-database attach to 1 database(s) in: great_outdoors_sales UDA-SQL-0031 Unable to access the “great_outdoors_sales” database. Check that the connection parameters to the database are configured correctly. For example, ensure that the data source connection contains the signon information, such as a password, to connect to the database.UDA-SQL-0534 Invalid connection string.UDA-SQL-0206 The OLEDB driver returned the following value: HRESULT= -2147221164″.RSV-SRV-0042 Trace back:RSReportService.cpp(722): QFException: CCL_CAUGHT: RSReportService::process()RSReportServiceMethod.cpp(263): QFException: CCL_RETHROW: RSReportServiceMethod::process(): reportEditQuery_RequestRSASyncExecutionThread.cpp(808): QFException: RSASyncExecutionThread::checkExceptionRSASyncExecutionThread.cpp(260): QFException: CCL_CAUGHT: RSASyncExecutionThread::runImpl(): reportEditQuery_RequestRSASyncExecutionThread.cpp(864): QFException: CCL_RETHROW: RSASyncExecutionThread::processCommand(): reportEditQuery_RequestExecution/RSRenderExecution.cpp(670): QFException: CCL_RETHROW: RSRenderExecution::executeAssembly/RSDocAssemblyDispatch.cpp(291): QFException: CCL_RETHROW: RSDocAssemblyDispatch::dispatchAssemblyAssembly/RSLayoutAssembly.cpp(79): QFException: CCL_RETHROW: RSLayoutAssembly::assembleAssembly/RSDocAssemblyDispatch.cpp(358): QFException: CCL_RETHROW: RSDocAssemblyDispatch::dispatchChildrenAssemblyForwardAssembly/RSReportPagesAssembly.cpp(179): QFException: CCL_RETHROW: RSReportPagesAssembly::assembleAssembly/RSDocAssemblyDispatch.cpp(308): QFException: CCL_RETHROW: RSDocAssemblyDispatch::dispatchAssemblyAssembly/RSPageAssembly.cpp(303): QFException: CCL_RETHROW: RSPageAssembly::assembleAssembly/RSDocAssemblyDispatch.cpp(308): QFException: CCL_RETHROW: RSDocAssemblyDispatch::dispatchAssemblyAssembly/RSTableRowAssembly.cpp(177): QFException: CCL_RETHROW: RSTableRowAssembly::assembleAssembly/RSDocAssemblyDispatch.cpp(308): QFException: CCL_RETHROW: RSDocAssemblyDispatch::dispatchAssemblyAssembly/RSTableCellAssembly.cpp(137): QFException: CCL_RETHROW: RSTableCellAssembly::assembleAssembly/RSDocAssemblyDispatch.cpp(358): QFException: CCL_RETHROW: RSDocAssemblyDispatch::dispatchChildrenAssemblyForwardAssembly/RSDocAssemblyDispatch.cpp(308): QFException: CCL_RETHROW: RSDocAssemblyDispatch::dispatchAssemblyAssembly/RSAssembly.cpp(662): QFException: CCL_RETHROW: RSAssembly::createListIteratorAssembly/RSAssembly.cpp(717): QFException: CCL_RETHROW: RSAssembly::createListIteratorRSQueryMgr.cpp(1055): QFException: CCL_RETHROW: RSQueryMgr::getListIteratorRSQueryMgr.cpp(1131): QFException: CCL_RETHROW: RSQueryMgr::getResultSetIteratorRSQueryMgr.cpp(1295): QFException: CCL_RETHROW: RSQueryMgr::createIteratorRSQueryMgr.cpp(1569): QFException: CCL_RETHROW: RSQueryMgr::executeRsapiCommandRSQueryMgr.cpp(1559): QFException: CCL_RETHROW: RSQueryMgr::executeRsapiCommandRSQueryMgrExecutionHandlerImpl.cpp(168): QFException: CCL_RETHROW: RSQueryMgrExecutionHandlerImpl::execute()RSQueryMgrExecutionHandlerImpl.cpp(160): QFException: CCL_RETHROW: RSQueryMgrExecutionHandlerImpl::execute()QFSSession.cpp(1147): QFException: CCL_RETHROW: QFSSession::ProcessDoRequest()QFSSession.cpp(1145): QFException: CCL_CAUGHT: QFSSession::ProcessDoRequest()QFSSession.cpp(1102): QFException: CCL_RETHROW: QFSSession::ProcessDoRequest()QFSSession.cpp(1078): QFException: CCL_RETHROW: QFSSession::ProcessDoRequest()QFSConnection.cpp(788): QFException: CCL_RETHROW: QFSConnection::ExecuteQFSQuery.cpp(213): QFException: CCL_RETHROW: QFSQuery::Execute v2CoordinationQFSQuery.cpp(2024): QFException: CCL_RETHROW: QECoordinationQFSQuery.cpp(4350): QFException: CCL_RETHROW: CoordinationQFSQuery::CallProviderQFSQuery.cpp(246): QFException: CCL_RETHROW: QFSQuery::EXecute v3Source/RQP_QFSQuery.cpp(492): QFException: CCL_RETHROW: QESource/QE_RsApi.cpp(3604): QFException: CCL_RETHROW: QESource/QE_RsApi.cpp(3552): QFException: CCL_RETHROW: QESource/QEI_ConnectionFault.cpp(814): QFException: CCL_THROW: QE

 

Cause:

Have only installed the JAVA SQL driver (sqljdbc4.jar) on the Cognos BI servers.

Solution:

Install the Microsoft SQL native client on the Cognos BI servers.

Run sqlncli_x64.msi as administrator on the Cognos BI server.

Download the driver from Microsoft

http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=17943

Product:

Cognos BI 10.1.1

Cognos Tm1 9.5.2

 

Symptom:

When starting TM1 architect , or when surf to Cognos Connection, they are not allowed to login,

 

Error message:

Exception occurred: java.lang.IncompatibleClassChangeError

Error in cogserver.log file:

10.240.17.54:9300      980      2012-01-09 09:47:41.171       +1        na        na                                Thread-93       DISP    6235    1          Audit.Other.dispatcher.DISP.pogo            pogo    com.cognos.pogo.contentmanager.coordinator.ActiveCMControl               Failure <messages><message><messageString>DPR-DPR-1035 Dispatcher detected an error.</messageString></message><message><messageString>DPR-DPR-1004 Expecting a BI Bus XML response but got:   &lt;html&gt;&lt;head&gt;&lt;title&gt;Apache Tomcat/6.0-snapshot – Error report&lt;/title&gt;&lt;style&gt;&lt;!–H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}–&gt;&lt;/style&gt; &lt;/head&gt;&lt;body&gt;&lt;h1&gt;HTTP Status 500 – &lt;/h1&gt;&lt;HR size=&quot;1&quot; noshade=&quot;noshade&quot;&gt;&lt;p&gt;&lt;b&gt;type&lt;/b&gt; Exception report&lt;/p&gt;&lt;p&gt;&lt;b&gt;message&lt;/b&gt; &lt;u&gt;&lt;/u&gt;&lt;/p&gt;&lt;p&gt;&lt;b&gt;description&lt;/b&gt; &lt;u&gt;The server encountered an internal error () that prevented it from fulfilling this request.&lt;/u&gt;&lt;/p&gt;&lt;p&gt;&lt;b&gt;exception&lt;/b&gt; &lt;pre&gt;javax.servlet.ServletException: Content Manager has not been started. com.cognos.cm.server.ContentManager.notStartedResponse(ContentManager.java:569)             com.cognos.cm.server.ContentManager.doPost(ContentManager.java:137)             javax.servlet.http.HttpServlet.service(HttpServlet.java:637)             javax.servlet.http.HttpServlet.service(HttpServlet.java:717)             com.cognos.pogo.isolation.ServletWrapper.service(ServletWrapper.java:258) &lt;/pre&gt;&lt;/p&gt;&lt;p&gt;&lt;b&gt;note&lt;/b&gt; &lt;u&gt;The full stack trace of the root cause is available in the Apache Tomcat/6.0-snapshot logs.&lt;/u&gt;&lt;/p&gt;&lt;HR size=&quot;1&quot; noshade=&quot;noshade&quot;&gt;&lt;h3&gt;Apache Tomcat/6.0-snapshot&lt;/h3&gt;&lt;/body&gt;&lt;/html&gt;</messageString></message></messages>            DPR-CMI-4007 Unable to perform an active Content Manager election on the local IP node. For more information, see the dispatcher and Content Manager detailed logs. Ensure that the local Content Manager service is started.DPR-DPR-1004 Expecting a BI Bus XML response but got: <html><head><title>Apache Tomcat/6.0-snapshot – Error report</title><style><!–H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}–></style> </head><body><h1>HTTP Status 500 – </h1><HR size=”1″ noshade=”noshade”><p><b>type</b> Exception report</p><p><b>message</b> <u></u></p><p><b>description</b> <u>The server encountered an internal error () that prevented it from fulfilling this request.</u></p><p><b>exception</b> <pre>javax.servlet.ServletException: Content Manager has not been started. com.cognos.cm.server.ContentManager.notStartedResponse(ContentManager.java:569)            com.cognos.cm.server.ContentManager.doPost(ContentManager.java:137)            javax.servlet.http.HttpServlet.service(HttpServlet.java:637)            javax.servlet.http.HttpServlet.service(HttpServlet.java:717) com.cognos.pogo.isolation.ServletWrapper.service(ServletWrapper.java:258)</pre></p><p><b>note</b> <u>The full stack trace of the root cause is available in the Apache Tomcat/6.0-snapshot logs.</u></p><HR size=”1″ noshade=”noshade”><h3>Apache Tomcat/6.0-snapshot</h3></body></html> com.cognos.pogo.bibus.CommandExecutionException: DPR-DPR-1004 Expecting a BI Bus XML response but got: <html><head><title>Apache Tomcat/6.0-snapshot – Error report</title><style><!–H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}–></style> </head><body><h1>HTTP Status 500 – </h1><HR size=”1″ noshade=”noshade”><p><b>type</b> Exception report</p><p><b>message</b> <u></u></p><p><b>description</b> <u>The server encountered an internal error () that prevented it from fulfilling this request.</u></p><p><b>exception</b> <pre>javax.servlet.ServletException: Content Manager has not been started. com.cognos.cm.server.ContentManager.notStartedResponse(ContentManager.java:569)            com.cognos.cm.server.ContentManager.doPost(ContentManager.java:137)            javax.servlet.http.HttpServlet.service(HttpServlet.java:637)            javax.servlet.http.HttpServlet.service(HttpServlet.java:717) com.cognos.pogo.isolation.ServletWrapper.service(ServletWrapper.java:258)</pre></p><p><b>note</b> <u>The full stack trace of the root cause is available in the Apache Tomcat/6.0-snapshot logs.</u></p><HR size=”1″ noshade=”noshade”><h3>Apache Tomcat/6.0-snapshot</h3></body></html>          at java.lang.Throwable.<init>(Throwable.java:80)             at java.lang.reflect.InvocationTargetException.<init>(InvocationTargetException.java:77)             at com.cognos.pogo.bibus.CommandExecutionException.<init>(CommandExecutionException.java:32)             at com.cognos.pogo.bibus.BIBusCommand.handleDefaultException(BIBusCommand.java:292)             at com.cognos.pogo.bibus.BIBusCommand.execute(BIBusCommand.java:194)             at com.cognos.pogo.contentmanager.StandbyContentManagerElectionCommand.executeIfLocal(StandbyContentManagerElectionCommand.java:53)             at com.cognos.pogo.contentmanager.coordinator.ActiveCMControl.sendElectCommand(ActiveCMControl.java:239)             at com.cognos.pogo.contentmanager.coordinator.ActiveCMControl.access$100(ActiveCMControl.java:31)             at com.cognos.pogo.contentmanager.coordinator.ActiveCMControl$ElectTask.safeRun(ActiveCMControl.java:250)             at com.cognos.pogo.util.threads.SafeTimerTask.run(SafeTimerTask.java:32)             at java.util.Timer$TimerImpl.run(Timer.java:293) Caused by: com.cognos.pogo.bibus.CommandExecutionException: DPR-DPR-1004 Expecting a BI Bus XML response but got: <html><head><title>Apache Tomcat/6.0-snapshot – Error report</title><style><!–H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}–></style> </head><body><h1>HTTP Status 500 – </h1><HR size=”1″ noshade=”noshade”><p><b>type</b> Exception report</p><p><b>message</b> <u></u></p><p><b>description</b> <u>The server encountered an internal error () that prevented it from fulfilling this request.</u></p><p><b>exception</b> <pre>javax.servlet.ServletException: Content Manager has not been started. com.cognos.cm.server.ContentManager.notStartedResponse(ContentManager.java:569)            com.cognos.cm.server.ContentManager.doPost(ContentManager.java:137)            javax.servlet.http.HttpServlet.service(HttpServlet.java:637)            javax.servlet.http.HttpServlet.service(HttpServlet.java:717) com.cognos.pogo.isolation.ServletWrapper.service(ServletWrapper.java:258)</pre></p><p><b>note</b> <u>The full stack trace of the root cause is available in the Apache Tomcat/6.0-snapshot logs.</u></p><HR size=”1″ noshade=”noshade”><h3>Apache Tomcat/6.0-snapshot</h3></body></html>          at java.lang.Throwable.<init>(Throwable.java:80)             at java.lang.reflect.InvocationTargetException.<init>(InvocationTargetException.java:77)             at com.cognos.pogo.bibus.CommandExecutionException.<init>(CommandExecutionException.java:28)             at com.cognos.pogo.bibus.BIBusCommand.checkResponseContentType(BIBusCommand.java:314)             at com.cognos.pogo.bibus.BIBusCommand.getSinglePartInputStream(BIBusCommand.java:273)             at com.cognos.pogo.bibus.BIBusCommand.getInputStream(BIBusCommand.java:259)             at com.cognos.pogo.bibus.BIBusCommand.parseResponse(BIBusCommand.java:249)             at com.cognos.pogo.bibus.BIBusCommand.processResponse(BIBusCommand.java:242)             at com.cognos.pogo.bibus.BIBusCommand.executeCommand(BIBusCommand.java:204)             at com.cognos.pogo.bibus.BIBusCommand.execute(BIBusCommand.java:190)             … 6 more

 

Fast workaround:

Restart the Cognos BI server or service.

Go to administrative tools on the Windows 2008 server.

Go to services

Find IBM Cognos in the list

Right click and select Restart

Wait 5 minutes and try again

 

Possible Solution:

In a multi server installation of Cognos BI

Ensure that Content Manager is active on all servers where it is installed.

Go into Cognos Configuration

Go to IBM Cognos Services

Set TRUE after Content Manager Service enabled?

Save

Exit and restart the Cognos Bi service.

Repeat on all servers.

 

The primary dispatcher used in a Cognos BI multi server solution must be on a Cognos BI server where the application layer is installed.

Product:
Cognos BI 10.1.1
Windows 2008 R2 Server
IIS

Symptom:
User get a login dialog from the web server (IIS) when they surf to Cognos Connection.
You can not get past the login dialog, even if you enter correct username and password.
This happens after you activated Kerberos to access Cognos BI.

Login Dialog:
User name:
Password:

Cause:
There is duplicated SPN values to the web server (Cognos bi server) in Microsoft Active Directory.
The web server can not handle Kerberos if there are two different user accounts that have the same web server address.

Solution:
Login to a workstation in the network.
Run the command SETSPN -X to list all duplicated addresses.
Check to ensure that the servername is not listed twice for different user accounts.

Enter following command to remove one entry
setspn.exe -D HTTP/Servername.domain.com DOMAIN\useraccount

Replace servername.domain.com and DOMAIN\useraccount with yours values.

You can use the command SETSPN -L USERNAME to find the values for that account in the Active Directory.

Product:
Cognos BI 10.1.1
Windows 2008 R2 server
Oracle 11

Symptom:
Error message when test the connection for the data source.
Oracle / Compatible = Succeeded.
Oracle (JDBC) / Dynamic Failed XQE-DS-0006 Unable to logon to the data source

Error message:
XQE-DS-0006 Unable to logon to the data source
Listener refused the connection with the following error:
ORA-12514 TNS:listener does not currently know of service
requested in connect descriptor

Listener refused the connection with the following error:
ORA-12514 TNS:listener does not currently know of service
requested in connect descriptor

Cause:
When the ORACLE DATABASE have more than one “node” to connect to you may experience similar issues. If you use Service ID in Connection string can give this issue.

Solution:
Change the why you connect to the ORACLE server in JDBC.
In Cognos Connection – Administration – Data Source Connections.
Click on the data link you have issues with.
Click on more (in the right side of Cognos connection)
Click on Set properties
Click on Connection tab
Click on icon right of connection string.
Click on JDBC
Change from Service ID to TNS name alias as Connection type.
Enter TNSname e.g. ORACLENAME.WORLD
Click on Test connection again.
Click TEST button

You should get
Oracle (JDBC) / Dynamic = Succeeded

Click Close

Product:
Cognos BI 10.1.1 64 bits
Windows 2008 R2 server

Symptom:
Get error when test the audit database in Cognos Configuration.
Access to the Content Store on the Microsoft SQL database server works.

Error message:
[Logging]
[ ERROR ] IPTTEST-006 Logging failed to connect to database:jdbc:JSQLConnect://servername:1433/databasename

Cause:
The database does not exit on the Microsoft SQL 2005 server

Solution:
Ask the SQL DBA to create the AUDIT database, before you try to connect to it.

Product:
Cognos BI 10.1.1
IBM HTTPServer 7
AIX

Symptom:
Error when surf to cognos connection on a AIX server with HTTPServer and Kerberos configured.

Error message:
Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, you@your.address and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.
——————————————————————————–

IBM_HTTP_Server at servername.domain.com Port 80

Possible solution:
The file http.keytab is missing from the /opt/IBM/HTTPServer/conf folder.
This file should contain the kerberos keytab information for that domain account that is set for the Webserver.

Use Putty to access the AIX server.
Go to the /opt/IBM/HTTPServer folder (with command cd /opt/IBM/HTTPServer)
List the contains of the folder (with command ls -l )

Check the http.keytab file is there.
Check the owner of the file, it should in most cases be root.
Check the access rights to the file, in most cases it should be -r–r–r–

Product:
Cognos BI 10.1.1
Internet Explorer

Symptom:
Error when you try to surf to Cognos Connection in Internet Explorer

Error message:
DPR-ERR-2107
The User Capabilities Cache cookie cannot be decoded.

Solution:
Close all Internet Explorer windows and start again.

You are logged into a other Cognos BI server Cognos Connection in other Internet Explorer window, that make it not possible to login to a new Cognos BI server.

Product:

Cognos BI 10.1.1

Microsoft Windows 2008 R2 server

 

Symptom:

Does the anti virus program affect my performance in cognos BI ?

 

Result:

Yes – you should disable any local active scanning on Cognos BI folders and subfolders.

If you have rules in the Anti virus program – you should test to turn them off, this can increase performance in Cognos BI reporting.

 

You must have all antivirus software turned off during install of Cognos BI products, or the installation may fail.

 

More Information:

<c10_location> refers to the installation directory of each Cognos BI Instance.

 

Configuration files

<c10_location>\configuration\

Example c:\Program Files\ibm\cognos\c10_64\configuration\

Exclude files of type:

*.ini

*.xml

*.xsd

*.xslt

The configuration folder is a tree structure with several levels. Exclusions should apply to the flder levels and any other subfolder level below.

 

Temporary files

<c10_location>\temp\

Example c:\Program Files\ibm\cognos\c10_64\temp\

The temp folder is used by Cognos BI to store temporary files used for local operations or cached data.

 

Files in this folder don’t have any extensions. Files can be differentiated based on their prefix, fx: ‘uda*’. The recommendation is that the entire folder and subfolder structure is excluded from access scanning.

 

You can inside Cognos Configuration set the environment value for TEMP files to something else than default – if you set to d:\temp you must exclude that folder also from the anti virus scan software.

 

Transformer Cubes

Example c:\Cubes\Current\

File types to exclude: *.mdc

The cubes folder is divided into various subfolders with different levels. Exclusion should apply all folder levels below.

 

Log files

<c10_location>\logs\

Example c:\Program Files\ibm\cognos\c10_64\ logs\

File types to exclude:

*.log

*.xml

*.lck

*.pid

*.service

cbs*  (Note: exclude on prefix, the ‘cbs*’ files does not have extensions)

 

The logs folder is also a tree structure with different levels below. Exclusions should apply to all levels below.

 

Runtime-models

<c10_location> data\

Example c:\Program Files\ibm\cognos\c10_64\data\

File types to exclude:

*.rtm

*.lck

The runtime models folder is a tree structure with sublevels. Exclusions should apply to all levels below.

 

DEP

Please also do not forget to turn DEP off in Microsoft Windows 2008 R2 servers.

Go to controller panel – system – advanced system settings

Go to system properties – advanced – system performance.

Go to Data Execution Prevention tab and select to top value only.

Click OK.

 

Data Execution Prevention (DEP) is a security feature that can help prevent damage to your computer from viruses and other security threats. Harmful programs can try to attack Windows by attempting to run (also known as execute) code from your computer’s memory reserved for Windows and other authorized programs. These types of attacks can harm your programs and files.

DEP can help protect your computer by monitoring your programs to make sure that they use computer memory safely. If DEP notices a program on your computer using memory incorrectly, it closes the program and notifies you.

Product:
Cognos BI 10.1.1 64 bit version
AIX
Oracle 11.2.0
Java version 1.5

Symptom:
When testing the connection to a oracle data source, the Compatible Query Mode is successful, but you get a error message for Dynamic Query Mode (JDBC).

Error message:
XQE-GEN-0002 An unexpected exception occurred: ocijdbc11 (A file or directory in the path name does not exist.)

Background:
You have installed 32 Bit Oracle client on your Cognos Aix server.
You have set the LIBPATH to /IBM/cognos/oracle/product/11.2.0/client32/lib
You have added oracle path to the PATH variable.
You have copied the ojdbc5.jar file to the /IBM/cognos/c10_64/webapps/p2pd/WEB-INF/lib folder.

Under Dynamic/JDBC connection setting, you can
choose “Service ID”, “TNS Names Alias” and ‘Oracle Net Descriptor”.
This error only occurs on “TNS Names Alias” (OCI driver type only), and ‘Oracle Net
Descriptor” (With OCI driver type).
“Service ID” option and Oracle Net Descriptor (Thin driver type) don’t have this issue.

Solution:
Cognos BI 10.1.1 needs to call 64 Bit Oracle libraries when you use a JAVA OCI driver.
But Compatible Query Mode only supports 32 Bit Oracle client (SQLNET).

Recommendation is to use SERVICE ID to access the Oracle database with JDBC.
Enter the server name to the oracle server using FQDN name.
Enter the port number e.g. 1521.
Enter the oracle service ID, that is the database name.

In previous OCI configuration you set the user name to the schema name and also enter the password for the user name.

Then test the connection again.

Otherwise you need to install both 32bit and 64bit oracle client and update the LIBPATH accordingly, to maybe get it to work.