Local Oracle Enterprise

Allocate at least 1GB of memory as the Oracle System Global Area (SGA) target size. Oracle recommends allocating 40-50% of available memory for the SGA.

Oracle instance with a previous Dimensions schema‌

If your Oracle Enterprise database already contains an Oracle instance with a previous schema, the server installer detects and upgrades the schema.

Create the Dimensions Oracle instance‌‌

Before you can install Dimensions CM with your own Oracle Enterprise, you must create an Oracle instance for the Dimensions CM schema.

• Create a fresh Oracle instance

• Verify the connection to the instance

• Save the container database access states and create tablespaces

• Log the creation of an Oracle instance

• Monitor the creation of an Oracle instance

Create a fresh Oracle instance

To create a fresh instance in your Oracle Enterprise database, install the supplied template file and run the Oracle Database Configuration Assistant (DBCA) using the template file to create an instance.

1. Copy the database template file from db_preinstall/oracle/unix to $ORACLE_HOME/assistants/dbca/templates.

   The template files are:

   • 11gR2.0.3: SerenaOracle11g.dbt

   • 12.1.0.1: SerenaOracle12c.dbt

   • 12c: SerenaOracle12102.dbt

   • 12.1.0.2: SerenaOracle12102.dbt

   • 12.1.0.2 (CM and SBM in the same Oracle instance): SerenaOracle12102CMSBM.dbt

   • PDB (for creating multitenant container databases with any version of Oracle): MicroFocusOraclePDB.dbt

2. Open the Oracle Database Configuration Assistant:
   

   cd $ORACLE_HOME/
./bin/dbca

   Note: The instructions below are applicable to the version of DBCA in Oracle 12c.

3. On the Database Operation page, select Create Database.

4. On the Creation Mode page, select Advanced Mode.

5. On the Database Template page, select the required template.

   To create a pluggable database (PDB), select the pdb_dim14 template.

6. On the Database Identification page, enter the Global Database Name and the Oracle SID (Oracle System ID). The former is limited to eight characters the first of which must be alphabetic. If the Oracle SID is eight characters or less, you can assign the same name to both fields.

   To create a container database:

   1. Verify that the Create as Container database option is selected.

   2. Select Use Local Undo tablespace for PDBs.

   3. Select the Create a Container database with one or more PDBs option.

   4. Set the Number of PDBS to 1.

   5. Enter a name for the PDB, for example, pdb_dim14.

7. On the Management Options page specify options for managing the database.

8. On the Database Credentials page, specify passwords for the user accounts. Set the passwords in accordance with your site policies and log the values for future reference.

9. On the Network Configuration page, select a current Oracle listener or create a new one.

10. On the Storage Locations page:

    • Select the storage type and locations for database files. From the Database files Storage Type list, select File System.

    • Accept the defaults for the common location of all database files or specify values supplied by your DBA.

    • Accept the default database recovery options and deselect Specify Fast Recovery Area or specify values supplied by your DBA.

11. On the Database Options page, optionally select database components, sample schemas, and custom scripts.

12. On the Initialization Parameters page, accept the default values for Memory, Sizing, Character Sets, and Connection Mode or specify values supplied by your DBA.

13. On the Create Options page, check that Create Database is selected.

14. On the Prerequisite Checks page, check the database validation results and any warnings.

15. On the Summary page, review the settings and click Finish to create the database instance.

Verify the connection to the instance

After the instance is created, verify the connection to your database:

1. Open a command prompt and enter the following:

   sqlplus system/<password>@<ora_instance>

   For the container database, specify the <ora_instance> as the PDB name, for example, pdb_dim14.

2. Check that the output confirms a successful connection.

   If sqlplus fails to connect to the container database, verify that a connector for the PDB name is defined in the tnsnames.ora file, for example:

   PDB_DIM14 = 
    (DESCRIPTION =
     (ADDRESS = (PROTOCOL = TCP)(HOST = <host name>)(PORT
      = 1521)) 
     (CONNECT_DATA =
       (SERVER = DEDICATED) 
       (SERVICE_NAME = PDB_DIM14)
     )
   )

3. To exit SQL, enter exit.

