Categories
OAS 2023: OAS Metadata tables in BIPLATFORM should have Dataset name along with object ID
Hi Team,
Current OAS configuration stores Dataset's object id as a plan name in DS_REQUEST table under BIPLATFORM schema, there should be another field or plan name should ideally show Dataset name.
Object ID is always different from the dataset's name while creating a copy of the dataset. This leads to difficulty in jobs monitoring.
Comments
-
@Kartik Mali-Oracle Your requirement is a quite nonsense, I guess. Tables in schema BIPLATFORM are not documented (not exposed for public usage) and are used internally by product to store all metadata (including definitions of DV objects). So if you are using it for your internal "reporting" , it is on your own risk and you cannot ask for changes in those tables (or complain that something is missing in those tables] just because you need some column for your internal reporting. Btw, you can join (in your SQL query) other table S_NQ_DSS_DATASETS (using DATASET_ID column) to get details about data set. And if you join other table S_NQ_DSS_DISPLAY_NAMES, you can get display name of data set (if it differs from "internal" name - which is part of object id - fully qualified name of DS). But again, as I wrote, this is at your own risk and responsbility - nobody will guarantee you, that structure of those tables will not change in a future release.
0 -
Hi @Michal Zima - Thanks for the explanation. Analytics on the BIPLATFORM is always for the internal tracking - agree with you. Purpose of sharing this idea to improve the usage of the dataset for the large enterprises.
Just a suggestion / idea to overall improve the jobs monitoring.0 -
HI @Kartik Mali-Oracle Area of "usage" reporting, lineage/dependency reporting etc.. is completely unresolved and neglected in product OAS (and OAC as well). I am pointing to this fact for pretty long time, so far without much success. For example having REST API in place, which will allow you to get DV object definitions, dependencies between objects etc… To be then used then by internal "governance" reporting - which is something highly needed (seems that there will be "first sign" in that sense for OAS - but not in OAS 2025). So for us currently is to use "dirty" method and query directly tables in BIPLATFORM schema (poor OAC users does not have even this option).
0 -
Hi @Michal Zima - Yes, i am specifically looking for a report to monitor the jobs of dataset reloads with proper dataset name and other details. Only struggling with the dataset name. Agree with you that the feature usage tracking need some more improvements. Hoping in the coming release. 🤞
0 -
@Kartik Mali-Oracle If your requirement is 'looking for a report to monitor the jobs of dataset reloads with proper dataset name and other details' - Perhaps log an Idea for this or vote for an existing, similar idea. We do have some existing requirements logged for this kind of functionality under review.
0 -
Sure @Adam Bloom-Oracle - I will have a look on the ideas and vote accordingly else create one. This is a more technical towards the application metadata. Thanks for the suggestion.
0
