Known Issues
This section describes known issues fixed in Hyperscale Compliance.
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 totalAllocatedMemoryForJobs property configured on the Continuous Compliance Engine. |
| HM-652 | Job execution is stuck in running state if mount server is powered off | Check the health of the mount server before starting the 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 mount server. |
| HM-745 | Table name is not present in error message while enabling/disabling triggers,indexes,constraints | Check the logs in the container logs to get the table details. |
| HM-812 | Application on registered masking engine is not deleted with cleanup | None |
| HM-813 | Dataset API requires user to specify schema_name with every table_name, which is not supported by Hyperscale job | Create a Hyperscale dataset for all the source and target tables present in the same schema. Use a different job to mask tables in different schemas. |
| HM-817 | Intermittently job fails with ORA-02270: no matching unique or primary key for this column-list | Restart the job using PUT /executions/{id}/restart. |
| 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, enable the disabled constraints manually. |
| HM-826 | hashicorp_vault_username_command_args field is displayed for a normal non-vault engine on restored VM | Check if any vaults are present using GET /vaults/hashicorp API (if not, then engine is not using any vaults). In case of presence of any vault (or multiple engines), can confirm with the customer (on what engines are actually registered using vaults.) |
| HM-1163 | Verify NFS mounts on masking engines prior to resuming a failed job | Use the API for each Continuous Compliance Engine, and manually remove the NFS mounts. |
| HM-1366 | NPE displayed in hyperscale masking service logs just before cleanup is performed | None |
| HM-1382 | Dataset having any one entry with invalid schema leaves indexes of other tables as UNUSABLE | None |
| HM-1397 | Load fails for table having triggers only with SQL*Loader-937 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 totalAllocatedMemoryForJobs property configured on Continuous Compliance Engine. |
| 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-812 | Application on registered masking engine is not deleted with cleanup | None |
| HM-813 | Dataset API requires user to specify schema_name with every table_name, which is not supported by Hyperscale job | Create a Hyperscale dataset for all source tables present in same schema and all target tables present in same schema. Use different job to mask tables in different schemas. |
| HM-817 | Intermittently job fails with ORA-02270: no matching unique or primary key for this column-list | Restart the job using PUT /executions/{id}/restart and it will succeed. |
| 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-826 | hashicorp_vault_username_command_args field is displayed for a normal non-vault engine on restored VM | Check if any vaults are present using GET /vaults/hashicorp API(if not, then engine is not using any vaults). In case of presence of any vault or multiple engines, can confirm with the customer (on what engines are actually registered using vaults). |
| 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-1163 | Verify NFS mounts on masking engines prior to resuming a failed job | Use the API for each masking engine, and manually remove the NFS mounts. |
| 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 |
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 totalAllocatedMemoryForJobs property configured on Continuous Compliance Engine. |
| 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-812 | Application on registered masking engine is not deleted with cleanup | None |
| HM-813 | Dataset API requires you to specify schema_name with every table_name which is not supported by Hyperscale job | Create a Hyperscale dataset for all source and target tables present in same schema. Use different job to mask tables in different schemas. |
| HM-817 | Intermittently job fails with ORA-02270: no matching unique or primary key for this column-list | Restart the job using PUT /executions/{id}/restart and it will succeed. |
| 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-826 | hashicorp_vault_username_command_args field is displayed for a normal non-vault engine on restored VM | Check if any vaults are present using GET /vaults/hashicorp API(if not, then engine is not using any vaults). |
| HM-935 | Load service fails when source DB contains BLOB type data that is not simple text file data | 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 totalAllocatedMemoryForJobs property configured on Continuous Compliance Engine. |
| 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-812 | Application on registered masking engine is not deleted with cleanup | None |
| HM-813 | Dataset API requires you to specify schema_name with every table_name which is not supported by Hyperscale job | Create a Hyperscale dataset for all source and target tables present in same schema. Use different job to mask tables in different schemas. |
| HM-817 | Intermittently job fails with ORA-02270: no matching unique or primary key for this column-list | Restart the job using PUT /executions/{id}/restart and it will succeed. |
| 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-826 | hashicorp_vault_username_command_args field is displayed for a normal non-vault engine on restored VM | Check if any vaults are present using GET /vaults/hashicorp API(if not, then engine is not using any vaults). |
| 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 |
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 |