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

  • IBM Cognos Series 7 Diagnostic
    This diagnostic will retrieve system and product information for IBM Cognos Series 7


    Download Description
    Run this diagnostic to help you troubleshoot issues with IBM Cognos Series 7.

    Certain Advantages
    To retrieve CPP port information
    To check processes
    To compare settings between development and production systems

    Summary of Information Collected from IBM Cognos Series 7 CCP Port Information for Network Status/Statistics information (file collected: netstat.txt)
    Files and Processes Collected for Components

    Summary of Information Collected from IBM Cognos Series 7 Configuration Manager
    List of Files Collected
    CFA-_.txt files based on the following selection criteria
    Files containing today’s date
    All files
    Files containing a selected date which is specified by the user

    CFE-_.txt files based on the following selection criteria
    Files containing today’s date
    All files
    Files containing a selected date which is specified by the user

    The file defined by the environment variable setting SAXmlLogFile


    Prerequisites
    Sun Microsystems Java Runtime Environment (JRE)
    JRE version 1.4.x or higher must be installed
    Sun Microsystems Java (java) must be in the system path


    Installation Instructions

    To Run Diagnostic do one of the following steps:

    For Microsoft Windows:
    From a Microsoft Windows DOS command, run the batch file.
    This is the recommended way, as progress will appear in the command window.
    Run the jar file
    This will run in the background, no progress will appear, only the result once the diagnostic has been completed.

    For UNIX:
    X Windows System Display is required to provide Graphical User Interface (GUI) protocol
    Download the tar file and uncompress all the files to the same directory using the command:
    tar xpf series7ux.tar
    To run the diagnostic do one of the following steps:
    type series7ux.bat
    type java -jar series7ux.jar

  • JVM Memory Utilization

    Wondering how many MB your Cognos JVM (Java Virtual Machine) uses? Type in the following URL in your browser

    http://localhost/cognos8/cgi-bin/cognosisapi.dll?b_action=/diagnostics

    Provide login credentials if required and the result appears.

    <Diagnostics>
      <Dispatcher host="localhost" port="9300" capacity="1.0" />
         <Memory Amount_of_free_memory_in_the_system="16199.064 KB" Total_memory_in_the_JVM="130955.776 KB" />
      <CM host="localhost" port="9300" />
    </Diagnostics>



  • IBM Cognos 8 Framework Manager Diagnostic Tool

    In the Cognos 8.4 distribution some diagnostic tools are default installed in the directory \bin\utilities\diagnostictools\win32. One of them is "C8FrameMgr". Most of these tools were earlier available on the support site of Cognos.

    Just execute the file "execute_ C8FrameMgr.bat" or java -jar C8FrameMgr.jar from the DOS prompt. Or execute the file "execute_IBMCognos8.bat" from windows explorer window.

    Summary of Information Collected

    · Content Store Information
    · Ambiguous Join Info
    · List of Facts
    · Multiple Valid Join Info
    · Recursive Join Info

    Sample output of a GO SALES framework model

    =============================================================================
    *** IBM Cognos 8 Framework Manager Result file generated 19:51:44
    =============================================================================



    =============================================================================
    *** Content Store Information
    =============================================================================

    Database Type: Microsoft SQL Server

    Database Version:
    9.0.3077

    Driver Type: JNetDirect JSQLConnect - JDBC 2.0

    Driver Version: 5.55


    =============================================================================
    *** Ambiguous Join Information
    =============================================================================


    Model File: D:\Data\fm\Security row based\model.xml

    ** VIEW THE LOG FILE FOR A LIST OF ALL RELATIONSHIPS **

    Potential Ambiguous Join #1
    Namespace: Product query subjects
    Query Subject: PRODUCT
    Type: Fact (previously defined as a Dimension)
    Relationship: PRODUCT_COLOR_LOOKUP <--> PRODUCT
    Expression:
    [gosales].[PRODUCT_COLOR_LOOKUP].[PRODUCT_COLOR_CODE] =
    [gosales].[PRODUCT].[PRODUCT_COLOR_CODE]


    Potential Ambiguous Join #2
    Namespace: Product query subjects
    Query Subject: PRODUCT
    Type: Fact (previously defined as a Dimension)
    Relationship: PRODUCT_SIZE_LOOKUP <--> PRODUCT
    Expression:
    [gosales].[PRODUCT_SIZE_LOOKUP].[PRODUCT_SIZE_CODE] =
    [gosales].[PRODUCT].[PRODUCT_SIZE_CODE]


    Potential Ambiguous Join #3
    Namespace: Product query subjects
    Query Subject: PRODUCT
    Type: Fact (previously defined as a Dimension)
    Relationship: PRODUCT_STYLE <--> PRODUCT
    Expression:
    [gosales].[PRODUCT_BRAND].[PRODUCT_BRAND_CODE] =
    [gosales].[PRODUCT].[PRODUCT_BRAND_CODE]


    Potential Ambiguous Join #4
    Namespace: Product query subjects
    Query Subject: PRODUCT
    Type: Fact (previously defined as a Dimension)
    Relationship: PRODUCT_TYPE <--> PRODUCT
    Expression:
    [gosales].[PRODUCT_TYPE].[PRODUCT_TYPE_CODE] =
    [gosales].[PRODUCT].[PRODUCT_TYPE_CODE]


    Potential Ambiguous Join #5
    Namespace: Product query subjects
    Query Subject: PRODUCT_TYPE
    Type: Fact (previously defined as a Dimension)
    Relationship: PRODUCT_LINE <--> PRODUCT_TYPE
    Expression:
    [gosales].[PRODUCT_LINE].[PRODUCT_LINE_CODE] =
    [gosales].[PRODUCT_TYPE].[PRODUCT_LINE_CODE]


    Potential Ambiguous Join #6
    Namespace: gosales
    Query Subject: TIME_DIMENSION
    Type: Dimension (previously defined as a Fact)
    Relationship: INVENTORY_LEVELS <--> TIME_DIMENSION
    Expression:
    [gosales].[INVENTORY_LEVELS].[INVENTORY_YEAR] =
    [gosales].[TIME_DIMENSION].[CURRENT_YEAR] AND
    [gosales].[INVENTORY_LEVELS].[INVENTORY_MONTH] =
    [gosales].[TIME_DIMENSION].[CURRENT_MONTH]


    Potential Ambiguous Join #7
    Namespace: gosales
    Query Subject: TIME_DIMENSION
    Type: Dimension (previously defined as a Fact)
    Relationship: PRODUCT_FORECAST <--> TIME_DIMENSION
    Expression:
    [gosales].[PRODUCT_FORECAST].[SALES_YEAR] =
    [gosales].[TIME_DIMENSION].[CURRENT_YEAR] AND
    [gosales].[PRODUCT_FORECAST].[SALES_MONTH] =
    [gosales].[TIME_DIMENSION].[CURRENT_MONTH]


    Potential Ambiguous Join #8
    Namespace: gosales
    Query Subject: COUNTRY
    Type: Dimension (previously defined as a Fact)
    Relationship: SALES_TARGET <--> COUNTRY
    Expression:
    [gosales].[SALES_TARGET].[COUNTRY_CODE_RETAILER] =
    [gosales].[COUNTRY].[COUNTRY_CODE]


    Potential Ambiguous Join #9
    Namespace: gosales
    Query Subject: TIME_DIMENSION
    Type: Dimension (previously defined as a Fact)
    Relationship: Orders <--> TIME_DIMENSION
    Expression:
    [gosales].[Sales].[Day key (order date)] =
    [gosales].[TIME_DIMENSION].[DAY_KEY]


    Potential Ambiguous Join #10
    Namespace: gosales
    Query Subject: TIME_DIMENSION
    Type: Dimension (previously defined as a Fact)
    Relationship: Returned item <--> TIME_DIMENSION
    Expression:
    [gosales].[Returned items].[Day key (return date)] =
    [gosales].[TIME_DIMENSION].[DAY_KEY]


    Potential Ambiguous Join #11
    Namespace: gosales
    Query Subject: Sales
    Type: Fact (previously defined as a Dimension)
    Relationship: Sales <--> PRODUCT
    Expression:
    [gosales].[Sales].[Product number] =
    [gosales].[PRODUCT].[PRODUCT_NUMBER]


    Potential Ambiguous Join #12
    Namespace: gosales
    Query Subject: Sales
    Type: Fact (previously defined as a Dimension)
    Relationship: Sales <--> BRANCH
    Expression:
    [gosales].[Sales].[Sales branch code] =
    [gosales].[BRANCH].[BRANCH_CODE]


    Potential Ambiguous Join #13
    Namespace: gosales
    Query Subject: Sales
    Type: Fact (previously defined as a Dimension)
    Relationship: Sales <--> ORDER_METHOD
    Expression:
    [gosales].[Sales].[Order method code] =
    [gosales].[ORDER_METHOD].[ORDER_METHOD_CODE]


    Potential Ambiguous Join #14
    Namespace: gosales
    Query Subject: TIME_DIMENSION
    Type: Dimension (previously defined as a Fact)
    Relationship: Sales target <--> TIME_DIMENSION
    Expression:
    [gosales].[Sales target].[Month key] =
    [gosales].[TIME_DIMENSION].[MONTH_KEY]


    Potential Ambiguous Join #15
    Namespace: gosales
    Query Subject: Product
    Type: Fact (previously defined as a Dimension)
    Relationship: PRODUCT_COLOR_LOOKUP <--> Product
    Expression:
    [gosales].[PRODUCT_COLOR_LOOKUP].[PRODUCT_COLOR_CODE] =
    [gosales].[Product].[Product color code]


    Potential Ambiguous Join #16
    Namespace: gosales
    Query Subject: Product
    Type: Fact (previously defined as a Dimension)
    Relationship: PRODUCT_SIZE_LOOKUP <--> Product
    Expression:
    [gosales].[PRODUCT_SIZE_LOOKUP].[PRODUCT_SIZE_CODE] =
    [gosales].[Product].[Product size code]


    Potential Ambiguous Join #17
    Namespace: gosales
    Query Subject: Product
    Type: Fact (previously defined as a Dimension)
    Relationship: PRODUCT_BRAND <--> Product
    Expression:
    [gosales].[PRODUCT_BRAND].[PRODUCT_BRAND_CODE] =
    [gosales].[Product].[Product brand code]


    Potential Ambiguous Join #18
    Namespace: goretailers
    Query Subject: RETAILER
    Type: Fact (previously defined as a Dimension)
    Relationship: RETAILER_TYPE <--> RETAILER
    Expression:
    [goretailers].[RETAILER_TYPE].[RETAILER_TYPE_CODE] =
    [goretailers].[RETAILER].[RETAILER_TYPE_CODE]


    Potential Ambiguous Join #19
    Namespace: goretailers
    Query Subject: RETAILER_SITE
    Type: Fact (previously defined as a Dimension)
    Relationship: RETAILER_SITE <--> ACTIVITY_STATUS_LOOKUP
    Expression:
    [goretailers].[RETAILER_SITE].[RTL_ACTIVITY_STATUS_CODE] =
    [goretailers].[ACTIVITY_STATUS_LOOKUP].[ACTIVITY_STATUS_CODE]


    Potential Ambiguous Join #20
    Namespace: goretailers
    Query Subject: RETAILER_SITE
    Type: Fact (previously defined as a Dimension)
    Relationship: RETAILER_SITE <--> RETAILER
    Expression:
    [goretailers].[RETAILER_SITE].[RETAILER_CODE] =
    [goretailers].[RETAILER].[RETAILER_CODE]


    Potential Ambiguous Join #21
    Namespace: goretailers
    Query Subject: Retailer
    Type: Fact (previously defined as a Dimension)
    Relationship: RETAILER_TYPE <--> Retailer
    Expression:
    [goretailers].[RETAILER_TYPE].[RETAILER_TYPE_CODE] =
    [goretailers].[Retailer].[Retailer type code]


    Potential Ambiguous Join #22
    Namespace: gohr
    Query Subject: EMPLOYEE
    Type: Fact (previously defined as a Dimension)
    Relationship: GENDER_LOOKUP <--> EMPLOYEE
    Expression:
    [gohr].[GENDER_LOOKUP].[GENDER_CODE] =
    [gohr].[EMPLOYEE].[GENDER_CODE]


    Potential Ambiguous Join #23
    Namespace: Database view
    Query Subject: RETAILER_SITE
    Type: Dimension (previously defined as a Fact)
    Relationship: Returned items <--> RETAILER_SITE
    Expression:
    [gosales].[Returned items].[Retailer site code] =
    [goretailers].[RETAILER_SITE].[RETAILER_SITE_CODE]


    Potential Ambiguous Join #24
    Namespace: Database view
    Query Subject: RETAILER_SITE
    Type: Dimension (previously defined as a Fact)
    Relationship: Sales <--> RETAILER_SITE
    Expression:
    [gosales].[Sales].[Retailer site code] =
    [goretailers].[RETAILER_SITE].[RETAILER_SITE_CODE]


    Potential Ambiguous Join #25
    Namespace: Database view
    Query Subject: Sales target
    Type: Dimension (previously defined as a Fact)
    Relationship: Sales target <--> RETAILER
    Expression:
    [gosales].[Sales target].[Retailer code] =
    [goretailers].[RETAILER].[RETAILER_CODE]


    Potential Ambiguous Join #26
    Namespace: Database view
    Query Subject: Sales target
    Type: Dimension (previously defined as a Fact)
    Relationship: Sales target <--> Retailer
    Expression:
    [gosales].[Sales target].[Retailer code] =
    [goretailers].[Retailer].[Retailer code]




    =============================================================================
    *** List of Query Subjects Which Are Facts (1..n) Only
    =============================================================================


    Model File: D:\Data\fm\Security row based\model.xml

    Query subjects that only have the many (n) cardinality:

    CONVERSION_RATE
    CURRENCY_LOOKUP
    EMPLOYEE_HISTORY
    EURO_CONVERSION
    INVENTORY_LEVELS
    ORDER_DETAILS
    Orders
    PRODUCT_FORECAST
    RETAILER_SITE_MB
    Returned item
    Returned items
    RETURNED_ITEM
    SALES_TARGET


    =============================================================================
    *** Multiple Valid Join Information
    =============================================================================


    Model File: D:\Data\fm\Security row based\model.xml

    ** VIEW THE LOG FILE FOR A LIST OF ALL RELATIONSHIPS **

    Potential Multiple Valid Join #1
    Namespace: gosales
    Relationship: INVENTORY_LEVELS <--> TIME_DIMENSION
    Expression:
    [gosales].[INVENTORY_LEVELS].[INVENTORY_YEAR] =
    [gosales].[TIME_DIMENSION].[CURRENT_YEAR] AND
    [gosales].[INVENTORY_LEVELS].[INVENTORY_MONTH] =
    [gosales].[TIME_DIMENSION].[CURRENT_MONTH]

    Potential Multiple Valid Join #2
    Namespace: gosales
    Relationship: PRODUCT_FORECAST <--> TIME_DIMENSION
    Expression:
    [gosales].[PRODUCT_FORECAST].[SALES_YEAR] =
    [gosales].[TIME_DIMENSION].[CURRENT_YEAR] AND
    [gosales].[PRODUCT_FORECAST].[SALES_MONTH] =
    [gosales].[TIME_DIMENSION].[CURRENT_MONTH]

    Potential Multiple Valid Join #3
    Namespace: Database view
    Relationship: Sales Staff <--> Sales target
    Expression:
    [gohr].[Sales Staff].[Sales staff code] =
    [gosales].[Sales target].[Sales staff code] and (
    [gosales].[Sales target].[Day key (sales target)] between
    [gohr].[Sales Staff].[Day key (record start date)] and
    [gohr].[Sales Staff].[Day key (period record end date)] )

    Potential Multiple Valid Join #4
    Namespace: Database view
    Relationship: Sales Staff <--> Orders
    Expression:
    [gohr].[Sales Staff].[Sales staff code] =
    [gosales].[Sales].[Sales staff code] and (
    [gosales].[Sales].[Day key (order date)] between
    [gohr].[Sales Staff].[Day key (record start date)] and
    [gohr].[Sales Staff].[Day key (period record end date)] )

    Potential Multiple Valid Join #5
    Namespace: Database view
    Relationship: Returned items <--> Sales Staff
    Expression:
    [gosales].[Returned items].[Sales staff code] =
    [gohr].[Sales Staff].[Sales staff code] and (
    [gosales].[Returned items].[Day key (return date)] between
    [gohr].[Sales Staff].[Day key (record start date)] and
    [gohr].[Sales Staff].[Day key (period record end date)] )

    Potential Multiple Valid Join #6
    Namespace: Database view
    Relationship: Sales target <--> Retailer site
    Expression:
    [gosales].[Sales target].[Country code retailer] =
    [goretailers].[Retailer site].[Retailer country code] AND
    [gosales].[Sales target].[Retailer code] =
    [goretailers].[Retailer site].[Retailer code]



    =============================================================================
    *** Recursive Join Information
    =============================================================================

    Model File: D:\Data\fm\Security row based\model.xml

    No potential Recursive Joins found

     

    www.cogknowhow.com



  • IBM Cognos 8 Diagnostic

    In the Cognos 8.4 distribution some diagnostic tools are default installed in the directory <cognosinstalldir>\bin\utilities\diagnostictools\win32. One of them is "IBM Cognos 8 Diagnostic". These tools were earlier available on the support site of Cognos.

    Cognos 8 Diagnostic will retrieve system and product information about IBM Cognos 8 environment.

    Just execute the file "execute_IBMCognos8.bat" or java -jar IBMCognos8.jar from the DOS prompt. Or execute the file "execute_IBMCognos8.bat" from windows explorer window.

    A lot of useful information is collected like: logs, processes, email settings, print settings, ldap settings, Cognos configuration settings extracted from the cogstartup.xml etc.


    www.cogknowhow.com

     



  • IBM C8_ContentStoreInfo
    In the Cognos 8.4 distribution some diagnostic tools are default installed in the directory <cognosinstalldir>\bin\utilities\diagnostictools\win32. One of them is "IBM C8_ContentStoreInfo". These tools were earlier available on the support site of Cognos.

    IBM C8_ContentStoreInfo retrieves Content Store Database Information.

    Use this diagnostic is executed when you have problems with creating tables in IBM Cognos 8.
    All Diagnostic Tools results will be found at <system temp>/ IBMCognos_Diagnostic/<name of diagnostic>

    The output generated are displayed in 2 forms:
    A Text file called DatabaseType_Config_30Jul2008_0914.txt and an XML file called C8_ContentStoreXML_30Jul2008_0919.xml

    Output looks like this:

    C8_ContentStoreInfo diagnostic RESULTS                        7Jun2009 06:35
    ======================================

    Database:  ContentStore83

    MSSQL Database Collation Sequence:  Latin1_General_CI_AS


    Connection established : true
    Connection URL           : jdbc:JSQLConnect://localhost:1433;database=ContentStore83
    Driver Name                : JNetDirect JSQLConnect - JDBC 2.0
    Driver Version              : 5.55
    Database Name           : Microsoft SQL Server
    Database Version         : 9.0.3077



  • How To Read Cogserver.log Easier With IPF Log Viewer

    The cogserver.log file is a good source of information when troubleshooting. But default the cogserver.log file is a 10 MB file (set in Cognos Configuration Manager) in xml format and hard to read.

    127.0.0.1:9300 3048 2009-06-04 09:16:53.218 +1     stopper-logService LOGSV 2015 1 server.Audit.IPF StopService LogService  Success  <parameters><item name="Port"><![CDATA[9362]]></item><item name="Mode"><![CDATA[TCP]]></item><item name="Secure"><![CDATA[FALSE]]></item></parameters>
    127.0.0.1:9300 1880 2009-06-05 10:07:53.187 +1     main LOGSV 2015 1 server.Audit.IPF StartService LogService  FAILED Log Server Database error <parameters><item name="DB URL"><![CDATA[jdbc:JSQLConnect://localhost:1433/Audit]]></item><item name="DB Error"><![CDATA[Failed Logon:com.jnetdirect.jsql.JSQLException: TCP/IP connection failed to host:localhost java.net.ConnectException: Connection refused: connect url:jdbc:JSQLConnect://localhost:1433/Audit]]></item></parameters>
    127.0.0.1:9300 1880 2009-06-05 10:07:53.234 +1     main LOGSV 2015 1 server.Audit.IPF StartService LogService  Success  <parameters><item name="Port"><![CDATA[9362]]></item><item name="Mode"><![CDATA[TCP]]></item><item name="Secure"><![CDATA[FALSE]]></item></parameters> 

    Since Cognos 8.1 there is a handy tool called LogviewV2.exe and can be found in the c8\bin directory. Start LogviewV2.exe and load the cogserver.log file. Now all the messages and errors are formatted, can be read much better.

     IPF Log Viewer

    If you use the summarize button in the toolbar you get a summary of all the errors in the cogserver.log file. Use this file to solve issues which are occurring frequently

    IPF Log Viewer Error Summary



  • Add Everyone To Cognos Role SystemAdministrator SQL script

    In Cognos 8.1 and Reportnet it was possible to delete the group Everyone from the Systemadministrators role in the Cognos namespace. In Cognos 8.2 and higher, it is not possible to delete the group Everyone, before you add another user, group or role to the role Systemadministrators. If you are somehow not able to get Systemadministrator permissions in the content store use the following script:

     insert into CMREFORD1 (PROPID, CMID, ORD, REFCMID)
     select 27, (select cmid from cmobjprops1 where objid='::System Administrators'),
       coalesce((select max(ord) from CMREFORD1 where propid=27 and cmid=(select cmid from cmobjprops1 where objid='::System Administrators')), -1)+1,
       CMID
      from CMOBJPROPS1 where OBJID='::Everyone'

    This script is called AddSysAdminMember.sql and can be found for SQL, Oracle, DB2, Sybase and Derby in the directory C:\Program Files\COGNOS\c8\configuration\schemas\content\

    Run this script in MS SQL Query Analyzer for your Content Store database and you can log in as SystemAdministrator to fix the security.



  • Content Store Size Profiling SQL Script

    With Cognos 8.4 there is a script,CSsize_profiling_mssqlserver2005.sql, which shows you the objects in your Content store database.  In the directory C:\Program Files\COGNOS\c8\configuration\schemas\content\sqlserver you can find it. This script exist also for oracle, db2 and derby. Execute the script for MS SQL, in SOL query Analyzer for your Content Store and you will get information like below.

    Total number of objects
    -----------------------
    1176

    class name                                         number of objects
    -------------------------------------------------- -----------------
    _deletedObject                                 13
    _deletedObjectFolder                           1
    account                                            12
    adminFolder                                        1
    agentDefinition                                    6
    agentService                                       1
    agentTaskDefinition                            10
    archiveLocation                                    2
    batchReportService                              1
    capability                                            1
    configuration                                       1
    content                                              1
    contentManagerService                         1
    contentTask                                        1
    credential                                            1
    dataIntegrationService                          1
    dataSource                                       130
    dataSourceConnection                       131
    dataSourceSignon                              11
    deliveryService                                    1
    deploymentDetail                              13
    directory                                           1
    dispatcher                                         1
    document                                         2
    documentContent                            10
    documentVersion                               2
    eventManagementService                   1
    exportDeployment                             8
    folder                                             33
    group                                              2
    history                                            41
    historyDetail                                  125
    historyDetailReportService                 11
    historyDetailRequestArguments          41
    importDeployment                              5
    installedComponent                           21
    jobDefinition                                      1
    jobService                                         1
    jobStepDefinition                               3
    logService                                         1
    memo                                               4
    metadataService                                 1
    metricsFileImportTask                          6
    metricsMaintenanceTask                     21
    metricsManagerService                         1
    model                                              17
    modelView                                        17
    monitorService                                    1
    mruFolder                                          12
    namespace                                          2
    namespaceFolder                                  1
    output                                               16
    package                                             12
    packageConfiguration                             9
    pageDefinition                                      7
    pagelet                                            16
    pageletFolder                                      6
    periodical                                            1
    planningApplication                               1
    portal                                                 1
    portalPackage                                      2
    portalSkin                                           6
    portalSkinFolder                                   1
    portlet                                              30
    portletFolder                                      3
    portletInstance                                 16
    portletProducer                                  6
    presentationService                            1
    query                                                5
    report                                             87
    reportDataService                              1
    reportService                                    1
    reportTemplate                               57
    reportVersion                                   4
    reportView                                       3
    role                                                41
    root                                               1
    runTimeState                                  16
    schedule                                           2
    securedFeature                                28
    securedFunction                               22
    shortcut                                          17
    subscriptionFolder                             12
    systemMetricThresholds                      4
    systemService                                    1
    transientStateFolder                            1
    uiProfile                                             2
    uiProfileFolder                                    2
    webServiceTask                                 2

    class name                                         number of secured objects
    -------------------------------------------------- -------------------------
    _deletedObjectFolder                        1
    account                                         12
    adminFolder                                     1
    capability                                         1
    configuration                                    1
    content                                          1
    directory                                         1
    documentVersion                             1
    folder                                             3
    group                                             2
    modelView                                      1
    namespace                                      2
    package                                         11
    pageDefinition                                  7
    periodical                                         1
    portal                                              1
    role                                               25
    root                                                1
    securedFeature                               22
    securedFunction                              22
    transientStateFolder                           1
    uiProfile                                            2
    uiProfileFolder                                    1

    Total number of outputs Total size of outputs
    ----------------------- ---------------------
    26                      709396

    Outputs under 10KB
    ------------------
    10

    Outputs 10KB - 100KB
    --------------------
    14

    Outputs 100KB - 1MB
    -------------------
    2

    Outputs 1MB - 10MB
    ------------------
    0

    Outputs 10MB-100MB
    ------------------
    0

    Outputs 100MB-1GB
    -----------------
    0

    Outputs > 1GB
    -------------
    0

    class name                                         Total number of specifications Total size of specifications
    -------------------------------------------------- ------------------------------ ----------------------------
    query                                              5                              11968
    report                                             87                             8950792
    reportTemplate                                57                             8428154
    reportVersion                                    4                              142124

    Specifications < 10KB
    ---------------------
    12

    Specifications 10KB - 100KB
    ---------------------------
    82

    Specifications 100KB - 1MB
    --------------------------
    59

    Specifications > 1MB
    --------------------
    0

    class name                                         Total number of specifications Total size of specifications
    -------------------------------------------------- ------------------------------ ----------------------------

    class name                                         Total number of specifications Total size of specifications
    -------------------------------------------------- ------------------------------ ----------------------------

    class name                                         Total number of specifications Total size of specifications
    -------------------------------------------------- ------------------------------ ----------------------------

    class name                                         Total number of specifications Total size of specifications
    -------------------------------------------------- ------------------------------ ----------------------------

    class name                                         Total number of specifications Total size of specifications
    -------------------------------------------------- ------------------------------ ----------------------------

    class name                                         Total number of specifications Total size of specifications
    -------------------------------------------------- ------------------------------ ----------------------------

    class name                                         Total number of specifications Total size of specifications
    -------------------------------------------------- ------------------------------ ----------------------------

    class name                                         Total number of specifications Total size of specifications
    -------------------------------------------------- ------------------------------ ----------------------------

    class name                                         Total number of specifications Total size of specifications
    -------------------------------------------------- ------------------------------ ----------------------------

    Total number of models
    ----------------------
    17

    Models < 10KB
    -------------
    5

    Models 10KB - 100KB
    -------------------
    4

    Models 100KB - 1MB
    ------------------
    8

    Models > 1MB
    ------------
    0

    object class                                       number of children   number of objects
    -------------------------------------------------- -------------------- -----------------
    dataSource                                      1                    129
    dataSource                                      2                    1
    dataSourceConnection                      1                    11
    folder                                             1                    3
    folder                                             2                    4
    folder                                             3                    5
    folder                                             5                    1
    folder                                             7                    1
    folder                                             9                    3
    folder                                             10                   3
    folder                                             17                   3
    reportVersion                                   1                    1
    reportVersion                                   2                    1
    reportVersion                                   4                    1
    reportVersion                                   9                    1

    schedule type number of schedules
    ------------- -------------------
    4             2

    object class                                       number of children   number of objects
    -------------------------------------------------- -------------------- -----------------
    dataSource                                     1                    129
    dataSource                                     2                    1
    dataSourceConnection                      1                    11
    folder                                             1                    3
    folder                                             2                    4
    folder                                             3                    5
    folder                                             5                    1
    folder                                             7                    1
    folder                                             9                    3
    folder                                             10                   3
    folder                                             17                   3
    jobDefinition                                     3                    1
    query                                              1                    1
    report                                             1                    2
    reportVersion                                   1                    1
    reportVersion                                   2                    1
    reportVersion                                   4                    1
    reportVersion                                   9                    1
    reportView                                      1                    1

    Number of empty policies
    ------------------------
    0

    Policies 1-127 bytes
    --------------------
    20

    Policies 128-255 bytes
    ----------------------
    61

    Policies 256-511 bytes
    ----------------------
    36

    Policies 512-1023 bytes
    -----------------------
    4

    Policies 1K-2K
    --------------
    0

    Policies 2K-4K
    --------------
    0

    Policies 4K-6K
    --------------
    0

    Policies 6K-8K
    --------------
    0

    Policies > 8K
    -------------
    0

     

    www.cogknowhow.com



  • AM_NamespaceReport utillity
    Run the AM_NamespaceReport command line utility to create an XML report that lists all users or user classes in a namespace.

    You can use the AM_NamespaceReport command line utility with any version of a namespace. Any user with a basic signon can log on.    However, only users and user classes for which you have show privileges appear in the report.
    If the report is the users type with the filter of the all type, the following information is returned: name, first name, last name, description, email, phone number, basic signons, and OS signons. For the namespace version 17.0, external user DN is also returned.

    If the report is userclasses type with the filter of the all type, the following information is returned: user class name, names of children user classes, names of member users, and access permissions.
    The XML schema for both types of report output is located in the Cognos_installation
    /cer5/accman/AM_NamespaceReport_users|AM_NamespaceReport_userclasses.xsd directory.

    Parameters

    Parameter Description
    -h Specifies the computer name of the directory server.default: localhost
    -p Specifies the port number of the directory server.default: 389
    -r Specifies the base DN of the directory server.default: o=cognos, c=ca
    -s Specifies that SSL is enabled.This parameter is optional.
    -C Specifies the location of the cert7.db file.This parameter is required only if SSL is enabled.
    -n Specifies the name of the namespace for reporting. default: default namespace
    -D Specifies the basic signon to use for namespace authentication.This parameter is mandatory.
    -w Specifies the basic signon password.This parameter is mandatory.
    -t Specifies the type of report. The report types users and userclasses are supported.default: users
    -f Specifies a filter type for a report.For the users report type, the following filter types are supported:  allReturns all user information; this is the default filter.  userclassesReturns only information about the users' user class membership.  brokenlinks Returns only the names of users whose DNs are broken. This filter is used only with the namespace version 17.0.  lockedout Returns only the names of users whose accounts are locked.  disabledReturns only the names of users whose accounts are disabled.For the userclasses report type, the following filter types are supported:  all Returns all user class information; this is the default filter.  usersReturns only the names of the member users.   userclasses Returns only information about the children user classes.
    -o Indicates the file to which output is written.This parameter is mandatory.
    Example

    To report all users in a namespace, type the following:

    D:\Cognos\cer4\bin>AM_NamespaceReport -n default -D Administrator -w "" -t users -f all -o all_users.xml

    Here is a sample output of the users report type:

    <?xml version="1.0" encoding="UTF-8"?>
    <NamespaceReport xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="D:\Cognos\cer4\accman\AM_NamespaceReport.xsd" host="localhost" port="389" baseDN="o=Cognos,c=ca" ns="Default" user="Administrator" type="users" filter="all">

    <User name="Sam Carter" first_name="Sam" last_name="Carter" email="sam.carter@cognos.com" phone="(123)456-7890" externalUserDN="uid=scarter,ou=people,o=cognos,c=ca">
      <BasicSignon>scarter</BasicSignon>
      <OSSignon>domain/scarter</OSSignon>
      <Description>Employee id: 12345</Description>
     </User>
     <User name="Ted Morris" first_name="Ted" last_name="Morris" email="ted.morris@cognos.com" phone="(123)456-7899" externalUserDN="uid=tmorris,ou=people,o=cognos,c=ca">

    <BasicSignon>tmorris</BasicSignon>
      <OSSignon>domain/tmorris</OSSignon>
      <Description>Employee id: 56789</Description>
     </User>

    </NamespaceReport>

 

Login

For more content en features!



CogKnowHow Newsletter

Season's Greetings


Receive HTML?

Polls

How many users are working on your Cognos environment?