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 from Version 6.0.4 to Version 6.1 >

Migrating Oracle Self-Service E-Billing Version 6.0.4 OLAP to Version 6.1

Follow these steps to migrate Oracle Self-Service E-Billing version 6.0.4 OLAP to version 6.1 for both UNIX and Windows.

This task is a step in Process of Migrating Oracle Self-Service E-Billing from Version 6.0.4 to Version 6.1.

To migrate Oracle Self-Service E-Billing version 6.0.4 OLAP to version 6.1

1. On UNIX, log in as the ORACLE user for migration activity.
2. Go to the following directory:
   • UNIX. EDX_HOME/db/oracle/olap/migration/ebilling6.0.4_to_6.1
   • Windows. EDX_HOME\db\oracle\olap\migration\ebilling6.0.4_to_6.1

     In the path, EDX_HOME is the location where Oracle Self-Service E-Billing is installed.

3. Open the migrate_olap_6.0.4_to_6.1.properties file, and set the correct value for each property in this file.

   Property	Value
   OLAP_USER	OLAP schema user name
   OLAP_PASSWD	OLAP schema password
   OLAP_SID	OLAP instance name
   OLTP_USER	OLTP schema user name
   OLTP_PASSWD	OLTP schema password
   OLTP_SID	OLTP instance name
   SYS_PASSWD	OLAP SYS user password
   L_DB_EDX_DATA_TB_FILE_LOC	Data tablespace file location, for example: /export/home/oracle/oradata
   GRP_MOVE_INDIR	The input directory path to use when moving ETL groups, for example: /export/home/oracle/testdata/GRPMV_INDATA
   GRP_MOVE_OUTDIR	The output directory path to use when moving ETL groups, for example: /export/home/oracle/testdata/GRPMV_OUTDATA

4. Save and close the migrate_olap_6.0.4_to_6.1.properties file.
5. Run the following command to start the migration:

   ant -f migrate_olap_6.0.4_to_6.1.xml

6. Select Option 1, Create New Staging Tablespaces for OLAP schema.
7. Select Option 2, Migrate OLAP Schema.
8. Select Option 3, Drop redundant object.
9. Select Option 4, Migrate OLAP data.

   BUILD SUCCESSFUL displays on the console screen if migration is successful.

10. Review all log files for possible errors.