extractData(tableName: String;
executionLocation: Integer;
scriptFilePath: String;
dataFilesPath: String;
rdbDataFilesPath: String;
rdbName: String;
extractHistoricalTables: Boolean;
serverName: String;
extractWorkers: Integer): Process;
The extractData method of the RelationalView class starts the RPS Datapump application on the server node to extract data for the table specified by the tableName parameter or for all tables on an SDS secondary or RPS node.
This method does not apply to ODBC relational views.
You can execute this method on an SDS secondary or an RPS node, but not on the primary node. Running an RPS extract on an SDS node causes tracking to be stopped during the extract.
The extractData method parameters are listed in the following table.
| Parameter | Specifies the … |
|---|---|
| tableName | The name of the table for which data is extracted. If null or an empty string, data for all tables is extracted. |
| executionLocation | The location used for loading the extracted data. Allowed values can be specified using the Load_ServerExecute (0) and Load_ClientExecute (1) RelationalView class constants. |
| scriptFilePath | The output directory for the script files. |
| dataFilesPath | The output directory for the data files. |
| rdbDataFilesPath | The path of the data files directory from the perspective of the RDBMS database. |
| rdbname | The name of the RDBMS database. |
| extractHistoricalTables | If historical table data is to be extracted. |
| serverName | The name of the RDBMS server. |
| extractWorkers | The number of extract worker processes to run. |
The method returns the process of the application that extracts the table data. You can register to receive notifications for events occurring for the process that carries out the data extraction in the following table.
| Process Class Constant | Value |
|---|---|
| RPS_EXTRACT_FAILED_EVENT | 202 |
| RPS_EXTRACT_FINISHED_EVENT | 203 |