Upgrading Oracle Pedigree and Serialization Manager from 2.0.0.3.0 to 2.1.0.0.0

This chapter lists the steps for upgrading Oracle Pedigree and Serialization Manager (OPSM) from 2.0.0.3.0 to 2.1.0.0.0.

This chapter covers the following topics:

Pre-Upgrade Tasks

  1. Shutdown the admin server and the managed servers (for example, soa_server1 and pas_server1).

  2. Upgrade to Oracle Database 12c Release 1 (12.1.0.1.0) 64-bit Production Database, Enterprise Edition, if needed.

    Upgrading the database is NOT required for Oracle Pedigree and Serialization Manager Release 2.1.0.0.0.

    Important: When installing Oracle Database 12c Release 1, choose Advanced Install, then in the following screens, deselect the Create as Container database option and select the AL32UTF8 character set.

  3. Download and apply the latest patches from Release 2.0 from support.oracle.com:

    Patch Part Number/Patch Number Notes
    OPSM 2.0.0.0.0 20492590 Available on My Oracle Support (https://support.oracle.com/)
    OPSM 2.0.0.0.1 21153372 Available on My Oracle Support (https://support.oracle.com/)
    OPSM 2.0.0.0.2 21221172 Available on My Oracle Support (https://support.oracle.com/)
    OPSM 2.0.0.1.0 22084249 Available on My Oracle Support (https://support.oracle.com/)
    OPSM 2.0.0.2.0 22544779 Available on My Oracle Support (https://support.oracle.com/)
    OPSM 2.0.0.3.0 23632063 Available on My Oracle Support (https://support.oracle.com/)

  4. Set the following environment variables:

    • MW_HOME to your Middleware Home.

      For example, MW_HOME=/slot/ems2383/oracle/mwhome

    • MW_ORA_HOME to your SOA HOME.

      For example, MW_ORA_HOME=$MW_HOME/Oracle_SOA1

    • ORACLE_DB_HOME to your database home.

      For example, ORACLE_DB_HOME=/slot/app/product/db_home

    • Set the PATH variable to include $ORACLE_DB_HOME/bin.

      For example, export PATH=$ORACLE_DB_HOME/bin:$PATH

  5. Copy the pas.zip file to the location that you have set in your MW_ORA_HOME environment variable.

  6. Merge the applications, db, soa, and scripts directories from the extracted pas.zip within the existing pas folder. The atglite and odi directories must remain since the deployed libraries refer to the jars inside that directory. There are no changes to the files in adapters, atglite, odi, soa, and templates directories.

    Unzip the pas.zip file using the following command:

    unzip -o pas.zip

  7. Take a backup of the OPSM data. In particular, take a backup of any custom code in the package specification and body of the PAS_SERIAL_GEN and PAS_SERIAL_VAL database packages.

  8. Move the jar utility from your JDK home folder into the search path. This is needed because the install script uses the jar utility to extract the files and modify the connection parameters.

  9. If you are using a 12c Database please execute this command using the sys user before the upgrade:

    GRANT INHERIT PRIVILEGES ON USER SYS TO XDBPM;

  10. Backup the user_projects directory under the middleware home. This is needed because the upgrade script modifies the domain and if the upgrade fails for any reason, you will need this backup to restore the original domain.

  11. Populate the values in pas_install.properties to ensure that a description of every property is available before the property is referred to. The appropriate parameters are described in the comments of the pas_install.properties file. The pas_install.properties file is located in the MW_ORA_HOME/pas/scripts directory.

Upgrade Tasks

  1. Make sure that the admin server and the managed servers (for example, soa_server1 and pas_server1) are not running.

  2. Navigate to the PAS script directory.

    For example, cd MW_ORA_HOME/pas/scripts

  3. Execute the upgrade script to upgrade Oracle Pedigree and Serialization Manager.

    For Unix-based installs, use the "pasMasterUpgrade20To21.py" script. Run the installation script using the following command:

    $MW_ORA_HOME/common/bin/wlst.sh ./pasMasterUpgrade20To21.py

    Ensure that the terminal on which you are running the upgrade has sufficient scroll-back lines (for example, 5000) to capture all the output from the install activities. This enables you to review all of the upgrade activities later.

    Important: The upgrade python script will run database upgrade scripts. Please observe the console output and check if there are errors while running of database scripts and continue with the upgradation.

    During the upgrade, you are prompted to answer this question after each SQL script is executed: Are there any errors in script? y/n. If you answer no, the upgrade script continues and assumes there are no errors in the script execution so far. If you answer yes, the upgrade script quits and assumes there are errors in the script execution.

    In the case of script execution failure, after you have corrected the errors, comment the sql script files in the upgrade script which have already run successfully before re-running the upgrade script.

    Note: If you see errors similar to below while removing soa temporary files, these errors can be ignored and you may continue with the upgrade:

    rm: cannot unlink entry "C:/Oracle/MIDDLE~1/user_projects/domains/base_domain/servers/soa_server1/tmp/_WL_user/soa-infra/y2559h/war/WEB-INF/default/PasTransmitSerialsViaFileComposite!1.0_soa_7c78c21f-f0d9-453b-91d3-04fdaaa5dcd3/transmitserialsviafile_client_ep/TransmitSerialsViaFile.wsdl": The system cannot find the path specified.

    The upgrade script attempts to start the Admin Server. It tests in a loop if the server is up before it continues. If you installed your WebLogic Server in Production Mode, the Admin server requires a userid and password to start which the script does not set for security reasons. In this case, you must start a new terminal window to start the Admin Server. After the script detects the server has started, it will continue.

    After the Admin Server has been started, the upgrade script will prompt you to start up the managed servers (for example, soa_server1 and pas_server1). To do so, make sure the environment variables are set as described in the Pre-Upgrade Tasks section, then navigate to MW_HOME/user_projects/domains/base_domain/bin. Using separate terminal windows, startup the PAS and SOA managed servers. Keeping in mind your actual managed server names may be different, use the following commands as examples:

    For Unix-based installs:

    • sh startManagedWebLogic.sh soa_server1
    • sh startManagedWebLogic.sh pas_server1

    After the managed servers are started, press enter in the first terminal where the ./pasMasterUpgrade20To21.py script is run to continue processing the install script.

  4. The OPSM installation output is captured in the scroll buffer of the terminal on which you run the installation. Scroll through the buffer to check for errors. The following warnings, if seen, can be ignored:

    • WARNING: Failed to create ConnectionDBean for {http://xmlns.oracle.com/oracle/apps/fnd/applcore/flex/deployment/service/model/}FlexDeploymentService

    • WARNING: Failed to create ConnectionDBean for AtkHelpPortalService

  5. After the upgrade script has completed successfully, you must restart the Admin Server and managed servers (for example, soa_server1 and pas_server1) for changes made by the upgrade script to take effect.

Post Upgrade Tasks

Verify Servers are Running

Refer to the Post Installation Tasks section to verify that the servers are running.

Configure Security for the Application and Services

Refer to the Oracle Pedigree and Serialization Manager Security Guide for the new jobs, duties, application roles, and privileges introduced in 2.0.0.0.0.

Load Existing OPSM Templates into Oracle BI Publisher 11g

If you decide to use Oracle BI Publisher 11g, follow the instructions in the Installing Oracle Pedigree and Serialization Manager 2.0.0.0.0 chapter, Post Installation Tasks section, Load Existing OPSM Templates Into Oracle BI Publisher 11g.

Restore Back Up of Custom PLSQL Procedures

Restore the backup of the custom code in the PAS_SERIAL_GEN and PAS_SERIAL_VAL packages.

Re-Upgrade Tasks

In the event that an upgrade fails, follow the procedure below to perform a new upgrade. Keep in mind that your actual managed server names may differ from those used in the sample commands listed below.

  1. Make sure that the environment variables are set as described in Pre-Upgrade Tasks, and that you are in the DOMAIN_HOME (typically MW_HOME/user_projects/domains/base_domain).

  2. Stop the SOA Server.

    Go to DOMAIN_HOME/bin and issue the following command at the prompt:

    For Unix-based installs:

    sh stopManagedWebLogic.sh soa_server1 t3://<servername>:<adminport>

    For example:

    sh stopManagedWebLogic.sh soa_server1 t3://host.oracle.com:7001

  3. Stop the PAS Server.

    Go to DOMAIN_HOME/bin and issue the following command at the prompt:

    For Unix-based installs:

    sh stopManagedWebLogic.sh pas_server1 t3://<servername>:<adminport>

    For example:

    sh stopManagedWebLogic.sh pas_server1 t3://host.oracle.com:7001

  4. Stop the Admin Server.

    Go to DOMAIN_HOME/bin and issue the following command at the prompt:

    For Unix-based installs:

    sh stopWebLogic.sh

  5. Perform cleanup tasks:

    1. Clean up the MW_HOME/user_projects directory and restore from the backup taken before the initial installation.

    2. Delete the pas directory under MW_ORA_HOME.

    Use dbUpgrade = no in the properties file to prevent repeated upgrade of the database if the database upgrade scripts were already successfully executed.

  6. Perform step 4 from Pre-Upgrade Tasks.

  7. Perform step 6 from Pre-Upgrade Tasks.

  8. Perform step 10 from Pre-Upgrade Tasks.

  9. Perform step 11 from Pre-Upgrade Tasks.

  10. Perform a new upgrade.

    Follow the steps for a new upgrade starting with step 1 under the section Upgrade Tasks.