I have a mapping on OWB 126.96.36.199, i can successfully deploy and validate it.
But if i like to run it it fails with the following Error:
ORA-06550: line 1, column 1487: PLS-00302: component 'MAPPING_NAME' must be declared ORA-06550: line 1, column 1470: PL/SQL: Statement ignored
I've alredy found a post that says: grant execute owner_name."mapping name" to user_name;
In my case this doesn't solve the Problem.
We have the same problem on OWB 188.8.131.52 and have solved renaming a schema name, because it was the same than another object on database. If this is your case, you can change the schema name on database and the location on OWB.
We hope this help you.
To view possible duplicate objects (schema-object):
WHERE OBJECT_NAME = '<SCHEMA_NAME>';
Oracle® Warehouse Builder Release Notes
*11g Release 2 (11.2) Part Number E24470-05*
7.14 Existence of an Object in the Schema With the Same Name as the Target Schema in the Database
12776878: If an object exists in the schema with the same name as the target schema in the database, then an error is displayed.
Schema named A has an object called Q. Schema named Q exists and has an object called Z.
When you call SchemaQ.ObjectZ from Schema A, it looks within Schema A for Q.Z. Z is not found and displays the following error:
ORA-06550: ..: PLS-00302: component 'XYZ' must be declared Workaround: Rename one of the Q objects to R or some letter other than Q.
I have seen this article, the situation described in there does not exist on our system, but a similar:
We have Schema B and an table called B on this Schema, on Schema B i also have the mapping Z, that i try to call.
Im now calling SchemaB.ObjectZ from Schema A.
I will now try to rename Schema B an then run the mapping Z.
awesome! We were looking for this solution for a long time. We couldnt figure why it says it cant find the package.
We thought the locations were messed up, or the flow calls it in the wrong schema (started to track owf activities).
We had a SR open for over a month and the guys didnt even had the slightest clue what is happening :(
cheers! you made our day!
to check if you have this bug just use:
FROM dba_users y
FROM dba_objects a