by ·0 Comments

Product:

Cognos BI 10.2.1 fix pack 2

Windows 2008 R2 server

Problem:

The free hard disk space on the Cognos BI report server is low.

The Cognos folder under c:\program files\   take more than 50 GB space.

Cause:

When a BIBUS or REPORT crashes a dmp file is created in the bin folder.

They fill up the disc, and you should periodical erase these *.DMP files.

 Solution:

Change the cclWinSEHConfig.xml file in folder C:\Program Files\ibm\cognos\c10_64\configuration

Change value below from

<env_var name=”CCL_HWE_ABORT” value=”2:2″/>

To

<env_var name=”CCL_HWE_ABORT” value=”0:0″/>

Save the file.

Restart all the Cognos BI services in correct order.

 

by ·0 Comments

Product:

Cognos BI 10.2.1 server

Windows 2008 R2 Server

Oracle database

Problem:

You have a report that take out all power of the database server, but you do not know that name of the report.

 Suggested Solution:

Add the name of the report to the SQL queries sent to the Oracle database, then the Database DBA can look into the trace of the queries and see what report give the issue.

On the Cognos BI server open the file CQEConfig.xml

Can be found in folder c:\Program Files\ibm\cognos\c10_64\configuration

Change to have this content;

 

<?xml version=”1.0″ encoding=”UTF-8″?>

<!–

Licensed Materials – Property of IBM

BI and PM: QECL

(C) Copyright IBM Corp. 2005, 2012

US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

–>

<configuration company=”Cognos” version=”0.1″ rendition=”cer2″>

<component name=”CQE”>

<section name=”DBConnectionPool”>

<!– Description: Database connection timeout. Default is 900 seconds (15 minutes) –>

<entry name=”Timeout” value=”900″/>

<!– –>

<!– Description: Database connection pool size. –>

<!– Maximum number of connections managed by the report server process. Default=40 –>

<entry name=”PoolSize” value=”40″/>

<!– –>

</section>

<section name=”QueryEngine”>

<!– Description: queryReuse feature –>

<!– value=”0″ means disable the feature –>

<!– default is value=”5″ which means cache up to 5 result sets per session –>

<entry name=”queryReuse” value=”5″/>

<!– –>

<!– Description: References to model query items may have 2-part names. (default(off)=0; choices=0,1) –>

<!– Off:  A parsing error is returned for a reference to a model query item using a 2-part name.  –>

<!– On:  The expression resolver will allow 2-part name references to model query items.    –>

<!– NOTE: Cognos 8.1 MR2 was the last release in which the default setting allowed 2-part names. This release (8.2) –>

<!– has the default set to disallow 2-part names. The next release (8.3) will no longer allow 2-part names. –>

<!– The use of 2-part names will generate the QE-DEF-496 warning message in the log file. –>

<!– entry name=”AllowModelQueryItem2PartNameReference” value=”0″/–>

<!– –>

<!– Generation of comments in native sql and cognos sql.–>

<entry name=”GenerateCommentInNativeSQL” value=”1″/>

<!– ( default(off)=0, on=1) –>

<entry name=”GenerateCommentInCognosSQL” value=”1″/>

<!– ( default(off)=0, on=1) –>

<!– The content of the comments is controlled with two entries, their defaults are specified in the value attribute –>

<entry name=”NativeCommentMacro” value=”#’ user=’ + $account.defaultName + ‘ report=’ + $report + ‘ reportPath=’ + $reportPath + ‘ queryName=’ + $queryName + ‘ start=’ + $startTime#”/>

<entry name=”CognosCommentMacro” value=”#’ user=’ + $account.defaultName + ‘ report=’ + $report + ‘ reportPath=’ + $reportPath + ‘ queryName=’ + $queryName + ‘ start=’ + $startTime#”/>

<!– –>

<!– Description: Include the preferred query subject into the join cache key –>

<!– ( default(off)=0, on=1) –>

<!–entry name=”IncludePreferredQuerySubjectsInJoinCacheKey” value=”1″/–>

<!– –>

