Accessing, using IADB
Accessing, using IADB
I am new at a project that wants to access and use the results of any IA analysis. For instance, after a referential integrity analysis, we may want to link invalid FKs to another table. Has anyone out there done something like this and can give me guidance?
Thanks in advance.
Thanks in advance.
Todd Ramirez
Sr Consultant, Data Quality
San Antonio TX
Sr Consultant, Data Quality
San Antonio TX
-
- Participant
- Posts: 3593
- Joined: Thu Jan 23, 2003 5:25 pm
- Location: Australia, Melbourne
- Contact:
Usually you detect a referential integrity problem in IA and then do something about it in DataStage. So a DataStage job processing the data would dump the bad rows into an exception file or table. I'm not sure whether you can crack IADB to find the exception keys.
Certus Solutions
Blog: Tooling Around in the InfoSphere
Twitter: @vmcburney
LinkedIn:Vincent McBurney LinkedIn
Blog: Tooling Around in the InfoSphere
Twitter: @vmcburney
LinkedIn:Vincent McBurney LinkedIn
What about an external app such as Oracle BI...can it have read permission? I am trying to avoid having to export analysis results to a file and loading the file into Oracle.datisaq wrote:IADB and XMETA are the repositories, and the developer won't be having any read permissions to it to access it...
Yes they are cryptic which makes it hard sometimes to figure out what result table belongs to which business rule profile.
Oh just a heads up on a feature/bug/issue that you might hit if you are profiling an Oracle database. When you run a report on the output of a business rule profiling job that includes a field defined as a number. The value in the report will come out as a exponential number. It has to do with how the 3rd party ODBC drivers import the data.
You will need to write a script which will change the field type in the business rule profiling result tables in the xmeta database to get around this problem. I can't remember if it was Decimal to number.
Tim
Oh just a heads up on a feature/bug/issue that you might hit if you are profiling an Oracle database. When you run a report on the output of a business rule profiling job that includes a field defined as a number. The value in the report will come out as a exponential number. It has to do with how the 3rd party ODBC drivers import the data.
You will need to write a script which will change the field type in the business rule profiling result tables in the xmeta database to get around this problem. I can't remember if it was Decimal to number.
Tim