1.2 Pre-Requisite

Below Privilege must be provided to the Database Schema from SYS Database User.

1. ALTER USER <SCHEMA NAME> ENABLE EDITIONS [FORCE];
2. GRANT CREATE ANY EDITION TO <SCHEMA NAME>;
3. GRANT DROP ANY EDITION TO <SCHEMA NAME>;
4. GRANT ALTER SESSION TO <SCHEMA NAME>;
5. GRANT EXECUTE on DBMS_SESSION TO <SCHEMA NAME>;

Note:

Refer to section Operational Issues and Troubleshooting.

Pre-Installation Configuration:

• ZDT_PATCHING is a property in the file env.properties. Set this property to ‘Y’ if ZDT patching is required and ‘N’ if application should be taken offline when patching is done.
• BASE_EDITION is a property in the file env.properties. This property is used to indicate the Base Edition. For example ‘ORA$BASE’.
• PATCHSET_EDITION is a property in the file env.properties. This property is used to specify the Edition that would be used as the alternate Edition during ZDT Patch-set Installation. For example, ‘E1’.
• PATCHSET_INSTALLATION is an existing property in the file env.properties. It will have value ‘Y’ for Patch set installation process.

Sample Entries in env.properties as given below:

Description of the illustration 1.2_properties.png

Refer “Property File Creation” User Manual section of User manual for detailed procedure to create Property file.

Application Domain - Prerequisite:

• Two application domains – <Domain1>, <Domain2> required. These Domains will be integrated and controlled with Oracle Traffic Director to support Zero downtime Patching.
• By default, <Domain2> will remain inactive (Standby mode) and all JDBC connections to Database (Schema) routed to <Domain1>

Any Bulk upload processing, Batch processing (including End of Day operations) to be planned either to complete before the start or after completion of the Patch Set Compilation / Deployment.