1.2 Pre-Requisite

This topic explains the per-requisites for the zero downtime database installer.

The following privilege must be provided to the Database Schema from the SYS Database User.
  • ALTER USER <SCHEMA NAME> ENABLE EDITIONS [FORCE];
  • GRANT CREATE ANY EDITION TO <SCHEMA NAME>;
  • GRANT DROP ANY EDITION TO <SCHEMA NAME>;
  • GRANT ALTER SESSION TO <SCHEMA NAME>;
  • GRANT EXECUTE on DBMS_SESSION TO <SCHEMA NAME>;

Refer to the Operational Issues and Troubleshooting topic in this user guide.

  1. For the Pre-Installation configuration, refer to the sample entries in the env.properties file.
    The env.properties file displays.

    Figure 1-1 Sample Entries in env.properties



    Refer to the table below for more information on sample entries in the env.properties file.

    Table 1-1 Sample Entries in env.properties

    Entries Description
    ZDT_PATCHING Set this property to Y if ZDT patching is required and N if the application is taken offline when patching is done.
    BASE_EDITION Indicates the Base Edition. For example, ORA$BASE.
    PATCHSET_EDITION This property is used to specify the Edition that would be used as the alternate Edition during ZDT Patch-set Installation. For example, E1.
    ZDT_OBJECTS_ACTUALIZATION_REQUIRED This property used to specify whether the actualization of objects from Base edition to Patchset Edition is required or not. It is recommended to give as Y for a smooth Zero Downtime patch set application process.
    ZDT_OBJECTS_COMPILE_THREAD This property used to specify the number of threads used to compile during actualization of objects from Base Edition to Patch-set Edition. Please give a numeric value greater than zero. For example 5.
    NUMBER_OF_CPU_CORES_FOR_ZDT_RECOMP This property used to specify the number of parallel threads the system can utilize for recompilation of invalids during the actualization of objects. This value depend on the number of CPU cores. Please give a numeric value. For example 4 or above.
    PATCHSET_INSTALLATION Displays the value Y for patch set installation process.

    Refer to the Installer Property File user guide for more information to create property file.

  2. For the Application Domain creation, refer the below per-requisites:
    1. Two application domains – <Domain1>, <Domain2> are required. These domains are integrated and controlled with Oracle Traffic Director to support Zero downtime Patching.
    2. By default, <Domain2> will remain inactive (Standby mode), and all JDBC connections to Database (Schema) routed to <Domain1>.
    For any Bulk upload processing, Batch processing (including End of Day operations) must be planned either to be completed before the start or after completion of the Patch Set Compilation/Deployment.