Oracle DGMGRL yapılandırılması

  1. Öncelikle database’deki dgmgrl parametrelerine bakılır.
SQL> sho parameter dg_broker
NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
dg_broker_config_file1               string      /u01/app/oracle/product/11.2.0/db_1/dbs/dr1newdb.dat
dg_broker_config_file2               string      /u01/app/oracle/product/11.2.0/db_1/dbs/dr2newdb.dat
dg_broker_start                      boolean     FALSE
  1. dg_broker_config_file1 ve dg_broker_config_file2 parametrelerindeki dizinleri olduğu kontrol edilir. dg_broker_start parametresi true’ya çekilir.
alter system set dg_broker_start=TRUE;
  1. DGMGRL komut satırına bağlanılır ve primary tarafta ilk konfigürasyon create edilir.
[oracle@rhel73 ~]$ dgmgrl /
DGMGRL for Linux: Version 11.2.0.4.0 - 64bit Production
 
Copyright (c) 2000, 2009, Oracle. All rights reserved.
 
Welcome to DGMGRL, type "help" for information.
Connected.

DGMGRL> create configuration PROD as primary database is newdb connect identifier is newdb;
Configuration "prod" created with primary database "newdb"
DGMGRL> show configuration
Configuration - prod
  Protection Mode: MaxPerformance
  Databases:
    newdb - Primary database
Fast-Start Failover: DISABLED
Configuration Status:
DISABLED
  1. Daha önceden oluşturulan standby database eklenir.
DGMGRL> add database stdnewdb;
Database "stdnewdb" added

DGMGRL> show configuration
Configuration - prod
  Protection Mode: MaxPerformance
  Databases:
    newdb    - Primary database
    stdnewdb - Physical standby database
Fast-Start Failover: DISABLED
Configuration Status:
DISABLED
  1. Database’lerin durumuna bakılır
DGMGRL> show database verbose newdb;

Database - newdb

  Role:            PRIMARY
  Intended State:  OFFLINE
  Instance(s):
    newdb

  Properties:
    DGConnectIdentifier             = 'newdb'
    ObserverConnectIdentifier       = ''
    LogXptMode                      = 'ASYNC'
    DelayMins                       = '0'
    Binding                         = 'optional'
    MaxFailure                      = '0'
    MaxConnections                  = '1'
    ReopenSecs                      = '300'
    NetTimeout                      = '30'
    RedoCompression                 = 'DISABLE'
    LogShipping                     = 'ON'
    PreferredApplyInstance          = ''
    ApplyInstanceTimeout            = '0'
    ApplyParallel                   = 'AUTO'
    StandbyFileManagement           = 'AUTO'
    ArchiveLagTarget                = '0'
    LogArchiveMaxProcesses          = '30'
    LogArchiveMinSucceedDest        = '1'
    DbFileNameConvert               = ''
    LogFileNameConvert              = ''
    FastStartFailoverTarget         = ''
    InconsistentProperties          = '(monitor)'
    InconsistentLogXptProps         = '(monitor)'
    SendQEntries                    = '(monitor)'
    LogXptStatus                    = '(monitor)'
    RecvQEntries                    = '(monitor)'
    ApplyLagThreshold               = '0'
    TransportLagThreshold           = '0'
    TransportDisconnectedThreshold  = '30'
    SidName                         = 'newdb'
    StaticConnectIdentifier         = '(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=rhel73.gantek.com)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=newdb_DGMGRL)(INSTANCE_NAME=newdb)(SERVER=DEDICATED)))'
    StandbyArchiveLocation          = 'USE_DB_RECOVERY_FILE_DEST'
    AlternateLocation               = ''
    LogArchiveTrace                 = '0'
    LogArchiveFormat                = '%t_%s_%r.dbf'
    TopWaitEvents                   = '(monitor)'

Database Status:
DISABLED
DGMGRL>  show database verbose stdnewdb;

