oracle data guard apply lag

The problem originates from a 12c database of the customer and needs to be booted to a non-real time apply mode, but the discovery is performed:ALTER DATABASE recover managed standby database cancel;ALTER DATABASE recover managed standby database disconnect from session; After that, the database is still working in the real time apply mode. Went to the alertlog for a while, found the answer: Thu June 09

Role Switching between Data Guard master and slave databases is divided into the following two types:1) SwitchoverSwithchover is generally designed to switch roles, such as upgrading. It is usually lossless, that is, there will be no data loss.Its execution is divided into two phases:1. convert Primary to Standby2. Convert Standby (one) to Primary2) FailoverFailo

The role switching between Data guard master and subordinate libraries is divided into the following two kinds:1) SwitchoverSwithchover are usually artificial and planned for role swaps, such as upgrades. It is usually lossless, that is, there will be no loss of data. its implementation is mainly divided into two stages:1.Primary Switch to Standby2.Standby (one)

/standby/system01.dbf /data/oradata/standby/undotbs01.dbf /data/oradata/standby/sysaux01.dbf /data/oradata/standby/users01.dbf /data/oradata/standby/test01.dbf Sql> Show Parameter Standby_file NAME TYPE VALUE ------------------------------- ----------- ------------------------------ Standby_file_management stri

---------------------------------------------PROD3 physical STANDBY to PRIMARY--ready for library cut Switch to the main library sys@aux> ALTER DATABASE commit to switchover to primary; Database altered. sys@aux> ALTER DATABASE open; Database altered. --Start the standby for recovery sys@prod3> startup ORACLE instance started. Total System Global area 958341120 bytes Fixed Size 1348972 bytes Variable Size 281021076 bytes Database buffers 671088

switch to the primary role. Otherwise, confirm that the Redo app is started until the query results show to primary or sessions ACTIVE. 7. Switch the physical standby to the primary role Execute the following SQL on the target physical standby: Sql> ALTER DATABASE COMMIT to switchover to PRIMARY with SESSION SHUTDOWN; Note: If the query results in step 1th are to PRIMARY, the WITH SESSION shutdown clause in the SQL statement can be omitted.

* ERROR in line 1:ora-03113: End-of-file on communication channel--trying to manipulate the main library throw error Process id:4810 session id:28 Serial: Not connected to Oracle Sys@priocm> exit disconnected from Oracle Database 11g Enterprise Edition release 11.2.0.3.0 -Production with the partitioning, OLAP, Data Mining and real application testing options--t

Oracle Data Guard from the macroscopic point of view, mainly provides the following two services: 1) Log transmission: The main library transmits the generated redo log to the standby library; 2 log application: The redo log, which is transferred from the main library, is used by the standby library. This article first describes the log Transport service, the

To test the creation of a data guard environment on the same server. The main library is in a normal state and there are available backups, and the force logging and associated initialization parameters for the main library are set below: sql> ALTER DATABASE force logging; Database altered. To modify the initialization parameters of the main library: Sql> alter system set Log_archive_config = ' dg_conf

permissions that are directly assigned to a user or role): Select*fromdba_sys_privs;select*fromuser_sys_ Privs;6, view roles (view only roles owned by logged-in users) Select*fromrole_sys_privs;7, view user object permissions:select* Fromdba_tab_privs;select*fromall_tab_privs;select*fromuser_tab_privs ; 8. View all roles: select*fromdba_roles;9, view roles owned by user or role:select*fromdba_role_privs; SELECTNBSP;*NBSP;FROMNBSP;USER_ROLE_PRIVS;10, see which users have SYSDBA or Sysoper system

The data guard provides the following three kinds of protection modes: 1 Maximum protection mode (Maximum Protection)"Maximum protection" here refers to the maximum protection of the data is not lost, that is, at least one standby and primary maintain real-time synchronization, but this is costly, that is, when a transaction is committed, not only to write to th

The following is a detailed analysis of the use of Oracle switchover and failover, the need for friends under the reference The role switching between Data guard master and subordinate libraries is divided into the following two kinds:1) SwitchoverSwithchover are usually artificial and planned for role swaps, such as upgrades. It is usually lossless, that is, th

Before you can create a logical repository, you must first create a physical repository, and for how to create a physical library, refer to the Data Guard series (4)-Creating a physical repository without stopping the main library. 1. Stop the Log Application service on the physical repository sys@jkka> ALTER database RECOVER MANAGED STANDBY database CANCEL; Database altered. 2. Reset the main