StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p><strong>Error</strong></p> <p>For what I know, whatever tool you use to debug, the pl/sql blocks(anonymous and named) should be <strong>valid</strong> for the <strong>PL/SQL compiler</strong>. The fact is that your block doesn't result valid for the PL/SQL compiler, and your <strong>error</strong> is there to tell you, and is coming out from the <strong>PL/SQL compiler</strong> and <strong>not</strong> from the <strong>Sql Developer</strong>!</p> <blockquote> <p>PLS-00428: an INTO clause is expected in this SELECT statement Cause: The INTO clause of a SELECT INTO statement was omitted. For example, the code might look like SELECT deptno, dname, loc FROM dept WHERE ... instead of SELECT deptno, dname, loc INTO dept_rec FROM dept WHERE ... In PL/SQL, only a subquery is written without an INTO clause. Action: Add the required INTO clause</p> </blockquote> <p>and</p> <blockquote> <p>ORA-06550: line string, column string: string Cause: Usually a PL/SQL compilation error. Action: None</p> </blockquote> <p><strong>Why error</strong></p> <p>When an Pl/sql error appear, you only have the choice to investigate in the <strong>code</strong> and in the <strong>manuals:</strong> <a href="http://download.oracle.com/docs/cd/E11882_01/appdev.112/e17126/nameresolution.htm#LNPLS99882" rel="nofollow">Resolution of names in static SQL statements</a></p> <hr> <p><strong>PS:</strong> The route is always the same:</p> <p><strong><a href="http://www.catb.org/~esr/faqs/smart-questions.html#before" rel="nofollow">How to ask</a></strong></p> <p><strong><a href="http://tahiti.oracle.com/" rel="nofollow">All the "oracles" are here:</a></strong> </p> <p><strong><a href="http://download.oracle.com/docs/cd/E11882_01/doc.112/e12152/toc.htm" rel="nofollow">Sql Developer</a></strong></p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload