Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> RE: PL/SQL Cursor

RE: PL/SQL Cursor

From: Jamadagni, Rajendra <Rajendra.Jamadagni_at_espn.com>
Date: Tue, 18 Dec 2001 08:35:13 -0800
Message-ID: <F001.003DEE3B.20011218070519@fatcity.com>


Isn't there a semicolon missing at the end of this line?

 and trh.tm_hist_reg_number = d.tm_hist_reg_number

Due to missing semicolon oracle things the statement (of cursor definition) is not yet complete and that's why you get the error.

???
Raj



Rajendra Jamadagni MIS, ESPN Inc. Rajendra dot Jamadagni at ESPN dot com
Any opinion expressed here is personal and doesn't reflect that of ESPN Inc.

QOTD: Any clod can have facts, but having an opinion is an art!

-----Original Message-----
Sent: Tuesday, December 18, 2001 9:45 AM To: Multiple recipients of list ORACLE-L

Raj:

Here is the code when I run it. Any idea what the problem is?

Thanks, Ken

DECLARE
  cursor ok_sos_hist_reg_nbr_cur is
    select tsh.tm_hist_reg_number,

               tdh.tm_hist_reg_number,
                   trh.tm_hist_reg_number,
                   d.tm_hist_reg_number
        from   tm_status_history tsh,
               trademark_data_history tdh,
                   trademark_registrant_history trh,
                   document d
    where  tsh.tm_hist_reg_number = tdh.tm_hist_reg_number
          and  tdh.tm_hist_reg_number = trh.tm_hist_reg_number
          and  trh.tm_hist_reg_number = d.tm_hist_reg_number
ORA-06550: line 14, column 0:

PLS-00103: Encountered the symbol "end-of-file" when expecting one of the following:

   . ( * @ % & - + ; / at for mod rem <an exponent (**)> and or    group having intersect minus order start union where connect    ||

BEGIN
  if not ok_sos_hist_reg_nbr_cur%ISOPEN
  then
    open ok_sos_hist_reg_nbr_cur

ORA-06550: line 5, column 0:
PLS-00103: Encountered the symbol "end-of-file" when expecting one of the
following:

   . ( % ; for

end if
end if
ORA-00900: invalid SQL statement

fetch ok_sos_hist_reg_nbr_cur into :tsh.tm_hist_reg_number fetch ok_sos_hist_reg_nbr_cur into :tsh.tm_hist_reg_number ORA-00900: invalid SQL statement

fetch ok_sos_hist_reg_nbr_cur into :tdh.tm_hist_reg_number fetch ok_sos_hist_reg_nbr_cur into :tdh.tm_hist_reg_number ORA-00900: invalid SQL statement

fetch ok_sos_hist_reg_nbr_cur into :trh.tm_hist_reg_number fetch ok_sos_hist_reg_nbr_cur into :trh.tm_hist_reg_number ORA-00900: invalid SQL statement

fetch ok_sos_hist_reg_nbr_cur into :d.tm_hist_reg_number fetch ok_sos_hist_reg_nbr_cur into :d.tm_hist_reg_number ORA-00900: invalid SQL statement

close ok_sos_hist_reg_nbr_cur
close ok_sos_hist_reg_nbr_cur
ORA-00900: invalid SQL statement

END
END
ORA-00900: invalid SQL statement

.
.

ORA-00900: invalid SQL statement

*********************************************************************2

This e-mail message is confidential, intended only for the named recipient(s) above and may contain information that is privileged, attorney work product or exempt from disclosure under applicable law. If you have received this message in error, or are not the named recipient(s), please immediately notify corporate MIS at (860) 766-2000 and delete this e-mail message from your computer, Thank you.

*********************************************************************2
Received on Tue Dec 18 2001 - 10:35:13 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US