1. Installation Guide
  2. Upgrading ASAP

11 Upgrading ASAP

This chapter describes how to upgrade your existing Oracle Communications ASAP system to ASAP. It also includes information about new features, any impact that these new features have with respect to the operation of ASAP, and instructions on how to recover from a failed upgrade.

In this chapter, the ASAP release running on your production or development system is called the old release. The release you are upgrading to is called the new release.

About Upgrading ASAP

Upgrading to ASAP 7.4.1 consists of the following process:

  • Planning the upgrade

  • Implementing and testing the upgrade on a development test system

  • Preparing to upgrade a production system

  • Implementing and testing the upgrade on the production system

The upgrade process includes these tasks:

  • Updating the Oracle database and client

  • Updating the WebLogic Server and domain

  • Updating the ASAP software

  • Implement new features

For current patch information, see ASAP Compatibility Matrix. For current release information, see "ASAP System Requirements."

Supported Upgrade Paths

You can directly upgrade to ASAP 7.4.1 from the ASAP 7.4 or ASAP 7.3 release.

Planning Your Upgrade

To plan your upgrade, review the following tasks:

Identifying Your Upgrade Team

Your upgrade team should include the following team members:

  • A database administrator to manage the database upgrade and tune the database

  • A system integrator to handle new and existing ASAP customizations

  • A system administrator to manage the WebLogic Server and ASAP software upgrade

  • A UNIX administrator to manage accounts, network setup, and IP configurations

Identifying Who Is Affected by the Upgrade

You should identify who might be affected by the upgrade. For example:

  • You might need to give your customer service representatives (CSRs) who send work orders to ASAP advanced notice of any system downtime.

  • Tell your system administrators in advance about any changes to the system architecture (for example, Oracle database, client, or WebLogic Server upgrades).

  • Train CSR, cartridge developers, or system integrators on any new ASAP functionality that the upgrade may provide that would have an impact on their role.

  • Notify Oracle so that Oracle can help you anticipate and avoid problems. Technical support might have additional information about upgrading ASAP or information specific to your implementation.

Determining the Impact of New Features

You might need to make changes to your current system to accommodate additional or modified functionality in the new ASAP release. For example, if the release provides new security functionality, additional system configuration steps may be required.

For more information, see "Upgrade Impacts from ASAP 7.3.0.x or ASAP 7.4.0.x to ASAP 7.4.1."

Estimating How Long the Upgrade Will Take

This is an important consideration because work order processing might be suspended as a result of upgrading ASAP.

The best way to determine how long the database upgrade will take is to run the upgrade on a test system that contains a duplicate of the data in your production system (see "Creating Test Environments").

In general, it takes longer to upgrade large databases with large tables.

Maintaining Access to Services While Upgrading

While upgrading ASAP, you must shutdown ASAP and the ASAP WebLogic Server domain. Do not start the upgrade procedure until the status for all work orders indicates Completed and no work order status indicates in Loading, Initial, or in progress.

To minimize service outage while you upgrade, perform the upgrade during off-peak hours.

Creating Test Environments

