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.
By default, Cognos 8 products share the content store database. You must create this database using one of the following:
Microsoft SQL Server
Oracle
DB2
Sybase Adaptive Server Enterprise (ASE)
On Linux, you can use Oracle, DB2, or Cognos Content Database for the content store.
A Microsoft SQL Server or Oracle database can use UTF-8 or UTF-16 encoding. A DB2 or Sybase database must use UTF-8 encoding. All database types must use the TCP/IP protocol, which is required by Cognos 8 to access data.
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 vendor documentation.
Your database administrator must back up 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.
If you are upgrading
from ReportNet, you can use your existing content store with Cognos
8. After the content store is upgraded to Cognos 8, you cannot use
it with ReportNet. If you are upgrading and you want to keep the
existing version of ReportNet, you must create a new content store
database for use with Cognos 8. You must follow the appropriate
upgrade process when creating the new content store database.
If you installed and are using Cognos Content Database as your content store, a database is already created and configured. However, you can create another database instance using Cognos Content Database.
Ensure that your installation of Microsoft SQL Server is configured as follows:
UTF-8 or UTF-16 encoding is used
For more information about character sets, encoding, and collation, see the Microsoft SQL documentation.
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.
the TCP/IP protocol is enabled
This protocol is required by Cognos 8 to access data.
Open Microsoft SQL Server Management Studio and connect to the database server using SQL server authentication.
If you connect using Windows authentication, the database that you create will also use Windows authentication. Cognos 8 is configured by default to use a database with SQL server authentication.
Create the database.
If you connected to the database server using Windows authentication, you must configure the database connection using a database type of SQL Server database (Windows Authentication) in Cognos Configuration.
For more information, see Set Database Connection Properties for the Content Store.
Create the user account that will be used to access the database:
Under Security, right click Logins and select New Login.
Specify a Login name.
Select SQL Server authentication and specify the Password.
Clear Enforce password policy.
This clears all three check boxes.
Click OK.
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 Cognos 8 instance is fully isolated from the others.
Create a schema:
Under Databases, expand the database (new_database) that you created in step 3.
Under new_database, expand Security.
Right-click Schemas and select New Schema.
Specify the Schema name and click OK.
Configure the database user:
Under Databases, new_database, Security, right click Users and select New User.
Specify the User name.
For Login name, browse and select the login that you created in step 4.
For Default schema, browse and select the schema that you created in step 5.
In the Owned Schemas list, select the same schema as Default schema.
In the Role Members list, select db_datareader, db_datawriter, and db_ddladmin.
Click OK.
Repeat steps 4 to 6 for each new user account.
Ensure that the parameter for the database instance compatibility level of the content store database is set to 9.0.1 or higher.
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
The result set returns NLS_CHARACTERSET as UTF-8 or UTF-16, or AL32UTF8 or AL16UTF16, or not Unicode.
If the result set returns an NLS_CHARACTERSET that is not Unicode, create a new database and specify AL32UTF8 or UTF-8 for the database character set parameters.
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 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
Set the appropriate environment variables for DB2.
Environment variable | Description |
DB2DIR | The top level directory that contains the database client software or the entire database installation. |
libraryPATH | The load library path.You must add driver location. Examples: |
On Solaris: LD_LIBRARY_PATH | Solaris example: LD_LIBRARY_PATH= $DB2DIR/lib: $LD_LIBRARY_PATH |
On AIX: LIBPATH | AIX example: LIBPATH=$DB2DIR/lib: $LIBPATH |
On HP-UX: SHLIB_PATH | HP-UX example: 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. |
Determine if the database is Unicode by typing the following at the command prompt:
db2 get database configuration for database_name
The codepage is Unicode if it has a value of 1208.
If the codepage is not Unicode, create a new database that has a codepage value of 1208.
Ensure that you set the following configuration parameters.
Property | Setting |
Application heap size (applheapsz) | 1024k |
Lock timeout | 4 min. (or 240 sec.) Do not set this to an infinite timeout value. |
Create a buffer pool with a page size of 32k.
Create a system temporary tablespace with a page size of 32k.
Create a user temporary tablespace with a page size of 4k.
Global temporary tables will be created in the user temporary tablespace.
Create a regular user tablespace with a page size of 4k.
If you already created the content store and are now creating a logging database, create an additional regular user tablespace with a page size of 8k.
Determine which user account Cognos 8 will use to access the database.
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 Cognos 8 instance is fully isolated from the others.
Grant create and drop table privileges on the database to the user account.
Ensure that the user account has CREATETAB, CONNECT and IMPLICITSCHEMA privileges for the database.
Ensure that the user account has USE privileges for the USER TEMPORARY tablespace and other appropriate tablespaces associated with the database.
For Windows XP, ensure that the user account has GRANT privileges for the USER TEMPORARY tablespace.
On the Sybase server, create a server instance with an 8K 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 Cognos 8 instance is fully isolated from the others.
Grant create and drop table privileges on the database to the user account.
Ensure that the user account has the following privileges for the database: create default, create procedure, create rule, create table, and create view.
For the database, set the Select into property to True and restart the server.
On the computer where you installed Cognos Content Database, go to the c8_location\derby10.1.2.1\bin directory.
You need only to perform this task if you want to create another content store database in Cognos Content Database. During Cognos Content Database installation, a database was created and Cognos 8 is already configured to use that database.
Start the ij utility using the ij.bat or ij.ksh script.
The ij utility is a command line utility for creating and managing Cognos Content Database.
Create a database by typing the following ij utility command:
connect 'jdbc:derby://host:port/db_name;create=true;user=username; password=password';
For example, to create a database named contentstore on the localhost computer on port number 1527 as a user named cognos with a password of cognos, you would type
connect 'jdbc:derby://localhost:1527/contenstore;create=true;user=cognos;password=cognos';
The database name is case sensitive.
The database files are located in the c8_location\contentstore directory.
Close the ij utility by typing the following command:
disconnect;