EXPM – Exporting a Process Model to a File

This command enables a process model, defined for a particular product, to be exported into an (operating-system) export file.

The export file thus generated can then be specified as an input when creating a Dimensions base database, the process data in the export file being imported into the product $GENERIC of the newly created base database. See System Administration.

For details on how to create a base database, see CRDB – Create Dimensions Base Database.

To run the expm command, you must either:

- First switch connection to the relevant base database once you have initially connected as SYSTEM, for example, to switch to the base database mydatabase:

SYSTEM> connect mydatabase

and then execute expm without the /basedb parameter at the MYDATABASE> prompt; or

- Remain connected as SYSTEM and execute expm with the /basedb parameter (which is no longer optional in that case).

The full syntax is as follows:

expm "<exportfilename>" [<productid>] [/basedb=<basedb>]

where:

Parameter | Description
<exportfilename> | Specifies the name of the file to contain the exported process model data defined for a particular product. On UNIX, if you want to specify a full pathname, for example, /tmp/test.exp, the <exportfilename> will need to be enclosed in double-quotes (") if run from the database prompt, for example: MYDATABASE> expm "/tmp/test.exp" qlarius If you want to run a similar UNIX command directly from the operating-system prompt, to ensure that the dmdba command gets parsed correctly, the <exportfilename> will need to be enclosed first in single-quotes (') and then further enclosed in double-quotes ("), for example: $ dmdba -s system/manager@dim10 expm "'/tmp/test.exp'" qlarius /basedb=qlarius_cm
<productid> | Specifies the particular product from which the process model is to be exported.
<basedb> | Specifies the optional base database to export, else the current base database is used.

NOTE The new database will only have a $GENERIC product containing the process model inherited from the particular product you based the export on; it will not have any other products until you subsequently create them using the Dimensions DNP command.
To clone the entire database content, you need to use RDBMS export/import utilities such as dm_backup/dm_restore for use with the Serena-Supplied RDBMS or Oracle EXP/IMP for use with Oracle Enterprise 10g or 11g.

SSEQ – Resetting the Sequence Value for a Current Base Database

NOTE You only need to run this command if requested by Support.

This command enables you to reset the RDBMS sequence value for the currently connected base database.

The syntax is as follows:

sseq

CPAS – Changing Passwords for Databases

NOTE Only available, and displayed, when connected to a Serena-Supplied Runtime RDBMS or an Oracle Enterprise database.

This command enables you to change the password associated with a Dimensions CM base database Oracle account.

The syntax is as follows:

cpas <basedb> /new_password=<new_password>

where:

Parameter | Description
<basedb> | Specifies the name of the base database for which the password is to be changed.
<new_password | Specifies the new password.

SPAC– Reporting on Tablespace Usage

NOTE Only available, and displayed, when connected to a Serena-Supplied Runtime RDBMS or an Oracle Enterprise database.

This command enables you to report on the space usage for Dimensions tablespaces.

The syntax is as follows:

spac [/list=<filename>] [/print]

where:

Parameter | Description
/list=<filename> | Specifies an optional filename for the report. By default, the report generated is called dm_space_usage.out.
/print | (Optional) Specifies if the report is to be printed.

INCR – Increasing Database Space Available to a Tablespace

NOTE Only available, and displayed, when connected to a Serena-Supplied Runtime RDBMS or an Oracle Enterprise database.

This command enables you to increase the space available for Dimensions tablespaces.

The syntax is as follows:

incr <tablespacename> /filename=filename

/filesize=<size_in_MB>

where:

Parameter | Description
<tablespacename> | Specifies the tablespace that is to be increased.
/filename | Specifies the name of the data file that is to be created or modified. If the file you specify does not exist, then it will be created.
/filesize | Specifies the size (in MB) to be added.