Skip to content

Commit f5899ad

Browse files
Merge pull request #230877 from whhender/patch-83
Update register-scan-oracle-source.md
2 parents 0e1edd6 + 8e42b68 commit f5899ad

File tree

1 file changed

+7
-2
lines changed

1 file changed

+7
-2
lines changed

articles/purview/register-scan-oracle-source.md

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.author: jingwang
66
ms.service: purview
77
ms.subservice: purview-data-map
88
ms.topic: how-to
9-
ms.date: 11/01/2022
9+
ms.date: 03/15/2023
1010
ms.custom: template-how-to, ignite-fall-2021
1111
---
1212

@@ -66,7 +66,12 @@ Currently, the Oracle service name isn't captured in the metadata or hierarchy.
6666
6767
### Required permissions for scan
6868

69-
Microsoft Purview supports basic authentication (username and password) for scanning Oracle. The Oracle user must have read access to system tables in order to access advanced metadata. For classification, user also needs to have read permission on the tables/views to retrieve sample data.
69+
Microsoft Purview supports basic authentication (username and password) for scanning Oracle. The Oracle user must have read access to system tables in order to access advanced metadata.
70+
71+
For classification, user also needs to be the owner of the table.
72+
73+
>[!IMPORTANT]
74+
>If the user is not the owner of the table, the scan will run successfully and ingest metadata, but will not identify any classifications.
7075
7176
The user should have permission to create a session and role SELECT\_CATALOG\_ROLE assigned. Alternatively, the user may have SELECT permission granted for every individual system table that this connector queries metadata from:
7277

0 commit comments

Comments
 (0)