I am running meta data collection for an ORACLE database and jobs aborts with the following error –
W-3026983] 2009-03-30 12:21:39.008 It was not found the dependency column spa_currency_mv."/BIC/ZPS_DATE" for the view DEV604.SPA_REPORT.SPA_CORE_VW
[E-3026987] 2009-03-30 12:21:39.633 Error in the repository persister
[C-3027107] 2009-03-30 12:21:39.727 Cache statistics were taken at 2009-03-30 12:21:39.711.
[C-3027108] 2009-03-30 12:21:39.727 Cache name=System count=0 avgGetTime=0.0 totalHits=0 totalMisses=0 inMemoryHits=0 onDiskHits=0 evictions=0
[C-3027109] 2009-03-30 12:21:39.727 End of cache statistics taken at 2009-03-30 12:21:39.711.
[E-3026103] 2009-03-30 12:21:39.727 Cannot set Relationship.post_processor_status value to null.
[C-0000000] 2009-03-30 12:21:39.742 com.bobj.mm.sdk.SDKException: Cannot set Relationship.post_processor_status value to null.
at com.bobj.mm.core.Column.getActualValue(Column.java:593)
at com.bobj.mm.core.Table.insertRow(Table.java:3589)
at com.bobj.mm.core.Table.insertRow(Table.java:2948)
at com.bobj.mm.core.Table.insertRow(Table.java:2921)
at com.bobj.mm.sdk.DBObject.insert(DBObject.java:1809)
at com.bobj.mm.sdk.DBObject.find(DBObject.java:1783)
at com.bobj.mm.sdk.DBObject.findByAlternateKeyCreate(DBObject.java:536)
at com.bobj.mm.sdk.relationship.Relationship.findByAlternateKeyCreate(Relationship.java:511)
at com.bobj.mm.integrator.rdbms.ViewMappingPersisterWorker.createColumnsViewRelationship(ViewMappingPersisterWorker.java:277)
at com.bobj.mm.integrator.rdbms.ViewMappingPersisterWorker.run(ViewMappingPersisterWorker.java:193)
[C-3026169] 2009-03-30 12:21:39.852 1 inserts and 0 deletes were rolled back from table MMT_Data_Package.
[C-3026169] 2009-03-30 12:21:39.867 1 inserts and 0 deletes were rolled back from table MMT_Deployed_Software_Module.
[C-3026169] 2009-03-30 12:21:39.867 191 inserts and 0 deletes were rolled back from table MMT_Data_Group.
[C-3026169] 2009-03-30 12:21:40.024 41 inserts and 0 deletes were rolled back from table MMT_Relationship_Attribute.
[C-3026169] 2009-03-30 12:21:40.024 125 inserts and 0 deletes were rolled back from table MMT_Relationship.
[C-3026169] 2009-03-30 12:21:40.133 1,782 inserts and 0 deletes were rolled back from table MMT_Data_Element.
[C-3026169] 2009-03-30 12:21:40.321 1,974 inserts and 0 deletes were rolled back from table MMT_Dictionary.
[C-3026248] 2009-03-30 12:21:40.508 Batch lock has been released.
[E-3026022] 2009-03-30 12:21:40.508 Utility failed with code 4.
A bunch of warnings and an error… basically collects nothing at the end
I have attached the entire log …
By the Way, where are all the error codes listed for Meta data manager (3.x)? I tried SAP notes and could not find anything…
My repository is on ORACLE 10g. Where are the error codes listed and I see that we can limit the tables using schema names but is there a way to exclude certain objects from lineage reporting (in this case views). Why should whole job fail when I have errors only with views. Is there a way to change to warnings?
the error message is returned by database, this is considered as fatal since the update is failing for repository table, such error can’t be ignored since this will leave the data in inconsistent state in the repo
If there is a problem with parsing or extracting info from VIEW or TABLE such error will be flagged as warning and that partiular table or view will not be collected
if you look at the log, the failue to get dpendency for column is flagged as warning
[W-3026983] 2009-03-30 12:21:39.008 It was not found the dependency column spa_currency_mv."/BIC/ZPS_DATE" for the view DEV604.SPA_REPORT.SPA_CORE_VW
but while updating the repo, the update failed with the error, hence the job terminated
no there is no option to ignore type of objects to collect or set of objects to collect and not to collect, you can only filter by schema name
today I got exactly the same error message, but with SQL server as the repository and SQL server as the database to be analyzed.
The error message obviousely does’n not come from the database but from the BOMM. So the question is: where is a list of error codes and correcting actions?
No, I get the error with the number “[W-3026983]”, and the derived table from the universe is not properly scanned (because the SQL in it is somewhat tricky but correct).
Universe Derived SQL Warning happens when the MM SQL Parser is not able to parse the derived table SQL.
the SQL statement is parsed based on ANSI SQL, in most cases if the SQL is based on joins and the column names are not fully qualified the MM SQL Parser is not able to identify to which table the column belongs
the parsing may fail in case of database specific functions and parser is not able to resolve that
you can try fixing the SQL statement
for example:
if you have SQL like
select C1, C2 from tabA, tabB
where aId = bId
change this to
select a.C1, b.C2 from tabA a, tabB b
where a.aId = b.bId
have you filed a support case for this ? if yes can you give me the support number ?
or can you send me the error message that you see in the log file along with the SQL its printing and also sned me the SQL for Derived table that is failing from the Universe Designer
I can check why MM SQL Parser is failing
you can send the info to following email
mdhyani at hotmail
I am running into a similar error. We are on oracle11 now and have multiple integrators for different environments. I ran the integrator for our TEST and DEV environments, which have data, and the run was successfull. Below is the error message for our PROD environment. I did not get a warning. We are on 12.1.0.9 for BOMM.
[I-3028003] 2012-01-18 15:52:50.791 Beginning to collect data
[E-3028024] 2012-01-18 15:52:51.119 Unable to retrieve database metadata: null
[E-3026987] 2012-01-18 15:56:55.640 Error in the repository persister
[E-3026968] 2012-01-18 15:56:55.687 Unable to retrieve table metadata: Property databaseId is null.
(BOB member since 2009-01-24)
(BOB member since 2002-10-21)