<!– Description: Compute measure query items just once (off(default)=0, on=1+ –>

<!– entry name=”ComputeMeasureQueryItemsOnce” value=”0″ –>

<!– –>

</section>

<!– The following section is disabled by default.    –>

<!– The CQE logging is turned on when the existing section name (“_Logging”) is changed to “Logging”. –>

<section name=”_Logging”>

<entry name=”CQEXMLAPI” value=”3″/>

<entry name=”UseIPFLogging” value=”0″/>

<entry name=”QueryEngine” value=”11″/>

<entry name=”LogFileName” value=”..\logs\CQE.log”/>

<entry name=”QR” value=”3″/>

<entry name=”DBC” value=”11″/>

<entry name=”JoinPath” value=”11″/>

</section>

</component>

</configuration>

 

Will give that you have

–         Username

–         Report name

–         Report path

–         Query name

–         Start time

In the Query.

 

More Information:

http://www-01.ibm.com/support/knowledgecenter/#!/SSMR4U_10.1.0/com.ibm.swg.ba.cognos.ug_cra.10.1.1.doc/t_add_comments_native_cognossql.html%23Add_Comments_Native_CognosSQL

https://www.ibm.com/docs/en/cognos-analytics/11.1.0?topic=database-using-application-context-in-dynamic-sql

To use comments in SQL for dynamic query mode (for CA11.1.x) you can configure the xqe.config.xml file, located in install_location/configuration.

You edit the following elements in the <queryPlanning> element.

<generateCommentsInNativeSQL enabled="true"/>
<NativeCommentMacro value="#'user=' + $account.defaultName + ' reportPath='
 + $reportPath +' queryName=' + $queryName + ' REMOTE_ADDR=' + $REMOTE_ADDR 
 + ' SERVER_NAME=' + $SERVER_NAME + ' requestID=' + $requestID#"/>

by ·0 Comments

Product:
Cognos BI 10.2.1
Windows 2008 R2 server
Outlook Mail program

Problem:
Mail sent is not coming forward to the end user from Cognos BI.
In some cases you get a message from the Exchange Mail server that the mail is
This is an automated message from the Extensible Content Security

A mail from you x to y was stopped and Quarantined because it contains one
or more forbidden attachments.

Summary of email contents:

Attachment: My personal report 1.mht
My personal report 1.mht forbidden file extension (.mht)
My personal report 1.mht forbidden file extension (.mht)
Attachment: html
Attachment: image

Because:
Cognos BI 10.2.1 send mail with Excel 2002 attachments as MHT files, that Excel can open but your mail system may have excluded that be allowed.

If you send a report as HTML and include a Body Text in the Schedule message you will get the same issue, please send a link instead of a HTML attachment to make it work.

Solution:
In Server Administration, add “RSVP.FILE.EXTENSION.XLS” parameter to ReportService and BatchReportService.
Steps:
1. Open Cognos Connection.
2.Click Tools menu in the portal and select Server Administration
3. Check Services for Type (All services appear)
4. Select Set Properties for ReportService
5. Select the Settings tab
6. Find the property named Advanced Settings, and click the Edit… link
7. In the first empty set of boxes, type in the parameter name RSVP.FILE.EXTENSION.XLSand set the value to TRUE
8. Press OK.

More Information:
http://www-01.ibm.com/support/docview.wss?uid=swg21342065

by ·0 Comments

Product:
IBM Cognos Planning 10.1.1
Microsoft Windows 2008 R2 Server

Problem:
How change the TEMP variable for a service account, without logging in as the user on the Windows Server?

Solution:
Create the service account in the Domain.
Ensure the service account is part of the local administration group on the planning server.
Go to the Administration tools – services.
(you can start it by type services.msc in Run dialog)
Double Click on your IBM Cognos 10 Planning service and select Log On tab.
Select this account and browse to your service account, in our example named cogplan.
Enter Password and click OK to save the change.
Click OK on message that the account have been added to “log on as a service” function.
Right Click on the service IBM Cognos 10 Planning and select RESTART.
Ensure that Cognos planning service have started.

The planningerrorlog.csv file is created in folder \users\cogplan\appdata\local\temp

Start REGEDIT
Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList
Check the last number in list – it is possible your service account.
You should see it on the ProfileImagePath value who would be : C:\Users\cogplan
Note the number if the user down
Go to HKEY_USERS\S-1-5-21-2298123480-4089459362-31738xxxxx-1001\Environment
(the number should be the number of the user you found under ProfileList.)
Double click on TEMP to change the value from
%USERPROFILE%\APPDATA\LOCAL\TEMP
to
D:\TEMP
Click OK
Repeat the change for TMP
Close REGEDIT

Restart the Cognos Planning service.

Now the log file is in the D:\TEMP folder.

by ·0 Comments

Product:
Cognos Controller 10.1 FAP
Microsoft Windows 2008 R2
Oracle Database

Error message:
** ERROR: java.sql.SQLException: IO Error: Invalid connection string format, a valid format is: “host:port:sid”

Problem:
When you setup the Cognos Controller FAP database, you need to populate it with tables by using the DBCONV program from Cognos Controller Configuration.
You enter the values for Database Connection and click Test – Connection Succeeded.
Then you click on the arrow to start DBCONV module, and click on CONNECT button to connect to the oracle database. Here you get above error.
If you get below error, it is because you have not entered domain.com value in the name in Cognos Configuration or in the TNSNAMES.ORA file.
** ERROR: java.sql.SQLException: IO Error: Unknown host specified
Only enter PT0572 in Cognos Controller data source will give that error.
Solution:
Inside Cognos Controller Configuration for the FAP database you must enter an EZCONNECT data source name. Like this;
oracleaixservername.domain.COM:1521/PT0572.domain.com
The important is that it is oracle host name (colon) port number (slash) tnsnames alias including domain.com
The TNSNAMES.ORA file should contain this;
PT0572.DOMAIN.COM=
(DESCRIPTION=
(ADDRESS=(PROTOCOL=TCP)(HOST=oracleaixservername.DOMAIN.COM)(PORT=1521))
(CONNECT_DATA=
(SID=PT0572)
)
)

And Cognos Controller Configuration should be like this:
Database type: Oracle
Name: FAP
Provider: ORAOLEDB.ORACLE.1
User ID: CCR_FAP_data_mart (the oracle schema name)
Password: *******
Data Source: oracleaixservername.domain.com:1521/PT0572.domain.com

You must exit Cognos Controller Configuration program between every change to the TNSNAMES.ORA file. The file is only read during start of the Controller Configuration program (ControllerConf.exe *32).

More Information:
http://www-01.ibm.com/support/docview.wss?uid=swg21635338

by ·0 Comments

Product:
Cognos Planning 10.1.1. Fix pack 3 (version 10.1.6303.19-0)
Windows 2008 R2 Server
Oracle database

Symptom:
When you start Cognos Planning Administration Console on a client you get a error message.
When opening the CAC the following error occurs:
“An error has occurred while starting IBM Cognos Planning Administrator.
Main form failed to initialize.
Error Details:
Unable to determine if the Planning Tables exist in Content Manager. Please ensure the Planning Service is running.”

Unexpected: missing HRESULT parameter”

When opening Analyst the following error occurs:
“Analyst failed to communicate with the Content Manager database. This can happen if the Cognos 10 Planning service is not running. Please check that the service is running.”

Error was:

DISP_E_EXCEPTION
Failed HRESULT [0x80020009] Exception occurred.”
Cause:
The gateway url in Cognos Configuration is not the same as the gateway url on the Cognos BI server for authentication.

Solution:
Log on to the Cognos Planning BI server.
Start Cognos Configuration.
Copy the value for Gateway URI under environment section.
Go to the client computer where you have CAC and Cognos Planning Analyst installed.
Start Cognos Configuration
Paste the value for Gateway URI under Gateway settings.
Click on Save
Exit Cognos Configuration
Try to start the IBM Cognos Planning – Contributor Administrator Console.

Can also be other causes;
http://www-01.ibm.com/support/docview.wss?uid=swg21621002

by ·0 Comments

Product:
Cognos Planning 10.1.1
Windows 2008 R2 server
Oracle database

Symptom:
When doing a GTP you get the PREPARE_ACCESS_BLOCKS to say QUEUING all the time. Why ?

Cause:
The Cognos Planning solution is setup with one JOB server and one ADMIN server.
The PREPARE ACCESS BLOCKS step is a change in the Cognos Planning application that is done from the job server. The other steps of a GTP is update of the Cognos Planning store database, that is accessed with the settings defined in Cognos Configuration. So Cognos Planning use different parts to access the databases.

Solution:
For access to oracle database to work you need to have a correct TNSNAMES.ORA file in your \oracle\client\network\admin folder on your Planning servers.

In this case the issue was solved by adding the tnsnames.ora file to the job server, there it was missing, the tnsnames.ora file was on the ADMIN server only, therefor some GTP task worked, that does not need a tnsnames.ora file.

Access defined in Cognos Configuration can be setup for oracle to direct define and access the server.

by ·0 Comments

Product:
Cognos Planning 10.1.1
(PLANSRVR_version=PLANSRVR-AW32-ML-RTM-10.1.6235.51-0)
C8BISRVR-AW32-ML-RTM-10.1.6304.10-0 = IBM Cognos Business Intelligence Server Update, PLANSRVR-AW32-ML-RTM-10.1.6303.19-0 = Planning Server Update
Windows 2008 R2 server
Oracle Database

Symptom:
Error when you try to Start Cognos Planning service.

Error message in Planningerrorlog.csv file:
E6525D43-48B1-4123-8C99-7BFA5DFA2515} 14 2014-04-09 16:57:09.832 UTC +120 epPlanningService 10.1.4074.0 default ThreadSystemConnectionPool.cpp RefreshConnectionPool 260 OraOLEDB -2147467259 Unable to open connection using connection string of Provider=OraOLEDB.Oracle;Data Source=server.DOMAIN.COM;User ID=SERVICEACCOUNT;Password=*********; and timeout of 15 seconds.~~~~ORA-12504: TNS:listener was not given the SERVICE_NAME in CONNECT_DATA DOMAIN\UserAccount DOMAIN\SERVER DOMAIN\UserAccount DOMAIN\SERVER 3408 4968
{E6525D43-48B1-4123-8C99-7BFA5DFA2515} 15 2014-04-09 16:57:09.847 UTC +120 epPlanningService 10.1.4074.0 default ThreadSystemConnectionPool.cpp Run 138 OraOLEDB -2147467259 Unable to open connection using connection string of Provider=OraOLEDB.Oracle;Data Source=server.DOMAIN.COM;User ID=SERVICEACCOUNT;Password=*********; and timeout of 15 seconds.~~~~ORA-12504: TNS:listener was not given the SERVICE_NAME in CONNECT_DATA DOMAIN\UserAccount DOMAIN\SERVER DOMAIN\UserAccount DOMAIN\SERVER 3408 4968

