Applies to:
Siebel System Software - Version: 7.7.1 SIA [18306] and later [Release: V7 and later ]
Oracle Solaris on SPARC (64-bit)
Product Release: V7 (Enterprise)
Version: 7.7.1 [18306] Auto
Database: Oracle 9.2.0.6
Application Server OS: Sun Solaris 9
Database Server OS: Sun Solaris 9
This document was previously published as Siebel SR 38-2032365241.
Symptoms
SBL-SMI-00038Hi,
I am setting up our QA system:
Gateway server is on soa020 (unix).
Siebel server is
on soa016 and soa017 (all unix)
Document server is on snt055 (win 2003 server)
Siebel
remote server is on soa020 also.
The problem is sometime one or both of the siebel servers
state show "Handshake failed" from the dedicated client --> Administration - Server -->
Enterprise view, and the web client would work. sometimes I restart those two siebel servers they
come up fine, sometime I need to restart them several times. Also even I enabled and start
components eAutomotive Object Manager (ENU) and eDealer Object Manager (ENU), after restart
siebel server, their state show "Shutdown".
I am attaching the screenshot, logfiles and
siebelns.dat for your review.
Thank you so much.
Cause
Configuration/ Setup
Solution
Message 1
For the benefits of other users:
When login to the dedicated client and go to SiteMap> Administration -
Server > Enterprise view, customer observed that siebel servers
state show "Handshake failed".
Resolution:
According to Troubleshooting Steps 8 “Siebel Server Installation
Troubleshooting Guide”, one of the cause of “handshake failed” error is
insufficient memory.
In addition, review of the Enterprise Server log show the following error,
GenericLog GenericError 1 0 2005-06-05
17:27:31 (schedule.cpp (452) err=2100038 sys=12) SBL-SMI-00038:
Internal: Cannot create process for siebsess
The “sys=12” in the error message above means ENOMEM which is out of memory error.
The customer increases the RAM size and did not encounter the “handshake failed” error again.
According to the System Requirement and Supported Platform document for
7.7, the RAM size recommendation is 1GB. Please note that this is only
the minimum memory requirement. For more precise memory sizing, please
engage Expert Service.
Many Thanks,
Applies to:
Siebel System Software - Version: 7.7.1 [18306] to 8.1.1.4 [21225] - Release: V7 to V8
Oracle Solaris on SPARC (64-bit)
Product Release: V7 (Professional)
Version: 7.8.2 [19213]
Database: Oracle 10g
Application Server OS: Sun Solaris 9
Database Server OS: None - Not Implementing Web Server OS
This document was previously published as Siebel SR 38-3015432521.
Symptoms
SBL-SMI-00038, SBL-ADM-02049Hi
Sometimes when we log into Siebel and navigate to the Administration - Server
Managment - Servers and Sessions screen to check on the status of ther server we cannot access
the screen and we get the following error.
"We detected an Error which may have occurred for
one or more of the following reasons:
Operation failed, possibly because of "SBL-ADM-02049:
There is no connected server targeted for that command."(SBL-SDM-00112) ".
When we
navigate to Administration - Server Managment - Tasks we get the following error"
"We detected
an Error which may have occurred for one or more of the following reasons:
SBL-NET-01023: Peer
disconnected"
I think we also have a related issue with above as we can not log into
srvrmgr from the command prompt. We were able to log in using the following commands, however it
is not working now: Here are the steps we are taking to log
in
*********************************************************************************************
Log
into the box
Change directory to root where Siebel is installed
$ cd /var/adm/Siebel
Get
a subshell
$ ksh
Navigate to siebsrvr folder
$ cd siebsrvr
Run the environment
variable
$ . ./siebenv.sh
Navigate to Bin folder
$ cd bin
Run the Srvrmgr
command
$ srvrmgr -g dmncvmdev2 -e SiebDev –s dmncvmdev2 -u sadmin -p
sadmin
srvrmgr:dmncvmdev2>
***********************************************************************************************
We
have been having this issue for some time. The workaround has been to restart the services and it
used to get corrected. How ever off late this has been happening more often and with start of
development this is getting
critical.
=================================================================
We are also
unable to run any EIM task. It errors out with the following error:
"SBL-EIM-00204: Invalid
configuration file (ifb) name." Please see the attached EIM log file.
Any help will be
highly appreciated
Regards
Solution
Message 1
For benefit of other readers:
They are able to startup the gateway and siebel server successfully. But
after sometime, they are no more able to access Server Admin screen and
connect via srvrmgr.
Below error was found in the log:
SBL-SMI-00038: Internal: Cannot create process for siebsess
The behavior was resolved after they increase the swap space to twice of the RAM, 4.5 GB.
Thanks
אין תגובות:
הוסף רשומת תגובה