A database administrator can, when required, manually upgrade the BPM database by running the necessary scripts, previously generated by TIBCO Configuration Tool.
Procedure
If necessary, edit the database scripts to run correctly on the target database, as shown in the following table.
Database
Changes required
SQL Server
When manually running scripts, incorrect use of ANSI_PADDING statements may change the ANSI_PADDING setting for SQL Server, causing all tables created or upgraded subsequently during the same query session to have the wrong setting.
Before manually running any SQL scripts, ensure that you do the following:
Delete any SET ANSI_PADDING ON and SET ANSI_PADDING OFF statements in the script.
Check the database query session settings and ensure that ANSI_PADDING is turned ON. To do this, right click the query window and select
Query Options, then select the
Execution->ANSI section and ensure that SET ANSI_PADDING is selected.
Oracle
If you need to manually amend any of the BPM database scripts, make sure that you do not include any blank lines. If there are any blank lines, you will receive an error similar to the ones below:
and the rest of the line is ignored. To resolve this, you can:
remove all blank lines from the script
set sqlblanklines on on the sqlplus session
DB2
Not all the database scripts use the same termination character. For example, the termination character for
WorkManagerCreate.sql is "/" and for
createdb-admin.sql and
ProcessManagerCreate.sql scripts is ";".
Ensure that you examine the scripts and set the appropriate termination character using the DB2 Control Center. Doing so ensures that the scripts can be used from either the DB2 Control Center or the DB2 Command Line Processor.
You can set the statement termination character from the DB2 Control Center.
To manually upgrade the BPM database, run the following scripts in the order shown.
Caution: Ensure that you commit the changes after running each script.