Kimberly,
Taking your code, passing the parameters you did, and taking a look at the
SQL statement that is built, you end up with this in your WHERE CLAUSE:
AND a.shift IN A AND a.equipment_id IN 1408
If shift is a varchar2 column, which by passing the value of A I assume it
is, you need deli
Kimberly,
Look closely at the following statement - put more debug statements in this
area to show the exact sql statement you are trying to parse.
The SELECT portion looks fine to me - provided that all of the columns do
exist in the tables you reference.
My guess is that the problem is in the
The owner of the package/tables is the one actually doing the execute
so permissions is not the issue in this case.
-Original Message-
[mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 30, 2001 8:13 PM
To: '[EMAIL PROTECTED]'
Cc: '[EMAIL PROTECTED]'
Kimberly,
A bit of a long shot here
Kimberly,
A bit of a long shot here - Might it be permissions related?
eg - does the package owner have select on all the columns that are
referenced in the package?
I know this isn't an appropriate long term solution, but try granting the
package owner "select any table" directly and then see i
first thing I'd do is to look at line 200 through 210 from user_source to
locate the problem. Also I'd put the sql statement as constructed using
dbms_output 9you'll have to do multiple calls as your sql might be > 225
characters).
Running this SQL in sqlplus usually solves the invalid column pro
