Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.server -> The Oracle Inconsistencies List -- please add to it!
Why do your fingers want to type "select name from v$logfile" or
"create tabespace data1 default storage (pct_increase 0)" even though
they don't work? Because Oracle makes it harder than it has to be.
V$SGA memory structure names and associated initSID.ora parameters do not match
Variable Size 12221104 bytes ---> shared_pool_size Database Buffers 16777216 bytes ---> db_block_buffers Redo Buffers 1048576 bytes ---> log_buffer
db_block_buffers initSID.ora parameter is plural log_buffer initSID.ora parameter is singular
the majority of DBA_... views are plural -- a few are singular.
Example: DBA_TABLESPACES
the majority of V$... views are singular -- a few are plural.
Example: V$TABLESPACE
DBA_OBJECTS is plural, DBA_OBJECT_SIZE is singular
Oracle uses the term "tablespace" as the generic description for a
storage area
but the term is misleading because a "TABLEspace" can hold
tables, indexes, rollbacks, and temporary segments.
STORAGE clause does not use underscores but DBA_* dictionary views do:
PCTFREE PCT_FREE PCTUSED PCT_USED INITRANS INI_TRANS MAXTRANS MAX_TRANS INITIAL INITIAL_EXTENT NEXT NEXT_EXTENT MINEXTENTS MIN_EXTENTS MAXEXTENTS MAX_EXTENTS PCTINCREASE PCT_INCREASE FREELISTS FREELISTSFREELIST GROUPS FREELIST_GROUPS STORAGE() clause is mostly about extent allocation. However, FREELISTS and FREELIST GROUPS are about blocks but are inside the STORAGE() clause unlike PCTFREE and PCTUSED.
DEFINE uses = but PL/SQL DECLARE section uses :=
V$SQLTEXT table name but SQL_TEXT field name
Analyze one object is DBMS_DDL. Analyze multiple objects with
DBMS_UTIL.
dbms_ddl.analyze_object()
dbms_util.analyze_schema()
Spelled "RESTRICT" in one command and "RESTRICTED" in another
STARTUP RESTRICT
ALTER SYSTEM ENABLE RESTRICTED SESSION
SVRMGRL and SQLDBA uses "command=@myscript.sql" but SQLPLUS uses
"@myscript.sql"
formally called "rollback segment" but most statistics call it "undo"
User name is not spelled the same way in all the tables:
TABLE_NAME COLUMN_NAME ------------------------------ ------------------------------ DBA_AUDIT_EXISTS USERNAME DBA_AUDIT_OBJECT USERNAME DBA_AUDIT_SESSION USERNAME DBA_AUDIT_STATEMENT USERNAME DBA_AUDIT_TRAIL USERNAME DBA_DB_LINKS USERNAME DBA_EXP_FILES USER_NAME DBA_PRIV_AUDIT_OPTS USER_NAME DBA_STMT_AUDIT_OPTS USER_NAME DBA_TS_QUOTAS USERNAME DBA_USERS USERNAME V$OPEN_CURSOR USER_NAME V$PROCESS USERNAME V$PWFILE_USERS USERNAME V$SESSION USERNAME AUD$ USERID three different ways of spelling "average" in field names table: V_$ROLLSTAT field: AVESHRINK
table: V_$SYSTEM_EVENT field: AVERAGE_WAIT
table: DBA_TABLES field: AVG_SPACE
optimizer_goal in "alter session set ..." optimizer_mode in initSID.ora
In V$STATNAME, CPU is sometimes uppercase, sometimes lowercase STATISTIC# NAME
most views have all uppercase field values, a few (V$PARAMETER, V$STATNAME) have lowercase field values
log_archive_start initSID.ora parameter.
"log archive start" command instead of an "alter system set ... "
FILE_ID in DBA_DATA_FILES but FILE# in V$DATAFILE FILE_NAME in DBA_DATA_FILES but NAME in V$DATAFILE
NAME in V$CONTROLFILE
MAME in V$DATAFILE
MEMBER in V$LOGFILE
One command uses "INCLUDING CONTENTS" while the other uses "CASCADE" DROP TABLESPACE DATA1 INCLUDING CONTENTS; DROP USER JOHNDOE CASCADE; initSID.ora has no underscore but alert_SID.ora has an underscore Received on Tue Aug 11 1998 - 22:27:51 CDT
![]() |
![]() |