Set up a friendly environment to share my understanding and ideas about Oracle / Oracle Spatial database administration, ESRI ArcSDE Geodatabase administration and UNIX (Solaris) operating system.
Name of the tablespace containing the rollback segment
SEGMENT_ID
NUMBER
NOT NULL
ID number of the rollback segment
FILE_ID
NUMBER
NOT NULL
File identifier number of the file containing the segment head
BLOCK_ID
NUMBER
NOT NULL
ID number of the block containing the segment header
INITIAL_EXTENT
NUMBER
Initial extent size in bytes
NEXT_EXTENT
NUMBER
Secondary extent size in bytes
MIN_EXTENTS
NUMBER
NOT NULL
Minimum number of extents
MAX_EXTENTS
NUMBER
NOT NULL
Maximum number of extent
PCT_INCREASE
NUMBER
Percent increase for extent size
STATUS
VARCHAR2(16)
Rollback segment status
INSTANCE_NUM
VARCHAR2(40)
Rollback segment owning Real Application Clusters instance number
RELATIVE_FNO
NUMBER
NOT NULL
Relative file number of the segment header
Note:
1.In automatic undo management (AUM) DBA's don't have privileges to offline/online undo segments. And this is controlled by SMON process. So the view will be useful only in few scenarios, where we have internal errors with undo segments.
V$ARCHIVED_LOG displays archived log information from the control file, including archive log names. An archive log record is inserted after the online redo log is successfully archived or cleared (name column is NULL if the log was cleared). If the log is archived twice, there will be two archived log records with the same THREAD#, SEQUENCE#, and FIRST_CHANGE#, but with a different name. An archive log record is also inserted when an archive log is restored from a backup set or a copy and whenever a copy of a log is made with the RMAN COPY command.
Column
Datatype
Description
RECID
NUMBER
Archived log record ID
STAMP
NUMBER
Archived log record stamp
NAME
VARCHAR2(513)
Archived log file name. If set to NULL, either the log file was cleared before it was archived or an RMAN backup command with the "delete input" option was executed to back up archivelog all (RMAN> backup archivelog all delete input;).
DEST_ID
NUMBER
Original destination from which the archive log was generated. The value is 0 if the destination identifier is not available.
THREAD#
NUMBER
Redo thread number
SEQUENCE#
NUMBER
Redo log sequence number
RESETLOGS_CHANGE#
NUMBER
Resetlogs change number of the database when the log was written
RESETLOGS_TIME
DATE
Resetlogs time of the database when the log was written
RESETLOGS_ID
NUMBER
Resetlogs identifier associated with the archived redo log
FIRST_CHANGE#
NUMBER
First change number in the archived log
FIRST_TIME
DATE
Timestamp of the first change
NEXT_CHANGE#
NUMBER
First change in the next log
NEXT_TIME
DATE
Timestamp of the next change
BLOCKS
NUMBER
Size of the archived log (in blocks)
BLOCK_SIZE
NUMBER
Redo log block size. This is the logical block size of the archived log, which is the same as the logical block size of the online log from which the archived log was copied. The online log logical block size is a platform-specific value that is not adjustable by the user.
CREATOR
VARCHAR2(7)
Creator of the archivelog:
·ARCH - Archiver process
·FGRD - Foreground process
·RMAN - Recovery Manager
·SRMN - RMAN at standby
·LGWR - Logwriter process
REGISTRAR
VARCHAR2(7)
Registrar of the entry:
·RFS - Remote File Server process
·ARCH - Archiver process
·FGRD - Foreground process
·RMAN - Recovery manager
·SRMN - RMAN at standby
·LGWR - Logwriter process
STANDBY_DEST
VARCHAR2(3)
Indicates whether the entry is an archivelog destination (YES) or not (NO)
ARCHIVED
VARCHAR2(3)
Indicates whether the online redo log was archived (YES) or whether RMAN only inspected the log and created a record for future application of redo logs during recovery (NO).
APPLIED
VARCHAR2(3)
Indicates whether the archivelog has been applied to its corresponding standby database (YES) or not (NO). The value is always NO for local destinations.
This column is meaningful at the physical standby site for the ARCHIVED_LOG entries with REGISTRAR='RFS' (which means this log is shipped from the primary to the standby database). If REGISTRAR='RFS' and APPLIED is NO, then the log has arrived at the standby but has not yet been applied. If REGISTRAR='RFS' and APPLIED is YES, the log has arrived and been applied at the standby database. You can use this field to identify archivelogs that can be backed up and removed from disk.
DELETED
VARCHAR2(3)
Indicates whether an RMAN DELETE command has physically deleted the archived log file from disk, as well as logically removing it from the control file of the target database and from the recovery catalog (YES) or not (NO)
STATUS
VARCHAR2(1)
Status of the archived log:
A - Available D - Deleted U - Unavailable X - Expired
COMPLETION_TIME
DATE
Time when the archiving completed
DICTIONARY_BEGIN
VARCHAR2(3)
Indicates whether the log contains the start of a LogMiner dictionary (YES) or not (NO)
DICTIONARY_END
VARCHAR2(3)
Indicates whether the log contains the end of a LogMiner dictionary (YES) or not (NO)
END_OF_REDO
VARCHAR2(3)
Indicates whether the archived redo log contains the end of all redo information from the primary database (YES) or not (NO)
BACKUP_COUNT
NUMBER
Indicates the number of times this file has been backed up. Values range from 0-15. If the file has been backed up more than 15 times, the value remains 15.
ARCHIVAL_THREAD#
NUMBER
Redo thread number of the instance that performed the archival operation. This column differs from the THREAD# column only when a closed thread is archived by another instance.
ACTIVATION#
NUMBER
Number assigned to the database instantiation
IS_RECOVERY_DEST_FILE
VARCHAR2(3)
Indicates whether the file was created in the flash recovery area (YES) or not (NO)
COMPRESSED
VARCHAR2(3)
This column is reserved for internal use only
FAL
VARCHAR2(3)
Indicates whether the archive log was generated as the result of a FAL request (YES) or not (NO)
END_OF_REDO_TYPE
VARCHAR2(10)
Possible values are as follows:
·SWITCHOVER - Shows archived redo log files that are produced at the end of a switchover
·TERMINAL - Shows archived redo log files produced after a failover
·RESETLOGS - Shows online redo log files archived on the primary database after an ALTER DATABASE OPEN RESETLOGS statement is issued
·ACTIVATION - Shows any log files archived on a physical standby database after an ALTER DATABASE ACTIVATE STANDBYDATABASE statement is issued
·"empty string" - Any empty string implies that that the log is just a normal archival and was not archived due to any of the other events
BACKED_BY_VSS
VARCHAR2(3)
Whether or not the file has been backed up by Volume Shadow Copy Service (VSS). This column is for internal use only.
Note:
V$ARCHIVED_LOG replaces V$LOG_HISTORY in Oracle8.
How to Delete All Archived Log Entries in the V$ARCHIVED_LOG?
The number of archived redo log files maintained in the controlfile and available through V$ARCHIVED_LOG is determined by the MAXLOGHISTORY parameter of the create database command. The archived redo log records are maintained up to the value of MAXLOGHISTORY, then wrap and overlay previous entries starting from the beginning. Eventually, all entries in V$ARCHIVED_LOG will be overwritten after the number of archived logs exceeds MAXLOGHISTORY. Recreate the controlfile to force the removal of all archived log entries from the controlfile and the V$ARCHIVED_LOG view.
Script to check when archived redo logs are applied
4.The following RMAN example shows how to backup all archived redo logs with a sequence number of 234 or higher to a backupset. After the archived redo logs are copied, they are deleted from disk and marked as deleted in the V$ARCHIVED_LOG.
I reserve the right to delete comments that are not contributing to the overall theme of the BLOG or are insulting or demeaning to anyone. The posts on this BLOG are provided "as is" with no warranties and confer no rights. The opinions expressed on this site are mine and mine alone, and do not necessarily represent those of my employer.
