Migrating Tokenized Unicode Data

Mon, 01 Jan 0001 00:00:00 +0000

The procedure to migrate tokenized Unicode data from and to a Teradata database are listed below.

This section is only applicable for Legacy Unicode and Base64 Unicode data element.
This section considers the Teradata database for reference.
In addition to the Teradata database, the Big Data Protector works with other databases, such as Netezza and Greenplum.

Migrating Tokenized Unicode Data from a Teradata Database

This section describes the task to unprotect the tokenized Unicode data in Hive, Impala, or Spark, which was tokenized in the Teradata database using the Protegrity Database Protector and then migrated to Hive, Impala, MapReduce, or Spark.

Return Codes for the Big Data Protector

Mon, 01 Jan 0001 00:00:00 +0000

If you are using the Big Data Protector and any failures occur, then the protector throws an exception. The exception consists of an error code and error message. All the possible error codes and error messages are described below.

The following table lists all errors returned from the Core layer that are logged.

Code	Error	Error Message
0	NONE
1	USER_NOT_FOUND	The username could not be found in the policy.
2	DATA_ELEMENT_NOT_FOUND	The data element could not be found in the policy.
3	PERMISSION_DENIED	The user does not have the appropriate permissions to perform the requested operation.
4	TWEAK_NULL	Tweak is null.
5	INTEGRITY_CHECK_FAILED	Integrity check failed.
6	PROTECT_SUCCESS	Data protect operation was successful.
7	PROTECT_FAILED	Data protect operation failed.
8	UNPROTECT_SUCCESS	Data unprotect operation was successful.
9	UNPROTECT_FAILED	Data unprotect operation failed.
10	OK_ACCESS	The user has appropriate permissions to perform the requested operation but no data has been protected/unprotected.
11	INACTIVE_KEYID_USED	Data unprotect operation was successful with use of an inactive keyid.
12	INVALID_PARAM	Input is null or not within allowed limits.
13	INTERNAL_ERROR	Internal error occurring in a function call after the Core Provider has been opened.
14	LOAD_KEY_FAILED	Failed to load data encryption key.
15	TWEAK_INPUT_TOO_LONG	Tweak input is too long.
17	INIT_FAILED	Failed to initialize the CORE - This is a fatal error
19	UNSUPPORTED_TWEAK	Unsupported tweak action for the specified FPE data element.
20	OUT_OF_MEMORY	Failed to allocate memory.
21	BUFFER_TOO_SMALL	Input or output buffer is too small.
22	INPUT_TOO_SHORT	Data is too short to be protected/unprotected.
23	INPUT_TOO_LONG	Data is too long to be protected/unprotected.
25	USERNAME_TOO_LONG	Username too long.
26	UNSUPPORTED	Unsupported algorithm or unsupported action for the specific data element.
27	APPLICATION_AUTHORIZED	Application has been authorized.
28	APPLICATION_NOT_AUTHORIZED	Application has not been authorized.
31	EMPTY_POLICY	Policy not available.
40	LICENSE_EXPIRED	No valid license or current date is beyond the license expiration date.
41	METHOD_RESTRICTED	The use of the protection method is restricted by license.
42	LICENSE_INVALID	Invalid license or time is before licensestart.
44	INVALID_FORMAT	The content of the input data is not valid.
49	LOG_UNSUPPORTED_ENCODING	Unsupported input encoding for the specific data element.
50	REPROTECT_SUCCESS	Data reprotect operation was successful.
51	LOG_LOG_UNREACHABLE	Failed to send logs, connection refused.

The following table lists all the error messages returned from the Core layer that are NOT logged.

Additional Information on

Migrating Tokenized Unicode Data

Migrating Tokenized Unicode Data from a Teradata Database

Return Codes for the Big Data Protector