Applies to:
Siebel Financial Services CRM - Version: 8.0.0.5 SIA [20420] and later [Release: V8 and later ]
Information in this document applies to any platform.
Symptoms
On : 8.0.0.5 SIA [20420] version, System Admin
When attempting to Start siebel services after patching from 8.0.0.5 to 8.0.0.11 FP,
the following error occurs.
ERROR
-----------------------
SBL-SMI-00024: Unable to load sssacbrkr
Reproduce Steps:
-----------------------
The issue can be reproduced at will with the following steps:
1. Install FP 8.0.0.11 on top of 8.0.0.5
2. Start siebel services
3. Siebel does not start and throws error
Cause
The issue is caused by the Corrupted Lib files at the time of Patch
upgrade from older version to new version. Which leads an issue to start
siebel services.
SBL-SMI-00024: Unable to load sssacbrkr.
Solution
How to resolve the library files issue after patching :
Option 1:
1. If this is first environment you are patching then degrade to old patch and copy lib directory from working environment
2. Re-patch to New FP version
3. Start the siebel services and verify the status of application
Option 2:
1. If you already holds a working environment with new FP, then just copy the lib directory to corrupted environment
2. Recycle the environment
3. Start the siebel services and verify the status of application
Applies to:
Siebel Remote - Version: 7.5.3.4 [16180] to 8.1 [21039] - Release: V7 to V8
IBM AIX on POWER Systems (64-bit)
Product Release: V7 (Enterprise)
Version: 7.5.3.4 [16180]
Database: Oracle 8.1.7.4
Application Server OS: IBM AIX 5L 5.1
Database Server OS: IBM AIX 5L 5.1
This document was previously published as Siebel SR 38-1923792601.
Symptoms
SBL-GDB-00004, SBL-SMI-00024, SBL-SRB-00061, SBL-GEN-09103Hi,
I am running "GenNewDb" and immediately, I got this following
error.
srvrmgr:nytids007tst> start task for component GenNewDb
start task for
component GenNewDb
SBL-NET-01034: The SISNAPI connection was closed by the peer
When I
checked the "GenNewDb_xxxx.log",I can see the following error
message.
ContextInit ContextInit 0 2005-04-18
23:15:50 SIEBEL_ASSERT_MODE =
0
GenericLog GenericWarn 2 2005-04-18
23:15:50 (smisched.cpp 17(266) err=9103 sys=0) SBL-GEN-09103:
Parameter value
was never set (i.e. is
null)
GenericLog GenericWarn 2 2005-04-18
23:15:50 (smisched.cpp 17(269) err=9103 sys=0) SBL-GEN-09103:
Parameter value
was never set (i.e. is
null)
GenericLog GenericError 1 2005-04-18
23:15:50 (smisched.cpp 17(285) err=2100024 sys=0) SBL-SMI-00024:
Unable to lo
ad gennewdb
Please look into this ASAP as we need to provide the extract
to TAM for review.
Thanks & Regards
Cause
Missing siebel server files
a] \siebsrvr\lib\libgennewdb.so
b] \siebsrvr\dbtempl\sse_utf8.dbf
Solution
Message 1
1 of 2
For the benefit of other readers, the issue and resolution are as follows.
Issue Description:
----------------------
When the GenNewDB was run, wither from the UI or from server manager, an
error occurred alomost immediately. In this case, customer ran from the
server manager prompt as follows. Customer encountered errors as
described below.
srvrmgr:nytids007tst> start task for component GenNewDb
start task for component GenNewDb
SBL-NET-01034: The SISNAPI connection was closed by the peer
When I checked the "GenNewDb_xxxx.log",I can see the following error message.
ContextInit ContextInit 0 2005-04-18 23:15:50 SIEBEL_ASSERT_MODE = 0
GenericLog GenericWarn 2 2005-04-18
23:15:50 (smisched.cpp 17(266) err=9103 sys=0) SBL-GEN-09103:
Parameter value
was never set (i.e. is null)
GenericLog GenericWarn 2 2005-04-18
23:15:50 (smisched.cpp 17(269) err=9103 sys=0) SBL-GEN-09103:
Parameter value
was never set (i.e. is null)
GenericLog GenericError 1 2005-04-18
23:15:50 (smisched.cpp 17(285) err=2100024 sys=0) SBL-SMI-00024:
Unable to lo
ad gennewdb
Resolution:
--------------
After detailed analysis, Siebel Technical Support discovered the following.
1. Customer environment was missing the following files
a] \siebsrvr\lib\libgennewdb.so
b] \siebsrvr\dbtempl\sse_utf8.dbf
Contd...
Message 2
2 of 2 - Contd from previous..
Customer had another environment similar to this one, where everything
was working. Since this non working environment was a test environment
and not a production environment, Siebel Technical Support recommended
copying the missing libray file \siebsrvr\lib\libgennewdb.so and
\siebsrvr\DBTEMPL\sse_utf8.dbf from the working environment.
After the copy was done, customer restarted the siebel server and gateway and ran the GenNewDB and it worked successfully.
Recommendations:
-----------------------
Other recommendations made to the customer were as follows
1. Refer Alert 899: Maintenance Level Update Recommended for AIX 5L v5.1
According to the Alert 899, which refers Alert 851, Customers have to
ensure Siebel deployment is running the latest C++ runtime libraries
(6.0.0.12) or later, if they are on AIX 5L v5.1
2. Other recommendation made was to not copy missing files, if the
environment is production. If missing files are noticed in production,
then for long term stability, customers must consider reinstallign their
Siebel environment.
Thank you
Applies to:
Siebel Sales - Version: 7.8.2.3 [19221] and later [Release: V7 and later ]
Information in this document applies to any platform.
kernel memory issue
Symptoms
=== ODM Issue Clarification ===
On : 7.8.2.3 [19221] version, System Admin
When attempting to restart the Siebel Server
the following error occurs.
ERROR
-----------------------
GenericLog GenericError 1 0 2010-07-06 17:13:07
(smishell.cpp (237) err=2100024 sys=0) SBL-SMI-00024: Unable to load
sssawmon
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Attempt to restart the Siebel Server using start_server ALL
2. A core file is written to ~siebsrvr/bin
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot restart the Siebel Server
Cause
=== ODM Cause Determination ===
The behaviour reported here was seen for AIX 5.2 TL10.
The callstacks and symptoms were similar to those reported for a known AIX 5.3 APAR
=== ODM Cause Justification ===
This is explained in the following IBM APAR:
APAR IY84780 for AIX 5.3.
http://www.ibm.com/developerworks/forums/thread.jspa?threadID=129099
Solution
=== ODM Solution /Action Plan ===
To implement the solution, please execute the following steps:
1. Download and review the readme and pre-requisites for AIX 5.3 TL5 or higher
2. Ensure that you have taken a backup of your system before applying
the recommended patch.
3. Apply the patch in a test environment.
4. Migrate the solution as appropriate to other environments.
Applies to:
Siebel Universal Customer Master - Version 8.1.1.4 [21225] and later
Information in this document applies to any platform.
Symptoms
When the Workflow "UCM Batch Process" is run using the "UCM Batch
Manager" component (alias UCMBatchProcess), an error is reported :-
SBL-SRB-00061: Process UCMBatchProcess on Siebel Server siebsrvr02 terminated.
In the UCMBatchProcess*.log, there is an error on the SSCFDM.DLL file :-
GenericLog GenericError 1 000002474e4312cc:0 2011-08-11 11:03:07 Błąd
menedżera obiektów: ([0] Nie można załadować pliku DLL
"SSCFDM.DLL".(SBL-DAT-00170) (0x7500aa))
Translated :-
Object manager error: ([0] The DLL 'SSCFDM.DLL' could not be loaded.(SBL-DAT-00170)
Also, when the "Workflow Process Manager" is used instead of the "UCM
Batch Manager" object manager, there are no errors (but "UCM Batch
Manager" is the recommended component).
Cause
In the Siebel 8.1.1.x Maintenance Release Guide, under ACR 475, there
are instructions to set UCMBatchProcess to be single threaded.
This was incorrect, and a bug was logged :-
Bug 12962891 : ACR 475 TELL TO SET UCM BATCH PROCESS TO SINGLE THREADED, BUT THIS CAUSES FAILURE
Note - on unix platforms, the following error can be seen instead of the error above :-
(smisched.cpp (295) err=1376280 sys=0) SBL-SMI-00024: Unable to load sssabsvm
Solution
Set Threaded to true for the UCMBatchProcess from srvrmgr, then shutdown/restart the Siebel Server :-
srvrmgr> change param Threaded=true for comp UCMBatchProcess
No comments:
Post a Comment