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

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

Configuring Oracle Self-Service E-Billing on Oracle Exadata, using Oracle Real Application Clusters (RAC) requires that you manually create database instances with Database Configuration Assistant (DBCA). You must also modify the Ant script before creating the schemas.

You do not have to configure Oracle Services.

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 Exadata with Oracle RAC

1. Use the NETCA command to create the listener, using the default value for all options.
2. Create the database instance manually, using DBCA.

   NOTE:  DBCA automatically creates a TNS name for a new instance. You do not have to manually configure the tnsnames.ora file.

3. 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

4. Make the following modifications to the buildinstance.xml file, found in the EDX_HOME/db/oracle directory:
   • 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 "SetupDatabaseOLAP"->replace->replacefilter, remove "${EBILL_SID}/${OLAP_USER}/data" from the following code, and remove the same code for all tokens with _LOC at the end of the name:

   token="$L_DB_EDX_DATA_TB_FILE_LOC"

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

   • In the target "SetupDatabaseOLTP "->replace->replacefilter, remove "${EBILL_SID}/${OLTP_USER}/data" in the following code, and remove the same code for all tokens with _LOC at the end of the name:

   token="$L_DB_EDX_DATA_TB_FILE_LOC"

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

   token="$L_DB_APP_DATA_TB_FILE_LOC"

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

   token="$L_DB_EDX_INDX_TB_FILE_LOC"

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

   token="$L_DB_APP_INDX_TB_FILE_LOC"

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

   token="$L_DB_LOAD_DATA_TB_FILE_LOC"

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

   token="$L_DB_LOAD_INDX_TB_FILE_LOC"

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

   token="$L_DB_FS_DATA_TB_FILE_LOC"

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

   token="$L_DB_FS_INDX_TB_FILE_LOC"

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

   token="$L_DB_STG_DATA_TB_FILE_LOC"

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

   token="$L_DB_STG_INDX_TB_FILE_LOC"

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

   token="$LARGE_DB_EDX_DATA_TB_FILE_LOC"

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

   token="$LARGE_DB_EDX_INDX_TB_FILE_LOC"

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

   token="$MEDIUM_DB_EDX_DATA_TB_FILE_LOC"

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

   token="$MEDIUM_DB_EDX_INDX_TB_FILE_LOC"

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

5. Make the following modifications to the Ant script property files:
   • Modifications to OLAP Properties. In the ebilling_olap.properties file, for the EBILL_SID, set the SID on your software database server, such as EBILL_SID=ebill1. Set all TB_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
   • Modifications to OLTP Properties. In the ebilling_oltp.properties file, for the EBILL_SID, set the SID on your software database server, such as EBILL_SID=ebill1. Set all TB_FILE_LOC properties to this format: DISK_GROUP/EBILL_TNS/datafile, for example: L_DB_EDX_DATA_TB_FILE_LOC=+DATA/ebill/oltp/datafile.
6. 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
7. Follow the procedures in Installing the ETL Module for Oracle Self-Service E-Billing.