What Should I Do If a DDL Change Made to an Ordinary Table at the Oracle Source of a Real-Time Migration Job by an Administrator Such as SYS or SYSTEM Is Not Found in the Job Log and Not Synchronized to the Destination?

Symptom

A DDL change made to an ordinary table at the oracle source of a real-time migration job by an administrator such as SYS or SYSTEM is not found in the job log and not synchronized to the destination.

Possible Causes

When reading DDL logs from the Oracle source, DataArts Migration filters out the logs of system users (SYS/SYSTEM) who may perform sensitive operations (such as changing passwords). For security reasons, DataArts Migration does not read the operation logs of SYS or SYSTEM.

Solution

The SYS user is generally used only for database management and is not recommended for operations on service data in databases. Common users are recommended for operations on service data. This complies with the separation of permissions for database management and service data operations described in the Oracle official documentation.

Oracle official warning: When the SYS user connects to a database, the SYS user has unlimited permissions on the data dictionaries of the database (including tables, views, indexes, functions, and triggers). Do not modify any data dictionary.

Generally, ordinary tables contain service data, and common users are used to perform DDL or DML operations on service tables. Common users are recommended for DDL operations on common Oracle data tables at the source.