Thursday, July 17, 2008

DBA_OBJECTS

DBA_OBJECTS describes all objects in the database. Its columns are the same as those in "ALL_OBJECTS".
Related Views
·         ALL_OBJECTS describes all objects accessible to the current user.
·         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)
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 the Oracle Database assigns to row objects in object tables in the system.
OBJECT_TYPE
VARCHAR2(19)

Type of the object (such as TABLE, INDEX)
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 statement (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)

Indicates whether the name of this object was system generated (Y) or not (N)
SECONDARY
VARCHAR2(1)

Whether this is a secondary object created by the ODCIIndexCreate method of the Oracle Data Cartridge (Y | N)
NAMESPACE
NUMBER

Namespace for the object
EDITION_NAME
VARCHAR2(30)

Name of the Application Edition where the object is identified

Note:
1.       For indexes of types IOT - NESTED and LOB, you can get the whole information from DBA_INDEXES rather than using DBA_OBJECTS.
2.       When TIMESTAMP and LAST_DDL_TIME columns will differ? (Metalink note 309235.1)

·         LAST_DDL_TIME:Timestamp for the last modification of the object resulting from a DDL command (including grants and revokes)
·         TIMESTAMP:Timestamp for the specification of the object

Example 1:   
Created a table called YY

SQL> select TO_CHAR(last_ddl_time, 'DD-MON-YYYY HH24:MI:SS') DDL, timestamp from
dba_objects where object_name='YY';

 DDL                        TIMESTAMP
--------------------    -------------------
30-MAR-2005 21:08:34    2005-03-30:21:08:34                

As it can be seen when the table is created both has the same value

SQL> GRANT SELECT ON YY TO PUBLIC;   <-----------DDL performed
Grant succeeded.

SQL> select TO_CHAR(last_ddl_time,'DD-MON-YYYY HH24:MI:SS') DDL,timestamp from
dba_objects where object_name='YY';

DDL                         TIMESTAMP
--------------------     -------------------
30-MAR-2005 21:13:44    2005-03-30:21:08:34                  

It is seen that last_ddl_time is different. TIMESTAMP remains same as object creation

Now we will see under what circumstances last_ddl_time and timestamp will differ.
1.       When DDL is performed on the dependent objects of the table. For example when an index is created or altered.
2.       When a table is truncated.
3.       When roles/privileges are granted/revoked.

Example 2: A small example to better understand point 1 :

SQL> CREATE TABLE YY(A NUMBER);
Table created.

SQL> select TO_CHAR(last_ddl_time,'DD-MON-YYYY HH24:MI:SS') DDL,timestamp from
dba_objects where object_name='YY';

DDL                                         TIMESTAMP
--------------------                    -------------------
31-MAR-2005 15:16:54                    2005-03-31:15:16:54

SQL> CREATE INDEX YYI ON YY(A);
Index created.

SQL> select TO_CHAR(last_ddl_time,'DD-MON-YYYY HH24:MI:SS') DDL, timestamp from
dba_objects where object_name='YY';

 DDL                                                TIMESTAMP
--------------------                              --------------
31-MAR-2005 15:21:53                          2005-03-31:15:16:54

It can be clearly seen that though we did not perform any DDL operation on the table but the creation of an index on the table changed its last_ddl_time. Timestamp does not change.

3.       Scripts using DBA_OBJECTS
--Distribution of objects and data: Which schemas are taking up all of the space

select  obj.owner, obj_cnt, decode(seg_size, NULL, 0, seg_size) "size MB"
from    (select owner, count(*) obj_cnt from dba_objects group by owner) obj,
        (select owner, ceil(sum(bytes)/1024/1024) seg_size   
         from dba_segments group by owner) seg
where  obj.owner  = seg.owner(+)
order  by 3 desc ,2 desc, 1
--Is JAVA installed in the database? This will return 9000'ish if it is...

select        count(*)
from   dba_objects
where object_type like '%JAVA%'
and    owner = 'SYS'
--to determining which segments have many buffers in the pool

