Batch Control | Description |
K1-CNVLD | Conversion - Load Data using SQL Loader. This process facilitates the legacy data extract upload using SQL Loader. The input data files are expected to be uploaded to a file storage location. See Input and Output File Location for more information about file storage locations. One run uploads the data into a single target Table or Maintenance Object. The process is multi-threaded. This process is discussed in more details in the Data Load Batch chapter |
K1-CNVDS | Conversion - Disable Conversion This process resets the environment indicators and prevents further conversion activities. Once conversion is disabled, the following actions are blocked: • Switching between Conversion and Production • Table truncation • Disable Indexes and Rebuilding the Statistics • Data insertion into Production • Data upload into staging Note: The process should be executed only once and only after all of the conversion activities are completed and the application is ready for the real production use. |
K1-CNVEN | Conversion - Enable Conversion This process resets the environment indicators and enables it for conversion activities. It should be executed at the start of the Conversion project. |
K1-DRPIN | Conversion - Disable Indexes on Production Tables This process can be used in two modes: • Populate Table or Maintenance Object batch parameter to process specific object • If no specific target is populated, the process disables indexes on all converted tables in Production schema |
K1-SDSIN | Conversion - Disable Indexes on Staging Tables This process can be used in two modes: • Populate Table or Maintenance Object batch parameter to process specific object • If no specific target is populated, the process disables indexes on all converted tables in Staging schema |
K1-RIUSP | Conversion - Rebuild Indexes and Update Statistics in Production This process can be used in two modes: • Populate Table or Maintenance Object batch parameter to process specific object • If no specific target is populated, the process rebuilds indexes and updates statistics on all converted tables in Production schema • Specify the sampling size (percentage) for statistics gathering. If not specified, the system will use default dbms_stats.auto_sample_size. • Specify whether you wish to rebuild indexes, to gather table statistics or both. It is recommended to rebuild the indexes and update statistics right after the data upload. |
K1-RIUSS | Conversion - Rebuild Indexes and Update Statistics in Staging This process can be used in two modes: • Populate Table or Maintenance Object batch parameter to process specific object • If no specific target is populated, the process rebuilds indexes and updates statistics on all converted tables in Staging schema • Specify the sampling size (percentage) for statistics gathering. If not specified, the system will use default dbms_stats.auto_sample_size • Specify whether you wish to rebuild indexes, to gather table statistics or both It is recommended to rebuild the indexes and update statistics right after the data upload. |
K1-CLNTB | Conversion - Truncate Tables in Production This process can be used in two modes: • Populate Table or Maintenance Object batch parameter to process specific object • If no specific target is populated, the truncates all converted tables in Production schema |
K1-SCLTB | Conversion - Truncate Tables in Staging This process can be used in two modes: • Populate Table or Maintenance Object batch parameter to process specific object • If no specific target is populated, the truncates all converted tables in Staging schema |
K1-CLNRT | Conversion — Truncate XML Resolution Tables This process is allowed to run only in the Staging schema and may be used in two modes: • Populate Table or Maintenance Object batch parameter to process specific object • If no specific target is populated, the truncates all XML Resolution tables in Staging schema |
K1-CLNKY | Conversion - Truncate Key Reference Tables This process is allowed to run only in the Staging schema and may be used in two modes: • Populate Table or Maintenance Object batch parameter to process specific object • If no specific target is populated, the truncates all Key Reference tables in Staging schema |