To test the upgrade process, create a test environment. Use this environment to do the following:

  • Test the upgrade process and its results.

  • Compare the default behavior of the old and new ASAP releases.

  • Determine what customizations you made in the old ASAP release. Any customized ASAP clients and servers (SRP or NEP) or application that provides a programmatic integration with ASAP (using of the APIs described in the Developer's Reference Guide) should be identified.

For more information on creating a test environment from an existing ASAP environment, see "Creating a Test Environment from an Existing Environment."

Testing Your Upgraded System

When testing your upgraded ASAP system, verify that:

  • The database tables are installed.

  • The data in database tables is correct.

  • All IP addresses and ports are correct.

  • The WebLogic Server starts.

  • The SARM starts.

  • The NEPs start.

  • Users and user permissions are correct.

  • Cartridges are imported correctly.

  • No changes need to be made to existing cartridges.

  • No changes need to be made to the SRT.

  • Work orders are being processed correctly.

  • NEs are properly provisioned.

Creating a Test Environment from an Existing Environment

When you create a new Oracle Communications ASAP environment, dynamic ASAP data is created automatically. However, if you want to create a new environment that is identical to an existing environment, you must copy the data from the existing ASAP static tables to the new environment.

You may want to create additional identical environments for comparison testing.

Copying Static Data

If you want to move your static data from one database to another, you must first save the data in a flat file and then load the data into the new database. If the data used for the static tables is already stored within flat files, then simply load the data into the tables. All the static data tables are listed by component following these procedures.

To save tables to files (Oracle):

The ora_dump_sql script copies the table data to a file named TABLE NAME.sql, where TABLE NAME is the name of the table in uppercase characters. If there is more than one table, the script creates a separate file for each one.

  1. In a UNIX operating system, type the command line:

    ora_dump_sql [-d|-n|-t] user ID/password [table name]

    where [-d|-n|-t] are options that apply to reinserting the data as follows:

    • d – Deletes and replaces with new rows

    • t – Truncates table first

    • n – Inserts new rows, no deletions

    user ID and password are your user ID and password for the appropriate component

    [table name] is the name of the static table. If you do not specify a table, the script takes all tables for the user and copies them to separate files.

To load data into tables:

  1. In a UNIX, type the command line:

    sqlplus user_name/password filename

    where:

  • user_name and password are your user name and password for the appropriate component

  • filename is the name of the file where the static data is stored

Control Schema Static Data tables

  • tbl_alarm_center

  • tbl_appl_proc

  • tbl_classA_secu

  • tbl_classB_secu

  • tbl_code_list

  • tbl_component

  • tbl_db_threshold

  • tbl_event_type

  • tbl_fs_threshold

  • tbl_name_value_pair

  • tbl_system_alarm

  • tbl_unid

Service Activation Request Manager Schema Static Provisioning Translation Tables

  • tbl_asdl_config

  • tbl_asdl_parm

  • tbl_csdl_asdl

  • tbl_csdl_config

  • tbl_nep_asdl_prog

  • tbl_nep_jprogram

  • tbl_nep_program

  • tbl_program_source

Service Activation Request Manager Schema Static NE Configuration Tables

  • tbl_clii_route

  • tbl_comm_param

  • tbl_cp_mux

  • tbl_err_threshold

  • tbl_host_clii

  • tbl_ne_config

  • tbl_ne_event

  • tbl_ne_monitor

  • tbl_nep

  • tbl_nep_mux

  • tbl_nep_rte_asdl_nxx

  • tbl_q3_agent_name

  • tbl_resource_pool

  • tbl_user_err_threshold

Upgrade Impacts from ASAP 7.3.0.x or ASAP 7.4.0.x to ASAP 7.4.1

This section explains any important system changes introduced by an upgrade.

New features and new functionality are described in the ASAP Release Notes.

Support for Oracle Fusion Middleware 14c

ASAP 7.4.1 supports Oracle WebLogic Server 14c. To upgrade your WebLogic Server, you must also upgrade your JDK to the version specified in ASAP Compatibility Matrix.

Support Oracle Database Server 19c

ASAP 7.4.1 supports Oracle Database Server 19c. You need to upgrade Oracle Database Server to the version specified in ASAP Compatibility Matrix.

Support for Oracle Database Client 19c

ASAP 7.4.1 supports Oracle Database Client 19c. You need to install only one version of the client. See ASAP Compatibility Matrix for more information.

Schema Changes

There are no schema changes for various possible upgrades between ASAP 7.3 and ASAP 7.4.

Upgrading from ASAP 7.3.0.x or ASAP 7.4.0.x to ASAP 7.4.1

Table 11-1 describes the upgrade methods for ASAP software component upgrade methods.

Table 11-1 ASAP Software Component Upgrade Methods

Software Upgrade Method Description

Oracle database

In-place or out-of-place

(during the database installation, using dbua after installing the database, or using the expdp and impdp utilities)

You can either upgrade your existing ASAP database when you install the new version of the database software, or run Oracle_home/bin/dbua after you have installed the new database software. You can also create a new database and use the expdp or impdp utilities to import the old database into the new one.

You may perform an in-place upgrade (into the same Oracle_home) or an out-of-place upgrade (into a separate Oracle_home). You may also upgrade your database from a single instance Oracle Database to an Oracle RAC database. Refer to the Oracle Database Upgrade Guide for recommendations and procedures.

In either case, Oracle recommends that you back up your database before the upgrade. For database backup and restore procedure, please refer to "Creating a Backup of the ASAP Schemas" and "Rolling Back the ASAP Database."

Oracle client

New installation

Install a new version of the Oracle client when you upgrade your database. Download and install the software as described in "Downloading and Installing the Oracle Client Software."

Oracle WebLogic Server

In-place

(using reconfig.sh script)

Locate the Oracle WebLogic Server software distribution file on the Oracle software delivery website. The WebLogic Server distribution file is located with the ASAP software components.

Also download and install the version of Java for the operating system you are using for your WebLogic Server software. See ASAP Compatibility Matrix for Java version requirements for your platform.

Run Middleware_home/oracle_common/common/bin/ reconfig.sh to activate the WebLogic Server Reconfiguration Wizard.

ASAP software

In-place

(using the ASAP installer file from the old installation)

Run the ASAP installer after you have upgraded all other ASAP software components. Run the RPM installer to upgrade ASAP files. Then run the upgradeASAP script to configure ASAP to latest verison. Download the ASAP installation files as described in "Downloading the ASAP Installation Files."

Caution:

Before you start the upgrade procedure, you must backup your WebLogic Server domain, ASAP, and Oracle database (see "Creating a Backup of ASAP, WebLogic Domain, and ASAP Schemas"). The upgrade process for these software components is in-place, meaning the upgrades are applied to the existing software. If the upgrade fails, you must use these backups to roll back your upgrades (see "About Rolling Back ASAP").

To upgrade from ASAP 7.3.0.x or 7.4.0.x to ASAP 7.4.1:

  1. Stop all the ASAP servers except WebLogic server.

  2. Backup ASAP Directory.

  3. Download the ASAP 7.4.1 RPM Installer. For more information, see Downloading the ASAP Installation Files

  4. Exit the current ASAP kernel.

  5. Open new kernel and run the following command to upgrade the installed RPM package: 

    sudo rpm -U --prefix ASAP_home asap-installer-7.4.1.0.0-Bxxx.x86_64.rpm

    ASAP_home is the existing ASAP installation directory path where the current version is installed.

  6. If you are upgrading from ASAP 7.3.0, do the following:

    1. Go to the ASAP directory.
    2. Source Environment_Profile.
    3. Export TNS_ADMIN.
    4. Go to the Scripts directory.
    5. Run the following script:
      asap741.wl.resource.update.sh
    6. Exit from the kernel.
    7. Start a new kernel and restart WebLogic server.

  7. To set the environment variables, run the following commands:

    export JAVA_HOME_ASAP=Java_17_path
export TNS_ADMIN=TNS_path

  8. Rename and update the sampleUpgradeConfiguration.properties file located at ASAP_home/config to provide the following details:

    Table 11-2 sampleUpgradeConfiguration.properties File

    Name Description Required
    ORACLE_HOME Specifies the name of the base directory of the Oracle database client program. The ASAP installation generates an ORACLE_HOME UNIX environment variable based on the directory name. The default value is Null. Yes
    ANT_HOME Specifies the path to ant program. Yes
    WL_HOME Specifies the path to the WebLogic installation directory. Yes
    WLS_ADMIN_PORT

    Specifies NON-SSL Port if WLS_SSL_ENABLED is false.

    Specifies SSL Port if WLS_SSL_ENABLED is true.

    		 Yes
    WLS_SERVER

    Specifies the Oracle WebLogic server. The default value is AdminServer.

    		Yes
    WLS_SSL_ENABLED

    Set to true if SSL is enable. The default value is false.

    		No
    KEYSTORE_FILE

    Specifies the path of the SSL KeyStore file.

    		 Yes, if SSL is enabled
    GRPC_SSL_ENABLED
    Specifies if SSL is enabled for GRPC. The valid values are:

    • 1 - Enabled

    • 0 - Disabled

    		 No
    GRPC_AUTH_ENABLED
    Specifies if the authentication is enabled for GRPC. The valid values are:

    • 1 - Enabled

    • 0 - Disabled

    		 No
    SSL_IDENTITY_PKCS12_LOCATION

    Specifies the absolute path of SSL identity certificate in the pkcs12 format.

    		Yes if GRPC_SSL_ENABLED is enabled
    SSL_TRUST_PKCS12_LOCATION

    Specifies the absolute path of SSL trust certificate in the pkcs12 format.

    		Yes if GRPC_SSL_ENABLED is enabled

  9. Run the upgrade script using the following commands:

    cd scripts
upgradeASAP -properties ../config/sampleUpgradeConfiguration.properties
cd..
source Environment_profile
  10. Uninstall the previous versions of NORTEL_DMS_POTS.sar (if present in the earlier versions of ASAP) and reinstall the NORTEL_DMS_POTS.sar cartridge as the state table based cartridge is changed to Java cartridge in ASAP 7.4.1. Use the following commands to uninstall the state table based cartridge and reinstall the Java based cartridge NORTEL_DMS_POTS.sar:
    asapd -start -d -host <DAEMON_HOST> -port <DAEMON_PORT>
uninstallCartridge $ASAP_BASE/activationModels/Nortel_DMS_POTS.sar
installCartridge $ASAP_BASE/activationModels/Nortel_DMS_POTS.sar
asapd -stop -d -url <DAEMON_HOST>:<DAEMON_PORT>

    Note:

    ASAP 7.4.1 does not support state table based cartridges and these cartridges must to be uninstalled if present after you upgrade to ASAP 7.4.1.
  11. Start ASAP servers.

Migrating Order Data from ASAP 7.3.0.x or 7.4.0.x to ASAP 7.4.1

To migrate order data from ASAP 7.4.0.x to ASAP 7.4.1:

  1. Install ASAP 7.4.1 For more information, see "Installing ASAP".

    Note:

    ASAP installation should have the same ENV_ID, database users credentials, default users credentials, port numbers, and cartridges deployed in the 7.3 deployment.

    The values of ENV_ID and port numbers are present in the ASAP installation directory.

  2. Use the expdp utility to export ASAP 7.3 database (12c) schemas. For more information, see "Creating a Backup of the ASAP Schemas". Oracle database server provides the impdp and expdp utilities to import and export database schemas.

  3. Use the following commands to drop the ASAP users from 19c database: 

    drop user admenvid cascade; 
drop user sarmenvid cascade; 
drop user ctrlenvid cascade; 
drop user nepenvid cascade; 
drop user srpenvid cascade;

    Where envid is the environment ID for your ASAP instance.

    For more information see "Rolling Back the ASAP Database".

  4. Use the impdp utility to import 12c database schemas into 19c database. For more information see "Rolling Back the ASAP Database".

  5. Update the following tables:

    1. Update hostname in tbl_listeners of the CTRL database by running the following command: 
      update tbl_listeners set HOST_NAME='asaphost';

      where asaphost is the name of the host in which ASAP is deployed.

    2. Update the hostname in the TBL_ASAP_SRP table of the SARM by running the following command:
      update TBL_ASAP_SRP set HOST_NAME='asaphost';
    3. Update the SRP_HOST_NAME field in the TBL_ASAP_SRP table by running the following command: 
      update TBL_ASAP_SRP set SRP_HOST_NAME='asaphost';
  6. Restart ASAP.

Upgrading ASAP from a Single Database to an Oracle RAC Database

The following sections describe additional upgrade procedures required if you are upgrading from a single Oracle database instance to an Oracle RAC database instance.

Upgrading the Oracle Database, WebLogic Server, and ASAP Servers

To upgrade the Oracle Database and ASAP Servers:

  1. Upgrade the single instance database (see Table 11-1).

  2. Upgrade ASAP as described in "Upgrading from ASAP 7.3.0.x or ASAP 7.4.0.x to ASAP 7.4.1."

  3. Stop ASAP.

  4. Migrate the upgraded single instance database to an Oracle RAC database. For instructions, see the Oracle Database documentation.

Creating WebLogic Generic and Multi Data Sources to the Oracle RAC Database

After upgrading ASAP and migrating the Oracle Database content to an Oracle RAC database, you must delete the original WebLogic data sources that connected to the single database instance and create new WebLogic data sources as listed in Table 11-3. Each Oracle RAC database requires a single generic data source that are both members of a common multi data source.

Table 11-3 ASAP Data Source Migration

Original Data Source Name and JNDI Name New Data Source Name and JNDI Name

envid.ADMDataSource

System.envid.ApplicationType.ServiceActivation. Application.1-0;7-3;ASAP.Comp.ADMDataSource

Generic data sources:

  • envid.ADMDataSource-1

    System.envid.ApplicationType.ServiceActivation.Application.1-0;7-4;ASAP.Comp.ADMDataSource-1

  • envid.ADMDataSource-2

    System.envid.ApplicationType.ServiceActivation.Application.1-0;7-4;ASAP.Comp.ADMDataSource-2

Multi Data Source:

  • envid.ADMDataSourcenew

  • System.envid.ApplicationType.ServiceActivation.Application.1-0;7-4;ASAP.Comp.ADMDataSource

envid.CTRLDataSource

System.envid.ApplicationType.ServiceActivation. Application.1-0;7-3;ASAP.Comp.CTRLDataSource

Generic data sources:

  • envid.CTRLDataSource-1

  • System.envid.ApplicationType.ServiceActivation. Application.1-0;7-4;ASAP.Comp.CTRLDataSource-2

Multi Data Source:

  • envid.CTRLDataSource

  • System.envid.ApplicationType.ServiceActivation. Application.1-0;7-4;ASAP.Comp.CTRLDataSource

envid.NEPDataSource

System.envid.ApplicationType.ServiceActivation. Application.1-0;7-3;ASAP.Comp.NEPDataSource

Generic data sources:

  • envid.NEPDataSource-1

    System.envid.ApplicationType.ServiceActivation. Application.1-0;7-4;ASAP.Comp.NEPDataSource-1

  • envid.NEPDataSource-2

    System.envid.ApplicationType.ServiceActivation. Application.1-0;7-4;ASAP.Comp.NEPDataSource-2

Multi Data Source:

  • envid.NEPDataSource

  • System.envid.ApplicationType.ServiceActivation. Application.1-0;7-4;ASAP.Comp.NEPDataSource

envid.SARMDataSource

System.envid.ApplicationType.ServiceActivation. Application.1-0;7-3;ASAP.Comp.SARMDataSource

Generic data sources:

  • envid.SARMDataSource-1

    System.envid.ApplicationType.ServiceActivation. Application.1-0;7-4;ASAP.Comp.SARMDataSource-1

  • envid.SARMDataSource-2

    System.envid.ApplicationType.ServiceActivation. Application.1-0;7-4;ASAP.Comp.SARMDataSource-2

Multi data source:

  • envid.SARMDataSource

  • System.envid.ApplicationType.ServiceActivation. Application.1-0;7-4;ASAP.Comp.SARMDataSource

envid.SRPDataSource

System.envid.ApplicationType.ServiceActivation. Application.1-0;7-3;ASAP.Comp.SRPDataSource

Generic data sources:

  • envid.SRPDataSource-1

    System.envid.ApplicationType.ServiceActivation. Application.1-0;7-4;ASAP.Comp.SRPDataSource-1

  • envid.SRPDataSource-2

    System.envid.ApplicationType.ServiceActivation. Application.1-0;7-4;ASAP.Comp.SRPDataSource-2

Multi data source:

  • envid.SRPDataSource

  • System.envid.ApplicationType.ServiceActivation. Application.1-0;7-4;ASAP.Comp.SRPDataSource

Table 11-4 Additional Settings for Generic Data Sources

Field Tab ADM Data Source Value SARM/NEP/SRP/CTRL Data Source Value

Row Prefetch Enabled

General

Enabled

Enabled

Row Prefetch Size

General

200

200

Driver Class Name

Connection Pool

oracle.jdbc.driver.OracleDriver

oracle.jdbc.driver.OracleDriver

Initial Capacity

Connection Pool

1

3

Maximum Capacity

Connection Pool

5

25

Capacity Increment

Connection Pool

1

3

Test Connections On Reserve

Connection Pool

Enabled

Enabled

Test Frequency

Connection Pool

0

0

Shrink Frequency

Connection Pool

0

0

Remove Infected Connections Enabled

Connection Pool

Disabled

Disabled

To create new generic and multi data sources to an Oracle RAC database:

  1. Log in to the WebLogic Server.

    The WebLogic Server Administration Console appears.

  2. Click Deployments.

  3. Select all Deployments

  4. Click Stop.

  5. Click Force Stop Now.

  6. Expand Services.

  7. Click Database Sources.

  8. Select all the original data sources listed in Table 11-3 except for the Admin data source. Do not select the RPC data source.

  9. Click Delete.

  10. You must create a generic data source for each Oracle RAC database. Click New.

  11. Click Generic Data Source.

    The Create a New JDBC Data Source screen appears.

  12. In the Name field, add the first new data source name listed in Table 11-3. For example, envid.ADMDataSource-1.

  13. In the JNDI Name field, add the first new JNDI name listed in Table 11-3. For example, System.envid.ApplicationType.ServiceActivation.Application.1-0;7-3;ASAP.Comp.ADMDataSource-1.

  14. From the Database Type list, select Oracle.

  15. Click Next.

  16. From Database Drive list, select Oracle Driver for RAC Service-Instance connections; Version 10: and later.

  17. Click Next.

  18. Click Next.

  19. Do the following:

    1. In the Service Name field, enter the service name of the Oracle RAC database you want this data source to connect to.

    2. In the Database Name field, enter the database name for the Oracle RAC database you want this data source to connect to.

    3. In the Hostname field, enter the host name for the Oracle RAC database you want this data source to connect to.

    4. In the Port field, enter the port number for the Oracle RAC database you want this data source to connect to.

    5. Enter the Database User Name for the Schema you want to create a data source for.

    6. Enter the Password for the ASAP schema you want to create a data source for.

    7. Confirm the Password for the ASAP schema you want to create a data source for.

  20. Click Next.

  21. Edit the URL field as follows: 

    jdbc:oracle:thin:@//ip_address:port/service_name

    where ip_address, port, and service_name are the IP address, port number, and service name for an Oracle RAC database.

  22. Click Test Configuration.

  23. Do the following:

    • If the test succeeds, click Next.

    • If the test did not succeed, review the steps in this procedure and check for configuration errors.

  24. In the Select Targets section, select Admin if ASAP is installed in a single Admin server or Managed Server if ASAP is installed with an Admin server and a managed server.

  25. Click Finish.

  26. Select the created data source.

  27. On the Transaction tab, deselect the Supports Global Transactions check box.

  28. Click Save.

  29. Repeat steps 6 to 28 for the second new data source name listed in Table 11-3. For example, envid.ADMDataSource-2 System.envid.ApplicationType.ServiceActivation.Application.1-0;7-3;ASAP.Comp.ADMDataSource-2.

  30. You must create a multi data source for Oracle RAC that references these two data sources. Click New.

  31. Click Multi Data Source.

  32. In the Name field, enter the multi data source name listed in Table 11-3.

  33. In the JNDI Name field, enter the multi data source JNDI name listed in Table 11-3.

  34. From the Algorithm Type list, select Failover.

  35. Click Next.

  36. In the Select Targets section, select Admin if ASAP is installed in a single Admin server or Managed Server if ASAP is installed with an Admin server and a managed server. The target server should be the same one used for the original data sources.

  37. Click Next.

  38. Click Next.

  39. From the Data Source Available section, select the two generic data sources that correspond to the multi data source node you are creating.

  40. Click the right arrow to choose them.

  41. Click Finish.

  42. Repeat steps 6 to 41 for all remaining generic and multi data sources listed in Table 11-3.

  43. Update the newly created generic data source values using the values shown in Table 11-4.

  44. Click Services.

  45. Click Persistent Stores.

  46. Click envid.JMSJDBCStore.

  47. In the Target list, do one of the following:

    • Select AdminServer if ASAP is installed on a single administration server.

    • Select ManagedServer if ASAP is installed on an administration server with one or more managed servers.

  48. In the Data Source field, select the new multi data source for the Admin server. This step only applies to the Admin server. All other servers used JDBC. The target server should be the same one used for the original data sources.

  49. Click Save.

  50. Click Database Sources.

  51. Select the old Admin data source.

  52. Click Delete.

  53. Restart the WebLogic server.

  54. Log in to the WebLogic server.

    The WebLogic Server Administration Console appears.

  55. Click Deployments.

  56. Select all Deployments

  57. Click Start.

  58. Select Service All Requests.

Configuring the ASAP Environment for the Oracle RAC Database

To configure the ASAP environment for the Oracle RAC database:

  1. From the ASAP environment, source the ASAP_home/Environment_Profile.

  2. Open the Environment_Profile with a text editor.

  3. Search for DSQUERY.

  4. Change the value for DSQUERY to the new Oracle RAC database service name.

  5. Save the Environment_Profile.

  6. Open ASAP_home/ASAP.properties with a text editor.

  7. Change the values for DB_CONNECT to the new Oracle RAC database tnsnames.ora DB_CONNECT values.

  8. Add the RACDB_CONNECT_STR parameter and set it to the Oracle RAC database connection string. This connection string repeats the IP addresses and port numbers for the Oracle RAC databases listed in the tnsnames.ora file in a different format. For example: 

    RACDB_CONNECT_STR=host1:port:servicename,host2:port:servicename

    Where HOST1 and HOST2 are the name or IP address of your Oracle RAC databases, port is the port number for the Oracle RAC databases, and servicename is the service name for the Oracle RAC databases.

  9. Restart ASAP.

Upgrading Stored Procedures for ASAP Servers

To upgrade ASAP server stored procedures:

  1. Change to the $ASAP_BASE/isql directory for the new version of ASAP: 

    cd $ASAP_BASE/isql

  2. Run the following commands to upgrade the stored procedures:

    sqlplus $SARM_USER/sarm_db_password < sarm_procs.sql
sqlplus $SARM_USER/sarm_db_password < oca_sarm_procs.sql
sqlplus $CTRL_USER/control_db_password < control_procs.sql
sqlplus $ADM_USER/admin_db_password < admin_procs.sql
sqlplus $ADM_USER/admin_db_password < aims_procs.sql
sqlplus $ADM_USER/admin_db_password < oca_admin_procs.sql
sqlplus $SRP_USER/srp_db_password < srp_emul_procs.sql
sqlplus $NEP_USER/nep_db_password < asc_nep_procs.sql

  3. Check the upgraded database object status as follows: 

    $ASAP_BASE/db_migration/oracle_from_asap_ver_to_asap_versionL
/scripts/check_db_obj_status.ksh

    The status of all database objects should be VALID. For example:

    $ASAP_BASE/db_migration/oracle_from_asap_ver_to_asap_versionL
/scripts/check_db_obj_status.ksh -U $SRP_USER -P srp_db_password

About Rolling Back ASAP

You can roll back to a previous version of ASAP by using the backup files that you created after you installed ASAP or before you started an upgrade (see "Creating a Backup of ASAP, WebLogic Domain, and ASAP Schemas").

If you are restoring a backup created on one machine to a different machine, ensure the following:

  • The new machine name must be identical to the old machine name.

  • The new user accounts and permissions should be identical to the old user accounts and permissions.

  • The IP addresses for the new box must be updated in the ASAP environment, WebLogic Server domain, and ASAP database servers.

Ensure that you have installed the zip and unzip utility before you start the roll back procedures for the ASAP environment and WebLogic Server Domain.

The Oracle Database Server provides the impdp and expdp utilities to import and export database schemas.

Rolling Back the ASAP Environment

To roll back the ASAP environment, use the following procedure.

  1. From the directory that contains the old ASAP_home folder, use the unzip utility to unzip an ASAP backup file. 

    unzip ASAP741_BACKUP.zip

Rolling Back the WebLogic Server Domain

To roll back the WebLogic Server domain, use the following procedure:

  1. From the directory that contains the old domain_home folder, use the unzip utility to unzip a WebLogic Server domain backup file. 

    unzip WLDOMAIN_BACKUP.zip

Rolling Back the ASAP Database

To roll back the ASAP Database, use the following procedure:

  1. Source the ASAP Environment_Profile in the ASAP_home folder (where ASAP_home is the location of your ASAP server installation directory). 

    . ./Environment_Profile

  2. Drop all database users, if you are importing your database back into an environment where those users were already created.

    1. Log in to your database using /as sysdba for the user-name.

    2. Enter the following commands to drop the ASAP users:

      drop user admenvid cascade;
drop user sarmenvid cascade;
drop user ctrlenvid cascade;
drop user nepenvid cascade;
drop user srpenvid cascade;

      Where envid is the environment ID for your ASAP instance.

    3. Log out of your database. 

      exit

  3. Use the following command to restore the backup file for the Control, Admin, SARM, NEP, and SRP servers. Where password is the database system admin password and filename is the name that you gave your DMP file when you created the backup (see "Creating a Backup of the ASAP Schemas"). 

    impdp system/password SCHEMAS=$CTRL_USER,$SARM_USER,$ADM_USER,$NEP_USER,$SRP_USER DUMPFILE=filename.dmp