25/4/23, 15:51 Document 10194190.

8
  Pedro (Not Available) (0) Contact Us Help
PoLast Login: April 25, 2023 12:31 PM CLST Switch to Cloud Support

 
Dashboard Knowledge Service Requests Patches & Updates

Give Feedback...
Copyright (c) 2023, Oracle. All rights reserved. Oracle Confidential.

Bug 10194190 - Solaris: Process spin and/or ASM and DB crash if RAC instance up for > 248 days (Doc ID To Bottom
10194190.8)

  Was this document helpful?  

Bug 10194190  Solaris: Process spin and/or ASM and DB crash if RAC instance up for > 248 days Yes
No
 This note gives a brief overview of bug 10194190.
 The content was last updated on: 08-MAR-2022
   

 Click here for details of each of the sections below.

  Document Details  
 This bug is marked as an important issue.

Affects: Type:
PATCH
Status:
PUBLISHED
Last Major
Product (Component) Oracle Server (Rdbms) Update:
Mar 10, 2022
Mar 10, 2022
Range of versions believed to be affected (Not specified) Last Update:
   

12.1.0.1 (Base Release)

11.2.0.4   Related Products  
11.2.0.3 Oracle Database - Enterprise
11.2.0.2 Edition
Versions confirmed as being affected
11.2.0.1
   

11.1.0.7   Information Centers  

10.2.0.5
Information Center:
10.2.0.4 Transportable Tablespaces
(TTS) for Oracle Database
[1461278.2]
Platforms affected Solaris 64bit (Sparc)
19c Database Upgrade - Self
Guided Assistance with Best
Practices [1919.2]
 Note that this fix has been superseded by the fix in Bug:18740837 Index of Oracle Database
Information Centers
Fixed: [1568043.2]

インフォメーション・センタ
This fix has been superseded - please see the fixed version information for Bug:18740837 . The box below only
ー: データベースおよび
shows versions where the code change/s for 10194190 are first included - those versions may not contain the later
Enterprise Manager 日本語ド
improved fix.
キュメント [1946305.2]

Information Center: Data

12.2.0.1 (Base Release) Warehousing [1487754.2]
The fix for 10194190 is first included in
11.2.0.4 Bundle Patch 9 for Exadata Database
Show More
   

  Document References  
Symptoms: Related To: No References available for
this document.
   

Automatic Storage Management (ASM)   Recently Viewed  

Instance May Crash
Network
Hang (Process Spins) Database Instance Crashes
RAC (Real Application Clusters) / OPS
Stack is likely to include sslsstehdlr With ORA-15064 ORA-
Net Parameter SQLNET.EXPIRE_TIME
03113: Possible Causes and
Solution [2378963.1]
Bug 30336742 - Hit ORA-
Description 29770: global enqueue
process LMON is hung When
ASM or DB processes may start spinning in a RAC environment Opening PDBs [30336742.8]
after the instance has been running continuously for more Bug 27254851 - INSTANCE
than 248 days. This issue only affects Solaris platforms and CRASHED WITH ORA-29770
is due to a faulty C compiler optimization. DUE TO LMON HAS NOT
HEARTBEAT [27254851.8]
The same problem can also affect non RAC / ASM sessions OERR: ORA-29770
(in particular if SQLNET.EXPIRE_TIME is used but this is not a requirement "global enqueue
to hit the problem) process %s (OSID %s) is
hung for more than %s
Rediscovery Notes seconds" Reference
- The RAC instance (DB or ASM) has been up for more than 248 days Note [2010718.1]
continuously with no shutdown. Session Wait On 'ges
- The spinning processes show stacks similar to: enter server mode
sslssalck <- sskgxp_alarm_set <- skgxp_setalarm() <- sslsstehdlr() event&#39; For 2 Seconds
<- __sighndlr() <- call_user_handler() <- __pollsys() <- _pollsys() [2776938.1]
... Show More
- Instance crashes can occur following process/es starting to spin

https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=227694943379718&id=10194190.8&_afrWindowMode=0&_adf.ctrl-state=127dr… 1/2
25/4/23, 15:51 Document 10194190.8
due to various timeouts and blocked resources and so the symptoms
   

of a crash due to this issue can vary.

eg: See Note:1473937.1 for an example scenario
OR
- User sessions are seen to spin with a stack like above especially if
SQLNET.EXPIRE_TIME is set in the server side SQLNET.ORA
( Note: It is NOT a requirement to have EXPIRE_TIME set to encounter
this bug issue, but if that is set then the issue may be more visible )

Workaround
Instance needs to be restarted, but before doing that take pstack and truss
on the spinning process for diagnostic purposes. This will help to determine
whether this is same issue or different one.

To proactively avoid this issue schedule instance restarts to occur before

248 days of uptime.

Note:
This fix was originally listed as fixed in 11.2.0.4 but the relevant change
was not made in that release and to the problem can still occur there.

The relevant change has now been merged into 12.2 using bug 18740837.
For backports on 12 please use bug 18740837.

Please note: The above is a summary description only. Actual symptoms can vary. Matching to any
symptoms here does not confirm that you are encountering this problem. For questions about this
bug please consult Oracle Support.

References

Bug:10194190 (This link will only work for PUBLISHED bugs)

Note:245840.1 Information on the sections in this article

Didn't find what you are looking for? Ask in Community...

Related
Products
Oracle Database Products > Oracle Database Suite > Oracle Database > Oracle Database - Enterprise Edition

Back to Top
 
Copyright (c) 2023, Oracle. All rights reserved. Legal Notices and Terms of Use Privacy Statement
   

https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=227694943379718&id=10194190.8&_afrWindowMode=0&_adf.ctrl-state=127dr… 2/2