Possible Cause:
This can happen when you restart the Cognos Planning service, from Cognos configuration or direct from windows services.

And the planning store settings inside Cognos configuration for oracle is set to advance and you use this syntax;
databasehostname.domain.COM:1521/oracleserverid.domain.COM

instead of this syntax;
(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=databaseserver.domain.COM)(PORT=1521))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=oraclename.domain.COM)))

Redo the access syntax in Cognos Configuration and try to start Cognos again.
Both syntax of access to Oracle work for Cognos Content Store, but not for Cognos Planning Store.

by ·0 Comments

Product:
Cognos Planning 10.1.1
(PLANSRVR_version=PLANSRVR-AW32-ML-RTM-10.1.6235.51-0)
C8BISRVR-AW32-ML-RTM-10.1.6304.10-0 = IBM Cognos Business Intelligence Server Update, PLANSRVR-AW32-ML-RTM-10.1.6303.19-0 = Planning Server Update
Windows 2008 R2 server
Oracle Database

Symptom:
Error when you try to Start Cognos Planning service.

Error msg:
02E05353-AF07-4C9D-B859-9CF2760616A4} 17 2014-04-09 17:35:09.522 UTC +120 epPlanningService 10.1.4074.0 default ThreadSystemConnectionPool.cpp ThreadProc 104 OraOLEDB -2147467259 Process exception DOMAIN\SERVICEACCOUNTNAME DOMAIN\SERVERNAME DOMAIN\SERVICEACCOUNTNAME DOMAIN\SERVERNAME 3880 1312
{481087D0-09B5-48E0-A685-A28D2E363A44} 1 2014-04-09 17:39:23.194 UTC +120 epPlanningService 10.1.4074.0 default Poller.cpp ManageErrorLogging 345 epPlanningService::default::Poller.cpp::ManageErrorLogging::345 0 Database Errors: Source: OraOLEDB Description: ORA-00942: table or view does not exist Number: -2147467259 SQLState: NativeError: 942 Source: OraOLEDB Description: ORA-00942: table or view does not exist Number: -2147217865 SQLState: NativeError: 942 DOMAIN\SERVICEACCOUNTNAME DOMAIN\SERVERNAME None\None None\None 3456 368
{B16556CC-68A9-40E0-92BA-4CF7C75D61B6} 1 2014-04-09 17:39:25.034 UTC +120 epPlanningService 10.1.4074.0 default Poller.cpp ManageErrorLogging 345 epPlanningService::default::Poller.cpp::ManageErrorLogging::345 0 Database Errors: Source: OraOLEDB Description: ORA-00942: table or view does not exist Number: -2147467259 SQLState: NativeError: 942 Source: OraOLEDB Description: ORA-00942: table or view does not exist Number: -2147217865 SQLState: NativeError: 942 DOMAIN\SERVICEACCOUNTNAME DOMAIN\SERVERNAME None\None None\None 3456 3872

