Home > Oracle, PLSQL > ORA-01003: no statement parsed

ORA-01003: no statement parsed

Not Java-related but since I started doing a bit of PL/SQL lately and I ran into this problem, I will post this. This error, in my case, was caused by having an Oracle keyword defined as a column name. For example the following

OPEN v_customer_recs FOR
         SELECT sc.EVENT_ID,
                sc.OPEN_DATE,
                ND.DESCRIPTION AS COMMENT,  -- This will cause the error
                SC.BC_DATE
           FROM CUSTOMERS sc, NEW_DESCRIPTION ND

will result in a ORA-01003: no statement parsed. The problem is that the COMMENT keyword is used as a column name. If you change this then the error will go away.

Advertisements
Categories: Oracle, PLSQL
  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: