Can't execute mappings

Question

Good morning,
I am having trouble executing a mapping that has a source table located on a different schema in the same database. The target schema does has SELECT privileges for the source table (I can select from the table in SQL Plus) but I am getting a warnings when I generate and deploy the mapping and I am getting an error when I try to execute the mapping. I don't know if any of these things are related.
Generate warning:
VLD-2771: System privileges may not allow extraction from source
Deploy warnings:
Warning ORA-06550: line 14, column 19: PL/SQL: ORA-00942: table or view does not exist
Warning ORA-06550: line 12, column 65530: PL/SQL: SQL Statement ignored
Warning ORA-06550: line 24, column 19: PL/SQL: ORA-00942: table or view does not exist
Warning ORA-06550: line 22, column 65530: PL/SQL: SQL Statement ignored
Warning ORA-06550: line 95, column 25: PL/SQL: ORA-00942: table or view does not exist
Warning ORA-06550: line 88, column 65530: PL/SQL: SQL Statement ignored
Execution errors:
ORA-04068: existing state of packages has been discarded ORA-04063: package body "OWB_TEST.MAP_TEST" has errors ORA-06508: PL/SQL: could not find program unit being called ORA-06512: at line 1
The mapping appears with an "X" next to it after it is deployed in the Deployment Manager.
Here is some of the code but it didn't seem like the line numbers in the messages lined up with the line numbers of the generated code...
line 14-27:
~~~~~
CREATE OR REPLACE PACKAGE MAP_TEST AS
-- Auditing mode constants
AUDIT_NONE CONSTANT BINARY_INTEGER := 0;
AUDIT_STATISTICS CONSTANT BINARY_INTEGER := 1;
AUDIT_ERROR_DETAILS CONSTANT BINARY_INTEGER := 2;
AUDIT_COMPLETE CONSTANT BINARY_INTEGER := 3;
-- Operating mode constants
MODE_SET CONSTANT BINARY_INTEGER := 0;
MODE_ROW CONSTANT BINARY_INTEGER := 1;
MODE_ROW_TARGET CONSTANT BINARY_INTEGER := 2;
MODE_SET_FAILOVER_ROW CONSTANT BINARY_INTEGER := 3;
MODE_SET_FAILOVER_ROW_TARGET CONSTANT BINARY_INTEGER := 4;
~~~~
line 94-97:
~~~~~
-- Function Main -- Entry point in package MAP_TEST
FUNCTION Main(p_env IN WB_RT_MAPAUDIT.WB_RT_NAME_VALUES) RETURN NUMBER;
END MAP_TEST;
~~~~~
line 83-90:
~~~~~
-- DML Exceptions
checked_table_not_empty EXCEPTION;
PRAGMA EXCEPTION_INIT(checked_table_not_empty, -111);
invalid_dml EXCEPTION;
PRAGMA EXCEPTION_INIT(invalid_dml, -112);
-- Status variable for Batch cursors
"TEST_TRG_St" BOOLEAN;
~~~~~
When the source table is in the same schema as the target, everything executes successfully.
I had a similar problem in the past (6 warning messages when deploying mapping), but was able to fix it by making a settings for the location registered. But I've never seen this error message before when I try to execute a mapping.
Using version 9.2.
Thanks!

Answer 1

Brian,
You are correct - error and warning line numbers do not match the code. It happens because the lines are offset. However, it is simple to make sense of this by doing the following:
1. Click View Code, and Search the code for 'FUNCTION Main(' , with no quotes around. This is the main entry point into the package that represents the mapping.
2. The function ends with '/' a few lines down. This is your offset. For example, let's say it's line 101.
3. Add it to the line reported in the error. For example, if error says "Line 38", then go to line 139. That is where the offending statement would be.
Back to your issue. It might be helpful to get the actual fragments of the code raising the error (using the above), but there are only a few things that can cause such trivial error: permissions, wrong table name, or incorrectly registered location.
Nikolai