Siebel Remote and Replication Manager Administration Guide > Administering Siebel Remote > Handling Failure and Recovery >

Database Server Failure


If your RDBMS fails, the database administrator must diagnose and rectify the problem. When the system returns to an operational state, use the Siebel Server Manager to restart the Siebel Remote components. Siebel Remote components automatically recovers their process state from the last committed transaction. A reextraction of the mobile Web clients may be necessary.

If the database is recovered up to the point of failure, no action is required because there is no loss of data. However, if the database is recovered up to a point of time prior to the point of failure, then you must reextract and reinitialize all mobile Web clients. In this case, follow the steps below after restoring the database backup:

  1. Disable the Synchronization Manager component.
  2. Stop the Transaction Router, Transaction Merger and Transaction Processor tasks if they are running.
  3. Reextract all mobile Web clients.
  4. Start the Transaction Processor task with the TS DB Recreate parameter set to TRUE.
  5. Start the Transaction Router and Transaction Merger tasks.
  6. Enable the Synchronization Manager component.

After you complete the steps above, the next action depends on when the last backup was completed, when the failure occurred, and when the user synchronized.


 Siebel Remote and Replication Manager Administration Guide, Version 7.5, Rev. A 
 Published: 18 April 2003