Recovering from Failed Media That Resides on the Siebel Server

A head failure or other media failure that involves the Siebel Server might result in an unusable Siebel database. For more information, see Protecting Against a Media Failure.

To recover from failed media that resides on the Siebel Server

1. Stop the following server components on the Siebel Server:

   • Transaction Router

   • Transaction Merger

   • Transaction Processor

2. Use the Server Manager to disable the Synchronization Manager.

3. Wait for the Siebel database administrator to return the Siebel Server to an operational state.

4. If the Transaction Router server component sent data to any remote clients after the most recent backup of the Siebel database was performed, then you must reinitialize the local database for each remote client who received data after the last backup:

   1. To determine if a remote client is not processed because of a corrupted file, you can examine the log file of the Transaction Router server component.

      If the log indicates that the dobjinst.dbf visibility database is corrupt, then you must reextract the Siebel database for the user that the log identifies. It might be necessary to delete the local database. For more information, see Example Where You Must Delete the Local Database and Naming Conventions for Log Files.

   2. Notify users to reinitialize their local databases.

      For more information, see Extracting the Server Database.

   3. Run Database Extract for the affected clients.

   4. Notify each user that Siebel Remote will reinitialize the local database the next time the user synchronizes.

      This is a potentially time-consuming step. The user might be required to reinitialize at different times. For example, to reduce download time, users who are located close to a field office might be required to use a LAN connection. Other users might be required to reinitialize during times when network traffic is reduced. For more information, see Initializing the Local Database.