Container database: After the connection is established, save the access states and create tablespaces.

Save the container database access states and create tablespaces

A container database is created with Open, Read, and Write access, but these access states are not stored as the default. Before you stop or restart the database, make sure to save the access state.

Additionally, when you create a container database, the tablespaces are not created by the Oracle Database Configuration Assistant (DBCA). You need to create them manually.

To preserve the access state after a database restart, and create tablespaces, connect to the instance as the administrator and run the following commands:

1. Save access states:

   $ sqlplus system/<system_password>@<dsn> 
   SQL> connect / as sysdba;
   SQL> ALTER PLUGGABLE DATABASE pdb_dim14 OPEN READ 
        WRITE;
   SQL> ALTER PLUGGABLE DATABASE pdb_dim14 SAVE STATE;

2. Create tablespaces, modifying the DATAFILE paths to suit your system:

   $ sqlplus system/<system_password>@<pdb_name> 
   SQL> CREATE BIGFILE TABLESPACE "PCMS_DATA" LOGGING
     DATAFILE '/var/opt/oracle/oradata/DIM14/ 
     pcms_dat_8xxc593z.dbf' SIZE 512M REUSE AUTOEXTEND 
     ON NEXT 100M MAXSIZE 65535M EXTENT MANAGEMENT LOCAL 
     SEGMENT SPACE MANAGEMENT AUTO BLOCKSIZE 16384;
   SQL> CREATE SMALLFILE TABLESPACE "PCMS_IDX" LOGGING
     DATAFILE '/var/opt/oracle/oradata/DIM14/
     pcms_idx_8xxc6ox9.dbf' SIZE 512M REUSE AUTOEXTEND 
     ON NEXT 100M MAXSIZE 65535M EXTENT MANAGEMENT LOCAL 
     SEGMENT SPACE MANAGEMENT AUTO BLOCKSIZE 16384
   SQL> CREATE SMALLFILE TABLESPACE "PCMS_RBS" LOGGING
     DATAFILE '/var/opt/oracle/oradata/DIM14/ 
     pcms_rbs_8xxc7no8.dbf' SIZE 512M REUSE AUTOEXTEND 
     ON NEXT 100M MAXSIZE 65535M EXTENT MANAGEMENT LOCAL 
     SEGMENT SPACE MANAGEMENT AUTO;
   SQL> CREATE SMALLFILE TEMPORARY TABLESPACE
     "PCMS_TEMP" TEMPFILE '/var/opt/oracle/oradata/ 
     DIM14/pcms_tem_8xxc4qdz.tmp' SIZE 512M REUSE AUTOEXTEND 
     ON NEXT 100M MAXSIZE 65535M EXTENT 
     MANAGEMENT LOCAL UNIFORM SIZE 1024K BLOCKSIZE 16384;

Log the creation of an Oracle instance

It is good practice to keep a log of the creation of the Oracle instance using the UNIX command script. Remember to exit from the log session after the pre-installation or installation.

Connect, resource, and create view privileges.

Monitor the creation of an Oracle instance

During the Oracle instance creation the Oracle template file is checked for integrity. This check takes time to complete. Fast completion may indicate that instance creation has failed, regardless of any "success" messages you may receive. The checks described in Prepare the Oracle environmentfails in such circumstances. You must check the logs that Oracle generates in $ORACLE_HOME/cfgtoollogs/dbca/<ora_sid> (especially <ora_sid>.log) or ask your DBA.

When instance creation is complete, stop logging the installation using script (if applicable), exit, and proceed to the next section.

PCMS_DATA
PCMS_IDX
PCMS_TEMP
PCMS_RBS
USERS

ra_ckpt_<orasid> 
ora_dbw0_<orasid> 
ora_lgwr_<orasid> 
ora_pmon_<orasid> 
ora_psp0_<orasid> 
ora_mman_<orasid> 
ora_mmnl_<orasid> 
ora_mmon_<orasid> 
ora_q000_<orasid> 
ora_q001_<orasid> 
ora_qmnc_<orasid> 
ora_reco_<orasid> 
ora_smon_<orasid>

tnslsnr LISTENER

dm_control rdbms_start