SELECT   o.OBJECT_NAME, COUNT(*) NUMBER_OF_BLOCKS
  FROM   DBA_OBJECTS o, V$BH bh
 WHERE   o.DATA_OBJECT_ID = bh.OBJD
   AND   o.OWNER != 'SYS'
GROUP BY o.OBJECT_NAME
ORDER BY COUNT(*) desc;
-- report the type and count of objects by user
 
select owner,
       sum(decode(object_type,'TABLE',1,0)) tables,
       sum(decode(object_type,'INDEX',1,0)) indexes,
       sum(decode(object_type,'SYNONYM',1,0)) synonyms,
       sum(decode(object_type,'SEQUENCE',1,0)) sequences,
       sum(decode(object_type,'VIEW',1,0)) views,
       sum(decode(object_type,'CLUSTER',1,0)) clusters,
       sum(decode(object_type,'DATABASE LINK',1,0)) database_links,
       sum(decode(object_type,'PACKAGE',1,0)) packages,
       sum(decode(object_type,'PACKAGE BODY',1,0)) package_bodies,
       sum(decode(object_type,'PROCEDURE',1,0)) procedures
from dba_objects
group by owner;
-- The script produces information about locks being held or waited on in the database
 
 
select B.SID, C.USERNAME, C.OSUSER, C.TERMINAL,
       DECODE(B.ID2, 0, A.OBJECT_NAME,'Trans-'||to_char(B.ID1)) OBJECT_NAME,
       B.TYPE,
       DECODE(B.LMODE,0,'--Waiting--',
                      1,'Null',
                      2,'Row Share',
                      3,'Row Excl',
                      4,'Share',
                      5,'Sha Row Exc',
                      6,'Exclusive',
                        'Other') "Lock Mode",
       DECODE(B.REQUEST,
                      0,' ',
                      1,'Null',
                      2,'Row Share',
                      3,'Row Excl',
                      4,'Share',
                      5,'Sha Row Exc',
                      6,'Exclusive',
                     'Other') "Req Mode"
  from DBA_OBJECTS A, V$LOCK B, V$SESSION C
where  A.OBJECT_ID(+) = B.ID1
  and  B.SID = C.SID
  and  C.USERNAME is not null
order by B.SID, B.ID2;
-- The script generates scripts to compile all invalid objects in the database
 
select
    decode(OBJECT_TYPE, 'PACKAGE BODY', 'alter package ' || OWNER||'.'||OBJECT_NAME || ' compile body;',
                                        'alter ' || OBJECT_TYPE || ' ' || OWNER||'.'||OBJECT_NAME || ' compile;' )
from  dba_objects
where STATUS = 'INVALID' and
      OBJECT_TYPE in ( 'PACKAGE BODY', 'PACKAGE', 'FUNCTION', 'PROCEDURE', 'TRIGGER', 'VIEW' )
order by OBJECT_TYPE, OBJECT_NAME;

Oracle data dictionary views


More Oracle DBA tips, please visit Oracle DBA Tips 

DBA_SEGMENTS

Oracle 11gR1

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

NULL

Description

OWNER

VARCHAR2(30)


Username of the segment owner

SEGMENT_NAME

VARCHAR2(81)


Name, if any, of the segment

PARTITION_NAME

VARCHAR2(30)


Object Partition Name (Set to NULL for non-partitioned objects)

SEGMENT_TYPE

VARCHAR2(18)


Type of segment:

· NESTED TABLE

· TABLE

· TABLE PARTITION

· CLUSTER

· LOBINDEX

· INDEX

· INDEX PARTITION

· LOBSEGMENT

· TABLE SUBPARTITION

· INDEX SUBPARTITION

· LOB PARTITION

· LOB SUBPARTITION

· ROLLBACK

· TYPE2 UNDO

· DEFERRED ROLLBACK

· TEMPORARY

· CACHE

· SPACE HEADER

· UNDEFINED

SEGMENT_SUBTYPE

