SIEBNS.DAT file stores all parameters of servers, enterprise, components and others, configured at the time of installation or later.
When we change some parameters in the Siebel Server Administration and restart Enterprise or Siebel Server, the siebns.dat file gets corrupt and therefore, Siebel Server won’t start any more.
That behavior happens often, but not always. There can be many possible scenarios/cause for this.
That behavior happens often, but not always. There can be many possible scenarios/cause for this.
In our case, We tried to disable server components. After restart Siebel Server, the siebns.dat files corrupt.
CAUSE
Possible reason behind this behavior is bad Configuration/ Setup
SOLUTION
Well you must have a backup of this file to replace it quickly. Then below are the root cause that the siebns.dat file became corrupt, so be careful next time.
1. The Siebel server was started too early after a shutdown of the server. Please make sure that the
server is completely shut down by verifying the status of the server through the server manager
command line utility (srvrmgr) and that all sieb* processes (such as siebsvc.exe, siebmtshmw.exe,
siebsess.exe, …) are exit for that specific server.
server is completely shut down by verifying the status of the server through the server manager
command line utility (srvrmgr) and that all sieb* processes (such as siebsvc.exe, siebmtshmw.exe,
siebsess.exe, …) are exit for that specific server.
2. The gateway was stopped but still one Siebel server was running belonging to the environment.
To shut down a Siebel deployment please follow the correct sequence
– Shut down the Siebel Server service(s)
– shutdown the Resonate service if applicable
– Shut down the Siebel Gateway service
– Shut down the Database Server
– Shut down the Siebel Server service(s)
– shutdown the Resonate service if applicable
– Shut down the Siebel Gateway service
– Shut down the Database Server
No comments:
Post a Comment