Extract the files from the compressed folders and restore
the databases.
Before you begin
- Make sure that the following are installed, configured, and running:
- IBM® Rational® Insight server
- Framework Manager
- On the system where the Rational Insight is installed,
make sure that database backup files are present in the [rational_insight_installation_directory]/cognos/webcontent/samples/datasources directory.
- Make sure that you have sufficient disk space in the target location.
You might need 150 MB for the four schemas of the GO Sales data
and 200 MB for the single schema of the GO Data Warehouse data.
For a list of the sample databases and associated files, see
the related links at the bottom of the page.
About this task
To set up the Great Outdoors databases:
- If you want to, copy the backup files for the samples databases
to your database backup directory. To ensure the security and integrity
of the IBM Cognos® Rational Insight
server, copy the files to a directory that is protected from unauthorized
or inappropriate access.
- Using your database management tool, restore the sample
databases.
Some points to help you during the process:
- Give the restored databases the same names as the backup or export
file names. The names are case-sensitive.
- Use the UTF-8 character set on the database server.
- To see reports in multiple languages, use the UTF-8 character
set on the Windows® client
system for an Oracle or DB2® dataabase.
- Create users with select privileges for tables in multiple
schemas. The GO Data Warehouse package specifies a single connection
object and user signon. It needs a single user named GOSALESDW with
select privilege on tables in the GOSALESDW schema. The GO Sales package
also specifies a single connection object and user signon. It needs
a single user named GOSALES with select privilege on tables in four
schemas: GOSALES, GOSALESHR, GOSALESMR, and GOSALESRT.
- To see reports in multiple languages, set the environment
variables:
- Use the UTF-8 character set on the Windows client system.
- For DB2, set the DB2CODEPAGE environment
variable value to 1208.
- For Oracle, 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.
- Restore the databases.
- For DB2:
- Create the GS_DB database, and create a buffer
pool with a page size of 16 KB and an associated table space.
- For each database, create at least one user who has select permissions
for all the tables in the restored databases.
- Extract the DB2 move file.
On Linux® systems, extract
the DB2 move file using the gnutar or tar command.
On Windows systems, if you
use WinZip to extract the DB2 move
file, make sure 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
Note: The
next two steps are needed if you want to add views, constraints, user
privileges, and stored procedures to the GS_DB database.
- Update the user name and password at the top of the gs_db_modify.sql file
and save the file.
- Run the gs_db_modify.bat file.
- For Microsoft® SQL
Server, use Microsoft SQL
Server 2000 or Microsoft SQL
Server 2005. Make sure that you use TCP/IP connectivity for the Microsoft SQL server. Restore
the database from a device, and make sure that the restore locations
for the LDF and MDF database files are correct.
- For Oracle Server:
- Create the foreign key constraints for tables that reference different
schemas.
- Run the gs_or_modify.sql file, which is present
in the same folder as the Oracle export files (DMP files).
Results
You can now create the data source connections in the portal.