VARCHAR2(10)


Subtype of LOB segment: SECUREFILE, ASSM, MSSM, and NULL

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

MAX_SIZE

NUMBER


Maximum number of blocks allowed in the segment

RETENTION

VARCHAR2(7)


Retention option for SECUREFILE segment

MINRETENTION

NUMBER


Minimum retention duration for SECUREFILE 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

ORA-04031

ORA-04031: unable to allocate string bytes of shared memory ("string","string","string","string")

Cause: More shared memory is needed than was allocated in the shared pool.

Action: If the shared pool is out of memory, either use the dbms_shared_pool package to pin large packages, reduce your use of shared memory, or increase the amount of available shared memory by increasing the value of the INIT.ORA parameters "shared_pool_reserved_size" and "shared_pool_size". If the large pool is out of memory, increase the INIT.ORA parameter "large_pool_size".


All Oracle errors in the blog can be found at: Oracle errors
All ESRI ArcSDE errors in the blog can found at: ArcSDE Errors

ORA-03135

ORA-03135: connection lost contact

Cause: 1) Server unexpectedly terminated or was forced to terminate.
2) Server timed out the connection.

Action: 1) Check if the server session was terminated.
2) Check if the timeout parameters are set properly in sqlnet.ora.



All Oracle errors in the blog can be found at: Oracle errors
All ESRI ArcSDE errors in the blog can found at: ArcSDE Errors

ORA-01149

ORA-01149: cannot shutdown - file string has online backup set

Cause: An attempt to shut down normally found that an online backup is still in progress.

Action: End the backup of the offending tablespace and retry this command.



All Oracle errors in the blog can be found at: Oracle errors
All ESRI ArcSDE errors in the blog can found at: ArcSDE Errors

Tuesday, July 15, 2008

ORA-01861

ORA-01861: literal does not match format string

Cause: Literals in the input must be the same length as literals in the format string (with the exception of leading whitespace). If the "FX" modifier has been toggled on, the literal must match exactly, with no extra whitespace.

Action: Correct the format string to match the literal.

sde.log:
db_sda_execute_stmt::OCIStmtExecute (1861)
.
[01/28/2008 09:52:34;SdeId=6036064;Client=mypc] db_array_fetch_attrs OCI Fetch Error (1861)
[01/28/2008 09:52:34;SdeId=6036064;Client=mypc] load_buffer error -51


All Oracle errors in the blog can be found at: Oracle errors
All ESRI ArcSDE errors in the blog can found at: ArcSDE Errors

ORA-01858

Error: ORA-01858: a non-numeric character found where a digit was expected
Cause: You tried to enter a date value using a specified date format, but you entered a non-numeric character where a numeric character was expected.
Action: The options to resolve this Oracle error are:
Check the date formats recognized by the to_date function. Correct the date value and retry.

sde.log:
db_sda_execute_stmt::OCIStmtExecute (1858)
.
[01/23/2008 13:42:08;SdeId=6021520;Client=STRINGER] db_array_fetch_attrs OCI Fetch Error (1858)
[01/23/2008 13:42:08;SdeId=6021520;Client=STRINGER] load_buffer error -51



All Oracle errors in the blog can be found at: Oracle errors
All ESRI ArcSDE errors in the blog can found at: ArcSDE Errors

ORA-01847

ORA-01847: day of month must be between 1 and last day of month

Cause: The day of the month listed in a date is invalid for the specified month. The day of the month (DD) must be between 1 and the number of days in that month.

Action: Enter a valid day value for the specified month.

sde.log:

db_sda_execute_stmt::OCIStmtExecute (1847)
.
[01/23/2008 13:40:22;SdeId=6021520;Client=STRINGER] db_array_fetch_spix_recs OCI Fetch Error (1847)
[01/23/2008 13:40:22;SdeId=6021520;Client=STRINGER] load_buffer error -51

ORA-01659

ORA-01659: unable to allocate MINEXTENTS beyond string in tablespace string

