Home RSS Feeds IBM Cognos Series 7
Follow us on Twitter
Cognos Feeds
Knowledge Articles
CogKnowHow.com - The IBM Cognos Knowledge Base | Links Documentation Forum Community Tips and Tricks

  • Sun Java System Directory Server software is no longer supplied with IBM Cognos Series 7.4 MR4

    IBM no longer has the rights to redistribute the Sun Java System Directory Server, as done in prior releases. Customers who received this software with previous Series 7 versions continue to have the rights to use the Directory Server versions they received with Cognos software, however, they cannot receive updated versions from IBM.

    Cognos Series 7 continues to support the use of the Sun Java Directory Server in addition to IBM Tivoli Directory Servers and Microsoft Active Directory product with Series 7. It is now, however, up to customers to provide their own compatible directory server. For details on all Directory Server versions supported with Series 7 please see the Cognos Series 7 Software Environments page at http://www.ibm.com/support/docview.wss?uid=swg27014445.

     

    www.cogknowhow.com



  • Unable to launch Transformer, no error message at all

    Symptom
    Clicking on the trnsfrmr.exe or executing it from the command line will appear to do nothing.

    Problem
    Trnsfrmr.exe will not launch. No error messages are displayed.

    Cause
    DEP (Data Execution Prevention) is preventing the application from executing correctly.

    Solution
    Disabling DEP completely, or add the transformer executable to the list of allowed programs in DEP may resolve this issue.

    Steps:

    1. Right click on "My Computer", choose "properties"
    2. Click the "Advanced" tab, then click "settings" under the "Performance" section
    3. Choose the "Data Execution Prevention" tab
    4. Select "Turn on DEP for all programs and services except those I select"
    5. Click "Add...", then select the the transformer executable
    6. Click "Apply", then "OK" twice.

     



  • Impromptu Error Codes

    Description of Cognos Impromptu error codes. Some error codes have solutions.

    100 to 299 Critical errors. These can occur at either compile-time or run time, depending on the nature of the error.
    300 to 499 Warnings. These are ignored unless the UseQueryWarnings property is set to 1.
    500 or greater Critical run time errors.

    100: Cannot execute query. Processing requirements exceed the current Client/Server limits.
    101: Data item [%1] could not be found.
    102: Data item [%1] is invalid because [%2] could not be found.
    103: Using the Governor denied Database Column [%1].
    104: This report will result in a 'cross product' query. This User Profile prevents the use of 'cross product' reports.
    105: The query for this report contains an 'outer join'. This User Profile prevents the use of 'outer join' queries.
    106: This report sorts on the non-indexed columns.
    107: This report contains circular [DATASET] references: %1.
    108: This report contains a prompt nested within a sub-report: %1.
    109: This report uses %1 tables. This exceeds the current Governor restriction of %2 tables for a report.
    110: Data item [%1] is invalid because it contains additional invalid Data Items.
    111: Invalid SQL query. Use read-only SELECT statements.
    112: Prompt uses column %1 of report %2 which doesn't exist.
    113: Prompt displays column %1 of report %2 which doesn't exist.
    300: This report is expected to use %1 tables.
    301: This report is expected to return %1 rows.
    302: The expected report preparation time is %1.
    303: This report suppresses duplicates.
    304: This report will result in a 'cross product' query.
    305: This report sorts on the non-indexed columns.
    306: The query for this report contains an 'outer join'.
    307: This crosstab report contains a query column, %1, that no longer exists.
    308: This crosstab report contains a bad reference to %2 in a conditional format.
    309: This crosstab report contains a bad reference in %1 to %2.
    310: This crosstab report contains a bad reference to %2 in the detail filter.
    311: This crosstab report contains a bad reference to %2 in the summary filter.
    500: This report exceeded the current Governor Restriction of %1 report preparation time.
    501: Database Retrieval Limit reached.  Governor restrictions specify a retrieval limit of %1 rows for the current User Profile.
    502: Could not open the following [DATASET] report: %1.

    24577
    An error has occurred during execution of the query.
    An error condition has been detected during the execution of the current query.
    The content of this message will vary depending on the nature of the problem.

    24578
    The stored procedure name has to be initialized first.
    You've attempted to execute a stored procedure before you've set the procedure name. Use the SetProcedure Method to set the name of the stored procedure.

    24579
    Parameter number <type> type is not supported.
    You've specified an invalid parameter type for a stored procedure parameter.

    24580
    Syntax error the char descriptor has to be VarChar, Char, or LongVarChar.
    You've specified an invalid descriptor for a variable length parameter of a stored procedure. Specify either VarChar[n], Char[n], or LongVarChar[n], where n indicates the maximum size for the variable length parameter. See the SetProcedure Method.

    24581
    Stored procedure has to be executed first.
    You've attempted to obtain the value of an output parameter before you've exected the stored procedure. Use the Execute Method to execute the stored procedure.

    24582
    The user class password is not correct.
    You've specified an invalid user class password. Ensure that the user class password is valid.

    24583
    Out of memory.
    The OLE automation procedure has run out of memory. Try closing some applications and running the automation script again.

    24584
    Parameter <parm> is invalid.
    You've specified an invalid parameter as the input to a method. For example, Impromptu has encountered a Boolean value for a parameter when a string value is expected.
    Make sure that you've specified the parameters correctly. Ensure that you also provide a comma to delimit each parameter when omitting values for some parameters.

    24585
    Catalog is not distributed. Cannot update.
    You've tried to use the UpdateCatalog method to obtain the latest changes for a catalog. The UpdateCatalog method is valid only for distributed catalogs, not for personal, shared, or secured catalogs.

    24587
    Update failed due to internal error. Contact customer support.
    CognosScript has encountered a fatal internal error.

    24588
    Current catalog specifies a master catalog which is not an Impromptu Catalog.
    When attempting to update your local copy of a distributed catalog, Impromptu has encountered a problem with the master catalog.

    24589
    Could not open the master catalog for update.
    The UpdateCatalog method could not open the master catalog. Make sure that you have the necessary LAN access, and that the master catalog exists and is intact.

    24590
    Master catalog is an incompatible version.
    During an UpdateCatalog, the master catalog could not be opened because it was created with an earlier version of Impromptu. Contact your database administrator.

    24591
    Catalog method called when no catalog was open.
    You've attempted to call a method that operates on a catalog when no catalog is currently open. Use the OpenCatalog Method to open a catalog before using methods such as ChangeUserClass, ConnectDatabase, CloseCatalog, UpdateCatalog, or AddTable.

    24592
    No valid selection for this operation.
    The GetSelectedText method has not found any valid selected text. Use this error to trap whether an Impromptu user has selected text prior to launching a macro that uses the GetSelectedText method.

    24593
    This catalog could not be found. <catalogname>
    A catalog name specified in a method could not be found. Ensure that the name is specified correctly, and that you have read access to it.

    24594
    Unable to open this catalog. <catalogname>
    A catalog that you've specified in either the OpenCatalog method or or GenerateReport method could not be opened. Ensure that the name is specified correctly, and that you have read access to it.

    24595
    Table name parameter is empty.
    You have not specified a value for theTable from within either the GenerateReport method or the AddTable method.

    24596
    Specified table was not found.
    Within the GenerateReport method or the AddTable method, the specified Table could not be found. Ensure that you've specified the correct name for the table.

    24597
    Unable to generate default report.
    Login or table information is valid, however, the GenerateReport method is unable to generate a default report. Ensure that the template name is specified correctly. Ensure also that the method didn't try to create the report on a full disk, and that the name specified for the report doesn't already exist.

    24598
    This Template could not be found. <templatename>
    The ApplyTemplate method could not locate the specified template. Ensure that you've specified the correct name for the template and that you have the necessary LAN access to it.

    24599
    Report could not be opened.
    The OpenReport method could not locate the specified Impromptu report. Ensure that you've specified the correct name for the report and that you have the necessary LAN access to it.

    24600
    Current catalog is read-only.
    You've attempted to make changes to the current catalog with the UpdateCatalog method. Check that the catalog file (CAT) is not read-only.

    24601
    Unable to add table <Database><HostDatabase><DBOwner><TableName>.
    The AddTable method was unable to add the specified table. Ensure that the database (Impromptu logical database name), HostDatabase (Host database name), DBOwner (host database owner), and TableName are all specified correctly. Ensure also that your connection to the database is active.

    24602
    Database name is invalid.
    The AddTable method has detected an invalid database name. Ensure that the database (Impromptu logical database name) name is specified correctly.

    24603
    Wrong or insufficient information provided. Could not connect database.
    In the ConnectDatabase method, the information provided was not sufficient to connect the database. Ensure that you've provided all of the required parameters (user ID, password).

    24604
    Login error while connecting the database.
    In the ConnectDatabase method, an error other than a security error occurred during an attempt to connect to the database.

    24605
    Database is already connected.
    You've used the ConnectDatabase method when the catalog is already connected to its associated database.

    24606
    Login error.  <errortype>
    In the ConnectDatabase method, the user ID and password are specified incorrectly or are not sufficient for the current level of security.

    24608
    Cannot execute a method.
    Impromptu is busy and cannot execute a macro method.

    24609
    Cannot convert to a snapshot report.
    The CreateSnapshot method is unable to save the current report as a snapshot. Ensure that your disk has sufficient space to store a snapshot of the report data.

    24610
    This report cannot be converted to access the database.
    The current report cannot revert to database access from a snapshot. Ensure that the connection to the database is active.

    24611
    Invalid printer name.
    You have specified the name of a printer that does not exist in the FileSetPrinter method. Make sure that the value specified for PrinterName matches exactly (including the case) the device name that's listed in the [Devices] section of your WIN.INI file. In general, this should be the name of the printer as it's displayed in Print Manager, up to but not including the "on <port number>" qualifier.

    24612
    The printer driver is not installed.
    Windows is unable to locate the printer driver for the printer that you've specified in the FileSetPrinter method. Ensure that the printer driver is installed correctly.

    24613
    Extended device mode is not supported with this driver.

    24614
    The driver could not get the size of the initialization buffer.

    24615
    The report cannot be edited.

    24616
    Multiple errors have occured with Impromptu. Use GetNextQueryError() method to retrieve the error information.
    The current report cannot execute because of query errors. Use the GetNextQueryError method to return the error number(s) and description.

    24617
    User class restriction.The report can not be created.
    A user class restriction, such as being prohibited from accessing a specific table or folder, is preventing the current report from executing successfully. Ensure that the restrictions for the current user class do not conflict with the report requirements.

    24618
    *** Unknown Error Type ***
    Impromptu has encountered an unexpected error. Contact Cognos Customer Support.

    24641
    Impromptu cannot open the required catalog.
    The required catalog cannot be open. Ensure you have specified the correct catalog name.

    24642
    Impromptu could not connect to the database.
    Ensure that the correct database has been specified.



  • Transformer batch mode switches in Scheduler

    Transformer batch mode switches in Scheduler

    Solution Description
    Command line switches are required to run transformer in batch mode from Scheduler.

    From the On-Line Help:

    You can use command-line options to

    ? run Transformer in batch to create or update PowerCubes,
    ? run Transformer in batch and update the model with new categories generated during the category generation process,
    ? change the current date setting so that relative time calculations in batch cube creation are based on a specific date,
    ? use different preference settings or preference files,
    ? open or delete checkpoint files,
    ? supply database signon information, or

    ? change the degree of detail for log file messages.

    The syntax is

    trnsfrmr -<option> <model_file>|<MDL_file>

    Notes

    ? The command-line syntax is not case-sensitive for Transformer running under Windows.
    ? Command-line options that take arguments cannot contain spaces between the switch and the argument. For example:

    trnsfrmr -r 2 july.mdl is not valid, whereas
    trnsfrmr -r2 july.mdl is valid.

    ? You can combine command-line options. For example:

    trnsfrmr -n -i sales.py?
    trnsfrmr -i -t19932 sales.py?

    The ? (question mark) in the extension .py? is replaced by the character that is used in your release of Transformer.

    ? The space character is used to separate multiple command-line options. Therefore, if any of the arguments contain spaces, you must enclose them in double quotes. For example:

    trnsfrmr -n -kfield three=CarlosR/pw462 is not valid, whereas
    trnsfrmr -n -k"field three=CarlosR/pw462" is valid.

    Related Topics

    -d (Set Preference directory!!!)
    -f (Set Preference File)
    -i (Open Saved Model)
    -k (Specify Database Signon)
    -n (Run in Batch Mode)
    -o (Do Not Create PowerCubes)
    -p (Open Checkpoint File)
    -r (Log Level Detail)
    -s (Save Model)
    -t (Set Current Period)
    -u (Get Partition Status)
    -nologo



  • Trigger The Notify Event For Correct Cube Build Date In Upfront

    When a cube is published for the first time in Upfront the publish timestamp is attached to the cube. But when the cube is refreshed the timestamp in Upfront does not change. You can change this by executing this script with the NOTIFY option.

    extra info:
    model name is Great Outdoors Company.mdl
    (published) cube name in PowerPlay Enterprise Server (PPES)

    ***************** Script *********************
    echo 1. disable the cube in PPES
    echo 2. build the cube
    echo 3. enable the cube and trigger the notify event so that the modified cube date in Upfront is current

    "c:\program files\cognos\cer4\bin\ppadmtool.exe" connect <SERVERNAME>:8010 user cognos password cognos disable "Great Outdoors Company"

    "c:\program files\cognos\cer4\bin\trnsfrmr.exe" -n -s "C:\Program Files\Cognos\cer4\samples\PowerPlay\Cubes and Reports\Great Outdoors Company.mdl"

    "c:\program files\cognos\cer4\bin\ppadmtool.exe" connect <SERVERNAME>:8010 user cognos password cognos enable "Great Outdoors Company" NOTIFY CUBE_OBJECT "/Great Outdoors Company" EVENT=UPDATE



  • How To Backup And Restore Upfront Data Store

    -- BackUp --

    1. From the command line, run the command upfpack.exe
        usage: upfdbadm [-q] [[-b | -r <file>] | [-p <oldpassword> <newpassword>]]
            -q : quiet mode
            -b : backup data store
            -r : restore data store
            <file> : name of backup file
            -p : change data store password
            <oldpassword> : previous data store password
            <newpassword> : new data store password

    2. Run the command upfdbadm.exe with the parameter -b
       upfdbadm.exe -b C:\BackUp\UpFrontStore.Bak

    -- Restore --

    1. Run the command upfdbadm.exe with the parameter -r
       upfdbadm.exe -r C:\BackUp\UpFrontStore.Bak
    2. Run the command upfunpack.exe with the follow parameters to delete old namespace references in the Upfront Data Store.
       -ns <NameSpace> -del

    You can also create a batch file for this

    ** Backup.bat **
    D:
    CD\Progra~1\Cognos\cerx\bin\
    Upfpack.exe -un Admin -pw admin1234 -d D:\Backup
    upfdbadm.exe -b D:\Backup\UpFrontStore.Bak

    ** Restore.bat **
    D:
    CD\Progra~1\Cognos\cerx\bin\
    Upfunpack.exe -un admin -pw admin1234 -p D:\Backup\Upfpackage.pkg -ns default -del
    upfdbadm.exe -r D:\Backup\UpFrontStore.Bak



  • Macro for scanning Transformer logfiles

    When you have a huge number of cubes, it takes a lot of time to check all the transformer logfiles. This macro scans the c:\temp directory for files with a log extension. All the found log files are scanned and when a TR, Warning or Error text is found the line is copied to a c:\temp\README.txt file.

    Copy this code and paste it in CognosScript editor. Change the directory path where your transformer log files are located. Save the file and run the macro.

     '****************************************************************************************
    ' Date:
    ' Name: CUBE_BUILD_NOTIFY
    ' Author: Administrator
    '
    ' Description: This macro parses Transformer logfiles for user-defined text strings
    ' and write the error to c:\temp when the strings occur.
    '
    '****************************************************************************************

    Option Explicit

    Dim LogFileNo  As Integer
    Dim FileNo     As Integer
    Dim FileLine   As String

    Dim AppPath  As String
    Dim iniFile  As String
    Dim LogPath  As String

    Dim TransformerLogFile  As String
    Dim ScriptLogFile           As String
    Dim CurrentLogFile        As String
    Dim CRLF                     As String

    ' Location of the logfile to be scanned.
    const REPORTDIRECTORYPATH  = "C:\Temp"

    Declare Sub Log_Info(Msg_In As String)

    ' -----------------------------------------------------------------------------------------
    Sub Main ()

    Dim FileName            As String
    Dim ReportDirectory  As String

    On Error Goto ErrorTrap

    CRLF = Chr$(13) & Chr$(10)
     
      LogPath = "C:\TEMP"
     
      'setup connection to output logfile Cube_Build_Notify_Script.log
      ScriptLogFile = LogPath  & "\README.txt"
      LogFileNo = Freefile()
      Open ScriptLogFile for Output As LogFileNo
     
      Print #LogFileNo, "CUBE_BUILD_NOTIFY Script " & Date() & " " & Time() & CRLF
      Print #LogFileNo, "Transformer Log File: " & ScriptLogFile & CRLF
      
      FileNo = FreeFile()
        
      ReportDirectory = REPORTDIRECTORYPATH & "\*.log"

      'Set directory to scan
      FileName= Dir (ReportDirectory)

    Do While FileName<>"" 
       CurrentLogFile = REPORTDIRECTORYPATH & "\" & FileName
       Open CurrentLogFile For Input As FileNo ' open Transformer log file       
         Print #LogFileNo, "<<< " & CurrentLogFile & " gestart... >>>"    
         Do While Not Eof(FileNo)             
        
            Line Input #FileNo, FileLine       ' read each line in log file
                        
            If InStr(1, FileLine, "Error:", 1) > 0 Then      
               call Log_Info(FileLine)
            End If 
                                          
            If InStr(1, FileLine, "Warning:", 1) > 0 Then      
               call Log_Info(FileLine)
            End If
                           
            If InStr(1, FileLine, "(TR", 1) > 0 Then      
               call Log_Info(FileLine)
            End If  
         Loop 
        
         Print #LogFileNo, "<<< " & CurrentLogFile & " afgerond >>>"
         Close FileNo ' close Transformer log file
           
       FileName=Dir
    Loop
        
         call Log_Info("End CUBE_BUILD_NOTIFY Script ")  
         Exit Sub
            
    errorTrap:
       Call Log_Info("Error " & Str(Err) & ": " & Error$(Err))
       Close #LogFileNo
            
    End Sub 'main

    '--------------------------------------------------------------------------------------------
    Sub Log_Info(Msg_In as String)

      Print #LogFileNo, Date() & "-" & Time() & ": " & Msg_In
     
    End Sub

    '--------------------------------------------------------------------------------------------



  • How to run CognosScript macros?
    CognosScript programs (macros) can be written, run, debugged and tested in the CognosScript Editor which comes default with the installation of Cognos Impromptu or PowerPlay. The CognosScript editor can be started on edmacro32.exe in the \bin\ cognos installation folder to open mac files.

    The Macros are saved to a text format and have a mac extension. When the file is run it is automatically compiled to a binary file, with a mcx extension.
    To run the macros from the command line the runmac32.exe in the \bin\ cognos installation folder is used.

    To run a cognos macro from the command line just type in the following at the command prompt:
    "D:\Program Files\Cognos\cer3\bin\runmac32.exe" D:\myfirstmacro.mac

    It is also possible to pass a parameter to the script (you'll find an example on how to read the parameter in CognosScript on our pages). It can be done by adding the parameter simply at the end of the command: "D:\Program Files\Cognos\cer5\bin\runmac32.exe" D:\myfirstmacro.mac

 

Login

For more content en features!



CogKnowHow Newsletter

Season's Greetings


Receive HTML?

Polls

How many users are working on your Cognos environment?