Why Cannot I Find a Table in an Existing Database When Creating a Database Data Masking Task?
If you selected an existing DB instance when you created a database masking task but could not find the table in the DB instance, DSC does not have the authorization.
Background
If you granted only the read-only permission of an RDS database to DSC, DSC can identify sensitive data but cannot mask data in the database.
Cause
You do not have the read and write permissions of the database.
Solutions
- Delete the database instance.
- Grant the read and write permission of the database instance to DSC by referring to Adding an RDS Database.
If the quota is finished when you authorize database permissions, purchase an extension package by referring to Upgrading Edition and Specifications. One extension package offers one database instance (RDS or DWS database, self-built database on ECSs, DLI, CSS, and big data on an ECS).
Sensitive Data Identification and Masking FAQs
- What Services Can Use DSC to Scan for Sensitive Data?
- How Long Does It Take for DSC to Identify and Mask Sensitive Data?
- What Are the Built-in Identification Rules of DSC?
- What Are the Identification Templates Supported by DSC?
- Does Data Masking Affect My Raw Data?
- Does DSC Have Specific Requirements on the Character Set for Which Sensitive Data Is to Be Identified and Masked?
- Why Cannot I Find a Table in an Existing Database When Creating a Database Data Masking Task?
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore
