Rerunning Post Installation Database Update

If there are failures with Post Installation Database Update, correct the condition that caused the failure and rerun the PostInstallDBSetup utility in standalone mode.

When the utility is rerun without the -cleanstart option, PostInstallDBSetup automatically determines whether a compatible unfinished execution is available. If a compatible unfinished execution is found, the utility resumes processing from the saved checkpoint state. Completed logical operations are bypassed and incomplete operations are executed again.

If no compatible unfinished execution is found, PostInstallDBSetup starts a new normal execution.

Rerun Post Installation Database Update

  1. Review the Post Installation Database Update Report and the applicable utility logs to identify and correct the condition that caused the failure. For more information, see Post Installation Database Update Report and Logging and Diagnostics.

  2. If required, update the setup.ini file in C:\siebel\siebsrvr\bin or equivalent location.

    The setup.ini file contains, for example, the following parameter definitions:

    GENERATE_SCHEMA=N
    SIEBSRVR_ROOT=d:\Siebel\ses\siebsrvr
    REPOSITORY=Siebel Repository
    DBTYPE=mssql
    ODBC_DSN=siebel_dsn
    SIEBEL_DSN=ServerDataSrc
    TBLO=dbo
    TBLOUSER=SIEBEL
    SIEBUSER=SADMIN
    SSE_ROLE=SSE_ROLE
    UNICODEDB=Y
    PRIMARY_LANG_CD=ENU
    OTHER_LANG_CD=TRK,THA,SVE,RUS,PTG,PTB,PLK,NLD,KOR,JPN,ITA,HEB,FRA,FIN,ESN,DEU,DAN,CSY,CHT,CHS,ARA
  3. Rerun PostInstallDBSetup.exe, located in C:\siebel\siebsrvr\bin or equivalent location, using the following command from the command line:
    PostInstallDBSetup.exe -i Setup.ini -p ******** -z ********

    where:

    • -i is the ini file name.
    • -p is the Database Table Owner Password.
    • -z is the Database Password.
  4. Review the Post Installation Database Update Report generated by the execution.
Note: You do not specify a separate resume option. Resume processing is automatic when a compatible unfinished execution is available.
Note: If the current invocation is not compatible with the unfinished execution, PostInstallDBSetup does not reuse the saved execution. Instead, it starts a new normal execution.

Start a New Execution

To force PostInstallDBSetup to create a new logical execution instead of resuming an unfinished execution, specify:

PostInstallDBSetup.exe -i Setup.ini -p ******** -z ********
        -cleanstart

The -cleanstart option does not delete previous checkpoint or update history information and does not roll back database changes made by the previous execution.

Caution: Use -cleanstart only when you intend to start a new logical execution.

The existing setup.ini parameter table should remain unchanged except for the general addition of the -cleanstart option to this topic. The current guide explicitly documents GENERATE_SCHEMA values N, Y, and A; those semantics are unaffected by Resume Capability.

Description of Parameters in the Setup.ini File

This table lists the parameters in the setup.ini file and provides sample values for these parameters:

Setting Sample Value Comments
SIEBSRVR_ROOT C:\siebel\siebsrvr This should be the path to the "siebsrvr" folder, not a "bin" folder.
REPOSITORY Siebel Repository The name of the Repository against which PostInstallDBSetup should execute.
GENERATE_SCHEMA N, Y, or A

Possible values:

  • N: PostInstallDBSetup generates the schema DDL, execute it, and then process the remaining steps.
  • Y: Generates the schema DDL file, but doesn't execute it. The DBA runs it separately.
  • A: Indicates that the DDL has already been executed by the DBA and that processing should begin after the schema step.
DBTYPE ORACLE, MSSQL, DB2UDB, DB2390 N/A
ODBC_DSN Siebel_DSN The name of the ODBC source to use to connect to the database.
TBLO SIEBEL The name of the tableowner.
Note: For MSSQL, this will typically be "dbo".
TBLOUSER SIEBEL The actual username associated to the tableowner.
Note: For MSSQL, this might be "SIEBEL".
SIEBUSER SADMIN A Siebel User with full administrative privileges.
SSE_ROLE SSE_ROLE The group that provides user access to Siebel schema objects.
UNICODEDB Y Indicates whether the existing database is Unicode-enabled.
PRIMARY_LANG_CD ENU The primary language for the Siebel Enterprise database.
OTHER_LANG_CD DEU,JPN,FRA,HEB A comma-separated list of any additional languages used in the Siebel Enterprise.
INDSPC INDX The Index Space as determined by the DBA. This is applicable for Oracle and DB2UDB only.
TBLSPC DATA The Table Space as determined by the DBA. This is applicable for Oracle and DB2UDB only.
TBLSPC16K TBS_16K 16K Tablespace. This is applicable for DB2UDB only.
TBLSPC32K TBS_32K 32K Tablespace. This is applicable for DB2UDB only.
4KBUFFERPOOL BP1 4K Buffer Pool. This is applicable to DB2 for z/OS only.
8KBUFFERPOOL BP8K1 8K Buffer Pool. This is applicable to DB2 for z/OS only.
16KBUFFERPOOL BP16K1 16K Buffer Pool. This is applicable to DB2 for z/OS only.
32KBUFFERPOOL BP32K1 32K Buffer Pool. This is applicable to DB2 for z/OS only.
DBNAMEPREFIX D002 The prefix to use for the objects in the database. This is applicable to DB2 for z/OS only.
DBCODE ASCII or EBCDIC Encoding for the database. This is applicable to DB2 for z/OS only.
INDEXBUFFERPOOL BP2 The name of the Index Buffer Pool. This is applicable to DB2 for z/OS only.
STOGROUPINDEXES SYSDEFLT The storage group for indexes. This is applicable to DB2 for z/OS only.
STOGROUPTABLES SYSDEFLT The storage group for tables. This is applicable to DB2 for z/OS only.