<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: How to find where an error was raised in PL/SQL</title>
	<atom:link href="http://awads.net/wp/2006/07/25/how-to-find-where-an-error-was-raised-in-plsql/feed/" rel="self" type="application/rss+xml" />
	<link>http://awads.net/wp/2006/07/25/how-to-find-where-an-error-was-raised-in-plsql/</link>
	<description>News, views, tips and tricks on Oracle and other fun stuff</description>
	<pubDate>Wed, 20 Aug 2008 17:44:39 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Lama</title>
		<link>http://awads.net/wp/2006/07/25/how-to-find-where-an-error-was-raised-in-plsql/#comment-51906</link>
		<dc:creator>Lama</dc:creator>
		<pubDate>Sun, 13 Jan 2008 23:00:22 +0000</pubDate>
		<guid isPermaLink="false">http://awads.net/wp/2006/07/25/how-to-find-where-an-error-was-raised-in-plsql/#comment-51906</guid>
		<description>DECLARE
CURR_CONS  CONSULTANT%ROWTYPE
BEGIN
SELECT *
INTO CURR_CONS
FROM CONSULTANT
END;
/
--find the error please</description>
		<content:encoded><![CDATA[<p>DECLARE<br />
CURR_CONS  CONSULTANT%ROWTYPE<br />
BEGIN<br />
SELECT *<br />
INTO CURR_CONS<br />
FROM CONSULTANT<br />
END;<br />
/<br />
&#8211;find the error please</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Todd</title>
		<link>http://awads.net/wp/2006/07/25/how-to-find-where-an-error-was-raised-in-plsql/#comment-31826</link>
		<dc:creator>Andy Todd</dc:creator>
		<pubDate>Wed, 26 Jul 2006 04:47:10 +0000</pubDate>
		<guid isPermaLink="false">http://awads.net/wp/2006/07/25/how-to-find-where-an-error-was-raised-in-plsql/#comment-31826</guid>
		<description>&lt;p&gt;I've always found the line numbers provided by the PL/SQL parser to be a little misleading, whenever I've tried to look them up they seem to correspond to the pcode rather than the source code. The biggest problem I've found is that the pcode doesn't include blank lines and in long blocks the line numbers can get seriously out of whack.&lt;/p&gt;

&lt;p&gt;Mind you, I haven't looked into this seriously since Oracle 8i so it may have changed in more recent versions of the database.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I&#8217;ve always found the line numbers provided by the PL/SQL parser to be a little misleading, whenever I&#8217;ve tried to look them up they seem to correspond to the pcode rather than the source code. The biggest problem I&#8217;ve found is that the pcode doesn&#8217;t include blank lines and in long blocks the line numbers can get seriously out of whack.</p>
<p>Mind you, I haven&#8217;t looked into this seriously since Oracle 8i so it may have changed in more recent versions of the database.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eddie Awad</title>
		<link>http://awads.net/wp/2006/07/25/how-to-find-where-an-error-was-raised-in-plsql/#comment-31722</link>
		<dc:creator>Eddie Awad</dc:creator>
		<pubDate>Tue, 25 Jul 2006 19:49:53 +0000</pubDate>
		<guid isPermaLink="false">http://awads.net/wp/2006/07/25/how-to-find-where-an-error-was-raised-in-plsql/#comment-31722</guid>
		<description>&lt;p&gt;Amihay, that will be the subject of another blog post. Thanks.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Amihay, that will be the subject of another blog post. Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: amihay gonen</title>
		<link>http://awads.net/wp/2006/07/25/how-to-find-where-an-error-was-raised-in-plsql/#comment-31721</link>
		<dc:creator>amihay gonen</dc:creator>
		<pubDate>Tue, 25 Jul 2006 19:34:24 +0000</pubDate>
		<guid isPermaLink="false">http://awads.net/wp/2006/07/25/how-to-find-where-an-error-was-raised-in-plsql/#comment-31721</guid>
		<description>&lt;p&gt;Also mention the use of $$PLSQL_UNIT.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Also mention the use of $$PLSQL_UNIT.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
