2.1 Pre-Requisite

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

From the SYS Database User the below privilege must be provided to the Database Schema.

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>;
6. For the Pre-Installation configuration refer to the sample entries in the env.properties file.
   env.properties file is displayed.

   Figure 2-1 Sample Entries in env.properties

   
   

   
   Description of "Figure 2-1 Sample Entries in env.properties"

   
   
7. On the env.properties, refer to the table for more information on sample entries in the env.properties file.

   Table 2-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.
   PATCHSET_INSTALLATION	Displays the value Y for patch set installation process.

8. For the Application Domain, refer the below per-requisites:
   1. Two application domains – <Domain1>, <Domain2> are required. These Domains will be 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>.
      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.