Archive "Error exceeded maximum number of latches" message in object manager log files
(Doc ID 514490.1)
Last updated on APRIL 04, 2025
Applies to:
Siebel System Software - Version 7.0.4.307 [14197] and laterOracle Solaris on SPARC (64-bit)
Version: 7.0.4.307 [14197] DEU
Database: Oracle 8.1.7.4
Application Server OS: Sun Solaris 8
Database Server OS: Sun Solaris 8
This document was previously published as Siebel SR 38-1079443971.
Symptoms
Siebel is running slow and crashing for all the users for the last couple of days. I looked in object manager log files and found the following error messages:
SSLObjMgr_231.log:GenericLog GenericError 1 2003-09-11 13:04:33 (scitask.cpp 24(191) err=1300217 s
ys=0) OSD-00217: Internal: Error exceeded maximum number of latches.
SSLObjMgr_231.log:GenericLog GenericError 1 2003-09-11 13:04:33 (smimtsh.cpp 25(276) err=1300217 s
ys=0) OSD-00217: Internal: Error exceeded maximum number of latches.
SSLObjMgr_233.log:GenericLog GenericError 1 2003-09-11 13:05:00 (scitask.cpp 24(191) err=1300217 s
ys=0) OSD-00217: Internal: Error exceeded maximum number of latches.
SSLObjMgr_233.log:GenericLog GenericError 1 2003-09-11 13:05:00 (smimtsh.cpp 25(276) err=1300217 s
ys=0) OSD-00217: Internal: Error exceeded maximum number of latches.
This message is not only appearing in object manager log files but in workflow and other component log files as well. We have already got the following variables set in siebenv.sh
SIEBEL_OSD_NLATCH=10800
SIEBEL_OSD_LATCH=5000
SIEBEL_OSD_NSEMA is not set, but I have added it to the file with the value of 5000. Could you please let us know what causes this problem and how we can fix it.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
Message 1 |