Database - stdnewdb

  Role:            PHYSICAL STANDBY
  Intended State:  OFFLINE
  Transport Lag:   (unknown)
  Apply Lag:       (unknown)
  Apply Rate:      (unknown)
  Real Time Query: OFF
  Instance(s):
    newdb

  Properties:
    DGConnectIdentifier             = 'stdnewdb'
    ObserverConnectIdentifier       = ''
    LogXptMode                      = 'ASYNC'
    DelayMins                       = '0'
    Binding                         = 'OPTIONAL'
    MaxFailure                      = '0'
    MaxConnections                  = '1'
    ReopenSecs                      = '300'
    NetTimeout                      = '30'
    RedoCompression                 = 'DISABLE'
    LogShipping                     = 'ON'
    PreferredApplyInstance          = ''
    ApplyInstanceTimeout            = '0'
    ApplyParallel                   = 'AUTO'
    StandbyFileManagement           = 'AUTO'
    ArchiveLagTarget                = '0'
    LogArchiveMaxProcesses          = '30'
    LogArchiveMinSucceedDest        = '1'
    DbFileNameConvert               = ''
    LogFileNameConvert              = ''
    FastStartFailoverTarget         = ''
    InconsistentProperties          = '(monitor)'
    InconsistentLogXptProps         = '(monitor)'
    SendQEntries                    = '(monitor)'
    LogXptStatus                    = '(monitor)'
    RecvQEntries                    = '(monitor)'
    ApplyLagThreshold               = '0'
    TransportLagThreshold           = '0'
    TransportDisconnectedThreshold  = '30'
    SidName                         = 'newdb'
    StaticConnectIdentifier         = '(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=rhel73-disaster.gantek.com)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=stdnewdb_DGMGRL)(INSTANCE_NAME=newdb)(SERVER=DEDICATED)))'
    StandbyArchiveLocation          = 'USE_DB_RECOVERY_FILE_DEST'
    AlternateLocation               = ''
    LogArchiveTrace                 = '0'
    LogArchiveFormat                = '%t_%s_%r.dbf'
    TopWaitEvents                   = '(monitor)'

Database Status:
DISABLED
  1. Konfigürasyon enable edilir.
DGMGRL> enable configuration;
Enabled.

DGMGRL> show configuration

Configuration - prod

  Protection Mode: MaxPerformance
  Databases:
    newdb    - Primary database
    stdnewdb - Physical standby database

Fast-Start Failover: DISABLED

Configuration Status:
SUCCESS

Oracle Database PGA Size Management

