Restoring backup files for the samples databases

To use the samples, you must restore backup files for the samples databases. This action re-creates multilingual versions of the Great Outdoors databases.

The following sample databases and associated files are provided with IBM® Cognos® Business Intelligence. For Microsoft SQL Server, each database is delivered as a Microsoft SQL Server backup file. For Oracle, you will need to unzip the file GS_DB_ORA.tar.gz. For IBM DB2, you will need to unzip the file GS_DB.tar.gz. The location for the databases are as follows.

Table 1. IBM DB2 and Oracle samples back up locations
Databases	File Location
IBM DB2	GS_DB\data
Oracle	GS_DB_ORA\data

Table 2. IBM DB2 databases and files
Database or schema description	File name
Great Outdoors sales	GS_DB.tar.gz
Great Outdoors retailers	GS_DB.tar.gz
Great Outdoors sales data warehouse	GS_DB.tar.gz
Great Outdoors market research	GS_DB.tar.gz
Great Outdoors human resources	GS_DB.tar.gz

Table 3. Microsoft SQL Server databases and files
Database or schema description	File name
Great Outdoors sales	GOSALES.zip
Great Outdoors retailers	GOSALES.zip
Great Outdoors sales data warehouse	GOSALESDW. zip
Great Outdoors market research	GOSALES.zip
Great Outdoors human resources	GOSALES.zip

Table 4. Oracle databases and files
Database or schema description	File name
Great Outdoors sales	GS_DB_ORA.tar.gz
Great Outdoors retailers	GS_DB_ORA.tar.gz
Great Outdoors sales data warehouse	GS_DB_ORA.tar.gz
Great Outdoors market research	GS_DB_ORA.tar.gz
Great Outdoors human resources	GS_DB_ORA.tar.gz

When restoring the samples databases, ensure that you do the following:

Give the restored databases the same names as the backup or export file names.
The names are case-sensitive.

You use the correct username and password.
Create users with select privileges for tables in multiple schemas.
Setup for the GO Data Warehouse packages specifies a single connection object and user signon. This requires a single user named GOSALESDW with the select privilege to tables in a single schema named GOSALESDW.

Setup for the GO Sales packages specifies a single connection object and user signon. This requires a single user named GOSALES with the select privilege to tables in four schemas: GOSALES, GOSALESHR, GOSALESMR, and GOSALESRT.
Use the UTF-8 character set on the Microsoft Windows operating system computer that is the Oracle or DB2 client to see reports in multiple languages.
For DB2, you must set the DB2CODEPAGE environment variable to a value of 1208. For Oracle, you must set the NLS_LANG environment variable to a value that is specific to a region. For example, set NLS_LANG for Americas to American_America.UTF8.
Have sufficient disk space available in the target location. Reserve 150MB for the GO Sales data (four schemas) and 200MB for the GO Data Warehouse data (one schema).

IBM DB2 Considerations

The data files for db2move and the scripts, to add constraints, are located in the data directory. The data directory is created when you unzip the GS_DB.tar.gz file.

If you use WinZip to extract the DB2 move file on Windows, ensure that the TAR file smart CR/LF conversion option is not selected.

After extracting the DB2 move file, restore the schemas to a database named GS_DB.

To add views, constraints, user privileges, and stored procedures to GS_DB, prepare and run the gs_db_modify files included with the samples in the following order:

Update the user name and password in gs_db_modify.sql and save it.
Execute gs_db_modify.bat

Note: If the script file attempts to create a stored procedure where the procedure does not exist an error is generated. This error does not affect the samples.

Oracle Considerations

To create foreign key constraints in tables that reference different schemas, you must run gs_or_modify.sql, found in the same folder as the .dmp files.

Microsoft SQL Server Considerations

If you restore the Microsoft SQL Server backup files, you must use Microsoft SQL Server 2000 or Microsoft SQL Server 2005. Ensure that TCP/IP connectivity is used for the Microsoft SQL Server.