Installation Guide for Oracle Self-Service E-Billing > Configuring the Oracle Database >

Configuring the Oracle Self-Service E-Billing Database on Oracle RAC

Configuring Oracle Self-Service E-Billing on Oracle Real Application Clusters (RAC), or on Oracle Exadata using RAC, requires that you manually create a database instance with Database Configuration Assistant (DBCA).

If you are using Oracle Automatic Storage Management (ASM) as the volume manager and file system for database files, then you must also modify the Ant script before creating the schemas. You do not need to modify the Ant script if you are using a conventional volume manager and file system for database files.

If you are using Oracle RAC One Node and creating a single instance of a database on Oracle Exadata, then you do not have to follow these steps. Use the procedures for UNIX described Creating the Oracle Self-Service E-Billing Database Using Ant (Single Node).

To configure the Oracle Self-Service E-Billing database on Oracle RAC

1. Configure the Single Client Access Name (SCAN) Virtual IP address and SCAN listener to connect to the RAC database. For details on how to use SCAN, see Oracle Grid Infrastructure Installation Guide.
2. Create the database instance manually, using DBCA. Create an instance for the Billing and Payment application on each node.

   NOTE:  DBCA automatically creates a RAC Net Service Name for a new instance. You do not have to manually configure the RAC Net Service Name in the tnsnames.ora file.

3. Create unique service names for each RAC node. Follow the instructions for ensuring the availability of service names for Oracle RAC nodes in Oracle Warehouse Builder Installation and Administration Guide. The following table shows sample data for each node.

   Host	SID	Service	Net Service Name for the Node in the tnsnames.ora File
   Hostname1	ebill1	ebill1	ebill1
   Hostname2	ebill2	ebill2	ebill2

4. Make sure each RAC Net Service Name exists in the tnsnames.ora file, adding any unique Net Service Names defined for a node.
5. Use SQL*Plus to log on the EBILL instance as sysdba. Run the following scripts individually as the EBILL sysdba user:

   $ORACLE_HOME/owb/UnifiedRepos/clean_owbsys.sql

   $ORACLE_HOME/owb/UnifiedRepos/cat_owb.sql SYSTEM

   $ORACLE_HOME/owb/UnifiedRepos/unlock_owbsys.sql

   $ORACLE_HOME/rdbms/admin/userlock.sql

   $ORACLE_HOME/rdbms/admin/dbmslock.sql