Cause: Failed to find sufficient contiguous space to allocate MINEXTENTS for the segment being created.

Action: Use ALTER TABLESPACE ADD DATAFILE to add additional space to the tablespace or retry with smaller value for MINEXTENTS, NEXT or PCTINCREASE.


All Oracle errors in the blog can be found at: Oracle errors
All ESRI ArcSDE errors in the blog can found at: ArcSDE Errors

More Oracle DBA tips, please visit Oracle DBA Tips 

ORA-01650

ORA-01650: unable to extend rollback segment name by num in tablespace name

Cause: Failed to allocate extent for the rollback segment in tablespace.

Action: Use the ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the specified tablespace.

Solution:


--Querying DBA_SEGMENTS for the rollback segments will determine if the rollback segments are at their maximum extent:

SELECT segment_name, extents, max_extents FROM dba_segments WHERE segment_type='ROLLBACK';

--If your rollback segments are at max extents, you can increase the max number of extents as follows:

ALTER ROLLBACK SEGMENT rollback_segment_name STORAGE (MAXEXTENTS xx);

--It may also be likely that your rollback segment tablespace is full. Increase the size of the tablespace by adding another datafile to the tablespace:

ALTER TABLESPACE ts_name ADD DATAFILE '/directory/file_name' SIZE xxxM AUTOEXTEND ON NEXT xxxM MAXSIZE xxxM;


All Oracle errors in the blog can be found at: Oracle errors
All ESRI ArcSDE errors in the blog can found at: ArcSDE Errors

ORA-01441

ORA-01441: cannot decrease column length because some value is too big

Cause: An ALTER TABLE MODIFY statement attempted to decrease the size of a character field containing data. A column whose maximum size is to be decreased must contain only NULL values.
Action: Set all values in column to NULL before decreasing the maximum size.



All Oracle errors in the blog can be found at: Oracle errors
All ESRI ArcSDE errors in the blog can found at: ArcSDE Errors

ORA-01089

ORA-01089: immediate shutdown in progress - no operations are permitted
Cause: The SHUTDOWN IMMEDIATE command was used to shut down a running ORACLE instance, so your operations have been terminated.
Action: Wait for the instance to be restarted, or contact your DBA.

sde.log:
[07/15/2008 13:02:02;SdeId=243827;Client=lawn] db_array_fetch_attrs OCI Fetch Error (1089)
[07/15/2008 13:02:02;SdeId=243827;Client=lawn] load_buffer error -51
db_sda_execute_stmt::OCIStmtExecute (3135)
.
[07/15/2008 13:08:00;SdeId=0;Client=GIOMGR] DBMS error code: 3114
ORA-03114: not connected to ORACLE


[07/15/2008 13:08:00;SdeId=0;Client=GIOMGR] Error in DB_instance_get_status(), SQL: SELECT num_prop_value FROM SDE.server_config WHERE prop_name = :prop_name

Monday, July 14, 2008

How to change Oracle hidden parameters


Thank you for visiting Spatial DBA - Oracle and ArcSDE.

Please visit Oracle DBA Tips (http://www.oracledbatips.com) for more Oracle DBA Tips.
==================================================================
 


Oracle hidden parameters start with "_". They can not be viewed from the output of show parameter,
or by querying v$parameter unless and until they are set explicitly in init.ora.

If you want to view all the hidden parameters and their default values, the following query
could be of help,

SELECT a.ksppinm "Parameter", b.ksppstvl "Session Value", c.ksppstvl "Instance Value"
FROM x$ksppi a, x$ksppcv b, x$ksppsv c
WHERE a.indx = b.indx AND a.indx = c.indx AND a.ksppinm LIKE '/_%' escape '/';

To see the listing of all hidden parameters query,

select *
from SYS.X$KSPPI
where substr(KSPPINM,1,1) = '_';

It is never recommended to modify Oracle hidden parameters without the assistance of Oracle Support. Changing these parameters may lead to high performance degradation and other problems in the database.

Methods to change Oracle hidden parameters:

1) If you use pfile, you can entry of the hidden parameter into initSID.ora, and restart the instance.

