Additional Parameters
[{-tsdata | --tablespacefordata} data_tspace_name] [{-tsindex | -- tablespaceforindex} index_tspace_name] [{-tsblob | -- tablespaceforblob} BLOB_tspace_name] [{-b | --bufferpool} buffer_pool_name]
If you are going to create database components in DB2 or Oracle, you can specify custom tablespace names. Your products support all tablespace configurations deployed by users. For Oracle, the custom tablespace names will replace the defaults WEBMDATA and WEBMINDX. For DB2, the custom tablespace names will replace the defaults WEBMDATA, WEBMINDX, and WEBMBLOB. You can also specify a custom name to use for the buffer pool (WEBMBUFF by default). For DB2 or Oracle, if you are going to drop storage and revoke the database user permissions, provide the custom tablespace names.
[{-t | --tablespacedir} directory]
If you are going to create a database user and storage, and want to create a tablespace directory for DB2 or Oracle, full path to the directory. For DB2 on Linux systems, tablespaces are created for each DB2 database. If you are creating database components in more than one DB2 database, either the tablespace directory or the tablespace names must be unique for each DB2 database. If you are going to drop storage and revoke the database user permissions for Oracle or DB2, identify the directory that contains the tablespaces to drop.
[{-n | --dbname} database_name]
If you are going to create a database user and storage in SQL Server, name of the target database. If you are going to drop storage and revoke the database user permissions in SQL Server, identify the database that contains the storage.
[-r | --runCatalog]
Runs the catalog action at the end of every execution.
[-h | --help]
Lists command line interface help.
[-pa | --printActions]
Lists the actions you can perform, like create or drop.
[-pc | --printComponents]
Lists all database component names and codes.
[-pp | --printProducts]
Lists the names of products for which you can run {-pr|--product} product.
[--resume]
Database scripts are executed as sections, with each section concluding with a commit to the database. If an action such as create fails (for example, because of a network outage, an expired connection, or invalid credentials), the failed section will not have been committed, and therefore can safely be re-attempted. To do so, re-enter the failed command and add the --resume option. You must specify the same values for all parameters except the credential parameters, which can be different if necessary.