ORA-00494: enqueue held for too long (more than 900 seconds) by 'inst, ospid ' (10.2.0.4 and later). ORA-00600: internal error code, arguments: (10.2.0.3 and Earlier). Requested to grow by 81 records added 3 blocks of records Number of Days that this information is stored in the control fileĮxpanded controlfile section 11 from 28 to 109 records. Archived redo logs that the database generates. Handling Errors during CREATE CONTROLFILE If compatibility is 10.2.0 or later, you do not have to create new control files when you make such a change the control files automatically expand, if necessary, to accommodate the new configuration information. You want to change the parameters from the CREATE DATABASE or CREATE CONTROLFILE commands: MAXLOGFILES, MAXLOGMEMBERS, MAXLOGHISTORY, and MAXINSTANCES, when the compatibility is earlier than 10.2.0. You want to change the database name. For example, you would change a database name if it conflicted with another database name in a distributed environment. All control files for the database have been permanently damaged and you do not have a control file backup. It does not apply to records such as datafile, tablespace, and redo thread records, which are never reused unless the corresponding object is dropped from the tablespace. This parameter applies only to records in the control file that are circularly reusable (such as archive log records and various backup records). It is the MINIMUM number of days that the details are retained. It is not mandatory that all the records will be reused after days specified for CONTROL_FILE_RECORD_KEEP_TIME. Backup datafile and redo log information. Backup set and backup piece information. The names and locations of associated datafiles and redo log files. It contains metadata that must be accessible when the database is not open. For example, when an administrator adds, renames, or drops a data file or online redo log file, the database updates the control file to reflect this change. The control file tracks structural changes to the database. 
It contains information about data files, online redo log files, and other files that are required to open the database. The average Input/Output time of the physical storage on the disk.Īverage read time to the physical storage on the disk.Īverage Synchronous Single-Block Read LatencyĪverage write time to the physical storage on the disk. Multiplexed Online Log Files Average Count Total number of I/O write requests for the disk 
Total I/O time for write requests for the disk Total number of failed I/O write requests for the disk Total number of bytes written to the disk Universal Device ID portion of the name returned by discovery
Global state of the disk with respect to the disk group Total number of I/O read requests for the disk Total I/O time for read requests for the disk Total number of failed I/O read requests for the disk The name of the manufacturer and the name of the product Operating system pathname portion of the name returned by discovery Per-instance status of the disk relative to group mounts Global status about which kinds of I/O requests are allowed to the diskĭate and time when the disk was was first mounted by the first instance
Name of the library that discovered the disk Per-instance status of the disk as seen by discoveryĭisk label portion of the name returned by discovery Number of the disk group containing the disk Name of the failure group containing the disk Number assigned to the disk withing its group Original destination from which the archive log was generatedĪ 32-bit number consisting of a disk group number in the high-order 8 bits and a disk number in the low-order 24 bitsĭate and time when the disk was added to the disk group 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) If the file has been backed up more than 15 times, the value remains 15 Indicates the number of times this file has been backed up.
0 kommentar(er)
