Data catalog not showing up classifications and metadata as discovered by Scanning of Oracle assets - Purview

Roopansh Gupta 0

We are scanning an Oracle DB from Purview and the scan shows that the data that has been scanned has 60% of the assets classified and also shows that there is metadata (relationships and lineage) related to the assets as can be seen below.
Data scan results

But the data catalog and data estate insights fail to identify these classifications and shows very limited amount of information, as can be seen below:

User's image

I have owner permissions to the database, Data Estate Insights has been refreshed properly.
Some days before, I ran the scans without being the owner, and the classified assets were showing in Insights, but after that I have rerun the scans with the owner role, even then the number of classifications showing up are extremely low. (Just 31 out of 70000 assets)

@BhargavaGunnam-MSFT @purview @purview 03 @Purview Policies Team @PurviewDev @Purview Test001 @purview01 @KranthiPakala-MSFT @PRADEEPCHEEKATLA-MSFT @ShaikMaheer-MSFT Or anyone with the right info.

Please help debug this.
URGENT

PRADEEPCHEEKATLA-MSFT 84,771 Reputation points Microsoft Employee

2023-12-18T10:13:32.0166667+00:00

@Roopansh Gupta - I agree that this issue looks strange and I wasn't able to reproduce this issue. If you have a support plan could you please file a support ticket for deeper investigation and do share the SR# with us?
PRADEEPCHEEKATLA-MSFT 84,771 Reputation points Microsoft Employee

2023-12-20T04:41:08.4866667+00:00

@Roopansh Gupta - Did you get a chance to open a support ticket?
Roopansh Gupta 0 Reputation points

2023-12-21T04:20:33.97+00:00

@PRADEEPCHEEKATLA-MSFT Yeah it's not even letting raise a ticket. I am a "Support Request Contributor" at the resource group level. That is not sufficient?
Roopansh Gupta 0 Reputation points

2023-12-21T04:32:15.17+00:00

The same is happening with the SQL Server data source. And SQL Server does not even require me to be an owner of the table, just a db_datareader role is required, even then, it is showing some 200 assets classified under the scan results. But the "Data Catalog" has nothing to show under the classifications section.
Roopansh Gupta 0 Reputation points

2023-12-21T04:48:23.77+00:00

@PRADEEPCHEEKATLA-MSFT For SQL Server data also, it is doing the same. I have the db_datareader role and public for the Master database. Even then, no classifications in the Data Catalog. Is owner role required for SQL Server data too, though this is nowhere mentioned in the MS documentation
PRADEEPCHEEKATLA-MSFT 84,771 Reputation points Microsoft Employee

2024-01-08T06:23:29.92+00:00

@Roopansh Gupta - Apologize for the delay in response.

Have you resolved the issue or still experiencing the same issue?
Roopansh Gupta 0 Reputation points

2024-01-09T05:37:20.0533333+00:00

Still the same issue
PRADEEPCHEEKATLA-MSFT 84,771 Reputation points Microsoft Employee

2024-01-10T01:47:00.8466667+00:00

@Roopansh Gupta - I agree that this issue looks strange and I wasn't able to reproduce this issue. If you have a support plan could you please file a support ticket for deeper investigation and do share the SR# with us?
PRADEEPCHEEKATLA-MSFT 84,771 Reputation points Microsoft Employee

2024-01-15T23:23:49.29+00:00

@Roopansh Gupta - Did you get a chance to open a support ticket?
Roopansh Gupta 0 Reputation points

2024-01-17T01:18:38.35+00:00
Hey @PRADEEPCHEEKATLA-MSFT , I did raise the ticket. Here is the number: 2401100030001208.

You might be requiring some specific information to check things, so here are some that I think might help:

One of the scans (Scan-OPHDB) is “71ac5875-8f4f-476d-a7de-6bdb2de3608f” shows assets classified to be 982 and the relationships ingested to be 206, but veyr few are to be seen in the Data Catalog.Here is the Run ID for another scan which discovered 40,000 of the 74,000 assets, which is “983694c2-baf8-4f79-8628-fcba5093ac9f” and the name of the scan is “Scan-CARDB” This one classifies nothing, 0 assets.

Here is a screenshot for the “Data Estate Health”. It is identifying some classifications, but that is very limited information. Main concern is the SQL Server, which just classified nothing.

Following are the only classifications identified based on the Data Catalog:

Since SQL Server is the main concern, as it shows 206 assets to be classified but classifies none, here is the scan run id for the SQL Server scan: a465f4c6-1bee-49a6-8b82-0f07479608d2

As an example, one of the tables (called CMS_Users) within the SQL Server database has a column called USERNAME which should have been classified under the "All Full Names" classification, but nothing is getting classified. Details for this table and column are as follows:

Fully qualified name: mssql://vw-pr-ctmsql-11.workcover.local:1433/MSSQLSERVER/ctrlm900/dbo/CMS_USERS guid=eac3c8e5-7817-4d1d-ade6-2cf6f6f60000 Hope this information will be helpful and you'll be able to guide me forward. Thanks
Roopansh Gupta 0 Reputation points

2024-01-17T01:20:32.8933333+00:00
Hey @PRADEEPCHEEKATLA-MSFT , I did raise the ticket. Here is the number: 2401100030001208.

You might be requiring some specific information to check things, so here are some that I think might help:

One of the scans (Scan-OPHDB) is “71ac5875-8f4f-476d-a7de-6bdb2de3608f” shows assets classified to be 982 and the relationships ingested to be 206, but veyr few are to be seen in the Data Catalog.Here is the Run ID for another scan which discovered 40,000 of the 74,000 assets, which is “983694c2-baf8-4f79-8628-fcba5093ac9f” and the name of the scan is “Scan-CARDB” This one classifies nothing, 0 assets.

Here is a screenshot for the “Data Estate Health”. It is identifying some classifications, but that is very limited information. Main concern is the SQL Server, which just classified nothing.

Following are the only classifications identified based on the Data Catalog:

Since SQL Server is the main concern, as it shows 206 assets to be classified but classifies none, here is the scan run id for the SQL Server scan: a465f4c6-1bee-49a6-8b82-0f07479608d2

As an example, one of the tables (called CMS_Users) within the SQL Server database has a column called USERNAME which should have been classified under the "All Full Names" classification, but nothing is getting classified. Details for this table and column are as follows:

Fully qualified name: mssql://vw-pr-ctmsql-11.workcover.local:1433/MSSQLSERVER/ctrlm900/dbo/CMS_USERS guid=eac3c8e5-7817-4d1d-ade6-2cf6f6f60000 Hope this information will be helpful and you'll be able to guide me forward. Thanks P.S - Somehow, it was not letting me post this as a comment, so am posting here

Share via

Data catalog not showing up classifications and metadata as discovered by Scanning of Oracle assets - Purview