Search This Blog

Thursday, 29 June 2017

Standby SYNC check

Check redo received and applied on standby:
STANDBY SIDE:

SELECT ARCH.THREAD# "Thread", ARCH.SEQUENCE# "Last Sequence Received",
APPL.SEQUENCE# "Last Sequence Applied", (ARCH.SEQUENCE# - APPL.SEQUENCE#) "Difference"
FROM
(SELECT THREAD# ,SEQUENCE# FROM V$ARCHIVED_LOG WHERE (THREAD#,FIRST_TIME ) IN
(SELECT THREAD#,MAX(FIRST_TIME) FROM V$ARCHIVED_LOG GROUP BY THREAD#)) ARCH,
(SELECT THREAD# ,SEQUENCE# FROM V$LOG_HISTORY WHERE (THREAD#,FIRST_TIME ) IN
(SELECT THREAD#,MAX(FIRST_TIME) FROM V$LOG_HISTORY GROUP BY THREAD#)) APPL
WHERE
ARCH.THREAD# = APPL.THREAD#
ORDER BY 1;

    Thread Last Sequence Received Last Sequence Applied Difference
---------- ---------------------- --------------------- ----------
         1                  56063                 54996       1067
         2                     85                    85          0


Primary:

select ads.dest_id,max(sequence#) "Current Sequence",
 max(log_sequence) "Last Archived"
   from v$archived_log al, v$archive_dest ad, v$archive_dest_status ads
   where ad.dest_id=al.dest_id
   and al.dest_id=ads.dest_id
   and al.resetlogs_change#=(select max(resetlogs_change#) from v$archived_log )
 group by ads.dest_id;


   DEST_ID Current Sequence Last Archived
---------- ---------------- -------------
         1              678           678
         2              678           679

Check for GAP on Standby:
Primary:
select max(sequence#) from v$log_history;

Standby :
select max(sequence#) from v$log_history; 


How to find the GAP on Standby with primay:


SELECT THREAD#, LOW_SEQUENCE#, HIGH_SEQUENCE# FROM V$ARCHIVE_GAP;

 Both primary and standby:

SELECT SEQUENCE#,APPLIED FROM V$ARCHIVED_LOG
ORDER BY SEQUENCE#; 

select sequence#, first_time, next_time, applied from v$archived_log;

========================================================================
If you start a foreground session, control is not returned to the command prompt until recovery is canceled by another session.
To start Redo Apply in the background, include the DISCONNECT keyword on the SQL statement. For example:

SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;

or

SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING current ARCHIVED LOGFILE DISCONNECT;
     ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT;



This statement starts a detached server process and immediately returns control to the user. While the managed recovery process is performing recovery in the background, the foreground process that issued the RECOVER statement can continue performing other tasks. This command does not disconnect the current SQL session.
=======================================================================
To stop Redo Apply, issue the following SQL statement:

SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;


--Monitoring Redo Apply on Physical Standby Databases---

SELECT PROTECTION_MODE, PROTECTION_LEVEL,DATABASE_ROLE ROLE, SWITCHOVER_STATUS FROM V$DATABASE;

SELECT PROCESS, STATUS, THREAD#, SEQUENCE#,BLOCK#, BLOCKS FROM V$MANAGED_STANDBY;

select sequence#, applied from v$archived_log order by sequence# ;

select THREAD#,SEQUENCE#,STANDBY_DEST,ARCHIVED,APPLIED from v$archived_log;
select RECOVERY_MODE from v$archive_dest_status;

select ERROR,STATUS from v$archive_dest_status;

SELECT MESSAGE FROM V$DATAGUARD_STATUS;

SELECT FS_FAILOVER_STATUS "FSFO STATUS",FS_FAILOVER_CURRENT_TARGET TARGET,FS_FAILOVER_THRESHOLD THRESHOLD,FS_FAILOVER_OBSERVER_PRESENT "OBSERVER PRESENT" FROM V$DATABASE;

SELECT THREAD#, SEQUENCE#, FIRST_CHANGE#,NEXT_CHANGE# FROM V$ARCHIVED_LOG;

SELECT THREAD#, SEQUENCE#, FIRST_CHANGE#,NEXT_CHANGE# FROM V$LOG_HISTORY;

SELECT DEST_ID, APPLIED_SCN FROM V$ARCHIVE_DEST WHERE TARGET='STANDBY';
col DEST_NAME format a30;

SELECT DEST_NAME,STATUS,APPLIED_SEQ#,SYNCHRONIZATION_STATUS,GAP_STATUS from V$ARCHIVE_DEST_STATUS where DEST_NAME='STANDBY_ARCHIVE_DEST';

============================================
Restore Point:

col name format a30
col value format a30

SELECT name, value  FROM gv$parameter WHERE name LIKE '%flashback%';

SELECT flashback_on, log_mode FROM v$database;

-- normal restore point
CREATE RESTORE POINT BOPPUDI_1_BEFORE_DEMAGE;

col name format a15
col time format a32
SELECT NAME, SCN, TIME, DATABASE_INCARNATION#,GUARANTEE_FLASHBACK_DATABASE, STORAGE_SIZE FROM V$RESTORE_POINT WHERE GUARANTEE_FLASHBACK_DATABASE='YES';

NAME                                  SCN TIME                                DATABASE_INCARNATION# GUA STORAGE_SIZE
------------------------------ ---------- ----------------------------------- --------------------- --- ------------
BOPPUDI_1_BEFORE_DEMAGE                       1.4690E+13 23-JUN-18 05.28.57.000000000 AM                         8 YES            0
BOPPUDI_2_BEFORE_DEMAGE                       1.4690E+13 23-JUN-18 08.39.53.000000000 AM                         8 YES   4.2950E+10


HOW TO RECOVER FROM RESTORE POINT:
-----------------------------------------------------------
SELECT NAME, SCN, TIME, DATABASE_INCARNATION#,GUARANTEE_FLASHBACK_DATABASE, STORAGE_SIZE FROM V$RESTORE_POINT WHERE GUARANTEE_FLASHBACK_DATABASE='YES' ;

shutdown immediate;

startup mount;

flashback database to restore point before_damage;

alter database open resetlogs;


DROP RESTORE POINT:
-------------------------------------
DROP RESTORE POINT BOPPUDI_RESTORE;





Friday, 3 March 2017

DBMS_METADATA.GET_DDL PACKAGE


DBMS_METADSATA package is used to get DDL of a particular object:



select dbms_metadata.get_ddl('DB_LINK','OBJECT_NAME','OWNER') from dual;
EXAMPLE:
select dbms_metadata.get_ddl('DB_LINK','CMIACC_CMIDEV','ESO_USER') from dual;

select dbms_metadata.get_ddl('MATERIALIZED_VIEW','OBJECT_NAME','OWNER') from dual;
EXAPPLE:
select dbms_metadata.get_ddl('MATERIALIZED_VIEW','MV_REPORT_PLANS','CMIACC') from dual;

select dbms_metadata.get_ddl('CLUSTER','OBJECT_NAME','SYS') from dual;

select dbms_metadata.get_ddl('CONTEXT','OBJECT_NAME') from dual;

select dbms_metadata.get_ddl('DB_LINK','OBJECT_NAME','PUBLIC') from dual;

select dbms_metadata.get_ddl('FUNCTION','OBJECT_NAME','SCOTT') from dual;

select dbms_metadata.get_ddl('INDEX','OBJECT_NAME','SYSTEM') from dual;

select dbms_metadata.get_ddl('JAVA_SOURCE','OBJECT_NAME','ADAM') from dual

select dbms_metadata.get_ddl('JAVA_SOURCE','OBJECT_NAME','SYS') from dual

select dbms_metadata.get_ddl('LIBRARY','OBJECT_NAME','SYS') from dual;

select dbms_metadata.get_ddl('MATERIALIZED_VIEW_LOG','OBJECT_NAME','SYS') from dual;

select dbms_metadata.get_ddl('OPERATOR','OBJECT_NAME') from dual;

select dbms_metadata.get_ddl('OPERATOR','OBJECT_NAME','SYS') from dual;

select dbms_metadata.get_ddl('PACKAGE','OBJECT_NAME') from dual;

select dbms_metadata.get_ddl('PACKAGE','OBJECT_NAME','SYS') from dual;

select dbms_metadata.get_ddl('PACKAGE_BODY','OBJECT_NAME','PERFSTAT') from dual;

select dbms_metadata.get_ddl('PROCEDURE','OBJECT_NAME','SYSTEM') from dual;

select dbms_metadata.get_ddl('SEQUENCE','OBJECT_NAME','PERFSTAT') from dual;

select dbms_metadata.get_ddl('SYNONYM','OBJECT_NAME','PUBLIC') from dual;

select dbms_metadata.get_ddl('TABLE','OBJECT_NAME','SYSTEM') from dual;

select dbms_metadata.get_ddl('TABLESPACE','USERS') from dual;

select dbms_metadata.get_ddl('TRIGGER','OBJECT_NAME','SYSTEM') from dual;

select dbms_metadata.get_ddl('TYPE','OBJECT_NAME','SYS') from dual;

select dbms_metadata.get_ddl('TYPE_BODY','OBJECT_NAME','SYS') from dual;

select dbms_metadata.get_ddl('VIEW','OBJECT_NAME','SYS') from dual;

select dbms_metadata.get_ddl('VIEW','OBJECT_NAME') from dual;

select dbms_metadata.get_ddl('PACKAGE','OBJECT_NAME','SYS') from dual;


Extract DDL for Users:

Let’s use DBMS_METADATA.GET_DDL package to extract CREATE USER DDL.
SQL> select dbms_metadata.get_ddl ('USER',username) as col1 from dba_users where username = 'SCOTT';

SYSTEM_GRANT:
select dbms_metadata.get_granted_ddl ('SYSTEM_GRANT',username) as col1 from dba_users where username  = 'SCOTT';

OBJECT_GRANT:
select dbms_metadata.get_granted_ddl('OBJECT_GRANT',username) as col1 from dba_users where username = 'SCOTT';

ROLES_GRANTED_TO_USERS: 
select dbms_metadata.get_granted_ddl('ROLE_GRANT',username) as col1 from dba_users where username  = 'SCOTT';

Tuesday, 7 February 2017

Recreating spfile on ASM storage from pfile

1. try to screw up the db parameters
SQL> show parameter memory
NAME TYPE VALUE
———————————— ———– ——————————
hi_shared_memory_address integer 0
memory_max_target big integer 1520M
memory_target big integer 1520M
shared_memory_address integer 0
SQL> alter system set memory_max_target=0 scope=spfile;
System altered.
2. now bounce the instance, db will complain about the new settings
SQL> shutdown
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup
ORA-01078: failure in processing system parameters
ORA-00837: Specified value of MEMORY_TARGET greater than MEMORY_MAX_TARGET
3. in my case the spfile sits on ASM
ASMCMD> ls -l spfile*
Type Redund Striped Time Sys Name
N spfileorcl.ora => +DATA/ORCL/PARAMETERFILE/spfile.267.744731331
4. what we need to do is creating a pfile from spfile then modify parameter back to valid value, then start db from pfile
1). With db not up, we can create pfile from spfile:
SQL> create pfile from spfile=’+DATA/orcl/spfileorcl.ora’;
2). modify the value in pfile ‘initorcl.ora’
$ vi initorcl.ora
*.memory_max_target=1583349760
3). startup db with pfile
SQL>startup mount –now it will use the pfile
5. create the new spfile to ASM storage from “good” pfile
SQL> create spfile=’+DATA/ORCL/spfileorcl.ora’ from pfile;
File created.
6. watch the file name in ASM storage has been changed, which means we just had a new spfile:
ASMCMD> ls -l spfile*
Type Redund Striped Time Sys Name
N spfileorcl.ora => +DATA/ORCL/PARAMETERFILE/spfile.267.744733351
7. now change the pfile back to be the “bootstrap” of correct spfile
$ cat initorcl.ora
spfile=’+DATA/ORCL/spfileorcl.ora’
8. restart the database, it will pickup the correct spfile again
$ sqlplus / as sysdba
SQL> startup
ORACLE instance started.
Total System Global Area 1586708480 bytes
Fixed Size 2213736 bytes
Variable Size 973080728 bytes
Database Buffers 603979776 bytes
Redo Buffers 7434240 bytes
Database mounted.
Database opened.
SQL> show parameter spfile
NAME TYPE VALUE
———————————— ———– ——————————
spfile string +DATA/orcl/spfileorcl.ora
SQL> show parameter memory
NAME TYPE VALUE
———————————— ———– ——————————
hi_shared_memory_address integer 0
memory_max_target big integer 1520M
memory_target big integer 1520M
shared_memory_address integer 0

Wednesday, 26 June 2013

Script to find ASM Disk and Diskgroup Space Utilization , ASM Operations in Progress

 To find the free space in an ASM disk :
select group_number, disk_number, name, failgroup, create_date, path, total_mb,free_mb from v$asm_disk;

To find the free space in an ASM diskgroup :
select name, group_number, name, type, state, total_mb, free_mb from v$asm_diskgroup;

To see the current ASM operations in Progress :
select group_number, operation, state, power, actual, sofar, est_work, est_rate, est_minutes from v$asm_operation;

Migrate database from file system to ASM

TO Migrate the database files from disk
to asm disk is as follows,
1.configure flash recovery area.
2.Migrate datafiles to ASM.
3.Control file to ASM.
4.Create Temporary tablespace.
5.Migrate Redo logfiles
6.Migrate spfile to ASM.


step 1:Configure flash recovery area.

SQL> connect sys/sys@prod1 as sysdba
Connected.
SQL> alter database disable block change tracking;

Database altered.

SQL> alter system set db_recovery_file_dest_size=500m;

System altered.

SQL> alter system set db_recovery_file_dest=’+RECOVERYDEST’;

System altered


step 2 and 3: Migrate data files and control file
to ASM.

use RMAN to migrate the data files to ASM disk groups.
All data files will be migrated to the newly created disk group, DATA

SQL> alter system set db_create_file_dest='+DATA';

System altered.

SQL> alter system set db_create_online_log_dest='+DATA';

System altered.

SQL> alter system set control_files='+DATA/ctf1.dbf' scope=spfile;

System altered.

SQL> shu immediate

[oracle@rac1 bin]$ ./rman target /


RMAN> startup nomount

Oracle instance started


RMAN> restore controlfile from '/u01/new/oracle/oradata/mydb/control01.ctl';

Starting restore at 08-DEC-09

allocated channel: ORA_DISK_1

channel ORA_DISK_1: SID=146 device type=DISK

channel ORA_DISK_1: copied control file copy

output file name=+DATA/ctf1.dbf

Finished restore at 08-DEC-09

RMAN> alter database mount;

database mounted

released channel: ORA_DISK_1

RMAN> backup as copy database format '+DATA';
Starting backup at 08-DEC-09

allocated channel: ORA_DISK_1

channel ORA_DISK_1: SID=146 device type=DISK

channel ORA_DISK_1: starting datafile copy

input datafile file number=00001 name=/u01/new/oracle/oradata/mydb/system01.dbf

output file name=+DATA/mydb/datafile/system.257.705063763 tag=TAG20091208T110241 RECID=1 STAMP=705064274

channel ORA_DISK_1: datafile copy complete, elapsed time: 00:08:39

channel ORA_DISK_1: starting datafile copy

input datafile file number=00002 name=/u01/new/oracle/oradata/mydb/sysaux01.dbf

output file name=+DATA/mydb/datafile/sysaux.258.705064283 tag=TAG20091208T110241 RECID=2 STAMP=705064812

channel ORA_DISK_1: datafile copy complete, elapsed time: 00:08:56

channel ORA_DISK_1: starting datafile copy

input datafile file number=00003 name=/u01/new/oracle/oradata/mydb/undotbs01.dbf

output file name=+DATA/mydb/datafile/undotbs1.259.705064821 tag=TAG20091208T110241 RECID=3 STAMP=705064897

channel ORA_DISK_1: datafile copy complete, elapsed time: 00:01:25

channel ORA_DISK_1: starting datafile copy

copying current control file

output file name=+DATA/mydb/controlfile/backup.260.705064907 tag=TAG20091208T110241 RECID=4 STAMP=705064912

channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:07

channel ORA_DISK_1: starting datafile copy

input datafile file number=00004 name=/u01/new/oracle/oradata/mydb/users01.dbf

output file name=+DATA/mydb/datafile/users.261.705064915 tag=TAG20091208T110241 RECID=5 STAMP=705064915

channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:03

channel ORA_DISK_1: starting full datafile backup set

channel ORA_DISK_1: specifying datafile(s) in backup set

including current SPFILE in backup set

channel ORA_DISK_1: starting piece 1 at 08-DEC-09

channel ORA_DISK_1: finished piece 1 at 08-DEC-09

piece handle=+DATA/mydb/backupset/2009_12_08/nnsnf0_tag20091208t110241_0.262.705064919 tag=TAG20091208T110241 comment=NONE

channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01

Finished backup at 08-DEC-09

RMAN> switch database to copy;

datafile 1 switched to datafile copy "+DATA/mydb/datafile/system.257.705063763"

datafile 2 switched to datafile copy "+DATA/mydb/datafile/sysaux.258.705064283"

datafile 3 switched to datafile copy "+DATA/mydb/datafile/undotbs1.259.705064821"

datafile 4 switched to datafile copy "+DATA/mydb/datafile/users.261.705064915"

RMAN> alter database open;
database opened

RMAN> exit

Recovery Manager complete.


SQL> conn sys/oracle as sysdba

Connected.

SQL> select tablespace_name,file_name from dba_data_files;

TABLESPACE_NAME FILE_NAME

------------------------------ ---------------------------------------------

USERS +DATA/mydb/datafile/users.261.705064915

UNDOTBS1 +DATA/mydb/datafile/undotbs1.259.705064821

SYSAUX +DATA/mydb/datafile/sysaux.258.705064283

SYSTEM +DATA/mydb/datafile/system.257.705063763



SQL> select name from v$controlfile;


NAME
----

+DATA/ctf1.dbf

NO 16384 594

step 4:Migrate temp tablespace to ASM.

SQL> alter tablespace temp add tempfile size 100m;

Tablespace altered.

SQL> select file_name from dba_temp_files;

FILE_NAME

---------------------------------------------

+DATA/mydb/tempfile/temp.263.705065455

otherwise,
Create temporary tablespace in ASM disk group.

SQL> CREATE TABLESPACE temp1 TEMPFILE ‘+diskgroup1’;

SQL> alter database default temporary tablespace temp1;

Database altered.


step 5:Migrate redo logs to ASM.

SQL> select member,group# from v$logfile;

MEMBER GROUP#

-------------------------------------------------- ----------

/u01/new/oracle/oradata/mydb/redo03.log 3

/u01/new/oracle/oradata/mydb/redo02.log 2

/u01/new/oracle/oradata/mydb/redo01.log 1

SQL> alter database add logfile group 4 size 5m;

Database altered.

SQL> alter database add logfile group 5 size 5m;

Database altered.

SQL> alter database add logfile group 6 size 5m;

Database altered.

SQL> select member,group# from v$logfile;

MEMBER GROUP#

-------------------------------------------------- ----------

/u01/new/oracle/oradata/mydb/redo03.log 3

/u01/new/oracle/oradata/mydb/redo02.log 2

/u01/new/oracle/oradata/mydb/redo01.log 1

+DATA/mydb/onlinelog/group_4.264.705065691 4

+DATA/mydb/onlinelog/group_5.265.705065703 5

+DATA/mydb/onlinelog/group_6.266.705065719 6

SQL> alter system switch logfile;

System altered.

SQL> alter database drop logfile group 2;

Database altered.

SQL> alter database drop logfile group 3;

Database altered.

SQL> alter database drop logfile group 4;

Database altered.

SQL> alter database drop logfile group 1;

Database altered.

Add additional control file.

If an additional control file is required for redundancy,

you can create it in ASM as you would on any other filesystem.

SQL> connect sys/sys@prod1 as sysdba
Connected to an idle instance.
SQL> startup mount
ORACLE instance started.

SQL> alter database backup controlfile to '+DATA/cf2.dbf';

Database altered.

SQL> alter system set control_files='+DATA/cf1.dbf '
,'+DATA/cf2.dbf' scope=spfile;

System altered.

SQL> shutdown immediate;
ORA-01109: database not open

Database dismounted.
ORACLE instance shut down.
SQL> startup
ORACLE instance started.

SQL> select name from v$controlfile;

NAME
---------------------------------------
+DATA/cf1.dbf
+DATA/cf2.dbf

step 6:Migrate spfile to ASM:

Create a copy of the SPFILE in the ASM disk group.
In this example, the SPFILE for the migrated database will be stored as +DISK/spfile.

If the database is using an SPFILE already, then run these commands:

run {
BACKUP AS BACKUPSET SPFILE;
RESTORE SPFILE TO "+DISK/spfile";
}


If you are not using an SPFILE, then use CREATE SPFILE
from SQL*Plus to create the new SPFILE in ASM.
For example, if your parameter file is called /private/init.ora,
use the following command:

SQL> create spfile='+DISK/spfile' from pfile='/private/init.ora';



After successfully migrating all the data files
over to ASM, the old data files are no longer
needed and can be removed. Your single-instance
database is now running on ASM!

These RMAN SQL queries will all find the number of days since the last database backup:

 -- *****************************************
-- SQL for v$backup_set to see last backup
-- *****************************************

select *
    from
    v$backup_set
where
    completion_time > sysdate-7
order by
    completion_time desc;

-- *****************************************
-- SQL for rc_backup_set to see most recent backup
-- *****************************************

select *
from
    rc_backup_set
where
    completion_time > sysdate-7
order by
    completion_time desc;

-- *****************************************
-- Display most recently completed RMAN backup
-- *****************************************

select *
from
    rc_backup_set
where
    backup_type = 'D'
and
    controlfile_included = 'BACKUP'
order by
    completion_time desc

-- *****************************************
-- Display newest_backupset_time for RMAN backup
-- *****************************************

select
    db_name,
    newest_backup_time
from
    rman.rc_backupset_summary 
where
    dn_name = 'DBNAME';


-- *****************************************
-- You can also outer join rc_backupset_summary
-- into rc_database to see the RMAN latest backup start time:
-- *****************************************

select
    name,
    max(start_time)
from
    rman.rc_database     d,
    rman.rc_backup_set  s
where
    db_id(+) = dbid
group by
    name
order by 2 desc;

-- *****************************************
-- Display RMAN backupo status start and end times:
-- *****************************************

select
    operation,
    status,
    object_type,
    to_char(start_time,'mm/dd/yyyy:hh:mi:ss') as start_time,
    to_char(end_time,'mm/dd/yyyy:hh:mi:ss') as end_time
from
    v$rman_status
where
    start_time > SYSDATE -1
and
    operation = 'BACKUP'
and
    object_type = 'DB FULL'
order by
    start_time desc;

LOCK Query

SELECT sn.username, m.sid, m.type,
   DECODE(m.lmode, 0, 'None'
                 , 1, 'Null'
                 , 2, 'Row Share'
                 , 3, 'Row Excl.'
                 , 4, 'Share'
                 , 5, 'S/Row Excl.'
                 , 6, 'Exclusive'
                 , lmode, ltrim(to_char(lmode,'990'))) lmode,
   DECODE(m.request, 0, 'None'
                 , 1, 'Null'
                 , 2, 'Row Share'
                 , 3, 'Row Excl.'
                 , 4, 'Share'
                 , 5, 'S/Row Excl.'
                 , 6, 'Exclusive'
                 , request, ltrim(to_char(request,'990'))) request,
         obj1.object_name objname, obj2.object_name objname
FROM v$session sn, V$lock m, dba_objects obj1, dba_objects obj2
WHERE sn.sid = m.sid
AND m.id1 = obj1.object_id (+)
AND m.id2 = obj2.object_id (+)
     AND lmode != 4
ORDER BY id1,id2, m.request
/

#############

select /*+ ordered use_nl(lob pn ses) */
       decode(lob.kglobtyp, 0, 'NEXT OBJECT', 1, 'INDEX', 2, 'TABLE', 3, 'CLUSTER',
                      4, 'VIEW', 5, 'SYNONYM', 6, 'SEQUENCE',
                      7, 'PROCEDURE', 8, 'FUNCTION', 9, 'PACKAGE',
                      11, 'PACKAGE BODY', 12, 'TRIGGER',
                      13, 'TYPE', 14, 'TYPE BODY',
                      19, 'TABLE PARTITION', 20, 'INDEX PARTITION', 21, 'LOB',
                      22, 'LIBRARY', 23, 'DIRECTORY', 24, 'QUEUE',
                      28, 'JAVA SOURCE', 29, 'JAVA CLASS', 30, 'JAVA RESOURCE',
                      32, 'INDEXTYPE', 33, 'OPERATOR',
                      34, 'TABLE SUBPARTITION', 35, 'INDEX SUBPARTITION',
                      40, 'LOB PARTITION', 41, 'LOB SUBPARTITION',
                      42, 'MATERIALIZED VIEW',
                      43, 'DIMENSION',
                      44, 'CONTEXT', 46, 'RULE SET', 47, 'RESOURCE PLAN',
                      48, 'CONSUMER GROUP',
                      51, 'SUBSCRIPTION', 52, 'LOCATION',
                      55, 'XML SCHEMA', 56, 'JAVA DATA',
                      57, 'SECURITY PROFILE', 59, 'RULE',
                      62, 'EVALUATION CONTEXT',
                     'UNDEFINED') object_type,
       lob.kglnaobj object_name,
       pn.kglpnmod lock_mode_held,
       pn.kglpnreq lock_mode_requested,
       ses.sid,
       ses.serial#,
       ses.username
  from v$session_wait vsw,
       x$kglob lob,
       x$kglpn pn,
       v$session ses
 where vsw.event = 'library cache lock'
   and vsw.p1raw = lob.kglhdadr
   and lob.kglhdadr = pn.kglpnhdl
   and pn.kglpnmod != 0
   and pn.kglpnuse = ses.saddr
order by pn.kglpnmod desc, pn.kglpnreq desc
/