Parameters - Perceptive Content Database Upgrade Package for Oracle Server - Foundation 24.1 - Foundation 24.1 - Ready - Perceptive Content - external

Perceptive Content Database Upgrade Package for Oracle Server

Platform
Perceptive Content
Product
Perceptive Content Database Upgrade Package for Oracle Server
Release
Foundation 24.1
License

The UPGRADE_SETUP procedure accepts the following optional parameters.

Parameter Description
TARGET_VERSION The target schema version for the database upgrade. This version of the upgrade package currently supports a target version of 7.5.0.0 and 7.7.0.0 and 7.9.0.0.

The default value is 7.9.0.0.

DEFAULT_MAX_MINUTES This only applies for upgrades with a starting schema version less than 7.5.0.0.

Used to define the default maximum number of minutes that an upgrade or synchronization procedure is permitted to start new operations. When greater than 0, the parameter is used to set an end time that defines when a procedure can no longer pick up new work. This parameter helps to limit the amount of work that a process is permitted to perform to help scope operations within a defined timeframe.

Applies to table synchronization (SYNC_TABLE_IN_DOC) and non-PK index creation executed by the UPTIME_STEPS procedure.

The default value of 0 is equal to unlimited.

DEFAULT_PARALLEL Used to define the default degree of parallelism for qualifying operations. The session will be forced to use the specified degree of parallelism during execution.

The default value of 0 is equal to CPU_COUNT-2.

DEFAULT_LOGGING Used to define the default logging option for qualifying operations. This applies to the creation of tables and indexes. Valid options are LOGGING or NOLOGGING.

If shipping archived redo logs for replication, then use LOGGING. Otherwise, consider using NOLOGGING to reduce logging during the creation of indexes to improve performance.

Note that with the NOLOGGING option objects will not be recoverable until they are successfully backed up.

The default value is LOGGING

SYNC_BATCH_SIZE This only applies for upgrades with a starting schema version less than 7.5.0.0.

Used to define the default batch size for the SYNC_TABLE_IN_DOC procedure. The batch size defines the number of rows to fetch (BULK COLLECT) into the synchronization work queue (cursor) for each batch.

The default value is 50,000 rows.

SYNC_BULK_LIMIT This only applies for upgrades with a starting schema version less than 7.5.0.0.

Used to define a limit on the number of rows fetched from the cursor by the bulk collect operation during the SYNC_TABLE_IN_DOC procedure. This helps reduce the memory utilization (PGA) for the process.

The default value is 10,000 rows.

SYNC_VALIDATE_FK This only applies for upgrades with a starting schema version less than 7.5.0.0.

Used to determine if the foreign key constraints, to and from the new IN_DOC table, should be validated after creation. If set to NO, then the SQL to manually validate the FK constraints will be displayed but not executed and must be manually executed as soon as possible after the upgrade.

The Foreign Key validation portion of the downtime steps is by far the longest part of the downtime for larger databases. If you are comfortable with the state of the synchronization process heading into the downtime then you can reduce your overall downtime duration by setting this parameter to NO and deferring the FK validation as a manual step after the downtime has completed.

The default value of YES means the FK constraints are validated as part of the downtime steps.

SYNC_KEEP_SRC_TABLE This only applies for upgrades with a starting schema version less than 7.5.0.0.

Used to specify whether to keep the original/source IN_DOC table upon successful completion of the downtime steps. If YES, then the source table will be renamed and saved after the downtime event. If NO, then the source table will be dropped at the end of the downtime event, which will free up the storage it is consuming.

The default value is YES to keep the original table and its PK constraint and index.

SYNC_DATA_TS_NAME This only applies for upgrades with a starting schema version less than 7.5.0.0.

The name of the tablespace to create the new IN_DOC table in. The user must have a sufficient quota on the specified tablespace.

The default value is the current tablespace of the IN_DOC table.

SYNC_INDX_TS_NAME This only applies for upgrades with a starting schema version less than 7.5.0.0.

The name of the tablespace to create the new IN_DOC table indexes in. The user must have a sufficient quota on the specified tablespace.

The default value is MAX(TABLESPACE_NAME) from ALL_INDEXES for the IN_DOC table.

MSG_DATA_TS_NAME This only applies for upgrades with a starting schema version less than 7.2.3.0.

The name of the tablespace to create the new IN_MESSAGE table in. The user must have a sufficient quota on the specified tablespace.

The default value is the current location of the IN_WF_AGENT_STATE table or the IN_MQ_D tablespace, if it exists.

MSG_INDX_TS_NAME This only applies for upgrades with a starting schema version less than 7.2.3.0.

The name of the tablespace to create the new IN_MESSAGE table indexes in. The user must have a sufficient quota on the specified tablespace.

The default value is the current location of the IN_WF_AGENT_STATE primary key index or the IN_MQ_I tablespace, if it exists.

TABLESPACE_NAME The name of the tablespace to create the temporary upgrade and synchronization control tables as well as the synchronization framework tables.

The default value is the current location of the IN_UPGRADE_TABLE_STATS table.