2.2.3 Create Patch set Edition

The Patch set Edition is created using the silent installer.
  1. At the start of the Zero downtime Database Setup process, Run ZDTInitRun.bat in Windows (ZDTInitRun.sh for Linux)
    A new Edition is created with the name configured in env.properties file for the property PATCHSET_EDITION.
  2. Run ZDTStageUpdateRun.bat in Windows (ZDTStageUpdateRun.sh for Linux) to move the process to the next stage operation.

Parent topic: Zero Downtime Database Setup

2.2.3 Database Setup in Patch set Edition

Backend Setup is done using Silent Installer. DDL Compilation, Object Compilation, and Static Data Loading are part of Backend Setup.
  1. Run the SMSDBCompileRun.bat in windows (SMSDBCompileRun.sh in Linux) for SMS schema (DB) compilation.
  2. Run the <Product Processor>DBCompileRun.bat to complete DDL Compilation, Object Compilation, and Static Data load.
    For Example: FCUBS INSTALLATION
    1. Run ROFCDBCompileRun.bat in windows (ROFCDBCompileRun.sh in linux) and check for the Invalid Count and make sure that the Invalid count is zero.
      The Database Backend Setup is done in Patch set Edition of the Schema.
  3. Run ZDTStageUpdateRun.bat in Windows (ZDTStageUpdateRun.sh for Linux) to move the process to the next stage operation.

2.2.3 Application Deployment in Patchset Edition

For the Application setup in<Domain 2>, refer the below steps.
  1. Generate Application / Gateway Ears and deploy in <Domain2> Application.
  2. <Domain 2> to be in inactive state (Standby mode).
    For more information on EAR building steps, refer to EAR building

2.2.3 Edition Switch in Patchset Edition

  1. Run ZDTLoginSwitchRun.bat (ZDTLoginSwitchRun.sh for Linux Operating System).
    The BAT/SH file execution ensures all new JDBC connections from application points to the new Edition created (as maintained by the property PATCHSET_EDITION).
  2. Run ZDTStageUpdateRun.bat in Windows (ZDTStageUpdateRun.sh for Linux) to move the process to the next stage operation.

2.2.3 Application Management in Patchset Edition

Refer to the below steps for the <Domain 2> application sanity and to activate for live transaction traffic.
  1. Start the <Domain 2> Application.
  2. Sanity Check of Patch set in <Domain 2> Application.
  3. All incoming transactions traffic routed to using Oracle Traffic Director.
  4. <Domain 1> to be made inactive status (Standby mode), once all the existing transactions in process in <Domain 1> completes its process.

2.2.3 Database Setup in Base Edition

Backend Setup is done using Silent Installer. DDL Compilation, Object Compilation, and Static Data Loading are part of Backend Setup.
  1. Run the SMSDBCompileRun.bat in windows (SMSDBCompileRun.sh in Linux) for SMS schema (DB) compilation.
  2. Run the <Product Processor>DBCompileRun.bat to complete Object Compilation.
    For Example: In case of FCUBS INSTALLATION
    1. Run ROFCDBCompileRun.bat in windows (ROFCDBCompileRun.sh in linux) and check for the Invalid Count and make sure that the Invalid count is zero.
      The Database Backend Setup is done in Base Edition of the Schema.
  3. Run ZDTStageUpdateRun.bat in Windows (ZDTStageUpdateRun.sh for Linux) to move the process to the next stage operation.

2.2.3 Application Deployment in Base Edition

For the Application setup in<Domain 1>, refer the below steps.
  1. Generate Application / Gateway Ears and deploy in <Domain1> Application.
  2. <Domain 1> to be in inactive state (Standby mode).
    For more information on EAR building steps, refer to EAR building.

2.2.3 Edition Switch in Base Edition

  1. Run ZDTLoginSwitchRun.bat (ZDTLoginSwitchRun.sh for Linux Operating System).
    The BAT/SH file execution ensures all new JDBC connections from application points to the Base Edition created (as maintained by the property BASE_EDITION).
  2. Run ZDTStageUpdateRun.bat in Windows (ZDTStageUpdateRun.sh for Linux) to move the process to the next stage operation.

2.2.3 Application Management in Base Edition

Refer to the below steps for the <Domain 1> application sanity and to activate for live transaction traffic.

  1. Start the <Domain 1> Application.
  2. Sanity Check of Patch set in <Domain 1> Application.
  3. All incoming transactions traffic routed to <Domain 1> using Oracle Traffic Director.
  4. <Domain 2> to be made inactive status (Standby mode), once all the existing transactions in process in <Domain 2> completes its process.
    The Operational Recommendation is briefed in section 1.6 (xref-cross ref)

2.2.3 Drop Patch Set Edition

  1. At the end of the Zero downtime Database Setup process, Run ZDTExitRun.bat in Windows (ZDTExitRun.sh for Linux).
    The Patch Set Edition (as maintained by the property PATCHSET_EDITION) is dropped.
  2. Run ZDTStageUpdateRun.bat in Windows (ZDTStageUpdateRun.sh for Linux) to move the process to the next stage of operation.