Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA Enterprise SCADA

TABLE OF CONTENTS

Understanding DPutil and DPDirect

Save PDF
Save selected topicSave selected topic and subtopicsSave all topics
Share
Share to emailCopy topic URL
  • Last UpdatedJul 05, 2024
  • 2 minute read

DPutil contains a source database option with the syntax -S [system: [RDBMS:]][DP:userid/paswd@]service. The examples shown in this document only show the use of the service value, as the -S option is most often used with defaulted parameters. To find the default -S configuration for your system, use DPutil -h.

  • For Sybase, the service name is found in the sql.ini interfaces file.

  • For Oracle, the service name is the SERVICE_NAME or SID in the tnsname.ora file.

  • For Microsoft SQL Server, the service name is typically the DAL DriverAlias, and the system name may be used to specify the DAL configuration directory from which to load the DAL configuration (for example, es:MS:Historical); if the service name is not a DAL DriverAlias, then it is assumed to be a SQLClient Data Source name used to make an Open Database Connectivity (ODBC) connection (that is, the same server name as you would use in the Microsoft SQL Server Management Studio utility).

DPutil and DPdirect expect a destination database service name to be provided with the syntax -D.

  • For destination databases within the same domain, the service name is typically -D [system]\[RDBMS]; for example, -D main\oasyshdb.

  • For destination databases located in an untrusted domain, the database name must be qualified with a Datapump dedicated Data Access Layer (DAL) connection type and alias, as well as a Remote Client Service (RCS); for example, -D main:MSDAL:Dir=sub\\remote_RCS_XFER;Alias=Historical_XFER.

    Where:

    • main is the DPSystem system.

    • sub is the destination system in the untrusted domain.

    • MSDAL is DAL driver.

    • remote_RCS_XFER is the Datapump-dedicated RCS.

    • Historical_XFER is configured as the Datapump-dedicated DAL alias.

The DPutil command examples used in this configuration document, by default, support a distributed AVEVA Enterprise SCADA system. If you are configuring Datapump on a non-distributed system (that is, non dataset-aware), then use the DPutil -T NoDataset option. If you are configuring global data sets (that is, no dataset ID specified), then use the -n option.
 
All generic Datapump tables and procedures are part of the xosapp database. All tables and procedures created to support datapumping a specific database (for example, accum) will be created in that specific database.

Related Links