Custom Search . . .
Sunday, May 18, 2008
ORA-16792
DataGuard Broker:
While connecting standby database in dataguard broker. I got the ORA-16792
It's due some missing configuration in standby database.
Error Message:
Warning: ORA-16792: configuration property value is inconsistent with database setting
Action:
DGMGRL> EDIT DATABASE "EDKSTBY" SET PROPERTY LsbyMaxEventsRecorded = 5000;
Property "lsbymaxeventsrecorded" updated
Thursday, May 8, 2008
Monitoring Logical Standby Database
Monitoring Logical Standby Database:
DBA_LOGSTDBY_EVENTS:
It’s very interesting events that occurred during SQL Apply. By default, the view records most 100 events. If need needed we can changed using DBMS_LOGSTDBY_APPLY_SET()
DBA_LOSTDBY_LOG:
It’s providing dynamic information about archive logs being processed by SQL apply.
V$LOGSTDBY_STATE:
It’s provide fail-over characteristics about logical standby database
V$LOGSTDBY_PROCESS:
This view provides current state and various process involved with SQL apply. Including
· Identifying information (sid
| serial#
| spid
)
· SQL Apply process: COORDINATOR
, READER
, BUILDER
, PREPARER
, ANALYZER
, or APPLIER
(type
)
· Status of the process's current activity (status_code
| status
)
· Highest redo record processed by this process (high_scn
)
V$LOGSTDBY_PROGRESS:
This view provide detailed information regarding process made by SQL apply.
V$LOGSTDBY_STATE:
This view provides a synopsis of the current state of SQL ApplY
V$LOGSTDBY_STATS:
This view provides SQL Apply statistics.
Wednesday, May 7, 2008
Purge_Master_Log
PURGE_MASTER_LOG
This procedure removes local messages in the DBA_REPCATLOG view associated with a specified identification number, source, or master group.
To purge all of the administrative requests from a particular source, specify NULL for the id parameter. To purge all administrative requests from all sources, specify NULL for both the id parameter and the source parameter.
Syntax:
DBMS_REPCAT.PURGE_MASTER_LOG (
id IN BINARY_INTEGER,
source IN VARCHAR2,
gname IN VARCHAR2);
Example:
SQL> select id,source,gname,timestamp from dba_repcatlog;
ID
----------
SOURCE
--------------------------------------------------------------------------------
GNAME TIMESTAMP
------------------------------ ---------
1801
SAMIDB.SAMIINDIA
SAMIQC
SQL> begin
dbms_repcat.purge_master_log (
id => 1801,
source => 'samidb.samiindia',
gname => 'samiqc' );
end;
PL/SQL procedure successfully completed.
SQL> commit;
Commit complete.
SQL> select id,source,gname,timestamp from dba_repcatlog;
no rows selected