Thanks to those who replied. Of course the answer was simple but
for some reason I thought the code was right in the whole quote
thing. I did need to have quotes get passed in on the third and
forth parameter.
I plan on rewriting the code anyway as I have not found a single
reason as to wh
Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Kimberly
> Smith
> Sent: Tuesday, October 30, 2001 6:25 PM
> To: Multiple recipients of list ORACLE-L
> Subject: Problem with DBMS_SQL - Long and probably annoying
>
>
> There is a Procedure that uses D
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
There is a Procedure that uses DBMS_SQL that is causing some problems.
Basically I am having problems debugging it. I got it
down to the parse statement but see nothing wrong. I have taken the SQL
statement out of this code and ran it manually and it works so I don't
understand the error. If s
