yexinru/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity
Files
f1bf1560d625de04ad15ae06d78bd54371d2d45d
doc-exports/docs/drs/umn/drs_11_0465.html
wangdengke2 b937f7e416 drs umn 20230210 version 
Reviewed-by: Boka, Ladislav <ladislav.boka@t-systems.com>
Co-authored-by: wangdengke2 <wangdengke2@huawei.com>
Co-committed-by: wangdengke2 <wangdengke2@huawei.com>
2024-01-11 07:40:50 +00:00

3.0 KiB
Raw Blame History

Checking the Physical Standby Database

Oracle Synchronization

Table 1 Physical standby database check

Check Item

Physical standby database check

Description

If the source Oracle database is in the incremental migration phase, the instance type of the source must be the same as that of the destination. Otherwise, the migration fails.

Item to Be Confirmed and Handling Suggestion

Item to be confirmed:

  1. The physical standby database does not generate logs. It replicates them from the primary database. Check whether supplemental logging of the primary database meets the incremental synchronization requirements.
  2. The physical standby database does not generate logs, resulting in synchronization task delay. You can shorten the interval for archiving logs from the primary database to the physical standby database. However, extremely low values can result in a large number of logs, so you are advised to synchronize data from the logical standby database. Run the following statement on the primary database to specify the log archive interval:
    alter system set archive_lag_target=seconds;
Parent topic: Database Parameters