Access table updating time stamp Free webcam chat belfast no registration

The most recent archived redo log file is sequence number 13, and it was received at the logical standby database at .

The SELECT NAME, VALUE, UNIT FROM V$DATAGUARD_STATS; NAME VALUE UNIT -------------------- ------------ ------------------------------ apply finish time 00 day(2) to second(1) interval apply lag 00 day(2) to second(0) interval transport lag 00 day(2) to second(0) interval SELECT SID, SERIAL#, SPID, TYPE, HIGH_SCN FROM V$LOGSTDBY_PROCESS; SID SERIAL# SPID TYPE HIGH_SCN ----- ------- ----------- ---------------- ---------- 48 6 11074 COORDINATOR 7178242899 56 56 10858 READER 7178243497 46 1 10860 BUILDER 7178242901 45 1 10862 PREPARER 7178243295 37 1 10864 ANALYZER 7178242900 36 1 10866 APPLIER 7178239467 35 3 10868 APPLIER 7178239463 34 7 10870 APPLIER 7178239461 33 1 10872 APPLIER 7178239472 9 rows selected.

The following sections describe the key views that can be used to monitor a logical standby database: view records interesting events that occurred during the operation of SQL Apply.

access table updating time stamp-81

Applying State In this state, SQL Apply has successfully loaded the initial snapshot of the Log Miner dictionary, and is currently applying redo data to the logical standby database.

For detailed information about the SQL Apply progress, query the FROM V$LOGSTDBY_PROGRESS; APPLIED_TIME APPLIED_SCN MINING_TIME MINING_SCN -------------------- ----------- -------------------- ----------- 10-JAN-2005 346791023 10-JAN-2005 3468810134 Foreign archived logs stored in the fast recovery area are always managed by SQL Apply.

You can override automatic management of foreign archived logs not stored in fast recovery area by executing the following PL/SQL procedure: view can be thought of as a circular log containing the most recent interesting events that occurred in the context of SQL Apply.

By default the last 10,000 events are remembered in the event view.

Foreign archived logs that are not stored in fast recovery area are by default managed by SQL Apply.

Under automatic management, foreign archived logs that are not stored in the fast recovery area are retained for the time period specified by the parameter once all redo records contained in the log have been applied at the logical standby database.

SQL Apply uses a collection of background processes to apply changes from the primary database to the logical standby database.

Figure 10-1 shows the flow of information and the role that each process performs.

In a well-tuned logical standby database, pageout activities will occur occasionally and should not effect the overall throughput of the system.

Modifications made to the logical standby database do not become persistent until the commit record of the transaction is mined from the redo log files and applied to the logical standby database.

To mitigate this, SQL Apply periodically checkpoints old uncommitted data.

Tags: , ,