Table of Contents

Search

  1. Preface
  2. Introduction to Dynamic Data Masking Administration
  3. Authentication
  4. Connection Management
  5. JDBC Client Configuration
  6. ODBC Client Configuration
  7. Access Control
  8. Logs
  9. High Availability
  10. Server Control
  11. Performance Tuning
  12. Troubleshooting

Administrator Guide

Administrator Guide

Import

Import

Imports a Dynamic Data Masking database or security rule set. The Dynamic Data Masking Server must be running.
Use the
import
command to import a Dynamic Data Masking database or security rule set into one or more Dynamic Data Masking Servers. The type of object that you import must be the same type of object that you specify as the location to import the object. For example, you can import a security rule set into a security rule set. You can import an Oracle database into an Oracle database node, but you cannot import an Oracle database into a Sybase database node.
If you do not specify a target Dynamic Data Masking Server, the
import
command imports the object into the local Dynamic Data Masking Server. Use the
-targets
parameter to specify multiple target Dynamic Data Masking Servers.
The command uses the following syntax:
server config import <object full path> <file> [[-targets] user/pwd@host:port [user/pwd@host:port user/pwd@host:port]]
For example, if you exported a database named DEV_SYBASE_DB and you named the file DEV_SYBASE_DB_1, and you want to import the database into the local Dynamic Data Masking Server, you might enter the following command:
server config import "Site\DEV_SYBASE_DB" "DEV_SYBASE_DB_1"
If you want to import the DEV_SYBASE_DB_1 file into multiple Dynamic Data Masking Servers, you might enter the following command:
server config import "Site\DEV_SYBASE_DB" "DEV_SYBASE_DB_1" -targets admin/admin@ABC12345:1111 admin/admin@XYZ98765:2222
The
import
command uses the following parameters:
object full path
The full path in the Management Console where you want to import the object. If the parent path does not exist in the Management Console tree, the command returns an error. If the object does not exist in the path, Dynamic Data Masking creates the object. If the object exists in the path, the object must be the same object type as the object that you want to import.
For example, you want to import a database into the following location in the Management Console tree:
Site\backup\SQL_SERVER_DB
The parent path is Site\backup and the object is SQL_SERVER_DB. The parent path must exist in the Management Console tree. If the object does not exist, Dynamic Data Masking creates a database node named SQL_SERVER_DB.
file
The file name of the object that you want to import.
-targets
Indicates that the following arguments are targets.
user
The Dynamic Data Masking user name that you use to log in to the Dynamic Data Masking Server.
pwd
The password for the Dynamic Data Masking user.
host
The Dynamic Data Masking Server host name or IP address.
port
The Dynamic Data Masking Server listener port.

0 COMMENTS

We’d like to hear from you!