The CREATE_INDEXES_IN_DOC procedure creates all the non-primary key indexes on the new IN_DOC table (NEW_DOC). This procedure is indirectly executed by the UPTIME_STEPS procedure or can be executed manually after running CREATE_DEST_TABLE_IN_DOC, and LOAD_DEST_TABLE_IN_DOC, and CREATE_PK_IN_DOC.
This procedure accepts the MAX_MINUTES parameter to limit the amount of work that is completed per execution of the procedure.
To further reduce the impact to other users, consider using smaller values for the degree of parallelism (PARALLEL) to limit the number of processors that the procedure can use. Note that using less processors will result in the operation taking longer to complete.
Alternatively, using a higher degree of parallelism and a smaller value for MAX_MINUTES can help to complete a single task as quickly as possible.
The use of these parameters can help to facilitate the incremental creation of the required indexes during uptime in the days or hours leading up to the downtime with minimal impact to the rest of the system.
- You may also consider leveraging Oracle consumer groups and map the UPGRADE client identifier (CLIENT_ID) to a specific consumer group to restrict the resources that an upgrade or synchronization procedure may utilize. Beware that doing so may result in a slower upgrade or downtime event if the upgrade processes are constrained and unable to run freely.
- You can schedule this procedure or manually execute it as necessary to incrementally create the indexes prior to the execution of the downtime steps.