Possible Cause:
The database is new and you have only installed Cognos planning and started the services.
You have not run the Cognos planning contributor admin console, to create the Cognos planning store with all its tables.

During startup in Cognos Configuration, the Cognos Planning service checks for tables in the planning store database.

by ·0 Comments

Product:
IBM Cognos Planning 10.1.1
Microsoft Windows 2008 R2 server

Problem:
Macro does not run, no error messages, but if you do a GTP manually it works.
You have several Cognos Planning servers, where some are dedicated Cognos Planning Job servers.

Solution:
Ensure that all Cognos Planning servers are added to the Cognos Planning JOB cluster in Cognos Contributor Administration Console (CAC). Not only the dedicated Job servers should be in the cluster, add also the Cognos Planning Admin servers. Set the number of Maximum of Concurrent job to 0 (zero) on the Cognos planning servers.
For Cognos Planning Job servers the number of maximum concurrent jobs should be one less than the number of cpu cores on the Cognos planning server. On a 4 cpu core server the value should be 3.
Start CAC
Login as administrator
Right click on cluster icon for Job Server and select Add Job Server.
From the dropdown list you should see all the Cognos Planning servers you can choose.
(All in list need to be added). But servers that are not JOB servers should have value 0 for maximum concurrent jobs.
Also add all the applications, by click on the ADD button under Monitored objects, on the Job server cluster level in CAC.
After you added all the job servers, you can test to run the macros again.
More Information:
Please note that for Cognos Planning 10.1.1 to work you should install both Cognos BI 10.1.1 and Cognos Planning 10.1.1 to the same folder. Then you do not need to enter a value in the Cognos Configuration for IBM Cognos BI installation location.
This versions will work together (there are other version that will also work)
tl-BISRVR-10.1-6235.144-
tl-PLANSRVR-10.1-6235.51-
tl-UPDATE_BISRVR-10.1-6304.10-
tl-UPDATE_PLANNING-10.1-6303.19-
(Above versions number from folder C:\Program Files (x86)\ibm\cognos\c10\instlog)
On the Cognos Planning Admin server only the QUERY Service enabled? is set to FALSE in the Cognos Configuration under Environment for IBM Cognos Service.
On the Cognos Planning Job servers only the Dispatcher Service enabled? and Planning Job Service enabled? is set to TRUE in the Cognos Configuration under Environment for IBM Cognos Service. The rest is set to FALSE.
There are other possibilities of configuration that will work for Cognos Planning.
http://www-01.ibm.com/support/docview.wss?uid=swg21507327
http://www-01.ibm.com/support/docview.wss?uid=swg21597536