6. If you are using Oracle Automatic Storage Management (ASM), then make the following modifications to the buildinstance.xml file, found in the EDX_HOME/db/oracle directory. Otherwise, skip this step.
   • Remove the following code from the CheckdirOLAP target:

   <available file="${filepath}" type="dir" property="direxists"/>

   <fail unless="direxists" message="${line.separator}${line.separator}Directory '${filepath}' does not exists. Create the folder and install again; or try a different path for the Tablespace"/>

   • Remove the following code from the CheckdirOLTP target:

   <available file="${filepath}" type="dir" property="direxists"/>

   <fail unless="direxists"

   message="${line.separator}${line.separator}Directory '${filepath}' does not

   exists. Create the folder and install again; or try a different path for the

   Tablespace"/>

   • In the target SetupTspaceMstKey -> replace -> replacefilter, remove /${OLAP_USER}/data from each place where it appears in the following code:

   <replacefilter

   token="$TDE_ENCRYPT_OLAPTSPACE"

   value="${TDE_ENCRYPT_OLAPTSPACE}"/>

   <replacefilter

   token="$L_DB_EDX_DATA_TB_FILE_LOC"

   value="${L_DB_EDX_DATA_TB_FILE_LOC}/${OLAP_USER}/data"/>

   <replacefilter

   token="$L_DB_EDX_INDX_TB_FILE_LOC"

   value="${L_DB_EDX_INDX_TB_FILE_LOC}/${OLAP_USER}/data"/>

   • Also in the target SetupTspaceMstKey -> replace -> replacefilter, remove /${OLTP_USER}/data from each place where it appears in the following code:

   <replacefilter

   token="$TDE_ENCRYPT_OLTPTSPACE"

   value="${TDE_ENCRYPT_OLTPTSPACE}"/>

   <replacefilter

   token="$L_DB_EDX_DATA_TB_FILE_LOC"

   value="${L_DB_EDX_DATA_TB_FILE_LOC}/${EBILL_SID}/${OLTP_USER}/data"/>

   <replacefilter

   token="$L_DB_APP_DATA_TB_FILE_LOC"

   value="${L_DB_APP_DATA_TB_FILE_LOC}/${EBILL_SID}/${OLTP_USER}/data"/>

   <replacefilter

   token="$L_DB_EDX_INDX_TB_FILE_LOC"

   value="${L_DB_EDX_INDX_TB_FILE_LOC}/${EBILL_SID}/${OLTP_USER}/data"/>

   <replacefilter

   token="$L_DB_APP_INDX_TB_FILE_LOC"

   value="${L_DB_APP_INDX_TB_FILE_LOC}/${EBILL_SID}/${OLTP_USER}/data"/>

   <replacefilter

   token="$L_DB_LOAD_DATA_TB_FILE_LOC"

   value="${L_DB_LOAD_DATA_TB_FILE_LOC}/${EBILL_SID}/${OLTP_USER}/data"/>

   <replacefilter

   token="$L_DB_LOAD_INDX_TB_FILE_LOC"

   value="${L_DB_LOAD_INDX_TB_FILE_LOC}/${EBILL_SID}/${OLTP_USER}/data"/>

   <replacefilter

   token="$L_DB_FS_DATA_TB_FILE_LOC"

   value="${L_DB_FS_DATA_TB_FILE_LOC}/${EBILL_SID}/${OLTP_USER}/data"/>

   <replacefilter

   token="$L_DB_FS_INDX_TB_FILE_LOC"

   value="${L_DB_FS_INDX_TB_FILE_LOC}/${EBILL_SID}/${OLTP_USER}/data"/>

   <replacefilter

   token="$L_DB_STG_DATA_TB_FILE_LOC"

   value="${L_DB_STG_DATA_TB_FILE_LOC}/${EBILL_SID}/${OLTP_USER}/data"/>

   <replacefilter

   token="$L_DB_STG_INDX_TB_FILE_LOC"

   value="${L_DB_STG_INDX_TB_FILE_LOC}/${EBILL_SID}/${OLTP_USER}/data"/>

   <replacefilter

   token="$LARGE_DB_EDX_DATA_TB_FILE_LOC"

   value="${LARGE_DB_EDX_DATA_TB_FILE_LOC}/${EBILL_SID}/${OLTP_USER}/data"/>

   <replacefilter

   token="$LARGE_DB_EDX_INDX_TB_FILE_LOC"

   value="${LARGE_DB_EDX_INDX_TB_FILE_LOC}/${EBILL_SID}/${OLTP_USER}/data"/>

   <replacefilter

   token="$MEDIUM_DB_EDX_DATA_TB_FILE_LOC"

   value="${MEDIUM_DB_EDX_DATA_TB_FILE_LOC}/${EBILL_SID}/${OLTP_USER}/data"/>

   <replacefilter

   token="$MEDIUM_DB_EDX_INDX_TB_FILE_LOC"

   value="${MEDIUM_DB_EDX_INDX_TB_FILE_LOC}/${EBILL_SID}/${OLTP_USER}/data"/>

7. Make the following modifications to the Ant script OLAP property file, ebilling_olap.properties:
   • Set the SID for your software database server in the EBILL_SID property, such as EBILL_SID=ebill1.
   • Set all DB_FILE_LOC properties to point to a shared file system location.
   • If you are using ASM, then set all DB_FILE_LOC properties to this format: DISK_GROUP/EBILL_TNS/datafile. For example: L_DB_EDX_DATA_TB_FILE_LOC=+DATA/ebill/olap/datafile. Specify a local directory value for the property TRACE_FILE_LOCN, for example: TRACE_FILE_LOCN=/export/oracle/ebill. Skip the following properties:
     • DB_CONTROL_FILE_LOCN1
     • DB_CONTROL_FILE_LOCN2
     • DB_CONTROL_FILE_LOCN3
     • REDO_LOG_FILE_LOCN1
     • REDO_LOG_FILE_LOCN2
     • SYSTEM_FILE_LOCN
8. Make the following modifications to the Ant script OLTP property file, ebilling_oltp.properties:
   • Set the SID for your software database server in the EBILL_SID property, such as EBILL_SID=ebill1.
   • Set all DB_FILE_LOC properties to point to a shared file system location.
   • If you are using ASM, then set all DB_FILE_LOC properties to this format: DISK_GROUP/EBILL_TNS/datafile, for example: L_DB_EDX_DATA_TB_FILE_LOC=+DATA/ebill/oltp/datafile.
9. Run the modified Ant script, using the install-existing option. Use either of the following procedures:
   • Creating the Oracle Self-Service E-Billing Database Using Ant (Single Node)
   • Creating the Oracle Self-Service E-Billing Database Using the Automated Ant Target
10. Follow the steps in Installing the ETL Module for Oracle Self-Service E-Billing.