Oracle 11gR2
total physical memory    : 6GB
total swap               : 4GB
memory_target parameter  : 3GB
_pga_max_size parameter  : 246MB
– 11g’de PGA alanına sınırlandırma getirilemiyor. _PGA_MAX_SIZE parametresi sözde session bazlı maximum pga alanını belirliyor ancak söylendiği gibi çalışmıyor. Örneğin _pga_max_size parametresi 246MB olmasına rağmen session’ların pga kullanımı bu değeri aşabiliyor.
asdsad
– Memory_target parametresi de pga kullanımına sınırlama getiremiyor. Oracle user’ının memory kullanımı aşağıdaki gibi. Makine önce fiziksel memory’yi bitirdi daha sonra da swap’i bitirdi. Swap bittinten sonra da database crash oldu.
[root@rhel03 ~]# smem -u -t -k
User     Count     Swap      USS      PSS      RSS
oracle     130     2.1G     4.1G     4.4G     5.9G
---------------------------------------------------
           270     2.3G     4.7G     5.0G     6.9G
 1 [####################################################################################################100.0%] Tasks: 267, 476 thr; 13 running
 2 [####################################################################################################100.0%] Load average: 12.48 12.66 11.49
 Mem[||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||#**5059/5852MB] Uptime: 7 days, 05:36:56
 Swp[|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||4095/4095MB]
Oracle 12C
pga_aggregate_limit        : 2GB
pga_aggregate_target       : 1G
memory_target              : 0
 
– 12c’de pga_aggregate_limit parametresi getirildi. Bu parametre sayesinde pga’in toplam size’ına limit konabiliyor. Ancak bu limit SYS user’ı ile çalışan session’larda işlemiyor.
– pga_aggregate_limit parametresindeki değer aşıldığından önce alert.log’a aşağıdaki hata düşüyor.
2017-06-19T17:31:05.229587+03:00
PGA_AGGREGATE_LIMIT has been exceeded but some processes using the most PGA
memory are not eligible to receive ORA-4036 interrupts.  Further occurrences
of this condition will be written to the trace file of the CKPT process.
– Daha sonra en çok PGA kullanan session terminate ediliyor. Session aşağıdaki hatayı alıyor.
*
ERROR at line 1:
ORA-04036: PGA memory used by the instance exceeds PGA_AGGREGATE_LIMIT
– Aynı anda da alert.log dosyasına aşağıdaki log’lar basılıyor.
Errors in file /u01/app/oracle/diag/rdbms/emdb/emdb/trace/emdb_ora_25495.trc  (incident=16138):
ORA-6544 [pevm_peruws_callback-1] [4036] [] [] [] [] [] [] [] [] [] []
Incident details in: /u01/app/oracle/diag/rdbms/emdb/emdb/incident/incdir_16138/emdb_ora_25495_i16138.trc
Bu sayede PGA kullanımına limitleme getirilmiş oluyor.

redo_sizes.sql

redo_size_by_hours.sql

  SELECT TO_CHAR (LH.FIRST_TIME, ‘YYYY-MM-DD’) DAY,
         TO_CHAR (LH.FIRST_TIME, ‘HH24’) HOURS,
         COUNT(*) TOTAL_COUNT,
         ROUND (SUM ( (AL.blocks * AL.block_size) / 1024 / 1024), 2) ARCHIVE_MB
    FROM V$LOG_HISTORY LH, v$archived_log AL
   WHERE     LH.thread# = AL.thread#
         AND LH.sequence# = AL.sequence#
         AND TO_CHAR (LH.FIRST_TIME, ‘YYYY-MM-DD’) >=
                TO_CHAR (SYSDATE 10, ‘YYYY-MM-DD’)
GROUP BY TO_CHAR (LH.FIRST_TIME, ‘YYYY-MM-DD’),
         TO_CHAR (LH.FIRST_TIME, ‘HH24’)
ORDER BY TO_CHAR (LH.FIRST_TIME, ‘YYYY-MM-DD’),
         TO_CHAR (LH.FIRST_TIME, ‘HH24’) ASC;

redo_size_by_days.sql
  
SELECT A.DAY, SUM (TOTAL_COUNT) TOTAL_COUNT, SUM (ARCHIVE_MB) TOTAL_GB
    FROM (  SELECT TO_CHAR (LH.FIRST_TIME, ‘YYYY-MM-DD’) DAY,
                   TO_CHAR (LH.FIRST_TIME, ‘HH24’) HOURS,
                   COUNT (*) TOTAL_COUNT,
                   ROUND (SUM ( (AL.blocks * AL.block_size) / 1024 / 1024 / 1024), 2)
                      ARCHIVE_MB
              FROM V$LOG_HISTORY LH, v$archived_log AL
             WHERE     LH.thread# = AL.thread#
                   AND LH.sequence# = AL.sequence#
                   AND TO_CHAR (LH.FIRST_TIME, ‘YYYY-MM-DD’) >=
                          TO_CHAR (SYSDATE 10, ‘YYYY-MM-DD’)
          GROUP BY TO_CHAR (LH.FIRST_TIME, ‘YYYY-MM-DD’),
                   TO_CHAR (LH.FIRST_TIME, ‘HH24’)
          ORDER BY TO_CHAR (LH.FIRST_TIME, ‘YYYY-MM-DD’),
                   TO_CHAR (LH.FIRST_TIME, ‘HH24’) ASC) A
GROUP BY A.DAY
ORDER BY 1;

redo_loglarin_tektek_gercek_boyutlari.sql
  SELECT al.recid,
         AL.THREAD#,
         AL.SEQUENCE#,
         TO_CHAR (LH.FIRST_TIME, ‘YYYY-MM-DD’) DAY,
         TO_CHAR (LH.FIRST_TIME, ‘HH24:MI:SS’) HOUR,
         ROUND ( (AL.blocks * AL.block_size) / 1024 / 1024, 2) ARCHIVE_MB
    FROM V$LOG_HISTORY LH, v$archived_log AL
   WHERE     LH.thread# = AL.thread#
         AND LH.sequence# = AL.sequence#
         AND TO_CHAR (LH.FIRST_TIME, ‘YYYY-MM-DD’) >=
                TO_CHAR (SYSDATE 10, ‘YYYY-MM-DD’)
ORDER BY 1 ASC;

tek_günlük_redo_log_boyutlari.sql
  SELECT al.recid,
         AL.THREAD#,
         AL.SEQUENCE#,
         TO_CHAR (LH.FIRST_TIME, ‘YYYY-MM-DD’) DAY,
         TO_CHAR (LH.FIRST_TIME, ‘HH24:MI:SS’) HOUR,
         ROUND ( (AL.blocks * AL.block_size) / 1024 / 1024, 2) ARCHIVE_MB
    FROM V$LOG_HISTORY LH, v$archived_log AL
   WHERE     LH.thread# = AL.thread#
         AND LH.sequence# = AL.sequence#
         AND TO_CHAR (LH.FIRST_TIME, ‘YYYY-MM-DD’) = ‘2017-06-06’
ORDER BY 1 asc;

ORA-600 [KTSPFFBMB:OBJDCHK_KCBNEW_3]

Hi,

I just faced with ORA-600 error while using CTAS.

RDBMS Version : 11.2.0.2 (standalone – file system)
OS Version         : Red Hat Enterprise Linux Server release 5.4 (Tikanga)

Here is my error details;

Tue May 02 09:10:02 2017
Errors in file /u01/app/oracle/diag/rdbms/kpi/kpi/trace/kpi_ora_17741.trc (incident=320607):
ORA-00600: internal error code, arguments: [ktspffbmb:objdchk_kcbnew_3], [1], [1779621], [4], [], [], [], [], [], [], [], []
Incident details in: /u01/app/oracle/diag/rdbms/kpi/kpi/incident/incdir_320607/kpi_ora_17741_i320607.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.

trace file;

[oracle@- ~]$ more /u01/app/oracle/diag/rdbms/kpi/kpi/trace/kpi_ora_17741.trc
Trace file /u01/app/oracle/diag/rdbms/kpi/kpi/trace/kpi_ora_17741.trc
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
With the Partitioning, Automatic Storage Management, OLAP, Data Mining
and Real Application Testing options
ORACLE_HOME = /u01/app/oracle/product/11.2.0/db
System name: Linux
Node name: -
Release: 2.6.18-164.el5
Version: #1 SMP Tue Aug 18 15:51:48 EDT 2009
Machine: x86_64
Instance name: kpi
Redo thread mounted by this instance: 1
Oracle process number: 48
Unix process pid: 17741, image: oracle@-


*** 2017-05-02 09:10:02.039
*** SESSION ID:(2.25129) 2017-05-02 09:10:02.039
*** CLIENT ID:() 2017-05-02 09:10:02.039
*** SERVICE NAME:(kpi) 2017-05-02 09:10:02.039
*** MODULE NAME:(TOAD 12.1.0.22) 2017-05-02 09:10:02.039
*** ACTION NAME:() 2017-05-02 09:10:02.039

Incident 320607 created, dump file: /u01/app/oracle/diag/rdbms/kpi/kpi/incident/incdir_320607/kpi_ora_17741_i320607.trc
ORA-00600: internal error code, arguments: [ktspffbmb:objdchk_kcbnew_3], [1], [1779621], [4], [], [], [], [], [], [], [], []

Related bug number is 11902008. Problem solved with patch 11902008

Interim patches (1) :

Patch 11902008 : applied on Tue May 02 11:10:14 EEST 2017
Unique Patch ID: 16286381
 Created on 24 Apr 2013, 19:05:40 hrs PST8PDT
 Bugs fixed:
 11902008

You can download and apply with following link;

https://support.oracle.com/epmos/faces/PatchDetail?_afrLoop=339632664795710&patchId=11902008&_adf.ctrl-state=145q9pp25u_384

Regards,

ibrisim

How to find Oracle patch history ?

  1. Go to $ORACLE_HOME/.patch_storage directory
[oracle@oel65_11g ~]$ cd $ORACLE_HOME/.patch_storage
  1. You can find all information about patchs and sub-patchs
[oracle@oel65_11g .patch_storage]$ ls -ltrh
total 76K
drwxr-xr-x 3 oracle oinstall 4.0K Apr 26 15:55 NRollback
drwxr-xr-x 4 oracle oinstall 4.0K Apr 26 16:00 NApply
-rw-r--r-- 1 oracle oinstall   52 Apr 26 16:00 record_inventory.txt
-rw-r--r-- 1 oracle oinstall 4.5K Apr 26 16:00 interim_inventory.txt
-rw-r--r-- 1 oracle oinstall   93 Apr 26 16:03 LatestOPatchSession.properties
drwxr-xr-x 4 oracle oinstall 4.0K Apr 26 16:06 19769489_Dec_28_2014_21_22_44
drwxr-xr-x 4 oracle oinstall 4.0K Apr 26 16:06 24732075_Feb_22_2017_21_40_49
drwxr-xr-x 4 oracle oinstall 4.0K Apr 26 16:06 19121551_Oct_6_2014_10_07_57
drwxr-xr-x 4 oracle oinstall 4.0K Apr 26 16:06 20760982_Jun_4_2015_00_23_20
drwxr-xr-x 4 oracle oinstall 4.0K Apr 26 16:06 18031668_Feb_20_2014_05_15_58
drwxr-xr-x 4 oracle oinstall 4.0K Apr 26 16:06 18522509_Jun_30_2014_08_14_42
drwxr-xr-x 4 oracle oinstall 4.0K Apr 26 16:06 20299013_Mar_4_2015_02_27_44
drwxr-xr-x 4 oracle oinstall 4.0K Apr 26 16:06 21948347_Dec_14_2015_03_31_48
drwxr-xr-x 4 oracle oinstall 4.0K Apr 26 16:06 23054359_Jun_15_2016_16_08_35
drwxr-xr-x 4 oracle oinstall 4.0K Apr 26 16:06 17478514_Dec_6_2013_04_22_19
drwxr-xr-x 4 oracle oinstall 4.0K Apr 26 16:06 21352635_Sep_1_2015_07_49_44
drwxr-xr-x 4 oracle oinstall 4.0K Apr 26 16:06 24006111_Aug_26_2016_05_54_48
drwxr-xr-x 4 oracle oinstall 4.0K Apr 26 16:06 22502456_Mar_21_2016_11_49_22
  1. All apply histories are in NApply directory.
[oracle@oel65_11g .patch_storage]$ cd NApply/
[oracle@oel65_11g NApply]$ ls -ltrh
total 8.0K
drwxr-xr-x 2 oracle oinstall 4.0K Oct 31 08:25 2016-10-31_08-25-22AM
drwxr-xr-x 2 oracle oinstall 4.0K Apr 26 16:06 2017-04-26_15-57-54PM

[oracle@oel65_11g NApply]$ cd 2016-10-31_08-25-22AM
[oracle@oel65_11g 2016-10-31_08-25-22AM]$ ls -l
total 4
-rw-r--r-- 1 oracle oinstall 222 Oct 31 08:25 patchlist.txt
[oracle@oel65_11g 2016-10-31_08-25-22AM]$ cat 2016-10-31_08-25-22AM
cat: 2016-10-31_08-25-22AM: No such file or directory
[oracle@oel65_11g 2016-10-31_08-25-22AM]$ cat patchlist.txt
User invokes OPatch via "NApply" to process the following patches:

Patch ID: 23543737
Patch Location: "/u01/23543737"
Patch storage area: "/u01/app/oracle/product/11.2.0/db_1/.patch_storage/23543737_Jul_22_2016_09_18_21"
[oracle@oel65_11g 2016-10-31_08-25-22AM]$ cd ..
[oracle@oel65_11g NApply]$ cd 2017-04-26_15-57-54PM/
[oracle@oel65_11g 2017-04-26_15-57-54PM]$ cat patchlist.txt
User invokes OPatch via "NApply" to process the following patches:

Patch ID: 17478514
Patch Location: "/u01/24732075/17478514"
Patch storage area: "/u01/app/oracle/product/11.2.0/db_1/.patch_storage/17478514_Dec_6_2013_04_22_19"

Patch ID: 18031668
Patch Location: "/u01/24732075/18031668"
Patch storage area: "/u01/app/oracle/product/11.2.0/db_1/.patch_storage/18031668_Feb_20_2014_05_15_58"

Patch ID: 18522509
Patch Location: "/u01/24732075/18522509"
Patch storage area: "/u01/app/oracle/product/11.2.0/db_1/.patch_storage/18522509_Jun_30_2014_08_14_42"

Patch ID: 19121551
Patch Location: "/u01/24732075/19121551"
Patch storage area: "/u01/app/oracle/product/11.2.0/db_1/.patch_storage/19121551_Oct_6_2014_10_07_57"

Patch ID: 19769489
Patch Location: "/u01/24732075/19769489"
Patch storage area: "/u01/app/oracle/product/11.2.0/db_1/.patch_storage/19769489_Dec_28_2014_21_22_44"

Patch ID: 20299013
Patch Location: "/u01/24732075/20299013"
Patch storage area: "/u01/app/oracle/product/11.2.0/db_1/.patch_storage/20299013_Mar_4_2015_02_27_44"

Patch ID: 20760982
Patch Location: "/u01/24732075/20760982"
Patch storage area: "/u01/app/oracle/product/11.2.0/db_1/.patch_storage/20760982_Jun_4_2015_00_23_20"

Patch ID: 21352635
Patch Location: "/u01/24732075/21352635"
Patch storage area: "/u01/app/oracle/product/11.2.0/db_1/.patch_storage/21352635_Sep_1_2015_07_49_44"

Patch ID: 21948347
Patch Location: "/u01/24732075/21948347"
Patch storage area: "/u01/app/oracle/product/11.2.0/db_1/.patch_storage/21948347_Dec_14_2015_03_31_48"

Patch ID: 22502456
Patch Location: "/u01/24732075/22502456"
Patch storage area: "/u01/app/oracle/product/11.2.0/db_1/.patch_storage/22502456_Mar_21_2016_11_49_22"

Patch ID: 23054359
Patch Location: "/u01/24732075/23054359"
Patch storage area: "/u01/app/oracle/product/11.2.0/db_1/.patch_storage/23054359_Jun_15_2016_16_08_35"

Patch ID: 24006111
Patch Location: "/u01/24732075/24006111"
Patch storage area: "/u01/app/oracle/product/11.2.0/db_1/.patch_storage/24006111_Aug_26_2016_05_54_48"

Patch ID: 24732075
Patch Location: "/u01/24732075/24732075"
Patch storage area: "/u01/app/oracle/product/11.2.0/db_1/.patch_storage/24732075_Feb_22_2017_21_40_49"
  1. All rollback histories are in NRollback directory.
[oracle@oel65_11g NApply]$ cd ..
[oracle@oel65_11g .patch_storage]$ cd NRollback/
[oracle@oel65_11g NRollback]$ ls -ltrh
total 4.0K
drwxr-xr-x 2 oracle oinstall 4.0K Apr 26 15:56 2017-04-26_15-55-07PM
[oracle@oel65_11g NRollback]$ cd 2017-04-26_15-55-07PM/
[oracle@oel65_11g 2017-04-26_15-55-07PM]$ ls -ltrh
total 4.0K
-rw-r--r-- 1 oracle oinstall 274 Apr 26 15:55 patchlist.txt
[oracle@oel65_11g 2017-04-26_15-55-07PM]$ cat patchlist.txt
User invokes OPatch via "NRollback" to process the following patches:

Patch ID: 23543737
Patch Location: "/u01/app/oracle/product/11.2.0/db_1/inventory/oneoffs/23543737"
Patch storage area: "/u01/app/oracle/product/11.2.0/db_1/.patch_storage/23543737_Jul_22_2016_09_18_21"
In my environment, I understand that patch number 23543737 applied on 2016-10-31 and rollbacked on 2017-04-26.
  1. You can find last opatch operation information in LatestOPatchSession.properties file.
[oracle@oel65_11g .patch_storage]$ cat LatestOPatchSession.properties
SessionName=apply
SessionID=24732075_Feb_22_2017_21_40_49
PatchID=24732075
TriggeredPatchID=

last ddls on database

set linesize 200;
set pagesize 100;
set heading on;
COLUMN OWNER FORMAT A15
COLUMN OBJECT_NAME FORMAT A40
COLUMN OBJECT_TYPE FORMAT A30
  SELECT OWNER,
         OBJECT_NAME,
         OBJECT_TYPE,
         CREATED,
         LAST_DDL_TIME,
         TIMESTAMP,
         STATUS
    FROM DBA_OBJECTS
   WHERE     (CREATED >= SYSDATE 7 OR LAST_DDL_TIME >= SYSDATE 7)
         AND OWNER NOT IN (‘SYS’,‘SYSTEM’, ‘SYSMAN’, ‘DBSNMP’)
ORDER BY LAST_DDL_TIME DESC;