"_shared_pool_reserved_pct"=10
2) If you want to set for the current session, use ALTER SESSION SET ...

3) If you want to set it permanently and you are using spfile, use ALTER SYSTEM SET ...... SCOPE=BOTH
Some hidden parameters cannot be changed in MEMORY, such as _shared_pool_reserved_pct. See below:
SQL> show parameter pfile
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
spfile string /fs/u01/oracle/product/1
0.2.0.2ee/dbs/spfilemydb.ora
SQL> alter system set "_shared_pool_reserved_pct"=10 scope=both;
alter system set "_shared_pool_reserved_pct"=10 scope=both
*
ERROR at line 1:
ORA-02095: specified initialization parameter cannot be modified
SQL> alter system set "_shared_pool_reserved_pct"=10 scope=memory;
alter system set "_shared_pool_reserved_pct"=10 scope=memory
*
ERROR at line 1:
ORA-02095: specified initialization parameter cannot be modified
SQL> alter system set "_shared_pool_reserved_pct"=10 scope=spfile;
System altered.
If SCOPE=SPFILE, the instance needs to be restarted.

Database upgrading methods

There are four different upgrade methods to upgrade Oracle database to the new Oracle database release:

1) Database Upgrade Assistant (DBUA)
2) Manual Upgrade
3) Export/Import
4) Data Copying

1) DBUA (Database Upgrade Assistant)

The Database Upgrade Assistant (DBUA) interactively steps you through the upgrade process and configures the database for the new Oracle Database 10g release. The DBUA automates the upgrade process by performing all of the tasks normally performed manually. The DBUA makes appropriate recommendations for configuration options such as tablespaces and redo logs. You can then act on these recommendations. This method is very easy and user friendly. But if any error occurs it will take time to diagnose the error as the upgrade process is automatically by the upgrade assistant.

2) Manual upgrade

A manual upgrade consists of running SQL scripts and utilities from a command line to upgrade a database to the new Oracle Database 10g release. A manual upgrade gives you finer control over the upgrade process as it is done step by step manually. So if any error occurs, it is easy to diagnose the error. While a manual upgrade gives you finer control over the upgrade process, it is more susceptible to error if any of the upgrade or pre-upgrade steps are either not followed or are performed out of order.
When manually upgrading a database, perform the following pre-upgrade steps:

  • Analyze the database using the Pre-Upgrade Information Tool. The Upgrade Information Tool is SQL script that ships with the new Oracle Database 10g release, and must be run in the environment of the database being upgraded.
    The Upgrade Information Tool displays warnings about possible upgrade issues with the database. It also displays information about required initialization parameters for the new Oracle Database 10g release.
  • Prepare the new Oracle Home.
  • Perform a backup of the database.

Depending on the release of the database being upgraded, you may need to perform additional pre-upgrade steps (adjust the parameter file for the upgrade, remove obsolete initialization parameters and adjust initialization parameters that might cause upgrade problems).

3) Export/Import

The Export/Import upgrade method does not change the current database, which enables the database to remain available throughout the upgrade process. However, if a consistent snapshot of the database is required (for data integrity or other purposes), then the database must run in restricted mode or must otherwise be protected from changes during the export procedure. Because the current database can remain available, you can, for example, keep an existing production database running while the new Oracle Database 10g database is being built at the same time by Export/Import. During the upgrade, to maintain complete database consistency, changes to the data in the database cannot be permitted without the same changes to the data in the new Oracle Database.

Most importantly, the Export/Import operation results in a completely new database. Although the current database ultimately contains a copy of the specified data, the upgraded database may perform differently from the original database. For example, although Export/Import creates an identical copy of the database, other factors, such as disk placement of data and unset tuning parameters, may cause unexpected performance problems.

Upgrading an entire database by using Export/Import can take a long time, especially compared to using the DBUA or performing a manual upgrade. Therefore, you may need to schedule the upgrade during non-peak hours or make provisions for propagating to the new database any changes that are made to the current database during the upgrade.

