Installation Guide for Oracle Self-Service E-Billing > Migrating to Oracle Self-Service E-Billing Version 6.2 from Other Products > Roadmap for Migrating the Oracle Communications Billing Manager Version 5.1.1 QF3 Database to Oracle Self-Service E-Billing Version 6.2 >

Migrating Oracle Communications Billing Manager Version 5.1.1 QF3 to Oracle Self-Service E-Billing Version 6.0.3

Follow these steps to migrate Oracle Communications Billing Manager version 5.1.1 QF3 to Oracle Self-Service E-Billing version 6.0.3 for both UNIX and Windows.

CAUTION:  You must complete the previous steps outlined in Roadmap for Migrating the Oracle Communications Billing Manager Version 5.1.1 QF3 Database to Oracle Self-Service E-Billing Version 6.2 before migrating Communications Billing Manager 5.1.1 to Oracle Self-Service E-Billing 6.0.3, or the migration will fail.

This task is a step in Roadmap for Migrating the Oracle Communications Billing Manager Version 5.1.1 QF3 Database to Oracle Self-Service E-Billing Version 6.2.

To migrate Oracle Communications Billing Manager version 5.1.1 QF3 to Oracle Self-Service E-Billing version 6.0.3

1. On UNIX, log in as the ORACLE user for migration activity.
2. Go to the following directory:
   • UNIX. EDX_HOME\db\ebilling\oracle\oltp\migration\cbm511qf3_to_603
   • Windows. EDX_HOME/db/ebilling/oracle/oltp/migration/cbm511qf3_to_603

     In the path, EDX_HOME is the location where Oracle Self-Service E-Billing is installed. You must run the migration process on the Oracle Self-Service E-Billing database server.

3. Open the migrate_cbm_to_ebilling603.properties file, and set the correct value for each property in the file.

   Property	Value
   migration_type	Migration type: B2B, B2C, or B2B&B2C
   cbmb2b_hostname	Host name of the Oracle Communications Billing Manager Business Edition database. Specify only if migration_type is B2B, or B2B and B2C.
   cbmb2b_db_port	Listener port of the Oracle Communications Billing Manager Business Edition database. Specify only if migration_type is B2B, or B2B and B2C.
   cbmb2b_sid	ORACLE_SID of the Oracle Communications Billing Manager Business Edition database. Specify only if migration_type is B2B, or B2B and B2C.
   cbmb2b_user	User name of the Oracle Communications Billing Manager Business Edition database. Specify only if migration_type is B2B, or B2B and B2C.
   cbmb2b_paswd	Password of the Oracle Communications Billing Manager Business Edition database. Specify only if migration_type is B2B, or B2B and B2C.
   cbmb2c_hostname	Host name of the Oracle Communications Billing Manager Consumer Edition database. Specify only if migration_type is B2B, or B2B and B2C.
   cbmb2c_db_port	Listener port of the Oracle Communications Billing Manager Consumer Edition database. Specify only if migration_type is B2B, or B2B and B2C.
   cbmb2c_sid	ORACLE_SID of the Oracle Communications Billing Manager Consumer Edition database. Specify only if migration_type is B2B, or B2B and B2C.
   cbmb2c_user	User name of the Oracle Communications Billing Manager Consumer Edition database. Specify only if migration_type is B2B, or B2B and B2C.
   cbmb2c_paswd	Password of the Oracle Communications Billing Manager Consumer Edition database. Specify only if migration_type is B2B, or B2B and B2C.
   ORACLE_HOME	Oracle home on the target (OLTP) database server.
   ebilling_oltp_tnsname	Oracle Self-Service E-Billing 6.0.3 OLTP database tnsname
   ebilling_oltp_user	Oracle Self-Service E-Billing 6.0.3 OLTP user
   ebilling_oltp_paswd	Oracle Self-Service E-Billing 6.0.3 OLTP password
   ebilling_oltp_sid	Oracle Self-Service E-Billing 6.0.3 OLTP ORACLE_SID
   ebilling_oltp_LISTEN_PORT	Oracle Self-Service E-Billing 6.0.3 OLTP listener port
   ebilling_oltp_hostname	Host name of the Oracle Self-Service E-Billing 6.0.3 OLTP database
   EBILLING_EAR_DIR	Directory that contains the ebilling-weblogic-10-6.0.3.ear file after packaging the LGPL libraries

4. Save and close migrate_cbm_to_ebilling603.properties file.
5. Set the Java environment variable (JRE 1.5 is required), as shown in the following example. In the variable, JDK150_11 is your JDK version.
   • UNIX. Run the following commands:

   export JAVA_HOME=/usr/local/bea10/jdk150_11

   export PATH=$JAVA_HOME/bin:$PATH

   • WINDOWS. Run the following commands:

   set JAVA_HOME=d:\bea\jdk150_11

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

6. Run the following command to start migration:

   ant

7. Select Option 1 to install the migration-related objects.
8. Choose the option appropriate for your product. To merge both the Oracle Communications Billing Manager Business and Consumer Editions into one database schema, complete both of the following steps:
   • Business Edition: Select Option 2 if you are migrating data for the Business Edition of Oracle Communications Billing Manager into Oracle Self-Service E-Billing 6.0.3. Then from the submenu for B2B data migration, select Option 1 to migrate user profile and payment data; select Option 2 to migrate hierarchy data. Select Option 3 to return to the Main Menu.
   • Consumer Edition: Select Option 3 if you are migrating data for the Consumer Edition of Oracle Communications Billing Manager into Oracle Self-Service E-Billing 6.0.3. Select Option 3 to return to the Main Menu.

     NOTE:  If you merge both Business and Consumer Editions into one schema, then the ant script checks for data conflicts; you must resolve any conflicts before continuing with the merge.

9. Select Option 4 to run the Java process and perform post-migration operations.
10. Review all log files for possible errors. If there were no errors, then select Option 5, Post Migration Cleanup.
11. After migrating to Oracle Self-Service E-Billing 6.0.3, you must create a new Command Center administrator user; the old user ID and password will not work.

    For details on creating a new administrator user in the Command Center, see Administration Guide for Oracle Self-Service E-Billing.