Database Replication Enablement for Oracle Transportation and Global Trade Management
Database Replication Enablement is an optional, separately priced feature (Part# B91919) of the Transportation and Global Trade Management that provides for a near real time replication of the main data from the Transportation and Global Trade Management production schema, which can be used for purposes of integrated reporting with other systems, or population of an external data lake. The key advantage to this feature is that it allows SQL access to a read-only copy of the Cloud database, a database which is owned by the customer and not part of the SaaS offering. The replication is performed using the Oracle GoldenGate product, which must be licensed by the customer along with the target database license.
The replication is performed on the glogowner and reportowner schemas (not hdowner or archive) and copies the data, structure and indexes. It doesn't copy the VPD information. The tables listed below are excluded from replication because they either include sensitive data or they contain high-volume transient data that isn't required for analytics type reporting. It is important to understand that deletions, including Business Data Purge for Orders, and Shipments, are also replicated. You'll need to propagate the data in the corresponding tables to another table or database if they intend to keep the data longer than the purge period. For more details on the setup and configuration required, please review this MOS note, GoldenGate Deployment for Oracle Transportation and Global Trade Management Cloud (OTM) - ATP and GGS (Doc ID 2977424.1).
To reduce the downtime required to apply Quarterly Updates, Oracle Transportation and Global Trade Management Cloud(OTM/GTM) runs a pre-downtime process several days before the scheduled Quarterly Update. This process includes applying database structure changes using the Oracle Database feature "Edition Based Redefinition". This feature prevents the database structure changes from impacting the current running version of the OTM/GTM service.
Customers using the paid optional GoldenGate based Database Replication service (Part# B91919) will see these database structure changes immediately in the replication service. This is the expected behavior since the replication is performed at the Database Table level and is near real time. These database structure changes will not impact your OGG Target server configuration or replication process. However, these changes will potentially impact your downstream queries from the OGG Target database.
Review the Cloud Documents > Database Structural Changes section in note Oracle Transportation and Global Trade Management Documentation Resources (Doc ID 796594.1).
Table Name
- APP_MACHINE_FAILOVER_T
- APP_MACHINE_T
- APP_POWER_ACTION_ACCESS_T
- APP_SERVER_DATA_QUEUE_DEF_T
- APP_SERVER_DOMAIN_T
- APP_SERVER_FUNCTION_T
- APP_SERVER_MACHINE_T
- APP_SERVER_QUEUE_T
- APP_SERVER_T
- BUSINESS_PROCESS_LOG_T
- CONNECTION_POOL_T
- DATA_PURGE_HISTORY_DETAIL_T
- DATA_Q_DEF_RELATED_Q_DEF_T
- DATA_QUEUE_DEF_T
- DATA_QUEUE_EXECUTOR_T
- DATA_QUEUE_INDEX_COL_T
- DATA_QUEUE_INDEX_T
- DATA_QUEUE_POLLER_INDEX_T
- DATA_QUEUE_POLLER_T
- DATA_QUEUE_TABLE_T
- DATA_SOURCE_T
- DB_TRACE_FILE
- DBPATCH_LOG_T
- DOMAIN_COPY_SCRIPT
- DOMAIN_COPY_SEQ_CACHE
- EBR_TABLE_T
- ERROR_LOG_T
- EXCEPTIONS
- EXPLANATION_T
- GL_LOGIN_HISTORY_T
- I_LOG_DETAIL_T
- I_LOG_T
- I_TRANSACTION_ACK_T
- I_TRANSACTION_DETAIL_T
- I_TRANSACTION_REFNUM_T
- I_TRANSACTION_T
- I_TRANSMISSION_ACK_T
- I_TRANSMISSION_PGROUP_T
- I_TRANSMISSION_REFNUM_T
- I_TRANSMISSION_REPORT_T
- I_TRANSMISSION_T
- JMSCONSUMER_T
- JMSDESTINATION_T
- JMSMESSAGE_T
- JMSMESSAGEQUEUE_T
- JMSTABLEID_T
- OBJECT_LOCK_T
- PLAN_TABLE
- Q_INTEGRATION_IN_EXCEPTION_T
- Q_INTEGRATION_IN_T
- Q_INTEGRATION_OUT_EXCEPTION_T
- Q_INTEGRATION_OUT_OVERFLOW_T
- Q_INTEGRATION_OUT_T
- Q_LIFETIME_EVENT_EXCEPTION_T
- Q_LIFETIME_EVENT_T
- Q_MESSAGE_EXCEPTION_T
- Q_MESSAGE_T