Skip to Main Content

Oracle Database Discussions

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

ORA-21780: Maximum number of object durations exceeded.

Samuel RabiniMay 16 2011 — edited Jun 3 2011
Hi,
I'm working on an Oracle Database 11g Release 11.1.0.6.0 - 64bit Production With the Real Application Clusters option.

I was reading at the alert log of my nodes and I saw that on both nodes I have the error of the subject.

Node 1
Errors in file /u01/app/oracle/diag/rdbms/evodb/EVODB1/trace/EVODB1_smon_1377.trc:
ORA-21780: Maximum number of object durations exceeded.

Node 2
Errors in file /u01/app/oracle/diag/rdbms/evodb/EVODB2/trace/EVODB2_smon_11934.trc:
ORA-21780: Maximum number of object durations exceeded.

This are first lines of the trace:
Trace file /u01/app/oracle/diag/rdbms/evodb/EVODB2/trace/EVODB2_smon_11934.trc
Oracle Database 11g Release 11.1.0.6.0 - 64bit Production
With the Real Application Clusters option
ORACLE_HOME = /u01/app/oracle/product/11.1.0/db1
System name:    Linux
Node name:      dcsrv-evodb02
Release:        2.6.18-194.32.1.el5
Version:        #1 SMP Mon Dec 20 10:52:42 EST 2010
Machine:        x86_64
Instance name: EVODB2
Redo thread mounted by this instance: 2
Oracle process number: 19
Unix process pid: 11934, image: oracle@dcsrv-evodb02 (SMON)


*** 2011-04-18 08:03:24.106
*** SESSION ID:(865.1) 2011-04-18 08:03:24.107
*** CLIENT ID:() 2011-04-18 08:03:24.107
*** SERVICE NAME:(SYS$BACKGROUND) 2011-04-18 08:03:24.107
*** MODULE NAME:() 2011-04-18 08:03:24.107
*** ACTION NAME:() 2011-04-18 08:03:24.107
 
Dead transaction 0x001a.014.00169739 recovered by SMON
Dead transaction 0x000f.036.0039ff1b recovered by SMON
Dead transaction 0x0011.011.00368276 recovered by SMON
Dead transaction 0x000c.000.003748c1 recovered by SMON
Dead transaction 0x0011.034.00375edd recovered by SMON
         Drop transient type:   SYSTPov6Ag4AQ+nHgQFEKHgo5Dw==

*** 2011-05-11 20:11:25.846
SMON: following errors trapped and ignored:
ORA-21779: duration not active

*** 2011-05-11 20:11:27.069
         Drop transient type:   SYSTPov6Ag4AQ+nHgQFEKHgo5Dw==

*** 2011-05-11 20:11:27.070
SMON: following errors trapped and ignored:
ORA-21779: duration not active

*** 2011-05-11 20:11:28.208
         Drop transient type:   SYSTPov6Ag4AQ+nHgQFEKHgo5Dw==

*** 2011-05-11 20:11:28.208
SMON: following errors trapped and ignored:
ORA-21779: duration not active

*** 2011-05-11 20:11:29.270
         Drop transient type:   SYSTPov6Ag4AQ+nHgQFEKHgo5Dw==

*** 2011-05-11 20:11:29.270
SMON: following errors trapped and ignored:
ORA-21779: duration not active

*** 2011-05-11 20:11:30.374
         Drop transient type:   SYSTPov6Ag4AQ+nHgQFEKHgo5Dw==

*** 2011-05-11 20:11:30.374
SMON: following errors trapped and ignored:
ORA-21779: duration not active
===================================================
PROCESS STATE
-------------
Process global information:
     process: 0x19369fde8, call: 0x19251a338, xact: (nil), curses: 0x192b5cfe8, usrses: 0x192b5cfe8
  ----------------------------------------
  SO: 0x19369fde8, type: 2, owner: (nil), flag: INIT/-/-/0x00 if: 0x3 c: 0x3
   proc=0x19369fde8, name=process, file=ksu.h LINE:10286, pg=0
  (process) Oracle pid:19, ser:1, calls cur/top: 0x19251a338/0x19251a338
            flags: (0x16) SYSTEM
            int error: 0, call error: 0, sess error: 0, txn error 0
  (post info) last post received: 0 0 69
              last post received-location: kji.h LINE:2160 ID:kjata: wake up enqueue owner
              last process to post me: 193697e68 1 6
              last post sent: 0 0 25
              last post sent-location: ksa2.h LINE:282 ID:ksasnd
              last process posted by me: 1936a7d68 1 6
    (latch info) wait_event=0 bits=0
    Process Group: DEFAULT, pseudo proc: 0x1931df010
    O/S info: user: oracle, term: UNKNOWN, ospid: 11934
    OSD pid info: Unix process pid: 11934, image: oracle@dcsrv-evodb02 (SMON)
Everything seems to work fine, but why those messages onto the logs?

Thanks in advance,
Samuel
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Jul 1 2011
Added on May 16 2011
3 comments
2,101 views