Zero Downtime Upgrade Guide for Oracle

10.5 HotFix 2

Back Next

Upgrade Steps Controlled from the Active Environment

The active environment must be prepared after you complete the upgrade steps on the passive environment. Run the steps from the active environment.

During the upgrade, you must drop the source schema, re-create it from the target schema, and then import the database dump file. Do not attempt to bypass this process by applying a change list, because the schemas must be exactly the same in both databases for the replication to work. To avoid making inadvertent changes, enable Production Mode on the source and target databases. Log in to the Hub Console, select the Databases tool, select the database, and enable Production Mode. In future, if you need to apply a change list to the target database, you can disable Production Mode and apply the change list.

Before you begin, open the following repository tables and make a note of the values in the columns.

C_REPOS_ZDT_STATUS

Record the values for all columns. You need these values in step 6.

C_REPOS_DB_RELEASE

Record the values for the following columns. You need these values in step 7.

db_password, tns_name

connection_port

oracle_sid

database_host

connect_url

database_id

connection_type

proxy_ind

db_proxy_username

db_proxy_password

db_replication_username

db_replication_password

debug_ind

debug_level

debug_file_name

debug_file_pat

Infrastructure Upgrade

. Upgrade hardware and third-party software in the active environment.

Stop the application servers, close connections, and then drop and re-create the schema in the active environment.

Stop the application servers in the active environment.

Close all the connections, such as SQL*Plus, Toad, and application server, to the active environment.

Drop the schema in active environment, and then create it.

Drop schema A - using system user (sqlplus system/password@tnsname)
 SQL> drop user envA cascade;
 
Create schema A - using system user (sqlplus system/password@tnsname)
 SQL> <hub_server_install>/resources/database/custom_scripts/oracle/import/@mk_cmx_ors_user; -- supply the schema name as A

Re-create the Operational Reference Store by importing the dump file that was generated from the passive environment.

C:\> impdp <dba_username>/<dba_password>@<tns_entry_name>
     directory=<DATA_PUMP_DIR_OBJECT>
     dumpfile==<mrm_backup_envb.dmp>
     logfile=<mrm_restore_after_upgrade.log>
     content=all 
     remap_schema=<from_user>:<to_user>
     parallel=8
     job_name=<RESTORE_ENVB>

When the schema is being created, you can safely ignore the following messages:

ORA-39083: Object type TYPE failed to create with error:
ORA-02304: invalid object identifier literal
The type already exists, and therefore it is not re-created

Remove event queues and drop tables.

/* Repository tables for ZDT */
delete from C_REPOS_ZDT_EVENT_QUEUE;
delete from C_REPOS_ZDT_REPLICAT_EXCEPTION;
update C_REPOS_ZDT_ENV_STATE set state = NULL, state_ts = NULL, 
state_desc = NULL, updated_by=NULL, update_date=NULL;

Run the following command to install the Java utility file:

sip_ant install_utility

To complete the swing installation process, run the following command:

sip_ant swing_finish

The replication parameter files install.

Check the environment-specific settings on the active environment in the C_REPOS_DB_RELEASE table.

All the values in the table must be local and the database entries must point to the local database. If necessary, update the values to match the values that were in the C_REPOS_DB_RELEASE table before you dropped the schema.

MDM Upgrade

. On the new passive environment, upgrade the

Multidomain MDM

and configure the Process Server.

Upgrading with Zero Downtime

Download Guide

Watch

Comments

Communities

Knowledge Base

Success Portal