Documente Academic
Documente Profesional
Documente Cultură
C O G N O S P L A N N I N G
DATABASE ADMINISTRATOR (DBA) GUIDE
Cognos Planning Database Administrator (DBA) Guide Cognos Planning Database Administrator (DBA) Guide
TM
Product Information
This document applies to Cognos Planning v 7.3 and may also apply to subsequent releases. To check for newer versions of this document, visit the Cognos support Web site (http://support.cognos.com).
Copyright
Copyright (C) 2005 Cognos Incorporated. Portions of Cognos(R) software products are protected by one or more of the following U.S. Patents: 6,609,123 B1; 6,611,838 B1; 6,662,188 B1; 6,728,697 B2; 6,741,982 B2; 6,763,520 B1; 6,768,995 B2; 6,782,378 B2; 6,847,973 B2; 6,907,428 B2; 6,853,375 B2. While every attempt has been made to ensure that the information in this document is accurate and complete, some typographical errors or technical inaccuracies may exist. Cognos does not accept responsibility for any kind of loss resulting from the use of information contained in this document. This document shows the publication date. The information contained in this document is subject to change without notice. Any improvements or changes to either the product or the document will be documented in subsequent editions. U.S. Government Restricted Rights. The software and accompanying materials are provided with Restricted Rights. Use, duplication, or disclosure by the Government is subject to the restrictions in subparagraph (C)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013, or subparagraphs (C) (1) and (2) of the Commercial Computer Software - Restricted Rights at 48CFR52.227-19, as applicable. The Contractor is Cognos Corporation, 15 Wayside Road, Burlington, MA 01803. This software/documentation contains proprietary information of Cognos Incorporated. All rights are reserved. Reverse engineering of this software is prohibited. No part of this software/documentation may be copied, photocopied, reproduced, stored in a retrieval system, transmitted in any form or by any means, or translated into another language without the prior written consent of Cognos Incorporated. Cognos and the Cognos logo are trademarks of Cognos Incorporated in the United States and/or other countries. All other names are trademarks or registered trademarks of their respective companies. Information about Cognos Products and Accessibility can be found at www.cognos.com
Table of Contents
Introduction 5 Chapter 1: The Contributor Datastore 7 Contributor Datastore Objects 8 Static and Dynamic Datastore Objects 8 The Planning Administration Domain Datastore and the Common Datastore 9 The Application Datastore 10 Publish Containers 10 Sizing Tablespaces 10 Tablespace Management 11 Chapter 2: Working with Contributor Applications 13 Creating a Contributor Application 13 Assigning User Access to Data 14 Importing Data into the Contributor Application 15 Go to Production 16 Maintaining the Contributor Application 16 Storing User Data 17 Getting Data Out of the Plan 17 Making Changes to the Model 17 Types of Jobs 17 Backup and Recovery 19 Chapter 3: Datastore Security 21 Generating Scripts 21 Create a Contributor Application 22 Add, Edit, and Delete D-List or D-Cube 22 No Change in Model, but Change in Dimension for Publish for View Publish Layout 22 Changing the DDL Script 23 Chapter 4: Publish Datastores 25 Publishing to a Different Datastore 25 The Table-Only Publish Layout 26 Items Tables for the Table-only Publish Layout 27 Hierarchy Tables for the Table-only Publish Layout 28 Export Tables For the Table-only Publish Layout 30 Annotations Tables for the Table-only Publish Layout 31 Metadata Tables 31 Common Tables 33 Job Tables 33 The objectlock Table 34 The View Publish Layout 34 Items Tables for the View Publish Layout 34 Hierarchy Tables for the View Publish Layout 35 Export Tables for the View Publish Layout 35 Annotation Tables for the View Publish Layout 35 Views 36 Chapter 5: Oracle Datastores 39 Oracle Client Tools 39 Securing the Oracle Datastore 40 Create the COGNOSEP User 40 Database Administrator (DBA) Guide 3
Create the LOCKDOWN User 40 Administering the Secured Datastore 42 Sizing Oracle Tablespaces 42 Locally Managed Tablespaces With Uniform Extent Sizing 43 Fine-tune Your Datastore for Better Performance 43 Rename an Application 44 Index 45
4 Cognos Planning
Introduction
This document provides an overview of the Cognos Planning - Contributor 7.3 datastore structure specifically for the Oracle DBA and provides tips to ensure a successful implementation on Oracle relational database. It also describes the interaction of Contributor with its datastores, and guidelines for the management of an RDBMS server for Cognos Planning applications. It is supplementary to the user documentation supplied with Cognos Planning 7.3, and training courses. Cognos Planning provides the ability to plan, budget, and forecast in a collaborative, secure manner. There are two major components, both of which you should be familiar with before using this document.
Related Information
The following documents contain related information, and may be referred to in this document. Document Analyst and Manager User Guide Contributor Administration Guide Cognos Planning New Features Guide Cognos Planning Best Practice Guide Description Using Analyst to create planning models Creating and administering Contributor applications Describing features that are new in Cognos Planning 7.3. Applying best practice guidelines, troubleshooting tips, focusing on how you can use the new features to get the best out of Cognos Planning 7.3.
Introduction
Description Using Contributor Get Data to load data into Contributor Configuring security information
Our documentation includes user guides, tutorial guides, reference books, and other materials to meet the needs of our varied audience.
Online Help
Some information is available in online help. Online help is available from the Help button in a Web browser, or the Help menu and Help button in Windows products.
6 Cognos Planning
Naming Conventions
The naming convention for datastore objects is SQL1992 compliant. When the enterprise database is not fully SQL 1992 compliant, datastore object names conform to the limitations of the target datastore. That is, the Contributor Administration Console restricts the length of the application or datastore container name during the create application process. From that point on, all datastore object names are fully qualified in DDL script or DML (Data Manipulation Language) using the datastore container name. Static object names are the same across all applications and do not change during the life cycle of the Contributor application. Dynamic objects, primarily import tables, publish tables, and views, are named after objects within the Analyst model. Object names correspond to Contributor model object names with a subsystem prefix, subject to database-specific limitations. All dynamic object names are forced to conform to naming conventions as per the Contributor application container. Other datastore object names, for example, indexes, are automatically generated and are not intended to be meaningful.
Metadata
Contributor application datastores contain the metadata subsystem. The content of the metadata tables is critical to the functioning of the Contributor application. The metadata provides a mapping from internal Contributor model identifiers to the external datastore objects. DDL scripts may be amended to conform to local storage conventions and may be tailored to suit your hardware. However, data integrity must be maintained. It is essential that you do not amend datastore object names within the DDL script and allow the information contained within the metadata tables to become out of synchronization with the underlying datastore objects.
PAD
Common
Application A
Application B
Application C
Application D
application containers
Datastore Object Static / dynamic Planning Administration Domain and common tables static
Application datastore no
Publish datastore no
no yes
yes yes
no yes
8 Cognos Planning
Datastore Object Static / dynamic application configuration tables application metadata tables static
Publish datastore no
static
no no no no
yes no no yes
extension static component tables import tables publish tables and views dynamic dynamic
Chapter 1: The Contributor Datastore The common datatore contains first class data objects (links and macros) which may contain sizeable XML binary blob data that is both written and read at reasonable frequency. Backup and restore of both the Planning Administration Domain and common datastores should be performed at the same time.
Publish Containers
When Cognos Planning data has been submitted, it can be extracted from the application datastores XML LOBs into a star schema formatted set of relational views and tables. Contributor refers to this star schema-based collection of views and tables as the Publish container. When published, you can move the planning data into a Data warehouse or other applications for reporting. Contributor provides two options for publishing plan data: View Publish, which is the traditional format for published plan data in Contributor, or Table-only Publish, a star schema that is optimized for reporting purposes. Contributor Publish containers are a snapshot of the plan, and contain data which meets the selection criteria of a Contributor Administrator. The Publish datastore is populated as required for your Cognos Planning environment and is not transactional in nature. That is, it is not an online transaction processing (OLTP) database. It is not necessary to perform transaction level logging or backup against Contributor Publish datastores.
Sizing Tablespaces
You can estimate an initial sizing for a Contributor application using the total number of cells per slice for the application and assuming an average storage utilization of 16 bytes per cell. Actual storage utilization varies based on data types, data density, use of annotations, and datastore management practices. For example, you can estimate rough storage requirements for an application with 34,849 cells per e.List item slice and an e.List with 27 e.List items as follows: 34,849 * 27 * 16 = 15,054,768 bytes Divide by 1,024 to get KB 15054768 / 1024 = 14,702 KB Divide by 1,024 to get MB 14702 / 1024 = 14.36 MB We recommend that you allow for approximately 2.8 times more storage than the results of this calculation. This extra storage will account for application growth through contributions as well as the following application behaviors: During administrative functions (Go to Production, reconcile, import, and publish), the application temporarily increases the size of the datastore as processing is completed. Space for logs and other associated RDBMS functions. For information about Oracle tablespaces, see "Sizing Oracle Tablespaces" (p. 42).
10 Cognos Planning
Tablespace Management
When Cognos Planning applications are created using Oracle or DB2 UDB, Contributor uses the default Data, Indexes, BLOBs, and Temporary tablespaces. Tip: You can view the tablespaces used by an existing application in the Contributor Administration Console: in Development, click Datastore Options, Datastore Maintenance, and then click the Tablespaces tab. You can customize these tablespaces when creating the application. Both the Oracle and IDB2 UDB datastores require the allocation and ongoing maintenance of tablespace storage requirements. The storage requirements for a Contributor application grow as contributions are saved by users, administrative jobs are run, and as iterative Go to Production tasks are completed. The use of user and audit annotations also impacts storage requirements based on the size and number of annotations. Monitor storage utilization for tablespaces used by Contributor datastores on a regular basis to ensure that Contributor does not grow beyond its allocated storage. As a general rule, new applications should be maintained below 40% tablespace utilization. For mature applications, the Contributor tablespace should be increased by 25% whenever utilization reaches 70% of available space.
12 Cognos Planning
Configure the Contributor application. For more information, see the Contributor
Administration Guide. Assign user access to data.
Import data. Make the Contributor application live to users using the Go to Production process. Publish data (p. 25).
Lockdown Environment
A lockdown environment is one where only a DBA can execute DDL commands.
Chapter 2: Working with Contributor Applications The Analyst model, named package.xml, is loaded into the applicationstate table after you run the Script.sql. When the DDL script has run, the Contributor administrator can link to the Contributor application and is then prompted to upload the compressed model, persisted as XML to local disk, into the applicationstate table. If you are using Oracle, you can create a LOCKDOWN user (p. 40).
Open Environment
In an open environment, the Contributor Administration Console interacts directly with the RDBMS through DDL from the administration server and so application creation does not require DBA intervention. The DDL script is executed at the end of the create application process and the package loaded into the applicationstate table. The administration server requires knowledge of the Analyst model to be able to write the development items.
development_items Table
The first time the Analyst model is written to the applicationstate table and every time the model is changed, rows are deleted and inserted into the development_items table. The number of rows is determined by the size of the model and the number of items within each dimension in the model. Note that if a dimension is used more than once in a model, there will only be one entry for it in the development_items table. Dimensions are lists of values and the development_items table contains all the valid values in each list along with the internal reference, a GUID. This information can be used to produce valid metadata to be imported into the Contributor application later. Rows in the development_items table always contain valid values for the most recent version of the development model.
User Data
At this point, there is no user data, and so the nodestate table is empty. Users cannot start to submit data into the application until the application has been configured and the Go to Production process run.
14 Cognos Planning
Chapter 2: Working with Contributor Applications Data now exists in the importqueue table. The next step is to process it through the Go to Production process.
Go to Production
The Go to Production process makes a Contributor application available to users. Go to Production can be executed from the Contributor Administration Console as a wizard, on demand through an administrator defined Contributor macro, or by using a scheduling tool that runs a Contributor macro from a batch file using the Contributor command line interface. The Go to Production process triggers a reconcile job that establishes the list of e.List items that will be processed by the Contributor job architecture. The reconcile job processes user data and makes it available for use with the latest version of the Contributor model stored in the applicationstate table. Immediately after application creation, all e.List items require processing. Contributor supports online changes to the Contributor model stored in applicationstate. These changes do not affect users accessing the system because user data is associated with a version of the Contributor model. The currently active version of the Contributor model is not changed. Instead, a copy of it, named the development model, is changed. The updated version only becomes the current version after the Go to Production process is run. The following steps occur during the Go to Production process: Pre Production Blank rows are inserted into the nodestate table for any new e.List items that are added to the updated package.xml. When an application is initially created, a blank row is inserted for all e.List items. Go to Production The processing of the updated and old model package.xml in the applicationstate table. This is a critical part of the process. The Web client computer cannot connect to the application datastore to ensure data integrity. The Contributor application is offline but only for a short period of time, typically less than one minute. Post Production Establishes which rows in nodestate require processing, that is, which users have data that require updating. A reconcile job is created to carry out this task. In the application datastore, no DDL is generated, only DML is run. Any existing user data is extracted from the nodestate table and reformatted by the job cluster to be compatible with the incoming (optionally updated) Contributor model stored in applicationstate. Any actuals data in the importqueue is incorporated into the user data at this stage and the compressed data block is stored as a LOB in XML format in the nodestate table. The Contributor e.List item data is aggregated to write review e.List item data during this process. The end result is a single row in nodestate with two LOB columns: one for data and one for annotations for each e.List item in the system. The format of this matches the Contributor model definition held in the applicationstate table. At this stage, users can start connecting to the Contributor application using the Web client.
16 Cognos Planning
Types of Jobs
A job is triggered by an administration task such as publish. Jobs run on job servers, which are in turn grouped by job server clusters, and are monitored by the Contributor Administration Console. Jobs are scalable; adding additional job servers speeds up processing of jobs. You can have the following types of jobs. Job type Annotations tidy Description Deletes user annotations and audit annotations.
Description Customized copies of the master Contributor model definition that have been cut-down to include only the specific elements required for a particular e.List item. Removes any cut-down models that are no longer required. Removes obsolete items from the export queue. Removes model import blocks from the import queue that are no longer required. Transfers data between applications. Cleans up unwanted languages from the data store after the Go to Production process is run. This job is created and runs after Go to Production is run. Processes import data ready for reconciliation. Publishes the data to a view format. Ensures that the structure of the e.List item data is up to date. This job is created and runs after Go to Production is run. Publishes the data to a table-only format. Checks to see if the owner or editor of an e.List item has the rights to access the e.List item. The job checks the rights of users, in Access Manager or in the Contributor model as appropriate, and updates the information in the Web browser. This job is created only if a change is made to the Contributor model, and runs after Go to Production is run.
Cut-down tidy Export queue tidy Import queue tidy Inter-app links Language tidy
Tidy Up Jobs
Some Contributor jobs, such as prepare import, have a tidy up mode. At key points they generate jobs to be executed by the job cluster, which help maintain the datastore by removing redundant data. The Contributor datastore grows for the following reasons: While the repair and tidy-up jobs remove redundant data, the storage requirements grow as users contribute data into the application. Additionally, as actuals are imported, or as the model is expanded (and consequently new dynamic datastore objects are created), the datastore grows. The Contributor datastores should still be subject to the normal enterprise monitoring. In particular, storage should be monitored on a regular basis. We recommend that you have a lockdown environment to control expansion and growth.
18 Cognos Planning
20 Cognos Planning
Privileges
The privileges required for the Contributor accounts are specific to each datastore provider and determined by the setting of the Generate Scripts option. If you decide not to use the generate scripts option, and allow the Contributor account to execute DDL interactively, then the Contributor account requires create / remove datastore permissions. The account also requires create / remove permissions on all Contributor datastore objects (as well as the standard SELECT, INSERT, UPDATE and DELETE). If you prefer to execute the DDL scripts using your own security credentials, you can restrict the Contributor administrator to a standard SELECT, INSERT, UPDATE, DELETE privilege on the Contributor datastore objects. In all circumstances, it is necessary for the Contributor account to have sufficient privileges to carry out a non-logged delete of all data in a table, such as a TRUNCATE table. The Contributor installation contains sample scripts to create the Contributor account for each supported datastore provider under both an open and Lockdown environment. Contributor can also operate under a regime of trusted security. You can also insert permission granting statements into DDL scripts.
Generating Scripts
The Generate Scripts option enables you to separate actions that should be performed only by a DBA. These actions include creating or dropping datastore objects from standard reading, writing, inserting, and deleting of data operations (DML), which take place on a day-to-day basis. When Generate Scripts is used, DDL scripts are generated when the datastore needs to be restructured, for example if tables need to be added or deleted when publishing, and when synchronizing. The DDL script contains a series of instructions to create or drop datastore objects, and can be edited. A DDL script can also be generated when creating an application.
Chapter 3: Datastore Security Set the Generate Scripts option on by setting the Gen_Scripts option to true in the adminoptions table, or set Generate Scripts to Yes in the Contributor Administration Console (Development, Application Maintenance, Admin Options). Do not drop Contributor datastore objects using your own enterprise database tools unless requested to do so by Customer Support. Use caution to avoid getting the Cognos Planning metadata out of synchronization with the underlying datastore objects. Look out for errors during the execution of the DDL script. Do not assume that the DDL script execution has worked. Consider synchronizing actions with DBA turnaround times for running scripts. Response may vary. Executed under SQL*PLUS, the script creates a log file, and aborts on error. Always check the output. Be careful when creating scripts not to overwrite or confuse two files with the same name. Best practice is to rename scripts and retain them in case you have issues for Customer Support. Do not execute the same script twice without seeking advice from Customer Support.
Modify and run the script.sql. Add the application to the Contributor Administration Console. Configure the Contributor application, as required. Configure the dimensions for publish if creating a Publish View layout. Run the Go to Production process. Configure publish, and if creating a Table-only layout, the dimensions for publish. Click Generate synchronization script for datastore to generate a publish script. Run the publish script (Publish script.sql).
Configure the dimensions for publish if creating a View layout. Run Go to Production. Configure publish, and if creating a Table-only layout, the dimensions for publish. Generate the publish script. Run the publish script.
No Change in Model, but Change in Dimension for Publish for View Publish Layout
These are the steps you typically perform when modifying dimensions for publish for the view publish layout in a lockdown environment. Configure the dimension for publish.
22 Cognos Planning
Unacceptable Changes
The following changes must NOT be made to the DDL script: Change the first level qualifier (the application name). Care should be taken to specify the correct string (subject to it conforming to SQL1992 standards) within the Contributor Administration Console Create Application wizard. That name will then appear within the resulting DDL script file. Change table or column names. Dynamic tables have the correct name based on the model definition. If you change the table or column names then the Contributor Administration Console attempts to change them back at the next possible opportunity. Doing so may prevent the Contributor application from functioning.
Acceptable Changes
The following changes can be made to the DDL script: Assign datastore objects to tablespaces which conform to their own standards. Add or amend storage clauses for capacity planning and to conform to local standards. Add or remove instructions GRANTing privileges on the datastore objects created within the script to relevant users/roles.
24 Cognos Planning
Steps
1. In the Production application, click Publish, and click either Table-only Layout or View Layout depending on the type of publish container you require.
Chapter 4: Publish Datastores 2. 3. 4. 5. 6. Click the Options tab, and then click the Configure button. Select the datastore server where you want to create the publish container. Click Create New. Click the button next to the Name box. Complete the New publish container dialog box: Application Name Type a name for the publish datastore. We recommend that you use the name of the current application and append to it a suffix, such as, _view for a view layout, or _table for a table-only layout. Enter an existing location for the datastore files on the datastore server. Required only by SQL Server applications.
7. If you have an Oracle and DB2 UDB application, click Tablespace. and then specify the following configuration options: Tablespace used for data Tablespace used for indexes Tablespace used for blobs Note that custom temp tablespaces are supported for Oracle only. 8. Click Create. The publish container must be added to a job server or job server cluster so that the publish jobs are processed.
26 Cognos Planning
Prefix or name applicationcolumn appcolumntype appobjecttype applicationobject dimensionformats adminevent adminhistory containeroption job jobitem jobitemstatetype jobstatetype jobtask jobtype objectlock publishparameter
Contains tables used to track when major events occurred in the publish container. Contains tables with information relating to jobs.
A table used to lock objects in the system when they are being processed.
Oracle 30 30
Names cannot begin with a number or underscore (_), and can include the following characters: A through Z and a through z 0 through 9 @, #, $, and _ (underscore)
Chapter 4: Publish Datastores The items tables have the following columns. Column itemid dimensionid itemname displayname disporder itemiid Description Unique Identifier for the item Unique identifier for the D-List Name of the Item Display name of the item Display order specified in Analyst, which is zero-based D-List integer identifier for the item, which is used as the primary key
Simple hierarchy tables are created by the publish table-only layout. They are intended to be used when there are simple parent-child relationships between D-List items that can be summed. The purpose of this is to allow a reporting tool to automatically generate summaries for each hierarchy level, or for use with applications that do not require precalculated data, such as a staging source for a data warehouse. In the following examples, D-List items are represented by letters, and the relationships between items are drawn as lines. Parent D-List items are calculated from child D-List item dependencies. Leaf D-List items do not have child D-List item dependencies. All D-List items have their values shown in simple parenthesis and in addition, leaf D-List item codes are shown in curly braces. D-List Value 0 1 2 3 Description Direct child of a simple sum D-List item. The leaf has multiple parents. The leaf item is part of a sub-hierarchy that has been moved to the root (no parent). The leaf item is an orphan.
28 Cognos Planning
The left pane is an example of simple hierarchies with values. The right pane is an example of simple hierarchies with values and leaf D-List item codes.
In the left pane, [E] has more than one parent, so parentage is assigned to the first parent in the IID order. In the right pane, [D] becomes a leaf D-List item, and [F] becomes orphaned and is moved to the root in the right pane.
In the left pane, [P] is the product of [S] and [T]. Leaf D-List items of non-simple summaries get moved to the root. In the right pane, [P] became a leaf D-List item, [S] and {T] were orphaned and moved to the root in the right pane.
In the left pane, [B] is the product of [C] and [E]. [C] has its own simple summary hierarchy. Because non-simple sums are not included in the hierarchy, in the right pane, [B] becomes a leaf, [E] and [C] become orphaned and moved to the root, and [C] keeps its sub-hierarchy because it is a simple sum.
30 Cognos Planning
Chapter 4: Publish Datastores The prefixes text_, date_, and float_ are used to identify the data types of columns in tables, and the suffix _[count] is used to guarantee name uniqueness.
Metadata Tables
Metadata about the publish tables is maintained in several tables.
Description Display name of the associated Planning object. A globally unique reference (GUID) for the object. The type of object, for example, EXPORT_TABLE, DIMENSION_SIMP_HIER Describes the datastore type: Table. This is an internal version number used for debugging.
32 Cognos Planning
Chapter 4: Publish Datastores The columns of the dimensionformats table are as follows. Column dimensionid itemguid formattype negativesignsymbol noofdecimalplaces scalingfactor zerovaluechars Description Globally unique identifier of the dimension for publish Globally unique identifier of the item of the dimension for publish One of percent, number, or date String indicating how negative values must be reported Number of decimal places for numerical values Integer for the scaling factor of numerical values Characters to use for zero of blank value
Common Tables
Common tables are created so that you can track the history of events in the publish container. The adminhistory table stores information about when major events occurred to the publish container. The adminevents table contains the IDs and descriptions of the event types used in the adminhistory table. The containeroption table is used for Oracle and DB2 to store tablespace information for blob, data, and index.
Job Tables
The following tables are created to support jobs. Table job Description Information about the jobs that are running or ran in the application. This information is used in the Job Management screen. Each Job Item is represented by a row in the jobitem table. The state of the Job Item is also stored. If a problem occurred while running the Job Item, descriptive text is stored in the failurenote column and is appended to the failurenote column for the job. Job item status types: failed, ready, running, succeeded. Job status types: canceled, complete, creating, queued, ready, running. Where and when the job items ran and the security context it used. Job types and their implementation program IDs.
jobitem
Metadata
Common
Contains tables used to track when major events occurred in the publish container. Contains tables with information relating to jobs.
Job
34 Cognos Planning
Chapter 4: Publish Datastores The items tables have the following columns. Column itemid dimensionid itemname displayname disporder Description Unique Identifier for the item Unique identifier for the D-List Name of the Item Display name of the item Display order specified in Analyst, which is zero-based
Views
The following views are created in a view publish layout. View name fv_cubename ev_cubename av_cubename cv_cubename Description A view on the cell data for a cube that resolves the star schema linking to the flattened out hierarchy for a dimension. A view on the cell data for a cube that resolves the star schema linking to the items in a dimension. A view on the cell annotations table for a cube that resolves the star schema. A complete view created for each cube being published.
An ev_view is created to provide a more user-friendly access to its associated export table (et_table), which contains cube data. In this view, GUIDs are simply replaced by the display name associated with the D-List items, and export value are cast to varchar when published as blobs. A fact view (with fv_prefix) is created for each cube being published and is limited to numeric values by joining the export values from the et_ table to the items in the hy_ tables for the cube.
36 Cognos Planning
Chapter 4: Publish Datastores A complete view (with cv_prefix) is created for each cube being published and is built by joining the export values from the et_ table to the items in the cy_ tables for the cube.
38 Cognos Planning
Note: In Contributor, application also refers to an Analyst plan that is made available to users on the Web through the Contributor Administration Console. A Contributor application consists of a series of linked cubes that can be used for data entry by many people at the same time.
Steps
1. Create the LOCKDOWN user by running the following SQL query:
create user LOCKDOWN identified by LOCKDOWN default tablespace users quota unlimited on users
40 Cognos Planning
2. Edit the following files on each Contributor server: epEAdminORA8Resources.xml Replace "truncate table" with "delete from". Because there is no DROP ANY TABLE privilege, the LOCKDOWN user must delete all rows in a table rather than truncating when all rows must be removed. This impacts performance because deleting is slower than truncating. epSQLDDLORA8Resources.xml Replace "--GRANT SELECT, INSERT, UPDATE, DELETE ON %1 TO "EP_DMLUSER"" with "GRANT SELECT, INSERT, UPDATE, DELETE ON %1 TO LOCKDOWN;". This allows all generated scripts to include the necessary object permission grants. 3. If datastore backups from the Contributor Administration Console are required, grant the EXP_FULL_DATABASE role to the LOCKDOWN user. 4. In the Contributor Administration Console, create the Planning Administration Domain script using the Planning Administration Domain Creation wizard. The wizard appears the first time the Contributor Administration Console is run on a computer. Alternatively, select Tools, Create Planning Administration Domain. In the Planning Administration Domain Configuration options screen, select Generate datastore scripts and data files. 5. Run the script. The LOCKDOWN user can now be used in the Contributor Administration Console. 6. In the Contributor Administration Console, select Tools, click Change Planning Administration Domain and select the Planning Administration Domain that was created. 7. In the Contributor Administration Console, under the appropriate datastore server, right-click Applications, and click Create Applications. Follow the wizard and on the Application Details screen, select Generate datastore scripts and data files, and complete the wizard. This creates an application script. 8. Run the application script. 9. In the Contributor Administration Console, select the appropriate datastore server, right-click Applications, click Link to Existing Applications, and select the application that was created. 10. Configure the Contributor Application as required. For more information, see the Contributor Administration Guide. 11. In the Contributor Administration Console, set the Generate Scripts option to Yes in Development, Application Maintenance, Admin Options. 12. If using Table-only Layout publish, in Application Maintenance, Dimensions for Publish, select the required data dimension for publish. 13. Generate the production version of the Contributor application by running Go to Production. 14. In the Contributor Administration Console, in the Contributor application, click Production, Publish, and either Table-only Layout, or View Layout as required. 15. Select the cubes, dimensions for publish if using View Layout, e.List items and all options except for the Publish datastore. 16. In the Options screen, click Configure. 17. Select the datastore server where the publish container will be held and click Create New. 18. Click the Create a New Publish Container button and type the name of the publish container, and location of datastore files. 19. Click Test Connection, and OK twice to return to the Options screen. 20. Click Generate synchronization script for datastore. 21. Run this script to make the required changes. 22. For pre-existing datastores, grant the LOCKDOWN user the following permissions for all objects in the datastore: select, insert, delete, and update. The LOCKDOWN user can now link to all the applications. Database Administrator (DBA) Guide 41
Cognos Planning 7.2 applications return a value of 3. Cognos Planning 7.3 applications return a value of 4. This represents a new naming convention for the Contributor database version, separate from the Contributor version.
Rollback
We recommend 1 GB tablespace, 10 segments with 1MB initial and next, and 10 min_extents. 42 Cognos Planning
Application/ function Application Data Application Index Application BLOB BLOB_Large (manual)
Contents Default Data Default Index Default LOB JOBITEM.DATA NODESTATE.DATAXML APPLICATIONSTATE.DEFINITION jOB.PARAMETERS IMPORTQUEUE.MIB NODELANGUAGEMODEL.DEFINITION Default Publish Data Default Publish Index
128 KB 128 KB 8 MB 8 MB
Import/Publish_Data_Large Table names: IM%, IE%, ET% (manual) Import/Publish_Index_Larg Indexes for Table names: IM%, IE%, ET% e (manual)
The following are minimum recommended parameters (init.ora)for Oracle 8i: open_cursors = 300 db_block_buffers = 5000 # with 8 KB db blocks shared_pool_size = 10,485,760 log_buffer = 163,840 sort_area_size = 16,384 The following are minimum recommended parameters (init.ora)for Oracle 9i/10g db_cache_size = 100 MB shared_pool_size = 100 MB log_buffer = 1 MB
Steps
1. In the appropriate Contributor application, go to Development, Configuration, Application Settings.
Chapter 5: Oracle Datastores 2. Customize the SQL*Loader command line variables in the PUBLISH_OPTIONS field. Increasing the bindsize to 2M-5M, or ROWS can be effective. Try using Direct_Path, but use with caution because this method builds the index after each session, and could cause index corruption due to the large number of SQL*Loader sessions.
Rename an Application
You clone an application/schema to rename it. You can also use the Import/Upgrade function in the Contributor Administration Console to do this. Either method is acceptable. For more information about upgrading, see the Contributor Administration Guide.
Steps
1. Export the schema. 2. Create a new Oracle user. 3. Import the schema, using FROMUSER=SOURCE_NAME TOUSER=TARGET_NAME (the new Oracle user). 4. Edit and recompile the triggers for the target_name, as the source_name is hard coded in the DDL. Use either a reverse-engineering pl/sql tool, or dba_triggers (columns: description and trigger_body) to get the create statements. 5. Run Go To Production in the Contributor Administration Console.
44 Cognos Planning
Index
A
access to data, 14 an_cubename table, 31 annotation tables table-only layout, 31 view layout, 35 annotationobject Table table-only layout, 31 annotationobject view layout table, 36 appcolumntype table, 32 application datastore, 10 applicationcolumn table, 32 applicationobject table, 32 appobjecttype table, 32
G
Go to Production, 16
H
hierarchy tables table-only layout, 28 view layout, 35
I
importing data, 15 initial data, loading, 14 items tables table-only layout, 27 view layout, 34
B
backup, 19
J
job, 17, 33 job tables table-only layout, 33 jobitem, 33 jobitemstatetype, 33 jobstatetype, 33 jobtask, 33 jobtype, 33
C
changing the Analyst model, 17 cloning, 44 Common datastore, 9 common tables table-only layout, 33 Contributor application creating, 13 Contributor datastore, 7 Contributor Datastore Objects, 8 copy data, 15 copyright, 2
L
large object types, 10 load data, 15 LOBs, 10 lockdown environment, 13
D
data types, 30 datastore object names table-only publish, 27 datastore objects, 8 DDL, modifying, 23 development_items table, 14 dimensionformats table, 33 document version, 2 dynamic datastore objects, 8
M
metadata, 7 metadata tables, 31
N
naming conventions, 7
O
object lock table, 34 objectlock table, 34 open environment, 14 Oracle security, 40 sizing, 42 version and license requirements, 5 Oracle client tools, 39
E
export tables view layout, 35 export tables, table-only layout, 30
Index
P
PAD, 9 performance, 43 Planning Administration Domain, 9 prepare data, 15 publish containers, 10 publish data, 17 applicationobject table, 32 views, 36 publishing to a different datastore, 25
R
recovery, 19 redo, 42
S
script.sql, 13 security administration, 42 CONGOSEP, 40 lockdown, 40 sizing datastore tablespaces, 10 SQL1992 compliant, 7 static datastore objects, 8 storing data, 17 synchronization, 17
T
table-only layout annotation tables, 31 appcolumn table, 32 applicationcolumn table, 32 appobject table, 32 common tables, 33 data types, 30 dimensionformats table, 33 export table, 30 hierachy tables, 28 items tables, 27 metadata tables, 31 tablespace management, 11 tablespaces, sizing, 10
U
user access to data, 14
V
version document, 2 views, 36
46 Cognos Planning