PDF file of Reference

PDF file of Reference
Oracle9i
Database Reference
Release 2 (9.2)
October 2002
Part No. A96536-02
Oracle9i Database Reference, Release 2 (9.2)
Part No. A96536-02
Copyright © 1996, 2002 Oracle Corporation. All rights reserved.
Primary Author:
Tony Morales
Contributing Author: Diana Lorentz
Contributors: Nipun Agarwal, Angela Amor, Rick Anderson, Lance Ashdown, Mark Bauer, Ruth
Baylis, Neerja Bhatt, Tudor Bosman, George Candea, Wilson Chan, Sumanta Chatterjee, Eugene Chong,
Michele Cyran, Mary Ann Davidson, Connie Dialeris Green, Harvey Eneman, Bruce Ernst, Ira
Greenberg, Steve Harris, Thuvan Hoang, Lilian Hobbs, Namit Jain, Hakkan Jakobsson, Bob Jenkins,
Mark Johnson, Jonathan Klein, Sushil Kumar, Tirthankar Lahiri, Bill Lee, Nina Lewis, Yunrui Li, Juan
Loaiza, Neil MacNaughton, Kant Patel, Shankar Raman, Ari Mozes, Subramanian Muralidhar, Ravi
Murthy, Karuna Muthiah, Arvind Nithrakashyap, Ronald Obermarck, Cetin Ozbutun, Christopher
Racicot, Mark Ramacher, Suvendu Ray, Ann Rhee, Vivian Schupmann, Harlan Sexton, Helen Slattery,
Ekrem Soylemez, Debbie Steiner, Seema Sundara, Juan Tellez, Alex Tsukerman, Kothanda
Umamageswaran, Randy Urbano, Steve Vivian, Eric Voss, Tak Wang, Steve Wertheimer, Andy
Witkowski, Daniel Wong, Graham Wood, Brian Wright, Aravind Yalamanchi, Qin Yu, Mohamed
Ziauddin
The Programs (which include both the software and documentation) contain proprietary information of
Oracle Corporation; they are provided under a license agreement containing restrictions on use and
disclosure and are also protected by copyright, patent and other intellectual and industrial property
laws. Reverse engineering, disassembly or decompilation of the Programs, except to the extent required
to obtain interoperability with other independently created software or as specified by law, is prohibited.
The information contained in this document is subject to change without notice. If you find any problems
in the documentation, please report them to us in writing. Oracle Corporation does not warrant that this
document is error-free. Except as may be expressly permitted in your license agreement for these
Programs, no part of these Programs may be reproduced or transmitted in any form or by any means,
electronic or mechanical, for any purpose, without the express written permission of Oracle Corporation.
If the Programs are delivered to the U.S. Government or anyone licensing or using the programs on
behalf of the U.S. Government, the following notice is applicable:
Restricted Rights Notice Programs delivered subject to the DOD FAR Supplement are "commercial
computer software" and use, duplication, and disclosure of the Programs, including documentation,
shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement.
Otherwise, Programs delivered subject to the Federal Acquisition Regulations are "restricted computer
software" and use, duplication, and disclosure of the Programs shall be subject to the restrictions in FAR
52.227-19, Commercial Computer Software - Restricted Rights (June, 1987). Oracle Corporation, 500
Oracle Parkway, Redwood City, CA 94065.
The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently
dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup,
redundancy, and other measures to ensure the safe use of such applications if the Programs are used for
such purposes, and Oracle Corporation disclaims liability for any damages caused by such use of the
Programs.
Oracle is a registered trademark, and Oracle Store, Oracle7, Oracle8, Oracle8i, Oracle9i, PL/SQL,
Pro*C/C++, SQL*Net, and SQL*Plus are trademarks or registered trademarks of Oracle Corporation.
Other names may be trademarks of their respective owners.
Contents
Send Us Your Comments .................................................................................................................. xli
Preface.......................................................................................................................................................... xliii
Audience .............................................................................................................................................. xliv
Organization........................................................................................................................................ xliv
Related Documentation ...................................................................................................................... xlv
Conventions......................................................................................................................................... xlvi
Documentation Accessibility ................................................................................................................. l
What’s New in Oracle9i Database Reference? ...................................................................... liii
Oracle9i Release 2 (9.2) New Features in Oracle9i Database Reference ....................................... liv
Oracle9i Release 1 (9.0.1) New Features in Oracle9i Database Reference ................................... lxii
1
Initialization Parameters
Uses of Initialization Parameters.....................................................................................................
Types of Initialization Parameters .............................................................................................
Parameter Files ....................................................................................................................................
Server Parameter Files .................................................................................................................
Initialization Parameter Files ......................................................................................................
Changing Parameter Values..............................................................................................................
Dynamic Parameters ....................................................................................................................
Displaying Current Parameter Values ....................................................................................
Parameters You Should Not Specify in the Parameter File..................................................
When Parameters Are Set Incorrectly .....................................................................................
1-2
1-2
1-4
1-4
1-4
1-7
1-8
1-11
1-11
1-12
iii
Reading the Parameter Descriptions.............................................................................................
Parameter Descriptions....................................................................................................................
ACTIVE_INSTANCE_COUNT ......................................................................................................
AQ_TM_PROCESSES......................................................................................................................
ARCHIVE_LAG_TARGET..............................................................................................................
AUDIT_FILE_DEST .........................................................................................................................
AUDIT_SYS_OPERATIONS ..........................................................................................................
AUDIT_TRAIL ..................................................................................................................................
BACKGROUND_CORE_DUMP ...................................................................................................
BACKGROUND_DUMP_DEST....................................................................................................
BACKUP_TAPE_IO_SLAVES ........................................................................................................
BITMAP_MERGE_AREA_SIZE ....................................................................................................
BLANK_TRIMMING.......................................................................................................................
BUFFER_POOL_KEEP .....................................................................................................................
BUFFER_POOL_RECYCLE.............................................................................................................
CIRCUITS...........................................................................................................................................
CLUSTER_DATABASE ...................................................................................................................
CLUSTER_DATABASE_INSTANCES..........................................................................................
CLUSTER_INTERCONNECTS .....................................................................................................
COMMIT_POINT_STRENGTH....................................................................................................
COMPATIBLE....................................................................................................................................
CONTROL_FILE_RECORD_KEEP_TIME ..................................................................................
CONTROL_FILES.............................................................................................................................
CORE_DUMP_DEST .......................................................................................................................
CPU_COUNT.....................................................................................................................................
CREATE_BITMAP_AREA_SIZE ...................................................................................................
CURSOR_SHARING .......................................................................................................................
CURSOR_SPACE_FOR_TIME.......................................................................................................
DB_nK_CACHE_SIZE .....................................................................................................................
DB_BLOCK_BUFFERS ....................................................................................................................
DB_BLOCK_CHECKING ...............................................................................................................
DB_BLOCK_CHECKSUM..............................................................................................................
DB_BLOCK_SIZE .............................................................................................................................
DB_CACHE_ADVICE .....................................................................................................................
DB_CACHE_SIZE.............................................................................................................................
iv
1-12
1-14
1-15
1-15
1-16
1-17
1-17
1-17
1-18
1-18
1-19
1-20
1-21
1-21
1-22
1-24
1-24
1-25
1-25
1-26
1-27
1-28
1-28
1-29
1-29
1-30
1-31
1-31
1-32
1-33
1-35
1-35
1-36
1-37
1-38
DB_CREATE_FILE_DEST...............................................................................................................
DB_CREATE_ONLINE_LOG_DEST_n........................................................................................
DB_DOMAIN....................................................................................................................................
DB_FILE_MULTIBLOCK_READ_COUNT.................................................................................
DB_FILE_NAME_CONVERT ........................................................................................................
DB_FILES ...........................................................................................................................................
DB_KEEP_CACHE_SIZE ................................................................................................................
DB_NAME .........................................................................................................................................
DB_RECYCLE_CACHE_SIZE........................................................................................................
DB_WRITER_PROCESSES ............................................................................................................
DBLINK_ENCRYPT_LOGIN.........................................................................................................
DBWR_IO_SLAVES .........................................................................................................................
DG_BROKER_CONFIG_FILEn.....................................................................................................
DG_BROKER_START .....................................................................................................................
DISK_ASYNCH_IO .........................................................................................................................
DISPATCHERS .................................................................................................................................
DISTRIBUTED_LOCK_TIMEOUT ..............................................................................................
DML_LOCKS ....................................................................................................................................
DRS_START ......................................................................................................................................
ENQUEUE_RESOURCES ...............................................................................................................
EVENT ................................................................................................................................................
FAL_CLIENT .....................................................................................................................................
FAL_SERVER.....................................................................................................................................
FAST_START_IO_TARGET ...........................................................................................................
FAST_START_MTTR_TARGET ....................................................................................................
FAST_START_PARALLEL_ROLLBACK .....................................................................................
FILE_MAPPING ...............................................................................................................................
FILESYSTEMIO_OPTIONS ...........................................................................................................
FIXED_DATE.....................................................................................................................................
GC_FILES_TO_LOCKS...................................................................................................................
GLOBAL_CONTEXT_POOL_SIZE ..............................................................................................
GLOBAL_NAMES............................................................................................................................
HASH_AREA_SIZE .........................................................................................................................
HASH_JOIN_ENABLED.................................................................................................................
HI_SHARED_MEMORY_ADDRESS...........................................................................................
1-38
1-39
1-39
1-40
1-41
1-43
1-44
1-44
1-45
1-45
1-46
1-46
1-47
1-48
1-48
1-49
1-53
1-53
1-54
1-55
1-56
1-56
1-57
1-57
1-58
1-59
1-59
1-60
1-60
1-60
1-62
1-62
1-63
1-64
1-64
v
HS_AUTOREGISTER......................................................................................................................
IFILE ....................................................................................................................................................
INSTANCE_GROUPS......................................................................................................................
INSTANCE_NAME ..........................................................................................................................
INSTANCE_NUMBER.....................................................................................................................
JAVA_MAX_SESSIONSPACE_SIZE.............................................................................................
JAVA_POOL_SIZE ............................................................................................................................
JAVA_SOFT_SESSIONSPACE_LIMIT.........................................................................................
JOB_QUEUE_PROCESSES.............................................................................................................
LARGE_POOL_SIZE........................................................................................................................
LICENSE_MAX_SESSIONS...........................................................................................................
LICENSE_MAX_USERS..................................................................................................................
LICENSE_SESSIONS_WARNING ...............................................................................................
LOCAL_LISTENER ..........................................................................................................................
LOCK_NAME_SPACE.....................................................................................................................
LOCK_SGA........................................................................................................................................
LOG_ARCHIVE_DEST ...................................................................................................................
LOG_ARCHIVE_DEST_n ...............................................................................................................
LOG_ARCHIVE_DEST_STATE_n ................................................................................................
LOG_ARCHIVE_DUPLEX_DEST.................................................................................................
LOG_ARCHIVE_FORMAT ............................................................................................................
LOG_ARCHIVE_MAX_PROCESSES...........................................................................................
LOG_ARCHIVE_MIN_SUCCEED_DEST...................................................................................
LOG_ARCHIVE_START.................................................................................................................
LOG_ARCHIVE_TRACE ................................................................................................................
LOG_BUFFER....................................................................................................................................
LOG_CHECKPOINT_INTERVAL.................................................................................................
LOG_CHECKPOINT_TIMEOUT..................................................................................................
LOG_CHECKPOINTS_TO_ALERT..............................................................................................
LOG_FILE_NAME_CONVERT .....................................................................................................
LOG_PARALLELISM ......................................................................................................................
LOGMNR_MAX_PERSISTENT_SESSIONS..............................................................................
MAX_COMMIT_PROPAGATION_DELAY................................................................................
MAX_DISPATCHERS......................................................................................................................
MAX_DUMP_FILE_SIZE ................................................................................................................
vi
1-64
1-65
1-66
1-67
1-67
1-68
1-68
1-69
1-69
1-70
1-71
1-72
1-72
1-73
1-74
1-74
1-75
1-76
1-78
1-79
1-80
1-81
1-82
1-83
1-84
1-85
1-86
1-87
1-88
1-88
1-90
1-90
1-91
1-92
1-93
MAX_ENABLED_ROLES ...............................................................................................................
MAX_ROLLBACK_SEGMENTS...................................................................................................
MAX_SHARED_SERVERS.............................................................................................................
NLS_CALENDAR.............................................................................................................................
NLS_COMP .......................................................................................................................................
NLS_CURRENCY .............................................................................................................................
NLS_DATE_FORMAT .....................................................................................................................
NLS_DATE_LANGUAGE...............................................................................................................
NLS_DUAL_CURRENCY ...............................................................................................................
NLS_ISO_CURRENCY....................................................................................................................
NLS_LANGUAGE............................................................................................................................
NLS_LENGTH_SEMANTICS......................................................................................................
NLS_NCHAR_CONV_EXCP .......................................................................................................
NLS_NUMERIC_CHARACTERS ...............................................................................................
NLS_SORT .......................................................................................................................................
NLS_TERRITORY ..........................................................................................................................
NLS_TIMESTAMP_FORMAT .....................................................................................................
NLS_TIMESTAMP_TZ_FORMAT ..............................................................................................
O7_DICTIONARY_ACCESSIBILITY.........................................................................................
OBJECT_CACHE_MAX_SIZE_PERCENT ................................................................................
OBJECT_CACHE_OPTIMAL_SIZE ...........................................................................................
OLAP_PAGE_POOL_SIZE ...........................................................................................................
OPEN_CURSORS...........................................................................................................................
OPEN_LINKS..................................................................................................................................
OPEN_LINKS_PER_INSTANCE.................................................................................................
OPTIMIZER_DYNAMIC_SAMPLING .....................................................................................
OPTIMIZER_FEATURES_ENABLE ...........................................................................................
OPTIMIZER_INDEX_CACHING ...............................................................................................
OPTIMIZER_INDEX_COST_ADJ ..............................................................................................
OPTIMIZER_MAX_PERMUTATIONS......................................................................................
OPTIMIZER_MODE......................................................................................................................
ORACLE_TRACE_COLLECTION_NAME ...............................................................................
ORACLE_TRACE_COLLECTION_PATH .................................................................................
ORACLE_TRACE_COLLECTION_SIZE...................................................................................
ORACLE_TRACE_ENABLE.........................................................................................................
1-94
1-94
1-94
1-95
1-96
1-96
1-97
1-98
1-98
1-99
1-99
1-100
1-100
1-101
1-101
1-102
1-103
1-104
1-104
1-105
1-106
1-106
1-107
1-107
1-108
1-109
1-109
1-112
1-113
1-113
1-114
1-115
1-116
1-116
1-117
vii
ORACLE_TRACE_FACILITY_NAME........................................................................................
ORACLE_TRACE_FACILITY_PATH..........................................................................................
OS_AUTHENT_PREFIX................................................................................................................
OS_ROLES .......................................................................................................................................
PARALLEL_ADAPTIVE_MULTI_USER ...................................................................................
PARALLEL_AUTOMATIC_TUNING ........................................................................................
PARALLEL_EXECUTION_MESSAGE_SIZE............................................................................
PARALLEL_INSTANCE_GROUP ...............................................................................................
PARALLEL_MAX_SERVERS .......................................................................................................
PARALLEL_MIN_PERCENT .......................................................................................................
PARALLEL_MIN_SERVERS ........................................................................................................
PARALLEL_THREADS_PER_CPU .............................................................................................
PARTITION_VIEW_ENABLED...................................................................................................
PGA_AGGREGATE_TARGET.....................................................................................................
PLSQL_COMPILER_FLAGS........................................................................................................
PLSQL_NATIVE_C_COMPILER.................................................................................................
PLSQL_NATIVE_LIBRARY_DIR................................................................................................
PLSQL_NATIVE_LIBRARY_SUBDIR_COUNT ......................................................................
PLSQL_NATIVE_LINKER............................................................................................................
PLSQL_NATIVE_MAKE_FILE_NAME .....................................................................................
PLSQL_NATIVE_MAKE_UTILITY ............................................................................................
PLSQL_V2_COMPATIBILITY .....................................................................................................
PRE_PAGE_SGA.............................................................................................................................
PROCESSES.....................................................................................................................................
QUERY_REWRITE_ENABLED....................................................................................................
QUERY_REWRITE_INTEGRITY ................................................................................................
RDBMS_SERVER_DN...................................................................................................................
READ_ONLY_OPEN_DELAYED ................................................................................................
RECOVERY_PARALLELISM .......................................................................................................
REMOTE_ARCHIVE_ENABLE ...................................................................................................
REMOTE_DEPENDENCIES_MODE .........................................................................................
REMOTE_LISTENER.....................................................................................................................
REMOTE_LOGIN_PASSWORDFILE ........................................................................................
REMOTE_OS_AUTHENT ............................................................................................................
REMOTE_OS_ROLES ...................................................................................................................
viii
1-117
1-118
1-119
1-120
1-120
1-121
1-122
1-122
1-123
1-124
1-125
1-126
1-126
1-127
1-128
1-129
1-129
1-129
1-130
1-130
1-131
1-131
1-132
1-133
1-133
1-134
1-135
1-136
1-136
1-137
1-138
1-138
1-139
1-140
1-140
REPLICATION_DEPENDENCY_TRACKING ........................................................................
RESOURCE_LIMIT........................................................................................................................
RESOURCE_MANAGER_PLAN ................................................................................................
ROLLBACK_SEGMENTS ............................................................................................................
ROW_LOCKING ............................................................................................................................
SERIAL _REUSE .............................................................................................................................
SERVICE_NAMES .........................................................................................................................
SESSION_CACHED_CURSORS ................................................................................................
SESSION_MAX_OPEN_FILES....................................................................................................
SESSIONS........................................................................................................................................
SGA_MAX_SIZE.............................................................................................................................
SHADOW_CORE_DUMP ............................................................................................................
SHARED_MEMORY_ADDRESS................................................................................................
SHARED_POOL_RESERVED_SIZE ..........................................................................................
SHARED_POOL_SIZE ..................................................................................................................
SHARED_SERVER_SESSIONS ..................................................................................................
SHARED_SERVERS ......................................................................................................................
SORT_AREA_RETAINED_SIZE .................................................................................................
SORT_AREA_SIZE.........................................................................................................................
SPFILE...............................................................................................................................................
SQL_TRACE ....................................................................................................................................
SQL92_SECURITY .........................................................................................................................
STANDBY_ARCHIVE_DEST ......................................................................................................
STANDBY_FILE_MANAGEMENT ............................................................................................
STAR_TRANSFORMATION_ENABLED .................................................................................
STATISTICS_LEVEL......................................................................................................................
TAPE_ASYNCH_IO .......................................................................................................................
THREAD...........................................................................................................................................
TIMED_OS_STATISTICS.............................................................................................................
TIMED_STATISTICS.....................................................................................................................
TRACE_ENABLED.........................................................................................................................
TRACEFILE_IDENTIFIER............................................................................................................
TRANSACTION_AUDITING .....................................................................................................
TRANSACTIONS...........................................................................................................................
TRANSACTIONS_PER_ROLLBACK_SEGMENT .................................................................
1-141
1-141
1-142
1-143
1-144
1-145
1-146
1-146
1-147
1-148
1-148
1-149
1-149
1-150
1-151
1-151
1-152
1-152
1-153
1-155
1-156
1-157
1-157
1-158
1-159
1-159
1-160
1-160
1-161
1-162
1-163
1-163
1-164
1-165
1-165
ix
UNDO_MANAGEMENT..............................................................................................................
UNDO_RETENTION.....................................................................................................................
UNDO_SUPPRESS_ERRORS......................................................................................................
UNDO_TABLESPACE ...................................................................................................................
USE_INDIRECT_DATA_BUFFERS ............................................................................................
USER_DUMP_DEST......................................................................................................................
UTL_FILE_DIR................................................................................................................................
WORKAREA_SIZE_POLICY .......................................................................................................
2
1-166
1-166
1-167
1-168
1-168
1-169
1-169
1-170
Static Data Dictionary Views
ALL_ALL_TABLES .............................................................................................................................
ALL_APPLY..........................................................................................................................................
ALL_APPLY_CONFLICT_COLUMNS...........................................................................................
ALL_APPLY_DML_HANDLERS...................................................................................................
ALL_APPLY_ERROR .......................................................................................................................
ALL_APPLY_KEY_COLUMNS ......................................................................................................
ALL_APPLY_PARAMETERS..........................................................................................................
ALL_APPLY_PROGRESS................................................................................................................
ALL_ARGUMENTS .........................................................................................................................
ALL_ASSOCIATIONS.....................................................................................................................
ALL_AUDIT_POLICIES..................................................................................................................
ALL_BASE_TABLE_MVIEWS .......................................................................................................
ALL_CAPTURE .................................................................................................................................
ALL_CAPTURE_PARAMETERS...................................................................................................
ALL_CAPTURE_PREPARED_DATABASE .................................................................................
ALL_CAPTURE_PREPARED_SCHEMAS...................................................................................
ALL_CAPTURE_PREPARED_TABLES........................................................................................
ALL_CATALOG ................................................................................................................................
ALL_CLUSTER_HASH_EXPRESSIONS .....................................................................................
ALL_CLUSTERS ...............................................................................................................................
ALL_COL_COMMENTS.................................................................................................................
ALL_COL_PRIVS .............................................................................................................................
ALL_COL_PRIVS_MADE...............................................................................................................
ALL_COL_PRIVS_RECD................................................................................................................
ALL_COLL_TYPES...........................................................................................................................
x
2-6
2-8
2-9
2-10
2-10
2-11
2-12
2-12
2-13
2-14
2-15
2-16
2-17
2-18
2-18
2-19
2-19
2-20
2-20
2-21
2-22
2-22
2-23
2-24
2-25
ALL_CONS_COLUMNS.................................................................................................................
ALL_CONS_OBJ_COLUMNS .......................................................................................................
ALL_CONSTRAINTS......................................................................................................................
ALL_CONTEXT ................................................................................................................................
ALL_DB_LINKS ...............................................................................................................................
ALL_DEF_AUDIT_OPTS................................................................................................................
ALL_DEPENDENCIES....................................................................................................................
ALL_DIM_ATTRIBUTES................................................................................................................
ALL_DIM_CHILD_OF ....................................................................................................................
ALL_DIM_HIERARCHIES.............................................................................................................
ALL_DIM_JOIN_KEY .....................................................................................................................
ALL_DIM_LEVEL_KEY ..................................................................................................................
ALL_DIM_LEVELS ..........................................................................................................................
ALL_DIMENSIONS.........................................................................................................................
ALL_DIRECTORIES........................................................................................................................
ALL_ERRORS ...................................................................................................................................
ALL_EVALUATION_CONTEXT_TABLES..................................................................................
ALL_EVALUATION_CONTEXT_VARS ......................................................................................
ALL_EVALUATION_CONTEXTS.................................................................................................
ALL_EXTERNAL_LOCATIONS....................................................................................................
ALL_EXTERNAL_TABLES.............................................................................................................
ALL_IND_COLUMNS.....................................................................................................................
ALL_IND_EXPRESSIONS..............................................................................................................
ALL_IND_PARTITIONS.................................................................................................................
ALL_IND_SUBPARTITIONS ........................................................................................................
ALL_INDEXES ..................................................................................................................................
ALL_INDEXTYPE_COMMENTS..................................................................................................
ALL_INDEXTYPE_OPERATORS..................................................................................................
ALL_INDEXTYPES ..........................................................................................................................
ALL_INTERNAL_TRIGGERS .......................................................................................................
ALL_JAVA_ARGUMENTS .............................................................................................................
ALL_JAVA_CLASSES ......................................................................................................................
ALL_JAVA_DERIVATIONS............................................................................................................
ALL_JAVA_FIELDS ..........................................................................................................................
ALL_JAVA_IMPLEMENTS.............................................................................................................
2-25
2-26
2-27
2-28
2-29
2-29
2-30
2-31
2-32
2-32
2-33
2-33
2-34
2-34
2-35
2-35
2-36
2-36
2-37
2-38
2-39
2-40
2-41
2-41
2-43
2-45
2-48
2-49
2-50
2-50
2-51
2-52
2-53
2-54
2-55
xi
ALL_JAVA_INNERS.........................................................................................................................
ALL_JAVA_LAYOUTS .....................................................................................................................
ALL_JAVA_METHODS ...................................................................................................................
ALL_JAVA_NCOMPS ......................................................................................................................
ALL_JAVA_RESOLVERS.................................................................................................................
ALL_JAVA_THROWS ......................................................................................................................
ALL_JOBS...........................................................................................................................................
ALL_JOIN_IND_COLUMNS .........................................................................................................
ALL_LIBRARIES...............................................................................................................................
ALL_LOB_PARTITIONS.................................................................................................................
ALL_LOB_SUBPARTITIONS ........................................................................................................
ALL_LOB_TEMPLATES..................................................................................................................
ALL_LOBS..........................................................................................................................................
ALL_LOG_GROUP_COLUMNS...................................................................................................
ALL_LOG_GROUPS........................................................................................................................
ALL_METHOD_PARAMS..............................................................................................................
ALL_METHOD_RESULTS .............................................................................................................
ALL_MVIEW_AGGREGATES.......................................................................................................
ALL_MVIEW_ANALYSIS...............................................................................................................
ALL_MVIEW_DETAIL_RELATIONS ..........................................................................................
ALL_MVIEW_JOINS .......................................................................................................................
ALL_MVIEW_KEYS.........................................................................................................................
ALL_MVIEW_LOGS........................................................................................................................
ALL_MVIEW_REFRESH_TIMES..................................................................................................
ALL_MVIEWS ...................................................................................................................................
ALL_NESTED_TABLES ..................................................................................................................
ALL_OBJ_COLATTRS.....................................................................................................................
ALL_OBJECT_TABLES....................................................................................................................
ALL_OBJECTS...................................................................................................................................
ALL_OPANCILLARY.......................................................................................................................
ALL_OPARGUMENTS....................................................................................................................
ALL_OPBINDINGS .........................................................................................................................
ALL_OPERATOR_COMMENTS...................................................................................................
ALL_OPERATORS ...........................................................................................................................
ALL_OUTLINE_HINTS ..................................................................................................................
xii
2-56
2-57
2-58
2-59
2-60
2-61
2-61
2-63
2-63
2-64
2-65
2-66
2-67
2-68
2-69
2-69
2-70
2-71
2-72
2-73
2-74
2-75
2-76
2-77
2-77
2-82
2-82
2-83
2-85
2-86
2-87
2-87
2-88
2-89
2-89
ALL_OUTLINES ...............................................................................................................................
ALL_PART_COL_STATISTICS .....................................................................................................
ALL_PART_HISTOGRAMS...........................................................................................................
ALL_PART_INDEXES .....................................................................................................................
ALL_PART_KEY_COLUMNS ........................................................................................................
ALL_PART_LOBS.............................................................................................................................
ALL_PART_TABLES ........................................................................................................................
ALL_PARTIAL_DROP_TABS ........................................................................................................
ALL_PENDING_CONV_TABLES ................................................................................................
ALL_POLICIES .................................................................................................................................
ALL_POLICY_CONTEXTS...........................................................................................................
ALL_POLICY_GROUPS ...............................................................................................................
ALL_PROCEDURES ......................................................................................................................
ALL_PROPAGATION ...................................................................................................................
ALL_PUBLISHED_COLUMNS ...................................................................................................
ALL_QUEUE_TABLES ..................................................................................................................
ALL_QUEUES .................................................................................................................................
ALL_REFRESH................................................................................................................................
ALL_REFRESH_CHILDREN .......................................................................................................
ALL_REFRESH_DEPENDENCIES .............................................................................................
ALL_REFS ........................................................................................................................................
ALL_REGISTERED_MVIEWS ....................................................................................................
ALL_REGISTRY_BANNERS .......................................................................................................
ALL_RULE_SET_RULES...............................................................................................................
ALL_RULE_SETS ...........................................................................................................................
ALL_RULES .....................................................................................................................................
ALL_SEQUENCES .........................................................................................................................
ALL_SOURCE .................................................................................................................................
ALL_SOURCE_TABLES................................................................................................................
ALL_SQLJ_TYPE_ATTRS.............................................................................................................
ALL_SQLJ_TYPE_METHODS.....................................................................................................
ALL_SQLJ_TYPES..........................................................................................................................
ALL_STORED_SETTINGS ..........................................................................................................
ALL_STREAMS_GLOBAL_RULES............................................................................................
ALL_STREAMS_SCHEMA_RULES...........................................................................................
2-90
2-91
2-92
2-92
2-94
2-95
2-96
2-98
2-98
2-99
2-100
2-101
2-101
2-102
2-103
2-103
2-105
2-105
2-106
2-107
2-108
2-108
2-109
2-110
2-110
2-111
2-112
2-112
2-113
2-113
2-114
2-115
2-116
2-117
2-118
xiii
ALL_STREAMS_TABLE_RULES ................................................................................................
ALL_SUBPART_COL_STATISTICS ...........................................................................................
ALL_SUBPART_HISTOGRAMS.................................................................................................
ALL_SUBPART_KEY_COLUMNS ..............................................................................................
ALL_SUBPARTITION_TEMPLATES .........................................................................................
ALL_SUBSCRIBED_COLUMNS.................................................................................................
ALL_SUBSCRIBED_TABLES.......................................................................................................
ALL_SUBSCRIPTIONS.................................................................................................................
ALL_SUMDELTA............................................................................................................................
ALL_SYNONYMS ..........................................................................................................................
ALL_TAB_COL_STATISTICS ......................................................................................................
ALL_TAB_COLUMNS...................................................................................................................
ALL_TAB_COMMENTS ...............................................................................................................
ALL_TAB_HISTOGRAMS ...........................................................................................................
ALL_TAB_MODIFICATIONS .....................................................................................................
ALL_TAB_PARTITIONS ...............................................................................................................
ALL_TAB_PRIVS ............................................................................................................................
ALL_TAB_PRIVS_MADE .............................................................................................................
ALL_TAB_PRIVS_RECD ..............................................................................................................
ALL_TAB_SUBPARTITIONS.......................................................................................................
ALL_TABLES ...................................................................................................................................
ALL_TRIGGER_COLS ..................................................................................................................
ALL_TRIGGERS .............................................................................................................................
ALL_TYPE_ATTRS.........................................................................................................................
ALL_TYPE_METHODS.................................................................................................................
ALL_TYPE_VERSIONS.................................................................................................................
ALL_TYPES......................................................................................................................................
ALL_UNUSED_COL_TABS..........................................................................................................
ALL_UPDATABLE_COLUMNS ..................................................................................................
ALL_USERS .....................................................................................................................................
ALL_USTATS...................................................................................................................................
ALL_VARRAYS ...............................................................................................................................
ALL_VIEWS .....................................................................................................................................
ALL_XML_SCHEMAS...................................................................................................................
ALL_XML_TAB_COLS ..................................................................................................................
xiv
2-119
2-121
2-122
2-123
2-124
2-124
2-125
2-125
2-126
2-126
2-127
2-128
2-130
2-130
2-131
2-132
2-133
2-134
2-135
2-136
2-137
2-140
2-141
2-142
2-143
2-144
2-144
2-145
2-146
2-146
2-147
2-148
2-148
2-149
2-150
ALL_XML_TABLES........................................................................................................................
ALL_XML_VIEW_COLS ...............................................................................................................
ALL_XML_VIEWS..........................................................................................................................
AUDIT_ACTIONS .........................................................................................................................
CATALOG ........................................................................................................................................
CAT ....................................................................................................................................................
CHAINED_ROWS..........................................................................................................................
CHANGE_SOURCES ....................................................................................................................
CHANGE_SETS..............................................................................................................................
CHANGE_TABLES ........................................................................................................................
CLU....................................................................................................................................................
CODE_PIECES ................................................................................................................................
CODE_SIZE .....................................................................................................................................
COL....................................................................................................................................................
COLS .................................................................................................................................................
COLUMN_PRIVILEGES...............................................................................................................
DATABASE_PROPERTIES...........................................................................................................
DBA_2PC_NEIGHBORS...............................................................................................................
DBA_2PC_PENDING ....................................................................................................................
DBA_ALL_TABLES........................................................................................................................
DBA_APPLICATION_ROLES .....................................................................................................
DBA_APPLY ....................................................................................................................................
DBA_APPLY_CONFLICT_COLUMNS......................................................................................
DBA_APPLY_DML_HANDLERS ...............................................................................................
DBA_APPLY_ERROR ....................................................................................................................
DBA_APPLY_INSTANTIATED_OBJECTS ...............................................................................
DBA_APPLY_KEY_COLUMNS...................................................................................................
DBA_APPLY_PARAMETERS ......................................................................................................
DBA_APPLY_PROGRESS ............................................................................................................
DBA_AQ_AGENT_PRIVS ...........................................................................................................
DBA_AQ_AGENTS .......................................................................................................................
DBA_ASSOCIATIONS .................................................................................................................
DBA_ATTRIBUTE_TRANSFORMATIONS.............................................................................
DBA_AUDIT_EXISTS ...................................................................................................................
DBA_AUDIT_OBJECT..................................................................................................................
2-151
2-151
2-152
2-153
2-153
2-153
2-153
2-154
2-154
2-155
2-155
2-156
2-156
2-156
2-156
2-156
2-156
2-157
2-157
2-158
2-158
2-158
2-159
2-159
2-159
2-159
2-160
2-160
2-160
2-160
2-161
2-161
2-161
2-162
2-163
xv
DBA_AUDIT_POLICIES...............................................................................................................
DBA_AUDIT_SESSION................................................................................................................
DBA_AUDIT_STATEMENT.........................................................................................................
DBA_AUDIT_TRAIL .....................................................................................................................
DBA_AW_PS....................................................................................................................................
DBA_AWS ........................................................................................................................................
DBA_BASE_TABLE_MVIEWS ....................................................................................................
DBA_BLOCKERS ...........................................................................................................................
DBA_CAPTURE..............................................................................................................................
DBA_CAPTURE_PARAMETERS................................................................................................
DBA_CAPTURE_PREPARED_DATABASE ..............................................................................
DBA_CAPTURE_PREPARED_SCHEMAS ...............................................................................
DBA_CAPTURE_PREPARED_TABLES.....................................................................................
DBA_CATALOG .............................................................................................................................
DBA_CLU_COLUMNS .................................................................................................................
DBA_CLUSTER_HASH_EXPRESSIONS..................................................................................
DBA_CLUSTERS ............................................................................................................................
DBA_COL_COMMENTS..............................................................................................................
DBA_COL_PRIVS ..........................................................................................................................
DBA_COLL_TYPES........................................................................................................................
DBA_CONS_COLUMNS..............................................................................................................
DBA_CONS_OBJ_COLUMNS ....................................................................................................
DBA_CONSTRAINTS...................................................................................................................
DBA_CONTEXT .............................................................................................................................
DBA_DATA_FILES.........................................................................................................................
DBA_DB_LINKS.............................................................................................................................
DBA_DDL_LOCKS ........................................................................................................................
DBA_DEPENDENCIES .................................................................................................................
DBA_DIM_ATTRIBUTES.............................................................................................................
DBA_DIM_CHILD_OF .................................................................................................................
DBA_DIM_HIERARCHIES..........................................................................................................
DBA_DIM_JOIN_KEY...................................................................................................................
DBA_DIM_LEVEL_KEY ...............................................................................................................
DBA_DIM_LEVELS .......................................................................................................................
DBA_DIMENSIONS......................................................................................................................
xvi
2-164
2-164
2-165
2-167
2-169
2-169
2-170
2-170
2-170
2-171
2-171
2-171
2-171
2-171
2-172
2-172
2-172
2-172
2-172
2-173
2-173
2-173
2-174
2-174
2-174
2-174
2-175
2-175
2-176
2-176
2-176
2-176
2-176
2-176
2-177
DBA_DIRECTORIES.....................................................................................................................
DBA_DML_LOCKS .......................................................................................................................
DBA_DMT_FREE_SPACE ............................................................................................................
DBA_DMT_USED_EXTENTS .....................................................................................................
DBA_ERRORS ................................................................................................................................
DBA_EVALUATION_CONTEXT_TABLES ..............................................................................
DBA_EVALUATION_CONTEXT_VARS...................................................................................
DBA_EVALUATION_CONTEXTS .............................................................................................
DBA_EXP_FILES.............................................................................................................................
DBA_EXP_OBJECTS......................................................................................................................
DBA_EXP_VERSION.....................................................................................................................
DBA_EXTENTS...............................................................................................................................
DBA_EXTERNAL_LOCATIONS ................................................................................................
DBA_EXTERNAL_TABLES..........................................................................................................
DBA_FGA_AUDIT_TRAIL ..........................................................................................................
DBA_FREE_SPACE ........................................................................................................................
DBA_FREE_SPACE_COALESCED.............................................................................................
DBA_IND_COLUMNS .................................................................................................................
DBA_IND_EXPRESSIONS...........................................................................................................
DBA_IND_PARTITIONS .............................................................................................................
DBA_IND_SUBPARTITIONS .....................................................................................................
DBA_INDEXES ...............................................................................................................................
DBA_INDEXTYPE_COMMENTS...............................................................................................
DBA_INDEXTYPE_OPERATORS ..............................................................................................
DBA_INDEXTYPES .......................................................................................................................
DBA_INTERNAL_TRIGGERS....................................................................................................
DBA_JAVA_ARGUMENTS ..........................................................................................................
DBA_JAVA_CLASSES ...................................................................................................................
DBA_JAVA_DERIVATIONS ........................................................................................................
DBA_JAVA_FIELDS.......................................................................................................................
DBA_JAVA_IMPLEMENTS..........................................................................................................
DBA_JAVA_INNERS .....................................................................................................................
DBA_JAVA_LAYOUTS ..................................................................................................................
DBA_JAVA_METHODS................................................................................................................
DBA_JAVA_NCOMPS...................................................................................................................
2-177
2-177
2-178
2-178
2-178
2-178
2-179
2-179
2-179
2-179
2-180
2-180
2-181
2-181
2-181
2-182
2-182
2-183
2-183
2-183
2-183
2-183
2-183
2-184
2-184
2-184
2-184
2-184
2-184
2-185
2-185
2-185
2-185
2-185
2-185
xvii
DBA_JAVA_POLICY ......................................................................................................................
DBA_JAVA_RESOLVERS .............................................................................................................
DBA_JAVA_THROWS...................................................................................................................
DBA_JOBS .......................................................................................................................................
DBA_JOBS_RUNNING.................................................................................................................
DBA_JOIN_IND_COLUMNS......................................................................................................
DBA_KGLLOCK.............................................................................................................................
DBA_LIBRARIES ...........................................................................................................................
DBA_LMT_FREE_SPACE .............................................................................................................
DBA_LMT_USED_EXTENTS ......................................................................................................
DBA_LOB_PARTITIONS .............................................................................................................
DBA_LOB_SUBPARTITIONS .....................................................................................................
DBA_LOB_TEMPLATES...............................................................................................................
DBA_LOBS.......................................................................................................................................
DBA_LOCK......................................................................................................................................
DBA_LOCK_INTERNAL..............................................................................................................
DBA_LOCKS ...................................................................................................................................
DBA_LOG_GROUP_COLUMNS................................................................................................
DBA_LOG_GROUPS.....................................................................................................................
DBA_LOGSTDBY_EVENTS ........................................................................................................
DBA_LOGSTDBY_LOG ...............................................................................................................
DBA_LOGSTDBY_NOT_UNIQUE ............................................................................................
DBA_LOGSTDBY_PARAMETERS ............................................................................................
DBA_LOGSTDBY_PROGRESS ..................................................................................................
DBA_LOGSTDBY_SKIP ...............................................................................................................
DBA_LOGSTDBY_SKIP_TRANSACTION..............................................................................
DBA_LOGSTDBY_UNSUPPORTED .........................................................................................
DBA_METHOD_PARAMS...........................................................................................................
DBA_METHOD_RESULTS ..........................................................................................................
DBA_MVIEW_AGGREGATES....................................................................................................
DBA_MVIEW_ANALYSIS............................................................................................................
DBA_MVIEW_DETAIL_RELATIONS .......................................................................................
DBA_MVIEW_JOINS ....................................................................................................................
DBA_MVIEW_KEYS......................................................................................................................
DBA_MVIEW_LOG_FILTER_COLS ..........................................................................................
xviii
2-186
2-186
2-187
2-187
2-187
2-187
2-188
2-188
2-188
2-188
2-189
2-189
2-189
2-189
2-189
2-190
2-190
2-191
2-191
2-191
2-191
2-192
2-193
2-194
2-195
2-195
2-196
2-196
2-196
2-196
2-197
2-197
2-197
2-197
2-197
DBA_MVIEW_LOGS.....................................................................................................................
DBA_MVIEW_REFRESH_TIMES ..............................................................................................
DBA_MVIEWS................................................................................................................................
DBA_NESTED_TABLES ...............................................................................................................
DBA_OBJ_AUDIT_OPTS .............................................................................................................
DBA_OBJ_COLATTRS..................................................................................................................
DBA_OBJECT_SIZE.......................................................................................................................
DBA_OBJECT_TABLES ................................................................................................................
DBA_OBJECTS ...............................................................................................................................
DBA_OPANCILLARY ...................................................................................................................
DBA_OPARGUMENTS ................................................................................................................
DBA_OPBINDINGS......................................................................................................................
DBA_OPERATOR_COMMENTS ...............................................................................................
DBA_OPERATORS ........................................................................................................................
DBA_ORPHAN_KEY_TABLE......................................................................................................
DBA_OUTLINE_HINTS ...............................................................................................................
DBA_OUTLINES............................................................................................................................
DBA_PART_COL_STATISTICS ..................................................................................................
DBA_PART_HISTOGRAMS .......................................................................................................
DBA_PART_INDEXES ..................................................................................................................
DBA_PART_KEY_COLUMNS.....................................................................................................
DBA_PART_LOBS..........................................................................................................................
DBA_PART_TABLES .....................................................................................................................
DBA_PARTIAL_DROP_TABS .....................................................................................................
DBA_PENDING_CONV_TABLES .............................................................................................
DBA_PENDING_TRANSACTIONS..........................................................................................
DBA_POLICIES ..............................................................................................................................
DBA_POLICY_CONTEXTS .........................................................................................................
DBA_POLICY_GROUPS ..............................................................................................................
DBA_PRIV_AUDIT_OPTS...........................................................................................................
DBA_PROCEDURES .....................................................................................................................
DBA_PROFILES .............................................................................................................................
DBA_PROPAGATION ..................................................................................................................
DBA_PROXIES ...............................................................................................................................
DBA_PUBLISHED_COLUMNS..................................................................................................
2-198
2-198
2-198
2-198
2-198
2-199
2-200
2-200
2-200
2-200
2-201
2-201
2-201
2-201
2-201
2-202
2-202
2-202
2-202
2-202
2-203
2-203
2-203
2-203
2-203
2-203
2-204
2-204
2-204
2-204
2-205
2-205
2-205
2-205
2-206
xix
DBA_QUEUE_SCHEDULES ........................................................................................................
DBA_QUEUE_TABLES..................................................................................................................
DBA_QUEUES.................................................................................................................................
DBA_RCHILD .................................................................................................................................
DBA_REFRESH...............................................................................................................................
DBA_REFRESH_CHILDREN.......................................................................................................
DBA_REFS .......................................................................................................................................
DBA_REGISTERED_MVIEW_GROUPS ..................................................................................
DBA_REGISTERED_MVIEWS ...................................................................................................
DBA_REGISTRY.............................................................................................................................
DBA_REGISTRY_HIERARCHY..................................................................................................
DBA_REPAIR_TABLE ...................................................................................................................
DBA_RESUMABLE........................................................................................................................
DBA_RGROUP ...............................................................................................................................
DBA_ROLE_PRIVS........................................................................................................................
DBA_ROLES....................................................................................................................................
DBA_ROLLBACK_SEGS..............................................................................................................
DBA_RSRC_CONSUMER_GROUP_PRIVS ............................................................................
DBA_RSRC_CONSUMER_GROUPS ........................................................................................
DBA_RSRC_MANAGER_SYSTEM_PRIVS .............................................................................
DBA_RSRC_PLAN_DIRECTIVES..............................................................................................
DBA_RSRC_PLANS.......................................................................................................................
DBA_RULE_SET_RULES..............................................................................................................
DBA_RULE_SETS...........................................................................................................................
DBA_RULES ....................................................................................................................................
DBA_SEGMENTS ..........................................................................................................................
DBA_SEQUENCES.........................................................................................................................
DBA_SOURCE ................................................................................................................................
DBA_SOURCE_TABLES...............................................................................................................
DBA_SQLJ_TYPE_ATTRS ............................................................................................................
DBA_SQLJ_TYPE_METHODS....................................................................................................
DBA_SQLJ_TYPES .........................................................................................................................
DBA_STMT_AUDIT_OPTS .........................................................................................................
DBA_STORED_SETTINGS .........................................................................................................
DBA_STREAMS_GLOBAL_RULES...........................................................................................
xx
2-207
2-208
2-208
2-209
2-209
2-209
2-209
2-209
2-210
2-210
2-211
2-212
2-213
2-214
2-215
2-215
2-215
2-216
2-217
2-217
2-218
2-219
2-220
2-220
2-220
2-220
2-221
2-222
2-222
2-222
2-222
2-222
2-222
2-223
2-223
DBA_STREAMS_SCHEMA_RULES..........................................................................................
DBA_STREAMS_TABLE_RULES...............................................................................................
DBA_SUBPART_COL_STATISTICS ..........................................................................................
DBA_SUBPART_HISTOGRAMS ...............................................................................................
DBA_SUBPART_KEY_COLUMNS.............................................................................................
DBA_SUBPARTITION_TEMPLATES........................................................................................
DBA_SUBSCRIBED_COLUMNS ...............................................................................................
DBA_SUBSCRIBED_TABLES .....................................................................................................
DBA_SUBSCRIPTIONS ...............................................................................................................
DBA_SYNONYMS .........................................................................................................................
DBA_SYS_PRIVS ...........................................................................................................................
DBA_TAB_COL_STATISTICS.....................................................................................................
DBA_TAB_COLUMNS..................................................................................................................
DBA_TAB_COMMENTS ..............................................................................................................
DBA_TAB_HISTOGRAMS ..........................................................................................................
DBA_TAB_MODIFICATIONS ....................................................................................................
DBA_TAB_PARTITIONS..............................................................................................................
DBA_TAB_PRIVS...........................................................................................................................
DBA_TAB_SUBPARTITIONS .....................................................................................................
DBA_TABLES..................................................................................................................................
DBA_TABLESPACES.....................................................................................................................
DBA_TEMP_FILES.........................................................................................................................
DBA_TRANSFORMATIONS ......................................................................................................
DBA_TRIGGER_COLS .................................................................................................................
DBA_TRIGGERS............................................................................................................................
DBA_TS_QUOTAS ........................................................................................................................
DBA_TYPE_ATTRS........................................................................................................................
DBA_TYPE_METHODS ...............................................................................................................
DBA_TYPE_VERSIONS ...............................................................................................................
DBA_TYPES.....................................................................................................................................
DBA_UNDO_EXTENTS ...............................................................................................................
DBA_UNUSED_COL_TABS ........................................................................................................
DBA_UPDATABLE_COLUMNS .................................................................................................
DBA_USERS....................................................................................................................................
DBA_USTATS .................................................................................................................................
2-223
2-224
2-224
2-224
2-224
2-224
2-224
2-225
2-225
2-225
2-225
2-226
2-226
2-226
2-226
2-226
2-226
2-227
2-227
2-227
2-228
2-229
2-230
2-230
2-230
2-230
2-231
2-231
2-231
2-231
2-232
2-232
2-232
2-233
2-234
xxi
DBA_VARRAYS ..............................................................................................................................
DBA_VIEWS....................................................................................................................................
DBA_WAITERS...............................................................................................................................
DBA_XML_SCHEMAS..................................................................................................................
DBA_XML_TAB_COLS .................................................................................................................
DBA_XML_TABLES.......................................................................................................................
DBA_XML_VIEW_COLS ..............................................................................................................
DBA_XML_VIEWS.........................................................................................................................
DBMS_ALERT_INFO ....................................................................................................................
DBMS_LOCK_ALLOCATED.......................................................................................................
DEPTREE..........................................................................................................................................
DICT ..................................................................................................................................................
DICT_COLUMNS...........................................................................................................................
DICTIONARY .................................................................................................................................
ERROR_SIZE ...................................................................................................................................
EXCEPTIONS ..................................................................................................................................
FILE_LOCK ......................................................................................................................................
FILE_PING .......................................................................................................................................
FILEXT$ ............................................................................................................................................
GLOBAL_NAME ............................................................................................................................
HS_ALL_CAPS................................................................................................................................
HS_ALL_DD ....................................................................................................................................
HS_ALL_INITS ...............................................................................................................................
HS_BASE_CAPS .............................................................................................................................
HS_BASE_DD .................................................................................................................................
HS_CLASS_CAPS...........................................................................................................................
HS_CLASS_DD...............................................................................................................................
HS_CLASS_INIT ............................................................................................................................
HS_EXTERNAL_OBJECT_PRIVILEGES...................................................................................
HS_EXTERNAL_OBJECTS...........................................................................................................
HS_EXTERNAL_USER_PRIVILEGES .......................................................................................
HS_FDS_CLASS .............................................................................................................................
HS_FDS_INST.................................................................................................................................
HS_INST_CAPS..............................................................................................................................
HS_INST_DD ..................................................................................................................................
xxii
2-234
2-234
2-234
2-234
2-235
2-235
2-235
2-235
2-235
2-236
2-236
2-236
2-236
2-237
2-237
2-237
2-237
2-238
2-239
2-240
2-240
2-240
2-241
2-241
2-241
2-242
2-242
2-243
2-243
2-243
2-244
2-244
2-244
2-245
2-245
HS_INST_INIT ...............................................................................................................................
IDEPTREE ........................................................................................................................................
IND ....................................................................................................................................................
INDEX_HISTOGRAM ..................................................................................................................
INDEX_STATS ................................................................................................................................
MAP_OBJECT .................................................................................................................................
NLS_DATABASE_PARAMETERS..............................................................................................
NLS_INSTANCE_PARAMETERS...............................................................................................
NLS_SESSION_PARAMETERS ..................................................................................................
OBJ.....................................................................................................................................................
PARSED_PIECES............................................................................................................................
PARSED_SIZE.................................................................................................................................
PLAN_TABLE ..................................................................................................................................
PLUGGABLE_SET_CHECK.........................................................................................................
PRODUCT_COMPONENT_VERSION.....................................................................................
PROXY_USERS ...............................................................................................................................
PSTUBTBL .......................................................................................................................................
PUBLIC_DEPENDENCY...............................................................................................................
PUBLICSYN.....................................................................................................................................
QUEUE_PRIVILEGES ...................................................................................................................
RESOURCE_COST.........................................................................................................................
RESOURCE_MAP ..........................................................................................................................
ROLE_ROLE_PRIVS......................................................................................................................
ROLE_SYS_PRIVS .........................................................................................................................
ROLE_TAB_PRIVS.........................................................................................................................
SEQ ....................................................................................................................................................
SESSION_CONTEXT ....................................................................................................................
SESSION_PRIVS............................................................................................................................
SESSION_ROLES...........................................................................................................................
SOURCE_SIZE ................................................................................................................................
STMT_AUDIT_OPTION_MAP...................................................................................................
SYN....................................................................................................................................................
SYSCATALOG.................................................................................................................................
SYSFILES..........................................................................................................................................
SYSSEGOBJ .....................................................................................................................................
2-246
2-246
2-247
2-247
2-247
2-248
2-249
2-249
2-249
2-250
2-250
2-250
2-250
2-252
2-253
2-253
2-254
2-254
2-254
2-255
2-255
2-255
2-256
2-256
2-256
2-256
2-257
2-257
2-257
2-257
2-258
2-258
2-258
2-258
2-258
xxiii
SYSTEM_PRIVILEGE_MAP ........................................................................................................
SYS_OBJECTS .................................................................................................................................
TAB ....................................................................................................................................................
TABLE_PRIVILEGE_MAP............................................................................................................
TABLE_PRIVILEGES.....................................................................................................................
TABS ..................................................................................................................................................
TABQUOTAS...................................................................................................................................
TRUSTED_SERVERS.....................................................................................................................
TS_PITR_CHECK ...........................................................................................................................
TS_PITR_OBJECTS_TO_BE_DROPPED...................................................................................
UNI_PLUGGABLE_SET_CHECK ...............................................................................................
USER_ALL_TABLES ......................................................................................................................
USER_AQ_AGENT_PRIVS..........................................................................................................
USER_ARGUMENTS ....................................................................................................................
USER_ASSOCIATIONS................................................................................................................
USER_ATTRIBUTE_TRANSFORMATIONS ...........................................................................
USER_AUDIT_OBJECT ................................................................................................................
USER_AUDIT_POLICIES.............................................................................................................
USER_AUDIT_SESSION..............................................................................................................
USER_AUDIT_STATEMENT.......................................................................................................
USER_AUDIT_TRAIL ...................................................................................................................
USER_AW_PS ..................................................................................................................................
USER_AWS ......................................................................................................................................
USER_BASE_TABLE_MVIEWS ..................................................................................................
USER_CATALOG ...........................................................................................................................
USER_CLU_COLUMNS................................................................................................................
USER_CLUSTER_HASH_EXPRESSIONS ................................................................................
USER_CLUSTERS ..........................................................................................................................
USER_COL_COMMENTS............................................................................................................
USER_COL_PRIVS.........................................................................................................................
USER_COL_PRIVS_MADE..........................................................................................................
USER_COL_PRIVS_RECD ...........................................................................................................
USER_COLL_TYPES......................................................................................................................
USER_CONS_COLUMNS ............................................................................................................
USER_CONS_OBJ_COLUMNS...................................................................................................
xxiv
2-258
2-259
2-259
2-259
2-259
2-260
2-260
2-260
2-261
2-262
2-262
2-263
2-263
2-263
2-264
2-264
2-264
2-264
2-264
2-264
2-265
2-265
2-265
2-265
2-266
2-266
2-266
2-266
2-266
2-266
2-267
2-267
2-267
2-267
2-267
USER_CONSTRAINTS.................................................................................................................
USER_DB_LINKS...........................................................................................................................
USER_DEPENDENCIES ...............................................................................................................
USER_DIM_ATTRIBUTES...........................................................................................................
USER_DIM_CHILD_OF ...............................................................................................................
USER_DIM_HIERARCHIES........................................................................................................
USER_DIM_JOIN_KEY.................................................................................................................
USER_DIM_LEVEL_KEY .............................................................................................................
USER_DIM_LEVELS .....................................................................................................................
USER_DIMENSIONS....................................................................................................................
USER_ERRORS...............................................................................................................................
USER_EVALUATION_CONTEXT_TABLES.............................................................................
USER_EVALUATION_CONTEXT_VARS .................................................................................
USER_EVALUATION_CONTEXTS............................................................................................
USER_EXTENTS.............................................................................................................................
USER_EXTERNAL_LOCATIONS...............................................................................................
USER_EXTERNAL_TABLES ........................................................................................................
USER_FREE_SPACE ......................................................................................................................
USER_IND_COLUMNS................................................................................................................
USER_IND_EXPRESSIONS.........................................................................................................
USER_IND_PARTITIONS............................................................................................................
USER_IND_SUBPARTITIONS ...................................................................................................
USER_INDEXES .............................................................................................................................
USER_INDEXTYPE_COMMENTS.............................................................................................
USER_INDEXTYPE_OPERATORS.............................................................................................
USER_INDEXTYPES .....................................................................................................................
USER_INTERNAL_TRIGGERS ..................................................................................................
USER_JAVA_ARGUMENTS ........................................................................................................
USER_JAVA_CLASSES .................................................................................................................
USER_JAVA_DERIVATIONS.......................................................................................................
USER_JAVA_FIELDS .....................................................................................................................
USER_JAVA_IMPLEMENTS........................................................................................................
USER_JAVA_INNERS....................................................................................................................
USER_JAVA_LAYOUTS ................................................................................................................
USER_JAVA_METHODS ..............................................................................................................
2-268
2-268
2-268
2-268
2-268
2-268
2-269
2-269
2-269
2-269
2-269
2-269
2-270
2-270
2-270
2-270
2-270
2-271
2-271
2-271
2-271
2-271
2-271
2-272
2-272
2-272
2-272
2-272
2-273
2-273
2-273
2-273
2-273
2-274
2-274
xxv
USER_JAVA_NCOMPS .................................................................................................................
USER_JAVA_POLICY ....................................................................................................................
USER_JAVA_RESOLVERS............................................................................................................
USER_JAVA_THROWS .................................................................................................................
USER_JOBS......................................................................................................................................
USER_JOIN_IND_COLUMNS ....................................................................................................
USER_LIBRARIES..........................................................................................................................
USER_LOB_PARTITIONS............................................................................................................
USER_LOB_SUBPARTITIONS ...................................................................................................
USER_LOB_TEMPLATES.............................................................................................................
USER_LOBS.....................................................................................................................................
USER_LOG_GROUP_COLUMNS..............................................................................................
USER_LOG_GROUPS ...................................................................................................................
USER_METHOD_PARAMS.........................................................................................................
USER_METHOD_RESULTS ........................................................................................................
USER_MVIEW_AGGREGATES..................................................................................................
USER_MVIEW_ANALYSIS..........................................................................................................
USER_MVIEW_DETAIL_RELATIONS .....................................................................................
USER_MVIEW_JOINS ..................................................................................................................
USER_MVIEW_KEYS....................................................................................................................
USER_MVIEW_LOGS ...................................................................................................................
USER_MVIEW_REFRESH_TIMES.............................................................................................
USER_MVIEWS ..............................................................................................................................
USER_NESTED_TABLES..............................................................................................................
USER_OBJ_AUDIT_OPTS ...........................................................................................................
USER_OBJ_COLATTRS ................................................................................................................
USER_OBJECT_SIZE .....................................................................................................................
USER_OBJECT_TABLES...............................................................................................................
USER_OBJECTS..............................................................................................................................
USER_OPANCILLARY ..................................................................................................................
USER_OPARGUMENTS...............................................................................................................
USER_OPBINDINGS ....................................................................................................................
USER_OPERATOR_COMMENTS..............................................................................................
USER_OPERATORS ......................................................................................................................
USER_OUTLINE_HINTS .............................................................................................................
xxvi
2-274
2-274
2-274
2-275
2-275
2-275
2-275
2-275
2-275
2-276
2-276
2-276
2-276
2-276
2-276
2-277
2-277
2-277
2-277
2-277
2-278
2-278
2-278
2-278
2-278
2-278
2-279
2-279
2-279
2-279
2-279
2-279
2-279
2-280
2-280
USER_OUTLINES ..........................................................................................................................
USER_PART_COL_STATISTICS ................................................................................................
USER_PART_HISTOGRAMS......................................................................................................
USER_PART_INDEXES.................................................................................................................
USER_PART_KEY_COLUMNS ...................................................................................................
USER_PART_LOBS ........................................................................................................................
USER_PART_TABLES ...................................................................................................................
USER_PARTIAL_DROP_TABS ...................................................................................................
USER_PASSWORD_LIMITS .......................................................................................................
USER_PENDING_CONV_TABLES............................................................................................
USER_POLICIES ............................................................................................................................
USER_POLICY_CONTEXTS........................................................................................................
USER_POLICY_GROUPS.............................................................................................................
USER_PROCEDURES ...................................................................................................................
USER_PROXIES..............................................................................................................................
USER_PUBLISHED_COLUMNS ................................................................................................
USER_QUEUE_SCHEDULES ......................................................................................................
USER_QUEUE_TABLES................................................................................................................
USER_QUEUES...............................................................................................................................
USER_REFRESH.............................................................................................................................
USER_REFRESH_CHILDREN.....................................................................................................
USER_REFS .....................................................................................................................................
USER_REGISTERED_MVIEWS .................................................................................................
USER_REGISTRY...........................................................................................................................
USER_RESOURCE_LIMITS ........................................................................................................
USER_RESUMABLE......................................................................................................................
USER_ROLE_PRIVS......................................................................................................................
USER_RSRC_CONSUMER_GROUP_PRIVS ..........................................................................
USER_RSRC_MANAGER_SYSTEM_PRIVS ...........................................................................
USER_RULE_SET_RULES............................................................................................................
USER_RULE_SETS.........................................................................................................................
USER_RULES ..................................................................................................................................
USER_SEGMENTS ........................................................................................................................
USER_SEQUENCES.......................................................................................................................
USER_SOURCE ..............................................................................................................................
2-280
2-280
2-280
2-280
2-281
2-281
2-281
2-281
2-281
2-282
2-282
2-282
2-282
2-282
2-283
2-283
2-283
2-283
2-284
2-284
2-284
2-284
2-284
2-284
2-285
2-285
2-285
2-285
2-286
2-286
2-286
2-286
2-286
2-286
2-287
xxvii
USER_SOURCE_TABLES .............................................................................................................
USER_SQLJ_TYPE_ATTRS ..........................................................................................................
USER_SQLJ_TYPE_METHODS ..................................................................................................
USER_SQLJ_TYPES .......................................................................................................................
USER_STORED_SETTINGS........................................................................................................
USER_SUBPART_COL_STATISTICS ........................................................................................
USER_SUBPART_HISTOGRAMS..............................................................................................
USER_SUBPART_KEY_COLUMNS ...........................................................................................
USER_SUBPARTITION_TEMPLATES ......................................................................................
USER_SUBSCRIBED_COLUMNS..............................................................................................
USER_SUBSCRIBED_TABLES....................................................................................................
USER_SUBSCRIPTIONS..............................................................................................................
USER_SYNONYMS .......................................................................................................................
USER_SYS_PRIVS..........................................................................................................................
USER_TAB_COL_STATISTICS ...................................................................................................
USER_TAB_COLUMNS ................................................................................................................
USER_TAB_COMMENTS ............................................................................................................
USER_TAB_HISTOGRAMS ........................................................................................................
USER_TAB_MODIFICATIONS...................................................................................................
USER_TAB_PARTITIONS ............................................................................................................
USER_TAB_PRIVS .........................................................................................................................
USER_TAB_PRIVS_MADE ..........................................................................................................
USER_TAB_PRIVS_RECD............................................................................................................
USER_TAB_SUBPARTITIONS....................................................................................................
USER_TABLES ................................................................................................................................
USER_TABLESPACES ...................................................................................................................
USER_TRANSFORMATIONS.....................................................................................................
USER_TRIGGER_COLS ...............................................................................................................
USER_TRIGGERS ..........................................................................................................................
USER_TS_QUOTAS.......................................................................................................................
USER_TYPE_ATTRS ......................................................................................................................
USER_TYPE_METHODS..............................................................................................................
USER_TYPE_VERSIONS..............................................................................................................
USER_TYPES ...................................................................................................................................
USER_UNUSED_COL_TABS.......................................................................................................
xxviii
2-287
2-287
2-287
2-287
2-287
2-288
2-288
2-288
2-288
2-288
2-289
2-289
2-289
2-289
2-289
2-289
2-289
2-290
2-290
2-290
2-290
2-290
2-291
2-291
2-291
2-291
2-291
2-292
2-292
2-292
2-292
2-292
2-292
2-293
2-293
USER_UPDATABLE_COLUMNS ...............................................................................................
USER_USERS ..................................................................................................................................
USER_USTATS................................................................................................................................
USER_VARRAYS ............................................................................................................................
USER_VIEWS..................................................................................................................................
USER_XML_SCHEMAS................................................................................................................
USER_XML_TAB_COLS ...............................................................................................................
USER_XML_TABLES.....................................................................................................................
USER_XML_VIEW_COLS ............................................................................................................
USER_XML_VIEWS.......................................................................................................................
3
2-293
2-293
2-293
2-293
2-294
2-294
2-294
2-294
2-294
2-294
Dynamic Performance (V$) Views
About Dynamic Performance Views .........................................................................................
V$ Views ........................................................................................................................................
GV$ Views .....................................................................................................................................
V$ACCESS ...........................................................................................................................................
V$ACTIVE_INSTANCES..................................................................................................................
V$ACTIVE_SESS_POOL_MTH ......................................................................................................
V$AQ.....................................................................................................................................................
V$ARCHIVE........................................................................................................................................
V$ARCHIVE_DEST ...........................................................................................................................
V$ARCHIVE_DEST_STATUS .........................................................................................................
V$ARCHIVE_GAP ...........................................................................................................................
V$ARCHIVE_PROCESSES ............................................................................................................
V$ARCHIVED_LOG .......................................................................................................................
V$BACKUP........................................................................................................................................
V$BACKUP_ASYNC_IO.................................................................................................................
V$BACKUP_CORRUPTION .........................................................................................................
V$BACKUP_DATAFILE..................................................................................................................
V$BACKUP_DEVICE ......................................................................................................................
V$BACKUP_PIECE ..........................................................................................................................
V$BACKUP_REDOLOG.................................................................................................................
V$BACKUP_SET ..............................................................................................................................
V$BACKUP_SPFILE ........................................................................................................................
V$BACKUP_SYNC_IO....................................................................................................................
3-1
3-2
3-2
3-4
3-4
3-4
3-4
3-5
3-5
3-8
3-10
3-10
3-10
3-12
3-13
3-14
3-15
3-16
3-17
3-18
3-18
3-20
3-20
xxix
V$BGPROCESS.................................................................................................................................
V$BH ...................................................................................................................................................
V$BUFFER_POOL ............................................................................................................................
V$BUFFER_POOL_STATISTICS...................................................................................................
V$CACHE...........................................................................................................................................
V$CACHE_LOCK .............................................................................................................................
V$CACHE_TRANSFER...................................................................................................................
V$CIRCUIT........................................................................................................................................
V$CLASS_CACHE_TRANSFER ...................................................................................................
V$COMPATIBILITY ........................................................................................................................
V$COMPATSEG ...............................................................................................................................
V$CONTEXT .....................................................................................................................................
V$CONTROLFILE............................................................................................................................
V$CONTROLFILE_RECORD_SECTION ...................................................................................
V$COPY_CORRUPTION................................................................................................................
V$CR_BLOCK_SERVER .................................................................................................................
V$DATABASE ...................................................................................................................................
V$DATABASE_BLOCK_CORRUPTION ....................................................................................
V$DATABASE_INCARNATION ..................................................................................................
V$DATAFILE .....................................................................................................................................
V$DATAFILE_COPY........................................................................................................................
V$DATAFILE_HEADER..................................................................................................................
V$DATAGUARD_STATUS ............................................................................................................
V$DB_CACHE_ADVICE ................................................................................................................
V$DB_OBJECT_CACHE .................................................................................................................
V$DB_PIPES ......................................................................................................................................
V$DBFILE...........................................................................................................................................
V$DBLINK .........................................................................................................................................
V$DELETED_OBJECT.....................................................................................................................
V$DISPATCHER ...............................................................................................................................
V$DISPATCHER_RATE ..................................................................................................................
V$ENABLEDPRIVS .........................................................................................................................
V$ENQUEUE_LOCK .......................................................................................................................
V$ENQUEUE_STAT .........................................................................................................................
V$EVENT_NAME.............................................................................................................................
xxx
3-21
3-21
3-23
3-24
3-25
3-26
3-29
3-30
3-31
3-31
3-32
3-32
3-32
3-32
3-33
3-34
3-35
3-38
3-39
3-39
3-41
3-42
3-43
3-44
3-45
3-46
3-46
3-46
3-47
3-47
3-48
3-53
3-53
3-54
3-55
V$EXECUTION.................................................................................................................................
V$FALSE_PING ................................................................................................................................
V$FAST_START_SERVERS ...........................................................................................................
V$FAST_START_TRANSACTIONS ............................................................................................
V$FILE_CACHE_TRANSFER........................................................................................................
V$FILESTAT ......................................................................................................................................
V$FIXED_TABLE ..............................................................................................................................
V$FIXED_VIEW_DEFINITION.....................................................................................................
V$GC_ELEMENT .............................................................................................................................
V$GC_ELEMENTS_WITH_COLLISIONS .................................................................................
V$GCSHVMASTER_INFO ............................................................................................................
V$GCSPFMASTER_INFO..............................................................................................................
V$GES_BLOCKING_ENQUEUE ..................................................................................................
V$GES_CONVERT_LOCAL ..........................................................................................................
V$GES_CONVERT_REMOTE.......................................................................................................
V$GES_ENQUEUE...........................................................................................................................
V$GES_LATCH.................................................................................................................................
V$GES_RESOURCE.........................................................................................................................
V$GES_STATISTICS .......................................................................................................................
V$GLOBAL_BLOCKED_LOCKS .................................................................................................
V$GLOBAL_TRANSACTION.......................................................................................................
V$HS_AGENT...................................................................................................................................
V$HS_PARAMETER........................................................................................................................
V$HS_SESSION ...............................................................................................................................
V$HVMASTER_INFO.....................................................................................................................
V$INDEXED_FIXED_COLUMN...................................................................................................
V$INSTANCE....................................................................................................................................
V$INSTANCE_RECOVERY ...........................................................................................................
V$LATCH ...........................................................................................................................................
V$LATCH_CHILDREN...................................................................................................................
V$LATCH_MISSES..........................................................................................................................
V$LATCH_PARENT.........................................................................................................................
V$LATCHHOLDER .........................................................................................................................
V$LATCHNAME ..............................................................................................................................
V$LIBRARY_CACHE_MEMORY .................................................................................................
3-55
3-55
3-56
3-57
3-57
3-58
3-59
3-59
3-60
3-60
3-61
3-61
3-61
3-63
3-63
3-64
3-65
3-65
3-66
3-66
3-66
3-67
3-67
3-68
3-68
3-68
3-69
3-70
3-71
3-72
3-73
3-74
3-74
3-74
3-75
xxxi
V$LIBRARYCACHE.........................................................................................................................
V$LICENSE........................................................................................................................................
V$LOADISTAT .................................................................................................................................
V$LOADPSTAT.................................................................................................................................
V$LOCK..............................................................................................................................................
V$LOCK_ACTIVITY .......................................................................................................................
V$LOCKED_OBJECT ......................................................................................................................
V$LOG ................................................................................................................................................
V$LOG_HISTORY............................................................................................................................
V$LOGFILE........................................................................................................................................
V$LOGHIST ......................................................................................................................................
V$LOGMNR_CONTENTS .............................................................................................................
V$LOGMNR_DICTIONARY .........................................................................................................
V$LOGMNR_LOGS.........................................................................................................................
V$LOGMNR_PARAMETERS ........................................................................................................
V$LOGSTDBY...................................................................................................................................
V$LOGSTDBY_STATS....................................................................................................................
V$MANAGED_STANDBY.............................................................................................................
V$MAP_COMP_LIST ......................................................................................................................
V$MAP_ELEMENT ..........................................................................................................................
V$MAP_EXT_ELEMENT ................................................................................................................
V$MAP_FILE .....................................................................................................................................
V$MAP_FILE_EXTENT ...................................................................................................................
V$MAP_FILE_IO_STACK ..............................................................................................................
V$MAP_LIBRARY............................................................................................................................
V$MAP_SUBELEMENT..................................................................................................................
V$MTTR_TARGET_ADVICE ........................................................................................................
V$MYSTAT.........................................................................................................................................
V$NLS_PARAMETERS ...................................................................................................................
V$NLS_VALID_VALUES ................................................................................................................
V$OBJECT_DEPENDENCY ...........................................................................................................
V$OBJECT_USAGE .........................................................................................................................
V$OBSOLETE_PARAMETER ........................................................................................................
V$OFFLINE_RANGE.......................................................................................................................
V$OPEN_CURSOR ..........................................................................................................................
xxxii
3-75
3-76
3-76
3-76
3-77
3-79
3-79
3-80
3-81
3-81
3-82
3-82
3-84
3-85
3-86
3-86
3-87
3-87
3-89
3-89
3-90
3-91
3-91
3-92
3-92
3-93
3-93
3-94
3-95
3-95
3-95
3-96
3-96
3-96
3-97
V$OPTION.........................................................................................................................................
V$PARALLEL_DEGREE_LIMIT_MTH .......................................................................................
V$PARAMETER ...............................................................................................................................
V$PARAMETER2 .............................................................................................................................
V$PGA_TARGET_ADVICE .........................................................................................................
V$PGA_TARGET_ADVICE_HISTOGRAM ............................................................................
V$PGASTAT ....................................................................................................................................
V$PQ_SESSTAT ..............................................................................................................................
V$PQ_SLAVE ..................................................................................................................................
V$PQ_SYSSTAT..............................................................................................................................
V$PQ_TQSTAT ...............................................................................................................................
V$PROCESS ....................................................................................................................................
V$PROXY_ARCHIVEDLOG .......................................................................................................
V$PROXY_DATAFILE ...................................................................................................................
V$PWFILE_USERS.........................................................................................................................
V$PX_PROCESS .............................................................................................................................
V$PX_PROCESS_SYSSTAT .........................................................................................................
V$PX_SESSION ..............................................................................................................................
V$PX_SESSTAT...............................................................................................................................
V$QUEUE.........................................................................................................................................
V$QUEUEING_MTH.....................................................................................................................
V$RECOVER_FILE.........................................................................................................................
V$RECOVERY_FILE_STATUS ....................................................................................................
V$RECOVERY_LOG......................................................................................................................
V$RECOVERY_PROGRESS.........................................................................................................
V$RECOVERY_STATUS ...............................................................................................................
V$REQDIST.....................................................................................................................................
V$RESERVED_WORDS ...............................................................................................................
V$RESOURCE.................................................................................................................................
V$RESOURCE_LIMIT...................................................................................................................
V$RMAN_CONFIGURATION....................................................................................................
V$ROLLNAME ...............................................................................................................................
V$ROLLSTAT ..................................................................................................................................
V$ROWCACHE ..............................................................................................................................
V$ROWCACHE_PARENT............................................................................................................
3-97
3-98
3-98
3-99
3-100
3-101
3-103
3-106
3-106
3-107
3-108
3-109
3-110
3-111
3-113
3-113
3-113
3-115
3-115
3-116
3-116
3-116
3-117
3-117
3-118
3-118
3-119
3-119
3-120
3-120
3-121
3-121
3-122
3-122
3-123
xxxiii
V$ROWCACHE_SUBORDINATE ..............................................................................................
V$RSRC_CONSUMER_GROUP.................................................................................................
V$RSRC_CONSUMER_GROUP_CPU_MTH ..........................................................................
V$RSRC_PLAN ...............................................................................................................................
V$RSRC_PLAN_CPU_MTH.........................................................................................................
V$SEGMENT_STATISTICS .........................................................................................................
V$SEGSTAT .....................................................................................................................................
V$SEGSTAT_NAME ......................................................................................................................
V$SESS_IO.......................................................................................................................................
V$SESSION .....................................................................................................................................
V$SESSION_CONNECT_INFO ..................................................................................................
V$SESSION_CURSOR_CACHE .................................................................................................
V$SESSION_EVENT .....................................................................................................................
V$SESSION_LONGOPS...............................................................................................................
V$SESSION_OBJECT_CACHE ...................................................................................................
V$SESSION_WAIT ........................................................................................................................
V$SESSTAT ......................................................................................................................................
V$SGA...............................................................................................................................................
V$SGA_CURRENT_RESIZE_OPS..............................................................................................
V$SGA_RESIZE_OPS....................................................................................................................
V$SGA_DYNAMIC_COMPONENTS .......................................................................................
V$SGA_DYNAMIC_FREE_MEMORY.......................................................................................
V$SGASTAT ....................................................................................................................................
V$SHARED_POOL_ADVICE......................................................................................................
V$SHARED_POOL_RESERVED.................................................................................................
V$SHARED_SERVER ....................................................................................................................
V$SHARED_SERVER_MONITOR.............................................................................................
V$SORT_SEGMENT......................................................................................................................
V$SPPARAMETER.........................................................................................................................
V$SQL ...............................................................................................................................................
V$SQL_BIND_DATA.....................................................................................................................
V$SQL_BIND_METADATA .........................................................................................................
V$SQL_CURSOR............................................................................................................................
V$SQL_PLAN..................................................................................................................................
V$SQL_PLAN_STATISTICS ........................................................................................................
xxxiv
3-124
3-124
3-125
3-126
3-126
3-127
3-127
3-127
3-128
3-128
3-133
3-134
3-134
3-135
3-136
3-137
3-138
3-139
3-139
3-140
3-140
3-141
3-141
3-142
3-142
3-143
3-144
3-145
3-146
3-146
3-148
3-149
3-149
3-150
3-152
V$SQL_PLAN_STATISTICS_ALL ..............................................................................................
V$SQL_REDIRECTION................................................................................................................
V$SQL_SHARED_CURSOR........................................................................................................
V$SQL_SHARED_MEMORY ......................................................................................................
V$SQL_WORKAREA ....................................................................................................................
V$SQL_WORKAREA_ACTIVE ..................................................................................................
V$SQL_WORKAREA_HISTOGRAM .......................................................................................
V$SQLAREA ...................................................................................................................................
V$SQLTEXT.....................................................................................................................................
V$SQLTEXT_WITH_NEWLINES ...............................................................................................
V$STANDBY_LOG ........................................................................................................................
V$STATISTICS_LEVEL.................................................................................................................
V$STATNAME ................................................................................................................................
V$STREAMS_APPLY_COORDINATOR ..................................................................................
V$STREAMS_APPLY_READER .................................................................................................
V$STREAMS_APPLY_SERVER...................................................................................................
V$STREAMS_CAPTURE..............................................................................................................
V$SUBCACHE ................................................................................................................................
V$SYSSTAT .....................................................................................................................................
V$SYSTEM_CURSOR_CACHE ..................................................................................................
V$SYSTEM_EVENT.......................................................................................................................
V$SYSTEM_PARAMETER...........................................................................................................
V$SYSTEM_PARAMETER2.........................................................................................................
V$TABLESPACE .............................................................................................................................
V$TEMP_CACHE_TRANSFER ...................................................................................................
V$TEMP_EXTENT_MAP..............................................................................................................
V$TEMP_EXTENT_POOL............................................................................................................
V$TEMP_SPACE_HEADER .........................................................................................................
V$TEMPFILE ...................................................................................................................................
V$TEMPORARY_LOBS ................................................................................................................
V$TEMPSEG_USAGE ...................................................................................................................
V$TEMPSTAT .................................................................................................................................
V$THREAD .....................................................................................................................................
V$TIMER..........................................................................................................................................
V$TIMEZONE_NAMES ...............................................................................................................
3-153
3-156
3-157
3-158
3-159
3-160
3-162
3-163
3-164
3-165
3-165
3-166
3-167
3-168
3-169
3-170
3-172
3-174
3-174
3-175
3-175
3-176
3-177
3-178
3-178
3-179
3-180
3-180
3-181
3-181
3-181
3-182
3-183
3-184
3-184
xxxv
V$TRANSACTION ........................................................................................................................
V$TRANSACTION_ENQUEUE..................................................................................................
V$TYPE_SIZE ..................................................................................................................................
V$UNDOSTAT ................................................................................................................................
V$VERSION ....................................................................................................................................
V$VPD_POLICY .............................................................................................................................
V$WAITSTAT ..................................................................................................................................
4
3-184
3-185
3-186
3-187
3-188
3-188
3-189
Database Limits
Datatype Limits ...................................................................................................................................
Physical Database Limits...................................................................................................................
Logical Database Limits.....................................................................................................................
Process and Runtime Limits .............................................................................................................
5
SQL Scripts
Creating the Data Dictionary............................................................................................................
Creating Additional Data Dictionary Structures..........................................................................
The "NO" Scripts.................................................................................................................................
Database Migration Scripts...............................................................................................................
Java Scripts ...........................................................................................................................................
A
4-2
4-2
4-3
4-4
5-2
5-3
5-6
5-7
5-8
Oracle Wait Events
Displaying Wait Events ..................................................................................................................... A-2
Wait Events and Parameters.............................................................................................................. A-2
Parameter Descriptions................................................................................................................... A-14
Wait Event Descriptions ................................................................................................................. A-16
alter system set dispatchers...................................................................................................... A-17
batched allocate scn lock request............................................................................................. A-17
BFILE check if exists .................................................................................................................. A-17
BFILE check if open ................................................................................................................... A-17
BFILE closure.............................................................................................................................. A-18
BFILE get length......................................................................................................................... A-18
BFILE get name object............................................................................................................... A-18
BFILE get path object................................................................................................................. A-18
xxxvi
BFILE internal seek.....................................................................................................................
BFILE open ..................................................................................................................................
BFILE read ...................................................................................................................................
buffer busy waits ........................................................................................................................
buffer deadlock ...........................................................................................................................
buffer for checkpoint..................................................................................................................
buffer latch...................................................................................................................................
buffer read retry..........................................................................................................................
checkpoint completed ................................................................................................................
checkpoint range buffer not saved...........................................................................................
control file parallel write ...........................................................................................................
control file sequential read ........................................................................................................
control file single write ..............................................................................................................
conversion file read ....................................................................................................................
db file parallel read.....................................................................................................................
db file parallel write ..................................................................................................................
db file scattered read .................................................................................................................
db file sequential read ...............................................................................................................
db file single write .....................................................................................................................
DFS db file lock ...........................................................................................................................
DFS lock handle .........................................................................................................................
direct path read ..........................................................................................................................
direct path write .........................................................................................................................
dispatcher shutdown ................................................................................................................
dispatcher timer .........................................................................................................................
duplicate cluster key ..................................................................................................................
enqueue ........................................................................................................................................
file identify...................................................................................................................................
file open........................................................................................................................................
free buffer waits ..........................................................................................................................
free global transaction table entry............................................................................................
free process state object..............................................................................................................
global cache busy........................................................................................................................
global cache lock cleanup .........................................................................................................
global cache freelist wait ...........................................................................................................
A-19
A-19
A-19
A-20
A-20
A-20
A-21
A-21
A-22
A-22
A-22
A-23
A-23
A-24
A-24
A-24
A-25
A-25
A-25
A-26
A-26
A-26
A-27
A-27
A-28
A-28
A-28
A-29
A-29
A-29
A-29
A-30
A-30
A-30
A-31
xxxvii
global cache null to s .................................................................................................................
global cache null to x .................................................................................................................
global cache open s ....................................................................................................................
global cache open x....................................................................................................................
global cache s to x ......................................................................................................................
inactive session ..........................................................................................................................
inactive transaction branch ......................................................................................................
index block split ........................................................................................................................
instance recovery ......................................................................................................................
instance state change ................................................................................................................
io done ........................................................................................................................................
kcl bg acks ..................................................................................................................................
latch activity ...............................................................................................................................
latch free .....................................................................................................................................
library cache load lock .............................................................................................................
library cache lock ......................................................................................................................
library cache pin ........................................................................................................................
lock manager wait for remote message .................................................................................
log buffer space .........................................................................................................................
log file parallel write ................................................................................................................
log file sequential read .............................................................................................................
log file single write ...................................................................................................................
log file switch (archiving needed) ..........................................................................................
log file switch (checkpoint incomplete) .................................................................................
log file switch (clearing log file) ..............................................................................................
log file switch completion ........................................................................................................
log file sync ................................................................................................................................
log switch/archive ....................................................................................................................
on-going SCN fetch to complete .............................................................................................
parallel execution create server ..............................................................................................
parallel execution dequeue wait .............................................................................................
parallel execution qref latch ....................................................................................................
parallel execution server shutdown .......................................................................................
parallel execution signal server ..............................................................................................
pending global transaction(s) ..................................................................................................
xxxviii
A-31
A-31
A-31
A-32
A-32
A-32
A-33
A-33
A-33
A-34
A-34
A-34
A-35
A-35
A-36
A-36
A-37
A-37
A-37
A-38
A-38
A-38
A-39
A-39
A-39
A-39
A-39
A-40
A-40
A-40
A-40
A-41
A-41
A-41
A-42
pipe get ........................................................................................................................................
pipe put .......................................................................................................................................
PL/SQL lock timer ....................................................................................................................
pmon rdomain attach ................................................................................................................
pmon timer .................................................................................................................................
process startup ...........................................................................................................................
queue messages ..........................................................................................................................
rdbms ipc message ....................................................................................................................
rdbms ipc message block ..........................................................................................................
rdbms ipc reply ..........................................................................................................................
redo wait .....................................................................................................................................
row cache lock ............................................................................................................................
scginq AST call ...........................................................................................................................
single-task message ...................................................................................................................
smon timer ..................................................................................................................................
SQL*Net break/reset to client .................................................................................................
SQL*Net break/reset to dblink ................................................................................................
SQL*Net message from client ..................................................................................................
SQL*Net message from dblink ................................................................................................
SQL*Net message to client .......................................................................................................
SQL*Net message to dblink .....................................................................................................
SQL*Net more data from client ...............................................................................................
SQL*Net more data from dblink .............................................................................................
SQL*Net more data to client ....................................................................................................
SQL*Net more data to dblink ..................................................................................................
switch logfile command ............................................................................................................
timer in sksawat .........................................................................................................................
transaction ..................................................................................................................................
unbound tx .................................................................................................................................
undo segment extension ...........................................................................................................
undo segment recovery ............................................................................................................
undo segment tx slot .................................................................................................................
virtual circuit status ...................................................................................................................
WMON goes to sleep ................................................................................................................
write complete waits .................................................................................................................
A-42
A-42
A-43
A-43
A-43
A-43
A-44
A-44
A-44
A-44
A-45
A-45
A-45
A-45
A-46
A-46
A-46
A-47
A-47
A-47
A-47
A-48
A-48
A-48
A-49
A-49
A-49
A-49
A-50
A-50
A-50
A-50
A-51
A-51
A-51
xxxix
writes stopped by instance recovery or database suspension ........................................... A-51
B
Oracle Enqueue Names
C
Statistics Descriptions
Displaying Statistics .................................................................................................................... C-1
Statistics Descriptions....................................................................................................................... C-2
Index
xl
Send Us Your Comments
Oracle9i Database Reference, Release 2 (9.2)
Part No. A96536-02
Oracle Corporation welcomes your comments and suggestions on the quality and usefulness of this
document. Your input is an important part of the information used for revision.
■
■
■
■
■
Did you find any errors?
Is the information clearly presented?
Do you need more information? If so, where?
Are the examples correct? Do you need more examples?
What features did you like most?
If you find any errors or have any other suggestions for improvement, please indicate the document
title and part number, and the chapter, section, and page number (if available). You can send comments to us in the following ways:
■
■
■
Electronic mail: [email protected]
FAX: (650) 506-7227 Attn: Server Technologies Documentation Manager
Postal service:
Oracle Corporation
Server Technologies Documentation
500 Oracle Parkway, Mailstop 4op11
Redwood Shores, CA 94065
USA
If you would like a reply, please give your name, address, telephone number, and (optionally) electronic mail address.
If you have problems with the software, please contact your local Oracle Support Services.
xli
xlii
Preface
This manual provides reference information about database initialization
parameters, static data dictionary views, dynamic performance views, database
limits, and SQL scripts that are part of the Oracle database system.
Oracle9i Database Reference contains information that describes the features and
functionality of the Oracle9i (also known as the standard edition) and the Oracle9i
Enterprise Edition products. Oracle9i and the Oracle9i Enterprise Edition have the
same basic features. However, several advanced features are available only with the
Enterprise Edition, and some of these are optional. For example, to use application
failover, you must have the Enterprise Edition with the Oracle9i Real Application
Clusters option.
See Also: Oracle9i Database New Features for information about the
differences between Oracle9i and the Oracle9i Enterprise Edition
and the features and options that are available to you.
This preface contains these topics:
■
Audience
■
Organization
■
Related Documentation
■
Conventions
■
Documentation Accessibility
xliii
Audience
Oracle9i Database Reference is intended for database administrators, system
administrators, and database application developers.
To use this document, you need TO BE FAMILIAR WITH THE FOLLOWING:
■
Oracle database management system (DBMS) concepts
■
Your operating system environment
Organization
This document contains:
Chapter 1, "Initialization Parameters"
This chapter describes the database initialization parameters you can specify in the
parameter file to start or configure an instance.
Chapter 2, "Static Data Dictionary Views"
This chapter describes the Oracle data dictionary tables and views, also known as
static data dictionary views.
Chapter 3, "Dynamic Performance (V$) Views"
This chapter describes the dynamic performance views, also known as the V$
views.
Chapter 4, "Database Limits"
This chapter lists the limits of values associated with database functions and objects.
Chapter 5, "SQL Scripts"
This chapter describes the SQL scripts that are required for optimal operation of the
Oracle database server.
Appendix A, "Oracle Wait Events"
This appendix describes some event names, wait times, and parameters for wait
events displayed by the V$SESSION_WAIT and V$SYSTEM_EVENT views.
Appendix B, "Oracle Enqueue Names"
This appendix lists some enqueues used by Oracle9i.
xliv
Appendix C, "Statistics Descriptions"
This appendix describes some statistics stored in the V$SESSION_WAIT and
V$SYSSTAT dynamic performance views.
Related Documentation
For more information, see these Oracle resources:
■
■
■
■
■
Oracle9i Database Concepts for a comprehensive introduction to the concepts and
terminology used in this manual
Oracle9i Database Administrator’s Guide for information about administering the
Oracle database server
Oracle9i Database Migration for the procedures for upgrading a previous release
of Oracle to the new Oracle9i release
Oracle9i SQL Reference for information on Oracle’s SQL commands and
functions
Oracle9i Application Developer’s Guide - Fundamentals for information about
developing database applications within the Oracle database server
Many of the examples in this book use the sample schemas of the seed database,
which is installed by default when you install Oracle. Refer to Oracle9i Sample
Schemas for information on how these schemas were created and how you can use
them yourself.
In North America, printed documentation is available for sale in the Oracle Store at
http://oraclestore.oracle.com/
Customers in Europe, the Middle East, and Africa (EMEA) can purchase
documentation from
http://www.oraclebookshop.com/
Other customers can contact their Oracle representative to purchase printed
documentation.
To download free release notes, installation documentation, white papers, or other
collateral, please visit the Oracle Technology Network (OTN). You must register
online before using OTN; registration is free and can be done at
http://otn.oracle.com/admin/account/membership.html
xlv
If you already have a username and password for OTN, then you can go directly to
the documentation section of the OTN Web site at
http://otn.oracle.com/docs/index.htm
To access the database documentation search engine directly, please visit
http://tahiti.oracle.com
Conventions
This section describes the conventions used in the text and code examples of this
documentation set. It describes:
■
Conventions in Text
■
Conventions in Code Examples
■
Conventions for Microsoft Windows Operating Systems
Conventions in Text
We use various conventions in text to help you more quickly identify special terms.
The following table describes those conventions and provides examples of their use.
Convention
Meaning
Bold
Bold typeface indicates terms that are
When you specify this clause, you create an
defined in the text or terms that appear in index-organized table.
a glossary, or both.
Italics
Italic typeface indicates book titles or
emphasis.
Oracle9i Database Concepts
Uppercase monospace typeface indicates
elements supplied by the system. Such
elements include parameters, privileges,
datatypes, RMAN keywords, SQL
keywords, SQL*Plus or utility commands,
packages and methods, as well as
system-supplied column names, database
objects and structures, usernames, and
roles.
You can specify this clause only for a NUMBER
column.
UPPERCASE
monospace
(fixed-width
font)
xlvi
Example
Ensure that the recovery catalog and target
database do not reside on the same disk.
You can back up the database by using the
BACKUP command.
Query the TABLE_NAME column in the USER_
TABLES data dictionary view.
Use the DBMS_STATS.GENERATE_STATS
procedure.
Convention
Meaning
Example
lowercase
monospace
(fixed-width
font)
Lowercase monospace typeface indicates
executables, filenames, directory names,
and sample user-supplied elements. Such
elements include computer and database
names, net service names, and connect
identifiers, as well as user-supplied
database objects and structures, column
names, packages and classes, usernames
and roles, program units, and parameter
values.
Enter sqlplus to open SQL*Plus.
Lowercase monospace italic font
represents placeholders or variables.
You can specify the parallel_clause.
The password is specified in the orapwd file.
Back up the datafiles and control files in the
/disk1/oracle/dbs directory.
The department_id, department_name, and
location_id columns are in the
hr.departments table.
Set the QUERY_REWRITE_ENABLED initialization
parameter to true.
Note: Some programmatic elements use a
mixture of UPPERCASE and lowercase.
Connect as oe user.
Enter these elements as shown.
The JRepUtil class implements these methods.
lowercase
monospace
(fixed-width
font) italic
Run Uold_release.SQL where old_release
refers to the release you installed prior to
upgrading.
Conventions in Code Examples
Code examples illustrate SQL, PL/SQL, SQL*Plus, or other command-line
statements. They are displayed in a monospace (fixed-width) font and separated
from normal text as shown in this example:
SELECT username FROM dba_users WHERE username = ’MIGRATE’;
The following table describes typographic conventions used in code examples and
provides examples of their use.
Convention
Meaning
Example
[ ]
Brackets enclose one or more optional
items. Do not enter the brackets.
DECIMAL (digits [ , precision ])
{ }
Braces enclose two or more items, one of
which is required. Do not enter the
braces.
{ENABLE | DISABLE}
|
A vertical bar represents a choice of two
{ENABLE | DISABLE}
or more options within brackets or braces. [COMPRESS | NOCOMPRESS]
Enter one of the options. Do not enter the
vertical bar.
xlvii
Convention
Meaning
...
Horizontal ellipsis points indicate either:
■
■
.
.
.
That we have omitted parts of the
code that are not directly related to
the example
That you can repeat a portion of the
code
Vertical ellipsis points indicate that we
have omitted several lines of code not
directly related to the example.
Example
CREATE TABLE ... AS subquery;
SELECT col1, col2, ... , coln FROM
employees;
SQL> SELECT NAME FROM V$DATAFILE;
NAME
-----------------------------------/fsl/dbs/tbs_01.dbf
/fs1/dbs/tbs_02.dbf
.
.
.
/fsl/dbs/tbs_09.dbf
9 rows selected.
Other notation
You must enter symbols other than
brackets, braces, vertical bars, and ellipsis
points as shown.
Italics
Italicized text indicates placeholders or
variables for which you must supply
particular values.
CONNECT SYSTEM/system_password
DB_NAME = database_name
UPPERCASE
Uppercase typeface indicates elements
supplied by the system. We show these
terms in uppercase in order to distinguish
them from terms you define. Unless terms
appear in brackets, enter them in the
order and with the spelling shown.
However, because these terms are not
case sensitive, you can enter them in
lowercase.
SELECT last_name, employee_id FROM
employees;
SELECT * FROM USER_TABLES;
DROP TABLE hr.employees;
lowercase
Lowercase typeface indicates
programmatic elements that you supply.
For example, lowercase indicates names
of tables, columns, or files.
SELECT last_name, employee_id FROM
employees;
sqlplus hr/hr
CREATE USER mjones IDENTIFIED BY ty3MU9;
Note: Some programmatic elements use a
mixture of UPPERCASE and lowercase.
Enter these elements as shown.
xlviii
acctbal NUMBER(11,2);
acct
CONSTANT NUMBER(4) := 3;
Conventions for Microsoft Windows Operating Systems
The following table describes conventions for Microsoft Windows operating
systems and provides examples of their use.
Convention
Meaning
Example
Choose Start >
How to start a program.
To start the Oracle Database Configuration
Assistant, choose Start > Programs > Oracle HOME_NAME > Configuration and Migration
Tools > Database Configuration Assistant.
c:\winnt"\"system32 is the same as
File and directory File and directory names are not case
names
sensitive. The following special characters C:\WINNT\SYSTEM32
are not allowed: left angle bracket (<),
right angle bracket (>), colon (:), double
quotation marks ("), slash (/), pipe (|),
and dash (-). The special character
backslash (\) is treated as an element
separator, even when it appears in quotes.
If the file name begins with \\, then
Windows assumes it uses the Universal
Naming Convention.
C:\>
HOME_NAME
Represents the Windows command
prompt of the current hard disk drive.
The escape character in a command
prompt is the caret (^). Your prompt
reflects the subdirectory in which you are
working. Referred to as the command
prompt in this manual.
C:\oracle\oradata>
The backslash (\) special character is
sometimes required as an escape
character for the double quotation mark
(") special character at the Windows
command prompt. Parentheses and the
single quotation mark (’) do not require
an escape character. Refer to your
Windows operating system
documentation for more information on
escape and special characters.
C:\>exp scott/tiger TABLES=emp
QUERY=\"WHERE job=’SALESMAN’ and
sal<1600\"
C:\>impSYSTEM/passwordFROMUSER=scott
TABLES=(emp, dept)
Represents the Oracle home name. The
C:\> net start OracleHOME_
home name can be up to 16 alphanumeric NAMETNSListener
characters. The only special character
allowed in the home name is the
underscore.
xlix
Convention
Meaning
Example
ORACLE_HOME
and ORACLE_
BASE
In releases prior to Oracle8i release 8.1.3,
when you installed Oracle components,
all subdirectories were located under a
top level ORACLE_HOME directory that by
default used one of the following names:
Go to the ORACLE_BASE\ORACLE_
HOME\rdbms\admin directory.
■
C:\orant for Windows NT
■
C:\orawin98 for Windows 98
This release complies with Optimal
Flexible Architecture (OFA) guidelines.
All subdirectories are not under a top
level ORACLE_HOME directory. There is a
top level directory called ORACLE_BASE
that by default is C:\oracle. If you
install Oracle9i release 1 (9.0.1) on a
computer with no other Oracle software
installed, then the default setting for the
first Oracle home directory is
C:\oracle\ora90. The Oracle home
directory is located directly under
ORACLE_BASE.
All directory path examples in this guide
follow OFA conventions.
Refer to Oracle9i Database Getting Started
for Windows for additional information
about OFA compliances and for
information about installing Oracle
products in non-OFA compliant
directories.
Documentation Accessibility
Our goal is to make Oracle products, services, and supporting documentation
accessible, with good usability, to the disabled community. To that end, our
documentation includes features that make information available to users of
assistive technology. This documentation is available in HTML format, and contains
markup to facilitate access by the disabled community. Standards will continue to
evolve over time, and Oracle Corporation is actively engaged with other
market-leading technology vendors to address technical obstacles so that our
documentation can be accessible to all of our customers. For additional information,
visit the Oracle Accessibility Program Web site at
http://www.oracle.com/accessibility/
l
JAWS, a Windows screen
reader, may not always correctly read the code examples in this document. The
conventions for writing code require that closing braces should appear on an
otherwise empty line; however, JAWS may not always read a line of text that
consists solely of a bracket or brace.
Accessibility of Code Examples in Documentation
Accessibility of Links to External Web Sites in Documentation This
documentation may contain links to Web sites of other companies or organizations
that Oracle Corporation does not own or control. Oracle Corporation neither
evaluates nor makes any representations regarding the accessibility of these Web
sites.
li
lii
What’s New in Oracle9i Database
Reference?
This section describes new features of Oracle9i release 2 (9.2) and provides pointers
to additional information. New features information from previous releases is also
retained to help those users upgrading to the current release.
The following sections describe the new features in Oracle9i Database Reference:
■
Oracle9i Release 2 (9.2) New Features in Oracle9i Database Reference
■
Oracle9i Release 1 (9.0.1) New Features in Oracle9i Database Reference
liii
Oracle9i Release 2 (9.2) New Features in Oracle9i Database Reference
The following initialization parameters are new to this release:
AUDIT_SYS_OPERATIONS
DG_BROKER_CONFIG_FILEn
DG_BROKER_START
FILE_MAPPING
FILESYSTEMIO_OPTIONS
LOG_PARALLELISM
OLAP_PAGE_POOL_SIZE
OPTIMIZER_DYNAMIC_SAMPLING
STATISTICS_LEVEL
See Also: Chapter 1, "Initialization Parameters" for more
information about these initialization parameters
The following static data dictionary views are new to this release:
ALL_ Views
DBA_ Views
ALL_APPLY
DBA_APPLY
ALL_APPLY_CONFLICT_COLUMNS
DBA_APPLY_CONFLICT_COLUMNS
ALL_APPLY_DML_HANDLERS
DBA_APPLY_DML_HANDLERS
ALL_APPLY_ERROR
DBA_APPLY_ERROR
USER_ Views
DBA_APPLY_INSTANTIATED_
OBJECTS
ALL_APPLY_KEY_COLUMNS
DBA_APPLY_KEY_COLUMNS
ALL_APPLY_PARAMETERS
DBA_APPLY_PARAMETERS
ALL_APPLY_PROGRESS
DBA_APPLY_PROGRESS
DBA_AQ_AGENT_PRIVS
USER_AQ_AGENT_PRIVS
DBA_AQ_AGENTS
DBA_AW_PS
USER_AW_PS
DBA_AWS
USER_AWS
ALL_CAPTURE
DBA_CAPTURE
ALL_CAPTURE_PARAMETERS
DBA_CAPTURE_PARAMETERS
ALL_CAPTURE_PREPARED_DATABASE
DBA_CAPTURE_PREPARED_DATABASE
ALL_CAPTURE_PREPARED_SCHEMAS
DBA_CAPTURE_PREPARED_SCHEMAS
ALL_CAPTURE_PREPARED_TABLES
DBA_CAPTURE_PREPARED_TABLES
ALL_CONS_OBJ_COLUMNS
DBA_CONS_OBJ_COLUMNS
liv
USER_CONS_OBJ_COLUMNS
ALL_ Views
DBA_ Views
USER_ Views
ALL_EVALUATION_CONTEXT_TABLES
DBA_EVALUATION_CONTEXT_TABLES
USER_EVALUATION_CONTEXT_
TABLES
ALL_EVALUATION_CONTEXT_VARS
DBA_EVALUATION_CONTEXT_VARS
USER_EVALUATION_CONTEXT_VARS
ALL_EVALUATION_CONTEXTS
DBA_EVALUATION_CONTEXTS
USER_EVALUATION_CONTEXTS
ALL_JAVA_ARGUMENTS
DBA_JAVA_ARGUMENTS
USER_JAVA_ARGUMENTS
ALL_JAVA_CLASSES
DBA_JAVA_CLASSES
USER_JAVA_CLASSES
ALL_JAVA_DERIVATIONS
DBA_JAVA_DERIVATIONS
USER_JAVA_DERIVATIONS
ALL_JAVA_FIELDS
DBA_JAVA_FIELDS
USER_JAVA_FIELDS
ALL_JAVA_IMPLEMENTS
DBA_JAVA_IMPLEMENTS
USER_JAVA_IMPLEMENTS
ALL_JAVA_INNERS
DBA_JAVA_INNERS
USER_JAVA_INNERS
ALL_JAVA_LAYOUTS
DBA_JAVA_LAYOUTS
USER_JAVA_LAYOUTS
ALL_JAVA_METHODS
DBA_JAVA_METHODS
USER_JAVA_METHODS
ALL_JAVA_NCOMPS
DBA_JAVA_NCOMPS
USER_JAVA_NCOMPS
ALL_JAVA_RESOLVERS
DBA_JAVA_RESOLVERS
USER_JAVA_RESOLVERS
ALL_JAVA_THROWS
DBA_JAVA_THROWS
USER_JAVA_THROWS
ALL_LOB_TEMPLATES
DBA_LOB_TEMPLATES
USER_LOB_TEMPLATES
DBA_LOGSTDBY_EVENTS
DBA_LOGSTDBY_LOG
DBA_LOGSTDBY_NOT_UNIQUE
DBA_LOGSTDBY_PARAMETERS
DBA_LOGSTDBY_PROGRESS
DBA_LOGSTDBY_SKIP
DBA_LOGSTDBY_SKIP_TRANSACTION
DBA_LOGSTDBY_UNSUPPORTED
ALL_OBJ_COLATTRS
DBA_OBJ_COLATTRS
ALL_PROPAGATION
DBA_PROPAGATION
USER_OBJ_COLATTRS
ALL_PUBLISHED_COLUMNS
DBA_PUBLISHED_COLUMNS
USER_PUBLISHED_COLUMNS
DBA_REGISTRY
USER_REGISTRY
ALL_REGISTRY_BANNERS
DBA_REGISTRY_HIERARCHY
ALL_RULE_SET_RULES
DBA_RULE_SET_RULES
USER_RULE_SET_RULES
ALL_RULE_SETS
DBA_RULE_SETS
USER_RULE_SETS
lv
ALL_ Views
DBA_ Views
USER_ Views
ALL_RULES
DBA_RULES
USER_RULES
ALL_STREAMS_GLOBAL_RULES
DBA_STREAMS_GLOBAL_RULES
ALL_STREAMS_SCHEMA_RULES
DBA_STREAMS_SCHEMA_RULES
ALL_STREAMS_TABLE_RULES
DBA_STREAMS_TABLE_RULES
ALL_SUBPARTITION_TEMPLATES
DBA_SUBPARTITION_TEMPLATES
USER_SUBPARTITION_TEMPLATES
ALL_XML_SCHEMAS
DBA_XML_SCHEMAS
USER_XML_SCHEMAS
ALL_XML_TAB_COLS
DBA_XML_TAB_COLS
USER_XML_TAB_COLS
ALL_XML_TABLES
DBA_XML_TABLES
USER_XML_TABLES
ALL_XML_VIEW_COLS
DBA_XML_VIEW_COLS
USER_XML_VIEW_COLS
ALL_XML_VIEWS
DBA_XML_VIEWS
USER_XML_VIEWS
See Also: Chapter 2, "Static Data Dictionary Views" for more
information about these static data dictionary views
The following dynamic performance views are new to this release:
lvi
GV$AW_CALC
V$AW_CALC
GV$AW_OLAP
V$AW_OLAP
GV$AW_SESSION_INFO
V$AW_SESSION_INFO
GV$BACKUP_SPFILE
V$BACKUP_SPFILE
GV$DATABASE_BLOCK_CORRUPTION
V$DATABASE_BLOCK_CORRUPTION
GV$DATABASE_INCARNATION
V$DATABASE_INCARNATION
GV$DATAGUARD_STATUS
V$DATAGUARD_STATUS
GV$LIBRARY_CACHE_MEMORY
V$LIBRARY_CACHE_MEMORY
GV$LOGMNR_STATS
V$LOGMNR_STATS
GV$MAP_COMP_LIST
V$MAP_COMP_LIST
GV$MAP_ELEMENT
V$MAP_ELEMENT
GV$MAP_EXT_ELEMENT
V$MAP_EXT_ELEMENT
GV$MAP_FILE
V$MAP_FILE
GV$MAP_FILE_EXTENT
V$MAP_FILE_EXTENT
GV$MAP_FILE_IO_STACK
V$MAP_FILE_IO_STACK
GV$MAP_LIBRARY
V$MAP_LIBRARY
GV$MAP_SUBELEMENT
V$MAP_SUBELEMENT
GV$MTTR_TARGET_ADVICE
V$MTTR_TARGET_ADVICE
GV$PGA_TARGET_ADVICE
V$PGA_TARGET_ADVICE
GV$PGA_TARGET_ADVICE_HISTOGRAM V$PGA_TARGET_ADVICE_HISTOGRAM
GV$SEGMENT_STATISTICS
V$SEGMENT_STATISTICS
GV$SEGSTAT
V$SEGSTAT
GV$SEGSTAT_NAME
V$SEGSTAT_NAME
GV$SGA_CURRENT_RESIZE_OPS
V$SGA_CURRENT_RESIZE_OPS
GV$SGA_DYNAMIC_COMPONENTS
V$SGA_DYNAMIC_COMPONENTS
GV$SGA_DYNAMIC_FREE_MEMORY
V$SGA_DYNAMIC_FREE_MEMORY
GV$SGA_RESIZE_OPS
V$SGA_RESIZE_OPS
GV$SHARED_POOL_ADVICE
V$SHARED_POOL_ADVICE
GV$SQL_PLAN_STATISTICS
V$SQL_PLAN_STATISTICS
GV$SQL_PLAN_STATISTICS_ALL
V$SQL_PLAN_STATISTICS_ALL
GV$SQL_WORKAREA_HISTOGRAM
V$SQL_WORKAREA_HISTOGRAM
GV$STATISTICS_LEVEL
V$STATISTICS_LEVEL
GV$STREAMS_APPLY_COORDINATOR
V$STREAMS_APPLY_COORDINATOR
GV$STREAMS_APPLY_READER
V$STREAMS_APPLY_READER
GV$STREAMS_APPLY_SERVER
V$STREAMS_APPLY_SERVER
GV$STREAMS_CAPTURE
V$STREAMS_CAPTURE
GV$TEMPSEG_USAGE
V$TEMPSEG_USAGE
See Also: Chapter 3, "Dynamic Performance (V$) Views" for more
information about these dynamic performance views
The following static data dictionary views have new columns in this release:
lvii
Static Data Dictionary View
New Columns
ALL_IND_SUBPARTITIONS
HIGH_VALUE
HIGH_VALUE_LENGTH
ALL_LOBS
RETENTION
FREEPOOLS
ALL_MVIEWS
UNKNOWN_PREBUILT
UNKNOWN_PLSQL_FUNC
UNKNOWN_EXTERNAL_TABLE
UNKNOWN_CONSIDER_FRESH
UNKNOWN_IMPORT
ALL_NESTED_TABLES
ELEMENT_SUBSTITUTABLE
ALL_PART_TABLES
DEF_COMPRESSION
ALL_QUEUE_TABLES
SECURE
ALL_TAB_PARTITIONS
COMPRESSION
ALL_TAB_SUBPARTITIONS
HIGH_VALUE
HIGH_VALUE_LENGTH
COMPRESSION
ALL_VARRAYS
ELEMENT_SUBSTITUTABLE
DBA_FGA_AUDIT_TRAIL
USERHOST
CLIENT_ID
EXT_NAME
DBA_IND_SUBPARTITIONS
HIGH_VALUE
HIGH_VALUE_LENGTH
DBA_LOBS
RETENTION
FREEPOOLS
DBA_MVIEWS
UNKNOWN_PREBUILT
UNKNOWN_PLSQL_FUNC
UNKNOWN_EXTERNAL_TABLE
UNKNOWN_CONSIDER_FRESH
UNKNOWN_IMPORT
lviii
Static Data Dictionary View
New Columns
DBA_NESTED_TABLES
ELEMENT_SUBSTITUTABLE
DBA_PART_TABLES
DEF_COMPRESSION
DBA_QUEUE_TABLES
SECURE
DBA_TAB_PARTITIONS
COMPRESSION
DBA_TAB_SUBPARTITIONS
HIGH_VALUE
HIGH_VALUE_LENGTH
COMPRESSION
DBA_TABLESPACES
FORCE_LOGGING
DBA_VARRAYS
ELEMENT_SUBSTITUTABLE
USER_IND_SUBPARTITIONS
HIGH_VALUE
HIGH_VALUE_LENGTH
USER_LOBS
RETENTION
FREEPOOLS
USER_MVIEWS
UNKNOWN_PREBUILT
UNKNOWN_PLSQL_FUNC
UNKNOWN_EXTERNAL_TABLE
UNKNOWN_CONSIDER_FRESH
UNKNOWN_IMPORT
USER_NESTED_TABLES
ELEMENT_SUBSTITUTABLE
USER_PART_TABLES
DEF_COMPRESSION
USER_QUEUE_TABLES
SECURE
USER_TAB_PARTITIONS
COMPRESSION
USER_TAB_SUBPARTITIONS
HIGH_VALUE
HIGH_VALUE_LENGTH
COMPRESSION
USER_TABLESPACES
FORCE_LOGGING
USER_VARRAYS
ELEMENT_SUBSTITUTABLE
lix
See Also: Chapter 2, "Static Data Dictionary Views" for more
information about the new columns in these static data dictionary
views
The following dynamic performance views have new columns in this release:
Dynamic Performance View
New Columns
GV$ARCHIVE_DEST and V$ARCHIVE_DEST
DEST_NAME
NET_TIMEOUT
REGISTER
REMOTE_TEMPLATE
GV$ARCHIVE_DEST_STATUSandV$ARCHIVE_ DEST_NAME
DEST_STATUS
PROTECTION_MODE
SRL
GV$ARCHIVED_LOG and V$ARCHIVED_LOG
ACTIVATION#
GV$BACKUP_CORRUPTION and V$BACKUP_
CORRUPTION
CORRUPTION_TYPE
GV$COPY_CORRUPTION and V$COPY_
CORRUPTION
CORRUPTION_TYPE
GV$DATABASE and V$DATABASE
PROTECTION_MODE
PROTECTION_LEVEL
DATAGUARD_BROKER
GUARD_STATUS
SUPPLEMENTAL_LOG_DATA_MIN
SUPPLEMENTAL_LOG_DATA_PK
SUPPLEMENTAL_LOG_DATA_UI
FORCE_LOGGING
GV$DATAFILE_COPYandV$DATAFILE_COPY SCANNED
GV$DB_CACHE_ADVICE and V$DB_CACHE_
ADVICE
SIZE_FACTOR
GV$DB_OBJECT_CACHE and V$DB_OBJECT_ CHILD_LATCH
CACHE
GV$FILE_CACHE_TRANSFER and V$FILE_
CACHE_TRANSFER
lx
CR_TRANSFERS
CUR_TRANSFERS
Dynamic Performance View
New Columns
GV$LATCH_CHILDREN and V$LATCH_
CHILDREN
MISSES_WAITLIST
SLEEPS_WAITLIST
WAIT_TIME_WAITLIST
GV$LATCH_PARENT and V$LATCH_PARENT
MISSES_WAITLIST
SLEEPS_WAITLIST
WAIT_TIME_WAITLIST
GV$LOGMNR_CALLBACK and V$LOGMNR_
CALLBACK
STATE
TYPE
CAPABILITY
GV$LOGMNR_CONTENTS and V$LOGMNR_
CONTENTS
PXIDUSN
PXIDSLT
PXIDSQN
GV$LOGMNR_REGIONandV$LOGMNR_REGION MEMSTATE
STATE
GV$LOGSTDBY and V$LOGSTDBY
HIGH_SCN
GV$PGASTAT and V$PGASTAT
UNIT
GV$PROCESS and V$PROCESS
PGA_FREEABLE_MEM
GV$ROLLSTAT and V$ROLLSTAT
LATCH
GV$SQL and V$SQL
FETCHES
CHILD_LATCH
GV$SQL_PLAN and V$SQL_PLAN
SEARCH_COLUMNS
ACCESS_PREDICATES
FILTER_PREDICATES
GV$SQL_SHARED_CURSOR and V$SQL_
SHARED_CURSOR
NO_TRIGGER_MISMATCH
GV$SQL_WORKAREA and V$SQL_WORKAREA
MAX_TEMPSEG_SIZE
FLASHBACK_CURSOR
LAST_TEMPSEG_SIZE
lxi
Dynamic Performance View
New Columns
GV$SQL_WORKAREA_ACTIVE and V$SQL_
WORKAREA_ACTIVE
TEMPSEG_SIZE
TABLESPACE
SEGRFNO#
SEGBLK#
GV$SQLAREA and V$SQLAREA
FETCHES
CHILD_LATCH
See Also: Chapter 3, "Dynamic Performance (V$) Views" for more
information about the new columns in these dynamic performance
views
Oracle9i Release 1 (9.0.1) New Features in Oracle9i Database
Reference
The following initialization parameters are new to this release:
ARCHIVE_LAG_TARGET
CIRCUITS
CLUSTER_INTERCONNECTS
CLUSTER_DATABASE
CLUSTER_DATABASE_INSTANCES
DB_nK_CACHE_SIZE
DB_CACHE_ADVICE
DB_CACHE_SIZE
DB_CREATE_FILE_DEST
DB_CREATE_ONLINE_LOG_DEST_n
DB_KEEP_CACHE_SIZE
DB_RECYCLE_CACHE_SIZE
DISPATCHERS
DRS_START
FAL_CLIENT
FAL_SERVER
FAST_START_MTTR_TARGET
GLOBAL_CONTEXT_POOL_SIZE
LOG_ARCHIVE_DEST_n (n = 6, 7, ... 10)
LOG_ARCHIVE_DEST_STATE_n (n = 6,
7, ... 10)
LOGMNR_MAX_PERSISTENT_SESSIONS MAX_DISPATCHERS
lxii
MAX_SHARED_SERVERS
NLS_LENGTH_SEMANTICS
NLS_NCHAR_CONV_EXCP
NLS_TIMESTAMP_FORMAT
NLS_TIMESTAMP_TZ_FORMAT
PGA_AGGREGATE_TARGET
PLSQL_COMPILER_FLAGS
PLSQL_NATIVE_C_COMPILER
PLSQL_NATIVE_LIBRARY_DIR
PLSQL_NATIVE_LIBRARY_SUBDIR_
COUNT
PLSQL_NATIVE_LINKER
PLSQL_NATIVE_MAKE_FILE_NAME
PLSQL_NATIVE_MAKE_UTILITY
REMOTE_ARCHIVE_ENABLE
REMOTE_LISTENER
SGA_MAX_SIZE
SHARED_SERVER_SESSIONS
SHARED_SERVERS
SPFILE
STANDBY_FILE_MANAGEMENT
STANDBY_PRESERVES_NAMES
trace_enabled
UNDO_MANAGEMENT
UNDO_RETENTION
UNDO_SUPPRESS_ERRORS
UNDO_TABLESPACE
WORKAREA_SIZE_POLICY
See Also: Chapter 1, "Initialization Parameters" for more
information about these initialization parameters
The following static data dictionary views are new to this release:
ALL_ Views
DBA_ Views
USER_ Views
DBA_APPLICATION_ROLES
USER_APPLICATION_ROLES
DBA_ATTRIBUTE_TRANSFORMATIONS
USER_ATTRIBUTE_
TRANSFORMATIONS
ALL_AUDIT_POLICIES
DBA_AUDIT_POLICIES
USER_AUDIT_POLICIES
ALL_BASE_TABLE_MVIEWS
DBA_BASE_TABLE_MVIEWS
USER_BASE_TABLE_MVIEWS
ALL_EXTERNAL_LOCATIONS
DBA_EXTERNAL_LOCATIONS
USER_EXTERNAL_LOCATIONS
ALL_EXTERNAL_TABLES
DBA_EXTERNAL_TABLES
USER_EXTERNAL_TABLES
DBA_FGA_AUDIT_TRAIL
DBA_GLOBAL_CONTEXT
ALL_INDEXTYPE_COMMENTS
DBA_INDEXTYPE_COMMENTS
USER_INDEXTYPE_COMMENTS
ALL_JOIN_IND_COLUMNS
DBA_JOIN_IND_COLUMNS
USER_JOIN_IND_COLUMNS
ALL_LOG_GROUP_COLUMNS
DBA_LOG_GROUP_COLUMNS
USER_LOG_GROUP_COLUMNS
ALL_LOG_GROUPS
DBA_LOG_GROUPS
USER_LOG_GROUPS
DBA_MVIEW_LOG_FILTER_COLS
lxiii
ALL_ Views
DBA_ Views
USER_ Views
ALL_MVIEW_LOGS
DBA_MVIEW_LOGS
USER_MVIEW_LOGS
ALL_MVIEW_REFRESH_TIMES
DBA_MVIEW_REFRESH_TIMES
USER_MVIEW_REFRESH_TIMES
ALL_OPERATOR_COMMENTS
DBA_OPERATOR_COMMENTS
USER_OPERATOR_COMMENTS
ALL_PENDING_CONV_TABLES
DBA_PENDING_CONV_TABLES
USER_PENDING_CONV_TABLES
ALL_POLICY_CONTEXTS
DBA_POLICY_CONTEXTS
USER_POLICY_CONTEXTS
ALL_POLICY_GROUPS
DBA_POLICY_GROUPS
USER_POLICY_GROUPS
ALL_PROCEDURES
DBA_PROCEDURES
USER_PROCEDURES
DBA_PROXIES
USER_PROXIES
DBA_REGISTERED_MVIEW_GROUPS
ALL_REGISTERED_MVIEWS
DBA_REGISTERED_MVIEWS
USER_REGISTERED_MVIEWS
DBA_REPCAT_EXCEPTIONS
DBA_REPEXTENSIONS
DBA_REPSITES_NEW
DBA_RESUMABLE
USER_RESUMABLE
ALL_SECONDARY_OBJECTS
DBA_SECONDARY_OBJECTS
USER_SECONDARY_OBJECTS
ALL_SOURCE_TAB_COLUMNS
DBA_SOURCE_TAB_COLUMNS
USER_SOURCE_TAB_COLUMNS
ALL_SOURCE_TABLES
DBA_SOURCE_TABLES
USER_SOURCE_TABLES
ALL_SQLJ_TYPE_ATTRS
DBA_SQLJ_TYPE_ATTRS
USER_SQLJ_TYPE_ATTRS
ALL_SQLJ_TYPE_METHODS
DBA_SQLJ_TYPE_METHODS
USER_SQLJ_TYPE_METHODS
ALL_SQLJ_TYPES
DBA_SQLJ_TYPES
USER_SQLJ_TYPES
ALL_STORED_SETTINGS
DBA_STORED_SETTINGS
USER_STORED_SETTINGS
ALL_SUBSCRIBED_COLUMNS
DBA_SUBSCRIBED_COLUMNS
USER_SUBSCRIBED_COLUMNS
ALL_SUBSCRIBED_TABLES
DBA_SUBSCRIBED_TABLES
USER_SUBSCRIBED_TABLES
ALL_SUBSCRIPTIONS
DBA_SUBSCRIPTIONS
USER_SUBSCRIPTIONS
ALL_TAB_COLS
DBA_TAB_COLS
USER_TAB_COLS
DBA_TEMPLATE_REFGROUPS
DBA_TEMPLATE_TARGETS
ALL_TYPE_VERSIONS
DBA_TRANSFORMATIONS
USER_TRANSFORMATIONS
DBA_TYPE_VERSIONS
USER_TYPE_VERSIONS
DBA_UNDO_EXTENTS
lxiv
See Also: Chapter 2, "Static Data Dictionary Views" for more
information about these static data dictionary views
The following dynamic performance views are new to this release:
GV$ACTIVE_SESS_POOL_MTH
V$ACTIVE_SESS_POOL_MTH
GV$ARCHIVE_DEST_STATUS
V$ARCHIVE_DEST_STATUS
GV$ARCHIVE_GAP
V$ARCHIVE_GAP
GV$CACHE_TRANSFER
V$CACHE_TRANSFER
GV$CLASS_CACHE_TRANSFER
V$CLASS_CACHE_TRANSFER
GV$CR_BLOCK_SERVER
V$CR_BLOCK_SERVER
GV$ENQUEUE_STAT
V$ENQUEUE_STAT
GV$FILE_CACHE_TRANSFER
V$FILE_CACHE_TRANSFER
GV$GC_ELEMENT
V$GC_ELEMENT
GV$GC_ELEMENTS_WITH_COLLISIONS V$GC_ELEMENTS_WITH_COLLISIONS
GV$GCSHVMASTER_INFO
V$GCSHVMASTER_INFO
GV$GCSPFMASTER_INFO
V$GCSPFMASTER_INFO
GV$GES_BLOCKING_ENQUEUE
V$GES_BLOCKING_ENQUEUE
GV$GES_CONVERT_LOCAL
V$GES_CONVERT_LOCAL
GV$GES_CONVERT_REMOTE
V$GES_CONVERT_REMOTE
GV$GES_ENQUEUE
V$GES_ENQUEUE
GV$GES_LATCH
V$GES_LATCH
GV$GES_RESOURCE
V$GES_RESOURCE
GV$GES_STATISTICS
V$GES_STATISTICS
GV$GES_TRAFFIC_CONTROLLER
V$GES_TRAFFIC_CONTROLLER
GV$GLOBALCONTEXT
V$GLOBALCONTEXT
GV$HVMASTER_INFO
V$HVMASTER_INFO
GV$LOGMNR_CALLBACK
V$LOGMNR_CALLBACK
GV$LOGMNR_LOGFILE
V$LOGMNR_LOGFILE
GV$LOGMNR_PROCESS
V$LOGMNR_PROCESS
lxv
GV$LOGMNR_REGION
V$LOGMNR_REGION
GV$LOGMNR_SESSION
V$LOGMNR_SESSION
GV$LOGMNR_TRANSACTION
V$LOGMNR_TRANSACTION
GV$LOGSTDBY
V$LOGSTDBY
GV$LOGSTDBY_STATS
V$LOGSTDBY_STATS
GV$MANAGED_STANDBY
V$MANAGED_STANDBY
GV$MVREFRESH
V$MVREFRESH
V$OBJECT_USAGE
GV$PGASTAT
V$PGASTAT
GV$QUEUEING_MTH
V$QUEUEING_MTH
GV$REPLPROP
V$REPLPROP
GV$REPLQUEUE
V$REPLQUEUE
GV$RESUMABLE
V$RESUMABLE
GV$RMAN_CONFIGURATION
V$RMAN_CONFIGURATION
GV$SHARED_SERVER_MONITOR
V$SHARED_SERVER_MONITOR
GV$SPPARAMETER
V$SPPARAMETER
GV$SQL_PLAN
V$SQL_PLAN
GV$SQL_REDIRECTION
V$SQL_REDIRECTION
GV$SQL_WORKAREA
V$SQL_WORKAREA
GV$SQL_WORKAREA_ACTIVE
V$SQL_WORKAREA_ACTIVE
GV$STANDBY_LOG
V$STANDBY_LOG
GV$TEMP_CACHE_TRANSFER
V$TEMP_CACHE_TRANSFER
GV$TIMEZONE_NAMES
V$TIMEZONE_NAMES
GV$UNDOSTAT
V$UNDOSTAT
GV$VPD_POLICY
V$VPD_POLICY
See Also: Chapter 3, "Dynamic Performance (V$) Views" for more
information about these dynamic performance views
The following static data dictionary views have new columns in this release:
lxvi
Static Data Dictionary View
New Columns
ALL_ALL_TABLES
DEPENDENCIES
ALL_ARGUMENTS
CHAR_LENGTH
CHAR_USED
ALL_ASSOCIATIONS
INTERFACE_VERSION
ALL_CLUSTERS
DEPENDENCIES
ALL_CONSTRAINTS
INDEX_OWNER
INDEX_NAME
INVALID
VIEW_RELATED
ALL_DIMENSIONS
COMPILE_STATE
ALL_IND_COLUMNS
CHAR_LENGTH
ALL_IND_PARTITIONS
DOMIDX_OPSTATUS
PARAMETERS
ALL_INDEXES
JOIN_INDEX
ALL_INDEXTYPE_OPERATORS
OPERATOR_SCHEMA
ALL_INDEXTYPES
INTERFACE_VERSION
PARTITIONING
ALL_MVIEWS
USE_NO_INDEX
ALL_OBJECT_TABLES
DEPENDENCIES
ALL_OPBINDINGS
PROPERTY
ALL_OUTLINES
SIGNATURE
ALL_PART_INDEXES
DEF_PARAMETERS
ALL_POLICIES
POLICY_GROUP
STATIC_POLICY
ALL_REPCAT_TEMPLATE_OBJECTS
DDL_NUM
ALL_REPCAT_TEMPLATE_SITES
INSTANTIATION_DATE
lxvii
Static Data Dictionary View
New Columns
ALL_REPCOLUMN
CTYPE_TOID
CTYPE_OWNER
CTYPE_HASHCODE
CTYPE_MOD
TOP
CHAR_LENGTH
CHAR_USED
ALL_REPDDL
DDL_NUM
ALL_REPFLAVOR_COLUMNS
TYPE_TOID
TYPE_OWNER
TYPE_HASHCODE
TYPE_MOD
TOP
ALL_REPOBJECT
NESTED_TABLE
ALL_SUMDELTA
SEQUENCE
ALL_TAB_COL_STATISTICS
OWNER
ALL_TAB_COLUMNS
CHAR_LENGTH
CHAR_USED
V80_FMT_IMAGE
DATA_UPGRADED
ALL_TAB_PRIVS
HIERARCHY
ALL_TAB_PRIVS_MADE
HIERARCHY
ALL_TAB_PRIVS_RECD
HIERARCHY
ALL_TABLES
DEPENDENCIES
ALL_TYPE_ATTRS
INHERITED
ALL_TYPE_METHODS
FINAL
INSTANTIABLE
OVERRIDING
INHERITED
lxviii
Static Data Dictionary View
New Columns
ALL_TYPES
FINAL
INSTANTIABLE
SUPERTYPE_OWNER
SUPERTYPE_NAME
LOCAL_ATTRIBUTES
LOCAL_METHODS
TYPEID
ALL_USTATS
PARTITION_NAME
ALL_VIEWS
SUPERVIEW_NAME
DBA_ALL_TABLES
DEPENDENCIES
DBA_ASSOCIATIONS
INTERFACE_VERSION
DBA_AUDIT_EXISTS
CLIENT_ID
SESSION_CPU
DBA_AUDIT_OBJECT
CLIENT_ID
SESSION_CPU
DBA_AUDIT_SESSION
CLIENT_ID
SESSION_CPU
DBA_AUDIT_STATEMENT
CLIENT_ID
SESSION_CPU
DBA_AUDIT_TRAIL
CLIENT_ID
SESSION_CPU
DBA_CLUSTERS
DEPENDENCIES
DBA_CONSTRAINTS
INDEX_OWNER
INDEX_NAME
INVALID
VIEW_RELATED
DBA_CONTEXT
TYPE
DBA_DIMENSIONS
COMPILE_STATE
DBA_IND_COLUMNS
CHAR_LENGTH
lxix
Static Data Dictionary View
New Columns
DBA_IND_PARTITIONS
DOMIDX_OPSTATUS
PARAMETERS
DBA_INDEXES
JOIN_INDEX
DBA_INDEXTYPE_OPERATORS
OPERATOR_SCHEMA
DBA_INDEXTYPES
INTERFACE_VERSION
PARTITIONING
DBA_MVIEWS
USE_NO_INDEX
DBA_OBJECT_TABLES
DEPENDENCIES
DBA_OPBINDINGS
PROPERTY
DBA_OUTLINES
SIGNATURE
DBA_PART_INDEXES
DEF_PARAMETERS
DBA_POLICIES
POLICY_GROUP
STATIC_POLICY
DBA_REPCAT_TEMPLATE_OBJECTS
DDL_NUM
DBA_REPCAT_TEMPLATE_SITES
INSTANTIATION_DATE
DBA_REPCOLUMN
CTYPE_TOID
CTYPE_OWNER
CTYPE_HASHCODE
CTYPE_MOD
TOP
CHAR_LENGTH
CHAR_USED
DBA_REPDDL
DDL_NUM
DBA_REPFLAVOR_COLUMNS
TYPE_TOID
TYPE_OWNER
TYPE_HASHCODE
TYPE_MOD
TOP
DBA_REPOBJECT
lxx
NESTED_TABLE
Static Data Dictionary View
New Columns
DBA_RSRC_PLAN_DIRECTIVES
ACTIVE_SESS_POOL_P1
QUEUEING_P1
SWITCH_GROUP
SWITCH_TIME
SWITCH_ESTIMATE
MAX_EST_EXEC_TIME
UNDO_POOL
DBA_RSRC_PLANS
ACTIVE_SESS_POOL_MTH
QUEUEING_MTH
DBA_TAB_COL_STATISTICS
OWNER
DBA_TAB_COLUMNS
CHAR_LENGTH
CHAR_USED
V80_FMT_IMAGE
DATA_UPGRADED
DBA_TAB_PRIVS
HIERARCHY
DBA_TABLES
DEPENDENCIES
DBA_TABLESPACES
BLOCK_SIZE
SEGMENT_SPACE_MANAGEMENT
DBA_TYPE_ATTRS
INHERITED
DBA_TYPE_METHODS
FINAL
INSTANTIABLE
OVERRIDING
INHERITED
DBA_TYPES
FINAL
INSTANTIABLE
SUPERTYPE_OWNER
SUPERTYPE_NAME
LOCAL_ATTRIBUTES
LOCAL_METHODS
TYPEID
lxxi
Static Data Dictionary View
New Columns
DBA_USTATS
PARTITION_NAME
DBA_VIEWS
SUPERVIEW_NAME
USER_ALL_TABLES
DEPENDENCIES
USER_ARGUMENTS
CHAR_LENGTH
CHAR_USED
USER_ASSOCIATIONS
INTERFACE_VERSION
USER_AUDIT_OBJECT
CLIENT_ID
SESSION_CPU
USER_AUDIT_SESSION
CLIENT_ID
SESSION_CPU
USER_AUDIT_STATEMENT
CLIENT_ID
SESSION_CPU
USER_AUDIT_TRAIL
CLIENT_ID
SESSION_CPU
USER_CLUSTERS
DEPENDENCIES
USER_CONSTRAINTS
INDEX_OWNER
INDEX_NAME
INVALID
VIEW_RELATED
USER_DIMENSIONS
COMPILE_STATE
USER_IND_COLUMNS
CHAR_LENGTH
USER_IND_PARTITIONS
DOMIDX_OPSTATUS
PARAMETERS
USER_INDEXES
JOIN_INDEX
USER_INDEXTYPE_OPERATORS
OPERATOR_SCHEMA
USER_INDEXTYPES
INTERFACE_VERSION
PARTITIONING
lxxii
USER_MVIEWS
USE_NO_INDEX
USER_OBJECT_TABLES
DEPENDENCIES
Static Data Dictionary View
New Columns
USER_OPBINDINGS
PROPERTY
USER_OUTLINES
SIGNATURE
USER_PART_INDEXES
DEF_PARAMETERS
USER_POLICIES
POLICY_GROUP
STATIC_POLICY
USER_REPCAT_TEMPLATE_OBJECTS
DDL_NUM
USER_REPCAT_TEMPLATE_SITES
INSTANTIATION_DATE
USER_REPCOLUMN
CTYPE_TOID
CTYPE_OWNER
CTYPE_HASHCODE
CTYPE_MOD
TOP
CHAR_LENGTH
CHAR_USED
USER_REPDDL
DDL_NUM
USER_REPFLAVOR_COLUMNS
TYPE_TOID
TYPE_OWNER
TYPE_HASHCODE
TYPE_MOD
TOP
USER_REPOBJECT
NESTED_TABLE
USER_REPPARAMETER_COLUMN
SNAME
USER_TAB_COLUMNS
CHAR_LENGTH
CHAR_USED
DATA_UPGRADED
V80_FMT_IMAGE
USER_TAB_PRIVS
HIERARCHY
USER_TAB_PRIVS_MADE
HIERARCHY
USER_TAB_PRIVS_RECD
HIERARCHY
lxxiii
Static Data Dictionary View
New Columns
USER_TABLES
DEPENDENCIES
USER_TABLESPACES
BLOCK_SIZE
SEGMENT_SPACE_MANAGEMENT
USER_TYPE_ATTRS
USER_TYPE_METHODS
INHERITED
FINAL
INSTANTIABLE
OVERRIDING
INHERITED
USER_TYPES
FINAL
INSTANTIABLE
SUPERTYPE_OWNER
SUPERTYPE_NAME
LOCAL_ATTRIBUTES
LOCAL_METHODS
TYPEID
USER_USTATS
PARTITION_NAME
USER_VIEWS
SUPERVIEW_NAME
See Also: Chapter 2, "Static Data Dictionary Views" for more
information about the new columns in these static data dictionary
views
The following dynamic performance views have new columns in this release:
lxxiv
Dynamic Performance View
New Columns
GV$ARCHIVE and V$ARCHIVE
ISCURRENT
Dynamic Performance View
New Columns
GV$ARCHIVE_DEST and V$ARCHIVE_DEST
ARCHIVER
SCHEDULE
LOG_SEQUENCE
DELAY_MINS
PROCESS
MANIFEST
FAILURE_COUNT
MAX_FAILURE
ALTERNATE
DEPENDENCY
REGISTER
QUOTA_SIZE
QUOTA_USED
MOUNTID
TRANSMIT_MODE
AFFIRM
TYPE
GV$ARCHIVED_LOG and V$ARCHIVED_LOG
DEST_ID
APPLIED
STATUS
DICTIONARY_BEGIN
DICTIONARY_END
END_OF_REDO
BACKUP_COUNT
ARCHIVAL_THREAD#
GV$BACKUP_SET and V$BACKUP_SET
KEEP
KEEP_UNTIL
KEEP_OPTIONS
lxxv
Dynamic Performance View
New Columns
GV$BUFFER_POOL and V$BUFFER_POOL
BLOCK_SIZE
RESIZE_STATE
CURRENT_SIZE
TARGET_SIZE
TARGET_BUFFERS
PREV_SIZE
PREV_BUFFERS
GV$BUFFER_POOL_STATISTICS and
V$BUFFER_POOL_STATISTICS
BLOCK_SIZE
GV$CIRCUIT and V$CIRCUIT
PCIRCUIT
GV$DATABASE and V$DATABASE
STANDBY_MODE
REMOTE_ARCHIVE
ACTIVATION#
DATABASE_ROLE
ARCHIVELOG_CHANGE#
SWITCHOVER_STATUS
GV$DATAFILE and V$DATAFILE
BLOCK1_OFFSET
AUX_NAME
GV$DATAFILE_COPYandV$DATAFILE_COPY STATUS
KEEP
KEEP_UNTIL
KEEP_OPTIONS
GV$DB_CACHE_ADVICE and V$DB_CACHE_
ADVICE
BLOCK_SIZE
GV$DELETED_OBJECT and V$DELETED_
OBJECT
OBJECT_DATA
GV$FILESTAT and V$FILESTAT
SINGLEBLKRDS
ADVICE_STATUS
SINGLEBLKRDTIM
GV$INSTANCE and V$INSTANCE
lxxvi
ACTIVE_STATE
Dynamic Performance View
New Columns
GV$INSTANCE_RECOVERYandV$INSTANCE_ TARGET_MTTR
RECOVERY
ESTIMATED_MTTR
CKPT_BLOCK_WRITES
GV$LATCH and V$LATCH
WAIT_TIME
GV$LATCH_CHILDREN and V$LATCH_
CHILDREN
WAIT_TIME
GV$LATCH_MISSES and V$LATCH_MISSES
LOCATION
GV$LATCH_PARENT and V$LATCH_PARENT
WAIT_TIME
GV$LOGFILE and V$LOGFILE
TYPE
GV$LOGMNR_CONTENTS and V$LOGMNR_
CONTENTS
CSCN
COMMIT_TIMESTAMP
TX_NAME
OPERATION_CODE
SEQUENCE#
REDO_VALUE
UNDO_VALUE
SQL_COLUMN_TYPE
SQL_COLUMN_NAME
REDO_LENGTH
REDO_OFFSET
UNDO_LENGTH
UNDO_OFFSET
GV$LOGMNR_LOGS and V$LOGMNR_LOGS
DICTIONARY_BEGIN
DICTIONARY_END
GV$MLS_PARAMETERS and V$MLS_
PARAMETERS
UPDATE_COMMENT
GV$PARAMETER and V$PARAMETER
UPDATE_COMMENT
GV$PARAMETER2 and V$PARAMETER2
ORDINAL
UPDATE_COMMENT
lxxvii
Dynamic Performance View
New Columns
GV$PROCESS and V$PROCESS
PGA_USED_MEM
PGA_ALLOC_MEM
PGA_MAX_MEM
GV$PROXY_DATAFILE and V$PROXY_
DATAFILE
KEEP
KEEP_UNTIL
KEEP_OPTIONS
GV$RECOVER_FILE and V$RECOVER_FILE
ONLINE_STATUS
GV$RSRC_CONSUMER_GROUP and V$RSRC_
CONSUMER_GROUP
QUEUE_LENGTH
GV$SESSION and V$SESSION
CURRENT_QUEUE_DURATION
CURRENT_UNDO_CONSUMPTION
CLIENT_IDENTIFIER
GV$SESSION_EVENTandV$SESSION_EVENT TIME_WAITED_MICRO
GV$SORT_USAGE and V$SORT_USAGE
USERNAME
GV$SQL and V$SQL
PLAN_HASH_VALUE
CPU_TIME
ELAPSED_TIME
OUTLINE_SID
CHILD_ADDRESS
SQLTYPE
REMOTE
OBJECT_STATUS
LITERAL_HASH_VALUE
LAST_LOAD_TIME
IS_OBSOLETE
GV$SQL_SHARED_CURSOR and V$SQL_
SHARED_CURSOR
LOGMINER_SESSION_MISMATCH
INCOMP_LTRL_MISMATCH
OVERLAP_TIME_MISMATCH
USER_BIND_PEEK_MISMATCH
TYPCHK_DEP_MISMATCH
lxxviii
Dynamic Performance View
New Columns
GV$SQLAREA and V$SQLAREA
CPU_TIME
ELAPSED_TIME
IS_OBSOLETE
GV$SYSTEM_EVENT and V$SYSTEM_EVENT
TIME_WAITED_MICRO
GV$SYSTEM_PARAMETER and V$SYSTEM_
PARAMETER
UPDATE_COMMENT
GV$SYSTEM_PARAMETER2 and V$SYSTEM_
PARAMETER2
ORDINAL
GV$TABLESPACE and V$TABLESPACE
INCLUDED_IN_DATABASE_BACKUP
GV$TEMPSTAT and V$TEMPSTAT
SINGLEBLKRDS
UPDATE_COMMENT
SINGLEBLKRDTIM
GV$TRANSACTION and V$TRANSACTION
NAME
See Also: Chapter 3, "Dynamic Performance (V$) Views" for more
information about the new columns in these dynamic performance
views
lxxix
lxxx
1
Initialization Parameters
This chapter contains detailed descriptions of the database initialization parameters
and includes the following topics:
■
Uses of Initialization Parameters
■
Parameter Files
■
Changing Parameter Values
■
Reading the Parameter Descriptions
■
Parameter Descriptions
Initialization Parameters 1-1
Uses of Initialization Parameters
Uses of Initialization Parameters
Initialization parameters fall into various functional groups. For example,
parameters perform the following functions:
■
Set limits for the entire database
■
Set user or process limits
■
Set limits on database resources
■
Affect performance (these are called variable parameters)
Variable parameters are of particular interest to database administrators,
because these parameters are used primarily to improve database performance.
Database administrators can use initialization parameters to:
■
■
Optimize performance by adjusting memory structures, such as the number of
database buffers in memory
Set database-wide defaults, such as the amount of space initially allocated for a
context area when it is created
■
Set database limits, such as the maximum number of database users
■
Specify names of files or directories required by the database
Many initialization parameters can be fine-tuned to improve database performance.
Other parameters should never be altered or should be altered only under the
supervision of Oracle Support Services.
All initialization parameters are optional. Oracle has a default value for each
parameter. This value may be operating system-dependent, depending on the
parameter.
Types of Initialization Parameters
The Oracle database server has the following types of initialization parameters:
■
Derived Parameters
■
Operating System-Dependent Parameters
■
Variable Parameters (these can be dynamic parameters or any of the preceding
ones)
1-2 Oracle9i Database Reference
Uses of Initialization Parameters
Derived Parameters
Some initialization parameters are derived, meaning that their values are calculated
from the values of other parameters. Normally, you should not alter values for
derived parameters, but if you do, then the value you specify will override the
calculated value.
For example, the default value of the SESSIONS parameter is derived from the
value of the PROCESSES parameter. If the value of PROCESSES changes, then the
default value of SESSIONS changes as well, unless you override it with a specified
value.
Operating System-Dependent Parameters
The valid values or value ranges of some initialization parameters depend upon the
host operating system. For example, the parameter DB_BLOCK_BUFFERS indicates
the number of data buffers in main memory, and its maximum value depends on
the operating system. The size of those buffers, set by DB_BLOCK_SIZE, has an
operating system-dependent default value.
See Also: Your operating system-specific Oracle documentation
for more information on operating system-dependent Oracle
parameters and operating system parameters
Variable Parameters
The variable initialization parameters offer the most potential for improving system
performance. Some variable parameters set capacity limits but do not affect
performance. For example, when the value of OPEN_CURSORS is 10, a user process
attempting to open its eleventh cursor receives an error. Other variable parameters
affect performance but do not impose absolute limits. For example, reducing the
value of DB_BLOCK_BUFFERS does not prevent work even though it may slow
down performance.
Increasing the values of variable parameters may improve your system’s
performance, but increasing most parameters also increases the system global area
(SGA) size. A larger SGA can improve database performance up to a point. In
virtual memory operating systems, an SGA that is too large can degrade
performance if it is swapped in and out of memory. Operating system parameters
that control virtual memory working areas should be set with the SGA size in mind.
The operating system configuration can also limit the maximum size of the SGA.
Initialization Parameters 1-3
Parameter Files
Parameter Files
A parameter file is a file that contains a list of initialization parameters and a value
for each parameter. You specify initialization parameters in a parameter file that
reflect your particular installation. Oracle supports the following two types of
parameter files:
■
Server Parameter Files
■
Initialization Parameter Files
Server Parameter Files
A server parameter file is a binary file that acts as a repository for initialization
parameters. The server parameter file can reside on the machine where the Oracle
database server executes. Initialization parameters stored in a server parameter file
are persistent, in that any changes made to the parameters while an instance is
running can persist across instance shutdown and startup.
Initialization Parameter Files
An initialization parameter file is a text file that contains a list of initialization
parameters. The file should be written in the client’s default character set.
The following are sample entries in an initialization parameter file:
PROCESSES = 100
OPEN_LINKS = 12
GLOBAL_NAMES = true
The name of the initialization parameter file varies depending on the operating
system. For example, it can be in mixed case or lowercase, or it can have a logical
name or a variation of the name init.ora. Also supplied is an initdw.ora file,
which contains suggested parameter settings for data warehouses and data marts.
The database administrator can choose a different filename for the initialization
parameter file.
Refer to your operating system-specific Oracle documentation for the default
locations and filenames for initialization parameter files on your operating system.
The initialization parameter file is read by the client-side tool used to start the
server (such as SQL*Plus).
Sample initialization parameter files are provided on the Oracle distribution
medium for each operating system. A sample file is sufficient for initial use, but you
will probably want to modify the file to tune the database for best performance.
1-4 Oracle9i Database Reference
Parameter Files
Any changes will take effect after you completely shut down and restart the
instance.
Specifying Values in the Initialization Parameter File
This section describes several aspects of setting parameter values in the
initialization parameter file.
Rules Governing Parameter Files The following rules govern the specification of
parameters in initialization parameter files:
■
■
■
■
The initialization parameter file should contain only parameters and comments.
A pound sign (#) starts a comment line. The rest of the line is ignored.
You can specify parameters in any order.
Case (upper or lower) in filenames is significant only if case is significant on the
host operating system.
To enter several parameters on one line, use spaces between parameter names
and values, as in the following example:
PROCESSES = 100 CPU_COUNT = 1 OPEN_CURSORS = 10
■
Some parameters, such as ROLLBACK_SEGMENTS, accept multiple value entries.
Enter multiple values enclosed in parentheses and separated by commas. For
example:
ROLLBACK_SEGMENTS = (SEG1, SEG2, SEG3, SEG4, SEG5)
Alternatively, you can enter multiple values without parentheses and commas.
For example:
ROLLBACK_SEGMENTS = SEG1 SEG2 SEG3 SEG4 SEG5
Either syntax is valid.
If you enter values for one parameter in multiple entries, then the entries must
be on consecutive lines. If they are not, then the first entry will not be processed
properly. For example, in the following entry the setting for SEG3 and SEG4
will override the setting for SEG1 and SEG2:
ROLLBACK_SEGMENTS = SEG1 SEG2
OPEN_CURSORS = 10
ROLLBACK_SEGMENTS = SEG3 SEG4
Initialization Parameters 1-5
Parameter Files
■
A backslash (\), also known as an escape character, indicates continuation of
the parameter specification. If a backslash continues a line, then the continued
line must have no leading spaces. For example:
ROLLBACK_SEGMENTS = (SEG1, SEG2, \
SEG3, SEG4, SEG5)
■
■
You can use the IFILE initialization parameter to embed the contents of
another initialization parameter file into the current initialization parameter file.
Enclose in quotation marks any parameter values that contain spaces or tabs.
You can use either single or double quotation marks unless otherwise indicated.
For example:
NLS_TERRITORY = ’CZECH REPUBLIC’
Note: Listing parameters in alphabetical order in the initialization
parameter file can help you to find them and can help ensure that
each parameter is specified only once.
■
Enclose in quotation marks any parameter value that contains a special
character.
See Also:
■
■
Your operating system-specific Oracle documentation for more
information on initialization parameter files
"IFILE" on page 1-65
Using Special Characters in Parameter Values If a parameter value contains a special
character, then the special character must be preceded by a backslash or the entire
parameter value must be enclosed in quotation marks. For example, you can specify
special characters using either of the following:
DB_DOMAIN = ’JAPAN.ACME#.COM’
DB_DOMAIN = JAPAN.ACME\#.COM
Table 1–1 lists the special characters you can use in initialization parameter files.
1-6 Oracle9i Database Reference
Changing Parameter Values
Table 1–1
Special Characters in the Initialization Parameter File
Character
Name
Description
#
Number sign
Comment
(
Left parenthesis
Start list of values
)
Right parenthesis
End list of values
"
Double quotation
mark
Start or end of quoted string
’
Single quotation
mark
Start or end of quoted string
=
Equal sign
Separator of keyword and values
,
Comma
Separator of elements
-
Minus sign
Precedes UNIX-style keywords
\
Backslash
Escape character
If a special character must be treated literally in the initialization parameter file,
then it must either be preceded by the backslash character, or the entire string
containing the special character must be enclosed in quotation marks.
Using the Escape Character As described in "Rules Governing Parameter Files" on
page 1-5, the backslash (\) can also signify a line continuation. If the backslash is
followed by an alphanumeric character, then the backslash is treated as a normal
character in the input. If it is not followed by an alphanumeric character, then the
backslash is treated either as a backslash or as a continuation character.
Using Quotation Marks Quotation marks can be nested in one of two ways. The first
method is to double the quotation marks in the nested string. For example:
NLS_DATE_FORMAT = ’’’Today is’’ MM/DD/YYYY’
The second method is to alternate single and double quotation marks. For example:
NLS_DATE_FORMAT = ’"Today is" MM/DD/YYYY’
Changing Parameter Values
You change the value of a parameter by editing the initialization parameter file. In
most cases, the new value takes effect the next time you start an instance of the
Initialization Parameters 1-7
Changing Parameter Values
database. However, you can change the value of some parameters for the duration
of the current session, as described in the following section.
Dynamic Parameters
Some initialization parameters are dynamic, that is, they can be modified using the
ALTER SESSION or ALTER SYSTEM statements while an instance is running.
Use the following syntax to dynamically alter initialization parameters:
ALTER SESSION SET parameter_name = value
ALTER SYSTEM SET parameter_name = value [DEFERRED]
Whenever a dynamic parameter is modified using the ALTER SYSTEM statement,
Oracle records the command that modifies the parameter in the alert log.
The ALTER SESSION statement changes the value of the specified parameter for
the duration of the session that invokes the statement. The value of the parameter
does not change for other sessions in the instance. The value of the following
initialization parameters can be changed with ALTER SESSION:
CURSOR_SHARING
DB_BLOCK_CHECKING
DB_CREATE_FILE_DEST
DB_CREATE_ONLINE_LOG_DEST_n
DB_FILE_MULTIBLOCK_READ_COUNT
FILESYSTEMIO_OPTIONS
GLOBAL_NAMES
HASH_AREA_SIZE
HASH_JOIN_ENABLED
LOG_ARCHIVE_DEST_n
LOG_ARCHIVE_DEST_STATE_n
LOG_ARCHIVE_MIN_SUCCEED_DEST
MAX_DUMP_FILE_SIZE
NLS_CALENDAR
NLS_COMP
NLS_CURRENCY
NLS_DATE_FORMAT
NLS_DATE_LANGUAGE
NLS_DUAL_CURRENCY
NLS_ISO_CURRENCY
NLS_LANGUAGE
NLS_NUMERIC_CHARACTERS
NLS_SORT
NLS_TERRITORY
NLS_TIMESTAMP_FORMAT
NLS_TIMESTAMP_TZ_FORMAT
OBJECT_CACHE_MAX_SIZE_PERCENT
OBJECT_CACHE_OPTIMAL_SIZE
OLAP_PAGE_POOL_SIZE
OPTIMIZER_DYNAMIC_SAMPLING
1-8 Oracle9i Database Reference
Changing Parameter Values
OPTIMIZER_INDEX_CACHING
OPTIMIZER_INDEX_COST_ADJ
OPTIMIZER_MAX_PERMUTATIONS
OPTIMIZER_MODE
ORACLE_TRACE_ENABLE
PARALLEL_INSTANCE_GROUP
PARALLEL_MIN_PERCENT
PARTITION_VIEW_ENABLED
PLSQL_COMPILER_FLAGS
PLSQL_V2_COMPATIBILITY
QUERY_REWRITE_ENABLED
QUERY_REWRITE_INTEGRITY
REMOTE_DEPENDENCIES_MODE
SESSION_CACHED_CURSORS
SORT_AREA_RETAINED_SIZE
SORT_AREA_SIZE
STAR_TRANSFORMATION_ENABLED
STATISTICS_LEVEL
TIMED_OS_STATISTICS
TIMED_STATISTICS
TRACEFILE_IDENTIFIER
UNDO_SUPPRESS_ERRORS
WORKAREA_SIZE_POLICY
The ALTER SYSTEM statement without the DEFERRED keyword modifies the global
value of the parameter for all sessions in the instance, for the duration of the
instance (until the database is shut down). The value of the following initialization
parameters can be changed with ALTER SYSTEM:
AQ_TM_PROCESSES
ARCHIVE_LAG_TARGET
BACKGROUND_DUMP_DEST
CONTROL_FILE_RECORD_KEEP_TIME
CORE_DUMP_DEST
CURSOR_SHARING
DB_nK_CACHE_SIZE
DB_BLOCK_CHECKING
DB_BLOCK_CHECKSUM
DB_CACHE_ADVICE
DB_CACHE_SIZE
DB_CREATE_FILE_DEST
DB_CREATE_ONLINE_LOG_DEST_n
DB_FILE_MULTIBLOCK_READ_COUNT
DB_KEEP_CACHE_SIZE
DB_RECYCLE_CACHE_SIZE
DG_BROKER_CONFIG_FILEn
DG_BROKER_START
DISPATCHERS
DRS_START
FAL_CLIENT
FAL_SERVER
FAST_START_IO_TARGET
FAST_START_MTTR_TARGET
FAST_START_PARALLEL_ROLLBACK
FILE_MAPPING
Initialization Parameters 1-9
Changing Parameter Values
1-10
FILESYSTEMIO_OPTIONS
FIXED_DATE
GLOBAL_NAMES
HS_AUTOREGISTER
JOB_QUEUE_PROCESSES
LARGE_POOL_SIZE
LICENSE_MAX_SESSIONS
LICENSE_MAX_USERS
LICENSE_SESSIONS_WARNING
LOCAL_LISTENER
LOG_ARCHIVE_DEST
LOG_ARCHIVE_DEST_n
LOG_ARCHIVE_DEST_STATE_n
LOG_ARCHIVE_DUPLEX_DEST
LOG_ARCHIVE_MAX_PROCESSES
LOG_ARCHIVE_MIN_SUCCEED_DEST
LOG_ARCHIVE_TRACE
LOG_CHECKPOINTS_TO_ALERT
LOG_CHECKPOINT_INTERVAL
LOG_CHECKPOINT_TIMEOUT
MAX_DUMP_FILE_SIZE
NLS_LENGTH_SEMANTICS
NLS_NCHAR_CONV_EXCP
OPEN_CURSORS
OPTIMIZER_DYNAMIC_SAMPLING
ORACLE_TRACE_ENABLE
PARALLEL_ADAPTIVE_MULTI_USER
PARALLEL_INSTANCE_GROUP
PARALLEL_THREADS_PER_CPU
PGA_AGGREGATE_TARGET
PLSQL_COMPILER_FLAGS
PLSQL_NATIVE_C_COMPILER
PLSQL_NATIVE_LIBRARY_DIR
PLSQL_NATIVE_LIBRARY_SUBDIR_
COUNT
PLSQL_NATIVE_LINKER
PLSQL_NATIVE_MAKE_FILE_NAME
PLSQL_NATIVE_MAKE_UTILITY
PLSQL_V2_COMPATIBILITY
QUERY_REWRITE_ENABLED
QUERY_REWRITE_INTEGRITY
REMOTE_DEPENDENCIES_MODE
REMOTE_LISTENER
RESOURCE_LIMIT
RESOURCE_MANAGER_PLAN
SERVICE_NAMES
SHARED_POOL_SIZE
SHARED_SERVERS
STANDBY_ARCHIVE_DEST
STANDBY_FILE_MANAGEMENT
STATISTICS_LEVEL
TIMED_OS_STATISTICS
TIMED_STATISTICS
TRACE_ENABLED
UNDO_RETENTION
UNDO_SUPPRESS_ERRORS
UNDO_TABLESPACE
Oracle9i Database Reference
Changing Parameter Values
USER_DUMP_DEST
WORKAREA_SIZE_POLICY
The ALTER SYSTEM ... DEFERRED statement does not modify the global value
of the parameter for existing sessions, but the value will be modified for future
sessions that connect to the database. The value of the following initialization
parameters can be changed with ALTER SYSTEM ... DEFERRED:
BACKUP_TAPE_IO_SLAVES
OBJECT_CACHE_MAX_SIZE_PERCENT
OBJECT_CACHE_OPTIMAL_SIZE
OLAP_PAGE_POOL_SIZE
SORT_AREA_RETAINED_SIZE
SORT_AREA_SIZE
TRANSACTION_AUDITING
Displaying Current Parameter Values
To see the current settings for initialization parameters, use the following SQL*Plus
command:
SQL> SHOW PARAMETERS
This command displays all parameters in alphabetical order, with their current
values.
Enter the following text string to display all parameters having BLOCK in their
names:
SQL> SHOW PARAMETERS BLOCK
You can use the SPOOL command to write the output to a file.
Parameters You Should Not Specify in the Parameter File
You should not specify the following two types of parameters in your parameter
files:
■
■
Parameters that you never alter except when instructed to do so by Oracle
Corporation to resolve a problem
Derived parameters, which normally do not need altering because their values
are calculated automatically by the Oracle database server
Initialization Parameters 1-11
Reading the Parameter Descriptions
When Parameters Are Set Incorrectly
Some parameters have a minimum setting below which an Oracle instance will not
start. For other parameters, setting the value too low or too high may cause Oracle
to perform badly, but it will still run. Also, Oracle may convert some values outside
the acceptable range to usable levels.
If a parameter value is too low or too high, or you have reached the maximum for
some resource, then Oracle returns an error. Frequently, you can wait a short while
and retry the operation when the system is not as busy. If a message occurs
repeatedly, then you should shut down the instance, adjust the relevant parameter,
and restart the instance.
Reading the Parameter Descriptions
The parameter descriptions in this chapter adhere to the following format.
PARAMETER_NAME
Parameter type
Specifies the type of the parameter:
■
■
■
■
■
A Boolean parameter accepts either true or false as
its value.
A string parameter accepts any sequence of characters as
its value, subject to the syntax for the parameter.
An integer parameter accepts a 4-byte value that can
range from 0 to 232-1.
A parameter file parameter accepts an initialization
parameter file specification as its value.
A big integer parameter accepts an 8-byte value that can
range from 0 to 264-1. You specify a value for a big
integer as an integer together with an optional modifier
such as K, M, or G, which respectively denotes kilobytes,
megabytes, or gigabytes.
For example, 1000, 100 KB, 50 MB and 2 GB are valid
specifications for big integers.
Syntax
1-12
Oracle9i Database Reference
For string and big integer parameters, specifies the valid
syntax for specifying the parameter.
Reading the Parameter Descriptions
Default value
Specifies the value this parameter assumes if not explicitly
specified.
Parameter class
Specifies whether the parameter is dynamic or static. If
dynamic, then it also specifies whether its value can be
changed by an ALTER SESSION or ALTER SYSTEM
statement. ALTER SESSION overrides the instance-wide
setting of the parameter for the current session only. You can
restore the instance-wide setting for that session only by
issuing another ALTER SESSION statement. ALTER
SYSTEM sets or changes the value of the parameter for all
sessions.
Range of values
Specifies the valid range of values that this parameter can
assume, shown as a minimum and maximum value. Not
applicable to all parameters.
Real Application
Clusters
Specifies how the values for this parameter must be specified
for multiple instances in a cluster database environment. Not
applicable to all parameters.
For each parameter, paragraphs following these details further describe the
parameter and the effects of different settings.
Initialization Parameters 1-13
Parameter Descriptions
Parameter Descriptions
Descriptions of the individual initialization parameters follow in alphabetical order.
Initialization parameter values apply to the entire database, not to an individual
user, unless otherwise specified.
Note: Parameters that have become obsolete are not documented.
See Also:
■
■
1-14
Oracle9i Database Migration for information about obsolete
parameters
Your system release bulletins or other operating system-specific
Oracle documentation
Oracle9i Database Reference
AQ_TM_PROCESSES
ACTIVE_INSTANCE_COUNT
Parameter type
Integer
Default value
There is no default value.
Parameter class
Static
Range of values
1 or >= the number of instances in the cluster. (Values other
than 1 have no effect on the active or standby status of any
instances.)
Real Application
Clusters
You must set this parameter for every instance, and multiple
instances must have the same value.
Note: This parameter functions only in a cluster with only two
instances.
ACTIVE_INSTANCE_COUNT enables you to designate one instance in a
two-instance cluster as the primary instance and the other instance as the secondary
instance. This parameter has no functionality in a cluster with more than two
instances.
When you set this parameter to 1, the first instance you start up becomes the
primary instance and accepts client connections. The second instance starts up as a
secondary instance and can accept client connections only if the first instance fails.
In such an event, the secondary instance becomes the primary instance.
When the failed instance can once again be started up, it starts up as the secondary
instance, and will not accept client connections unless the current primary instance
fails.
See Also: Oracle9i Real Application Clusters Setup and Configuration
for more information on setting this parameter
AQ_TM_PROCESSES
Parameter type
Integer
Default value
0
Parameter class
Dynamic: ALTER SYSTEM
Initialization Parameters 1-15
ARCHIVE_LAG_TARGET
Range of values
0 to 10
AQ_TM_PROCESSES enables time monitoring of queue messages. The times can be
used in messages that specify delay and expiration properties. Values from 1 to 10
specify the number of queue monitor processes created to monitor the messages. If
AQ_TM_PROCESSES is not specified or is set to 0, then the queue monitor is not
created.
See Also: Oracle9i Application Developer’s Guide - Advanced
Queuing for more information about this parameter and Advanced
Queuing
ARCHIVE_LAG_TARGET
Parameter type
Integer
Default value
0 (disabled)
Parameter class
Dynamic: ALTER SYSTEM
Range of values
0 or any integer in [60, 7200]
Real Application
Clusters
Multiple instances should use the same value.
ARCHIVE_LAG_TARGET limits the amount of data that can be lost and effectively
increases the availability of the standby database by forcing a log switch after a
user-specified time period elapses.
A 0 value disables the time-based thread advance feature; otherwise, the value
represents the number of seconds. Values larger than 7200 seconds are not of much
use in maintaining a reasonable lag in the standby database. The typical, or
recommended value is 1800 (30 minutes). Extremely low values can result in
frequent log switches, which could degrade performance; such values can also
make the archiver process too busy to archive the continuously generated logs.
See Also: Oracle9i Data Guard Concepts and Administration for
more information about criteria for setting this parameter
1-16
Oracle9i Database Reference
AUDIT_TRAIL
AUDIT_FILE_DEST
Parameter type
String
Syntax
AUDIT_FILE_DEST = ’directory’
Default value
ORACLE_HOME/rdbms/audit
Parameter class
Static
AUDIT_FILE_DEST specifies the directory where Oracle stores auditing files.
AUDIT_SYS_OPERATIONS
Parameter type
Boolean
Default value
false
Parameter class
Static
Range of values
true | false
AUDIT_SYS_OPERATIONS enables or disables the auditing of operations issued by
user SYS, and users connecting with SYSDBA or SYSOPER privileges. The audit
records are written to the operating system’s audit trail.
AUDIT_TRAIL
Parameter type
String
Syntax
AUDIT_TRAIL = {NONE | FALSE | DB | TRUE | OS}
Default value
There is no default value.
Parameter class
Static
AUDIT_TRAIL enables or disables the automatic writing of rows to the audit trail.
Values:
■
NONE or FALSE
Initialization Parameters 1-17
BACKGROUND_CORE_DUMP
Audit records are not written.
■
OS
Enables system-wide auditing and causes audited records to be written to the
operating system’s audit trail.
■
DB or TRUE
Enables system-wide auditing and causes audited records to be written to the
database audit trail (the SYS.AUD$ table).
You can use the SQL statement AUDIT to set auditing options regardless of the
setting of this parameter.
BACKGROUND_CORE_DUMP
Parameter type
String
Syntax
BACKGROUND_CORE_DUMP = {partial | full}
Default value
partial
Parameter class
Static
BACKGROUND_CORE_DUMP specifies whether Oracle includes the SGA in the core
file for Oracle background processes.
Values:
■
partial
Oracle does not include the SGA in the core dump.
■
full
Oracle includes the SGA in the core dump.
See Also: "SHADOW_CORE_DUMP" on page 1-149
BACKGROUND_DUMP_DEST
1-18
Parameter type
String
Syntax
BACKGROUND_DUMP_DEST = {pathname | directory}
Oracle9i Database Reference
BACKUP_TAPE_IO_SLAVES
Default value
Operating system-dependent
Parameter class
Dynamic: ALTER SYSTEM
Range of values
Any valid local path, directory, or disk
BACKGROUND_DUMP_DEST specifies the pathname (directory or disc) where
debugging trace files for the background processes (LGWR, DBWn, and so on) are
written during Oracle operations.
An alert file in the directory specified by BACKGROUND_DUMP_DEST logs significant
database events and messages. Anything that affects the database instance or global
database is recorded here. The alert file is a normal text file. Its filename is operating
system-dependent. For platforms that support multiple instances, it takes the form
alert_sid.log, where sid is the system identifier. This file grows slowly, but
without limit, so you might want to delete it periodically. You can delete the file
even when the database is running.
See Also:
■
■
■
Oracle9i Database Administrator’s Guide for more information on
setting this parameter and on alert files
Your operating system-specific Oracle documentation for the
default value of this parameter
"USER_DUMP_DEST" on page 1-169 for information on
setting a destination for server process trace files
BACKUP_TAPE_IO_SLAVES
Parameter type
Boolean
Default value
false
Parameter class
Dynamic: ALTER SYSTEM ... DEFERRED
Range of values
true | false
BACKUP_TAPE_IO_SLAVES specifies whether I/O server processes (also called
slaves) are used by the Recovery Manager to back up, copy, or restore data to tape.
When the value is set to true, Oracle uses an I/O server process to write to or read
from a tape device. When the value is set to false (the default), Oracle does not
use I/O server process for backups. Instead, the shadow process engaged in the
backup accesses the tape device.
Initialization Parameters 1-19
BITMAP_MERGE_AREA_SIZE
Note: You cannot perform duplexed backups unless you enable
this parameter. Otherwise, Oracle returns an error. When this
parameter is enabled, Recovery Manager will configure as many
server processes as needed for the number of backup copies
requested.
See Also:
■
■
Oracle9i Recovery Manager User’s Guide for more information on
duplexed backups
"DBWR_IO_SLAVES" on page 1-46
BITMAP_MERGE_AREA_SIZE
Parameter type
Integer
Default value
1048576 (1 MB)
Parameter class
Static
Range of values
Operating system-dependent
Note: Oracle does not recommend using the BITMAP_MERGE_
AREA_SIZE parameter unless the instance is configured with the
shared server option. Oracle recommends that you enable
automatic sizing of SQL working areas by setting PGA_
AGGREGATE_TARGET instead. BITMAP_MERGE_AREA_SIZE is
retained for backward compatibility.
BITMAP_MERGE_AREA_SIZE is relevant only for systems containing bitmap
indexes. It specifies the amount of memory Oracle uses to merge bitmaps retrieved
from a range scan of the index. The default value is 1 MB. A larger value usually
improves performance, because the bitmap segments must be sorted before being
merged into a single bitmap.
See Also: Oracle9i Database Performance Tuning Guide and Reference
for more information on setting this parameter
1-20
Oracle9i Database Reference
BUFFER_POOL_KEEP
BLANK_TRIMMING
Parameter type
Boolean
Default value
false
Parameter class
Static
Range of values
true | false
BLANK_TRIMMING specifies the data assignment semantics of character datatypes.
Values:
■
TRUE
Allows the data assignment of a source character string or variable to a
destination character column or variable even though the source length is
longer than the destination length. In this case, however, the additional length
over the destination length is all blanks. This value complies with the semantics
of SQL92 Transitional Level and above.
■
FALSE
Disallows the data assignment if the source length is longer than the destination
length and reverts to SQL92 Entry Level semantics.
BUFFER_POOL_KEEP
Parameter type
String
Syntax
BUFFER_POOL_KEEP = {integer |
(BUFFERS:integer, LRU_LATCHES:integer)}
where integer is the number of buffers and, optionally, the
number of LRU latches.
Default value
There is no default value.
Parameter class
Static
Initialization Parameters 1-21
BUFFER_POOL_RECYCLE
Note: This parameter is deprecated in favor of the DB_KEEP_
CACHE_SIZE parameter. Oracle recommends that you use DB_
KEEP_CACHE_SIZE instead. Also, BUFFER_POOL_KEEP cannot be
combined with the new dynamic DB_KEEP_CACHE_SIZE
parameter; combining these parameters in the same parameter file
will produce an error. BUFFER_POOL_KEEP is retained for
backward compatibility only.
BUFFER_POOL_KEEP lets you save objects in the buffer cache by setting aside a
portion of the total number of buffers (the value of the DB_BLOCK_BUFFERS
parameter) as a KEEP buffer pool. You can also allocate to the KEEP buffer pool a
specified portion of the total number of LRU latches.
The string value can take one of two forms. You can simply specify a buffer count:
BUFFER_POOL_KEEP = 5
Or, you can specify a combination of buffers and LRU latches. Specifying LRU
latches is optional:
BUFFER_POOL_KEEP = (BUFFERS:400, LRU_LATCHES:3)
This parameter is most useful in combination with the BUFFER_POOL_RECYCLE
parameter.
See Also:
■
■
"BUFFER_POOL_RECYCLE" on page 1-22
Oracle9i Database Performance Tuning Guide and Reference for
information on setting these parameters and on using multiple
buffer pools
BUFFER_POOL_RECYCLE
Parameter type
1-22
Oracle9i Database Reference
String
BUFFER_POOL_RECYCLE
Syntax
BUFFER_POOL_RECYCLE = {integer |
(BUFFERS:integer, LRU_LATCHES:integer)}
where integer is the number of buffers and, optionally, the
number of LRU latches.
Default value
There is no default value.
Parameter class
Static
Note: This parameter is deprecated in favor of the DB_RECYCLE_
CACHE_SIZE parameter. Oracle recommends that you use DB_
RECYCLE_CACHE_SIZE instead. Also, BUFFER_POOL_RECYCLE
cannot be combined with the new dynamic DB_RECYCLE_CACHE_
SIZE parameter; combining these parameters in the same
parameter file will produce an error. BUFFER_POOL_RECYCLE is
retained for backward compatibility only.
BUFFER_POOL_RECYCLE lets you limit the size of objects in the buffer cache by
setting aside a portion of the total number of buffers (the value of the DB_BLOCK_
BUFFERS parameter) as a RECYCLE buffer pool. You can also allocate to the
RECYCLE buffer pool a specified portion of the total number of LRU latches.
The string value can take one of two forms. You can simply specify a buffer count:
BUFFER_POOL_RECYCLE = 5
Or, you can specify a combination of buffers and LRU latches. Specifying LRU
latches is optional:
BUFFER_POOL_RECYCLE = (BUFFERS:50, LRU_LATCHES:1)
This parameter is most useful in combination with the BUFFER_POOL_KEEP
parameter.
See Also:
■
■
"BUFFER_POOL_KEEP" on page 1-21
Oracle9i Database Performance Tuning Guide and Reference for
information on setting these parameters and on using multiple
buffer pools
Initialization Parameters 1-23
CIRCUITS
CIRCUITS
Parameter type
Integer
Default value
Derived:
■
■
Parameter class
If you are using shared server architecture, then the
value of SESSIONS
If you are not using the shared server architecture, then
the value is 0
Static
CIRCUITS specifies the total number of virtual circuits that are available for
inbound and outbound network sessions. It is one of several parameters that
contribute to the total SGA requirements of an instance.
See Also:
■
■
Oracle9i Database Concepts for more information on memory
structures and processes
"DB_BLOCK_BUFFERS" on page 1-33 and "TRANSACTIONS"
on page 1-165, which also contribute to SGA requirements
CLUSTER_DATABASE
Parameter type
Boolean
Default value
false
Parameter class
Static
Range of values
true | false
Real Application
Clusters
Multiple instances must have the same value.
CLUSTER_DATABASE is an Oracle9i Real Application Clusters parameter that
specifies whether or not Oracle9i Real Application Clusters is enabled.
See Also: Oracle9i Real Application Clusters Administration
1-24
Oracle9i Database Reference
CLUSTER_INTERCONNECTS
CLUSTER_DATABASE_INSTANCES
Parameter type
Integer
Default value
1
Parameter class
Static
Range of values
Any nonzero value
CLUSTER_DATABASE_INSTANCES is an Oracle9i Real Application Clusters
parameter that specifies the number of instances that are configured as part of your
cluster database. You must set this parameter for every instance. Normally you
should set this parameter to the number of instances in your Oracle9i Real
Application Clusters environment. A proper setting for this parameter can improve
memory use.
Oracle uses the value of this parameter to compute the default value of the LARGE_
POOL_SIZE parameter when the PARALLEL_AUTOMATIC_TUNING parameter is set
to true.
See Also:
■
■
Oracle9i Database Performance Tuning Guide and Reference for
more information on tuning parallel execution
Oracle9i Real Application Clusters Administration for information
on Oracle9i Real Application Clusters
CLUSTER_INTERCONNECTS
Parameter type
String
Syntax
CLUSTER_INTERCONNECTS = ifn [: ifn ... ]
Default value
There is no default value.
Parameter class
Static
Range of values
One or more IP addresses, separated by colons
CLUSTER_INTERCONNECTS provides Oracle with information about additional
cluster interconnects available for use in Oracle9i Real Application Clusters
environments.
Initialization Parameters 1-25
COMMIT_POINT_STRENGTH
The CLUSTER_INTERCONNECTS parameter can be used to override the default
interconnect with a preferred cluster traffic network. This parameter is useful in
Data Warehouse systems that have reduced availibility requirements and high
interconnect bandwidth demands. You can also use CLUSTER_INTERCONNECTS to
override the default interconnect chosen by Oracle.
For example, if you are running two instances of Oracle for two databases on the
same machine, then you can load balance the interconnect traffic to different
physical interconnects. This does not reduce Oracle availability.
See Also: Oracle9i Real Application Clusters Administration
COMMIT_POINT_STRENGTH
Parameter type
Integer
Default value
1
Parameter class
Static
Range of values
0 to 255
COMMIT_POINT_STRENGTH is relevant only in distributed database systems. It
specifies a value that determines the commit point site in a distributed transaction.
The node in the transaction with the highest value for COMMIT_POINT_STRENGTH
will be the commit point site.
The commit point site of a database should reflect the amount of critical shared data
in the database. For example, a database on a mainframe computer typically shares
more data among users than one on a personal computer. Therefore, COMMIT_
POINT_STRENGTH should be set to a higher value for the mainframe computer.
The commit point site stores information about the status of transactions. Other
computers in a distributed transaction require this information during Oracle’s
two-phase commit, so it is desirable to have machines that are always available as
commit point sites. Therefore, set COMMIT_POINT_STRENGTH to a higher value on
your more available machines.
1-26
Oracle9i Database Reference
COMPATIBLE
See Also:
■
■
Oracle9i Database Concepts and Oracle9i Database Administrator’s
Guide for information on two-phase commit
Your operating system-specific Oracle documentation for the
default value of this parameter
COMPATIBLE
Parameter type
String
Syntax
COMPATIBLE = release_number
Default value
8.1.0
Parameter class
Static
Range of values
Default release to current release
Real Application
Clusters
Multiple instances must have the same value.
COMPATIBLE allows you to use a new release, while at the same time guaranteeing
backward compatibility with an earlier release. This is helpful if it becomes
necessary to revert to the earlier release.
This parameter specifies the release with which the Oracle server must maintain
compatibility. It allows you to take advantage of the maintenance improvements of
a new release immediately in your production systems without testing the new
functionality in your environment. Some features of the current release may be
restricted.
When using the standby database feature, this parameter must have the same value
on the primary and standby databases, and the value must be 7.3.0.0.0 or higher.
The default value is the earliest release with which compatibility can be guaranteed.
The value of COMPATIBLE must be set to 8.1.0 or higher in order to use stored
columns of UROWID type. You can use ROWID pseudo columns for index-organized
tables regardless of the parameter setting.
See Also: Oracle9i Database Migration for more information on setting
this parameter
Initialization Parameters 1-27
CONTROL_FILE_RECORD_KEEP_TIME
CONTROL_FILE_RECORD_KEEP_TIME
Parameter type
Integer
Default value
7 (days)
Parameter class
Dynamic: ALTER SYSTEM
Range of values
0 to 365 (days)
CONTROL_FILE_RECORD_KEEP_TIME specifies the minimum number of days
before a reusable record in the control file can be reused. In the event a new record
needs to be added to a reusable section and the oldest record has not aged enough,
the record section expands. If this parameter is set to 0, then reusable sections never
expand, and records are reused as needed.
Note: This parameter applies only to records in the control file that are
circularly reusable (such as archive log records and various backup
records). 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.
See Also:
■
"CONTROL_FILES" on page 1-28
■
Oracle9i Database Concepts
■
Oracle9i User-Managed Backup and Recovery Guide
CONTROL_FILES
Parameter type
String
Syntax
CONTROL_FILES = filename [, filename [...] ]
Note: The control file name can be an OMF (Oracle Managed
Files) name. This occurs when the control file is re-created
using the CREATE CONTROLFILE REUSE statement.
1-28
Default value
Operating system-dependent
Parameter class
Static
Oracle9i Database Reference
CPU_COUNT
Range of values
1 to 8 filenames
Real Application
Clusters
Multiple instances must have the same value.
Every database has a control file, which contains entries that describe the structure
of the database (such as its name, the timestamp of its creation, and the names and
locations of its datafiles and redo files). CONTROL_FILES specifies one or more
names of control files, separated by commas.
Oracle Corporation recommends that you multiplex multiple control files on
different devices or mirror the file at the operating system level.
See Also:
■
Oracle9i Database Performance Tuning Guide and Reference
■
Oracle9i Database Administrator’s Guide
CORE_DUMP_DEST
Parameter type
String
Syntax
CORE_DUMP_DEST = directory
Default value
ORACLE_HOME/DBS
Parameter class
Dynamic: ALTER SYSTEM
CORE_DUMP_DEST is primarily a UNIX parameter and may not be supported on
your platform. It specifies the directory where Oracle dumps core files.
CPU_COUNT
Parameter type
Integer
Default value
Set automatically by Oracle
Parameter class
Static
Range of values
0 to unlimited
Initialization Parameters 1-29
CREATE_BITMAP_AREA_SIZE
Caution: On most platforms, Oracle automatically sets the value
of CPU_COUNT to the number of CPUs available to your Oracle
instance. Do not change the value of CPU_COUNT.
CPU_COUNT specifies the number of CPUs available to Oracle. On single-CPU
computers, the value of CPU_COUNT is 1.
See Also: Your operating system-specific Oracle documentation
for more information about this parameter
CREATE_BITMAP_AREA_SIZE
Parameter type
Integer
Default value
8388608 (8 MB)
Parameter class
Static
Range of values
Operating system-dependent
Note: Oracle does not recommend using the CREATE_BITMAP_
AREA_SIZE parameter unless the instance is configured with the
shared server option. Oracle recommends that you enable
automatic sizing of SQL working areas by setting PGA_
AGGREGATE_TARGET instead. CREATE_BITMAP_AREA_SIZE is
retained for backward compatibility.
CREATE_BITMAP_AREA_SIZE is relevant only for systems containing bitmap
indexes. It specifies the amount of memory (in bytes) allocated for bitmap creation.
The default value is 8 MB. A larger value may speed up index creation.
Cardinality is the number of unique values in a column in relation to the number of
rows in the table. If cardinality is very small, you can set a small value for this
parameter. For example, if cardinality is only 2, then the value can be on the order
of kilobytes rather than megabytes. As a general rule, the higher the cardinality, the
more memory is needed for optimal performance.
See Also: Oracle9i Database Performance Tuning Guide and Reference
for more information on using bitmap indexes
1-30
Oracle9i Database Reference
CURSOR_SPACE_FOR_TIME
CURSOR_SHARING
Parameter type
String
Syntax
CURSOR_SHARING = {SIMILAR | EXACT | FORCE}
Default value
EXACT
Parameter class
Dynamic: ALTER SESSION, ALTER SYSTEM
CURSOR_SHARING determines what kind of SQL statements can share the same
cursors.
Values:
■
FORCE
Forces statements that may differ in some literals, but are otherwise identical, to
share a cursor, unless the literals affect the meaning of the statement.
■
SIMILAR
Causes statements that may differ in some literals, but are otherwise identical,
to share a cursor, unless the literals affect either the meaning of the statement or
the degree to which the plan is optimized.
■
EXACT
Only allows statements with identical text to share the same cursor.
Note: Forcing cursor sharing among similar (but not identical)
statements can have unexpected results in some DSS applications,
or applications that use stored outlines.
See Also: Oracle9i Database Performance Tuning Guide and Reference
for information on setting this parameter in these and other
environments
CURSOR_SPACE_FOR_TIME
Parameter type
Boolean
Default value
false
Initialization Parameters 1-31
DB_nK_CACHE_SIZE
Parameter class
Static
Range of values
true | false
CURSOR_SPACE_FOR_TIME lets you use more space for cursors in order to save
time. It affects both the shared SQL area and the client’s private SQL area.
Values:
■
TRUE
Shared SQL areas are kept pinned in the shared pool. As a result, shared SQL
areas are not aged out of the pool as long as an open cursor references them.
Because each active cursor’s SQL area is present in memory, execution is faster.
However, the shared SQL areas never leave memory while they are in use.
Therefore, you should set this parameter to TRUE only when the shared pool is
large enough to hold all open cursors simultaneously.
In addition, a setting of TRUE retains the private SQL area allocated for each
cursor between executions instead of discarding it after cursor execution, saving
cursor allocation and initialization time
■
FALSE
Shared SQL areas can be deallocated from the library cache to make room for
new SQL statements.
Note: If this parameter is set to TRUE, the SERIAL_REUSE
parameter is disabled.
See Also:
■
■
Oracle9i Database Concepts and Oracle9i Database Performance
Tuning Guide and Reference
"SERIAL _REUSE" on page 1-145
DB_nK_CACHE_SIZE
1-32
Parameter type
Big integer
Syntax
DB_[2 | 4 | 8 | 16 | 32]K_CACHE_SIZE =
integer [K | M | G]
Oracle9i Database Reference
DB_BLOCK_BUFFERS
Default value
0 (additional block size caches are not configured by default)
Parameter class
Dynamic: ALTER SYSTEM
Range of values
Minimum: the granule size
Maximum: operating system-dependent
DB_nK_CACHE_SIZE (where n = 2, 4, 8, 16, 32) specifies the size of the cache for the
nK buffers. You can set this parameter only when DB_BLOCK_SIZE has a value
other than nK. For example, if DB_BLOCK_SIZE=4096, then it is illegal to specify
the parameter DB_4K_CACHE_SIZE (because the size for the 4 KB block cache is
already specified by DB_CACHE_SIZE).
Do not set this parameter to zero if there are any online tablespaces with an nK
block size.
Platform-specific block size restrictions apply. For example, you cannot set DB_
32K_CACHE_SIZE if the maximum block size on the platform is less than 32 KB.
Also, you cannot set DB_2K_CACHE_SIZE if the minimum block size is greater than
2 KB.
See Also: For more information on block size restrictions, see
your platform specific documentation
DB_BLOCK_BUFFERS
Parameter type
Integer
Default value
Derived: 48 MB / DB_BLOCK_SIZE
Parameter class
Static
Range of values
50 to an operating system-specific maximum
Real Application
Clusters
Multiple instances can have different values, and you can
change the values as needed.
Initialization Parameters 1-33
DB_BLOCK_BUFFERS
Note: This parameter is deprecated in favor of the DB_CACHE_
SIZE parameter. Oracle recommends that you use DB_CACHE_
SIZE instead. Also, DB_BLOCK_BUFFERS cannot be combined with
the new dynamic DB_CACHE_SIZE parameter; combining these
parameters in the same parameter file will produce an error. DB_
BLOCK_BUFFERS is retained for backward compatibility.
DB_BLOCK_BUFFERS specifies the number of database buffers in the buffer cache. It
is one of several parameters that contribute to the total memory requirements of the
SGA of an instance.
This parameter, together with DB_BLOCK_SIZE, determines the total size of the
buffer cache. Effective use of the buffer cache can greatly reduce the I/O load on the
database. DB_BLOCK_SIZE can be specified only when the database is first created,
so you use DB_BLOCK_BUFFERS to control the size of the buffer cache.
The buffers for the "keep" buffer pool and the "recycle" buffer pool come out of the
buffer cache. In addition, each LRU list in the buffer cache must have at least 50
buffers. Therefore, if you specify BUFFER_POOL_KEEP and BUFFER_POOL_
RECYCLE, be sure the value of DB_BLOCK_BUFFERS conforms to the following
formula:
DB_BLOCK_BUFFERS > #_buffers_in_"keep"_buffer_pool
+ #_BUFFERS_IN_"recycle"_buffer_pool
+ 50*(DB_BLOCK_LRU_LATCHES
- #_lru_latches_in_"keep"_buffer_pool
- #_lru_latches_in_"recycle"_buffer_pool)
If you did not specify any LRU latches in BUFFER_POOL_KEEP and BUFFER_
POOL_RECYCLE, then the values default to 1.
This parameter affects the probability of data block pinging when Oracle9i Real
Application Clusters are enabled: the more buffers, the greater the chance of
pinging.
1-34
Oracle9i Database Reference
DB_BLOCK_CHECKSUM
See Also:
■
■
■
Oracle9i Database Performance Tuning Guide and Reference,
"BUFFER_POOL_KEEP" on page 1-21, and "BUFFER_POOL_
RECYCLE" on page 1-22 for more information on setting this
parameter
Oracle9i Real Application Clusters Concepts for more information
on data block pinging
Your operating system-specific Oracle documentation
DB_BLOCK_CHECKING
Parameter type
Boolean
Default value
false
Parameter class
Dynamic: ALTER SESSION, ALTER SYSTEM
Range of values
true | false
DB_BLOCK_CHECKING controls whether Oracle performs block checking for data
blocks. When this parameter is set to true, Oracle performs block checking for all
data blocks. When it is set to false, Oracle does not perform block checking for
blocks in the user tablespaces. However, block checking for the SYSTEM tablespace
is always turned on.
Oracle checks a block by going through the data on the block, making sure it is
self-consistent. Block checking can often prevent memory and data corruption.
Block checking typically causes 1% to 10% overhead, depending on workload. The
more updates or inserts in a workload, the more expensive it is to turn on block
checking. You should set DB_BLOCK_CHECKING to true if the performance
overhead is acceptable.
DB_BLOCK_CHECKSUM
Parameter type
Boolean
Default value
true
Parameter class
Dynamic: ALTER SYSTEM
Initialization Parameters 1-35
DB_BLOCK_SIZE
Range of values
true | false
DB_BLOCK_CHECKSUM determines whether DBWn and the direct loader will
calculate a checksum (a number calculated from all the bytes stored in the block)
and store it in the cache header of every data block when writing it to disk.
Checksums are verified when a block is read-only if this parameter is true and the
last write of the block stored a checksum. In addition, Oracle gives every log block a
checksum before writing it to the current log.
If this parameter is set to false, DBWn calculates checksums only for the SYSTEM
tablespace, but not for user tablespaces.
Checksums allow Oracle to detect corruption caused by underlying disks, storage
systems, or I/O systems. Turning on this feature typically causes only an additional
1% to 2% overhead. Therefore, Oracle Corporation recommends that you set DB_
BLOCK_CHECKSUM to true.
DB_BLOCK_SIZE
Parameter type
Integer
Default value
2048
Parameter class
Static
Range of values
2048 to 32768, but your operating system may have a
narrower range
Real Application
Clusters
You must set this parameter for every instance, and multiple
instances must have the same value.
Caution: Set this parameter at the time of database creation. Do
not alter it afterward.
DB_BLOCK_SIZE specifies the size (in bytes) of Oracle database blocks. Typical
values are 2048 and 4096. The value for DB_BLOCK_SIZE in effect at the time you
create the database determines the size of the blocks. The value must remain set to
its initial value.
If you are using Oracle9i Real Application Clusters, then this parameter affects the
maximum value of the FREELISTS storage parameter for tables and indexes.
Oracle uses one database block for each freelist group. Decision support system
1-36
Oracle9i Database Reference
DB_CACHE_ADVICE
(DSS) and data warehouse database environments tend to benefit from larger block
size values.
See Also:
■
■
■
■
Oracle9i Database Performance Tuning Guide and Reference and
Oracle9i Database Administrator’s Guide for information on
setting this parameter
Oracle9i SQL Reference for information on freelist groups
Oracle9i Database Performance Tuning Guide and Reference for
more information on the DSS and data warehouse
environments
Oracle9i Database Concepts for general information on block
sizes
DB_CACHE_ADVICE
Parameter type
String
Syntax
DB_CACHE_ADVICE = {ON | READY | OFF}
Default value
If STATISTICS_LEVEL is set to TYPICAL or ALL, then ON
If STATISTICS_LEVEL is set to BASIC, then OFF
Parameter class
Dynamic: ALTER SYSTEM
DB_CACHE_ADVICE enables or disables statistics gathering used for predicting
behavior with different cache sizes through the V$DB_CACHE_ADVICE performance
view.
Values:
■
OFF
Advisory is turned off and the memory for the advisory is not allocated.
■
READY
Advisory is turned off but the memory for the advisory remains allocated.
Allocating the memory before the advisory is actually turned on avoids the risk
of an error when you switch the parameter to ON.
Initialization Parameters 1-37
DB_CACHE_SIZE
If the parameter is switched to this state from ON, the contents of the view are
preserved and the memory for the advisory is retained.
If the parameter is switched to this state from OFF, you may get an error.
■
ON
Advisory is turned on. CPU and memory overheads are incurred. Attempting
to set the parameter to this state when it is already in the OFF state may result in
an error. Otherwise, the view (V$DB_CACHE_ADVICE) is reset and statistics are
gathered to the newly refreshed view.
If the parameter is in the READY state, you can set it to ON without any errors
because the memory is already allocated. The view is reset and statistics are
displayed in the newly refreshed view.
DB_CACHE_SIZE
Parameter type
Big integer
Syntax
DB_CACHE_SIZE = integer [K | M | G]
Default value
48 MB, rounded up to the nearest granule size
Parameter class
Dynamic: ALTER SYSTEM
DB_CACHE_SIZE specifies the size of the DEFAULT buffer pool for buffers with the
primary block size (the block size defined by the DB_BLOCK_SIZE parameter).
The value must be at least the size of one granule (smaller values are automatically
rounded up to the granule size). A value of zero is illegal because zero is the size of
the DEFAULT pool for the standard block size, which is the block size for the
SYSTEM tablespace.
DB_CREATE_FILE_DEST
1-38
Parameter type
String
Syntax
DB_CREATE_FILE_DEST = directory
Default value
There is no default value.
Parameter class
Dynamic: ALTER SESSION, ALTER SYSTEM
Oracle9i Database Reference
DB_DOMAIN
DB_CREATE_FILE_DEST sets the default location for Oracle-managed datafiles.
This location is also used as the default for Oracle-managed control files and online
redo logs if DB_CREATE_ONLINE_LOG_DEST_n is not specified.
You can specify a file system directory as the default location for the creation of
datafiles, control files, and online redo logs. However, the directory must already
exist; Oracle does not create it. The directory must have appropriate permissions
that allow Oracle to create files in it. Oracle generates unique names for the files,
and a file thus created is an Oracle-managed file.
DB_CREATE_ONLINE_LOG_DEST_n
Parameter type
String
Syntax
DB_CREATE_ONLINE_LOG_DEST_[1 | 2 | 3 | 4 | 5]
= directory
Default value
There is no default value.
Parameter class
Dynamic: ALTER SESSION, ALTER SYSTEM
DB_CREATE_ONLINE_LOG_DEST_n (where n = 1, 2, 3, ... 5) sets the default location
for Oracle-managed control files and online redo logs.
You should specify at least two parameters: DB_CREATE_ONLINE_LOG_DEST_1
and DB_CREATE_ONLINE_LOG_DEST_2. This provides greater fault tolerance for
the logs if one of the destinations should fail.
If more than one directory is specified, then the control file or online redo log is
multiplexed across the directories. One member of each online redo log is created in
each directory, and one control file is created in each directory.
The directory must already exist; Oracle does not create it. The directory must have
appropriate permissions that allow Oracle to create files in it. Oracle generates
unique names for the files, and a file thus created is an Oracle-managed file.
DB_DOMAIN
Parameter type
String
Syntax
DB_DOMAIN = domain_name
Initialization Parameters 1-39
DB_FILE_MULTIBLOCK_READ_COUNT
Default value
There is no default value.
Parameter class
Static
Range of values
Any legal string of name components, separated by periods
and up to 128 characters long (including the periods). This
value cannot be NULL.
Real Application
Clusters
You must set this parameter for every instance, and multiple
instances must have the same value.
In a distributed database system, DB_DOMAIN specifies the logical location of the
database within the network structure. You should set this parameter if this
database is or ever will be part of a distributed system. The value consists of the
extension components of a global database name, consisting of valid identifiers,
separated by periods. Oracle Corporation recommends that you specify DB_
DOMAIN as a unique string for all databases in a domain.
This parameter allows one department to create a database without worrying that it
might have the same name as a database created by another department. If one
sales department’s DB_DOMAIN is JAPAN.ACME.COM, then their SALES database
(SALES.JAPAN.ACME.COM) is uniquely distinguished from another database with
DB_NAME = SALES but with DB_DOMAIN = US.ACME.COM.
If you omit the domains from the name of a database link, Oracle expands the name
by qualifying the database with the domain of your local database as it currently
exists in the data dictionary, and then stores the link name in the data dictionary.
The characters valid in a database domain name are: alphanumeric characters,
underscore (_), and number sign (#).
See Also:
■
■
Oracle9i Database Performance Tuning Guide and Reference for
more information on setting this parameter
The data dictionary view "GLOBAL_NAME" on page 2-240
DB_FILE_MULTIBLOCK_READ_COUNT
1-40
Parameter type
Integer
Default value
8
Parameter class
Dynamic: ALTER SESSION, ALTER SYSTEM
Oracle9i Database Reference
DB_FILE_NAME_CONVERT
Range of values
Operating system-dependent
DB_FILE_MULTIBLOCK_READ_COUNT is one of the parameters you can use to
minimize I/O during table scans. It specifies the maximum number of blocks read
in one I/O operation during a sequential scan. The total number of I/Os needed to
perform a full table scan depends on such factors as the size of the table, the
multiblock read count, and whether parallel execution is being utilized for the
operation.
Online transaction processing (OLTP) and batch environments typically have values
in the range of 4 to 16 for this parameter. DSS and data warehouse environments
tend to benefit most from maximizing the value of this parameter. The optimizer is
more likely to choose a full table scan over an index if the value of this parameter is
high.
The maximum value is always less than the operating system's maximum I/O size
expressed as Oracle blocks ((max I/O size)/DB_BLOCK_SIZE). If you set this
parameter to a value greater than the maximum, Oracle uses the maximum.
See Also:
■
■
Oracle9i Database Performance Tuning Guide and Reference for
more information on setting this parameter
Your operating system-specific Oracle documentation for the
default value of this parameter
DB_FILE_NAME_CONVERT
Parameter type
String
Initialization Parameters 1-41
DB_FILE_NAME_CONVERT
Syntax
DB_FILE_NAME_CONVERT = [(]’string1’ ,
’string2’ , ’string3’ , ’string4’ , ...[)]
Where:
■
string1 is the pattern of the primary database filename
■
string2 is the pattern of the standby database filename
■
string3 is the pattern of the primary database filename
■
string4 is the pattern of the standby database filename
You can use as many pairs of primary and standby
replacement strings as required. You can use single or
double quotation marks. The parentheses are optional.
Following are example settings that are acceptable:
DB_FILE_NAME_CONVERT =
(’/dbs/t1/’,’/dbs/t1/s_’,’dbs/t2/
’,’dbs/t2/s_’)
Default value
None
Parameter class
Static
DB_FILE_NAME_CONVERT is useful for creating a duplicate database for recovery
purposes. It converts the filename of a new datafile on the primary database to a
filename on the standby database. If you add a datafile to the primary database, you
must add a corresponding file to the standby database. When the standby database
is updated, this parameter converts the datafile name on the primary database to
the datafile name on the standby database. The file on the standby database must
exist and be writable, or the recovery process will halt with an error.
If you specify an odd number of strings (the last string has no corresponding
replacement string), an error is signalled during startup. If the filename being
converted matches more than one pattern in the pattern/replace string list, the first
matched pattern takes effect. There is no limit on the number of pairs that you can
specify in this parameter (other than the hard limit of the maximum length of
multivalue parameters).
Set the value of this parameter to two strings. The first string is the pattern found in
the datafile names on the primary database. The second string is the pattern found
in the datafile names on the standby database.
1-42
Oracle9i Database Reference
DB_FILES
You can also use DB_FILE_NAME_CONVERT to rename the datafiles in the clone
controlfile when setting up a clone database during tablespace point-in-time
recovery.
See Also:
■
Oracle9i User-Managed Backup and Recovery Guide
■
Oracle9i Data Guard Concepts and Administration
■
Oracle9i Recovery Manager User’s Guide
DB_FILES
Parameter type
Integer
Default value
200
Parameter class
Static
Range of values
Minimum: the largest among the absolute file numbers of
the datafiles in the database
Maximum: operating system-dependent
Real Application
Clusters
You must set this parameter for every instance, and multiple
instances must have the same value.
DB_FILES specifies the maximum number of database files that can be opened for
this database. The maximum valid value is the maximum number of files, subject to
operating system constraint, that will ever be specified for the database, including
files to be added by ADD DATAFILE statements.
If you increase the value of DB_FILES, then you must shut down and restart all
instances accessing the database before the new value can take effect. If you have a
primary and standby database, then they should have the same value for this
parameter.
See Also:
■
■
Oracle9i Real Application Clusters Administration for information
on setting this parameter in an Oracle9i Real Application
Clusters environment
Your operating system-specific Oracle documentation for the
default value of this parameter
Initialization Parameters 1-43
DB_KEEP_CACHE_SIZE
DB_KEEP_CACHE_SIZE
Parameter type
Big integer
Syntax
DB_KEEP_CACHE_SIZE = integer [K | M | G]
Default value
0 (KEEP cache is not configured by default)
Parameter class
Dynamic: ALTER SYSTEM
Range of values
Minimum: the granule size
Maximum: operating system-dependent
DB_KEEP_CACHE_SIZE specifies the size of the KEEP buffer pool. The size of the
buffers in the KEEP buffer pool is the primary block size (the block size defined by
the DB_BLOCK_SIZE parameter).
DB_NAME
Parameter type
String
Syntax
DB_NAME = database_name
Default value
There is no default value.
Parameter class
Static
Real Application
Clusters
You must set this parameter for every instance. Multiple
instances must have the same value, or the same value must
be specified in the STARTUP OPEN SQL*Plus statement or
the ALTER DATABASE MOUNT SQL statement.
DB_NAME specifies a database identifier of up to 8 characters. If specified, it must
correspond to the name specified in the CREATE DATABASE statement. Although
the use of DB_NAME is optional, you should generally set it before issuing the
CREATE DATABASE statement, and then reference it in that statement.
If you have multiple databases, the value of this parameter should match the Oracle
instance identifier of each one to avoid confusion with other databases running on
the system. The value of DB_NAME should be the same in both the standby and
production initialization parameter files.
1-44
Oracle9i Database Reference
DB_WRITER_PROCESSES
If you do not specify this parameter, you must specify a database name in either the
STARTUP command or the ALTER DATABASE ... MOUNT statement for each
instance of the cluster database.
The following characters are valid in a database name: alphanumeric characters,
underscore (_), number sign (#), and dollar sign ($). No other characters are valid.
Oracle removes double quotation marks before processing the database name.
Therefore you cannot use double quotation marks to embed other characters in the
name. The database name is case insensitive.
See Also: Oracle9i Database Administrator’s Guide and Oracle9i Real
Application Clusters Administration for more information on setting
this parameter
DB_RECYCLE_CACHE_SIZE
Parameter type
Big integer
Syntax
DB_RECYCLE_CACHE_SIZE = integer [K | M | G]
Default value
0 (RECYCLE cache is not configured by default)
Parameter class
Dynamic: ALTER SYSTEM
Range of values
Minimum: the granule size
Maximum: operating system-dependent
DB_RECYCLE_CACHE_SIZE specifies the size of the RECYCLE buffer pool. The size
of the buffers in the RECYCLE pool is the primary block size (the block size defined
by the DB_BLOCK_SIZE parameter).
DB_WRITER_PROCESSES
Parameter type
Integer
Default value
1
Parameter class
Static
Range of values
1 to 20
Initialization Parameters 1-45
DBLINK_ENCRYPT_LOGIN
DB_WRITER_PROCESSES is useful for systems that modify data heavily. It specifies
the initial number of database writer processes for an instance.
See Also:
■
■
Oracle9i Database Concepts for more information on the database
writer processes
Oracle9i Database Performance Tuning Guide and Reference for
information on setting the DBWn parameters
DBLINK_ENCRYPT_LOGIN
Parameter type
Boolean
Default value
false
Parameter class
Static
Range of values
true | false
When you attempt to connect to a database using a password, Oracle encrypts the
password before sending it to the database. DBLINK_ENCRYPT_LOGIN specifies
whether or not attempts to connect to other Oracle servers through database links
should use encrypted passwords.
Values:
■
TRUE
When a connection fails Oracle does not reattempt the connection.
■
FALSE
When a connection fails Oracle reattempts the connection using an unencrypted
version of the password.
DBWR_IO_SLAVES
1-46
Parameter type
Integer
Default value
0
Oracle9i Database Reference
DG_BROKER_CONFIG_FILEn
Parameter class
Static
Range of values
0 to operating system-dependent
DBWR_IO_SLAVES is relevant only on systems with only one database writer
process (DBW0). It specifies the number of I/O server processes used by the DBW0
process. The DBW0 process and its server processes always write to disk. By default,
the value is 0 and I/O server processes are not used.
If you set DBWR_IO_SLAVES to a nonzero value, the number of I/O server
processes used by the ARCH and LGWR processes is set to 4. However, the number of
I/O server processes used by Recovery Manager is set to 4 only if asynchronous
I/O is disabled (either your platform does not support asynchronous I/O or disk_
asynch_io is set to false.
Typically, I/O server processes are used to simulate asynchronous I/O on platforms
that do not support asynchronous I/O or that implement it inefficiently. However,
you can use I/O server processes even when asynchronous I/O is being used. In
that case the I/O server processes will use asynchronous I/O.
I/O server processes are also useful in database environments with very large I/O
throughput, even if asynchronous I/O is enabled.
See Also: "BACKUP_TAPE_IO_SLAVES" on page 1-19
DG_BROKER_CONFIG_FILEn
Parameter type
String
Syntax
DG_BROKER_CONFIG_FILE[1 | 2] = filename
Default value
Operating system-dependent
Parameter class
Dynamic: ALTER SYSTEM
Range of values
One filename
DG_BROKER_CONFIG_FILEn (where n = 1, 2) specifies the names for the Data
Guard broker configuration files.
Every database that is part of a Data Guard broker configuration has two broker
configuration files, which contain entries that describe the state and properties of
the configuration (such as the sites and databases that are part of the configuration,
the roles and properties of each of the databases, and the state of each of the
Initialization Parameters 1-47
DG_BROKER_START
elements of the configuration). Two files are provided so as to always maintain the
last known good state of the configuration.
If DG_BROKER_CONFIG_FILEn is not explicitly defined, then it is set to an
operating system-specific default value at instance startup. The parameter can only
be altered when the DMON (Data Guard broker) process is not running.
See Also: Oracle9i Data Guard Broker for more information about
setting this parameter
DG_BROKER_START
Parameter type
Boolean
Default value
false
Parameter class
Dynamic: ALTER SYSTEM
Range of values
true | false
DG_BROKER_START enables Oracle to determine whether or not the DMON (Data
Guard broker) process should be started. DMON is a non-fatal Oracle background
process and exists as long as the instance exists, whenever this parameter is set to
true.
If the site is never going to be configured in a Data Guard broker configuration, then
you can leave the parameter unspecified and accept the default value of false. If
the site is part of a Data Guard broker configuration, then automatic startup of the
DRMON process is simplified by setting DG_BROKER_START to true in the
initialization parameter file.
DISK_ASYNCH_IO
Parameter type
Boolean
Default value
true
Parameter class
Static
Range of values
true | false
DISK_ASYNCH_IO controls whether I/O to datafiles, control files, and logfiles is
asynchronous (that is, whether parallel server processes can overlap I/O requests
1-48
Oracle9i Database Reference
DISPATCHERS
with CPU processing during table scans). If your platform supports asynchronous
I/O to disk, Oracle Corporation recommends that you leave this parameter set to its
default value. However, if the asynchronous I/O implementation is not stable, you
can set this parameter to false to disable asynchronous I/O. If your platform does
not support asynchronous I/O to disk, this parameter has no effect.
If you set DISK_ASYNCH_IO to false, then you should also set DBWR_IO_SLAVES
to a value other than its default of zero in order to simulate asynchronous I/O.
See Also:
■
■
"DBWR_IO_SLAVES" on page 1-46
Oracle9i Database Performance Tuning Guide and Reference for
more information on asynchronous I/O and on setting this
parameter
DISPATCHERS
Parameter type
String
Syntax
DISPATCHERS = ’dispatch_clause’
dispatch_clause::=
(PROTOCOL = protocol) |
(ADDRESS = address) |
(DESCRIPTION = description )
[options_clause]
Initialization Parameters 1-49
DISPATCHERS
options_clause::=
(DISPATCHERS = integer |
SESSIONS = integer |
CONNECTIONS = integer |
TICKS = seconds |
POOL = {1 | ON | YES | TRUE | BOTH |
({IN | OUT} = ticks) | 0 | OFF | NO |
FALSE |
ticks} |
MULTIPLEX = {1 | ON | YES | TRUE |
0 | OFF | NO | FALSE | BOTH | IN | OUT} |
LISTENER = tnsname |
SERVICE = service |
INDEX = integer)
Default value
There is no default value.
Parameter class
Dynamic: ALTER SYSTEM
DISPATCHERS configures dispatcher processes in the shared server architecture.
The parsing software supports a name-value syntax to enable the specification of
attributes in a position-independent case-insensitive manner. For example:
DISPATCHERS = "(PROTOCOL=TCP)(DISPATCHERS=3)"
Specify only one of the following attributes: PROTOCOL, ADDRESS, or
DESCRIPTION. If you specify either ADDRESS or DESCRIPTION, then you can
specify additional network attributes. Doing so supports multi-homed hosts.
dispatch_clause
■
PROTOCOL (PRO or PROT)
The network protocol for which the dispatcher generates a listening endpoint.
■
ADDRESS (ADD or ADDR)
The network protocol address of the endpoint on which the dispatchers listen.
■
1-50
DESCRIPTION (DES or DESC)
Oracle9i Database Reference
DISPATCHERS
The network description of the endpoint on which the dispatchers listen,
including the protocol address.
options_clause
■
DISPATCHERS (DIS or DISP)
The initial number of dispatchers to start. The default is 1.
■
SESSIONS (SES or SESS)
The maximum number of network sessions to allow for each dispatcher. The
default is operating system-specific. Most operating systems have a default of
16 KB.
■
CONNECTIONS (CON or CONN)
The maximum number of network connections to allow for each dispatcher.
The default is operating system-specific.
■
TICKS (TIC or TICK)
The length of a network tick in seconds. The default is 1 second.
■
POOL (POO)
Enables Connection Pooling.
–
An integer indicates that Connection Pooling is enabled for both incoming
and outgoing network connections. The number specified is the timeout in
ticks for both incoming and outgoing network connections.
–
ON, YES, TRUE, and BOTH indicate that Connection Pooling is enabled for
both incoming and outgoing network connections. A default timeout of 10
ticks is used for both incoming and outgoing network connections.
–
IN indicates that Connection Pooling is enabled for incoming network
connections and the default timeout of 10 ticks is used for incoming
network connections.
–
OUT indicates that Connection Pooling is enabled for outgoing network
connections and the default timeout of 10 ticks is used for outgoing
network connections.
–
NO, OFF, and FALSE indicate that Connection Pooling is disabled for both
incoming and outgoing network connections. This is the default.
POOL can also be assigned a name-value string such as: "(IN=10)", "(OUT=20)", or
"(IN=10)(OUT=20)". In such cases:
Initialization Parameters 1-51
DISPATCHERS
■
–
If an IN numeric value is specified, then Connection Pooling is enabled for
incoming connections, and the number specified is the timeout in ticks for
incoming network connections.
–
If an OUT numeric value is specified, then Connection Pooling is enabled for
outgoing network connections, and the number specified is the timeout in
ticks for outgoing network connections.
–
If the numeric value of a specified timeout is 0 or 1, then the default value
of 10 ticks is used.
MULTIPLEX (MUL or MULT)
Enables the Oracle Connection Manager session multiplexing feature.
■
–
The values 1, ON, YES, TRUE, and BOTH indicate that Network Session
Multiplex is enabled for both incoming and outgoing network connections.
–
The value IN indicates that Network Session Multiplex is enabled for
incoming network connections.
–
The value OUT indicates that Network Session Multiplexing is enabled for
outgoing network connections.
–
The values 0, NO, OFF, and FALSE indicate that Network Session
Multiplexing is disabled for both incoming and outgoing network
connections. This is the default.
LISTENER (LIS, LIST)
Specifies the network name of an address or address list of the Oracle Net
listeners with which the dispatchers will register.
The LISTENER attribute facilitates administration of multi-homed hosts. This
attribute specifies the appropriate listeners with which the dispatchers will
register. The LISTENER attribute takes precedence over the LOCAL_LISTENER
and REMOTE_LISTENER parameters. See "LOCAL_LISTENER" on page 1-73
and "REMOTE_LISTENER" on page 1-138.
■
SERVICE (SER, SERV)
The service names the dispatchers register with the listeners.
■
INDEX
Use this parameter in an ALTER SYSTEM SET DISPATCHERS statement to
indicate which dispatcher you want to modify. (If you specify INDEX in the
initialization parameter file, Oracle ignores it.) In an ALTER SYSTEM statement,
INDEX specifies the order in which the parameter’s values were initialized. The
1-52
Oracle9i Database Reference
DML_LOCKS
value ranges from 0 (for the first dispatcher process) to one less than the total
number of dispatchers you define.
For example, if you specify 3 dispatchers in the initialization parameter file, you
would modify the third dispatcher by specifying INDEX=2 in the ALTER
SYSTEM statement. You could also add an additional dispatcher in the ALTER
SYSTEM statement by specifying INDEX=3.
See Also: Oracle9i Net Services Administrator’s Guide for more
information on setting this parameter
DISTRIBUTED_LOCK_TIMEOUT
Parameter type
Integer
Default value
60
Parameter class
Static
Range of values
1 to unlimited
DISTRIBUTED_LOCK_TIMEOUT specifies the amount of time (in seconds) for
distributed transactions to wait for locked resources.
See Also: Oracle9i Database Concepts and Oracle9i Database
Administrator’s Guide for more information on data concurrency
DML_LOCKS
Parameter type
Integer
Default value
Derived: 4 * TRANSACTIONS
Parameter class
Static
Range of values
20 to unlimited; a setting of 0 disables enqueues
Real Application
Clusters
You must set this parameter for every instance, and all
instances must have positive values or all must be 0.
A DML lock is a lock obtained on a table that is undergoing a DML operation
(insert, update, delete). DML_LOCKS specifies the maximum number of DML
locks—one for each table modified in a transaction. The value should equal the
grand total of locks on tables currently referenced by all users. For example, if three
Initialization Parameters 1-53
DRS_START
users are modifying data in one table, then three entries would be required. If three
users are modifying data in two tables, then six entries would be required.
The default value assumes an average of four tables referenced for each transaction.
For some systems, this value may not be enough.
Enqueues are shared memory structures that serialize access to database resources.
If you set the value of DML_LOCKS to 0, enqueues are disabled and performance is
slightly increased. However, you cannot use DROP TABLE, CREATE INDEX, or
explicit lock statements such as LOCK TABLE IN EXCLUSIVE MODE.
Oracle holds more locks during parallel DML than during serial execution.
Therefore, if your database supports a lot of parallel DML, you may need to
increase the value of this parameter.
See Also:
■
■
Oracle9i Database Concepts for a discussion of lock and enqueue
resources needed for parallel DML
Oracle9i Real Application Clusters Administration, Oracle9i
Database Concepts, and Oracle9i Database Administrator’s Guide
for more information on data concurrency
DRS_START
Parameter type
Boolean
Default value
false
Parameter class
Dynamic: ALTER SYSTEM
Range of values
true | false
Note: This parameter is deprecated in favor of the DG_BROKER_
START parameter. Oracle recommends that you use DG_BROKER_
START instead. DRS_START is retained for backward compatibility
only.
DRS_START enables Oracle to determine whether or not the DMON (Data Guard
broker) process should be started. DMON is a non-fatal Oracle background process
and exists as long as the instance exists, whenever this parameter is set to true.
1-54
Oracle9i Database Reference
ENQUEUE_RESOURCES
If the site is never going to be configured in a Data Guard broker configuration, then
you can leave the parameter unspecified and accept the default value of false. If
the site is part of a Data Guard broker configuration, then automatic startup of the
DRMON process is simplified by setting DRS_START to true in the initialization
parameter file.
ENQUEUE_RESOURCES
Parameter type
Integer
Default value
Derived from SESSIONS parameter
Parameter class
Static
Range of values
10 to unlimited
ENQUEUE_RESOURCES sets the number of resources that can be concurrently locked
by the lock manager. An enqueue is a sophisticated locking mechanism that permits
several concurrent processes to share known resources to varying degrees. Any
object that can be used concurrently can be protected with enqueues. For example,
Oracle allows varying levels of sharing on tables: two processes can lock a table in
share mode or in share update mode.
One difference between enqueues and latches is that latches do not entail an
ordered queue of waiting processes as do enqueues. Processes waiting for latches
can either use timers to wake up and retry or (in multiprocessors) spin.
At database startup time, Oracle allocates the number of enqueues specified by the
ENQUEUE_RESOURCES parameter. The default value of ENQUEUE_RESOURCES is
derived from the SESSIONS parameter and is usually adequate, as long as its value
is greater than DML_LOCKS + 20. For three or fewer sessions, the default value is the
number of database files + 20. For 4 to 10 sessions, the default value is the number
of database files + ((SESSIONS - 3) * 5) + 20. For more than 10 sessions, it is the
number of database files + ((SESSIONS - 10) * 2) + 55.
If you explicitly set ENQUEUE_RESOURCES to a value higher than DML_LOCKS + 20,
then Oracle uses the value you provide. Oracle will automatically allocate
additional enqueues from the shared pool as needed if the number specified by
ENQUEUE_RESOURCES is exceeded. You can check resource usage by querying
V$RESOURCE_LIMIT.
Initialization Parameters 1-55
EVENT
See Also:
■
Oracle9i Real Application Clusters Administration
■
Oracle9i Database Concepts
■
Oracle9i Database Administrator’s Guide
EVENT
Parameter type
String
Default value
There is no default value.
Parameter class
Static
EVENT is a parameter used only to debug the system. Do not alter the value of this
parameter except under the supervision of Oracle Support Services staff.
FAL_CLIENT
Parameter type
String
Syntax
FAL_CLIENT = string
Default value
There is no default value.
Parameter class
Dynamic: ALTER SYSTEM
FAL_CLIENT specifies the FAL (fetch archive log) client name that is used by the
FAL service, configured through the FAL_SERVER parameter, to refer to the FAL
client. The value is an Oracle Net service name, which is assumed to be configured
properly on the FAL server system to point to the FAL client (standby database).
Given the dependency of FAL_CLIENT on FAL_SERVER, the two parameters
should be configured or changed at the same time.
See Also: Oracle9i Data Guard Concepts and Administration for
more information about FAL server
1-56
Oracle9i Database Reference
FAST_START_IO_TARGET
FAL_SERVER
Parameter type
String
Syntax
FAL_SERVER = string
Default value
There is no default value.
Parameter class
Dynamic: ALTER SYSTEM
FAL_SERVER specifies the FAL (fetch archive log) server for a standby database.
The value is an Oracle Net service name, which is assumed to be configured
properly on the standby database system to point to the desired FAL server.
See Also: Oracle9i Data Guard Concepts and Administration for
more information about FAL server
FAST_START_IO_TARGET
Parameter type
Integer
Default value
All the buffers in the cache
Parameter class
Dynamic: ALTER SYSTEM
Range of values
1000 to all buffers in the cache. A setting of 0 disables
limiting recovery I/Os.
Real Application
Clusters
Multiple instances can have different values, and you can
change the values at runtime.
Note: This parameter is deprecated in favor of the FAST_START_
MTTR_TARGET parameter. Oracle recommends that you use FAST_
START_MTTR_TARGET instead. FAST_START_IO_TARGETis
retained for backward compatibility only.
FAST_START_IO_TARGET (available only with the Oracle Enterprise Edition)
specifies the number of I/Os that should be needed during crash or instance
recovery.
When you set this parameter, DBWn writes dirty buffers out more aggressively, so
that the number of blocks that must be processed during recovery stays below the
value specified in the parameter. However, this parameter does not impose a hard
Initialization Parameters 1-57
FAST_START_MTTR_TARGET
limit on the number of recovery I/Os. Under transient workload situations, the
number of I/Os needed during recovery may be greater than the value specified in
this parameter. In such situations, DBWn will not slow down database activity.
Smaller values for this parameter result in faster recovery times. This improvement
in recovery performance is achieved at the expense of additional writing activity
during normal processing.
Setting this parameter to 0 disables fast-start checkpointing, which is the
mechanism that limits the number of I/Os that need to be performed during
recovery. All other writing activity is unaffected.
Recovery I/O can also be limited by setting the LOG_
CHECKPOINT_INTERVAL or LOG_CHECKPOINT_TIMEOUT
parameter or by the size specified for the smallest redo log. For
information on which mechanism is controlling checkpointing
behavior, query the V$INSTANCE_RECOVERY view.
Notes:
See Also:
■
■
Oracle9i Database Performance Tuning Guide and Reference for
more information on setting this parameter
V$INSTANCE_RECOVERY on page 3-70 for information on
fast-start checkpointing
FAST_START_MTTR_TARGET
Parameter type
Integer
Default value
0
Parameter class
Dynamic: ALTER SYSTEM
Range of values
0 to 3600 seconds
Real Application
Clusters
Multiple instances can have different values, and you can
change the values at runtime.
FAST_START_MTTR_TARGET enables you to specify the number of seconds the
database takes to perform crash recovery of a single instance. When specified,
FAST_START_MTTR_TARGET
1-58
Oracle9i Database Reference
FILE_MAPPING
■
Is overridden by FAST_START_IO_TARGET
■
Is overridden by LOG_CHECKPOINT_INTERVAL
FAST_START_PARALLEL_ROLLBACK
Parameter type
String
Syntax
FAST_START_PARALLEL_ROLLBACK = {HI | LO |
FALSE}
Default value
LOW
Parameter class
Dynamic: ALTER SYSTEM
FAST_START_PARALLEL_ROLLBACK determines the maximum number of
processes that can exist for performing parallel rollback. This parameter is useful on
systems in which some or all of the transactions are long running.
Values:
■
FALSE indicates that parallel rollback is disabled
■
LOW limits the number of rollback processes to 2 * CPU_COUNT
■
HIGH limits the number of rollback processes to 4 * CPU_COUNT
FILE_MAPPING
Parameter type
Boolean
Default value
false
Parameter class
Dynamic: ALTER SYSTEM
Range of values
true | false
FILE_MAPPING enables or disables file mapping. The FMON background process
will be started to manage the mapping information when file mapping is enabled.
Initialization Parameters 1-59
FILESYSTEMIO_OPTIONS
FILESYSTEMIO_OPTIONS
Parameter type
String
Syntax
FILESYSTEMIO_OPTIONS = {none | setall |
directIO | asynch}
Default value
There is no default value.
Parameter class
Dynamic: ALTER SESSION, ALTER SYSTEM
FILESYSTEMIO_OPTIONS specifies I/O operations for file system files.
FIXED_DATE
Parameter type
String
Syntax
FIXED_DATE = YYYY-MM-DD-HH24:MI:SS (or the default
Oracle date format)
Default value
There is no default value.
Parameter class
Dynamic: ALTER SYSTEM
FIXED_DATE enables you to set a constant date that SYSDATE will always return
instead of the current date. This parameter is useful primarily for testing. The value
can be in the format shown above or in the default Oracle date format, without a
time.
Specify the value either without quotation marks or with double quotation marks.
Note: Do not use single quotation marks.
GC_FILES_TO_LOCKS
Parameter type
1-60
Oracle9i Database Reference
String
GC_FILES_TO_LOCKS
Syntax
GC_FILES_TO_LOCKS =
’{file_list=lock_count[!blocks][EACH][:...]}’
Spaces are not allowed within the quotation marks.
Default value
There is no default value.
Parameter class
Static
Real Application
Clusters
You must set this parameter for every instance, and multiple
instances must have identical values. To change the value,
you must shut down all instances in the cluster, change the
value for each instance, and then start up each instance.
Note: Setting this parameter to any value other than the default
will disable Cache Fusion processing in Oracle9i Real Application
Clusters.
GC_FILES_TO_LOCKS is an Oracle9i Real Application Clusters parameter that has
no effect on an instance running in exclusive mode. It controls the mapping of
pre-release 9.0.1 parallel cache management (PCM) locks to datafiles.
Values:
■
file_list
One or more datafiles listed by their file numbers, or ranges of file numbers,
with comma separators:
filenumber[-filenumber][,filenumber[-filenumber]]...
To find the correspondence between filenames and file numbers, query the
FILE_NAME and FILE_ID columns of the DBA_DATA_FILES data dictionary
view.
■
lock_count
The number of PCM locks assigned to file_list. By default these locks are
fixed. If you set lock_count to 0, then Oracle uses fine-grain locking for these
files and takes locks as needed from the pool of releasable locks.
■
blocks
Specifies the number of contiguous blocks covered by one lock. The default is
noncontiguous blocks.
Initialization Parameters 1-61
GLOBAL_CONTEXT_POOL_SIZE
■
EACH
Indicates that each datafile in file_list is assigned a separate set of lock_
count PCM locks.
The value of the parameter should be set to cover as many files as possible.
Therefore, to avoid performance problems, you should always change GC_FILES_
TO_LOCKS when the size of datafiles change or when new datafiles are added.
Doing so requires you to shut down and restart your cluster database.
If the number of PCM locks allocated to a datafile is less than or equal to the
number of blocks in a datafile, each of these locks will cover a number of
contiguous blocks within the datafile equal to blocks. If the number of PCM locks
assigned to the datafile is larger than its number of blocks, resources will be wasted
because some locks will not be covering any blocks.
A colon (:) separates each clause that assigns a number of PCM locks to file_
list.
See Also: Oracle9i Real Application Clusters Concepts and Oracle9i
Real Application Clusters Deployment and Performance for more
information on setting this parameter
GLOBAL_CONTEXT_POOL_SIZE
Parameter type
String
Default value
1 MB
Parameter class
Static
Range of values
Any integer value in MB
GLOBAL_CONTEXT_POOL_SIZE specifies the amount of memory to allocate in the
SGA for storing and managing global application context.
GLOBAL_NAMES
1-62
Parameter type
Boolean
Default value
false
Oracle9i Database Reference
HASH_AREA_SIZE
Parameter class
Dynamic: ALTER SESSION, ALTER SYSTEM
Range of values
true | false
GLOBAL_NAMES specifies whether a database link is required to have the same
name as the database to which it connects.
If the value of GLOBAL_NAMES is false, then no check is performed. If you use or
plan to use distributed processing, then Oracle Corporation recommends that you
set this parameter to true to ensure the use of consistent naming conventions for
databases and links in a networked environment.
See Also: Oracle9i Database Administrator’s Guide for more
information on setting this parameter
HASH_AREA_SIZE
Parameter type
Integer
Default value
Derived: 2 * SORT_AREA_SIZE
Parameter class
Dynamic: ALTER SESSION
Range of values
0 to operating system-dependent
Note: Oracle does not recommend using the HASH_AREA_SIZE
parameter unless the instance is configured with the shared server
option. Oracle recommends that you enable automatic sizing of
SQL working areas by setting PGA_AGGREGATE_TARGET instead.
HASH_AREA_SIZE is retained for backward compatibility.
HASH_AREA_SIZE is relevant to parallel execution operations and to the query
portion of DML or DDL statements. It specifies the maximum amount of memory,
in bytes, to be used for hash joins.
See Also:
■
■
Oracle9i Database Concepts for information on hash joins in
general
Oracle9i Database Performance Tuning Guide and Reference for
information on calculating an appropriate value for this
parameter
Initialization Parameters 1-63
HASH_JOIN_ENABLED
HASH_JOIN_ENABLED
Parameter type
Boolean
Default value
true
Parameter class
Dynamic: ALTER SESSION
Range of values
true | false
HASH_JOIN_ENABLED specifies whether the optimizer should consider using a
hash join as a join method. If set to false, then hashing is not available as a join
method. If set to true, then the optimizer compares the cost of a hash join with
other types of joins, and chooses hashing if it gives the best cost. Oracle Corporation
recommends that you set this parameter to true for all data warehousing
applications.
HI_SHARED_MEMORY_ADDRESS
Parameter type
Integer
Default value
0
Parameter class
Static
HI_SHARED_MEMORY_ADDRESS specifies the starting address at runtime of the
system global area (SGA). It is ignored on platforms that specify the SGA’s starting
address at linktime.
On 64-bit platforms, use HI_SHARED_MEMORY_ADDRESS to specify the high-order
32 bits of a 64-bit address. Use SHARED_MEMORY_ADDRESS to specify the low-order
32 bits of the address (see "SHARED_MEMORY_ADDRESS" on page 1-149). If both
parameters are 0 or unspecified, the SGA address defaults to a platform-specific
location.
HS_AUTOREGISTER
Parameter type
1-64
Oracle9i Database Reference
Boolean
IFILE
Default value
true
Parameter class
Dynamic: ALTER SYSTEM
Range of values
true | false
HS_AUTOREGISTER enables or disables automatic self-registration of
Heterogeneous Services (HS) agents. When enabled, information is uploaded into
the server’s data dictionary to describe a previously unknown agent class or a new
agent version.
Oracle Corporation recommends that you set this parameter to true. Oracle incurs
less overhead when establishing subsequent connections through the same agent if
self-registered information is available in the server’s data dictionary.
See Also: Oracle9i Heterogeneous Connectivity Administrator’s Guide
for more information on HS agents
IFILE
Parameter type
Parameter file
Syntax
IFILE = parameter_file_name
Default value
There is no default value.
Parameter class
Static
Range of values
Valid parameter filenames
Real Application
Clusters
Multiple instances can have different values.
Use IFILE to embed another parameter file within the current parameter file. For
example:
IFILE = COMMON.ORA
You can have up to three levels of nesting. In this example, the file COMMON.ORA
could contain a second IFILE parameter for the file COMMON2.ORA, which could
contain a third IFILE parameter for the file GCPARMS.ORA. You can also include
multiple parameter files in one parameter file by listing IFILE several times with
different values:
IFILE = DBPARMS.ORA
IFILE = GCPARMS.ORA
Initialization Parameters 1-65
INSTANCE_GROUPS
IFILE = LOGPARMS.ORA
Note: You must list multiple entries on contiguous lines of the
parameter file.
INSTANCE_GROUPS
Parameter type
String
Syntax
INSTANCE_GROUPS = group_name [, group_name
... ]
Default value
There is no default value.
Parameter class
Static
Range of values
One or more instance group names, separated by commas
Real Application
Clusters
Multiple instances can have different values.
INSTANCE_GROUPS is an Oracle9i Real Application Clusters parameter that you
can specify only in parallel mode. Used in conjunction with the PARALLEL_
INSTANCE_GROUP parameter, it lets you restrict parallel query operations to a
limited number of instances.
This parameter specifies one or more instance groups and assigns the current
instance to those groups. If one of the specified groups is also specified in the
PARALLEL_INSTANCE_GROUP parameter, then Oracle allocates query processes for
a parallel operation from this instance.
See Also:
■
■
1-66
Oracle9i Real Application Clusters Administration for more
information on parallel query execution in an Oracle9i Real
Application Clusters environment
"PARALLEL_INSTANCE_GROUP" on page 1-122
Oracle9i Database Reference
INSTANCE_NUMBER
INSTANCE_NAME
Parameter type
String
Syntax
INSTANCE_NAME = instance_id
Default value
The instance’s SID
Note: The SID identifies the instance’s shared memory on a
host, but may not uniquely distinguish this instance from
other instances.
Parameter class
Static
Range of values
Any alphanumeric characters
In an Oracle9i Real Application Clusters environment, multiple instances can be
associated with a single database service. Clients can override Oracle’s connection
load balancing by specifying a particular instance by which to connect to the
database. INSTANCE_NAME specifies the unique name of this instance.
In a single-instance database system, the instance name is usually the same as the
database name.
See Also: Oracle9i Real Application Clusters Administration and
Oracle9i Net Services Administrator’s Guide for more information
INSTANCE_NUMBER
Parameter type
Integer
Default value
Lowest available number; derived from instance start up
order and INSTANCE_NUMBER value of other instances. If
not configured for Oracle9i Real Application Clusters, then
0.
Parameter class
Static
Range of values
1 to maximum number of instances specified when the
database was created
Real Application
Clusters
You must set this parameter for every instance, and all
instances must have different values.
Initialization Parameters 1-67
JAVA_MAX_SESSIONSPACE_SIZE
INSTANCE_NUMBER is an Oracle9i Real Application Clusters parameter that can be
specified in parallel mode or exclusive mode. It specifies a unique number that
maps the instance to one free list group for each database object created with
storage parameter FREELIST GROUPS.
The INSTANCE parameter of the ALTER TABLE ... ALLOCATE EXTENT
statement assigns an extent to a particular free list group. If you set INSTANCE_
NUMBER to the value specified for the INSTANCE parameter, the instance uses that
extent for inserts and for updates that expand rows.
The practical maximum value of this parameter is the maximum number of
instances specified in the CREATE DATABASE statement. The absolute maximum is
operating system-dependent.
See Also: Oracle9i Real Application Clusters Administration for more
information
JAVA_MAX_SESSIONSPACE_SIZE
Parameter type
Integer
Default value
0
Parameter class
Static
Range of values
0 to 4 GB
Java session space is the memory that holds Java state from one database call to
another. JAVA_MAX_SESSIONSPACE_SIZE specifies (in bytes) the maximum
amount of session space made available to a Java program executing in the server.
When a user’s session-duration Java state attempts to exceed this amount, the Java
virtual machine kills the session with an out-of-memory failure.
See Also:
■
Oracle9i Java Developer’s Guide
■
"JAVA_SOFT_SESSIONSPACE_LIMIT" on page 1-69
JAVA_POOL_SIZE
1-68
Parameter type
Big integer
Syntax
LARGE_POOL_SIZE = integer [K | M | G]
Oracle9i Database Reference
JOB_QUEUE_PROCESSES
Default value
24 MB, rounded up to the nearest granule size
Parameter class
Static
Range of values
Minimum: the granule size
Maximum: operating system-dependent
JAVA_POOL_SIZE specifies the size (in bytes) of the Java pool, from which the Java
memory manager allocates most Java state during runtime execution. This memory
includes the shared in-memory representation of Java method and class definitions,
as well as the Java objects that are migrated to the Java session space at end-of-call.
See Also: Oracle9i Java Developer’s Guide for information on
adjusting this parameter
JAVA_SOFT_SESSIONSPACE_LIMIT
Parameter type
Integer
Default value
0
Parameter class
Static
Range of values
0 to 4 GB
Java session space is the memory that holds Java state from one database call to
another. JAVA_SOFT_SESSIONSPACE_LIMIT specifies (in bytes) a soft limit on
Java memory usage in a session, as a means to warn you if a user’s session-duration
Java state is using too much memory. When a user’s session-duration Java state
exceeds this size, Oracle generates a warning that goes into the trace files.
See Also:
■
■
Oracle9i Java Developer’s Guide for more information on this
parameter
"JAVA_MAX_SESSIONSPACE_SIZE" on page 1-68
JOB_QUEUE_PROCESSES
Parameter type
Integer
Default value
0
Initialization Parameters 1-69
LARGE_POOL_SIZE
Parameter class
Dynamic: ALTER SYSTEM
Range of values
0 to 1000
Real Application
Clusters
Multiple instances can have different values.
JOB_QUEUE_PROCESSES specifies the maximum number of processes that can be
created for the execution of jobs. It specifies the number of job queue processes per
instance (J000, ... J999). Replication uses job queues for data refreshes. Advanced
queuing uses job queues for message propagation. You can create user job requests
through the DBMS_JOB package.
Some job queue requests are created automatically. An example is refresh support
for materialized views. If you wish to have your materialized views updated
automatically, you must set JOB_QUEUE_PROCESSES to a value of one or higher.
See Also:
■
■
Oracle9i Replication and Oracle9i Data Warehousing Guide for
more information on managing materialized views
Oracle9i Application Developer’s Guide - Advanced Queuing for
more information on message propagation
LARGE_POOL_SIZE
Parameter type
Big integer
Syntax
LARGE_POOL_SIZE = integer [K | M | G]
Default value
0 if both of the following are true:
■
The pool is not required by parallel execution
■
DBWR_IO_SLAVES is not set
Otherwise, derived from the values of PARALLEL_MAX_
SERVERS, PARALLEL_THREADS_PER_CPU, CLUSTER_
DATABASE_INSTANCES, DISPATCHERS, and DBWR_IO_
SLAVES.
1-70
Parameter class
Dynamic: ALTER SYSTEM
Range of values
300 KB to at least 2 GB (actual maximum is operating
system-specific)
Oracle9i Database Reference
LICENSE_MAX_SESSIONS
LARGE_POOL_SIZE lets you specify the size (in bytes) of the large pool allocation
heap. The large pool allocation heap is used in shared server systems for session
memory, by parallel execution for message buffers, and by backup processes for
disk I/O buffers. (Parallel execution allocates buffers out of the large pool only
when PARALLEL_AUTOMATIC_TUNING is set to true.)
Caution: When Oracle derives a default value, it adds 250K for
each session for the shared server if DISPATCHERS is configured.
The final derived value also includes a port-specific amount of
memory for backup I/O buffers. The total derived default value
can either be too large to allocate or can cause performance
problems. In that case, set LARGE_POOL_SIZE to a number
sufficiently small so that the database can start.
You can specify the value of this parameter using a number, optionally followed by
K or M to specify kilobytes or megabytes, respectively. If you do not specify K or M,
then the number is taken as bytes.
See Also: Oracle9i Database Performance Tuning Guide and Reference
and Oracle9i Database Migration for more information on setting this
parameter
LICENSE_MAX_SESSIONS
Parameter type
Integer
Default value
0
Parameter class
Dynamic: ALTER SYSTEM
Range of values
0 to number of session licenses
Real Application
Clusters
Multiple instances can have different values, but the total for
all instances mounting a database should be less than or
equal to the total number of sessions licensed for that
database.
LICENSE_MAX_SESSIONS specifies the maximum number of concurrent user
sessions allowed. When this limit is reached, only users with the RESTRICTED
SESSION privilege can connect to the database. Users who are not able to connect
Initialization Parameters 1-71
LICENSE_MAX_USERS
receive a warning message indicating that the system has reached maximum
capacity.
A zero value indicates that concurrent usage (session) licensing is not enforced. If
you set this parameter to a nonzero number, you might also want to set LICENSE_
SESSIONS_WARNING (see "LICENSE_SESSIONS_WARNING" on page 1-72).
Do not enable both concurrent usage licensing and user licensing. Set either
LICENSE_MAX_SESSIONS or LICENSE_MAX_USERS to zero.
See Also: Oracle9i Database Administrator’s Guide for more
information on setting this parameter
LICENSE_MAX_USERS
Parameter type
Integer
Default value
0
Parameter class
Dynamic: ALTER SYSTEM
Range of values
0 to number of user licenses
Real Application
Clusters
Multiple instances should have the same values. If different
instances specify different values for this parameter, then the
value of the first instance to mount the database takes
precedence.
LICENSE_MAX_USERS specifies the maximum number of users you can create in
the database. When you reach this limit, you cannot create more users. You can,
however, increase the limit.
Do not enable both concurrent usage (session) licensing and user licensing. Set
either LICENSE_MAX_SESSIONS or LICENSE_MAX_USERS to zero.
See Also: Oracle9i Database Administrator’s Guide for more
information on setting this parameter
LICENSE_SESSIONS_WARNING
1-72
Parameter type
Integer
Default value
0
Oracle9i Database Reference
LOCAL_LISTENER
Parameter class
Dynamic: ALTER SYSTEM
Range of values
0 to value of LICENSE_MAX_SESSIONS parameter
Real Application
Clusters
Multiple instances can have different values.
LICENSE_SESSIONS_WARNING specifies a warning limit on the number of
concurrent user sessions. When this limit is reached, additional users can connect,
but Oracle writes a message in the alert file for each new connection. Users with
RESTRICTED SESSION privilege who connect after the limit is reached receive a
warning message stating that the system is nearing its maximum capacity.
If this parameter is set to zero, no warning is given as you approach the concurrent
usage (session) limit. If you set this parameter to a nonzero number, you should also
set LICENSE_MAX_SESSIONS (see "LICENSE_MAX_SESSIONS" on page 1-71).
See Also:
■
■
Oracle9i Database Administrator’s Guide for more information on
setting this parameter
Oracle9i Real Application Clusters Administration for more
information on calculating an appropriate value for this
parameter
LOCAL_LISTENER
Parameter type
String
Syntax
LOCAL_LISTENER = network_name
Default value
(ADDRESS = (PROTOCOL=TCP)(HOST=)(PORT=1521))
Parameter class
Dynamic: ALTER SYSTEM
LOCAL_LISTENER specifies a network name that resolves to an address or address
list of Oracle Net local listeners (that is, listeners that are running on the same
machine as this instance). The address or address list is specified in the
TNSNAMES.ORA file or other address repository as configured for your system.
Initialization Parameters 1-73
LOCK_NAME_SPACE
See Also:
■
■
Oracle9i Database Concepts for more information about
instances, listener processes, and dispatcher processes
Oracle9i Net Services Administrator’s Guide and your operating
system-specific Oracle documentation for more information
about specifying network addresses for the protocols on your
system
LOCK_NAME_SPACE
Parameter type
String
Syntax
LOCK_NAME_SPACE = namespace
Default value
There is no default value.
Parameter class
Static
Range of values
Up to 8 alphanumeric characters. No special characters
allowed.
LOCK_NAME_SPACE specifies the namespace that the distributed lock manager
(DLM) uses to generate lock names. Consider setting this parameter if a standby or
clone database has the same database name on the same cluster as the primary
database.
If the standby database resides on the same file system as the primary database, set
LOCK_NAME_SPACE in the standby initialization parameter file to a distinct value
such as the following:
LOCK_NAME_SPACE = standby
LOCK_SGA
1-74
Parameter type
Boolean
Default value
false
Parameter class
Static
Range of values
true | false
Oracle9i Database Reference
LOG_ARCHIVE_DEST
LOCK_SGA locks the entire SGA into physical memory. It is usually advisable to lock
the SGA into real (physical) memory, especially if the use of virtual memory would
include storing some of the SGA using disk space. This parameter is ignored on
platforms that do not support it.
LOG_ARCHIVE_DEST
Parameter type
String
Syntax
LOG_ARCHIVE_DEST = filespec
Default value
Null
Parameter class
Dynamic: ALTER SYSTEM
Range of values
Any valid path or device name, except raw partitions
Real Application
Clusters
Multiple instances can have different values.
Note: For Enterprise Edition users, this parameter has been
deprecated in favor of the LOG_ARCHIVE_DEST_n parameters. If
Oracle Enterprise Edition is not installed or it is installed, but you
have not specified any LOG_ARCHIVE_DEST_n parameters, this
parameter is valid.
LOG_ARCHIVE_DEST is applicable only if you are running the database in
ARCHIVELOG mode or are recovering a database from archived redo logs. LOG_
ARCHIVE_DEST is incompatible with the LOG_ARCHIVE_DEST_n parameters, and
must be defined as the null string ("") or (’ ’) when any LOG_ARCHIVE_DEST_n
parameter has a value other than a null string. Use a text string to specify the
default location and root of the disk file or tape device when archiving redo log
files. (Archiving to tape is not supported on all operating systems.) The value
cannot be a raw partition.
If LOG_ARCHIVE_DEST is not explicitly defined and all the LOG_ARCHIVE_DEST_n
parameters have null string values, LOG_ARCHIVE_DEST is set to an operating
system-specific default value on instance startup.
Initialization Parameters 1-75
LOG_ARCHIVE_DEST_n
To override the destination that this parameter specifies, either specify a different
destination for manual archiving or use the SQL*Plus statement ARCHIVE LOG
START filespec for automatic archiving, where filespec is the new archive
destination. To permanently change the destination, use the statement ALTER
SYSTEM SET LOG_ARCHIVE_DEST = filespec, where filespec is the new
archive destination.
Neither LOG_ARCHIVE_DEST nor LOG_ARCHIVE_FORMAT have to be complete file
or directory specifiers themselves; they only need to form a valid file path after the
variables are substituted into LOG_ARCHIVE_FORMAT and the two parameters are
concatenated together.
See Also:
■
■
■
Oracle9i User-Managed Backup and Recovery Guide
"LOG_ARCHIVE_DUPLEX_DEST" on page 1-79, "LOG_
ARCHIVE_MIN_SUCCEED_DEST" on page 1-82, and
"V$ARCHIVE_DEST" on page 3-5 for more information on
setting this parameter
Your Oracle operating system-specific documentation for the
default value and for an example of how to specify the
destination path or filename using LOG_ARCHIVE_DEST
LOG_ARCHIVE_DEST_n
Parameter type
1-76
Oracle9i Database Reference
String
LOG_ARCHIVE_DEST_n
Syntax
LOG_ARCHIVE_DEST_[1 | 2 | 3 | 4 | 5 | 6 | 7 |
8 | 9 | 10] =
{ null_string} |
{ LOCATION=path_name | SERVICE=service_name }
[ { MANDATORY | OPTIONAL } ]
[ REOPEN[=seconds] | NOREOPEN ]
[ DELAY[=minutes] | NODELAY ]
[ REGISTER[=template] | NOREGISTER ]
[ TEMPLATE=template] | NOTEMPLATE ]
[ ALTERNATE=destination | NOALTERNATE ]
[ DEPENDENCY=destination | NODEPENDENCY ]
[ MAX_FAILURE=count | NOMAX_FAILURE ]
[ QUOTA_SIZE=blocks | NOQUOTA_SIZE ]
[ QUOTA_USED=blocks | NOQUOTA_USED ]
[ ARCH | LGWR ]
[ SYNC[=PARALLEL|NOPARALLEL] | ASYNC[=blocks] ]
[ AFFIRM | NOAFFIRM ]
[ NET_TIMEOUT=seconds | NONET_TIMEOUT ]
}
Default value
There is no default value.
Parameter class
Dynamic: ALTER SESSION, ALTER SYSTEM
Note: This parameter is valid only if you have installed Oracle
Enterprise Edition. You may continue to use LOG_ARCHIVE_DEST
if you have installed Oracle Enterprise Edition. However, you
cannot use both LOG_ARCHIVE_DEST_n and LOG_ARCHIVE_
DEST, as they are not compatible.
The LOG_ARCHIVE_DEST_n parameters (where n = 1, 2, 3, ... 10) define up to ten
archive log destinations. The parameter integer suffix is defined as the handle
displayed by the V$ARCHIVE_DEST dynamic performance view.
Values:
■
SERVICE
Specifies a standby destination. Oracle Net (IPC or TCP) transmits the
archivelog. A standby instance must be associated with the destination. The
value represented by tnsnames_service corresponds to an appropriate
service name in tnsnames.ora.
Initialization Parameters 1-77
LOG_ARCHIVE_DEST_STATE_n
■
LOCATION
Specifies a local file system destination. You must specify this parameter for at
least one destination.
■
MANDATORY
Specifies that archiving to the destination must succeed before the redo log file
can be made available for reuse.
■
OPTIONAL
Specifies that successful archiving to the destination is not required before the
redo log file can be made available for reuse. If the "must succeed count," set
with LOG_ARCHIVE_MIN_SUCCEED_DEST, is met, the redo logfile is marked
for reuse. This is the default.
■
REOPEN
Specifies the minimum number of seconds before the archiver process (ARCn,
foreground, or log writer process) should try again to access a previously failed
destination. Future attempts are made when the next redo log file is archived. If
a destination is MANDATORY, Oracle Corporation recommends that you specify a
REOPEN time that reduces the possibility of primary database shutdown due to
lack of available online redo log files.
If you do not specify seconds, the default value is 300 seconds.
See Also: Oracle9i User-Managed Backup and Recovery Guide and
Oracle9i Database Administrator’s Guide for more information and
examples
LOG_ARCHIVE_DEST_STATE_n
Parameter type
String
Syntax
LOG_ARCHIVE_DEST_STATE_n = {alternate | reset
| defer | enable}
Default value
enable
Parameter class
Dynamic: ALTER SESSION, ALTER SYSTEM
The LOG_ARCHIVE_DEST_STATE_n parameters (where n = 1, 2, 3, ... 10) specify
the availability state of the corresponding destination. The parameter suffix (1
1-78
Oracle9i Database Reference
LOG_ARCHIVE_DUPLEX_DEST
through 10) specifies one of the ten corresponding LOG_ARCHIVE_DEST_n
destination parameters.
Values:
■
enabled
Specifies that a valid log archive destination can be used for a subsequent
archiving operation (automatic or manual). This is the default.
■
defer
Specifies that valid destination information and attributes are preserved, but the
destination is excluded from archiving operations until re-enabled.
■
alternate
Specifies that a log archive destination is not enabled but will become enabled if
communications to another destination fail.
The LOG_ARCHIVE_DEST_STATE_n parameters have no effect on the ENABLE state
for the LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST parameters.
The V$ARCHIVE_DEST dynamic performance view shows values in use for the
current session. The DEST_ID column of that view corresponds to the archive
destination suffix n.
See Also:
■
■
Oracle9i User-Managed Backup and Recovery Guide and Oracle9i
Database Administrator’s Guide for more information and
examples
"V$ARCHIVE_DEST" on page 3-5
LOG_ARCHIVE_DUPLEX_DEST
Parameter type
String
Syntax
LOG_ARCHIVE_DUPLEX_DEST = filespec
Default value
There is no default value.
Parameter class
Dynamic: ALTER SYSTEM
Range of values
Either a null string or any valid path or device name, except
raw partitions
Initialization Parameters 1-79
LOG_ARCHIVE_FORMAT
Note: If you are using Oracle Enterprise Edition, this parameter is
deprecated in favor of the LOG_ARCHIVE_DEST_n parameters. If
Oracle Enterprise Edition is not installed or it is installed but you
have not specified any LOG_ARCHIVE_DEST_n parameters, this
parameter is valid.
LOG_ARCHIVE_DUPLEX_DEST is similar to the initialization parameter LOG_
ARCHIVE_DEST. This parameter specifies a second archive destination: the duplex
archive destination. This duplex archive destination can be either a must-succeed or
a best-effort archive destination, depending on how many archive destinations
must succeed (as specified in the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter).
The default setting of a null string ("") or (’ ’) indicates that a duplex archive
destination does not exist.
See Also:
■
"LOG_ARCHIVE_DEST_n" on page 1-76
■
"LOG_ARCHIVE_MIN_SUCCEED_DEST" on page 1-82
■
"V$ARCHIVE_DEST" on page 3-5
LOG_ARCHIVE_FORMAT
Parameter type
String
Syntax
LOG_ARCHIVE_FORMAT = filename
Default value
Operating system-dependent
Parameter class
Static
Range of values
Any string that resolves to a valid filename
Real Application
Clusters
Multiple instances can have different values, but identical
values are recommended.
LOG_ARCHIVE_FORMAT is applicable only if you are using the redo log in
ARCHIVELOG mode. Use a text string and variables to specify the default filename
format when archiving redo log files. The string generated from this format is
appended to the string specified in the LOG_ARCHIVE_DEST parameter.
The following variables can be used in the format:
1-80
Oracle9i Database Reference
LOG_ARCHIVE_MAX_PROCESSES
%s log sequence number
%S log sequence number, zero filled
%t thread number
%T thread number, zero filled
Using uppercase letters for the variables (for example, %S) causes the value to be
fixed length and padded to the left with zeros. An example of specifying the archive
redo log filename format follows:
LOG_ARCHIVE_FORMAT = "LOG%s_%t.ARC"
Neither LOG_ARCHIVE_DEST nor LOG_ARCHIVE_FORMAT have to be complete file
or directory specifiers themselves; they only need to form a valid file path after the
variables are substituted into LOG_ARCHIVE_FORMAT and the two parameters are
concatenated together.
See Also:
■
■
Oracle9i User-Managed Backup and Recovery Guide and Oracle9i
Real Application Clusters Administration for more information on
setting this parameter
Your operating system- specific Oracle documentation for the
default value and range of values for LOG_ARCHIVE_FORMAT
LOG_ARCHIVE_MAX_PROCESSES
Parameter type
Integer
Default value
1
Parameter class
Dynamic: ALTER SYSTEM
Range of values
Any integer from 1 to 10
LOG_ARCHIVE_MAX_PROCESSES specifies the number of archiver background
processes (ARC0 through ARC9) Oracle initially invokes.
■
■
If the LOG_ARCHIVE_START initialization parameter has the value true, then
this value is evaluated at instance startup.
Otherwise, this parameter is evaluated when the archiver process is first
invoked by SQL*Plus or SQL syntax.
Initialization Parameters 1-81
LOG_ARCHIVE_MIN_SUCCEED_DEST
The actual number of archiver processes in use may vary subsequently based on
archive workload.
See Also: Oracle9i Database Concepts
LOG_ARCHIVE_MIN_SUCCEED_DEST
Parameter type
Integer
Default value
1
Parameter class
Dynamic: ALTER SESSION, ALTER SYSTEM
Range of values
1 to 10 if you are using LOG_ARCHIVE_DEST_n
1 or 2 if you are using LOG_ARCHIVE_DEST and LOG_
ARCHIVE_DUPLEX_DEST
LOG_ARCHIVE_MIN_SUCCEED_DEST defines the minimum number of destinations
that must succeed in order for the online logfile to be available for reuse.
■
If you are using the LOG_ARCHIVE_DEST_n parameters and automatic
archiving is enabled, the value of this parameter cannot exceed either of the
following:
- The total number of destinations
- The number of enabled, valid destinations specified as MANDATORY plus the
number of enabled, valid non-standby destinations specified as OPTIONAL
■
If you are using LOG_ARCHIVE_DEST and LOG_ARCHIVE_DUPLEX_DEST and
automatic archiving is enabled, a value of 1 specifies that the destination
specified in LOG_ARCHIVE_DEST must succeed. A value of 2 specifies that the
destinations specified in both parameters must succeed.
If the value of this parameter is less than the number of enabled, valid MANDATORY
destinations, this parameter is ignored in favor of the MANDATORY destination
count. If the value is more than the number of enabled, valid MANDATORY
destinations, some of the enabled, valid OPTIONAL non-standby destinations are
treated as MANDATORY.
You cannot set a value for this parameter dynamically if LOG_ARCHIVE_DEST or
LOG_ARCHIVE_DUPLEX_DEST are in use. However, you can switch dynamically
from one system to the other using ALTER SYSTEM, as follows:
1.
1-82
Set LOG_ARCHIVE_MIN_SUCCEED_DEST to 1.
Oracle9i Database Reference
LOG_ARCHIVE_START
2.
Set the value of LOG_ARCHIVE_DEST and LOG_ARCHIVE_DUPLEX_DEST to the
null string.
3.
Set the desired number of destinations for the LOG_ARCHIVE_DEST_n
parameters.
4.
Reset LOG_ARCHIVE_MIN_SUCCEED_DEST to the desired value.
See Also:
■
■
Oracle9i Database Administrator’s Guide for more information on
setting this parameter
"LOG_ARCHIVE_DEST_n" on page 1-76, "LOG_ARCHIVE_
DUPLEX_DEST" on page 1-79, and "V$ARCHIVE_DEST" on
page 3-5 for information on related parameters
LOG_ARCHIVE_START
Parameter type
Boolean
Default value
false
Parameter class
Static
Range of values
true | false
Real Application
Clusters
Multiple instances can have different values.
LOG_ARCHIVE_START is applicable only when you use the redo log in
ARCHIVELOG mode. It indicates whether archiving should be automatic or manual
when the instance starts up.
Values:
■
true
Indicates that archiving is automatic
■
false
Indicates that the database administrator will archive filled redo log files
manually
The SQL*Plus statements ARCHIVE LOG START or ARCHIVE LOG STOP override
this parameter.
Initialization Parameters 1-83
LOG_ARCHIVE_TRACE
In ARCHIVELOG mode, if all online redo log files fill without being archived, Oracle
issues an error and suspends instance operations until the necessary archiving is
performed. This delay is more likely if you use manual archiving. You can reduce its
likelihood by increasing the number of online redo log files.
To use ARCHIVELOG mode while creating a database, set this parameter to true.
Normally, a database is created in NOARCHIVELOG mode and then altered to
ARCHIVELOG mode after creation.
See Also: Oracle9i Database Administrator’s Guide and Oracle9i Real
Application Clusters Administration
LOG_ARCHIVE_TRACE
Parameter type
Integer
Default value
0
Parameter class
Dynamic: ALTER SYSTEM
Range of values
0, 1, 2, 4, 8, 16, 32, 64, 128
Real Application
Clusters
Multiple instances can have different values.
LOG_ARCHIVE_TRACE controls output generated by the archivelog process.
This process can be initiated by any of the following:
■
■
An ARCn background process (designated as ARCn in the output logs)
An explicit session-invoked foreground process (designated as ARCH in the
output logs)
The valid values have the following meanings:
1-84
■
0: Disable archivelog tracing (this is the default)
■
1: Track archival of redo log file
■
2: Track archival status of each archivelog destination
■
4: Track archival operational phase
■
8: Track archivelog destination activity
■
16: Track detailed archivelog destination activity
Oracle9i Database Reference
LOG_BUFFER
■
32: Track archivelog destination parameter modifications
■
64: Track ARCn process state activity
■
128: Track FAL (fetch archived log) server related activities
You can combine tracing levels by adding together the values of the desired tracing
levels. For example, a setting of 3 will generate level 1 and level 2 trace output. You
can set different values for the primary and standby database.
When this parameter is set to the default value of 0, Oracle will still generate
appropriate alert and trace entries in response to error conditions. If you change the
value of this parameter dynamically in an ALTER SYSTEM statement, the changes
will take effect at the start of the next archivelog operation.
See Also: Oracle9i User-Managed Backup and Recovery Guide
LOG_BUFFER
Parameter type
Integer
Default value
512 KB or 128 KB * CPU_COUNT, whichever is greater
Parameter class
Static
Range of values
Operating system-dependent
LOG_BUFFER specifies the amount of memory (in bytes) that Oracle uses when
buffering redo entries to a redo log file. Redo log entries contain a record of the
changes that have been made to the database block buffers. The LGWR process
writes redo log entries from the log buffer to a redo log file.
In general, larger values for LOG_BUFFER reduce redo log file I/O, particularly if
transactions are long or numerous. In a busy system, a value 65536 or higher is
reasonable.
See Also:
■
■
Oracle9i Database Performance Tuning Guide and Reference for
more information on setting this parameter
Your operating system-specific Oracle documentation for the
default value and range of values
Initialization Parameters 1-85
LOG_CHECKPOINT_INTERVAL
LOG_CHECKPOINT_INTERVAL
Parameter type
Integer
Default value
0
Parameter class
Dynamic: ALTER SYSTEM
Range of values
Unlimited
Real Application
Clusters
Multiple instances can have different values.
LOG_CHECKPOINT_INTERVAL specifies the frequency of checkpoints in terms of
the number of redo log file blocks that can exist between an incremental checkpoint
and the last block written to the redo log. This number refers to physical operating
system blocks, not database blocks.
Regardless of this value, a checkpoint always occurs when switching from one
online redo log file to another. Therefore, if the value exceeds the actual redo log file
size, checkpoints occur only when switching logs. Checkpoint frequency is one of
the factors that influence the time required for the database to recover from an
unexpected failure.
Notes:
■
■
1-86
Specifying a value of 0 (zero) for LOG_CHECKPOINT_
INTERVAL has the same effect as setting the parameter to
infinity and causes the parameter to be ignored. Only nonzero
values of this parameter are considered meaningful.
Recovery I/O can also be limited by setting the FAST_START_
IO_TARGET or LOG_CHECKPOINT_TIMEOUT parameter or by
the size specified for the smallest redo log. For information on
which mechanism is controlling checkpointing behavior, query
the V$INSTANCE_RECOVERY view.
Oracle9i Database Reference
LOG_CHECKPOINT_TIMEOUT
See Also:
■
■
Oracle9i Database Performance Tuning Guide and Reference for
more information on setting this parameter
"FAST_START_IO_TARGET" on page 1-57, "LOG_
CHECKPOINT_TIMEOUT" on page 1-87, and "V$INSTANCE_
RECOVERY" on page 3-70
LOG_CHECKPOINT_TIMEOUT
Parameter type
Integer
Default value
1800
Parameter class
Dynamic: ALTER SYSTEM
Range of values
0 to unlimited
Real Application
Clusters
Multiple instances can have different values.
LOG_CHECKPOINT_TIMEOUT specifies (in seconds) the amount of time that has
passed since the incremental checkpoint at the position where the last write to the
redo log (sometimes called the tail of the log) occurred. This parameter also
signifies that no buffer will remain dirty (in the cache) for more than integer seconds.
Specifying a value of 0 for the timeout disables time-based checkpoints. Hence,
setting the value to 0 is not recommended.
Notes:
■
■
A checkpoint scheduled to occur because of this parameter is
delayed until the completion of the previous checkpoint if the
previous checkpoint has not yet completed.
Recovery I/O can also be limited by setting the FAST_START_
IO_TARGET or LOG_CHECKPOINT_INTERVAL parameter or by
the size specified for the smallest redo log. For information on
which mechanism is controlling checkpointing behavior, query
the V$INSTANCE_RECOVERY view.
Initialization Parameters 1-87
LOG_CHECKPOINTS_TO_ALERT
See Also:
■
■
Oracle9i Database Performance Tuning Guide and Reference for
more information on setting this parameter
"FAST_START_IO_TARGET" on page 1-57, "LOG_
CHECKPOINT_TIMEOUT" on page 1-87, and "V$INSTANCE_
RECOVERY" on page 3-70
LOG_CHECKPOINTS_TO_ALERT
Parameter type
Boolean
Default value
false
Parameter class
Dynamic: ALTER SYSTEM
Range of values
true | false
LOG_CHECKPOINTS_TO_ALERT lets you log your checkpoints to the alert file.
Doing so is useful for determining whether checkpoints are occurring at the desired
frequency.
LOG_FILE_NAME_CONVERT
Parameter type
1-88
Oracle9i Database Reference
String
LOG_FILE_NAME_CONVERT
Syntax
LOG_FILE_NAME_CONVERT = [(]’string1’ ,
’string2’ , ’string3’ , ’string4’ , ...[)]
Where:
■
string1 is the pattern of the primary database filename
■
string2 is the pattern of the standby database filename
■
string3 is the pattern of the primary database filename
■
string4 is the pattern of the standby database filename
You can use as many pairs of primary and standby
replacement strings as required. You can use single or
double quotation marks. The parentheses are optional.
Following are example settings that are acceptable:
LOG_FILE_NAME_CONVERT=(’/dbs/t1/’,’/dbs/t1/s_
’,’dbs/t2/ ’,’dbs/t2/s_’)
Default value
None
Parameter class
Static
Range of values
Character strings
LOG_FILE_NAME_CONVERT converts the filename of a new log file on the primary
database to the filename of a log file on the standby database. If you add a log file to
the primary database, you must add a corresponding file to the standby database.
If you specify an odd number of strings (the last string has no corresponding
replacement string), an error is signalled during startup. If the filename being
converted matches more than one pattern in the pattern/replace string list, the first
matched pattern takes effect. There is no limit on the number of pairs that you can
specify in this parameter (other than the hard limit of the maximum length of
multivalue parameters).
When the standby database is updated, this parameter converts the log file name on
the primary database to the log file name on the standby database. The file must
exist on the standby database and must be writable or the recovery process will halt
with an error.
The first string is the pattern found in the log file names on the primary database.
The second string is the pattern found in the log file names on the standby database.
Initialization Parameters 1-89
LOG_PARALLELISM
You should also use LOG_FILE_NAME_CONVERT to rename the logfiles in the clone
controlfile when setting up the clone database during tablespace point-in-time
recovery.
See Also: Oracle9i User-Managed Backup and Recovery Guide and Oracle9i
Data Guard Concepts and Administration
LOG_PARALLELISM
Parameter type
Integer
Default value
1
Parameter class
Static
Range of values
1 to 255
LOG_PARALLELISM specifies the level of concurrency for redo allocation within
Oracle.
If you are using Oracle on high-end servers that have more than 16 processors, and
you are experiencing very high contention on the redo allocation latch, then you
should consider enabling parallel redo. This allows the parallel generation of redo
and can increase the throughput of certain update-intensive workloads. You can
examine the V$LATCH view to observe the cumulative wait times on the redo
allocation latch.
To enable parallel redo, set the LOG_PARALLELISM parameter in the initialization
parameter file to the desired level of concurrency for redo allocation. Oracle
Corporation recommends setting LOG_PARALLELISM to a value between 2 and 8
when running on systems with 16 to 64 processors. You can start with a low value
(such as 2) and increment it by 1 until you determine that the redo allocation latch
is no longer contended, and that the parameter improves the performance of the
application.
Setting LOG_PARALLELISM to values greater than 8 is not currently recommended.
LOGMNR_MAX_PERSISTENT_SESSIONS
1-90
Parameter type
Integer
Default value
1
Oracle9i Database Reference
MAX_COMMIT_PROPAGATION_DELAY
Parameter class
Static
Range of values
1 to LICENSE_MAX_SESSIONS
LOGMNR_MAX_PERSISTENT_SESSIONS enables you to specify the maximum
number of persistent LogMiner mining sessions (which are LogMiner sessions that
are backed up on disk) that are concurrently active when all sessions are mining
redo logs generated by standalone instances. This pre-allocates 2*LOGMNR_MAX_
PERSISTENT_SESSIONS MB of contiguous memory in the SGA for use by
LogMiner.
LogMiner requires 2 MB of contiguous memory for mining the redo log stream
generated by a non-cluster database instance. To mine redo logs generated by an
n-instance cluster database system, 2 MB of contiguous memory is required for each
redo thread (or, a total of 2*n). Because persistent LogMiner sessions stage all data
in the SGA, read buffers must be allocated in the SGA. The required contiguous
memory is allocated at instance startup.
LOGMNR_MAX_PERSISTENT_SESSIONS is normalized for redo logs generated by
non-cluster database instances. If you wish to mine a redo log stream generated by
a 3-node cluster database instance, you should set this parameter to 3 (because one
persistent session mining redo log generated in a 3-node cluster database instance is
equivalent to 3 persistent sessions, each with mining redo logs generated by a
non-cluster database instance). The memory remains exclusively allocated for
LogMiner persistent sessions. This parameter does not affect transient LogMiner
sessions that are not backed up on disk and are staged entirely in the Process Global
Area (PGA).
See Also: Oracle9i Supplied PL/SQL Packages and Types Reference for
information on the DBMS_LOGMNR_SESSION package
MAX_COMMIT_PROPAGATION_DELAY
Parameter type
Integer
Default value
700
Parameter class
Static
Range of values
0 to 90000
Real Application
Clusters
You must set this parameter for every instance, and multiple
instances must have identical values.
Initialization Parameters 1-91
MAX_DISPATCHERS
Caution: Change this parameter only when it is absolutely
necessary to see the most current version of the database when
performing a query.
MAX_COMMIT_PROPAGATION_DELAY is an Oracle9i Real Application Clusters
parameter. This initialization parameter should not be changed except under a
limited set of circumstances specific to the cluster database.
This parameter specifies the maximum amount of time allowed before the system
change number (SCN) held in the SGA of an instance is refreshed by the log writer
process (LGWR). It determines whether the local SCN should be refreshed from the
lock value when getting the snapshot SCN for a query. Units are in hundredths of
seconds.
Under very unusual circumstances involving rapid updates and queries of the same
data from different instances, the SCN might not be refreshed in a timely manner.
Setting the parameter to zero causes the SCN to be refreshed immediately after a
commit. The default value (700 hundredths of a second, or seven seconds) is an
upper bound that allows the preferred existing high performance mechanism to
remain in place.
See Also: Oracle9i Real Application Clusters Administration for more
information on setting this parameter
MAX_DISPATCHERS
Parameter type
Integer
Default value
5
Parameter class
Static
Range of values
5 or the number of dispatchers configured, whichever is
greater
MAX_DISPATCHERS specifies the maximum number of dispatcher processes
allowed to be running simultaneously. The default value applies only if dispatchers
have been configured for the system.
The value of MAX_DISPATCHERS should at least equal the maximum number of
concurrent sessions divided by the number of connections for each dispatcher. For
1-92
Oracle9i Database Reference
MAX_DUMP_FILE_SIZE
most systems, a value of 250 connections for each dispatcher provides good
performance.
See Also:
■
■
Oracle9i Database Performance Tuning Guide and Reference for
more information on setting this parameter
Your operating system-specific Oracle documentation for the
default value and range of values
MAX_DUMP_FILE_SIZE
Parameter type
String
Syntax
MAX_DUMP_FILE_SIZE = {integer [K | M] |
UNLIMITED}
Default value
UNLIMITED
Parameter class
Dynamic: ALTER SESSION, ALTER SYSTEM
Range of values
0 to unlimited, or UNLIMITED
MAX_DUMP_FILE_SIZE specifies the maximum size of trace files (excluding the
alert file). Change this limit if you are concerned that trace files may use too much
space.
■
■
■
A numerical value for MAX_DUMP_FILE_SIZE specifies the maximum size in
operating system blocks.
A number followed by a K or M suffix specifies the file size in kilobytes or
megabytes.
The special value string UNLIMITED means that there is no upper limit on trace
file size. Thus, dump files can be as large as the operating system permits.
See Also: Oracle9i Database Administrator’s Guide and Oracle9i
Database Performance Tuning Guide and Reference for more
information on setting this parameter
Initialization Parameters 1-93
MAX_ENABLED_ROLES
MAX_ENABLED_ROLES
Parameter type
Integer
Default value
20
Parameter class
Static
Range of values
0 to 148
MAX_ENABLED_ROLES specifies the maximum number of database roles that users
can enable, including roles contained within other roles.
The actual number of roles users can enable is 2 plus the value of MAX_ENABLED_
ROLES, because each user has two additional roles, PUBLIC and the user’s own
role. For example, if MAX_ENABLED_ROLES is set to 5, user HR can have seven roles
enabled: the five enabled by MAX_ENABLED_ROLES, plus PUBLIC and HR.
See Also: Oracle9i Database Administrator’s Guide for more
information on setting this parameter
MAX_ROLLBACK_SEGMENTS
Parameter type
Integer
Default value
MAX(30, TRANSACTIONS/TRANSACTIONS_PER_
ROLLBACK_SEGMENT)
Parameter class
Static
Range of values
2 to 65535
MAX_ROLLBACK_SEGMENTS specifies the maximum size of the rollback segment
cache in the SGA. The number specified signifies the maximum number of rollback
segments that can be kept online (that is, status of ONLINE) simultaneously by one
instance.
See Also: Oracle9i Database Administrator’s Guide for more
information on setting this parameter
MAX_SHARED_SERVERS
Parameter type
1-94
Oracle9i Database Reference
Integer
NLS_CALENDAR
Default value
Derived from SHARED_SERVERS (either 20 or 2*SHARED_
SERVERS)
Parameter class
Static
Range of values
Operating system-dependent
MAX_SHARED_SERVERS specifies the maximum number of shared server processes
allowed to be running simultaneously. If artificial deadlocks occur too frequently on
your system, you should increase the value of MAX_SHARED_SERVERS.
See Also:
■
■
■
Oracle9i Database Performance Tuning Guide and Reference for
more information on setting this parameter
Oracle9i Database Concepts for information on artificial
deadlocks
Your operating system-specific Oracle documentation for the
default value and range of values
NLS_CALENDAR
Parameter type
String
Syntax
NLS_CALENDAR = "calendar_system"
Default value
None
Parameter class
Dynamic: ALTER SESSION
Range of values
Any valid calendar format name
NLS_CALENDAR specifies which calendar system Oracle uses. It can have one of the
following values:
■
Arabic Hijrah
■
English Hijrah
■
Gregorian
■
Japanese Imperial
■
Persian
■
ROC Official (Republic of China)
Initialization Parameters 1-95
NLS_COMP
■
Thai Buddha
For example, suppose NLS_CALENDAR is set to "Japanese Imperial", the date format
is "E YY-MM-DD". ("E" is the date format element for the abbreviated era name.) If
the date is May 15, 1997, then the SYSDATE is displayed as follows:
SELECT SYSDATE FROM DUAL;
SYSDATE
-------H 09-05-15
See Also: Oracle9i Database Globalization Support Guide for a listing
of available calendar systems
NLS_COMP
Parameter type
String
Syntax
NLS_COMP = {BINARY | ANSI}
Default value
BINARY
Parameter class
Dynamic: ALTER SESSION
Normally, comparisons in the WHERE clause and in PL/SQL blocks is binary unless
you specify the NLSSORT function. By setting NLS_COMP to ANSI, you indicate that
comparisons in the WHERE clause and in PL/SQL blocks should use the linguistic
sort specified in the NLS_SORT parameter. You must also define an index on the
column for which you want linguistic sorts.
See Also: Oracle9i Database Globalization Support Guide for more
information on setting this parameter
NLS_CURRENCY
1-96
Parameter type
String
Syntax
NLS_CURRENCY = currency_symbol
Default value
Derived from NLS_TERRITORY
Parameter class
Dynamic: ALTER SESSION
Range of values
Any valid character string, with a maximum of 10 bytes (not
including null)
Oracle9i Database Reference
NLS_DATE_FORMAT
NLS_CURRENCY specifies the string to use as the local currency symbol for the L
number format element. The default value of this parameter is determined by NLS_
TERRITORY.
See Also:
■
■
Oracle9i Database Globalization Support Guide for more
information on setting this parameter
Oracle9i SQL Reference for information on number format
elements
NLS_DATE_FORMAT
Parameter type
String
Syntax
NLS_DATE_FORMAT = "format"
Default value
Derived from NLS_TERRITORY
Parameter class
Dynamic: ALTER SESSION
Range of values
Any valid date format mask but not exceeding a fixed length
NLS_DATE_FORMAT specifies the default date format to use with the TO_CHAR and
TO_DATE functions. The default value of this parameter is determined by NLS_
TERRITORY.
The value of this parameter can be any valid date format mask, and the value must
be surrounded by double quotation marks. For example:
NLS_DATE_FORMAT = "MM/DD/YYYY"
See Also:
■
■
Oracle9i Database Globalization Support Guide for more
information on setting this parameter
Oracle9i Heterogeneous Connectivity Administrator’s Guide for
information on setting this parameter in heterogeneous systems
Initialization Parameters 1-97
NLS_DATE_LANGUAGE
NLS_DATE_LANGUAGE
Parameter type
String
Syntax
NLS_DATE_LANGUAGE = language
Default value
Derived from NLS_LANGUAGE
Parameter class
Dynamic: ALTER SESSION
Range of values
Any valid NLS_LANGUAGE value
NLS_DATE_LANGUAGE specifies the language to use for the spelling of day and
month names and date abbreviations (a.m., p.m., AD, BC) returned by the TO_DATE
and TO_CHAR functions.
See Also:
■
■
■
Oracle9i Database Globalization Support Guide for more
information on setting this parameter
Oracle9i SQL Reference for information on the TO_DATE and TO_
CHAR functions.
Oracle9i Heterogeneous Connectivity Administrator’s Guide for
information on setting this parameter in heterogeneous systems
NLS_DUAL_CURRENCY
Parameter type
String
Syntax
NLS_DUAL_CURRENCY = currency_symbol
Default value
Derived from NLS_TERRITORY
Parameter class
Dynamic: ALTER SESSION
Range of values
Any valid format name up to 10 characters
NLS_DUAL_CURRENCY specifies the dual currency symbol (such as "Euro") for the
territory. The default is the dual currency symbol defined in the territory of your
current language environment.
See Also: Oracle9i Database Globalization Support Guide for more
information on setting this parameter
1-98
Oracle9i Database Reference
NLS_LANGUAGE
NLS_ISO_CURRENCY
Parameter type
String
Syntax
NLS_ISO_CURRENCY = territory
Default value
Derived from NLS_TERRITORY
Parameter class
Dynamic : ALTER SESSION
Range of values
Any valid NLS_TERRITORY value
NLS_ISO_CURRENCY specifies the string to use as the international currency
symbol for the C number format element.
Local currency symbols can be ambiguous. For example, a dollar sign ($) can refer
to U.S. dollars or Australian dollars. ISO Specification 4217 1987-07-15 defines
unique "international" currency symbols for the currencies of specific territories or
countries.
See Also:
■
■
Oracle9i Database Globalization Support Guide for more
information on setting this parameter
Oracle9i SQL Reference for information on number format
elements
NLS_LANGUAGE
Parameter type
String
Syntax
NLS_LANGUAGE = language
Default value
Operating system-dependent, derived from the NLS_LANG
environment variable
Parameter class
Dynamic: ALTER SESSION
Range of values
Any valid language name
NLS_LANGUAGE specifies the default language of the database. This language is
used for messages, day and month names, symbols for AD, BC, a.m., and p.m., and
the default sorting mechanism. This parameter also determines the default values of
the parameters NLS_DATE_LANGUAGE and NLS_SORT.
Initialization Parameters 1-99
NLS_LENGTH_SEMANTICS
See Also:
■
■
Oracle9i Database Globalization Support Guide for a complete list
of languages and additional information on this parameter
Your operating system-specific Oracle documentation and the
release notes for your country
NLS_LENGTH_SEMANTICS
Parameter type
String
Syntax
NLS_LENGTH_SEMANTICS = string
Example: NLS_LENGTH_SEMANTICS = ’CHAR’
Default value
BYTE
Parameter class
Dynamic: ALTER SESSION, ALTER SYSTEM
Range of values
BYTE | CHAR
NLS_LENGTH_SEMANTICS enables you to create CHAR and VARCHAR2 columns
using either byte or character length semantics. Existing columns are not affected.
NCHAR, NVARCHAR2, CLOB, and NCLOB columns are always character-based. You
may be required to use byte semantics in order to maintain compatibility with
existing applications.
NLS_LENGTH_SEMANTICS does not apply to tables in SYS and SYSTEM. The data
dictionary always uses byte semantics.
NLS_NCHAR_CONV_EXCP
Parameter type
String
Syntax
NLS_NCHAR_CONV_EXCP = {TRUE | FALSE}
Default value
FALSE
Parameter class
Dynamic: ALTER SESSION, ALTER SYSTEM
NLS_NCHAR_CONV_EXCP determines whether data loss during an implicit or
explicit character type conversion will report an error.
1-100 Oracle9i Database Reference
NLS_SORT
See Also: Oracle9i Database Globalization Support Guide for more
information on setting this parameter
NLS_NUMERIC_CHARACTERS
Parameter type
String
Syntax
NLS_NUMERIC_CHARACTERS =
"decimal_character group_separator"
Default value
Derived from NLS_TERRITORY
Parameter class
Dynamic: ALTER SESSION
NLS_NUMERIC_CHARACTERS specifies the characters to use as the group separator
and decimal character. It overrides those characters defined implicitly by NLS_
TERRITORY. The group separator separates integer groups (that is, thousands,
millions, billions, and so on). The decimal separates the integer portion of a number
from the decimal portion.
You can specify any character as the decimal or group separator. The two characters
specified must be single-byte and must be different from each other. The characters
cannot be any numeric character or any of the following characters: plus (+), minus
sign (-), less than sign (<), greater than sign (>). Either character can be a space.
For example, if you wish to specify a comma as the decimal character and a space as
the group separator, you would set this parameter as follows:
NLS_NUMERIC_CHARACTERS = ", "
See Also: Oracle9i Database Globalization Support Guide for more
information on setting this parameter
NLS_SORT
Parameter type
String
Syntax
NLS_SORT = {BINARY | linguistic_definition}
Initialization Parameters 1-101
NLS_TERRITORY
Default value
Derived from NLS_LANGUAGE
Parameter class
Dynamic: ALTER SESSION
Range of values
BINARY or any valid linguistic definition name
NLS_SORT specifies the collating sequence for ORDER BY queries.
■
■
If the value is BINARY, then the collating sequence for ORDER BY queries is
based on the numeric value of characters (a binary sort that requires less system
overhead).
If the value is a named linguistic sort, sorting is based on the order of the
defined linguistic sort. Most (but not all) languages supported by the NLS_
LANGUAGE parameter also support a linguistic sort with the same name.
Note: Setting NLS_SORT to anything other than BINARY causes a
sort to use a full table scan, regardless of the path chosen by the
optimizer. BINARY is the exception because indexes are built
according to a binary order of keys. Thus the optimizer can use an
index to satisfy the ORDER BY clause when NLS_SORT is set to
BINARY. If NLS_SORT is set to any linguistic sort, the optimizer
must include a full table scan and a full sort in the execution plan.
You must use the NLS_SORT operator with comparison operations if you want the
linguistic sort behavior.
See Also:
■
■
Oracle9i Database Globalization Support Guide for a current listing
of values you can specify for this parameter
Oracle9i Database Concepts for more information on this
parameter
NLS_TERRITORY
Parameter type
String
Syntax
NLS_TERRITORY = territory
Default value
Operating system-dependent
1-102 Oracle9i Database Reference
NLS_TIMESTAMP_FORMAT
Parameter class
Dynamic: ALTER SESSION
Range of values
Any valid territory name
NLS_TERRITORY specifies the name of the territory whose conventions are to be
followed for day and week numbering.
This parameter also establishes the default date format, the default decimal
character and group separator, and the default ISO and local currency symbols.
For information on these settings, see "NLS_DATE_FORMAT" on page 1-97, "NLS_
NUMERIC_CHARACTERS" on page 1-101, "NLS_CURRENCY" on page 1-96, and
"NLS_ISO_CURRENCY" on page 1-99.
See Also:
■
■
Oracle9i Database Globalization Support Guide for a complete list
of territories
Your operating system-specific Oracle documentation for the
territory-dependent default values for these parameters
NLS_TIMESTAMP_FORMAT
Parameter type
String
Syntax
NLS_TIMESTAMP_FORMAT = "format"
Default value
Derived from NLS_TERRITORY
Parameter class
Dynamic: ALTER SESSION
Range of values
Any valid datetime format mask
NLS_TIMESTAMP_FORMAT defines the default timestamp format to use with the
TO_CHAR and TO_TIMESTAMP functions.
The value must be surrounded by quotation marks as follows:
NLS_TIMESTAMP_FORMAT = ’YYYY-MM-DD HH:MI:SS.FF’
You can specify the value of NLS_TIMESTAMP_FORMAT by setting it in the
initialization parameter file. You can specify its value for a client as a client
environment variable.
Initialization Parameters 1-103
NLS_TIMESTAMP_TZ_FORMAT
You can also alter the value of NLS_TIMESTAMP_FORMAT by changing its value in
the initialization parameter and then restarting the instance. To alter the value
during a session use the ALTER SESSION SET statement.
NLS_TIMESTAMP_TZ_FORMAT
Parameter type
String
Syntax
NLS_TIMESTAMP_TZ_FORMAT = "format"
Default value
Derived from NLS_TERRITORY
Parameter class
Dynamic: ALTER SESSION
Range of values
Any valid datetime format mask
NLS_TIMESTAMP_TZ_FORMAT defines the default timestamp with time zone
format to use with the TO_CHAR and TO_TIMESTAMP_TZfunctions.
The value must be surrounded by quotation marks as follows:
NLS_TIMESTAMP_TZ_FORMAT = ’YYYY-MM-DD HH:MI:SS.FF TZH:TZM’
You can specify the value of NLS_TIMESTAMP_TZ_FORMAT by setting it in the
initialization parameter file. You can specify its value for a client as a client
environment variable.
You can also alter the value of NLS_TIMESTAMP_TZ_FORMAT by changing its value
in the initialization parameter and then restarting the instance. To alter the value
during a session use the ALTER SESSION SET statement.
O7_DICTIONARY_ACCESSIBILITY
Parameter type
Boolean
Default value
false
Parameter class
Static
Range of values
true | false
O7_DICTIONARY_ACCESSIBILITY is intended for use when you migrate from
Oracle7 to Oracle9i. It controls restrictions on SYSTEM privileges. If the parameter is
set to true, access to objects in the SYS schema is allowed (Oracle7 behavior). The
1-104 Oracle9i Database Reference
OBJECT_CACHE_MAX_SIZE_PERCENT
default setting of false ensures that system privileges that allow access to objects
in "any schema" do not allow access to objects in SYS schema.
For example, if O7_DICTIONARY_ACCESSIBILITY = false, then the SELECT
ANY TABLE privilege allows access to views or tables in any schema except the SYS
schema (data dictionary tables cannot be accessed). The system privilege EXECUTE
ANY PROCEDURE allows access on the procedures in any schema except the SYS
schema.
If this parameter is set to false and you need to access objects in the SYS schema,
then you must be granted explicit object privilege. Also, the following roles, which
can be granted to the database administrator, also allow access to dictionary objects:
SELECT_CATALOG_ROLE, EXECUTE_CATALOG_ROLE, and DELETE_CATALOG_
ROLE.
See Also:
■
■
Oracle9i Database Migration for more information on this
parameter and the roles mentioned here
Oracle9i SQL Reference for information on granting roles
OBJECT_CACHE_MAX_SIZE_PERCENT
Parameter type
Integer
Default value
10
Parameter class
Dynamic: ALTER SESSION, ALTER SYSTEM ...
DEFERRED
Range of values
0 to operating system-dependent maximum
The object cache is a memory block on the client that allows applications to store
entire objects and to navigate among them without round trips to the server.
OBJECT_CACHE_MAX_SIZE_PERCENT specifies the percentage of the optimal
cache size that the session object cache can grow past the optimal size. The
maximum size is equal to the optimal size plus the product of this percentage and
the optimal size. When the cache size exceeds this maximum size, the system will
attempt to shrink the cache to the optimal size.
Initialization Parameters 1-105
OBJECT_CACHE_OPTIMAL_SIZE
See Also:
■
■
"OBJECT_CACHE_OPTIMAL_SIZE" on page 1-106 for a
description of the object cache
Oracle9i Database Concepts, Pro*C/C++ Precompiler Programmer’s
Guide, and Oracle Call Interface Programmer’s Guide for
information on precompiler use of the object cache
OBJECT_CACHE_OPTIMAL_SIZE
Parameter type
Integer
Default value
102400 (100K)
Parameter class
Dynamic: ALTER SESSION, ALTER SYSTEM ...
DEFERRED
Range of values
10 KB to operating system-dependent maximum
The object cache is a memory block on the client that allows applications to store
entire objects and to navigate among them without round trips to the server.
OBJECT_CACHE_OPTIMAL_SIZE specifies (in bytes) the size to which the session
object cache is reduced when the size of the cache exceeds the maximum size.
See Also: Oracle9i Database Concepts, Pro*C/C++ Precompiler
Programmer’s Guide, and Oracle Call Interface Programmer’s Guide for
information on precompiler use of the object cache
OLAP_PAGE_POOL_SIZE
Parameter type
Integer
Default value
32 MB
Parameter class
Dynamic: ALTER SESSION, ALTER SYSTEM ...
DEFERRED
Range of values
32 MB to 2 GB
OLAP_PAGE_POOL_SIZE specifies the size (in bytes) of the OLAP pool.
1-106 Oracle9i Database Reference
OPEN_LINKS
OPEN_CURSORS
Parameter type
Integer
Default value
50
Parameter class
Dynamic: ALTER SYSTEM
Range of values
1 to 4294967295 (4 GB -1)
OPEN_CURSORS specifies the maximum number of open cursors (handles to private
SQL areas) a session can have at once. You can use this parameter to prevent a
session from opening an excessive number of cursors. This parameter also
constrains the size of the PL/SQL cursor cache which PL/SQL uses to avoid having
to reparse as statements are reexecuted by a user.
It is important to set the value of OPEN_CURSORS high enough to prevent your
application from running out of open cursors. The number will vary from one
application to another. Assuming that a session does not open the number of
cursors specified by OPEN_CURSORS, there is no added overhead to setting this
value higher than actually needed.
See Also:
■
■
Oracle9i Database Performance Tuning Guide and Reference for
more information on setting this parameter
Your operating system-specific Oracle documentation for the
range of values
OPEN_LINKS
Parameter type
Integer
Default value
4
Parameter class
Static
Range of values
0 to 255
OPEN_LINKS specifies the maximum number of concurrent open connections to
remote databases in one session. These connections include database links, as well
as external procedures and cartridges, each of which uses a separate process.
Initialization Parameters 1-107
OPEN_LINKS_PER_INSTANCE
Oracle counts one open link for the following:
■
■
For each user that references a public or private database link
For each external procedure or cartridge connection when it is executed for the
first time
Both types of connections close when the session ends. You can also close a database
link connection explicitly by issuing an ALTER SESSION CLOSE DATABASE
LINK statement.
You should set this parameter to allow for the external procedure and cartridge
connections expected during the session plus the number of databases referred to in
typical distributed transactions (that is, a single SQL statement that references
multiple databases), so that all the databases can be open to execute the statement.
For example, if queries alternately access databases A, B, and C, and OPEN_LINKS
is set to 2, time will be lost waiting while one connection is broken and another
made. Increase the value if many different databases are accessed over time.
This parameter refers only to connections used for distributed transactions. Direct
connections to a remote database specified as an application connects are not
counted.
If you set OPEN_LINKS to 0, then no distributed transactions are allowed.
See Also: "OPEN_LINKS_PER_INSTANCE" on page 1-108 for
information on setting open connections globally for a database
instance
OPEN_LINKS_PER_INSTANCE
Parameter type
Integer
Default value
4
Parameter class
Static
Range of values
0 to 4294967295 (4 GB -1)
Real Application
Clusters
Multiple instances can have different values.
OPEN_LINKS_PER_INSTANCE specifies the maximum number of migratable open
connections globally for each database instance. XA transactions use migratable
1-108 Oracle9i Database Reference
OPTIMIZER_FEATURES_ENABLE
open connections so that the connections are cached after a transaction is
committed. Another transaction can use the connection, provided the user who
created the connection is the same as the user who owns the transaction.
OPEN_LINKS_PER_INSTANCE is different from OPEN_LINKS, which indicates the
number of connections from a session. The OPEN_LINKS parameter is not
applicable to XA applications.
See Also: "OPEN_LINKS" on page 1-107
OPTIMIZER_DYNAMIC_SAMPLING
Parameter type
Integer
Default value
If OPTIMIZER_FEATURES_ENABLE is set to 9.2.0 or
higher, then 1
If OPTIMIZER_FEATURES_ENABLE is set to 9.0.1 or lower,
then 0
Parameter class
Dynamic: ALTER SESSION, ALTER SYSTEM
Range of values
0 to 10
OPTIMIZER_DYNAMIC_SAMPLING controls the level of dynamic sampling
performed by the optimizer.
See Also: Oracle9i Database Performance Tuning Guide and Reference
for more information on setting this parameter
OPTIMIZER_FEATURES_ENABLE
Parameter type
String
Syntax
OPTIMIZER_FEATURES_ENABLE = {8.0.0 | 8.0.3 |
8.0.4 | 8.0.5 | 8.0.6 | 8.0.7 | 8.1.0 | 8.1.3
| 8.1.4 | 8.1.5 | 8.1.6 | 8.1.7 | 9.0.0 |
9.0.1 | 9.2.0}
Default value
9.2.0
Parameter class
Static
Initialization Parameters 1-109
OPTIMIZER_FEATURES_ENABLE
OPTIMIZER_FEATURES_ENABLE acts as an umbrella parameter for enabling a
series of optimizer features based on an Oracle release number.
For example, if you upgrade your database from release 8.0.6 to release 9.2, but you
want to keep the release 8.0.6 optimizer behavior, you can do so by setting this
parameter to 8.0.6. At a later time, you can try the enhancements introduced in
releases up to and including release 9.2 by setting the parameter to 9.2.0.
Table 1–2 describes some of the optimizer features that are enabled when you set
the OPTIMIZER_FEATURES_ENABLE parameter to an 8.0 release or an 8.1 release.
Table 1–3 describes some of the optimizer features that are enabled when you set
the OPTIMIZER_FEATURES_ENABLE parameter to a 9.0 release or a 9.2 release.
See Also: Oracle9i Database Performance Tuning Guide and Reference for
more information about the optimizer and for information about the
features listed in the following tables
Table 1–2
Release 8.0 and Release 8.1 Optimizer Features
Features
Release
8.0.0 8.0.3 8.0.4 8.0.5 8.0.6 8.0.7 8.1.0 8.1.3 8.1.4 8.1.5 8.1.6 8.1.7
Index fast full scan
X
X
X
X
X
X
X
X
X
X
Consideration of bitmap
access paths for tables with
only B-tree indexes
X
X
X
X
Complex view merging
X
X
X
X
Push-join predicate
X
X
X
X
Ordered nested loop costing
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
Random distribution method
for left of nested loops
X
X
Type-dependent selectivity
estimates
X
X
Setting of optimizer mode for
user recursive SQL
X
X
Improved outer join
cardinality calculation
Improved verification of
NULLs inclusion in B-tree
indexes
1-110 Oracle9i Database Reference
OPTIMIZER_FEATURES_ENABLE
Table 1–2 (Cont.) Release 8.0 and Release 8.1 Optimizer Features
Release
Features
8.0.0 8.0.3 8.0.4 8.0.5 8.0.6 8.0.7 8.1.0 8.1.3 8.1.4 8.1.5 8.1.6 8.1.7
Improved average row length
calculation
X
X
Partition pruning based on
subquery predicates
X
X
Common subexpression
elimination
X
Use statistics of a column
imbedded in some selected
functions such as TO_CHAR to
compute selectivity
X
Improved partition statistics
aggregation
X
Table 1–3
Release 9.0 and Release 9.2 Optimizer Features
Features
Release
9.0.0 9.0.1 9.2.0
Index fast full scan
X
X
X
Consideration of bitmap access paths for tables with only B-tree indexes
X
X
X
Complex view merging
X
X
X
Push-join predicate
X
X
X
Ordered nested loop costing
X
X
X
Improved outer join cardinality calculation
X
X
X
Improved verification of NULLs inclusion in B-tree indexes
X
X
X
Random distribution method for left of nested loops
X
X
X
Type-dependent selectivity estimates
X
X
X
Setting of optimizer mode for user recursive SQL
X
X
X
Improved average row length calculation
X
X
X
Partition pruning based on subquery predicates
X
X
X
Common subexpression elimination
X
X
X
Initialization Parameters 1-111
OPTIMIZER_INDEX_CACHING
Table 1–3 (Cont.) Release 9.0 and Release 9.2 Optimizer Features
Release
Features
9.0.0 9.0.1 9.2.0
Use statistics of a column imbedded in some selected functions such as TO_CHAR to
compute selectivity
X
X
X
Improved partition statistics aggregation
X
X
X
Peeking at user-defined bind variables
X
X
X
Index joins
X
X
X
Subquery unnesting
X
X
X
OPTIMIZER_INDEX_CACHING
Parameter type
Integer
Default value
0
Parameter class
Dynamic: ALTER SESSION
Range of values
0 to 100
OPTIMIZER_INDEX_CACHING lets you adjust the behavior of cost-based
optimization to favor nested loops joins and IN-list iterators.
The cost of executing an index using an IN-list iterator or of executing a nested
loops join when an index is used to access the inner table depends on the caching of
that index in the buffer cache. The amount of caching depends on factors that the
optimizer cannot predict, such as the load on the system and the block access
patterns of different users.
You can modify the optimizer’s assumptions about index caching for nested loops
joins and IN-list iterators by setting this parameter to a value between 0 and 100 to
indicate the percentage of the index blocks the optimizer should assume are in the
cache. Setting this parameter to a higher value makes nested loops joins and IN-list
iterators look less expensive to the optimizer. As a result, it will be more likely to
pick nested loops joins over hash or sort-merge joins and to pick indexes using
IN-list iterators over other indexes or full table scans. The default for this parameter
is 0, which results in default optimizer behavior.
See Also: Oracle9i Database Performance Tuning Guide and Reference
for more information on setting this parameter
1-112 Oracle9i Database Reference
OPTIMIZER_MAX_PERMUTATIONS
OPTIMIZER_INDEX_COST_ADJ
Parameter type
Integer
Default value
100
Parameter class
Dynamic: ALTER SESSION
Range of values
1 to 10000
OPTIMIZER_INDEX_COST_ADJ lets you tune optimizer behavior for access path
selection to be more or less index friendly—that is, to make the optimizer more or
less prone to selecting an index access path over a full table scan.
The default for this parameter is 100 percent, at which the optimizer evaluates index
access paths at the regular cost. Any other value makes the optimizer evaluate the
access path at that percentage of the regular cost. For example, a setting of 50 makes
the index access path look half as expensive as normal.
Note: The adjustment does not apply to user-defined cost
functions for domain indexes.
See Also: Oracle9i Database Performance Tuning Guide and Reference
for more information on setting this parameter, and on its
relationship to "OPTIMIZER_INDEX_CACHING"
OPTIMIZER_MAX_PERMUTATIONS
Parameter type
Integer
Default value
If OPTIMIZER_FEATURES_ENABLE is set to 9.0.0 or
higher, then 2000
If OPTIMIZER_FEATURES_ENABLE is set to 8.1.7 or lower,
then 80000
Parameter class
Dynamic: ALTER SESSION
Range of values
4 to 80000
OPTIMIZER_MAX_PERMUTATIONS restricts the number of permutations of the
tables the optimizer will consider in queries with joins. Such a restriction ensures
Initialization Parameters 1-113
OPTIMIZER_MODE
that the parse time for the query stays within acceptable limits. However, a slight
risk exists that the optimizer will overlook a good plan it would otherwise have
found.
The default value for this parameter is 80000, which corresponds to no limitation at
all. Setting this parameter to a value less than 1000 normally ensures parse times of
a few seconds or less.
OPTIMIZER_MODE
Parameter type
String
Syntax
OPTIMIZER_MODE =
{first_rows_[1 | 10 | 100 | 1000] | first_
rows | all_rows | choose | rule}
Default value
choose
Parameter class
Dynamic: ALTER SESSION
OPTIMIZER_MODE establishes the default behavior for choosing an optimization
approach for the instance.
Values:
■
rule
The optimizer chooses a rule-based approach for all SQL statements regardless
of the presence of statistics.
■
choose
The optimizer chooses between a cost-based approach and a rule-based
approach based on whether statistics are available.
If the data dictionary contains statistics for at least one of the accessed tables,
then the optimizer uses a cost-based approach and optimizes with a goal of best
throughput. If the data dictionary contains only some statistics, then the
cost-based approach is used, and the optimizer must guess the statistics for the
subjects without any statistics. This can result in sub-optimal execution plans. If
the data dictionary contains no statistics for any of the accessed tables, then the
optimizer uses a rule-based approach.
■
first_rows_n
1-114 Oracle9i Database Reference
ORACLE_TRACE_COLLECTION_NAME
The optimizer uses a cost-based approach, regardless of the presence of
statistics, and optimizes with a goal of best response time to return the first n
rows (where n = 1, 10, 100, 1000).
■
first_rows
The optimizer uses a mix of costs and heuristics to find a best plan for fast
delivery of the first few rows.
■
all_rows
The optimizer uses a cost-based approach for all SQL statements in the session
regardless of the presence of statistics and optimizes with a goal of best
throughput (minimum resource use to complete the entire statement).
See Also:
■
■
Oracle9i Database Performance Tuning Guide and Reference for
more information on setting this parameter
Oracle9i Database Concepts and Oracle9i Database Performance
Tuning Guide and Reference for more information about the
optimizer
ORACLE_TRACE_COLLECTION_NAME
Parameter type
String
Syntax
ORACLE_TRACE_COLLECTION_NAME = collection_
name
Default value
There is no default value.
Parameter class
Static
Range of values
Valid collection name up to 16 characters long (except for
platforms that enforce 8-character file names)
A collection is data collected for events that occurred while an instrumented
product was running. ORACLE_TRACE_COLLECTION_NAME specifies the Oracle
Trace collection name for this instance. Oracle also uses this parameter in the output
file names (collection definition file .cdf and data collection file .dat). If you set
ORACLE_TRACE_ENABLE to true, setting this value to a non-null string will start a
default Oracle Trace collection that will run until this value is set to null again.
Initialization Parameters 1-115
ORACLE_TRACE_COLLECTION_PATH
See Also:
■
■
Oracle9i Database Performance Tuning Guide and Reference for
more information on the Oracle Trace facility and on setting
this parameter
"ORACLE_TRACE_ENABLE" on page 1-117
ORACLE_TRACE_COLLECTION_PATH
Parameter type
String
Syntax
ORACLE_TRACE_COLLECTION_PATH = pathname
Default value
Operating system-specific
Parameter class
Static
Range of values
Full directory pathname
ORACLE_TRACE_COLLECTION_PATH specifies the directory pathname where the
Oracle Trace collection definition (.cdf) and data collection (.dat) files are located. If
you accept the default, the Oracle Trace .cdf and .dat files will be located in
ORACLE_HOME/otrace/admin/cdf.
You must specify this parameter if you set the ORACLE_TRACE_FACILITY_NAME
parameter.
See Also: Oracle9i Database Performance Tuning Guide and Reference
for more information on the Oracle Trace facility and on setting this
parameter
ORACLE_TRACE_COLLECTION_SIZE
Parameter type
Integer
Default value
5242880
Parameter class
Static
Range of values
0 to 4294967295
ORACLE_TRACE_COLLECTION_SIZE specifies (in bytes) the maximum size of the
Oracle Trace collection file (.dat). Once the collection file reaches this maximum, the
collection is disabled. A value of 0 means that the file has no size limit.
1-116 Oracle9i Database Reference
ORACLE_TRACE_FACILITY_NAME
See Also: Oracle9i Database Performance Tuning Guide and Reference
for more information on the Oracle Trace facility and on setting this
parameter
ORACLE_TRACE_ENABLE
Parameter type
Boolean
Default value
false
Parameter class
Dynamic: ALTER SESSION, ALTER SYSTEM
Range of values
true | false
To enable Oracle Trace collections for the server, set ORACLE_TRACE_ENABLE to
true. This setting alone does not start an Oracle Trace collection, but it allows
Oracle Trace to be used for the server.
With ORACLE_TRACE_ENABLE set to true, you can perform Oracle Trace collection
of server event data in any of the following ways:
■
■
■
By using Oracle Trace Manager, which is supplied with the Oracle Diagnostic
Pack
By using the Oracle Trace command line interface, which is supplied with the
server
By specifying a collection name in the ORACLE_TRACE_COLLECTION_NAME
parameter
See Also:
■
■
Oracle9i Database Performance Tuning Guide and Reference for
more information on the Oracle Trace facility and on setting
this parameter
"ORACLE_TRACE_COLLECTION_NAME" on page 1-115
ORACLE_TRACE_FACILITY_NAME
Parameter type
String
Initialization Parameters 1-117
ORACLE_TRACE_FACILITY_PATH
Syntax
ORACLE_TRACE_FACILITY_NAME =
{ORACLED | ORACLEE | ORACLESM | ORACLEC}
Default value
ORACLED
Parameter class
Static
ORACLE_TRACE_FACILITY_NAME specifies the event set that Oracle Trace collects.
The value of this parameter, followed by the .fdf extension, is the name of the
Oracle Trace product definition file. That file must be located in the directory
specified by the ORACLE_TRACE_FACILITY_PATH parameter. The product
definition file contains definition information for all the events and data items that
can be collected for products that use the Oracle Trace data collection API.
The Oracle server has multiple event sets and therefore multiple product definition
files:
■
ORACLE is the ALL event set
■
ORACLED is the DEFAULT event set
■
ORACLEE is the EXPERT event set
■
ORACLESM is the SUMMARY event set
■
ORACLEC is the CACHEIO event set
Oracle Corporation recommends that you use the DEFAULT event set for Oracle
server collections, ORACLED.
See Also:
■
■
Oracle9i Database Performance Tuning Guide and Reference for
more information on the Oracle Trace facility and on setting
this parameter
"ORACLE_TRACE_COLLECTION_PATH" on page 1-116
ORACLE_TRACE_FACILITY_PATH
Parameter type
String
Syntax
ORACLE_TRACE_FACILITY_PATH = pathname
Default value
Operating system-specific
Parameter class
Static
1-118 Oracle9i Database Reference
OS_AUTHENT_PREFIX
Range of values
Full directory pathname
ORACLE_TRACE_FACILITY_PATH specifies the directory pathname where Oracle
Trace facility definition files are located. On Solaris, the default path is ORACLE_
HOME/otrace/admin/fdf/. On NT, the default path is
%OTRACE80%\ADMIN\FDF\.
See Also: Oracle9i Database Performance Tuning Guide and Reference
for more information on the Oracle Trace facility and on setting this
parameter
OS_AUTHENT_PREFIX
Parameter type
String
Syntax
OS_AUTHENT_PREFIX = authentication_prefix
Default value
OPS$
Parameter class
Static
OS_AUTHENT_PREFIX specifies a prefix that Oracle uses to authenticate users
attempting to connect to the server. Oracle concatenates the value of this parameter
to the beginning of the user’s operating system account name and password. When
a connection request is attempted, Oracle compares the prefixed username with
Oracle usernames in the database.
The default value of this parameter is OPS$ for backward compatibility with
previous versions. However, you might prefer to set the prefix value to "" (a null
string), thereby eliminating the addition of any prefix to operating system account
names.
Note: The text of the OS_AUTHENT_PREFIX parameter is case
sensitive on some operating systems.
See Also:
■
■
Oracle Advanced Security Administrator’s Guide for more
information on setting this parameter
Your operating system-specific Oracle documentation for the
default value
Initialization Parameters 1-119
OS_ROLES
OS_ROLES
Parameter type
Boolean
Default value
false
Parameter class
Static
Range of values
true | false
OS_ROLES determines whether Oracle or the operating system identifies and
manages the roles of each username.
Values:
■
TRUE
The operating system completely manages the role grants for all database
usernames. When a user attempts to create a session, the username’s security
domain is initialized using the roles identified by the operating system. A user
can subsequently enable as many roles identified by the operating system as
specified by the parameter MAX_ENABLED_ROLES.
Revocation by Oracle of roles granted by the operating system is ignored, as are
any roles previously granted by Oracle.
■
FALSE
Oracle identifies and manages the roles.
See Also:
■
■
Oracle9i Database Administrator’s Guide and Oracle Advanced
Security Administrator’s Guide for more information on roles and
on setting this parameter
"MAX_ENABLED_ROLES" on page 1-94 and "REMOTE_OS_
ROLES" on page 1-140
PARALLEL_ADAPTIVE_MULTI_USER
Parameter type
Boolean
Default value
Derived from the value of PARALLEL_AUTOMATIC_TUNING
Parameter class
Dynamic: ALTER SYSTEM
1-120 Oracle9i Database Reference
PARALLEL_AUTOMATIC_TUNING
Range of values
true | false
PARALLEL_ADAPTIVE_MULTI_USER, when set to true, enables an adaptive
algorithm designed to improve performance in multiuser environments that use
parallel execution. The algorithm automatically reduces the requested degree of
parallelism based on the system load at query startup time. The effective degree of
parallelism is based on the default degree of parallelism, or the degree from the
table or hints, divided by a reduction factor.
The algorithm assumes the following:
■
■
The system has been tuned for optimal performance in a single-user
environment
The parameter PARALLEL_AUTOMATIC_TUNING parameter is set to TRUE
Tables and hints use the default degree of parallelism.
See Also: Oracle9i Database Performance Tuning Guide and Reference
for more information on tuning parallel execution and on the
algorithm described here
PARALLEL_AUTOMATIC_TUNING
Parameter type
Boolean
Default value
false
Parameter class
Static
Range of values
true | false
Note: This parameter applies to parallel execution in exclusive
mode as well as in the Oracle9i Real Application Clusters
environment.
When PARALLEL_AUTOMATIC_TUNING is set to true, Oracle determines the
default values for parameters that control parallel execution. In addition to setting
this parameter, you must specify the PARALLEL clause for the target tables in the
system. Oracle then tunes all subsequent parallel operations automatically.
If you used parallel execution in a previous release and are now enabling
PARALLEL_AUTOMATIC_TUNING, you should reduce the amount of memory
Initialization Parameters 1-121
PARALLEL_EXECUTION_MESSAGE_SIZE
allocated from the shared pool to account for the decreased demand on that pool.
This memory will now be allocated from the large pool, and will be computed
automatically if LARGE_POOL_SIZE is left unset.
As part of the automatic tuning, Oracle will enable the PARALLEL_ADAPTIVE_
MULTI_USER parameter. You can override any of the system-provided defaults if
desired.
See Also: Oracle9i Database Performance Tuning Guide and Reference
for more information on tuning parallel execution
PARALLEL_EXECUTION_MESSAGE_SIZE
Parameter type
Integer
Default value
Operating system-dependent
Parameter class
Static
Range of values
2148 to 65535 (64 KB - 1)
Real Application
Clusters
Multiple instances must have the same value.
PARALLEL_EXECUTION_MESSAGE_SIZE specifies the size of messages for parallel
execution (formerly referred to as parallel query, PDML, Parallel Recovery,
replication).
On most platforms, the default value is 2148bytes if PARALLEL_AUTOMATIC_
TUNING is set to false, and 4096 bytes if PARALLEL_AUTOMATIC_TUNING is set
to true. The default value is adequate for most applications. Larger values require
a larger shared pool. Larger values result in better performance at the cost of higher
memory use. For this reason, replication gets no benefit from increasing the size.
Note: When PARALLEL_AUTOMATIC_TUNING is set to TRUE,
message buffers are allocated out of the large pool. In this case, the
default is generally higher.
PARALLEL_INSTANCE_GROUP
Parameter type
1-122 Oracle9i Database Reference
String
PARALLEL_MAX_SERVERS
Syntax
PARALLEL_INSTANCE_GROUP = group_name
Default value
A group consisting of all instances currently active
Parameter class
Dynamic: ALTER SESSION, ALTER SYSTEM
Range of values
Any group name specified in the INSTANCE_GROUPS
parameter of any active instance
Real Application
Clusters
Different instances can have different values.
PARALLEL_INSTANCE_GROUP is an Oracle9i Real Application Clusters parameter
that you can specify in parallel mode only. Used in conjunction with the
INSTANCE_GROUPS parameter, it lets you restrict parallel query operations to a
limited number of instances.
This parameter identifies the parallel instance group Oracle will use for spawning
parallel execution processes. Parallel operations will spawn parallel execution
processes only on instances that specify a matching group in their INSTANCE_
GROUPS parameter.
If the value of PARALLEL_INSTANCE_GROUP does not correspond to an instance
group name specified for an active instance, Oracle returns an error.
See Also: Oracle9i Real Application Clusters Administration for more
information on parallel query execution in an Oracle9i Real
Application Clusters environment
PARALLEL_MAX_SERVERS
Parameter type
Integer
Default value
Derived from the values of CPU_COUNT, PARALLEL_
AUTOMATIC_TUNING, and PARALLEL_ADAPTIVE_MULTI_
USER
Parameter class
Static
Range of values
0 to 3599
Real Application
Clusters
Multiple instances must have the same value.
Initialization Parameters 1-123
PARALLEL_MIN_PERCENT
Note: This parameter applies to parallel execution in exclusive
mode as well as in the Oracle9i Real Application Clusters
environment.
PARALLEL_MAX_SERVERS specifies the maximum number of parallel execution
processes and parallel recovery processes for an instance. As demand increases,
Oracle increases the number of processes from the number created at instance
startup up to this value.
If you set this parameter too low, some queries may not have a parallel execution
process available to them during query processing. If you set it too high, memory
resource shortages may occur during peak periods, which can degrade
performance.
See Also: Oracle9i Database Performance Tuning Guide and Reference
for more information on tuning parallel execution
PARALLEL_MIN_PERCENT
Parameter type
Integer
Default value
0
Parameter class
Dynamic: ALTER SESSION
Range of values
0 to 100
Real Application
Clusters
Multiple instances can have different values.
PARALLEL_MIN_PERCENT operates in conjunction with PARALLEL_MAX_SERVERS
and PARALLEL_MIN_SERVERS. It lets you specify the minimum percentage of
parallel execution processes (of the value of PARALLEL_MAX_SERVERS) required
for parallel execution. Setting this parameter ensures that parallel operations will
not execute sequentially unless adequate resources are available. The default value
of 0 means that no minimum percentage of processes has been set.
Consider the following settings:
PARALLEL_MIN_PERCENT = 50
PARALLEL_MIN_SERVERS = 5
PARALLEL_MAX_SERVERS = 10
1-124 Oracle9i Database Reference
PARALLEL_MIN_SERVERS
If 8 of the 10 parallel execution processes are busy, only 2 processes are available. If
you then request a query with a degree of parallelism of 8, the minimum 50% will
not be met.
You can use this parameter in conjunction with PARALLEL_ADAPTIVE_MULTI_
USER. In a multi-user environment, an individual user or application can set
PARALLEL_MIN_PERCENT to a minimum value until sufficient resources are
available on the system and an acceptable degree of parallelism is returned.
See Also:
■
■
Oracle9i Database Performance Tuning Guide and Reference for
more information on tuning parallel execution
"PARALLEL_MAX_SERVERS" on page 1-123, "PARALLEL_
MIN_SERVERS" on page 1-125, and "PARALLEL_ADAPTIVE_
MULTI_USER" on page 1-120
PARALLEL_MIN_SERVERS
Parameter type
Integer
Default value
0
Parameter class
Static
Range of values
0 to value of PARALLEL_MAX_SERVERS
Real Application
Clusters
Multiple instances can have different values.
Note: This parameter applies to parallel execution in exclusive
mode as well as in the Oracle9i Real Application Clusters
environment.
PARALLEL_MIN_SERVERS specifies the minimum number of parallel execution
processes for the instance. This value is the number of parallel execution processes
Oracle creates when the instance is started.
See Also: Oracle9i Database Performance Tuning Guide and Reference
for more information on tuning parallel execution
Initialization Parameters 1-125
PARALLEL_THREADS_PER_CPU
PARALLEL_THREADS_PER_CPU
Parameter type
Integer
Default value
Operating system-dependent, usually 2
Parameter class
Dynamic: ALTER SYSTEM
Range of values
Any nonzero number
Note: This parameter applies to parallel execution in exclusive
mode as well as in the Oracle9i Real Application Clusters
environment.
PARALLEL_THREADS_PER_CPU specifies the default degree of parallelism for the
instance and determines the parallel adaptive and load balancing algorithms. The
parameter describes the number of parallel execution processes or threads that a
CPU can handle during parallel execution.
The default is platform-dependent and is adequate in most cases. You should
decrease the value of this parameter if the machine appears to be overloaded when
a representative parallel query is executed. You should increase the value if the
system is I/O bound.
See Also: Oracle9i Database Performance Tuning Guide and Reference
for more information on tuning parallel execution
PARTITION_VIEW_ENABLED
Parameter type
Boolean
Default value
false
Parameter class
Dynamic: ALTER SESSION
Range of values
true | false
Note: Oracle Corporation recommends that you use partitioned
tables (available starting with Oracle8) rather than partition views.
Partition views are supported for backward compatibility only.
1-126 Oracle9i Database Reference
PGA_AGGREGATE_TARGET
PARTITION_VIEW_ENABLED specifies whether the optimizer uses partition views.
If you set this parameter to true, the optimizer prunes (or skips) unnecessary table
accesses in a partition view and alters the way it computes statistics on a partition
view from statistics on underlying tables.
See Also: Oracle9i Database Concepts for information on the
advantages of partitioned tables and how to convert partition
views to partitioned tables
PGA_AGGREGATE_TARGET
Parameter type
Big integer
Syntax
PGA_AGGREGATE_TARGET = integer [K | M | G]
Default value
0 (automatic memory management is turned OFF by
default)
Parameter class
Dynamic: ALTER SYSTEM
Range of values
Minimum: 10 MB
Maximum: 4096 GB - 1
PGA_AGGREGATE_TARGET specifies the target aggregate PGA memory available to
all server processes attached to the instance. You must set this parameter to enable
the automatic sizing of SQL working areas used by memory-intensive SQL
operators such as sort, group-by, hash-join, bitmap merge, and bitmap create.
Oracle uses this parameter as a target for PGA memory. Use this parameter to
determine the optimal size of each work area allocated in AUTO mode (in other
words, when WORKAREA_SIZE_POLICY is set to AUTO.
Oracle attempts to keep the amount of private memory below the target specified
by this parameter by adapting the size of the work areas to private memory. When
increasing the value of this parameter, you indirectly increase the memory allotted
to work areas. Consequently, more memory-intensive operations are able to run
fully in memory and less will work their way over to disk.
When setting this parameter, you should examine the total memory on your system
that is available to the Oracle instance and subtract the SGA. You can assign the
remaining memory to PGA_AGGREGATE_TARGET.
Initialization Parameters 1-127
PLSQL_COMPILER_FLAGS
PLSQL_COMPILER_FLAGS
Parameter type
String
Syntax
PLSQL_COMPILER_FLAGS = { [DEBUG | NON_DEBUG]
[INTERPRETED | NATIVE] }
Default value
INTERPRETED, NON_DEBUG
Parameter class
Dynamic: ALTER SESSION, ALTER SYSTEM
PLSQL_COMPILER_FLAGS is a parameter used by the PL/SQL compiler. It specifies
a list of compiler flags as a comma-separated list of strings.
Values:
■
INTERPRETED
PL/SQL modules will be compiled to PL/SQL bytecode format. Such modules
are executed by the PL/SQL interpreter engine.
■
NATIVE
PL/SQL modules (with the possible exception of top-level anonymous PL/SQL
blocks) will be compiled to native (machine) code. Such modules will be
executed natively without incurring any interpreter overhead.
■
DEBUG
PL/SQL modules will be compiled with PROBE debug symbols.
The following combinations of flags are invalid specifications for the PLSQL_
COMPILER_FLAGS parameter:
■
NATIVE & DEBUG
■
NATIVE & INTERPRETED
When the value of the parameter is changed, it has no effect on PL/SQL modules
that have already been compiled.
The value of this parameter is stored persistently with the library unit. If a pl/sql
library unit is compiled native, all subsequent automatic recompilations of that
library unit will use native compilation.
1-128 Oracle9i Database Reference
PLSQL_NATIVE_LIBRARY_SUBDIR_COUNT
PLSQL_NATIVE_C_COMPILER
Parameter type
String
Syntax
PLSQL_NATIVE_C_COMPILER = pathname
Default value
There is no default value.
Parameter class
Dynamic: ALTER SYSTEM
Range of values
Any valid path name
PLSQL_NATIVE_C_COMPILER specifies the full path name of a C compiler which is
used to compile the generated C file into an object file.
PLSQL_NATIVE_C_COMPILER is optional. The platform-specific make file that is
shipped for each platform contains a default value for this parameter. If a value is
specified for this parameter, it will override the default value in the make file.
PLSQL_NATIVE_LIBRARY_DIR
Parameter type
String
Syntax
PLSQL_NATIVE_LIBRARY_DIR = directory
Default value
There is no default value.
Parameter class
Dynamic: ALTER SYSTEM
Range of values
Any valid directory path
PLSQL_NATIVE_LIBRARY_DIR is a parameter used by the PL/SQL compiler. It
specifies the name of a directory where the shared objects produced by the native
compiler are stored.
PLSQL_NATIVE_LIBRARY_SUBDIR_COUNT
Parameter type
Integer
Default value
0
Parameter class
Dynamic: ALTER SYSTEM
Initialization Parameters 1-129
PLSQL_NATIVE_LINKER
Range of values
0 to 232-1 (max value represented by 32 bits)
PLSQL_NATIVE_LIBRARY_SUBDIR_COUNT specifies the number of subdirectories
created by the database administrator in the directory specified by PLSQL_
NATIVE_LIBRARY_DIR.
When using the PL/SQL native compiler, Performance of file create/open
operations is unacceptably slow if the number of files in a directory is very large. It
is usually advisable to create subdirectories and use this parameter if the total
number of different PL/SQL packages that may need to be compiled natively by all
users of the database instance exceeds 10000.
The subdirectories should have names corresponding to zero-based decimal
numbers, prefixed by d. For example, the database administrator can create 1000
subdirectories named d0, d1, ... d999, and set PLSQL_NATIVE_LIBRARY_
SUBDIR_COUNT to 1000.
PLSQL_NATIVE_LINKER
Parameter type
String
Syntax
PLSQL_NATIVE_LINKER = pathname
Default value
There is no default value.
Parameter class
Dynamic: ALTER SYSTEM
Range of values
Any valid path name
PLSQL_NATIVE_LINKER specifies the full path name of a linker such as ld in UNIX
or GNU ld which is used to link the object file into a shared object or DLL.
PLSQL_NATIVE_LINKER is optional. The platform-specific make file that is
shipped for each platform contains a default value for this parameter. If a value is
specified for this parameter, it will override the default value in the make file.
PLSQL_NATIVE_MAKE_FILE_NAME
Parameter type
String
Syntax
PLSQL_NATIVE_MAKE_FILE_NAME = pathname
Default value
There is no default value.
1-130 Oracle9i Database Reference
PLSQL_V2_COMPATIBILITY
Parameter class
Dynamic: ALTER SYSTEM
Range of values
Any valid path name
PLSQL_NATIVE_MAKE_FILE_NAME specifies the full path name of a make file. The
make utility (specified by PLSQL_NATIVE_MAKE_UTILITY) uses this make file to
generate the shared object or DLL.
A port-specific make file is shipped for each platform that contains the rules for the
make utility to generate DLLs on that platform.
PLSQL_NATIVE_MAKE_UTILITY
Parameter type
String
Syntax
PLSQL_NATIVE_MAKE_UTILITY = pathname
Default value
There is no default value.
Parameter class
Dynamic: ALTER SYSTEM
Range of values
Any valid path name
PLSQL_NATIVE_MAKE_UTILITY specifies the full path name of a make utility such
as make in UNIX or gmake (GNU make). The make utility is needed to generate the
shared object or DLL from the generated C source.
PLSQL_V2_COMPATIBILITY
Parameter type
Boolean
Default value
false
Parameter class
Dynamic: ALTER SESSION, ALTER SYSTEM
Range of values
true | false
PL/SQL Version 2 allows some abnormal behavior that Version 8 disallows. If you
want to retain that behavior for backward compatibility, set PLSQL_V2_
COMPATIBILITY to true. If you set it to false, PL/SQL Version 8 behavior is
enforced and Version 2 behavior is not allowed.
Initialization Parameters 1-131
PRE_PAGE_SGA
See Also: PL/SQL User’s Guide and Reference for a description of
the differences between PL/SQL Version 2 and Version 8, and for
more information on setting this parameter
PRE_PAGE_SGA
Parameter type
Boolean
Default value
false
Parameter class
Static
Range of values
true | false
PRE_PAGE_SGA determines whether Oracle reads the entire SGA into memory at
instance startup. Operating system page table entries are then prebuilt for each page
of the SGA. This setting can increase the amount of time necessary for instance
startup, but it is likely to decrease the amount of time necessary for Oracle to reach
its full performance capacity after startup.
Note: This setting does not prevent your operating system from
paging or swapping the SGA after it is initially read into memory.
PRE_PAGE_SGA can increase the process startup duration, because every process
that starts must access every page in the SGA. The cost of this strategy is fixed;
however, you might simply determine that 20,000 pages must be touched every
time a process starts. This approach can be useful with some applications, but not
with all applications. Overhead can be significant if your system frequently creates
and destroys processes by, for example, continually logging on and logging off.
The advantage that PRE_PAGE_SGA can afford depends on page size. For example,
if the SGA is 80 MB in size and the page size is 4 KB, then 20,000 pages must be
touched to refresh the SGA (80,000/4 = 20,000).
If the system permits you to set a 4 MB page size, then only 20 pages must be
touched to refresh the SGA (80,000/4,000 = 20). The page size is operating
system-specific and generally cannot be changed. Some operating systems,
however, have a special implementation for shared memory whereby you can
change the page size.
1-132 Oracle9i Database Reference
QUERY_REWRITE_ENABLED
PROCESSES
Parameter type
Integer
Default value
Derived from PARALLEL_MAX_SERVERS
Parameter class
Static
Range of values
6 to operating system-dependent
Real Application
Clusters
Multiple instances can have different values.
PROCESSES specifies the maximum number of operating system user processes that
can simultaneously connect to Oracle. Its value should allow for all background
processes such as locks, job queue processes, and parallel execution processes.
The default values of the SESSIONS and TRANSACTIONS parameters are derived
from this parameter. Therefore, if you change the value of PROCESSES, you should
evaluate whether to adjust the values of those derived parameters.
See Also:
■
■
■
Oracle9i Database Administrator’s Guide for information on
setting this parameter in exclusive mode
Oracle9i Real Application Clusters Administration for information
on setting this parameter in an Oracle9i Real Application
Clusters environment
Your operating system-specific Oracle documentation for the
range of values
QUERY_REWRITE_ENABLED
Parameter type
String
Syntax
QUERY_REWRITE_ENABLED = {force | true |
false}
Default value
false
Parameter class
Dynamic: ALTER SESSION, ALTER SYSTEM
Initialization Parameters 1-133
QUERY_REWRITE_INTEGRITY
Real Application
Clusters
Multiple instances can have different values.
QUERY_REWRITE_ENABLED allows you to enable or disable query rewriting
globally for the database.
Values:
■
true
Oracle costs the query with rewrite and without rewrite and chooses the
method with the lower cost.
■
false
Oracle does not use rewrite.
■
force
Oracle always uses rewrite and does not evaluate the cost before doing so. Use
force when you know that the query will always benefit from rewrite and
when reduction in compile time is important.
To take advantage of query rewrite for a particular materialized view, you must
enable query rewrite for that materialized view, and you must enable cost-based
optimization.
See Also:
■
■
Oracle9i Data Warehousing Guide for information on query
rewrite of materialized views
Oracle9i Database Performance Tuning Guide and Reference and
"OPTIMIZER_MODE" on page 1-114 for information on
cost-based optimization
QUERY_REWRITE_INTEGRITY
Parameter type
String
Syntax
QUERY_REWRITE_INTEGRITY =
{stale_tolerated | trusted | enforced}
Default value
enforced
Parameter class
Dynamic: ALTER SESSION, ALTER SYSTEM
1-134 Oracle9i Database Reference
RDBMS_SERVER_DN
Real Application
Clusters
Multiple instances can have different values.
QUERY_REWRITE_INTEGRITY determines the degree to which Oracle must enforce
query rewriting. At the safest level, Oracle does not use query rewrite
transformations that rely on unenforced relationships.
Values:
■
ENFORCED
Oracle enforces and guarantees consistency and integrity.
■
TRUSTED
Oracle allows rewrites using relationships that have been declared, but that are
not enforced by Oracle.
■
STALE_TOLERATED
Oracle allows rewrites using unenforced relationships. Materialized views are
eligible for rewrite even if they are known to be inconsistent with the
underlying detail data.
RDBMS_SERVER_DN
Parameter type
X.500 Distinguished Name
Default value
There is no default value.
Parameter class
Static
Range of values
All X.500 Distinguished Name format values
RDBMS_SERVER_DN specifies the Distinguished Name (DN) of the Oracle server. It
is used for retrieving Enterprise Roles from an enterprise directory service.
If you do not want to use a directory for enterprise user and privilege management,
but prefer to use SSL authentication alone, do not set this parameter.
See Also: Oracle Advanced Security Administrator’s Guide for more
information on enterprise roles and the enterprise directory service
Initialization Parameters 1-135
READ_ONLY_OPEN_DELAYED
READ_ONLY_OPEN_DELAYED
Parameter type
Boolean
Default value
false
Parameter class
Static
Range of values
true | false
READ_ONLY_OPEN_DELAYED determines when datafiles in read-only tablespaces
are accessed.
Values:
■
true
The datafiles are accessed for the first time only when an attempt is made to
read data stored within them.
■
false
The datafiles are accessed at database open time.
You can use this parameter to speed up some operations (primarily opening the
database) for very large databases when substantial portions of the database are
stored in read-only tablespaces. Consider setting this parameter to true for such
databases, especially if portions of the read-only data are stored on slow-access
devices or hierarchical storage.
See Also: Oracle9i Database Administrator’s Guide for information
on the consequences of delaying access of datafiles in read-only
tablespaces
RECOVERY_PARALLELISM
Parameter type
Integer
Default value
Operating system-dependent
Parameter class
Static
Range of values
Operating system-dependent, but cannot exceed
PARALLEL_MAX_SERVERS
1-136 Oracle9i Database Reference
REMOTE_ARCHIVE_ENABLE
RECOVERY_PARALLELISM specifies the number of processes to participate in
instance or crash recovery. A value of 0 or 1 indicates that recovery is to be
performed serially by one process.
See Also:
■
■
Oracle9i Database Performance Tuning Guide and Reference for
information on setting this parameter in exclusive mode
Oracle9i Real Application Clusters Administration for information
on setting this parameter in an Oracle9i Real Application
Clusters environment
REMOTE_ARCHIVE_ENABLE
Parameter type
String
Syntax
REMOTE_ARCHIVE_ENABLE = {receive [, send] |
false | true}
Default value
true
Parameter class
Static
REMOTE_ARCHIVE_ENABLE enables or disables the sending of redo archival to
remote destinations and the receipt of remotely archived redo.
Values:
■
receive
Disables the sending of redo archival to remote destinations and enables the
receipt of remotely archived redo.
■
send
Enables the sending of redo archival to remote destinations and disables the
receipt of remotely archived redo.
■
false
Disables both the sending of redo archival to remote destinations and the
receipt of remotely archived redo.
■
receive, send or true
Initialization Parameters 1-137
REMOTE_DEPENDENCIES_MODE
Enables both the sending of redo archival to remote destinations and the receipt
of remotely archived redo.
REMOTE_DEPENDENCIES_MODE
Parameter type
String
Syntax
REMOTE_DEPENDENCIES_MODE = {TIMESTAMP |
SIGNATURE}
Default value
TIMESTAMP
Parameter class
Dynamic: ALTER SESSION, ALTER SYSTEM
REMOTE_DEPENDENCIES_MODE specifies how Oracle should handle dependencies
upon remote PL/SQL stored procedures.
Values:
■
TIMESTAMP
The client running the procedure compares the timestamp recorded on the
server-side procedure with the current timestamp of the local procedure and
executes the procedure only if the timestamps match.
■
SIGNATURE
Oracle allows the procedure to execute as long as the signatures are considered
safe. This setting allows client PL/SQL applications to be run without
recompilation.
See Also: Oracle9i Application Developer’s Guide - Fundamentals for
information about the consequences of the settings of this
parameter
REMOTE_LISTENER
Parameter type
String
Syntax
REMOTE_LISTENER = network_name
Default value
There is no default value.
Parameter class
Dynamic: ALTER SYSTEM
1-138 Oracle9i Database Reference
REMOTE_LOGIN_PASSWORDFILE
REMOTE_LISTENER specifies a network name that resolves to an address or
address list of Oracle Net remote listeners (that is, listeners that are not running on
the same machine as this instance). The address or address list is specified in the
TNSNAMES.ORA file or other address repository as configured for your system.
See Also:
Oracle9i Database Concepts for more information about
instances, listener processes, and dispatcher processes
■
Oracle9i Net Services Administrator’s Guide and your operating
system-specific Oracle documentation for more information
about specifying network addresses for the protocols on your
system
■
REMOTE_LOGIN_PASSWORDFILE
Parameter type
String
Syntax
REMOTE_LOGIN_PASSWORDFILE=
{NONE | SHARED | EXCLUSIVE}
Default value
NONE
Parameter class
Static
Real Application
Clusters
Multiple instances must have the same value.
REMOTE_LOGIN_PASSWORDFILE specifies whether Oracle checks for a password
file and how many databases can use the password file.
Values:
■
NONE
Oracle ignores any password file. Therefore, privileged users must be
authenticated by the operating system.
■
SHARED
More than one database can use a password file. However, the only user
recognized by the password file is SYS.
■
EXCLUSIVE
Initialization Parameters 1-139
REMOTE_OS_AUTHENT
The password file can be used by only one database and the password file can
contain names other than SYS.
Note: This setting is required for Oracle9i Real Application
Clusters
See Also: Oracle9i Database Administrator’s Guidefor more
information about secure connections for privileged users
REMOTE_OS_AUTHENT
Parameter type
Boolean
Default value
false
Parameter class
Static
Range of values
true | false
REMOTE_OS_AUTHENT specifies whether remote clients will be authenticated with
the value of the OS_AUTHENT_PREFIX parameter.
See Also:
■
■
Oracle Advanced Security Administrator’s Guide for more
information on setting this parameter
"OS_AUTHENT_PREFIX" on page 1-119
REMOTE_OS_ROLES
Parameter type
Boolean
Default value
false
Parameter class
Static
Range of values
true | false
REMOTE_OS_ROLES specifies whether operating system roles are allowed for
remote clients. The default value, false, causes Oracle to identify and manage
roles for remote clients.
1-140 Oracle9i Database Reference
RESOURCE_LIMIT
See Also:
■
■
Oracle9i Database Administrator’s Guide for more information on
setting this parameter
"OS_ROLES" on page 1-120
REPLICATION_DEPENDENCY_TRACKING
Parameter type
Boolean
Default value
true
Parameter class
Static
Range of values
true | false
REPLICATION_DEPENDENCY_TRACKING enables or disables dependency tracking
for read/write operations to the database. Dependency tracking is essential for
propagating changes in a replicated environment in parallel.
Values:
■
TRUE
Enables dependency tracking.
■
FALSE
Allows read/write operations to the database to run faster, but does not
produce dependency information for Oracle to perform parallel propagation.
Note: Do not specify this value unless you are sure that your
application will not perform any read/write operations to the
replicated tables.
See Also: Oracle9i Replication for more information on parallel
propagation dependency tracking
RESOURCE_LIMIT
Parameter type
Boolean
Initialization Parameters 1-141
RESOURCE_MANAGER_PLAN
Default value
false
Parameter class
Dynamic: ALTER SYSTEM
Range of values
true | false
RESOURCE_LIMIT determines whether resource limits are enforced in database
profiles.
Values:
■
TRUE
Enables the enforcement of resource limits
■
FALSE
Disables the enforcement of resource limits
See Also: Oracle9i Database Administrator’s Guide and Oracle9i SQL
Reference for more information on setting resource limits for profiles
RESOURCE_MANAGER_PLAN
Parameter type
String
Syntax
RESOURCE_MANAGER_PLAN = plan_name
Default value
There is no default value.
Parameter class
Dynamic: ALTER SYSTEM
Range of values
Any valid character string
RESOURCE_MANAGER_PLAN specifies the top-level resource plan to use for an
instance. The resource manager will load this top-level plan along with all its
descendants (subplans, directives, and consumer groups). If you do not specify this
parameter, the resource manager is off by default.
You can change the setting of this parameter using the ALTER SYSTEM statement to
turn on the resource manager (if it was previously off) or to turn off the resource
manager or change the current plan (if it was previously on). If you specify a plan
that does not exist in the data dictionary, Oracle returns an error message.
1-142 Oracle9i Database Reference
ROLLBACK_SEGMENTS
See Also:
■
■
■
Oracle9i Database Administrator’s Guide for information on
resource plans
Oracle9i Supplied PL/SQL Packages and Types Reference for
information on the DBMS_RESOURCE_MANAGER and DBMS_
RESOURCE_MANAGER_PRIVS packages
"DBA_RSRC_PLANS" on page 2-219, "DBA_RSRC_PLAN_
DIRECTIVES" on page 2-218, and the various V$RSRC_ dynamic
performance views in Chapter 3 for information on existing
resource plans
ROLLBACK_SEGMENTS
Parameter type
String
Syntax
ROLLBACK_SEGMENTS =
(segment_name [, segment_name] ... )
Default value
The instance uses public rollback segments by default if you
do not specify this parameter
Parameter class
Static
Range of values
Any rollback segment names listed in DBA_ROLLBACK_
SEGS except SYSTEM
Real Application
Clusters
Multiple instances must have different values.
ROLLBACK_SEGMENTS allocates one or more rollback segments by name to this
instance. If you set this parameter, the instance acquires all of the rollback segments
named in this parameter, even if the number of rollback segments exceeds the
minimum number required by the instance (calculated as TRANSACTIONS /
TRANSACTIONS_PER_ROLLBACK_SEGMENT).
You cannot change the value of this parameter dynamically, but you can change its
value and then restart the instance. Although this parameter usually specifies
private rollback segments, it can also specify public rollback segments if they are
not already in use.
To find the name, segment ID number, and status of each rollback segment in the
database, query the data dictionary view DBA_ROLLBACK_SEGS.
Initialization Parameters 1-143
ROW_LOCKING
When UNDO_MANAGEMENT is set to AUTO, ROLLBACK_SEGMENTS is ignored.
See Also:
Oracle9i Database Administrator’s Guide for more information on
setting this parameter
■
Oracle9i Real Application Clusters Deployment and Performance for
information on setting this parameter in an Oracle9i Real
Application Clusters environment
■
"DBA_ROLLBACK_SEGS" on page 2-215
■
ROW_LOCKING
Parameter type
String
Syntax
ROW_LOCKING = {ALWAYS | DEFAULT | INTENT}
Default value
ALWAYS
Parameter class
Static
Real Application
Clusters
You must set this parameter for every instance, and multiple
instances must have the same value.
ROW_LOCKING specifies whether row locks are acquired during UPDATE operations.
Values:
■
ALWAYS and DEFAULT
Row locks are acquired. Table locks are not acquired.
■
INTENT
In addition to row locks, restricted table-level locks are acquired during
UPDATE operations.
The acquisition of table-level locks is a way to ensure data concurrency. However,
Oracle Corporation recommends that you use the SQL statement LOCK TABLE for
that purpose rather than changing the setting of this parameter from its default
setting of ALWAYS.
1-144 Oracle9i Database Reference
SERIAL _REUSE
SERIAL _REUSE
Parameter type
String
Syntax
SERIAL_REUSE =
{DISABLE | SELECT | DML | PLSQL | ALL}
Default value
DISABLE
Parameter class
Static
SERIAL_REUSE specifies which types of cursors make use of the serial-reusable
memory feature. This feature allocates private cursor memory in the SGA so that it
can be reused (serially, not concurrently) by sessions executing the same cursor.
Values:
■
DISABLE
Disables the option for all SQL statement types. This value overrides any other
values included in the list.
■
SELECT
Enables the option for SELECT statements.
■
DML
Enables the option for DML statements.
■
PLSQL
Currently has no effect (although PLSQL packages do support the serial-reuse
memory option using PLSQL pragmas).
■
ALL
Enables the option for both DML and SELECT statements. Equivalent to setting
SELECT, DML, and PLSQL.
Note: If CURSOR_SPACE_FOR_TIME is set to TRUE, then the value
of SERIAL_REUSE is ignored and treated as if it were set to
DISABLE.
See Also: "CURSOR_SPACE_FOR_TIME" on page 1-31
Initialization Parameters 1-145
SERVICE_NAMES
SERVICE_NAMES
Parameter type
String
Syntax
SERVICE_NAMES =
db_service_name [, db_service_name [,...]
]
Default value
DB_NAME.DB_DOMAIN if defined
Parameter class
Dynamic: ALTER SYSTEM
Range of values
Any ASCII string or comma-separated list of string names
SERVICE_NAMES specifies one or more names for the database service to which this
instance connects. You can specify multiple service names in order to distinguish
among different uses of the same database.
For example:
SERVICE_NAMES = sales.acme.com, widgetsales.acme.com
You can also use service names to identify a single service that is available from two
different databases through the use of replication.
In an Oracle9i Real Application Clusters environment, you must set this parameter
for every instance.
If you do not qualify the names in this parameter with a domain, Oracle qualifies
them with the value of the DB_DOMAIN parameter. If DB_DOMAIN is not specified,
Oracle uses the domain of your local database as it currently exists in the data
dictionary.
See Also:
■
■
Oracle9i Net Services Administrator’s Guide for more information
on this parameter and its settings
"DB_DOMAIN" on page 1-39
SESSION_CACHED_CURSORS
Parameter type
Integer
Default value
0
1-146 Oracle9i Database Reference
SESSION_MAX_OPEN_FILES
Parameter class
Dynamic: ALTER SESSION
Range of values
0 to operating system-dependent
Real Application
Clusters
Multiple instances can have different values.
SESSION_CACHED_CURSORS lets you specify the number of session cursors to
cache. Repeated parse calls of the same SQL statement cause the session cursor for
that statement to be moved into the session cursor cache. Subsequent parse calls
will find the cursor in the cache and do not need to reopen the cursor. Oracle uses a
least recently used algorithm to remove entries in the session cursor cache to make
room for new entries when needed.
See Also: Oracle9i Database Performance Tuning Guide and Reference
for more information on setting this parameter and its uses
SESSION_MAX_OPEN_FILES
Parameter type
Integer
Default value
10
Parameter class
Static
Range of values
1 to either 50 or the value of MAX_OPEN_FILES defined at
the operating system level, whichever is less
SESSION_MAX_OPEN_FILES specifies the maximum number of BFILEs that can be
opened in any session. Once this number is reached, subsequent attempts to open
more files in the session by using DBMS_LOB.FILEOPEN() or
OCILobFileOpen() will fail. The maximum value for this parameter depends on
the equivalent parameter defined for the underlying operating system.
See Also:
■
■
■
Oracle9i Application Developer’s Guide - Large Objects (LOBs) for
information on LOBs in general and BFILEs in particular
Oracle9i Supplied PL/SQL Packages and Types Reference for
information on the DBMS_LOB.FILEOPEN() procedure
Oracle Call Interface Programmer’s Guide for information on the
OCILobFileOpen() procedure
Initialization Parameters 1-147
SESSIONS
SESSIONS
Parameter type
Integer
Default value
Derived: (1.1 * PROCESSES) + 5
Parameter class
Static
Range of values
1 to 231
SESSIONS specifies the maximum number of sessions that can be created in the
system. Because every login requires a session, this parameter effectively
determines the maximum number of concurrent users in the system. You should
always set this parameter explicitly to a value equivalent to your estimate of the
maximum number of concurrent users, plus the number of background processes,
plus approximately 10% for recursive sessions.
Oracle uses the default value of this parameter as its minimum. Values between 1
and the default do not trigger errors, but Oracle ignores them and uses the default
instead.
The default values of the ENQUEUE_RESOURCES and TRANSACTIONS parameters
are derived from SESSIONS. Therefore, if you increase the value of SESSIONS, you
should consider whether to adjust the values of ENQUEUE_RESOURCES and
TRANSACTIONS as well.
In a shared server environment, the value of PROCESSES can be quite small.
Therefore, Oracle Corporation recommends that you adjust the value of SESSIONS
to approximately 1.1 * total number of connections.
See Also:
■
■
Oracle9i Database Concepts for more information on memory
structures and processes
"ENQUEUE_RESOURCES" on page 1-55 and
"TRANSACTIONS" on page 1-165
SGA_MAX_SIZE
Parameter type
Big integer
Syntax
SGA_MAX_SIZE = integer [K | M | G]
1-148 Oracle9i Database Reference
SHARED_MEMORY_ADDRESS
Default value
Initial size of SGA at startup, dependent on the sizes of
different pools in the SGA, such as buffer cache, shared pool,
large pool, and so on.
Parameter class
Static
Range of values
0 to operating system-dependent
SGA_MAX_SIZE specifies the maximum size of SGA for the lifetime of the instance.
SHADOW_CORE_DUMP
Parameter type
String
Syntax
SHADOW_CORE_DUMP = {partial | full | none}
Default value
partial
Parameter class
Static
SHADOW_CORE_DUMP specifies whether Oracle includes the SGA in the core file for
foreground (client) processes.
Values:
■
partial
Oracle does not include the SGA in the core dump.
■
full
Oracle includes the SGA in the core dump.
■
none
No core files will be generated for foreground processes.
See Also: "BACKGROUND_CORE_DUMP" on page 1-18
SHARED_MEMORY_ADDRESS
Parameter type
Integer
Initialization Parameters 1-149
SHARED_POOL_RESERVED_SIZE
Default value
0
Parameter class
Static
SHARED_MEMORY_ADDRESS and HI_SHARED_MEMORY_ADDRESS specify the
starting address at runtime of the system global area (SGA). This parameter is
ignored on the many platforms that specify the SGA’s starting address at linktime.
Use this parameter to specify the entire address on 32-bit platforms and to specify
the low-order 32 bits of a 64-bit address on 64-bit platforms. Use HI_SHARED_
MEMORY_ADDRESS to specify the high-order 32 bits of a 64-bit address on 64-bit
platforms. If both parameters are 0 or unspecified, the SGA address defaults to a
platform-specific location.
See Also: "HI_SHARED_MEMORY_ADDRESS" on page 1-64
SHARED_POOL_RESERVED_SIZE
Parameter type
Big integer
Syntax
SHARED_POOL_RESERVED_SIZE = integer [K | M |
G]
Default value
5% of the value of SHARED_POOL_SIZE
Parameter class
Static
Range of values
Minimum: 5000
Maximum: one half of the value of SHARED_POOL_SIZE
SHARED_POOL_RESERVED_SIZE specifies (in bytes) the shared pool space that is
reserved for large contiguous requests for shared pool memory.
You can use this parameter to avoid performance degradation in the shared pool in
situations where pool fragmentation forces Oracle to search for and free chunks of
unused pool to satisfy the current request.
See Also:
■
■
Oracle9i Database Performance Tuning Guide and Reference for
more information on setting this parameter
"SHARED_POOL_SIZE" on page 1-151
1-150 Oracle9i Database Reference
SHARED_SERVER_SESSIONS
SHARED_POOL_SIZE
Parameter type
Big integer
Syntax
SHARED_POOL_SIZE = integer [K | M | G]
Default value
32-bit platforms: 8 MB, rounded up to the nearest granule
size
64-bit platforms: 64 MB, rounded up to the nearest granule
size
Parameter class
Dynamic: ALTER SYSTEM
Range of values
Minimum: the granule size
Maximum: operating system-dependent
SHARED_POOL_SIZE specifies (in bytes) the size of the shared pool. The shared
pool contains shared cursors, stored procedures, control structures, and other
structures. If you set PARALLEL_AUTOMATIC_TUNING to false, then Oracle also
allocates parallel execution message buffers from the shared pool. Larger values
improve performance in multi-user systems. Smaller values use less memory.
You can monitor utilization of the shared pool by querying the view V$SGASTAT.
See Also:
■
■
■
Oracle9i Database Performance Tuning Guide and Reference for
more information on setting this parameter
Oracle9i Database Migration for information on parallel
execution message buffers
"PARALLEL_AUTOMATIC_TUNING" on page 1-121 and
"V$SGASTAT" on page 3-141
SHARED_SERVER_SESSIONS
Parameter type
Integer
Default value
Derived: the lesser of CIRCUITS and SESSIONS - 5
Parameter class
Static
Range of values
0 to SESSIONS - 5
Initialization Parameters 1-151
SHARED_SERVERS
SHARED_SERVER_SESSIONS specifies the total number of shared server
architecture user sessions to allow. Setting this parameter enables you to reserve
user sessions for dedicated servers.
See Also: Oracle9i Database Concepts for more information on
memory structures and processes
SHARED_SERVERS
Parameter type
Integer
Default value
If you are using shared server architecture, then the value is
1.
If you are not using shared server architecture, then the
value is 0.
Parameter class
Dynamic: ALTER SYSTEM
Range of values
Operating system-dependent
SHARED_SERVERS specifies the number of server processes that you want to create
when an instance is started up. If system load decreases, this minimum number of
servers is maintained. Therefore, you should take care not to set SHARED_SERVERS
too high at system startup.
See Also: Oracle9i Database Performance Tuning Guide and Reference
for more information on setting this parameter
SORT_AREA_RETAINED_SIZE
Parameter type
Integer
Default value
Derived from SORT_AREA_SIZE
Parameter class
Dynamic: ALTER SESSION, ALTER SYSTEM ...
DEFERRED
Range of values
From the value equivalent of two database blocks to the
value of SORT_AREA_SIZE
1-152 Oracle9i Database Reference
SORT_AREA_SIZE
Note: Oracle does not recommend using the SORT_AREA_
RETAINED_SIZE parameter unless the instance is configured with
the shared server option. Oracle recommends that you enable
automatic sizing of SQL working areas by setting PGA_
AGGREGATE_TARGET instead. SORT_AREA_RETAINED_SIZE is
retained for backward compatibility.
SORT_AREA_RETAINED_SIZE specifies (in bytes) the maximum amount of the
user global area (UGA) memory retained after a sort run completes. The retained
size controls the size of the read buffer, which Oracle uses to maintain a portion of
the sort in memory. This memory is released back to the UGA, not to the operating
system, after the last row is fetched from the sort space.
Oracle may allocate multiple sort spaces of this size for each query. Usually, only
one or two sorts occur at one time, even for complex queries. In some cases,
however, additional concurrent sorts are required, and each sort keeps its own
memory area. If the shared server is used, allocation is to the SGA until the value in
SORT_AREA_RETAINED_SIZE is reached. The difference between SORT_AREA_
RETAINED_SIZE and SORT_AREA_SIZE is allocated to the PGA.
Note: The default value as reflected in the V$PARAMETER
dynamic performance view is 0. However, if you do not explicitly
set this parameter, Oracle actually uses the value of the SORT_
AREA_SIZE parameter.
See Also:
■
■
Oracle9i Database Performance Tuning Guide and Reference for
more information on setting this parameter
"SORT_AREA_SIZE" on page 1-153
SORT_AREA_SIZE
Parameter type
Integer
Default value
65536
Initialization Parameters 1-153
SORT_AREA_SIZE
Parameter class
Dynamic: ALTER SESSION, ALTER SYSTEM ...
DEFERRED
Range of values
Minimum: the value equivalent of six database blocks
Maximum: operating system-dependent
Note: Oracle does not recommend using the SORT_AREA_SIZE
parameter unless the instance is configured with the shared server
option. Oracle recommends that you enable automatic sizing of
SQL working areas by setting PGA_AGGREGATE_TARGET instead.
SORT_AREA_SIZE is retained for backward compatibility.
SORT_AREA_SIZE specifies in bytes the maximum amount of memory Oracle will
use for a sort. After the sort is complete, but before the rows are returned, Oracle
releases all of the memory allocated for the sort, except the amount specified by the
SORT_AREA_RETAINED_SIZE parameter. After the last row is returned, Oracle
releases the remainder of the memory.
Increasing SORT_AREA_SIZE size improves the efficiency of large sorts. Multiple
allocations never occur. Only one memory area of SORT_AREA_SIZE exists for each
user process at any time.
SORT_AREA_SIZE is also used for inserts and updates to bitmap indexes. Setting
this value appropriately results in a bitmap segment being updated only once for
each DML operation, even if more than one row in that segment changes.
Larger values of SORT_AREA_SIZE permit more sorts to be performed in memory.
If more space is required to complete the sort than will fit into the memory
provided, then temporary segments on disk are used to hold the intermediate sort
runs.
The default is adequate for most OLTP operations. You might want to adjust this
parameter for decision support systems, batch jobs, or large CREATE INDEX
operations.
1-154 Oracle9i Database Reference
SPFILE
See Also:
■
■
■
■
Oracle9i Database Performance Tuning Guide and Reference for
more information on setting this parameter
Oracle9i Database Concepts for information on logical storage
structures such as sort areas
Your operating system-specific Oracle documentation for the
default value on your system
"SORT_AREA_RETAINED_SIZE" on page 1-152
SPFILE
Parameter type
String
Syntax
SPFILE = spfile_name
Default value
ORACLE_HOME/dbs/spfile.ora
Parameter class
Static
Range of values
Any valid SPFILE
Real Application
Clusters
Multiple instances should have the same value.
The value of this parameter is the name of the current server parameter file
(SPFILE) in use. This parameter can be defined in a client side PFILE to indicate the
name of the server parameter file to use.
When the default server parameter file is used by the server, the value of SPFILE is
internally set by the server.
The SPFILE resides in the ORACLE_HOME/dbs directory; however, users can place
it anywhere on their machine as long as it is specified in an initialization parameter
file.
See Also: Oracle9i Database Administrator’s Guide for more
information about creating the server parameter file
Initialization Parameters 1-155
SQL_TRACE
SQL_TRACE
Parameter type
Boolean
Default value
false
Parameter class
Static
Range of values
true | false
The value of SQL_TRACE disables or enables the SQL trace facility. Setting this
parameter to true provides information on tuning that you can use to improve
performance. You can change the value using the DBMS_SYSTEM package.
Caution: Using this initialization parameter to enable the SQL
trace facility for the entire instance can have a severe performance
impact. Enable the facility for specific sessions using the ALTER
SESSION statement. If you must enable the facility on an entire
production environment, you can minimize performance impact
by:
■
■
■
Maintaining at least 25% idle CPU capacity
Maintaining adequate disk space for the USER_DUMP_DEST
location
Striping disk space over sufficient disks
Note: If you change the value of this parameter by using the
ALTER SESSION SET SQL_TRACE statement, the resulting
change will not be reflected in the V$PARAMETER dynamic
performance view. Therefore, this parameter is not considered
dynamic. For information on the ALTER SESSION statement, see
Oracle9i SQL Reference.
See Also: Oracle9i Database Performance Tuning Guide and
Referencefor more information about performance diagnostic tools
1-156 Oracle9i Database Reference
STANDBY_ARCHIVE_DEST
SQL92_SECURITY
Parameter type
Boolean
Default value
false
Parameter class
Static
Range of values
true | false
The SQL92 standards specify that security administrators should be able to require
that users have SELECT privilege on a table when executing an UPDATE or DELETE
statement that references table column values in a WHERE or SET clause. SQL92_
SECURITY lets you specify whether users must have been granted the SELECT
object privilege in order to execute such UPDATE or DELETE statements.
STANDBY_ARCHIVE_DEST
Parameter type
String
Syntax
STANDBY_ARCHIVE_DEST = filespec
Default value
Operating system-specific
Parameter class
Dynamic: ALTER SYSTEM
Range of values
A valid path or device name other than RAW
STANDBY_ARCHIVE_DEST is relevant only for a standby database in managed
recovery mode. It specifies the location of archive logs arriving from a primary
database. Oracle uses STANDBY_ARCHIVE_DEST and LOG_ARCHIVE_FORMAT to
fabricate the fully qualified standby log filenames and stores the filenames in the
standby control file.
You can see the value of this parameter by querying the V$ARCHIVE_DEST data
dictionary view.
Initialization Parameters 1-157
STANDBY_FILE_MANAGEMENT
See Also:
Oracle9i Data Guard Concepts and Administration for more
information on setting this parameter and on managed
recovery mode in general
■
"LOG_ARCHIVE_DEST" on page 1-75 and "V$ARCHIVE_
DEST" on page 3-5
■
STANDBY_FILE_MANAGEMENT
Parameter type
String
Syntax
STANDBY_FILE_MANAGEMENT = {MANUAL | AUTO}
Default value
MANUAL
Parameter class
Dynamic: ALTER SYSTEM
STANDBY_FILE_MANAGEMENT enables or disables automatic standby file
management. When automatic standby file management is enabled, operating
system file additions and deletions on the primary database are replicated on the
standby database.
Values:
■
MANUAL
disables automatic standby file management
■
AUTO
enables automatic standby file management
Setting STANDBY_FILE_MANAGEMENT to AUTO causes Oracle to automatically
create files on the standby database and, in some cases, overwrite existing files. Care
must be taken when setting STANDBY_FILE_MANAGEMENT and DB_FILE_NAME_
CONVERT so that existing standby files will not be accidentally overwritten.
If the standby database is on the same system as the primary database, then ensure
that the primary and standby systems do not point to the same files.
See Also: Oracle9i Data Guard Concepts and Administration for
more information about setting this parameter
1-158 Oracle9i Database Reference
STATISTICS_LEVEL
STAR_TRANSFORMATION_ENABLED
Parameter type
String
Syntax
STAR_TRANSFORMATION_ENABLED =
{TEMP_DISABLE | TRUE | FALSE}
Default value
FALSE
Parameter class
Dynamic: ALTER SESSION
STAR_TRANSFORMATION_ENABLED determines whether a cost-based query
transformation will be applied to star queries.
Values:
■
TRUE
The optimizer will consider performing a cost-based query transformation on
the star query.
■
FALSE
The transformation will not be applied.
■
TEMP_DISABLE
The optimizer will consider performing a cost-based query transformation on
the star query but will not use temporary tables in the star transformation.
See Also:
■
■
Oracle9i Database Concepts for information on star queries
Oracle9i Database Performance Tuning Guide and Reference for
information on enabling star query
STATISTICS_LEVEL
Parameter type
String
Syntax
STATISTICS_LEVEL = {ALL | TYPICAL | BASIC}
Default value
TYPICAL
Parameter class
Dynamic: ALTER SESSION, ALTER SYSTEM
Initialization Parameters 1-159
TAPE_ASYNCH_IO
STATISTICS_LEVEL sets the statistics collection level of the database.
TAPE_ASYNCH_IO
Parameter type
Boolean
Default value
true
Parameter class
Static
Range of values
true | false
TAPE_ASYNCH_IO controls whether I/O to sequential devices (for example, backup
or restore of Oracle data to or from tape) is asynchronous—that is, whether parallel
server processes can overlap I/O requests with CPU processing during table scans.
If your platform supports asynchronous I/O to sequential devices, Oracle
Corporation recommends that you leave this parameter set to its default. However,
if the asynchronous I/O implementation is not stable, you can set TAPE_ASYNCH_
IO to false to disable asynchronous I/O. If your platform does not support
asynchronous I/O to sequential devices, this parameter has no effect.
See Also: Oracle9i Database Performance Tuning Guide and Reference
for more information on asynchronous I/O and on setting this
parameter
THREAD
Parameter type
Integer
Default value
0
Parameter class
Static
Range of values
0 to the maximum number of enabled threads
Real Application
Clusters
If specified, multiple instances must have different values.
THREAD is an Oracle9i Real Application Clusters parameter that specifies the
number of the redo thread to be used by an instance.
1-160 Oracle9i Database Reference
TIMED_OS_STATISTICS
When you create a database, Oracle creates and enables thread 1 as a public thread
(one that can be used by any instance). You must create and enable subsequent
threads using the ADD LOGFILE THREAD clause and ENABLE THREAD clause of
the ALTER DATABASE statement. The number of threads you create is limited by
the MAXINSTANCES parameter specified in the CREATE DATABASE statement.
In exclusive mode, thread 1 is the default thread. However, you can specify THREAD
for an instance running in exclusive mode if you want to use the redo log files in a
thread other than thread 1.
In parallel mode, you can specify any available redo thread number, as long as that
thread number is enabled and is not in use by another instance.
A value of zero specifies that this instance can use any available, enabled public
thread.
See Also: Oracle9i Real Application Clusters Administration and
Oracle9i SQL Reference
TIMED_OS_STATISTICS
Parameter type
Integer
Default value
If STATISTICS_LEVEL is set to ALL, then 5
If STATISTICS_LEVEL is set to BASIC or TYPICAL, then 0
Parameter class
Dynamic: ALTER SESSION, ALTER SYSTEM
Range of values
Unlimited
TIMED_OS_STATISTICS specifies the interval (in seconds) at which Oracle collects
operating system statistics when a request is made from the client to the server or
when a request completes.
■
■
On dedicated servers, Oracle collects operating system statistics at user logon
and after each subsequent client invocation through the OCI into the Oracle
server as a remote procedure call message.
On shared servers, Oracle collects statistics when client calls to Oracle are
processed.
A value of zero specifies that operating system statistics are not gathered. To collect
statistics, set a value meaningful for your application and site needs.
Initialization Parameters 1-161
TIMED_STATISTICS
Note: Gathering operating system statistics is very expensive.
Oracle Corporation recommends that you set this parameter in an
ALTER SYSTEM statement rather than in the initialization
parameter file, and that you reset the value to zero as soon as the
needed statistics have been gathered.
TIMED_STATISTICS
Parameter type
Boolean
Default value
If STATISTICS_LEVEL is set to TYPICAL or ALL, then true
If STATISTICS_LEVEL is set to BASIC, then false
Parameter class
Dynamic: ALTER SESSION, ALTER SYSTEM
Range of values
true | false
TIMED_STATISTICS specifies whether or not statistics related to time are collected.
Values:
■
true
The statistics are collected and stored in trace files or displayed in the
V$SESSTATS and V$SYSSTATS dynamic performance views.
■
false
The value of all time-related statistics is set to zero. This setting lets Oracle
avoid the overhead of requesting the time from the operating system. Normally,
TIMED_STATISTICS should be false.
On some systems with very fast timer access, Oracle might enable timing even if
this parameter is set to false. On these systems, setting the parameter to true can
sometimes produce more accurate statistics for long-running operations.
See Also:
■
■
Oracle9i Database Performance Tuning Guide and Reference for
more information on setting this parameter and on
performance diagnostic tools in general
Appendix C, "Statistics Descriptions" indicates which statistics
depend on the setting of this parameter.
1-162 Oracle9i Database Reference
TRACEFILE_IDENTIFIER
TRACE_ENABLED
Parameter type
Boolean
Default value
true
Parameter class
Dynamic: ALTER SYSTEM
Range of values
true | false
Real Application
Clusters
You must set this parameter for every instance, and multiple
instances must have the same value.
TRACE_ENABLED controls tracing of the execution history, or code path, of Oracle.
Oracle Support Services uses this information for debugging.
When TRACE_ENABLED is set to true, Oracle records information in specific files
when errors occur. See Oracle9i Real Application Clusters Deployment and Performance
for the types of files and the default destination directories in which Oracle records
the execution history.
Oracle records this information for all instances, even if only one instance
terminates. This allows Oracle to retain diagnostics for the entire cluster.
Although the overhead incurred from this processing is not excessive, you can
improve performance by setting TRACE_ENABLED to false. You might do this, for
example, to meet high-end benchmark requirements. However, if you leave this
parameter set to false, you may lose valuable diagnostic information. Therefore,
always set TRACE_ENABLED to true to trace system problems and to reduce
diagnostic efforts in the event of unexplained instance failures.
TRACEFILE_IDENTIFIER
Parameter type
String
Syntax
TRACEFILE_IDENTIFIER = "traceid"
Default value
There is no default value.
Parameter class
Dynamic: ALTER SESSION
Range of values
Any characters that can occur as part of a file name on the
customer platform
Initialization Parameters 1-163
TRANSACTION_AUDITING
TRACEFILE_IDENTIFIER specifies a custom identifier that becomes part of the
Oracle Trace file name. Such a custom identifier is used to identify a trace file
simply from its name and without having to open it or view its contents.
Each time this parameter is dynamically modified, the next trace dump will be
written to a trace file which has the new parameter value embedded in its name.
Trace file continuity information is automatically added to both the old and new
trace files to indicate that these trace files belong to the same process.
This parameter can only be used to change the name of the foreground process’
trace file; the background processes continue to have their trace files named in the
regular format. For foreground processes, the TRACEID column of the V$PROCESS
view contains the current value of the TRACEFILE_IDENTIFIER parameter. When
this parameter value is set, the trace file name has the following format:
sid_ora_pid_traceid.trc
In this example, sid is the oracle instance ID, pid is the process ID, and traceid
is the value of the TRACEFILE_IDENTIFIER parameter.
See Also: This parameter is not supported on all operating
systems. See your operating system-specific Oracle documentation
for more information.
TRANSACTION_AUDITING
Parameter type
Boolean
Default value
true
Parameter class
Dynamic: ALTER SYSTEM ... DEFERRED
Range of values
true | false
If TRANSACTION_AUDITING is true, Oracle generates a special redo record that
contains the user logon name, username, the session ID, some operating system
information, and client information. For each successive transaction, Oracle
generates a record that contains only the session ID. These subsequent records link
back to the first record, which also contains the session ID.
These records might be useful if you are using a redo log analysis tool. You can
access the records by dumping the redo log.
If TRANSACTION_AUDITING is false, no redo record will be generated.
1-164 Oracle9i Database Reference
TRANSACTIONS_PER_ROLLBACK_SEGMENT
TRANSACTIONS
Parameter type
Integer
Default value
Derived: (1.1 * SESSIONS)
Parameter class
Static
Range of values
4 to 232
Real Application
Clusters
Multiple instances can have different values.
TRANSACTIONS specifies the maximum number of concurrent transactions. Greater
values increase the size of the SGA and can increase the number of rollback
segments allocated. The default value is greater than SESSIONS (and, in turn,
PROCESSES) to allow for recursive transactions.
See Also:
■
■
Oracle9i Database Administrator’s Guide for information on
setting this parameter
Oracle9i Real Application Clusters Administration for the
relationship of this parameter to the number of rollback
segments
TRANSACTIONS_PER_ROLLBACK_SEGMENT
Parameter type
Integer
Default value
5
Parameter class
Static
Range of values
1 to operating system-dependent
Real Application
Clusters
Multiple instances can have different values.
TRANSACTIONS_PER_ROLLBACK_SEGMENT specifies the number of concurrent
transactions you expect each rollback segment to have to handle. The minimum
number of rollback segments acquired at startup is TRANSACTIONS divided by the
value for this parameter. For example, if TRANSACTIONS is 101 and this parameter
Initialization Parameters 1-165
UNDO_MANAGEMENT
is 10, then the minimum number of rollback segments acquired would be the ratio
101/10, rounded up to 11.
You can acquire more rollback segments by naming them in the parameter
ROLLBACK_SEGMENTS.
See Also:
■
■
■
Oracle9i Database Administrator’s Guide for information on
setting this parameter.
Oracle9i Real Application Clusters Administration for how Oracle
acquires rollback segments.
Your operating system-specific Oracle documentation for the
range of values for this parameter.
UNDO_MANAGEMENT
Parameter type
String
Syntax
UNDO_MANAGEMENT = {MANUAL | AUTO}
Default value
MANUAL
Parameter class
Static
Real Application
Clusters
Multiple instances must have the same value.
UNDO_MANAGEMENT specifies which undo space management mode the system
should use. When set to AUTO, the instance starts in automatic undo management
mode. In manual undo management mode, undo space is allocated externally as
rollback segments.
UNDO_RETENTION
Parameter type
Integer
Default value
900
Parameter class
Dynamic: ALTER SYSTEM
1-166 Oracle9i Database Reference
UNDO_SUPPRESS_ERRORS
Range of values
0 to 232-1 (max value represented by 32 bits)
Real Application
Clusters
Multiple instances must have the same value.
UNDO_RETENTION specifies (in seconds) the amount of committed undo
information to retain in the database. You can use UNDO_RETENTION to satisfy
queries that require old undo information to rollback changes to produce older
images of data blocks. You can set the value at instance startup.
The UNDO_RETENTION parameter works best if the current undo tablespace has
enough space for the active transactions. If an active transaction needs undo space
and the undo tablespace does not have any free space, then the system will start
reusing undo space that would have been retained. This may cause long queries to
fail. Be sure to allocate enough space in the undo tablespace to satisfy the space
requirement for the current setting of this parameter.
See Also: Oracle9i SQL Reference for more information about
creating undo tablespaces
UNDO_SUPPRESS_ERRORS
Parameter type
Boolean
Default value
false
Parameter class
Dynamic: ALTER SESSION, ALTER SYSTEM
Range of values
true | false
UNDO_SUPPRESS_ERRORS enables users to suppress errors while executing manual
undo management mode operations (for example, ALTER ROLLBACK SEGMENT
ONLINE) in automatic undo management mode. Setting this parameter enables
users to use the undo tablespace feature before all application programs and scripts
are converted to automatic undo management mode. For example, if you have a
tool that uses SET TRANSACTION USE ROLLBACK SEGMENT statement, you can
add the statement "ALTER SESSION SET UNDO_SUPPRESS_ERRORS = true" to
the tool to suppress the ORA-30019 error.
If you want to run in automatic undo management mode, ensure that your tools or
applications are updated to run in automatic undo management mode.
Initialization Parameters 1-167
UNDO_TABLESPACE
UNDO_TABLESPACE
Parameter type
String
Syntax
UNDO_TABLESPACE = undoname
Default value
The first available undo tablespace in the database.
Parameter class
Dynamic: ALTER SYSTEM
Range of values
Legal name of an existing undo tablespace
Real Application
Clusters
Multiple instances can have different values.
UNDO_TABLESPACE specifies the undo tablespace to be used when an instance
starts up. If this parameter is specified when the instance is in manual undo
management mode, an error will occur and startup will fail.
If the UNDO_TABLESPACE parameter is omitted, the first available undo tablespace
in the database is chosen. If no undo tablespace is available, the instance will start
without an undo tablespace. In such cases, user transactions will be executed using
the SYSTEM rollback segment. You should avoid running in this mode under
normal circumstances.
You can replace an undo tablespace with another undo tablespace while the
instance is running.
See Also: Oracle9i SQL Reference.
USE_INDIRECT_DATA_BUFFERS
Parameter type
Boolean
Default value
false
Parameter class
Static
Range of values
true | false
USE_INDIRECT_DATA_BUFFERS controls how the system global area (SGA) uses
memory. It enables or disables the use of the extended buffer cache mechanism for
32-bit platforms that can support more than 4 GB of physical memory. On platforms
that do not support this much physical memory, this parameter is ignored.
1-168 Oracle9i Database Reference
UTL_FILE_DIR
See Also:
■
■
"LOCK_SGA" on page 1-74, "SHARED_MEMORY_ADDRESS"
on page 1-149, and "HI_SHARED_MEMORY_ADDRESS" on
page 1-64, which are other parameters that control how the
SGA uses memory.
Oracle9i Database Concepts for more information about the SGA.
USER_DUMP_DEST
Parameter type
String
Syntax
USER_DUMP_DEST = {pathname | directory}
Default value
Operating system-dependent
Parameter class
Dynamic: ALTER SYSTEM
Range of values
Any valid local path, directory, or disk
USER_DUMP_DEST specifies the pathname for a directory where the server will
write debugging trace files on behalf of a user process.
For example, this directory might be set as follows:
■
On MS-DOS: C:\ORACLE\UTRC
■
On UNIX: /oracle/utrc
■
On VMS: DISK$UR3:[ORACLE.UTRC]
See Also:
■
■
Oracle9i Database Performance Tuning Guide and Reference for
more information about the use of trace files
Your operating system-specific Oracle documentation for the
range of values
UTL_FILE_DIR
Parameter type
String
Syntax
UTL_FILE_DIR = pathname
Initialization Parameters 1-169
WORKAREA_SIZE_POLICY
Default value
There is no default value.
Parameter class
Static
Range of values
Any valid directory path
UTL_FILE_DIR lets you specify one or more directories that Oracle should use for
PL/SQL file I/O. If you are specifying multiple directories, you must repeat the
UTL_FILE_DIR parameter for each directory on separate lines of the initialization
parameter file.
All users can read or write to all files specified by this parameter. Therefore all
PL/SQL users must be trusted with the information in the directories specified by
this parameter.
Note: If you list multiple values, all entries of this parameter must
be on contiguous lines of the parameter file. If you separate them
with other parameters, Oracle will read only the last (contiguous)
lines.
WORKAREA_SIZE_POLICY
Parameter type
String
Syntax
WORKAREA_SIZE_POLICY = {AUTO | MANUAL}
Default value
If PGA_AGGREGATE_TARGET is set, then AUTO
If PGA_AGGREGATE_TARGET is not set, then MANUAL
Parameter class
Dynamic: ALTER SESSION, ALTER SYSTEM
WORKAREA_SIZE_POLICY specifies the policy for sizing work areas. This
parameter controls the mode in which working areas are tuned.
Values:
■
AUTO
Work areas used by memory-intensive operators are sized automatically, based
on the PGA memory used by the system, the target PGA memory set in PGA_
AGGREGATE_TARGET, and the requirement of each individual operator. You can
specify AUTO only when PGA_AGGREGATE_TARGET is defined.
■
MANUAL
1-170 Oracle9i Database Reference
WORKAREA_SIZE_POLICY
The sizing of work areas is manual and based on the values of the *_AREA_
SIZE parameter corresponding to the operation (for example, a sort uses SORT_
AREA_SIZE). Specifying MANUAL may result in sub-optimal performance and
poor PGA memory utilization.
Initialization Parameters 1-171
WORKAREA_SIZE_POLICY
1-172 Oracle9i Database Reference
2
Static Data Dictionary Views
This chapter describes data dictionary tables and views. These tables and views are
called static, because they change only when a change is made to the data
dictionary (for example, when a new table is created or a user is granted new
privileges). Oracle also maintains tables that monitor ongoing database activity.
These dynamic performance tables are described in Chapter 3, "Dynamic
Performance (V$) Views".
Data dictionary tables are not directly accessible, but you can access information in
them through data dictionary views. To list the data dictionary views available to
you, query the view DICTIONARY.
Many data dictionary tables have three corresponding views:
■
■
■
An ALL_ view displays all the information accessible to the current user,
including information from the current user’s schema as well as information
from objects in other schemas, if the current user has access to those objects by
way of grants of privileges or roles.
A DBA_ view displays all relevant information in the entire database. DBA_
views are intended only for administrators. They can be accessed only by users
with the SELECT_ANY_TABLE privilege. (This privilege is assigned to the DBA
role when the system is initially installed.)
A USER_ view displays all the information from the schema of the current user.
No special privileges are required to query these views.
The columns of the ALL_, DBA_, and USER_ views corresponding to a single data
dictionary table are usually nearly identical. Therefore, these views are described in
full only once in this chapter, at their first occurrence alphabetically, and are listed
without full descriptions at their other occurrences.
Static Data Dictionary Views 2-1
A number of data dictionary views are relevant only if you are using Oracle
Replication. Table 2–1 lists these views.
Table 2–1
Oracle Replication Data Dictionary Views
ALL_ Views
DBA_ Views
USER_ Views
ALL_REPAUDIT_ATTRIBUTE
DBA_REPAUDIT_ATTRIBUTE
USER_REPAUDIT_ATTRIBUTE
ALL_REPAUDIT_COLUMN
DBA_REPAUDIT_COLUMN
USER_REPAUDIT_COLUMN
ALL_REPCAT
DBA_REPCAT
USER_REPCAT
DBA_REPCAT_EXCEPTIONS
ALL_REPCAT_REFRESH_TEMPLATES
DBA_REPCAT_REFRESH_TEMPLATES
USER_REPCAT_REFRESH_TEMPLATES
ALL_REPCAT_TEMPLATE_OBJECTS
DBA_REPCAT_TEMPLATE_OBJECTS
USER_REPCAT_TEMPLATE_OBJECTS
ALL_REPCAT_TEMPLATE_PARMS
DBA_REPCAT_TEMPLATE_PARMS
USER_REPCAT_TEMPLATE_PARMS
ALL_REPCAT_TEMPLATE_SITES
DBA_REPCAT_TEMPLATE_SITES
USER_REPCAT_TEMPLATE_SITES
ALL_REPCAT_USER_
AUTHORIZATIONS
DBA_REPCAT_USER_
AUTHORIZATIONS
USER_REPCAT_USER_
AUTHORIZATIONS
ALL_REPCAT_USER_PARM_VALUES
DBA_REPCAT_USER_PARM_VALUES
USER_REPCAT_USER_PARM_VALUES
ALL_REPCATLOG
DBA_REPCATLOG
USER_REPCATLOG
ALL_REPCOLUMN
DBA_REPCOLUMN
USER_REPCOLUMN
ALL_REPCOLUMN_GROUP
DBA_REPCOLUMN_GROUP
USER_REPCOLUMN_GROUP
ALL_REPCONFLICT
DBA_REPCONFLICT
USER_REPCONFLICT
ALL_REPDDL
DBA_REPDDL
USER_REPDDL
DBA_REPEXTENSIONS
ALL_REPFLAVOR_COLUMNS
DBA_REPFLAVOR_COLUMNS
USER_REPFLAVOR_COLUMNS
ALL_REPFLAVOR_OBJECTS
DBA_REPFLAVOR_OBJECTS
USER_REPFLAVOR_OBJECTS
ALL_REPFLAVORS
DBA_REPFLAVORS
USER_REPFLAVORS
ALL_REPGENERATED
DBA_REPGENERATED
USER_REPGENERATED
ALL_REPGENOBJECTS
DBA_REPGENOBJECTS
USER_REPGENOBJECTS
ALL_REPGROUP
DBA_REPGROUP
USER_REPGROUP
ALL_REPGROUP_PRIVILEGES
DBA_REPGROUP_PRIVILEGES
USER_REPGROUP_PRIVILEGES
ALL_REPGROUPED_COLUMN
DBA_REPGROUPED_COLUMN
USER_REPGROUPED_COLUMN
ALL_REPKEY_COLUMNS
DBA_REPKEY_COLUMNS
USER_REPKEY_COLUMNS
ALL_REPOBJECT
DBA_REPOBJECT
USER_REPOBJECT
ALL_REPPARAMETER_COLUMN
DBA_REPPARAMETER_COLUMN
USER_REPPARAMETER_COLUMN
ALL_REPPRIORITY
DBA_REPPRIORITY
USER_REPPRIORITY
2-2 Oracle9i Database Reference
Table 2–1 (Cont.) Oracle Replication Data Dictionary Views
ALL_ Views
DBA_ Views
USER_ Views
ALL_REPPRIORITY_GROUP
DBA_REPPRIORITY_GROUP
USER_REPPRIORITY_GROUP
ALL_REPPROP
DBA_REPPROP
USER_REPPROP
ALL_REPRESOL_STATS_CONTROL
DBA_REPRESOL_STATS_CONTROL
USER_REPRESOL_STATS_CONTROL
ALL_REPRESOLUTION
DBA_REPRESOLUTION
USER_REPRESOLUTION
ALL_REPRESOLUTION_METHOD
DBA_REPRESOLUTION_METHOD
USER_REPRESOLUTION_METHOD
ALL_REPRESOLUTION_STATISTICS
DBA_REPRESOLUTION_STATISTICS
USER_REPRESOLUTION_STATISTICS
ALL_REPSCHEMA
DBA_REPSCHEMA
USER_REPSCHEMA
ALL_REPSITES
DBA_REPSITES
USER_REPSITES
DBA_REPSITES_NEW
The following are additional Oracle Replication data dictionary views:
DEFCALL
DEFCALLDEST
DEFDEFAULTDEST
DEFERRCOUNT
DEFERROR
DEFLOB
DEFPROPAGATOR
DEFSCHEDULE
DEFTRAN
DEFTRANDEST
See Also: Oracle9i Replication Management API Reference for
information about these views
A number of data dictionary views are relevant only if you are using Oracle
Workspace Manager. Table 2–2 lists these views.
Table 2–2
Oracle Workspace Manager Data Dictionary Views
ALL_ Views
DBA_ Views
USER_ Views
ALL_VERSION_HVIEW
ALL_WM_LOCKED_TABLES
USER_WM_LOCKED_TABLES
ALL_WM_MODIFIED_TABLES
USER_WM_MODIFIED_TABLES
USER_WM_PRIVS
ALL_WM_RIC_INFO
USER_WM_RIC_INFO
ALL_WM_TAB_TRIGGERS
USER_WM_TAB_TRIGGERS
Static Data Dictionary Views 2-3
Table 2–2 (Cont.) Oracle Workspace Manager Data Dictionary Views
ALL_ Views
DBA_ Views
USER_ Views
ALL_WM_VERSIONED_TABLES
USER_WM_VERSIONED_TABLES
ALL_WM_VT_ERRORS
USER_WM_VT_ERRORS
ALL_WORKSPACE_PRIVS
USER_WORKSPACE_PRIVS
ALL_WORKSPACE_SAVEPOINTS
USER_WORKSPACE_SAVEPOINTS
DBA_WORKSPACE_SESSIONS
ALL_WORKSPACES
USER_WORKSPACES
The following are additional Oracle Workspace Manager data dictionary views:
ROLE_WM_PRIVS
WM_INSTALLATION
WM_REPLICATION_INFO
See Also: Oracle9i Application Developer’s Guide - Workspace
Manager for information about these views
The following data dictionary views are only available after you create an optional
recovery catalog (which contains schemas containing information about backups)
for use with Recovery Manager:
RC_ARCHIVED_LOG
RC_BACKUP_CONTROLFILE
RC_BACKUP_CORRUPTION
RC_BACKUP_DATAFILE
RC_BACKUP_PIECE
RC_BACKUP_REDOLOG
RC_BACKUP_SET
RC_BACKUP_SPFILE
RC_CHECKPOINT
RC_CONTROLFILE_COPY
RC_COPY_CORRUPTION
RC_DATABASE
RC_DATABASE_BLOCK_CORRUPTION
RC_DATABASE_INCARNATION
RC_DATAFILE
RC_DATAFILE_COPY
RC_LOG_HISTORY
RC_OFFLINE_RANGE
RC_PROXY_CONTROLFILE
RC_PROXY_DATAFILE
RC_REDO_LOG
RC_REDO_THREAD
RC_RESYNC
RC_RMAN_CONFIGURATION
2-4 Oracle9i Database Reference
RC_STORED_SCRIPT
RC_STORED_SCRIPT_LINE
RC_TABLESPACE
See Also: Oracle9i Recovery Manager Reference for information
about these views
The remainder of this chapter lists the data dictionary views in alphabetical order.
Static Data Dictionary Views 2-5
ALL_ALL_TABLES
ALL_ALL_TABLES
ALL_ALL_TABLES describes all object tables and relational tables accessible to the
current user.
Related Views
■
■
DBA_ALL_TABLES describes all object tables and relational tables in the
database.
USER_ALL_TABLES describes all object tables and relational tables owned by
the current user. This view does not display the OWNER column.
Column
Datatype
OWNER
VARCHAR2(30)
Owner of the table
TABLE_NAME
VARCHAR2(30)
Name of the table
TABLESPACE_NAME
VARCHAR2(30)
Name of the tablespace containing the table
CLUSTER_NAME
VARCHAR2(30)
Name of the cluster, if any, to which the table belongs
IOT_NAME
VARCHAR2(30)
Name of the index-organized table, if any, to which
the overflow entry belongs
PCT_FREE
NUMBER
Minimum percentage of free space in a block
PCT_USED
NUMBER
Minimum percentage of used space in a block
INI_TRANS
NUMBER
Initial number of transactions
MAX_TRANS
NUMBER
Maximum number of transactions
INITIAL_EXTENT
NUMBER
Size of the initial extent in bytes
NEXT_EXTENT
NUMBER
Size of secondary extents in bytes
MIN_EXTENTS
NUMBER
Minimum number of extents allowed in the segment
MAX_EXTENTS
NUMBER
Maximum number of extents allowed in the segment
PCT_INCREASE
NUMBER
Percentage increase in extent size
FREELISTS
NUMBER
Number of process freelists allocated in this segment
FREELIST_GROUPS
NUMBER
Number of freelist groups allocated in this segment
LOGGING
VARCHAR2(3)
Logging attribute
BACKED_UP
VARCHAR2(1)
Whether the table has been backed up since the last
modification
NUM_ROWS
NUMBER
Number of rows in the table
BLOCKS
NUMBER
Number of used blocks in the table
EMPTY_BLOCKS
NUMBER
Number of empty (never used) blocks in the table
2-6 Oracle9i Database Reference
NULL
Description
ALL_ALL_TABLES
Column
Datatype
NULL
Description
AVG_SPACE
NUMBER
Average available free space in the table
CHAIN_CNT
NUMBER
Number of rows in the table that are chained from
one data block to another or that have migrated to a
new block, requiring a link to preserve the old rowid.
This column is updated only after you analyze the
table.
AVG_ROW_LEN
NUMBER
Average row length, including row overhead
AVG_SPACE_FREELIST_
BLOCKS
NUMBER
Average freespace of all blocks on a freelist
NUM_FREELIST_BLOCKS
NUMBER
Number of blocks on the freelist
DEGREE
VARCHAR2(10)
Number of threads per instance for scanning the table
INSTANCES
VARCHAR2(10)
Number of instances across which the table is to be
scanned
CACHE
VARCHAR2(5)
Whether the cluster is to be cached in the buffer cache
(CACHE | NOCACHE)
TABLE_LOCK
VARCHAR2(8)
Whether table locking is enabled or disabled
SAMPLE_SIZE
NUMBER
Sample size used in analyzing this table
LAST_ANALYZED
DATE
Date on which this table was most recently analyzed
PARTITIONED
VARCHAR2(3)
Whether this table is partitioned (YES | NO)
IOT_TYPE
VARCHAR2(12)
If an index-organized table, whether an overflow
segment has been specified (OVERFLOW) or not (NULL)
OBJECT_ID_TYPE
VARCHAR2(16)
Whether the object ID is USER-DEFINED or SYSTEM
GENERATED
TABLE_TYPE_OWNER
VARCHAR2(30)
If an object table, owner of the type from which the
table is created
TABLE_TYPE
VARCHAR2(30)
If an object table, type of the table
TEMPORARY
VARCHAR2(1)
Whether the table is temporary
SECONDARY
VARCHAR2(1)
Whether the table is a secondary object created by the
ODCIIndexCreate method of the Oracle9i Data
Cartridge to contain the contents of a domain index (Y
| N)
NESTED
VARCHAR2(3)
Whether this is a nested table
BUFFER_POOL
VARCHAR2(7)
Default buffer pool for the table
ROW_MOVEMENT
VARCHAR2(8)
If a partitioned table, whether row movement is
enabled or disabled
Static Data Dictionary Views 2-7
ALL_APPLY
Column
Datatype
NULL
Description
GLOBAL_STATS
VARCHAR2(3)
For partitioned tables, indicates whether statistics
were collected by analyzing the table as a whole (YES)
or were estimated from statistics on underlying
partitions and subpartitions (NO).
USER_STATS
VARCHAR2(3)
Whether statistics were entered directly by the user
DURATION
VARCHAR2(15)
Indicates the duration of a temporary table:
SYS$SESSION: the rows are preserved for the
duration of the session
SYS$TRANSACTION: the rows are deleted after
COMMIT
Null for a permanent table
SKIP_CORRUPT
VARCHAR2(8)
Whether Oracle ignores blocks marked corrupt
during table and index scans (ENABLED) or raises an
error (DISABLED). To enable this feature, run the
DBMS_REPAIR.skip_corrupt_blocks procedure.
MONITORING
VARCHAR2(3)
Whether the table has the MONITORING attribute set
ALL_APPLY
ALL_APPLY displays information about the apply processes that dequeue events
from queues accessible to the current user.
Related View
DBA_APPLY displays information about all apply processes in the database.
Column
Datatype
NULL
Description
APPLY_NAME
VARCHAR2(30)
NOT NULL
Name of the apply process
QUEUE_NAME
VARCHAR2(30)
NOT NULL
Name of the queue from which the apply process
dequeues
QUEUE_OWNER
VARCHAR2(30)
NOT NULL
Owner of the queue from which the apply process
dequeues
APPLY_CAPTURED
VARCHAR2(3)
Indicates whether the apply process applies captured
events (YES) or user-enqueued events (NO)
RULE_SET_NAME
VARCHAR2(30)
Rule set used by the apply process for filtering
RULE_SET_OWNER
VARCHAR2(30)
Owner of the rule set
APPLY_USER
VARCHAR2(30)
APPLY_DATABASE_LINK
VARCHAR2(128)
2-8 Oracle9i Database Reference
NOT NULL
User who is applying events
Database link to which changes are applied. If null,
then changes are applied to the local database.
ALL_APPLY_CONFLICT_COLUMNS
Column
Datatype
NULL
Description
APPLY_TAG
RAW(2000)
Tag associated with redo log records that are
generated when changes are made by the apply
process
DDL_HANDLER
VARCHAR2(92)
Name of the user-specified DDL handler, which
handles DDL logical change records
MESSAGE_HANDLER
VARCHAR2(92)
Name of the user-specified procedure that handles
dequeued events other than logical change records
STATUS
VARCHAR2(8)
Status of the apply process:
■
DISABLED
■
ENABLED
■
ABORTED
See Also: "DBA_APPLY" on page 2-158
ALL_APPLY_CONFLICT_COLUMNS
ALL_APPLY_CONFLICT_COLUMNS displays information about conflict handlers on
the tables accessible to the current user.
Related View
DBA_APPLY_CONFLICT_COLUMNS displays information about conflict handlers on
all tables in the database.
Column
Datatype
NULL
Description
OBJECT_OWNER
VARCHAR2(30)
Owner of the object on which the update conflict
handler is defined
OBJECT_NAME
VARCHAR2(30)
Name of the object on which the update conflict
handler is defined
METHOD_NAME
VARCHAR2(92)
Name of the update conflict handler used to resolve
conflicts
RESOLUTION_COLUMN
VARCHAR2(4000)
Name of the column used to resolve conflicts
COLUMN_NAME
VARCHAR2(30)
Name of a column in the column list for the update
conflict handler
APPLY_DATABASE_LINK
VARCHAR2(128)
Database link to which changes are applied. If null,
then changes are applied to the local database.
See Also: "DBA_APPLY_CONFLICT_COLUMNS" on page 2-159
Static Data Dictionary Views 2-9
ALL_APPLY_DML_HANDLERS
ALL_APPLY_DML_HANDLERS
ALL_APPLY_DML_HANDLERS displays information about the DML handlers on the
tables accessible to the current user.
Related View
DBA_APPLY_DML_HANDLERS displays information about the DML handlers on all
tables in the database.
Column
Datatype
NULL
Description
OBJECT_OWNER
VARCHAR2(30)
Owner of the object on which the DML handler is
specified
OBJECT_NAME
VARCHAR2(30)
Name of the object on which the DML handler is
specified
OPERATION_NAME
VARCHAR2(12)
Name of the DML operation for which the DML
handler is used
USER_PROCEDURE
VARCHAR2(92)
Name of the user-specified DML handler, which
handles row logical change records that contain the
DML operation in the OPERATION_NAME column on
the object
ERROR_HANDLER
VARCHAR2(1)
Indicates whether the DML handler handles only the
relevant row logical change records that result in
apply errors (Y) or all relevant row logical change
records (N)
APPLY_DATABASE_LINK
VARCHAR2(128)
Database link to which changes are applied. If null,
then changes are applied to the local database.
See Also: "DBA_APPLY_DML_HANDLERS" on page 2-159
ALL_APPLY_ERROR
ALL_APPLY_ERROR displays information about error transactions generated by the
apply processes that dequeue events from queues accessible to the current user.
Related View
DBA_APPLY_ERROR displays information about error transactions generated by all
apply processes in the database.
2-10
Oracle9i Database Reference
ALL_APPLY_KEY_COLUMNS
Column
Datatype
NULL
Description
APPLY_NAME
VARCHAR2(30)
QUEUE_NAME
VARCHAR2(30)
NOT NULL
Name of the queue at the local database from which
the transaction was dequeued
QUEUE_OWNER
VARCHAR2(30)
NOT NULL
Owner of the queue at the local database from which
the transaction was dequeued
Name of the apply process at the local database which
processed the transaction
LOCAL_TRANSACTION_ID
VARCHAR2(22)
Local transaction ID for the error transaction
SOURCE_DATABASE
VARCHAR2(128)
Database where the transaction originated
SOURCE_TRANSACTION_ID VARCHAR2(22)
Original transaction ID at the source database
SOURCE_COMMIT_SCN
NUMBER
Original commit system change number (SCN) for the
transaction at the source database
MESSAGE_NUMBER
NUMBER
Identifier for the event in the transaction that raised
an error
ERROR_NUMBER
NUMBER
Error number of the error raised by the transaction
ERROR_MESSAGE
VARCHAR2(4000)
Error message of the error raised by the transaction
RECIPIENT_ID
NUMBER
User ID of the original user that applied the
transaction
RECIPIENT_NAME
VARCHAR2(30)
Name of the original user that applied the transaction
MESSAGE_COUNT
NUMBER
Total number of events inside the error transaction
See Also: "DBA_APPLY_ERROR" on page 2-159
ALL_APPLY_KEY_COLUMNS
ALL_APPLY_KEY_COLUMNS displays information about substitute key columns for
the tables accessible to the current user. Substitute key columns are set using the
SET_KEY_COLUMNS procedure in the DBMS_APPLY_ADM package.
Related View
DBA_APPLY_KEY_COLUMNS displays information about substitute key columns for
all tables in the database.
Column
Datatype
NULL
Description
OBJECT_OWNER
VARCHAR2(30)
NOT NULL
Owner of the object on which substitute key columns
are set
Static Data Dictionary Views 2-11
ALL_APPLY_PARAMETERS
Column
Datatype
NULL
Description
OBJECT_NAME
VARCHAR2(30)
NOT NULL
Name of the object on which substitute key columns
are set
COLUMN_NAME
VARCHAR2(30)
NOT NULL
Column name of a column specified as a substitute
key column
APPLY_DATABASE_LINK
VARCHAR2(128)
Database link to which changes are applied. If null,
then changes are applied to the local database.
See Also: "DBA_APPLY_KEY_COLUMNS" on page 2-160
ALL_APPLY_PARAMETERS
ALL_APPLY_PARAMETERS displays information about the parameters for the apply
processes that dequeue events from queues accessible to the current user.
Related View
DBA_APPLY_PARAMETERS displays information about the parameters for all apply
processes in the database.
Column
Datatype
NULL
Description
APPLY_NAME
VARCHAR2(30)
NOT NULL
Name of the apply process
PARAMETER
VARCHAR2(128)
NOT NULL
Name of the parameter
VALUE
VARCHAR2(4000)
Parameter value
SET_BY_USER
VARCHAR2(3)
Indicates whether the parameter value was set by the
user (YES) or was not set by the user (NO). If NO for a
parameter, then the parameter is set to its default
value. If YES for a parameter, then the parameter may
or may not be set to its default value.
See Also: "DBA_APPLY_PARAMETERS" on page 2-160
ALL_APPLY_PROGRESS
ALL_APPLY_PROGRESS displays information about the progress made by the
apply processes that dequeue events from queues accessible to the current user.
This view only contains information about captured events. It does not contain
information about user-enqueued events.
2-12
Oracle9i Database Reference
ALL_ARGUMENTS
Related View
DBA_APPLY_PROGRESS displays information about the progress made by all apply
processes in the database.
Column
Datatype
NULL
Description
APPLY_NAME
VARCHAR2(30)
NOT NULL
Name of the apply process
APPLIED_MESSAGE_
NUMBER
NUMBER
NOT NULL
Message number up to which all transactions have
definitely been applied. This value is the
low-watermark for the apply process. That is,
messages with a commit message number less than or
equal to this message number have definitely been
applied, but some messages with a higher commit
message number also may have been applied.
OLDEST_MESSAGE_NUMBER NUMBER
NOT NULL
Earliest message number of the transactions currently
being dequeued and applied
APPLY_TIME
DATE
Time at which the message with the message number
displayed in the APPLIED_MESSAGE_NUMBER
column was applied
APPLIED_MESSAGE_
CREATE_TIME
DATE
Time at which the message with the message number
displayed in the APPLIED_MESSAGE_NUMBER
column was created at its source database
See Also: "DBA_APPLY_PROGRESS" on page 2-160
ALL_ARGUMENTS
ALL_ARGUMENTS lists all arguments of procedures and functions that are accessible
to the current user.
Related View
USER_ARGUMENTS lists all arguments of procedures and functions that are owned
by the current user. This view does not display the OWNER column.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the object
OBJECT_NAME
VARCHAR2(30)
PACKAGE_NAME
VARCHAR2(30)
OBJECT_ID
NUMBER
OVERLOAD
VARCHAR2(40)
Name of the procedure or function
Name of the procedure or function
NOT NULL
Object number of the object
Overload unique identifier
Static Data Dictionary Views 2-13
ALL_ASSOCIATIONS
Column
Datatype
NULL
Description
ARGUMENT_NAME
VARCHAR2(30)
POSITION
NUMBER
NOT NULL
Position in the argument list, or null for a function
return value
SEQUENCE
NUMBER
NOT NULL
Argument sequence, including all nesting levels
DATA_LEVEL
NUMBER
NOT NULL
Nesting depth of the argument for composite types
DATA_TYPE
VARCHAR2(30)
Datatype of the argument
DEFAULT_VALUE
LONG
Default value for the argument
DEFAULT_LENGTH
NUMBER
Length of the default value for the argument
IN_OUT
VARCHAR2(9)
Direction of the argument:
Name of the argument
■
IN
■
OUT
■
IN/OUT
DATA_LENGTH
NUMBER
Length of the column (in bytes)
DATA_PRECISION
NUMBER
Length in decimal digits (NUMBER) or binary digits
(FLOAT)
DATA_SCALE
NUMBER
Digits to the right of the decimal point in a number
RADIX
NUMBER
Argument radix for a number
CHARACTER_SET_NAME
VARCHAR2(44)
Character set name for the argument
TYPE_OWNER
VARCHAR2(30)
Owner of the type of the argument
TYPE_NAME
VARCHAR2(30)
Name of the type of the argument. If the type is a
package local type (that is, it is declared in a package
specification), then this column displays the name of
the package.
TYPE_SUBNAME
VARCHAR2(30)
Relevant only for package local types. Displays the
name of the type declared in the package identified in
the TYPE_NAME column.
TYPE_LINK
VARCHAR2(128)
Relevant only for package local types when the
package identified in the TYPE_NAME column is a
remote package. This column displays the database
link used to refer to the remote package.
PLS_TYPE
VARCHAR2(30)
For numeric arguments, the name of the PL/SQL type
of the argument. Null otherwise.
ALL_ASSOCIATIONS
ALL_ASSOCIATIONS describes user-defined statistics associated with objects
accessible to the current user.
2-14
Oracle9i Database Reference
ALL_AUDIT_POLICIES
Related Views
■
■
DBA_ASSOCIATIONS describes all user-defined statistics in the database.
USER_ASSOCIATIONS describes user-defined statistics associated with objects
owned by the current user.
Column
Datatype
NULL
Description
OBJECT_OWNER
VARCHAR2(30)
NOT NULL
Owner of the object for which the association is being
defined
OBJECT_NAME
VARCHAR2(30)
NOT NULL
Name of the object for which the association is being
defined
COLUMN_NAME
VARCHAR2(30)
Column name in the object for which the association
is being defined
OBJECT_TYPE
VARCHAR2(9)
Kind of object with which statistics are being
associated: column, type, package or function,
indextype, or domain index.
STATSTYPE_SCHEMA
VARCHAR2(30)
Owner of the statistics type
STATSTYPE_NAME
VARCHAR2(30)
Name of statistics type that contains the cost,
selectivity or statistics functions
DEF_SELECTIVITY
NUMBER
Default selectivity of the object, if any
DEF_CPU_COST
NUMBER
Default CPU cost of the object, if any
DEF_IO_COST
NUMBER
Default I/O cost of the object, if any
DEF_NET_COST
NUMBER
Default networking cost of the object, if any
INTERFACE_VERSION
NUMBER
Identifies the version number of the ODCIStats
interface. Value is 1 for statistics type implementing
Oracle8i 8.1; 0 for types implementing Oracle9i 9.0.0.
ALL_AUDIT_POLICIES
ALL_AUDIT_POLICIES describes the fine-grained auditing policies on the tables
and views accessible to the current user.
Related Views
■
■
DBA_AUDIT_POLICIES describes all fine-grained auditing policies in the
database.
USER_AUDIT_POLICIES describes the fine-grained auditing policies on the
tables and views owned by the current user. This view does not display the
OBJECT_SCHEMA column.
Static Data Dictionary Views 2-15
ALL_BASE_TABLE_MVIEWS
Column
Datatype
NULL
Description
OBJECT_SCHEMA
VARCHAR2(30)
Owner of the table or view
OBJECT_NAME
VARCHAR2(30)
Name of the table or view
POLICY_NAME
VARCHAR2(30)
Name of the policy
POLICY_TEXT
VARCHAR2(30)
Audit condition
POLICY_COLUMN
VARCHAR2(30)
Relevant column
PF_SCHEMA
VARCHAR2(30)
Owner of the audit handler function
PF_PACKAGE
VARCHAR2(30)
Name of the package containing the audit handler
function
PF_FUNCTION
VARCHAR2(30)
Name of the audit handler function
ENABLED
VARCHAR2(3)
Indicates whether the policy is enabled (YES) or
disabled (NO)
See Also:
■
"DBA_AUDIT_POLICIES" on page 2-164
■
"USER_AUDIT_POLICIES" on page 2-264
ALL_BASE_TABLE_MVIEWS
ALL_BASE_TABLE_MVIEWS describes all materialized views using materialized
view logs accessible to the current user. A materialized view log can be created for a
master or base table or a master materialized view. Query this view at the master
site or the master materialized view site to show one row for each materialized view
using a materialized view log.
Related Views
■
■
DBA_BASE_TABLE_MVIEWS describes all materialized views using
materialized view logs in the database.
USER_BASE_TABLE_MVIEWS describes all materialized views using
materialized view logs owned by the current user.
Column
Datatype
OWNER
VARCHAR2(30)
Schema in which the master table or the master
materialized view was created
MASTER
VARCHAR2(30)
Name of the master table or the master materialized
view
2-16
Oracle9i Database Reference
NULL
Description
ALL_CAPTURE
Column
Datatype
NULL
Description
MVIEW_LAST_REFRESH_
TIME
DATE
Date when the materialized view based on the master
was last refreshed
MVIEW_ID
NUMBER
Unique identifier of the materialized view that is
based on the master
See Also:
■
"DBA_BASE_TABLE_MVIEWS" on page 2-170
■
"USER_BASE_TABLE_MVIEWS" on page 2-265
ALL_CAPTURE
ALL_CAPTURE displays information about the capture processes that enqueue the
captured changes into queues accessible to the current user.
Related View
DBA_CAPTURE displays information about all capture processes in the database.
Column
Datatype
NULL
Description
CAPTURE_NAME
VARCHAR2(30)
NOT NULL
Name of the capture process
QUEUE_NAME
VARCHAR2(30)
NOT NULL
Name of the queue used for staging captured changes
QUEUE_OWNER
VARCHAR2(30)
NOT NULL
Owner of the queue used for staging captured
changes
RULE_SET_NAME
VARCHAR2(30)
Name of the rule set used by the capture process for
filtering
RULE_SET_OWNER
VARCHAR2(30)
Owner of the rule set
START_SCN
NUMBER
System change number (SCN) from which the capture
process will start to capture changes
STATUS
VARCHAR2(8)
Status of the capture process:
CAPTURED_SCN
NUMBER
■
DISABLED
■
ENABLED
■
ABORTED
System change number (SCN) of the last captured
message
Static Data Dictionary Views 2-17
ALL_CAPTURE_PARAMETERS
Column
Datatype
APPLIED_SCN
NUMBER
NULL
Description
System change number (SCN) of the most recent
message dequeued by the relevant apply processes.
All changes below this SCN have been dequeued by
all apply processes that apply changes captured by
this capture process.
See Also: "DBA_CAPTURE" on page 2-170
ALL_CAPTURE_PARAMETERS
ALL_CAPTURE_PARAMETERS displays information about the parameters for the
capture processes that enqueue the captured changes into queues accessible to the
current user.
Related View
DBA_CAPTURE_PARAMETERS displays information about the parameters for all
capture processes in the database.
Column
Datatype
NULL
Description
CAPTURE_NAME
VARCHAR2(30)
NOT NULL
Name of the capture process
PARAMETER
VARCHAR2(128)
NOT NULL
Name of the parameter
VALUE
VARCHAR2(4000)
Parameter value
SET_BY_USER
VARCHAR2(3)
Indicates whether the parameter value was set by the
user (YES) or was not set by the user (NO). If NO, then
the parameter is set to its default value. If YES, then
the parameter may or may not be set to its default
value.
See Also: "DBA_CAPTURE_PARAMETERS" on page 2-171
ALL_CAPTURE_PREPARED_DATABASE
ALL_CAPTURE_PREPARED_DATABASE displays information about when the local
database was prepared for instantiation. If the local database was not prepared for
instantiation, then this view contains no rows.
2-18
Oracle9i Database Reference
ALL_CAPTURE_PREPARED_TABLES
Related View
DBA_CAPTURE_PREPARED_DATABASE displays information about when the local
database was prepared for instantiation.
Column
Datatype
TIMESTAMP
DATE
NULL
Description
Time when the local database was prepared for
instantiation
See Also: "DBA_CAPTURE_PREPARED_DATABASE" on
page 2-171
ALL_CAPTURE_PREPARED_SCHEMAS
ALL_CAPTURE_PREPARED_SCHEMAS displays information about the schemas
prepared for instantiation that are accessible to the current user at the local
database.
Related View
DBA_CAPTURE_PREPARED_SCHEMAS displays information about all schemas
prepared for instantiation at the local database.
Column
Datatype
NULL
Description
SCHEMA_NAME
VARCHAR2(30)
NOT NULL
Name of the schema prepared for instantiation
TIMESTAMP
DATE
Time when the schema was prepared for instantiation
See Also: "DBA_CAPTURE_PREPARED_SCHEMAS" on
page 2-171
ALL_CAPTURE_PREPARED_TABLES
ALL_CAPTURE_PREPARED_TABLES displays information about the tables prepared
for instantiation that are accessible to the current user at the local database.
Related View
DBA_CAPTURE_PREPARED_TABLES displays information about all tables prepared
for instantiation at the local database.
Static Data Dictionary Views 2-19
ALL_CATALOG
Column
Datatype
NULL
TABLE_OWNER
VARCHAR2(30)
Owner of the table prepared for instantiation
TABLE_NAME
VARCHAR2(30)
Name of the table prepared for instantiation
SCN
NUMBER
TIMESTAMP
DATE
NOT NULL
Description
Smallest system change number (SCN) for which the
table can be instantiated
Time when the table was prepared for instantiation
See Also: "DBA_CAPTURE_PREPARED_TABLES" on page 2-171
ALL_CATALOG
ALL_CATALOG lists all indexes, tables, clusters, views, synonyms, and sequences
accessible to the current user.
Related Views
■
■
DBA_CATALOG lists all indexes, tables, clusters, views, synonyms, and
sequences in the entire database.
USER_CATALOG lists all indexes, tables, clusters, views, synonyms, and
sequences in the current user’s schema. This view does not display the OWNER
column.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the INDEX, TABLE, CLUSTER, VIEW,
SYNONYM, SEQUENCE, or UNDEFINED
TABLE_NAME
VARCHAR2(30)
NOT NULL
Name of the INDEX, TABLE, CLUSTER, VIEW,
SYNONYM, SEQUENCE, or UNDEFINED
TABLE_TYPE
VARCHAR2(11)
Type of the INDEX, TABLE, CLUSTER, VIEW,
SYNONYM, SEQUENCE, or UNDEFINED
ALL_CLUSTER_HASH_EXPRESSIONS
ALL_CLUSTER_HASH_EXPRESSIONS lists hash functions for all hash clusters
accessible to the current user.
Related Views
■
2-20
DBA_CLUSTER_HASH_EXPRESSIONS lists hash functions for all hash clusters
in the database.
Oracle9i Database Reference
ALL_CLUSTERS
■
USER_CLUSTER_HASH_EXPRESSIONS lists hash functions for all hash clusters
owned by the current user.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Name of the owner of the cluster
CLUSTER_NAME
VARCHAR2(30)
NOT NULL
Name of the cluster
HASH_EXPRESSION
LONG
Text of hash function of the hash cluster
ALL_CLUSTERS
ALL_CLUSTERS describes all clusters accessible to the current user.
Related Views
■
■
DBA_CLUSTERS describes all clusters in the database.
USER_CLUSTERS describes all clusters owned by the current user. This view
does not display the OWNER column.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the cluster
CLUSTER_NAME
VARCHAR2(30)
NOT NULL
Name of the cluster
TABLESPACE_NAME
VARCHAR2(30)
NOT NULL
Name of the tablespace containing the cluster
PCT_FREE
NUMBER
PCT_USED
NUMBER
KEY_SIZE
NUMBER
INI_TRANS
NUMBER
NOT NULL
Initial number of transactions
MAX_TRANS
NUMBER
NOT NULL
Maximum number of transactions
INITIAL_EXTENT
NUMBER
Size of the initial extent in bytes
NEXT_EXTENT
NUMBER
Size of secondary extents in bytes
MIN_EXTENTS
NUMBER
NOT NULL
Minimum number of extents allowed in the segment
MAX_EXTENTS
NUMBER
NOT NULL
Maximum number of extents allowed in the segment
PCT_INCREASE
NUMBER
NOT NULL
Percentage increase in extent size
FREELISTS
NUMBER
Number of process freelists allocated to this segment
FREELIST_GROUPS
NUMBER
Number of freelist groups allocated to this segment
Minimum percentage of free space in a block
NOT NULL
Minimum percentage of used space in a block
Estimated size of cluster key plus associated rows
Static Data Dictionary Views 2-21
ALL_COL_COMMENTS
Column
Datatype
NULL
Description
AVG_BLOCKS_PER_KEY
NUMBER
Number of blocks in the table divided by number of
cluster keys
CLUSTER_TYPE
VARCHAR2(5)
Type of cluster: B*-Tree index or hash
FUNCTION
VARCHAR2(15)
If a hash cluster, the hash function
HASHKEYS
NUMBER
If a hash cluster, the number of hash keys (hash
buckets)
DEGREE
VARCHAR2(10)
Number of threads per instance for scanning the
cluster
INSTANCES
VARCHAR2(10)
Number of instances across which the cluster is to be
scanned
CACHE
VARCHAR2(5)
Whether the cluster is to be cached in the buffer cache
(CACHE | NOCACHE)
BUFFER_POOL
VARCHAR2(7)
Default buffer pool for the cluster
SINGLE_TABLE
VARCHAR2(5)
Whether this is a single-table cluster (Y | N)
ALL_COL_COMMENTS
ALL_COL_COMMENTS lists comments on columns of tables and views accessible to
the current user.
Related Views
■
■
DBA_COL_COMMENTS lists comments on all tables and views in the database.
USER_COL_COMMENTS lists comments on tables and views owned by the
current user. This view does not display the OWNER column.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the object
TABLE_NAME
VARCHAR2(30)
NOT NULL
Name of the object
COLUMN_NAME
VARCHAR2(30)
NOT NULL
Name of the column
COMMENTS
VARCHAR2(4000)
Comment on the column
ALL_COL_PRIVS
ALL_COL_PRIVS describes the following types of grants:
2-22
Oracle9i Database Reference
ALL_COL_PRIVS_MADE
■
■
Column object grants for which the current user is the object owner, grantor, or
grantee
Column object grants for which an enabled role or PUBLIC is the grantee
Related Views
■
■
DBA_COL_PRIVS describes all column object grants in the database.
USER_COL_PRIVS describes the column object grants for which the current
user is the object owner, grantor, or grantee.
Column
Datatype
NULL
Description
GRANTOR
VARCHAR2(30)
NOT NULL
Name of the user who performed the grant
GRANTEE
VARCHAR2(30)
NOT NULL
Name of the user to whom access was granted
TABLE_SCHEMA
VARCHAR2(30)
NOT NULL
Schema of the object
TABLE_NAME
VARCHAR2(30)
NOT NULL
Name of the object
COLUMN_NAME
VARCHAR2(30)
NOT NULL
Name of the column
PRIVILEGE
VARCHAR2(40)
NOT NULL
Privilege on the column
GRANTABLE
VARCHAR2(3)
Indicates whether the privilege was granted with the
GRANT OPTION (YES) or not (NO)
See Also:
■
"DBA_COL_PRIVS" on page 2-172
■
"USER_COL_PRIVS" on page 2-266
ALL_COL_PRIVS_MADE
ALL_COL_PRIVS_MADE describes the column object grants for which the current
user is the object owner or grantor.
Related View
USER_COL_PRIVS_MADE describes the column object grants for which the current
user is the object owner. This view does not display the OWNER column.
Column
Datatype
NULL
Description
GRANTEE
VARCHAR2(30)
NOT NULL
Name of the user to whom access was granted
OWNER
VARCHAR2(30)
NOT NULL
Owner of the object
Static Data Dictionary Views 2-23
ALL_COL_PRIVS_RECD
Column
Datatype
NULL
Description
TABLE_NAME
VARCHAR2(30)
NOT NULL
Name of the object
COLUMN_NAME
VARCHAR2(30)
NOT NULL
Name of the column
GRANTOR
VARCHAR2(30)
NOT NULL
Name of the user who performed the grant
PRIVILEGE
VARCHAR2(40)
NOT NULL
Privilege on the column
GRANTABLE
VARCHAR2(3)
Indicates whether the privilege was granted with the
GRANT OPTION (YES) or not (NO)
See Also: "USER_COL_PRIVS_MADE" on page 2-267
ALL_COL_PRIVS_RECD
ALL_COL_PRIVS_RECD describes the following types of grants:
■
Column object grants for which the current user is the grantee
■
Column object grants for which an enabled role or PUBLIC is the grantee
Related View
USER_COL_PRIVS_RECD describes the column object grants for which the current
user is the grantee. This view does not display the GRANTEE column.
Column
Datatype
NULL
Description
GRANTEE
VARCHAR2(30)
NOT NULL
Name of the user to whom access was granted
OWNER
VARCHAR2(30)
NOT NUL
Owner of the object
TABLE_NAME
VARCHAR2(30)
NOT NULL
Name of the object
COLUMN_NAME
VARCHAR2(30)
NOT NULL
Name of the column
GRANTOR
VARCHAR2(30)
NOT NULL
Name of the user who performed the grant
PRIVILEGE
VARCHAR2(40)
NOT NULL
Privilege on the column
GRANTABLE
VARCHAR2(3)
Indicates whether the privilege was granted with the
GRANT OPTION (YES) or not (NO)
See Also: "USER_COL_PRIVS_RECD" on page 2-267
2-24
Oracle9i Database Reference
ALL_CONS_COLUMNS
ALL_COLL_TYPES
ALL_COLL_TYPES describes all named collection types (varrays and nested tables)
accessible to the current user.
Related Views
■
■
DBA_COLL_TYPES describes all named collection types in the database.
USER_COLL_TYPES describes all named collection types owned by the current
user. This view does not display the OWNER column.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the collection
TYPE_NAME
VARCHAR2(30)
NOT NULL
Name of the collection
COLL_TYPE
VARCHAR2(30)
NOT NULL
Description of the collection, such as VARYING ARRAY,
[nested] TABLE
UPPER_BOUND
NUMBER
For varrays only, maximum size
ELEM_TYPE_MOD
VARCHAR2(7)
Whether the collection
ELEM_TYPE_OWNER
VARCHAR2(30)
Owner of the type upon which the collection is based.
This value is useful primarily in the case of a
user-defined type.
ELEM_TYPE_NAME
VARCHAR2(30)
Name of the datatype or user-defined type upon
which the collection is based
LENGTH
NUMBER
Length of CHAR elements or maximum length of
VARCHAR or VARCHAR2 elements
PRECISION
NUMBER
Decimal precision of NUMBER or DECIMAL elements;
binary precision of FLOAT elements
SCALE
NUMBER
Scale of NUMBER or DECIMAL elements
CHARACTER_SET_NAME
VARCHAR2(44)
Name of the character set (CHAR_CS | NCHAR_CS)
ELEM_STORAGE
VARCHAR2(7)
[Obsolete column]
NULLS_STORED
VARCHAR2(3)
[Obsolete column]
ALL_CONS_COLUMNS
ALL_CONS_COLUMNS describes columns that are accessible to the current user and
that are specified in constraints.
Static Data Dictionary Views 2-25
ALL_CONS_OBJ_COLUMNS
Related Views
■
■
DBA_CONS_COLUMNS describes all columns in the database that are specified in
constraints.
USER_CONS_COLUMNS describes columns that are owned by the current user
and that are specified in constraints.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the constraint definition
CONSTRAINT_NAME
VARCHAR2(30)
NOT NULL
Name of the constraint definition
TABLE_NAME
VARCHAR2(30)
NOT NULL
Name of the table with constraint definition
COLUMN_NAME
VARCHAR2(4000)
Name of the column or attribute of the object type
column specified in the constraint definition
Note: If you create a constraint on a user-defined REF
column, the system creates the constraint on the
attributes that make up the REF column. Therefore,
the column names displayed in this view are the
attribute names, with the REF column name as a
prefix, in the following form:
"REF_name"."attribute"
POSITION
NUMBER
Original position of column or attribute in the
definition of the object
ALL_CONS_OBJ_COLUMNS
ALL_CONS_OBJ_COLUMNS displays information about the types that object
columns (or attributes) or collection elements have been constrained to, in the tables
accessible to the current user.
Related Views
■
■
2-26
DBA_CONS_OBJ_COLUMNS displays information about the types that object
columns (or attributes) or collection elements have been constrained to, in all
tables in the database.
USER_CONS_OBJ_COLUMNS displays information about the types that object
columns (or attributes) or collection elements have been constrained to, in the
tables owned by the current user. This view does not display the OWNER
column.
Oracle9i Database Reference
ALL_CONSTRAINTS
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
Owner of the table
TABLE_NAME
VARCHAR2(30)
Name of the table containing the object column or
attribute
COLUMN_NAME
VARCHAR2(4000)
Fully qualified name of the object column or attribute
CONS_TYPE_OWNER
VARCHAR2(30)
Owner of the type that the column (or element) is
constrained to
CONS_TYPE_NAME
VARCHAR2(30)
Name of the type that the column (or element) is
constrained to
CONS_TYPE_ONLY
VARCHAR2(15)
Indicates whether the column (or element) is
constrained to ONLY type (Y) or not (N)
See Also:
■
"DBA_CONS_OBJ_COLUMNS" on page 2-173
■
"USER_CONS_OBJ_COLUMNS" on page 2-267
ALL_CONSTRAINTS
ALL_CONSTRAINTS describes constraint definitions on tables accessible to the
current user.
Related Views
■
■
DBA_CONSTRAINTS describes all constraint definitions in the database.
USER_CONSTRAINTS describes constraint definitions on tables in the current
user’s schema.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the constraint definition
CONSTRAINT_NAME
VARCHAR2(30)
NOT NULL
Name of the constraint definition
CONSTRAINT_TYPE
VARCHAR2(1)
Type of constraint definition:
■
C (check constraint on a table)
■
P (primary key)
■
U (unique key)
■
R (referential integrity)
■
V (with check option, on a view)
■
O (with read only, on a view)
Static Data Dictionary Views 2-27
ALL_CONTEXT
Column
Datatype
NULL
Description
TABLE_NAME
VARCHAR2(30)
NOT NULL
Name associated with the table (or view) with
constraint definition
SEARCH_CONDITION
LONG
Text of search condition for a check constraint
R_OWNER
VARCHAR2(30)
Owner of table referred to in a referential constraint
R_CONSTRAINT_NAME
VARCHAR2(30)
Name of the unique constraint definition for
referenced table
DELETE_RULE
VARCHAR2(9)
Delete rule for a referential constraint (CASCADE or NO
ACTION)
STATUS
VARCHAR2(8)
Enforcement status of constraint (ENABLED or
DISABLED)
DEFERRABLE
VARCHAR2(14)
Whether the constraint is deferrable
DEFERRED
VARCHAR2(9)
Whether the constraint was initially deferred
VALIDATED
VARCHAR2(13)
Whether all data obeys the constraint (VALIDATED or
NOT VALIDATED)
GENERATED
VARCHAR2(14)
Whether the name of the constraint is user or system
generated
BAD
VARCHAR2(3)
A YES value indicates that this constraint specifies a
century in an ambiguous manner. To avoid errors
resulting from this ambiguity, rewrite the constraint
using the TO_DATE function with a four-digit year.
See Also: the TO_DATE function in Oracle9i SQL
Reference and Oracle9i Application Developer’s Guide Fundamentals
RELY
VARCHAR2(4)
Whether an enabled constraint is enforced or
unenforced.
See Also: the constraints in Oracle9i SQL Reference
LAST_CHANGE
DATE
When the constraint was last enabled or disabled
INDEX_OWNER
VARCHAR2(30)
Name of the user owning the index
INDEX_NAME
VARCHAR2(30)
Name of the index
ALL_CONTEXT
ALL_CONTEXT describes all context namespaces in the current session for which
attributes and values have been specified using the DBMS_SESSION.SET_CONTEXT
procedure.
2-28
Oracle9i Database Reference
ALL_DEF_AUDIT_OPTS
Related View
DBA_CONTEXT describes all context namespaces defined in the database, regardless
whether any attributes have been specified for them using the DBMS_
SESSION.SET_CONTEXT procedure.
Column
Datatype
NULL
Description
NAMESPACE
VARCHAR2(30)
NOT NULL
Name of the context namespace
SCHEMA
VARCHAR2(30)
NOT NULL
Schema name of the designated package that can set
attributes using this namespace
PACKAGE
VARCHAR2(30)
NOT NULL
Package name of the designated package that can set
attributes using this namespace
ALL_DB_LINKS
ALL_DB_LINKS describes database links accessible to the current user. This view
does not display the PASSWORD column.
Related Views
■
■
DBA_DB_LINKS describes all database links defined in the database. This view
does not display the PASSWORD column.
USER_DB_LINKS describes database links in the current user’s schema. This
view does not display the OWNER column.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Name of the owner of the database link
DB_LINK
VARCHAR2(12)
NOT NULL
Name of the database link
USERNAME
VARCHAR2(30)
Name of user when logging in
PASSWORD
VARCHAR2(30)
Login password for current user
HOST
VARCHAR2(200)
Net8 connect string
CREATED
DATE
NOT NULL
Creation time of the database link
ALL_DEF_AUDIT_OPTS
ALL_DEF_AUDIT_OPTS contains default object-auditing options that will be
applied when objects are created. The output for each column takes one of the
following forms:
Static Data Dictionary Views 2-29
ALL_DEPENDENCIES
■
-/-: no default auditing
■
S/-: auditing whenever successful
■
-/S: auditing whenever not successful
Column
Datatype
NULL
Description
ALT
VARCHAR2(3)
Auditing ALTER WHENEVER SUCCESSFUL /
UNSUCCESSFUL
AUD
VARCHAR2(3)
Auditing AUDIT WHENEVER SUCCESSFUL /
UNSUCCESSFUL
COM
VARCHAR2(3)
Auditing COMMENT WHENEVER SUCCESSFUL /
UNSUCCESSFUL
DEL
VARCHAR2(3)
Auditing DELETE WHENEVER SUCCESSFUL /
UNSUCCESSFUL
GRA
VARCHAR2(3)
Auditing GRANT WHENEVER SUCCESSFUL /
UNSUCCESSFUL
IND
VARCHAR2(3)
Auditing INDEX WHENEVER SUCCESSFUL /
UNSUCCESSFUL
INS
VARCHAR2(3)
Auditing INSERT WHENEVER SUCCESSFUL /
UNSUCCESSFUL
LOC
VARCHAR2(3)
Auditing LOCK WHENEVER SUCCESSFUL /
UNSUCCESSFUL
REN
VARCHAR2(3)
Auditing RENAME WHENEVER SUCCESSFUL /
UNSUCCESSFUL
SEL
VARCHAR2(3)
Auditing SELECT WHENEVER SUCCESSFUL /
UNSUCCESSFUL
UPD
VARCHAR2(3)
Auditing UPDATE WHENEVER SUCCESSFUL /
UNSUCCESSFUL
REF
VARCHAR2(3)
Auditing REFERENCES WHENEVER SUCCESSFUL /
UNSUCCESSFUL (not used)
EXE
VARCHAR2(3)
Auditing EXECUTE WHENEVER SUCCESSFUL /
UNSUCCESSFUL
ALL_DEPENDENCIES
ALL_DEPENDENCIES describes dependencies between procedures, packages,
functions, package bodies, and triggers accessible to the current user, including
dependencies on views created without any database links. This view does not
display the SCHEMAID column.
2-30
Oracle9i Database Reference
ALL_DIM_ATTRIBUTES
Related Views
■
■
DBA_DEPENDENCIES describes all dependencies between objects in the
database. This view does not display the SCHEMAID column.
USER_DEPENDENCIES describes dependencies between objects in the current
user’s schema. This view does not display the OWNER column.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the object
NAME
VARCHAR2(30)
NOT NULL
Name of the object
TYPE
VARCHAR2(12)
Type of object
REFERENCED_OWNER
VARCHAR2(30)
Owner of the parent object
REFERENCED_NAME
VARCHAR2(64)
Type of parent object
REFERENCED_TYPE
VARCHAR2(12)
Type of referenced object
REFERENCED_LINK_NAME
VARCHAR2(128)
Name of the link to the parent object (if remote)
SCHEMAID
NUMBER
ID of the current schema
DEPENDENCY_TYPE
VARCHAR2(4)
Whether the dependency is a REF dependency (REF)
or not (HARD)
ALL_DIM_ATTRIBUTES
ALL_DIM_ATTRIBUTES describes the relationship between a dimension level and a
functionally dependent column. The level columns and the dependent column must
be in the same table.
Related Views
■
■
DBA_DIM_ATTRIBUTES describes all such dimension relationships in the
database.
USER_DIM_ATTRIBUTES describes all such dimension attributes in the current
user’s schema.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the dimension
DIMENSION_NAME
VARCHAR2(30)
NOT NULL
Name of the dimension
LEVEL_NAME
VARCHAR2(30)
COLUMN_NAME
VARCHAR2(30)
Name of the hierarchy level
NOT NULL
Dependent column name
Static Data Dictionary Views 2-31
ALL_DIM_CHILD_OF
Column
Datatype
INFERRED
CHAR(1)
NULL
Description
Whether inferred
ALL_DIM_CHILD_OF
ALL_DIM_CHILD_OF describes hierarchical relationships of 1 to n between the
pairs of levels in the dimensions accessible to the current user.
Related Views
■
■
DBA_DIM_CHILD_OF describes all such hierarchical relationships in the
database.
USER_DIM_CHILD_OF describes all such hierarchical attributes in the current
user’s schema.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the dimension
DIMENSION_NAME
VARCHAR2(30)
NOT NULL
Name of the dimension
HIERARCHY_NAME
VARCHAR2(30)
POSITION
NUMBER
CHILD_LEVEL_NAME
VARCHAR2(30)
Child side of 1:n relationship
JOIN_KEY_ID
VARCHAR2(40)
If non-null, then the child joins to the parent
PARENT_LEVEL_NAME
VARCHAR2(30)
Parent side of 1:n relationship in relation to the
CHILD_LEVEL_NAME
Hierarchy name
NOT NULL
Hierarchical position within this hierarchy, position 1
being the most detailed
ALL_DIM_HIERARCHIES
ALL_DIM_HIERARCHIES describes all dimension hierarchies accessible to the
current user.
Related Views
■
■
2-32
DBA_DIM_HIERARCHIES describes all such hierarchies in the database.
USER_DIM_HIERARCHIES describes all such hierarchies owned by the current
user.
Oracle9i Database Reference
ALL_DIM_LEVEL_KEY
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the dimension
DIMENSION_NAME
VARCHAR2(30)
NOT NULL
Name of the dimension
HIERARCHY_NAME
VARCHAR2(30)
Hierarchy name
ALL_DIM_JOIN_KEY
ALL_DIM_JOIN_KEY describes the joins between two dimension tables that are
accessible to the current user. The join is always specified between a parent
dimension level column and a child column.
Related Views
■
DBA_DIM_JOIN_KEY describes all such joins in the database.
■
USER_DIM_JOIN_KEY describes all such joins owned by the current user.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the dimension
DIMENSION_NAME
VARCHAR2(30)
NOT NULL
Name of the dimension
DIM_KEY_ID
NUMBER
NOT NULL
Join key ID (unique within a dimension)
LEVEL_NAME
VARCHAR2(30)
KEY_POSITION
NUMBER
HIERARCHY_NAME
VARCHAR2(30)
CHILD_JOIN_COLUMN
VARCHAR2(30)
Name of the hierarchy level
NOT NULL
Ordinal position of the key column within the level
Name of the hierarchy
NOT NULL
Name of the join column
ALL_DIM_LEVEL_KEY
ALL_DIM_LEVEL_KEY describes a column of a dimension level accessible to the
current user. The position of a column within a level is specified by KEY_
POSITION.
Related Views
■
■
DBA_DIM_LEVEL_KEY describes all columns of dimension levels in the
database.
USER_DIM_LEVEL_KEY describes all columns of dimension levels owned by
the current user.
Static Data Dictionary Views 2-33
ALL_DIM_LEVELS
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the dimension
DIMENSION_NAME
VARCHAR2(30)
NOT NULL
Name of the dimension
LEVEL_NAME
VARCHAR2(30)
KEY_POSITION
NUMBER
NOT NULL
Ordinal position of the key column within the level
COLUMN_NAME
VARCHAR2(30)
NOT NULL
Name of the key column
Name of the hierarchy level
ALL_DIM_LEVELS
ALL_DIM_LEVELS describes the dimension levels accessible to the current user. All
columns of a dimension level must come from the same relation.
Related Views
■
■
DBA_DIM_LEVELS describes all dimension levels in the database.
USER_DIM_LEVELS describes the levels of all dimensions owned by the current
user.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the dimension
DIMENSION_NAME
VARCHAR2(30)
NOT NULL
Name of the dimension
LEVEL_NAME
VARCHAR2(30)
Unique within a dimension
NUM_COLUMNS
NUMBER
Number of columns in the level definition
DETAILOBJ_OWNER
VARCHAR2(30)
NOT NULL
Owner of the detail object that the keys of this level
come from
DETAILOBJ_NAME
VARCHAR2(30)
NOT NULL
Name of the table that the keys of this level come
from
ALL_DIMENSIONS
ALL_DIMENSIONS describes dimension objects accessible to the current user.
Related Views
2-34
■
DBA_DIMENSIONS describes all dimensions in the database.
■
USER_DIMENSIONS describes dimensions in the current user’s schema.
Oracle9i Database Reference
ALL_ERRORS
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the dimension
DIMENSION_NAME
VARCHAR2(30)
NOT NULL
Name of the dimension
INVALID
VARCHAR2(1)
Whether the dimension is invalid (Y/N)
REVISION
NUMBER
Dimension revision level
ALL_DIRECTORIES
ALL_DIRECTORIES describes all directories accessible to the current user.
Related View
DBA_DIRECTORIES describes all directories in the database.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the directory (always SYS)
DIRECTORY_NAME
VARCHAR2(30)
NOT NULL
Name of the directory
DIRECTORY_PATH
VARCHAR2(4000)
Operating system pathname for the directory
ALL_ERRORS
ALL_ERRORS describes current errors on all stored objects (views, procedures,
functions, packages, and package bodies) accessible to the current user.
Related Views
■
■
DBA_ERRORS describes all current errors on all views, procedures, functions,
packages, and package bodies in the database.
USER_ERRORS describes all current errors on all views, procedures, functions,
packages, and package bodies owned by the current user. This view does not
display the OWNER column.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the object
NAME
VARCHAR2(30)
NOT NULL
Name of the object
TYPE
VARCHAR2(12)
SEQUENCE
NUMBER
Type of object
NOT NULL
Sequence number, for ordering
Static Data Dictionary Views 2-35
ALL_EVALUATION_CONTEXT_TABLES
Column
Datatype
NULL
Description
LINE
NUMBER
NOT NULL
Line number at which this error occurs
POSITION
NUMBER
NOT NULL
Position in the line at which this error occurs
TEXT
VARCHAR2(4000)
NOT NULL
Text of the error
ALL_EVALUATION_CONTEXT_TABLES
ALL_EVALUATION_CONTEXT_TABLES describes the tables in the rule evaluation
contexts accessible to the current user.
Related Views
■
■
DBA_EVALUATION_CONTEXT_TABLES describes the tables in all rule
evaluation contexts in the database.
USER_EVALUATION_CONTEXT_TABLES describes the tables in the rule
evaluation contexts owned by the current user. This view does not display the
EVALUATION_CONTEXT_OWNER column.
Column
Datatype
NULL
Description
EVALUATION_CONTEXT_
OWNER
VARCHAR2(30)
NOT NULL
Owner of the evaluation context
EVALUATION_CONTEXT_
NAME
VARCHAR2(30)
NOT NULL
Name of the evaluation context
TABLE_ALIAS
VARCHAR2(30)
Alias for a table in the evaluation context
TABLE_NAME
VARCHAR2(4000)
Name of the table referred to by the table alias
See Also:
■
"DBA_EVALUATION_CONTEXT_TABLES" on page 2-178
■
"USER_EVALUATION_CONTEXT_TABLES" on page 2-269
ALL_EVALUATION_CONTEXT_VARS
ALL_EVALUATION_CONTEXT_VARS describes the variables in the rule evaluation
contexts accessible to the current user.
2-36
Oracle9i Database Reference
ALL_EVALUATION_CONTEXTS
Related Views
■
■
DBA_EVALUATION_CONTEXT_VARS describes the variables in all rule
evaluation contexts in the database.
USER_EVALUATION_CONTEXT_VARS describes the variables in the rule
evaluation contexts owned by the current user. This view does not display the
EVALUATION_CONTEXT_OWNER column.
Column
Datatype
NULL
Description
EVALUATION_CONTEXT_
OWNER
VARCHAR2(30)
NOT NULL
Owner of the evaluation context
EVALUATION_CONTEXT_
NAME
VARCHAR2(30)
NOT NULL
Name of the evaluation context
VARIABLE_NAME
VARCHAR2(30)
Name of a variable in the evaluation context
VARIABLE_TYPE
VARCHAR2(4000)
Datatype of the variable
VARIABLE_VALUE_
FUNCTION
VARCHAR2(4000)
Function used to retrieve the value of the variable
(NULL for variables that are not implicit)
VARIABLE_METHOD_
FUNCTION
VARCHAR2(228)
Function used to retrieve the result of method
invocation on the variable. Such a function can speed
up evaluation, if there are many simple rules that
invoke the method on the variable.
See Also:
■
"DBA_EVALUATION_CONTEXT_VARS" on page 2-179
■
"USER_EVALUATION_CONTEXT_VARS" on page 2-270
ALL_EVALUATION_CONTEXTS
ALL_EVALUATION_CONTEXTS describes the rule evaluation contexts accessible to
the current user.
Related Views
■
■
DBA_EVALUATION_CONTEXTS describes all rule evaluation contexts in the
database.
USER_EVALUATION_CONTEXTS describes the rule evaluation contexts owned
by the current user. This view does not display the EVALUATION_CONTEXT_
OWNER column.
Static Data Dictionary Views 2-37
ALL_EXTERNAL_LOCATIONS
Column
Datatype
NULL
Description
EVALUATION_CONTEXT_
OWNER
VARCHAR2(30)
NOT NULL
Owner of the evaluation context
EVALUATION_CONTEXT_
NAME
VARCHAR2(30)
NOT NULL
Name of the evaluation context
EVALUATION_FUNCTION
VARCHAR2(4000)
Evaluation function associated with the evaluation
context, if any
EVALUATION_CONTEXT_
COMMENT
VARCHAR2(4000)
Comment specified with the evaluation context, if any
See Also:
■
"DBA_EVALUATION_CONTEXTS" on page 2-179
■
"USER_EVALUATION_CONTEXTS" on page 2-270
ALL_EXTERNAL_LOCATIONS
ALL_EXTERNAL_LOCATIONS describes the locations (data sources) of the external
tables accessible to the current user.
Related Views
■
■
DBA_EXTERNAL_LOCATIONS describes the locations (data sources) of all
external tables in the database.
USER_EXTERNAL_LOCATIONS describes the locations (data sources) of the
external tables owned by the current user. This view does not display the
OWNER column.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the external table location
TABLE_NAME
VARCHAR2(30)
NOT NULL
Name of the corresponding external table
LOCATION
VARCHAR2(4000)
External table location clause
DIRECTORY_OWNER
CHAR(3)
Owner of the directory containing the external table
location
DIRECTORY_NAME
VARCHAR2(30)
Name of the directory containing the external table
location
2-38
Oracle9i Database Reference
ALL_EXTERNAL_TABLES
See Also:
■
"DBA_EXTERNAL_LOCATIONS" on page 2-181
■
"USER_EXTERNAL_LOCATIONS" on page 2-270
ALL_EXTERNAL_TABLES
ALL_EXTERNAL_TABLES describes the external tables accessible to the current user.
Related Views
■
■
DBA_EXTERNAL_TABLES describes all external tables in the database.
USER_EXTERNAL_TABLES describes the external tables owned by the current
user. This view does not display the OWNER column.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the external table
TABLE_NAME
VARCHAR2(30)
NOT NULL
Name of the external table
TYPE_OWNER
CHAR(3)
TYPE_NAME
VARCHAR2(30)
DEFAULT_DIRECTORY_
OWNER
CHAR(3)
DEFAULT_DIRECTORY_
NAME
VARCHAR2(30)
REJECT_LIMIT
NUMBER
Reject limit for the external table (default is 0)
ACCESS_TYPE
VARCHAR2(7)
Type of access parameters for the external table
(CLOB/BLOB)
ACCESS_PARAMETERS
VARCHAR2(4000)
Access parameters for the external table
Owner of the implementation type for the external
table access driver
NOT NULL
Name of the implementation type for the external
table access driver
Owner of the default directory for the external table
(can be NULL)
NOT NULL
Name of the default directory for the external table
(can be NULL)
See Also:
■
"DBA_EXTERNAL_TABLES" on page 2-181
■
"USER_EXTERNAL_TABLES" on page 2-270
Static Data Dictionary Views 2-39
ALL_IND_COLUMNS
ALL_IND_COLUMNS
ALL_IND_COLUMNS describes the columns of indexes on all tables accessible to the
current user.
Note: For join indexes, the TABLE_NAME and TABLE_OWNER
columns in this view may not match the TABLE_NAME and TABLE_
OWNER columns you find in the *_INDEXES (and other similar)
data dictionary views.
Related Views
■
■
DBA_IND_COLUMNS describes the columns of indexes on all tables in the
database.
USER_IND_COLUMNS describes the columns of indexes owned by the current
user and columns of indexes on tables owned by the current user. This view
does not display the INDEX_OWNER or TABLE_OWNER columns.
Column
Datatype
NULL
Description
INDEX_OWNER
VARCHAR2(30)
NOT NULL
Owner of the index
INDEX_NAME
VARCHAR2(30)
NOT NULL
Name of the index
TABLE_OWNER
VARCHAR2(30)
NOT NULL
Owner of the table or cluster
TABLE_NAME
VARCHAR2(30)
NOT NULL
Name of the table or cluster
COLUMN_NAME
VARCHAR2(4000)
Column name or attribute of object type column
Note: If you create an index on a user-defined REF
column, the system creates the index on the attributes
that make up the REF column. Therefore, the column
names displayed in this view are the attribute names,
with the REF column name as a prefix, in the
following form:
"REF_name"."attribute"
COLUMN_POSITION
NUMBER
NOT NULL
Position of column or attribute within the index
COLUMN_LENGTH
NUMBER
NOT NULL
Indexed length of the column
CHAR_LENGTH
NUMBER
Maximum codepoint length of the column
DESCEND
VARCHAR2(4)
Whether the column is sorted in descending order
(Y/N)
2-40
Oracle9i Database Reference
ALL_IND_PARTITIONS
ALL_IND_EXPRESSIONS
ALL_IND_EXPRESSIONS describes the expressions of function-based indexes on
tables accessible to the current user.
Related Views
■
■
DBA_IND_EXPRESSIONS describes the expressions of all function-based
indexes in the database.
USER_IND_EXPRESSIONS describes the expressions of function-based indexes
on tables owned by the current user. This view does not display the INDEX_
OWNER or TABLE_OWNER columns.
Column
Datatype
NULL
Description
INDEX_OWNER
VARCHAR2(30)
NOT NULL
Index owner
INDEX_NAME
VARCHAR2(30)
NOT NULL
Index name
TABLE_OWNER
VARCHAR2(30)
NOT NULL
Table or cluster owner
TABLE_NAME
VARCHAR2(30)
NOT NULL
Table or cluster name
COLUMN_EXPRESSION
LONG
COLUMN_POSITION
NUMBER
Function-based index expression defining the column
NOT NULL
Position of column or attribute within index
ALL_IND_PARTITIONS
ALL_IND_PARTITIONS describes, for each index partition accessible to the current
user, the partition-level partitioning information, the storage parameters for the
partition, and various partition statistics collected by ANALYZE statements.
Related Views
■
■
DBA_IND_PARTITIONS describes all index partitions in the database.
USER_IND_PARTITIONS describes the index partitions owned by the current
user. This view does not display the INDEX_OWNER column.
Column
Datatype
Description
INDEX_OWNER
VARCHAR2(30)
Owner of the index
INDEX_NAME
VARCHAR2(30)
Name of the index
COMPOSITE
VARCHAR2(3)
Whether the partition belongs to a local index on a
composite-partitioned table (YES | NO)
Static Data Dictionary Views 2-41
ALL_IND_PARTITIONS
Column
Datatype
Description
PARTITION_NAME
VARCHAR2(30)
Name of the partition
SUBPARTITION_COUNT
NUMBER
If a local index on a composite-partitioned table, the number of
subpartitions in the partition
HIGH_VALUE
LONG
Partition bound value expression
HIGH_VALUE_LENGTH
NUMBER
Length of partition bound value expression
PARTITION_POSITION
NUMBER
Position of the partition within the index
STATUS
VARCHAR2(8)
Whether index partition is USABLE or UNUSABLE
TABLESPACE_NAME
VARCHAR2(30)
Name of the tablespace containing the partition
PCT_FREE
NUMBER
Minimum percentage of free space in a block
INI_TRANS
NUMBER
Initial number of transactions
MAX_TRANS
NUMBER
Maximum number of transactions
INITIAL_EXTENT
NUMBER
Size of the initial extent in bytes
NEXT_EXTENT
NUMBER
Size of secondary extents in bytes
MIN_EXTENT
NUMBER
Minimum number of extents allowed in the segment
MAX_EXTENT
NUMBER
Maximum number of extents allowed in the segment
PCT_INCREASE
NUMBER
Percentage increase in extent size
FREELISTS
NUMBER
Number of process freelists allocated in this segment
FREELIST_GROUPS
NUMBER
Number of process freelist groups allocated in this segment
LOGGING
VARCHAR2(7)
Logging attribute of partition
COMPRESSION
VARCHAR2(8)
Indicates whether key compression is ENABLED or DISABLED for a
partitioned index. NULL for a nonpartitioned index.
BLEVEL
NUMBER
B*-Tree level: depth of the index from its root block to its leaf blocks. A
depth of 0 indicates that the root block and leaf block are the same.
LEAF_BLOCKS
NUMBER
Number of leaf blocks in the index partition
DISTINCT_KEYS
NUMBER
Number of distinct keys in the index partition
AVG_LEAF_BLOCKS_PER_
KEY
NUMBER
Average number of leaf blocks in which each distinct value in the index
appears, rounded to the nearest integer. For indexes that enforce
UNIQUE and PRIMARY KEY constraints, this value is always 1.
AVG_DATA_BLOCKS_PER_
KEY
NUMBER
Average number of data blocks in the table that are pointed to by a
distinct value in the index rounded to the nearest integer. This statistic
is the average number of data blocks that contain rows that contain a
given value for the indexed columns.
2-42
Oracle9i Database Reference
ALL_IND_SUBPARTITIONS
Column
Datatype
Description
CLUSTERING_FACTOR
NUMBER
Indicates the amount of order of the rows in the table based on the
values of the index.
■
■
If the value is near the number of blocks, then the table is very well
ordered. In this case, the index entries in a single leaf block tend to
point to rows in the same data blocks.
If the value is near the number of rows, then the table is very
randomly ordered. In this case, it is unlikely that index entries in
the same leaf block point to rows in the same data blocks.
NUM_ROWS
NUMBER
Number of rows returned by the ANALYZE statement
SAMPLE_SIZE
NUMBER
Sample size used in analyzing this partition
LAST_ANALYZED
DATE
Date on which this partition was most recently analyzed
BUFFER_POOL
VARCHAR2(7)
Actual buffer pool for the partition
USER_STATS
VARCHAR2(3)
Indicates whether the statistics were entered directly by the user (YES)
or not (NO)
PCT_DIRECT_ACCESS
NUMBER
If a secondary index on index-organized table, the percentage of rows
with VALID guess
GLOBAL_STATS
VARCHAR2(3)
Indicates whether statistics for the partition were collected for the
partition as a whole (YES) or were estimated from statistics on
underlying subpartitions (NO).
DOMIDX_OPSTATUS
VARCHAR2(6)
PARAMETERS
VARCHAR2(1000)
ALL_IND_SUBPARTITIONS
ALL_IND_SUBPARTITIONS describes, for each index subpartition accessible to the
current user, the partition-level partitioning information, the storage parameters for
the subpartition, and various partition statistics collected by ANALYZE statements.
Related Views
■
■
DBA_IND_SUBPARTITIONS describes all index subpartitions in the database.
USER_IND_SUBPARTITIONS describes the index subpartitions owned by the
current user. This view does not display the INDEX_OWNER column.
Column
Datatype
NULL
Description
INDEX_OWNER
VARCHAR2(30)
NOT NULL
Owner of the index
INDEX_NAME
VARCHAR2(30)
NOT NULL
Name of the index
PARTITION_NAME
VARCHAR2(30)
Name of the partition
Static Data Dictionary Views 2-43
ALL_IND_SUBPARTITIONS
Column
Datatype
SUBPARTITION_NAME
VARCHAR2(30)
SUBPARTITION_POSITION NUMBER
NULL
Description
Name of the subpartition
NOT NULL
Position of a subpartition within a partition
Whether index partition is usable or not
STATUS
VARCHAR2(8)
TABLESPACE_NAME
VARCHAR2(30)
NOT NULL
Name of the tablespace containing the partition
PCT_FREE
NUMBER
NOT NULL
Minimum percentage of free space in a block
INI_TRANS
NUMBER
NOT NULL
Initial number of transactions
MAX_TRANS
NUMBER
NOT NULL
Maximum number of transactions
INITIAL_EXTENT
NUMBER
Size of the initial extent in bytes
NEXT_EXTENT
NUMBER
Size of secondary extents in bytes
MIN_EXTENT
NUMBER
NOT NULL
Minimum number of extents allowed in the segment
MAX_EXTENT
NUMBER
NOT NULL
Maximum number of extents allowed in the segment
PCT_INCREASE
NUMBER
NOT NULL
Percentage increase in extent size
FREELISTS
NUMBER
Number of process freelists allocated in this segment
FREELIST_GROUPS
NUMBER
Number of process freelist groups allocated in this
segment
LOGGING
VARCHAR2(3)
Logging attribute of partition
BLEVEL
NUMBER
B-Tree level: depth of the index from its root block to
its leaf blocks. A depth of 0 indicates that the root
block and leaf block are the same.
LEAF_BLOCKS
NUMBER
Number of leaf blocks in the index
DISTINCT_KEYS
NUMBER
Number of distinct keys in the index partition
AVG_LEAF_BLOCKS_PER_
KEY
NUMBER
Average number of leaf blocks in which each distinct
value in the index appears, rounded to the nearest
integer. For indexes that enforce UNIQUE and
PRIMARY KEY constraints, this value is always 1.
AVG_DATA_BLOCKS_PER_
KEY
NUMBER
Average number of data blocks in the table that are
pointed to by a distinct value in the index rounded to
the nearest integer. This statistic is the average
number of data blocks that contain rows that contain
a given value for the indexed columns.
2-44
Oracle9i Database Reference
ALL_INDEXES
Column
Datatype
CLUSTERING_FACTOR
NUMBER
NULL
Description
Indicates the amount of order of the rows in the table
based on the values of the index.
■
■
If the value is near the number of blocks, then
the table is very well ordered. In this case, the
index entries in a single leaf block tend to point
to rows in the same data blocks.
If the value is near the number of rows, then the
table is very randomly ordered. In this case, it is
unlikely that index entries in the same leaf block
point to rows in the same data blocks.
NUM_ROWS
NUMBER
Number of rows in this index subpartition
SAMPLE_SIZE
NUMBER
Sample size used in analyzing this subpartition
LAST_ANALYZED
DATE
Date on which this partition was most recently
analyzed
BUFFER_POOL
VARCHAR2(7)
Default buffer pool for the subpartition
USER_STATS
VARCHAR2(3)
Whether the statistics were entered directly by the
user
GLOBAL_STATS
VARCHAR2(3)
Indicates whether column statistics for the
subpartition statistics were collected by analyzing the
table as a whole (YES) or estimated from statistics
gathered on partitions and subpartitions (NO).
ALL_INDEXES
ALL_INDEXES describes indexes on all tables accessible to the current user. To
gather statistics for this view and the related views DBA_INDEXES and USER_
INDEXES, use the SQL ANALYZE statement.
Note: Column names followed by an asterisk are populated only
if you collect statistics on the index using the ANALYZE statement or
the DBMS_STATS package.
Related Views
■
■
DBA_INDEXES describes all indexes in the database.
USER_INDEXES describes the indexes owned by the current user. This view
does not display the OWNER column.
Static Data Dictionary Views 2-45
ALL_INDEXES
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the index
INDEX_NAME
VARCHAR2(30)
NOT NULL
Name of the index
INDEX_TYPE
VARCHAR2(12)
TABLE_OWNER
VARCHAR2(30)
NOT NULL
Owner of the indexed object
TABLE_NAME
VARCHAR2(30)
NOT NULL
Name of the indexed object
TABLE_TYPE
CHAR(5)
Type of the indexed object (for example, TABLE,
CLUSTER)
UNIQUENESS
VARCHAR2(9)
Whether the index is UNIQUE or NONUNIQUE
COMPRESSION
VARCHAR2(11)
Whether the index is ENABLED or DISABLED
PREFIX_LENGTH
NUMBER
Number of columns in the prefix of the compression
key
TABLESPACE_NAME
VARCHAR2(30)
Name of the tablespace containing the index
INI_TRANS
NUMBER
Initial number of transactions
MAX_TRANS
NUMBER
Maximum number of transactions
INITIAL_EXTENT
NUMBER
Size of the initial extent
NEXT_EXTENT
NUMBER
Size of secondary extents
MIN_EXTENTS
NUMBER
Minimum number of extents allowed in the segment
MAX_EXTENTS
NUMBER
Maximum number of extents allowed in the segment
PCT_INCREASE
NUMBER
Percentage increase in extent size
PCT_THRESHOLD
NUMBER
Threshold percentage of block space allowed per
index entry
INCLUDE_COLUMN
NUMBER
Column ID of the last column to be included in
index-organized table primary key (non-overflow)
index. This column maps to the COLUMN_ID column
of the *_TAB_COLUMNS data dictionary views.
FREELISTS
NUMBER
Number of process freelists allocated to this segment
FREELIST_GROUPS
NUMBER
Number of freelist groups allocated to this segment
PCT_FREE
NUMBER
Minimum percentage of free space in a block
LOGGING
VARCHAR2(3)
Logging information
BLEVEL*
NUMBER
B*-Tree level: depth of the index from its root block to
its leaf blocks. A depth of 0 indicates that the root
block and leaf block are the same.
LEAF_BLOCKS*
NUMBER
Number of leaf blocks in the index
2-46
Oracle9i Database Reference
Type of index (NORMAL, BITMAP, FUNCTION-BASED
NORMAL, FUNCTION-BASED BITMAP, or DOMAIN)
ALL_INDEXES
Column
Datatype
NULL
Description
DISTINCT_KEYS*
NUMBER
Number of distinct indexed values. For indexes that
enforce UNIQUE and PRIMARY KEY constraints, this
value is the same as the number of rows in the table
(USER_TABLES.NUM_ROWS)
AVG_LEAF_BLOCKS_PER_
KEY*
NUMBER
Average number of leaf blocks in which each distinct
value in the index appears, rounded to the nearest
integer. For indexes that enforce UNIQUE and
PRIMARY KEY constraints, this value is always 1.
AVG_DATA_BLOCKS_PER_
KEY*
NUMBER
Average number of data blocks in the table that are
pointed to by a distinct value in the index rounded to
the nearest integer. This statistic is the average
number of data blocks that contain rows that contain
a given value for the indexed columns.
CLUSTERING_FACTOR*
NUMBER
Indicates the amount of order of the rows in the table
based on the values of the index.
■
■
If the value is near the number of blocks, then
the table is very well ordered. In this case, the
index entries in a single leaf block tend to point
to rows in the same data blocks.
If the value is near the number of rows, then the
table is very randomly ordered. In this case, it is
unlikely that index entries in the same leaf block
point to rows in the same data blocks.
STATUS
VARCHAR2(8)
Whether a nonpartitioned index is VALID or
UNUSABLE
NUM_ROWS
NUMBER
Number of rows in the index
SAMPLE_SIZE
NUMBER
Size of the sample used to analyze the index
LAST_ANALYZED
DATE
Date on which this index was most recently analyzed
DEGREE
VARCHAR2(40)
Number of threads per instance for scanning the
index
INSTANCES
VARCHAR2(40)
Number of instances across which the indexes to be
scanned
PARTITIONED
VARCHAR2(3)
Whether this index is partitioned (YES | NO)
TEMPORARY
VARCHAR2(1)
Whether the index is on a temporary table
GENERATED
VARCHAR2(1)
Whether the name of the index is system generated
(Y|N)
SECONDARY
VARCHAR2(1)
Whether the index is a secondary object created by
the ODCIIndexCreate method of the Oracle9i Data
Cartridge (Y|N)
BUFFER_POOL
VARCHAR2(7)
Name of the default buffer pool to be used for the
index blocks
Static Data Dictionary Views 2-47
ALL_INDEXTYPE_COMMENTS
Column
Datatype
NULL
Description
USER_STATS
VARCHAR2(3)
Whether the statistics were entered directly by the
user
DURATION
VARCHAR2(15)
Indicates the duration of a temporary table:
■
■
SYS$SESSION: the rows are preserved for the
duration of the session
SYS$TRANSACTION: the rows are deleted after
COMMIT
Null for a permanent table
PCT_DIRECT_ACCESS
NUMBER
For a secondary index on an index-organized table,
the percentage of rows with VALID guess
ITYP_OWNER
NUMBER
For a domain index, the owner of the indextype
ITYP_NAME
VARCHAR2(30)
For a domain index, the name of the indextype
PARAMETERS
VARCHAR2(1000)
For a domain index, the parameter string
GLOBAL_STATS
VARCHAR2(3)
For partitioned indexes, indicates whether statistics
were collected by analyzing index as a whole (YES) or
were estimated from statistics on underlying index
partitions and subpartitions (NO).
DOMIDX_STATUS
VARCHAR
Reflects the status of the domain index
■
NULL: the specified index is not a domain index
■
VALID: the index is a valid domain index
■
DOMIDX_OPSTATUS
FUNCIDX_STATUS
VARCHAR
VARCHAR
IDXTYP_INVLD: the indextype of this domain
index is invalid
Reflects the status of an operation that was performed
on a domain index
■
NULL: the specified index is not a domain index
■
VALID: the operation performed without errors
■
FAILED: the operation failed with an error
Indicates the status of a function-based index
■
NULL: this is not a function-based index
■
ENABLED: the function-based index is enabled
■
DISABLED: the function-based index is disabled
ALL_INDEXTYPE_COMMENTS
ALL_INDEXTYPE_COMMENTS lists all comments for user-defined indextypes
accessible to the current user.
2-48
Oracle9i Database Reference
ALL_INDEXTYPE_OPERATORS
Related Views
■
■
DBA_INDEXTYPE_COMMENTS lists all comments for user-defined indextypes in
the database.
USER_INDEXTYPE_COMMENTS lists all comments for user-defined indextypes
owned by the current user.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the user-defined indextype
INDEXTYPE_NAME
VARCHAR2(30)
NOT NULL
Name of the user-defined indextype
COMMENTS
VARCHAR2(4000)
Comment for the user-defined indextype
See Also:
■
"DBA_INDEXTYPE_COMMENTS" on page 2-183
■
"USER_INDEXTYPE_COMMENTS" on page 2-272
ALL_INDEXTYPE_OPERATORS
ALL_INDEXTYPE_OPERATORS lists all operators supported by indextypes
accessible to the current user.
Related Views
■
■
DBA_INDEXTYPE_OPERATORS lists all operators supported by indextypes in
the database.
USER_INDEXTYPE_OPERATORS lists all operators supported by indextypes
owned by the current user.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the indextype
INDEXTYPE_NAME
VARCHAR2(30)
NOT NULL
Name of the indextype
OPERATOR_SCHEMA
VARCHAR2(30)
NOT NULL
Name of the operator schema
OPERATOR_NAME
VARCHAR2(30)
NOT NULL
Name of the operator for which the indextype is
defined
BINDING#
NUMBER
NOT NULL
Binding# associated with the operator
Static Data Dictionary Views 2-49
ALL_INDEXTYPES
See Also:
■
"DBA_INDEXTYPE_OPERATORS" on page 2-184
■
"USER_INDEXTYPE_OPERATORS" on page 2-272
ALL_INDEXTYPES
ALL_INDEXTYPES describes all indextypes accessible to the current user.
Related Views
■
DBA_INDEXTYPES describes all indextypes in the database.
■
USER_INDEXTYPES describes all indextypes owned by the current user.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the indextype
INDEXTYPE_NAME
VARCHAR2(30)
NOT NULL
Name of the indextype
IMPLEMENTATION_SCHEMA VARCHAR2(30)
NOT NULL
Name of the schema for indextype implementation
(that is, containing the indextype operators)
IMPLEMENTATION_NAME
VARCHAR2(30)
NOT NULL
Name of indextype implementation type
INTERFACE_VERSION
NUMBER
IMPLEMENTATION_
VERSION
NUMBER
NUMBER_OF_OPERATORS
NUMBER
Number of operators associated with the indextype
PARTITIONING
VARCHAR2(10)
Kinds of local partitioning supported by the
indextype
Version of indextype interface
NOT NULL
Version of indextype implementation
See Also:
■
"DBA_INDEXTYPES" on page 2-184
■
"USER_INDEXTYPES" on page 2-272
ALL_INTERNAL_TRIGGERS
ALL_INTERNAL_TRIGGERS describes internal triggers on tables accessible to the
current user. Internal triggers are internal pieces of code executed when a particular
flag is set for a table.
2-50
Oracle9i Database Reference
ALL_JAVA_ARGUMENTS
Related Views
■
■
DBA_INTERNAL_TRIGGERS describes internal triggers on all tables in the
database. This view does not display the OWNER_NAME column.
USER_INTERNAL_TRIGGERS describes all internal triggers on tables owned by
the current user. This view does not display the OWNER_NAME column.
Column
Datatype
NULL
Description
TABLE_NAME
VARCHAR2(30)
Name of the table on which the trigger is defined
OWNER_NAME
VARCHAR2(30)
Owner of the table
Indicates the type of internal trigger on the table
INTERNAL_TRIGGER_TYPE VARCHAR2(19)
ALL_JAVA_ARGUMENTS
ALL_JAVA_ARGUMENTS displays argument information about the stored Java
classes accessible to the current user.
Related Views
■
■
DBA_JAVA_ARGUMENTS displays argument information about all stored Java
classes in the database.
USER_JAVA_ARGUMENTS displays argument information about the stored Java
classes owned by the current user. This view does not display the OWNER
column.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the Java class
NAME
VARCHAR2(4000)
Name of the Java class
METHOD_INDEX
NUMBER
Index of the hosting method of the argument
METHOD_NAME
VARCHAR2(4000)
Name of the hosting method of the argument
ARGUMENT_POSITION
NUMBER
Position of the argument, starting from 0
ARRAY_DEPTH
NUMBER
Array depth of the type of the argument
Static Data Dictionary Views 2-51
ALL_JAVA_CLASSES
Column
Datatype
BASE_TYPE
VARCHAR2(7)
ARGUMENT_CLASS
NULL
Description
Base type of the type of the argument:
■
int
■
long
■
float
■
double
■
boolean
■
byte
■
char
■
short
■
class
Actual class name of the argument if the base type is
class
VARCHAR2(4000)
See Also:
■
"DBA_JAVA_ARGUMENTS" on page 2-184
■
"USER_JAVA_ARGUMENTS" on page 2-272
ALL_JAVA_CLASSES
ALL_JAVA_CLASSES displays class level information about the stored Java classes
accessible to the current user.
Related Views
■
■
DBA_JAVA_CLASSES displays class level information about all stored Java
classes in the database.
USER_JAVA_CLASSES displays class level information about the stored Java
classes owned by the current user. This view does not display the OWNER
column.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the Java class
NAME
VARCHAR2(4000)
Name of the Java class
MAJOR
NUMBER
Major version number of the Java class, as defined in
the JVM specification
2-52
Oracle9i Database Reference
ALL_JAVA_DERIVATIONS
Column
Datatype
NULL
Description
MINOR
NUMBER
Minor version number of the Java class, as defined in
the JVM specification
KIND
VARCHAR2(9)
Indicates whether the stored object is a Java class
(CLASS) or a Java interface (INTERFACE)
ACCESSIBILITY
VARCHAR2(6)
Accessibility of the Java class
IS_INNER
VARCHAR2(3)
Indicates whether this Java class is an inner class
(YES) or not (NO)
IS_ABSTRACT
VARCHAR2(3)
Indicates whether this Java class is an abstract class
(YES) or not (NO)
IS_FINAL
VARCHAR2(3)
Indicates whether this Java class is a final class (YES)
or not (NO)
IS_DEBUG
VARCHAR2(3)
Indicates whether this Java class contains debug
information (YES) or not (NO)
SOURCE
VARCHAR2(4000)
Source designation of the Java class
SUPER
VARCHAR2(4000)
Super class of this Java class
OUTER
VARCHAR2(4000)
Outer class of this Java class if this Java class is an
inner class
See Also:
■
"DBA_JAVA_CLASSES" on page 2-184
■
"USER_JAVA_CLASSES" on page 2-273
ALL_JAVA_DERIVATIONS
ALL_JAVA_DERIVATIONS displays mapping information about Java source objects
and their derived Java class objects and Java resource objects for the Java classes
accessible to the current user.
Related Views
■
■
DBA_JAVA_DERIVATIONS displays mapping information about Java source
objects and their derived Java class objects and Java resource objects for all Java
classes in the database.
USER_JAVA_DERIVATIONS displays mapping information about Java source
objects and their derived Java class objects and Java resource objects for the Java
classes owned by the current user. This view does not display the OWNER
column.
Static Data Dictionary Views 2-53
ALL_JAVA_FIELDS
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the Java source object
SOURCE_NAME
VARCHAR2(4000)
Name of the Java source object
CLASS_INDEX
NUMBER
Index of the derived Java class object
CLASS_NAME
VARCHAR2(4000)
Name of the derived Java class object
RESOURCE_INDEX
NUMBER
Index of the derived Java resource object
RESOURCE_NAME
VARCHAR2(4000)
Name of the derived Java resource object
See Also:
■
"DBA_JAVA_DERIVATIONS" on page 2-184
■
"USER_JAVA_DERIVATIONS" on page 2-273
ALL_JAVA_FIELDS
ALL_JAVA_FIELDS displays field information about the stored Java classes
accessible to the current user.
Related Views
■
■
DBA_JAVA_FIELDS displays field information about all stored Java classes in
the database.
USER_JAVA_FIELDS displays field information about the stored Java classes
owned by the current user. This view does not display the OWNER column.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the Java class
NAME
VARCHAR2(4000)
Name of the Java class
FIELD_INDEX
NUMBER
Index of the field
FIELD_NAME
VARCHAR2(4000)
Name of the field identified by the FIELD_INDEX
column
ACCESSIBILITY
VARCHAR2(9)
Accessibility of the field:
IS_STATIC
2-54
VARCHAR2(3)
Oracle9i Database Reference
■
PUBLIC
■
PRIVATE
■
PROTECTED
Indicates whether the field is a static field (YES) or not
(NO)
ALL_JAVA_IMPLEMENTS
Column
Datatype
IS_FINAL
VARCHAR2(3)
Indicates whether the field is a final field (YES) or not
(NO)
IS_VOLATILE
VARCHAR2(3)
Indicates whether the field is volotile (YES) or not
(NO)
IS_TRANSIENT
VARCHAR2(3)
Indicates whether the field is transient (YES) or not
(NO)
ARRAY_DEPTH
NUMBER
Array depth of the type of the field
BASE_TYPE
VARCHAR2(7)
Base type of the type of the field:
FIELD_CLASS
VARCHAR2(4000)
NULL
Description
■
int
■
long
■
float
■
double
■
boolean
■
byte
■
char
■
short
■
class
Actual class name of the base object if the base type is
class
See Also:
■
"DBA_JAVA_FIELDS" on page 2-185
■
"USER_JAVA_FIELDS" on page 2-273
ALL_JAVA_IMPLEMENTS
ALL_JAVA_IMPLEMENTS describes interfaces implemented by the stored Java
classes accessible to the current user.
Related Views
■
■
DBA_JAVA_IMPLEMENTS describes interfaces implemented by all stored Java
classes in the database.
USER_JAVA_IMPLEMENTS describes interfaces implemented by the stored Java
classes owned by the current user. This view does not display the OWNER
column.
Static Data Dictionary Views 2-55
ALL_JAVA_INNERS
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the Java class
NAME
VARCHAR2(4000)
Name of the Java class
INTERFACE_INDEX
NUMBER
Index of the interfaces implemented by the Java class
INTERFACE_NAME
VARCHAR2(4000)
Name of the interface identified by the INTERFACE_
INDEX column
See Also:
■
"DBA_JAVA_IMPLEMENTS" on page 2-185
■
"USER_JAVA_IMPLEMENTS" on page 2-273
ALL_JAVA_INNERS
ALL_JAVA_INNERS displays information about inner classes referred to by the
stored Java classes accessible to the current user.
Related Views
■
■
DBA_JAVA_INNERS displays information about inner classes referred to by all
stored Java classes in the database.
USER_JAVA_INNERS displays information about inner classes referred to by
the stored Java classes owned by the current user. This view does not display
the OWNER column.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the Java class
NAME
VARCHAR2(4000)
Name of the Java class
INNER_INDEX
NUMBER
Index of the referred inner class
SIMPLE_NAME
VARCHAR2(4000)
Simple name of the referred inner class
FULL_NAME
VARCHAR2(4000)
Full name of the referred inner class
ACCESSIBILITY
VARCHAR2(9)
Accessibility of the referred inner class:
IS_STATIC
2-56
VARCHAR2(3)
Oracle9i Database Reference
■
PUBLIC
■
PRIVATE
■
PROTECTED
Indicates whether the referred inner class is declared
static in the sorce file (YES) or not (NO)
ALL_JAVA_LAYOUTS
Column
Datatype
NULL
Description
IS_FINAL
VARCHAR2(3)
Indicates whether the referred inner class is declared
final in the sorce file (YES) or not (NO)
IS_ABSTRACT
VARCHAR2(3)
Indicates whether the referred inner class is declared
abstract in the sorce file (YES) or not (NO)
IS_INTERFACE
VARCHAR2(3)
Indicates whether the referred inner class is declared
interface in the sorce file (YES) or not (NO)
See Also:
■
"DBA_JAVA_INNERS" on page 2-185
■
"USER_JAVA_INNERS" on page 2-273
ALL_JAVA_LAYOUTS
ALL_JAVA_LAYOUTS displays class layout information about the stored Java
classes accessible to the current user.
Related Views
■
■
DBA_JAVA_LAYOUTS displays class layout information about all stored Java
classes in the database.
USER_JAVA_LAYOUTS displays class layout information about the stored Java
classes owned by the current user. This view does not display the OWNER
column.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the Java class
NAME
VARCHAR2(4000)
Name of the Java class
INTERFACES
NUMBER
Number of interfaces that this Java class implements
INNER_CLASSES
NUMBER
Number of inner classes that this Java class contains
FIELDS
NUMBER
Number of locally declared fields that this Java class
contains
STATIC_FIELDS
NUMBER
Number of locally declared static fields that this Java
class contains
METHODS
NUMBER
Number of locally declared methods that this Java
class contains
STATIC_METHODS
NUMBER
Number of locally declared static methods that this
Java class contains
Static Data Dictionary Views 2-57
ALL_JAVA_METHODS
Column
Datatype
NATIVE_METHODS
NUMBER
NULL
Description
Number of locally declared native methods that this
Java class contains
See Also:
■
"DBA_JAVA_LAYOUTS" on page 2-185
■
"USER_JAVA_LAYOUTS" on page 2-274
ALL_JAVA_METHODS
ALL_JAVA_METHODS displays method information about the stored Java classes
accessible to the current user.
Related Views
■
■
DBA_JAVA_METHODS displays method information about all stored Java classes
in the database.
USER_JAVA_METHODS displays method information about the stored Java
classes owned by the current user. This view does not display the OWNER
column.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the Java class
NAME
VARCHAR2(4000)
Name of the Java class
METHOD_INDEX
NUMBER
Index of the method
METHOD_NAME
VARCHAR2(4000)
Name of the method identified by the METHOD_
INDEX column
ACCESSIBILITY
VARCHAR2(9)
Accessibility of the method:
■
PUBLIC
■
PRIVATE
■
PROTECTED
IS_STATIC
VARCHAR2(3)
Indicates whether the method is a static method (YES)
or not (NO)
IS_FINAL
VARCHAR2(3)
Indicates whether the method is a final method (YES)
or not (NO)
IS_SYNCHRONIZED
VARCHAR2(3)
Indicates whether the method is a synchronized
method (YES) or not (NO)
2-58
Oracle9i Database Reference
ALL_JAVA_NCOMPS
Column
Datatype
IS_NATIVE
VARCHAR2(3)
Indicates whether the method is a native method
(YES) or not (NO)
IS_ABSTRACT
VARCHAR2(3)
Indicates whether the method is an abstract method
(YES) or not (NO)
IS_STRICT
VARCHAR2(3)
Indicates whether the method is a strict method (YES)
or not (NO)
ARGUMENTS
NUMBER
Number of arguments of the method
THROWS
NUMBER
Number of exceptions thrown by the method
ARRAY_DEPTH
NUMBER
Array depth of the return type of the method
BASE_TYPE
VARCHAR2(7)
RETURN_CLASS
VARCHAR2(4000)
NULL
Description
Base type of the return type of the method:
■
int
■
long
■
float
■
double
■
boolean
■
byte
■
char
■
short
■
class
■
void
Actual class name of the return value if the base type
is class
See Also:
■
"DBA_JAVA_METHODS" on page 2-185
■
"USER_JAVA_METHODS" on page 2-274
ALL_JAVA_NCOMPS
ALL_JAVA_NCOMPS displays ncomp-related information about the Java classes
accessible to the current user.
Related Views
■
DBA_JAVA_NCOMPS displays ncomp-related information about all Java classes
in the database.
Static Data Dictionary Views 2-59
ALL_JAVA_RESOLVERS
■
USER_JAVA_NCOMPS displays ncomp-related information about the Java
classes owned by the current user. This view does not display the OWNER
column.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the Java class object
NAME
VARCHAR2(4000)
Name of the Java class object
SOURCE
VARCHAR2(4000)
ncomp source shown in this row
INITIALIZER
VARCHAR2(4000)
ncomp initializer shown in this row
LIBRARYFILE
VARCHAR2(4000)
ncomp library file shown in this row
LIBRARY
VARCHAR2(4000)
ncomp library shown in this row
See Also:
■
"DBA_JAVA_NCOMPS" on page 2-185
■
"USER_JAVA_NCOMPS" on page 2-274
ALL_JAVA_RESOLVERS
ALL_JAVA_RESOLVERS displays information about resolvers of the Java classes
accessible to the current user.
Related Views
■
■
DBA_JAVA_RESOLVERS displays information about resolvers of all Java classes
in the database.
USER_JAVA_RESOLVERS displays information about resolvers of the Java
classes owned by the current user. This view does not display the OWNER
column.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the Java class object
NAME
VARCHAR2(4000)
Name of the Java class object
TERM_INDEX
NUMBER
Index of the resolver term in this row
PATTERN
VARCHAR2(4000)
Resolver pattern of the resolver term identified by the
TERM_INDEX column
SCHEMA
VARCHAR2(64)
Resolver schema of the resolver term identified by the
TERM_INDEX column
2-60
Oracle9i Database Reference
ALL_JOBS
See Also:
■
"DBA_JAVA_RESOLVERS" on page 2-186
■
"USER_JAVA_RESOLVERS" on page 2-274
ALL_JAVA_THROWS
ALL_JAVA_THROWS displays information about exceptions thrown from methods
of the Java classes accessible to the current user.
Related Views
■
■
DBA_JAVA_THROWS displays information about exceptions thrown from
methods of all Java classes in the database.
USER_JAVA_THROWS displays information about exceptions thrown from
methods of the Java classes owned by the current user. This view does not
display the OWNER column.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the Java class
NAME
VARCHAR2(4000)
Name of the Java class
METHOD_INDEX
NUMBER
Index of the throwing method of the exception
METHOD_NAME
VARCHAR2(4000)
Name of the throwing method of the exception
EXCEPTION_INDEX
NUMBER
Index of the exception
EXCEPTION_CLASS
VARCHAR2(4000)
Class of the exception
See Also:
■
"DBA_JAVA_THROWS" on page 2-187
■
"USER_JAVA_THROWS" on page 2-275
ALL_JOBS
ALL_JOBS describes all jobs in the database that are accessible to the current user.
See Also: Oracle9i Database Administrator’s Guide
Static Data Dictionary Views 2-61
ALL_JOBS
Related Views
■
DBA_JOBS describes all jobs in the database.
■
USER_JOBS describes all jobs owned by the current user.
Column
Datatype
NULL
Description
JOB
NUMBER
NOT NULL
Identifier of job. Neither import/export nor repeated
executions change this value.
LOG_USER
VARCHAR2(30)
NOT NULL
Login user when the job was submitted
PRIV_USER
VARCHAR2(30)
NOT NULL
User whose default privileges apply to this job
SCHEMA_USER
VARCHAR2(30)
NOT NULL
Default schema used to parse the job
For example, if the SCHEMA_USER is SCOTT and you
submit the procedure HIRE_EMP as a job, Oracle
looks for SCOTT.HIRE_EMP
LAST_DATE
DATE
Date on which this job last successfully executed
LAST_SEC
VARCHAR2(8)
Same as LAST_DATE. This is when the last successful
execution started.
THIS_DATE
DATE
Date that this job started executing (usually null if not
executing)
THIS_SEC
VARCHAR2(8)
Same as THIS_DATE. This is when the last successful
execution started.
NEXT_DATE
DATE
NEXT_SEC
VARCHAR2(8))
Same as NEXT_DATE. This is when the last successful
execution started.
TOTAL_TIME
NUMBER
Total wall clock time spent by the system on this job,
in seconds
BROKEN
VARCHAR2(1)
Y: no attempt is made to run this job
NOT NULL
Date that this job will next be executed
N: an attempt is made to run this job
VARCHAR2(200)
FAILURES
NUMBER
Number of times this job has started and failed since
its last success
WHAT
VARCHAR2(4000)
Body of the anonymous PL/SQL block that this job
executes
NLS_ENV
VARCHAR2(4000)
Session parameters describing the NLS environment
of the job
MISC_ENV
RAW(32)
Other session parameters that apply to this job
INSTANCE
NUMBER
ID of the instance that can execute or is executing the
job. The default is 0.
2-62
Oracle9i Database Reference
NOT NULL
A date function, evaluated at the start of execution,
becomes next NEXT_DATE
INTERVAL
ALL_LIBRARIES
ALL_JOIN_IND_COLUMNS
ALL_JOIN_IND_COLUMNS describes the join conditions of bitmap join indexes to
which you have access. Bitmap join indexes are indexes built on a child table with
an index key containing columns from associated parent tables, where all of the
tables are connected through join conditions. There is one row for each join
condition.
Related Views
■
■
DBA_JOIN_IND_COLUMNS describes all join conditions exiting in the database.
USER_JOIN_IND_COLUMNS describes join conditions owned by the current
user. This view does not display the INDEX_OWNER column.
Column
Datatype
Description
INDEX_OWNER
VARCHAR2(30)
Bitmap join index owner
INDEX_NAME
VARCHAR2(30)
Name of bitmap join index
INNER_TABLE_OWNER
VARCHAR2(30)
Fact table owner
INNER_TABLE_NAME
VARCHAR2(30)
Name of the fact table
OUTER_TABLE_OWNER
VARCHAR2(30)
Dimension table owner
OUTER_TABLE_NAME
VARCHAR2(30)
Name of the dimension table
COL_NAME_INNER
VARCHAR2(4000)
Name of the fact table join column
COL_NAME_OUTER
VARCHAR2(4000)
Name of the dimension table join column
ALL_LIBRARIES
ALL_LIBRARIES describes all the libraries that are accessible to the current user.
Related Views
■
■
DBA_LIBRARIES describes all libraries in the database.
USER_LIBRARIES describes libraries owned by the current user. This view
does not display the OWNER column.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the library
LIBRARY_NAME
VARCHAR2(30)
NOT NULL
Library name
Static Data Dictionary Views 2-63
ALL_LOB_PARTITIONS
Column
Datatype
NULL
Description
FILE_SPEC
VARCHAR2(2000)
Operating system file specification associated with the
library
DYNAMIC
VARCHAR2(1)
Whether the library is dynamically loadable (YES |
NO)
STATUS
VARCHAR2(7)
Status of the library (VALID, INVALID, or N/A)
ALL_LOB_PARTITIONS
ALL_LOB_PARTITIONS displays LOB partitions contained in tables accessible to
the current user.
Related Views
■
■
DBA_LOB_PARTITIONS describes all LOB partitions in the database.
USER_LOB_PARTITIONS describes the LOB partitions owned by the current
user. This view does not display the TABLE_OWNER column.
Column
Datatype
TABLE_OWNER
VARCHAR2(30)
Owner of the table
TABLE_NAME
VARCHAR2(30)
Name of the table
COLUMN_NAME
VARCHAR2(30)
Name of the LOB column
LOB_NAME
VARCHAR2(30)
Name of the partitioned LOB item
PARTITION_NAME
VARCHAR2(30)
Name of the table partition
LOB_PARTITION_NAME
VARCHAR2(30)
Name of the LOB data partition
LOB_INDPART_NAME
VARCHAR2(30)
Name of the corresponding LOB index partition
PARTITION_POSITION
NUMBER
Position of the LOB data partition within the LOB
item
COMPOSITE
VARCHAR2(3)
Whether the partition is composite (YES | NO)
CHUNK
NUMBER
Value of the CHUNK attribute of the LOB data partition
PCTVERSION
NUMBER
Value of the PCTVERSION attribute of the LOB data
partition
CACHE
VARCHAR2(3)
Whether and how the cluster is to be cached in the
buffer cache (CACHE, NOCACHE, CACHEREADS)
IN_ROW
VARCHAR2(3)
Whether the STORAGE IN ROW attribute is enabled
for the LOB data partition
2-64
Oracle9i Database Reference
NULL
Description
ALL_LOB_SUBPARTITIONS
Column
Datatype
NULL
Description
TABLESPACE_NAME
VARCHAR2(30)
Name of the tablespace containing the LOB data
partition
INITIAL_EXTENT
VARCHAR2(40)
Size in bytes of the initial extent of the LOB data
partition
NEXT_EXTENT
VARCHAR2(40)
Size in bytes of secondary extents of the LOB data
partition
MIN_EXTENTS
VARCHAR2(40)
Minimum number of extents allowed in the segment
of the LOB data partition
MAX_EXTENTS
VARCHAR2(40)
Maximum number of extents allowed in the segment
of the LOB data partition
PCT_INCREASE
VARCHAR2(40)
Percentage increase in extent size for the LOB data
partition
FREELISTS
VARCHAR2(40)
Number of process freelists allocated in the segment
of the LOB data partition
FREELIST_GROUPS
VARCHAR2(40)
Number of freelist groups allocated in the segment of
the LOB data partition
LOGGING
VARCHAR2(7)
Logging attribute of the LOB data partition
BUFFER_POOL
VARCHAR2(7)
Default buffer pool for the LOB partition blocks
ALL_LOB_SUBPARTITIONS
ALL_LOB_SUBPARTITIONS displays partition-level attributes of LOB data
subpartitions accessible to the current user.
Related Views
■
■
DBA_LOB_SUBPARTITIONS describes all LOB subpartitions in the database.
USER_LOB_SUBPARTITIONS describes the LOB subpartitions owned by the
current user. This view does not display the TABLE_OWNER column.
Column
Datatype
TABLE_OWNER
VARCHAR2(30)
NULL
Description
Owner of the table
TABLE_NAME
VARCHAR2(30)
Name of the table
COLUMN_NAME
VARCHAR2(30)
Name of the LOB column
LOB_NAME
VARCHAR2(30)
Name of the partitioned LOB item
LOB_PARTITION_NAME
VARCHAR2(30)
Name of LOB data partition to which this LOB data
subpartition belongs
Static Data Dictionary Views 2-65
ALL_LOB_TEMPLATES
Column
Datatype
SUBPARTITION_NAME
VARCHAR2(30)
NULL
Description
Name of the table subpartition to which this LOB
subpartition corresponds
LOB_SUBPARTITION_NAME VARCHAR2(30)
Name of the LOB subpartition
LOB_INDSUBPART_NAME
Name of corresponding LOB index subpartition
VARCHAR2(30)
SUBPARTITION_POSITION NUMBER
Position of the LOB data partition within the LOB
item
CHUNK
NUMBER
Value of the CHUNK attribute of the LOB data partition
PCTVERSION
NUMBER
Value of the PCTVERSION attribute of the LOB data
partition
CACHE
VARCHAR2(3)
Whether and how the cluster is to be cached in the
buffer cache (CACHE, NOCACHE, CACHEREADS)
IN_ROW
VARCHAR2(3)
Whether the STORAGE IN ROW attribute of the LOB
data partition is enabled
TABLESPACE_NAME
VARCHAR2(30)
Name of the tablespace containing the LOB data
partition
INITIAL_EXTENT
VARCHAR2(40)
Size in bytes of the initial extent for the LOB data
partition
NEXT_EXTENT
VARCHAR2(40)
Size in bytes of secondary extents for the LOB data
partition
MIN_EXTENTS
VARCHAR2(40)
Minimum number of extents allowed in the segment
of the LOB data partition
MAX_EXTENTS
VARCHAR2(40)
Maximum number of extents allowed in the segment
of the LOB data partition
PCT_INCREASE
VARCHAR2(40)
Percentage increase in extent size for the LOB data
partition
FREELISTS
VARCHAR2(40)
Number of process freelists allocated in the segment
of the LOB data partition
FREELIST_GROUPS
VARCHAR2(40)
Number of freelist groups allocated in the segment of
the LOB data partition
LOGGING
VARCHAR2(7)
Logging attribute of the LOB data partition
BUFFER_POOL
VARCHAR2(7)
Default buffer pool to be used for the LOB data
partition blocks
ALL_LOB_TEMPLATES
ALL_LOB_TEMPLATES describes the LOB subpartition templates accessible to the
current user.
2-66
Oracle9i Database Reference
ALL_LOBS
Related Views
■
■
DBA_LOB_TEMPLATES describes all LOB subpartition templates in the
database.
USER_LOB_TEMPLATES describes the LOB subpartition templates owned by
the current user. This view does not display the USER_NAME column.
Column
Datatype
NULL
Description
USER_NAME
VARCHAR2(30)
NOT NULL
Owner of the table
TABLE_NAME
VARCHAR2(30)
NOT NULL
Name of the table
LOB_COL_NAME
VARCHAR2(4000)
SUBPARTITION_NAME
VARCHAR2(34)
NOT NULL
Name of the subpartition
LOB_SEGMENT_NAME
VARCHAR2(34)
NOT NULL
Name of the LOB segment
TABLESPACE_NAME
VARCHAR2(30)
Name of the LOB column
Tablespace name of the subpartition
See Also:
■
"DBA_LOB_TEMPLATES" on page 2-189
■
"USER_LOB_TEMPLATES" on page 2-276
ALL_LOBS
ALL_LOBS displays the large objects (LOBs) contained in tables accessible to the
current user. LOBs include binary large objects (BLOBs) and character large objects
(CLOBs). Binary files (BFILEs) are stored outside the database, so they are not
displayed by this view or the related views.
Related Views
■
■
DBA_LOBS describes all LOBs in the database.
USER_LOBS describes the LOBs owned by the current user. This view does not
display the OWNER column.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
Owner of the object containing the LOB
TABLE_NAME
VARCHAR2(30)
Name of the object containing the LOB
COLUMN_NAME
VARCHAR2(4000)
Name of the LOB column or attribute
Static Data Dictionary Views 2-67
ALL_LOG_GROUP_COLUMNS
Column
Datatype
NULL
Description
SEGMENT_NAME
VARCHAR2(30)
Name of the LOB segment
INDEX_NAME
VARCHAR2(30)
Name of the LOB index
CHUNK
NUMBER
Size (in bytes) of the LOB chunk as a unit of allocation
or manipulation
PCTVERSION
NUMBER
Maximum percentage of the LOB space used for
versioning
RETENTION
NUMBER
Maximum time duration for versioning of the LOB
space
FREEPOOLS
NUMBER
Number of freepools for this LOB segment
CACHE
VARCHAR2(10)
Whether and how the cluster is to be cached in the
buffer cache (YES, NO, CACHEREADS)
LOGGING
VARCHAR2(7)
Indicates whether changes to the LOB are logged
IN_ROW
VARCHAR2(3)
Indicates whether some of the LOBs are stored inline
with the base row
ALL_LOG_GROUP_COLUMNS
ALL_LOG_GROUP_COLUMNS describes columns that are accessible to the current
user and that are specified in log groups.
Related Views
■
■
DBA_LOG_GROUP_COLUMNS describes all columns in the database that are
specified in log groups.
USER_LOG_COLUMN_GROUPS describes columns that are owned by the current
user and that are specified in log groups.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the log group definition
LOG_GROUP_NAME
VARCHAR2(30)
NOT NULL
Name of the log group definition
TABLE_NAME
VARCHAR2(30)
NOT NULL
Name of the table with log group definition
COLUMN_NAME
VARCHAR2(4000)
NOT NULL
Name of the column or attribute of the object type
column specified in the log group definition
POSITION
NUMBER
2-68
Oracle9i Database Reference
Original position of column or attribute in the
definition of the object
ALL_METHOD_PARAMS
ALL_LOG_GROUPS
ALL_LOG_GROUPS describes log group definitions on tables accessible to the
current user.
Related Views
■
■
DBA_LOG_GROUPS describes log group definitions on tables owned by the
current users.
USER_LOG_GROUPS describes log group definitions on all tables in the
database.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the log group definition
LOG_GROUP_NAME
VARCHAR2(30)
NOT NULL
Name of the log group definition
TABLE_NAME
VARCHAR2(30)
NOT NULL
Name of the table with log group definition
ALWAYS
VARCHAR2(6)
Y indicates the log group is logged any time a row is
updated; N indicates the log group is logged any time
a member column is updated.
ALL_METHOD_PARAMS
ALL_METHOD_PARAMS describes the method parameters of the object types
accessible to the current user.
Related Views
■
■
DBA_METHOD_PARAMS describes the method parameters of all object types in
the database.
USER_METHOD_PARAMS describes the method parameters of the object types
owned by the current user. This view does not display the OWNER column.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the type
TYPE_NAME
VARCHAR2(30)
NOT NULL
Name of the type
METHOD_NAME
VARCHAR2(30)
NOT NULL
Name of the method
METHOD_NO
NUMBER
NOT NULL
For an overloaded method, a number distinguishing
this method from others of the same. Do not confuse
this number with the object ID.
Static Data Dictionary Views 2-69
ALL_METHOD_RESULTS
Column
Datatype
NULL
Description
PARAM_NAME
VARCHAR2(30)
NOT NULL
Name of the parameter
PARAM_NO
NUMBER
NOT NULL
Parameter number (position)
PARAM_MODE
VARCHAR2(6)
Mode of the parameter (IN, OUT, IN OUT)
PARAM_TYPE_MOD
VARCHAR2(7)
Whether this parameter is a REF to another object
PARAM_TYPE_OWNER
VARCHAR2(30)
Owner of the type of the parameter
PARAM_TYPE_NAME
VARCHAR2(30)
Name of the type of the parameter
CHARACTER_SET_NAME
VARCHAR2(44)
Whether the character set or the method is
fixed-length character set (CHAR_CS) or fixed-length
national character set (NCHAR_CS), or a particular
character set specified by the user
See Also:
■
"DBA_METHOD_PARAMS" on page 2-196
■
"USER_METHOD_PARAMS" on page 2-276
ALL_METHOD_RESULTS
ALL_METHOD_RESULTS describes the method results of the object types accessible
to the current user.
Related Views
■
■
DBA_METHOD_RESULTS describes the method results of all object types in the
database.
USER_METHOD_RESULTS describes the method results of the object types
owned by the current user. This view does not display the OWNER column.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the type
TYPE_NAME
VARCHAR2(30)
NOT NULL
Name of the type
METHOD_NAME
VARCHAR2(30)
NOT NULL
Name of the method
METHOD_NO
NUMBER
NOT NULL
For an overloaded method, a number distinguishing
this method from others of the same. Do not confuse
this number with the object ID.
RESULT_TYPE_MOD
VARCHAR2(7)
NOT NULL
Whether this result is a REF to another object
RESULT_TYPE_OWNER
VARCHAR2(30)
2-70
Oracle9i Database Reference
Owner of the type of the result
ALL_MVIEW_AGGREGATES
Column
Datatype
NULL
Description
RESULT_TYPE_NAME
VARCHAR2(30)
Name of the type of the result
CHARACTER_SET_NAME
VARCHAR2(44)
Whether the character set or the method is
fixed-length character set (CHAR_CS) or fixed-length
national character set (NCHAR_CS), or a particular
character set specified by the user
See Also:
■
"DBA_METHOD_RESULTS" on page 2-196
■
"USER_METHOD_RESULTS" on page 2-276
ALL_MVIEW_AGGREGATES
ALL_MVIEW_AGGREGATES describes the grouping functions (aggregate operations)
that appear in the SELECT list of materialized aggregate views accessible to the
current user.
Related Views
■
■
DBA_MVIEW_AGGREGATES describes all such grouping functions defined for all
materialized views in the database.
USER_MVIEW_AGGREGATES describes all such grouping functions defined for
all materialized views owned by the current user.
All three views exclude materialized views that reference remote tables or that
include references to a nonstatic value such as SYSDATE or USER. These views also
exclude materialized views that were created as "snapshots" prior to Oracle8i and
that were never altered to enable query rewrite.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the materialized view
MVIEW_NAME
VARCHAR2(30)
NOT NULL
Name of the materialized view
POSITION_IN_SELECT
NUMBER
NOT NULL
Ordinal position of this aggregation within the
SELECT list. For the position of nonaggregate
elements of the select list, see "ALL_MVIEW_KEYS"
on page 2-75.
CONTAINER_COLUMN
VARCHAR2(30)
NOT NULL
Name of this column in the container table
AGG_FUNCTION
VARCHAR2(8)
Aggregation function
DISTINCTFLAG
VARCHAR2(1)
Whether this aggregation is distinct (Y | N)
Static Data Dictionary Views 2-71
ALL_MVIEW_ANALYSIS
Column
Datatype
MEASURE
LONG
NULL
Description
SQL text of the measure, excluding the aggregation
function. Equal to * for COUNT(*).
ALL_MVIEW_ANALYSIS
ALL_MVIEW_ANALYSIS describes the materialized views accessible to the current
user. It provides additional information for analysis by applications. Minimal
information is displayed for materialized views that do not support query rewrite
(such as materialized views with remote master tables or nondeterministic
functions).
Related Views
■
■
DBA_MVIEW_ANALYSIS describes all such materialized views in the database.
USER_MVIEW_ANALYSIS describes all such materialized views owned by the
current user.
Note: All of the information in these views is also displayed in
ALL_MVIEWS and its related views. Oracle Corporation
recommends that you refer to ALL_MVIEWS for this information
instead of these views.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the materialized view
MVIEW_NAME
VARCHAR2(30)
NOT NULL
Name of the materialized view
MVIEW_TABLE_OWNER
VARCHAR2(30)
NOT NULL
Owner of the container table (see next column)
CONTAINER_NAME
VARCHAR2(30)
Name of the internal container in which the
materialized view data is held. Normally this is the
same as MVIEW_NAME. For materialized views created
in releases before 8.1 (or under pre-8.1 compatibility
mode), Oracle attaches the 6-byte prefix SNAP$_. If
MVIEW_NAME has more than 19 bytes, Oracle
truncates the name to 19 bytes and adds a 4-byte
sequence number as a suffix to produce a
nonambiguous CONTAINER_NAME.
LAST_REFRESH_SCN
NUMBER
System change number (SCN) of the last refresh
operation
LAST_REFRESH_DATE
DATE
SYSDATE of the last refresh
2-72
Oracle9i Database Reference
ALL_MVIEW_DETAIL_RELATIONS
Column
Datatype
NULL
Description
REFRESH_METHOD
VARCHAR2(8)
Default refresh method: FORCE, FAST, COMPLETE, or
NONE
SUMMARY
VARCHAR2(1)
Whether this materialized view includes a GROUP BY
clause or aggregation (Y | N)
FULLREFRESHTIM
NUMBER
Approximate refresh time, in seconds, for full refresh
(defined only when SUMMARY = Y)
INCREFRESHTIM
NUMBER
Approximate refresh time, in seconds, for fast refresh
(defined only when SUMMARY = Y)
CONTAINS_VIEWS
VARCHAR2(1)
Whether this materialized view contains a view in its
definition (Y | N)
UNUSABLE
VARCHAR2(1)
Whether this materialized view is UNUSABLE
(inconsistent data) (Y | N). A materialized view can be
UNUSABLE if a system failure occurs during a full
refresh.
RESTRICTED_SYNTAX
VARCHAR2(1)
Whether this materialized view had a restriction in its
defining query that limits the use of query rewrite (Y
| N). More complete information is provided by the
REWRITE_CAPABILITY column of the ALL_, DBA_,
and USER_MVIEWS views.
INC_REFRESHABLE
VARCHAR2(1)
Whether this materialized view can be fast refreshed
(Y | N)
KNOWN_STALE
VARCHAR2(1)
Whether the data contained in the materialized view
is known to be inconsistent with the master table data
because that has been updated since the last
successful refresh (Y | N)
INVALID
VARCHAR2(1)
Whether this materialized view is in an invalid state
(inconsistent metadata) (Y | N)
REWRITE_ENABLED
VARCHAR2(1)
Whether this materialized view is currently enabled
for query rewrite (Y | N)
QUERY_LEN
NUMBER
NOT NULL
Length (in bytes) of the query field
QUERY
LONG
NOT NULL
SELECT expression of the materialized view
definition
REVISION
NUMBER
Reserved for internal use
ALL_MVIEW_DETAIL_RELATIONS
ALL_MVIEW_DETAIL_RELATIONS describes the named detail relations that are
either specified in the FROM list of the subquery that defines a materialized view
accessible to the current user, or that are indirectly referenced through views in that
FROM list. Inline views in the materialized view definition are not represented in this
view or the related views.
Static Data Dictionary Views 2-73
ALL_MVIEW_JOINS
Related Views
■
■
DBA_MVIEW_DETAIL_RELATIONS describes all such detail relations defined
for all materialized views in the database.
USER_MVIEW_DETAIL_RELATIONS describes such detail relations defined for
all materialized views owned by the current user.
All three views exclude materialized views that reference remote tables or that
includes references to a nonstatic value such as SYSDATE or USER. These views also
exclude materialized views that were created as snapshots prior to Oracle8i and that
were never altered to enable query rewrite.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the materialized view
MVIEW_NAME
VARCHAR2(30)
NOT NULL
Name of the materialized view
DETAILOBJ_OWNER
VARCHAR2(30)
NOT NULL
Detail object owner
DETAILOBJ_NAME
VARCHAR2(30)
NOT NULL
Detail object name (that is, the name of a table or
view)
DETAILOBJ_TYPE
VARCHAR2(9)
TABLE, VIEW, SNAPSHOT, CONTAINER, or
UNDEFINED
DETAILOBJ_ALIAS
VARCHAR2(30)
Implicit or explicit alias for detail relation
ALL_MVIEW_JOINS
ALL_MVIEW_JOINS describes joins between two columns in the WHERE clause of
the subquery that defines a materialized view accessible to the current user.
Related Views
■
■
DBA_MVIEW_JOINS describes all such joins for all materialized views in the
database.
USER_MVIEW_JOINS describes such joins for all materialized views owned by
the current user.
All three views exclude materialized views that reference remote tables or that
includes references to a nonstatic value such as SYSDATE or USER. These views also
exclude materialized views that were created as "snapshots" prior to Oracle8i and
that were never altered to enable query rewrite.
2-74
Oracle9i Database Reference
ALL_MVIEW_KEYS
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the materialized view
MVIEW_NAME
VARCHAR2(30)
NOT NULL
Materialized view name
Note: The next 8 rows relate only to materialized join views and materialized aggregate views. They describe
the two detail objects of a materialized view join.
DETAILOBJ1_OWNER
VARCHAR2(30)
NOT NULL
Owner of the first object in the join
DETAILOBJ1_RELATION
VARCHAR2(30)
NOT NULL
Name of the first object in the join
DETAILOBJ1_COLUMN
VARCHAR2(30)
NOT NULL
Join column of the first object in the join
OPERATOR
CHAR(1)
OPERATOR_TYPE
VARCHAR2(1)
DETAILOBJ2_OWNER
VARCHAR2(30)
NOT NULL
Owner of the second object in the join
DETAILOBJ2_RELATION
VARCHAR2(30)
NOT NULL
Name of the second object in the join
DETAILOBJ2_COLUMN
VARCHAR2(30)
NOT NULL
Join column of the second object in the join
Join operator
Whether the join is an inner or outer join
ALL_MVIEW_KEYS
ALL_MVIEW_KEYS describes the columns or expressions in the SELECT list upon
which materialized views accessible to the current user are based.
Related Views
■
■
DBA_MVIEW_KEYS describes such columns and expressions for all materialized
views in the database.
USER_MVIEW_KEYS describes such columns and expressions for all
materialized views owned by the current user.
All three views exclude materialized views that reference remote tables or that
includes references to a nonstatic value such as SYSDATE or USER. These views also
exclude materialized views that were created as snapshots prior to Oracle8i and that
were never altered to enable query rewrite.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the materialized view
MVIEW_NAME
VARCHAR2(30)
NOT NULL
Materialized view name
POSITION_IN_SELECT
NUMBER
NOT NULL
Ordinal position of this key within the SELECT list
CONTAINER_COLUMN
VARCHAR2(30)
NOT NULL
Name of the column in the container table
Static Data Dictionary Views 2-75
ALL_MVIEW_LOGS
Column
Datatype
NULL
Description
DETAILOBJ_OWNER
VARCHAR2(30)
NOT NULL
Detail object owner
DETAILOBJ_NAME
VARCHAR2(30)
NOT NULL
Detail object name (for example, the name of a table
or view)
DETAILOBJ_TYPE
VARCHAR2(5)
DETAILOBJ_ALIAS
VARCHAR2(30)
DETAILOBJ_COLUMN
VARCHAR2(30)
Detail object type (VIEW | TABLE)
Implicit or explicit alias for detail relation
NOT NULL
Name of the detail relation column
ALL_MVIEW_LOGS
ALL_MVIEW_LOGS describes all materialized view logs accessible to the current
user.
Related Views
■
■
DBA_MVIEW_LOGS describes all materialized view logs in the database.
USER_MVIEW_LOGS describes all materialized view logs owned by the current
user.
Column
Datatype
NULL
Description
LOG_OWNER
VARCHAR2(30)
Owner of the materialized view log
MASTER
VARCHAR2(30)
Name of the master table or master materialized view
whose changes are logged
LOG_TABLE
VARCHAR2(30)
Name of the table where the changes to the master
table or master materialized view are logged
LOG_TRIGGER
VARCHAR2(30)
Obsolete with the release of Oracle8i and higher. Set
to NULL. Formerly, this parameter was an after-row
trigger on the master which inserted rows into the
log.
ROWIDS
VARCHAR2(3)
If YES, records rowid information
PRIMARY_KEY
VARCHAR2(3)
If YES, records primary key information
OBJECT_ID
VARCHAR2(3)
If YES, records object identifier information in an
object table
FILTER_COLUMNS
VARCHAR2(3)
If YES, records filter columns
SEQUENCE
VARCHAR2(3)
If YES, records the sequence value, which provides
additional ordering information
INCLUDE_NEW_VALUES
VARCHAR2(3)
If YES, records both old and new values. If NO,
records old values, but does not record new values.
2-76
Oracle9i Database Reference
ALL_MVIEWS
See Also:
■
"DBA_MVIEW_LOGS" on page 2-198
■
"USER_MVIEW_LOGS" on page 2-278
ALL_MVIEW_REFRESH_TIMES
ALL_MVIEW_REFRESH_TIMES describes refresh times of the materialized views
accessible to the current user.
Related Views
■
■
DBA_MVIEW_REFRESH_TIMES describes refresh times of all materialized views
in the database.
USER_MVIEW_REFRESH_TIMES describes refresh times of the materialized
views owned by the current user.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the materialized view
NAME
VARCHAR2(30)
NOT NULL
Name of the materialized view
MASTER_OWNER
VARCHAR2(30)
Owner of the master table
MASTER
VARCHAR2(30)
Name of the master table
LAST_REFRESH
DATE
The last refresh
See Also:
■
"DBA_MVIEW_REFRESH_TIMES" on page 2-198
■
"USER_MVIEW_REFRESH_TIMES" on page 2-278
ALL_MVIEWS
ALL_MVIEWS describes all materialized views accessible to the current user.
Related views
■
DBA_MVIEWS describes all materialized views in the database.
■
USER_MVIEWS describes all materialized views owned by the current user.
Static Data Dictionary Views 2-77
ALL_MVIEWS
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Schema in which the materialized view was created
MVIEW_NAME
VARCHAR2(30)
NOT NULL
Name of the materialized view
CONTAINER_NAME
VARCHAR2(30)
NOT NULL
Name of the container in which the materialized
view’s data is held. Normally this is the same as
MVIEW_NAME. For materialized views created in
releases before 8.1 (or under pre-8.1 compatibility
mode), Oracle attaches the 6-byte prefix SNAP$_. If
MVIEW_NAME has more than 19 bytes, then Oracle
truncates the name to 19 bytes and may add a 4-byte
sequence number as a suffix to produce a
nonambiguous CONTAINER_NAME.
QUERY
LONG
Query that defines the materialized view
QUERY_LEN
NUMBER(38)
Length (in bytes) of the defining query
UPDATABLE
VARCHAR2(1)
Indicates whether the materialized view is updatable
(Y) or not (N)
UPDATE_LOG
VARCHAR2(30)
For updatable materialized views, the filename of the
update log
MASTER_ROLLBACK_SEG
VARCHAR2(30)
Rollback segment for the master site or the master
materialized view site
MASTER_LINK
VARCHAR2(128)
Database link for the master site or the master
materialized view site
REWRITE_ENABLED
VARCHAR2(1)
Indicates whether rewrite is enabled (Y) or not (N)
REWRITE_CAPABILITY
VARCHAR2(9)
Indicates whether the materialized view is eligible for
rewrite, and if so, what rules must be followed:
■
■
■
2-78
Oracle9i Database Reference
NONE - Materialized view cannot be used for
rewrite, because rewrite is disallowed or
prevented
TEXTMATCH - Defining query of the materialized
view contained restrictions on the use of query
rewrite
GENERAL - Defining query of the materialized
view contained no restrictions on the use of
query rewrite, so Oracle can apply any rewrite
rule that is supported
ALL_MVIEWS
Column
Datatype
REFRESH_MODE
VARCHAR2(6)
NULL
Description
Refresh mode of the materialized view:
■
■
■
REFRESH_METHOD
VARCHAR2(8)
■
■
■
VARCHAR2(9)
COMMIT - Oracle refreshes this materialized view
when a transaction on one of the materialized
view’s masters commits
NEVER - Oracle never refreshes this materialized
view
Default method used to refresh the materialized view
(can be overridden through the API):
■
BUILD_MODE
DEMAND - Oracle refreshes this materialized view
whenever an appropriate refresh procedure is
called
COMPLETE (C) - Materialized view is completely
refreshed from the masters
FORCE (?) - Oracle performs a fast refresh if
possible, otherwise a complete refresh
FAST (F) - Oracle performs an incremental
refresh applying changes that correspond to
changes in the masters since the last refresh
NEVER (N) - User specified that Oracle should not
refresh this materialized view
Indicates how the materialized view was populated
during creation:
■
■
■
IMMEDIATE - Populated from the masters
during creation
DEFERRED - Not populated during creation.
Must be explicitly populated later by the user.
PREBUILT - Populated with an existing table
during creation. The relationship of the contents
of this prebuilt table to the materialized view’s
masters is unknown to Oracle.
Static Data Dictionary Views 2-79
ALL_MVIEWS
Column
Datatype
FAST_REFRESHABLE
VARCHAR2(18)
NULL
Description
Indicates whether the materialized view is eligible for
incremental (fast) refresh. Oracle calculates this value
statically, based on the materialized view definition
query:
■
■
■
■
■
LAST_REFRESH_TYPE
VARCHAR2(8)
NO - Materialized view is not fast refreshable,
and hence is complex
DIRLOAD - Fast refresh is supported only for
direct loads
DML - Fast refresh is supported only for DML
operations
DIRLOAD_DML - Fast refresh is supported for
both direct loads and DML operations
DIRLOAD_LIMITEDDML - Fast refresh is
supported for direct loads and a subset of DML
operations
Method used for the most recent refresh:
■
COMPLETE - Most recent refresh was complete
■
FAST - Most recent refresh was fast (incremental)
■
NA - Materialized view has not yet been
refreshed (for example, if it was created
DEFERRED)
LAST_REFRESH_DATE
DATE
Date on which the materialized view was most
recently refreshed. Blank if not yet populated.
STALENESS
VARCHAR2(19)
Relationship between the contents of the materialized
view and the contents of the materialized view’s
masters:
■
■
■
■
■
2-80
Oracle9i Database Reference
FRESH - Materialized view is a read-consistent
view of the current state of its masters
STALE - Materialized view is out of date because
one or more of its masters has changed. If the
materialized view was FRESH before it became
STALE, then it is a read-consistent view of a
former state of its masters.
UNUSABLE - Materialized view is not a
read-consistent view of its masters from any
point in time
UNKNOWN - Oracle does not know whether the
materialized view is in a read-consistent view of
its masters from any point in time (this is the
case for materialized views created on prebuilt
tables)
UNDEFINED - Materialized view has remote
masters. The concept of staleness is not defined
for such materialized views.
ALL_MVIEWS
Column
Datatype
NULL
Description
AFTER_FAST_REFRESH
VARCHAR2(19)
Specifies the staleness value that will occur if a fast
refresh is applied to this materialized view. Its values
are the same as for the STALENESS column, plus the
value NA, which is used when fast refresh is not
applicable to this materialized view.
UNKNOWN_PREBUILT
VARCHAR2(1)
Indicates whether the materialized view is prebuilt
(Y) or not (N)
UNKNOWN_PLSQL_FUNC
VARCHAR2(1)
Indicates whether the materialized view contains
PL/SQL functions (Y) or not (N)
UNKNOWN_EXTERNAL_
TABLE
VARCHAR2(1)
Indicates whether the materialized view contains
external tables (Y) or not (N)
UNKNOWN_CONSIDER_
FRESH
VARCHAR2(1)
Indicates whether the materialized view is considered
fresh (Y) or not (N)
UNKNOWN_IMPORT
VARCHAR2(1)
Indicates whether the materialized view is imported
(Y) or not (N)
COMPILE_STATE
VARCHAR2(19)
Validity of the materialized view with respect to the
objects upon which it depends:
■
■
■
USE_NO_INDEX
VARCHAR2(1)
VALID - Materialized view has been validated
without error, and no object upon which it
depends has changed since the last validation
NEEDS_COMPILE - Some object upon which the
materialized view depends has changed (other
than normal DML changes). An ALTER
MATERIALIZED VIEW...COMPILE statement is
required to validate this materialized view.
ERROR - Materialized view has been validated
with one or more errors
Indicates whether the materialized view was created
using the USING NO INDEX clause (Y) or the
materialized view was created with the default index
(N). The USING NO INDEX clause suppresses the
creation of the default index.
See Also:
■
"DBA_MVIEWS" on page 2-198
■
"USER_MVIEWS" on page 2-278
■
■
Oracle9i Replication for more information on materialized views
to support replication
Oracle9i Data Warehousing Guide for more information on
materialized views to support data warehousing
Static Data Dictionary Views 2-81
ALL_NESTED_TABLES
ALL_NESTED_TABLES
ALL_NESTED_TABLES describes the nested tables in tables accessible to the current
user.
Related Views
■
■
DBA_NESTED_TABLES describes all nested tables in the database.
USER_NESTED_TABLES describes nested tables owned by the current user. This
view does not display the OWNER column.
Column
Datatype
OWNER
VARCHAR2(30)
Owner of the nested table
TABLE_NAME
VARCHAR2(30)
Name of the nested table
TABLE_TYPE_OWNER
VARCHAR2(30)
Owner of the type of which the nested table was
created
TABLE_TYPE_NAME
VARCHAR2(30)
Name of the type of the nested table
PARENT_TABLE_NAME
VARCHAR2(30)
Name of the parent table containing the nested table
PARENT_TABLE_COLUMN
VARCHAR2(4000)
Column name of the parent table that corresponds to
the nested table
STORAGE_SPEC
VARCHAR2(30)
Whether storage for the nested table is
USER-SPECIFIED or DEFAULT
RETURN_TYPE
VARCHAR2(20)
Return type of the varray column (LOCATOR |
VALUE)
ELEMENT_SUBSTITUTABLE VARCHAR2(25)
NULL
Description
Indicates whether the nested table element is
substitutable (Y) or not (N)
ALL_OBJ_COLATTRS
ALL_OBJ_COLATTRS describes object columns and attributes contained in the
tables accessible to the current user.
Related Views
■
■
2-82
DBA_OBJ_COLATTRS describes object columns and attributes contained in all
tables in the database.
USER_OBJ_COLATTRS describes object columns and attributes contained in the
tables owned by the current user. This view does not display the OWNER
column.
Oracle9i Database Reference
ALL_OBJECT_TABLES
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
Owner of the table
TABLE_NAME
VARCHAR2(30)
Name of the table containing the object column or
attribute
COLUMN_NAME
VARCHAR2(4000)
Fully qualified name of the object column or attribute
SUBSTITUTABLE
VARCHAR2(15)
Indicates whether the column is substitutable (Y) or
not (N)
See Also:
■
"DBA_OBJ_COLATTRS" on page 2-199
■
"USER_OBJ_COLATTRS" on page 2-278
ALL_OBJECT_TABLES
ALL_OBJECT_TABLES describes all object tables accessible to the current user.
Related Views
■
■
DBA_OBJECT_TABLES describes all object tables in the database.
USER_OBJECT_TABLES describes all object tables owned by the current user.
This view does not display the OWNER column.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the table
TABLE_NAME
VARCHAR2(30)
NOT NULL
Name of the table
TABLESPACE_NAME
VARCHAR2(30)
Name of the tablespace containing the table
CLUSTER_NAME
VARCHAR2(30)
Name of the cluster, if any, to which the table belongs
IOT_NAME
VARCHAR2(30)
Name of the index-organized table, if any, to which
the overflow entry belongs
PCT_FREE
NUMBER
Minimum percentage of free space in a block
PCT_USED
NUMBER
Minimum percentage of used space in a block
INI_TRANS
NUMBER
Initial number of transactions
MAX_TRANS
NUMBER
Maximum number of transactions
INITIAL_EXTENT
NUMBER
Size (in bytes) of the initial extent
NEXT_EXTENT
NUMBER
Size (in bytes) of secondary extents
Static Data Dictionary Views 2-83
ALL_OBJECT_TABLES
Column
Datatype
NULL
Description
MIN_EXTENTS
NUMBER
Minimum number of extents allowed in the segment
MAX_EXTENTS
NUMBER
Maximum number of extents allowed in the segment
PCT_INCREASE
NUMBER
Percentage increase in extent size
FREELISTS
NUMBER
Number of process freelists allocated in this segment
FREELIST_GROUPS
NUMBER
Number of freelist groups allocated in this segment
LOGGING
VARCHAR2(3)
Logging attribute
BACKED_UP
VARCHAR2(1)
Whether the table has been backed up since last
modification
NUM_ROWS
NUMBER
Number of rows in the table
BLOCKS
NUMBER
Number of used blocks in the table
EMPTY_BLOCKS
NUMBER
Number of empty (never used) blocks in the table
AVG_SPACE
NUMBER
Average available free space in the table
CHAIN_CNT
NUMBER
Number of chained rows in the table
AVG_ROW_LEN
NUMBER
Average row length, including row overhead
AVG_SPACE_FREELIST_
BLOCKS
NUMBER
Average free space of all blocks on a freelist
NUM_FREELIST_BLOCKS
NUMBER
Number of blocks on the freelist
DEGREE
VARCHAR2(10)
Number of parallel execution processes per instance
for scanning the table
INSTANCES
VARCHAR2(10)
Number of instances across which the table is to be
scanned
CACHE
VARCHAR2(5)
Whether the cluster is to be cached in the buffer cache
(CACHE | NOCACHE)
TABLE_LOCK
VARCHAR2(8)
Whether table locking is enabled or disabled
SAMPLE_SIZE
NUMBER
Sample size used in analyzing this table
LAST_ANALYZED
DATE
Date on which this table was most recently analyzed
PARTITIONED
VARCHAR2(3)
Whether the table is partitioned (YES | NO)
IOT_TYPE
VARCHAR2(12)
If index-organized table, then IOT_TYPE is IOT or
IOT_OVERFLOW else NULL
OBJECT_ID_TYPE
VARCHAR2(16)
Whether the object ID (OID) is USER-DEFINED or
SYSTEM-GENERATED
TABLE_TYPE_OWNER
VARCHAR2(30)
NOT NULL
Owner of the type of the table
TABLE_TYPE
VARCHAR2(30)
NOT NULL
Type of the table
TEMPORARY
VARCHAR2(1)
2-84
Oracle9i Database Reference
Whether this is a temporary table
ALL_OBJECTS
Column
Datatype
NULL
Description
SECONDARY
VARCHAR2(1)
Whether the object table is a secondary object created
by the ODCIIndexCreate method of the Oracle8i Data
Cartridge (Y | N)
NESTED
VARCHAR2(3)
Whether the table a nested table
BUFFER_POOL
VARCHAR2(7)
Default buffer pool to be used for table blocks
ROW_MOVEMENT
VARCHAR2(8)
Whether partitioned row movement is ENABLED or
DISABLED
GLOBAL_STATS
VARCHAR2(3)
For partitioned object tables, whether statistics were
collected for the table as a whole (YES) or were
estimated from statistics on underlying partitions and
subpartitions (NO).
USER_STATS
VARCHAR2(3)
Whether statistics were entered directly by the user
DURATION
VARCHAR2(15)
Indicates the duration of a temporary table:
■
■
SYS$SESSION: the rows are preserved for the
duration of the session
SYS$TRANSACTION: the rows are deleted after
COMMIT
Null for a permanent table
SKIP_CORRUPT
VARCHAR2(8)
Whether Oracle ignores blocks marked corrupt
during table and index scans (ENABLED) or raises an
error (DISABLED). To enable this feature, run the
DBMS_REPAIR.SKIP_CORRUPT_BLOCKS procedure.
MONITORING
VARCHAR2(3)
Whether the table has the MONITORING attribute set
ALL_OBJECTS
ALL_OBJECTS describes all objects accessible to the current user.
Related Views
■
■
DBA_OBJECTS describes all objects in the database.
USER_OBJECTS describes all objects owned by the current user. This view does
not display the OWNER column.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the object
OBJECT_NAME
VARCHAR2(30)
NOT NULL
Name of the object
SUBOBJECT_NAME
VARCHAR2(30)
Name of the subobject (for example, partition)
Static Data Dictionary Views 2-85
ALL_OPANCILLARY
Column
Datatype
NULL
Description
OBJECT_ID
NUMBER
NOT NULL
Dictionary object number of the object
DATA_OBJECT_ID
NUMBER
Dictionary object number of the segment that contains
the object
Note: OBJECT_ID and DATA_OBJECT_ID display
data dictionary metadata. Do not confuse these
numbers with the unique 16-byte object identifier
(object ID) that Oracle assigns to row objects in object
tables in the system.
OBJECT_TYPE
Type of the object (such as TABLE, INDEX)
VARCHAR2(15)
CREATED
DATE
NOT NULL
Timestamp for the creation of the object
LAST_DDL_TIME
DATE
NOT NULL
Timestamp for the last modification of the object
resulting from a DDL command (including grants and
revokes)
TIMESTAMP
VARCHAR2(20)
Timestamp for the specification of the object
(character data)
STATUS
VARCHAR2(7)
Status of the object (VALID, INVALID, or N/A)
TEMPORARY
VARCHAR2(1)
Whether the object is temporary (the current session
can see only data that it placed in this object itself)
GENERATED
VARCHAR2(1)
Was the name of this object system generated? (Y|N)
SECONDARY
VARCHAR2(1)
Whether this is a secondary object created by the
ODCIIndexCreate method of the Oracle9i Data
Cartridge (Y | N)
ALL_OPANCILLARY
ALL_OPANCILLARY describes operators whose bindings are ancillary to other
(primary) operators.
Related Views
■
■
Column
DBA_OPANCILLARY provides such information about all operators in the
database.
USER_OPANCILLARY provides such information about operators owned by the
current user.
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the ancillary operator
OPERATOR_NAME
VARCHAR2(30)
NOT NULL
Name of the ancillary operator
2-86
Oracle9i Database Reference
ALL_OPBINDINGS
Column
Datatype
NULL
Description
BINDING#
NUMBER
NOT NULL
Binding number the of ancillary operator
PRIMOP_OWNER
VARCHAR2(30)
NOT NULL
Owner of the primary operator
PRIMOP_NAME
VARCHAR2(30)
NOT NULL
Name of the primary operator
PRIMOP_BIND#
NUMBER
NOT NULL
Binding number of the primary operator
ALL_OPARGUMENTS
ALL_OPARGUMENTS describes arguments for each operator binding accessible to the
current user.
Related Views
■
■
DBA_OPARGUMENTS describes arguments of all operator bindings in the
database.
USER_OPARGUMENTS describes arguments of all operator bindings owned by
the current user.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the operator argument
OPERATOR_NAME
VARCHAR2(30)
NOT NULL
Name of the operator argument
BINDING#
NUMBER
NOT NULL
Binding number of the operator argument
POSITION
NUMBER
NOT NULL
Position of the operator argument (1, 2, 3, ...)
ARGUMENT_TYPE
VARCHAR2(61)
Datatype of the operator argument
ALL_OPBINDINGS
ALL_OPBINDINGS describes operator bindings accessible to the current user.
Related Views
■
■
DBA_OPBINDINGS describes bindings of all operators in the database.
USER_OPBINDINGS describes bindings of all operators owned by the current
user.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the operator
Static Data Dictionary Views 2-87
ALL_OPERATOR_COMMENTS
Column
Datatype
NULL
Description
OPERATOR_NAME
VARCHAR2(30)
NOT NULL
Name of the operator
BINDING#
NUMBER
NOT NULL
Binding number of the operator
FUNCTION_NAME
VARCHAR2(92)
Name of the binding function or method as specified
by the user
RETURN_SCHEMA
VARCHAR2(30)
If the return type of the binding is an object type, the
schema of the type
RETURN_TYPE
VARCHAR2(30)
Name of the return type
IMPLEMENTATION_TYPE_
SCHEMA
VARCHAR2(30)
If the operator was created WITH INDEX CONTEXT,
SCAN CONTEXT, this column displays the schema of
the implementation type used by the functional
implementation of the operator as a scan context.
(Blank if the operator was created without this
syntax.)
See Also: the CREATE OPERATOR statement in
Oracle9i SQL Reference
IMPLEMENTATION_TYPE
If the operator was created WITH INDEX CONTEXT,
SCAN CONTEXT, this column displays the name of the
implementation type used by the functional
implementation of the operator as a scan context.
(Blank if the operator was created without this
syntax.)
VARCHAR2(30)
See Also: the CREATE OPERATOR statement in
Oracle9i SQL Reference
ALL_OPERATOR_COMMENTS
ALL_OPERATOR_COMMENTS lists all comments for user-defined operators accessible
to the current user.
Related Views
■
■
DBA_OPERATOR_COMMENTS lists all comments for user-defined operators in the
database.
USER_OPERATOR_COMMENTS lists all comments for user-defined operators
owned by the current user.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the user-defined operator
OPERATOR_NAME
VARCHAR2(30)
NOT NULL
Name of the user-defined operator
COMMENTS
VARCHAR2(4000)
2-88
Oracle9i Database Reference
Comment for the user-defined operator
ALL_OUTLINE_HINTS
See Also:
■
"DBA_OPERATOR_COMMENTS" on page 2-201
■
"USER_OPERATOR_COMMENTS" on page 2-279
ALL_OPERATORS
ALL_OPERATORS describes operators accessible to the current user.
Related Views
■
DBA_OPERATORS describes all operators in the database.
■
USER_OPERATORS describes all operators owned by the current user.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the operator
OPERATOR_NAME
VARCHAR2(30)
NOT NULL
Name of the operator
NUMBER_OF_BINDS
NUMBER
NOT NULL
Number of bindings associated with the operator
See Also:
■
"DBA_OPERATORS" on page 2-201
■
"USER_OPERATORS" on page 2-280
ALL_OUTLINE_HINTS
ALL_OUTLINE_HINTS describes the set of hints stored in outlines accessible to the
current user.
Related Views
■
■
DBA_OUTLINE_HINTS describes such hints for all outlines in the database. This
is the only one of the three views that displays the OWNER column.
USER_OUTLINE_HINTS describes such hints for all outlines owned by the
current user.
Column
Datatype
NAME
VARCHAR2(30)
NULL
Description
Name of the outline
Static Data Dictionary Views 2-89
ALL_OUTLINES
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
Name of the user who created the outline
NODE
NUMBER
ID of the query or subquery to which the hint applies.
The top-level query is labeled 1. Subqueries are
assigned sequentially numbered labels, starting with
2.
STAGE
NUMBER
Outline hints can be applied at three different stages
during the compilation process. This column indicates
the stage at which this hint was applied.
JOIN_POS
NUMBER
Position of the table in the join order. The value is 0
for all hints except access method hints, which
identify a table to which the hint and the join position
apply.
HINT
VARCHAR2(512)
Text of the hint
ALL_OUTLINES
ALL_OUTLINES describes all stored outlines accessible to the current user.
Related Views
■
■
DBA_OUTLINES describes all stored outlines in the database. This is the only
one of the three views that displays the OWNER column.
USER_OUTLINES describes all stored outlines owned by the current user.
Column
Datatype
NAME
VARCHAR2(30)
User-specified or generated name of the stored
outline. The name must be of a form that can be
expressed in SQL.
OWNER
VARCHAR2(30)
Name of the user who created the outline
CATEGORY
VARCHAR2(30)
User-defined name of the category to which this
outline belongs
USED
VARCHAR2(9)
Whether the outline has ever been used (USED,
UNUSED, or UNDEFINED)
TIMESTAMP
DATE
Timestamp of outline creation
VERSION
VARCHAR2(64)
Oracle version that created the outline
SQL_TEXT
LONG
SQL text of the query, including any hints that were a
part of the original statement. If bind variables are
included, the variable names are stored as SQL text,
not the values that are assigned to the variables.
2-90
Oracle9i Database Reference
NULL
Description
ALL_PART_COL_STATISTICS
Column
Datatype
NULL
Description
Note: This field may contain sensitive information
about your database or application. Therefore, use
discretion when granting SELECT or VIEW object
privileges on these views.
ALL_PART_COL_STATISTICS
ALL_PART_COL_STATISTICS provides column statistics and histogram
information for table partitions accessible to the current user.
Related Views
■
■
DBA_PART_COL_STATISTICS provides such information for all table
partitions in the database.
USER_PART_COL_STATISTICS provides such information for all partitions of
tables owned by the current user. This view does not display the OWNER
column.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the partitioned table
TABLE_NAME
VARCHAR2(30)
NOT NULL
Name of the table
PARTITION_NAME
VARCHAR2(30)
COLUMN_NAME
VARCHAR2(30)
NUM_DISTINCT
NUMBER
Number of distinct values in the column
LOW_VALUE
RAW(32)
Low value in the column
HIGH_VALUE
RAW(32)
High value in the column
DENSITY
NUMBER
Density of the column
NUM_NULLS
NUMBER
Number of nulls in the column
NUM_BUCKETS
NUMBER
Number of buckets in histogram for the column
SAMPLE_SIZE
NUMBER
Sample size used in analyzing this column
LAST_ANALYZED
DATE
Date on which this column was most recently
analyzed
GLOBAL_STATS
VARCHAR2(3)
Indicates whether column statistics were collected for
the partition as a whole (YES) or were estimated from
statistics on underlying subpartitions (NO).
Name of the table partition
NOT NULL
Name of the column
Static Data Dictionary Views 2-91
ALL_PART_HISTOGRAMS
Column
Datatype
NULL
Description
USER_STATS
VARCHAR2(3)
Whether the statistics were entered directly by the
user
AVG_COL_LEN
NUMBER
Average length of the column, in bytes
ALL_PART_HISTOGRAMS
ALL_PART_HISTOGRAMS provides the histogram data (endpoints per histogram)
for histograms on table partitions accessible to the current user.
Note: These views are populated only if you collect statistics on
the index using the ANALYZE statement or the DBMS_STATS
package.
Related Views
■
■
DBA_PART_HISTOGRAMS provides such information for all table partitions in
the database.
USER_PART_HISTOGRAMS provides such information for all partitions of tables
owned by the current user. This view does not display the OWNER column.
Column
Datatype
OWNER
VARCHAR2(30)
Owner of the table
TABLE_NAME
VARCHAR2(30)
Name of the table
PARTITION_NAME
VARCHAR2(30)
Name of the table partition
COLUMN_NAME
VARCHAR2(30)
Name of the column
BUCKET_NUMBER
NUMBER
Bucket number of the histogram
ENDPOINT_VALUE
NUMBER
Normalized endpoint values for this bucket
ENDPOINT_ACTUAL_VALUE VARCHAR2(1000)
NULL
Description
Actual (not normalized) string value of the endpoint
for this bucket
ALL_PART_INDEXES
ALL_PART_INDEXES describes the object-level partitioning information for the
partitioned indexes accessible to the current user.
2-92
Oracle9i Database Reference
ALL_PART_INDEXES
Related Views
■
■
DBA_PART_INDEXES describes the object-level partitioning information for all
partitioned indexes in the database.
USER_PART_INDEXES describes the object-level partitioning information for
the partitioned indexes owned by the current user. This view does not display
the OWNER column.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the partitioned index
INDEX_NAME
VARCHAR2(30)
NOT NULL
Name of the partitioned index
TABLE_NAME
VARCHAR2(30)
NOT NULL
Name of the partitioned table
PARTITIONING_TYPE
VARCHAR2(7)
RANGE, HASH, SYSTEM, or UNKNOWN
SUBPARTITIONING_TYPE
VARCHAR2(7)
HASH, SYSTEM, or NONE
PARTITION_COUNT
NUMBER
NOT NULL
Number of partitions in this index
DEF_SUBPARTITION_
COUNT
NUMBER
NOT NULL
For a composite-partitioned index, the default
number of subpartitions, if specified
PARTITIONING_KEY_
COUNT
NUMBER
NOT NULL
Number of columns in the partitioning key
SUBPARTITIONING_KEY_
COUNT
NUMBER
NOT NULL
For a composite-partitioned index, the number of
columns in the subpartitioning key
LOCALITY
VARCHAR2(6)
Whether this partitioned index is LOCAL or GLOBAL
ALIGNMENT
VARCHAR2(12)
Whether this partitioned index is PREFIXED or
NON-PREFIXED
DEF_TABLESPACE_NAME
VARCHAR2(30)
For a local index, the default tablespace to be used
when adding or splitting a table partition
DEF_PCT_FREE
NUMBER
NOT NULL
For a local index, the default PCTFREE value to be
used when adding a table partition
DEF_INI_TRANS
NUMBER
NOT NULL
For a local index, the default INITRANS to be used
when adding a table partition
DEF_MAX_TRANS
NUMBER
NOT NULL
For a local index, the default MAXTRANS to be used
when adding a table partition
DEF_INITIAL_EXTENT
VARCHAR2(40)
NOT NULL
For a local index, the default INITIAL value to be
used when adding a table partition, or DEFAULT if no
INITIAL value was specified
DEF_NEXT_EXTENT
VARCHAR2(40)
NOT NULL
For a local index, the default NEXT, or DEFAULT if no
NEXT value was specified
Static Data Dictionary Views 2-93
ALL_PART_KEY_COLUMNS
Column
Datatype
NULL
Description
DEF_MIN_EXTENTS
VARCHAR2(40)
NOT NULL
For a local index, the default MINEXTENTS value to be
used when adding a table partition, or DEFAULT if no
MINEXTENTS value was specified
DEF_MAX_EXTENTS
VARCHAR2(40)
NOT NULL
For a local index, the default MAXEXTENTS value to be
used when adding a table partition, or DEFAULT if no
MAXEXTENTS value was specified
DEF_PCT_INCREASE
VARCHAR2(40)
NOT NULL
For a local index, the default PCTINCREASE value to
be used when adding a table partition, or DEFAULT if
no PCTINCREASE value was specified
DEF_FREELISTS
NUMBER
NOT NULL
For a local index, the default FREELISTS value to be
used when adding a table partition, or DEFAULT if no
FREELISTS value was specified
DEF_FREELIST_GROUPS
NUMBER
NOT NULL
For a local index, the default FREELIST GROUPS
value to be used when adding a table partition, or
DEFAULT if no FREELIST GROUPS value was
specified
DEF_LOGGING
VARCHAR2(7)
For a local index, the default LOGGING attribute to be
used when adding a table partition, or DEFAULT if no
LOGGING attribute was specified
DEF_BUFFER_POOL
VARCHAR2(7)
For a local index, the default buffer pool to be used
when adding a table partition
DEF_PARAMETERS
VARCHAR2(1000)
Default parameter string for domain indexes
See Also:
■
"DBA_PART_INDEXES" on page 2-202
■
"USER_PART_INDEXES" on page 2-280
ALL_PART_KEY_COLUMNS
ALL_PART_KEY_COLUMNS describes the partitioning key columns for the
partitioned objects accessible to the current user.
Related Views
■
■
2-94
DBA_PART_KEY_COLUMNS describes the partitioning key columns for all
partitioned objects in the database.
USER_PART_KEY_COLUMNS describes the partitioning key columns for the
partitioned objects owned by the current user. This view does not display the
OWNER column.
Oracle9i Database Reference
ALL_PART_LOBS
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
Owner of the partitioned table or index
NAME
VARCHAR2(30)
Name of the partitioned table or index
OBJECT_TYPE
CHAR(5)
Object type:
■
TABLE
■
INDEX
COLUMN_NAME
VARCHAR2(30)
Name of the column
COLUMN_POSITION
NUMBER
Position of the column within the partitioning key
See Also:
■
"DBA_PART_KEY_COLUMNS" on page 2-203
■
"USER_PART_KEY_COLUMNS" on page 2-281
ALL_PART_LOBS
ALL_PART_LOBS provides table-level information about partitioned LOBs that are
accessible to the current user, including default attributes for LOB data partitions.
Related Views
■
■
DBA_PART_LOBS provides such information for all partitioned LOBs in the
database.
USER_PART_LOBS provides such information for all partitioned LOBs owned
by the current user. This view does not display the OWNER column.
Column
Datatype
NULL
Description
TABLE_OWNER
VARCHAR2(30)
NOT NULL
Owner of the partitioned table containing LOB(s)
TABLE_NAME
VARCHAR2(30)
NOT NULL
Name of the partitioned table containing LOB(s)
COLUMN_NAME
VARCHAR2(30)
NOT NULL
Name of the LOB column
LOB_NAME
VARCHAR2(30)
NOT NULL
Name of the partitioned LOB
LOB_INDEX_NAME
VARCHAR2(30)
NOT NULL
Name of the partitioned LOB index
DEF_CHUNK
NUMBER
NOT NULL
Default value of CHUNK for a LOB data partition to be
used when adding a partition
DEF_PCTVERSION
NUMBER
NOT NULL
Default value of PCTVERSION for a LOB data
partition to be used when adding a partition
Static Data Dictionary Views 2-95
ALL_PART_TABLES
Column
Datatype
NULL
Description
DEF_CACHE
VARCHAR2(3)
Whether and how the cluster is to be cached by
default in the buffer cache (CACHE, NOCACHE,
CACHEREADS)
DEF_IN_ROW
VARCHAR2(3)
Whether LOB data < 4000 bytes is stored in the row
(inline)—that is, whether ENABLE STORAGE IN ROW
was specified when the LOB column was created or
last altered
DEF_TABLESPACE_NAME
VARCHAR2(30)
Default tablespace for a LOB data partition to be used
when adding a partition
DEF_INITIAL_EXTENT
VARCHAR2(40)
Default value of INITIAL for a LOB data partition to
be used when adding a partition
DEF_NEXT_EXTENT
VARCHAR2(40)
Default value of NEXT for a LOB data partition to be
used when adding a partition
DEF_MIN_EXTENTS
VARCHAR2(40)
Default value of MINEXTENT for a LOB data partition
to be used when adding a partition
DEF_MAX_EXTENTS
VARCHAR2(40)
Default value of MAXEXTENTS for a LOB data
partition to be used when adding a partition
DEF_PCT_INCREASE
VARCHAR2(40)
Default value of PCTINCREASE for a LOB data
partition to be used when adding a partition
DEF_FREELISTS
VARCHAR2(40)
Default value of FREELISTS for a LOB data partition
to be used when adding a partition
DEF_FREELIST_GROUPS
VARCHAR2(40)
Default value of FREELIST GROUPS for a LOB data
partition to be used when adding a partition
DEF_LOGGING
VARCHAR2(7)
Default LOGGING attribute for a LOB data partition to
be used when adding a partition
DEF_BUFFER_POOL
VARCHAR2(7)
Default buffer pool for a LOB data partition to be
used when adding a partition
ALL_PART_TABLES
ALL_PART_TABLES describes the object-level partitioning information for the
partitioned tables accessible to the current user.
Related Views
■
■
2-96
DBA_PART_TABLES describes the object-level partitioning information for all
partitioned tables in the database.
USER_PART_TABLES describes the object-level partitioning information for the
partitioned tables owned by the current user. This view does not display the
OWNER column.
Oracle9i Database Reference
ALL_PART_TABLES
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
Owner of the partitioned table
TABLE_NAME
VARCHAR2(30)
Name of the partitioned table
PARTITIONING_TYPE
VARCHAR2(7)
Type of partitioning (RANGE | HASH | SYSTEM |
LIST)
SUBPARTITIONING_TYPE
VARCHAR2(7)
Type of subpartitioning (NONE | HASH | SYSTEM |
LIST)
PARTITION_COUNT
NUMBER
Number of partitions in this table
DEF_SUBPARTITION_
COUNT
NUMBER
For a composite-partitioned table, the default number
of subpartitions, if specified
PARTITIONING_KEY_
COUNT
NUMBER
Number of columns in the partitioning key
SUBPARTITIONING_KEY_
COUNT
NUMBER
For a composite-partitioned table, the number of
columns in the subpartitioning key
DEF_TABLESPACE_NAME
VARCHAR2(30)
Default tablespace to be used when adding a partition
DEF_PCT_FREE
NUMBER
Default value of PCTFREE to be used when adding a
partition
DEF_PCT_USED
NUMBER
Default value of PCTUSED to be used when adding a
partition
DEF_INI_TRANS
NUMBER
Default value of INITRANS to be used when adding a
partition
DEF_MAX_TRANS
NUMBER
Default value of MAXTRANS to be used when adding a
partition
DEF_INITIAL_EXTENT
VARCHAR2(40)
Default value of INITIAL to be used when adding a
partition. DEFAULT if INITIAL was not specified.
DEF_NEXT_EXTENT
VARCHAR2(40)
Default value of NEXT to be used when adding a
partition. DEFAULT if NEXT was not specified.
DEF_MIN_EXTENTS
VARCHAR2(40)
Default value of MINEXTENTS to be used when
adding a partition. DEFAULT if MINEXTENTS was not
specified.
DEF_MAX_EXTENTS
VARCHAR2(40)
Default value of MAXEXTENTS to be used when
adding a partition. DEFAULT if MAXEXTENTS was not
specified.
DEF_PCT_INCREASE
VARCHAR2(40)
Default value of PCTINCREASE to be used when
adding a partition. DEFAULT if PCTINCREASE was
not specified.
DEF_FREELISTS
NUMBER
Default value of FREELISTS to be used when adding
a partition
DEF_FREELIST_GROUPS
NUMBER
Default value of FREELIST GROUPS to be used when
adding a partition
Static Data Dictionary Views 2-97
ALL_PARTIAL_DROP_TABS
Column
Datatype
NULL
Description
DEF_LOGGING
VARCHAR2(7)
Default logging attribute to be used when adding a
partition (NONE | YES | NO)
DEF_COMPRESSION
VARCHAR2(8)
Default compression to be used when adding a
partition (NONE | ENABLED | DISABLED)
DEF_BUFFER_POOL
VARCHAR2(7)
Default buffer pool to be used when adding a
partition (DEFAULT | KEEP | RECYCLE)
See Also:
■
"DBA_PART_TABLES" on page 2-203
■
"USER_PART_TABLES" on page 2-281
ALL_PARTIAL_DROP_TABS
ALL_PARTIAL_DROP_TABS describes tables accessible to the current user that have
partially completed DROP COLUMN operations. Such operations might have been
interrupted by the user or by a system crash.
Related Views
■
■
DBA_PARTIAL_DROP_TABS describes all tables in the database that have
partially completed DROP COLUMN operations.
USER_PARTIAL_DROP_TABS describes tables in the schema of the current user
that have partially completed DROP COLUMN operations. This view does not
display the OWNER column.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the object
TABLE_NAME
VARCHAR2(30)
NOT NULL
Name of the table
ALL_PENDING_CONV_TABLES
ALL_PENDING_CONV_TABLES describes the pending conversion tables (tables
which are not upgraded to the latest type version) accessible to the current user.
Related Views
■
2-98
DBA_PENDING_CONV_TABLES describes all pending conversion tables in the
database.
Oracle9i Database Reference
ALL_POLICIES
■
USER_PENDING_CONV_TABLES describes the pending conversion tables
owned by the current user. This view does not display the OWNER column.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the table
TABLE_NAME
VARCHAR2(30)
NOT NULL
Name of the table
See Also:
■
"DBA_PENDING_CONV_TABLES" on page 2-203
■
"USER_PENDING_CONV_TABLES" on page 2-282
ALL_POLICIES
ALL_POLICIES describes the security policies on the synonyms, tables, and views
accessible to the current user.
Related Views
■
■
DBA_POLICIES describes all security policies in the database.
USER_POLICIES describes the security policies on the synonyms, tables, and
views owned by the current user. This view does not display the OBJECT_
OWNER column.
Column
Datatype
NULL
Description
OBJECT_OWNER
VARCHAR2(30)
Owner of the synonym, table, or view
OBJECT_NAME
VARCHAR2(30)
Name of the synonym, table, or view
POLICY_GROUP
VARCHAR2(30)
Name of the policy group
POLICY_NAME
VARCHAR2(30)
Name of the policy
PF_OWNER
VARCHAR2(30)
Owner of the policy function
PACKAGE
VARCHAR2(30)
Name of the package containing the policy function
FUNCTION
VARCHAR2(30)
Name of the policy function
SEL
VARCHAR2(3)
Indicates whether the policy is applied to query on
the object (YES) or not (NO)
INS
VARCHAR2(3)
Indicates whether the policy is applied to insert on
the object (YES) or not (NO)
Static Data Dictionary Views 2-99
ALL_POLICY_CONTEXTS
Column
Datatype
NULL
Description
UPD
VARCHAR2(3)
Indicates whether the policy is applied to update on
the object (YES) or not (NO)
DEL
VARCHAR2(3)
Indicates whether the policy is applied to delete on
the object (YES) or not (NO)
CHK_OPTION
VARCHAR2(3)
Indicates whether the check option is enforced for the
policy (YES) or not (NO)
ENABLE
VARCHAR2(3)
Indicates whether the policy is enabled (YES) or
disabled (NO)
STATIC_POLICY
VARCHAR2(3)
Indicates whether the policy is static (YES) or not (NO)
See Also:
■
"DBA_POLICIES" on page 2-204
■
"USER_POLICIES" on page 2-282
■
■
Oracle9i Database Concepts for information on security policies
and fine-grained access control
The DBMS_RLS package in Oracle9i Supplied PL/SQL Packages
and Types Reference for information on administering security
policies
ALL_POLICY_CONTEXTS
ALL_POLICY_CONTEXTS describes the driving contexts defined for the synonyms,
tables, and views accessible to the current user.
Related Views
■
■
DBA_POLICY_CONTEXTS describes all driving contexts in the database.
USER_POLICY_CONTEXTS describes the driving contexts defined for the
synonyms, tables, and views owned by the current user. This view does not
display the OBJECT_OWNER column.
Column
Datatype
OBJECT_OWNER
VARCHAR2(30)
Owner of the synonym, table, or view
OBJECT_NAME
VARCHAR2(30)
Name of the synonym, table, or view
NAMESPACE
VARCHAR2(30)
Namespace of the driving context
2-100 Oracle9i Database Reference
NULL
Description
ALL_PROCEDURES
Column
Datatype
ATTRIBUTE
VARCHAR2(30)
NULL
Description
Attribute of the driving context
See Also:
■
"DBA_POLICY_CONTEXTS" on page 2-204
■
"USER_POLICY_CONTEXTS" on page 2-282
ALL_POLICY_GROUPS
ALL_POLICY_GROUPS describes the policy groups defined for the synonyms,
tables, and views accessible to the current user.
Related Views
■
■
Column
DBA_POLICY_GROUPS describes all policy groups in the database.
USER_POLICY_GROUPS describes the policy groups defined for the synonyms,
tables, and views owned by the current user. This view does not display the
OBJECT_OWNER column.
Datatype
NULL
Description
OBJECT_OWNER
VARCHAR2(30)
Owner of the synonym, table, or view
OBJECT_NAME
VARCHAR2(30)
Name of the synonym, table, or view
POLICY_GROUP
VARCHAR2(30)
Name of the policy group
See Also:
■
"DBA_POLICY_GROUPS" on page 2-204
■
"USER_POLICY_GROUPS" on page 2-282
ALL_PROCEDURES
ALL_PROCEDURES lists all functions and procedures, along with associated
properties. For example, ALL_PROCEDURES indicates whether or not a function is
pipelined, parallel enabled or an aggregate function. If a function is pipelined or an
aggregate function, the associated implementation type (if any) is also identified.
Static Data Dictionary Views 2-101
ALL_PROPAGATION
Related Views
■
■
DBA_PROCEDURES lists all functions and procedures, along with associated
properties.
USER_PROCEDURES lists all functions and procedures, along with associated
properties. It does not contain the OWNER column.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the procedure
OBJECT_NAME
VARCHAR2(30)
NOT NULL
Name of the object: top-level function, procedure, or
package name
PROCEDURE_NAME
VARCHAR2(30)
Name of the procedure
AGGREGATE
VARCHAR2(3)
Indicates whether the procedure is an aggregate
function (YES) or not (NO)
PIPELINED
VARCHAR2(3)
Indicates whether the procedure is a pipelined table
function (YES) or not (NO)
IMPLTYPEOWNER
VARCHAR2(30)
Name of the owner of the implementation type, if any
IMPLTYPENAME
VARCHAR2(30)
Name of the implementation type, if any
PARALLEL
VARCHAR2(3)
Indicates whether the procedure or function is
parallel-enabled (YES) or not (NO)
ALL_PROPAGATION
ALL_PROPAGATION displays information about the Streams propagations that have
a source queue accessible to the current user.
Related View
DBA_PROPAGATION displays information about all Streams propagations in the
database.
Column
Datatype
NULL
Description
PROPAGATION_NAME
VARCHAR2(30)
NOT NULL
Name of the Streams propagation
SOURCE_QUEUE_OWNER
VARCHAR2(30)
Owner of the source queue of the propagation
SOURCE_QUEUE_NAME
VARCHAR2(30)
Name of the source queue of the propagation
DESTINATION_QUEUE_
OWNER
VARCHAR2(30)
Owner of the destination queue of the propagation
DESTINATION_QUEUE_
NAME
VARCHAR2(30)
Name of the destination queue of the propagation
2-102 Oracle9i Database Reference
ALL_QUEUE_TABLES
Column
Datatype
NULL
Description
DESTINATION_DBLINK
VARCHAR2(128)
Database link to propagate events from the source
queue to the destination queue
RULE_SET_OWNER
VARCHAR2(30)
Propagation rule set owner
RULE_SET_NAME
VARCHAR2(30)
Propagation rule set name
See Also: "DBA_PROPAGATION" on page 2-205
ALL_PUBLISHED_COLUMNS
ALL_PUBLISHED_COLUMNS describes all existing source table columns for which
users have privileges.
Related Views
■
■
DBA_PUBLISHED_COLUMNS describes all existing source column tables.
USER_PUBLISHED_COLUMNS describes all existing source table columns for
which a user has privileges.
Column
Datatype
Description
CHANGE_SET_NAME
VARCHAR2(30)
Name of the change set
SOURCE_SCHEMA_NAME
VARCHAR2(30)
Table owner in the source system
SOURCE_TABLE_NAME
VARCHAR2(31)
Table name in the source system
PUB_ID
NUMBER
Publication identifier (change table object number)
COLUMN_NAME
VARCHAR2(30)
Column name
DATA_TYPE
VARCHAR2(30)
Column datatype
DATA_LENGTH
NUMBER
Column length (in bytes)
DATA_PRECISION
NUMBER
Decimal precision for NUMBER datatype; binary precision for FLOAT
datatype; NULL for all other datatypes
DATA_SCALE
NUMBER
Digits to the right of a decimal point in a number
NULLABLE
CHAR(1)
Nulls allowed (Y |N)?
ALL_QUEUE_TABLES
ALL_QUEUE_TABLES describes the queues in the queue tables accessible to the
current user.
Static Data Dictionary Views 2-103
ALL_QUEUE_TABLES
Related Views
■
■
DBA_QUEUE_TABLES describes the queues in all queue tables in the database.
USER_QUEUE_TABLES describes the queues in the queue tables created in the
current user’s schema. This view does not display the OWNER column.
Column
Datatype
OWNER
VARCHAR2(30)
NULL
Description
Schema of the queue table
QUEUE_TABLE
VARCHAR2(30)
Name of the queue table
TYPE
VARCHAR2(7)
Type of user data:
■
RAW - Raw type
■
OBJECT - User-defined object type
■
VARIANT - Variant type (internal use only)
OBJECT_TYPE
VARCHAR2(61)
Object type of the payload when TYPE is OBJECT
SORT_ORDER
VARCHAR2(22)
User-specified sort order
RECIPIENTS
VARCHAR2(8)
SINGLE or MULTIPLE recipients
MESSAGE_GROUPING
VARCHAR2(13)
NONE or TRANSACTIONAL
COMPATIBLE
VARCHAR2(5)
Lowest release level which the queue table is
compatible with (for example, 8.0.3)
PRIMARY_INSTANCE
NUMBER
Indicates the instance number of the instance which is
the primary owner of the queue table. A value of 0
indicates that there is no primary owner.
SECONDARY_INSTANCE
NUMBER
Indicates the instance number of the instance which is
the secondary owner of the queue table. This instance
becomes the owner of the queue table if the primary
owner is not alive. A value of 0 indicates that there is
no secondary owner.
OWNER_INSTANCE
NUMBER
Instance number of the instance which currently owns
the queue table
USER_COMMENT
VARCHAR2(50)
Comment supplied by the user
SECURE
VARCHAR2(3)
Indicates whether the queue table is secure (YES) or
not (NO)
See Also:
■
"DBA_QUEUE_TABLES" on page 2-208
■
"USER_QUEUE_TABLES" on page 2-283
■
Oracle9i Application Developer’s Guide - Advanced Queuing for
more information about these views and Advanced Queuing
2-104 Oracle9i Database Reference
ALL_REFRESH
ALL_QUEUES
ALL_QUEUES describes all queues on which the current user has enqueue or
dequeue privileges. If the user has any Advanced Queuing system privileges, like
MANAGE ANY QUEUE, ENQUEUE ANY QUEUE or DEQUEUE ANY QUEUE, then this
view describes all queues in the database.
Related Views
■
■
DBA_QUEUES describes all queues in the database.
USER_QUEUES describes the operational characteristics of every queue owned
by the current user. This view does not display the OWNER column.
See Also: Oracle9i Application Developer’s Guide - Advanced
Queuing for more information about these views and Advanced
Queuing
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the queue
NAME
VARCHAR2(30)
NOT NULL
Name of the queue
QUEUE_TABLE
VARCHAR2(30)
NOT NULL
Name of the table the queue data resides in
QID
NUMBER
NOT NULL
Object number of the queue
QUEUE_TYPE
VARCHAR2(15)
Type of the queue
MAX_RETRIES
NUMBER
Maximum number of retries allowed when
dequeuing from the queue
RETRY_DELAY
NUMBER
Time interval between retries
ENQUEUE_ENABLED
VARCHAR2(7)
Queue is enabled for enqueue
DEQUEUE_ENABLED
VARCHAR2(7)
Queue is enabled for dequeue
RETENTION
VARCHAR2(40)
Time interval processed messages retained in the
queue
USER_COMMENT
VARCHAR2(50)
User specified comment
ALL_REFRESH
ALL_REFRESH describes all the refresh groups accessible to the current user.
Related Views
■
DBA_REFRESH describes all refresh groups in the database.
Static Data Dictionary Views 2-105
ALL_REFRESH_CHILDREN
■
USER_REFRESH describes all refresh groups owned by the current user.
Column
Datatype
NULL
Description
ROWNER
VARCHAR2(30)
NOT NULL
Name of the owner of the refresh group
RNAME
VARCHAR2(30)
NOT NULL
Name of the refresh group
REFGROUP
NUMBER
Internal identifier of refresh group
IMPLICIT_DESTROY
VARCHAR2(1)
(Y |N) If Y, then destroy the refresh group when its
last item is subtracted
PUSH_DEFERRED_RPC
VARCHAR2(1)
(Y |N) If Y then push changes from snapshot to master
before refresh
REFRESH_AFTER
_ERRORS
VARCHAR2(1)
If Y, proceed with refresh despite error when pushing
deferred RPCs
ROLLBACK_SEG
VARCHAR2(30)
Name of the rollback segment to use while refreshing
JOB
NUMBER
Identifier of job used to refresh the group
automatically
NEXT_DATE
DATE
Date that this job will next be refreshed automatically,
if not broken
INTERVAL
VARCHAR2(200)
A date function used to compute the next NEXT_DATE
BROKEN
VARCHAR2(1)
(Y |N) Y means the job is broken and will never be run
PURGE_OPTION
NUMBER(38)
The method for purging the transaction queue after
each push. 1 indicates quick purge option; 2 indicates
precise purge option
PARALLELISM
NUMBER(38)
The level of parallelism for transaction propagation
HEAP_SIZE
NUMBER(38)
The size of the heap
ALL_REFRESH_CHILDREN
ALL_REFRESH_CHILDREN lists all the objects in refresh groups that are accessible
to the current user.
Related Views
■
■
DBA_REFRESH_CHILDREN describes the objects in all refresh groups in the
database.
USER_REFRESH_CHILDREN describes the objects in all refresh groups owned
by the current user.
2-106 Oracle9i Database Reference
ALL_REFRESH_DEPENDENCIES
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the object in the refresh group
NAME
VARCHAR2(30)
NOT NULL
Name of the object in the refresh group
OWNER
VARCHAR2(30)
NOT NULL
Owner of the object
NAME
VARCHAR2(30)
NOT NULL
Name of the object
TYPE
VARCHAR2(30)
ROWNER
VARCHAR2(30)
NOT NULL
Name of the owner of the refresh group
RNAME
VARCHAR2(30)
NOT NULL
Name of the refresh group
REFGROUP
NUMBER
Internal identifier of refresh group
IMPLICIT_DESTROY
VARCHAR2(1)
(Y| N) If Y, then destroy the refresh group when its
last item is subtracted
PUSH_DEFERRED_RPC
VARCHAR2(1)
(Y |N) If Y then push changes from snapshot to master
before refresh
REFRESH_AFTER
_ERRORS
VARCHAR2(1)
If Y, proceed with refresh despite error when pushing
deferred RPCs
ROLLBACK_SEG
VARCHAR2(30)
Name of the rollback segment to use while refreshing
JOB
NUMBER
Identifier of job used to refresh the group
automatically
NEXT_DATE
DATE
Date that this job will next be refreshed automatically,
if not broken
INTERVAL
VARCHAR2(200)
A date function used to compute the next NEXT_DATE
BROKEN
VARCHAR2(1)
(Y |N) Y means the job is broken and will never be run
PURGE_OPTION
NUMBER(38)
The method for purging the transaction queue after
each push. 1 indicates quick purge option; 2 indicates
precise purge option
PARALLELISM
NUMBER(38)
The level of parallelism for transaction propagation
HEAP_SIZE
NUMBER(38)
The size of the heap
Type of the object in the refresh group
ALL_REFRESH_DEPENDENCIES
ALL_REFRESH_DEPENDENCIES lists the names of the dependent detail or
container tables of all the summaries or materialized views in the current schema.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the table
TABLE_NAME
VARCHAR2(30)
NOT NULL
Table name, unique within this schema
Static Data Dictionary Views 2-107
ALL_REFS
Column
Datatype
NULL
Description
PARENT_OBJECT_TYPE
CHAR(7)
MVIEW or SUMMARY
OLDEST_REFRESH_SCN
NUMBER
The minimum SCN of any summary or materialized
view that has TABLE_NAME as a detail table
OLDEST_REFRESH_DATE
DATE
SYSDATE when last refreshed
ALL_REFS
ALL_REFS describes the REF columns and REF attributes in object type columns
accessible to the current user.
Related Views
■
■
Column
DBA_REFS describes all REF columns and REF attributes in the database.
USER_REFS describes the REF columns and REF attributes in object type
columns owned by the current user. This view does not display the OWNER
column.
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Name of the owner
TABLE_NAME
VARCHAR2(30)
NOT NULL
Name of the table
COLUMN_NAME
VARCHAR2(4000)
Name of the REF column or attribute. If it is not a
top-level attribute, the value of COLUMN_NAME should
be a path name starting with the column name
WITH_ROWID
VARCHAR2(3)
Whether the REF value is stored with ROWID
(YES|NO)?
IS_SCOPED
VARCHAR2(3)
Whether the REF column is scoped (YES| NO)?
SCOPE_TABLE_OWNER
VARCHAR2(30)
Name of the owner of the scope table, if it exists and
is accessible by the user
SCOPE_TABLE_NAME
VARCHAR2(30)
Name of the scope table, if it exists and is accessible
by the user
OBJECT_ID_TYPE
VARCHAR2(16)
If user-defined OID, then USER-DEFINED, else if
system generated OID, then SYSTEM GENERATED
ALL_REGISTERED_MVIEWS
ALL_REGISTERED_MVIEWS describes all registered materialized views (registered
at a master site or a master materialized view site) accessible to the current user.
2-108 Oracle9i Database Reference
ALL_REGISTRY_BANNERS
Related Views
■
■
DBA_REGISTERED_MVIEWS describes all registered materialized views in the
database.
USER_REGISTERED_MVIEWS describes all registered materialized views
owned by the current user.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the materialized view
NAME
VARCHAR2(30)
NOT NULL
Name of the materialized view
MVIEW_SITE
VARCHAR2(128)
NOT NULL
Global name of the materialized view site
CAN_USE_LOG
VARCHAR2(3)
YES if the materialized view can use a materialized
view log, NO if the materialized view is too complex
to use a log.
UPDATABLE
VARCHAR2(3)
(YES/NO) Indicates whether the materialized view is
updatable. If set to NO, then the materialized view is
read only.
REFRESH_METHOD
VARCHAR2(11)
Whether the materialized view uses primary key,
rowids, or object identifiers for fast refresh
MVIEW_ID
NUMBER(38)
Identifier for the materialized view used by the
masters for fast refresh
VERSION
VARCHAR2(26)
Oracle version of the materialized view
Note: Oracle9i materialized views show ORACLE 8
MATERIALIZED VIEW.
QUERY_TXT
Query that defines the materialized view
LONG
See Also:
■
"DBA_REGISTERED_MVIEWS" on page 2-210
■
"USER_REGISTERED_MVIEWS" on page 2-284
ALL_REGISTRY_BANNERS
ALL_REGISTRY_BANNERS displays the valid components loaded into the database.
Column
Datatype
BANNER
VARCHAR2(80)
NULL
Description
Component display banner
Static Data Dictionary Views 2-109
ALL_RULE_SET_RULES
ALL_RULE_SET_RULES
ALL_RULE_SET_RULES describes the rules in the rule sets accessible to the current
user.
Related Views
■
■
DBA_RULE_SET_RULES describes the rules in all rule sets in the database.
USER_RULE_SET_RULES describes the rules in the rule sets owned by the
current user. This view does not display the RULE_SET_OWNER column.
Column
Datatype
NULL
Description
RULE_SET_OWNER
VARCHAR2(30)
NOT NULL
Owner of the rule set
RULE_SET_NAME
VARCHAR2(30)
NOT NULL
Name of the rule set
RULE_OWNER
VARCHAR2(30)
NOT NULL
Owner of the rule
RULE_NAME
VARCHAR2(30)
NOT NULL
Name of the rule
RULE_SET_RULE_ENABLED VARCHAR2(8)
Indicates whether the rule is enabled in the rule set
(ENABLED) or not (DISABLED)
RULE_SET_RULE_EVAL_
CTX_OWNER
VARCHAR2(30)
Owner of the evaluation context specified when the
rule was added to the rule set, if any
RULE_SET_RULE_EVAL_
CTX_NAME
VARCHAR2(30)
Name of the evaluation context specified when the
rule was added to the rule set, if any
RULE_SET_RULE_COMMENT VARCHAR2(4000)
Comment specified when the rule was added to the
rule set, if any
See Also:
■
"DBA_RULE_SET_RULES" on page 2-220
■
"USER_RULE_SET_RULES" on page 2-286
ALL_RULE_SETS
ALL_RULE_SETS describes the rule sets accessible to the current user.
Related Views
■
■
DBA_RULE_SETS describes all rule sets in the database.
USER_RULE_SETS describes the rule sets owned by the current user. This view
does not display the RULE_SET_OWNER column.
2-110 Oracle9i Database Reference
ALL_RULES
Column
Datatype
NULL
Description
RULE_SET_OWNER
VARCHAR2(30)
NOT NULL
Owner of the rule set
RULE_SET_NAME
VARCHAR2(30)
NOT NULL
Name of the rule set
RULE_SET_EVAL_
CONTEXT_OWNER
VARCHAR2(30)
Owner of the evaluation context associated with the
rule set, if any
RULE_SET_EVAL_
CONTEXT_NAME
VARCHAR2(30)
Name of the evaluation context associated with the
rule set, if any
RULE_SET_COMMENT
VARCHAR2(4000)
Comment specified with the rule set, if any
See Also:
■
"DBA_RULE_SETS" on page 2-220
■
"USER_RULE_SETS" on page 2-286
ALL_RULES
ALL_RULES describes the rules accessible to the current user.
Related Views
■
■
DBA_RULES describes all rules in the database.
USER_RULES describes the rules owned by the current user. This view does not
display the RULE_OWNER column.
Column
Datatype
NULL
Description
RULE_OWNER
VARCHAR2(30)
NOT NULL
Owner of the rule
RULE_NAME
VARCHAR2(30)
NOT NULL
Name of the rule
RULE_CONDITION
CLOB
Expressions and operators that constitute the rule
condition
RULE_EVALUATION_
CONTEXT_OWNER
VARCHAR2(30)
Owner of the evaluation context associated with the
rule, if any
RULE_EVALUATION_
CONTEXT_NAME
VARCHAR2(30)
Name of the evaluation context associated with the
rule, if any
RULE_ACTION_CONTEXT
RE$NV_LIST
Action context associated with the rule, if any
RULE_COMMENT
VARCHAR2(4000)
Comment specified with the rule, if any
Static Data Dictionary Views 2-111
ALL_SEQUENCES
See Also:
■
"DBA_RULES" on page 2-220
■
"USER_RULES" on page 2-286
ALL_SEQUENCES
ALL_SEQUENCES describes all sequences accessible to the current user.
Related Views
■
■
DBA_SEQUENCES describes all sequences in the database.
USER_SEQUENCES describes all sequences owned by the current user. This
view does not display the SEQUENCE_OWNER column.
Column
Datatype
NULL
Description
SEQUENCE_OWNER
VARCHAR2(30)
NOT NULL
Name of the owner of the sequence
SEQUENCE_NAME
VARCHAR2(30)
NOT NULL
Sequence name
MIN_VALUE
NUMBER
Minimum value of the sequence
MAX_VALUE
NUMBER
Maximum value of the sequence
INCREMENT_BY
NUMBER
CYCLE_FLAG
VARCHAR2(1)
Does sequence wrap around on reaching limit
ORDER_FLAG
VARCHAR2(1)
Are sequence numbers generated in order
CACHE_SIZE
NUMBER
NOT NULL
Number of sequence numbers to cache
LAST_NUMBER
NUMBER
NOT NULL
Last sequence number written to disk. If a sequence
uses caching, the number written to disk is the last
number placed in the sequence cache. This number is
likely to be greater than the last sequence number that
was used.
NOT NULL
Value by which sequence is incremented
ALL_SOURCE
ALL_SOURCE describes the text source of the stored objects accessible to the current
user.
Related Views
■
DBA_SOURCE describes the text source of all stored objects in the database.
2-112 Oracle9i Database Reference
ALL_SQLJ_TYPE_ATTRS
■
USER_SOURCE describes the text source of the stored objects owned by the
current user. This view does not display the OWNER column.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the object
NAME
VARCHAR2(30)
NOT NULL
Name of the object
TYPE
VARCHAR2(12)
LINE
NUMBER
TEXT
VARCHAR2(4000)
Type of object: FUNCTION, JAVA SOURCE, PACKAGE,
PACKAGE BODY, PROCEDURE, TRIGGER, TYPE, TYPE
BODY
NOT NULL
Line number of this line of source
Text source of the stored object
ALL_SOURCE_TABLES
ALL_SOURCE_TABLES enables publishers to see all existing source tables.
Related Views
■
■
DBA_SOURCE_TABLES describes all existing source tables.
USER_SOURCE_TABLES describes all existing source tables to which the user
has subscribe privileges.
Column
Datatype
Description
SOURCE_SCHEMA_NAME
VARCHAR2(30)
The table owner in the source system
SOURCE_TABLE_NAME
VARCHAR2(31)
The table name in the source system
See Also:
■
"DBA_SOURCE_TABLES" on page 2-222
■
"USER_SOURCE_TABLES" on page 2-287
ALL_SQLJ_TYPE_ATTRS
ALL_SQLJ_TYPE_ATTRS describes the attributes of the SQLJ object types accessible
to the current user.
Static Data Dictionary Views 2-113
ALL_SQLJ_TYPE_METHODS
Related Views
■
■
DBA_SQLJ_TYPE_ATTRS describes the attributes of all SQLJ object types in the
database.
USER_SQLJ_TYPE_ATTRS describes the attributes of the object types owned by
the current user. This view does not display the OWNER column.
Column
Datatype
OWNER
VARCHAR2(30)
NULL
Description
TYPE_NAME
VARCHAR2(30)
NOT NULL
Name of the type
ATTR_NAME
VARCHAR2(30)
NOT NULL
Name of the attribute
Owner of the type
EXTERNAL_ATTR_NAME
VARCHAR2(4000)
External name of the attribute
ATTR_TYPE_MOD
VARCHAR2(7)
Type modifier of the attribute
ATTR_TYPE_OWNER
VARCHAR2(30)
Owner of the type of the attribute
ATTR_TYPE_NAME
VARCHAR2(30)
Name of the type of the attribute
LENGTH
NUMBER
Length of the CHAR attribute, or maximum length of
the VARCHAR or VARCHAR2 attribute.
PRECISION
NUMBER
Decimal precision of the NUMBER or DECIMAL
attribute, or binary precision of the FLOAT attribute.
SCALE
NUMBER
Scale of the NUMBER or DECIMAL attribute
CHARACTER_SET
_NAME
VARCHAR2(44)
Character set name of the attribute (CHAR_CS or
NCHAR_CS)
ATTR_NO
NUMBER
INHERITED
VARCHAR2(3)
NOT NULL
Syntactical order number or position of the attribute
as specified in the type specification or CREATE
TYPE statement (not to be used as an ID number)
Indicates whether the attribute is inherited from a
supertype (YES) or not (NO)
See Also:
■
"DBA_SQLJ_TYPE_ATTRS" on page 2-222
■
"USER_SQLJ_TYPE_ATTRS" on page 2-287
ALL_SQLJ_TYPE_METHODS
ALL_SQLJ_TYPE_METHODS describes the methods of the SQLJ object types
accessible to the current user.
2-114 Oracle9i Database Reference
ALL_SQLJ_TYPES
Related Views
■
■
DBA_SQLJ_TYPE_METHODS describes the methods of all SQLJ object types in
the database.
USER_SQLJ_TYPE_METHODS describes the methods of the SQLJ object types
owned by the current user. This view does not display the OWNER column.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the type
TYPE_NAME
VARCHAR2(30)
NOT NULL
Name of the type
METHOD_NAME
VARCHAR2(30)
NOT NULL
Name of the method
EXTERNAL_VAR_NAME
VARCHAR2(4000)
METHOD_NO
NUMBER
METHOD_TYPE
VARCHAR2(6)
PARAMETERS
NUMBER
NOT NULL
Number of parameters to the method
RESULTS
NUMBER
NOT NULL
Number of results returned by the method
FINAL
VARCHAR2(3)
Indicates whether the method is final (YES) or not
(NO)
INSTANTIABLE
VARCHAR2(3)
Indicates whether the method is instantiable (YES) or
not (NO)
OVERRIDING
VARCHAR2(3)
Indicates whether the method is overriding a
supertype method (YES) or not (NO)
INHERITED
VARCHAR2(3)
Indicates whether the method is inherited from a
supertype (YES) or not (NO)
Name of the external variable
NOT NULL
Method number that distinguishes overloaded
method (not to be used as an ID number)
Type of the method
See Also:
■
"DBA_SQLJ_TYPE_METHODS" on page 2-222
■
"USER_SQLJ_TYPE_METHODS" on page 2-287
ALL_SQLJ_TYPES
ALL_SQLJ_TYPES describes the SQLJ object types accessible to the current user.
Related Views
■
DBA_SQLJ_TYPES describes all SQLJ object types in the database.
Static Data Dictionary Views 2-115
ALL_STORED_SETTINGS
■
USER_SQLJ_TYPES describes the SQLJ object types owned by the current user.
This view does not display the OWNER column.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
TYPE_NAME
VARCHAR2(30)
NOT NULL
Name of the type
TYPE_OID
RAW(16)
NOT NULL
Object identifier (OID) of the type
EXTERNAL_NAME
VARCHAR2(4000)
External class name of the type
USING
VARCHAR2(21)
Representation of the type
TYPECODE
VARCHAR2(30)
Typecode of the type
ATTRIBUTES
NUMBER
Number of attributes (if any) in the type
METHODS
NUMBER
Number of methods (if any) in the type
PREDEFINED
VARCHAR2(3)
Indicates whether the type is a predefined type (YES)
or not (NO)
INCOMPLETE
VARCHAR2(3)
Indicates whether the type is an incomplete type
(YES) or not (NO)
FINAL
VARCHAR2(3)
Indicates whether the type is a final type (YES) or not
(NO)
INSTANTIABLE
VARCHAR2(3)
Indicates whether the type is an instantiable type
(YES) or not (NO)
SUPERTYPE_OWNER
VARCHAR2(30)
Owner of the supertype (NULL if type is not a
subtype)
SUPERTYPE_NAME
VARCHAR2(30)
Name of the supertype (NULL if type is not a subtype)
LOCAL_ATTRIBUTES
NUMBER
Number of local (not inherited) attributes (if any) in
the subtype
LOCAL_METHODS
NUMBER
Number of local (not inherited) methods (if any) in
the subtype
Owner of the type
See Also:
■
"DBA_SQLJ_TYPES" on page 2-222
■
"USER_SQLJ_TYPES" on page 2-287
ALL_STORED_SETTINGS
ALL_STORED_SETTINGS provides information about the persistent parameter
settings for stored PL/SQL units for which the current user has execute privileges.
2-116 Oracle9i Database Reference
ALL_STREAMS_GLOBAL_RULES
Related Views
■
■
DBA_STORED_SETTINGS lists information about the persistent parameter
settings for stored PL/SQL units for which the current user has execute
privileges. It also returns parameter information for all objects in the database
and is accessible only to users with the SELECT_CATALOG_ROLE privilege.
USER_STORED_SETTINGS lists information about the persistent parameter
settings for stored PL/SQL units, but only shows information about PL/SQL
units owned by the current user. This view does not display the OWNER column.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Name of the database user owning the stored
PL/SQL unit
OBJECT_NAME
VARCHAR2(30)
NOT NULL
Name of the PL/SQL unit
OBJECT_ID
NUMBER
NOT NULL
Object number of the PL/SQL unit
OBJECT_TYPE
VARCHAR2(12)
The type of PL/SQL unit: PROCEDURE, FUNCTION,
PACKAGE, PACKAGE BODY, TRIGGER, TYPE, or TYPE
BODY
PARAM_NAME
VARCHAR2(30)
The name of the parameter stored persistently with
the PL/SQL unit
PARAM_VALUE
VARCHAR2(4000)
The TO_CHAR() representation of the value of the
persistently stored parameter. The width of this
column is operating system dependent; however, it is
never less than 255.
ALL_STREAMS_GLOBAL_RULES
ALL_STREAMS_GLOBAL_RULES displays information about the following types of
rules:
■
■
■
Global rules created for the Streams capture processes that enqueue the
captured changes into queues accessible to the current user
Global rules created for the Streams propagations that have a source queue
accessible to the current user
Global rules created for the Streams apply processes that dequeue events from
queues accessible to the current user
This view only contains information about rules created using the ADD_GLOBAL_
RULES or ADD_GLOBAL_PROPAGATION_RULES procedures in the DBMS_
STREAMS_ADM package. It does not contain information about rules created using
the DBMS_RULE_ADM package.
Static Data Dictionary Views 2-117
ALL_STREAMS_SCHEMA_RULES
Related View
DBA_STREAMS_GLOBAL_RULES displays information about the global rules created
for all Streams capture processes, propagations, and apply processes in the
database.
Column
Datatype
NULL
Description
STREAMS_NAME
VARCHAR2(30)
Name of the Streams process or propagation
STREAMS_TYPE
VARCHAR2(11)
Type of the Streams process or propagation:
■
CAPTURE
■
PROPAGATION
■
APPLY
RULE_TYPE
VARCHAR2(7)
Type of rule (DML or DDL)
INCLUDE_TAGGED_LCR
VARCHAR2(3)
Indicates whether a redo entry or logical change
record (LCR) with a non-null tag is considered for
capture, propagation, or apply (YES) or not (NO)
SOURCE_DATABASE
VARCHAR2(128)
Source database in the rule condition. The rule
evaluates to true for a redo entry or logical change
record (LCR) only if the redo entry or LCR contains
this source database.
RULE_NAME
VARCHAR2(30)
Name of the rule
RULE_OWNER
VARCHAR2(30)
Owner of the rule
RULE_CONDITION
VARCHAR2(4000)
First 4000 bytes of the system-generated rule
condition evaluated by the rules engine
See Also: "DBA_STREAMS_GLOBAL_RULES" on page 2-223
ALL_STREAMS_SCHEMA_RULES
ALL_STREAMS_SCHEMA_RULES displays information about the following types of
rules:
■
■
■
Schema rules created for the Streams capture processes that enqueue the
captured changes into queues accessible to the current user
Schema rules created for the Streams propagations that have a source queue
accessible to the current user
Schema rules created for the Streams apply processes that dequeue events from
queues accessible to the current user
2-118 Oracle9i Database Reference
ALL_STREAMS_TABLE_RULES
This view only contains information about rules created using the ADD_SCHEMA_
RULES or ADD_SCHEMA_PROPAGATION_RULES procedures in the DBMS_
STREAMS_ADM package. It does not contain information about rules created using
the DBMS_RULE_ADM package.
Related View
DBA_STREAMS_SCHEMA_RULES displays information about the schema rules
created for all Streams capture processes, propagations, and apply processes in the
database.
Column
Datatype
NULL
Description
STREAMS_NAME
VARCHAR2(30)
Name of the Streams process or propagation
STREAMS_TYPE
VARCHAR2(11)
Type of the Streams process or propagation:
■
CAPTURE
■
PROPAGATION
■
APPLY
SCHEMA_NAME
VARCHAR2(30)
Schema name in the rule condition. The rule evaluates
to true for a redo entry or logical change record
(LCR) only if the redo entry or LCR contains this
schema name.
RULE_TYPE
VARCHAR2(7)
Type of rule (DML or DDL)
INCLUDE_TAGGED_LCR
VARCHAR2(3)
Indicates whether a redo entry or logical change
record (LCR) with a non-null tag is considered for
capture, propagation, or apply (YES) or not (NO)
SOURCE_DATABASE
VARCHAR2(128)
Source database in the rule condition. The rule
evaluates to true for a redo entry or logical change
record (LCR) only if the redo entry or LCR contains
this source database.
RULE_NAME
VARCHAR2(30)
Name of the rule
RULE_OWNER
VARCHAR2(30)
Owner of the rule
RULE_CONDITION
VARCHAR2(4000)
First 4000 bytes of the system-generated rule
condition evaluated by the rules engine
See Also: "DBA_STREAMS_SCHEMA_RULES" on page 2-223
ALL_STREAMS_TABLE_RULES
ALL_STREAMS_TABLE_RULES displays information about the following types of
rules:
Static Data Dictionary Views 2-119
ALL_STREAMS_TABLE_RULES
■
■
■
■
Table rules created for the Streams capture processes that enqueue the captured
changes into queues accessible to the current user
Table rules created for the Streams propagations that have a source queue
accessible to the current user
Table rules created for the Streams apply processes that dequeue events from
queues accessible to the current user
Subset rules created for the Streams apply processes that have a source queue
accessible to the current user
This view only contains information about rules created using the ADD_TABLE_
RULES, ADD_TABLE_PROPAGATION_RULES, or ADD_SUBSET_RULES procedures
in the DBMS_STREAMS_ADM package. It does not contain information about rules
created using the DBMS_RULE_ADM package.
Related View
DBA_STREAMS_TABLE_RULES displays information about the table rules created
for all Streams capture processes, propagations, and apply processes in the
database.
Column
Datatype
NULL
Description
STREAMS_NAME
VARCHAR2(30)
Name of the Streams process or propagation
STREAMS_TYPE
VARCHAR2(11)
Type of the Streams process or propagation:
■
CAPTURE
■
PROPAGATION
■
APPLY
TABLE_OWNER
VARCHAR2(30)
Table owner in the rule condition. The rule evaluates
to true for a redo entry or logical change record
(LCR) only if the redo entry or LCR contains this table
owner.
TABLE_NAME
VARCHAR2(30)
Table name in the rule condition. The rule evaluates to
true for a redo entry or logical change record (LCR)
only if the redo entry or LCR contains this table name.
RULE_TYPE
VARCHAR2(7)
Type of rule (DML or DDL)
DML_CONDITION
VARCHAR2(4000)
Row subsetting condition, if the rule is a subset rule
2-120 Oracle9i Database Reference
ALL_SUBPART_COL_STATISTICS
Column
Datatype
SUBSETTING_OPERATION
VARCHAR2(6)
NULL
Description
DML operation for row subsetting in the rule
condition, if the rule is a subset rule:
■
INSERT
■
UPDATE
■
DELETE
The rule evaluates to true for a logical change record
(LCR) only if the LCR contains this command type
after internal transformation.
INCLUDE_TAGGED_LCR
VARCHAR2(3)
Indicates whether a redo entry or logical change
record (LCR) with a non-null tag is considered for
capture, propagation, or apply (YES) or not (NO)
SOURCE_DATABASE
VARCHAR2(128)
Source database in the rule condition. The rule
evaluates to true for a redo entry or logical change
record (LCR) only if the redo entry or LCR contains
this source database.
RULE_NAME
VARCHAR2(30)
Name of the rule
RULE_OWNER
VARCHAR2(30)
Owner of the rule
RULE_CONDITION
VARCHAR2(4000)
First 4000 bytes of the system-generated rule
condition evaluated by the rules engine
See Also: "DBA_STREAMS_TABLE_RULES" on page 2-224
ALL_SUBPART_COL_STATISTICS
ALL_SUBPART_COL_STATISTICS describes column statistics and histogram
information for subpartitions of partitioned objects accessible to the current user.
Related Views
■
■
DBA_SUBPART_COL_STATISTICS provides this information for all
subpartitions in the database.
USER_SUBPART_COL_STATISTICS provides this information for subpartitions
of all partitioned objects owned by the current user. This view does not display
the OWNER column.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner name
TABLE_NAME
VARCHAR2(30)
NOT NULL
Table name
Static Data Dictionary Views 2-121
ALL_SUBPART_HISTOGRAMS
Column
Datatype
NULL
Description
SUBPARTITION_NAME
VARCHAR2(30)
COLUMN_NAME
VARCHAR2(30)
NUM_DISTINCT
NUMBER
Number of distinct values in the column
LOW_VALUE
RAW(32)
Low value in the column
HIGH_VALUE
RAW(32)
High value in the column
DENSITY
NUMBER
Density of the column
NUM_NULLS
NUMBER
Number of nulls in the column
NUM_BUCKETS
NUMBER
Number of buckets in histogram for the column
SAMPLE_SIZE
NUMBER
Sample size used in analyzing this column
LAST_ANALYZED
DATE
Date on which this column was most recently
analyzed
GLOBAL_STATS
VARCHAR2(3)
Indicates whether column statistics for the
subpartition were collected by analyzing the table as a
whole (YES) or estimated from statistics gathered on
partitions and subpartitions (NO).
USER_STATS
VARCHAR2(3)
Were the statistics entered directly by the user?
AVG_COL_LEN
NUMBER
The average length of the column, in bytes
Table subpartition name
NOT NULL
Column name
ALL_SUBPART_HISTOGRAMS
ALL_SUBPART_HISTOGRAMS lists the actual histogram data (end-points per
histogram) for histograms on table subpartitions accessible to the current user.
Related Views
■
■
DBA_SUBPART_HISTOGRAMS provides this information for all subpartitions in
the database.
USER_SUBPART_HISTOGRAMS provides this information for subpartitions of
all partitioned objects owned by the current user. This view does not display the
OWNER column.
Note: These views are populated only if you called statistics on
the index using the ANALYZE statement or the DBMS_STATS
package.
2-122 Oracle9i Database Reference
ALL_SUBPART_KEY_COLUMNS
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
Owner name
TABLE_NAME
VARCHAR2(30)
Table name
SUBPARTITION_NAME
VARCHAR2(30)
Table subpartition name
COLUMN_NAME
VARCHAR2(30)
Column name
BUCKET_NUMBER
NUMBER
Bucket number
ENDPOINT_VALUE
NUMBER
Normalized endpoint values for this bucket
Actual (not normalized) string value of the endpoint
for this bucket
ENDPOINT_ACTUAL_VALUE VARCHAR2(1000)
ALL_SUBPART_KEY_COLUMNS
ALL_SUBPART_KEY_COLUMNS lists subpartitioning key columns for
composite-partitioned tables (and local indexes on composite-partitioned tables)
accessible to the current user.
Related Views
■
■
DBA_SUBPART_KEY_COLUMNS provides this information for all subpartitions
in the database.
USER_SUBPART_KEY_COLUMNS provides this information for subpartitions of
all partitioned objects owned by the current user. This view does not display the
OWNER column.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
The partitioned table or index owner
NAME
VARCHAR2(30)
The partitioned table or index name
OBJECT_TYPE
VARCHAR2(11)
The object type (TABLE or INDEX)
COLUMN_NAME
VARCHAR2(30)
The column name
COLUMN_POSITION
NUMBER
The position of the column within the subpartitioning
key
See Also:
■
"DBA_SUBPART_KEY_COLUMNS" on page 2-224
■
"USER_SUBPART_KEY_COLUMNS" on page 2-288
Static Data Dictionary Views 2-123
ALL_SUBPARTITION_TEMPLATES
ALL_SUBPARTITION_TEMPLATES
ALL_SUBPARTITION_TEMPLATES describes the subpartition templates accessible
to the current user.
Related Views
■
■
DBA_SUBPARTITION_TEMPLATES describes all subpartition templates in the
database.
USER_SUBPARTITION_TEMPLATES describes the subpartition templates
owned by the current user. This view does not display the USER_NAME column.
Column
Datatype
NULL
Description
USER_NAME
VARCHAR2(30)
NOT NULL
Owner of the table
TABLE_NAME
VARCHAR2(30)
NOT NULL
Name of the table
SUBPARTITION_NAME
VARCHAR2(34)
NOT NULL
Name of the subpartition
SUBPARTITION_POSITION NUMBER
Position of the subpartition
TABLESPACE_NAME
VARCHAR2(30)
Tablespace name of the subpartition
HIGH_BOUND
LONG
Literal list values of the subpartition
See Also:
■
"DBA_SUBPARTITION_TEMPLATES" on page 2-224
■
"USER_SUBPARTITION_TEMPLATES" on page 2-288
ALL_SUBSCRIBED_COLUMNS
ALL_SUBSCRIBED_COLUMNS enables publishers to view the columns of published
tables to which they have subscribed.
Related Views
■
■
DBA_SUBSCRIBED_COLUMNS enables publishers to view the columns of
published tables to which they have subscribed. You must have the SELECT_
CATALOG_ROLE privilege to access this view.
USER_SUBSCRIBED_COLUMNS enables publishers to view the columns of
published tables to which they have subscribed.
2-124 Oracle9i Database Reference
ALL_SUBSCRIPTIONS
Column
Datatype
Description
HANDLE
NUMBER
The subscription handle
SOURCE_SCHEMA_NAME
VARCHAR2(30)
The source table schema identifier
SOURCE_TABLE_NAME
VARCHAR2(31)
The source table identifier
COLUMN_NAME
VARCHAR2(30)
The source table column identifier
ALL_SUBSCRIBED_TABLES
ALL_SUBSCRIBED_TABLES enables subscribers to view all published tables to
which they have subscribed.
Related Views
■
■
DBA_SUBSCRIBED_TABLES enables publishers to view all published tables to
which they have subscribed.
USER_SUBSCRIBED_TABLES enables subscribers to view all published tables
to which they have subscribed.
Column
Datatype
Description
HANDLE
NUMBER
The subscription handle
SOURCE_SCHEMA_NAME
VARCHAR2(30)
The source table schema identifier
SOURCE_TABLE_NAME
VARCHAR2(31)
The source table identifier
VIEW_NAME
VARCHAR2(30)
Holds the generated view name so that change data capture can drop
the view when necessary
CHANGE_SET_NAME
VARCHAR2(30)
The name of the change set to which the change table belongs
ALL_SUBSCRIPTIONS
ALL_SUBSCRIPTIONS enables subscribers to view all subscriptions. Neither ALL_
SUBSCRIPTIONS nor USER_SUBSCRIPTIONS contains the USERNAME column.
Related Views
■
■
DBA_SUBSCRIPTIONS enables publishers to view all subscriptions. You must
have the SELECT_CATALOG_ROLE privilege to access this view. DBA_
SUBSCRIPTIONS contains the USERNAME column, which lists the user name of
the subscriber.
USER_SUBSCRIPTIONS enables subscribers to view all of their subscriptions.
Static Data Dictionary Views 2-125
ALL_SUMDELTA
Column
Datatype
Description
HANDLE
NUMBER
The subscription handler
SET_NAME
VARCHAR2(30)
The change set identifier
CREATED
DATE
Subscription creation date
STATUS
VARCHAR2(1)
N indicates not yet active, A indicates is currently active
EARLIEST_SCN
NUMBER
Starting point for the select/view
LATEST_SCN
NUMBER
The ending point for the select/view
DESCRIPTION
VARCHAR2(30)
A comment field for the subscriber
LAST_PURGED
DATE
The last time the subscriber called the PURGE_WINDOW for this
subscription
LAST_EXTENDED
DATE
The last time the subscriber called the EXTEND_WINDOW for this
subscription
ALL_SUMDELTA
ALL_SUMDELTA lists direct path load entries accessible to the current user.
Column
Datatype
NULL
Description
TABLEOBJ#
NUMBER
NOT NULL
Object number of the table
PARTITIONOBJ#
NUMBER
NOT NULL
Object number of table partitions (if the table is
partitioned)
DMLOPERATION
VARCHAR2(1)
SCN
NUMBER
NOT NULL
SCN when the bulk DML occurred
TIMESTAMP
DATE
NOT NULL
Timestamp of log entry
LOWROWID
ROWID
NOT NULL
The start ROWID in the loaded rowid range
HIGHROWID
ROWID
NOT NULL
The end ROWID in the loaded rowid range
Type of DML operation applied to the table
ALL_SYNONYMS
ALL_SYNONYMS describes all synonyms accessible to the current user.
Related Views
■
■
DBA_SYNONYMS describes all synonyms in the database.
USER_SYNONYMS describes all synonyms owned by the current user. This view
does not display the OWNER column.
2-126 Oracle9i Database Reference
ALL_TAB_COL_STATISTICS
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the synonym
SYNONYM_NAME
VARCHAR2(30)
NOT NULL
Name of the synonym
TABLE_OWNER
VARCHAR2(30)
TABLE_NAME
VARCHAR2(30)
DB_LINK
VARCHAR2(128)
Owner of the object referenced by the synonym
NOT NULL
Name of the object referenced by the synonym
Name of the database link referenced, if any
ALL_TAB_COL_STATISTICS
ALL_TAB_COL_STATISTICS provides column statistics and histogram information
extracted from "ALL_TAB_COLUMNS" on page 2-128.
Related Views
■
■
DBA_TAB_COL_STATISTICS provides such information extracted from "DBA_
TAB_COLUMNS" on page 2-226.
USER_TAB_COL_STATISTICS provides such information extracted from
"USER_TAB_COLUMNS" on page 2-289.
Column
Datatype
NULL
Description
TABLE_NAME
VARCHAR2(30)
NOT NULL
Table name
COLUMN_NAME
VARCHAR2(30)
NOT NULL
Column name
NUM_DISTINCT
NUMBER
Number of distinct values in the column
LOW_VALUE
RAW(32)
Low value in the column
HIGH_VALUE
RAW(32)
High value in the column
DENSITY
NUMBER
Density of the column
NUM_NULLS
NUMBER
Number of nulls in the column
NUM_BUCKETS
NUMBER
Number of buckets in histogram for the column
LAST_ANALYZED
DATE
Date on which this column was most recently
analyzed
SAMPLE_SIZE
NUMBER
Sample size used in analyzing this column
GLOBAL_STATS
VARCHAR2(3)
For partitioned tables, indicates whether column
statistics were collected for the table as a whole (YES)
or were estimated from statistics on underlying
partitions and subpartitions (NO).
USER_STATS
VARCHAR2(3)
Were the statistics entered directly by the user?
Static Data Dictionary Views 2-127
ALL_TAB_COLUMNS
Column
Datatype
AVG_COL_LEN
NUMBER
NULL
Description
The average length of the column, in bytes
ALL_TAB_COLUMNS
ALL_TAB_COLUMNS describes the columns of the tables, views, and clusters
accessible to the current user. To gather statistics for this view, use the SQL
ANALYZE statement or the DBMS_STATS package.
Related Views
■
■
DBA_TAB_COLUMNS describes the columns of all tables, views, and clusters in
the database.
USER_TAB_COLUMNS describes the columns of the tables, views, and clusters
owned by the current user. This view does not display the OWNER column.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the table, view, or cluster
TABLE_NAME
VARCHAR2(30)
NOT NULL
Name of the table, view, or cluster
COLUMN_NAME
VARCHAR2(30)
NOT NULL
Column name
DATA_TYPE
VARCHAR2(30)
Datatype of the column
DATA_TYPE_MOD
VARCHAR2(3)
Datatype modifier of the column
DATA_TYPE_OWNER
VARCHAR2(30)
Owner of the datatype of the column
DATA_LENGTH
NUMBER
DATA_PRECISION
NUMBER
Decimal precision for NUMBER datatype; binary
precision for FLOAT datatype, null for all other
datatypes
DATA_SCALE
NUMBER
Digits to right of decimal point in a number
NULLABLE
VARCHAR2(1)
Specifies whether a column allows NULLs. Value is N
if there is a NOT NULL constraint on the column or if
the column is part of a PRIMARY KEY.
COLUMN_ID
NUMBER
DEFAULT_LENGTH
NUMBER
Length of default value for the column
DATA_DEFAULT
LONG
Default value for the column
2-128 Oracle9i Database Reference
NOT NULL
NOT NULL
Length of the column in bytes
Sequence number of the column as created
ALL_TAB_COLUMNS
Column
Datatype
NULL
Description
NUM_DISTINCT
NUMBER
LOW_VALUE
RAW(32)
HIGH_VALUE
RAW(32)
DENSITY
NUMBER
NUM_NULLS
NUMBER
Number of nulls in the column
NUM_BUCKETS
NUMBER
The number of buckets in histogram for the column
These columns remain for backward compatibility
with Oracle7. This information is now in the
{TAB|PART}_COL_STATISTICS views. This view
now picks up these values from HIST_HEAD$ rather
than COL$.
Note: The number of buckets in a histogram is
specified in the SIZE parameter of the SQL statement
ANALYZE. However, Oracle does not create a
histogram with more buckets than the number of
rows in the sample. Also, if the sample contains any
values that are very repetitious, Oracle creates the
specified number of buckets, but the value indicated
by this column may be smaller because of an internal
compression algorithm.
LAST_ANALYZED
DATE
The date on which this column was most recently
analyzed
The sample size used in analyzing this column
SAMPLE_SIZE
CHARACTER_SET_NAME
VARCHAR2(44)
The name of the character set: CHAR_CS or NCHAR_CS
CHAR_COL_DECL_LENGTH
NUMBER
The length
GLOBAL_STATS
VARCHAR2(3)
For partitioned tables, indicates whether column
statistics were collected for the table as a whole (YES)
or were estimated from statistics on underlying
partitions and subpartitions (NO).
USER_STATS
VARCHAR2(3)
Were the statistics entered directly by the user?
AVG_COL_LEN
NUMBER
Average length of the column (in bytes)
CHAR_LENGTH
NUMBER
Displays the length of the column in characters. This
value only applies to the following datatypes:
■
CHAR
■
VARCHAR2
■
NCHAR
■
NVARCHAR
Static Data Dictionary Views 2-129
ALL_TAB_COMMENTS
Column
Datatype
CHAR_USED
VARCHAR2(1)
NULL
Description
B | C. B indicates that the column uses BYTE length
semantics. C indicates that the column uses CHAR
length semantics. NULL indicates the datatype is not
any of the following:
■
CHAR
■
VARCHAR2
■
NCHAR
■
NVARCHAR2
ALL_TAB_COMMENTS
ALL_TAB_COMMENTS describes comments on tables and views accessible to the
current user.
Related Views
■
■
DBA_TAB_COMMENTS describes comments on all tables and views in the
database.
USER_TAB_COMMENTS describes comments on all tables and views owned by
the current user. This view does not display the OWNER column.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the object
TABLE_NAME
VARCHAR2(30)
NOT NULL
Name of the object
TABLE_TYPE
VARCHAR2(11)
Type of the object
COMMENTS
VARCHAR2(4000)
Comment on the object
ALL_TAB_HISTOGRAMS
ALL_TAB_HISTOGRAMS describes histograms on tables and views accessible to the
current user.
Related Views
■
■
DBA_TAB_HISTOGRAMS describes histograms on all tables and views in the
database.
USER_TAB_HISTOGRAMS describes histograms on all tables and views owned
by the current user. This view does not display the OWNER column.
2-130 Oracle9i Database Reference
ALL_TAB_MODIFICATIONS
Note: These views are populated only if you called statistics on
the index using the ANALYZE statement or the DBMS_STATS
package.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
Owner of table
TABLE_NAME
VARCHAR2(30)
Name of the table
COLUMN_NAME
VARCHAR2(4000)
Column name or attribute of the object type column
ENDPOINT_NUMBER
NUMBER
Histogram bucket number
ENDPOINT_VALUE
NUMBER
Normalized endpoint value for this bucket
Actual (not normalized) string value of the endpoint
for this bucket
ENDPOINT_ACTUAL_VALUE VARCHAR2(1000)
ALL_TAB_MODIFICATIONS
ALL_TAB_MODIFICATIONS describes tables accessible to the current user that have
been modified since the last time statistics were gathered on the tables.
Related Views
■
■
DBA_TAB_MODIFICATIONS provides such information for all tables in the
database.
USER_TAB_MODIFICATIONS provides such information for tables owned by
the current user. This view does not display the TABLE_OWNER column.
Note: These views are populated only for tables with the
MONITORING attribute. They are intended for statistics collection
over a long period of time. For performance reasons, Oracle may
not populate these views until a few hours after the actual
modifications occurred.
Column
Datatype
TABLE_OWNER
VARCHAR2(30)
NULL
Description
Owner of the modified table.
TABLE_NAME
VARCHAR2(30)
Name of the modified table
Static Data Dictionary Views 2-131
ALL_TAB_PARTITIONS
Column
Datatype
NULL
Description
PARTITION_NAME
VARCHAR2(30)
Name of the modified partition
SUBPARTITION_NAME
VARCHAR2(30)
Name of the modified subpartition
INSERTS
NUMBER
Approximate number of inserts since the last time
statistics were gathered
UPDATES
NUMBER
Approximate number of updates since the last time
statistics were gathered
DELETES
NUMBER
Approximate number of deletes since the last time
statistics were gathered
TIMESTAMP
DATE
Indicates the last time the table was modified
TRUNCATED
VARCHAR2(3)
Whether or not the table was truncated since the last
time statistics were gathered
ALL_TAB_PARTITIONS
ALL_TAB_PARTITIONS provides partition-level partitioning information, partition
storage parameters, and partition statistics collected by ANALYZE statements for
partitions accessible to the current user.
Related Views
■
■
DBA_TAB_PARTITIONS provides such information for all partitions in the
database.
USER_TAB_PARTITIONS provides such information for partitions of all
partitioned objects owned by the current user. This view does not display the
OWNER column.
Column
Datatype
NULL
Description
TABLE_OWNER
VARCHAR2(30)
NOT NULL
Table owner
TABLE_NAME
VARCHAR2(30)
NOT NULL
Table name
COMPOSITE
VARCHAR2(3)
YES if the partition belongs to a Local index on a table
partitioned using Composite method; NO otherwise
PARTITION_NAME
VARCHAR2(30)
Partition name
SUBPARTITION_COUNT
NUMBER
If this is a Local index on a table partitioned using a
Composite method, the number of subpartitions in
the partition
HIGH_VALUE
LONG
Partition bound value expression
HIGH_VALUE_LENGTH
NUMBER
2-132 Oracle9i Database Reference
NOT NULL
Length of partition bound value expression
ALL_TAB_PRIVS
Column
Datatype
NULL
Description
PARTITION_POSITION
NUMBER
NOT NULL
Position of the partition within the table
TABLESPACE_NAME
VARCHAR2(30)
NOT NULL
Name of the tablespace containing the partition
PCT_FREE
NUMBER
NOT NULL
Minimum percentage of free space in a block
PCT_USED
NUMBER
NOT NULL
Minimum percentage of used space in a block
INI_TRANS
NUMBER
NOT NULL
Initial number of transactions
MAX_TRANS
NUMBER
NOT NULL
Maximum number of transactions
INITIAL_EXTENT
NUMBER
Size of the initial extent in bytes
NEXT_EXTENT
NUMBER
Size of secondary extents in bytes
MIN_EXTENT
NUMBER
NOT NULL
Minimum number of extents allowed in the segment
MAX_EXTENT
NUMBER
NOT NULL
Maximum number of extents allowed in the segment
PCT_INCREASE
NUMBER
NOT NULL
Percentage increase in extent size
FREELISTS
NUMBER
Number of process freelists allocated in this segment
FREELIST_GROUPS
NUMBER
Number of freelist groups allocated in this segment
LOGGING
VARCHAR2(3)
Logging attribute of partition
NUM_ROWS
NUMBER
Number of rows in the partition
BLOCKS
NUMBER
Number of used blocks in the partition
EMPTY_BLOCKS
NUMBER
Number of empty (never used) blocks in the partition
AVG_SPACE
NUMBER
Average available free space in the partition
CHAIN_CNT
NUMBER
Number of chained rows in the partition
AVG_ROW_LEN
NUMBER
Average row length, including row overhead
SAMPLE_SIZE
NUMBER
Sample size used in analyzing this partition
LAST_ANALYZED
DATE
Date on which this partition was most recently
analyzed
BUFFER_POOL
VARCHAR2(7)
The default buffer pool to be used for the partition
blocks
GLOBAL_STATS
VARCHAR2(3)
Indicates whether statistics were collected for the
partition as a whole (YES) or were estimated from
statistics on underlying subpartitions (NO)
USER_STATS
VARCHAR2(3)
User statistics
ALL_TAB_PRIVS
ALL_TAB_PRIVS describes the following types of grants:
Static Data Dictionary Views 2-133
ALL_TAB_PRIVS_MADE
■
Object grants for which the current user is the object owner, grantor, or grantee
■
Object grants for which an enabled role or PUBLIC is the grantee
Related Views
■
■
DBA_TAB_PRIVS describes all object grants in the database.
USER_TAB_PRIVS describes the object grants for which the current user is the
object owner, grantor, or grantee.
Column
Datatype
NULL
Description
GRANTOR
VARCHAR2(30)
NOT NULL
Name of the user who performed the grant
GRANTEE
VARCHAR2(30)
NOT NULL
Name of the user to whom access was granted
TABLE_SCHEMA
VARCHAR2(30)
NOT NULL
Schema of the object
TABLE_NAME
VARCHAR2(30)
NOT NULL
Name of the object
PRIVILEGE
VARCHAR2(40)
NOT NULL
Privilege on the object
GRANTABLE
VARCHAR2(3)
Indicates whether the privilege was granted with the
GRANT OPTION (YES) or not (NO)
HIERARCHY
VARCHAR2(3)
Indicates whether the privilege was granted with the
HIERARCHY OPTION (YES) or not (NO)
See Also:
■
"DBA_TAB_PRIVS" on page 2-227
■
"USER_TAB_PRIVS" on page 2-290
ALL_TAB_PRIVS_MADE
ALL_TAB_PRIVS_MADE describes the object grants for which the current user is the
object owner or grantor.
Related View
USER_TAB_PRIVS_MADE describes the object grants for which the current user is
the object owner. This view does not display the OWNER column.
Column
Datatype
NULL
Description
GRANTEE
VARCHAR2(30)
NOT NULL
Name of the user to whom access was granted
OWNER
VARCHAR2(30)
NOT NULL
Owner of the object
2-134 Oracle9i Database Reference
ALL_TAB_PRIVS_RECD
Column
Datatype
NULL
Description
TABLE_NAME
VARCHAR2(30)
NOT NULL
Name of the object
GRANTOR
VARCHAR2(30)
NOT NULL
Name of the user who performed the grant
PRIVILEGE
VARCHAR2(40)
NOT NULL
Privilege on the object
GRANTABLE
VARCHAR2(3)
Indicates whether the privilege was granted with the
GRANT OPTION (YES) or not (NO)
HIERARCHY
VARCHAR2(3)
Indicates whether the privilege was granted with the
HIERARCHY OPTION (YES) or not (NO)
See Also: "USER_TAB_PRIVS_MADE" on page 2-290
ALL_TAB_PRIVS_RECD
ALL_TAB_PRIVS_RECD describes the following types of grants:
■
Object grants for which the current user is the grantee
■
Object grants for which an enabled role or PUBLIC is the grantee
Related View
USER_TAB_PRIVS_RECD describes the object grants for which the current user is
the grantee. This view does not display the GRANTEE column.
Column
Datatype
NULL
Description
GRANTEE
VARCHAR2(30)
NOT NULL
Name of the user to whom access was granted
OWNER
VARCHAR2(30)
NOT NULL
Owner of the object
TABLE_NAME
VARCHAR2(30)
NOT NULL
Name of the object
GRANTOR
VARCHAR2(30)
NOT NULL
Name of the user who performed the grant
PRIVILEGE
VARCHAR2(40)
NOT NULL
Privilege on the object
GRANTABLE
VARCHAR2(3)
Indicates whether the privilege was granted with the
GRANT OPTION (YES) or not (NO)
HIERARCHY
VARCHAR2(3)
Indicates whether the privilege was granted with the
HIERARCHY OPTION (YES) or not (NO)
See Also: "USER_TAB_PRIVS_RECD" on page 2-291
Static Data Dictionary Views 2-135
ALL_TAB_SUBPARTITIONS
ALL_TAB_SUBPARTITIONS
ALL_TAB_SUBPARTITIONS describes, for each table subpartition accessible to the
current user, the subpartition name, name of the table and partition to which it
belongs, and its storage attributes.
Related Views
■
■
DBA_TAB_SUBPARTITIONS provides such information for all subpartitions in
the database.
USER_TAB_SUBPARTITIONS provides such information for subpartitions of all
partitioned objects owned by the current user. This view does not display the
TABLE_OWNER column.
Note: Statistics are not collected on a per-subpartition basis.
Column
Datatype
NULL
Description
TABLE_OWNER
VARCHAR2(30)
NOT NULL
Table owner
TABLE_NAME
VARCHAR2(30)
NOT NULL
Table name
PARTITION_NAME
VARCHAR2(30)
Partition name
SUBPARTITION_NAME
VARCHAR2(30)
Subpartition name
SUBPARTITION_POSITION NUMBER
NOT NULL
Position of a subpartition within a partition
TABLESPACE_NAME
VARCHAR2(30)
NOT NULL
Name of the tablespace containing the subpartition
PCT_FREE
NUMBER
NOT NULL
Minimum percentage of free space in a block
PCT_USED
NUMBER
NOT NULL
Minimum percentage of used space in a block
INI_TRANS
NUMBER
NOT NULL
Initial number of transactions
MAX_TRANS
NUMBER
NOT NULL
Maximum number of transactions
INITIAL_EXTENT
NUMBER
Size of the initial extent in bytes
NEXT_EXTENT
NUMBER
Size of secondary extents in bytes
MIN_EXTENT
NUMBER
NOT NULL
Minimum number of extents allowed in the segment
MAX_EXTENT
NUMBER
NOT NULL
Maximum number of extents allowed in the segment
PCT_INCREASE
NUMBER
NOT NULL
Percentage increase in extent size
FREELISTS
NUMBER
Number of freelist groups allocated in this segment
FREELIST_GROUPS
NUMBER
Number of freelist groups allocated in this segment
LOGGING
VARCHAR2(3)
Logging attribute of subpartition
2-136 Oracle9i Database Reference
ALL_TABLES
Column
Datatype
NULL
Description
NUM_ROWS
NUMBER
The number of rows
BLOCKS
NUMBER
The number of blocks
EMPTY_BLOCKS
NUMBER
The number of empty blocks
AVG_SPACE
NUMBER
The average space
CHAIN_CNT
NUMBER
The chain count
AVG_ROW_LEN
NUMBER
The average row length
SAMPLE_SIZE
NUMBER
The sample size
LAST_ANALYZED
DATE
The date on which this table was most recently
analyzed
BUFFER_POOL
VARCHAR2(7)
The default buffer pool for this subpartition
GLOBAL_STATS
VARCHAR2(3)
Indicates whether column statistics for the
subpartition were collected by analyzing the table as a
whole (YES) or estimated from statistics collected for
partitions and subpartitions (NO)
USER_STATS
VARCHAR2(3)
Were the statistics entered directly by the user?
ALL_TABLES
ALL_TABLES describes all relational tables accessible to the current user. To gather
statistics for this view, use the SQL ANALYZE statement.
Related Views
■
■
DBA_TABLES describes all relational tables in the database.
USER_TABLES describes all relational tables owned by the current user. This
view does not display the OWNER column.
Note: Columns marked with an asterisk are populated only if you
collect statistics on the table with the ANALYZE statement or the
DBMS_STATS package.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
Owner of the table
TABLE_NAME
VARCHAR2(30)
Name of the table
Static Data Dictionary Views 2-137
ALL_TABLES
Column
Datatype
TABLESPACE_NAME
VARCHAR2(30)
Name of the tablespace containing the table; NULL for
partitioned, temporary and index-organized tables
CLUSTER_NAME
VARCHAR2(30)
Name of the cluster, if any, to which the table belongs
IOT_NAME
VARCHAR2(30)
Name of the index-organized table, if any, to which
the overflow entry belongs. If IOT_TYPE column is
not null, this column contains the base table name.
PCT_FREE
NUMBER
Minimum percentage of free space in a block; NULL
for partitioned tables
PCT_USED
NUMBER
Minimum percentage of used space in a block; NULL
for partitioned tables
INI_TRANS
NUMBER
Initial number of transactions; NULL for partitioned
tables
MAX_TRANS
NUMBER
Maximum number of transactions; NULL for
partitioned tables
INITIAL_EXTENT
NUMBER
Size of the initial extent in bytes; NULL for partitioned
tables
NEXT_EXTENT
NUMBER
Size of the secondary extension bytes; NULL for
partitioned tables
MIN_EXTENTS
NUMBER
Minimum number of extents allowed in the segment;
NULL for partitioned tables
MAX_EXTENTS
NUMBER
Maximum number of extents allowed in the segment;
NULL for partitioned tables
PCT_INCREASE
NUMBER
Percentage increase in extent size; NULL for
partitioned tables
FREELISTS
NUMBER
Number of process freelists allocated to this segment;
NULL for partitioned tables
FREELIST_GROUPS
NUMBER
Number of freelist groups allocated to this segment;
NULL for partitioned tables
LOGGING
VARCHAR2(3)
Logging attribute; NULL for partitioned tables
BACKED_UP
VARCHAR2(1)
Has table been backed up since last change
NUM_ROWS*
NUMBER
Number of rows in the table
BLOCKS*
NUMBER
Number of used data blocks in the table
EMPTY_BLOCKS*
NUMBER
Number of empty (never used) data blocks in the
table
AVG_SPACE*
NUMBER
Average amount of free space, in bytes, in a data
block allocated to the table
2-138 Oracle9i Database Reference
NULL
Description
ALL_TABLES
Column
Datatype
NULL
Description
CHAIN_CNT*
NUMBER
Number of rows in the table that are chained from
one data block to another, or which have migrated to
a new block, requiring a link to preserve the old
ROWID
AVG_ROW_LEN*
NUMBER
Average length of a row in the table in bytes
AVG_SPACE_FREELIST
_BLOCKS
NUMBER
The average freespace of all blocks on a freelist
NUM_FREELIST_BLOCKS
NUMBER
The number of blocks on the freelist
DEGREE
VARCHAR2(10)
The number of threads per instance for scanning the
table
INSTANCES
VARCHAR2(10)
The number of instances across which the table is to
be scanned
CACHE
VARCHAR2(5)
Whether the cluster is to be cached in the buffer cache
(CACHE | NOCACHE)
TABLE_LOCK
VARCHAR2(8)
Whether table locking is enabled or disabled
SAMPLE_SIZE
NUMBER
Sample size used in analyzing this table
LAST_ANALYZED
DATE
Date on which this table was most recently analyzed
PARTITIONED
VARCHAR2(3)
Indicates whether this table is partitioned. Set to YES
if it is partitioned.
IOT_TYPE
VARCHAR2(12)
If this is an index-organized table, then IOT_TYPE is
IOT, IOT_OVERFLOW, or IOT_MAPPING. If this is not
an index-organized table, then IOT_TYPE is NULL.
TEMPORARY
VARCHAR2(1)
Can the current session only see data that it place in
this object itself?
SECONDARY
VARCHAR2(1)
Whether the trigger is a secondary object created by
the ODCIIndexCreate method of the Oracle9i Data
Cartridge (Y |N)
NESTED
VARCHAR2(3)
Is the table a nested table?
BUFFER_POOL
VARCHAR2(7)
The default buffer pool for the object. NULL for
partitioned tables
ROW_MOVEMENT
VARCHAR2(8)
Whether partitioned row movement is enabled or
disabled
GLOBAL_STATS
VARCHAR2(3)
For partitioned tables, indicates whether statistics
were collected for the table as a whole (YES) or were
estimated from statistics on underlying partitions and
subpartitions (NO)
USER_STATS
VARCHAR2(3)
Were the statistics entered directly by the user?
Static Data Dictionary Views 2-139
ALL_TRIGGER_COLS
Column
Datatype
DURATION
VARCHAR2(15)
NULL
Description
Indicates the duration of a temporary table:
■
■
SYS$SESSION: the rows are preserved for the
duration of the session
SYS$TRANSACTION: the rows are deleted after
COMMIT
Null for a permanent table
SKIP_CORRUPT
VARCHAR2(8)
Whether Oracle ignores blocks marked corrupt
during table and index scans (ENABLED) or raises an
error (DISABLED). To enable this feature, run the
DBMS_REPAIR.SKIP_CORRUPT_BLOCKS procedure.
MONITORING
VARCHAR2(3)
Whether the table has the MONITORING attribute set
See Also:
■
"DBA_TABLES" on page 2-227
■
"USER_TABLES" on page 2-291
ALL_TRIGGER_COLS
ALL_TRIGGER_COLS describes the use of columns in triggers owned by user or in
triggers on tables owned by user. If the user has the CREATE ANY TRIGGER
privilege, this view describes the use of columns in all triggers.
Related Views
■
■
DBA_TRIGGER_COLS provides such information for all triggers in the database.
USER_TRIGGER_COLS provides such information for all triggers owned by the
current user.
Column
Datatype
NULL
Description
TRIGGER_OWNER
VARCHAR2(30)
NOT NULL
Owner of the triggers
TRIGGER_NAME
VARCHAR2(30)
NOT NULL
Name of the trigger
TABLE_OWNER
VARCHAR2(30)
NOT NULL
Owner of the table on which the trigger is defined
TABLE_NAME
VARCHAR2(30)
NOT NULL
Table on which the trigger is defined
COLUMN_NAME
VARCHAR2(4000)
Name of the column used in the trigger
COLUMN_LIST
VARCHAR2(3)
Column specified in UPDATE clause (Y | N)
2-140 Oracle9i Database Reference
ALL_TRIGGERS
Column
Datatype
COLUMN_USAGE
VARCHAR2(17)
NULL
Description
How the column is used in the trigger. All applicable
combinations of NEW, OLD, IN, OUT, and IN OUT.
ALL_TRIGGERS
ALL_TRIGGERS describes owned by the current user and triggers on tables owned
by the current user. If the user has the CREATE ANY TRIGGER privilege, then this
view describes all triggers in the database.
Related Views
■
■
DBA_TRIGGERS describes all triggers in the database.
USER_TRIGGERS describes all triggers owned by the current user. This view
does not display the OWNER column.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the trigger
TRIGGER_NAME
VARCHAR2(30)
NOT NULL
Name of the trigger
TRIGGER_TYPE
VARCHAR2(16)
When the trigger fires: BEFORE STATEMENT, BEFORE
EACH ROW, BEFORE EVENT, AFTER STATEMENT,
AFTER EACH ROW, and AFTER EVENT
TRIGGERING_EVENT
VARCHAR2(216)
The DML, DDL, or database event that fires the
trigger. For a listing of triggering events, see the
CREATE TRIGGER statement in Oracle9i SQL
Reference.
TABLE_OWNER
VARCHAR2(30)
BASE_OBJECT_TYPE
VARCHAR2(16)
The base object on which the trigger is defined:
TABLE, VIEW, SCHEMA, or DATABASE
TABLE_NAME
VARCHAR2(30)
If the base object type of the trigger is SCHEMA or
DATABASE, then this column is NULL; if the base
object type of the trigger is TABLE or VIEW, this
columns indicates the table/view name on which the
trigger is defined
COLUMN_NAME
VARCHAR2(30)
Name of the nested table column (if nested table
trigger), else null
REFERENCING_NAMES
VARCHAR2(87)
Names used for referencing OLD and NEW column
values from within the trigger
WHEN_CLAUSE
VARCHAR2(4000)
Must evaluate to TRUE for TRIGGER_BODY to execute
STATUS
VARCHAR2(8)
Whether the trigger is enabled (ENABLED|DISABLED)
NOT NULL
Owner of the table on which the trigger is defined
Static Data Dictionary Views 2-141
ALL_TYPE_ATTRS
Column
Datatype
NULL
Description
DESCRIPTION
VARCHAR2(4000)
Trigger description; useful for re-creating a trigger
creation statement
ACTION_TYPE
VARCHAR2(11)
The action type of the trigger body (CALL or PL/SQL)
TRIGGER_BODY
LONG
Statement(s) executed by the trigger when it fires
ALL_TYPE_ATTRS
ALL_TYPE_ATTRS describes the attributes of the object types accessible to the
current user.
Related Views
■
■
DBA_TYPE_ATTRS describes the attributes of all object types in the database.
USER_TYPE_ATTRS describes the attributes of the object types owned by the
current user. This view does not display the OWNER column.
Column
Datatype
OWNER
VARCHAR2(30)
TYPE_NAME
VARCHAR2(30)
NOT NULL
Name of the type
ATTR_NAME
VARCHAR2(30)
NOT NULL
Name of the attribute
ATTR_TYPE_MOD
VARCHAR2(7)
Type modifier of the attribute
ATTR_TYPE_OWNER
VARCHAR2(30)
Owner of the type of the attribute
ATTR_TYPE_NAME
VARCHAR2(30)
Name of the type of the attribute
LENGTH
NUMBER
Length of the CHAR attribute, or maximum length of
the VARCHAR or VARCHAR2 attribute.
PRECISION
NUMBER
Decimal precision of the NUMBER or DECIMAL
attribute, or binary precision of the FLOAT attribute.
SCALE
NUMBER
Scale of the NUMBER or DECIMAL attribute
CHARACTER_SET
_NAME
VARCHAR2(44)
Character set name of the attribute (CHAR_CS or
NCHAR_CS)
ATTR_NO
NUMBER
INHERITED
VARCHAR2(3)
2-142 Oracle9i Database Reference
NULL
Description
Owner of the type
NOT NULL
Syntactical order number or position of the attribute
as specified in the type specification or CREATE
TYPE statement (not to be used as an ID number)
Indicates whether the attribute is inherited from a
supertype (YES) or not (NO)
ALL_TYPE_METHODS
See Also:
■
"DBA_TYPE_ATTRS" on page 2-231
■
"USER_TYPE_ATTRS" on page 2-292
ALL_TYPE_METHODS
ALL_TYPE_METHODS describes the methods of the object types accessible to the
current user.
Related Views
■
■
DBA_TYPE_METHODS describes the methods of all object types in the database.
USER_TYPE_METHODS describes the methods of the object types owned by the
current user. This view does not display the OWNER column.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the type
TYPE_NAME
VARCHAR2(30)
NOT NULL
Name of the type
METHOD_NAME
VARCHAR2(30)
NOT NULL
Name of the method
METHOD_NO
NUMBER
NOT NULL
Method number for distinguishing overloaded
method (not to be used as ID number)
METHOD_TYPE
VARCHAR2(6)
PARAMETERS
NUMBER
NOT NULL
Number of parameters to the method
RESULTS
NUMBER
NOT NULL
Number of results returned by the method
FINAL
VARCHAR2(3)
Indicates whether the method is final (YES) or not
(NO)
INSTANTIABLE
VARCHAR2(3)
Indicates whether the method is instantiable (YES) or
not (NO)
OVERRIDING
VARCHAR2(3)
Indicates whether the method is overriding a
supertype method (YES) or not (NO)
INHERITED
VARCHAR2(3)
Indicates whether the method is inherited from a
supertype (YES) or not (NO)
Type of the method
See Also:
■
"DBA_TYPE_METHODS" on page 2-231
■
"USER_TYPE_METHODS" on page 2-292
Static Data Dictionary Views 2-143
ALL_TYPE_VERSIONS
ALL_TYPE_VERSIONS
ALL_TYPE_VERSIONS describes the versions of the object types accessible to the
current user.
Related Views
■
■
DBA_TYPE_VERSIONS describes the versions of all object types in the database.
USER_TYPE_VERSIONS describes the versions of the object types owned by the
current user. This view does not display the OWNER column.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the type
TYPE_NAME
VARCHAR2(30)
NOT NULL
Name of the type
VERSION#
NUMBER
NOT NULL
Internal version number of the type
TYPECODE
VARCHAR2(30)
Typecode of the type
STATUS
VARCHAR2(7)
Status of the type
LINE
NUMBER
TEXT
VARCHAR2(4000)
Text of the type’s spec
HASHCODE
RAW(17)
Hashcode of the type
NOT NULL
Line number of the type’s spec
See Also:
■
"DBA_TYPE_VERSIONS" on page 2-231
■
"USER_TYPE_VERSIONS" on page 2-292
ALL_TYPES
ALL_TYPES describes the object types accessible to the current user.
Related Views
■
■
DBA_TYPES describes all object types in the database.
USER_TYPES describes the object types owned by the current user. This view
does not display the OWNER column.
Column
Datatype
OWNER
VARCHAR2(30)
2-144 Oracle9i Database Reference
NULL
Description
Owner of the type
ALL_UNUSED_COL_TABS
Column
Datatype
NULL
Description
TYPE_NAME
TYPE_OID
VARCHAR2(30)
NOT NULL
Name of the type
RAW(16)
NOT NULL
Object identifier (OID) of the type
TYPECODE
VARCHAR2(30)
Typecode of the type
ATTRIBUTES
NUMBER
Number of attributes (if any) in the type
METHODS
NUMBER
Number of methods (if any) in the type
PREDEFINED
VARCHAR2(3)
Indicates whether the type is a predefined type (YES)
or not (NO)
INCOMPLETE
VARCHAR2(3)
Indicates whether the type is an incomplete type
(YES) or not (NO)
FINAL
VARCHAR2(3)
Indicates whether the type is a final type (YES) or not
(NO)
INSTANTIABLE
VARCHAR2(3)
Indicates whether the type is an instantiable type
(YES) or not (NO)
SUPERTYPE_OWNER
VARCHAR2(30)
Owner of the supertype (NULL if type is not a
subtype)
SUPERTYPE_NAME
VARCHAR2(30)
Name of the supertype (NULL if type is not a subtype)
LOCAL_ATTRIBUTES
NUMBER
Number of local (not inherited) attributes (if any) in
the subtype
LOCAL_METHODS
NUMBER
Number of local (not inherited) methods (if any) in
the subtype
TYPEID
RAW(16)
Type ID value of the type
See Also:
■
"DBA_TYPES" on page 2-231
■
"USER_TYPES" on page 2-293
ALL_UNUSED_COL_TABS
ALL_UNUSED_COL_TABS describes all tables accessible to the current user that
contain unused columns.
Related Views
■
DBA_UNUSED_COL_TABS describes all tables in the database that contain
unused columns.
Static Data Dictionary Views 2-145
ALL_UPDATABLE_COLUMNS
■
USER_UNUSED_COL_TABS describes all tables owned by the current user that
contain unused columns. This view does not display the OWNER column.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
The owner of the object
TABLE_NAME
VARCHAR2(30)
NOT NULL
The name of the table
COUNT
NUMBER
The number of unused columns
ALL_UPDATABLE_COLUMNS
ALL_UPDATABLE_COLUMNS describes all columns in a join view that are updatable
by the current user.
Related Views
■
■
Column
DBA_UPDATABLE_COLUMNS describes all columns in a join view that are
updatable by the database administrator.
USER_UPDATABLE_COLUMNS describes all columns owned by the current user
that are in a join view and are updatable by the current user.
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Table owner
TABLE_NAME
VARCHAR2(30)
NOT NULL
Table name
COLUMN_NAME
VARCHAR2(30)
NOT NULL
Column name
UPDATABLE
VARCHAR2(3)
Indicates whether the column is updatable
INSERTABLE
VARCHAR2(3)
Indicates whether the column is insertable
DELETABLE
VARCHAR2(3)
Indicates whether the column is deletable
ALL_USERS
ALL_USERS lists all users of the database visible to the current user. This view does
not describe the users (see the related views).
Related Views
■
DBA_USERS describes all users of the database, and contains more columns
than ALL_USERS.
2-146 Oracle9i Database Reference
ALL_USTATS
■
USER_USERS describes the current user, and contains more columns than ALL_
USERS.
Column
Datatype
NULL
Description
USERNAME
USER_ID
VARCHAR2(30)
NOT NULL
Name of the user
NUMBER
NOT NULL
ID number of the user
CREATED
DATE
NOT NULL
User creation date
See Also:
■
"DBA_USERS" on page 2-233
■
"USER_USERS" on page 2-293
ALL_USTATS
ALL_USTATS describes all user-defined statistics accessible to the current user.
Related Views
■
DBA_USTATS describes all user-defined statistics in the database.
■
USER_USTATS describes all user-defined statistics owned by the current user.
Column
Datatype
NULL
Description
OBJECT_OWNER
VARCHAR2(30)
Owner of the table or index for which the statistics
have been collected
OBJECT_NAME
VARCHAR2(30)
Name of the table or index for which the statistics
have been collected
OBJECT_TYPE
VARCHAR2(6)
Indicates the type of object for which statistics have
been collected: COLUMN or INDEX
ASSOCIATION
VARCHAR2(8)
DIRECT Indicates a direct association with the object
for which the statistics have been collected.
IMPLICIT indicates the association for which the
statistics have been collected is with the column type
or index type, and the object is an instance of that
column type or index type.
COLUMN_NAME
VARCHAR2(30)
Column name, if property is column for which
statistics have been collected
STATSTYPE_SCHEMA
VARCHAR2(30)
Schema of statistics type which was used to collect the
statistics
Static Data Dictionary Views 2-147
ALL_VARRAYS
Column
Datatype
NULL
Description
STATSTYPE_NAME
VARCHAR2(30)
Name of statistics type which was used to collect
statistics
STATISTICS
RAW(2000)
User collected statistics for the object
PARTITION_NAME
VARCHAR2(30)
Partition name of a table. If null, the table is either
non-partitioned or the entry corresponds to the
aggregate statistics for the table.
ALL_VARRAYS
ALL_VARRAYS describes all varrays accessible to the current user.
Related Views
■
■
DBA_VARRAYS describes all varrays in the database.
USER_VARRAYS describes all varrays owned by the current user. This view
does not display the OWNER column.
Column
Datatype
OWNER
VARCHAR2(30)
Owner of the table containing the varray
PARENT_TABLE_NAME
VARCHAR2(30)
Name of the containing table
PARENT_TABLE_COLUMN
VARCHAR2(4000)
Name of the varray column or attribute
TYPE_OWNER
VARCHAR2(30)
Owner of the varray type
TYPE_NAME
VARCHAR2(30)
Name of the varray type
LOB_NAME
VARCHAR2(30)
Name of the LOB if the varray is stored in a LOB
STORAGE_SPEC
VARCHAR2(30)
DEFAULT value indicates that the storage was
defaulted. USER_SPECIFIED value indicates that the
storage was user-specified.
RETURN_TYPE
VARCHAR2(20)
Return type of the column
ELEMENT_SUBSTITUTABLE VARCHAR2(25)
NULL
Description
Indicates whether the varray element is substitutable
(Y) or not (N)
ALL_VIEWS
ALL_VIEWS describes the views accessible to the current user.
Related Views
■
DBA_VIEWS describes all views in the database.
2-148 Oracle9i Database Reference
ALL_XML_SCHEMAS
■
USER_VIEWS describes the views owned by the current user. This view does
not display the OWNER column.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the view
VIEW_NAME
VARCHAR2(30)
NOT NULL
Name of the view
TEXT_LENGTH
NUMBER
Length of the view text
TEXT
LONG
View text
TYPE_TEXT_LENGTH
NUMBER
Length of the type clause of the typed view
TYPE_TEXT
VARCHAR2(4000)
Type clause of the typed view
OID_TEXT_LENGTH
NUMBER
Length of the WITH OID clause of the typed view
OID_TEXT
VARCHAR2(4000)
WITH OID clause of the typed view
VIEW_TYPE_OWNER
VARCHAR2(30)
Owner of the type of the view if the view is a typed
view
VIEW_TYPE
VARCHAR2(30)
Type of the view if the view is a typed view
SUPERVIEW_NAME
VARCHAR2(30)
Name of the superview
See Also:
■
"DBA_VIEWS" on page 2-234
■
"USER_VIEWS" on page 2-294
ALL_XML_SCHEMAS
ALL_XML_SCHEMAS describes the registered XML schemas accessible to the current
user.
Related Views
■
■
DBA_XML_SCHEMAS describes all registered XML schemas in the database.
USER_XML_SCHEMAS describes the registered XML schemas owned by the
current user. This view does not display the OWNER column.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
Owner of the XML schema
SCHEMA_URL
VARCHAR2(700)
Schema URL of the XML schema
Static Data Dictionary Views 2-149
ALL_XML_TAB_COLS
Column
Datatype
NULL
Description
LOCAL
VARCHAR2(3)
Indicates whether the XML schema is local (YES) or
global (NO)
SCHEMA
XMLTYPE
XML schema document
INT_OBJNAME
VARCHAR2(4000)
Internal database object name for the schema
QUAL_SCHEMA_URL
VARCHAR2(767)
Fully qualified schema URL
See Also:
■
"DBA_XML_SCHEMAS" on page 2-234
■
"USER_XML_SCHEMAS" on page 2-294
ALL_XML_TAB_COLS
ALL_XML_TAB_COLS describes the columns of the XML tables accessible to the
current user.
Related Views
■
■
Column
DBA_XML_TAB_COLS describes the columns of all XML tables in the database.
USER_XML_TAB_COLS describes the columns of the XML tables owned by the
current user. This view does not display the OWNER column.
Datatype
NULL
Description
OWNER
VARCHAR2(30)
Owner of the XML table
TABLE_NAME
VARCHAR2(30)
Name of the XML table
COLUMN_NAME
VARCHAR2(4000)
Name of the XML table column
XMLSCHEMA
VARCHAR2(700)
Name of the XML Schema that is used for the table
definition
SCHEMA_OWNER
VARCHAR2(30)
Owner of the XML Schema that is used for the table
definition
ELEMENT_NAME
VARCHAR2(256)
Name of the XML SChema element that is used for
the table
STORAGE_TYPE
VARCHAR2(17)
Storage option for the XMLtype data
(OBJECT-RELATIONAL or CLOB)
2-150 Oracle9i Database Reference
ALL_XML_VIEW_COLS
See Also:
■
"DBA_XML_TAB_COLS" on page 2-235
■
"USER_XML_TAB_COLS" on page 2-294
ALL_XML_TABLES
ALL_XML_TABLES describes the XML tables accessible to the current user.
Related Views
■
■
DBA_XML_TABLES describes all XML tables in the database.
USER_XML_TABLES describes the XML tables owned by the current user. This
view does not display the OWNER column.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
Owner of the XML table
TABLE_NAME
VARCHAR2(30)
Name of the XML table
XMLSCHEMA
VARCHAR2(700)
Name of the XML Schema that is used for the table
definition
SCHEMA_OWNER
VARCHAR2(30)
Owner of the XML Schema that is used for the table
definition
ELEMENT_NAME
VARCHAR2(256)
Name of the XML SChema element that is used for
the table
STORAGE_TYPE
VARCHAR2(17)
Storage option for the XMLtype data
(OBJECT-RELATIONAL or CLOB)
See Also:
■
"DBA_XML_TABLES" on page 2-235
■
"USER_XML_TABLES" on page 2-294
ALL_XML_VIEW_COLS
ALL_XML_VIEW_COLS describes the columns of the XML views accessible to the
current user.
Related Views
■
DBA_XML_VIEW_COLS describes the columns of all XML views in the database.
Static Data Dictionary Views 2-151
ALL_XML_VIEWS
■
USER_XML_VIEW_COLS describes the columns of the XML views owned by the
current user. This view does not display the OWNER column.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
Owner of the XML view
VIEW_NAME
VARCHAR2(30)
Name of the XML view
COLUMN_NAME
VARCHAR2(4000)
Name of the XML view column
XMLSCHEMA
VARCHAR2(700)
Name of the XML Schema that is used for the view
definition
SCHEMA_OWNER
VARCHAR2(30)
Owner of the XML Schema that is used for the view
definition
ELEMENT_NAME
VARCHAR2(256)
Name of the XML SChema element that is used for
the view
See Also:
■
"DBA_XML_VIEW_COLS" on page 2-235
■
"USER_XML_VIEW_COLS" on page 2-294
ALL_XML_VIEWS
ALL_XML_VIEWS describes the XML views accessible to the current user.
Related Views
■
■
DBA_XML_VIEWS describes all XML views the database.
USER_XML_VIEWS describes the XML views owned by the current user. This
view does not display the OWNER column.
Column
Datatype
OWNER
VARCHAR2(30)
Owner of the XML view
VIEW_NAME
VARCHAR2(30)
Name of the XML view
XMLSCHEMA
VARCHAR2(700)
Name of the XML Schema that is used for the view
definition
SCHEMA_OWNER
VARCHAR2(30)
Owner of the XML Schema that is used for the view
definition
ELEMENT_NAME
VARCHAR2(256)
Name of the XML SChema element that is used for
the view
2-152 Oracle9i Database Reference
NULL
Description
CHAINED_ROWS
See Also:
■
"DBA_XML_VIEWS" on page 2-235
■
"USER_XML_VIEWS" on page 2-294
AUDIT_ACTIONS
AUDIT_ACTIONS describes audit trail action type codes. This table can be used to
map action type numbers to action type names.
Column
Datatype
NULL
Description
ACTION
NUMBER
NOT NULL
Numeric audit trail action type code. These values
also appear in the COMMAND column of the
V$SESSION dynamic performance view, and are
listed with that view.
See Also: Table 3–3 on page 3-131 for a listing of the
action type codes
NAME
VARCHAR2(27)
NOT NULL
Name of the type of audit trail action
CATALOG
CATALOG is included for compatibility with Oracle version 5. Oracle Corporation
recommends that you not use this view.
CAT
CAT is a synonym for USER_CATALOG.
See Also: "USER_CATALOG" on page 2-266
CHAINED_ROWS
CHAINED_ROWS stores the output for the ANALYZE statement with the LIST
CHAINED ROWS clause. You must run the utlchain.sql or utlchn1.sql script
to create this table.
Column
Description
OWNER_NAME
Table owner
TABLE_NAME
Table name
Static Data Dictionary Views 2-153
CHANGE_SOURCES
Column
Description
CLUSTER_NAME
Cluster the table is in, if any
PARTITION_NAME
The name of the partition
SUBPARTITION_NAME
The name of the subpartition
HEAD_ROWID
ROWID the chained row is accessed by
ANALYZE_TIMESTAMP
Date/time that the ANALYZE statement was issued
CHANGE_SOURCES
CHANGE_SOURCES enables publishers to view existing change sources. You must
have the SELECT_CATALOG_ROLE privilege to access this view.
Column
Datatype
NULL
Description
SOURCE_NAME
VARCHAR2(30)
NOT NULL
User specified identifier. For synchronous change
sources, there is one pre-created source with the
SOURCE_NAME "SYNC_SOURCE."
DBID
NUMBER
LOG_DIRECTORY
VARCHAR2(4000)
LOGFILE_PATTERN
VARCHAR2(30)
This pattern enables you to recognize log files (for
example, *.log) if the log location has files in it other
than log files
SOURCE_DESCRIPTION
VARCHAR2(255)
Comment field for customers
CREATED
DATE
The database identifier of the Oracle host instance (set
by CDC when the first log is added to LogMiner)
NOT NULL
NOT NULL
File system path on the CDC machine where log files
for this source are maintained
Creation date of the change source
CHANGE_SETS
CHANGE_SETS enables publishers to view existing change sets. You must have the
SELECT_CATALOG_ROLE privilege to access this view.
Column
Datatype
NULL
Description
SET_NAME
VARCHAR2(30)
NOT NULL
User specified identifier. For synchronous change
sources, there is one pre-created source with the SET_
NAME "SYNC_SET."
CHANGE_SOURCE_NAME
VARCHAR2(30)
NOT NULL
The change source to which this set belongs
BEGIN_DATE
DATE
Starting point for capturing change data
END_DATE
DATE
Stopping point for capturing change data
2-154 Oracle9i Database Reference
CLU
Column
Datatype
NULL
Description
BEGIN_SCN
NUMBER
Starting point for capturing change data
END_SCN
NUMBER
Stopping point for capturing change data
FRESHNESS_DATE
DATE
Stopping point for the last successful advance
FRESHNESS_SCN
NUMBER
Stopping point for the last successful advance
ADVANCE_ENABLED
VARCHAR2(1)
NOT NULL
Identifies eligibility for advance (Y|N)
IGNORE_DDL
VARCHAR2(1)
NOT NULL
Identifies whether to continue (Y) or stop (N)
CREATED
DATE
NOT NULL
The creation date of the change set
Used during advance (optional)
ROLLBACK_SEGMENT_NAME VARCHAR2(30)
ADVANCING
VARCHAR2(1)
NOT NULL
Identifies whether or not (Y|N) an advance is in
progress for this set (set by advance)
PURGING
VARCHAR2(1)
NOT NULL
Identifies whether or not (Y|N) a purge of old data is
in progress for this change set (set by advance)
LOWEST_SCN
NUMBER
NOT NULL
Current low water mark for change data remaining in
this set after the latest purge
TABLESPACE
VARCHAR2(30)
NOT NULL
Location where advance creates LCR staging tables
CHANGE_TABLES
CHANGE_TABLES enables publishers to see existing change tables. You must have
the SELECT_CATALOG_ROLE privilege to access this view.
Column
Datatype
NULL
Description
CHANGE_TABLE_SCHEMA
VARCHAR2(30)
NOT NULL
Change table owner
CHANGE_TABLE_NAME
VARCHAR2(30)
NOT NULL
Change table name
CHANGE_SET_NAME
VARCHAR2(30)
NOT NULL
The change set this table belongs to
SOURCE_SCHEMA_NAME
VARCHAR2(30)
NOT NULL
The table owner in the source system
SOURCE_TABLE_NAME
VARCHAR2(30)
NOT NULL
The name of the corresponding table in the source
system
CREATED
DATE
NOT NULL
Date on which this change table was created
CREATED_SCN
NUMBER
CAPTURED_VALUES
VARCHAR2(1)
The system commit SCN when this table was created
NOT NULL
Indicates the values O (old), N (new), or B (both)
CLU
CLU is a synonym for USER_CLUSTERS.
Static Data Dictionary Views 2-155
CODE_PIECES
See Also: "USER_CLUSTERS" on page 2-266
CODE_PIECES
Oracle accesses this view to create the DBA_OBJECT_SIZE and USER_OBJECT_
SIZE views.
See Also: "DBA_OBJECT_SIZE" on page 2-200 and "USER_
OBJECT_SIZE" on page 2-279
CODE_SIZE
Oracle accesses this view to create the DBA_OBJECT_SIZE and USER_OBJECT_
SIZE views.
See Also: "DBA_OBJECT_SIZE" on page 2-200 and "USER_
OBJECT_SIZE" on page 2-279
COL
COL is included for compatibility with Oracle version 5. Oracle Corporation
recommends that you not use this view.
COLS
COLS is a synonym for USER_TAB_COLUMNS.
See Also: "USER_TAB_COLUMNS" on page 2-289
COLUMN_PRIVILEGES
COLUMN_PRIVILEGES is included for compatibility with Oracle version 6. Oracle
Corporation does not recommend use of this view.
DATABASE_PROPERTIES
DATABASE_PROPERTIES lists Permanent database properties.
Column
Datatype
NULL
Description
PROPERTY_NAME
VARCHAR2(30)
NOT NULL
Property name
2-156 Oracle9i Database Reference
DBA_2PC_PENDING
Column
Datatype
NULL
Description
PROPERTY_VALUE
VARCHAR2(4000)
Property value
DESCRIPTION
VARCHAR2(4000)
Property description
DBA_2PC_NEIGHBORS
DBA_2PC_NEIGHBORS describes incoming and outgoing connections for pending
transactions.
Column
Datatype
NULL
Description
LOCAL_TRAN_ID
VARCHAR2(22)
Local identifier of a transaction
IN_OUT
VARCHAR2(3)
IN for incoming connections, OUT for outgoing
DATABASE
VARCHAR2(128)
IN for client database name, OUT for outgoing
database link
DBUSER_OWNER
VARCHAR2(30)
IN for name of local user, OUT for owner of database
link
INTERFACE
VARCHAR2(1)
C for request commit, otherwise N for prepare or
request readonly commit
DBID
VARCHAR2(16)
The database ID at the other end of the connection
SESS#
NUMBER
Session number of the connection at this database
BRANCH
VARCHAR2(128)
Transaction branch ID of the connection at this
database
DBA_2PC_PENDING
DBA_2PC_PENDING describes distributed transactions awaiting recovery.
Column
Datatype
NULL
Description
LOCAL_TRAN_ID
VARCHAR2(22)
NOT NULL
String of form: n.n.n; n is a number
GLOBAL_TRAN_ID
VARCHAR2(169)
STATE
VARCHAR2(16)
MIXED
VARCHAR2(3)
YES indicates part of the transaction committed and
part rolled back
ADVICE
VARCHAR2(1)
C for commit, R for rollback, else NULL
TRAN_COMMENT
VARCHAR2(2000)
Text for commit work comment text
Globally unique transaction ID
NOT NULL
Collecting, prepared, committed, forced commit, or
forced rollback
Static Data Dictionary Views 2-157
DBA_ALL_TABLES
Column
Datatype
NULL
Description
FAIL_TIME
DATE
NOT NULL
Value of SYSDATE when the row was inserted
(transaction or system recovery)
FORCE_TIME
DATE
RETRY_TIME
DATE
OS_USER
VARCHAR2(64)
Operating system-specific name for the end-user
OS_TERMINAL
VARCHAR2(255)
Operating system-specific name for the end-user
terminal
HOST
VARCHAR2(128)
Name of the host machine for the end-user
DB_USER
VARCHAR2(30)
Oracle user name of the end-user at the topmost
database
COMMIT#
VARCHAR2(16)
Global commit number for committed transactions
Time of manual force decision (null if not forced
locally)
NOT NULL
Time automatic recovery (RECO) last tried to recover
the transaction
DBA_ALL_TABLES
DBA_ALL_TABLES displays descriptions of all object tables and relational tables in
the database. Its columns are the same as those in "ALL_ALL_TABLES" on page 2-6.
DBA_APPLICATION_ROLES
DBA_APPLICATION_ROLES describes all the roles that have authentication policy
functions defined.
Column
Datatype
NULL
Description
ROLE
VARCHAR2(30)
NOT NULL
Name of the application role
SCHEMA
VARCHAR2(30)
NOT NULL
Schema of the authorized package
PACKAGE
VARCHAR2(30)
NOT NULL
Name of the authorized package
DBA_APPLY
DBA_APPLY displays information about all apply processes in the database. Its
columns are the same as those in ALL_APPLY.
See Also: "ALL_APPLY" on page 2-8
2-158 Oracle9i Database Reference
DBA_APPLY_INSTANTIATED_OBJECTS
DBA_APPLY_CONFLICT_COLUMNS
DBA_APPLY_CONFLICT_COLUMNS displays information about conflict handlers on
all tables in the database. Its columns are the same as those in ALL_APPLY_
CONFLICT_COLUMNS.
See Also: "ALL_APPLY_CONFLICT_COLUMNS" on page 2-9
DBA_APPLY_DML_HANDLERS
DBA_APPLY_DML_HANDLERS displays information about the DML handlers on all
tables in the database. Its columns are the same as those in ALL_APPLY_DML_
HANDLERS.
See Also: "ALL_APPLY_DML_HANDLERS" on page 2-10
DBA_APPLY_ERROR
DBA_APPLY_ERROR displays information about error transactions generated by all
apply processes in the database. Its columns are the same as those in ALL_APPLY_
ERROR.
See Also: "ALL_APPLY_ERROR" on page 2-10
DBA_APPLY_INSTANTIATED_OBJECTS
DBA_APPLY_INSTANTIATED_OBJECTS displays information about objects for
which an instantiation SCN has been set.
Column
Datatype
NULL
Description
SOURCE_DATABASE
VARCHAR2(128)
NOT NULL
Name of the database where the object originated
SOURCE_OBJECT_OWNER
VARCHAR2(30)
NOT NULL
Owner of the object at the source database
SOURCE_OBJECT_NAME
VARCHAR2(30)
NOT NULL
Name of the object at the source database
SOURCE_OBJECT_TYPE
NUMBER
NOT NULL
Type of the object at the source database
INSTANTIATION_SCN
NUMBER
Instantiation SCN for the object. Only changes
committed after this SCN are applied by an apply
process.
IGNORE_SCN
NUMBER
SCN below which the instantiation SCN cannot be
set. This value corresponds to the SCN value at the
source database at the time when the object was
prepared for instantiation.
Static Data Dictionary Views 2-159
DBA_APPLY_KEY_COLUMNS
Column
Datatype
APPLY_DATABASE_LINK
VARCHAR2(128)
NULL
Description
Database link to which changes are applied. If null,
then changes are applied to the local database.
DBA_APPLY_KEY_COLUMNS
DBA_APPLY_KEY_COLUMNS displays information about substitute key columns for
all tables in the database. Its columns are the same as those in ALL_APPLY_KEY_
COLUMNS.
See Also: "ALL_APPLY_KEY_COLUMNS" on page 2-11
DBA_APPLY_PARAMETERS
DBA_APPLY_PARAMETERS displays information about the parameters for all apply
processes in the database. Its columns are the same as those in ALL_APPLY_
PARAMETERS.
See Also: "ALL_APPLY_PARAMETERS" on page 2-12
DBA_APPLY_PROGRESS
DBA_APPLY_PROGRESS displays information about the progress made by all apply
processes in the database. Its columns are the same as those in ALL_APPLY_
PROGRESS.
See Also: "ALL_APPLY_PROGRESS" on page 2-12
DBA_AQ_AGENT_PRIVS
DBA_AQ_AGENT_PRIVS displays information about the registered AQ agents that
are mapped to all users in the database.
Related View
USER_AQ_AGENT_PRIVS displays information about the registered AQ agents that
are mapped to the current user. This view does not display the DB_USERNAME
column.
2-160 Oracle9i Database Reference
DBA_ATTRIBUTE_TRANSFORMATIONS
Column
Datatype
NULL
Description
AGENT_NAME
VARCHAR2(30)
NOT NULL
Name of the AQ agent
DB_USERNAME
VARCHAR2(30)
Name of the database user that the agent maps to
HTTP_ENABLED
VARCHAR2(4)
Indicates whether the agent is allowed to access AQ
through HTTP (YES) or not (NO)
SMTP_ENABLED
VARCHAR2(4)
Indicates whether the agent is allowed to access AQ
through SMTP (YES) or not (NO)
See Also: "USER_AQ_AGENT_PRIVS" on page 2-263
DBA_AQ_AGENTS
DBA_AQ_AGENTS displays information about all registered AQ agents in the
database.
Column
Datatype
NULL
Description
AGENT_NAME
VARCHAR2(30)
NOT NULL
Name of the AQ agent
HTTP_ENABLED
VARCHAR2(4)
Indicates whether the agent is allowed to access AQ
through HTTP (YES) or not (NO)
SMTP_ENABLED
VARCHAR2(4)
Indicates whether the agent is allowed to access AQ
through SMTP (YES) or not (NO)
DBA_ASSOCIATIONS
DBA_ASSOCIATIONS describes all user-defined statistics in the database. Its
columns are the same as those for "ALL_ASSOCIATIONS" on page 2-14.
DBA_ATTRIBUTE_TRANSFORMATIONS
DBA_ATTRIBUTE_TRANSFORMATIONS displays information about the
transformation functions for all transformations in the database.
Related View
USER_ATTRIBUTE_TRANSFORMATIONS displays information about the
transformation functions for the transformations owned by the current user. This
view does not display the OWNER column.
Static Data Dictionary Views 2-161
DBA_AUDIT_EXISTS
Column
Datatype
NULL
Description
TRANSFORMATION_ID
NUMBER
NOT NULL
Unique identifier for the transformation
OWNER
VARCHAR2(30)
NOT NULL
Owning user of the transformation
NAME
VARCHAR2(30)
NOT NULL
Transformation name
FROM_TYPE
VARCHAR2(61)
Source type name
TO_TYPE
VARCHAR2(91)
Target type name
ATTRIBUTE
NUMBER
ATTRIBUTE_
TRANSFORMATION
VARCHAR2(4000)
NOT NULL
Target type attribute number
Transformation function for the attribute
See Also: "USER_ATTRIBUTE_TRANSFORMATIONS" on
page 2-264
DBA_AUDIT_EXISTS
DBA_AUDIT_EXISTS lists audit trail entries produced by AUDIT EXISTS and
AUDIT NOT EXISTS.
Column
Datatype
OS_USERNAME
VARCHAR2(255)
Operating system login username of the user whose
actions were audited
USERNAME
VARCHAR2(30)
Name (not ID number) of the user whose actions were
audited
USERHOST
VARCHAR2(128)
Numeric instance ID for the Oracle instance from
which the user is accessing the database
TERMINAL
VARCHAR2(255)
Identifier of the user’s terminal
TIMESTAMP
DATE
OWNER
VARCHAR2(30)
Intended creator of the non-existent object
OBJ_NAME
VARCHAR2(128)
Name of the object affected by the action
ACTION_NAME
VARCHAR2(27)
Name of the action type corresponding to the numeric
code in the ACTION column in DBA_AUDIT_TRAIL
NEW_OWNER
VARCHAR2(30)
Owner of the object named in the NEW_NAME column
NEW_NAME
VARCHAR2(128)
New name of an object after a RENAME or the name of
the underlying object
OBJ_PRIVILEGE
VARCHAR2(16)
Object privileges granted or revoked by a GRANT or
REVOKE statement
2-162 Oracle9i Database Reference
NULL
NOT NULL
Description
Timestamp for the creation of the audit trail entry
DBA_AUDIT_OBJECT
Column
Datatype
NULL
Description
SYS_PRIVILEGE
VARCHAR2(40)
System privileges granted or revoked by a GRANT or
REVOKE statement
GRANTEE
VARCHAR2(30)
Name of the grantee specified in a GRANT or REVOKE
statement
SESSIONID
NUMBER
NOT NULL
Numeric ID for each Oracle session
ENTRYID
NUMBER
NOT NULL
Numeric ID for each audit trail entry in the session
STATEMENTID
NUMBER
NOT NULL
Numeric ID for each statement run
RETURNCODE
NUMBER
NOT NULL
Oracle error code generated by the action. Some
useful values:
■
0: the action succeeded
■
2004: security violation
CLIENT_ID
VARCHAR2(64)
Client identifier in each Oracle session
SESSION_CPU
NUMBER
Amount of CPU time used by each Oracle session
DBA_AUDIT_OBJECT
DBA_AUDIT_OBJECT contains audit trail records for all objects in the system.
Related View
USER_AUDIT_OBJECT contains audit trail records for all objects accessible to the
current user.
Column
Datatype
NULL
OS_USERNAME
VARCHAR2(255)
Operating system login username of the user whose
actions were audited
USERNAME
VARCHAR2(30)
Name (not ID number) of the user whose actions were
audited
USERHOST
VARCHAR2(2000)
Numeric instance ID for the Oracle instance from
which the user is accessing the database
TERMINAL
VARCHAR2(2000)
Identifier of the user’s terminal
TIMESTAMP
DATE
OWNER
VARCHAR2(30)
Creator of the object affected by the action
OBJ_NAME
VARCHAR2(128)
Name of the object affected by the action
ACTION_NAME
VARCHAR2(27)
Name of the action type corresponding to the numeric
code in the ACTION column in DBA_AUDIT_TRAIL
NOT NULL
Description
Timestamp for the creation of the audit trail entry or
login time for the CONNECT statement
Static Data Dictionary Views 2-163
DBA_AUDIT_POLICIES
Column
Datatype
NULL
Description
NEW_OWNER
VARCHAR2(30)
Owner of the object named in the NEW_NAME column
NEW_NAME
VARCHAR2(128)
New name of an object after a RENAME or the name of
the underlying object
SES_ACTIONS
VARCHAR2(19)
Session summary (a string of 16 characters, one for
each action type in the order ALTER, AUDIT,
COMMENT, DELETE, GRANT, INDEX, INSERT,
LOCK, RENAME, SELECT, UPDATE,
REFERENCES, and EXECUTE. Positions 14, 15, and 16
are reserved for future use. The characters are: - for
none, S for success, F for failure, and B for both).
COMMENT_TEXT
VARCHAR2(4000)
Text comment on the audit trail
SESSIONID
NUMBER
NOT NULL
Numeric ID for each Oracle session
ENTRYID
NUMBER
NOT NULL
Numeric ID for each audit trail entry in the session
STATEMENTID
NUMBER
NOT NULL
Numeric ID for each statement run
RETURNCODE
NUMBER
NOT NULL
Oracle error code generated by the action. Some
useful values:
■
0: the action succeeded
■
2004: security violation
PRIV_USED
VARCHAR2(40)
System privilege used to execute the action
CLIENT_ID
VARCHAR2(64)
Client identifier in each Oracle session
SESSION_CPU
NUMBER
Amount of CPU time used by each Oracle session
DBA_AUDIT_POLICIES
DBA_AUDIT_POLICIES describes all fine-grained auditing policies in the database.
Its columns are the same as those in ALL_AUDIT_POLICIES.
See Also: "ALL_AUDIT_POLICIES" on page 2-15
DBA_AUDIT_SESSION
DBA_AUDIT_SESSION lists all audit trail records concerning CONNECT and
DISCONNECT.
Related View
USER_AUDIT_SESSION contains audit trail records concerning connections and
disconnections of the current user.
2-164 Oracle9i Database Reference
DBA_AUDIT_STATEMENT
Column
Datatype
NULL
OS_USERNAME
VARCHAR2(255)
Operating system login username of the user whose
actions were audited
USERNAME
VARCHAR2(30)
Name (not ID number) of the user whose actions were
audited
USERHOST
VARCHAR2(2000)
Numeric instance ID for the Oracle instance from
which the user is accessing the database
TERMINAL
VARCHAR2(2000)
Identifier of the user’s terminal
TIMESTAMP
DATE
ACTION_NAME
VARCHAR2(27)
Name of the action type corresponding to the numeric
code in the ACTION column in DBA_AUDIT_TRAIL
LOGOFF_TIME
DATE
Timestamp for user log off
LOGOFF_LREAD
NUMBER
Logical reads for the session
LOGOFF_PREAD
NUMBER
Physical reads for the session
LOGOFF_LWRITE
NUMBER
Logical writes for the session
LOGOFF_DLOCK
VARCHAR2(40)
Deadlocks detected during the session
SESSIONID
NUMBER
NOT NULL
Numeric ID for each Oracle session
RETURNCODE
NUMBER
NOT NULL
Oracle error code generated by the action. Some
useful values:
NOT NULL
Description
Timestamp for the creation of the audit trail entry or
login time for the CONNECT statement
■
0: the action succeeded
■
2004: security violation
CLIENT_ID
VARCHAR2(64)
Client identifier in each Oracle session
SESSION_CPU
NUMBER
Amount of CPU time used by each Oracle session
DBA_AUDIT_STATEMENT
DBA_AUDIT_STATEMENT lists audit trail records concerning GRANT, REVOKE,
AUDIT, NOAUDIT, and ALTER SYSTEM statements throughout the database.
Related View
USER_AUDIT_STATEMENT contains audit trail records for the same statements
issued by the current user.
Static Data Dictionary Views 2-165
DBA_AUDIT_STATEMENT
Column
Datatype
OS_USERNAME
VARCHAR2(255)
Operating system login username of the user whose
actions were audited
USERNAME
VARCHAR2(30)
Name (not ID number) of the user whose actions were
audited
USERHOST
VARCHAR2(2000)
Numeric instance ID for the Oracle instance from
which the user is accessing the database
TERMINAL
VARCHAR2(2000)
Identifier of the user’s terminal
TIMESTAMP
DATE
OWNER
VARCHAR2(30)
Creator of the object affected by the action
OBJ_NAME
VARCHAR2(128)
Name of object affected by the action
ACTION_NAME
VARCHAR2(27)
Name of the action type corresponding to the numeric
code in the ACTION column in DBA_AUDIT_TRAIL
NEW_NAME
VARCHAR2(128)
New name of an object after a RENAME or the name of
the underlying object
OBJ_PRIVILEGE
VARCHAR2(16)
Object privileges granted or revoked by a GRANT or
REVOKE statement
SYS_PRIVILEGE
VARCHAR2(40)
System privileges granted or revoked by a GRANT or
REVOKE statement
ADMIN_OPTION
VARCHAR2(1)
Signifies the role or system privilege was granted
with ADMIN option
GRANTEE
VARCHAR2(30)
Name of grantee specified in a GRANT or REVOKE
statement
AUDIT_OPTION
VARCHAR2(40)
Auditing option set with the AUDIT statement
SES_ACTIONS
VARCHAR2(19)
Session summary (a string of 16 characters, one for
each action type in the order ALTER, AUDIT,
COMMENT, DELETE, GRANT, INDEX, INSERT,
LOCK, RENAME, SELECT, UPDATE,
REFERENCES, and EXECUTE. Positions 14, 15, and 16
are reserved for future use. The characters are: - for
none, S for success, F for failure, and B for both).
COMMENT_TEXT
VARCHAR2(4000)
Text comment on the audit trail, inserted by the
application
SESSIONID
NUMBER
NOT NULL
Numeric ID for each Oracle session
ENTRYID
NUMBER
NOT NULL
Numeric ID for each audit trail entry in the session
STATEMENTID
NUMBER
NOT NULL
Numeric ID for each statement run
2-166 Oracle9i Database Reference
NULL
NOT NULL
Description
Timestamp for the creation of the audit trail entry or
login time for the CONNECT statement
DBA_AUDIT_TRAIL
Column
Datatype
NULL
Description
RETURNCODE
NUMBER
NOT NULL
Oracle error code generated by the action. Some
useful values:
PRIV_USED
■
0: the action succeeded
■
2004: security violation
System privilege used to execute the action
VARCHAR2(40)
CLIENT_ID
VARCHAR2(64)
Client identifier in each Oracle session
SESSION_CPU
NUMBER
Amount of CPU time used by each Oracle session
DBA_AUDIT_TRAIL
DBA_AUDIT_TRAIL lists all audit trail entries.
Related View
USER_AUDIT_TRAIL contains all audit trail entries related to the current user.
Column
Datatype
NULL
OS_USERNAME
VARCHAR2(255)
Operating system login username of the user whose
actions were audited
USERNAME
VARCHAR2(30)
Name (not ID number) of the user whose actions were
audited
USERHOST
VARCHAR2(128)
Numeric instance ID for the Oracle instance from
which the user is accessing the database. Used only in
environments with distributed file systems and
shared database files.
TERMINAL
VARCHAR2(255)
Identifier of the user’s terminal
TIMESTAMP
DATE
OWNER
VARCHAR2(30)
Creator of the object affected by the action
OBJ_NAME
VARCHAR2(128)
Name of the object affected by the action
ACTION
NUMBER
ACTION_NAME
VARCHAR2(27)
Name of the action type corresponding to the numeric
code in the ACTION column
NEW_OWNER
VARCHAR2(30)
Owner of the object named in the NEW_NAME column
NEW_NAME
VARCHAR2(128)
New name of the object after a RENAME or the name of
the underlying object
NOT NULL
NOT NULL
Description
Timestamp for the creation of the audit trail entry or
login time for the CONNECT statement
Numeric action type code. The corresponding name
of the action type is in the ACTION_NAME column.
Static Data Dictionary Views 2-167
DBA_AUDIT_TRAIL
Column
Datatype
NULL
Description
OBJ_PRIVILEGE
VARCHAR2(16)
Object privileges granted or revoked by a GRANT or
REVOKE statement
SYS_PRIVILEGE
VARCHAR2(40)
System privileges granted or revoked by a GRANT or
REVOKE statement
ADMIN_OPTION
VARCHAR2(1)
Indicates whether the role or system privilege was
granted with the ADMIN option
GRANTEE
VARCHAR2(30)
Name of the grantee specified in a GRANT or REVOKE
statement
AUDIT_OPTION
VARCHAR2(40)
Auditing option set with the AUDIT statement
SES_ACTIONS
VARCHAR2(19)
Session summary (a string of 16 characters, one for
each action type in the order ALTER, AUDIT,
COMMENT, DELETE, GRANT, INDEX, INSERT, LOCK,
RENAME, SELECT, UPDATE, REFERENCES, and
EXECUTE. Positions 14, 15, and 16 are reserved for
future use. The characters are:
■
- - None
■
S - Success
■
F - Failure
■
B - Both
LOGOFF_TIME
DATE
Timestamp for user log off
LOGOFF_LREAD
NUMBER
Logical reads for the session
LOGOFF_PREAD
NUMBER
Physical reads for the session
LOGOFF_LWRITE
NUMBER
Logical writes for the session
LOGOFF_DLOCK
VARCHAR2(40)
Deadlocks detected during the session
COMMENT_TEXT
VARCHAR2(4000)
Text comment on the audit trail entry, providing more
information about the statement audited
Also indicates how the user was authenticated. The
method can be one of the following:
■
■
■
DATABASE - Authentication was done by
password
NETWORK - Authentication was done by Oracle
Net Services or the Advanced Security option
PROXY - Client was authenticated by another
user; the name of the proxy user follows the
method type
NUMBER
NOT NULL
Numeric ID for each Oracle session
ENTRYID
NUMBER
NOT NULL
Numeric ID for each audit trail entry in the session
STATEMENTID
NUMBER
NOT NULL
Numeric ID for each statement run
SESSIONID
2-168 Oracle9i Database Reference
DBA_AWS
Column
Datatype
NULL
Description
RETURNCODE
NUMBER
NOT NULL
Oracle error code generated by the action. Some
useful values:
■
0 - Action succeeded
■
2004 - Security violation
PRIV_USED
VARCHAR2(40)
System privilege used to execute the action
CLIENT_ID
VARCHAR2(64)
Client identifier in each Oracle session
SESSION_CPU
NUMBER
Amount of CPU time used by each Oracle session
DBA_AW_PS
DBA_AW_PS describes the pagespaces in all analytic workspaces in the database.
Related View
USER_AW_PS describes the pagespaces in the analytic workspaces owned by the
current user. This view does not display the OWNER column.
Column
Datatype
NULL
Description
OWNER
AW_NUMBER
VARCHAR2(30)
NOT NULL
Owner of the analytic workspace
NUMBER
NOT NULL
Number of the analytic workspace
AW_NAME
VARCHAR2(30)
Name of the analytic workspace
PSNUMBER
NUMBER(10)
Number of the pagespace
GENERATIONS
NUMBER
Number of active generations in the pagespace
See Also:
■
■
"USER_AW_PS" on page 2-265
Oracle9i OLAP User’s Guide for more information about this
view
DBA_AWS
DBA_AWS describes all analytic workspaces in the database.
Static Data Dictionary Views 2-169
DBA_BASE_TABLE_MVIEWS
Related View
USER_AWS describes the analytic workspaces owned by the current user. This view
does not display the OWNER column.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the analytic workspace
AW_NUMBER
NUMBER
NOT NULL
Number of the analytic workspace
AW_NAME
VARCHAR2(30)
Name of the analytic workspace
PAGESPACES
NUMBER
Number of pagespaces in the analytic workspace
GENERATIONS
NUMBER
Number of active generations in the analytic
workspace
See Also:
■
■
"USER_AWS" on page 2-265
Oracle9i OLAP User’s Guide for more information about this
view
DBA_BASE_TABLE_MVIEWS
DBA_BASE_TABLE_MVIEWS describes all materialized views using materialized
view logs in the database. Its columns are the same as those in ALL_BASE_TABLE_
MVIEWS.
See Also: "ALL_BASE_TABLE_MVIEWS" on page 2-16
DBA_BLOCKERS
DBA_BLOCKERS displays a session if it is not waiting for a locked object but is
holding a lock on an object for which another session is waiting.
Column
Datatype
HOLDING_SESSION
NUMBER
NULL
Description
Session holding a lock
DBA_CAPTURE
DBA_CAPTURE displays information about all capture processes in the database. Its
columns are the same as those in ALL_CAPTURE.
2-170 Oracle9i Database Reference
DBA_CATALOG
See Also: "ALL_CAPTURE" on page 2-17
DBA_CAPTURE_PARAMETERS
DBA_CAPTURE_PARAMETERS displays information about the parameters for all
capture processes in the database. Its columns are the same as those in ALL_
CAPTURE_PARAMETERS.
See Also: "ALL_CAPTURE_PARAMETERS" on page 2-18
DBA_CAPTURE_PREPARED_DATABASE
DBA_CAPTURE_PREPARED_DATABASE displays information about when the local
database was prepared for instantiation. Its columns are the same as those in ALL_
CAPTURE_PREPARED_DATABASE.
See Also: "ALL_CAPTURE_PREPARED_DATABASE" on
page 2-18
DBA_CAPTURE_PREPARED_SCHEMAS
DBA_CAPTURE_PREPARED_SCHEMAS displays information about all schemas
prepared for instantiation at the local database. Its columns are the same as those in
ALL_CAPTURE_PREPARED_SCHEMAS.
See Also: "ALL_CAPTURE_PREPARED_SCHEMAS" on
page 2-19
DBA_CAPTURE_PREPARED_TABLES
DBA_CAPTURE_PREPARED_TABLES displays information about all tables prepared
for instantiation at the local database. Its columns are the same as those in ALL_
CAPTURE_PREPARED_TABLES.
See Also: "ALL_CAPTURE_PREPARED_TABLES" on page 2-19
DBA_CATALOG
DBA_CATALOG lists all indexes, tables, views, clusters, synonyms, and sequences in
the database. Its columns are the same as those in "ALL_CATALOG" on page 2-20.
Static Data Dictionary Views 2-171
DBA_CLU_COLUMNS
DBA_CLU_COLUMNS
DBA_CLU_COLUMNS maps all table columns to related cluster columns.
Related View
USER_CLU_COLUMNS maps all table columns owned by the current user to related
cluster columns. This view does not display the OWNER column.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the cluster
CLUSTER_NAME
VARCHAR2(30)
NOT NULL
Cluster name
CLU_COLUMN_NAME
VARCHAR2(30)
NOT NULL
Key column in the cluster
TABLE_NAME
VARCHAR2(30)
NOT NULL
Clustered table name
TAB_COLUMN_NAME
VARCHAR2(4000)
Key column or attribute of the object type column
DBA_CLUSTER_HASH_EXPRESSIONS
DBA_CLUSTER_HASH_EXPRESSIONS lists hash functions for all hash clusters in the
database. Its columns are the same as those in "ALL_CLUSTER_HASH_
EXPRESSIONS" on page 2-20.
DBA_CLUSTERS
DBA_CLUSTERS describes all clusters in the database. Its columns are the same as
those in "ALL_CLUSTERS" on page 2-21.
DBA_COL_COMMENTS
DBA_COL_COMMENTS describes comments on columns of all tables and views in the
database. Its columns are the same as those in "ALL_COL_COMMENTS" on
page 2-22.
DBA_COL_PRIVS
DBA_COL_PRIVS describes all column object grants in the database.
2-172 Oracle9i Database Reference
DBA_CONS_OBJ_COLUMNS
Related View
USER_COL_PRIVS describes the column object grants for which the current user is
the object owner, grantor, or grantee.
Column
Datatype
NULL
Description
GRANTEE
VARCHAR2(30)
NOT NULL
Name of the user to whom access was granted
OWNER
VARCHAR2(30)
NOT NULL
Owner of the object
TABLE_NAME
VARCHAR2(30)
NOT NULL
Name of the object
COLUMN_NAME
VARCHAR2(30)
NOT NULL
Name of the column
GRANTOR
VARCHAR2(30)
NOT NULL
Name of the user who performed the grant
PRIVILEGE
VARCHAR2(40)
NOT NULL
Privilege on the column
GRANTABLE
VARCHAR2(3)
Indicates whether the privilege was granted with the
GRANT OPTION (YES) or not (NO)
See Also: "USER_COL_PRIVS" on page 2-266
DBA_COLL_TYPES
DBA_COLL_TYPES describes all named collection types (arrays, nested tables, object
tables, and so on) in the database. Its columns are the same as those in "ALL_
COLL_TYPES" on page 2-25.
DBA_CONS_COLUMNS
DBA_CONS_COLUMNS describes all columns in the database that are specified in
constraint definitions. Its columns are the same as those in "ALL_CONS_
COLUMNS" on page 2-25.
DBA_CONS_OBJ_COLUMNS
DBA_CONS_OBJ_COLUMNS displays information about the types that object
columns (or attributes) or collection elements have been constrained to, in all tables
in the database. Its columns are the same as those in ALL_CONS_OBJ_COLUMNS.
See Also: "ALL_CONS_OBJ_COLUMNS" on page 2-26
Static Data Dictionary Views 2-173
DBA_CONSTRAINTS
DBA_CONSTRAINTS
DBA_CONSTRAINTS describes all constraint definitions on all tables in the database.
Its columns are the same as those in "ALL_CONSTRAINTS" on page 2-27.
DBA_CONTEXT
DBA_CONTEXT provides all context namespace information in the database. Its
columns are the same as those in "ALL_CONTEXT" on page 2-28.
DBA_DATA_FILES
DBA_DATA_FILES describes database files.
Column
Datatype
FILE_NAME
VARCHAR2(513)
NULL
Description
FILE_ID
NUMBER
NOT NULL
File identifier number of the database file
TABLESPACE_NAME
VARCHAR2(30)
NOT NULL
Name of the tablespace to which the file belongs
BYTES
NUMBER
BLOCKS
NUMBER
STATUS
VARCHAR2(9)
File status: AVAILABLE or INVALID (INVALID means
that the file number is not in use, for example, a file in
a tablespace that was dropped)
RELATIVE_FNO
NUMBER
Relative file number
AUTOEXTENSIBLE
VARCHAR2(3)
Autoextensible indicator
MAXBYTES
NUMBER
Maximum file size in bytes
MAXBLOCKS
NUMBER
Maximum file size in blocks
INCREMENT_BY
NUMBER
Autoextension increment
USER_BYTES
NUMBER
Corresponding number of bytes
USER_BLOCKS
NUMBER
Number of blocks which can be used by the data
Name of the database file
Size of the file in bytes
NOT NULL
Size of the file in Oracle blocks
DBA_DB_LINKS
DBA_DB_LINKS describes all database links in the database. Its columns are the
same as those in "ALL_DB_LINKS" on page 2-29.
2-174 Oracle9i Database Reference
DBA_DEPENDENCIES
DBA_DDL_LOCKS
DBA_DDL_LOCKS lists all DDL locks held in the database and all outstanding
requests for a DDL lock.
Column
Datatype
SESSION_ID
NUMBER
Session identifier
OWNER
VARCHAR2(30)
Owner of the lock
NAME
VARCHAR2(30)
Name of the lock
TYPE
VARCHAR2(40)
Lock type:
MODE_HELD
MODE_REQUESTED
VARCHAR2(9)
VARCHAR2(9)
NULL
Description
■
Cursor
■
Table/Procedure/Type
■
Body
■
Trigger
■
Index
■
Cluster
■
Java Source
■
Java Resource
■
Java Data
Lock mode:
■
None
■
Null
■
Share
■
Exclusive
Lock request type:
■
None
■
Null
■
Share
■
Exclusive
DBA_DEPENDENCIES
DBA_DEPENDENCIES describes all dependencies in the database between
procedures, packages, functions, package bodies, and triggers, including
dependencies on views created without any database links. Its columns are the
same as those in "ALL_DEPENDENCIES" on page 2-30.
Static Data Dictionary Views 2-175
DBA_DIM_ATTRIBUTES
DBA_DIM_ATTRIBUTES
DBA_DIM_ATTRIBUTES describes the relationships between dimension levels and
functionally dependent columns in the database. The level columns and the
dependent column must be in the same table. This view’s columns are the same as
those in "ALL_DIM_ATTRIBUTES" on page 2-31.
DBA_DIM_CHILD_OF
DBA_DIM_CHILD_OF describes a hierarchical relationship of 1 to n between all the
pairs of levels in the dimensions in the database. Its columns are the same as those
in "ALL_DIM_CHILD_OF" on page 2-32.
DBA_DIM_HIERARCHIES
DBA_DIM_HIERARCHIES describes all the dimension hierarchies in the database.
Its columns are the same as those in "ALL_DIM_HIERARCHIES" on page 2-32.
DBA_DIM_JOIN_KEY
DBA_DIM_JOIN_KEY describes all joins in the database between two dimension
tables. The join is always specified between a parent dimension level column and a
child column. This view’s columns are the same as those in "ALL_DIM_JOIN_KEY"
on page 2-33.
DBA_DIM_LEVEL_KEY
DBA_DIM_LEVEL_KEY describes the columns of all dimension levels in the
database. This view’s columns are the same as those in "ALL_DIM_LEVEL_KEY"
on page 2-33.
DBA_DIM_LEVELS
DBA_DIM_LEVELS describes all dimension levels in the database. All columns of a
dimension level must come from the same relation. This view’s columns are the
same as those in "ALL_DIM_LEVELS" on page 2-34.
2-176 Oracle9i Database Reference
DBA_DML_LOCKS
DBA_DIMENSIONS
DBA_DIMENSIONS represents dimension objects. Its columns are the same as those
in "ALL_DIMENSIONS" on page 2-34.
DBA_DIRECTORIES
DBA_DIRECTORIES describes all directory objects in the database. Its columns are
the same as those in "ALL_DIRECTORIES" on page 2-35.
DBA_DML_LOCKS
DBA_DML_LOCKS lists all DML locks held in the database and all outstanding
requests for a DML lock.
Column
Datatype
SESSION_ID
NUMBER
OWNER
VARCHAR2(30)
NOT NULL
Owner of the lock
NAME
VARCHAR2(30)
NOT NULL
Name of the lock
MODE_HELD
VARCHAR2(13)
MODE_REQUESTED
VARCHAR2(13)
NULL
Description
Session holding or acquiring the lock
The type of lock held. The values are:
■
ROWS_S (SS): row share lock
■
ROW-X (SX): row exclusive lock
■
SHARE (S): share lock
■
S/ROW-X (SSX): exclusive lock
■
NONE: lock requested but not yet obtained
Lock request type. The values are:
■
ROWS_S (SS): row share lock
■
ROW-X (SX): row exclusive lock
■
SHARE (S): share lock
■
S/ROW-X (SSX): exclusive lock
■
NONE: Lock identifier obtained; lock not held or
requested
LAST_CONVERT
NUMBER
The last convert
BLOCKING_OTHERS
VARCHAR2(40)
Blocking others
Static Data Dictionary Views 2-177
DBA_DMT_FREE_SPACE
DBA_DMT_FREE_SPACE
DBA_DMT_FREE_SPACE describes the free extents in all dictionary managed
tablespaces in the database.
Column
Datatype
NULL
Description
TABLESPACE_ID
NUMBER
NOT NULL
Identifier number of the tablespace containing the
extent
FILE_ID
NUMBER
NOT NULL
File identifier number of the file containing the extent
BLOCK_ID
NUMBER
NOT NULL
Starting block number of the extent
BLOCKS
NUMBER
NOT NULL
Size of the extent (in Oracle blocks)
DBA_DMT_USED_EXTENTS
DBA_DMT_USED_EXTENTS describes the extents comprising the segments in all
dictionary managed tablespaces in the database.
Column
Datatype
NULL
Description
SEGMENT_FILEID
NUMBER
NOT NULL
File number of the segment header of the extent
SEGMENT_BLOCK
NUMBER
NOT NULL
Block number of the segment header of the extent
TABLESPACE_ID
NUMBER
NOT NULL
Identifier number of the tablespace containing the
extent
EXTENT_ID
NUMBER
NOT NULL
Extent number in the segment
FILEID
NUMBER
NOT NULL
File identifier number of the file containing the extent
BLOCK
NUMBER
NOT NULL
Starting block number of the extent
LENGTH
NUMBER
NOT NULL
Number of blocks in the extent
DBA_ERRORS
DBA_ERRORS describes current errors on all stored objects (views, procedures,
functions, packages, and package bodies) in the database. Its columns are the same
as those in "ALL_ERRORS" on page 2-35.
DBA_EVALUATION_CONTEXT_TABLES
DBA_EVALUATION_CONTEXT_TABLES describes the tables in all rule evaluation
contexts in the database. Its columns are the same as those in ALL_EVALUATION_
CONTEXT_TABLES.
2-178 Oracle9i Database Reference
DBA_EXP_OBJECTS
See Also: "ALL_EVALUATION_CONTEXT_TABLES" on
page 2-36
DBA_EVALUATION_CONTEXT_VARS
DBA_EVALUATION_CONTEXT_VARS describes the variables in all rule evaluation
contexts in the database. Its columns are the same as those in ALL_EVALUATION_
CONTEXT_VARS.
See Also: "ALL_EVALUATION_CONTEXT_VARS" on page 2-36
DBA_EVALUATION_CONTEXTS
DBA_EVALUATION_CONTEXTS describes all rule evaluation contexts in the
database. Its columns are the same as those in ALL_EVALUATION_CONTEXTS.
See Also: "ALL_EVALUATION_CONTEXTS" on page 2-37
DBA_EXP_FILES
DBA_EXP_FILES describes export files.
Column
Datatype
NULL
Description
EXP_VERSION
NUMBER(3)
NOT NULL
Version number of the export session
EXP_TYPE
VARCHAR2(11)
FILE_NAME
VARCHAR2(100)
NOT NULL
Name of the export file
USER_NAME
VARCHAR2(30)
NOT NULL
Name of user who executed export
TIMESTAMP
DATE
NOT NULL
Timestamp of the export session
Type of export file: complete, cumulative, or
incremental
DBA_EXP_OBJECTS
DBA_EXP_OBJECTS describes objects that have been incrementally exported.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of exported object
OBJECT_NAME
VARCHAR2(30)
NOT NULL
Name of exported object
OBJECT_TYPE
VARCHAR2(12)
Type of exported object
Static Data Dictionary Views 2-179
DBA_EXP_VERSION
Column
Datatype
NULL
Description
CUMULATIVE
DATE
INCREMENTAL
DATE
NOT NULL
Timestamp of last incremental export
EXPORT_VERSION
NUMBER(3)
NOT NULL
The ID of the export session
Timestamp of last cumulative export
DBA_EXP_VERSION
DBA_EXP_VERSION displays the version number of the last export session.
Column
Datatype
NULL
Description
EXP_VERSION
NUMBER(3)
NOT NULL
Version number of the last export session
DBA_EXTENTS
DBA_EXTENTS describes the extents comprising the segments in all tablespaces in
the database.
Related View
USER_EXTENTS describes the extents comprising the segments owned by the
current user’s objects. This view does not display the OWNER, FILE_ID, BLOCK_ID,
or RELATIVE_FNO columns.
Column
Datatype
OWNER
VARCHAR2(30)
Owner of the segment associated with the extent
SEGMENT_NAME
VARCHAR2(81)
Name of the segment associated with the extent
SEGMENT_TYPE
VARCHAR2(17)
Type of the segment: INDEX PARTITION, TABLE
PARTITION
TABLESPACE_NAME
VARCHAR2(30)
Name of the tablespace containing the extent
EXTENT_ID
NUMBER
NOT NULL
Extent number in the segment
FILE_ID
NUMBER
NOT NULL
File identifier number of the file containing the extent
BLOCK_ID
NUMBER
NOT NULL
Starting block number of the extent
BYTES
NUMBER
BLOCKS
NUMBER
NOT NULL
Size of the extent in Oracle blocks
RELATIVE_FNO
NUMBER
NOT NULL
Relative file number of the first extent block
PARTITION_NAME
VARCHAR2(30)
2-180 Oracle9i Database Reference
NULL
Description
Size of the extent in bytes
Object Partition Name (Set to NULL for
non-partitioned objects)
DBA_FGA_AUDIT_TRAIL
See Also: "USER_EXTENTS" on page 2-270
DBA_EXTERNAL_LOCATIONS
DBA_EXTERNAL_TABLES describes the locations (data sources) of all external tables
in the database. Its columns are the same as those in ALL_EXTERNAL_LOCATIONS.
See Also: "ALL_EXTERNAL_LOCATIONS" on page 2-38
DBA_EXTERNAL_TABLES
DBA_EXTERNAL_TABLES describes all external tables in the database. Its columns
are the same as those in ALL_EXTERNAL_TABLES.
See Also: "ALL_EXTERNAL_TABLES" on page 2-39
DBA_FGA_AUDIT_TRAIL
DBA_FGA_AUDIT_TRAIL lists all audit records for fine-grained auditing.
Column
Datatype
NULL
Description
SESSION_ID
NUMBER
NOT NULL
Session id of the query
TIMESTAMP
DATE
NOT NULL
Timestamp of the query
DB_USER
VARCHAR2(30)
Database username who executed the query
OS_USER
VARCHAR2(255)
Operating system username who executed the query
USERHOST
VARCHAR2(128)
Numeric instance ID for the Oracle instance from
which the user is accessing the database. Used only in
environments with distributed file systems and
shared database files.
CLIENT_ID
VARCHAR2(64)
Client identifier in each Oracle session
EXT_NAME
VARCHAR2(4000)
External name
OBJECT_SCHEMA
VARCHAR2(30)
Owner of the table or view
OBJECT_NAME
VARCHAR2(128)
Name of the table or view
POLICY_NAME
VARCHAR2(30)
Name of the Fine-Grained Auditing Policy
SCN
NUMBER
System change number (SCN) of the query
SQL_TEXT
NVARCHAR2(2000)
SQL text of the query
SQL_BIND
VARCHAR2(4000)
Bind variable data of the query
COMMENT$TEXT
VARCHAR2(4000)
Comments
Static Data Dictionary Views 2-181
DBA_FREE_SPACE
DBA_FREE_SPACE
DBA_FREE_SPACE describes the free extents in all tablespaces in the database.
Related View
USER_FREE_SPACE describes the free extents in the tablespaces accessible to the
current user.
Column
Datatype
NULL
Description
TABLESPACE_NAME
VARCHAR2(30)
Name of the tablespace containing the extent
FILE_ID
NUMBER
File identifier number of the file containing the extent
BLOCK_ID
NUMBER
Starting block number of the extent
BYTES
NUMBER
Size of the extent (in bytes)
BLOCKS
NUMBER
Size of the extent (in Oracle blocks)
RELATIVE_FNO
NUMBER
Relative file number of the file containing the extent
See Also: "USER_FREE_SPACE" on page 2-271
DBA_FREE_SPACE_COALESCED
DBA_FREE_SPACE_COALESCED describes statistics on coalesced space in all
tablespaces in the database.
Column
Datatype
NULL
Description
TABLESPACE_NAME
VARCHAR2(30)
NOT NULL
Name of the tablespace
TOTAL_EXTENTS
NUMBER
Total number of free extents in the tablespace
EXTENTS_COALESCED
NUMBER
Total number of coalesced free extents in the
tablespace
PERCENT_EXTENTS
_COALESCED
NUMBER
Percentage of coalesced free extents in the tablespace
TOTAL_BYTES
NUMBER
Total number of free bytes in the tablespace
BYTES_COALESCED
NUMBER
Total number of coalesced free bytes in the tablespace
TOTAL_BLOCKS
NUMBER
Total number of free Oracle blocks in the tablespace
BLOCKS_COALESCED
NUMBER
Total number of coalesced free Oracle blocks in the
tablespace
PERCENT_BLOCKS
_COALESCED
NUMBER
Percentage of coalesced free Oracle blocks in the
tablespace
2-182 Oracle9i Database Reference
DBA_INDEXTYPE_COMMENTS
DBA_IND_COLUMNS
DBA_IND_COLUMNS describes the columns of all the indexes on all tables and
clusters in the database. Its columns are the same as those in "ALL_IND_
COLUMNS" on page 2-40.
DBA_IND_EXPRESSIONS
DBA_IND_EXPRESSIONS lists expressions of function-based indexes on all tables
and clusters in the database. Its columns are the same as those in "ALL_IND_
EXPRESSIONS" on page 2-41.
DBA_IND_PARTITIONS
DBA_IND_PARTITIONS describes, for each index partition in the database, the
partition-level partitioning information, the storage parameters for the partition,
and various partition statistics collected by ANALYZE statements. Its columns are
the same as those in "ALL_IND_PARTITIONS" on page 2-41.
DBA_IND_SUBPARTITIONS
DBA_IND_SUBPARTITIONS describes, for each index subpartition in the database,
the partition-level partitioning information, the storage parameters for the
subpartition, and various partition statistics collected by ANALYZE statements. Its
columns are the same as those in "ALL_IND_SUBPARTITIONS" on page 2-43.
DBA_INDEXES
DBA_INDEXES describes all indexes in the database. To gather statistics for this
view, use the SQL ANALYZE statement. This view supports parallel partitioned
index scans. Its columns are the same as those in "ALL_INDEXES" on page 2-45.
DBA_INDEXTYPE_COMMENTS
DBA_INDEXTYPE_COMMENTS lists all comments for user-defined indextypes in the
database. Its columns are the same as those in ALL_INDEXTYPE_COMMENTS.
See Also: "ALL_INDEXTYPE_COMMENTS" on page 2-48
Static Data Dictionary Views 2-183
DBA_INDEXTYPE_OPERATORS
DBA_INDEXTYPE_OPERATORS
DBA_INDEXTYPE_OPERATORS lists all the operators supported by indextypes in
the database. Its columns are the same as those in ALL_INDEXTYPE_OPERATORS.
See Also: "ALL_INDEXTYPE_OPERATORS" on page 2-49
DBA_INDEXTYPES
DBA_INDEXTYPES describes all indextypes in the database. Its columns are the
same as those in ALL_INDEXTYPES.
See Also: "ALL_INDEXTYPES" on page 2-50
DBA_INTERNAL_TRIGGERS
DBA_INTERNAL_TRIGGERS describes internal triggers on all tables in the database.
Its columns are the same as those in "ALL_INTERNAL_TRIGGERS" on page 2-50.
DBA_JAVA_ARGUMENTS
DBA_JAVA_ARGUMENTS displays argument information about all stored Java
classes in the database. Its columns are the same as those in ALL_JAVA_
ARGUMENTS.
See Also: "ALL_JAVA_ARGUMENTS" on page 2-51
DBA_JAVA_CLASSES
DBA_JAVA_CLASSES displays class level information about all stored Java classes
in the database. Its columns are the same as those in ALL_JAVA_CLASSES.
See Also: "ALL_JAVA_CLASSES" on page 2-52
DBA_JAVA_DERIVATIONS
DBA_JAVA_DERIVATIONS displays mapping information about Java source objects
and their derived Java class objects and Java resource objects for all Java classes in
the database. Its columns are the same as those in ALL_JAVA_DERIVATIONS.
See Also: "ALL_JAVA_DERIVATIONS" on page 2-53
2-184 Oracle9i Database Reference
DBA_JAVA_NCOMPS
DBA_JAVA_FIELDS
DBA_JAVA_FIELDS displays field information about all stored Java classes in the
database. Its columns are the same as those in ALL_JAVA_FIELDS.
See Also: "ALL_JAVA_FIELDS" on page 2-54
DBA_JAVA_IMPLEMENTS
DBA_JAVA_IMPLEMENTS describes interfaces implemented by all stored Java
classes in the database. Its columns are the same as those in ALL_JAVA_
IMPLEMENTS.
See Also: "ALL_JAVA_IMPLEMENTS" on page 2-55
DBA_JAVA_INNERS
DBA_JAVA_INNERS displays information about inner classes referred to by all
stored Java classes in the database. Its columns are the same as those in ALL_JAVA_
INNERS.
See Also: "ALL_JAVA_INNERS" on page 2-56
DBA_JAVA_LAYOUTS
DBA_JAVA_LAYOUTS displays class layout information about all stored Java classes
in the database. Its columns are the same as those in ALL_JAVA_LAYOUTS.
See Also: "ALL_JAVA_LAYOUTS" on page 2-57
DBA_JAVA_METHODS
DBA_JAVA_METHODS displays method information about all stored Java classes in
the database. Its columns are the same as those in ALL_JAVA_METHODS.
See Also: "ALL_JAVA_METHODS" on page 2-58
DBA_JAVA_NCOMPS
DBA_JAVA_NCOMPS displays ncomp-related information about all Java classes in
the database. Its columns are the same as those in ALL_JAVA_NCOMPS.
Static Data Dictionary Views 2-185
DBA_JAVA_POLICY
See Also: "ALL_JAVA_NCOMPS" on page 2-59
DBA_JAVA_POLICY
DBA_JAVA_POLICY describes Java security permissions for all users in the
database.
Related View
USER_JAVA_POLICY describes Java security permissions for the current user.
Column
Datatype
NULL
Description
KIND
VARCHAR2(8)
GRANTEE
VARCHAR2(30)
NOT NULL
Name of the user, schema, or role to which the
permission object is assigned
TYPE_SCHEMA
VARCHAR2(30)
NOT NULL
Schema in which the permission object is loaded
TYPE_NAME
VARCHAR2(4000)
Permission class type, which is designated by a string
containing the full class name, such as,
java.io.FilePermission
NAME
VARCHAR2(4000)
Target attribute (name) of the permission object. This
name is used when defining the permission.
ACTION
VARCHAR2(4000)
Action attribute for this permission. Many
permissions expect a null value if no action is
appropriate for the permission.
ENABLED
VARCHAR2(8)
Indicates whether the permission is enabled
(ENABLED) or disabled (DISABLED)
SEQ
NUMBER
Sequence number used to identify this row. This
number should be supplied when disabling, enabling,
or deleting the permission.
Indicates whether this permission is a positive
(GRANT) or a limitation (RESTRICT)
See Also: "USER_JAVA_POLICY" on page 2-274
DBA_JAVA_RESOLVERS
DBA_JAVA_RESOLVERS displays information about resolvers of all Java classes in
the database. Its columns are the same as those in ALL_JAVA_RESOLVERS.
See Also: "ALL_JAVA_RESOLVERS" on page 2-60
2-186 Oracle9i Database Reference
DBA_JOIN_IND_COLUMNS
DBA_JAVA_THROWS
DBA_JAVA_THROWS displays information about exceptions thrown from methods
of all Java classes in the database. Its columns are the same as those in ALL_JAVA_
THROWSa.
See Also: "ALL_JAVA_THROWS" on page 2-61
DBA_JOBS
DBA_JOBS describes all jobs in the database. Its columns are the same as those in
"ALL_JOBS" on page 2-61.
See Also: Oracle9i Database Administrator’s Guide for more
information on jobs
DBA_JOBS_RUNNING
DBA_JOBS_RUNNING lists all jobs in the database that are currently running.
Column
Datatype
NULL
Description
SID
NUMBER
Identifier of process that is executing the job. See
"V$LOCK".
JOB
NUMBER
Identifier of job. This job is currently executing.
FAILURES
NUMBER
Number of times this job started and failed since its
last success.
LAST_DATE
DATE
Date that this job last successfully executed.
LAST_SEC
VARCHAR2(8)
Same as LAST_DATE. This is when the last successful
execution started.
THIS_DATE
DATE
Date that this job started executing.
THIS_SEC
VARCHAR2(8)
Same as THIS_DATE. This is when the last successful
execution started.
INSTANCE
NUMBER
Indicates which instance can execute or is executing
the job; the default is 0.
DBA_JOIN_IND_COLUMNS
DBA_JOIN_IND_COLUMNS describes all join conditions in the database. Its columns
are the same as those in "ALL_JOIN_IND_COLUMNS" on page 2-63.
Static Data Dictionary Views 2-187
DBA_KGLLOCK
DBA_KGLLOCK
DBA_KGLLOCK lists all the locks and pins held on KGL objects (objects in the Kernel
Generic Library cache).
Column
Datatype
kgllkuse
RAW(4)
NULL
Description
Address of the user session that holds the lock or pin
kgllkhdl
RAW(4)
Address of the handle for the KGL object
kgllkmod
NUMBER
Current mode of the lock or pin
kgllkreq
NUMBER
Mode in which the lock or pin was requested
kgllktype
VARCHAR2(4)
Whether this is a lock or a pin
DBA_LIBRARIES
DBA_LIBRARIES describes all the libraries in the database. Its columns are the
same as those in "ALL_LIBRARIES" on page 2-63.
DBA_LMT_FREE_SPACE
DBA_LMT_FREE_SPACE describes the free extents in all locally managed
tablespaces in the database.
Column
Datatype
NULL
Description
TABLESPACE_ID
NUMBER
Identifier number of the tablespace containing the
extent
FILE_ID
NUMBER
File identifier number of the file containing the extent
BLOCK_ID
NUMBER
Starting block number of the extent
BLOCKS
NUMBER
Size of the extent (in Oracle blocks)
DBA_LMT_USED_EXTENTS
DBA_LMT_USED_EXTENTS describes the extents comprising the segments in all
locally managed tablespaces in the database.
Column
Datatype
NULL
Description
SEGMENT_FILEID
NUMBER
NOT NULL
File number of the segment header of the extent
SEGMENT_BLOCK
NUMBER
NOT NULL
Block number of the segment header of the extent
2-188 Oracle9i Database Reference
DBA_LOCK
Column
Datatype
NULL
Description
TABLESPACE_ID
NUMBER
NOT NULL
Identifier number of the tablespace containing the
extent
EXTENT_ID
NUMBER
NOT NULL
Extent number in the segment
FILEID
NUMBER
NOT NULL
File identifier number of the file containing the extent
BLOCK
NUMBER
NOT NULL
Starting block number of the extent
LENGTH
NUMBER
NOT NULL
Number of blocks in the extent
DBA_LOB_PARTITIONS
DBA_LOB_PARTITIONS displays all LOB partitions in the database. Its columns are
the same as those in "ALL_LOB_PARTITIONS" on page 2-64.
DBA_LOB_SUBPARTITIONS
DBA_LOB_SUBPARTITIONS displays partition-level attributes of all LOB data
subpartitions in the database. Its columns are the same as those in "ALL_LOB_
SUBPARTITIONS" on page 2-65.
DBA_LOB_TEMPLATES
DBA_LOB_TEMPLATES describes all LOB subpartition templates in the database. Its
columns are the same as those in ALL_LOB_TEMPLATES.
See Also: "ALL_LOB_TEMPLATES" on page 2-66
DBA_LOBS
DBA_LOBS displays the BLOBs and CLOBs contained in all tables in the database.
BFILEs are stored outside the database, so they are not described by this view. This
view’s columns are the same as those in "ALL_LOBS" on page 2-67.
DBA_LOCK
DBA_LOCK lists all locks or latches held in the database, and all outstanding
requests for a lock or latch.
Static Data Dictionary Views 2-189
DBA_LOCK_INTERNAL
Column
Datatype
NULL
Description
SESSION_ID
NUMBER
Session holding or acquiring the lock
LOCK_TYPE
VARCHAR2(26)
Lock type
See Also: For a listing of lock types, see Appendix B,
"Oracle Enqueue Names"
MODE HELD
VARCHAR2(40)
Lock mode
MODE REQUESTED
VARCHAR2(40)
Lock mode requested
LOCK_ID1
VARCHAR2(40)
Type-specific lock identifier, part 1
LOCK_ID2
VARCHAR2(40)
Type-specific lock identifier, part 2
LAST_CONVERT
NUMBER
The last convert
BLOCKING_OTHERS
VARCHAR2(40)
Whether the lock is currently blocking others
DBA_LOCK_INTERNAL
DBA_LOCK_INTERNAL displays a row for each lock or latch that is being held, and
one row for each outstanding request for a lock or latch.
Column
Datatype
NULL
Description
SESSION_ID
NUMBER
Session holding or acquiring the lock
LOCK_TYPE
VARCHAR2(56)
Lock type
See Also: For a listing of lock types, see Appendix B,
"Oracle Enqueue Names"
MODE HELD
VARCHAR2(40)
Lock mode
MODE REQUESTED
VARCHAR2(40)
Lock mode requested
LOCK_ID1
VARCHAR2(1130)
Type-specific lock identifier, part 1
LOCK_ID2
VARCHAR2(40)
Type-specific lock identifier, part 2
DBA_LOCKS
DBA_LOCKS is a synonym for DBA_LOCK.
See Also: "DBA_LOCK" on page 2-189
2-190 Oracle9i Database Reference
DBA_LOGSTDBY_LOG
DBA_LOG_GROUP_COLUMNS
DBA_LOG_GROUP_COLUMNS describes all columns in the database that are specified
in log groups. Its columns are the same as those in "ALL_LOG_GROUP_
COLUMNS" on page 2-68.
DBA_LOG_GROUPS
DBA_LOG_GROUPS describes log group definitions on all tables in the database. Its
columns are the same as those in "ALL_LOG_GROUPS" on page 2-69.
DBA_LOGSTDBY_EVENTS
DBA_LOGSTDBY_EVENTS displays information about the activity of the logical
standby database system. It can be used to determine the cause of failures that occur
when applying redo logs.
Column
Datatype
NULL
Description
EVENT_TIME
DATE
Time the event was logged
CURRENT_SCN
NUMBER
Change vector SCN for the change. If a failure
occurred, then examine this column to determine
which archived log file contains the source of the
failure (for example, an unsupported record).
COMMIT_SCN
NUMBER
SCN value on which the change was committed
XIDUSN
NUMBER
Transaction ID undo segment number
XIDSLT
NUMBER
Transaction ID slot number
XIDSQN
NUMBER
Transaction ID sequence number
EVENT
CLOB
Statement that was being processed when the failure
occurred
STATUS_CODE
NUMBER
Status (or Oracle error code) belonging to the STATUS
message
STATUS
VARCHAR2(2000)
Description of the current activity of the process or
the reason why the apply operation stopped
DBA_LOGSTDBY_LOG
DBA_LOGSTDBY_LOG shows the logs registered for a logical standby database.
Static Data Dictionary Views 2-191
DBA_LOGSTDBY_NOT_UNIQUE
Column
Datatype
NULL
Description
THREAD#
NUMBER
NOT NULL
Thread ID of the archived redo log. The THREAD
number is 1 for a single instance. For Real Application
Clusters, this column will contain different numbers.
SEQUENCE#
NUMBER
NOT NULL
Sequence number of the archived redo log file
FIRST_CHANGE#
NUMBER
System change number (SCN) of the current archived
redo log
NEXT_CHANGE#
NUMBER
System change number (SCN) of the next archived
redo log
FIRST_TIME
DATE
Date of the current archived redo log
NEXT_TIME
DATE
Date of the next archived redo log
FILE_NAME
VARCHAR2(513)
Name of the archived redo log
TIMESTAMP
DATE
Time when the archived redo log was registered
DICT_BEGIN
VARCHAR2(3)
Indicates whether the beginning of the dictionary
build is in this particular archived redo log (YES) or
not (NO)
DICT_END
VARCHAR2(3)
Indicates whether the end of the dictionary build is in
this particular archived redo log (YES) or not (NO)
Note: The SCN values in this view correlate to the SCN values
shown in the DBA_LOGSTDBY_PROGRESS view.
DBA_LOGSTDBY_NOT_UNIQUE
DBA_LOGSTDBY_NOT_UNIQUE identifies tables that have no primary and no
non-null unique indexes. Most of the tables displayed in this view are supported
because their columns contain enough information to be maintained in a logical
standby database. Some tables, however, cannot be supported because their
columns do not contain the necessary information. Unsupported tables usually
contain a column defined using an unsupported datatype.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Schema name
TABLE_NAME
VARCHAR2(30)
NOT NULL
Name of the table
2-192 Oracle9i Database Reference
DBA_LOGSTDBY_PARAMETERS
Column
Datatype
BAD_COLUMN
VARCHAR2(1)
NULL
Description
■
■
Y - the table column is defined using an
unbounded data type, such as LONG or BLOB. If
two rows in the table match except in their LOB
column, then the table cannot be maintained
properly. Log apply services will attempt to
maintain these tables, but you must ensure the
application does not allow uniqueness only in
the unbounded columns.
N - enough column information is present to
maintain the table in the logical standby
database but the log transport services and log
apply services would run more efficiently if you
added a primary key. You should consider
adding a disabled RELY constraint to these
tables.
DBA_LOGSTDBY_PARAMETERS
DBA_LOGSTDBY_PARAMETERS contains the list of parameters used by the log apply
services for logical standby databases.
Static Data Dictionary Views 2-193
DBA_LOGSTDBY_PROGRESS
Column
Datatype
NAME
VARCHAR2(30)
NULL
Description
Name of the parameter:
■
■
■
■
■
■
■
■
■
■
■
■
■
■
VALUE
VARCHAR2(2000)
MAX_SGA - system global area (SGA) allocated
for the log apply services cache (in megabytes)
MAX_SLAVES - number of parallel query servers
specifically reserved for log apply services
MAX_EVENTS_RECORDED - number of events
stored in the DBA_LOGSTDBY_EVENTS table
TRANSACTION_CONSISTENCY - shows the level
of transaction consistency maintained (FULL,
READ_ONLY, or NONE)
RECORD_SKIP_ERRORS - indicates records that
are skipped
RECORD_SKIP_DDL - indicates skipped DDL
statements
RECORD_APPLIED_DDL - indicates applied DDL
statements
FIRST_SCN - SCN at which log transport
services will begin applying redo information
PRIMARY - database ID of the database to which
logs are being applied
LMNR_SID - LogMiner Session ID. This internal
value indicates which LogMiner session is in
use.
UNTIL_SCN - SCN value at which the log apply
services will shut down all transactions that have
been applied
END_PRIMARY_SCN - during a switchover, this
value indicates the last SCN applied by the new
primary from the old primary
NEW_PRIMARY_SCN - during a switchover, this
value indicates the starting SCN for the new
primary database
COMPLETED_SESSION - indicates that the log
apply services session has concluded. The value
will indicate SWITCHOVER or FAILOVER, as
appropriate.
Value of the parameter
DBA_LOGSTDBY_PROGRESS
DBA_LOGSTDBY_PROGRESS describes the progress of log apply services on the
logical standby database.
2-194 Oracle9i Database Reference
DBA_LOGSTDBY_SKIP_TRANSACTION
Column
Datatype
NULL
Description
APPLIED_SCN
NUMBER
Shows the newest SCN at which all changes have
been applied. The values in the APPLIED_SCN and
NEWEST_SCN columns will match if all available redo
log data has been processed.
APPLIED_TIME
DATE
Estimate of the time and date of the APPLIED_SCN
READ_SCN
NUMBER
All log data greater than this SCN has been read and
saved
READ_TIME
DATE
Estimate of the time and date of the READ_SCN
NEWEST_SCN
NUMBER
Most recent SCN available on the standby system. If
no more logs are being shipped, then changes could
be applied to this SCN. The values in the APPLIED_
SCN and NEWEST_SCN columns will match if all
available redo log data has been processed.
NEWEST_TIME
DATE
Estimate of the time and date of the NEWEST_SCN
Note: The SCN values shown in this view correlate to the SCN
values shown in the DBA_LOGSTDBY_LOG view.
DBA_LOGSTDBY_SKIP
DBA_LOGSTDBY_SKIP lists the tables that will be skipped by log apply services.
Column
Datatype
NULL
Description
ERROR
VARCHAR2(1)
Indicates whether the statement should be skipped
(Yes) or just return errors for the statement (No)
STATEMENT_OPT
VARCHAR2(30)
Specifies the type of statement that should be
skipped. It must be one of the AUDIT_OPTIONS.
OWNER
VARCHAR2(30)
Name of the schema under which this skip option
should be used
NAME
VARCHAR2(30)
Name of the option under which this skip option
should be used
PROC
VARCHAR2(98)
Name of a stored procedure that will be executed
when processing the skip option
DBA_LOGSTDBY_SKIP_TRANSACTION
DBA_LOGSTDBY_SKIP_TRANSACTION lists the skip settings chosen.
Static Data Dictionary Views 2-195
DBA_LOGSTDBY_UNSUPPORTED
Column
Datatype
NULL
Description
XIDUSN
NUMBER
Transaction ID undo segment number
XIDSLT
NUMBER
Transaction ID slot number
XIDSQN
NUMBER
Transaction ID sequence number
DBA_LOGSTDBY_UNSUPPORTED
DBA_LOGSTDBY_UNSUPPORTED identifies the schemas, tables, and columns in
those tables that contain unsupported datatypes. Use this view when you are
preparing to create a logical standby database.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Schema name of the unsupported table
TABLE_NAME
VARCHAR2(30)
NOT NULL
Name of the unsupported table
COLUMN_NAME
VARCHAR2(30)
NOT NULL
Name of the unsupported column
DATA_TYPE
VARCHAR2(106)
Data type of the unsupported column
DBA_METHOD_PARAMS
DBA_METHOD_PARAMS describes the method parameters of all object types in the
database. Its columns are the same as those in ALL_METHOD_PARAMS.
See Also: "ALL_METHOD_PARAMS" on page 2-69
DBA_METHOD_RESULTS
DBA_METHOD_RESULTS describes the method results of all object types in the
database. Its columns are the same as those in ALL_METHOD_RESULTS.
See Also: "ALL_METHOD_RESULTS" on page 2-70
DBA_MVIEW_AGGREGATES
DBA_MVIEW_AGGREGATES describes the grouping functions (aggregated measures)
that appear in the SELECT list of all aggregated materialized view in the database.
Its columns are the same as those in "ALL_MVIEW_AGGREGATES" on page 2-71.
2-196 Oracle9i Database Reference
DBA_MVIEW_LOG_FILTER_COLS
DBA_MVIEW_ANALYSIS
DBA_MVIEW_ANALYSIS describes all materialized views in the database that
potentially support query rewrite and that provide additional information for
analysis by applications. Its columns are the same as those in "ALL_MVIEW_
ANALYSIS" on page 2-72.
Note: This view excludes materialized views that reference
remote tables or that include references to non-static values such as
SYSDATE or USER. This view also excludes materialized views that
were created as snapshots prior to Oracle8i and that were never
altered to enable query rewrite.
DBA_MVIEW_DETAIL_RELATIONS
DBA_MVIEW_DETAIL_RELATIONS represents the named detail relations that are
either in the FROM list of a materialized view, or that are indirectly referenced
through views in the FROM list. Its columns are the same as those in "ALL_MVIEW_
DETAIL_RELATIONS" on page 2-73.
DBA_MVIEW_JOINS
DBA_MVIEW_JOINS describes a join between two columns in the WHERE clause of a
subquery that defines a materialized view. Its columns are the same as those in
"ALL_MVIEW_JOINS" on page 2-74.
DBA_MVIEW_KEYS
DBA_MVIEW_KEYS describes the columns or expressions in the SELECT list upon
which materialized views in the database are based. Its columns are the same as
those in "ALL_MVIEW_KEYS" on page 2-75.
DBA_MVIEW_LOG_FILTER_COLS
DBA_MVIEW_LOG_FILTER_COLS lists all columns (excluding primary key
columns) being logged in the materialized view logs.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the master table being logged
Static Data Dictionary Views 2-197
DBA_MVIEW_LOGS
Column
Datatype
NULL
Description
NAME
VARCHAR2(30)
NOT NULL
Name of the master table being logged
COLUMN_NAME
VARCHAR2(30)
NOT NULL
Column being logged
DBA_MVIEW_LOGS
DBA_MVIEW_LOGS describes all materialized view logs in the database. Its columns
are the same as those in ALL_MVIEW_LOGS.
See Also: "ALL_MVIEW_LOGS" on page 2-76
DBA_MVIEW_REFRESH_TIMES
DBA_MVIEW_REFRESH_TIMES describes refresh times of all materialized views in
the database. Its columns are the same as those in ALL_MVIEW_REFRESH_TIMES.
See Also: "ALL_MVIEW_REFRESH_TIMES" on page 2-77
DBA_MVIEWS
DBA_MVIEWS describes all materialized views in the database. Its columns are the
same as those in ALL_MVIEWS.
See Also: "ALL_MVIEWS" on page 2-77
DBA_NESTED_TABLES
DBA_NESTED_TABLES describes all nested tables contained in all tables in the
database. Its columns are the same as those in "ALL_NESTED_TABLES" on
page 2-82.
DBA_OBJ_AUDIT_OPTS
DBA_OBJ_AUDIT_OPTS describes auditing options on all objects.
Related View
USER_OBJ_AUDIT_OPTS describes auditing options on all objects owned by the
current user. This view does not display the OWNER column.
2-198 Oracle9i Database Reference
DBA_OBJ_COLATTRS
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
Owner of the object
OBJECT_NAME
VARCHAR2(30)
Name of the object
OBJECT_TYPE
VARCHAR2(9)
Type of the object
ALT
VARCHAR2(3)
Auditing ALTER WHENEVER
SUCCESSFUL/UNSUCCESSFUL
AUD
VARCHAR2(3)
Auditing AUDIT WHENEVER
SUCCESSFUL/UNSUCCESSFUL
COM
VARCHAR2(3)
Auditing COMMENT WHENEVER
SUCCESSFUL/UNSUCCESSFUL
DEL
VARCHAR2(3)
Auditing DELETE WHENEVER
SUCCESSFUL/UNSUCCESSFUL
GRA
VARCHAR2(3)
Auditing GRANT WHENEVER
SUCCESSFUL/UNSUCCESSFUL
IND
VARCHAR2(3)
Auditing INDEX WHENEVER
SUCCESSFUL/UNSUCCESSFUL
INS
VARCHAR2(3)
Auditing INSERT WHENEVER
SUCCESSFUL/UNSUCCESSFUL
LOC
VARCHAR2(3)
Auditing LOCK WHENEVER
SUCCESSFUL/UNSUCCESSFUL
REN
VARCHAR2(3)
Auditing RENAME WHENEVER
SUCCESSFUL/UNSUCCESSFUL
SEL
VARCHAR2(3)
Auditing SELECT WHENEVER
SUCCESSFUL/UNSUCCESSFUL
UPD
VARCHAR2(3)
Auditing UPDATE WHENEVER
SUCCESSFUL/UNSUCCESSFUL
REF
VARCHAR2(3)
Auditing REFERENCE WHENEVER
SUCCESSFUL/UNSUCCESSFUL (not used)
EXE
VARCHAR2(3)
Auditing EXECUTE WHENEVER
SUCCESSFUL/UNSUCCESSFUL
REA
VARCHAR2(3)
Auditing READ WHENEVER
SUCCESSFUL/UNSUCCESSFUL
DBA_OBJ_COLATTRS
DBA_OBJ_COLATTRS describes object columns and attributes contained in all tables
in the database. Its columns are the same as those in ALL_OBJ_COLATTRS.
See Also: "ALL_OBJ_COLATTRS" on page 2-82
Static Data Dictionary Views 2-199
DBA_OBJECT_SIZE
DBA_OBJECT_SIZE
DBA_OBJECT_SIZE lists the sizes, in bytes, of various PL/SQL objects.
Related View
USER_OBJECT_SIZE lists the size of PL/SQL objects owned by the current user.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the object
NAME
VARCHAR2(30)
NOT NULL
Name of the object
TYPE
VARCHAR2(12)
Type of the object: TYPE, TYPE BODY, TABLE,
VIEW, SYNONYM, SEQUENCE, PROCEDURE,
FUNCTION, PACKAGE, PACKAGE BODY, JAVA
SOURCE, JAVA CLASS or JAVA RESOURCE
SOURCE_SIZE
NUMBER
Size of the source in bytes. Must be in memory during
compilation, or dynamic recompilation.
PARSED_SIZE
NUMBER
Size of the parsed form of the object, in bytes. Must be
in memory when an object is being compiled that
references this object.
CODE_SIZE
NUMBER
Code size, in bytes. Must be in memory when this
object is executing.
ERROR_SIZE
NUMBER
Size of error messages, in bytes. In memory during
the compilation of the object when there are
compilation errors.
DBA_OBJECT_TABLES
DBA_OBJECT_TABLES describes all object tables in the database. Its columns are
the same as those in "ALL_OBJECT_TABLES" on page 2-83.
DBA_OBJECTS
DBA_OBJECTS describes all objects in the database. Its columns are the same as
those in "ALL_OBJECTS" on page 2-85.
DBA_OPANCILLARY
DBA_OPANCILLARY provides ancillary information for all operator bindings in the
database. Its columns are the same as those in "ALL_OPANCILLARY" on page 2-86.
2-200 Oracle9i Database Reference
DBA_ORPHAN_KEY_TABLE
DBA_OPARGUMENTS
DBA_OPARGUMENTS provides argument information for all operator bindings in the
database. Its columns are the same as those in "ALL_OPARGUMENTS" on
page 2-87.
DBA_OPBINDINGS
DBA_OPBINDINGS describes bindings of all operators in the database. Its columns
are the same as those in "ALL_OPBINDINGS" on page 2-87.
DBA_OPERATOR_COMMENTS
DBA_OPERATOR_COMMENTS lists all comments for user-defined operators in the
database. Its columns are the same as those in ALL_OPERATOR_COMMENTS.
See Also: "ALL_OPERATOR_COMMENTS" on page 2-88
DBA_OPERATORS
DBA_OPERATORS describes all operators in the database. Its columns are the same
as those in ALL_OPERATORS.
See Also: "ALL_OPERATORS" on page 2-89
DBA_ORPHAN_KEY_TABLE
DBA_ORPHAN_KEY_TABLE reports key values from indexes where the underlying
base table has block corruptions. To create the view, run the DBMS_REPAIR.ADMIN_
TABLES procedure. To populate the orphan key table for an index, run the DBMS_
REPAIR.DUMP_ORPHAN_KEYS procedure on the index. For each key in the index
that points to a corrupt data block, Oracle inserts a row into the orphan key table.
Column
Datatype
NULL
Description
SCHEMA_NAME
VARCHAR2(30)
NOT NULL
Schema name of the index
INDEX_NAME
VARCHAR2(30)
NOT NULL
Name of the index
IPART_NAME
VARCHAR2(30)
NULL
Name of the index partition or subpartition
INDEX_ID
NUMBER
NOT NULL
Dictionary object ID of the index
TABLE_NAME
VARCHAR2(30)
NOT NULL
Name of the base table of the index
Static Data Dictionary Views 2-201
DBA_OUTLINE_HINTS
Column
Datatype
NULL
Description
PART_NAME
VARCHAR2(30)
NULL
Name of the base table partition or subpartition
TABLE_ID
NUMBER
NOT NULL
Dictionary object ID of the base table
KEYDATA
UROWID
NOT NULL
Physical rowid of the corrupt data row
KEY
UROWID
NOT NULL
Key values for the index entry
DUMP_TIMESTAMP
DATE
NOT NULL
Timestamp when the entry was made into the orphan
key table
DBA_OUTLINE_HINTS
DBA_OUTLINE_HINTS describes the set of hints that make up the all the outlines in
the database. Its columns are the same as those in "ALL_OUTLINE_HINTS" on
page 2-89.
DBA_OUTLINES
DBA_OUTLINES describes all outlines in the database. Its columns are the same as
those in "ALL_OUTLINES" on page 2-90.
DBA_PART_COL_STATISTICS
DBA_PART_COL_STATISTICS provides column statistics and histogram
information for partitions of all tables in the database. Its columns are the same as
those in "ALL_PART_COL_STATISTICS" on page 2-91.
DBA_PART_HISTOGRAMS
DBA_PART_HISTOGRAMS provides the histogram data (end-points per histogram)
for histograms on all table partitions in the database. Its columns are the same as
those in "ALL_PART_HISTOGRAMS" on page 2-92.
DBA_PART_INDEXES
DBA_PART_INDEXES describes the object-level partitioning information for all
partitioned indexes in the database. Its columns are the same as those in ALL_
PART_INDEXES.
See Also: "ALL_PART_INDEXES" on page 2-92
2-202 Oracle9i Database Reference
DBA_PENDING_TRANSACTIONS
DBA_PART_KEY_COLUMNS
DBA_PART_KEY_COLUMNS describes the partitioning key columns for all
partitioned objects in the database. Its columns are the same as those in ALL_PART_
KEY_COLUMNS.
See Also: "ALL_PART_KEY_COLUMNS" on page 2-94
DBA_PART_LOBS
DBA_PART_LOBS provides table-level information for all partitioned LOBs in the
database, including default attributes for LOB data partitions. Its columns are the
same as those in "ALL_PART_LOBS" on page 2-95.
DBA_PART_TABLES
DBA_PART_TABLES describes the object-level partitioning information for all
partitioned tables in the database. Its columns are the same as those in ALL_PART_
TABLES.
See Also: "ALL_PART_TABLES" on page 2-96
DBA_PARTIAL_DROP_TABS
DBA_PARTIAL_DROP_TABS describes all tables in the database that have partially
completed DROP COLUMN operations. Its columns are the same as those in "ALL_
PARTIAL_DROP_TABS" on page 2-98.
DBA_PENDING_CONV_TABLES
DBA_PENDING_CONV_TABLES describes all pending conversion tables in the
database. Its columns are the same as those in ALL_PENDING_CONV_TABLES.
See Also: "ALL_PENDING_CONV_TABLES" on page 2-98
DBA_PENDING_TRANSACTIONS
DBA_PENDING_TRANSACTIONS describes unresolved transactions (either due to
failure or if the coordinator has not sent a commit/rollback).
Static Data Dictionary Views 2-203
DBA_POLICIES
Column
Datatype
NULL
Description
FORMATID
NUMBER
The format identifier of the transaction identifier
GLOBALID
RAW(64)
The global part (gtrid) of the transaction identifier
BRANCHID
RAW(64)
The branch qualifier (bqual) of the transaction
identifier
DBA_POLICIES
DBA_POLICIES describes all security policies in the database. Its columns are the
same as those in ALL_POLICIES.
See Also: "ALL_POLICIES" on page 2-99
DBA_POLICY_CONTEXTS
DBA_POLICY_CONTEXTS describes all driving contexts in the database. Its columns
are the same as those in ALL_POLICY_CONTEXTS.
See Also: "ALL_POLICY_CONTEXTS" on page 2-100
DBA_POLICY_GROUPS
DBA_POLICY_GROUPS describes all policy groups in the database. Its columns are
the same as those in ALL_POLICY_GROUPS.
See Also: "ALL_POLICY_GROUPS" on page 2-101
DBA_PRIV_AUDIT_OPTS
DBA_PRIV_AUDIT_OPTS describes current system privileges being audited across
the system and by user.
Column
Datatype
USER_NAME
VARCHAR2(30)
PROXY_NAME
VARCHAR2(30)
NULL
Description
User name if by user auditing. ANY CLIENT if access
by a proxy on behalf of a client is being audited.
NULL for system-wide auditing
2-204 Oracle9i Database Reference
The name of the proxy user which is performing an
operation for the client; NULL if the client is
performing the operation directly.
DBA_PROXIES
Column
Datatype
NULL
Description
PRIVILEGE
VARCHAR2(40)
NOT NULL
Name of the system privilege being audited
SUCCESS
VARCHAR2(10)
Mode for WHENEVER SUCCESSFUL system auditing
FAILURE
VARCHAR2(10)
Mode for WHENEVER NOT SUCCESSFUL system
auditing
DBA_PROCEDURES
DBA_PROCEDURES lists all functions and procedures along with their associated
properties. Its columns are the same as those in "ALL_PROCEDURES" on
page 2-101.
DBA_PROFILES
DBA_PROFILES displays all profiles and their limits.
Column
Datatype
NULL
Description
PROFILE
VARCHAR2(30)
NOT NULL
Profile name
RESOURCE_NAME
VARCHAR2(32)
NOT NULL
Resource name
RESOURCE_TYPE
VARCHAR2(8)
Indicates whether the resource profile is a KERNEL or
a PASSWORD parameter
LIMIT
VARCHAR2(40)
Limit placed on this resource for this profile
DBA_PROPAGATION
DBA_PROPAGATION displays information about all Streams propagations in the
database. Its columns are the same as those in ALL_PROPAGATION.
See Also: "ALL_PROPAGATION" on page 2-102
DBA_PROXIES
DBA_PROXIES displays Information about all proxy connections in the system.
Related View
USER_PROXIES displays information about connections the current user is allowed
to proxy. This view does not display the PROXY column.
Static Data Dictionary Views 2-205
DBA_PUBLISHED_COLUMNS
Column
Datatype
NULL
Description
PROXY
VARCHAR2(30)
NOT NULL
Name of the proxy user
CLIENT
VARCHAR2(30)
NOT NULL
Name of the client user who the proxy user can act on
behalf of
CREDENTIAL
VARCHAR2(18)
Credential passed by the proxy for the client (if any)
TYPE
VARCHAR2(5)
Type of the credential
VERSION
VARCHAR2(1)
Version of the credential
AUTHORIZATION_
CONSTRAINT
VARCHAR2(35)
Indicates the proxy’s authority to exercise roles on
client’s behalf.
ROLE
VARCHAR2(30)
Name of the role referenced in authorization
constraint
See Also: "USER_PROXIES" on page 2-283
DBA_PUBLISHED_COLUMNS
DBA_PUBLISHED_COLUMNS describes all existing source column tables. You must
have the SELECT_CATALOG_ROLE privilege to access this view.
Column
Datatype
Description
CHANGE_SET_NAME
VARCHAR2(30)
Name of the change set
CHANGE_TABLE_SCHEMA
VARCHAR2(30)
Associated change table owner
CHANGE_TABLE_NAME
VARCHAR2(31)
Associated change table name
PUB_ID
NUMBER
Publication identifier (change table object number)
SOURCE_SCHEMA_NAME
VARCHAR2(30)
Table owner in the source system
SOURCE_TABLE_NAME
VARCHAR2(31)
Table name in the source system
COLUMN_NAME
VARCHAR2(30)
Column name
DATA_TYPE
VARCHAR2(30)
Column datatype
DATA_LENGTH
NUMBER
Column length in bytes
DATA_PRECISION
NUMBER
Decimal precision for NUMBER datatype; binary precision for FLOAT
datatype; NULL for all other datatypes
DATA_SCALE
NUMBER
Digits to the right of a decimal point in a number
NULLABLE
CHAR(1)
Nulls allowed (Y |N)?
2-206 Oracle9i Database Reference
DBA_QUEUE_SCHEDULES
DBA_QUEUE_SCHEDULES
DBA_QUEUE_SCHEDULES describes the current schedules for propagating
messages.
Related View
USER_QUEUE_SCHEDULES describes current schedules related to the current user.
This view does not display the SCHEMA column.
Column
Datatype
NULL
Description
SCHEMA
VARCHAR2(30)
NOT NULL
The schema
QNAME
VARCHAR2(30)
NOT NULL
Source queue name
DESTINATION
VARCHAR2(128)
NOT NULL
Destination name, currently limited to be a DBLINK
name
START_DATE
DATE
Date to start propagation in the default date format
START_TIME
VARCHAR2(8)
Time of day at which to start propagation in
HH:MI:SS format
PROPAGATION_WINDOW
NUMBER
Duration in seconds for the propagation window
NEXT_TIME
VARCHAR2(200)
Function to compute the start of the next propagation
window
LATENCY
NUMBER
Maximum wait time to propagate a message during
the propagation window
SCHEDULE_DISABLED
VARCHAR2(1)
N if enabled; Y if disabled and schedule will not be
executed
PROCESS_NAME
VARCHAR2(8)
The name of the process executing the schedule; NULL
if not currently executing
SESSION_ID
NUMBER
The session ID (SID, SERIAL#) of the job executing
this schedule; NULL if not currently executing
INSTANCE
NUMBER
The cluster database instance number executing the
schedule
LAST_RUN_DATE
DATE
The date on the last successful execution
LAST_RUN_TIME
VARCHAR2(8)
The time of the last successful execution in HH:MI:SS
format
CURRENT_START_DATE
DATE
The date at which the current window of this
schedule was started
CURRENT_START_TIME
VARCHAR2(8)
The time of day at which the current window of this
schedule was started in HH:MI:SS format
Static Data Dictionary Views 2-207
DBA_QUEUE_TABLES
Column
Datatype
NULL
Description
NEXT_RUN_DATE
DATE
The date at which the next window of this schedule
will be started
NEXT_RUN_TIME
VARCHAR2(8)
The time of day at which the next window of this
schedule will be started in HH:MI:SS format
TOTAL_TIME
NUMBER
The total time, in seconds, spent by the system in
executing this schedule
TOTAL_NUMBER
NUMBER
The total number of messages propagated in this
schedule
TOTAL_BYTES
NUMBER
The total number of bytes propagated in this schedule
MAX_NUMBER
NUMBER
The maximum number of messages propagated in a
propagation window
MAX_BYTES
NUMBER
The maximum number of bytes propagated in a
propagation window
AVG_NUMBER
NUMBER
The average number of messages propagated in a
propagation window
AVG_SIZE
NUMBER
The average size of a propagated message in bytes
AVG_TIME
NUMBER
The average time, in seconds, to propagate a message
FAILURES
NUMBER
The number of times the execution failed; if 16, the
schedule will be disabled
LAST_ERROR_DATE
DATE
The date of the last unsuccessful execution
LAST_ERROR_TIME
VARCHAR2(8)
The time of the last unsuccessful execution
LAST_ERROR_MSG
VARCHAR2(4000)
The error number and error message text of the last
unsuccessful execution
DBA_QUEUE_TABLES
DBA_QUEUE_TABLES describes the queues in all queue tables in the database. Its
columns are the same as those in ALL_QUEUE_TABLES.
See Also: "ALL_QUEUE_TABLES" on page 2-103
DBA_QUEUES
DBA_QUEUES describes the operational characteristics of every queue in a database.
Its columns are the same as those in "ALL_QUEUES" on page 2-105.
2-208 Oracle9i Database Reference
DBA_REGISTERED_MVIEW_GROUPS
See Also: Oracle9i Application Developer’s Guide - Advanced
Queuing for more information about this view and Advanced
Queuing
DBA_RCHILD
DBA_RCHILD lists all the children in any refresh group.
Column
Datatype
REFGROUP
NUMBER
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
Owner of the object in the refresh group
NAME
VARCHAR2(30)
NOT NULL
Name of the object in the refresh group
TYPE#
VARCHAR2(30)
Internal identifier of refresh group
Type of the object in the refresh group
DBA_REFRESH
DBA_REFRESH describes all refresh groups in the database. Its columns are the
same as those in "ALL_REFRESH" on page 2-105.
DBA_REFRESH_CHILDREN
DBA_REFRESH_CHILDREN lists all of the objects in all refresh groups in the
database. Its columns are the same as those in "ALL_REFRESH_CHILDREN" on
page 2-106.
DBA_REFS
DBA_REFS describes the REF columns and REF attributes in object type columns of
all the objects in the database. Its columns are the same as those in "ALL_REFS" on
page 2-108.
DBA_REGISTERED_MVIEW_GROUPS
DBA_REGISTERED_MVIEW_GROUPS lists all the materialized view repgroups at this
site.
Static Data Dictionary Views 2-209
DBA_REGISTERED_MVIEWS
Column
Datatype
NULL
Description
NAME
VARCHAR2(30)
Name of the materialized view replication group
MVIEW_SITE
VARCHAR2(128)
Site of the master of the materialized view repgroup
GROUP_COMMENT
VARCHAR2(80)
Description of the materialized view repgroup
VERSION
VARCHAR2(8)
Version of the materialized view repgroup
FNAME
VARCHAR2(30)
Name of the flavor of the materialized view object
group
OWNER
VARCHAR2(30)
Owner of the materialized view group
DBA_REGISTERED_MVIEWS
DBA_REGISTERED_MVIEWS describes all registered materialized views (registered
at a master site or a master materialized view site) in the database. Its columns are
the same as those in ALL_REGISTERED_MVIEWS.
See Also: "ALL_REGISTERED_MVIEWS" on page 2-108
DBA_REGISTRY
DBA_REGISTRY displays information about the components loaded into the
database.
Related View
USER_REGISTRY displays information about the components loaded into the
database that are owned by the current user.
Column
Datatype
NULL
Description
COMP_ID
VARCHAR2(30)
NOT NULL
Component identifier
COMP_NAME
VARCHAR2(255)
Component name
VERSION
VARCHAR2(30)
Component version loaded
2-210 Oracle9i Database Reference
DBA_REGISTRY_HIERARCHY
Column
Datatype
STATUS
VARCHAR2(11)
NULL
Description
Component status:
■
INVALID
■
VALID
■
LOADING
■
LOADED
■
UPGRADING
■
UPGRADED
■
DOWNGRADING
■
DOWNGRADED
■
REMOVING
■
REMOVED
Time when the component was last modified
MODIFIED
VARCHAR2(20)
CONTROL
VARCHAR2(30)
NOT NULL
User that created the component entry
SCHEMA
VARCHAR2(30)
NOT NULL
User that contains the objects for the component
PROCEDURE
VARCHAR2(61)
Validation procedure
STARTUP
VARCHAR2(8)
Indicates whether the component requires a startup
after the upgrade
PARENT_ID
VARCHAR2(30)
Parent component identifier
See Also: "USER_REGISTRY" on page 2-284
DBA_REGISTRY_HIERARCHY
DBA_REGISTRY_HIERARCHY displays information about the components loaded
into the database, grouped by owner and organized in the component hierarchy.
Column
Datatype
NULL
Description
COMP_ID
VARCHAR2(4000)
Component identifier
VERSION
VARCHAR2(30)
Component version loaded
Static Data Dictionary Views 2-211
DBA_REPAIR_TABLE
Column
Datatype
STATUS
VARCHAR2(11)
MODIFIED
NULL
Description
Component status:
■
INVALID
■
VALID
■
LOADING
■
LOADED
■
UPGRADING
■
UPGRADED
■
DOWNGRADING
■
DOWNGRADED
■
REMOVING
■
REMOVED
Time when the component was last modified
VARCHAR2(20)
DBA_REPAIR_TABLE
DBA_REPAIR_TABLE describes any corruptions found by the DBMS_
REPAIR.CHECK_OBJECT procedure. This information is used by the DBMS_
REPAIR.FIX_CORRUPT_BLOCKS procedure on execution. To create this view, first
run the DBMS_REPAIR.ADMIN_TABLES procedure. To populate the resulting repair
table for an object, run the DBMS_REPAIR.CHECK_OBJECT procedure on the object.
Note: The table created by the DBMS_REPAIR.ADMIN_TABLES
procedure is called REPAIR TABLE by default. If you specify a
different name, this view will have the name you specify, preceded
by "DBA_REPAIR_".
Column
Datatype
NULL
Description
OBJECT_ID
NUMBER
NOT NULL
Dictionary object number of the object with the
corruption
TABLESPACE_ID
NUMBER
NOT NULL
Tablespace number of the corrupt object
RELATIVE_FILE_ID
NUMBER)
NOT NULL
Relative file number of the corrupt object
BLOCK_ID
NUMBER
NOT NULL
Block number of the corruption
CORRUPT_TYPE
NUMBER
NOT NULL
Type of corruption encountered
SCHEMA_NAME
VARCHAR2(30)
NOT NULL
Schema of the corrupt object
OBJECT_NAME
VARCHAR2(30)
NOT NULL
Name of the corrupt object
2-212 Oracle9i Database Reference
DBA_RESUMABLE
Column
Datatype
NULL
Description
BASEOBJECT_NAME
VARCHAR2(30)
NULL
If the object is an index, the name of its base table
PARTITION_NAME
VARCHAR2(30)
NULL
Partition or subpartition name, if applicable
CORRUPT_DESCRIPTION
VARCHAR2(200)
NULL
Description of corruption
REPAIR_DESCRIPTION
VARCHAR2(200)
NULL
Description of repair action
MARKED_CORRUPT
VARCHAR2(10)
NOT NULL
Whether the block is marked corrupt (TRUE | FALSE)
CHECK_TIMESTAMP
DATE
NOT NULL
Date on which this row was insert into the repair table
FIX_TIMESTAMP
DATE
NULL
Date on which the block was modified by the FIX_
CORRUPT_BLOCKS procedure, if applicable
REFORMAT_TIMESTAMP
DATE
NULL
Reserved for future use
DBA_RESUMABLE
DBA_RESUMABLE lists all resumable statements executed in the system.
Related View
USER_RESUMABLE lists resumable statements executed by the current user. This
view does not display the USER_ID column.
Column
Datatype
NULL
Description
USER_ID
NUMBER
User ID Number of the Resumable Statement Owner
SESSION_ID
NUMBER
Session Identifier of Resumable Statement
INSTANCE_ID
NUMBER
Instance Number of Resumable Statement
COORD_SESSION_ID
NUMBER
Session Identifier of Parallel Coordinator
COORD_INSTANCE_ID
NUMBER
Instance Number on which the Parallel Coordinator is
Running
SQL_TEXT
VARCHAR2(1000)
The resumable statement, selected from the V$SQL
view.
NAME
VARCHAR2(4000)
The name given in the resumable clause of this
resumable statement.
STATUS
VARCHAR2(16)
The status of the resumable statement. Its value can
be one of RUNNING, SUSPENDED, ABORTED,
ABORTING, TIMEOUT
ERROR_NUMBER
NUMBER
The error code of the last correctable error. When
STATUS is equal to RUNNING, its value will be set to 0.
Static Data Dictionary Views 2-213
DBA_RGROUP
Column
Datatype
NULL
Description
ERROR_MSG
VARCHAR2(4000)
The error message corresponding to ERROR_NUMBER.
It will be set to NULL when ERROR_NUMBER is
NULL.
ERROR_PARAMETER1
VARCHAR2(80)
The first parameter for the error message. NULL if no
error.
ERROR_PARAMETER2
VARCHAR2(80)
The second parameter for the error message. NULL if
no error.
ERROR_PARAMETER3
VARCHAR2(80)
The third parameter for the error message. NULL if
no error.
ERROR_PARAMETER4
VARCHAR2(80)
The forth parameter for the error message. NULL if
no error.
ERROR_PARAMETER5
VARCHAR2(80)
The fifth parameter for the error message. NULL if no
error.
START_TIME
DATE
The start local time of the resumable statement.
SUSPEND_TIME
DATE
The last local time when the resumable statement was
suspended. It is initialized to NULL.
RESUME_TIME
DATE
The last local time when the suspended resumable
statement is resumed. It is initialized to NULL.
TIMEOUT
NUMBER
Timeout of the resumable statement
See Also: "USER_RESUMABLE" on page 2-285
DBA_RGROUP
DBA_RGROUP lists all refresh groups.
Column
Datatype
REFGROUP
NUMBER
OWNER
VARCHAR2(30)
NOT NULL
Owner of the object in the refresh group
NAME
VARCHAR2(30)
NOT NULL
Name of the object in the refresh group
IMPLICIT_DESTROY
VARCHAR2(1)
(Y or N) If Y, then destroy the refresh group when its
last item is removed
PUSH_DEFERRED_RPC
VARCHAR2(1)
(Y or N) If Y, then push changes from snapshot to
master before refresh
REFRESH_AFTER_ERRORS
VARCHAR2(1)
(Y or N) If Y, proceed with refresh despite error when
pushing deferred RPC’s
ROLLBACK_SEG
VARCHAR2(30)
Name of the rollback segment to use while refreshing
2-214 Oracle9i Database Reference
NULL
Description
Internal identifier of refresh group
DBA_ROLLBACK_SEGS
Column
Datatype
NULL
Description
JOB
NUMBER
NOT NULL
Identifier of job used to refresh the group
automatically
PURGE_OPTION
NUMBER(38)
The method for purging the transaction queue after
each push. 1 indicates quick purge option; 2 indicates
precise purge option
PARALLELISM
NUMBER(38)
The level of parallelism for transaction propagation
HEAP_SIZE
NUMBER(38)
The size of the heap
DBA_ROLE_PRIVS
DBA_ROLE_PRIVS describes the roles granted to all users and roles in the database.
Related View
USER_ROLE_PRIVS describes the roles granted to the current user.
Column
Datatype
NULL
Description
GRANTEE
VARCHAR2(30)
GRANTED_ROLE
VARCHAR2(30)
ADMIN_OPTION
VARCHAR2(3)
Indicates whether the grant was with the ADMIN
OPTION (YES) or not (NO)
DEFAULT_ROLE
VARCHAR2(3)
Indicates whether the role is designated as a DEFAULT
ROLE for the user (YES) or not (NO)
Name of the user or role receiving the grant
NOT NULL
Granted role name
See Also: "USER_ROLE_PRIVS" on page 2-285
DBA_ROLES
DBA_ROLES lists all roles that exist in the database.
Column
Datatype
NULL
Description
ROLE
VARCHAR2(30)
NOT NULL
Role name
PASSWORD_REQUIRED
VARCHAR2(8)
Indicates if the role requires a password to be enabled
DBA_ROLLBACK_SEGS
DBA_ROLLBACK_SEGS describes rollback segments.
Static Data Dictionary Views 2-215
DBA_RSRC_CONSUMER_GROUP_PRIVS
Column
Datatype
NULL
Description
SEGMENT_NAME
VARCHAR2(30)
NOT NULL
Name of the rollback segment
OWNER
VARCHAR2(6)
TABLESPACE_NAME
VARCHAR2(30)
NOT NULL
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
NOT NULL
Percent increase for extent size
STATUS
VARCHAR2(16)
Rollback segment status
INSTANCE_NUM
VARCHAR2(40)
Rollback segment owning Oracle Real Application
Cluster instance number
RELATIVE_FNO
NUMBER
Owner of the rollback segment
NOT NULL
Relative file number of the segment header
DBA_RSRC_CONSUMER_GROUP_PRIVS
DBA_RSRC_CONSUMER_GROUP_PRIVS lists all resource consumer groups and the
users and roles assigned to them. The grant referred to in this view and the related
view is the grant of the SWITCH_CONSUMER_GROUP object privilege, which is
granted using the DBMS_RESOURCE_MANAGER_PRIVS package. (This privilege is
not granted through the GRANT SQL statement.)
Related View
USER_RSRC_CONSUMER_GROUP_PRIVS lists all resource consumer groups to
which the current user is assigned. This view does not display the GRANTEE
column.
Column
Datatype
NULL
Description
GRANTEE
VARCHAR2(30)
NOT NULL
User or role receiving the grant
GRANTED_GROUP
VARCHAR2(30)
2-216 Oracle9i Database Reference
Granted consumer group name
DBA_RSRC_MANAGER_SYSTEM_PRIVS
Column
Datatype
NULL
Description
GRANT_OPTION
VARCHAR2(3)
(YES/NO) Indicates whether grant was with the
GRANT option
INITIAL_GROUP
VARCHAR2(3)
(YES/NO) Indicates whether consumer group is
designated as the default for this user or role
See Also:
■
■
"USER_RSRC_CONSUMER_GROUP_PRIVS" on page 2-285
Oracle9i Supplied PL/SQL Packages and Types Reference for more
information on consumer group privileges
DBA_RSRC_CONSUMER_GROUPS
DBA_RSRC_CONSUMER_GROUPS lists all resource consumer groups in the database.
Column
Datatype
NULL
Description
CONSUMER_GROUP
VARCHAR2(30)
Name of the consumer group
CPU_METHOD
VARCHAR2(30)
CPU resource allocation method for the consumer
group
COMMENTS
VARCHAR2(2000)
Text comment on the consumer group
STATUS
VARCHAR2(30)
Status of the consumer group: PENDING if the group
is part of the pending area, ACTIVE otherwise.
MANDATORY
VARCHAR2(3)
Whether the consumer group is mandatory (YES |
NO)
DBA_RSRC_MANAGER_SYSTEM_PRIVS
DBA_RSRC_MANAGER_SYSTEM_PRIVS lists all the users and roles that have been
granted the ADMINISTER_RESOURCE_MANAGER system privilege, which is granted
using the DBMS_RESOURCE_MANAGER_PRIVS package. (This privilege is not
granted through the SQL GRANT statement.)
Related View
USER_RSRC_MANAGER_SYSTEM_PRIVS lists users who are granted system
privilege for the DBMS_RESOURCE_MANAGER package. This view does not display
the GRANTEE column.
Static Data Dictionary Views 2-217
DBA_RSRC_PLAN_DIRECTIVES
Column
Datatype
NULL
Description
GRANTEE
VARCHAR2(30)
NOT NULL
User or role receiving the grant
PRIVILEGE
VARCHAR2(40)
NOT NULL
Name of the system privilege
ADMIN_OPTION
VARCHAR2(3)
Whether the grant was with the ADMIN option
See Also: Oracle9i Supplied PL/SQL Packages and Types Reference for
more information on consumer group privileges
DBA_RSRC_PLAN_DIRECTIVES
DBA_RSRC_PLAN_DIRECTIVES lists all resource plan directives in the database.
See Also:
■
■
Oracle9i Database Administrator’s Guide for information on
resource plans in general
Oracle9i Supplied PL/SQL Packages and Types Reference for more
information on creating resource plans with the DBMS_
RESOURCE_MANAGER package
Column
Datatype
Description
PLAN
VARCHAR2(30)
Name of the plan to which this directive belongs
GROUP_OR_SUBPLAN
VARCHAR2(30)
Name of the consumer group or subplan referred to
TYPE
VARCHAR2(14)
Whether GROUP_OR_SUBPLAN refers to a consumer group or plan
CPU_P1
NUMBER
First parameter for the CPU resource allocation method
CPU_P2
NUMBER
Second parameter for the CPU resource allocation method
CPU_P3
NUMBER
Third parameter for the CPU resource allocation method
CPU_P4
NUMBER
Fourth parameter for the CPU resource allocation method
CPU_P5
NUMBER
Fifth parameter for the CPU resource allocation method
CPU_P6
NUMBER
Sixth parameter for the CPU resource allocation method
CPU_P7
NUMBER
Seventh parameter for the CPU resource allocation method
CPU_P8
NUMBER
Eighth parameter for the CPU resource allocation method
ACTIVE_SESS_POOL_P1
NUMBER
First parameter for the active session pool resource allocation method
QUEUING_P1
NUMBER
First parameter for the queuing resource allocation method
2-218 Oracle9i Database Reference
DBA_RSRC_PLANS
Column
Datatype
Description
PARALLEL_DEGREE_
LIMIT_P1
NUMBER
First parameter for the parallel degree limit resource allocation method
SWITCH_GROUP
VARCHAR2(30)
Group to switch into
SWITCH_TIME
NUMBER
Amount of run time before session is automatically switched
SWITCH_ESTIMATE
VARCHAR2(5)
(TRUE/FALSE) TRUE indicates estimated execution time should be
used for switch criteria
MAX_EST_EXEC_TIME
NUMBER
First parameter for the maximum estimated execution time
UNDO_POOL
NUMBER
Undo pool size for the consumer group
COMMENTS
VARCHAR2(2000)
Text comment on the plan directive
STATUS
VARCHAR2(30)
Status of the directive: PENDING if it is part of the pending area,
ACTIVE otherwise
MANDATORY
VARCHAR2(3)
Whether the plan is mandatory (YES | NO)
DBA_RSRC_PLANS
DBA_RSRC_PLANS lists all resource plans in the database. For a list of currently
active plans, see "V$RSRC_PLAN" on page 3-126.
See Also:
■
■
Oracle9i Database Administrator’s Guide for information on
resource plans in general
Oracle9i Supplied PL/SQL Packages and Types Reference for more
information on creating resource plans with the DBMS_
RESOURCE_MANAGER package
Column
Datatype
NULL
Description
PLAN
VARCHAR2(30)
Name of the resource plan
NUM_PLAN_DIRECTIVES
NUMBER
Number of plan directives for the plan
CPU_METHOD
VARCHAR2(30)
CPU resource allocation method for the plan
ACTIVE_SESS_POOL_MTH
VARCHAR2(30)
Active session pool resource allocation method for the
plan
PARALLEL_DEGREE_
LIMIT_MTH
VARCHAR2(30)
Parallel degree limit resource allocation method for
the plan
QUEUING_MTH
VARCHAR2(30)
Queuing resource allocation method for the plan
COMMENTS
VARCHAR2(2000)
Text comment on the plan
Static Data Dictionary Views 2-219
DBA_RULE_SET_RULES
Column
Datatype
NULL
Description
STATUS
VARCHAR2(30)
Status of the plan: PENDING if it is part of the pending
area, ACTIVE otherwise
MANDATORY
VARCHAR2(3)
(YES/NO) Indicates whether the plan is mandatory
DBA_RULE_SET_RULES
DBA_RULE_SET_RULES describes the rules in all rule sets in the database. Its
columns are the same as those in ALL_RULE_SET_RULES.
See Also: "ALL_RULE_SET_RULES" on page 2-110
DBA_RULE_SETS
DBA_RULE_SETS describes all rule sets in the database. Its columns are the same as
those in ALL_RULE_SETS.
See Also: "ALL_RULE_SETS" on page 2-110
DBA_RULES
DBA_RULES describes all rules in the database. Its columns are the same as those in
ALL_RULES.
See Also: "ALL_RULES" on page 2-111
DBA_SEGMENTS
DBA_SEGMENTS describes the storage allocated for all segments in the database.
Related View
USER_SEGMENTS describes the storage allocated for the segments owned by the
current user’s objects. This view does not display the OWNER, HEADER_FILE,
HEADER_BLOCK, or RELATIVE_FNO columns.
Column
Datatype
OWNER
VARCHAR2(30)
Username of the segment owner
SEGMENT_NAME
VARCHAR2(81)
Name, if any, of the segment
2-220 Oracle9i Database Reference
NULL
Description
DBA_SEQUENCES
Column
Datatype
NULL
Description
PARTITION_NAME
VARCHAR2(30)
Object Partition Name (Set to NULL for
non-partitioned objects)
SEGMENT_TYPE
VARCHAR2(17)
Type of segment: INDEX PARTITION, TABLE
PARTITION, TABLE, CLUSTER, INDEX,
ROLLBACK, DEFERRED ROLLBACK, TEMPORARY,
CACHE, LOBSEGMENT and LOBINDEX
TABLESPACE_NAME
VARCHAR2(30)
Name of the tablespace containing the segment
HEADER_FILE
NUMBER
ID of the file containing the segment header
HEADER_BLOCK
NUMBER
ID of the block containing the segment header
BYTES
NUMBER
Size in bytes, of the segment
BLOCKS
NUMBER
Size, in Oracle blocks, of the segment
EXTENTS
NUMBER
Number of extents allocated to the segment
INITIAL_EXTENT
NUMBER
Size in bytes requested for the initial extent of the
segment at create time. (Oracle rounds the extent size
to multiples of 5 blocks if the requested size is greater
than 5 blocks.)
NEXT_EXTENT
NUMBER
Size in bytes of the next extent to be allocated to the
segment
MIN_EXTENTS
NUMBER
Minimum number of extents allowed in the segment
MAX_EXTENTS
NUMBER
Maximum number of extents allowed in the segment
PCT_INCREASE
NUMBER
Percent by which to increase the size of the next
extent to be allocated
FREELISTS
NUMBER
Number of process freelists allocated to this segment
FREELIST_GROUPS
NUMBER
Number of freelist groups allocated to this segment
RELATIVE_FNO
NUMBER
Relative file number of the segment header
BUFFER_POOL
VARCHAR2(7)
Default buffer pool for the object
See Also: "USER_SEGMENTS" on page 2-286
DBA_SEQUENCES
DBA_SEQUENCES describes all sequences in the database. Its columns are the same
as those in "ALL_SEQUENCES" on page 2-112.
Static Data Dictionary Views 2-221
DBA_SOURCE
DBA_SOURCE
DBA_SOURCE describes the text source of all stored objects in the database. Its
columns are the same as those in "ALL_SOURCE" on page 2-112.
DBA_SOURCE_TABLES
DBA_SOURCE_TABLES enables publishers to see all existing (published) source
tables. Its columns are the same as those in ALL_SOURCE_TABLES.
See Also: "ALL_SOURCE_TABLES" on page 2-113
DBA_SQLJ_TYPE_ATTRS
DBA_SQLJ_TYPE_ATTRS describes the attributes of all SQLJ object types in the
database. Its columns are the same as those in ALL_SQLJ_TYPE_ATTRS.
See Also: "ALL_SQLJ_TYPE_ATTRS" on page 2-113
DBA_SQLJ_TYPE_METHODS
DBA_SQLJ_TYPE_METHODS describes the methods of all SQLJ object types in the
database. Its columns are the same as those in ALL_SQLJ_TYPE_METHODS.
See Also: "ALL_SQLJ_TYPE_METHODS" on page 2-114
DBA_SQLJ_TYPES
DBA_SQLJ_TYPES describes all SQLJ object types in the database. Its columns are
the same as those in ALL_SQLJ_TYPES.
See Also: "ALL_SQLJ_TYPES" on page 2-115
DBA_STMT_AUDIT_OPTS
DBA_STMT_AUDIT_OPTS describes current system auditing options across the
system and by user.
2-222 Oracle9i Database Reference
DBA_STREAMS_SCHEMA_RULES
Column
Datatype
USER_NAME
VARCHAR2(30)
NULL
Description
User name if by user auditing. ANY CLIENT if access
by a proxy on behalf of a client is being audited.
NULL for system-wide auditing
The name of the proxy user which is performing an
operation for the client. NULL if the client is
performing the operation directly.
PROXY_NAME
VARCHAR2(30)
AUDIT_OPTION
VARCHAR2(40)
SUCCESS
VARCHAR2(10)
Mode for WHENEVER SUCCESSFUL system auditing
FAILURE
VARCHAR2(10)
Mode for WHENEVER NOT SUCCESSFUL system
auditing
NOT NULL
Name of the system auditing option
DBA_STORED_SETTINGS
DBA_STORED_SETTINGS lists information about the persistent parameter settings
for stored PL/SQL units for which the current user has execute privileges. It also
returns parameter information for all objects in the database and is accessible only
to users with the SELECT_CATALOG_ROLE privilege. Its columns are the same as
those in "ALL_STORED_SETTINGS" on page 2-116.
DBA_STREAMS_GLOBAL_RULES
DBA_STREAMS_GLOBAL_RULES displays information about the global rules created
for all Streams capture processes, propagations, and apply processes in the
database. Its columns are the same as those in ALL_STREAMS_GLOBAL_RULES.
See Also: "ALL_STREAMS_GLOBAL_RULES" on page 2-117
DBA_STREAMS_SCHEMA_RULES
DBA_STREAMS_SCHEMA_RULES displays information about the schema rules
created for all Streams capture processes, propagations, and apply processes in the
database. Its columns are the same as those in ALL_STREAMS_SCHEMA_RULES.
See Also: "ALL_STREAMS_SCHEMA_RULES" on page 2-118
Static Data Dictionary Views 2-223
DBA_STREAMS_TABLE_RULES
DBA_STREAMS_TABLE_RULES
DBA_STREAMS_TABLE_RULES displays information about the table rules created
for all Streams capture processes, propagations, and apply processes in the
database. Its columns are the same as those in ALL_STREAMS_TABLE_RULES.
See Also: "ALL_STREAMS_TABLE_RULES" on page 2-119
DBA_SUBPART_COL_STATISTICS
DBA_SUBPART_COL_STATISTICS provides column statistics and histogram
information for all subpartitions in the database. Its columns are the same as those
in "ALL_STORED_SETTINGS" on page 2-116.
DBA_SUBPART_HISTOGRAMS
DBA_SUBPART_HISTOGRAMS lists actual histogram data (end-points per
histogram) for histograms on all table subpartitions in the database. Its columns are
the same as those in "ALL_SUBPART_HISTOGRAMS" on page 2-122.
DBA_SUBPART_KEY_COLUMNS
DBA_SUBPART_KEY_COLUMNS lists subpartitioning key columns for all
composite-partitioned tables (and local indexes on composite-partitioned tables) in
the database. Its columns are the same as those in ALL_SUBPART_KEY_COLUMNS.
See Also: "ALL_SUBPART_KEY_COLUMNS" on page 2-123
DBA_SUBPARTITION_TEMPLATES
DBA_SUBPARTITION_TEMPLATES describes all subpartition templates in the
database. Its columns are the same as those in ALL_SUBPARTITION_TEMPLATES.
See Also: "ALL_SUBPARTITION_TEMPLATES" on page 2-124
DBA_SUBSCRIBED_COLUMNS
DBA_SUBSCRIBED_COLUMNS enables publishers to view the columns of published
tables to which they have subscribed. You must have the SELECT_CATALOG_ROLE
privilege to access this view. The columns in DBA_SUBSCRIBED_COLUMNS are the
same as those in "ALL_SUBSCRIBED_COLUMNS" on page 2-124.
2-224 Oracle9i Database Reference
DBA_SYS_PRIVS
DBA_SUBSCRIBED_TABLES
DBA_SUBSCRIBED_TABLES enables publishers to view all of the published tables
to which they have subscribed. Its columns are the same as those in "ALL_
SUBSCRIBED_TABLES" on page 2-125.
DBA_SUBSCRIPTIONS
DBA_SUBSCRIPTIONS enables publishers to see all subscriptions. You must have
the SELECT_CATALOG_ROLE privilege to access this view. Except for the
USERNAME column, which identifies the user name of the subscriber, DBA_
SUBSCRIPTIONS has the same columns as those in "ALL_SUBSCRIPTIONS" on
page 2-125.
DBA_SYNONYMS
DBA_SYNONYMS describes all synonyms in the database. Its columns are the same as
those in "ALL_SYNONYMS" on page 2-126.
DBA_SYS_PRIVS
DBA_SYS_PRIVS describes system privileges granted to users and roles. This view
does not display the USERNAME column.
Related View
USER_SYS_PRIVS describes system privileges granted to the current user. This
view does not display the GRANTEE column, but instead displays the USERNAME
column.
Column
Datatype
NULL
Description
GRANTEE
VARCHAR2(30)
NOT NULL
Grantee name, user, or role receiving the grant
USERNAME
VARCHAR2(30)
PRIVILEGE
VARCHAR2(40)
ADMIN_OPTION
VARCHAR2(3)
Name of the current user
NOT NULL
System privilege
Grant was with the ADMIN option
Static Data Dictionary Views 2-225
DBA_TAB_COL_STATISTICS
DBA_TAB_COL_STATISTICS
DBA_TAB_COL_STATISTICS contains column statistics and histogram information
extracted from "DBA_TAB_COLUMNS" on page 2-226. Its columns are the same as
those in "ALL_TAB_COL_STATISTICS" on page 2-127.
DBA_TAB_COLUMNS
DBA_TAB_COLUMNS describes columns of all tables, views, and clusters in the
database. Its columns are the same as those in "ALL_TAB_COLUMNS" on
page 2-128. To gather statistics for this view, use the SQL ANALYZE statement.
DBA_TAB_COMMENTS
DBA_TAB_COMMENTS describes comments on all tables and views in the database.
Its columns are the same as those in "ALL_TAB_COMMENTS" on page 2-130.
DBA_TAB_HISTOGRAMS
DBA_TAB_HISTOGRAMS describes histograms on columns of all tables in the
database. Its columns are the same as those in "ALL_TAB_HISTOGRAMS" on
page 2-130.
DBA_TAB_MODIFICATIONS
DBA_TAB_MODIFICATIONS describes modifications to all tables in the database
that have been modified since the last time statistics were gathered on the tables. Its
columns are the same as those in "ALL_TAB_MODIFICATIONS" on page 2-131.
Note: This view is populated only for tables with the
MONITORING attribute. It is intended for statistics collection over a
long period of time and may not be populated until a few hours
after the actual modifications occurred.
DBA_TAB_PARTITIONS
DBA_TAB_PARTITIONS provides the partition-level partitioning information,
partition storage parameters, and partition statistics determined by ANALYZE
2-226 Oracle9i Database Reference
DBA_TABLES
statements for all partitions in the database. Its columns are the same as those in
"ALL_TAB_PARTITIONS" on page 2-132.
DBA_TAB_PRIVS
DBA_TAB_PRIVS describes all object grants in the database.
Related View
USER_TAB_PRIVS describes the object grants for which the current user is the
object owner, grantor, or grantee.
Column
Datatype
NULL
Description
GRANTEE
VARCHAR2(30)
NOT NULL
Name of the user to whom access was granted
OWNER
VARCHAR2(30)
NOT NULL
Owner of the object
TABLE_NAME
VARCHAR2(30)
NOT NULL
Name of the object
GRANTOR
VARCHAR2(30)
NOT NULL
Name of the user who performed the grant
PRIVILEGE
VARCHAR2(40)
NOT NULL
Privilege on the object
GRANTABLE
VARCHAR2(3)
Indicates whether the privilege was granted with the
GRANT OPTION (YES) or not (NO)
HIERARCHY
VARCHAR2(3)
Indicates whether the privilege was granted with the
HIERARCHY OPTION (YES) or not (NO)
See Also: "USER_TAB_PRIVS" on page 2-290
DBA_TAB_SUBPARTITIONS
DBA_TAB_SUBPARTITIONS describes, for each table subpartition, the subpartition
name, name of the table and partition to which it belongs, and its storage attributes.
Its columns are the same as those in "ALL_TAB_SUBPARTITIONS" on page 2-136.
Note: Statistics are not collected on a per-subpartition basis.
DBA_TABLES
DBA_TABLES describes all relational tables in the database. Its columns are the
same as those in ALL_TABLES. To gather statistics for this view, use the SQL
ANALYZE statement.
Static Data Dictionary Views 2-227
DBA_TABLESPACES
See Also: "ALL_TABLES" on page 2-137
DBA_TABLESPACES
DBA_TABLESPACES describes all tablespaces in the database.
Related View
USER_TABLESPACES describes the tablespaces accessible to the current user. This
view does not display the PLUGGED_IN column.
Column
Datatype
NULL
Description
TABLESPACE_NAME
VARCHAR2(30)
NOT NULL
Tablespace name
BLOCK_SIZE
NUMBER
NOT NULL
Tablespace block size
INITIAL_EXTENT
NUMBER
Default initial extent size
NEXT_EXTENT
NUMBER
Default incremental extent size
MIN_EXTENTS
NUMBER
MAX_EXTENTS
NUMBER
Default maximum number of extents
PCT_INCREASE
NUMBER
Default percent increase for extent size
MIN_EXTLEN
NUMBER
Minimum extent size for this tablespace
STATUS
VARCHAR2(9)
Tablespace status:
CONTENTS
LOGGING
VARCHAR2(9)
VARCHAR2(9)
NOT NULL
Default minimum number of extents
■
ONLINE
■
OFFLINE
■
READ ONLY
Tablespace contents:
■
UNDO
■
PERMANENT
■
TEMPORARY
Default logging attribute:
■
LOGGING
■
NOLOGGING
FORCE_LOGGING
VARCHAR2(3)
Indicates whether this tablespace is under force
logging mode (YES) or not (NO)
EXTENT_MANAGEMENT
VARCHAR2(10)
Indicates how the extents of this tablespace are
managed:
2-228 Oracle9i Database Reference
■
DICTIONARY - Tablespace is dictionary managed
■
LOCAL - Tablespace is locally managed
DBA_TEMP_FILES
Column
Datatype
ALLOCATION_TYPE
VARCHAR2(9)
NULL
Description
Type of extent allocation in effect for this tablespace:
■
SYSTEM
■
UNIFORM
■
USER
PLUGGED_IN
VARCHAR2(3)
Indicates whether this tablespace is plugged in (YES)
or not (NO)
SEGMENT_SPACE_
MANAGEMENT
VARCHAR2(6)
Indicates how the used and free space in the segments
in this tablespace are managed:
■
■
MANUAL - Segment space in this tablespace is
managed using free lists
AUTO - Segment space in this tablespace is
managed using bitmaps
See Also: "USER_TABLESPACES" on page 2-291
DBA_TEMP_FILES
DBA_TEMP_FILES describes all temporary files (tempfiles) in the database.
Column
Datatype
NULL
FILE_NAME
VARCHAR2(513)
Name of the database temp file
FILE_ID
NUMBER
File identifier number of the database temp file
NOT NULL
Description
Name of the tablespace to which the file belongs
TABLESPACE_NAME
VARCHAR2(30)
BYTES
NUMBER
Size of the file (in bytes)
BLOCKS
NUMBER
Size of the file (in Oracle blocks)
STATUS
CHAR(9)
File status:
■
AVAILABLE
RELATIVE_FNO
NUMBER
Tablespace-relative file number
AUTOEXTENSIBLE
VARCHAR2(3)
Indicates whether the file is autoextensible (YES) or
not (NO)
MAXBYTES
NUMBER
maximum size of the file (in bytes)
MAXBLOCKS
NUMBER
Maximum size of the file (in Oracle blocks)
INCREMENT_BY
NUMBER
Default increment for autoextension
USER_BYTES
NUMBER
Size of the useful portion of the file (in bytes)
USER_BLOCKS
NUMBER
Size of the useful portion of the file (in Oracle blocks)
Static Data Dictionary Views 2-229
DBA_TRANSFORMATIONS
DBA_TRANSFORMATIONS
DBA_TRANSFORMATIONS displays information about all transformations in the
database. These transformations can be specified with Advanced Queuing
operations such as enqueue, dequeue, and subscribe to automatically integrate
transformations in AQ messaging.
Related View
USER_TRANSFORMATIONS displays information about transformations owned by
the current user. This view does not display the OWNER column.
Column
Datatype
NULL
Description
TRANSFORMATION_ID
NUMBER
NOT NULL
Unique identifier for the transformation
OWNER
VARCHAR2(30)
NOT NULL
Owning user of the transformation
NAME
VARCHAR2(30)
NOT NULL
Transformation name
FROM_TYPE
VARCHAR2(61)
Source type name
TO_TYPE
VARCHAR2(91)
Target type name
See Also: "USER_TRANSFORMATIONS" on page 2-291
DBA_TRIGGER_COLS
DBA_TRIGGER_COLS lists the use of columns in all triggers in the database. Its
columns are the same as those in "ALL_TRIGGER_COLS" on page 2-140.
DBA_TRIGGERS
DBA_TRIGGERS describes all triggers in the database. Its columns are the same as
those in "ALL_TRIGGERS" on page 2-141.
DBA_TS_QUOTAS
DBA_TS_QUOTAS describes tablespace quotas for all users.
Related View
USER_TS_QUOTAS describes tablespace quotas for the current user. This view does
not display the USERNAME column.
2-230 Oracle9i Database Reference
DBA_TYPES
Column
Datatype
NULL
Description
TABLESPACE_NAME
VARCHAR2(30)
NOT NULL
Tablespace name
USERNAME
VARCHAR2(30)
NOT NULL
User with resource rights on the tablespace
BYTES
NUMBER
Number of bytes charged to the user
MAX_BYTES
NUMBER
User’s quota in bytes, or -1 if no limit
BLOCKS
NUMBER
MAX_BLOCKS
NUMBER
NOT NULL
Number of Oracle blocks charged to the user
User’s quota in Oracle blocks, or -1 if no limit
DBA_TYPE_ATTRS
DBA_TYPE_ATTRS describes the attributes of all object types in the database. Its
columns are the same as those in ALL_TYPE_ATTRS.
See Also: "ALL_TYPE_ATTRS" on page 2-142
DBA_TYPE_METHODS
DBA_TYPE_METHODS describes the methods of all object types in the database. Its
columns are the same as those in ALL_TYPE_METHODS.
See Also: "ALL_TYPE_METHODS" on page 2-143
DBA_TYPE_VERSIONS
DBA_TYPE_VERSIONS describes the versions of all object types in the database. Its
columns are the same as those in ALL_TYPE_VERSIONS.
See Also: "ALL_TYPE_VERSIONS" on page 2-144
DBA_TYPES
DBA_TYPES describes all object types in the database. Its columns are the same as
those in ALL_TYPES.
See Also: "ALL_TYPES" on page 2-144
Static Data Dictionary Views 2-231
DBA_UNDO_EXTENTS
DBA_UNDO_EXTENTS
DBA_UNDO_EXTENTS describes the extents comprising the segments in all undo
tablespaces in the database.
Column
Datatype
OWNER
CHAR(3)
NULL
Description
SEGMENT_NAME
VARCHAR2(30)
NOT NULL
Name of the undo segment
TABLESPACE_NAME
VARCHAR2(30)
NOT NULL
Name of the undo tablespace
EXTENT_ID
NUMBER
FILE_ID
NUMBER
BLOCK_ID
NUMBER
Start block number of the extent
BYTES
NUMBER
Size of the extent (in bytes)
BLOCKS
NUMBER
Size of the extent (in blocks)
RELATIVE_FNO
NUMBER
Relative number of the file containing the segment
header
COMMIT_JTIME
NUMBER
Commit time of the undo in the extent expressed as
Julian time
COMMIT_WTIME
VARCHAR2(20)
Commit time of the undo in the extent expressed as
Wallclock time
STATUS
VARCHAR2(9)
Transaction Status of the undo in the extent:
Owner of the undo tablespace
ID of the extent
NOT NULL
File identifier number of the file containing the extent
■
ACTIVE
■
EXPIRED
■
UNEXPIRED
DBA_UNUSED_COL_TABS
DBA_UNUSED_COL_TABS describes all tables in the database containing unused
columns. Its columns are the same as those in "ALL_UNUSED_COL_TABS" on
page 2-145.
DBA_UPDATABLE_COLUMNS
DBA_UPDATABLE_COLUMNS describes all columns in a join view that can be
updated by the database administrator. Its columns are the same as those in "ALL_
UPDATABLE_COLUMNS" on page 2-146.
2-232 Oracle9i Database Reference
DBA_USERS
See Also: Oracle9i Database Concepts for information on updatable
join views
DBA_USERS
DBA_USERS describes all users of the database.
Related View
USER_USERS describes the current user. This view does not display the PASSWORD
or PROFILE columns.
Column
Datatype
NULL
Description
USERNAME
VARCHAR2(30)
NOT NULL
Name of the user
USER_ID
NUMBER
NOT NULL
ID number of the user
PASSWORD
VARCHAR2(30)
ACCOUNT_STATUS
VARCHAR2(32)
Encrypted password
NOT NULL
Account status:
■
OPEN
■
EXPIRED
■
EXPIRED(GRACE)
■
LOCKED(TIMED)
■
LOCKED
■
EXPIRED & LOCKED(TIMED)
■
EXPIRED(GRACE) & LOCKED(TIMED)
■
EXPIRED & LOCKED
■
EXPIRED(GRACE) & LOCKED
LOCK_DATE
DATE
Date the account was locked if account status was
LOCKED
EXPIRY_DATE
DATE
Date of expiration of the account
DEFAULT_TABLESPACE
VARCHAR2(30)
NOT NULL
Default tablespace for data
TEMPORARY_TABLESPACE
VARCHAR2(30)
NOT NULL
Default tablespace for temporary table
CREATED
DATE
NOT NULL
User creation date
PROFILE
VARCHAR2(30)
NOT NULL
User resource profile name
INITIAL_RSRC_
CONSUMER_GROUP
VARCHAR2(30)
Initial resource consumer group for the user
EXTERNAL_NAME
VARCHAR2(4000)
User external name
Static Data Dictionary Views 2-233
DBA_USTATS
See Also: "USER_USERS" on page 2-293
DBA_USTATS
DBA_USTATS describes all user-defined statistics collected on all objects in the
database. Its columns are the same as those in "ALL_USTATS" on page 2-147.
DBA_VARRAYS
DBA_VARRAYS describes all the varrays in the database. Its columns are the same as
those in "ALL_VARRAYS" on page 2-148.
DBA_VIEWS
DBA_VIEWS describes all views in the database. Its columns are the same as those in
ALL_VIEWS.
See Also: "ALL_VIEWS" on page 2-148
DBA_WAITERS
DBA_WAITERS shows all the sessions that are waiting for a lock, but do not hold
locks for which another session is waiting.
Column
Datatype
NULL
Description
WAITING_SESSION
NUMBER
The waiting session
HOLDING_SESSION
NUMBER
The holding session
LOCK_TYPE
VARCHAR2(26)
The lock type
MODE_HELD
VARCHAR2(40)
The mode held
MODE_REQUESTED
VARCHAR2(40)
The mode requested
LOCK_ID1
VARCHAR2(40)
Lock ID 1
LOCK_ID2
VARCHAR2(40)
Lock ID 2
DBA_XML_SCHEMAS
DBA_XML_SCHEMAS describes all registered XML schemas in the database. Its
columns are the same as those in ALL_XML_SCHEMAS.
2-234 Oracle9i Database Reference
DBMS_ALERT_INFO
See Also: "ALL_XML_SCHEMAS" on page 2-149
DBA_XML_TAB_COLS
DBA_XML_TAB_COLS describes the columns of all XML tables in the database. Its
columns are the same as those in ALL_XML_TAB_COLS.
See Also: "ALL_XML_TAB_COLS" on page 2-150
DBA_XML_TABLES
DBA_XML_TABLES describes all XML tables in the database. Its columns are the
same as those in ALL_XML_TABLES.
See Also: "ALL_XML_TABLES" on page 2-151
DBA_XML_VIEW_COLS
DBA_XML_VIEW_COLS describes the columns of all XML views in the database. Its
columns are the same as those in ALL_XML_VIEW_COLS.
See Also: "ALL_XML_VIEW_COLS" on page 2-151
DBA_XML_VIEWS
DBA_XML_VIEWS describes all XML views in the database. Its columns are the same
as those in ALL_XML_VIEWS.
See Also: "ALL_XML_VIEWS" on page 2-152
DBMS_ALERT_INFO
DBMS_ALERT_INFO describes registered alerts.
Column
Datatype
NULL
Description
NAME
VARCHAR2(30)
NOT NULL
Name of the alert
SID
VARCHAR2(30)
NOT NULL
Session ID of a session waiting for this alert
CHANGED
VARCHAR2(1)
Boolean flag to indicate that an alert has been
signaled. Y: alert signaled, N: no alert.
MESSAGE
VARCHAR2(1800)
Optional message passed by signaler
Static Data Dictionary Views 2-235
DBMS_LOCK_ALLOCATED
DBMS_LOCK_ALLOCATED
DBMS_LOCK_ALLOCATED describes user-allocated locks.
Column
Datatype
NULL
Description
NAME
VARCHAR2(128)
NOT NULL
Name of the lock
LOCKID
NUMBER(38)
Lock identifier number
EXPIRATION
DATE
Planned lock expiration date (updates whenever the
allocation procedure is run)
DEPTREE
This view, created by utldtree.sql, contains information on the object
dependency tree. For user SYS, this view displays shared cursors (and only shared
cursors) that depend on the object. For all other users, it displays objects other than
shared cursors. Other users can access SYS.DEPTREE for information on shared
cursors.
Column
Datatype
NESTED_LEVEL
NUMBER
NULL
Description
Nesting level in the dependency tree
TYPE
VARCHAR2(15)
Object type
OWNER
VARCHAR2(30)
Object owner
NAME
VARCHAR2(1002)
Object name
SEQ#
NUMBER
Sequence number in the dependency tree. Used for
ordering queries.
See Also: "IDEPTREE" on page 2-246
DICT
DICT is a synonym for DICTIONARY.
See Also: "DICTIONARY" on page 2-237
DICT_COLUMNS
DICT_COLUMNS contains descriptions of columns in data dictionary tables and
views.
2-236 Oracle9i Database Reference
FILE_LOCK
Column
Datatype
NULL
Description
TABLE_NAME
VARCHAR2(30)
Name of the object that contains the column
COLUMN_NAME
VARCHAR2(30)
Name of the column
COMMENTS
VARCHAR2(4000)
Text comment on the column
DICTIONARY
DICTIONARY contains descriptions of data dictionary tables and views.
Column
Datatype
NULL
Description
TABLE_NAME
VARCHAR2(30)
Name of the object
COMMENTS
VARCHAR2(4000)
Text comment on the object
ERROR_SIZE
ERROR_SIZE is accessed to create "DBA_OBJECT_SIZE" on page 2-200 and "USER_
OBJECT_SIZE" on page 2-279.
EXCEPTIONS
EXCEPTIONS contains information on violations of integrity constraints. This view
is created by the utlexcpt.sql script.
Column
Datatype
NULL
Description
ROW_ID
ROWID
Row that caused the violation
OWNER
VARCHAR2(30)
Owner of the table
TABLE_NAME
VARCHAR2(30)
Name of the table
CONSTRAINT
VARCHAR2(30)
Integrity constraint that was violated
FILE_LOCK
This Oracle Real Application Cluster view displays the mapping of PCM locks to
datafiles as specified in initialization parameter GC_FILES_TO_LOCKS.
See Also: "GC_FILES_TO_LOCKS" on page 1-60 and Oracle9i Real
Application Clusters Concepts
Static Data Dictionary Views 2-237
FILE_PING
Column
Datatype
NULL
Description
FILE_ID
NUMBER
NOT NULL
Datafile identifier number (to find the file name,
query DBA_DATA_FILES or V$DBFILES)
FILE_NAME
VARCHAR2(513)
TS_NAME
VARCHAR2(30)
START_LK
NUMBER
The first lock corresponding to the datafile
NLOCKS
NUMBER
The number of PCM locks allocated to the datafile
BLOCKING
NUMBER
The number of contiguous blocks protected by each
PCM lock on the datafile
The datafile name
NOT NULL
The tablespace name for the datafile
FILE_PING
This Oracle Real Application Cluster view displays the number of blocks pinged
per datafile. You can use this information to determine access usage of existing
datafiles for better settings of GC_FILES_TO_LOCKS.
See Also: "GC_FILES_TO_LOCKS" on page 1-60 and Oracle9i Real
Application Clusters Concepts
Column
Datatype
NULL
Description
FILE_ID
NUMBER
NOT NULL
Datafile identifier number (to find the file name,
query DBA_DATA_FILES or V$DBFILES)
FILE_NAME
NUMBER
TS_NAME
VARCHAR2(30)
FREQUENCY
NUMBER
The ping count
X_2_NULL
NUMBER
Number of lock conversions from Exclusive-to-NULL
for all blocks in the file
The file name
NOT NULL
Datafile identifier number (to find file name, query
DBA_DATA_FILES or V$DBFILES)
X_2_NULL_FORCED_WRITE NUMBER
Number of forced writes that occur for blocks of the
specified file due to Exclusive-to-NULL conversions
X_2_NULL_FORCED_STALE NUMBER
Number of times a block in the file was made STALE
due to Exclusive-to-NULL conversions
X_2_S
NUMBER
Number of lock conversions from Exclusive-to-Shared
for all blocks in the file
X_2_S_FORCED_WRITES
NUMBER
Number of forced writes that occur for blocks of the
specified file due to Exclusive-to-Shared conversions
X_2_SSX
NUMBER
Number of lock conversions from Exclusive-to-Sub
Shared Exclusive for all blocks in the file
2-238 Oracle9i Database Reference
FILEXT$
Column
Datatype
NULL
Description
X_2_SSX_FORCED_WRITES NUMBER
Number of forced writes that occur for blocks of the
specified file due to Exclusive-to-Sub Shared
Exclusive conversions
S_2_NULL
Number of lock conversions from Shared-to-NULL for
all blocks in the file
NUMBER
S_2_NULL_FORCED_STALE NUMBER
Number of times a block in the file was made STALE
due to Shared-to-NULL conversions
SS_2_NULL
NUMBER
Number of lock conversions from Sub
Shared-to-NULL for all blocks in the file
WRB
NUMBER
Number of times the instance received a write single
buffer cross instance call for this file
WRB_FORCED_WRITE
NUMBER
Number of blocks written due to write single buffer
cross instance calls for this file
RBR
NUMBER
Number of times the instance received a reuse block
range cross instance call for this file
RBR_FORCED_WRITE
NUMBER
Number of blocks written due to resuse block range
cross instance calls for this file
RBR_FORCED_STALE
NUMBER
Number of times a block in this file was made STALE
due to resuse block range cross instance calls
CBR
NUMBER
Number of times the instance received a checkpoint
block range cross instance call for this file
CBR_FORCED_WRITE
NUMBER
Number of blocks in this file which were written due
to checkpoint cross range cross instance calls
NULL_2_X
NUMBER
Number of lock conversions from NULL-to-Exclusive
for all blocks of the specified file
S_2_X
NUMBER
Number of lock conversions from Shared-to-Exclusive
for all blocks of the specified file
SSX_2_X
NUMBER
Number of lock conversions from Sub Shared
Exclusive-to-Exclusive for all blocks of the specified
file
N_2_S
NUMBER
Number of lock conversions from NULL-to-Shared for
all blocks of the specified file
N_2_SS
NUMBER
Number of lock conversions from NULL-to-Sub
Shared for all blocks of the specified file
FILEXT$
FILEXT$ is the equivalent of DBA_DATA_FILES. Oracle Corporation recommends
you use DBA_DATA_FILES instead of FILEXT$.
Static Data Dictionary Views 2-239
GLOBAL_NAME
See Also: "DBA_DATA_FILES"
Column
Datatype
NULL
Description
FILE#
NUMBER
NOT NULL
Absolute file number
MAXEXTEND
NUMBER
Maximum file size
INC
NUMBER
Increment amount
GLOBAL_NAME
GLOBAL_NAME contains one row that displays the global name of the current
database.
Column
Datatype
GLOBAL_NAME
VARCHAR2(4000)
NULL
Description
Global name of the database
HS_ALL_CAPS
HS_ALL_CAPS contains information about all of the capabilities (that is, features)
associated with non-Oracle (FDS) data stores.
Column
Datatype
CAP_NUMBER
NUMBER
NULL
Description
Capability number
CONTEXT
NUMBER
Context in which this capability is applicable
TRANSLATION
VARCHAR2(255)
Valid for functions; contains translation to FDS dialect
ADDITIONAL_INFO
NUMBER
Flag for internal use
FDS_CLASS_NAME
VARCHAR2(30)
Name of the FDS Class
FDS_INST_NAME
VARCHAR2(30)
Name of the FDS instance
HS_ALL_DD
HS_ALL_DD contains data dictionary information about non-Oracle (FDS) data
stores.
Column
Datatype
DD_TABLE_NAME
VARCHAR2(30)
2-240 Oracle9i Database Reference
NULL
Description
Data dictionary table name
HS_BASE_DD
Column
Datatype
NULL
Description
TRANSLATION_TYPE
CHAR(1)
T = Translation, M = Mimic
TRANSLATION_TEXT
VARCHAR2(4000)
SQL statement containing the mapping
FDS_CLASS_NAME
VARCHAR2(30)
Name of the FDS Class
FDS_INST_NAME
VARCHAR2(30)
Name of the FDS instance
DD_TABLE_DESC
VARCHAR2(255)
Description of the Oracle data dictionary table
HS_ALL_INITS
HS_ALL_INITS contains initialization parameter information about non-Oracle
(FDS) data stores.
Column
Datatype
INIT_VALUE_NAME
VARCHAR2(64)
NULL
Description
Name of the initialization parameter
INIT_VALUE
VARCHAR2(255)
Value of the initialization parameter
INIT_VALUE_TYPE
VARCHAR2(1)
Environment variable (T or F). T means this is an
environment variable; F means do not set as an
environment variable
FDS_CLASS_NAME
VARCHAR2(30)
Name of the FDS Class
FDS_INST_NAME
VARCHAR2(30)
Name of the FDS instance
HS_BASE_CAPS
HS_BASE_CAPS contains information about base capability (that is, base features)
of the non-Oracle (FDS) data store.
Column
Datatype
NULL
Description
CAP_NUMBER
NUMBER
NOT NULL
Capability number
CAP_DESCRIPTION
VARCHAR2(255)
Description of the capability
HS_BASE_DD
HS_BASE_DD displays information from the base data dictionary translation table.
Static Data Dictionary Views 2-241
HS_CLASS_CAPS
Column
Datatype
NULL
Description
DD_TABLE_ID
NUMBER
NOT NULL
Sequence: a counter that is incremented for every row
inserted (used internally)
DD_TABLE_NAME
VARCHAR2(30)
NOT NULL
Name of the Oracle data dictionary table
DD_TABLE_DESC
VARCHAR2(255)
Description of the Oracle data dictionary table
HS_CLASS_CAPS
HS_CLASS_CAPS contains information about the class-specific (driver) capabilities
belonging to the non-Oracle (FDS) data store.
Column
Datatype
NULL
Description
CAP_NUMBER
NUMBER
NOT NULL
Capability number
CAP_DESCRIPTION
VARCHAR2(255)
Capability description
CONTEXT
NUMBER
Flag indicating the context in which the capability is
enabled
TRANSLATION
VARCHAR2(255)
Valid for functions; contains translation to FDS dialect
ADDITIONAL_INFO
NUMBER
Additional flags for internal use
FDS_CLASS_NAME
VARCHAR2(30)
NOT NULL
Name of the FDS Class
FDS_CLASS_ID
NUMBER
NOT NULL
Sequence: a counter that is incremented for every row
inserted (used internally)
HS_CLASS_DD
HS_CLASS_DD displays information from the non-Oracle data store (FDS)
class-specific data dictionary translations.
Column
Datatype
NULL
Description
DD_TABLE_NAME
VARCHAR2(30)
NOT NULL
Name of the Oracle data dictionary table
DD_TABLE_DESC
VARCHAR2(255)
TRANSLATION_TYPE
CHAR(1)
TRANSLATION_TEXT
VARCHAR2(4000)
FDS_CLASS_ID
NUMBER
NOT NULL
Sequence: a counter that is incremented for every row
inserted (used internally)
FDS_CLASS_NAME
VARCHAR2(30)
NOT NULL
Name of the FDS Class
DD_TABLE_ID
NUMBER
NOT NULL
Sequence: a counter that is incremented for every row
inserted (used internally)
2-242 Oracle9i Database Reference
Description of the Oracle data dictionary table
NOT NULL
T = Translation, M = Mimic
SQL statement containing the mapping
HS_EXTERNAL_OBJECTS
HS_CLASS_INIT
HS_CLASS_INIT displays information about the non-Oracle (FDS) class-specific
initialization parameters.
Column
Datatype
NULL
Description
INIT_VALUE_NAME
VARCHAR2(64)
NOT NULL
Name of the initialization parameter
INIT_VALUE
VARCHAR2(255)
NOT NULL
Value of the initialization parameter
INIT_VALUE_TYPE
VARCHAR2(1)
NOT NULL
Environment variable (T or F). T means this is an
environment variable; F means do not set as an
environment variable
FDS_CLASS_NAME
VARCHAR2(30)
NOT NULL
Name of the FDS Class
FDS_CLASS_INIT_ID
NUMBER
NOT NULL
Sequence: a counter that is incremented for every row
inserted (used internally)
FDS_CLASS_ID
NUMBER
NOT NULL
Sequence: a counter that is incremented for every row
inserted (used internally)
HS_EXTERNAL_OBJECT_PRIVILEGES
HS_EXTERNAL_OBJECT_PRIVILEGES contains information about the privileges
on objects that are granted to users.
Column
Datatype
NULL
Description
OBJECT_NAME
VARCHAR2(30)
NOT NULL
Name of the object; unique for each instance
PRIVILEGE_NAME
VARCHAR2(30)
NOT NULL
Name of the privilege that was granted
GRANTEE
VARCHAR2(30)
NOT NULL
ID of the user that was granted the privilege
FDS_CLASS_NAME
VARCHAR2(30)
NOT NULL
Name of the FDS Class
FDS_INST_NAME
VARCHAR2(30)
NOT NULL
Name of the FDS instance
HS_EXTERNAL_OBJECTS
HS_EXTERNAL_OBJECTS contains information about all of the distributed external
objects accessible from the Oracle server.
Column
Datatype
NULL
Description
FDS_CLASS_NAME
VARCHAR2(30)
NOT NULL
Name of the FDS Class
FDS_INST_NAME
VARCHAR2(30)
NOT NULL
Name of the FDS instance
OWNER
VARCHAR(30)
NOT NULL
Name of the user who created the object
Static Data Dictionary Views 2-243
HS_EXTERNAL_USER_PRIVILEGES
Column
Datatype
NULL
Description
OBJECT_NAME
VARCHAR2(30)
NOT NULL
Name of the object; unique for each instance
OBJECT_TYPE
VARCHAR2(13)
NOT NULL
Type of object: FUNCTION, PROCEDURE, PACKAGE, or
LIBRARY
OBJECT_TEXT
LONG
NOT NULL
SQL text used to create the object
HS_EXTERNAL_USER_PRIVILEGES
HS_EXTERNAL_USER_PRIVILEGES contains information about all of the granted
privileges that are not tied to any particular object.
Column
Datatype
NULL
Description
PRIVILEGE_NAME
VARCHAR2(30)
NOT NULL
Name of the privilege that was granted
GRANTEE
VARCHAR2(30)
NOT NULL
ID of the user that was granted the privilege
FDS_CLASS_NAME
VARCHAR2(30)
NOT NULL
Name of the FDS Class
FDS_INST_NAME
VARCHAR2(30)
NOT NULL
Name of the FDS instance
HS_FDS_CLASS
HS_FDS_CLASS contains information about legal non-Oracle (FDS) classes.
Column
Datatype
NULL
Description
FDS_CLASS_NAME
VARCHAR2(30)
NOT NULL
Name of the FDS class (for example, ODBC, DB2)
FDS_CLASS
_COMMENTS
VARCHAR2(255)
FDS_CLASS_ID
NUMBER
Text description of the non-Oracle class
NOT NULL
Sequence: a counter that is incremented for every row
inserted (used internally)
HS_FDS_INST
HS_FDS_INST contains information about non-Oracle (FDS) instances.
Column
Datatype
NULL
Description
FDS_INST_NAME
VARCHAR2(30)
NOT NULL
Name of the FDS instance
FDS_INST_COMMENTS
VARCHAR2(255)
FDS_CLASS_NAME
VARCHAR2(30)
2-244 Oracle9i Database Reference
Text description of the non-Oracle instance
NOT NULL
Name of the FDS class
HS_INST_DD
Column
Datatype
NULL
Description
FDS_INST_ID
NUMBER
NOT NULL
Sequence: a counter that is incremented for every row
inserted (used internally)
FDS_CLASS_ID
NUMBER
NOT NULL
Sequence: a counter that is incremented for every row
inserted (used internally)
HS_INST_CAPS
HS_INST_CAPS contains information about instance-specific capabilities (that is,
features).
Column
Datatype
NULL
Description
CAP_NUMBER
NUMBER
NOT NULL
Capability number
CAP_DESCRIPTION
VARCHAR2(255)
Capability description
CONTEXT
NUMBER
Context in which this capability is applicable
TRANSLATION
VARCHAR2(255)
Valid for functions; contains translation to FDS dialect
ADDITIONAL_INFO
NUMBER
Additional flags for internal use
FDS_CLASS_NAME
VARCHAR2(30)
NOT NULL
Name of the FDS class (for example, ODBC, DB2)
FDS_INST_NAME
VARCHAR2(30)
NOT NULL
Name of the FDS instance
FDS_CLASS_ID
NUMBER
NOT NULL
Sequence: a counter that is incremented for every row
inserted (used internally)
FDS_INST_ID
NUMBER
NOT NULL
Sequence: a counter that is incremented for every row
inserted (used internally)
HS_INST_DD
HS_INST_DD displays information from the non-Oracle (FDS) instance-specific data
dictionary translations.
Column
Datatype
NULL
Description
DD_TABLE_NAME
VARCHAR2(30)
NOT NULL
Name of the Oracle data dictionary table
DD_TABLE_DESC
VARCHAR2(255)
TRANSLATION_TYPE
CHAR(1)
TRANSLATION_TEXT
VARCHAR2(4000)
FDS_CLASS_NAME
VARCHAR2(30)
NOT NULL
Name of the FDS class (for example, ODBC, DB2)
FDS_INST_NAME
VARCHAR2(30)
NOT NULL
Name of the FDS instance
Description of the Oracle data dictionary table
NOT NULL
T = Translation, M = Mimic
SQL statement containing the mapping
Static Data Dictionary Views 2-245
HS_INST_INIT
Column
Datatype
NULL
Description
DD_TABLE_ID
NUMBER
NOT NULL
Sequence: a counter that is incremented for every row
inserted (used internally)
FDS_CLASS_ID
NUMBER
NOT NULL
Sequence: a counter that is incremented for every row
inserted (used internally)
FDS_INST_ID
NUMBER
NOT NULL
Sequence: a counter that is incremented for every row
inserted (used internally)
HS_INST_INIT
HS_INST_INIT contains information about the non-Oracle (FDS) instance-specific
initialization parameters.
Column
Datatype
NULL
Description
INIT_VALUE_NAME
VARCHAR2(64)
NOT NULL
Name of the initialization parameter
INIT_VALUE
VARCHAR2(255)
NOT NULL
Value of the initialization parameter
INIT_VALUE_TYPE
VARCHAR2(1)
NOT NULL
Environment variable (T or F). T means this is an
environment variable; F means do not set as an
environment variable
FDS_CLASS_NAME
VARCHAR2(30)
NOT NULL
Name of the FDS class (for example: ODBC, DB2)
FDS_INST_NAME
VARCHAR2(30)
NOT NULL
Name of the FDS instance
FDS_INST_INIT_ID
NUMBER
NOT NULL
Sequence: a counter that is incremented for every row
inserted (used internally)
FDS_CLASS_ID
NUMBER
NOT NULL
Sequence: a counter that is incremented for every row
inserted (used internally)
FDS_INST_ID
NUMBER
NOT NULL
Sequence: a counter that is incremented for every row
inserted (used internally)
IDEPTREE
This view, created by UTLDTREE.SQL, lists the indented dependency tree. It is a
pre-sorted, pretty-print version of DEPTREE.
Column
Datatype
NESTED_LEVEL
NUMBER
Nesting level in the dependency tree
TYPE
VARCHAR2(15)
Object type
OWNER
VARCHAR2(30)
Object owner
NAME
VARCHAR2(1002)
Object name
2-246 Oracle9i Database Reference
NULL
Description
INDEX_STATS
IND
IND is a synonym for USER_INDEXES.
See Also: "USER_INDEXES" on page 2-271
INDEX_HISTOGRAM
INDEX_HISTOGRAM contains information from the ANALYZE INDEX ...
VALIDATE STRUCTURE statement.
Column
Datatype
NULL
Description
REPEAT_COUNT
NUMBER
Number of times that one or more index keys is
repeated in the table
KEYS_WITH_REPEAT_
COUNT
NUMBER
Number of index keys that are repeated that many
times
INDEX_STATS
INDEX_STATS stores information from the last ANALYZE INDEX ... VALIDATE
STRUCTURE statement.
Column
Datatype
NULL
Description
HEIGHT
NUMBER
BLOCKS
NUMBER
NOT NULL
Blocks allocated to the segment
NAME
VARCHAR2(30)
NOT NULL
Name of the index
PARTITION_NAME
VARCHAR2(30)
Name of the partition of the index which was
analyzed. If the index is not partitioned, a NULL is
returned.
LF_ROWS
NUMBER
Number of leaf rows (values in the index)
LF_BLKS
NUMBER
Number of leaf blocks in the B-Tree
LF_ROWS_LEN
NUMBER
Sum of the lengths of all the leaf rows
LF_BLK_LEN
NUMBER
Usable space in a leaf block
BR_ROWS
NUMBER
Number of branch rows in the B-Tree
BR_BLKS
NUMBER
Number of branch blocks in the B-Tree
BR_ROWS_LEN
NUMBER
Sum of the lengths of all the branch blocks in the
B-Tree
BR_BLK_LEN
NUMBER
Usable space in a branch block
Height of the B-Tree
Static Data Dictionary Views 2-247
MAP_OBJECT
Column
Datatype
NULL
Description
DEL_LF_ROWS
NUMBER
Number of deleted leaf rows in the index
DEL_LF_ROWS_LEN
NUMBER
Total length of all deleted rows in the index
DISTINCT_KEYS
NUMBER
Number of distinct keys in the index (may include
rows that have been deleted)
MOST_REPEATED_KEY
NUMBER
How many times the most repeated key is repeated
(may include rows that have been deleted)
BTREE_SPACE
NUMBER
Total space currently allocated in the B-Tree
USED_SPACE
NUMBER
Total space that is currently being used in the B-Tree
PCT_USED
NUMBER
Percent of space allocated in the B-Tree that is being
used
ROWS_PER_KEY
NUMBER
Average number of rows per distinct key (this figure
is calculated without consideration of deleted rows)
BLKS_GETS_PER_ACCESS
NUMBER
Expected number of consistent mode block reads per
row, assuming that a randomly chosen row is
accessed using the index. Used to calculate the
number of consistent reads that will occur during an
index scan.
PRE_ROWS
NUMBER
Number of prefix rows (values in the index)
PRE_ROWS_LEN
NUMBER
Sum of lengths of all prefix rows
OPT_CMPR_COUNT
NUMBER
Optimal key compression length
OPT_CMPR_PCTSAVE
NUMBER
Corresponding space savings after an ANALYZE
MAP_OBJECT
MAP_OBJECT displays the hierarchical arrangement of storage containers for
objects. Each row in the table represents a level in the hierarchy.
Column
Datatype
OBJECT_NAME
VARCHAR2(2000)
Name of the object
OBJECT_OWNER
VARCHAR2(2000)
Owner of the object
OBJECT_TYPE
VARCHAR2(2000)
Object type
FILE_MAP_IDX
NUMBER
File index (corresponds to FILE_MAP_IDX in V$MAP_
FILE)
DEPTH
NUMBER
Element depth within the I/O stack
ELEM_IDX
NUMBER
Index corresponding to the element
2-248 Oracle9i Database Reference
NULL
Description
NLS_SESSION_PARAMETERS
Column
Datatype
NULL
Description
CU_SIZE
NUMBER
Contiguous set of logical blocks of the file (in HKB
units) that is resident contiguously on the element
STRIDE
NUMBER
Number of HKB between contiguous units (CU) in
the file that are contiguous on this element. Used in
RAID5 and striped files.
NUM_CU
NUMBER
Number of contiguous units that are adjacent to each
other on this element that are separated by STRIDE
HKB in the file. In RAID5, the number of contiguous
units also include the parity stripes.
ELEM_OFFSET
NUMBER
Element offset (in HKB units)
FILE_OFFSET
NUMBER
Offset (in HKB units) from the start of the file to the
first byte of the contiguous units
DATA_TYPE
VARCHAR2(2000)
Datatype (DATA, PARITY, or DATA AND PARITY)
PARITY_POS
NUMBER
Position of the parity. Only for RAID5. This field is
needed to distinguish the parity from the data part.
PARITY_PERIOD
NUMBER
Parity period. Only for RAID5.
NLS_DATABASE_PARAMETERS
NLS_DATABASE_PARAMETERS lists permanent NLS parameters of the database.
Column
Datatype
NULL
Description
PARAMETER
VARCHAR2(30)
NOT NULL
Parameter name
VALUE
VARCHAR2(40)
Parameter value
NLS_INSTANCE_PARAMETERS
NLS_INSTANCE_PARAMETERS lists NLS parameters of the instance.
Column
Datatype
NULL
Description
PARAMETER
VARCHAR2(30)
Parameter name
VALUE
VARCHAR2(40)
Parameter value
NLS_SESSION_PARAMETERS
NLS_SESSION_PARAMETERS lists NLS parameters of the user session.
Static Data Dictionary Views 2-249
OBJ
Column
Datatype
NULL
Description
PARAMETER
VARCHAR2(30)
Parameter name
VALUE
VARCHAR2(40)
Parameter value
OBJ
OBJ is a synonym for USER_OBJECTS.
See Also: "USER_OBJECTS" on page 2-279
PARSED_PIECES
Oracle accesses this view to create views about object size.
See Also: "DBA_OBJECT_SIZE" on page 2-200 and "USER_
OBJECT_SIZE" on page 2-279
PARSED_SIZE
Oracle accesses this view to create views about object size.
See Also: "DBA_OBJECT_SIZE" on page 2-200 and "USER_
OBJECT_SIZE" on page 2-279
PLAN_TABLE
PLAN_TABLE is the default table for results of the EXPLAIN PLAN statement. It is
created by utlxplan.sql, and it contains one row for each step in the execution
plan.
Column
Datatype
STATEMENT_ID
VARCHAR2(30)
Optional statement identifier specified in the
EXPLAIN PLAN statement
TIMESTAMP
DATE
Date and time that the EXPLAIN PLAN statement was
issued
REMARKS
VARCHAR2(80)
Place for comments that can be added to the steps of
the execution plan
OPERATION
VARCHAR2(30)
Name of the operation performed at this step
2-250 Oracle9i Database Reference
NULL
Description
PLAN_TABLE
Column
Datatype
NULL
Description
OPTIONS
VARCHAR2(255)
Options used for the operation performed at this step;
the string returned by the index cost function
OBJECT_NODE
VARCHAR2(128)
Name of the database link used to reference the object
OBJECT_OWNER
VARCHAR2(30)
Owner of the object
OBJECT_NAME
VARCHAR2(30)
Name of the object
OBJECT_INSTANCE
NUMBER(38)
Numbered position of the object name in the original
SQL statement
OBJECT_TYPE
VARCHAR2(30)
Descriptive modifier that further describes the type of
object
OPTIMIZER
VARCHAR2(255)
The current mode of the optimizer
SEARCH_COLUMNS
NUMBER
Number of index columns with start and stop keys
(that is, the number of columns with matching
predicates)
ID
NUMBER(38)
Identification number for this step in the execution
plan
PARENT_ID
NUMBER(38)
ID of the next step that operates on the results of this
step
POSITION
NUMBER(38)
Order of processing for steps with the same parent ID.
For cost-based optimization, the value in the first row
of the plan is the statement’s execution cost. For
rule-based optimization, the value is null in the first
row.
COST
NUMBER(38)
The cost of the current operation estimated by the
cost-based optimizer (CBO)
CARDINALITY
NUMBER(38)
The number of rows returned by the current
operation (estimated by the CBO)
BYTES
NUMBER(38)
The number of bytes returned by the current
operation
Static Data Dictionary Views 2-251
PLUGGABLE_SET_CHECK
Column
Datatype
OTHER_TAG
VARCHAR2(255)
NULL
Description
OTHER_TAG describes the function of the SQL text in
the OTHER column. Values for OTHER_TAG are:
■
■
■
■
■
■
■
SERIAL - the SQL is the text of a
locally-executed, serial query plan. Currently,
SQL is not loaded in OTHER for this case.
SERIAL_FROM_REMOTE - the SQL text shown in
the OTHER column will be executed at a remote
site.
PARALLEL_COMBINED_WITH_PARENT - the
parent of this operation is a DFO that performs
both operations in the parallel execution plan.
PARALLEL_COMBINED_WITH_CHILD - the child
of this operation is a DFO that performs both
operations in the parallel execution plan.
PARALLEL_TO_SERIAL - the SQL text shown in
the OTHER column is the top-level of the parallel
plan.
PARALLEL_TO_PARALLEL - the SQL text shown
in the OTHER column is executed and output in
parallel.
PARALLEL_FROM_SERIAL - this operation
consumes data from a serial operation and
outputs it in parallel.
PARTITION_START
VARCHAR2(255)
The start partition of a range of accessed partitions
PARTITION_STOP
VARCHAR2(255)
The stop partition of a range of accessed partitions
PARTITION_ID
NUMBER(38)
The step that has computed the pair of values of the
PARTITION_START and PARTITION_STOP columns
OTHER
LONG
Information about parallel execution slaves and
parallel queries
DISTRIBUTION
VARCHAR2(30)
The distribution method
CPU_COST
NUMBER
User-defined CPU cost
IO_COST
NUMBER
User-defined I/O cost
PLUGGABLE_SET_CHECK
PLUGGABLE_SET_CHECK contains pluggable set checks.
Column
Datatype
OBJ1_OWNER
VARCHAR2(30)
Owner of the object
OBJ1_NAME
VARCHAR2(30)
Object 1
2-252 Oracle9i Database Reference
NULL
Description
PROXY_USERS
Column
Datatype
NULL
Description
OBJ1_SUBNAME
VARCHAR2(30)
SubObject1Name
OBJ1_TYPE
VARCHAR2(15)
Object Type
TS1_NAME
VARCHAR2(30)
Tablespace containing Object 1
OBJ2_NAME
VARCHAR2(30)
Object Name
OBJ2_SUBNAME
VARCHAR2(30)
SubObject2Name
OBJ2_TYPE
VARCHAR2(15)
Object Type
OBJ2_OWNER
VARCHAR2(30)
Object owner of second object
TS2_NAME
VARCHAR2(30)
Tablespace containing Object 1
CONSTRAINT_NAME
VARCHAR2(30)
Name of dependent constraint
REASON
VARCHAR2(79)
Reason for Pluggable check violation
MESG_ID
NUMBER
The message ID
PRODUCT_COMPONENT_VERSION
PRODUCT_COMPONENT_VERSION contains version and status information for
component products.
Column
Datatype
PRODUCT
VARCHAR2(64)
NULL
Description
Product name
VERSION
VARCHAR2(64)
Version number
STATUS
VARCHAR2(64)
Status of release
PROXY_USERS
PROXY_USERS describes users who can assume the identity of other users.
Column
Datatype
NULL
Description
PROXY
VARCHAR2(30)
NOT NULL
Name of the client whose identity a proxy may
assume
CLIENT
VARCHAR2(30)
NOT NULL
Name of a user which assume the identity of a client
ROLE
VARCHAR2(30)
Name of a role that a proxy user may or may not
activate while acting as a client
FLAGS
VARCHAR2(35)
Indicates whether or not a proxy can activate all client
roles, no client roles, or a specific client role
Static Data Dictionary Views 2-253
PSTUBTBL
PSTUBTBL
This table contains information on stubs generated by the PSTUB utility so that an
Oracle Forms 3.0 client can call stored procedures in an Oracle database.
Note: The contents of this table are intended only for use by the
PSTUB utility.
Column
Datatype
NULL
Description
USERNAME
VARCHAR2(30)
Schema part of the identifier of a stored procedure
DBNAME
VARCHAR2(128)
Database link part of the identifier of a stored
procedure
LUN
VARCHAR2(30)
Library unit name part of the identifier of a stored
procedure
LUTYPE
VARCHAR2(3)
Type of the stored procedure
LINENO
NUMBER
Line number of the stub
LINE
VARCHAR2(1800)
Text of the stub
PUBLIC_DEPENDENCY
PUBLIC_DEPENDENCY lists dependencies to and from objects, by object number.
Column
Datatype
NULL
Description
OBJECT_ID
NUMBER
NOT NULL
Object number
REFERENCED_OBJECT_ID
NUMBER
NOT NULL
Referenced object (the parent object)
PUBLICSYN
PUBLICSYN contains information on public synonyms.
Column
Datatype
SNAME
VARCHAR2(30)
Name of the synonym
CREATOR
VARCHAR2(30)
Owner of the synonym
TNAME
VARCHAR2(30)
Table of which this is a synonym
DATABASE
VARCHAR2(128)
Database in which the table resides
2-254 Oracle9i Database Reference
NULL
Description
RESOURCE_MAP
Column
Datatype
TABTYPE
VARCHAR2(9)
NULL
Description
Type of table
QUEUE_PRIVILEGES
QUEUE_PRIVILEGES shows all Advanced Queuing object privileges granted to the
session.
Column
Datatype
NULL
Description
GRANTEE
VARCHAR2(30)
NOT NULL
Name of the user to whom access was granted
OWNER
VARCHAR2(30)
NOT NULL
Owner of the object
NAME
VARCHAR2(30)
NOT NULL
Name of the object
GRANTOR
VARCHAR2(30)
NOT NULL
Name of the user who performed the grant
ENQUEUE_PRIVILEGE
NUMBER
Permission to ENQUEUE to the queue
DEQUEUE_PRIVILEGE
NUMBER
Permission to DEQUEUE from the queue
RESOURCE_COST
RESOURCE_COST lists the cost for each resource.
Column
Datatype
NULL
Description
RESOURCE_NAME
VARCHAR2(32)
NOT NULL
Name of the resource
UNIT_COST
NUMBER
NOT NULL
Cost of the resource
RESOURCE_MAP
RESOURCE_MAP describes resources. This table can be used to map resource names
to resource numbers.
Column
Datatype
NULL
Description
RESOURCE#
NUMBER
NOT NULL
Numeric resource code
TYPE#
NUMBER
NOT NULL
Numeric type code
NAME
VARCHAR2(32)
NOT NULL
Name of the resource
Static Data Dictionary Views 2-255
ROLE_ROLE_PRIVS
ROLE_ROLE_PRIVS
ROLE_ROLE_PRIVS describes the roles granted to other roles. Information is
provided only about roles to which the user has access.
Column
Datatype
NULL
Description
ROLE
VARCHAR2(30)
NOT NULL
Name of the role
GRANTED_ROLE
VARCHAR2(30)
NOT NULL
Role that was granted
ADMIN_OPTION
VARCHAR2(3)
Signifies that the role was granted with ADMIN option
ROLE_SYS_PRIVS
ROLE_SYS_PRIVS describes system privileges granted to roles. Information is
provided only about roles to which the user has access.
Column
Datatype
NULL
Description
ROLE
VARCHAR2(30)
NOT NULL
Name of the role
PRIVILEGE
VARCHAR2(40)
NOT NULL
System privilege granted to the role
ADMIN_OPTION
VARCHAR2(3)
Signifies the grant was with the ADMIN option
ROLE_TAB_PRIVS
ROLE_TAB_PRIVS describes table privileges granted to roles. Information is
provided only about roles to which the user has access.
Column
Datatype
NULL
Description
ROLE
VARCHAR2(30)
NOT NULL
Name of the role
OWNER
VARCHAR2(30)
NOT NULL
Owner of the object
TABLE_NAME
VARCHAR2(30)
NOT NULL
Name of the object
COLUMN_NAME
VARCHAR2(30)
PRIVILEGE
VARCHAR2(40)
GRANTABLE
VARCHAR2(3)
Name of the column, if applicable
NOT NULL
Object privilege granted to the role
YES if the role was granted with ADMIN OPTION;
otherwise NO
SEQ
SEQ is a synonym for USER_SEQUENCES.
2-256 Oracle9i Database Reference
SOURCE_SIZE
See Also: "USER_SEQUENCES" on page 2-286
SESSION_CONTEXT
SESSION_CONTEXT lists attributes and the values set for the current session.
See Also: Oracle9i SQL Reference for information on the
predefined attributes of the current session
Column
Datatype
NULL
Description
NAMESPACE
VARCHAR2(30)
NOT NULL
The namespace that the active attribute is in
ATTRIBUTE
VARCHAR2(30)
NOT NULL
The name of the active attribute
VALUE
VARCHAR2(4000)
NOT NULL
The value of the active attribute
SESSION_PRIVS
SESSION_PRIVS lists the privileges that are currently available to the user.
Column
Datatype
NULL
Description
PRIVILEGE
VARCHAR2(40)
NOT NULL
Name of the privilege
SESSION_ROLES
SESSION_ROLES lists the roles that are currently enabled to the user.
Column
Datatype
NULL
Description
ROLE
VARCHAR2(30)
NOT NULL
Name of the role
SOURCE_SIZE
Oracle accesses this view to create views about object size.
See Also: "DBA_OBJECT_SIZE" on page 2-200 and "USER_
OBJECT_SIZE" on page 2-279
Static Data Dictionary Views 2-257
STMT_AUDIT_OPTION_MAP
STMT_AUDIT_OPTION_MAP
STMT_AUDIT_OPTION_MAP describes auditing option type codes. This table can be
used to map auditing option type numbers to type names.
Column
Datatype
NULL
Description
OPTION#
NUMBER
NOT NULL
Numeric auditing option type code
NAME
VARCHAR2(40)
NOT NULL
Name of the type of auditing option
PROPERTY
NUMBER
NOT NULL
Property flag of the auditing option
SYN
SYN is a synonym for USER_SYNONYMS.
SYNONYMS is included for compatibility with Oracle version 5. Oracle Corporation
recommends that you do not use this view.
SYNONYMS
SYSCATALOG
SYSCATALOG is included for compatibility with Oracle version 5. Oracle
Corporation recommends that you do not use this view.
SYSFILES
SYSFILES is included for compatibility with Oracle version 5. Oracle Corporation
recommends that you do not use this view.
SYSSEGOBJ
SYSSEGOBJ is included for compatibility with Oracle version 5. Oracle Corporation
recommends that you do not use this view.
SYSTEM_PRIVILEGE_MAP
SYSTEM_PRIVILEGE_MAP describes privilege type codes. This table can be used to
map privilege type numbers to type names.
Column
Datatype
NULL
Description
PRIVILEGE
NUMBER
NOT NULL
Numeric privilege type code
2-258 Oracle9i Database Reference
TABLE_PRIVILEGES
Column
Datatype
NULL
Description
NAME
PROPERTY
VARCHAR2(40)
NOT NULL
Name of the type of privilege
NUMBER
NOT NULL
Property flag of the privilege
SYS_OBJECTS
SYS_OBJECTS maps object IDs to object types and segment data block addresses.
Column
Datatype
NULL
Description
OBJECT_TYPE
VARCHAR2(15)
Type of the object
OBJECT_TYPE_ID
NUMBER
Type ID of the object
SEGMENT_TYPE_ID
NUMBER
Type of segment: TABLE, CLUSTER, INDEX,
ROLLBACK, DEFERRED ROLLBACK, TEMPORARY,
CACHE
OBJECT_ID
NUMBER
Object identifier
HEADER_FILE
NUMBER
ID of the file containing the segment header
HEADER_BLOCK
NUMBER
ID of the block containing the segment header
TS_NUMBER
NUMBER
The tablespace number
TAB
TAB is included for compatibility with Oracle version 5. Oracle Corporation
recommends that you do not use this view.
TABLE_PRIVILEGE_MAP
TABLE_PRIVILEGE_MAP describes privilege (auditing option) type codes. This
table can be used to map privilege (auditing option) type numbers to type names.
Column
Datatype
NULL
Description
PRIVILEGE
NUMBER
NOT NULL
Numeric privilege (auditing option) type code
NAME
VARCHAR2(40)
NOT NULL
Name of the type of privilege (auditing option)
TABLE_PRIVILEGES
TABLE_PRIVILEGES contains information on grants on objects for which the user
is the grantor, grantee, or owner, or PUBLIC is the grantee. This view is included for
Static Data Dictionary Views 2-259
TABS
compatibility with Oracle version 6. Oracle Corporation recommends that you do
not use this view.
Column
Datatype
NULL
Description
GRANTEE
VARCHAR2(30)
NOT NULL
Name of the user to whom access was granted
OWNER
VARCHAR2(30)
NOT NULL
Owner of the object
TABLE_NAME
VARCHAR2(30)
NOT NULL
Name of the object
GRANTOR
VARCHAR2(30)
NOT NULL
Name of the user who performed the grant
SELECT_PRIV
VARCHAR2(1)
Permission to select from the object
INSERT_PRIV
VARCHAR2(1)
Permission to insert into the object
DELETE_PRIV
VARCHAR2(1)
Permission to delete from the object
UPDATE_PRIV
VARCHAR2(1)
Permission to update the object
REFERENCES_PRIV
VARCHAR2(1)
Permission to reference the object
ALTER_PRIV
VARCHAR2(1)
Permission to alter the object
INDEX_PRIV
VARCHAR2(1)
Permission to create or drop an index on the object
CREATED
VARCHAR2(0)
Timestamp for the grant
TABS
TABS is a synonym for USER_TABLES.
See Also: "USER_TABLES" on page 2-291
TABQUOTAS
TABQUOTAS is included for compatibility with Oracle version 5. Oracle Corporation
recommends that you do not use this view.
TRUSTED_SERVERS
TRUSTED_SERVERS displays whether a server is trusted or untrusted.
Column
Datatype
TRUST
VARCHAR2(9)
2-260 Oracle9i Database Reference
NULL
Description
Trustedness of the server listed. Values can be
TRUSTED or UNTRUSTED servers which are not listed
in the NAME column have opposite trustedness.
TS_PITR_CHECK
Column
Datatype
NAME
VARCHAR2(128)
NULL
Description
Server name. Can be a specific server name or ALL
for all servers.
Table 2–3 shows examples of the values returned depending on the status of the
servers.
Table 2–3 TRUSTED_SERVERS Values
Condition (If . . . )
TRUSTED column
NAME column
... all servers are trusted
Trusted
ALL
... no servers are trusted
Untrusted
ALL
... all servers except DB1 are trusted
Untrusted
DB1
... all servers except DB1 are untrusted
Trusted
DB1
See Also: Oracle9i Heterogeneous Connectivity Administrator’s Guide
TS_PITR_CHECK
This view, created by catpitr.sql provides information on any dependencies or
restrictions that might prevent tablespace point-in-time recovery from proceeding.
This view applies only to the tablespace point-in-time recovery feature.
See Also: Oracle9i User-Managed Backup and Recovery Guide
Column
Datatype
NULL
Description
OBJ1_OWNER
VARCHAR2(30)
NOT NULL
The owner of the object preventing tablespace
point-in-time recovery. See the REASON column for
details.
OBJ1_NAME
VARCHAR2(30)
NOT NULL
The name of the object preventing tablespace
point-in-time recovery
OBJ1_TYPE
VARCHAR2(15)
The object type for the object preventing tablespace
point-in-time recovery
OBJ1_SUBNAME
VARCHAR2(30)
Subordinate to OBJ1_NAME
TS1_NAME
VARCHAR2(30)
NOT NULL
Name of the tablespace containing the object
preventing tablespace point-in-time recovery
Static Data Dictionary Views 2-261
TS_PITR_OBJECTS_TO_BE_DROPPED
Column
Datatype
NULL
Description
OBJ2_NAME
VARCHAR2(30)
The name of a second object which may be preventing
tablespace point-in-time recovery. If NULL, object 1 is
the only object preventing recovery.
OBJ2_TYPE
VARCHAR2(15)
The object type for the second object (will be NULL if
OBJ2_NAME is NULL)
OBJ2_OWNER
VARCHAR2(30)
The owner of the second object (will be NULL if
OBJ2_NAME is NULL)
OBJ2_SUBNAME
VARCHAR2(30)
Subordinate to OBJ2_NAME
TS2_NAME
VARCHAR2(30)
Name of the tablespace containing second object
which may be preventing tablespace point-in-time
recovery (-1 indicates not applicable)
CONSTRAINT_NAME
VARCHAR2(30)
Name of the constraint
REASON
VARCHAR2(78)
Reason why tablespace point-in-time recovery cannot
proceed
TS_PITR_OBJECTS_TO_BE_DROPPED
TS_PITR_OBJECTS_TO_BE_DROPPED lists all objects lost as a result of performing
tablespace point-in-time recovery. This view applies only to the tablespace
point-in-time recovery feature.
Column
Datatype
NULL
Description
OWNER
VARCHAR2(30)
NOT NULL
The owner of the object
NAME
VARCHAR2(30)
NOT NULL
The name of the object that will be lost as a result of
undergoing tablespace point-in-time recovery
CREATION_TIME
DATE
NOT NULL
Creation timestamp of the object
TABLESPACE_NAME
VARCHAR2(30)
Name of the tablespace containing the object
UNI_PLUGGABLE_SET_CHECK
UNI_PLUGGABLE_SET_CHECK contains pluggable check information.
Column
Datatype
OBJ1_OWNER
VARCHAR2(30)
Owner of object
OBJ1_NAME
VARCHAR2(30)
Object 1
OBJ1_SUBNAME
VARCHAR2(30)
SubObject1Name
2-262 Oracle9i Database Reference
NULL
Description
USER_ARGUMENTS
Column
Datatype
NULL
Description
OBJ1_TYPE
VARCHAR2(15)
Object Type
TS1_NAME
VARCHAR2(30)
Tablespace containing Object 1
OBJ2_NAME
VARCHAR2(30)
Object Name
OBJ2_SUBNAME
VARCHAR2(30)
SubObject2Name
OBJ2_TYPE
VARCHAR2(15)
Object Type
OBJ2_OWNER
VARCHAR2(30)
Object owner of second object
TS2_NAME
VARCHAR2(30)
Tablespace containing Object 1
CONSTRAINT_NAME
VARCHAR2(30)
Name of dependent constraint
REASON
VARCHAR2(79)
Reason for Pluggable check violation
MESG_ID
NUMBER
The message ID
USER_ALL_TABLES
USER_ALL_TABLES contains descriptions of the object tables and relational tables
owned by the current user. Its columns are the same as those in "ALL_ALL_
TABLES" on page 2-6.
USER_AQ_AGENT_PRIVS
USER_AQ_AGENT_PRIVS displays information about the registered AQ agents that
are mapped to the current user. Its columns (except for DB_USERNAME) are the same
as those in DBA_AQ_AGENT_PRIVS.
See Also: "DBA_AQ_AGENT_PRIVS" on page 2-160
USER_ARGUMENTS
USER_ARGUMENTS lists the arguments in all procedures and functions that are
owned by the current user. Its columns are the same as those in "ALL_
ARGUMENTS" on page 2-13.
Static Data Dictionary Views 2-263
USER_ASSOCIATIONS
USER_ASSOCIATIONS
USER_ASSOCIATIONS describes user-defined statistics associated with objects
owned by the current user. Its columns are the same as those in "ALL_
ASSOCIATIONS" on page 2-14.
USER_ATTRIBUTE_TRANSFORMATIONS
USER_ATTRIBUTE_TRANSFORMATIONS displays information about the
transformation functions for the transformations owned by the current user. Its
columns (except for OWNER) are the same as those in DBA_ATTRIBUTE_
TRANSFORMATIONS.
See Also: "DBA_ATTRIBUTE_TRANSFORMATIONS" on
page 2-161
USER_AUDIT_OBJECT
This view, created by cataudit.sql, lists audit trail records for statements
concerning objects that are accessible to the current user. Its columns are the same as
those in "DBA_AUDIT_OBJECT" on page 2-163.
USER_AUDIT_POLICIES
USER_AUDIT_POLICIES describes the fine-grained auditing policies on the tables
and views owned by the current user. Its columns (except for OBJECT_SCHEMA) are
the same as those in ALL_AUDIT_POLICIES.
See Also: "ALL_AUDIT_POLICIES" on page 2-15
USER_AUDIT_SESSION
This view, created by cataudit.sql, lists all audit trail records concerning
connections and disconnections for the user. Its columns are the same as those in
"DBA_AUDIT_SESSION" on page 2-164.
USER_AUDIT_STATEMENT
This view, created by cataudit.sql, lists audit trail entries for the following
statements issued by the user: GRANT, REVOKE, AUDIT, NOAUDIT, and ALTER
2-264 Oracle9i Database Reference
USER_BASE_TABLE_MVIEWS
SYSTEM. Its columns are the same as those in "DBA_AUDIT_STATEMENT" on
page 2-165.
USER_AUDIT_TRAIL
This view, created by cataudit.sql, lists audit trail entries relevant to the user. Its
columns are the same as those in "DBA_AUDIT_TRAIL" on page 2-167.
USER_AW_PS
USER_AW_PS describes the pagespaces in the analytic workspaces owned by the
current user. Its columns (except for OWNER) are the same as those in DBA_AW_PS.
See Also:
■
■
"DBA_AW_PS" on page 2-169
Oracle9i OLAP User’s Guide for more information about this
view
USER_AWS
USER_AWS describes the analytic workspaces owned by the current user. Its
columns (except for OWNER) are the same as those in DBA_AWS.
See Also:
■
■
"DBA_AWS" on page 2-169
Oracle9i OLAP User’s Guide for more information about this
view
USER_BASE_TABLE_MVIEWS
USER_BASE_TABLE_MVIEWS describes all materialized views using materialized
view logs owned by the current user. Its columns are the same as those in ALL_
BASE_TABLE_MVIEWS.
See Also: "ALL_BASE_TABLE_MVIEWS" on page 2-16
Static Data Dictionary Views 2-265
USER_CATALOG
USER_CATALOG
USER_CATALOG lists indexes, tables, views, clusters, synonyms, and sequences
owned by the current user. Its columns are the same as those in "ALL_CATALOG"
on page 2-20.
USER_CLU_COLUMNS
USER_CLU_COLUMNS maps columns in the current user’s tables to cluster columns.
Its columns are the same as those in "DBA_CLU_COLUMNS" on page 2-172.
USER_CLUSTER_HASH_EXPRESSIONS
USER_CLUSTER_HASH_EXPRESSIONS lists hash functions for the hash clusters
owned by the current user. Its columns are the same as those in "ALL_CLUSTER_
HASH_EXPRESSIONS" on page 2-20.
USER_CLUSTERS
USER_CLUSTERS describes all the clusters owned by the current user. Its columns
are the same as those in "ALL_CLUSTERS" on page 2-21.
USER_COL_COMMENTS
USER_COL_COMMENTS describes comments on columns of tables and views in the
current user’s schema. Its columns are the same as those in "ALL_COL_
COMMENTS" on page 2-22.
USER_COL_PRIVS
USER_COL_PRIVS describes the column object grants for which the current user is
the object owner, grantor, or grantee. Its columns are the same as those in DBA_
COL_PRIVS.
See Also: "DBA_COL_PRIVS" on page 2-172
2-266 Oracle9i Database Reference
USER_CONS_OBJ_COLUMNS
USER_COL_PRIVS_MADE
USER_COL_PRIVS_MADE describes the column object grants for which the current
user is the object owner. Its columns (except for OWNER) are the same as those in
ALL_COL_PRIVS_MADE.
See Also: "ALL_COL_PRIVS_MADE" on page 2-23
USER_COL_PRIVS_RECD
USER_COL_PRIVS_RECD describes the column object grants for which the current
user is the grantee. Its columns (except for GRANTEE) are the same as those in ALL_
COL_PRIVS_RECD.
See Also: "ALL_COL_PRIVS_RECD" on page 2-24
USER_COLL_TYPES
USER_COLL_TYPES describes named collection types (VARRAYs, nested tables,
object tables, and so on) in the current user’s schema. Its columns are the same as
those in "ALL_COLL_TYPES" on page 2-25.
USER_CONS_COLUMNS
USER_CONS_COLUMNS describes columns that are owned by the current user and
that are specified in constraint definitions. Its columns are the same as those in
"ALL_CONS_COLUMNS" on page 2-25.
USER_CONS_OBJ_COLUMNS
USER_CONS_OBJ_COLUMNS displays information about the types that object
columns (or attributes) or collection elements have been constrained to, in the tables
owned by the current user. Its columns (except for OWNER) are the same as those in
ALL_CONS_OBJ_COLUMNS.
See Also: "ALL_CONS_OBJ_COLUMNS" on page 2-26
Static Data Dictionary Views 2-267
USER_CONSTRAINTS
USER_CONSTRAINTS
USER_CONSTRAINTS describes all constraint definitions on tables owned by the
current user. Its columns are the same as those in "ALL_CONSTRAINTS" on
page 2-27.
USER_DB_LINKS
USER_DB_LINKS describes database links owned by the current user. Its columns
are the same as those in "ALL_DB_LINKS" on page 2-29.
USER_DEPENDENCIES
USER_DEPENDENCIES describes dependencies between procedures, packages,
functions, package bodies, and triggers owned by the current user, including
dependencies on views created without any database links. Its columns are the
same as those in "ALL_DEPENDENCIES" on page 2-30.
USER_DIM_ATTRIBUTES
USER_DIM_ATTRIBUTES describes the relationship between dimension levels and
functionally dependent columns in the current user’s schema. The level columns
and the dependent column must be in the same table. This view’s columns are the
same as those in "ALL_DIM_ATTRIBUTES" on page 2-31.
USER_DIM_CHILD_OF
USER_DIM_CHILD_OF describes a hierarchical relationship of 1 to n between pairs
of levels in dimensions owned by the current user. Its columns are the same as those
in "ALL_DIM_CHILD_OF" on page 2-32.
USER_DIM_HIERARCHIES
USER_DIM_HIERARCHIES describes the dimension hierarchies owned by the
current user. Its columns are the same as those in "ALL_DIM_HIERARCHIES" on
page 2-32.
2-268 Oracle9i Database Reference
USER_EVALUATION_CONTEXT_TABLES
USER_DIM_JOIN_KEY
USER_DIM_JOIN_KEY describes the join between two dimension tables owned by
the current user. The join is always specified between a parent dimension level
column and a child column. This view’s columns are the same as those in "ALL_
DIM_JOIN_KEY" on page 2-33.
USER_DIM_LEVEL_KEY
USER_DIM_LEVEL_KEY describes columns of dimension levels owned by the
current user. This view’s columns are the same as those in "ALL_DIM_LEVEL_
KEY" on page 2-33.
USER_DIM_LEVELS
USER_DIM_LEVELS describes the levels of dimensions owned by the current user.
All columns of a dimension level must come from the same relation. This view’s
columns are the same as those in "ALL_DIM_LEVELS" on page 2-34.
USER_DIMENSIONS
USER_DIMENSIONS describes dimension objects in the user’s schema. Its columns
are the same as those in "ALL_DIMENSIONS" on page 2-34.
USER_ERRORS
USER_ERRORS describes current errors on all stored objects (views, procedures,
functions, packages, and package bodies) owned by the current user. Its columns
are the same as those in "ALL_ERRORS" on page 2-35.
USER_EVALUATION_CONTEXT_TABLES
USER_EVALUATION_CONTEXT_TABLES describes the tables in the rule evaluation
contexts owned by the current user. Its columns (except for EVALUATION_
CONTEXT_OWNER) are the same as those in ALL_EVALUATION_CONTEXT_TABLES.
See Also: "ALL_EVALUATION_CONTEXT_TABLES" on
page 2-36
Static Data Dictionary Views 2-269
USER_EVALUATION_CONTEXT_VARS
USER_EVALUATION_CONTEXT_VARS
USER_EVALUATION_CONTEXT_VARS describes the variables in the rule evaluation
contexts owned by the current user. Its columns (except for EVALUATION_
CONTEXT_OWNER) are the same as those in ALL_EVALUATION_CONTEXT_VARS.
See Also: "ALL_EVALUATION_CONTEXT_VARS" on page 2-36
USER_EVALUATION_CONTEXTS
USER_EVALUATION_CONTEXTS describes the rule evaluation contexts owned by
the current user. Its columns (except for EVALUATION_CONTEXT_OWNER) are the
same as those in ALL_EVALUATION_CONTEXTS.
See Also: "ALL_EVALUATION_CONTEXTS" on page 2-37
USER_EXTENTS
USER_EXTENTS describes the extents comprising the segments owned by the
current user’s objects. Its columns (except for OWNER, FILE_ID, BLOCK_ID, and
RELATIVE_FNO) are the same as those in DBA_EXTENTS.
See Also: "DBA_EXTENTS" on page 2-180
USER_EXTERNAL_LOCATIONS
USER_EXTERNAL_TABLES describes the locations (data sources) of the external
tables owned by the current user. Its columns (except for OWNER) are the same as
those in ALL_EXTERNAL_LOCATIONS.
See Also: "ALL_EXTERNAL_LOCATIONS" on page 2-38
USER_EXTERNAL_TABLES
USER_EXTERNAL_TABLES describes the external tables owned by the current user.
Its columns (except for OWNER) are the same as those in ALL_EXTERNAL_TABLES.
See Also: "ALL_EXTERNAL_TABLES" on page 2-39
2-270 Oracle9i Database Reference
USER_INDEXES
USER_FREE_SPACE
USER_FREE_SPACE describes the free extents in the tablespaces accessible to the
current user. Its columns are the same as those in DBA_FREE_SPACE.
See Also: "DBA_FREE_SPACE" on page 2-182
USER_IND_COLUMNS
USER_IND_COLUMNS describes the columns of the indexes owned by the current
user and columns of indexes on tables owned by the current user. Its columns are
the same as those in "ALL_IND_COLUMNS" on page 2-40.
USER_IND_EXPRESSIONS
USER_IND_EXPRESSIONS describes expressions of function-based indexes on
tables owned by the current user. Its columns are the same as those in "ALL_IND_
EXPRESSIONS" on page 2-41.
USER_IND_PARTITIONS
USER_IND_PARTITIONS describes, for each index partition owned by the current
user, the partition-level partitioning information, the storage parameters for the
partition, and various partition statistics analyzed by ANALYZE statements. Its
columns are the same as those in "ALL_IND_PARTITIONS" on page 2-41.
USER_IND_SUBPARTITIONS
USER_IND_SUBPARTITIONS describes, for each index subpartition owned by the
current user, the partition-level partitioning information, the storage parameters for
the subpartition, and various partition statistics collected by ANALYZE statements.
Its columns are the same as those in "ALL_IND_SUBPARTITIONS" on page 2-43.
USER_INDEXES
USER_INDEXES describes indexes owned by the current user. To gather statistics
for this view, use the SQL ANALYZE statement. This view supports parallel
partitioned index scans. Its columns (except for OWNER) are the same as those in
"ALL_INDEXES" on page 2-45.
Static Data Dictionary Views 2-271
USER_INDEXTYPE_COMMENTS
USER_INDEXTYPE_COMMENTS
USER_INDEXTYPE_COMMENTS lists all comments for user-defined indextypes
owned by the current user. Its columns are the same as those in ALL_INDEXTYPE_
COMMENTS.
See Also: "ALL_INDEXTYPE_COMMENTS" on page 2-48
USER_INDEXTYPE_OPERATORS
USER_INDEXTYPE_OPERATORS lists all the operators supported by indextypes
owned by the current user. Its columns are the same as those in ALL_INDEXTYPE_
OPERATORS.
See Also: "ALL_INDEXTYPE_OPERATORS" on page 2-49
USER_INDEXTYPES
USER_INDEXTYPES describes all indextypes owned by the current user. Its
columns are the same as those in ALL_INDEXTYPES.
See Also: "ALL_INDEXTYPES" on page 2-50
USER_INTERNAL_TRIGGERS
USER_INTERNAL_TRIGGERS describes the internal triggers on all tables owned by
the current user. Its columns are the same as those in "ALL_INTERNAL_
TRIGGERS" on page 2-50.
USER_JAVA_ARGUMENTS
USER_JAVA_ARGUMENTS displays argument information about the stored Java
classes owned by the current user. Its columns (except for OWNER) are the same as
those in ALL_JAVA_ARGUMENTS.
See Also: "ALL_JAVA_ARGUMENTS" on page 2-51
2-272 Oracle9i Database Reference
USER_JAVA_INNERS
USER_JAVA_CLASSES
USER_JAVA_CLASSES displays class level information about the stored Java classes
owned by the current user. Its columns (except for OWNER) are the same as those in
ALL_JAVA_CLASSES.
See Also: "ALL_JAVA_CLASSES" on page 2-52
USER_JAVA_DERIVATIONS
USER_JAVA_DERIVATIONS displays mapping information about Java source
objects and their derived Java class objects and Java resource objects for the Java
classes owned by the current user. Its columns (except for OWNER) are the same as
those in ALL_JAVA_DERIVATIONS.
See Also: "ALL_JAVA_DERIVATIONS" on page 2-53
USER_JAVA_FIELDS
USER_JAVA_FIELDS displays field information about the stored Java classes
owned by the current user. Its columns (except for OWNER) are the same as those in
ALL_JAVA_FIELDS.
See Also: "ALL_JAVA_FIELDS" on page 2-54
USER_JAVA_IMPLEMENTS
USER_JAVA_IMPLEMENTS describes interfaces implemented by the stored Java
classes owned by the current user. Its columns (except for OWNER) are the same as
those in ALL_JAVA_IMPLEMENTS.
See Also: "ALL_JAVA_IMPLEMENTS" on page 2-55
USER_JAVA_INNERS
USER_JAVA_INNERS displays information about inner classes referred to by the
stored Java classes owned by the current user. Its columns (except for OWNER) are
the same as those in ALL_JAVA_INNERS.
See Also: "ALL_JAVA_INNERS" on page 2-56
Static Data Dictionary Views 2-273
USER_JAVA_LAYOUTS
USER_JAVA_LAYOUTS
USER_JAVA_LAYOUTS displays class layout information about the stored Java
classes owned by the current user. Its columns (except for OWNER) are the same as
those in ALL_JAVA_LAYOUTS.
See Also: "ALL_JAVA_LAYOUTS" on page 2-57
USER_JAVA_METHODS
USER_JAVA_METHODS displays method information about the stored Java classes
owned by the current user. Its columns (except for OWNER) are the same as those in
ALL_JAVA_METHODS.
See Also: "ALL_JAVA_METHODS" on page 2-58
USER_JAVA_NCOMPS
USER_JAVA_NCOMPS displays ncomp-related information about the Java classes
owned by the current user. Its columns (except for OWNER) are the same as those in
ALL_JAVA_NCOMPS.
See Also: "ALL_JAVA_NCOMPS" on page 2-59
USER_JAVA_POLICY
USER_JAVA_POLICY describes Java security permissions for the current user. Its
columns are the same as those in DBA_JAVA_POLICY.
See Also: "DBA_JAVA_POLICY" on page 2-186
USER_JAVA_RESOLVERS
USER_JAVA_RESOLVERS displays information about resolvers of the Java classes
owned by the current user. Its columns (except for OWNER) are the same as those in
ALL_JAVA_RESOLVERS.
See Also: "ALL_JAVA_RESOLVERS" on page 2-60
2-274 Oracle9i Database Reference
USER_LOB_SUBPARTITIONS
USER_JAVA_THROWS
USER_JAVA_THROWS displays information about exceptions thrown from methods
of the Java classes owned by the current user. Its columns (except for OWNER) are the
same as those in ALL_JAVA_THROWS.
See Also: "ALL_JAVA_THROWS" on page 2-61
USER_JOBS
USER_JOBS describes all jobs owned by the user. Its columns are the same as those
in "ALL_JOBS" on page 2-61.
See Also: Oracle9i Database Administrator’s Guide for more
information on jobs
USER_JOIN_IND_COLUMNS
USER_JOIN_IND_COLUMNS describes all join conditions owned by the current user.
Its columns are the same as those in "ALL_JOIN_IND_COLUMNS" on page 2-63.
USER_LIBRARIES
USER_LIBRARIES describes all libraries owned by the current user. Its columns are
the same as those in "ALL_LIBRARIES" on page 2-63.
USER_LOB_PARTITIONS
USER_LOB_PARTITIONS displays the LOB partitions contained in tables owned by
the current user. Its columns are the same as those in "ALL_LOB_PARTITIONS" on
page 2-64.
USER_LOB_SUBPARTITIONS
USER_LOB_SUBPARTITIONS describes partition-level attributes of LOB data
subpartitions owned by the current user. Its columns are the same as those in "ALL_
LOB_SUBPARTITIONS" on page 2-65.
■
DBA_LOB_TEMPLATES describes all LOB subpartition templates in the
database.
Static Data Dictionary Views 2-275
USER_LOB_TEMPLATES
USER_LOB_TEMPLATES
USER_LOB_TEMPLATES describes the LOB subpartition templates owned by the
current user. Its columns (except for USER_NAME) are the same as those in ALL_
LOB_TEMPLATES.
See Also: "ALL_LOB_TEMPLATES" on page 2-66
USER_LOBS
USER_LOBS displays the user’s CLOBs and BLOBs contained in the user’s tables.
BFILEs are stored outside the database, so they are not described by this view. This
view’s columns are the same as those in "ALL_LOBS" on page 2-67.
USER_LOG_GROUP_COLUMNS
USER_LOG_GROUP_COLUMNS describes columns that are owned by the current user
and that are specified in log groups. Its columns are the same as those in "ALL_
LOG_GROUP_COLUMNS" on page 2-68.
USER_LOG_GROUPS
USER_LOG_GROUPS describes log group definitions on tables owned by the current
user. Its columns are the same as those in "ALL_LOG_GROUPS" on page 2-69.
USER_METHOD_PARAMS
USER_METHOD_PARAMS describes the method parameters of the object types
owned by the current user. Its columns (except for OWNER) are the same as those in
ALL_METHOD_PARAMS.
See Also: "ALL_METHOD_PARAMS" on page 2-69
USER_METHOD_RESULTS
USER_METHOD_RESULTS describes the method results of the object types owned by
the current user. Its columns (except for OWNER) are the same as those in ALL_
METHOD_RESULTS.
See Also: "ALL_METHOD_RESULTS" on page 2-70
2-276 Oracle9i Database Reference
USER_MVIEW_KEYS
USER_MVIEW_AGGREGATES
USER_MVIEW_AGGREGATES describes the grouping functions (aggregated
measures) that appear in the SELECT list of aggregated materialized views owned
by the current user. Its columns are the same as those in "ALL_MVIEW_
AGGREGATES" on page 2-71.
USER_MVIEW_ANALYSIS
USER_MVIEW_ANALYSIS describes all materialized views owned by the current
user that potentially support query rewrite and that provide additional information
for analysis by applications. Its columns are the same as those in "ALL_MVIEW_
ANALYSIS" on page 2-72.
Note: This view excludes materialized views that reference
remote tables or that include references to non-static values such as
SYSDATE or USER. This view also excludes materialized views that
were created as snapshots prior to Oracle8i and that were never
altered to enable query rewrite.
USER_MVIEW_DETAIL_RELATIONS
USER_MVIEW_DETAIL_RELATIONS represents the named detail relations that are
either in the FROM list of a materialized view, or that are indirectly referenced
through views in the FROM list. Its columns are the same as those in "ALL_MVIEW_
DETAIL_RELATIONS" on page 2-73.
USER_MVIEW_JOINS
USER_MVIEW_JOINS describes a join between two columns in the WHERE clause
of a subquery that defines a materialized view. Its columns are the same as those in
"ALL_MVIEW_JOINS" on page 2-74.
USER_MVIEW_KEYS
USER_MVIEW_KEYS describes the columns or expressions in the SELECT list upon
which materialized views in the current user’s schema are based. Its columns are
the same as those in "ALL_MVIEW_KEYS" on page 2-75.
Static Data Dictionary Views 2-277
USER_MVIEW_LOGS
USER_MVIEW_LOGS
USER_MVIEW_LOGS describes all materialized view logs owned by the current user.
Its columns are the same as those in ALL_MVIEW_LOGS.
See Also: "ALL_MVIEW_LOGS" on page 2-76
USER_MVIEW_REFRESH_TIMES
USER_MVIEW_REFRESH_TIMES describes refresh times of the materialized views
owned by the current user. Its columns are the same as those in ALL_MVIEW_
REFRESH_TIMES.
See Also: "ALL_MVIEW_REFRESH_TIMES" on page 2-77
USER_MVIEWS
USER_MVIEWS describes all materialized views owned by the current user. Its
columns are the same as those in ALL_MVIEWS.
See Also: "ALL_MVIEWS" on page 2-77
USER_NESTED_TABLES
USER_NESTED_TABLES describes the nested tables in tables owned by the current
user. Its columns are the same as those in "ALL_NESTED_TABLES" on page 2-82.
USER_OBJ_AUDIT_OPTS
This view, created by cataudit.sql, lists auditing characteristics for all objects
owned by the current user. Its columns are the same as those in "DBA_OBJ_AUDIT_
OPTS" on page 2-198.
USER_OBJ_COLATTRS
USER_OBJ_COLATTRS describes object columns and attributes contained in the
tables owned by the current user. Its columns (except for OWNER) are the same as
those in ALL_OBJ_COLATTRS.
See Also: "ALL_OBJ_COLATTRS" on page 2-82
2-278 Oracle9i Database Reference
USER_OPERATOR_COMMENTS
USER_OBJECT_SIZE
USER_OBJECT_SIZE lists the sizes, in bytes, of various PL/SQL objects. Its
columns are the same as those in "DBA_OBJECT_SIZE" on page 2-200.
USER_OBJECT_TABLES
USER_OBJECT_TABLES describes the object tables owned by the current user. Its
columns are the same as those in "ALL_OBJECT_TABLES" on page 2-83.
USER_OBJECTS
USER_OBJECTS describes all objects owned by the current user. Its columns are the
same as those in "ALL_OBJECTS" on page 2-85.
USER_OPANCILLARY
USER_OPANCILLARY provides ancillary information for operators owned by the
current user. Its columns are the same as those in "ALL_OPANCILLARY" on
page 2-86.
USER_OPARGUMENTS
USER_OPARGUMENTS provides argument information for operator bindings owned
by the current user. Its columns are the same as those in "ALL_OPARGUMENTS"
on page 2-87.
USER_OPBINDINGS
USER_OPBINDINGS describes bindings of operators owned by the current user. Its
columns are the same as those in "ALL_OPBINDINGS" on page 2-87.
USER_OPERATOR_COMMENTS
USER_OPERATOR_COMMENTS lists all comments for user-defined operators owned
by the current user. Its columns are the same as those in ALL_INDEXTYPE_
COMMENTS.
See Also: "ALL_OPERATOR_COMMENTS" on page 2-88
Static Data Dictionary Views 2-279
USER_OPERATORS
USER_OPERATORS
USER_OPERATORS describes all operators owned by the current user. Its columns
are the same as those in ALL_OPERATORS.
See Also: "ALL_OPERATORS" on page 2-89
USER_OUTLINE_HINTS
USER_OUTLINE_HINTS describes the set of hints that make up the outlines owned
by the current user. Its columns are the same as those in "ALL_OUTLINE_HINTS"
on page 2-89.
USER_OUTLINES
USER_OUTLINES describes all outlines owned by the current user. Its columns are
the same as those in "ALL_OUTLINES" on page 2-90.
USER_PART_COL_STATISTICS
USER_PART_COL_STATISTICS provides column statistics and histogram
information for table partitions owned by the current user. Its columns are the same
as those in "ALL_PART_COL_STATISTICS" on page 2-91.
USER_PART_HISTOGRAMS
USER_PART_HISTOGRAMS contains the histogram data (end-points per histogram)
for histograms on table partitions that the current user can access. Its columns are
the same as those in "ALL_PART_HISTOGRAMS" on page 2-92.
USER_PART_INDEXES
USER_PART_INDEXES describes the object-level partitioning information for the
partitioned indexes owned by the current user. Its columns (except for OWNER) are
the same as those in ALL_PART_INDEXES.
See Also: "ALL_PART_INDEXES" on page 2-92
2-280 Oracle9i Database Reference
USER_PASSWORD_LIMITS
USER_PART_KEY_COLUMNS
USER_PART_KEY_COLUMNS describes the partitioning key columns for the
partitioned objects owned by the current user. Its columns (except for OWNER) are
the same as those in ALL_PART_KEY_COLUMNS.
See Also: "ALL_PART_KEY_COLUMNS" on page 2-94
USER_PART_LOBS
USER_PART_LOBS provides table-level information for partitioned LOBs owned by
the current user, including default attributes for LOB data partitions. Its columns
are the same as those in "ALL_PART_LOBS" on page 2-95.
USER_PART_TABLES
USER_PART_TABLES describes the object-level partitioning information for the
partitioned tables owned by the current user. Its columns (except for OWNER) are the
same as those in ALL_PART_TABLES.
See Also: "ALL_PART_TABLES" on page 2-96
USER_PARTIAL_DROP_TABS
USER_PARTIAL_DROP_TABS describes all tables in the schema of the current user
that have partially completed DROP COLUMN operations. Its columns are the same
as those in "ALL_PARTIAL_DROP_TABS" on page 2-98.
USER_PASSWORD_LIMITS
USER_PASSWORD_LIMITS describes the password profile parameters that are
assigned to the user.
Column
Datatype
NULL
Description
RESOURCE_NAME
VARCHAR2(32)
NOT NULL
Name of the password resource
LIMIT
VARCHAR2(40)
Value of the resource limit
Static Data Dictionary Views 2-281
USER_PENDING_CONV_TABLES
USER_PENDING_CONV_TABLES
USER_PENDING_CONV_TABLES describes the pending conversion tables owned by
the current user. Its columns (except for OWNER) are the same as those in ALL_
PENDING_CONV_TABLES.
See Also: "ALL_PENDING_CONV_TABLES" on page 2-98
USER_POLICIES
USER_POLICIES describes the security policies on the synonyms, tables, and views
owned by the current user. Its columns (except for OBJECT_OWNER) are the same as
those in ALL_POLICIES.
See Also: "ALL_POLICIES" on page 2-99
USER_POLICY_CONTEXTS
USER_POLICY_CONTEXTS describes the driving contexts defined for the
synonyms, tables, and views owned by the current user. Its columns (except for
OBJECT_OWNER) are the same as those in ALL_POLICY_CONTEXTS.
See Also: "ALL_POLICY_CONTEXTS" on page 2-100
USER_POLICY_GROUPS
USER_POLICY_GROUPS describes the policy groups defined for the synonyms,
tables, and views owned by the current user. Its columns (except for OBJECT_
OWNER) are the same as those in ALL_POLICY_GROUPS.
See Also: "ALL_POLICY_GROUPS" on page 2-101
USER_PROCEDURES
USER_PROCEDURES lists all functions and procedures, along with their associated
properties. Its columns (except OWNER) are the same as those in "ALL_
PROCEDURES" on page 2-101.
2-282 Oracle9i Database Reference
USER_QUEUE_TABLES
USER_PROXIES
USER_PROXIES displays information about connections the current user is allowed
to proxy. Its columns are the same as those in DBA_PROXIES.
See Also: "DBA_PROXIES" on page 2-205
USER_PUBLISHED_COLUMNS
USER_PUBLISHED_COLUMNS describes all existing source table columns for which
the user has privileges.
Column
Datatype
Description
SOURCE_SCHEMA_NAME
VARCHAR2(30)
Table owner in the source system
SOURCE_TABLE_NAME
VARCHAR2(31)
Table name in the source system
COLUMN_NAME
VARCHAR2(30)
Column name
DATA_TYPE
VARCHAR2(30)
Column datatype
DATA_LENGTH
NUMBER
Column length in bytes
DATA_PRECISION
NUMBER
Decimal precision for NUMBER datatype; binary precision for FLOAT
datatype; NULL for all other datatypes
DATA_SCALE
NUMBER
Digits to the right of a decimal point in a number
NULLABLE
CHAR(1)
Nulls allowed (Y |N)?
USER_QUEUE_SCHEDULES
USER_QUEUE_SCHEDULES lists information about queue schedules. Its columns are
the same as those in "DBA_QUEUE_SCHEDULES" on page 2-207.
USER_QUEUE_TABLES
USER_QUEUE_TABLES describes the queues in the queue tables created in the
current user’s schema. Its columns (except for OWNER) are the same as those in ALL_
QUEUE_TABLES.
See Also: "ALL_QUEUE_TABLES" on page 2-103
Static Data Dictionary Views 2-283
USER_QUEUES
USER_QUEUES
USER_QUEUES describes the operational characteristics of every queue in the user’s
schema. Its columns are the same as those in "ALL_QUEUES" on page 2-105.
See Also: Oracle9i Application Developer’s Guide - Advanced
Queuing for more information about these views and Advanced
Queuing
USER_REFRESH
USER_REFRESH describes all refresh groups owned by the current user. Its columns
are the same as those in "ALL_REFRESH" on page 2-105.
USER_REFRESH_CHILDREN
USER_REFRESH_CHILDREN lists all the objects in refresh groups owned by the
current user. Its columns are the same as those in "ALL_REFRESH_CHILDREN" on
page 2-106.
USER_REFS
USER_REFS describes the REF columns and REF attributes in the object type
columns of tables owned by the current user. Its columns are the same as those in
"ALL_REFS" on page 2-108.
USER_REGISTERED_MVIEWS
USER_REGISTERED_MVIEWS describes all registered materialized views (registered
at a master site or a master materialized view site) owned by the current user. Its
columns are the same as those in ALL_REGISTERED_MVIEWS.
See Also: "ALL_REGISTERED_MVIEWS" on page 2-108
USER_REGISTRY
USER_REGISTRY displays information about the components loaded into the
database that are owned by the current user. Its columns are the same as those in
DBA_REGISTRY.
2-284 Oracle9i Database Reference
USER_RSRC_CONSUMER_GROUP_PRIVS
See Also: "DBA_REGISTRY" on page 2-210
USER_RESOURCE_LIMITS
USER_RESOURCE_LIMITS displays the resource limits for the current user.
Column
Datatype
NULL
Description
RESOURCE_NAME
VARCHAR2(32)
NOT NULL
Name of the resource
LIMIT
VARCHAR2(40)
Limit placed on this resource
USER_RESUMABLE
USER_RESUMABLE lists resumable statements executed by the current user. Its
columns are the same as those in DBA_RESUMABLE.
See Also: "DBA_RESUMABLE" on page 2-213
USER_ROLE_PRIVS
USER_ROLE_PRIVS describes the roles granted to the current user.
Column
Datatype
USERNAME
VARCHAR2(30)
NULL
Description
Name of the user, or PUBLIC
GRANTED_ROLE
VARCHAR2(30)
Name of the role granted to the user
ADMIN_OPTION
VARCHAR2(3)
Indicates whether the grant was with the ADMIN
OPTION (YES) or not (NO)
DEFAULT_ROLE
VARCHAR2(3)
Indicates whether the role is designated as a DEFAULT
ROLE for the user (YES) or not (NO)
OS_GRANTED
VARCHAR2(3)
Granted by the operating system (YES) or not (NO);
occurs if configuration parameter OS_ROLES = true.
USER_RSRC_CONSUMER_GROUP_PRIVS
USER_RSRC_CONSUMER_GROUP_PRIVS lists all resource consumer groups granted
to the user. Its columns are the same as those in DBA_RSRC_CONSUMER_GROUP_
PRIVS.
See Also: "DBA_RSRC_CONSUMER_GROUP_PRIVS" on
page 2-216
Static Data Dictionary Views 2-285
USER_RSRC_MANAGER_SYSTEM_PRIVS
USER_RSRC_MANAGER_SYSTEM_PRIVS
USER_RSRC_MANAGER_SYSTEM_PRIVS lists all the users who are granted system
privileges for the DBMS_RESOURCE_MANAGER package. Its columns are the same as
those in "DBA_RSRC_MANAGER_SYSTEM_PRIVS" on page 2-217.
USER_RULE_SET_RULES
USER_RULE_SET_RULES describes the rules in the rule sets owned by the current
user. Its columns (except for RULE_SET_OWNER) are the same as those in ALL_
RULE_SET_RULES.
See Also: "ALL_RULE_SET_RULES" on page 2-110
USER_RULE_SETS
USER_RULE_SETS describes the rule sets owned by the current user. Its columns
(except for RULE_SET_OWNER) are the same as those in ALL_RULE_SETS.
See Also: "ALL_RULE_SETS" on page 2-110
USER_RULES
USER_RULES describes the rules owned by the current user. Its columns (except for
RULE_OWNER) are the same as those in ALL_RULES.
See Also: "ALL_RULES" on page 2-111
USER_SEGMENTS
USER_SEGMENTS describes the storage allocated for the segments owned by the
current user’s objects. Its columns (except for OWNER, HEADER_FILE, HEADER_
BLOCK, and RELATIVE_FNO) are the same as those in DBA_SEGMENTS.
See Also: "DBA_SEGMENTS" on page 2-220
USER_SEQUENCES
USER_SEQUENCES describes all sequences owned by the current user. Its columns
are the same as those in "ALL_SEQUENCES" on page 2-112.
2-286 Oracle9i Database Reference
USER_STORED_SETTINGS
USER_SOURCE
USER_SOURCE describes the text source of the stored objects owned by the current
user. Its columns (except for OWNER) are the same as those in "ALL_SOURCE" on
page 2-112.
USER_SOURCE_TABLES
USER_SOURCE_TABLES enables you to see all of the existing source tables to which
you have subscribe privileges. Its columns are the same as those in ALL_SOURCE_
TABLES.
See Also: "ALL_SOURCE_TABLES" on page 2-113
USER_SQLJ_TYPE_ATTRS
USER_SQLJ_TYPE_ATTRS describes the attributes of the SQLJ object types owned
by the current user. Its columns (except for OWNER) are the same as those in ALL_
SQLJ_TYPE_ATTRS.
See Also: "ALL_SQLJ_TYPE_ATTRS" on page 2-113
USER_SQLJ_TYPE_METHODS
USER_SQLJ_TYPE_METHODS describes the methods of the SQLJ object types
owned by the current user. Its columns (except for OWNER) are the same as those in
ALL_SQLJ_TYPE_METHODS.
See Also: "ALL_SQLJ_TYPE_METHODS" on page 2-114
USER_SQLJ_TYPES
USER_SQLJ_TYPES describes the SQLJ object types owned by the current user. Its
columns (except for OWNER) are the same as those in ALL_SQLJ_TYPES.
See Also: "ALL_SQLJ_TYPES" on page 2-115
USER_STORED_SETTINGS
USER_STORED_SETTINGS lists information about the persistent parameter settings
for stored PL/SQL units, but only shows information about PL/SQL units owned
Static Data Dictionary Views 2-287
USER_SUBPART_COL_STATISTICS
by the current user. USER_STORED_SETTINGS does not display the OWNER column.
The rest of its columns are the same as those in "ALL_STORED_SETTINGS" on
page 2-116.
USER_SUBPART_COL_STATISTICS
USER_SUBPART_COL_STATISTICS provides column statistics and histogram
information for subpartitions of subpartitioned objects owned by the current user.
Its columns are the same as those in "ALL_STORED_SETTINGS" on page 2-116.
USER_SUBPART_HISTOGRAMS
USER_SUBPART_HISTOGRAMS lists actual histogram data (end-points per
histogram) for histograms on table subpartitions owned by the current user. Its
columns are the same as those in "ALL_SUBPART_HISTOGRAMS" on page 2-122.
USER_SUBPART_KEY_COLUMNS
USER_SUBPART_KEY_COLUMNS lists subpartitioning key columns for
composite-partitioned tables (and local indexes on composite-partitioned tables)
owned by the current user. Its columns are the same as those in ALL_SUBPART_
KEY_COLUMNS.
See Also: "ALL_SUBPART_KEY_COLUMNS" on page 2-123
USER_SUBPARTITION_TEMPLATES
USER_SUBPARTITION_TEMPLATES describes the subpartition templates owned by
the current user. Its columns (except for USER_NAME) are the same as those in ALL_
SUBPARTITION_TEMPLATES.
See Also: "ALL_SUBPARTITION_TEMPLATES" on page 2-124
USER_SUBSCRIBED_COLUMNS
USER_SUBSCRIBED_COLUMNS enables publishers to view the columns of
published tables to which they have subscribed. Its columns are the same as those
in "ALL_SUBSCRIBED_COLUMNS" on page 2-124.
2-288 Oracle9i Database Reference
USER_TAB_COMMENTS
USER_SUBSCRIBED_TABLES
USER_SUBSCRIBED_TABLES enables subscribers to view all published tables to
which they have subscribed. Its columns are the same as those in "ALL_
SUBSCRIBED_TABLES" on page 2-125.
USER_SUBSCRIPTIONS
USER_SUBSCRIPTIONS enables subscribers to view all of their subscriptions. Its
columns are the same as those in "ALL_SUBSCRIPTIONS" on page 2-125.
USER_SYNONYMS
USER_SYNONYMS describes private synonyms (synonyms owned by the current
user). Its columns are the same as those in "ALL_SYNONYMS" on page 2-126.
USER_SYS_PRIVS
USER_SYS_PRIVS lists system privileges granted to the current user. Its columns
are the same as those in "DBA_SYS_PRIVS" on page 2-225.
USER_TAB_COL_STATISTICS
USER_TAB_COL_STATISTICS contains column statistics and histogram
information extracted from "USER_TAB_COLUMNS" on page 2-289. Its columns
are the same as those in "ALL_TAB_COL_STATISTICS" on page 2-127.
USER_TAB_COLUMNS
USER_TAB_COLUMNS describes the columns of tables, views, and clusters owned by
the current user. Its columns are the same as those in "ALL_TAB_COLUMNS" on
page 2-128. To gather statistics for this view, use the SQL ANALYZE statement.
USER_TAB_COMMENTS
USER_TAB_COMMENTS describes comments on the tables and views owned by the
current user. Its columns are the same as those in "ALL_TAB_COMMENTS" on
page 2-130.
Static Data Dictionary Views 2-289
USER_TAB_HISTOGRAMS
USER_TAB_HISTOGRAMS
USER_TAB_HISTOGRAMS describes histograms on columns of tables owned by the
current user. Its columns are the same as those in "ALL_TAB_HISTOGRAMS" on
page 2-130.
USER_TAB_MODIFICATIONS
USER_TAB_MODIFICATIONS describes modifications to all tables owned by the
current user that have been modified since the last time statistics were gathered on
the tables. Its columns are the same as those in "ALL_TAB_MODIFICATIONS" on
page 2-131.
Note: This view is populated only for tables with the
MONITORING attribute. It is intended for statistics collection over a
long period of time and may not be populated until a few hours
after the actual modifications occurred.
USER_TAB_PARTITIONS
USER_TAB_PARTITIONS describes partition-level partitioning information,
partition storage parameters, and partition statistics determined by ANALYZE
statements for all partitions owned by the current user. Its columns are the same as
those in "ALL_TAB_PARTITIONS" on page 2-132.
USER_TAB_PRIVS
USER_TAB_PRIVS describes the object grants for which the current user is the
object owner, grantor, or grantee. Its columns are the same as those in DBA_TAB_
PRIVS.
See Also: "DBA_TAB_PRIVS" on page 2-227
USER_TAB_PRIVS_MADE
USER_TAB_PRIVS_MADE describes the object grants for which the current user is
the object owner. Its columns (except for OWNER) are the same as those in ALL_TAB_
PRIVS_MADE.
See Also: "ALL_TAB_PRIVS_MADE" on page 2-134
2-290 Oracle9i Database Reference
USER_TRANSFORMATIONS
USER_TAB_PRIVS_RECD
USER_TAB_PRIVS_RECD describes the object grants for which the current user is
the grantee. Its columns (except for GRANTEE) are the same as those in ALL_TAB_
PRIVS_RECD.
See Also: "ALL_TAB_PRIVS_RECD" on page 2-135
USER_TAB_SUBPARTITIONS
USER_TAB_SUBPARTITIONS describes, for each table subpartition, the
subpartition name, name of the table and partition to which it belongs, and its
storage attributes. Its columns are the same as those in "ALL_TAB_
SUBPARTITIONS" on page 2-136.
Note: Statistics are not collected on a per-subpartition basis.
USER_TABLES
USER_TABLES describes all relational tables owned by the current user. Its columns
are the same as those in ALL_TABLES. To gather statistics for this view, use the SQL
ANALYZE statement.
See Also: "ALL_TABLES" on page 2-137
USER_TABLESPACES
USER_TABLESPACES describes the tablespaces accessible to the current user. Its
columns (except for PLUGGED_IN) are the same as those in DBA_TABLESPACES.
See Also: "DBA_TABLESPACES" on page 2-228
USER_TRANSFORMATIONS
USER_TRANSFORMATIONS displays information about the transformations owned
by the current user. Its columns (except for OWNER) are the same as those in DBA_
TRANSFORMATIONS.
See Also: "DBA_TRANSFORMATIONS" on page 2-230
Static Data Dictionary Views 2-291
USER_TRIGGER_COLS
USER_TRIGGER_COLS
USER_TRIGGER_COLS describes the use of columns in triggers owned by the
current user and triggers on tables owned by the current user. Its columns are the
same as those in "ALL_TRIGGER_COLS" on page 2-140.
USER_TRIGGERS
USER_TRIGGERS describes all triggers owned by the current. Its columns are the
same as those in "ALL_TRIGGERS" on page 2-141.
USER_TS_QUOTAS
USER_TS_QUOTAS contains information about tablespace quotas for the current
user. Its columns are the same as those in "DBA_TS_QUOTAS" on page 2-230.
USER_TYPE_ATTRS
USER_TYPE_ATTRS describes the attributes of the object types owned by the
current user. Its columns (except for OWNER) are the same as those in ALL_TYPE_
ATTRS.
See Also: "ALL_TYPE_ATTRS" on page 2-142
USER_TYPE_METHODS
USER_TYPE_METHODS describes the methods of the object types owned by the
current user. Its columns (except for OWNER) are the same as those in ALL_TYPE_
METHODS.
See Also: "ALL_TYPE_METHODS" on page 2-143
USER_TYPE_VERSIONS
USER_TYPE_VERSIONS describes the versions of the object types owned by the
current user. Its columns (except for OWNER) are the same as those in ALL_TYPE_
VERSIONS.
See Also: "ALL_TYPE_VERSIONS" on page 2-144
2-292 Oracle9i Database Reference
USER_VARRAYS
USER_TYPES
USER_TYPES describes the object types owned by the current user. Its columns
(except for OWNER) are the same as those in ALL_TYPES.
See Also: "ALL_TYPES" on page 2-144
USER_UNUSED_COL_TABS
USER_UNUSED_COL_TABS contains a description of all tables containing unused
columns. Its columns are the same as those in "ALL_UNUSED_COL_TABS" on
page 2-145.
USER_UPDATABLE_COLUMNS
USER_UPDATABLE_COLUMNS describes columns in a join view that can be updated
by the current user. Its columns are the same as those in "ALL_UPDATABLE_
COLUMNS" on page 2-146.
See Also: Oracle9i Database Concepts for information on updatable
join views
USER_USERS
USER_USERS describes the current user. Its columns (except for PASSWORD and
PROFILE) are the same as those in DBA_USERS.
See Also: "DBA_USERS" on page 2-233
USER_USTATS
USER_USTATS describes all user-defined statistics owned by the current user. Its
columns are the same as those in "ALL_USTATS" on page 2-147.
USER_VARRAYS
USER_VARRAYS describes the varrays owned by the current user. Its columns are
the same as those in "ALL_VARRAYS" on page 2-148.
Static Data Dictionary Views 2-293
USER_VIEWS
USER_VIEWS
USER_VIEWS describes the views owned by the current user. Its columns (except
for OWNER) are the same as those in ALL_VIEWS.
See Also: "ALL_VIEWS" on page 2-148
USER_XML_SCHEMAS
USER_XML_SCHEMAS describes the registered XML schemas owned by the current
user. Its columns (except for OWNER) are the same as those in ALL_XML_SCHEMAS.
See Also: "ALL_XML_SCHEMAS" on page 2-149
USER_XML_TAB_COLS
USER_XML_TAB_COLS describes the columns of the XML tables owned by the
current user. Its columns (except for OWNER) are the same as those in ALL_XML_
TAB_COLS.
See Also: "ALL_XML_TAB_COLS" on page 2-150
USER_XML_TABLES
USER_XML_TABLES describes the XML tables owned by the current user. Its
columns (except for OWNER) are the same as those in ALL_XML_TABLES.
See Also: "ALL_XML_TABLES" on page 2-151
USER_XML_VIEW_COLS
USER_XML_VIEW_COLS describes the columns of the XML views owned by the
current user. Its columns (except for OWNER) are the same as those in ALL_XML_
VIEW_COLS.
See Also: "ALL_XML_VIEW_COLS" on page 2-151
USER_XML_VIEWS
USER_XML_VIEWS describes the XML views owned by the current user. Its columns
(except for OWNER) are the same as those in ALL_XML_VIEWS.
2-294 Oracle9i Database Reference
USER_XML_VIEWS
See Also: "ALL_XML_VIEWS" on page 2-152
Static Data Dictionary Views 2-295
USER_XML_VIEWS
2-296 Oracle9i Database Reference
3
Dynamic Performance (V$) Views
This chapter describes the dynamic performance views, which are often referred to
as V$ views.
About Dynamic Performance Views
Oracle contains a set of underlying views that are maintained by the server and
accessible to the database administrator user SYS. These views are called dynamic
performance views because they are continuously updated while a database is
open and in use, and their contents relate primarily to performance.
Although these views appear to be regular database tables, they are not. These
views provide data on internal disk structures and memory structures. You can
select from these views, but you can never update or alter them.
Note:
■
■
You can query the dynamic performance views to extract
information from them. However, only simple queries are
supported. If sorts, joins, GROUP BY clauses and the like are
needed, then you should copy the information from each V$
view into a table (for example, using a CREATE TABLE ...
AS SELECT statement), and then query from those tables.
Because the information in the V$ views is dynamic, read
consistency is not guaranteed for SELECT operations on these
views.
Dynamic Performance (V$) Views 3-1
The catalog.sql script contains definitions of the views and public synonyms for
the dynamic performance views. You must run catalog.sql to create these views
and synonyms. After installation, only username SYS or anyone with SYSDBA role
has access to the dynamic performance tables.
V$ Views
The actual dynamic performance views are identified by the prefix V_$. Public
synonyms for these views have the prefix V$. Database administrators and other
users should access only the V$ objects, not the V_$ objects.
The dynamic performance views are used by Enterprise Manager and Oracle Trace,
which is the primary interface for accessing information about system performance.
After an instance is started, the V$ views that read from memory are accessible.
Views that read data from disk require that the database be mounted, and some
require that the database be open.
A number of dynamic performance views are relevant only if you are using Oracle
Replication. Descriptions of the following Oracle Replication dynamic performance
views can be found in the Oracle9i Replication Management API Reference.
■
V$MVREFRESH
■
V$REPLPROP
■
V$REPLQUEUE
GV$ Views
For almost every V$ view described in this chapter, Oracle has a corresponding GV$
(global V$) view. In Oracle9i Real Application Clusters, querying a GV$ view
retrieves the V$ view information from all qualified instances. In addition to the V$
information, each GV$ view contains an extra column named INST_ID of datatype
NUMBER. The INST_ID column displays the instance number from which the
associated V$ view information was obtained. The INST_ID column can be used as
a filter to retrieve V$ information from a subset of available instances. For example,
the following query retrieves the information from the V$LOCK view on instances 2
and 5:
SELECT * FROM GV$LOCK WHERE INST_ID = 2 OR INST_ID = 5;
3-2 Oracle9i Database Reference
In order to query the GV$ views, the value of the PARALLEL_MAX_SERVERS
initialization parameter must be greater than zero on all instances mounting the
database.
See Also: Oracle9i Real Application Clusters Concepts
The following sections list the columns and public synonyms for the dynamic
performance views.
Dynamic Performance (V$) Views 3-3
V$ACCESS
V$ACCESS
This view displays objects in the database that are currently locked and the sessions
that are accessing them.
Column
Datatype
Description
SID
NUMBER
Session number that is accessing an object
OWNER
VARCHAR2(64)
Owner of the object
OBJECT
VARCHAR2(1000)
Name of the object
TYPE
VARCHAR2(24)
Type identifier for the object
V$ACTIVE_INSTANCES
This view maps instance names to instance numbers for all instances that have the
database currently mounted.
Column
Datatype
Description
INST_NUMBER
NUMBER
The instance number
INST_NAME
VARCHAR2(60)
The instance name
V$ACTIVE_SESS_POOL_MTH
This view displays all available active session pool resource allocation methods.
Column
Datatype
Description
NAME
VARCHAR2(40)
Name of the active session pool resource allocation method
V$AQ
This view describes statistics for the queues in the database.
Column
Datatype
Description
QID
NUMBER
The unique queue identifier
WAITING
NUMBER
Number of messages in the queue in the state ’WAITING’
READY
NUMBER
Number of messages in the queue in the state ’READY’
EXPIRED
NUMBER
Number of messages in the queue the state ’EXPIRED’
TOTAL_WAIT
NUMBER
Total wait time of all ’READY’ messages in the queue
3-4 Oracle9i Database Reference
V$ARCHIVE_DEST
Column
Datatype
Description
AVERAGE_WAIT
NUMBER
Average wait time of ’READY’ messages in the queue
V$ARCHIVE
This view contains information on redo log files in need of archiving. Each row
provides information for one thread. This information is also available in V$LOG.
Oracle recommends that you use V$LOG.
See Also: "V$LOG" on page 3-80
Column
Datatype
Description
GROUP#
NUMBER
Log file group number
THREAD#
NUMBER
Log file thread number
SEQUENCE#
NUMBER
Log file sequence number
ISCURRENT
VARCHAR2(3)
This is the current online redo log
CURRENT
VARCHAR2(3)
This column is obsolete and maintained only for compatibility reasons.
The value of this column is always equal to the value in ISCURRENT.
FIRST_CHANGE#
NUMBER
First SCN stored in the current log
V$ARCHIVE_DEST
V$ARCHIVE_DEST describes, for the current instance, all the archived redo log
destinations, their current value, mode, and status.
Column
Datatype
Description
DEST_ID
NUMBER
Identifies the log archive destination parameter (1 to 10)
DEST_NAME
VARCHAR2(256)
???
Dynamic Performance (V$) Views 3-5
V$ARCHIVE_DEST
Column
Datatype
Description
STATUS
VARCHAR2(9)
Identifies the current status of the destination:
BINDING
VARCHAR2(9)
■
VALID - Initialized and available
■
INACTIVE - No destination information
■
DEFERRED - Manually disabled by the user
■
ERROR - Error during open or copy
■
DISABLED - Disabled after error
■
BAD PARAM - Parameter has errors
■
ALTERNATE - Destination is in an alternate state
■
FULL - Exceeded quota size for the destination
Specifies how failure will affect the archival operation:
■
■
NAME_SPACE
TARGET
ARCHIVER
VARCHAR2(7)
VARCHAR2(7)
VARCHAR2(10)
MANDATORY - Successful archival is required
OPTIONAL - Successful archival is not required (depends on LOG_
ARCHIVE_MIN_SUCCEED_DEST)
Identifies the scope of parameter setting:
■
SYSTEM - System definition
■
SESSION - Session definition
Specifies whether the archive destination is local or remote to the
primary database:
■
PRIMARY - local
■
STANDBY - remote
Identifies the archiver process relative to the database where the query
is issued:
■
ARCn
■
FOREGROUND
■
LGWR
■
RFS
SCHEDULE
VARCHAR2(8)
Indicates whether the archival of this destination is INACTIVE,
PENDING, ACTIVE, or LATENT
DESTINATION
VARCHAR2(256)
Specifies the location where the archived redo logs are to be archived
LOG_SEQUENCE
NUMBER
Identifies the sequence number of the last archived redo log to be
archived
REOPEN_SECS
NUMBER
Identifies the retry time (in seconds) after error
DELAY_MINS
NUMBER
Identifies the delay interval (in minutes) before the archived redo log is
automatically applied to a standby database
NET_TIMEOUT
NUMBER
Number of seconds the log writer process will wait for status from the
network server of a network operation issued by the log writer process
3-6 Oracle9i Database Reference
V$ARCHIVE_DEST
Column
Datatype
Description
PROCESS
VARCHAR2(10)
Identifies the archiver process relative to the primary database, even if
the query is issued on the standby database:
REGISTER
VARCHAR2(3)
■
ARCn
■
FOREGROUND
■
LGWR
Indicates whether the archived redo log is registered in the remote
destination control file. If the archived redo log is registered, it is
available to the managed recovery operation:
■
YES
■
NO
FAIL_DATE
DATE
Date and time of last error
FAIL_SEQUENCE
NUMBER
Sequence number of the archived redo log being archived when the last
error occurred
FAIL_BLOCK
NUMBER
Block number of the archived redo log being archived when the last
error occurred
FAILURE_COUNT
NUMBER
Current number of contiguous archival operation failures that have
occurred for the destination
MAX_FAILURE
NUMBER
Allows you to control the number of times log transport services will
attempt to re-establish communication and resume archival operations
with a failed destination
ERROR
VARCHAR2(256)
Displays the error text
ALTERNATE
VARCHAR2(256)
Alternate destination, if any
DEPENDENCY
VARCHAR2(256)
Dependent archive destination, if any
REMOTE_TEMPLATE
VARCHAR2(256)
Specifies the template to be used to derive the location to be recorded
QUOTA_SIZE
NUMBER
Destination quotas, expressed in bytes
QUOTA_USED
NUMBER
Size of all the archived redo logs currently residing on the specified
destination
MOUNTID
NUMBER
Instance mount identifier
TRANSMIT_MODE
VARCHAR2(12)
Specifies network transmission mode:
■
SYNC=PARALLEL
■
SYNC=NOPARALLEL
■
ASYNC
ASYNC_BLOCKS
NUMBER
Number of blocks specified for the ASYNC attribute
AFFIRM
VARCHAR2(3)
Specifies disk I/O mode
Dynamic Performance (V$) Views 3-7
V$ARCHIVE_DEST_STATUS
Column
Datatype
Description
TYPE
VARCHAR2(7)
Indicates whether the archived log destination definition is PUBLIC or
PRIVATE. Only PUBLIC destinations can be modified at runtime using
the ALTER SYSTEM SET or ALTER SESSION SET statements. By
default, all archived log destinations are PUBLIC.
See Also:
■
■
"LOG_ARCHIVE_DEST" on page 1-75 and "LOG_ARCHIVE_
DEST_n" on page 1-76
"LOG_ARCHIVE_DUPLEX_DEST" on page 1-79 and "LOG_
ARCHIVE_DEST_STATE_n" on page 1-78
■
"STANDBY_ARCHIVE_DEST" on page 1-157
■
"LOG_ARCHIVE_MIN_SUCCEED_DEST" on page 1-82
V$ARCHIVE_DEST_STATUS
V$ARCHIVE_DEST_STATUS displays runtime and configuration information for the
archived redo log destinations.
Column
Datatype
Description
DEST_ID
NUMBER
Identifies the log archive destination parameter (1 to 10)
DEST_NAME
VARCHAR2(256)
???
STATUS
VARCHAR2(9)
Identifies the current status of the destination:
TYPE
VARCHAR2(14)
3-8 Oracle9i Database Reference
■
VALID - Initialized and available
■
INACTIVE - No destination information
■
DEFERRED - Manually disabled by the user
■
ERROR - Error during open or copy
■
DISABLED - Disabled after error
■
BAD PARAM - Parameter has errors
■
ALTERNATE - Destination is in an alternate state
■
FULL - Exceeded quota size for the destination
Identifies the type of archival destination database:
■
LOCAL - Local to primary database
■
PHYSICAL - Physical standby
■
CROSS-INSTANCE - An instance of the primary
V$ARCHIVE_DEST_STATUS
Column
Datatype
Description
DATABASE_MODE
VARCHAR2(15)
Identifies the current mode of the archival destination database:
RECOVERY_MODE
PROTECTION_MODE
DESTINATION
VARCHAR2(7)
VARCHAR2(20)
VARCHAR2(256)
■
STARTED - Instance started, not mounted
■
MOUNTED - Mounted
■
MOUNTED-STANDBY - Mounted standby
■
OPEN - Open read/write
■
OPEN_READ-ONLY - Open read-only
Identifies the current mode of media recovery at the archival
destination database
■
IDLE - Managed recovery is not active
■
MANUAL - Manual media recovery active
■
MANAGED - Managed recovery is active
Indicates whether the database is protected:
■
MAXIMUM PROTECTION
■
MAXIMUM AVAILABILITY
■
RESYNCHRONIZATION
■
MAXIMUM PERFORMANCE
■
UNPROTECTED
Specifies the location where the archived redo logs are to be archived
STANDBY_LOGFILE_COUNT NUMBER
Indicates the total number of standby redo logs created on the standby
database
STANDBY_LOGFILE_
ACTIVE
NUMBER
Indicates the total number of standby redo logs on the standby database
that are active and contain primary database online redo log
information
ARCHIVED_THREAD#
NUMBER
Identifies the thread number of the most recent archived redo log
received at the destination
ARCHIVED_SEQ#
NUMBER
Identifies the log sequence number of the most recent archived redo log
received at the destination
APPLIED_THREAD#
NUMBER
Identifies the thread number of the most recent applied redo log
received at the destination
APPLIED_SEQ#
NUMBER
Identifies the log sequence number of the most recent applied redo log
received at the destination
ERROR
VARCHAR2(256)
Displays the error text
SRL
VARCHAR2(3)
Indicates the use of standby redo logfiles on the standby database (YES)
or (NO)
Dynamic Performance (V$) Views 3-9
V$ARCHIVE_GAP
V$ARCHIVE_GAP
V$ARCHIVE_GAP displays information about archive gaps on a standby database.
This view can be used to find out the current archive gap that is blocking recovery.
Column
Datatype
Description
THREAD#
NUMBER
Thread number
LOW_SEQUENCE#
NUMBER
Low number of the log file
HIGH_SEQUENCE#
NUMBER
High number of the log file
V$ARCHIVE_PROCESSES
This view provides information about the state of the various ARCH processes for
the instance.
Column
Datatype
Description
PROCESS
NUMBER
The identifier for the ARCH process for the instance, numbered from
0-9
STATUS
VARCHAR2(10)
The status of the ARCH process, displayed as a keyword. Possible
values are: STOPPED, SCHEDULED, STARTING, ACTIVE, STOPPING,
and TERMINATED.
LOG_SEQUENCE
NUMBER
This is the online redo log sequence number currently being archived, if
STATE="BUSY"
STATE
VARCHAR2(4)
This is the current state of the ARCH process, displayed as a keyword.
Possible keywords are IDLE or BUSY.
V$ARCHIVED_LOG
This view 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
3-10
Oracle9i Database Reference
V$ARCHIVED_LOG
Column
Datatype
Description
NAME
VARCHAR2(513)
Archived log file name. If set to NULL, the log file was cleared before it
was archived.
DEST_ID
NUMBER
Original destination from which the archivelog 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# of the database when this log was written
RESETLOGS_TIME
DATE
Resetlogs time of the database when this log was written
FIRST_CHANGE#
NUMBER
First change# 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
this 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:
REGISTRAR
VARCHAR2(7)
■
ARCH - ARCH process
■
FGRD - Foreground process
■
RMAN
■
SRMN - RMAN at standby
■
LGWR - LGWR process
Registrar of the entry:
■
RFS
■
ARCH - ARCH process
■
FGRD - Foreground process
■
RMAN
■
SRMN - RMAN at standby
■
LGWR - LGWR process
STANDBY_DEST
VARCHAR2(3)
(YES|NO) Indicates if the entry is an archivelog destination
ARCHIVED
VARCHAR2(3)
Indicates that the online redo log was archived (YES) or that RMAN
only inspected the log and created a record for future application of
redo logs during recovery.
See Also: Oracle9i Recovery Manager User’s Guide.
Dynamic Performance (V$) Views 3-11
V$BACKUP
Column
Datatype
Description
APPLIED
VARCHAR2(3)
(YES|NO) Indicates whether or not the archivelog has been applied to
its corresponding standby database. YES indicates it has been applied;
NO indicates it has not. 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)
Specifies (YES | NO) 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.
STATUS
VARCHAR2(1)
The status of this archived log. Possible values are:
A - Available
D - Deleted
U - Unavailable
X - Expired
COMPLETION_TIME
DATE
Time when the archiving completed
DICTIONARY_BEGIN
VARCHAR2(3)
(YES|NO) Indicates whether or not this log contains the start of a
LogMiner dictionary. This column also appears in the RC_ARCHIVED_
LOG view.
DICTIONARY_END
VARCHAR2(3)
(YES|NO) Indicates whether or not this log contains the end of a
LogMiner dictionary. This column also appears in the RC_ARCHIVED_
LOG view.
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
V$BACKUP
This view displays the backup status of all online datafiles.
3-12
Oracle9i Database Reference
V$BACKUP_ASYNC_IO
Column
Datatype
Description
FILE#
NUMBER
File identifier
STATUS
VARCHAR2(18)
File status: NOT ACTIVE, ACTIVE (backup in progress), OFFLINE
NORMAL, or description of an error
CHANGE#
NUMBER
System change number when backup started
TIME
DATE
Time the backup started
V$BACKUP_ASYNC_IO
This view displays performance information about ongoing and recently completed
RMAN backups and restores. For each backup, it contains one row for each input
datafile, one row for the aggregate total performance of all datafiles, and one row
for the output backup piece. This data is not stored persistently, and is not
preserved when the instance is re-started.
See Also: Oracle9i Database Performance Tuning Guide and Reference
for information on how to use this table to tune backup
performance
Column
Datatype
Description
SID
NUMBER
The Oracle SID of the session doing the backup or restore
SERIAL
NUMBER
The use count for the SID doing the backup or restore
USE_COUNT
NUMBER
A counter that can be used to identify rows from different backup sets
DEVICE_TYPE
VARCHAR2(17)
The device type where the file is located
TYPE
VARCHAR2(9)
INPUT, OUTPUT, or AGGREGATE
STATUS
VARCHAR2(11)
NOT STARTED, IN PROGRESS, or FINISHED
FILENAME
VARCHAR2(513)
The name of the backup file being read or written
SET_COUNT
NUMBER
The set count of the backup set being read or written
SET_STAMP
NUMBER
The set stamp of the backup set being read or written
BUFFER_SIZE
NUMBER
The size of the buffers being used to read/write this file, in bytes
BUFFER_COUNT
NUMBER
The number of buffers being used to read/write this file
TOTAL_BYTES
NUMBER
The total number of bytes that will be read or written for this file, if
known. If not known, this column will be null
OPEN_TIME
DATE
The time this file was opened. If TYPE=’AGGREGATE’, then this is the
time that the first file in the aggregate was opened
Dynamic Performance (V$) Views 3-13
V$BACKUP_CORRUPTION
Column
Datatype
Description
CLOSE_TIME
DATE
The time this file was closed. If TYPE=’AGGREGATE’, then this is the
time that the last file in the aggregate was closed
ELAPSED_TIME
NUMBER
The time, in 100ths of seconds, that the file was open
MAXOPENFILES
NUMBER
The number of concurrently open DISK files. This value is only present
in rows where TYPE=’AGGREGATE’.
BYTES
NUMBER
The number of bytes read or written so far
EFFECTIVE_BYTES_PER_
SECOND
NUMBER
The I/O rate that was achieved with this device during this backup
IO_COUNT
NUMBER
The number of I/Os that were performed to this file
READY
NUMBER
The number of asynchronous requests for which a buffer was
immediately ready for use
SHORT_WAITS
NUMBER
The number of times that a buffer was not immediately available, but a
buffer became available after doing a non-blocking poll for I/O
completion
SHORT_WAIT_TIME_TOTAL NUMBER
The total time, in 100ths of seconds, taken by non-blocking polls for I/O
completion
SHORT_WAIT_TIME_MAX
NUMBER
The maximum time taken for a non-blocking poll for I/O completion,
in 100ths of seconds
LONG_WAITS
NUMBER
The number of times that a buffer was not immediately available, and
only became available after a blocking wait was issued
LONG_WAIT_TIME_TOTAL
NUMBER
The total time, in 100ths of seconds, taken by blocking waits for I/O
completion
LONG_WAIT_TIME_MAX
NUMBER
The maximum time taken for a blocking wait for I/O completion, in
100ths of seconds
V$BACKUP_CORRUPTION
V$BACKUP_CORRUPTION displays information about corrupt block ranges in
datafile backups from the control file. Note that corruptions are not tolerated in the
control file and archived redo log backups.
Column
Datatype
Description
RECID
NUMBER
Backup corruption record ID
STAMP
NUMBER
Backup corruption record stamp
SET_STAMP
NUMBER
Backup set stamp
SET_COUNT
NUMBER
Backup set count
PIECE#
NUMBER
backup piece that contains this corrupt block
3-14
Oracle9i Database Reference
V$BACKUP_DATAFILE
Column
Datatype
Description
FILE#
NUMBER
Absolute file number of the datafile that contains the corrupt blocks
BLOCK#
NUMBER
Block number of the first corrupt block in the range of corrupted blocks
BLOCKS
NUMBER
Number of corrupted blocks found starting with BLOCK#
CORRUPTION_CHANGE#
NUMBER
Change number at which the logical corruption was detected. Set to 0 to
indicate media corruption.
MARKED_CORRUPT
VARCHAR2(3)
Indicates whether this corruption was not previously detected by
Oracle (YES) or Oracle had already discovered this corrupt block and
marked it as corrupt in the database (NO). Note that when a corrupt
block is encountered in a backup, and was not already marked corrupt
by Oracle, then the backup process does not mark the block as corrupt
in the production datafile. Thus, this field may be YES for the same
block in more than one backup set.
CORRUPTION_TYPE
VARCHAR2(9)
Type of block corruption in the datafile:
■
■
■
■
■
ALL ZERO - Block header on disk contained only zeros. The block
may be valid if it was never filled and if it is in an Oracle7 file. The
buffer will be reformatted to the Oracle8 standard for an empty
block.
FRACTURED - Block header looks reasonable, but the front and
back of the block are different versions.
CHECKSUM - optional check value shows that the block is not
self-consistent. It is impossible to determine exactly why the check
value fails, but it probably fails because sectors in the middle of
the block are from different versions.
CORRUPT - Block is wrongly identified or is not a data block (for
example, the data block address is missing)
LOGICAL - Specifies the range is for logically corrupt blocks.
CORRUPTION_CHANGE# will have a nonzero value.
V$BACKUP_DATAFILE
This view displays backup datafile and backup control file information from the
control file.
Column
Datatype
Description
RECID
NUMBER
Backup datafile record ID
STAMP
NUMBER
Backup datafile record stamp
SET_STAMP
NUMBER
Backup set stamp
SET_COUNT
NUMBER
Backup set count
FILE#
NUMBER
Datafile number; set to 0 for control file
CREATION_CHANGE#
NUMBER
Creation change of the datafile
Dynamic Performance (V$) Views 3-15
V$BACKUP_DEVICE
Column
Datatype
Description
CREATION_TIME
DATE
Creation timestamp of the datafile
RESETLOGS_CHANGE#
NUMBER
Resetlogs change# of the datafile when it was backed up
RESETLOGS_TIME
DATE
Resetlogs timestamp of the datafile when it was backed up
INCREMENTAL_LEVEL
NUMBER
(0-4) incremental backup level
INCREMENTAL_CHANGE#
NUMBER
All blocks changed after incremental change# is included in this
backup; set to 0 for a full backup
CHECKPOINT_CHANGE#
NUMBER
All changes up to checkpoint change# are included in this backup
CHECKPOINT_TIME
DATE
Timestamp of the checkpoint
ABSOLUTE_FUZZY_
CHANGE#
NUMBER
Highest change# in this backup
MARKED_CORRUPT
NUMBER
Number of blocks marked corrupt
MEDIA_CORRUPT
NUMBER
Number of blocks media corrupt
LOGICALLY_CORRUPT
NUMBER
Number of blocks logically corrupt
DATAFILE_BLOCKS
NUMBER
Size of the datafile in blocks at backup time. This value is also the
number of blocks taken by the datafile restarted from this backup.
BLOCKS
NUMBER
Size of the backup datafile in blocks. Unused blocks are not copied to
the backup.
BLOCK_SIZE
NUMBER
Block size
OLDEST_OFFLINE_RANGE
NUMBER
The RECID of the oldest offline range record in this backup control file.
0 for datafile backups.
COMPLETION_TIME
DATE
The time completed
CONTROLFILE_TYPE
VARCHAR2(1)
B indicates normal copies
S indicates standby copies
V$BACKUP_DEVICE
This view displays information about supported backup devices. If a device type
does not support named devices, then one row with the device type and a null
device name is returned for that device type. If a device type supports named
devices then 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
Datatype
Description
DEVICE_TYPE
VARCHAR2(17)
Type of the backup device
DEVICE_NAME
VARCHAR2(512)
Name of the backup device
3-16
Oracle9i Database Reference
V$BACKUP_PIECE
V$BACKUP_PIECE
This view displays information about backup pieces from the control file. Each
backup set consist of one or more backup pieces.
Column
Datatype
Description
RECID
NUMBER
Backup piece record ID
STAMP
NUMBER
Backup piece record stamp
SET_STAMP
NUMBER
Backup set stamp
SET_COUNT
NUMBER
Backup set count
PIECE#
NUMBER
Backup piece number (1-N)
COPY#
NUMBER
Indicates the copy number for backup pieces created with duplex
enabled. 1 if the backup piece is not duplexed.
DEVICE_TYPE
VARCHAR2(17)
Type of the device on which the backup piece resides. Set to DISK for
backup sets on disk.
See Also: V$BACKUP_DEVICE
HANDLE
VARCHAR2(513)
Backup piece handle identifies the backup piece on restore
COMMENTS
VARCHAR2(81)
Comment returned by the operating system or storage subsystem. Set
to NULL for backup pieces on disk. This value is informational only;
not needed for restore.
MEDIA
VARCHAR2(65)
Name of the media on which the backup piece resides. This value is
informational only; not needed for restore.
MEDIA_POOL
NUMBER
The media pool in which the copy resides. This is the same value that
was entered in the POOL operand of the Recovery Manager backup
command.
CONCUR
VARCHAR2(3)
(YES | NO) Indicates whether the piece on a media that can be accessed
concurrently
TAG
VARCHAR2(32)
Backup piece tag. The tag is specified at backup set level, but stored at
piece level.
STATUS
VARCHAR2(1)
Indicates the status of the piece: A (available), D (deleted), or X
(expired)
START_TIME
DATE
The starting time
COMPLETION_TIME
DATE
The completion time
ELAPSED_SECONDS
NUMBER
The number of elapsed seconds
DELETED
VARCHAR2(3)
(YES/NO) NO indicates that the file still exists. YES indicates the file no
longer exists because it has been deleted.
Dynamic Performance (V$) Views 3-17
V$BACKUP_REDOLOG
V$BACKUP_REDOLOG
This view displays information about archived logs in backup sets from the control
file. Note that online redo logs cannot be backed up directly; they must be archived
first to disk and then backed up. An archive log backup set can contain one or more
archived logs.
Column
Datatype
Description
RECID
NUMBER
Record ID for this row; it is an integer that identifies this row
STAMP
NUMBER
Timestamp used with RECID to uniquely identify this row
SET_STAMP
NUMBER
One of the foreign keys for the row of the V$BACKUP_SET table that
identifies this backup set
SET_COUNT
NUMBER
One of the foreign keys for the row of the V$BACKUP_SET table that
identifies this backup set
THREAD#
NUMBER
Thread number for the log
SEQUENCE#
NUMBER
Log sequence number
RESETLOGS_CHANGE#
NUMBER
Change number of the last resetlogs before the log was written
RESETLOGS_TIME
DATE
Change time of the last resetlogs before the log was written. These will
be the same for all logs in a backup set.
FIRST_CHANGE#
NUMBER
SCN when the log was switched into. The redo in the log is at this SCN
and greater.
FIRST_TIME
DATE
Time allocated when the log was switched into
NEXT_CHANGE#
NUMBER
SCN when the next log in this thread was switched into. The redo in the
log is below this SCN.
NEXT_TIME
DATE
Time when the next log in this thread was switched into
BLOCKS
NUMBER
Size of the log in logical blocks including the header block
BLOCK_SIZE
NUMBER
Size of the log blocks in bytes
V$BACKUP_SET
V$BACKUP_SET displays backup set information from the control file. A backup set
record is inserted after the backup set is successfully completed.
Column
Datatype
Description
RECID
NUMBER
Backup set record ID
STAMP
NUMBER
Backup set record stamp
3-18
Oracle9i Database Reference
V$BACKUP_SET
Column
Datatype
Description
SET_STAMP
NUMBER
Backup set stamp. The backup set stamp and count uniquely identify
the backup set.
Primary key for the V$BACKUP_SET table, and the foreign key for the
following tables: V$BACKUP_PIECE, V$BACKUP_DATAFILE,
V$BACKUP_REDOLOG, V$BACKUP_CORRUPTION.
SET_COUNT
NUMBER
Backup set count. The backup set count is incremented by one every
time a new backup set is started (if the backup set is never completed
the number is "lost"). If the control file is re-created then the count is
reset to 1. Therefore the count must be used with the stamp to uniquely
identify a backup set.
Primary key for the V$BACKUP_SET table, and the foreign key for the
following tables: V$BACKUP_PIECE, V$BACKUP_DATAFILE,
V$BACKUP_REDOLOG, V$BACKUP_CORRUPTION
BACKUP_TYPE
VARCHAR2(1)
Type of files that are in this backup. If the backup contains archived
redo logs, the value is L. If this is a datafile full backup, the value is D. If
this is an incremental backup, the value is I.
CONTROLFILE_INCLUDED
VARCHAR2(3)
Set to YES if there is a control file included in this backup set, otherwise
set to NO
INCREMENTAL_LEVEL
NUMBER
Location where this backup set fits into the database’s backup strategy.
Set to zero for full datafile backups, nonzero for incremental datafile
backups, and NULL for archivelog backups.
PIECES
NUMBER
Number of distinct backup pieces in the backup set
START_TIME
DATE
The starting time
COMPLETION_TIME
DATE
The time that this backup set completed
ELAPSED_SECONDS
NUMBER
The number of elapsed seconds
BLOCK_SIZE
NUMBER
Block size of the backup set
INPUT_FILE_SCAN_ONLY
VARCHAR2(3)
YES indicates no actual backup is performed, but the datafiles are read.
NO indicates a normal backup is performed.
KEEP
VARCHAR2(3)
(YES/NO) Indicates whether or not this backup set has a retention
policy that is different than the value for the configure retention policy
KEEP_UNTIL
DATE
If KEEP_UNTIL_TIME is specified, this is the date after which the
backup becomes obsolete. If this column is null, then the backup never
expires.
KEEP_OPTIONS
VARCHAR2(10)
Lists additional retention options for this backup set. Possible values
are:
LOGS - The logs need to recover this backup are kept
NOLOGS - The logs needed to recover this backup will not be kept
Dynamic Performance (V$) Views 3-19
V$BACKUP_SPFILE
V$BACKUP_SPFILE
V$BACKUP_SPFILE displays information about server parameter files in backup
sets.
Column
Datatype
Description
RECID
NUMBER
Backup SPFILE record ID
STAMP
NUMBER
Backup SPFILE record stamp
SET_STAMP
NUMBER
Backup set stamp (of the set which contains this SPFILE backup)
SET_COUNT
NUMBER
Backup set count (of the set which contains this SPFILE backup)
MODIFICATION_TIME
DATE
Time when the SPFILE was last modified (this also includes creation
time)
BYTES
NUMBER
Size of the SPFILE (in bytes)
COMPLETION_TIME
DATE
Time when the backup of the SPFILE completed
V$BACKUP_SYNC_IO
This view displays performance information about ongoing and recently completed
RMAN backups and restores. For each backup, it contains one row for each input
datafile, one row for the aggregate total performance of all datafiles, and one row
for the output backup piece. This data is not stored persistently, and is not
preserved when the instance is re-started.
See Also: Oracle9i Database Performance Tuning Guide and Reference
for information on how to use this table to tune backup
performance
Column
Datatype
Description
SID
NUMBER
The Oracle SID of the session doing the backup or restore
SERIAL
NUMBER
The use count for the SID doing the backup or restore
USE_COUNT
NUMBER
A counter that can be used to identify rows from different backup sets
DEVICE_TYPE
VARCHAR2(17)
The device type where the file is located
TYPE
VARCHAR2(9)
INPUT, OUTPUT, or AGGREGATE
STATUS
VARCHAR2(11)
NOT STARTED, IN PROGRESS, or FINISHED
FILENAME
VARCHAR2(513)
The name of the backup file being read or written
SET_COUNT
NUMBER
The set count of the backup set being read or written
SET_STAMP
NUMBER
The set stamp of the backup set being read or written
3-20
Oracle9i Database Reference
V$BH
Column
Datatype
Description
BUFFER_SIZE
NUMBER
The size of the buffers being used to read/write this file, in bytes
BUFFER_COUNT
NUMBER
The number of buffers being used to read/write this file
TOTAL_BYTES
NUMBER
The total number of bytes that will be read or written for this file, if
known. If not known, this column will be null.
OPEN_TIME
DATE
The time this file was opened. If TYPE=’AGGREGATE’, then this is the
time that the first file in the aggregate was opened.
CLOSE_TIME
DATE
The time this file was closed. If TYPE=’AGGREGATE’, then this is the
time that the last file in the aggregate was closed.
ELAPSED_TIME
NUMBER
The time, in 100ths of seconds, that the file was open
MAXOPENFILES
NUMBER
The number of concurrently open DISK files. This value is only present
in rows where TYPE=’AGGREGATE’.
BYTES
NUMBER
The number of bytes read or written so far
EFFECTIVE_BYTES_PER_
SECOND
NUMBER
The I/O rate that was achieved with this device during this backup
IO_COUNT
NUMBER
The number of I/Os that were performed to this file
IO_TIME_TOTAL
NUMBER
The total time, in 100ths of seconds, taken to do I/O for this file
IO_TIME_MAX
NUMBER
The maximum time taken for a single I/O request
DISCRETE_BYTES_PER_
SECOND
NUMBER
The average transfer rate for this file
V$BGPROCESS
This view describes the background processes.
Column
Datatype
Description
PADDR
RAW(4 | 8)
Address of the process state object
NAME
VARCHAR2(5)
Name of this background process
DESCRIPTION
VARCHAR2(64)
Description of the background process
ERROR
NUMBER
Error encountered
V$BH
This is an Oracle9i Real Application Clusters view. This view gives the status and
number of pings for every buffer in the SGA.
Dynamic Performance (V$) Views 3-21
V$BH
Column
Datatype
Description
FILE#
NUMBER
Datafile identifier number (to find filename, query DBA_DATA_FILES
or V$DBFILES)
BLOCK#
NUMBER
Block number
CLASS#
NUMBER
The class number
STATUS
VARCHAR2(1)
Status of the buffer:
■
FREE - not currently in use
■
XCUR - exclusive
■
SCUR - shared current
■
CR - consistent read
■
READ - being read from disk
■
MREC - in media recovery mode
■
IREC - in instance recovery mode
XNC
NUMBER
Number of PCM x to null lock conversions due to contention with
another instance. This column is obsolete but is retained for historical
compatibility.
LOCK_ELEMENT_ADDR
RAW(4 | 8)
Address of the lock element that contains the PCM lock that is covering
the buffer. If more than one buffer has the same address, then these
buffers are covered by the same PCM lock.
LOCK_ELEMENT_NAME
NUMBER
The address of the lock element that contains the PCM lock that is
covering the buffer. If more than one buffer has the same address, then
these buffers are covered by the same PCM lock.
LOCK_ELEMENT_CLASS
NUMBER
The address of the lock element that contains the PCM lock that is
covering the buffer. If more than one buffer has the same address, then
these buffers are covered by the same PCM lock.
FORCED_READS
NUMBER
Number of times the block had to be made re-read from disk because
another instance had forced it out of this instance’s cache by requesting
the PCM lock on this block in lock mode.
FORCED_WRITES
NUMBER
Number of times DBWR had to write this block to disk because this
instance had dirtied the block and another instance had requested the
PCM lock on the block in conflicting mode.
DIRTY
VARCHAR2(1)
Y - block modified
TEMP
VARCHAR2(1)
Y - temporary block
PING
VARCHAR2(1)
Y - block pinged
STALE
VARCHAR2(1)
Y - block is stale
DIRECT
VARCHAR2(1)
Y - direct block
NEW
VARCHAR2(1)
Always set to N. This column is obsolete but is retained for historical
compatibility.
OBJD
NUMBER
Database object number of the block that the buffer represents
3-22
Oracle9i Database Reference
V$BUFFER_POOL
Column
Datatype
Description
TS#
NUMBER
Tablespace number of block
See Also: Oracle9i Real Application Clusters Concepts
V$BUFFER_POOL
This view displays information about all buffer pools available for the instance. The
"sets" pertain to the number of LRU latch sets.
See Also: "DB_BLOCK_SIZE" on page 1-36
Column
Datatype
Description
ID
NUMBER
Buffer pool ID number
NAME
VARCHAR2(20)
Buffer pool name. Possible values: DEFAULT, KEEP, RECYCLE. Note:
Currently, KEEP and RECYCLE pools only exist for the standard block
size. All non-standard block size pools are DEFAULT.
BLOCK_SIZE
NUMBER
Block size in bytes for buffers in this pool. Possible values: the standard
block size, the power of 2 non-standard block sizes, 2048, 4096, 8192,
16384, 32768.
RESIZE_STATE
VARCHAR2(10)
Current state of the resize operation
STATIC - not being resized
ALLOCATING - memory is being allocated (can be cancelled by the user)
ACTIVATING - new buffers are being created (user cannot cancel)
SHRINKING - buffers are being deleted (can be cancelled by the user)
CURRENT_SIZE
NUMBER
Present size of the sub-cache in megabytes
BUFFERS
NUMBER
Current instantaneous number of buffers
TARGET_SIZE
NUMBER
If a resize is in progress (state is not STATIC), records new target size in
megabytes. If the pool is STATIC, the value in this column is the same
as the current size of the pool.
TARGET_BUFFERS
NUMBER
If a resize is in progress, records new target size in terms of buffers.
Otherwise, the value in this column is the same as the current number
of buffers.
PREV_SIZE
NUMBER
Previous buffer pool size. If the buffer pool has never been resized, the
previous size is zero.
PREV_BUFFERS
NUMBER
Previous number of buffers in the buffer pool. Value is zero if the buffer
pool has never been resized.
LO_BNUM
NUMBER
Obsolete column
Dynamic Performance (V$) Views 3-23
V$BUFFER_POOL_STATISTICS
Column
Datatype
Description
HI_BNUM
NUMBER
Obsolete column
LO_SETID
NUMBER
Obsolete column
HI_SETID
NUMBER
Obsolete column
SET_COUNT
NUMBER
Obsolete column
V$BUFFER_POOL_STATISTICS
V$BUFFER_POOL_STATISTICS displays information about all buffer pools
available for the instance. The "sets" pertain to the number of LRU latch sets.
See Also: "DB_CACHE_SIZE" on page 1-38
Column
Datatype
Description
ID
NUMBER
Buffer pool ID number
NAME
VARCHAR2(20)
Buffer pool name
SET_MSIZE
NUMBER
Buffer pool maximum set size
CNUM_REPL
NUMBER
Number of buffers on replacement list
CNUM_WRITE
NUMBER
Number of buffers on write list
CNUM_SET
NUMBER
Number of buffers in set
BUF_GOT
NUMBER
Number of buffers gotten by the set
SUM_WRITE
NUMBER
Number of buffers written by the set
SUM_SCAN
NUMBER
Number of buffers scanned in the set
FREE_BUFFER_WAIT
NUMBER
Free buffer wait statistic
WRITE_COMPLETE_WAIT
NUMBER
Write complete wait statistic
BUFFER_BUSY_WAIT
NUMBER
Buffer busy wait statistic
FREE_BUFFER_INSPECTED NUMBER
Free buffer inspected statistic
DIRTY_BUFFERS_
INSPECTED
NUMBER
Dirty buffers inspected statistic
DB_BLOCK_CHANGE
NUMBER
Database blocks changed statistic
DB_BLOCK_GETS
NUMBER
Database blocks gotten statistic
CONSISTENT_GETS
NUMBER
Consistent gets statistic
PHYSICAL_READS
NUMBER
Physical reads statistic
PHYSICAL_WRITES
NUMBER
Physical writes statistic
3-24
Oracle9i Database Reference
V$CACHE
V$CACHE
This is an Oracle9i Real Application Clusters view. This view contains information
from the block header of each block in the SGA of the current instance as related to
particular database objects.
See Also: Oracle9i Real Application Clusters Concepts
Column
Datatype
Description
FILE#
NUMBER
Datafile identifier number (to find filename, query DBA_DATA_FILES
or V$DBFILES)
BLOCK#
NUMBER
Block number
CLASS#
NUMBER
Class number
STATUS
VARCHAR2(1)
Status of block:
■
FREE - Not currently in use
■
XCUR - Exclusive
■
SCUR - Shared current
■
CR - Consistent read
■
READ - Being read from disk
■
MREC - In media recovery mode
■
IREC - In instance recovery mode
XNC
NUMBER
Number of PCM x to null lock conversions due to contention with
another instance. This column is obsolete and maintained only for
compatibility reasons.
FORCED_READS
NUMBER
Forced reads
FORCED_WRITES
NUMBER
Forced writes
NAME
VARCHAR2(30)
Name of the database object containing the block
PARTITION_NAME
VARCHAR2(30)
Name of the partition; NULL for non-partitioned objects
Dynamic Performance (V$) Views 3-25
V$CACHE_LOCK
Column
Datatype
Description
KIND
VARCHAR2(12)
Type of database object:
■
1 - Index
■
2 - Table
■
3 - Cluster
■
4 - View
■
5 - Synonym
■
6 - Sequence
■
7 - Procedure
■
8 - Function
■
9 - Package
■
10 - Nonexistent
■
11 - Package body
■
12 - Trigger
■
13 - Type
■
14 - Type body
■
19 - Table partition
■
20 - Index partition
■
21 - LOB
■
22 - Library
■
Null - Unknown
OWNER#
NUMBER
Owner number
LOCK_ELEMENT_ADDR
RAW(4 | 8)
Address of the lock element that contains the PCM lock that is covering
the buffer. If more than one buffer has the same address, then these
buffers are covered by the same PCM lock.
LOCK_ELEMENT_NAME
NUMBER
Address of the lock element that contains the PCM lock that is covering
the buffer. If more than one buffer has the same address, then these
buffers are covered by the same PCM lock.
V$CACHE_LOCK
This is an Oracle9i Real Application Clusters view. V$CACHE_LOCK is similar to
V$CACHE, except for the platform specific lock manager identifiers. This
information may be useful if the platform- specific lock manager provides tools for
monitoring the PCM lock operations that are occurring. For example, first query to
find the lock element address using INDX and CLASS, then query V$BH to find the
buffers that are covered by the lock.
3-26
Oracle9i Database Reference
V$CACHE_LOCK
See Also:
■
Oracle9i Real Application Clusters Concepts
■
"V$CACHE" on page 3-25
Column
Datatype
Description
FILE#
NUMBER
Datafile identifier number (to find filename, query DBA_DATA_FILES
or V$DBFILES)
BLOCK#
NUMBER
Block number
STATUS
VARCHAR2(4)
Status of block:
■
FREE - Not currently in use
■
XCUR - Exclusive
■
SCUR - Shared current
■
CR - Consistent read
■
READ - Being read from disk
■
MREC - In media recovery mode
■
IREC - In instance recovery mode
XNC
NUMBER
Number of parallel cache management (PCM) lock conversions due to
contention with another instance
NAME
VARCHAR2(30)
Name of the database object containing the block
Dynamic Performance (V$) Views 3-27
V$CACHE_LOCK
Column
Datatype
Description
KIND
VARCHAR2(12)
Type of database object:
■
1 - Index
■
2 - Table
■
3 - Cluster
■
4 - View
■
5 - Synonym
■
6 - Sequence
■
7 - Procedure
■
8 - Function
■
9 - Package
■
10 - Nonexistent
■
11 - Package body
■
12 - Trigger
■
13 - Type
■
14 - Type body
■
19 - Table partition
■
20 - Index partition
■
21 - LOB
■
22 - Library
■
Null - Unknown
OWNER#
NUMBER
Owner number
LOCK_ELEMENT_ADDR
RAW(4 | 8)
Address of the lock element that contains the PCM lock that is covering
the buffer. If more than one buffer has the same address, then these
buffers are covered by the same PCM lock.
LOCK_ELEMENT_NAME
NUMBER
Address of the lock element that contains the PCM lock that is covering
the buffer. If more than one buffer has the same address, then these
buffers are covered by the same PCM lock.
FORCED_READS
NUMBER
Number of times the block had to be made re-read from disk because
another instance had forced it out of this instance’s cache by requesting
the PCM lock on this block in lock mode
FORCED_WRITES
NUMBER
Number of times DBWR had to write this block to disk because this
instance had dirtied the block and another instance had requested the
PCM lock on the block in conflicting mode.
INDX
NUMBER
Platform-specific lock manager identifier
CLASS
NUMBER
Platform-specific lock manager identifier
3-28
Oracle9i Database Reference
V$CACHE_TRANSFER
V$CACHE_TRANSFER
This is an Oracle9i Real Application Clusters view. The V$CACHE_TRANSFER view
is identical to the V$CACHE view but only displays blocks that have been pinged at
least once. This view contains information from the block header of each block in
the SGA of the current instance as related to particular database objects.
See Also: "V$CACHE" on page 3-25 and Oracle9i Real Application
Clusters Concepts
Column
Datatype
Description
FILE#
NUMBER
Datafile identifier number (to find the filename, query DBA_DATA_
FILES or V$DBFILE)
BLOCK#
NUMBER
Block number
CLASS#
NUMBER
Class number
STATUS
VARCHAR2(4)
Status of block:
■
FREE - not currently in use
■
XCUR - exclusive
■
SCUR - shared current
■
CR - consistent read
■
READ - being read from disk
■
MREC - in media recovery mode
■
IREC - in instance recovery mode
XNC
NUMBER
Number of PCM lock conversions due to contention with another
instance. This column is obsolete but is retained for historical
compatibility.
FORCED_READS
NUMBER
Number of times the block had to be reread from disk because another
instance had forced it out of this instance’s cache by requesting the
PCM lock on the block in exclusive mode
FORCED_WRITES
NUMBER
Number of times DBWR had to write this block to disk because this
instance had used the block and another instance had requested the
lock on the block in a conflicting mode
NAME
VARCHAR2(30)
Name of the database object containing the block
PARTITION_NAME
VARCHAR2(30)
NULL for non-partitioned objects
KIND
VARCHAR2(15)
Type of database object
See Also: Table 3–1 on page 3-78
OWNER#
NUMBER
Owner number
Dynamic Performance (V$) Views 3-29
V$CIRCUIT
Column
Datatype
Description
GC_ELEMENT_ADDR
RAW(4 | 8)
Address of the lock element that contains the PCM lock that is covering
the buffer. If more than one buffer has the same address, then these
buffers are covered by the same PCM lock.
GC_ELEMENT_NAME
NUMBER
The name of the lock that contains the PCM lock that is covering the
buffer
V$CIRCUIT
V$CIRCUIT contains information about virtual circuits, which are user connections
to the database through dispatchers and servers.
Column
Datatype
Description
CIRCUIT
RAW(4 | 8)
Circuit address
DISPATCHER
RAW(4 | 8)
Current dispatcher process address
SERVER
RAW(4 | 8)
Current server process address
WAITER
RAW(4 | 8)
Address of server process that is waiting for the (currently busy) circuit
to become available
SADDR
RAW(4 | 8)
Address of session bound to the circuit
STATUS
VARCHAR2(16)
Status of the circuit:
QUEUE
VARCHAR2(16)
■
BREAK - currently interrupted
■
EOF - about to be removed
■
OUTBOUND - an outward link to a remote database
■
NORMAL - normal circuit into the local database
Queue the circuit is currently on:
■
COMMON - on the common queue, waiting to be picked up by a
server process
■
DISPATCHER - waiting for the dispatcher
■
SERVER - currently being serviced
■
NONE - idle circuit
MESSAGE0
NUMBER
Size in bytes of the messages in the first message buffer
MESSAGE1
NUMBER
Size in bytes of the messages in the second message buffer
MESSAGE2
NUMBER
Size in bytes of the messages in the third message buffer
MESSAGE3
NUMBER
Size in bytes of the messages in the fourth message buffer
MESSAGES
NUMBER
Total number of messages that have gone through this circuit
BYTES
NUMBER
Total number of bytes that have gone through this circuit
BREAKS
NUMBER
Total number of breaks (interruptions) for this circuit
3-30
Oracle9i Database Reference
V$COMPATIBILITY
Column
Datatype
Description
PRESENTATION
VARCHAR2(16)
The presentation protocol used by the client and server
V$CLASS_CACHE_TRANSFER
V$CLASS_CACHE_TRANSFER displays the number of blocks pinged per block class.
Use this view to compare contentions for blocks in different classes.
Column
Datatype
Description
CLASS
VARCHAR2(18)
The block class
X_2_NULL
NUMBER
Number of lock conversions from Exclusive-to-NULL for all blocks of
the specified CLASS
X_2_NULL_FORCED_WRITE NUMBER
Number of forced writes that occur for blocks of the specified CLASS
due to Exclusive-to-NULL conversions
X_2_NULL_FORCED_STALE NUMBER
Number of times a block in the CLASS was made STALE due to
Exclusive-to-NULL conversions
X_2_S
NUMBER
Number of lock conversions from Exclusive-to-Shared for all blocks of
the specified CLASS
X_2_S_FORCED_WRITE
NUMBER
Number of forced writes that occur for blocks of the specified CLASS
due to Exclusive-to-Shared conversions
S_2_NULL
NUMBER
Number of lock conversions from Shared-to-NULL for all blocks of the
specified CLASS
S_2_NULL_FORCED_STALE NUMBER
Number of times a block in the CLASS was made STALE due to
Shared-to-NULL conversions
NULL_2_X
NUMBER
Number of lock conversions from NULL-to-Exclusive for all blocks of
the specified CLASS
S_2_X
NUMBER
Number of lock conversions from Shared-to-Exclusive for all blocks of
the specified CLASS
NULL_2_S
NUMBER
Number of lock conversions from NULL-to-Shared for all blocks of the
specified CLASS
V$COMPATIBILITY
This view displays features in use by the database instance that may prevent
downgrading to a previous release. This is the dynamic (SGA) version of this
information, and may not reflect features that other instances have used, and may
include temporary incompatibilities (like UNDO segments) that will not exist after
the database is shut down cleanly.
Dynamic Performance (V$) Views 3-31
V$COMPATSEG
Column
Datatype
Description
TYPE_ID
VARCHAR2(8)
Internal feature identifier
RELEASE
VARCHAR2(60)
Release in which that feature appeared
DESCRIPTION
VARCHAR2(64)
Description of the feature
V$COMPATSEG
This view lists the permanent features in use by the database that will prevent
moving back to an earlier release.
Column
Datatype
Description
TYPE_ID
VARCHAR2(8)
Internal feature identifier
RELEASE
VARCHAR2(60)
Release in which that feature appeared. The software must be able to
interpret data formats added in that release.
UPDATED
VARCHAR2(60)
Release that first used the feature
V$CONTEXT
This view lists set attributes in the current session.
Column
Datatype
Description
NAMESPACE
VARCHAR2(30)
The namespace that the attribute is in
ATTRIBUTE
VARCHAR2(30)
The name of attribute
VALUE
VARCHAR2(4000)
The value of attribute
V$CONTROLFILE
This view lists the names of the control files.
Column
Datatype
Description
STATUS
VARCHAR2(7)
INVALID if the name cannot be determined, which should not occur.
NULL if the name can be determined.
NAME
VARCHAR2(257)
The name of the control file
V$CONTROLFILE_RECORD_SECTION
This view displays information about the control file record sections.
3-32
Oracle9i Database Reference
V$COPY_CORRUPTION
Column
Datatype
Description
TYPE
VARCHAR2(17)
Identifies the type of record section: DATABASE, CKPT PROGRESS,
REDO THREAD, REDO LOG, DATAFILE, FILENAME,
TABLESPACE, LOG HISTORY, OFFLINE RANGE, ARCHIVED LOG,
BACKUP SET, BACKUP PIECE, BACKUP DATAFILE, BACKUP
REDOLOG, DATAFILE COPY, BACKUP CORRUPTION, COPY
CORRUPTION, DELETED OBJECT, or PROXY COPY
RECORD_SIZE
NUMBER
Record size in bytes
RECORDS_TOTAL
NUMBER
Number of records allocated for the section
RECORDS_USED
NUMBER
Number of records used in the section
FIRST_INDEX
NUMBER
Index (position) of the first record
LAST_INDEX
NUMBER
Index of the last record
LAST_RECID
NUMBER
Record ID of the last record
V$COPY_CORRUPTION
This view displays information about datafile copy corruptions from the control file.
Column
Datatype
Description
RECID
NUMBER
Copy corruption record ID
STAMP
NUMBER
Copy corruption record stamp
COPY_RECID
NUMBER
Datafile copy record ID
COPY_STAMP
NUMBER
Datafile copy record stamp
FILE#
NUMBER
Datafile number
BLOCK#
NUMBER
First block of the corrupted range
BLOCKS
NUMBER
Number of contiguous blocks in the corrupted range
CORRUPTION_CHANGE#
NUMBER
Change# at which the logical corruption was detected. Set to 0 to
indicate media corruption.
MARKED_CORRUPT
VARCHAR2(3)
(YES | NO) If set to YES the blocks were not marked corrupted in the
datafile, but were detected and marked as corrupted while making the
datafile copy
Dynamic Performance (V$) Views 3-33
V$CR_BLOCK_SERVER
Column
Datatype
Description
CORRUPTION_TYPE
VARCHAR2(9)
Type of block corruption in the datafile:
■
■
■
■
■
ALL ZERO - Block header on disk contained only zeros. The block
may be valid if it was never filled and if it is in an Oracle7 file. The
buffer will be reformatted to the Oracle8 standard for an empty
block.
FRACTURED - Block header looks reasonable, but the front and
back of the block are different versions.
CHECKSUM - optional check value shows that the block is not
self-consistent. It is impossible to determine exactly why the check
value fails, but it probably fails because sectors in the middle of
the block are from different versions.
CORRUPT - Block is wrongly identified or is not a data block (for
example, the data block address is missing)
LOGICAL - Specifies the range is for logically corrupt blocks.
CORRUPTION_CHANGE# will have a nonzero value.
V$CR_BLOCK_SERVER
This view displays statistics on the block server background processes (BSPn) used
in cache fusion.
Column
Datatype
Description
CR_REQUESTS
NUMBER
Number of requests received for a version of a block at a specific SCN
("CR" refers to "consistent-read")
CURRENT_REQUESTS
NUMBER
Number of requests for the most recent (current) version of a block
CR_REQUESTS + CURRENT_REQUESTS = total number of requests
handled by the BSPn processes
DATA_REQUESTS
NUMBER
Number of current or CR requests for data blocks
UNDO_REQUESTS
NUMBER
Number of CR requests for undo blocks
TX_REQUESTS
NUMBER
Number of CR requests for undo segment header blocks
DATA_REQUESTS + UNDO_REQUESTS + TX_REQUESTS = total number
of requests handled by the BSPn processes
CURRENT_RESULTS
NUMBER
Number of requests for which no changes were rolled out of the block
returned to the requesting instance
PRIVATE_RESULTS
NUMBER
Number of requests for which changes were rolled out of the block
returned to the requesting instance, and only the requesting transaction
can use the resulting CR block
ZERO_RESULTS
NUMBER
Number of requests for which changes were rolled out of the block
returned to the requesting instance. Only zero-XID transactions can use
the block.
3-34
Oracle9i Database Reference
V$DATABASE
Column
Datatype
Description
DISK_READ_RESULTS
NUMBER
Number of requests for which the requesting instance had to read the
requested block from disk
FAIL_RESULTS
NUMBER
Number of requests that failed; the requesting transaction must reissue
the request
FAIRNESS_DOWN_
CONVERTS
NUMBER
Number of times an instance receiving a request has down-converted
an X lock on a block because it was not modifying the block
FAIRNESS_CLEARS
NUMBER
Number of times the "fairness counter" was cleared. This counter tracks
the number of times a block was modified after it was served.
FREE_GC_ELEMENTS
NUMBER
Number of times a request was received from another instance and the
X lock had no buffers
FLUSHES
NUMBER
Number of times the log has been flushed by a BSPn process
LIGHT_WORKS
NUMBER
Number of times the light-work rule was evoked. This rule prevents the
BSP back ground process from going to disk while responding to CR
requests for data, undo, or undo segment header blocks. This rule can
prevent the BSP process from completing its response to the CR request.
See Also: Oracle9i Real Application Clusters Concepts for more
information on these processes and on cache fusion
Note: This view contains internal diagnostic information for use
by Oracle Support Services. It is subject to change without notice.
V$DATABASE
V$DATABASE contains database information from the control file.
Column
Datatype
Description
DBID
NUMBER
Database ID calculated when the database is created and stored in all
file headers
NAME
VARCHAR2(9)
Name of the database
CREATED
DATE
Creation date
RESETLOGS_CHANGE#
NUMBER
Change number at open resetlogs
RESETLOGS_TIME
DATE
Timestamp of open resetlogs
PRIOR_RESETLOGS_
CHANGE#
NUMBER
Change number at prior resetlogs
PRIOR_RESETLOGS_TIME
DATE
Timestamp of prior resetlogs
Dynamic Performance (V$) Views 3-35
V$DATABASE
Column
Datatype
Description
LOG_MODE
VARCHAR2(12)
Archive log mode (NOARCHIVELOG or ARCHIVELOG)
CHECKPOINT_CHANGE#
NUMBER
Last SCN checkpointed
ARCHIVE_CHANGE#
NUMBER
Last SCN archived
CONTROLFILE_TYPE
VARCHAR2(7)
Type of control file:
■
STANDBY - Indicates that the database is in standby mode
■
CLONE - indicates a clone database
■
■
CONTROLFILE_CREATED
DATE
BACKUP | CREATED - indicates the database is being recovered
using a backup or created control file
CURRENT - the control file changes to this type following a standby
database activate or database open after recovery
Control file creation timestamp
CONTROLFILE_SEQUENCE# NUMBER
Control file sequence number incremented by control file transactions
CONTROLFILE_CHANGE#
NUMBER
Last change number in backup control file (null if the control file is not
a backup)
CONTROLFILE_TIME
DATE
Last timestamp in backup control file (null if the control file is not a
backup)
OPEN_RESETLOGS
VARCHAR2(11)
(NOT ALLOWED | ALLOWED | REQUIRED) Indicates whether the next
database open allows or requires the resetlogs option
VERSION_TIME
DATE
Version time
OPEN_MODE
VARCHAR2(10)
Open mode information
PROTECTION_MODE
VARCHAR2(20)
Protection mode currently in effect for the database:
■
■
■
■
■
3-36
Oracle9i Database Reference
MAXIMUM PROTECTION - Database is running in maximized
protection mode
MAXIMUM AVAILABILITY - Database is running in maximized
availability mode
RESYNCHRONIZATION - Database is running in resynchronization
mode
MAXIMUM PERFORMANCE - database is running in maximized
protection mode
UNPROTECTED - Database is unprotected (this normally occurs
when the primary database is mounted and not open)
V$DATABASE
Column
Datatype
Description
PROTECTION_LEVEL
VARCHAR2(20)
Aggregated protection mode currently in effect for the database:
■
■
■
■
■
MAXIMUM PROTECTION - Database is running in maximized
protection mode
MAXIMUM AVAILABILITY - Database is running in maximized
availability mode
RESYNCHRONIZATION - Database is running in resynchronization
mode
MAXIMUM PERFORMANCE - database is running in maximized
protection mode
UNPROTECTED - Database is unprotected (this normally occurs
when the primary database is mounted and not open)
Note:This column is an aggregation of the PROTECTION_MODE of all
standby archivelog destinations.
REMOTE_ARCHIVE
VARCHAR2(8)
Value of the REMOTE_ARCHIVE_ENABLE initialization parameter
ACTIVATION#
NUMBER
Number assigned to the database instantiation
DATABASE_ROLE
VARCHAR2(16)
Current role of the database; either primary or standby
ARCHIVELOG_CHANGE#
NUMBER
Highest NEXT_CHANGE# (from the V$ARCHIVED_LOG view) for an
archived log
SWITCHOVER_STATUS
VARCHAR2(18)
Indicates whether switchover is allowed:
■
■
■
■
■
■
■
NOT ALLOWED - Either this is a standby database and the primary
database has not been switched first or this is a primary database
and there are no standby databases.
SESSIONS ACTIVE - Indicates that there are active SQL sessions
attached to the primary or standby database that need to be
disconnected before the switchover operation is permitted. Query
the V$SESSION view to identify the specific processes that need to
be terminated.
SWITCHOVER PENDING - This is a standby database and the
primary database switchover request has been received but not
processed.
SWITCHOVER LATENT - The switchover was in pending mode,
but did not complete and went back to the primary database.
TO PRIMARY - This is a standby database and is allowed to switch
over to a primary database.
TO STANDBY - This is a primary database and is allowed to switch
over to a standby database.
RECOVERY NEEDED - This is a standby database that has not
received the switchover request.
Dynamic Performance (V$) Views 3-37
V$DATABASE_BLOCK_CORRUPTION
Column
Datatype
Description
GUARD_STATUS
VARCHAR2(7)
Protects data from being changed:
■
■
■
SUPPLEMENTAL_LOG_
DATA_MIN
VARCHAR2(3)
ALL - Indicates all users other than SYS are prevented from
making changes to any data in the database.
STANDBY - Indicates all users other than SYS are prevented from
making changes to any database object being maintained by
logical standby.
NONE - Indicates normal security for all data in the database.
Ensures that LogMiner will have sufficient information to support
chained rows and various storage arrangements such as cluster tables.
See Oracle9i SQL Reference for additional information about the ALTER
DATABASE ADD SUPPLEMENTAL LOG DATA statement.
SUPPLEMENTAL_LOG_
DATA_PK
VARCHAR2(3)
For all tables with a primary key, ensures that all columns of the
primary key are placed into the redo log whenever an update operation
is performed.
See Oracle9i SQL Reference for additional information about the ALTER
DATABASE ADD SUPPLEMENTAL LOG DATA statement.
SUPPLEMENTAL_LOG_
DATA_UI
VARCHAR2(3)
For all tables with a unique key, ensures that if any unique key columns
are modified, all other columns belonging to the unique key are also
placed into the redo log.
See Oracle9i SQL Reference for additional information about the ALTER
DATABASE ADD SUPPLEMENTAL LOG DATA statement.
FORCE_LOGGING
VARCHAR2(3)
Indicates whether the database is under force logging mode (YES) or
not (NO)
V$DATABASE_BLOCK_CORRUPTION
V$DATABASE_BLOCK_CORRUPTION displays information about database blocks
that were corrupted after the last backup.
Column
Datatype
Description
FILE#
NUMBER
Absolute file number of the datafile that contains the corrupt blocks
BLOCK#
NUMBER
Block number of the first corrupt block in the range of corrupted blocks
BLOCKS
NUMBER
Number of corrupted blocks found starting with BLOCK#
CORRUPTION_CHANGE#
NUMBER
Change number at which the logical corruption was detected. Set to 0 to
indicate media corruption.
3-38
Oracle9i Database Reference
V$DATAFILE
Column
Datatype
Description
CORRUPTION_TYPE
VARCHAR2(9)
Type of block corruption in the datafile:
■
■
■
■
■
ALL ZERO - Block header on disk contained only zeros. The block
may be valid if it was never filled and if it is in an Oracle7 file. The
buffer will be reformatted to the Oracle8 standard for an empty
block.
FRACTURED - Block header looks reasonable, but the front and
back of the block are different versions.
CHECKSUM - optional check value shows that the block is not
self-consistent. It is impossible to determine exactly why the check
value fails, but it probably fails because sectors in the middle of
the block are from different versions.
CORRUPT - Block is wrongly identified or is not a data block (for
example, the data block address is missing)
LOGICAL - Specifies the range is for logically corrupt blocks.
CORRUPTION_CHANGE# will have a nonzero value.
V$DATABASE_INCARNATION
V$DATABASE_INCARNATION displays information about all database incarnations.
Oracle creates a new incarnation whenever you open a database with the
RESETLOGS option. Records about the current and immediately previous
incarnation are also contained in the V$DATABASE view.
Column
Datatype
Description
RESETLOGS_CHANGE#
NUMBER
SCN of the RESETLOGS operation that created this incarnation
RESETLOGS_TIME
DATE
Timestamp of the RESETLOGS operation that created this incarnation
PRIOR_RESETLOGS_
CHANGE#
NUMBER
SCN of the previous RESETLOGS operation
PRIOR_RESETLOGS_TIME
DATE
Timestamp of the previous RESETLOGS operation
V$DATAFILE
This view contains datafile information from the control file.
See Also: "V$DATAFILE_HEADER" on page 3-42, which displays
information from datafile headers
Column
Datatype
Description
FILE#
NUMBER
File identification number
Dynamic Performance (V$) Views 3-39
V$DATAFILE
Column
Datatype
Description
CREATION_CHANGE#
NUMBER
Change number at which the datafile was created
CREATION_TIME
DATE
Timestamp of the datafile creation
TS#
NUMBER
Tablespace number
RFILE#
NUMBER
Tablespace relative datafile number
STATUS
VARCHAR2(7)
Type of file (system or user) and its status. Values: OFFLINE, ONLINE,
SYSTEM, RECOVER, SYSOFF (an offline file from the SYSTEM tablespace)
ENABLED
VARCHAR2(10)
Describes how accessible the file is from SQL:
■
DISABLED - no SQL access allowed
■
READ ONLY - no SQL updates allowed
■
READ WRITE - full access allowed
■
UNKNOWN - should not occur unless the control file is corrupted
CHECKPOINT_CHANGE#
NUMBER
SCN at last checkpoint
CHECKPOINT_TIME
DATE
Time stamp of the checkpoint#
UNRECOVERABLE_CHANGE# NUMBER
Last unrecoverable change# made to this datafile. This column is
always updated when an unrecoverable operation completes.
UNRECOVERABLE_TIME
DATE
Time stamp of the last unrecoverable change
LAST_CHANGE#
NUMBER
Last change# made to this datafile. Set to NULL if the datafile is being
changed.
LAST_TIME
DATE
Timestamp of the last change
OFFLINE_CHANGE#
NUMBER
Offline change# of the last offline range. This column is updated only
when the datafile is brought online.
ONLINE_CHANGE#
NUMBER
Online change# of the last offline range
ONLINE_TIME
DATE
Online timestamp of the last offline range
BYTES
NUMBER
Current size in bytes; 0 if inaccessible
BLOCKS
NUMBER
Current datafile size in blocks; 0 if inaccessible
CREATE_BYTES
NUMBER
Size when created, in bytes
BLOCK_SIZE
NUMBER
Block size of the datafile
NAME
VARCHAR2(513)
Datafile name
PLUGGED_IN
NUMBER
Describes whether the tablespace is plugged in. The value is 1 if the
tablespace is plugged in and has not been made read-write, 0 if not.
BLOCK1_OFFSET
NUMBER
The offset from the beginning of the file to where the Oracle generic
information begins. The exact length of the file can be computed as
follows: BYTES+BLOCK1_OFFSET.
AUX_NAME
VARCHAR2(513)
The auxiliary name that has been set for this file via CONFIGURE
AUXNAME
3-40
Oracle9i Database Reference
V$DATAFILE_COPY
V$DATAFILE_COPY
This view displays datafile copy information from the control file.
Column
Datatype
Description
RECID
NUMBER
Datafile copy record ID
STAMP
NUMBER
Datafile copy record stamp
NAME
VARCHAR2(513)
Filename of the datafile copy. The maximum length of the name is OS
dependent.
TAG
VARCHAR2(32)
Datafile copy tag
FILE#
NUMBER
Absolute datafile number
RFILE#
NUMBER
Tablespace relative datafile number
CREATION_CHANGE#
NUMBER
Datafile creation change#
CREATION_TIME
DATE
Datafile creation timestamp
RESETLOGS_CHANGE#
NUMBER
Resetlogs change# of the datafile when the copy was made
RESETLOGS_TIME
DATE
Resetlogs timestamp of the datafile when the copy was made
INCREMENTAL_LEVEL
NUMBER
The incremental level
CHECKPOINT_CHANGE#
NUMBER
Checkpoint change# of the datafile when the copy was made
CHECKPOINT_TIME
DATE
Checkpoint timestamp of the datafile when the copy was made
ABSOLUTE_FUZZY_
CHANGE#
NUMBER
Highest change seen when the datafile was copied
RECOVERY_FUZZY_
CHANGE#
NUMBER
Highest change written to the file by media recovery
RECOVERY_FUZZY_TIME
DATE
Timestamp of the highest change written to the file by media recovery
ONLINE_FUZZY
VARCHAR2(3)
(YES|NO) If set to YES, this is a copy taken using an operating system
utility after a crash or offline immediate (or an invalid copy taken while
datafile was online and the database open). Recovery will need to apply
all redo up to the next crash recovery marker to make the file consistent.
BACKUP_FUZZY
VARCHAR2(3)
(YES|NO) If set to YES, this is a copy taken using the BEGIN
BACKUP/END BACKUP technique. Recovery will need to apply all redo
up to the end backup marker to make this copy consistent.
MARKED_CORRUPT
NUMBER
Number of blocks marked corrupt by this copy operation. That is,
blocks that were not marked corrupted in the source datafile, but were
detected and marked as corrupted during the copy operation.
MEDIA_CORRUPT
NUMBER
Total number of media corrupt blocks. For example, blocks with
checksum errors are marked media corrupt.
LOGICALLY_CORRUPT
NUMBER
Total number of logically corrupt blocks. For example, applying redo
for unrecoverable operations will mark affected blocks logically
corrupt.
Dynamic Performance (V$) Views 3-41
V$DATAFILE_HEADER
Column
Datatype
Description
BLOCKS
NUMBER
Size of the datafile copy in blocks (also the size of the datafile when the
copy was made)
BLOCK_SIZE
NUMBER
Block size of the datafile
OLDEST_OFFLINE_RANGE
NUMBER
The RECID of the oldest offline range record in this control file copy; 0
for datafile copies
DELETED
VARCHAR2(3)
(YES|NO) If set to YES the datafile copy has been deleted or overwritten
STATUS
VARCHAR2(1)
Identifies the status of this datafile copy. Possible values are:
A - Available
D - Deleted
U - Unavailable
X - Expired
COMPLETION_TIME
DATE
CONTROLFILE_TYPE
VARCHAR2(1)
Time when the copy was completed
B indicates normal copies
S indicates standby copies
KEEP
VARCHAR2(3)
(YES/NO) Indicates whether or not this backup set has a retention
policy that is different than the value for the configure retention policy
KEEP_UNTIL
DATE
If KEEP_UNTIL_TIME is specified, this is the date after which the
backup becomes obsolete. If this column is null, then the backup never
expires.
KEEP_OPTIONS
VARCHAR2(10)
Lists additional retention options for this backup set. Possible values
are:
LOGS - The logs need to recover this backup are kept
NOLOGS - The logs needed to recover this backup will not be kept
V$DATAFILE_HEADER
This view displays datafile information from the datafile headers.
Column
Datatype
Description
FILE#
NUMBER
Datafile number (from control file)
STATUS
VARCHAR2(7)
ONLINE | OFFLINE (from control file)
ERROR
VARCHAR2(18)
NULL if the datafile header read and validation were successful. If the
read failed then the rest of the columns are NULL. If the validation
failed then the rest of columns may display invalid data. If there is an
error then usually the datafile must be restored from a backup before it
can be recovered or used.
3-42
Oracle9i Database Reference
V$DATAGUARD_STATUS
Column
Datatype
Description
FORMAT
NUMBER
Indicates the format for the header block. The possible values are 6, 7,
8, or 0.
6 - indicates Oracle Version 6
7 - indicates Oracle Version 7
8 - indicates Oracle Version 8
0 - indicates the format could not be determined (for example, the
header could not be read)
RECOVER
VARCHAR2(3)
File needs media recovery (YES | NO)
FUZZY
VARCHAR2(3)
File is fuzzy (YES | NO)
CREATION_CHANGE#
NUMBER
Datafile creation change#
CREATION_TIME
DATE
Datafile creation timestamp
TABLESPACE_NAME
VARCHAR2(30)
Tablespace name
TS#
NUMBER
Tablespace number
RFILE#
NUMBER
Tablespace relative datafile number
RESETLOGS_CHANGE#
NUMBER
Resetlogs change#
RESETLOGS_TIME
DATE
Resetlogs timestamp
CHECKPOINT_CHANGE#
NUMBER
Datafile checkpoint change#
CHECKPOINT_TIME
DATE
Datafile checkpoint timestamp
CHECKPOINT_COUNT
NUMBER
Datafile checkpoint count
BYTES
NUMBER
Current datafile size in bytes
BLOCKS
NUMBER
Current datafile size in blocks
NAME
VARCHAR2(512)
Datafile name
V$DATAGUARD_STATUS
V$DATAGUARD_STATUS displays and logs events that would typically be triggered
by any message to the alert log or server process trace files.
Dynamic Performance (V$) Views 3-43
V$DB_CACHE_ADVICE
Column
Datatype
Description
FACILITY
VARCHAR2(24)
Facility that encountered the event. Possible values are:
SEVERITY
VARCHAR2(13)
■
CRASH RECOVERY
■
LTS
■
LAS
■
RMS
■
REMOTE FILE SERVER
■
FETCH ARCHIVE LOG
■
DATA GUARD
■
NETWORK SERVICES
Severity of the event. Possible values are:
■
INFORMATIONAL - informational message
■
WARNING - warning message
■
ERROR - indicates the process has failed
■
FATAL
■
CONTROL - an expected change in state such as the start or
completion of an archival, log recovery, or switchover operation
DEST_ID
NUMBER
Destination ID number to which the event pertains. If the event does
not pertain to a particular destination, then the value is 0.
MESSAGE_NUM
NUMBER
A chronologically increasing number giving each event a unique
number
ERROR_CODE
NUMBER
Error ID pertaining to the event
CALLOUT
VARCHAR2(3)
Indicates whether the current entry is a callout event (YES) or not (NO)
A YES value in this column indicates that this event may require the
DBA to perform some action. Examine the ERROR_CODE and MESSAGE
columns for more information.
A NO value in this column generally corresponds to an
INFORMATIONAL or WARNING event which would not require any
action by the DBA.
TIMESTAMP
DATE
???
MESSAGE
VARCHAR2(256)
A text message describing the event
V$DB_CACHE_ADVICE
V$DB_CACHE_ADVICE contains rows that predict the number of physical reads for
the cache size corresponding to each row. The rows also compute a "physical read
factor," which is the ratio of the number of estimated reads to the number of reads
actually performed by the real buffer cache during the measurement interval .
3-44
Oracle9i Database Reference
V$DB_OBJECT_CACHE
See Also: "DB_CACHE_ADVICE" on page 1-37
Column
Datatype
Description
ID
NUMBER
Buffer pool identifier (ranges from 1 to 8)
NAME
VARCHAR2(20)
Buffer pool name
BLOCK_SIZE
NUMBER
Block size in bytes for buffers in this pool. Possible values: the standard
block size, the power of 2 non-standard block sizes, 2048, 4096, 8192,
16384, 32768.
ADVICE_STATUS
VARCHAR2(3)
Status of the advisory. ON indicates it is currently running; OFF indicates
it is disabled (in this case the estimates are historical and calculated
when last enabled).
SIZE_FOR_ESTIMATE
NUMBER
Cache size for prediction (in megabytes)
BUFFERS_FOR_ESTIMATE
NUMBER
Cache size for prediction (in terms of buffers)
ESTD_PHYSICAL_READ_
FACTOR
NUMBER
Physical read factor for this cache size, which is the ratio of the number
of estimated physical reads to the number of reads in the real cache. If
there are no physical reads in the real cache, the value of this column is
null.
ESTD_PHYSICAL_READS
NUMBER
Estimated number of physical reads for this cache size
V$DB_OBJECT_CACHE
This view displays database objects that are cached in the library cache. Objects
include tables, indexes, clusters, synonym definitions, PL/SQL procedures and
packages, and triggers.
Column
Datatype
Description
OWNER
VARCHAR2(64)
Owner of the object
NAME
VARCHAR2(1000)
Name of the object
DB_LINK
VARCHAR2(64)
Database link name, if any
NAMESPACE
VARCHAR2(28)
Library cache namespace of the object: TABLE/PROCEDURE, BODY,
TRIGGER, INDEX, CLUSTER, OBJECT
TYPE
VARCHAR2(28)
Type of the object: INDEX, TABLE, CLUSTER, VIEW, SET,
SYNONYM, SEQUENCE, PROCEDURE, FUNCTION, PACKAGE,
PACKAGE BODY, TRIGGER, CLASS, OBJECT, USER, DBLINK
SHARABLE_MEM
NUMBER
Amount of sharable memory in the shared pool consumed by the object
LOADS
NUMBER
Number of times the object has been loaded. This count also increases
when an object has been invalidated.
Dynamic Performance (V$) Views 3-45
V$DB_PIPES
Column
Datatype
Description
EXECUTIONS
NUMBER
Not used
See: "V$SQLAREA" on page 3-163 to see actual execution counts
LOCKS
NUMBER
Number of users currently locking this object
PINS
NUMBER
Number of users currently pinning this object
KEPT
VARCHAR2(3)
(YES | NO) Depends on whether this object has been "kept"
(permanently pinned in memory) with the PL/SQL procedure DBMS_
SHARED_POOL.KEEP
CHILD_LATCH
NUMBER
Child latch number that is protecting the object
V$DB_PIPES
This view displays the pipes that are currently represented in the shared pool for
this instance.
Column
Datatype
Description
OWNERID
NUMBER
The owner ID of the owner if this is a private pipe. NULL otherwise.
NAME
VARCHAR2(1000)
The name of the pipe (for example, SCOTT.PIPE)
TYPE
VARCHAR2(7)
PUBLIC or PRIVATE
PIPE_SIZE
NUMBER
The amount of memory the pipe uses
V$DBFILE
This view lists all datafiles making up the database. This view is retained for
historical compatibility. Use of V$DATAFILE is recommended instead.
Column
Datatype
Description
FILE#
NUMBER
File identifier
NAME
VARCHAR2(513)
Name of the file
See Also: "V$DATAFILE" on page 3-39
V$DBLINK
This view describes all database links (links with IN_TRANSACTION = YES)
opened by the session issuing the query on V$DBLINK. These database links must
be committed or rolled back before being closed.
3-46
Oracle9i Database Reference
V$DISPATCHER
Column
Datatype
Description
DB_LINK
VARCHAR2(128)
Name of the database link
OWNER_ID
NUMBER
Owner of the database link UID
LOGGED_ON
VARCHAR2(3)
Whether the database link is currently logged on
HETEROGENEOUS
VARCHAR2(3)
Whether the database link is heterogeneous
PROTOCOL
VARCHAR2(6)
Communication protocol for the database link
OPEN_CURSORS
NUMBER
Whether there are open cursors for the database link
IN_TRANSACTION
VARCHAR2(3)
Whether the database link is currently in a transaction
UPDATE_SENT
VARCHAR2(3)
Whether there has been an update on the database link
COMMIT_POINT_STRENGTH NUMBER
Commit point strength of the transactions on the database link
V$DELETED_OBJECT
This view displays information about deleted archived logs, datafile copies and
backup pieces from the control file. The only 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
Datatype
Description
RECID
NUMBER
Deleted object record ID
STAMP
NUMBER
Deleted object record stamp
TYPE
VARCHAR2(13)
Identifies the type of deleted object: ARCHIVED LOG, DATAFILE
COPY, BACKUP PIECE, PROXY COPY, BACKUP PIECE
AVAILABLE, BACKUP PIECE EXPIRED, PROXY COPY
AVAILABLE, or PROXY COPY EXPIRED
OBJECT_RECID
NUMBER
Record ID of the deleted object
OBJECT_STAMP
NUMBER
Record timestamp of the deleted object
OBJECT_DATA
NUMBER
Displays additional internal information related to this deleted object.
For internal Oracle use only.
V$DISPATCHER
This view provides information on the dispatcher processes.
Dynamic Performance (V$) Views 3-47
V$DISPATCHER_RATE
Column
Datatype
Description
NAME
VARCHAR2(4)
Name of the dispatcher process
NETWORK
VARCHAR2(128)
Network address of the dispatcher
PADDR
RAW(4 | 8)
Process address
STATUS
VARCHAR2(16)
Status of the dispatcher:
■
WAIT - Idle
■
SEND - Sending a message
■
RECEIVE - Receiving a message
■
CONNECT - Establishing a connection
■
DISCONNECT - Handling a disconnect request
■
BREAK - Handling a break
■
TERMINATE - In the process of terminating
■
ACCEPT - Accepting connections (no further information available)
■
REFUSE - Rejecting connections (no further information available)
ACCEPT
VARCHAR2(3)
Indicates whether this dispatcher is accepting new connections (YES) or
not (NO)
MESSAGES
NUMBER
Number of messages processed by the dispatcher
BYTES
NUMBER
Size (in bytes) of messages processed by the dispatcher
BREAKS
NUMBER
Number of breaks occurring in the connection
OWNED
NUMBER
Number of circuits owned by the dispatcher
CREATED
NUMBER
Number of circuits created by the dispatcher
IDLE
NUMBER
Total idle time for the dispatcher (in hundredths of a second)
BUSY
NUMBER
Total busy time for the dispatcher (in hundredths of a second)
LISTENER
NUMBER
Most recent Oracle error number the dispatcher received from the
listener
CONF_INDX
NUMBER
Zero-based index of the DISPATCHERS configuration used by the
dispatcher
V$DISPATCHER_RATE
This view provides rate statistics for a number of activities performed by the
dispatcher processes. Collected samples have an activity-specific "time-to-live"
(TTL_* columns). Statistics are reported over the following two types of time
intervals:
■
3-48
Current statistics (CUR_ columns)
Oracle9i Database Reference
V$DISPATCHER_RATE
Current statistics use samples collected over the most recent time-to-live
interval.
■
Historical statistics (AVG_ and most of the MAX_ columns)
Historical statistics make use of all samples that are no longer current.
At the time of collection, a sample is current. After the time-to-live has elapsed, the
sample becomes historical. Each type of activity has a specific scale (represented by
the SCALE_* columns) at which the statistics are reported.
Column
Datatype
Description
NAME
CHAR
Name of the dispatcher process
PADDR
RAW(4 | 8)
Address of the dispatcher process
CUR_LOOP_RATE
NUMBER
Rate at which the dispatcher has been iterating through its dispatching
loop, reported over the past TTL_LOOPS, in iterations/SCALE_LOOPS
CUR_EVENT_RATE
NUMBER
Rate at which the dispatcher has been processing dispatcher events,
reported over the past TTL_LOOPS, in events/SCALE_LOOPS. Such
dispatcher events include network events and shared server requests.
CUR_EVENTS_PER_LOOP
NUMBER
Average number of events the dispatcher has been processing in each
iteration through its dispatching loop, reported over the past TTL_
LOOPS, in events/iteration
CUR_MSG_RATE
NUMBER
Rate at which the dispatcher has been relaying messages between
clients and shared servers, reported over the past TTL_MSG, in
messages/SCALE_MSG
CUR_SVR_BUF_RATE
NUMBER
Rate at which the dispatcher has been relaying buffers to shared
servers, reported over the past TTL_SVR_BUF, in messages/SCALE_
SVR_BUF
CUR_SVR_BYTE_RATE
NUMBER
Rate at which the dispatcher has been relaying data to shared servers,
reported over the past TTL_SVR_BUF, in bytes/SCALE_SVR_BUF
CUR_SVR_BYTE_PER_BUF
NUMBER
Average number of data types in each buffer relayed to shared servers,
reported over the past TTL_SVR_BUF, in bytes/buffer
CUR_CLT_BUF_RATE
NUMBER
Rate at which the dispatcher has been relaying buffers to clients,
reported over the past TTL_CLT_BUF, in buffers/SCALE_CLT_BUF
CUR_CLT_BYTE_RATE
NUMBER
Rate at which the dispatcher has been relaying data to clients, reported
over the past TTL_CLT_BUF, in bytes/SCALE_CLT_BUF
CUR_CLT_BYTE_PER_BUF
NUMBER
Average number of data bytes in each buffer relayed to clients, reported
over the past TTL_CLT_BUF, in bytes/buffer
CUR_BUF_RATE
NUMBER
Rate at which the dispatcher has been relaying buffers to either clients
or shared servers, reported over the past TTL_BUF, in bytes/SCALE_
BUF
CUR_BYTE_RATE
NUMBER
Rate at which the dispatcher has been relaying data to either clients or
shared servers, reported over the past TTL_BUF, in bytes/SCALE_BUF
Dynamic Performance (V$) Views 3-49
V$DISPATCHER_RATE
Column
Datatype
Description
CUR_BYTE_PER_BUF
NUMBER
Average number of data bytes in each buffer relayed to either clients or
shared servers, reported over the past TTL_BUF, in bytes/buffer
CUR_IN_CONNECT_RATE
NUMBER
Rate at which the dispatcher has been accepting incoming client
connections, reported over the past TTL_IN_CONNECT, in
connections/SCALE_IN_CONNECT
CUR_OUT_CONNECT_RATE
NUMBER
Rate at which the dispatcher has been establishing outbound
connections, reported over the past TTL_OUT_CONNECT, in
connections/SCALE_OUT_CONNECT
CUR_RECONNECT_RATE
NUMBER
In a connection pooling setup, the rate at which clients have been
reconnecting to the dispatcher, reported over the past TTL_RECONNECT,
in reconnections/SCALE_RECONNECT
MAX_LOOP_RATE
NUMBER
Maximum rate at which the dispatcher has ever iterated through its
dispatching loop, reported in iterations/SCALE_LOOPS, over the
dispatcher’s lifetime excluding the past TTL_LOOPS
MAX_EVENT_RATE
NUMBER
Maximum rate at which the dispatcher has ever processed dispatcher
events, reported in events/SCALE_LOOPS, over the dispatcher’s
lifetime excluding the past TTL_LOOPS
MAX_EVENTS_PER_LOOP
NUMBER
Maximum number of events the dispatcher has ever processed in one
iteration through its dispatching loop, reported in events/iteration,
over the dispatcher’s lifetime
MAX_MSG_RATE
NUMBER
Maximum rate at which the dispatcher has ever relayed messages
between clients and shared servers, reported in messages/SCALE_MSG,
over the dispatcher’s lifetime excluding the past TTL_MSG
MAX_SVR_BUF_RATE
NUMBER
Maximum rate at which the dispatcher has ever relayed buffers to
shared servers, reported in buffers/SCALE_SVR_BUF, over the
dispatcher’s lifetime excluding the past TTL_SVR_BUF
MAX_SVR_BYTE_RATE
NUMBER
Maximum rate at which the dispatcher has ever relayed data to shared
servers, reported in bytes/SCALE_SVR_BUF, over the dispatcher’s
lifetime excluding the past TTL_SVR_BUF
MAX_SVR_BYTE_PER_BUF
NUMBER
Maximum number of data bytes the dispatcher has ever relayed in one
buffer to a client, reported in bytes/buffer, over the dispatcher’s lifetime
MAX_CLT_BUF_RATE
NUMBER
Maximum rate at which the dispatcher has ever relayed buffers to
either clients or shared servers, reported in buffers/SCALE_CLT_BUF,
over the dispatcher’s life time excluding the past TTL_CLT_BUF
MAX_CLT_BYTE_RATE
NUMBER
Maximum rate at which the dispatcher has ever relayed buffers to
clients, reported in bytes/SCALE_CLT_BUF, over the dispatcher’s
lifetime excluding the last TTL_CLT_BUF
MAX_CLT_BYTE_PER_BUF
NUMBER
Maximum number of data bytes the dispatcher has ever relayed in one
buffer to a client, reported in bytes/buffer, over the dispatcher’s lifetime
MAX_BUF_RATE
NUMBER
Maximum rate at which the dispatcher has ever relayed buffers to
either clients or shared servers, reported in buffers/SCALE_BUF, over
the dispatcher’s lifetime, excluding the past TTL_BUF
3-50
Oracle9i Database Reference
V$DISPATCHER_RATE
Column
Datatype
Description
MAX_BYTE_RATE
NUMBER
Maximum rate at which the dispatcher has ever relayed data to either
clients or shared servers, reported in bytes/SCALE_BUF, over the
dispatcher’s lifetime excluding the past TTL_BUF
MAX_BYTE_PER_BUF
NUMBER
Maximum number of data bytes the dispatcher has ever relayed in one
buffer to either a client or a shared server, reported in bytes/buffer, over
the dispatcher’s lifetime
MAX_IN_CONNECT_RATE
NUMBER
Maximum rate at which the dispatcher has ever accepted incoming
client connections, reported in connections/SCALE_IN_CONNECT, over
the dispatcher’s lifetime excluding the past TTL_IN_CONNECT
MAX_OUT_CONNECT_RATE
NUMBER
Maximum rate at which the dispatcher has ever established outbound
connections, reported in connections/SCALE_OUT_CONNECT, over the
dispatcher’s lifetime excluding the past TTL_OUT_CONNECT
MAX_RECONNECT_RATE
NUMBER
In a connection pooling setup, the maximum rate at which clients have
ever reconnected to this dispatcher, reported in reconnections/SCALE_
RECONNECT, over the dispatcher’s lifetime excluding the past TTL_
RECONNECT
AVG_LOOP_RATE
NUMBER
Historical average rate at which the dispatcher has iterated through its
dispatching loop, reported in iterations/SCALE_LOOPS, over the
dispatcher’s lifetime excluding the past TTL_LOOPS
AVG_EVENT_RATE
NUMBER
Historical average rate at which the dispatcher has processed
dispatcher events, reported in events/SCALE_LOOPS, over the
dispatcher’s lifetime excluding the past TTL_LOOPS
AVG_EVENTS_PER_LOOP
NUMBER
Historical average number of events the dispatcher has processed in
one iteration through its dispatching loop, reported in events/iteration,
over the dispatcher’s lifetime excluding the past TTL_LOOPS
AVG_MSG_RATE
NUMBER
Historical average rate at which the dispatcher has relayed messages
between clients and shared servers, reported in messages/SCALE_MSG,
over the dispatcher’s lifetime excluding the past TTL_MSG
AVG_SVR_BUF_RATE
NUMBER
Historical average rate at which the dispatcher has relayed buffers to
shared servers, reported in buffers/SCALE_SVR_BUF, over the
dispatcher’s lifetime excluding the past TTL_SVR_BUF
AVG_SVR_BYTE_RATE
NUMBER
Historical average rate at which the dispatcher has relayed data to
shared servers, reported in bytes/SCALE_SVR_BUF, over the
dispatcher’s lifetime excluding the past TTL_SVR_BUF
AVG_SVR_BYTE_PER_BUF
NUMBER
Historical average number of data bytes per buffer the dispatcher has
relayed to shared servers, reported in bytes/buffer, over the
dispatcher’s lifetime excluding the past TTL_SVR_BUF
AVG_CLT_BUF_RATE
NUMBER
Historical average rate at which the dispatcher has relayed buffers to
clients, reported in buffers/SCALE_CLT_BUF, over the dispatcher’s
lifetime excluding the past TTL_CLT_BUF
AVG_CLT_BYTE_RATE
NUMBER
Historical average rate at which the dispatcher has relayed data to
clients, reported in bytes/SCALE_CLT_BUF, over the dispatcher’s
lifetime excluding the past TTL_CLT_BUF
Dynamic Performance (V$) Views 3-51
V$DISPATCHER_RATE
Column
Datatype
Description
AVG_CLT_BYTE_PER_BUF
NUMBER
Historical average number of data bytes per buffer the dispatcher has
relayed to clients, reported in bytes/buffer, over the dispatcher’s
lifetime excluding the past TTL_CLT_BUF
AVG_BUF_RATE
NUMBER
Historical average rate at which the dispatcher has relayed buffers to
either clients or shared servers, reported in buffers/SCALE_BUF, over
the dispatcher’s lifetime excluding the past TTL_BUF
AVG_BYTE_RATE
NUMBER
Historical average rate at which the dispatcher has relayed data to
either clients or shared servers, reported in bytes/SCALE_BUF, over the
dispatcher’s lifetime excluding the past TTL_BUF
AVG_BYTE_PER_BUF
NUMBER
Historical average number of data bytes per buffer the dispatcher has
relayed to either clients or shared servers, reported in bytes/buffer, over
the dispatcher’s lifetime excluding the past TTL_BUF
AVG_IN_CONNECT_RATE
NUMBER
Historical average rate at which the dispatcher has accepted incoming
client connections, reported in connections/SCALE_IN_CONNECT, over
the dispatcher’s lifetime excluding the past TTL_IN_CONNECT
AVG_OUT_CONNECT_RATE
NUMBER
Historical average rate at which the dispatcher has established
outbound connections, reported in connections/SCALE_OUT_CONNECT,
over the dispatcher’s lifetime excluding the past TTL_OUT_CONNECT
AVG_RECONNECT_RATE
NUMBER
In a connection pooling setup, the historical average rate at which
clients have reconnected to this dispatcher, reported in
reconnections/SCALE_RECONNECT, over the dispatcher’s lifetime
excluding the past TTL_RECONNECT
TTL_LOOPS
NUMBER
Time-to-live for "loops" samples, reported in hundredths of a second.
Default is 10 minutes.
TTL_MSG
NUMBER
Time-to-live for "messages" samples, reported in hundredths of a
second. Default is 10 seconds.
TTL_SVR_BUF
NUMBER
Time-to-live for "buffers to servers" samples, reported in hundredths of
a second. Default is 1 second.
TTL_CLT_BUF
NUMBER
Time-to-live for "buffers to clients" samples, reported in hundredths of a
second. Default is 1 second.
TTL_BUF
NUMBER
Time-to-live for "buffers to clients/servers" samples, reported in
hundredths of a second. Default is 1 second.
TTL_IN_CONNECT
NUMBER
Time-to-live for "inbound connections" samples, reported in hundredths
of a second. Default is 10 minutes.
TTL_OUT_CONNECT
NUMBER
Time-to-live for "outbound connections" samples, reported in
hundredths of a second. Default is 10 minutes.
TTL_RECONNECT
NUMBER
Time-to-live for "reconnections" samples, reported in hundredths of a
second. Default is 10 minutes.
SCALE_LOOPS
NUMBER
Scale for "loops" statistics, reported in hundredths of a second. Default
is 1 minute.
SCALE_MSG
NUMBER
Scale for "messages" statistics, reported in hundredths of a second.
Default is 1 second.
3-52
Oracle9i Database Reference
V$ENQUEUE_LOCK
Column
Datatype
Description
SCALE_SVR_BUF
NUMBER
Scale for "buffers to servers" statistics, reported in hundredths of a
second. Default is 1/10 second.
SCALE_CLT_BUF
NUMBER
Scale for "buffers to clients" statistics, reported in hundredths of a
second. Default is 1/10 second.
SCALE_BUF
NUMBER
Scale for "buffers to clients/servers" statistics, reported in hundredths of
a second. Default is 1/10 second.
SCALE_IN_CONNECT
NUMBER
Scale for "inbound connections" statistics, reported in hundredths of a
second. Default is 1 minute.
SCALE_OUT_CONNECT
NUMBER
Scale for "outbound connections" statistics, reported in hundredths of a
second. Default is 1 minute.
SCALE_RECONNECT
NUMBER
Scale for "reconnections" statistics, reported in hundredths of a second.
Default is 1 minute.
V$ENABLEDPRIVS
This view displays which privileges are enabled. These privileges can be found in
the table SYS.SYSTEM_PRIVILEGES_MAP.
Column
Datatype
Description
PRIV_NUMBER
NUMBER
Numeric identifier of enabled privileges
V$ENQUEUE_LOCK
This view displays all locks owned by enqueue state objects. The columns in this
view are identical to the columns in V$LOCK.
See Also: "V$LOCK" on page 3-77
Column
Datatype
Description
ADDR
RAW(4 | 8)
Address of lock state object
KADDR
RAW(4 | 8)
Address of lock
SID
NUMBER
Identifier for session holding or acquiring the lock
TYPE
VARCHAR2(2)
Type of lock. Lists user and system types that can have locks.
ID1
NUMBER
Lock identifier #1 (depends on type)
ID2
NUMBER
Lock identifier #2 (depends on type)
Dynamic Performance (V$) Views 3-53
V$ENQUEUE_STAT
Column
Datatype
Description
LMODE
NUMBER
Lock mode in which the session holds the lock:
REQUEST
NUMBER
■
0 - none
■
1 - null (NULL)
■
2 - row-S (SS)
■
3 - row-X (SX)
■
4 - share (S)
■
5 - S/Row-X (SSX)
■
6 - exclusive (X)
Lock mode in which the process requests the lock:
■
0 - none
■
1 - null (NULL)
■
2 - row-S (SS)
■
3 - row-X (SX)
■
4 - share (S)
■
5 - S/Row-X (SSX)
■
6 - exclusive (X)
CTIME
NUMBER
Time since current mode was granted
BLOCK
NUMBER
The lock is blocking another lock
V$ENQUEUE_STAT
This view displays statistics on the number of enqueue (lock) requests for each type
of lock.
Column
Datatype
Description
INST_ID
NUMBER
Database instance number
EQ_TYPE
VARCHAR2(2)
Type of enqueue requested
TOTAL_REQ#
NUMBER
Total number of enqueue requests or enqueue conversions for this type
of enqueue
TOTAL_WAIT#
NUMBER
Total number of times an enqueue request or conversion resulted in a
wait
SUCC_REQ#
NUMBER
Number of times an enqueue request or conversion was granted
FAILED_REQ#
NUMBER
Number of times an enqueue request or conversion failed
CUM_WAIT_TIME
NUMBER
Total amount of time (in milliseconds) spent waiting for the enqueue or
enqueue conversion
3-54
Oracle9i Database Reference
V$FALSE_PING
V$EVENT_NAME
This view contains information about wait events.
Column
Datatype
Description
EVENT#
NUMBER
The number of the wait event
NAME
VARCHAR2(64)
The name of the wait event
PARAMETER1
VARCHAR2(64)
The description of the first parameter for the wait event
PARAMETER2
VARCHAR2(64)
The description of the second parameter for the wait event
PARAMETER3
VARCHAR2(64)
The description of the third parameter for the wait event
V$EXECUTION
This view displays information on parallel execution.
Column
Datatype
Description
PID
NUMBER
Session ID
DEPTH
NUMBER
The depth
FUNCTION
VARCHAR2(10)
Session serial number
TYPE
VARCHAR2(7)
Name of the OBJECT_NODE in plan table
NVALS
NUMBER
Elapsed time for OBJECT_NODE
VAL1
NUMBER
The value for number 1
VAL2
NUMBER
The value for number 2
SEQH
NUMBER
A sequence
SEQL
NUMBER
A sequence
V$FALSE_PING
V$FALSE_PING is an Oracle9i Real Application Clusters view. This view displays
buffers that may be getting false pings. That is, buffers pinged more than 10 times
that are protected by the same lock as another buffer that pinged more than 10
times. Buffers identified as getting false pings can be remapped in "GC_FILES_TO_
LOCKS" to reduce lock collisions.
See Also: "GC_FILES_TO_LOCKS" on page 1-60 and Oracle9i Real
Application Clusters Concepts
Dynamic Performance (V$) Views 3-55
V$FAST_START_SERVERS
Column
Datatype
Description
FILE#
NUMBER
Datafile identifier number (to find the filename, query DBA_DATA_
FILES or V$DBFILES)
BLOCK#
NUMBER
Block number
STATUS
VARCHAR2(5)
Status of the block:
■
FREE - Not currently in use
■
XCUR - Exclusive
■
SCUR - Shared current
■
CR - Consistent read
■
READ - Being read from disk
■
MREC - In media recovery mode
■
IREC - In instance recovery mode
XNC
NUMBER
Number of PCM lock conversions from Exclusive mode due to
contention with another instance. This column is obsolete but is
retained for historical compatibility.
FORCED_READS
NUMBER
Number of times the block had to be reread from disk because another
instance had forced it out of this instance’s cache by requesting the
PCM lock on the block in exclusive mode
FORCED_WRITES
NUMBER
Number of times DBWR had to write this block to disk because this
instance had used the block and another instance had requested the
lock on the block in a conflicting mode
NAME
VARCHAR2(30)
Name of the database object containing the block
PARTITION_NAME
VARCHAR2(30)
NULL for non-partitioned objects
KIND
VARCHAR2(15)
Type of database object
OWNER#
NUMBER
Owner number
LOCK_ELEMENT_ADDR
RAW(4 | 8)
Address of the lock element that contains the PCM lock that is covering
the buffer. If more than one buffer has the same address, then these
buffers are covered by the same PCM lock.
LOCK_ELEMENT_NAME
NUMBER
Name of the lock that contains the PCM lock that is covering the buffer
LOCK_ELEMENT_CLASS
NUMBER
Lock element class
V$FAST_START_SERVERS
V$FAST_START_SERVERS provides information about all the recovery slaves
performing parallel transaction recovery.
See Also: Oracle9i User-Managed Backup and Recovery Guide
3-56
Oracle9i Database Reference
V$FILE_CACHE_TRANSFER
Column
Datatype
Description
STATE
VARCHAR2(11)
State of the server (IDLE or RECOVERING)
UNDOBLOCKSDONE
NUMBER
Number of undo blocks done so far
PID
NUMBER
Process ID
V$FAST_START_TRANSACTIONS
V$FAST_START_TRANSACTIONS contains information about the progress of the
transactions that Oracle is recovering.
See Also: Oracle9i User-Managed Backup and Recovery Guide
Column
Datatype
Description
USN
NUMBER
The undo segment number of the transaction
SLT
NUMBER
The slot within the rollback segment
SEQ
NUMBER
The incarnation number of the slot
STATE
VARCHAR2(16)
The state of the transaction may be TO BE RECOVERED, RECOVERED,
or RECOVERING
UNDOBLOCKSDONE
NUMBER
The number of undo blocks completed on this transaction
UNDOBLOCKSTOTAL
NUMBER
The total number of undo blocks that need recovery
PID
NUMBER
The ID of the current server it has been assigned to
CPUTIME
NUMBER
The time for which recovery has progressed, in seconds
PARENTUSN
NUMBER
The undo segment number of the parent transaction in PDML
PARENTSLT
NUMBER
The slot of the parent transaction in PDML
PARENTSEQ
NUMBER
The sequence number of the parent transaction in PDML
V$FILE_CACHE_TRANSFER
V$FILE_CACHE_TRANSFER displays the number of blocks pinged per datafile. This
information in turn can be used to determine access patterns to existing datafiles
and deciding new mappings from datafile blocks to PCM locks.
Column
Datatype
Description
FILE_NUMBER
NUMBER
Number of the datafile
X_2_NULL
NUMBER
Number of lock conversions from Exclusive-to-NULL for all blocks in
the file
Dynamic Performance (V$) Views 3-57
V$FILESTAT
Column
Datatype
Description
X_2_NULL_FORCED_WRITE NUMBER
Number of forced writes that occur for blocks of the specified file due to
Exclusive-to-NULL conversions
X_2_NULL_FORCED_STALE NUMBER
Number of times a block in the file was made STALE due to
Exclusive-to-NULL conversions
X_2_S
NUMBER
Number of lock conversions from Exclusive-to-Shared for all blocks in
the file
X_2_S_FORCED_WRITE
NUMBER
Number of forced writes that occur for blocks of the specified file due to
Exclusive-to-Shared conversions
S_2_NULL
NUMBER
Number of lock conversions from Shared-to-NULL for all blocks in the
file
S_2_NULL_FORCED_STALE NUMBER
Number of times a block in the file was made STALE due to
Shared-to-NULL conversions
RBR
NUMBER
Number of times the instance received a reuse block range cross
instance call for this file
RBR_FORCED_WRITE
NUMBER
Number of blocks written due to reuse block range cross instance calls
for this file
RBR_FORCED_STALE
NUMBER
Number of times a block in this file was made STALE due to reuse block
range cross instance calls
NULL_2_X
NUMBER
Number of lock conversions from NULL-to-Exclusive for all blocks of
the specified file
S_2_X
NUMBER
Number of lock conversions from Shared-to-Exclusive for all blocks of
the specified file
NULL_2_S
NUMBER
Number of lock conversions from NULL-to-Shared for all blocks of the
specified file
V$FILESTAT
This view contains information about file read/write statistics.
Column
Datatype
Description
FILE#
NUMBER
Number of the file
PHYRDS
NUMBER
Number of physical reads done
PHYWRTS
NUMBER
Number of times DBWR is required to write
PHYBLKRD
NUMBER
Number of physical blocks read
PHYBLKWRT
NUMBER
Number of blocks written to disk, which may be the same as PHYWRTS
if all writes are single blocks
SINGLEBLKRDS
NUMBER
Number of single block reads
3-58
Oracle9i Database Reference
V$FIXED_VIEW_DEFINITION
Column
Datatype
Description
READTIM
NUMBER
Time (in hundredths of a second) spent doing reads if the TIMED_
STATISTICS parameter is true; 0 if false
WRITETIM
NUMBER
Time (in hundredths of a second) spent doing writes if the TIMED_
STATISTICS parameter is true; 0 if false
SINGLEBLKRDTIM
NUMBER
Cumulative single block read time (in hundredths of a second)
AVGIOTIM
NUMBER
Average time (in hundredths of a second) spent on I/O, if the TIMED_
STATISTICS parameter is true; 0 if false
LSTIOTIM
NUMBER
Time (in hundredths of a second) spent doing the last I/O, if the
TIMED_STATISTICS parameter is true; 0 if false
MINIOTIM
NUMBER
Minimum time (in hundredths of a second) spent on a single I/O, if the
TIMED_STATISTICS parameter is true; 0 if false
MAXIORTM
NUMBER
Maximum time (in hundredths of a second) spent doing a single read, if
the TIMED_STATISTICS parameter is true; 0 if false
MAXIOWTM
NUMBER
Maximum time (in hundredths of a second) spent doing a single write,
if the TIMED_STATISTICS parameter is true; 0 if false
V$FIXED_TABLE
This view displays all dynamic performance tables, views, and derived tables in the
database. Some V$ tables (for example, V$ROLLNAME) refer to real tables and are
therefore not listed.
Column
Datatype
Description
NAME
VARCHAR2(30)
Name of the object
OBJECT_ID
NUMBER
Identifier of the fixed object
TYPE
VARCHAR2(5)
Object type (TABLE | VIEW)
TABLE_NUM
NUMBER
Number that identifies the dynamic performance table if it is of type
TABLE
V$FIXED_VIEW_DEFINITION
This view contains the definitions of all the fixed views (views beginning with V$).
Use this table with caution. Oracle tries to keep the behavior of fixed views the
same from release to release, but the definitions of the fixed views can change
without notice. Use these definitions to optimize your queries by using indexed
columns of the dynamic performance tables.
Dynamic Performance (V$) Views 3-59
V$GC_ELEMENT
Column
Datatype
Description
VIEW_NAME
VARCHAR2(30)
The name of the fixed view
VIEW_DEFINITION
VARCHAR2(2000)
The definition of the fixed view
V$GC_ELEMENT
This is an Oracle9i Real Application Clusters view. There is one entry in V$GC_
ELEMENT for each PCM lock that is used by the buffer cache. The name of the PCM
lock that corresponds to a lock element is {’BL’, indx, class}.
See Also: Oracle9i Real Application Clusters Concepts
Column
Datatype
Description
GC_ELEMENT_ADDR
RAW(4 | 8)
Address of the lock element that contains the PCM lock that is covering
the buffer. If more than one buffer has the same address, then these
buffers are covered by the same PCM lock.
INDX
NUMBER
Platform specific lock manager identifier
CLASS
NUMBER
Platform specific lock manager identifier
GC_ELEMENT_NAME
NUMBER
Name of the lock that contains the PCM lock that is covering the buffer
MODE_HELD
NUMBER
Platform dependent value for lock mode held; often: 3 = share; 5 =
exclusive
BLOCK_COUNT
NUMBER
Number of blocks covered by PCM lock
RELEASING
NUMBER
Nonzero if PCM lock is being downgraded
ACQUIRING
NUMBER
Nonzero if PCM lock is being upgraded
INVALID
NUMBER
Nonzero if PCM lock is invalid (a lock may become invalid after a
system failure)
FLAGS
NUMBER
Process level flags for the lock element
V$GC_ELEMENTS_WITH_COLLISIONS
This is an Oracle9i Real Application Clusters view. Use this view to find the locks
that protect multiple buffers, each of which has been either force-written or
force-read at least 10 times. It is very likely that those buffers are experiencing false
pings due to being mapped to the same lock.
See Also: Oracle9i Real Application Clusters Concepts
3-60
Oracle9i Database Reference
V$GES_BLOCKING_ENQUEUE
Column
Datatype
Description
GC_ELEMENT_ADDR
RAW(4 | 8)
Address of the lock element that contains the PCM lock covering the
buffer. If more than one buffer has the same address, then these buffers
are covered by the same PCM lock.
V$GCSHVMASTER_INFO
V$GCSHVMASTER_INFO describes the current and previous master instances and
the number of re-masterings of Global Cache Service resources except those
belonging to files mapped to a particular master.
Column
Datatype
Description
HV_ID
NUMBER
PCM hash value ID
CURRENT_MASTER
NUMBER
Master instance of this PCM hash value ID
PREVIOUS_MASTER
NUMBER
Previous master instance of this PCM hash value ID
REMASTER_CNT
NUMBER
Number of times this has been remastered
V$GCSPFMASTER_INFO
V$GCSPFMASTER_INFO describes the current and previous master instances and
the number of re-masterings of Global Cache Service resources belonging to files
mapped to instances.
Column
Datatype
Description
FILE_ID
NUMBER
File number
CURRENT_MASTER
NUMBER
Master instance of this file
PREVIOUS_MASTER
NUMBER
Previous master instance of this file
REMASTER_CNT
NUMBER
Number of times this has been remastered
V$GES_BLOCKING_ENQUEUE
This Oracle9i Real Application Clusters view describes all locks currently known to
lock manager that are being blocked or blocking others. The output of this view is a
subset of the output from V$GES_ENQUEUE.
See Also: "V$GES_ENQUEUE" on page 3-64 for a description of
all locks known to the lock manager
Dynamic Performance (V$) Views 3-61
V$GES_BLOCKING_ENQUEUE
Column
Datatype
Description
HANDLE
RAW(4 | 8)
Lock pointer
GRANT_LEVEL
VARCHAR2(9)
Granted level of the lock
REQUEST_LEVEL
VARCHAR2(9)
Requested level of the lock
RESOURCE_NAME1
VARCHAR2(30)
Resource name for the lock
RESOURCE_NAME2
VARCHAR2(30)
Resource name for the lock
PID
NUMBER
Process identifier which holds the lock
TRANSACTION_ID0
NUMBER
Lower 4 bytes of the transaction identifier where the lock belongs to
TRANSACTION_ID1
NUMBER
Upper 4 bytes of the transaction identifier where the lock belongs to
GROUP_ID
NUMBER
Group identifier for the lock
OPEN_OPT_DEADLOCK
NUMBER
1 if DEADLOCK open option is set, otherwise 0
OPEN_OPT_PERSISTENT
NUMBER
1 if PERSISTENT open option is set, otherwise 0
OPEN_OPT_PROCESS_
OWNED
NUMBER
1 if PROCESS_OWNED open option is set, otherwise 0
OPEN_OPT_NO_XID
NUMBER
1 if NO_XID open option is set, otherwise 0
CONVERT_OPT_GETVALUE
NUMBER
1 if GETVALUE convert option is set, otherwise 0
CONVERT_OPT_PUTVALUE
NUMBER
1 if PUTVALUE convert option is set, otherwise 0
CONVERT_OPT_NOVALUE
NUMBER
1 if NOVALUE convert option is set, otherwise 0
CONVERT_OPT_DUBVALUE
NUMBER
1 if DUBVALUE convert option is set, otherwise 0
CONVERT_OPT_NOQUEUE
NUMBER
1 if NOQUEUE convert option is set, otherwise 0
CONVERT_OPT_EXPRESS
NUMBER
1 if EXPRESS convert option is set, otherwise 0
CONVERT_OPT_
NODEADLOCKWAIT
NUMBER
1 if NODEADLOCKWAIT convert option is set, otherwise 0
CONVERT_OPT_
NODEADLOCKBLOCK
NUMBER
1 if NODEADLOCKBLOCK convert option is set, otherwise 0
WHICH_QUEUE
NUMBER
Which queue the lock is currently located. 0 for NULL queue; 1 for
GRANTED queue; 2 for CONVERT queue.
STATE
VARCHAR2(64)
State of lock as owner sees it
AST_EVENT0
NUMBER
Last AST event
OWNER_NODE
NUMBER
Node identifier
BLOCKED
NUMBER
1 if this lock request is blocked by others, otherwise 0
BLOCKER
NUMBER
1 if this lock is blocking others, otherwise 0
3-62
Oracle9i Database Reference
V$GES_CONVERT_REMOTE
V$GES_CONVERT_LOCAL
V$GES_CONVERT_LOCAL displays average convert time, count information, and
timed statistics for remote GES enqueue operations.
Column
Datatype
Description
INST_ID
NUMBER
ID of the instance
CONVERT_TYPE
VARCHAR2(64)
Conversion types are listed in Table 3–3
AVERAGE_CONVERT_TIME
NUMBER
Average conversion time for each type of lock operation (in 100th of a
second)
CONVERT_COUNT
NUMBER
The number of operations
V$GES_CONVERT_REMOTE
V$GES_CONVERT_REMOTE displays average convert time, count information, and
timed statistics for remote GES enqueue operations.
Column
Datatype
Description
INST_ID
NUMBER
ID of the instance
CONVERT_TYPE
VARCHAR2(64)
Conversion types are listed in Table 3–3
AVERAGE_CONVERT_TIME
NUMBER
■
NULL -> SS - NULL mode to subshared mode
■
NULL -> SX - NULL mode to shared exclusive mode
■
NULL -> S - NULL mode to shared mode
■
NULL -> SSX - NULL mode to subshared exclusive mode
■
NULL -> X - NULL mode to exclusive mode
■
SS -> SX - Subshared mode to shared exclusive mode
■
SS -> S - Subshared mode to shared mode
■
SS -> SSX - Subshared mode to subshared exclusive mode
■
SS -> X - Subshared mode to exclusive mode
■
SX -> S - Shared exclusive mode to shared mode
■
SX -> SSX - Shared exclusive mode to subshared exclusive mode
■
SX -> X - Shared exclusive mode to exclusive mode
■
S -> SX - Shared mode to shared exclusive mode
■
S -> SSX - Shared mode to subshared exclusive mode
■
S -> X - Shared mode to exclusive mode
■
SSX -> X - Sub-shared exclusive mode to exclusive mode
Average conversion time for each type of lock operation (in hundredths
of a second)
Dynamic Performance (V$) Views 3-63
V$GES_ENQUEUE
Column
Datatype
Description
CONVERT_COUNT
NUMBER
Number of operations
V$GES_ENQUEUE
This Oracle9i Real Application Clusters view describes all lo