Installation Guide for Oracle Self-Service E-Billing > Migrating to Oracle Self-Service E-Billing Version 6.2 > Process of Migrating Oracle Self-Service E-Billing Version 6.0 to Version 6.0.1 >

Migrating Oracle Self-Service E-Billing Version 6.0 OLAP to Version 6.0.1 OLAP (UNIX and Windows)

If you are migrating from Oracle Self-Service E-Billing version 6.0 to version 6.0.1 one UNIX or Windows, then follow these steps to migrate your OLAP database.

This task is a step in Process of Migrating Oracle Self-Service E-Billing Version 6.0 to Version 6.0.1.

To migrate your Oracle Self-Service E-Billing version 6.0 OLAP database to version 6.0.1

1. On UNIX, log in as the ORACLE user for migration activity.
2. Go to the following directory:
   • UNIX. EDX_HOME/db/ebilling/oracle/olap/migration/ebilling_6.0_to_6.0.1
   • Windows. EDX_HOME\db\ebilling\oracle\olap\migration\ebilling_6.0_to_6.0.1
3. Verify that the following files exist:
   • migrate_olap_6.0_to_6.0.1.sh
   • migrate_olap_6.0_to_6.0.1.sql
   • Create_Tables.sql
   • Load_Data.sql
   • Create_Procedure.sql
   • Create_Indexes.sql
   • Create_Constraints.sql
4. Create the database link (OLTP_LINK) in the OLAP schema. Log on to the OLAP instance as SYSDBA, and run the following command. In the command, OLAP_Schema is the name of the OLAP schema.

   GRANT CREATE DATABASE LINK TO OLAP_Schema;

5. Go to the following directory:
   • UNIX. EDX_HOME/eBilling/db/ebilling/oracle
   • Windows. EDX_HOME\eBilling\db\ebilling\oracle
6. Log on to the OLAP schema, using SQL*Plus, not as SYSDBA.
7. Run the following script at SQL prompt, providing the three input parameters:

   SQL> DROP DATABASE LINK OLTP_LINK;

   SQL>CREATE DATABASE LINK OLTP_LINK CONNECT TO OLTP_User IDENTIFIED BY OLTP_Password USING 'OLTP_TNS_Name';

   SQL>exit

   where:

   • OLTP_User is the name of the OLTP schema user.
   • OLTP_Password is the OLTP schema user's password.
   • OLTP_TNS_Name is the name of the OLTP instance.
8. (UNIX only) Perform the following steps:
   1. Run the following commands at the shell prompt:

   Bash$ chmod 777 migrate_olap_6.0_to_6.0.1.sh

   Bash$.<space>migrate_olap_6.0_to_6.0.1.sh

   2. Substitute the correct values for your environment where appropriate.

      Field	What to Enter
      OLAP Database SID	OLAP instance name
      OLAP Database Username	OLAP schema name
      OLAP Database Password	OLAP schema password
      OLAP SYS Password	Password of SYS

   3. If you are migrating on to an Oracle Database 11g database, then enter the following additional parameters.

      Field	What to Enter
      Mail server name	Mail server name
      Lower port	Lower port of the mail server
      Upper Port	Upper port of the mail server

   4. Check db_oltp_migrate_6.0_6.0.1.log, and migrate_oltp_6.0_to_6.0.1.log files for errors.
9. (Windows only) Go to the EDX_HOME\db\ebilling\oracle\olap\migration\Ebilling_6.0_to_6.0.1 directory, and perform the following steps:
   1. Verify that the migrate_olap_6.0_to_6.0.1.sql file exists.
   2. Copy EDX_RPT_ETL.sql from the EDX_HOME\db\oracle\olap\migration\Ebilling_6.0_to_6.0.1 directory to the EDX_HOME\db\oracle\olap\etl\packages directory.
   3. Run the migration script as follows:

   C:\set ORACLE_SID=olap

   C:\sqlplus olap/olap

   SQL> @ migrate_olap_6.0_to_6.0.1.sql

   SQL> exit;

   4. Check the migrate_olap_6.0_to_6.0.1.log file for errors.
   5. If you are migrating to Oracle Database 11g, then run the acl.sql script, specifying the input values appropriate for your implementation:

   CD EDX_HOME\db\ebilling\oracle\olap\etl\packages

   c:\set ORACLE_SID=olap

   c:\Sqlplus olap/olap

   SQL>acl.sql Mail_Servername Lower_port_of_mail_server Upper_port_of_mail_server

   SQL>exit

   where:

   • EDX_HOME is the directory where you installed Oracle Self-Service E-Billing.
   • Mail_servername is the name of your mail server.
   • Lower_port_of_mail_server is the number of the lower port on your mail server.
   • Upper_port_of_mail_server is the number of the upper port on your mail server.
   6. Check the acl.log file for errors. Ignore errors ORA-31003 and ORA-06512.