Known issues
This section describes the known issues in Hyperscale Compliance.
Release 2025.4.0
|
Key |
Summary |
Workaround |
|---|---|---|
|
DLPXECO-9149
|
Pyspark doesn’t support INT64 timestamp with nanoseconds for parquet file_types. |
You can use pyarrow writer as an alternative. |
| HM-3947 | Oracle: The application expects all of the columns of related composite foreign keys to be present in the Data Set and as a result it fails the job execution when composite primary/unique keys are partially masked (not all of the composite key's columns are masked). | None |
|
HM-3636 |
MSSQL: Unexpected movement of count from constraints (Primary & Unique) to index in postload response. |
None |
|
HM-1397 |
Oracle Load fails for table having triggers only with SQL*Loader-937 error |
None |
|
HM-663 |
Oracle : Load process is failing with "Error disabling constraint" for identity columns. |
None |
Release 2025.3.0
|
Key |
Summary |
Workaround |
|---|---|---|
|
DLPXECO-9149
|
Pyspark doesn’t support INT64 timestamp with nanoseconds for parquet file_types. |
You can use pyarrow writer as an alternative. |
| HM-4379 | MSSQL Unload service fails to initialize | None |
| HM-3947 | Oracle: The application expects all of the columns of related composite foreign keys to be present in the Data Set and as a result it fails the job execution when composite primary/unique keys are partially masked (not all of the composite key's columns are masked). | None |
|
HM-3636 |
MSSQL: Unexpected movement of count from constraints (Primary & Unique) to index in postload response. |
None |
|
HM-1397 |
Oracle Load fails for table having triggers only with SQL*Loader-937 error |
None |
|
HM-663 |
Oracle : Load process is failing with "Error disabling constraint" for identity columns. |
None |
Release 2025.2.0
|
Key |
Summary |
Workaround |
|---|---|---|
|
DLPXECO-9149
|
Pyspark doesn’t support INT64 timestamp with nanoseconds for parquet file_types. |
You can use pyarrow writer as an alternative. |
| DLPXECO-11402 | Snowflake Connector – Jobs may intermittently fail with larger data sizes (over 500 GB) when S3 is used as the staging area. | None |
| HM-3947 | Oracle: The application expects all of the columns of related composite foreign keys to be present in the Data Set and as a result it fails the job execution when composite primary/unique keys are partially masked (not all of the composite key's columns are masked). | None |
|
HM-3636 |
MSSQL: Unexpected movement of count from constraints (Primary & Unique) to index in postload response. |
None |
|
HM-1397 |
Oracle Load fails for table having triggers only with SQL*Loader-937 error |
None |
|
HM-663 |
Oracle : Load process is failing with "Error disabling constraint" for identity columns. |
None |
Release 2025.1.0
|
Key |
Summary |
Workaround |
|---|---|---|
|
DLPXECO-11402 |
Snowflake Connector – Jobs may intermittently fail with larger data sizes (over 500 GB) when S3 is used as the staging area. |
None |
|
HSC- 759 (ECO-9149)
|
Pyspark doesn’t support INT64 timestamp with nanoseconds for parquet file_types. | You can use pyarrow writer as an alternative. |
| HM-3947 | Oracle: The application expects all of the columns of related composite foreign keys to be present in the Data Set and as a result it fails the job execution when composite primary/unique keys are partially masked (not all of the composite key's columns are masked). | None |
|
HM-3636 |
MSSQL: Unexpected movement of count from constraints (Primary & Unique) to index in postload response. |
None |
|
HM-1397 |
Oracle Load fails for table having triggers only with SQL*Loader-937 error |
None |
|
HM-663 |
Oracle : Load process is failing with "Error disabling constraint" for identity columns. |
None |
Release 27.0.0
|
Key |
Summary |
Workaround |
|---|---|---|
|
HSC- 759 (ECO-9149) |
Pyspark doesn’t support INT64 timestamp with nanoseconds for parquet file_types. |
You can use pyarrow writer as an alternative. |
|
HM-3636 |
MSSQL: Unexpected movement of count from constraints (Primary & Unique) to index in postload response. |
None |
|
HM-2593 |
MSSQL - In PreLoad table references not fetched until last level in relationship hierarchy. |
None |
|
HM-1397 |
Oracle Load fails for table having triggers only with SQL*Loader-937 error |
None |
|
HM-663 |
Oracle : Load process is failing with "Error disabling constraint" for identity columns. |
None |
Release 26.0.0
|
Key |
Summary |
Workaround |
|---|---|---|
|
HSC- 759 |
Pyspark doesn’t support INT64 timestamp with nanoseconds for parquet file_types. |
You can use pyarrow writer as an alternative. |
|
HM-3636 |
MSSQL: Unexpected movement of count from constraints (Primary & Unique) to index in postload response. |
None |
|
HM-2593 |
MSSQL - In PreLoad table references not fetched until last level in relationship hierarchy. |
None |
|
HM-1397 |
Oracle Load fails for table having triggers only with SQL*Loader-937 error |
None |
|
HM-663 |
Oracle : Load process is failing with "Error disabling constraint" for identity columns. |
None |
Release 25.0.0
|
Key |
Summary |
Workaround |
|---|---|---|
|
HSC-725 |
The spark session isn't getting modified for different connector-infos such as FS, AWS-with-credentials, AWS-without-credentials. |
None |
|
HSC- 759 |
Pyspark doesn’t support INT64 timestamp with nanoseconds for parquet file_types. |
You can go for pyarrow writer. |
|
HM-3636 |
MSSQL: Unexpected movement of count from constraints (Primary & Unique) to index in postload response. |
None |
|
HM-2593 |
MSSQL - In PreLoad table references not fetched until last level in relationship hierarchy. |
None |
|
HM-1397 |
Oracle Load fails for table having triggers only with SQL*Loader-937 error |
None |
|
HM-663 |
Oracle : Load process is failing with "Error disabling constraint" for identity columns. |
None |
Release 24.0.0
|
Key |
Summary |
Workaround |
|---|---|---|
|
HSC-725 |
The spark session isn't getting modified for different connector-infos such as FS, AWS-with-credentials, AWS-without-credentials. |
None |
|
HSC- 759 |
Pyspark doesn’t support INT64 timestamp with nanoseconds for parquet file_types. |
You can go for pyarrow writer. |
|
HM-3636 |
MSSQL: Unexpected movement of count from constraints (Primary & Unique) to index in postload response. |
None |
|
HM-2593 |
MSSQL - In PreLoad table references not fetched until last level in relationship hierarchy. |
None |
|
HM-1397 |
Oracle Load fails for table having triggers only with SQL*Loader-937 error |
None |
|
HM-663 |
Oracle : Load process is failing with "Error disabling constraint" for identity columns. |
None |
Release 23.0.0
|
Key |
Summary |
Workaround |
|---|---|---|
|
HSC-725 |
The spark session isn't getting modified for different connector-infos, i.e FS, AWS-with-credentials, AWS-without-credentials, etc |
None |
|
HSC-759 |
Pyspark doesn’t support INT64 timestamp with nanoseconds for parquet file_types |
You can go for pyarrow writer. |
|
HM-3685 |
MSSQL: The Unload service fails startup on hosts that do not support IPv6. This issue is caused by the JDWP (Java debug wire protocol) debugging configuration. |
For Docker or Podman Compose, add the environment variable JAVA_TOOL_OPTIONS having value agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=0.0.0.0:9093 under
|
|
HM-3636 |
MSSQL: Unexpected movement of count from constraints (Primary & Unique) to index in postload response |
None |
|
HM-2593 |
MSSQL - In PreLoad table references not fetched till last level in relationship hierarchy |
None |
|
HM-1397 |
Oracle Load fails for table having triggers only with SQL*Loader-937 error |
None |
|
HM-663 |
Oracle : Load process is failing with "Error disabling constraint" for identity columns |
None |
Release 22.0.0
|
Key |
Summary |
Workaround |
|---|---|---|
|
HM-3554 |
[MSSQL]-FILLFACTOR attribute is not included while recreating index on post load |
None |
|
HM-2593 |
MSSQL - In PreLoad table references not fetched till last level in relationship hierarchy |
None |
|
HM-1397 |
Oracle Load fails for table having triggers only with SQL*Loader-937 error |
None |
|
HM-715 |
Parquet connector: compression of source parquet files do not match compression of target parquet files - when using PySpark writer. |
None |
|
HM-709 |
Parquet connector: There is an issue when the source file paths have folder names with only number, ex: '/source/files/1/*'. |
None |
|
HM-701 |
Parquet connector: Providing a delimiter character other than the default character comma will result in a issue when using PySpark writer |
None |
|
HM-663 |
Oracle : Load process is failing with "Error disabling constraint" for identity columns |
None |
Release 21.0.0
|
Key |
Summary |
Workaround |
|---|---|---|
|
HM-663 |
Oracle: The load process is failing with "Error disabling constraint" for identity columns |
None |
|
HM-1397 |
Oracle Load fails for table having triggers only with SQL*Loader-937 error |
None |
|
HM-2593 |
MSSQL - In PreLoad table references not fetched till last level in relationship hierarchy |
None |
Release 20.0.0
|
Key |
Summary |
Workaround |
|---|---|---|
|
HM-663 |
Oracle: The load process is failing with "Error disabling constraint" for identity columns |
None |
|
HM-1397 |
Oracle Load fails for table having triggers only with SQL*Loader-937 error |
None |
|
HM-2593 |
MSSQL - In PreLoad table references not fetched till last level in relationship hierarchy |
None |
Release 19.0.0
|
Key |
Summary |
Workaround |
|---|---|---|
|
HM-663 |
Oracle: The load process is failing with "Error disabling constraint" for identity columns |
None |
|
HM-1397 |
Oracle Load fails for table having triggers only with SQL*Loader-937 error |
None |
|
HM-2593 |
MSSQL - In PreLoad table references not fetched till last level in relationship hierarchy |
None |
|
HSC-558 |
Delimited load service with "perform_join=false" fails for multiple source files in a single data set for S3 target location |
None |
Release 18.0.0
|
Key |
Summary |
Workaround |
|---|---|---|
|
HM-663 |
Oracle: The load process is failing with "Error disabling constraint" for identity columns |
None |
|
HM-1397 |
Oracle Load fails for table having triggers only with SQL*Loader-937 error |
None |
|
HM-2593 |
MSSQL - In PreLoad table references not fetched till last level in relationship hierarchy |
None |
Release 17.0.0
|
Key |
Summary |
Workaround |
|---|---|---|
|
HM-663 |
Oracle: The load process is failing with "Error disabling constraint" for identity columns |
None |
|
HM-1397 |
Oracle Load fails for table having triggers only with SQL*Loader-937 error |
None |
|
HM-2593 |
MSSQL - In PreLoad table references not fetched till last level in relationship hierarchy |
None |
Release 16.0.0
|
Key |
Summary |
Workaround |
|---|---|---|
|
HM-663 |
Oracle: The load process is failing with "Error disabling constraint" for identity columns |
None |
|
HM-1397 |
Oracle Load fails for table having triggers only with SQL*Loader-937 error |
None |
|
HM-1705 |
Improper error message in Hyperscale status response if CCE gets mount file system connection error |
None |
|
HM-2593 |
MSSQL - In PreLoad table references not fetched till last level in relationship hierarchy |
None |
Release 15.0.0
|
Key |
Summary |
Workaround |
|---|---|---|
|
HM-663 |
Oracle: The load process is failing with "Error disabling constraint" for identity columns |
None |
|
HM-1397 |
Oracle Load fails for table having triggers only with SQL*Loader-937 error |
None |
|
HM-1705 |
Improper error message in Hyperscale status response if CCE gets mount file system connection error |
None |
|
HM-2593 |
MSSQL - In PreLoad table references not fetched till last level in relationship hierarchy |
None |
Release 14.0.0
|
Key |
Summary |
Workaround |
|---|---|---|
|
HM-663 |
Oracle: The load process is failing with "Error disabling constraint" for identity columns |
None |
|
HM-1397 |
Oracle Load fails for table having triggers only with SQL*Loader-937 error |
None |
|
HM-1705 |
Improper error message in Hyperscale status response if CCE gets mount file system connection error |
None |
|
HM-2413 |
In PreLoad table references not fetched till last level in relationship hierarchy |
None |
Release 13.0.0
Delimited Files Connector
|
Key |
Summary |
Workaround |
|---|---|---|
|
HSC-174 |
Delimited unload service does not show incremental unload row count, it always should unloaded count is the same as the total count |
None |
|
HSC-176 |
Delimited connector: values with data type double and int64 will always be converted into a string |
None |
|
HSC-177 |
Delimited connector: Irrespective of user provided enclosure character, the output strings will be quoted using double quotes |
None |
|
Key |
Summary |
Workaround |
|---|---|---|
|
HM-663 |
Oracle: The load process is failing with "Error disabling constraint" for identity columns |
None |
|
HM-1397 |
Oracle Load fails for table having triggers only with SQL*Loader-937 error |
None |
|
HM-1705 |
Improper error message in Hyperscale status response if CCE gets mount file system connection error |
None |
|
HM-2413 |
In PreLoad table references not fetched till last level in relationship hierarchy |
None |
Release 12.0.0
Delimited Files Connector
|
Key |
Summary |
Workaround |
|---|---|---|
|
HSC-174 |
Delimited unload service does not show incremental unload row count, it always should unloaded count is the same as the total count |
None |
|
HSC-176 |
Delimited connector: values with data type double and int64 will always be converted into a string |
None |
|
HSC-177 |
Delimited connector: Irrespective of user provided enclosure character, the output strings will be quoted using double quotes |
None |
|
HSC-178 |
Delimited load service will show the status as FAILED while it is waiting for all split files to be masked in order to perform join |
None |
|
HM-2443 |
Masking service is mapping the wrong file metadata when multiple data_info objects with varying delimiters are passed during data-sets creation. |
Create individual data-sets for files with different delimiter character. |
Release 11.0.0
|
Key |
Summary |
Workaround |
|---|---|---|
|
HM-663 |
Oracle: The load process is failing with "Error disabling constraint" for identity columns |
None |
|
HM-1397 |
Oracle Load fails for table having triggers only with SQL*Loader-937 error |
None |
|
HM-1705 |
Improper error message in Hyperscale status response if CCE gets mount file system connection error |
None |
Release 10.0.0
|
Key |
Summary |
Workaround |
|---|---|---|
|
HM-663 |
Oracle: The load process is failing with "Error disabling constraint" for identity columns |
None |
|
HM-1397 |
Oracle Load fails for table having triggers only with SQL*Loader-937 error |
None |
|
HM-1705 |
Improper error message in Hyperscale status response if CCE gets mount file system connection error |
None |
Release 9.0.0
|
Key |
Summary |
Workaround |
|---|---|---|
|
HM-663 |
Oracle: The load process is failing with "Error disabling constraint" for identity columns |
None |
|
HM-1397 |
Oracle Load fails for tables having triggers only with SQL*Loader-937 error |
None |
|
HM-1705 |
Improper error message in Hyperscale status response if CCE gets mount file system connection error |
None |
Release 8.0.0
|
Key |
Summary |
Workaround |
|---|---|---|
|
HM-663 |
Oracle: The load process is failing with "Error disabling constraint" for identity columns |
None |
|
HM-1397 |
Oracle Load fails for tables having triggers only with SQL*Loader-937 error |
None |
|
HM-1705 |
Improper error message in Hyperscale status response if CCE gets mount file system connection error |
None |
Release 7.0.0.0
|
Key |
Summary |
Workaround |
|---|---|---|
|
HM-663 |
Oracle: The load process is failing with "Error disabling constraint" for identity columns |
None |
|
HM-1397 |
Oracle Load fails for tables having triggers only with SQL*Loader-937 error |
None |
|
HM-1705 |
Improper error message in Hyperscale status response if CCE gets mount file system connection error |
None |
Release 6.0.0.0
|
Key |
Summary |
Workaround |
|---|---|---|
|
HM-663 |
Oracle: The load process is failing with "Error disabling constraint" for identity columns |
None |
|
HM-1397 |
Oracle: Dataset having any one entry with invalid schema leaves indexes of other tables as UNUSABLE |
None |
|
HM-1705 |
Improper error message in Hyperscale status response if CCE gets mount file system connection error |
None |
Release 5.0.0.0
|
Key |
Summary |
Workaround |
|---|---|---|
|
HM-291 |
Hyperscale job execution with an intelligent load balancer configured is stuck in a loop if the job's max memory is more than totalAllocatedMemoryForJobs |
Change the max memory to a value under the value of |
|
HM-652 |
Job execution is stuck in a running state if the mount server is powered off |
Check the health of the mount server before starting a job. |
|
HM-663 |
Oracle: Load process is failing with "Error disabling constraint" for identity columns |
None |
|
HM-718 |
Not all data on the mount server is cleaned up if the continuous compliance engine is stopped |
|
|
HM-745 |
The table name is not present in the error message while enabling/disabling triggers, indexes, constraints |
Check the logs in container logs to get table details |
|
HM-817 |
Intermittently job fails with ORA-02270: no matching unique or primary key for this column-list |
Restart the job using |
|
HM-821 |
Hyperscale job does not handle post-load task properly during restart if failed in pre-load (disabling trigger/indexes/constraints) steps |
After job execution is completed successfully, check and manually enable the disabled constraints. |
|
HM-1251 |
MSSQL: Row is not loaded if masked BIT type column has values other than true(1),false(0) or NULL |
None |
|
HM-1366 |
NPE displayed in hyperscale masking service logs just after masking task is done |
None |
|
HM-1397 |
Oracle Load fails for table having triggers only with SQL*Loader-937 error |
None |
|
HM-1512 |
received_objects in Load step are more than succeeded_objects in Masking step intermittently |
None |
|
HM-1513 |
MSSQL - Slowness while performing load with large tables( more that 4M rows and 10 Columns) |
None |
|
HM-1521 |
MSSQL - Post load fails with 'transaction log is full due to 'ACTIVE_TRANSACTION' for large tables |
None |
|
HM-1528 |
Initial delay in updating response of unload/masking/load execution objects with large number of tables |
None |
|
HM-1561 |
Oracle Load Failure: sql loader control files doesn't contain character length when column size is less than 256 CHAR |
None |
|
HM-1705 |
Improper error message in Hyperscale status response if CCE gets mount file system connection error |
None |
Release 4.1.0
|
Key |
Summary |
Workaround |
|---|---|---|
|
HM-291 |
Hyperscale job execution with intelligent load balancer configured is stuck in a loop if job’s max memory is more than totalAllocatedMemoryForJobs |
Change the max memory to a value under the value of |
|
HM-652 |
Job execution is stuck in running state if mount server is powered off |
Check the health of mount server before starting a job. |
|
HM-663 |
Load process is failing with “Error disabling constraint” for identity columns |
None |
|
HM-718 |
Not all data on mount server is cleaned up if masking engine is stopped |
Cleanup up the data manually from the mount server. |
|
HM-745 |
Table name is not present in error message while enabling/disabling triggers,indexes,constraints |
Check the logs in container logs to get table details |
|
HM-817 |
Intermittently job fails with ORA-02270: no matching unique or primary key for this column-list |
Restart the job using |
|
HM-821 |
Hyperscale job does not handle post load task properly during restart if failed in pre-load (disabling trigger/indexes/constraints) steps |
After job execution is completed successfully, check and manually enable the disabled constraints. |
|
HM-1155 |
Diagnosibility: How do I tell which masking job on the masking engine relates to the failed message on the HS Jobs API status |
Check the error details in masking service logs |
|
HM-1168 |
The error text is inaccurate, and doesn’t contain enough information to diagnose it without accessing logs on the Hyperscale server. |
Check the error details in the logs |
|
HM-1561 |
Oracle Load Failure: sql loader control files doesn't contain character length when column size is less than 256 CHAR |
None |
|
HM-1705 |
Improper error message in Hyperscale status response if CCE gets mount file system connection error |
None |
Release 4.0.0
|
Key |
Summary |
Workaround |
|---|---|---|
|
HM-291 |
Hyperscale job execution with intelligent load balancer configured is stuck in a loop if job’s max memory is more than totalAllocatedMemoryForJobs |
Change the max memory to a value under the value of |
|
HM-652 |
Job execution is stuck in running state if mount server is powered off |
Check the health of mount server before starting a job. |
|
HM-663 |
Load process is failing with “Error disabling constraint” for identity columns |
None |
|
HM-718 |
Not all data on mount server is cleaned up if masking engine is stopped |
Cleanup up the data manually from the mount server. |
|
HM-745 |
Table name is not present in error message while enabling/disabling triggers,indexes,constraints |
Check the logs in container logs to get table details |
|
HM-817 |
Intermittently job fails with ORA-02270: no matching unique or primary key for this column-list |
Restart the job using |
|
HM-821 |
Hyperscale job does not handle post load task properly during restart if failed in pre-load (disabling trigger/indexes/constraints) steps |
After job execution is completed successfully, check and manually enable the disabled constraints. |
|
HM-1366 |
NPE displayed in hyperscale masking service logs just before cleanup is performed |
None |
|
HM-1397 |
Load fails for table having triggers only with SQL*Loader-937 error |
None |
|
HM-1561 |
Oracle Load Failure: sql loader control files doesn't contain character length when column size is less than 256 CHAR |
None |
|
HM-1705 |
Improper error message in Hyperscale status response if CCE gets mount file system connection error |
None |
Release 3.0.0.1
|
Key |
Summary |
Workaround |
|---|---|---|
|
HM-177 |
Able to POST /hyperscale-masking/jobs with min job memory > max job memory |
Change the max job memory value to higher than min job memory in API request. |
|
HM-291 |
Hyperscale job execution with intelligent load balancer configured is stuck in a loop if job’s max memory is more than totalAllocatedMemoryForJobs |
Change the max memory to a value under the value of |
|
HM-652 |
Job execution is stuck in running state if mount server is powered off |
Check the health of mount server before starting a job. |
|
HM-663 |
Load process is failing with “Error disabling constraint” for identity columns |
None |
|
HM-684 |
Hypescale does not support other TIMESTAMP(6) datatype variations apart from TIMESTAMP |
None |
|
HM-718 |
Not all data on mount server is cleaned up if batch masking service is stopped |
Cleanup up the data manually from mount server. |
|
HM-745 |
Table name is not present in error message while enabling/disabling triggers,indexes,constraints |
Check the logs in container logs to get table details. |
|
HM-754 |
Able to POST/PUT a connector with whitespace as jdbc_url, username, password |
Remove white space and use valid values for jdbc_url, username and password. |
|
HM-789 |
Error message upon not setting ‘ssl’ field to False indicates ‘insecure_ssl’ property which no longer exists in the schema |
None |
|
HM-817 |
Intermittently job fails with ORA-02270: no matching unique or primary key for this column-list |
Restart the job using |
|
HM-821 |
Hyperscale job does not handle post load task properly during restart if failed in pre-load (disabling trigger/indexes/constraints) steps |
After job execution is completed successfully, check and manually enable the disabled constraints. |
|
HM-935 |
Load service fails when source DB contains BLOB type data that is not simple text file data |
None |
|
HM-1561 |
Oracle Load Failure: sql loader control files doesn't contain character length when column size is less than 256 CHAR |
None |
|
HM-1705 |
Improper error message in Hyperscale status response if CCE gets mount file system connection error |
None |
Release 3.0.0
|
Key |
Summary |
Workaround |
|---|---|---|
|
HM-177 |
Able to POST /hyperscale-masking/jobs with min job memory > max job memory |
Change the max job memory value to higher than min job memory in API request. |
|
HM-291 |
Hyperscale job execution with intelligent load balancer configured is stuck in a loop if job’s max memory is more than totalAllocatedMemoryForJobs |
Change the max memory to a value under the value of |
|
HM-652 |
Job execution is stuck in running state if mount server is powered off |
Check the health of mount server before starting a job. |
|
HM-663 |
Load process is failing with “Error disabling constraint” for identity columns |
None |
|
HM-684 |
Hypescale does not support other TIMESTAMP(6) datatype variations apart from TIMESTAMP |
None |
|
HM-718 |
Not all data on mount server is cleaned up if batch masking service is stopped |
Cleanup up the data manually from mount server. |
|
HM-745 |
Table name is not present in error message while enabling/disabling triggers,indexes,constraints |
Check the logs in container logs to get table details. |
|
HM-754 |
Able to POST/PUT a connector with whitespace as jdbc_url,username,password |
Remove white space and use valid values for jdbc_url, username and password. |
|
HM-789 |
Error message upon not setting ‘ssl’ field to False indicates ‘insecure_ssl’ property which no longer exists in the schema |
None |
|
HM-817 |
Intermittently job fails with ORA-02270: no matching unique or primary key for this column-list |
Restart the job using |
|
HM-821 |
Hyperscale job does not handle post load task properly during restart if failed in pre-load (disabling trigger/indexes/constraints) steps |
After job execution is completed successfully, check and manually enable the disabled constraints. |
|
HM-858 |
Status of sub task coming wrong when overall execution failed |
None |
|
HM-873 |
Intermittently there is a mismatch in loaded_rows displayed in load task vs the actual rows loaded in target table |
None |
|
HM-915 |
Load: driver support plugin throws ORA-02297: cannot disable constraint - dependencies exist error for foreign key |
None |
|
HM-935 |
Load service fails when source DB contains BLOB type data that is not simple text file data |
None |
|
HM-1561 |
Oracle Load Failure: sql loader control files doesn't contain character length when column size is less than 256 CHAR |
None |
|
HM-1705 |
Improper error message in Hyperscale status response if CCE gets mount file system connection error |
None |
Release 2.0.0
The following is a list of the known issues in the Hyperscale Compliance version 2.0.0.
|
Key |
Summary |
Workaround |
|---|---|---|
|
HM-294 |
Updated file format is not POST’ed on the Continuous Compliance Engine if file format name is same |
|
|
HM-291 |
Hyperscale job execution with intelligent load balancer configured is stuck in a loop if job’s max memory is more than totalAllocatedMemoryForJobs |
None |
|
HM-216 |
POST/PUT /data-sets accepts duplicate values as source_files path in Single File Info Object |
None |
|
HM-177 |
Able to POST /hyperscale-masking/jobs with min job memory > max job memory |
None |
|
HM-1705 |
Improper error message in Hyperscale status response if CCE gets mount file system connection error |
None |