sibDBUpgrade command
A messaging engine needs DDL statements to alter the existing database management system (DBMS) resources. The DBMS resources can be altered using the sibDBUpgrade command.
The sibDBUpgrade command is required to modify the tables for the new functions such as the Keep count of failed deliveries per message and Restrict long running locks. The sibDBUpgrade command can be used for migrating a messaging engine from the previous version of WAS to v8.5.
Syntax
The command-line syntax for Unix is:
>>-sibDBUpgrade.sh--+-----------------------------+-------------> '- -runUpgrade--true or false-' >--+------------------------------+-----------------------------> '- -dbUser--database user name-' >--+----------------------------------+-------------------------> '- -dbSchema--database schema name-' >--+-------------------------+--+---------------------------+---> '- -dbType--database type-' '- -serverName--server name-' >--+-------------------------+----------------------------------> '- -dbName--database name-' >--+---------------------------------+--------------------------> '- -dbPassword--database password-' >--+------------------------------+-----------------------------> '- -dbNode--database node name-' >--+--------------------------------+---------------------------> '- -oracleHome--Oracle home path-' >--+-------------------------------+----------------------------> '- -scriptDir--script directory-' >--+-----------------------------------------+------------------> '- -permanent--number of permanent tables-' >--+-----------------------------------------+----------------->< '- -temporary--number of temporary tables-'
The command-line syntax for Windows is:
Purpose
The database administrator can use the sibDBUpgrade utility command to alter the DBMS resources of the messaging engine. The sibDBUpgrade command generates the DDL statements which the database administrator can save and later process to alter the DBMS resources listed in the Altered database tables. Besides the database administrator, users who have the authority to alter the database tables can also use the utility to alter the database tables.
To access the IBM i command line, use the STRQSH command to start a Qshell session. For more information, see Configure Qshell to run WebSphere scripts .
Required parameters
The sibDBUpgrade command is case-sensitive. For example, the parameter value Oracle is not the same as the parameter value oracle.
- -runUpgrade true or false [for z/OS, Derby, and Informix, the value must be false]
- The command to alter the database resources. Specify the parameter value as true to alter the database resources and false to generate the DDL scripts only.
- -dbUser
- The name of the user ID used to interact with the DBMS.
- -dbSchema
- The name of the schema containing all the objects used by the messaging engine.
- -dbType
- Identifies the type of DBMS. Valid values are:
- DB2
- Oracle
- SqlServer
- Sybase
- Informix
- Derby
DB2 on zos and iseries platforms is supported.
- DB2
Optional parameters
- -dbName
- The name of the database that is allocated for the messaging engine tables. The-dbName parameter is mandatory if the value for the runUpgrade parameter is specified as true.
- -serverName
- The name of the server used to interact with the DBMS. If we do not supply a -serverName parameter, the default value is IBMUSER.
- -dbPassword
- The password for the user ID used to interact with the DBMS.
- -dbNode
- The name of the database node. This optional parameter is applicable only for DB2. The system on which the script is running with -runUpgrade option must have only DB2 Client installed.
- -oracleHome
- The path to the Oracle Home directory if the -dbType parameter value is Oracle.
- -scriptDir
- The name of the directory in which the DDL scripts must be generated. If we do not specify a directory, the scripts are generated into <current_directory>/SIBusUpgradeDatabase directory where current_directory is the active directory.
- -permanent
- The number of permanent tables created when the service integration messaging engines are created. For more information about the number of tables configured, see Data store [Settings]. There will be one permanent table by default. If the messaging engine is configured to use multiple permanent tables, then specify the number of tables.
- -temporary
- The number of temporary tables created when the service integration messaging engines are created. For more information about the number of tables configured, see Data store [Settings]. There will be one temporary table by default. If the messaging engine is configured to use multiple temporary tables, then specify the number of tables.
Examples
To upgrade the database schema of the service integration bus from the previous version of WAS to v8.5.
- sibDBUpgrade.sh -runUpgrade false -dbUser db2inst1 -dbSchema SIBusMESchema -dbType DB2
- sibDBUpgrade.sh -runUpgrade true -dbName SIBus -dbUser db2inst1 -dbSchema SIBusMESchema -dbType DB2
To upgrade the database schema of the service integration bus from the previous version of WAS tov8.5.
- sibDBUpgrade.bat runUpgrade=false dbUser=db2inst1 dbSchema=SIBusMESchema dbType=DB2
- sibDBUpgrade.bat runUpgrade=true dbName=SIBus dbUser=db2inst1 dbSchema=SIBusMESchema dbType=DB2
Related tasks
Reference topic