Product:
Cognos Controller 10.3
Problem:
User try to login to Cognos Controller and get a message
Solution:
The database is set in “single mode” and therefor you can not login. Wait for the administrator to logout and let the controller database be accessible for all users again.
More Information:
Product:
Cognos Controller 10.1.1 and 10.3
Oracle database
Microsoft Windows 2008 R2 server
Symptom:
When you publish to DataMart from inside Cognos controller you get an error message.
You have inside Cognos Controller configuration setup a DataMart connection for you Controller database like this:
Error message:
ORA-04052: error occurred when looking up remote object FRANGO.DMTEMPLATE@DMPUBLISH.COMPANYX.COM
Possible Solution:
Start SQL Developer and connect to the controller data schema.
The connection string is not updated correct inside the database from the Controller configuration setup.
Then do this commands (you need to edit the connection for your environment)
DROP DATABASE LINK “DMPUBLISH.COMPANYX.COM”;
CREATE DATABASE LINK “DMPUBLISH.COMPANYX.COM”;
CONNECT TO FRANGO
IDENTIFIED BY <PASSWORD>
USING ‘
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP) (HOST = LX1234.COMPANYX.COM) (PORT = 1521))
( CONNECT_DATA =
( SERVER = DEDICATED)
( SERVICE_NAME = IT0123.COMPANYX.COM)
)
) ‘ ;
Then after this update – try the DataMart function inside Cognos controller again.
Product:
Cognos Controller 10.3 (CONTRL_version=CCR-AW64-ML-RTM-10.3.0.169-0)
Microsoft Windows 2008 R2 Server
Oracle 12c database (version Release 12.1.0.2.0) 64 bit
Symptom:
When connect to an Oracle Controller database you get an error during the upgrade steps inside Cognos Controller Configuration program.
Error message in DBCONV:
Running DB Step: 950
Running script batch: script/ora_950.batch
Running script: script/ora/ora_update_xmenu.sql
Running DB Step: 951
Running DB Step: 952
Running script batch: ora_952.batch
Running script: script/ora_xrclayout_add_column.sql
** ERROR: java.sql.SQLSyntaxErrorException: ORA-00904: “DBMS_LOB”.”SUBSTR”: ogiltig identifierare
ORA-06512: vid rad 12
The SQL command that give the error are:
DECLARE
sSql VARCHAR2(4000);
BEGIN
IF NOT UFNC_OBJECT_EXISTS(‘SELECT 1 FROM user_tab_COLUMNS WHERE table_name = ”XRCLAYOUT” AND column_name = ”EXCELFILEFORMAT”’) THEN
sSql := ‘ALTER TABLE XRCLAYOUT ADD EXCELFILEFORMAT number DEFAULT (0) NOT NULL’;
EXECUTE IMMEDIATE (sSql);
sSql := ‘UPDATE XRCLAYOUT SET EXCELFILEFORMAT = 56’;
EXECUTE IMMEDIATE (sSql);
sSql := ‘UPDATE XRCLAYOUT SET EXCELFILEFORMAT = 51 WHERE UTL_RAW.CAST_TO_VARCHAR2(DBMS_LOB.SUBSTR(layout, 2,1)) = ”PK”’;
EXECUTE IMMEDIATE (sSql);
END IF;
END;
Possible Solution:
There can be a setting on the Oracle database that does not allow that many connections. Please check and increase.
Please note: If you get a error during upgrade of a cognos controller database – then the database will be corrupt, because some upgrade steps will be missing. You must restore the original database and run the upgrade steps again from the beginning to ensure the database is fully functional.
It can be that you have the wrong ojdbc7.jar file in the controller folder.
Copy the correct ODBC file from the Oracle client installation on the server
Can be this folder:
C:\orarun\ora12102\Client\jdbc\lib\ojdbc6.jar
To the folders of the Cognos controller installation
that normally is these folders;
C:\Program Files\ibm\cognos\ccr_64
C:\Program Files\ibm\cognos\ccr_64\server\integration
C:\Program Files\ibm\cognos\ccr_64\server\FAP\lib
C:\Program Files\ibm\cognos\ccr_64\webapps\p2pd\WEB-INF\lib
Close the Controller Configuration and start it again so it can pick up the new driver jar file you have paste into the controller ccr_64 folder.
You can also be needing to run the DBCONV.EXE program as standalone from Cognos Controller Configuration.
Go to folder /ccr_64/ and start DBCONV.EXE
Click on the button with dots to select the correct UDL file.
Then click on Connection Button.
Now you can click on Upgrade button, and it should work better.
There can also be other cause of this issue – ensure the host name in cognos controller configuration only use the servername and not .domain.com – the new code does not accept period in server name for the data source.
More Information:
Cognos Controller use different connection methods to connect to ORACLE databases, like this:
ODBC = Controller Consolidation part
OLEDB = Controller Applications part
JDBC = used by DBCONV and java parts, also used by Cognos BI CQM reports
OCI = used by Cognos BI DQM reports (not found on Cognos Controller server)
Product:
Cognos Planning 10.2
Windows 2012 server
Issue:
How install the new Cognos planning on windows server?
Some help:
Use of this information should help you get it right, ensure this things are done before you test the installation.
To integrate with Cognos BI try this tips from ”How can I install IBM Cognos Planning in the same environment as 64-bit IBM Cognos Business Intelligence”
http://www-01.ibm.com/support/docview.wss?uid=swg21501838
Error when start Planning Analyst and other tools ”cannot find files”
Ensure to do this:
renamed adminbifs.amf to adminbif.AMF
renamed adminodbc.AMF to adminodb.AMF
http://www-01.ibm.com/support/docview.wss?uid=swg21635667
Windows supports long file names up to 255 characters in length. Windows also generates an MS-DOS compatible short file name in 8.3 format to allow MS-DOS based or 16-bit windows based programs to access these files. When the 8.3 setting is enabled only short file names are generated. Therefore the long file name of adminbifs.AMF is shortened to adminbif.AMF and adminodbc.AMF is shortened to adminodb.AMF and this causes the error on startup as the file cannot be located as it does not exist under that name and Analyst is a 32-bit program and works off the long file name only.
Error when starting Planning Analyst of type ”cannot connect libraries”
Ensure to do this:
1. Launch MSCONFIG by from the Run menu.
2. Click on the Tools tab. Scroll down till you find “Disable UAC” . Click on that line.
3. Press the Launch button.
4. A CMD window will open. When the command is done, you can close the window.
5. Close MSCONFIG. You need to reboot the computer for changes to apply.
OR
Alternate Solution:
1. Give the everyone group full control to the folder where the libraries are located.
OR
Alternate Solution: If User Account Control resolution above does not resolve issue:
1. Right-click the Analyst shortcut
2. Select Properties > Compatibility tab
3. Check the box: Run this Program as Administrator
4. Now open Analyst as the user who is receiving the error.
http://www-01.ibm.com/support/docview.wss?uid=swg21380414
To have access to the folders on the SQL server you need to do this:
Install the SQL Server Client tools (if this has not already been done).
NB For SQL Server 2005 you need to have the full SQL Client installed (comes with SQL Express) as the Native Client does not install all of the required .dll files.
For SQL Server 2008 full client tools required.
Once the SQL Server Client tools are installed, ensure that the Contributor user account used to connect to SQL Server has EXEC permissions to the following Extended Stored Procedures in the Masters Database:
xp_availablemedia
xp_subdirs
http://www-01.ibm.com/support/docview.wss?uid=swg21343839
Contributor Datastore server connection check Trusted Connection instead of login with an account
Depending on the setup you should use Trusted or SQL account login. Try the other if you have issues like “Subscript out of range”
http://www-01.ibm.com/support/docview.wss?uid=swg21986012
There are more things to configure — search google.com if you get issues.
Product:
Cognos BI 10.2.2 fix pack 7
Microsoft Windows 2008 R2 Server
Symptom:
Running the installation program for Cognos BI and Cognos BI fix pack are very slow. The program stand still a long time at same step.
Cause:
If you look in task manager you will see that the process using more than 25% of the CPU are MsMpEng.exe Antimalware service Executable. The System Center Endpoint Protection program is installed and set to have real-time protection on the server.
Antivirus software will always slow down the copy of files during installation of Cognos Programs. It is recommended to turn off Antivirus software during install and exclude the Cognos program and subfolder from the real time scan on the servers.
Installation of IBM Cognos Business Intelligence Server Updates 7 took 3 hours with Microsoft anti-virus software turned on instead of a few minutes when it was turned off.
If IT department do not want to turn off Antivirus on servers, work around is that you can try to install both Cognos BI and Cognos TM1 at the same time but to different folders. This will gain you a little time.
Product:
Cognos BI 10.2.2 fix pack 7
Microsoft Windows 2008 R2 Server
Symptom:
When user surf to http://biservername.domain.com/ibmcognos they get a windows security login dialog. If they surf to only http://biservername.domain.com they get the standard IIS7 start page.
If the same user surf to http://biservername.domain.com/ibmcognos direct from inside the BI server with Internet Explorer there is no problem.
On both server and client the *.domain.com is added as local intranet in Internet Options.
Solution:
On the Microsoft Windows 2008 server start up Internet Information Services (IIS) Manager program and go to the IBMCOGNOS folder.
Select Authentication.
Select Windows Authentication (that is enabled) and click on Providers link at the right.
Move NLMT to be on top over Negotiate.
Click OK.
Test now from the client laptop computer – now SSO should work.
Product:
Cognos Tm1 10.2.2 fix pack 6
Microsoft Windows 2008 R2 Server
Symptom:
When new updated express TM1 instance start, it is named = CXMD
Cause:
In the TM1S.CFG file the servername is as Servername = CXMD, but in TM1 you need to not have a space – it should be Servername=CXMD.
Uninstall the TM1 instance, change the TM1S.CFG to not use space at = , then start the service again from Cognos Configuration for TM1.
If you not have uninstalled Cognos Express – then the new start of TM1 instance with same name as a existing one will make it look like the new one is installed in Cognos Configuration, but in Windows services if you check on properties on the TM1 instance CXMD it will show it use the old Cognos express engine under \program files (x86)\ that make it not work.
You notice something is wrong if no log files are created in the new folder you have setup for the new TM1 instance – then there is a different folder in use, probably the old one.
Solution:
How to move a Cognos Express application to a TM1 10.2.2 application.
Make a backup of all excel sheets used in the TM1WEB part.
You need to login to Cognos Express with Tm1 architect and do savedataall step and take a backup of the data folder, mostly there exist a TI process already written for this.
Then copy the Cognos express folder c:\program files (x86)\IBM\cognos express\xcelerator\custom\tm1data\cxmd\ to your new folder for tm1 that in most cases are c:\program files\ibm\cognos\tm1_64\samples\tm1\cxmd\.
Recommend to create a separate folder for log files like this c:\program files\ibm\cognos\tm1_64\samples\tm1\cxmd_logs.
To get Cognos Express BI security you need to take screen shoots how it is setup in Cognos Express and then manually add the same AD groups to Cognos BI groups inside the New Cognos Connection on the new installation.
Download fix pack for TM1 and Cognos BI
Uninstall Cognos Express program from the server.
Install Cognos BI and setup IIS as show here:
http://www.ibm.com/developerworks/data/library/cognos/infrastructure/web_servers/page599.html
Active SSO for Cognos BI with this steps
The connection to customers Active Directory must have the namespace id to be “CognosExpressActiveDirectoryID” set, to allow the users that before was setup in Cognos Express come in as the same user in the new TM1 solution.
Inside Cognos Configuration for BI, under Security – Authentication, select New Resource – Namespace.
Set Name to domain.com and select Type to Active Directory.
Set the Namespace ID to CognosExpressActiveDirectoryID.
Set host and port to; customer´s Domain.com:389
The name that you show in left for the authentication is what is shown inside Cognos Connection as the name of the namespace, the namespace ID is the Cognos BI internal ID and that should be the same as used in Cognos Express to ensure the users end up in the same rows inside TM1 security table.
Best Practices is to have this two field the same, that should mean namespace id is CognosExpressActiveDirectoryID in this case.
Install Cognos Tm1 10.2.2 and set it up as show here:
Install Cognos TM1 10.2.2 fix pack 6 new certs as of this page
http://www-01.ibm.com/support/docview.wss?uid=swg21991545
http://www-01.ibm.com/support/docview.wss?uid=swg21992411
Install SSO for TM1 applications by following this steps:
In the new CXMD data folder – remove the tm1s.cfg and TM1.lic files.
Create a new TM1S.CFG file with content like this:
[TM1S]
CAMPortalVariableFile=portal/variables_TM1.xml
Language=ENG
IntegratedSecurityMode=5
ClientMessagePortNumber=12307
DataBaseDirectory=C:\Program Files\ibm\cognos\tm1_64\samples\tm1\CXMD
UseSSL=T
PortNumber=12306
ClientPingCAMPassport=900
LoggingDirectory=C:\Program Files\ibm\cognos\tm1_64\samples\tm1\CXMD_logs
ServerName=CXMD
AdminHost=
ForceReevaluationOfFeedersForFedCellsOnDataChange=T
DistributedPlanningOutputDir=.\tunit
AllowSeparateNandCRules=T
ServerCAMIPVersion=ipv4
IPVersion=ipv4
ClientCAMURI=http://BISERVER.domain.com/ibmcognos/cgi-bin/cognosisapi.dll
ServerCAMURI=http://BISERVER.domain.com:9300/p2pd/servlet/dispatch
##ServerCAMURI=http://EXPRESSSERVER.domain.com:9300/p2pd/servlet/dispatch
##ClientCAMURI=http://EXPRESSSERVER.domain.com:9300/p2pd/servlet/dispatch
ParallelInteraction=T
SupportPreTLSv12Clients=T
Update the BISERVER values with your server and domain name in above file.
Inside Cognos Configuration for TM1 click on TM1 server – New Resource – TM1 server instances. Enter CXMD as name. then browse to the folder where the tm1s.cfg file are in our example that is in c:\program files\ibm\cognos\tm1_64\samples\tm1\cxmd.
Save and start the CXMD instance from Configuration program.
Start TM1 architect on the Server to see if you can access the CXMD application.
To get TM1 perspective to work after you have used Cognos Express the end user must do a few things;
Ensure the new Cognos BI/TM1 servers are in Internet Options local intranet zone.
Uninstall the previous Cognos Express client.
Install the new TM1 perspective from setup files you place on a share (\\TM1server\clientsetup$).
(select default options during install)
first run setup from
\\TM1server\clientsetup$\tm1_clt_10.2.2_32b_ml.tar\win32\iisetup.exe
second run setup from
\\TM1server\clientsetup$\up_tm1client_win32_10.2.5260.168_ml.tar\win32\iisetup.exe
Then copy all files from folder
\\TM1server\clientsetup$\NewSSLCerts\*.*
to this folders on your computer
C:\Program Files (x86)\ibm\cognos\tm1\bin\ssl\*.*
Inside Microsoft Excel 2010 add the new folder for TM1\bin to trusted locations.
Go to File – Options in Excel.
Click on Trust Center
Click on Trust Center Settings button
Click on Trusted Locations
Click on Add new location button
Browse to the folder for TM1 that is c:\program files (x86)\ibm\cognos\tm1\bin
Click OK all the way out of Microsoft Excel
Now it should work to start TM1 Perspective from icon on start menu.
Excel sheet you have published in TM1WEB, you may need to republish from TM1 Perspective again.
If you get the error message “STOP Failed to open the target workbook. Please make sure the file has not been renamed or deleted.” when you open a xlsx file in Tm1web applications, then the solution is to create the xlsx-page in new Excel Workbook files and publish them again to the TM1WEB application. Hopefully you can copy the layout and code from the old xls file. The xls files previous used in Cognos Express can in many case not be working in the new Cognos TM1 10.2.2.
More Information:
To test and see error better set it up like this
https://tm1help.wordpress.com/2011/06/19/how-to-set-up-a-new-tm1-model/
Ensure that you have uninstall Cognos Express before you install TM1 otherwise this can help
http://www-01.ibm.com/support/docview.wss?uid=swg21635821
To active sso in Cognos BI do this steps
Product:
Cognos TM1 10.2.2
Windows Server 2008 R2 64 bit
Problem:
After change to use DNS alias to surf to the Cognos servers there is an error message after you try to login that says;
The TM1Web service parameter was not specified or is not one of the configured locations
You can login if you enter the TM1 server direct like this;
http://servername.domain.com:9510/tm1web/
Possible solution:
You need to update the TM1WEB.HTML file with the DNS alias.
Open the TM1WEB.HTML file from your Cognos BI gateway server in folder
C:\Program Files\ibm\cognos\c10_64\webcontent\tm1\web\tm1web.html
Update the value below by adding the DNS alias for the TM1 server.
// Update the following to point to the location of the TM1Web service(s)
var tm1webServices = [“http://servername.domain.com:9510″,”http://dnsalias.domain.com:9510”];
Save the file, and start Internet Explorer to test again.
Product:
IBM Cognos TM1 10.2 server (version 10.2.5000.367-0)
IBM Cognos TM1 package connector (version 10.2.5000.14-0)
IBM Cognos BI 10.2.1 Fix Pack 1 (version 10.2.5001.156-0)
IBM Cognos BI 10.2.1 Fix Pack 2 (version 10.2.5002.78-0)
Windows 2008 R2 server
Symptom:
After installation of TM1 Package Connector (tm1pc_10.1.1_bi_10.2.1_win_ml.tar) on the same computer where you have TM1 Architect and Framework Manager installed, the option inside TI Turbo Integrator dialog for “IBM Cognos Package” is greyed out and not select-able.
You only get this issue on the Developer computer where you have also installed frame work manager for Cognos BI 10.2.1 fix pack 1.
If there is only TM1 installed or there is not a Cognos BI fix pack installed, it will work.
Solution:
Uninstall TM1 package connector from your computer.
Leave the Framework Manager and other software still installed.
Run installation of TM1 Package Connector again, but
Select a new folder, like:
C:\program files (x86)\ibm\cognos\c10pack
And also remember to set a new shortcut folder name to “IBM Cognos 10 Package Connector”
Finish the installation.
Then go to start menu and open Cognos configuration from “IBM Cognos 10 Package Connector”.
Update the environment tab with values for you Cognos Gateway server;
http://BIgatewayname.domain.com:80/ibmcognos/cgi-bin/cognosisapi.dll
And for you Dispatcher URI for external applications set it to;
http://BIservername.domain.com:9300/p2pd/servlet/dispatch
Save the settings.
Exit Cognos Configuration.
Start TM1 Architect
Click on a TM1 application to login.
Inside a TM1 application right click on “processes” and select “create new process”
Try to click on “IBM Cognos Package” – if it works, then you have succeeded.
TM1 architect use the windows variable TM1_PACKAGE_CONNECTOR to find the installation files its needs, so this variable should be a system variable. You can type SET in the command prompt on the server to check its current value, it should be
TM1_PACKAGE_CONNECTOR=c:\program files (x86)\ibm\cognos\c10pack\bin
You need to replace the URL/PATHS with the correct values for your servers.
Note: This will only work with 32 bit version of TM1 Architect.
And you must REBOOT the server after installation of the Package Connector.
Product:
Cognos TM1 10.2 64 bit
Cognos TM1 Architect 10.2 32 bit
Cognos TM1 package connector 10.1.1 32 bit
Microsoft Windows 2008 R2 server 64 bit
Oracle database server
Symptom:
Error when connecting from TM1 Architect to Oracle source through Cognos BI via TM1 Package Connector.
You have installed TM1 Package Connector on your TM1 server, and on your Terminal Server where you have installed TM1 Architect and Cognos Framework Manager.
You get a Data Source Sign on when you inside TM1 Architect are trying to Query the data with the IBM Cognos Package. This is because the client computer where TM1 Architect are trying to connect direct to the Oracle data source. You need to install Oracle 32 bit Drivers on the computer where TM1 Architect are installed. Also you need to update the tnsnames.ora file with the values needed for the database you try to connect to.
Error Message:
Error: MetaData procedure line (0): CCognosPackage::BuildDataSource Exception: (TR0324) Invalid logon.
– QE-DEF-0285 The logon failed.
– QE-DEF-0325 The logon failed for the following reason:
– RQP-DEF-0068 Unable to connect to at least one database during a multi-database attach to 1 database(s) in:
– CNSDW
–
– UDA-SQL-0432 Unable to locate the gateway “cogudaor”.
or
Error: MetaData procedure line (0): CCognosPackage::BuildDataSource Exception: (TR0324) Invalid logon.
– 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:
– CNSDW
–
– UDA-SQL-0031 Unable to access the “CNSDW” 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-0532 Data Source is not accessible: “data.test.domain.com”.
– ORA-12154: TNS:could not resolve the connect identifier specified
Solution:
Install the Oracle 32 bit drivers on the terminal server where TM1 architect and TM1 Package Connector are installed.
Update the tnsnames.ora file in folder \network\admin to include your data source.
Install the Oracle 32 bit drivers on the Windows server where TM1 Application and TM1 Package Connector are installed. This is the TM1 server where you have your TM1 data folder and you TM1 application.
Update the tnsnames.ora file in folder \network\admin to include your data source.
To get ODBC connections to work in TM1 Architect you need to also install the Oracle 64 bit drivers (in its own directory) on the Windows server where TM1 Application or TM1 Architect are installed. The ODBC connection is using the 64 bit parts of TM1 applications.
You need to start the ODBC Admin (odbcad32) and configure your odbc connection before start of TM1 Architect.
You must restart the TM1 application server, to make it be aware of your new installation of Oracle Drivers.
The Windows Path variable must include the path to the BIN folder of both the Oracle drivers installed.
More information:
Error:UDA-SQL-0432 Unable to locate the gateway “cogudaor”.
= missing 32 bit driver on TM1 server
Error: ORA-12154: TNS:could not resolve the connect identifier specified
= missing TNSNAMES.ORA file on the TM1 server
The TM1 server 64 bit version is using 32 bit drivers when access to data is made though the TM1 Package Connector (who is a 32 bit application). The TM1 architect also need direct connection to the Oracle datasource when developing, so you need 32 bit drivers on the TM1 Architect computer when using the TM1 package connector software.
The TM1 server 64 bit version is using 64 bit drivers when access to data is made through the ODBC connection on the server, here is the same on the terminal server where you have installed TM1 Architect. You must install the 64 bit database drivers on the TM1 servers and TM1 Architect clients.