Creating tablespaces and users on Oracle
You can use the create_oracle_tablespaces_and_users.sql script to create databases and users for the Oracle database. This script is available in the TSSA-DW<version>-external-files.zip file on the TrueSight Server Automation - Data Warehouse BMC Electronic Product Distribution (EPD) location.
By default, the script creates the following Oracle tablespace names:
Oracle tablespaces
Database instance | Tablespace name | Purpose |
---|---|---|
1 | BSARA_DATA | To store the data warehouse tables except for the Audit and Inventory tables. |
1 | BSARA_INDEX | To store the data warehouse indexes except for the Audit and Inventory tables. |
1 | BSARA_DATA2 | To store the Inventory Snapshot tables. |
1 | BSARA_INDEX2 | To store the Inventory Snapshot indexes. |
1 | BSARA_DATA3 | To store the Audit tables. |
1 | BSARA_INDEX3 | To store the Audit indexes. |
1 | BSARA_ETL_REPO | To store information required by Oracle Data Integrator (ODI) during the ETL process. |
1 | BSARA_ETL_STAGE | To store the ETL staging tables that are created, used, and dropped by the ETL processes. |
By default, the script creates the users shown in the following table.
Oracle users
User | Description | Required privileges |
---|---|---|
TSSADW_DW | This user has the following responsibilities:
Default password - sa | This user requires the following privileges:
This user also needs an unlimited quota on the BSARA_DATA, BSARA_INDEX, BSARA_DATA2, BSARA_INDEX2, BSARA_DATA3, BSARA_INDEX3, and BSARA_ETL_STAGE tablespaces. |
TSSADW_ETL_MASTER | This user has the following responsibilities:
Default password - sa | This user requires the following privileges:
This user also needs an unlimited quota on the BSARA_ETL_REPO tablespace. |
TSSADW_ETL_WORK | This user has the following responsibilities:
Default password - sa | This user requires the following privileges:
This user also needs an unlimited quota on the BSARA_ETL_REPO tablespace. |
To create tablespaces and users
- Download the product files from the TrueSight Server Automation - Data Warehouse BMC Electronic Product Distribution location.
- Extract the TSSA-DW<version>-external-files.zip file to a directory outside the C:\Program Files directory to avoid any file sharing conflicts.
Ensure that the data warehouse schema type aligns with the TrueSight Server Automation database in one of the following ways:
If you have one or more TrueSight Server Automation databases that use the CHAR schema, the data warehouse must use the CHAR schema.
If you have one or more TrueSight Server Automation databases that use the NCHAR schema, the data warehouse must use the NCHAR schema.
If you have multiple TrueSight Server Automation databases and some use the CHAR schema and others use the NCHAR schema, the data warehouse must use the NCHAR schema.
If you are using NCHAR schema, ensure that you use a Unicode value of AL16UTF16.
NLS_NCHAR_CHARACTERSET=AL16UTF16.
- Ensure that the data warehouse uses the same character set as TrueSight Server Automation database or its subset character set. For example, if the TrueSight Server Automation database uses AL32UTF8, the data warehouse must use the same character set or its subset character set.
- If you are using non-English databases, such as Asian customers, ensure that you use the NCHAR character set.
- Ensure that the setting for the
NLS_LENGTH_SEMANTICS
parameter for the data warehouse schema is CHAR. Ensure that the
global_names
parameter for the Oracle instance where TrueSight Server Automation - Data Warehouse is located is set to false. If theglobal_names
parameter is not set to false, the primary site installation fails. After you install the product, you can set this parameter to true if needed.Ensure that the TrueSight Server Automation database user must have Execute permission on the DBMS_JOB and DBMS_LOCK Oracle packages.
Ensure that the tnsnames.ora file on the data warehouse database server contains the TNS entry of the TrueSight Server Automation database instance and the TNS name matches with the Service name.
Note: Installing Oracle server on the same server as Oracle client
An error might occur when the Oracle server is installed on the same server with Oracle client because of an incorrect sequence of the Oracle path in the
PATH
variable. To avoid this issue, set the client entry before the Oracle server entry in the path variable. For example (Linux), set thePATH
variable as follows:/data1/oracle/product/11.2.0/client_1/bin;data1/oracle/product/11.2.0/db_1/bin;
- Navigate to the ../TSSA-DW<version>-external-files/Oracle/create_oracle_tablespaces_and_users.sql script and edit it as follows:
For each user, modify the password as required. Ensure that the passwords:
- Do not begin with an equal sign (=) character.
- Do not begin with an integer.
- Do not contain spaces.
Do not use the following special characters:
- Ampersand (&)
- Double quotes (" ")
- Pipe (|)
- Less than sign (<)
- Greater than sign (>)
- Single quotes (' ')
- Forward slash (
/
) - Semicolon (;)
Modify the Oracle data file paths as required.
Do not modify the tablespace names. Do not save the following tablespaces on the same physical disk as the BSARA_ETL_STAGE tablespace to prevent an impact on the ETL performance:
BSARA_DATA, BSARA_INDEX, BSARA_DATA2, BSARA_INDEX2, BSARA_DATA3, and BSARA_INDEX3Change the value of the
MAXSIZE
parameter for the following tablespaces according to your sizing requirements.Note: Calculating sizing requirements
To know the size requirements, see Sizing tools . The sizing worksheet returns the tablespace size in GB. Before you modify the
MAXSIZE
parameter in the script, convert it into MB.
- BSARA_DATA
- BSARA_INDEX
- BSARA_DATA2
- BSARA_INDEX2
- BSARA_DATA3
- BSARA_INDEX3
- BSARA_ETL_STAGE
BSARA_ETL_REPO
- Save the script.
Log in to SQL Plus by using a user account with sysdba privileges on the Oracle database instance where you want to create the data warehouse. For example, you can log in using the following commands:
sqlplus /nolog connect sys/<password>@<TNS_ENTRY> as sysdba
To create the reports data warehouse tablespaces and users, run the script.
@create_oracle_tablespaces_and_users.sql;
- Log out of SQL Plus.
Comments
Log in or register to comment.