when
creating the new content store database.The content store is a database that Content Manager uses to store global configuration data, global settings (such as the language and currency formats shown in the user interface), connections to data sources, and product-specific content.
Design models and log files are not stored in the content store.
You must create the content store before you can use IBM Cognos 8.
If you are upgrading
from ReportNet or a previous version of IBM Cognos 8, you
can use your existing content store with the new version of IBM
Cognos 8. After the content store is upgraded, you cannot
use it with the previous version. If you are upgrading and you want
to keep running ReportNet or the older version of IBM Cognos 8,
you must create a new content store database for use with IBM Cognos 8.
You must follow the appropriate upgrade process when
creating the new content store database.
You must create the database using one of the databases listed in the following table:
| Database | Character Encoding | Protocol |
| DB2 | UTF-8 | TCP/IP |
| Oracle | AL32UTF8 or AL32UTF16 | TCP/IP |
| SQL Server | UTF-8 or UTF-16 | TCP/IP |
| Sybase | UTF-8 | TCP/IP |
| Cognos Content Database | pre configured | pre configured |
If you plan to use the Cognos Content Database as your content store, a database is created and pre configured when the installation is complete.
You can create another instance of the Cognos Content Database. For more information see Create a New Content Store Using Cognos Content Database.
Note that Cognos 8 uses a single sort order that specifies the rules used by the database to interpret, collect, compare, and present character data. For example, a sort order defines whether the letter A is less than, equal to, or greater than the letter B; whether the collation is case sensitive; and whether the collation is accent sensitive. For more information about collation and collation sequences, see the database documentation.
The database you create for the content store must contain the recommended configuration settings.
To ensure a successful installation, use the following guidelines when creating the content store.
IBM Cognos 8 requires 32-bit library files when running in a 32-bit application server. If you have installed DB2 version 9.5, the 64-bit library files may be set in your environment variables. You must change the library files used or change the order in which the library files are listed so that IBM Cognos 8 can find the 32-bit library files. The 32-bit library files must be listed first for IBM Cognos 8.
If you create your own content store, use the following checklist to help you set up the content store on DB2.
If you use type 2 UDBC connectivity, set the appropriate environment variables for DB2, which are as follows.
Environment variable
Description
DB2DIR
The top level directory that contains the database client software or the entire database installation.
LD_LIBRARY_PATH
The load library path.You must add the driver location.
For example, LD_LIBRARY_PATH= $DB2_location/sqllib/lib32: $LD_LIBRARY_PATH
Examples:
For Solaris and Linux:
LD_LIBRARY_PATH= $DB2DIR/lib: $LD_LIBRARY_PATH
For AIX:
LIBPATH=$DB2DIR/lib:$LIBPATH
For HP-UX:
SHLIB_PATH=$DB2DIR/lib:$SHLIB_PATH
DB2INSTANCE
The default database server connection.
DB2CODEPAGE
Setting this optional environment variable to a value of 1208 provides support for multilingual databases.
For information about whether to use this environment variable, see the DB2 documentation.
Use UTF-8 as the code set value when you create the database. To check if your database has the correct code set, using the command line interface, type the following at the command prompt:
db2 get database configuration for database_name
The code set value should be UTF-8 and the code page value should be 1208.
Ensure that you set the following configuration parameters.
Property
Setting
Application heap size
(applheapsz)
1024 KB
Lock timeout (locktimeout)
240 seconds
Do not set this to an infinite timeout value.
If the application heap size value is too small, out of memory errors may occur when there are many users.
Create a buffer pool with a page size of 32 KB, and a second one with a page size of 4 KB.
Create a system temporary tablespace using the 32 KB buffer pool you created in the previous step.
Create a user temporary tablespace using the 4 KB buffer pool you created.
Global temporary tables will be created in the user temporary tablespace.
Create a regular user tablespace using the 4 KB buffer pool you created.
If you are also creating a logging database, create an additional regular user tablespace with a page size of 8 KB.
Grant the following database privileges for the user account IBM Cognos 8 will use to access the database:
connect to database
create tables
create schemas implicitly
Tip: If you want to host more than one content store on your DB2 instance and you will use both at the same time, use a different user account for each content store to ensure that each IBM Cognos 8 instance is fully isolated from the other.
Ensure that the user account has use privileges for the user temporary tablespace and other appropriate tablespaces associated with the database.
Create a schema for the user account IBM Cognos 8 will use to access the database, and ensure the user has create, drop, and alter permissions for the schema.
We recommend that you create a profile that sources the sqllib/db2profile from the DB2 user’s home directory. For example, the content of your .profile will be similar to the following:
if [ -f /home/db2user/sqllib/db2profile ]; then./home/db2user/sqllib/db2profilefiYour database administrator must back up IBM Cognos 8 databases regularly because they contain the IBM Cognos data. To ensure the security and integrity of databases, protect them from unauthorized or inappropriate access.
The database you create for the content store must contain some recommended configuration settings.
To ensure a successful installation, use the following guidelines when creating the content store.
Use the following checklist to help you help you set up the content store in DB2 on z/OS.
Create a database instance, storage group, and a user account for the content store.
A user must have permissions to create and delete tables in the database.
IBM Cognos 8 uses the credentials of the user account to communicate with the database server.
Ensure you reserve a buffer pool with a page size of 32 KB, and a second one with a page size of 4 KB for the database instance.
Administrators must run a script to create tablespaces to hold Large Objects and other data for the content store and grant user rights to the tablespaces. For information about running the script, see Create Tablespaces for DB2 Content Store on z/OS. Your database administrator must back up IBM Cognos 8 databases regularly because they contain the IBM Cognos data. To ensure the security and integrity of databases, protect them from unauthorized or inappropriate access.
The database you create for the content store must contain some recommended configuration settings.
To ensure a successful installation, use the following guidelines when creating the content store.
Use the following checklist to help you set up the content store on Oracle.
Ensure that the parameter for the database instance compatibility level of the content store database is set to 9.0.1 or higher.
For example, you can check the COMPATIBLE initialization parameter setting by issuing the following SQL statement:
SELECT name, value, description FROM v$parameter WHERE name='compatible';
For information about changing an instance configuration parameter, see the Oracle documentation.
Determine if the database is Unicode.
Tip: One method is to type the following select statement:
select * from NLS_DATABASE_PARAMETERS
If the result set returns an NLS_CHARACTERSET that is not Unicode, create a new database and specify AL32UTF8 for the database character set parameters.
Determine which user account will be used to access the database.
Tip: If you want to host more than one content store on your Oracle instance and you will use both at the same time, use a different user account for each content store to ensure that each IBM Cognos 8 instance is fully isolated from the others.
Ensure that the user account that accesses the database has permission to do the following:
connect to the database
create, alter, and drop tables, triggers, views, procedures, and sequences
insert, update, and delete data in the database tables
Your database administrator must back up IBM Cognos 8 databases regularly because they contain the Cognos data. To ensure the security and integrity of databases, protect them from unauthorized or inappropriate access.
The database you create for the content store must contain some recommended configuration settings.
To ensure a successful installation, use the following guidelines when creating the content store.
Use the following checklist to help you set up the content store on Microsoft SQL Server.
Ensure that the collation sequence is case-insensitive. In a Custom installation, you choose a collation, which includes character sets and sort order, during the SQL Server setup. In a Typical installation, the installation uses the locale identified by the installation program for the collation. This setting cannot be changed later.
When connecting to Microsoft SQL Server Management Studio to create the database, use SQL server authentication.
If you connect using Windows authentication, the database that you create will also use Windows authentication. In this situation, you must configure the database connection using a database type of SQL Server database (Windows Authentication) in IBM Cognos Configuration.
For the user account that will be used to access the database, create a new login under Security and use the following settings:
Select SQL Server authentication.
Clear the Enforce password policy check box.
Tip: If you want to host more than one content store on your Microsoft SQL Server instance and you will use both at the same time, use a different user account for each content store to ensure that each IBM Cognos 8 instance is fully isolated from the others.
For Microsoft SQL Server 2008, grant EXECUTE permission to the user account that accesses the database.
For the content store database, create a new database under Databases.
Under Security for the new database, create a new schema and assign a name to it.
Under Security for the new database, create a new user with the following settings:
For Login name, specify the new login that you created for the user account.
For Default schema, specify the new schema.
For Owned Schemas, select the new schema.
For Role Members, select db_datareader, db_datawriter, and db_ddladmin.
The database you create for the content store must contain some recommended configuration settings.
To ensure a successful installation, use the following guidelines when creating the content store.
Use the following checklist to help you set up the content store on Sybase.
On the Sybase server, create a server instance with an 8 KB server page size. For instructions, see the Sybase documentation.
If required, install jConnect 5.5. This tool sets up the communication between the JDBC driver and the Sybase Adaptive Server instance.
For instructions, see the Sybase documentation.
If your version of Sybase does not include JConnect 5.5, you must download the installer from Sybase’s Web site.
Add the UTF-8 character set to the server instance. If required, make UTF-8 the default character set on the server. Create a database device. Tip: Set log_segment to a minimum of 10 MB.
Set the new database device as the default. Information about the new database will be stored in the new database device. Keep a backup of the database device for recovery purposes.
Create the database. Determine which user account will be used to access the database. Tip: If you want to host more than one content store on your Sybase instance and you will use them at the same time, use a different user account for each content store to ensure that each IBM Cognos 8 instance is fully isolated from the others.
Ensure that the user account has the following privileges for the database: create default, create procedure, create rule, create table, and create view. Ensure that the database has the following settings and is restarted:
create and drop table privileges for the user account
Select into property is set to True
