CRDB – Create Dimensions Base Database

This command enables you to create a Dimensions base database.

NOTE When you create a new base database, the default grant rules for the Update Files from Project/Stream and Deliver Files into Project/Stream privileges include the "User holds any role on the product owning the object" rule. As a result, there is a security issue where certain users are able to download and upload files from any project in the product including those to which they should not have access. To correct this, you must remove the "User holds any role on the product owning the object" rule from the grant rules for "Update Files from Project/Stream" and "Deliver Files into Project/Stream" privileges.

The syntax is as follows:

crdb <newbasedb> /toolman=<username> /pass[word]=<pcms_sys_passwd>

[[/basedon=<basedb> /product=<product-id>] |

/import=<exportfile>]

[/def_tab=<default_tablespace>

/temptab=<temporaray_tablespace>]

[/indextab=<index_tablespace>] [/installviews]

NOTE Either /basedon or /import needs to be specified. Their use is mutually exclusive.

where:

Parameter | Description
<newbasedb> | The database name for the new base database (schema) that is to be created, e.g. PROJ_A. Note that the name of the new base database should be alphanumeric and that the first character must be alphabetic. For example, PROJ1 is valid but not 1PROJ. NOTE For Oracle systems the database name will be <NEWBASEDDB> (upper case) and a password of <NEWBASEDB> (upper case) will be also be assigned to the new base database. See CPAS – Changing Passwords for Databases for instructions on how to change the password.
<username> | The login-id of the user who will act as base database manager for this Dimensions base database.
<pcms_sys_passwd> | The password for the PCMS_SYS schema. For the Serena-supplied runtime this is PCMS_SYS by default (if this default password has not been changed then the /PASS[WORD] parameter need not be specified).
<basedb> | The name of an existing base database from which to copy a process model during creation of the new base database. Note that the process model data is imported into the product $GENERIC of the new base database.
<product_id> | If /basedon is used, the name of a product defined in the existing base database given by <generic_db> whose process model is to be used to set up the Generic Process Model in the new Dimensions base database. If this is not specified, then the process model for the $GENERIC product is used by default.
<exportfile> | Specifies the process model export file that is to be imported when creating the new base database.
<default_tablespace> | Serena-Supplied Runtime RDBMS or Oracle Enterprise only: Specifies the optional default tablespace for this user.
<temporary_tablespace> | Serena-Supplied Runtime RDBMS or Oracle Enterprise only: Specifies the optional temporary tablespace for this user.
<index_tablespace> | Serena-Supplied Runtime RDBMS or Oracle Enterprise only: Specifies the optional index tablespace for this user.
/installviews | Install Published Views (Report Views) for the Report User that gets created. An example invocation using SQL Server: PCMS_SYS> crdb fred /basedon=qlarius_cm /toolman=dmsys /installviews Creating the new base database FRED. Please wait... Base Database has been successfully created Installing report views in FRED@dim10, please wait.... Report views have been successfully installed.

Experienced Oracle Enterprise users may note that Dimensions DBA commands will by default support the use of RDBMS tablespaces other than the SYSTEM tablespace when an Oracle user is created. By default the PCMS_DATA tablespace is used.

IMPORTANT!

- In order to connect to the newly created database, the Dimensions service may require stopping and restarting.

- The length of each item of information regarding the new base database is limited, and any excess will be truncated. Base database names and passwords are limited to 25 characters and logins IDs to 64 characters.