Error 2103 In Oracle
Contents |
SQL TuningSecurityOracle UNIXOracle LinuxMonitoringRemote supportRemote plansRemote servicesApplication Server ApplicationsOracle FormsOracle PortalApp UpgradesSQL ServerOracle ConceptsSoftware SupportRemote Support Development Implementation Consulting StaffConsulting PricesHelp Wanted! Oracle PostersOracle Books Oracle Scripts Ion Excel-DB netflix error 2103 Don Burleson Blog
Silverlight Error 2103
ORA-00494 enqueue [CF] held for too long tips Oracle Database Tips by Burleson Consulting August oracle terminating the instance due to error 2103 8, 2015 Question: I am getting an ORA-00494 error and the trace file. This error causes my database to crash:. ORA-00494: enqueue [CF] held for too long /u01/app/oracle/admin/mysid/bdump/ora_lgwr_143.trcKilling enqueue ora-00239 blocker (pid=152) on resourceCF-00000000-00000000 by killing session 83.0 What is the cure for this ORA-00494 error? Answer: The oerr utility shows this on the ORA-00494 ORA-00494: enqueue string held for too long (more than string seconds) by 'inst string, osid string' Cause: The specified process did not release the enqueue within the maximum allowed time.Action: Reissue any commands that failed
Ora-239
and contact Oracle Support Services with the incident information. The ORA-00494 error occurs during periods of super-high stress, activity to the point there the server becomes unresponsive due to overloaded disk I/O, CPU or RAM. See MOSC Note ID 779552.1 "ORA-00494 During High Load After 10.2.0.4 Upgrade" says that Oracle kills blocking processes during periods of high DML load and issues the ORA-00494 error. In your case, it is the log writer process. Also see Database Crashes With ORA-00494 [MOSC Note ID 753290.1 Solutions for ORA-00494: Resize online redo logs Spread-out the DML over longer periods Adjust several hidden parameters: Two Oracle database hidden parameters can be reconfigured to prevent further incident happens by the same cause - Oracle Kill Blocker Interface mechanism: 1) _kill_controlfile_enqueue_blocker = { TRUE | FALSE } TRUE. Default value. Enables this mechanism and kills blocker process in CF enqueue. FALSE. Disables this mechanism and no blocker process in CF enqueue will be killed. 2) _kill_enqueue_blocker = { 0 | 1 | 2 | 3 } 0. Disables this mechanism and no foregr
ORA-00494: enqueue [CF] held for too long (more than 900 seconds) by 'inst 1, osid 5488' Incident details in: d:\oracle\admin\ecore\diag\rdbms\ecore\ecore\incident\incdir_12529\ecore_lgwr_5484_i12529.trc Killing enqueue blocker (pid=5488) on resource http://serdarturgut.blogspot.com/2010/12/database-crashes-with-ora-00494.html CF-00000000-00000000 by (pid=5484) by killing session 3.1 Killing enqueue blocker (pid=5488) on resource CF-00000000-00000000 by (pid=5484) by terminating the process LGWR (ospid: 5484): terminating the instance due to error 2103 Fri Dec 17 03:05:09 2010 Instance terminated by LGWR, pid = 5484 Cause The lgwr has killed the ckpt process, causing the instance to crash. From the alert.log we can see: That the database error 2103 has waited too long for a CF enqueue, so the following error has been reported. ORA-00494: enqueue [CF] held for too long (more than 900 seconds) by by 'inst 1, osid 5488' Then the LGWR has killed the blocker, which was in this case the CKPT process which cause the instance to crash. Checking the alert.log we can see that the frequency of redo log error 2103 in files switch is very high(almost every 1 min). Solution 1-We usually suggest to configure the redo log switches to be done every 20~30 min to reduce the contention on the control files. You can use the V$INSTANCE_RECOVERY view column OPTIMAL_LOGFILE_SIZE to determine the size of your online redo logs. This field shows the redo log file size in megabytes that is considered optimal based on the current setting of FAST_START_MTTR_TARGET. If this field consistently shows a value greater than the size of your smallest online log, then you should configure all your online logs to be at least this size. References BUG:7448854 - ORA-00494 CAUSE THE INSTANCE TO CRASH Metalink Note: 753290.1 Posted by SERDARTURGUT at 7:03 AM Labels: bug, ORAERR No comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Blog Archive ► 2013 (4) ► September (1) ► August (1) ► March (1) ► February (1) ► 2012 (2) ► July (1) ► January (1) ► 2011 (4) ► November (1) ► September (1) ► July (1) ► January (1) ▼ 2010 (60) ▼ December (6) Where to find MAXxxxxxx control file parameters in... Database Crashe
be down. Please try the request again. Your cache administrator is webmaster. Generated Mon, 10 Oct 2016 20:45:50 GMT by s_wx1131 (squid/3.5.20)