Oracle8 Migration Release 8.0 A58243-01 |
|
This appendix briefly describes changes from version 7, release 7.3 to the version 8 server Control File Fixed Views.
In version 7, all control file views date columns are VARCHAR2(20) strings in 'MM/DD/YY HH24:MI:SS' format.
In version 8, every new date column is a real DATE column. In contrast to the previous VARCHAR2(20) string, DATE provides users the following benefits:
This appendix lists the names of the views and the names of the columns in the views that have been changed or added to version 8.
See Also:
Oracle8 Reference for descriptions of each column and for a complete listing of the columns in the tables. |
V$ARCHIVE still shows logs that must be archived.
V$LOG was superceded by V$LOG_HISTORY, which is superseded by the new version 8 view, V$ARCHIVED_LOG. In version 8, however, V$LOG is still provided and still lists all archived logs in its ARCHIVED column.
The obsolete V$LOGHIST view is retained for historical compatibility.
In version 8, several V$LOG_HISTORY columns have been renamed, as shown in the following table. Further, the (version 7) ARCHIVE_NAME column is not present in version 8.
Version 8 Column | Version 7 Column |
FIRST_TIME |
TIME |
FIRST_CHANGE# |
LOW_CHANGE# |
NEXT_CHANGE# |
HIGH_CHANGE# |
[not present] |
ARCHIVE_NAME |
The new version 8 view, V$ARCHIVED_LOG, shows archived logs, including their names. If a log is never archived, the V$ARCHIVED_LOG view does not return any row for the log. If a log is archived twice, V$ARCHIVED_LOG returns two rows for the log.
Certain columns in this new view correspond to version 7 V$LOG_HISTORY names and use formats that match the column names in other version 8 views. The V$ARCHIVED_LOG view shows archived log information from the control file:
An archive log record is inserted each time the online redo log is archived successfully or cleared-the name column is null when the log is cleared. If the log is archived twice, two archive log records are inserted with the same thread#, sequence#, and first_change#, but with different names. An archive log record also is inserted when an archive log is restored from a backup set or a copy.
The V$BACKUP_CORRUPTION view shows information about corruptions in datafile backups from the control file. Corruptions are not tolerated in control file and archived log backups.
Column Name | Column Type |
---|---|
RECID |
NUMBER |
STAMP |
NUMBER |
SET_STAMP |
NUMBER |
SET_COUNT |
NUMBER |
PIECE# |
NUMBER |
FILE# |
NUMBER |
BLOCK# |
NUMBER |
BLOCKS |
NUMBER |
CORRUPTION_CHANGE# |
NUMBER |
MARKED_CORRUPT |
VARCHAR2(3) |
The V$bBACKUP_DATAFILE view shows backup datafile and backup control file information from the control file. A datafile backup set can contain one control file and multiple datafiles.
The new version 8 view, V$BACKUP_DEVICE, shows information about supported backup devices. If a device type does not support named devices, one row with the device type and a null device name is returned for that device type. If a device type supports named devices, one row is returned for each available device of that type. The special device type DISK is not returned by this view because it is always available.
Column Name | Column Type |
---|---|
DEVICE_TYPE |
VARCHAR2(17) |
DEVICE_NAME |
VARCHAR2(512) |
The new version 8 view, V$BACKUP_PIECE, shows information about backup pieces stored in the control file. Each backup set consist of one or more backup pieces.
The V$BACKUP_REDOLOG view shows information about archived logs in backup sets from the control file. Online redo logs cannot be backed up directly, they first must be archived to disk and then backed up. An archive log backup set can contain one or more archived logs.
The V$BACKUP_SET view shows backup set information from the control file. A backup set record is inserted after the backup set is completed successfully.
The new version 8 view, V$CONTROLFILE_RECORD_SECTION, shows information about the control file record sections.
Column name | Column type |
---|---|
TYPE |
VARCHAR2(17) |
RECORD_SIZE |
NUMBER |
RECORDS_TOTAL |
NUMBER |
RECORDS_USED |
NUMBER |
FIRST_INDEX |
NUMBER |
LAST_INDEX |
NUMBER |
LAST_RECID |
NUMBER |
The new version 8 view, V$COPY_CORRUPTION, shows information about datafile copy corruptions from the control file.
Column name | Column type |
---|---|
RECID |
NUMBER |
STAMP |
NUMBER |
COPY_RECID |
NUMBER |
COPY_STAMP |
NUMBER |
FILE# |
NUMBER |
BLOCK# |
NUMBER |
BLOCKS |
NUMBER |
CORRUPTION_CHANGE# |
NUMBER |
MARKED_CORRUPT |
VARCHAR2(3) |
The V$DATABASE view shows database information from the control file. The following V$DATABASE columns are new to version 8:
The V$DATAFILE view shows datafile information from the control file. The version 8 V$DATAFILE view shows the following new columns, in addition to the columns of the existing version 7 V$DATAFILE view. See also the V$DATAFILE_HEADER view, which shows information from datafile headers.
The V$DATAFILE_COPY view shows datafile copy information from the control file. A datafile copy record is inserted after the datafile (or datafile copy) is copied successfully or restored from a backup set.
The new version 8 view, V$DATAFILE_HEADER, shows datafile information from the datafile head.
The new version 8 view, V$DELETED_OBJECT, shows information about deleted archived logs, datafile copies, and backup pieces from the control file. The purpose of this view is to optimize the recovery catalog resync operation. When an archived log, datafile copy, or backup piece is deleted, the corresponding record is marked deleted.
Column Name | Column Type |
---|---|
RECID |
NUMBER |
STAMP |
NUMBER |
TYPE |
VARCHAR2(13) |
OBJECT_RECID |
NUMBER |
OBJECT_STAMP |
NUMBER |
The new version 8 view, V$INSTANCE, shows status information for the database instance. Returning only one row, it is incompatible with the version 7 view, V$INSTANCE, which returns one row per value. The STARTUP_TIME, LOGINS, and SHUTDOWN_PENDING columns return the same information as the version 7 version of the V$INSTANCE:
SVRMGR> select startup_time, logins, shutdown_pending from v$instance;
STARTUP_TIME |
LOGINS |
SHUTDOWN_PENDING |
96.05.29 20:29:38 |
ALLOWED |
NO |
KEY |
VALUE |
RESTRICTED MODE |
0 |
SHUTDOWN PENDING |
0 |
STARTUP TIME - JULIAN |
2450215 |
STARTUP TIME - SECONDS |
50407 |
4 rows selected. |
|
Although the version 8 V$INSTANCE view is not compatible with the version 7 V$INSTANCE view, it provides all of the same information, as well as additional information:
If the instance is not started, a query from this view signals ORA-1034.
The V$OFFLINE_RANGE view shows offline range information from the control file. The most recent offline range of each datafile is stored in the datafile record. V$OFFLINE_RANGE: Datafile offline range information from control file:
Column Name | Value |
RECID |
NUMBER |
STAMP |
NUMBER |
FILE# |
NUMBER |
OFFLINE_CHANGE# |
NUMBER |
ONLINE_CHANGE# |
NUMBER |
ONLINE_TIME# |
DATE |
The last offline range of each datafile is kept in the datafile record; see the V$DATAFILE view.
The new version 8 view, V$RESOURCE_LIMIT, displays information about global resource use for some of the system resources.
Column Name | Column Type |
---|---|
RESOURCE_NAME |
VARCHAR2(30) |
CURRENT_UTILIZATION |
NUMBER |
MAX_UTILIZATION |
NUMBER |
INITIAL_ALLOCATION |
VARCHAR2(10) |
LIMIT_VALUE |
VARCHAR2(10) |
The new version 8 view, V$TABLESPACE, shows tablespace information from the control file:
Column Name | Value | Description |
TS# |
NUMBER |
Tablespace number |
NAME |
VARCHAR2(30) |
Tablespace name |
The V$THREAD view contains thread information from the control file.
In version 8, the datatype of the following time stamp columns have been changed to DATE from version 7 VARCHAR2(20).
The primary goal of the Database Scheduling feature is to provide more control over the following:
Pre-Version 8 View Name | Version 8 Table Name |
---|---|
ALL_HISTOGRAMS |
ALL_TAB_HISTOGRAMS |
DBA_HISTOGRAMS |
DBA_TAB_HISTOGRAMS |
USER_HISTOGRAMS |
USER_TAB_HISTOGRAMS |