You can use an existing installation of an Oracle database
to create a metadata repository for InfoSphere® Information Server.
Before you begin
Include the $ORACLE_HOME/bin
directory in your system PATH to properly
invoke the sqlplus command. Requirements:
- You must configure your Oracle database with
the following character sets. These character sets are the only ones
that are compatible with InfoSphere Information Server.
NLS_CHARACTERSET = AL32UTF8
NLS_NCHAR_CHARACTERSET = AL16UTF16
If the database is
configured to use another character set, some characters will not
be stored, processed, or displayed correctly. The preinstallation
check in the InfoSphere Information Server installation
program will report a failure for this condition, and if you force
the installation it will fail.
- For Oracle 12c and 12cR2 databases, CDB is supported in InfoSphere
Information Server release 11.5.0.2 and later versions. CDB is not supported in InfoSphere
Information Server releases prior to 11.5.0.2.
About this task
This script creates a tablespace within an existing database. Attention: This script also
sets the OPEN_CURSORS initialization parameter to the minimum required
value of 1500. If this parameter is already set to a higher value,
modify the configure_xmeta_db.sql file to not
set this parameter.
Procedure
- Navigate to the following directory of the InfoSphere Information Server installation
media, where IS_suite is the
directory where you extracted the media.
Database version |
Directory |
Oracle 12c |
IS_suite/DatabaseSupport/UNIX_Linux/MetadataRepository/Oracle12c |
Oracle 12cR2 |
IS_suite/DatabaseSupport/UNIX_Linux/MetadataRepository/Oracle12cR2 |
-
From the command line, run the create_xmeta_db script to set up the
database for the metadata repository. All arguments are required and must be specified in the order
that is shown in the following example.
create_xmeta_db.sh OracleSystemUser OracleSystemPassword NetServiceName
XmetaUserName XmetaUserPassword XmetaTableSpaceName
XmetaDatafilePath
For example,
create_xmeta_db.sh SYS MANAGER DBNAME xmetauser xmetapwd xmetaspace
/u01/app/oracle/oradata/dbname
- OracleSystemUser
- The Oracle system user name to log into SQL*Plus with to create the tablespace and user. This
user must be assigned the database administrator role and must have the SYSDBA
role.
- OracleSystemPassword
- The password for the Oracle system user.
- NetServiceName
- The name for the connect descriptor as specified in the tnsnames.ora
file.
- XmetaUserName
- The name of the Oracle user that you are creating for the metadata repository tablespace.
- XmetaUserPassword
- The password for the metadata repository tablespace user.
- XmetaTableSpaceName
- The name of the metadata repository tablespace.
- XmetaDatafilePath
- The location where you want to create the data files for the tablespace. This location must
reference an existing directory. For example,
/u01/app/oracle/oradata/dbname.
- From the same directory as step 1, run the same command
but with staging area information to set up the database for the staging
area. All arguments are required and must be specified in the order
that is shown in the following example.
create_xmeta_db.sh OracleSystemUser OracleSystemPassword NetServiceName
StagingUser StagingUserPassword StagingTableSpace
StagingDatafilePath
For
example, the following command runs as the user,
SYS
,
using the password
sys_pwd
. The command connects
to Oracle with the TNS name
xmeta
, and creates a
tablespace named
xmetasrsp
under the
/u01/app/oracle/oradata/dbname directory.
The Oracle account named
xmetasr
is created using
the password
xmetapwd
, and is used to access the
staging area schema.
create_xmeta_db.sh SYS sys_pwd xmeta xmetasr xmetapwd xmetasrsp
/u01/app/oracle/oradata/dbname
- OracleSystemUser
- The Oracle system user name to log into SQL*Plus with to create the tablespace and user. This
user must be assigned the database administrator role and must have the SYSDBA
role.
- OracleSystemPassword
- The password for the Oracle system user.
- NetServiceName
- The name for the connect descriptor as specified in the tnsnames.ora
file.
- StagingUser
- The name of the user that you are creating to access the staging
area schema. This user must be different from the active repository
user because the staging area schema must be a different schema within
the metadata repository database.
- StagingUserPassword
- The password for the staging area schema user.
- StagingTableSpace
- The name of the tablespace that you are creating for the staging
area schema.
- StagingDatafilePath
- The location where you want to create the data files for the staging
area tablespace. This location must reference an existing directory.
For example, /u01/app/oracle/oradata/dbname.
- If you are using IBM®
DataStage® Flow Designer, you must
create the user preference table to store the user settings. For information on creating the user
preference table, see the README document in the directory
install_dir\DatabaseSupport\UNIX_Linux\CognitiveDesignerRepository\Oracle12c.
-
Create the necessary IBM Information Server Enterprise Search users and schema by running the
create_ug_schemas.sh script from the command line. This step is required if
during installation you choose to install IBM Information Server Enterprise Search.
-
Navigate to the following directory of the InfoSphere Information Server installation
media, where IS_suite is the directory where you extracted
the media.
IS_suite/DatabaseSupport/UNIX_Linux/InformationAnalyzer/Oracle/ug
-
Run the following command to create the IBM Information Server Enterprise Search schema. All
arguments are required and must be specified in the order that is shown in the following
example.
./create_ug_schemas.sh OracleSystemUser OracleSystemPassword ServiceName TableSpaceName
For
example:
./create_ug_schemas.sh SYS MANAGER DBNAME xmetaspace
- OracleSystemUser
- The Oracle system user used to log in to the
sqlplus
utility to create the
schema. This user must be assigned the database administrator role.
- OracleSystemPassword
- The password for the Oracle system user.
- ServiceName
- The Oracle TNS service name. The name is the same as the TNS service name that is provided as
the
NetServiceName
argument to the create_xmeta_db.sh script
in step 2.
- TableSpaceName
- Name of the tablespace to use for the new schema. The name is the same as the metadata
tablespace that is provided as the
XmetaTableSpaceName
argument to the
create_xmeta_db.sh script in step 2.