Last updated on MARCH 21, 2013
Applies to:Siebel System Software - Version 7.7.2  to 22.214.171.124 SIA [Release V7 to V8]
Oracle Solaris on SPARC (64-bit)
Product Release: V7 (Enterprise)
Version: 7.7.2 
Database: IBM DB2 8.1 FixPack 8
Application Server OS: Sun Solaris 2.8
Database Server OS: Sun Solaris 2.8
This document was previously published as Siebel SR 38-2521738391.
***Checked for relevance on 22-Mar-2013***
In our production environment the siebns.dat file is getting corrupted too often. We upgraded from Siebel 7.0.4 to Siebel7.7.2 on 6th August 2005 and after that we had 3/4 instances of siebns.dat file getting corrupted. Then after 08/30 we had not seen any more instance of siebns.dat getting corrupted. Then on 09/16, we did a code page migration from code page 819 to 1252. Then we have seen another two instances of siebns.dat getting corrupted on 09/19 and 09/21. While the application is up and running fine we are getting calls from users that they are not able not access the application. Gradually it's happening for all the users. Then we stop all the siebel and gateway servers and restore the siebns.dat file from back up and the Application comes up.
When it happened 09/21 we have captured the logs, the corrupted siebns.dat file and the working siebns.dat file.On 09/21, there was no Object Manager Logs being created when this corruption happened. So, we have only the SWE logs and the gateway Server logs.
I am attaching the SWE Log, Gateway Log , Working siebns.dat file and corrupted siebns.dat file. Please look into the issue and suggest something to prevent the corruption of the siebns.dat file. We have a very poor user satisfication now as the Application is going down during the prime business hour.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms