Applies to:
Product Release: V7 (Enterprise)Version: 7.5.3.16 [16284] ESN
Database: Oracle 9.2.0.5
Application Server OS: IBM AIX 5L 5.2
Database Server OS: IBM AIX 5L 5.3
This document was previously published as Siebel SR 38-3442227811.
Symptoms
SBL-ESC-00054, SBL-SVR-01074, SBL-SMI-01000, SBL-SRB-00051, SBL-GEN-09103Hi support
We upgraded our Siebel systems to 7.5.3.16 a month ago. Everythisg worked
fine until we modified asignement rules in application.
Due to holidays periods,
administrator had to remove/add users . After these operations were done, and new rules released,
Aignment failed first time it tried to assign one SR to new user, and it is neccesary to stop and
re-start component.
We didn't see These behaviour in 7.5.3.15.
We attach yo
assignment logs; twice times when it became not available.
Regards
Solution
Message 1
For the benefit of other readers, after applying 7.5.3.16 patch on AIX, it was found that the Assignment Manager server (AsgnSrvr) component became assumed a status pf “unavailable”.The following error was repeatedly reported in the Srvrmgr.logowing error:
“srvrmgr 25746 1 /vol1/siebel/dmessias/sia75316/siebsrvr/log/srvrmgr.log 7.5.3.16
[16284] ENU
GenericLog GenericError 1 2007-10-17 11:58:59 (sacmd.cpp 10(44
0) err=902055 sys=902058) SBL-ADM-02055: Error from server "(null)"
GenericLog GenericError 1 2007-10-17 11:58:59 (sacmdl.cpp 29(6
71) err=902055 sys=0) SBL-ADM-02055: Error from server "(null)"
GenericLog GenericError 1 2007-10-17 12:09:09 (sacmd.cpp 10(38
8) err=902049 sys=0) SBL-ADM-02049: There is no connected server targeted for th
at command”
The behaviour was reproducible on 7.5.3.16 ENU on AIX but not on Windows.
A new Change Request -12-1LO0K79 has been raised to report this behaviour as a defect.
Applies to:
Product Release: V7 (Enterprise)Version: 7.5.3 [16157] Life Sci
Database: Oracle 9.2.0.2
Application Server OS: Microsoft Windows 2000 Server SP 4
Database Server OS: HP-UX 11i
This document was previously published as Siebel SR 38-3299863351.
Symptoms
SBL-ADM-02055Siebel -
2 of our remote servers are not functioning properly. When looking at them in
the application they (and the services) appear running but TXNs are not being routed out to our
users.
I've attached logs from the 2 servers (WILECRS1 and WILECRS2). I've also attached
the results of the remote queries showing the txn status.
To note, per 38-3272633287, we
have recently moved our data center. The move was completed around 5:00PM ET on Sunday
11-Mar-2007. Everything appeared "normal" after the move - the remote/txn query shows one of
these servers last routed at 11:59AM ET on 12-Mar and the other last routed at 5:02PM ET today
(13-Mar).
This is, of course, major impact so any help would be appreciated.
Thanks
as always -
Stephen
Solution
Message 1
For the benefit of others:The customer has relocated 3 remote servers to another data center. They have encountered the following issue on the 2 remote servers out of the 3 remote servers:
1. On srvrmgr command prompt, when they issue "stop task <TK_TASKID> for Processor and Router, it status is always showing "Shutting Down".
2. After restarting the Siebel Server service, the Processor and Router is running fine. But there are no dx files been created on the TXNPROC directory and there is no Processor logs generated, eventhough the Processor is showing status "Running". This happen to the Router as well.
After reviewing public Service Request 38-1018911541, it was discovered that the problem was due to the port setting of full-duplex. After changing this to full-duplex, the problem has been resolved.
You may refer to "http://www.intel.com/support/express/switches/10/sb/cs-014346.htm" on Google for more reading up on this duplex setting.
Thank you.
No comments:
Post a Comment