ORA-12751

-

What is ORA-12751?

ORA-12751 is a generic error which can occur during a resource exhausted condition. Oracle definition for the particular error is below.
ora12c@racaprdb1:~$ oerr ora 12751
ora-12751 cpu time or run time policy violation"
// *Document: NO
// *Cause: A piece of code ran longer than it is supposed to
// *Action: If this error persists, contact Oracle Support Services.
ora12c@racaprdb1:~$

ORA-12751 example

In the given example one of the rac databases was not accepting connections intermittently.
Alert log contained ora-12751 errors as below and TNS timeouts were also recorded.
 2020-07-14T12:59:34.407693+05:30  
 MOBPDB(3):minact-scn: useg scan erroring out with error e:12751  
 2020-07-14T13:02:23.311541+05:30  
 Thread 1 advanced to log sequence 145866 (LGWR switch)  
  Current log# 2 seq# 145866 mem# 0: +MOBREDO1DG/MOBCDB/ONLINELOG/group_2.258.989494005  
  Current log# 2 seq# 145866 mem# 1: +MOBREDO2DG/MOBCDB/ONLINELOG/group_2.258.989494005  
 2020-07-14T13:02:23.373617+05:30  
 Archived Log entry 604281 added for T-1.S-145865 ID 0x68692340 LAD:1  
 2020-07-14T13:02:23.775470+05:30  
 TT02: Standby redo logfile selected for thread 1 sequence 145866 for destination LOG_ARCHIVE_DEST_2  
 2020-07-14T13:03:14.438453+05:30  
 TABLE AUDSYS.AUD$UNIFIED: ADDED INTERVAL PARTITION SYS_P23126 (73) VALUES LESS THAN (TIMESTAMP' 2020-08-01 00:00:00')  
 2020-07-14T13:04:04.620028+05:30
First observations included that the MMON (Manageability Monitor process which takes AWR snapshots and stores) was running during the same time as the issue. MMON trace was reporting below errors,
 *** 2020-07-14T12:59:34.407893+05:30 (CDB$ROOT(1))  
 KEBM: MMON action policy violation. 'Block Cleanout Optim, Undo Segment Scan' viol=1; err=12751  
 *** 2020-07-14T12:59:37.837572+05:30 (MOBPDB(3))  
 : cleared SCNs  
 DDE rules only execution for: ORA 12751
With Oracle support help, this was pointed to document id 1671412.1 and Bug 9040676. As per the doc when MMON starts accessing undo tablespace rapidly this condition can occur. Solution for ORA-12751 on this case was to set _smu_debug_mode parameter to 134217728. 
 alter system set "_smu_debug_mode"=134217728;

Comments

Post a Comment

Popular posts from this blog

ORA-16433: The database or pluggable database must be opened in read/write

-
Image
ORA-16433 is an error returned when a database cannot be opened. This can be a result of multiple conditions including, The inconsistency of the database Physical corruption Loss of dependent files or access issues etc.. More often than not the solution is to recover from available backups, but there can be situations where backups are not available, specially on UAT or Test setups. Although not the ideal scenario, in this type of situation you might want to open the databases even with inconsistency.  In Comes --> _ALLOW_RESETLOGS_CORRUPTION First, if you are in a position to use _ALLOW_RESETLOGS_CORRUPTION=TRUE, that means it has to be a critical moment, and when you come across more ora- errors while you are trying to reopen the databsae, that can be annoying. Note - _ALLOW_RESETLOGS_CORRUPTION=TRUE must only be used after Oracle support confirmation as a last resort. Also make sure to take cold backup before proceeding. Basic steps to be followed to resolve ORA 16433 after
Read more

Oracle Multitenant - Create new service for PDB using DBMS_SERVICE

-
Image
When an Oracle PDB is created it starts up a default service with the PDB name. For direct connections to    PDB this service can be used. But there are situations where new service name is required in PDB level, common example is after a PDB restoration/clone, in order to enable application connections without changes in connection string. Setting service_names parameter in PDB level is not possible hence it is not an option in multitenant setup. How to create a new PDB service on Oracle 12C Check the current services, here only the default service is running, SQL> show pdbs; CON_ID CON_NAME OPEN MODE RESTRICTED ---------- ------------------------------ ---------- ---------- 3 NFACTORPDB READ WRITE NO SQL> select service_id, name, pdb from dba_Services; SERVICE_ID NAME PDB ---------- ---------------------------------------- ---------- 7 nfactorpdb NFACTORPDB SQL> Create
Read more

Wait for unread message on broadcast channel - Blocking Sessions

-
Image
What is Wait for unread message on broadcast channel wait event? Wait for unread message on broadcast channel is a wait event where source destination communication is involved and the database is waiting for a reply from remote party. Mostly this wait is seen related to data pump export (expdp) or import (impdp) operations. Although categorized in idle wait class "Wait for unread message on broadcast channel" can become the blocking session for some other sessions. Common causes for stuck sessions waiting on this wait event includes, Broken databases links, where remote database is not responding. Abnormally killed remote processes causing the sessions to wait. When a session is waiting on "Wait for unread message on broadcast channel" it can become a blocking session for dependent sessions. Most probably these sessions will be waiting on "library cache pin" or related concurrency wait events. The blocking_session column of (g)v$session view
Read more