4) Data Copying

You can copy data from one Oracle Database to another using database links. For example, you can create new tables and fill the tables with data by using the INSERT INTO statement and the CREATE TABLE ... AS statement. Copying data and Export/Import offer the same advantages for upgrading. Using either method, you can defragment data files and restructure the database by creating new tablespaces or modifying existing tables or tablespaces. In addition, you can copy only specified database objects or users.

Copying data, however, unlike Export/Import, enables the selection of specific rows of tables to be placed into the new database. Copying data is a good method for copying only part of a database table. In contrast, using Export/Import, you can copy only entire tables

Friday, July 11, 2008

Quick Reference to Auditing Information


1.       Database Audit mode
SQL> show parameter audit

NAME                                 TYPE        VALUE
------------------------------------ ----------- -----------------------------
audit_file_dest                      string      /u02/oracle/admin/mydb/adump
audit_sys_operations                 boolean     FALSE
audit_syslog_level                   string
audit_trail                          string      TRUE
2.       What Statements are being audited ?
To set audit:
AUDIT [option] [BY USER|SESSION|ACCESS] [WHENEVER {NOT} SUCCESSFUL]
To check audit result:
select * from dba_stmt_audit_opts where USER_NAME='...';

Note:
AUDIT_OPTION: from table STMT_AUDIT_OPTION_MAP;
SUCCESS:      'BY SESSION', 'BY ACCESS' or 'NOT SET'
FAILURE:      ""
3.       What Privileges are being audited ?
To set audit:
AUDIT [option] [BY user|SESSION|ACCESS] [WHENEVER {NOT} SUCCESSFUL]
To check audit result:
select * from dba_priv_audit_opts where USER_NAME='...';

Note:
PRIVILEGE: from SYSTEM_PRIVILEGE_MAP
SUCCESS:   'BY SESSION', 'BY ACCESS' or 'NOT SET'
FAILURE:   ""
4.       What Objects are being audited ?
To set Auditing:
AUDIT [object_option] ON [schema].object|DEFAULT [BY SESSION|ACCESS] [WHENEVER {NOT} SUCCESSFUL]
To check audit result:
select * from dba_obj_audit_opts where owner='..' and OBJECT_NAME='...';
select * from all_def_audit_opts;

Note:

Values of columns (ALT AUD COM DEL GRA IND INS LOC REN SEL UPD REF EXE FBK REA) are X/Y:
-    is no option set
-    X is when successful
-    S set by session
-    Y is when Unsuccessful
-    A set by access
5.       Audit results
-    Raw results go to DBA_AUDIT_TRAIL (view on SYS.AUD$ table).
-    Main where columns are: USERNAME, TIMESTAMP, OWNER
-    For underlying results see: Select STATEMENT, TIMESTAMP, ACTION, USERID from AUD$;

6.       Auditing administrative connections
The administrative user connections (CONNECT / AS SYSDBA or CONNECT / AS SYSOPER) are always logged regardless of audit setting. On UNIX platforms these are logged to *.aud files in $ORACLE_HOME/rdbms/audit regardless of any init.ora parameter settings.
Last updated: 2009-September-23, Tuesday

TABLE_PRIVILEGE_MAP

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)
Oracle 11.1.0.6.0
select * from table_PRIVILEGE_MAP order by privilege;
PRIVILEGE
NAME
0
ALTER
1
AUDIT
2
COMMENT
3
DELETE
4
GRANT
5
INDEX
6
INSERT
7
LOCK
8
RENAME
9
SELECT
10
UPDATE
11
REFERENCES
12
EXECUTE
16
CREATE
17
READ
18
WRITE
20
ENQUEUE
21
DEQUEUE
22
UNDER
23
ON COMMIT REFRESH
24
QUERY REWRITE
26
DEBUG
27
FLASHBACK
28
MERGE VIEW
29
USE
30
FLASHBACK ARCHIVE