Configuring › How to Implement Multi-Tenancy › Utilities Used for Multi-Tenancy › pdm_tenant_extract—Extracting Tenant Data

pdm_tenant_extract—Extracting Tenant Data

The pdm_tenant_extract utility extracts all data for a specified tenant from the database. It extracts the data in pdm_userload format so that it can easily be loaded into another database. This utility has the following syntax:

pdm_tenant_extract -h | -c control_file [-d domsrvr] [-g yes|no] [-o output_file]	-p phase  [[-t tenant_name]…] [-Q] [table1 [table2...]]

-h

Displays the usage information for pdm_tenant_extract.

-c control_file

Specifies the location of the control file for this tenant extract. For the Initial phase, the file is created in the specified location (and must not already exist). The file must exist for the Update and Final phases.

-d domsrvr

(Optional) Specifies a domsrvr to use.

-g yes|no

(Optional) Specifies whether or not public data is included in the output file. If this argument is not specified, public data from all tables is included.

-o output_file

(Optional) Specifies the location of the output file. If this argument is not specified, output is directed to stdout.

-p phase

Specifies the phase of the extract. Use one of the following values:

I—Initial

U—Update

F—Final

-t tenant_name

Specifies the name of a tenant to be extracted. This argument is required for the Initial phase and can be repeated for multiple tenants. It is not valid on the Update and Final phase.

-Q

Specifies quick query processing to execute database queries as fast as possible. If this argument is not specified, the utility uses background query processing so that queries run only when the system is otherwise idle

table1 [table2...]

(Optional) Specifies the tables to extract. If omitted, all tables are extracted.

Important! The output from the initial phase must be loaded into a database that has never been used for CA SDM or for any other product. Each table loaded from initial phase data is truncated prior to the load, which could cause loss of data if the database is already in use.

Note: To avoid referential problems during the data load, run the appropriate drop constraints script ($NX_ROOT/samples/views/Oracle/OracleDropConstraints.sql or $NX_ROOT/samples/views/SQLServer/SQLDropConstraints.sql ). After the loads complete, re-apply the constraints with the appropriate xxxAddConstraints.sql script found in the same directory.

Important! On UNIX, the LIBPATH must be set before running several CA SDM utilities. Use pdm_task to set the LIBPATH before running a utility. For example, input "pdm_task pdm_clean_attachments ...".

More information:

How to Export and Import Tenant Data