The onLoad and onBeforeUnLoad event aren't called anymore between pages
and autosubmit. There is currently no workaround for this issue.
Cognos 8.3 javascript update -- onBeforeunLoad event
The onLoad and onBeforeUnLoad event aren't called anymore between pages
and autosubmit. There is currently no workaround for this issue.
and autosubmit. There is currently no workaround for this issue.
Cognos 8.3 javascript update -- checkBoxList updateSelected()
The checkBoxList*.updateSelected( ) function was used to indicate that the
prompt value was set or changed. This function is no longer used and all
references to it can simply be deleted. There is no analogous function. The
prompt state is determined using alternate means.
prompt value was set or changed. This function is no longer used and all
references to it can simply be deleted. There is no analogous function. The
prompt state is determined using alternate means.
Cognos 8.3 javascript update -- checkBoxList updateSelected()
The checkBoxList*.updateSelected( ) function was used to indicate that the
prompt value was set or changed. This function is no longer used and all
references to it can simply be deleted. There is no analogous function. The
prompt state is determined using alternate means.
prompt value was set or changed. This function is no longer used and all
references to it can simply be deleted. There is no analogous function. The
prompt state is determined using alternate means.
Cognos 8.3 javascript update -- checkData ( ) Function Replaced
checkData ( ) Function Replaced
The obj.checkData( ) function no longer exists, having been replaced by the
global function canSubmitPrompt( ) function. References to the checkData( )
button must be replaced with the new function.
For an example, refer to Knowledge Base (KB) article:
1036117 – JavaScript: Sample to automatically select first item in value
prompt
A bulk search/replace utility such as DRU may be useful to deal with this
issue.
The obj.checkData( ) function no longer exists, having been replaced by the
global function canSubmitPrompt( ) function. References to the checkData( )
button must be replaced with the new function.
For an example, refer to Knowledge Base (KB) article:
1036117 – JavaScript: Sample to automatically select first item in value
prompt
A bulk search/replace utility such as DRU may be useful to deal with this
issue.
Cognos 8.3 javascript update -- checkData ( ) Function Replaced
checkData ( ) Function Replaced
The obj.checkData( ) function no longer exists, having been replaced by the
global function canSubmitPrompt( ) function. References to the checkData( )
button must be replaced with the new function.
For an example, refer to Knowledge Base (KB) article:
1036117 – JavaScript: Sample to automatically select first item in value
prompt
A bulk search/replace utility such as DRU may be useful to deal with this
issue.
The obj.checkData( ) function no longer exists, having been replaced by the
global function canSubmitPrompt( ) function. References to the checkData( )
button must be replaced with the new function.
For an example, refer to Knowledge Base (KB) article:
1036117 – JavaScript: Sample to automatically select first item in value
prompt
A bulk search/replace utility such as DRU may be useful to deal with this
issue.
Cognos 8.3 javascript update --
autoSubmit( ) Function Replaced
The autoSubmit( ) function no longer exists, having been replaced by the
promptButtonFinish( ) or promptAction(‘finish’) function. References to the
autoSubmit( ) button must be replaced with the new function.
For an example, refer to Knowledge Base (KB) article:
1012254 – JavaScript: Set default value for a value prompt by using HTML
item
A bulk search/replace utility such as DRU may be useful to deal with this
issue.
The autoSubmit( ) function no longer exists, having been replaced by the
promptButtonFinish( ) or promptAction(‘finish’) function. References to the
autoSubmit( ) button must be replaced with the new function.
For an example, refer to Knowledge Base (KB) article:
1012254 – JavaScript: Set default value for a value prompt by using HTML
item
A bulk search/replace utility such as DRU may be useful to deal with this
issue.
Cognos 8.3 javascript update --
autoSubmit( ) Function Replaced
The autoSubmit( ) function no longer exists, having been replaced by the
promptButtonFinish( ) or promptAction(‘finish’) function. References to the
autoSubmit( ) button must be replaced with the new function.
For an example, refer to Knowledge Base (KB) article:
1012254 – JavaScript: Set default value for a value prompt by using HTML
item
A bulk search/replace utility such as DRU may be useful to deal with this
issue.
The autoSubmit( ) function no longer exists, having been replaced by the
promptButtonFinish( ) or promptAction(‘finish’) function. References to the
autoSubmit( ) button must be replaced with the new function.
For an example, refer to Knowledge Base (KB) article:
1012254 – JavaScript: Set default value for a value prompt by using HTML
item
A bulk search/replace utility such as DRU may be useful to deal with this
issue.
Cognos sample web service to execute a report
The Cognos KB site has a Java/AXIS based web service to run a report sample in their Proven Practices section. It includes a sample C# application to call the web service. You can see the document c8ReportRequestServiceNOTES.pdf for instructions on installation and operation.
Cognos sample web service to execute a report
The Cognos KB site has a Java/AXIS based web service to run a report sample in their Proven Practices section. It includes a sample C# application to call the web service. You can see the document c8ReportRequestServiceNOTES.pdf for instructions on installation and operation.
Cognos 8 Oracle Content Store
Here are some common issues in troubleshooting an Oracle Content Store creation.
A) JDBC driver(classes12.jar) has not been been copied from ORACLE_HOME/jdbc/lib to <C8_CRN_location>/webapps/p2pd/WEB-INF/lib. Ensure the 32-bit JDBC driver of the correct version and being used.
B) In SQL Plus, determine if the database is Unicode by typing the following Select statement:
1. Open SQL Plus
2. Issue the following command: select * from NLS_DATABASE_PARAMETERS;
3. Make sure the NLS_CHARACTERSET is one of the following: {UTF-8 or UTF-16, or AL32UTF8 or ALI6UTF16, or not unicode}. If the result set returns
an NLS_CHARACTERSET that is not Unicode, create a new database and specify AL32UTF8 or UTF-8 for the database character set parameters.
4. If the character set is different, create a new Oracle instance with the correct character set.
C) Ensure that the user account that accesses the database has permission to do the following:
connect to the database
create, alter, and drop tables
create, alter, and drop triggers
create, alter, and dropviews
create, alter, and drop procedures
create, alter, and drop sequences
Cognos 8 Oracle Content Store
Here are some common issues in troubleshooting an Oracle Content Store creation.
A) JDBC driver(classes12.jar) has not been been copied from ORACLE_HOME/jdbc/lib to <C8_CRN_location>/webapps/p2pd/WEB-INF/lib. Ensure the 32-bit JDBC driver of the correct version and being used.
B) In SQL Plus, determine if the database is Unicode by typing the following Select statement:
1. Open SQL Plus
2. Issue the following command: select * from NLS_DATABASE_PARAMETERS;
3. Make sure the NLS_CHARACTERSET is one of the following: {UTF-8 or UTF-16, or AL32UTF8 or ALI6UTF16, or not unicode}. If the result set returns
an NLS_CHARACTERSET that is not Unicode, create a new database and specify AL32UTF8 or UTF-8 for the database character set parameters.
4. If the character set is different, create a new Oracle instance with the correct character set.
C) Ensure that the user account that accesses the database has permission to do the following:
connect to the database
create, alter, and drop tables
create, alter, and drop triggers
create, alter, and dropviews
create, alter, and drop procedures
create, alter, and drop sequences
JDBC Driver Conflict for Oracle
If you use Oracle for data source, import source, logging database, or the content store database, you must ensure that there is no conflict with the JDBC driver file. In earlier releases of Cognos 8, Oracle databases required a classes12.jar file. In Cognos 8 Version 8.2, Oracle databases require an ojdbc14.jar file.
To ensure that there is no conflict, check the c8_location\webapps\p2pd\WEB-INF\lib directory on each computer where Content Manager, the Application Tier, Framework Manager, or Metric Studio is installed. If both the classes12.jar file and the ojdbc14.jar file are present, you must delete the obsolete classes12.jar file.
JDBC Driver Conflict for Oracle
If you use Oracle for data source, import source, logging database, or the content store database, you must ensure that there is no conflict with the JDBC driver file. In earlier releases of Cognos 8, Oracle databases required a classes12.jar file. In Cognos 8 Version 8.2, Oracle databases require an ojdbc14.jar file.
To ensure that there is no conflict, check the c8_location\webapps\p2pd\WEB-INF\lib directory on each computer where Content Manager, the Application Tier, Framework Manager, or Metric Studio is installed. If both the classes12.jar file and the ojdbc14.jar file are present, you must delete the obsolete classes12.jar file.
Starting and Stopping Cognos 8 in Silent Mode on UNIX and Linux Computers
You run Cognos Configuration in silent mode to apply the configuration settings and start the services on UNIX or Linux computers that do not support a Java-based graphical user interface. Before you run the configuration tool in silent mode, you should ensure the cogstartup.xml file is valid according to the rules defined in the cogstartup.xsd file. The cogstartup.xsd file is located in the c8_location/configuration directory.
Steps to Start Cognos 8
-
Ensure that the cogstartup.xml file, located in the c8_location/configuration directory, has been modified for your environment.
-
Go to the c8_location/bin directory.
-
Type the following command
./cogconfig.sh -s
Tip: To view log messages that were generated during an unattended configuration, see the cogconfig_response.csv file in the c8_location/logs directory.
Cognos Configuration applies the configuration settings specified in the cogstartup.xml file, encrypts credentials, generates digital certificates, and if applicable, starts the Cognos 8 service or process.
Steps to Stop Cognos 8
-
Go to the c8_location/bin directory.
-
Type the following command
./cogconfig.sh -stop
Starting and Stopping Cognos 8 in Silent Mode on UNIX and Linux Computers
You run Cognos Configuration in silent mode to apply the configuration settings and start the services on UNIX or Linux computers that do not support a Java-based graphical user interface. Before you run the configuration tool in silent mode, you should ensure the cogstartup.xml file is valid according to the rules defined in the cogstartup.xsd file. The cogstartup.xsd file is located in the c8_location/configuration directory.
Steps to Start Cognos 8
-
Ensure that the cogstartup.xml file, located in the c8_location/configuration directory, has been modified for your environment.
-
Go to the c8_location/bin directory.
-
Type the following command
./cogconfig.sh -s
Tip: To view log messages that were generated during an unattended configuration, see the cogconfig_response.csv file in the c8_location/logs directory.
Cognos Configuration applies the configuration settings specified in the cogstartup.xml file, encrypts credentials, generates digital certificates, and if applicable, starts the Cognos 8 service or process.
Steps to Stop Cognos 8
-
Go to the c8_location/bin directory.
-
Type the following command
./cogconfig.sh -stop
Cognos default Content Store Derby database
If you install Cognos Content Database, the default database that is created is given a user ID and password. It is recommend that you change this user ID and password.
Administration tasks for Cognos Content Database are performed using a utility named ij. The documentation for derby is available in the c8_location\derby10.1.2.1\docs directory where you installed Cognos Content Database.
Steps to Change the Default User Password
-
On the computer where you installed Cognos Content Database, go to the c8_location\derby10.1.2.1\bin directory.
-
Start the ij utility using the ij.bat or ij.ksh script file.
The ij utility is a command line utility for creating and managing Cognos Content Database.
-
Connect to the default database by typing the following ij utility command:
connect 'jdbc:derby://localhost:1527/cm;user=cognos;password=cognos';
If you changed the port number from the default 1527, use the correct port number for your Cognos Content Database.
The default database is named cm. The database name is case sensitive.
-
Change the default password for the cognos user by typing the following ij utility command:
CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY('derby.user.cognos', 'NewPassword');
The new password must be used for the next connection to the database.
-
Close the ij utility by typing the following command:
disconnect;
Steps to Create a New User and Password
-
On the computer where you installed Cognos Content Database, go to the c8_location\derby10.1.2.1\bin directory.
-
Start the ij utility using the ij.bat or ij.ksh script file.
-
Connect to the default database by typing the following ij utility command:
connect 'jdbc:derby://localhost:1527/cm;user=cognos;password=cognos';
If you changed the port number from the default 1527, use the correct port number for your Cognos Content Database.
The default database is named cm. The database name is case sensitive.
-
Create a new user by typing the following ij utility command:
CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY('derby.user.NewUser', 'NewUserPassword');
-
Give the new user full access to the database by typing the following ij utility command:
CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY ('derby.database.fullAccessUsers','cognos, NewUser');
The property that you are changing, the list of users, is a comma-delimited field. In this step, you are including the new user in the list of users with full access. The default user, cognos, is still part of the list of users with full access. You can remove the cognos user.
-
Close the ij utility by typing the following command:
disconnect;
Steps to Remove a User
-
On the computer where you installed Cognos Content Database, go to the c8_location\derby10.1.2.1\bin directory.
-
Start the ij utility using the ij.bat or ij.ksh script file.
-
Connect to the default database by typing the following ij utility command:
connect 'jdbc:derby://localhost:1527/cm;user=NewUser; password=NewUserPassword';
-
Choose the kind of user that you want to remove:
-
To remove a user from the list of users with full access, type the following ij utility command:
CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY ('derby.database.fullAccessUsers', 'NewUser');
You omit the user name from the list of users with full access. For example, the above command removes the default cognos user and keeps the new user that you just created.
-
To remove a user from the database, type the following ij utility command and omit the user password:
CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY('derby.user.cognos', '');
This command removes the password for the default cognos user, which also removes the user from the database.
-
-
Close the ij utility by typing the following command:
disconnect;
Cognos default Content Store Derby database
If you install Cognos Content Database, the default database that is created is given a user ID and password. It is recommend that you change this user ID and password.
Administration tasks for Cognos Content Database are performed using a utility named ij. The documentation for derby is available in the c8_location\derby10.1.2.1\docs directory where you installed Cognos Content Database.
Steps to Change the Default User Password
-
On the computer where you installed Cognos Content Database, go to the c8_location\derby10.1.2.1\bin directory.
-
Start the ij utility using the ij.bat or ij.ksh script file.
The ij utility is a command line utility for creating and managing Cognos Content Database.
-
Connect to the default database by typing the following ij utility command:
connect 'jdbc:derby://localhost:1527/cm;user=cognos;password=cognos';
If you changed the port number from the default 1527, use the correct port number for your Cognos Content Database.
The default database is named cm. The database name is case sensitive.
-
Change the default password for the cognos user by typing the following ij utility command:
CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY('derby.user.cognos', 'NewPassword');
The new password must be used for the next connection to the database.
-
Close the ij utility by typing the following command:
disconnect;
Steps to Create a New User and Password
-
On the computer where you installed Cognos Content Database, go to the c8_location\derby10.1.2.1\bin directory.
-
Start the ij utility using the ij.bat or ij.ksh script file.
-
Connect to the default database by typing the following ij utility command:
connect 'jdbc:derby://localhost:1527/cm;user=cognos;password=cognos';
If you changed the port number from the default 1527, use the correct port number for your Cognos Content Database.
The default database is named cm. The database name is case sensitive.
-
Create a new user by typing the following ij utility command:
CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY('derby.user.NewUser', 'NewUserPassword');
-
Give the new user full access to the database by typing the following ij utility command:
CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY ('derby.database.fullAccessUsers','cognos, NewUser');
The property that you are changing, the list of users, is a comma-delimited field. In this step, you are including the new user in the list of users with full access. The default user, cognos, is still part of the list of users with full access. You can remove the cognos user.
-
Close the ij utility by typing the following command:
disconnect;
Steps to Remove a User
-
On the computer where you installed Cognos Content Database, go to the c8_location\derby10.1.2.1\bin directory.
-
Start the ij utility using the ij.bat or ij.ksh script file.
-
Connect to the default database by typing the following ij utility command:
connect 'jdbc:derby://localhost:1527/cm;user=NewUser; password=NewUserPassword';
-
Choose the kind of user that you want to remove:
-
To remove a user from the list of users with full access, type the following ij utility command:
CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY ('derby.database.fullAccessUsers', 'NewUser');
You omit the user name from the list of users with full access. For example, the above command removes the default cognos user and keeps the new user that you just created.
-
To remove a user from the database, type the following ij utility command and omit the user password:
CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY('derby.user.cognos', '');
This command removes the password for the default cognos user, which also removes the user from the database.
-
-
Close the ij utility by typing the following command:
disconnect;
Errors Displayed Deploying to Oracle 10G Application Server
In a distributed installation, you can configure the log server on each Cognos 8 computer to send log messages to a single remote log server, which acts as a common log server. You can then configure the common log server to send the log messages to a local file or database on the same or another computer.
If the remote log server becomes unavailable, log messages are redirected to recovery files on the local computer in the c8_location\logs\recovery\remote directory. These recovery files have timestamp information in their file names, and are not readable like regular log files. When the remote log server becomes available, an automatic recovery process moves all log information to the remote log server and deletes the local log files.
Errors Displayed Deploying to Oracle 10G Application Server
In a distributed installation, you can configure the log server on each Cognos 8 computer to send log messages to a single remote log server, which acts as a common log server. You can then configure the common log server to send the log messages to a local file or database on the same or another computer.
If the remote log server becomes unavailable, log messages are redirected to recovery files on the local computer in the c8_location\logs\recovery\remote directory. These recovery files have timestamp information in their file names, and are not readable like regular log files. When the remote log server becomes available, an automatic recovery process moves all log information to the remote log server and deletes the local log files.
Cognos 8 logging
In a distributed installation, you can configure the log server on each Cognos 8 computer to send log messages to a single remote log server, which acts as a common log server. You can then configure the common log server to send the log messages to a local file or database on the same or another computer.
If the remote log server becomes unavailable, log messages are redirected to recovery files on the local computer in the c8_location\logs\recovery\remote directory. These recovery files have timestamp information in their file names, and are not readable like regular log files. When the remote log server becomes available, an automatic recovery process moves all log information to the remote log server and deletes the local log files.
Cognos 8 logging
In a distributed installation, you can configure the log server on each Cognos 8 computer to send log messages to a single remote log server, which acts as a common log server. You can then configure the common log server to send the log messages to a local file or database on the same or another computer.
If the remote log server becomes unavailable, log messages are redirected to recovery files on the local computer in the c8_location\logs\recovery\remote directory. These recovery files have timestamp information in their file names, and are not readable like regular log files. When the remote log server becomes available, an automatic recovery process moves all log information to the remote log server and deletes the local log files.
Metric Studio Error -- CMM-SYS-5999
If you have multiple dispatchers and encounter the following error:
CMM-SYS-5999 - The Metrics Management Service encountered an internal error.
java.lang.UnsatisfiedLinkError: no ocijdbc9 in java.library.path
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1517)
at java.lang.Runtime.loadLibrary0(Runtime.java:788)
at java.lang.System.loadLibrary(System.java:834)
at oracle.jdbc.oci8.OCIDBAccess.logon(OCIDBAccess.java:262)
at oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:346)
at oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.java:468)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:314)
at java.sql.DriverManager.getConnection(DriverManager.java:512)
at java.sql.DriverManager.getConnection(DriverManager.java:171)
at com.cognos.canaveral.database.ConnectionPool$PooledConnection.reConnect(ConnectionPool.java:603)
at com.cognos.canaveral.database.ConnectionPool.resetConnections(ConnectionPool.java:397)
at com.cognos.canaveral.database.ConnectionPool.activateMoreConnections(ConnectionPool.java:365)
at com.cognos.canaveral.database.ConnectionPool.initialize(ConnectionPool.java:244)
at com.cognos.canaveral.database.ConnectionPool.<init>(ConnectionPool.java:82)
at com.cognos.canaveral.database.PooledDBManager.initialize(PooledDBManager.java:98)
at com.cognos.canaveral.database.PooledDBManager.<init>(PooledDBManager.java:50)
at com.cognos.alp.control.Alp.createDBManager(Alp.java:1624)
at com.cognos.cmm.MetricsManager.createDBInstance(MetricsManager.java:902)
at com.cognos.cmm.MetricsManager.getUserDBAccessor(MetricsManager.java:833)
at com.cognos.cmm.MetricsManager.processRequest(MetricsManager.java:483)
at com.cognos.alp.control.Alp.service(Alp.java:621)
at com.cognos.cpms.dispatcher.DispatcherAlpDriver$RunnableAlpRequest.run(DispatcherAlpDriver.java:377)
at java.lang.Thread.run(Thread.java:534)
]]></item></parameters>
The problem likely occurred because the classes12.jar and the ojdbc14.jar file had been copied into the .../webapps/p2pd/WEB-INF/lib directory on the problem dispatcher. Metric Studio 8.2 requires the use of the ojdbc14.jar file, remove the classes12.jar file from the .../webapps/p2pd/WEB-INF/lib directory
1. Stop the Cognos 8 service
2. Navigate to the .../webapps/p2pd/WEB-INF/lib directory
3. Remove the classes12.jar file
4. Start the Cognos 8 service
Metric Studio Error -- CMM-SYS-5999
If you have multiple dispatchers and encounter the following error:
CMM-SYS-5999 - The Metrics Management Service encountered an internal error.
java.lang.UnsatisfiedLinkError: no ocijdbc9 in java.library.path
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1517)
at java.lang.Runtime.loadLibrary0(Runtime.java:788)
at java.lang.System.loadLibrary(System.java:834)
at oracle.jdbc.oci8.OCIDBAccess.logon(OCIDBAccess.java:262)
at oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:346)
at oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.java:468)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:314)
at java.sql.DriverManager.getConnection(DriverManager.java:512)
at java.sql.DriverManager.getConnection(DriverManager.java:171)
at com.cognos.canaveral.database.ConnectionPool$PooledConnection.reConnect(ConnectionPool.java:603)
at com.cognos.canaveral.database.ConnectionPool.resetConnections(ConnectionPool.java:397)
at com.cognos.canaveral.database.ConnectionPool.activateMoreConnections(ConnectionPool.java:365)
at com.cognos.canaveral.database.ConnectionPool.initialize(ConnectionPool.java:244)
at com.cognos.canaveral.database.ConnectionPool.<init>(ConnectionPool.java:82)
at com.cognos.canaveral.database.PooledDBManager.initialize(PooledDBManager.java:98)
at com.cognos.canaveral.database.PooledDBManager.<init>(PooledDBManager.java:50)
at com.cognos.alp.control.Alp.createDBManager(Alp.java:1624)
at com.cognos.cmm.MetricsManager.createDBInstance(MetricsManager.java:902)
at com.cognos.cmm.MetricsManager.getUserDBAccessor(MetricsManager.java:833)
at com.cognos.cmm.MetricsManager.processRequest(MetricsManager.java:483)
at com.cognos.alp.control.Alp.service(Alp.java:621)
at com.cognos.cpms.dispatcher.DispatcherAlpDriver$RunnableAlpRequest.run(DispatcherAlpDriver.java:377)
at java.lang.Thread.run(Thread.java:534)
]]></item></parameters>
The problem likely occurred because the classes12.jar and the ojdbc14.jar file had been copied into the .../webapps/p2pd/WEB-INF/lib directory on the problem dispatcher. Metric Studio 8.2 requires the use of the ojdbc14.jar file, remove the classes12.jar file from the .../webapps/p2pd/WEB-INF/lib directory
1. Stop the Cognos 8 service
2. Navigate to the .../webapps/p2pd/WEB-INF/lib directory
3. Remove the classes12.jar file
4. Start the Cognos 8 service
QE-DEF-0259 Error
This error occurs if you use braces { } in the wrong position in an expression. Cognos 8 expects anything between the braces { } to be at the same level as a function. If you have used braces elsewhere in an expression, you will see the following error message:
QE-DEF-0259 There was a parsing error
You can also use braces to send unique syntax to the data source. For example, your database uses a keyword for a function but this keyword is not used in Cognos 8. Cognos 8 does not validate the syntax you enter between braces. The syntax is simply sent to the data source.
The solution is to make sure that braces are not used in the wrong positions.
QE-DEF-0259 Error
This error occurs if you use braces { } in the wrong position in an expression. Cognos 8 expects anything between the braces { } to be at the same level as a function. If you have used braces elsewhere in an expression, you will see the following error message:
QE-DEF-0259 There was a parsing error
You can also use braces to send unique syntax to the data source. For example, your database uses a keyword for a function but this keyword is not used in Cognos 8. Cognos 8 does not validate the syntax you enter between braces. The syntax is simply sent to the data source.
The solution is to make sure that braces are not used in the wrong positions.
Unable to Use an IQD Created in Framework Manager That Contains an Oracle
In Transformer, when trying to open an IQD created in Framework Manager that contains an Oracle stored procedure, you may receive a message similar to the following:
(TR0118) Transformer can't read the database [datasource] defined in <Lan location>\<datasource><iqd_name>
.iqd. DMS-E_General A general exception has occurred during operation 'execute' The native SQL generated in an IQD created in Framework Manager is wrong. The IQD cannot be used in Transformer.To resolve this problem, execute the stored procedure in Framework Manager and set the
Externalize Method to IQD. Create a model query subject from the executed stored procedure, then publish the package and open it in Transformer
Unable to Use an IQD Created in Framework Manager That Contains an Oracle
In Transformer, when trying to open an IQD created in Framework Manager that contains an Oracle stored procedure, you may receive a message similar to the following:
(TR0118) Transformer can't read the database [datasource] defined in <Lan location>\<datasource><iqd_name>
.iqd. DMS-E_General A general exception has occurred during operation 'execute' The native SQL generated in an IQD created in Framework Manager is wrong. The IQD cannot be used in Transformer.To resolve this problem, execute the stored procedure in Framework Manager and set the
Externalize Method to IQD. Create a model query subject from the executed stored procedure, then publish the package and open it in Transformer
Framework Manager and Oracle Full Outer Joins
When using an Oracle RDBMS data source prior to version 9.2.02, full outer joins return incorrect data results. To avoid this problem, Cognos 8 processes these as local operations.
As a result of this processing, you must set the query processing to limitedLocal for any projects that expect explicit or implicit outer joins.
Framework Manager and Oracle Full Outer Joins
When using an Oracle RDBMS data source prior to version 9.2.02, full outer joins return incorrect data results. To avoid this problem, Cognos 8 processes these as local operations.
As a result of this processing, you must set the query processing to limitedLocal for any projects that expect explicit or implicit outer joins.
Cognos Planning -- command line options
Command Line Options
You must enclose all arguments containing special characters in double quotation marks. Each argument has a number associated with it.:
Options Definitions Parameters
-m Runs any Analyst macro using the library number
-1 LibNo -2 Macro_Name -3 UID -4 PWD -5 Language -6 Log_File
-m0 Runs any Analyst macro using the library name
-1 LibName -2 Macro_Name -3 UID -4 PWD -5 Language -6
Log_File
-m1 Runs a macro that reruns an IQD to update a D-List
-1 LibNo -2 D-List_Name -3 UID -4 PWD -5 Language -6
Keep_GUID
-m2 Runs a macro that updates an IQD
-1 LibNo -2 D-List_Name -3 UID -4 PWD -5 Language -6 Update
DW-7 bAddNewItems -8 bRemoveDeletedItems
-m3 Runs a macro that updates a data warehouse
-1 LibNo -2 D-List_Name -3UID -4 PWD -5 Language
-m4 Run a macro that reruns an IQD to update an e.Lis.
-1 LibNo -2 D-List_Name -3 UID -4 PWD -5 Language -6
Keep_GUID -7IncludeAllItems -8TextFilePath
-b Runs a Batch Utility job -1 Job_Name -2 UID -3 PWD
-f Run a command file Command_File_Path
Cognos Planning -- command line example
To run a macro named UPDATE ALL, using library number 1090, in OS Sign-on mode within Access Manager, in English, and creating a log in c:\MyLogFile.txt, type the following:
CepBatch -m -1 1090 -2 "UPDATE ALL" -6 "c:\MyLogFile.txt"
To run the same macro without using an OS sign-on, type the following:
CepBatch.exe –m -1 1090 -2 "UPDATE ALL" -3 SmithJ -4 psswd1 -6
"c:\MyLogFile.txt"
Cognos Planning -- command line options
Command Line Options
You must enclose all arguments containing special characters in double quotation marks. Each argument has a number associated with it.:
Options Definitions Parameters
-m Runs any Analyst macro using the library number
-1 LibNo -2 Macro_Name -3 UID -4 PWD -5 Language -6 Log_File
-m0 Runs any Analyst macro using the library name
-1 LibName -2 Macro_Name -3 UID -4 PWD -5 Language -6
Log_File
-m1 Runs a macro that reruns an IQD to update a D-List
-1 LibNo -2 D-List_Name -3 UID -4 PWD -5 Language -6
Keep_GUID
-m2 Runs a macro that updates an IQD
-1 LibNo -2 D-List_Name -3 UID -4 PWD -5 Language -6 Update
DW-7 bAddNewItems -8 bRemoveDeletedItems
-m3 Runs a macro that updates a data warehouse
-1 LibNo -2 D-List_Name -3UID -4 PWD -5 Language
-m4 Run a macro that reruns an IQD to update an e.Lis.
-1 LibNo -2 D-List_Name -3 UID -4 PWD -5 Language -6
Keep_GUID -7IncludeAllItems -8TextFilePath
-b Runs a Batch Utility job -1 Job_Name -2 UID -3 PWD
-f Run a command file Command_File_Path
Cognos Planning -- command line example
To run a macro named UPDATE ALL, using library number 1090, in OS Sign-on mode within Access Manager, in English, and creating a log in c:\MyLogFile.txt, type the following:
CepBatch -m -1 1090 -2 "UPDATE ALL" -6 "c:\MyLogFile.txt"
To run the same macro without using an OS sign-on, type the following:
CepBatch.exe –m -1 1090 -2 "UPDATE ALL" -3 SmithJ -4 psswd1 -6
"c:\MyLogFile.txt"
Cognos 8 BI Powerplay Studio
What functionality does the PowerPlay Studio in IBM Cognos 8 BI PowerPlay have in common with Analysis Studio? How are they different?
An IBM Cognos PowerPlay user may wonder if Analysis Studio is the same as the IBM Cognos PowerPlay Series 7 web functionality. Analysis Studio provides deep comparative analysis, which IBM Cognos 8 BI PowerPlay Studio does not offer. The PowerPlay Studio in IBM Cognos 8 BI PowerPlay offers a rich exploration experience.
One of the biggest differences between Analysis Studio and the PowerPlay Studio in IBM Cognos 8 BI PowerPlay is that Analysis Studio enables analysis of information independent of where your data is stored. This means that you can analyze and report against online analytical processing (OLAP) dimensionally-aware relational sources. IBM Cognos PowerPlay users who are familiar with IBM Cognos PowerPlay web functionality and exploration capabilities, and who expect the same functionality and exploration capabilities in Cognos 8, should consider moving to IBM Cognos 8 BI PowerPlay.
IBM Cognos PowerPlay users, who perform analysis, or deep comparative analysis, use unbalanced hierarchies, or use large data sets will find that Analysis Studio is well suited for their business needs. Consider migrating any IBM Cognos PowerPlay Series 7 applications that would benefit from this functionality to Analysis Studio when the time is right for your business.
What version of IBM Cognos PowerPlay do customers have to be on to migrate to IBM Cognos 8 BI PowerPlay?
Customers must be running IBM Cognos PowerPlay Series 7 version 4 in order to migrate to IBM Cognos 8 BI PowerPlay.
What, if any, new functionality is gained when moving to the PowerPlay Studio in IBM Cognos 8 BI PowerPlay from IBM Cognos PowerPlay Series 7?
IBM Cognos 8 BI PowerPlay users have the advantage of access to additional capabilities in IBM Cognos 8 BI such as the Professional report authoring mode in Report Studio, richer drill-through capabilities, and scheduling and event management capabilities in the Cognos 8 platform.Administrators will be able to manage IBM Cognos PowerPlay services, cubes, and report settings from within the Cognos 8 zero-footprint administration console. In addition, administrators will be able to take advantage of all of Cognos 8 administration, lowering maintenance costs, and accessing the Cognos 8 infrastructure for scalability and performance.
When used in conjunction with cubes created in Transformer 8, IBM Cognos 8 BI PowerPlay can also leverage the security from a Cognos 8 namespace, as an additional alternative to an IBM Cognos PowerPlay Series 7 namespace.
.
Cognos 8 BI Powerplay Studio
What functionality does the PowerPlay Studio in IBM Cognos 8 BI PowerPlay have in common with Analysis Studio? How are they different?
An IBM Cognos PowerPlay user may wonder if Analysis Studio is the same as the IBM Cognos PowerPlay Series 7 web functionality. Analysis Studio provides deep comparative analysis, which IBM Cognos 8 BI PowerPlay Studio does not offer. The PowerPlay Studio in IBM Cognos 8 BI PowerPlay offers a rich exploration experience.
One of the biggest differences between Analysis Studio and the PowerPlay Studio in IBM Cognos 8 BI PowerPlay is that Analysis Studio enables analysis of information independent of where your data is stored. This means that you can analyze and report against online analytical processing (OLAP) dimensionally-aware relational sources. IBM Cognos PowerPlay users who are familiar with IBM Cognos PowerPlay web functionality and exploration capabilities, and who expect the same functionality and exploration capabilities in Cognos 8, should consider moving to IBM Cognos 8 BI PowerPlay.
IBM Cognos PowerPlay users, who perform analysis, or deep comparative analysis, use unbalanced hierarchies, or use large data sets will find that Analysis Studio is well suited for their business needs. Consider migrating any IBM Cognos PowerPlay Series 7 applications that would benefit from this functionality to Analysis Studio when the time is right for your business.
What version of IBM Cognos PowerPlay do customers have to be on to migrate to IBM Cognos 8 BI PowerPlay?
Customers must be running IBM Cognos PowerPlay Series 7 version 4 in order to migrate to IBM Cognos 8 BI PowerPlay.
What, if any, new functionality is gained when moving to the PowerPlay Studio in IBM Cognos 8 BI PowerPlay from IBM Cognos PowerPlay Series 7?
IBM Cognos 8 BI PowerPlay users have the advantage of access to additional capabilities in IBM Cognos 8 BI such as the Professional report authoring mode in Report Studio, richer drill-through capabilities, and scheduling and event management capabilities in the Cognos 8 platform.Administrators will be able to manage IBM Cognos PowerPlay services, cubes, and report settings from within the Cognos 8 zero-footprint administration console. In addition, administrators will be able to take advantage of all of Cognos 8 administration, lowering maintenance costs, and accessing the Cognos 8 infrastructure for scalability and performance.
When used in conjunction with cubes created in Transformer 8, IBM Cognos 8 BI PowerPlay can also leverage the security from a Cognos 8 namespace, as an additional alternative to an IBM Cognos PowerPlay Series 7 namespace.
.
Integrating IBM Lotus Domino for BI with Cognos 8
http://www.acumetricsbi.com/assets/sunandson.pdf
This capability is provided through a simple wizard-style interface that allows you to integrate Lotus Notes databases and applications with your Cognos enterprise BI infrastructure. Another key feature is the handling of data type fidelity, which has historically been difficult to do. With the Cognos BI Modeler for Lotus Domino date, numeric, multi-value, and custom computed fields are easily incorporated into the BI environment. In addition, the solution automatically optimizes the data for fast query access. Once the Lotus Notes data has been modeled, a Cognos metadata model is automatically generated. The metadata model is then translated into a Cognos 8 Framework, and all the Lotus Notes data can be joined to other enterprise data sources without coding or data mirroring.
Technical Benefits
􀂃 Easy selection of Notes data sources, tables, and columns.
􀂃 Choose data elements and label them with names that are meaningful to the business.
􀂃 Manage different data types automatically.
􀂃 Automatic data optimization for fast query access.
􀂃 Access all BI capabilities for Lotus Notes data,including reporting, dashboarding, analysis, scorecarding, and business event management.
Integrating IBM Lotus Domino for BI with Cognos 8
http://www.acumetricsbi.com/assets/sunandson.pdf
This capability is provided through a simple wizard-style interface that allows you to integrate Lotus Notes databases and applications with your Cognos enterprise BI infrastructure. Another key feature is the handling of data type fidelity, which has historically been difficult to do. With the Cognos BI Modeler for Lotus Domino date, numeric, multi-value, and custom computed fields are easily incorporated into the BI environment. In addition, the solution automatically optimizes the data for fast query access. Once the Lotus Notes data has been modeled, a Cognos metadata model is automatically generated. The metadata model is then translated into a Cognos 8 Framework, and all the Lotus Notes data can be joined to other enterprise data sources without coding or data mirroring.
Technical Benefits
􀂃 Easy selection of Notes data sources, tables, and columns.
􀂃 Choose data elements and label them with names that are meaningful to the business.
􀂃 Manage different data types automatically.
􀂃 Automatic data optimization for fast query access.
􀂃 Access all BI capabilities for Lotus Notes data,including reporting, dashboarding, analysis, scorecarding, and business event management.
Cognos 8 error message codes
CNC-SDC-0366
Unable to find data for related attachment with source ID:[{0}]
Ensure that the content IDs are properly constructed in the SOAP request.
CNC-SDC-0397
Unable to retrieve attachments from the SOAP message.
Ensure that you streamed the attachment in the SOAP request.
Dispatcher Errors
DPR-DPR-1031
Unable to complete the request. The user does not have the 'canUseServerAdministrationTool'
capability.
Ensure that the user has the canUseServerAdministrationTool capability.
DPR-DPR-1032
The stop request cannot be completed because the user lacks write capability on this object.
Ensure that the user has write permission for the service object.
Unable to find data for related attachment with source ID:[{0}]
Ensure that the content IDs are properly constructed in the SOAP request.
CNC-SDC-0397
Unable to retrieve attachments from the SOAP message.
Ensure that you streamed the attachment in the SOAP request.
Dispatcher Errors
DPR-DPR-1031
Unable to complete the request. The user does not have the 'canUseServerAdministrationTool'
capability.
Ensure that the user has the canUseServerAdministrationTool capability.
DPR-DPR-1032
The stop request cannot be completed because the user lacks write capability on this object.
Ensure that the user has write permission for the service object.
Cognos 8 error message codes
CNC-SDC-0366
Unable to find data for related attachment with source ID:[{0}]
Ensure that the content IDs are properly constructed in the SOAP request.
CNC-SDC-0397
Unable to retrieve attachments from the SOAP message.
Ensure that you streamed the attachment in the SOAP request.
Dispatcher Errors
DPR-DPR-1031
Unable to complete the request. The user does not have the 'canUseServerAdministrationTool'
capability.
Ensure that the user has the canUseServerAdministrationTool capability.
DPR-DPR-1032
The stop request cannot be completed because the user lacks write capability on this object.
Ensure that the user has write permission for the service object.
Unable to find data for related attachment with source ID:[{0}]
Ensure that the content IDs are properly constructed in the SOAP request.
CNC-SDC-0397
Unable to retrieve attachments from the SOAP message.
Ensure that you streamed the attachment in the SOAP request.
Dispatcher Errors
DPR-DPR-1031
Unable to complete the request. The user does not have the 'canUseServerAdministrationTool'
capability.
Ensure that the user has the canUseServerAdministrationTool capability.
DPR-DPR-1032
The stop request cannot be completed because the user lacks write capability on this object.
Ensure that the user has write permission for the service object.
Cognos SDK Secondary Requests
Each time you call an asynchronous method, the set of methods that you can use as secondary
requests is returned in property secondaryRequests of class asynchReply. Which methods are
included depends on property status of class asynchReply. The following table lists valid
secondary requests for all methods that return a value of class asynchReply.
Status Secondary requests
complete method release (conversation)
conversationComplete no additional requests are possible
stillWorking method cancel (conversation)
method wait (conversation, parameterValues, options)
working method cancel (conversation)
method wait (conversation, parameterValues, options)
When property status of class asynchReply is complete, the report service may return
additional secondary requests, depending on the report status. The report status is stored as
property status of class asynchDetailReportStatus. An instance of this class may be returned in
property details of class asynchReply.
requests is returned in property secondaryRequests of class asynchReply. Which methods are
included depends on property status of class asynchReply. The following table lists valid
secondary requests for all methods that return a value of class asynchReply.
Status Secondary requests
complete method release (conversation)
conversationComplete no additional requests are possible
stillWorking method cancel (conversation)
method wait (conversation, parameterValues, options)
working method cancel (conversation)
method wait (conversation, parameterValues, options)
When property status of class asynchReply is complete, the report service may return
additional secondary requests, depending on the report status. The report status is stored as
property status of class asynchDetailReportStatus. An instance of this class may be returned in
property details of class asynchReply.
Cognos SDK Secondary Requests
Each time you call an asynchronous method, the set of methods that you can use as secondary
requests is returned in property secondaryRequests of class asynchReply. Which methods are
included depends on property status of class asynchReply. The following table lists valid
secondary requests for all methods that return a value of class asynchReply.
Status Secondary requests
complete method release (conversation)
conversationComplete no additional requests are possible
stillWorking method cancel (conversation)
method wait (conversation, parameterValues, options)
working method cancel (conversation)
method wait (conversation, parameterValues, options)
When property status of class asynchReply is complete, the report service may return
additional secondary requests, depending on the report status. The report status is stored as
property status of class asynchDetailReportStatus. An instance of this class may be returned in
property details of class asynchReply.
requests is returned in property secondaryRequests of class asynchReply. Which methods are
included depends on property status of class asynchReply. The following table lists valid
secondary requests for all methods that return a value of class asynchReply.
Status Secondary requests
complete method release (conversation)
conversationComplete no additional requests are possible
stillWorking method cancel (conversation)
method wait (conversation, parameterValues, options)
working method cancel (conversation)
method wait (conversation, parameterValues, options)
When property status of class asynchReply is complete, the report service may return
additional secondary requests, depending on the report status. The report status is stored as
property status of class asynchDetailReportStatus. An instance of this class may be returned in
property details of class asynchReply.
Subscribe to:
Posts (Atom)