Installation Guide for Oracle Self-Service E-Billing > Migrating to Oracle Self-Service E-Billing Version 6.0.4 > Roadmap for Migrating Oracle Self-Service E-Billing 6.0.2 to 6.0.3 >

Migrating Oracle Self-Service E-Billing Version 6.0.2 OLTP to 6.0.3

Follow these steps to migrate Oracle Self-Service E-Billing 6.0.2 OLTP to 6.0.3 for both UNIX and Windows.

This task is a step in Roadmap for Migrating Oracle Self-Service E-Billing 6.0.2 to 6.0.3.

To migrate Oracle Self-Service E-Billing 6.0.2 OLTP to 6.0.3

1. The following directories are required for migrating OLTP database. Make sure they are accessible on the OLTP database server:
   • $EDX_HOME/xma (%EDX_HOME%\xma on Windows)
   • $EDX_HOME/keystore(%EDX_HOME%\keystore on Windows)
2. On UNIX, log in as the ORACLE user for migration activity. Go to the EDX_HOME/db/ebilling/oracle/oltp/migration/ebilling 6.0.2_to_6.0.3 directory (or the EDX_HOME\db\ebilling\oracle\oltp\migration\ebilling6.0.2_to_6.0.3 directory on Windows). In the path, EDX_HOME is the location where Oracle Self-Service E-Billing is installed.
3. Open the migrate_oltp_6.0.2_to_6.0.3.properties file, and set the correct value for each property in the file.

   Property	Value
   ORACLE_HOME	ORACLE HOME directory
   OLTP_USER	OLTP schema user name
   OLTP_PASSWD	OLTP schema password
   OLTP_SID	OLTP instance name
   OLTP_HOST	OLTP database host name or IP address
   LISTEN_PORT	OLTP database listen port
   EBILLING_EAR_DIR	Directory containing the ebilling-weblogic-10-6.0.3.ear file after packaging LGPL libraries

   NOTE:  Use a backslash (\) as the path separation character on Windows.

4. Save and close the migrate_oltp_6.0.2_to_6.0.3.properties file.
5. Set the Java environment variable (JRE 1.5 is required), where JDK150_11 is your JDK version. For example:
   • UNIX:

   export JAVA_HOME=/usr/local/bea10/jdk150_11

   export PATH=$JAVA_HOME/bin:$PATH

   • Windows:

   set JAVA_HOME=D:\bea\jdk150_11

   set PATH=%JAVA_HOME%\bin;%PATH%

6. Run following command to start migration:

   ant -f migrate_oltp_6.0.2_to_6.0.3.xml

7. Select Option 1, Migrate OLTP Database.

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

8. Review all log files for possible errors. If there were no errors, select Option 2, Post Migration Cleanup. You can ignore the following error (later in the migration process you compile the schema and validate the package):

   Errors for PROCEDURE PR_LOAD_LATEST_STATEMENT:

   LINE/COL ERROR

   -------- -----------------------------------------------------------------

   22/1 PL/SQL: SQL Statement ignored

   34/9 PL/SQL: ORA-00904: "ERSF"."MEDIA_TYPE": invalid identifier