Friday, 12 January 2018

Restart the Failed Installation of Siebel Database

Recovering from a Failure While Initializing a Regional Database:

If the regional database initialization fails, then you must recover from this failure before you restart Replication Manager. An example cause for failure is insufficient storage space on the regional database.

To recover from a failure while initializing a regional database:

Restart the Regional Database Initialization program.
Examine the log files.
The log files include srvrinit.log and upgwiz.log on Windows or srvrupgwiz1.log on UNIX.

Do the required corrective actions.
To resume the procedure for initializing a regional database, restart the Siebel Upgrade Wizard.
To restart the executable for this wizard on Windows, you type siebupg.exe. On UNIX, you type srvrupgwiz.

The state logging feature of the Siebel Upgrade Wizard allows you to restart the Siebel Upgrade Wizard. The Siebel Upgrade Wizard remembers the progress of the initialization process and resumes from the same location where it stopped.

Restarting the Procedure to Initialize a Regional Database:

This topic describes how to restart an interrupted initialization procedure.

To restart the procedure to initialize a regional database:

1. On the regional node, navigate to the SIEBEL_ROOT/bin folder.

2. If you are working in Windows, then do the following steps:
                  a)  Run the Siebel Upgrade Wizard.
                  b)  Click Cancel when this wizard prompts you to choose Yes to retry, No to abort,
                  or Cancel to abort and clean up.

3. If you are working in UNIX, then do the following steps:
                  a)  Locate the upgwiz.ucf file, and then delete it.
                  b)  Navigate to the SIEBEL_ROOT/upgrade folder, and then delete all files that
                  contain state.log in the file name.

4. Rerun the initialization procedure, starting with Step 1.

No comments:

Post a Comment