Oracle® Retail Bulk Data Integration Installation Guide Release 19.0 F23581-01 |
|
Previous |
Next |
To accelerate the application performance, following indexes are created on the listed tables in JobAdmin, Processflow and SchedulerAdmin applications.
Process Flow Admin
Table Name | Index Name |
---|---|
BDI_ACTIVITY_EXEC_INSTANCE |
INDX_ACTIVITY_EXEC_INSTANCE_1 |
BDI_PROCESS_EXEC_INSTANCE |
INDX_PROCESS_EXECUTION_1 |
INDX_PROCESS_EXECUTION_2 |
|
INDX_PROCESS_EXECUTION_3 |
|
BDI_PROCESS_CALL_STACK |
INDX_PROCESS_CALL_STACK_1 |
INDX_PROCESS_CALL_STACK_2 |
Scheduler Admin
Table Name | Index Name |
---|---|
BDI_SCHEDULE_EXECUTION |
INDX_SCHEDULE_EXEC_1 |
INDX_SCHEDULE_EXEC_2 |
|
INDX_SCHEDULE_EXEC_3 |
|
INDX_SCHEDULE_EXEC_4 |
Job Admin
Table Name | Index Name |
---|---|
BDI_DWNLDR_IFACE_MOD_DATA_CTL |
INDX_DNLDR_IFACE_MD_DAT_CL_1 |
INDX_DNLDR_IFACE_MD_DAT_CL_2 |
|
INDX_DNLDR_IFACE_MD_DAT_CL_3 |
|
BDI_DWNLDR_TRNSMITR_EXE_DSET |
INDX_DT_TRANSMITR_EXE_DSET_1 |
INDX_DT_TRANSMITR_EXE_DSET_2 |
|
INDX_DT_TRANSMITR_EXE_DSET_3 |
|
INDX_DT_TRANSMITR_EXE_DSET_4 |
|
BDI_UPLOADER_TRANSACTION |
INDX_UPLOADER_TRANSACTION_1 |
INDX_UPLOADER_TRANSACTION_2 |
|
BDI_RECEIVER_TRANSACTION |
INDX_RECV_TRANSACTION_1 |
BDI_RECEIVER_TRANSMISSION |
INDX_RECEIVER_TRANSMISSION_1 |
BDI_UPLDER_IFACE_MOD_DATA_CTL |
INDX_UPLDR_IFACE_MD_DAT_CL_1 |
INDX_UPLDR_IFACE_MD_DAT_CL_2 |
|
BDI_UPLOADER_EXE_DATASET |
INDX_UPLOADER_EXE_DATASET_1 |
INDX_UPLOADER_EXE_DATASET_2 |
Migration Steps
During migration from 16.0.025 to 16.0.027, to accommodate for the above-created indexes run the following SQL scripts against respective schemas as listed below.
Name | File Location | Database Schema for Execution |
---|---|---|
migrate-schema-from-16.0.025-to-16.0.027.sql |
bdi-process-home/setup-data/ddl/migration |
Processflow Schema |
Note: If both integration schema and receiver schema are same, do not run the migration script twice from bdi-<edge>-app-job-home/setup-data/ddl/migration.If both schemas are different, the user may see the "SQL Error: ORA-00942: table or view does not exist" for the table that does not exist on that schema. For migrating from any version older than 16.0.025, the user needs to run the migration scripts incrementally. |