<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Invalid package error for a valid package!</title>
	<atom:link href="http://www.workflowfaq.com/invalid-package-error-for-a-valid-package/feed" rel="self" type="application/rss+xml" />
	<link>http://www.workflowfaq.com/invalid-package-error-for-a-valid-package</link>
	<description></description>
	<lastBuildDate>Wed, 14 Dec 2011 09:06:56 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Mark Parkins</title>
		<link>http://www.workflowfaq.com/invalid-package-error-for-a-valid-package/comment-page-1#comment-863</link>
		<dc:creator>Mark Parkins</dc:creator>
		<pubDate>Mon, 13 Dec 2010 21:25:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.workflowfaq.com/?p=22#comment-863</guid>
		<description>I can&#039;t vouch for this being a perfect solution but it has helped me during development.  Try the following query to see which sessions are &#039;accessing&#039; your PLSQL package, then the following statement to kill them.  

SELECT * FROM v$session s WHERE sid IN (SELECT sid FROM gv$access WHERE object LIKE &#039;YOUR_PKG_NAME_HERE&#039;) ORDER BY sid;

Then you can kill those sessions (at your own risk) using:

ALTER SYSTEM KILL SESSION &#039;&amp;P_SID_COMMA_SERIAL&#039; IMMEDIATE;

It&#039;s rough, I know!  Bouncing the &#039;Agent Listener Service&#039; from the &#039;Workflow Manager&#039; area of &#039;Oracle Applications Manger (OAM)&#039; is still needed sometimes too but not always!

Mark</description>
		<content:encoded><![CDATA[<p>I can&#8217;t vouch for this being a perfect solution but it has helped me during development.  Try the following query to see which sessions are &#8216;accessing&#8217; your PLSQL package, then the following statement to kill them.  </p>
<p>SELECT * FROM v$session s WHERE sid IN (SELECT sid FROM gv$access WHERE object LIKE &#8216;YOUR_PKG_NAME_HERE&#8217;) ORDER BY sid;</p>
<p>Then you can kill those sessions (at your own risk) using:</p>
<p>ALTER SYSTEM KILL SESSION &#8216;&amp;P_SID_COMMA_SERIAL&#8217; IMMEDIATE;</p>
<p>It&#8217;s rough, I know!  Bouncing the &#8216;Agent Listener Service&#8217; from the &#8216;Workflow Manager&#8217; area of &#8216;Oracle Applications Manger (OAM)&#8217; is still needed sometimes too but not always!</p>
<p>Mark</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Priyanka</title>
		<link>http://www.workflowfaq.com/invalid-package-error-for-a-valid-package/comment-page-1#comment-52</link>
		<dc:creator>Priyanka</dc:creator>
		<pubDate>Wed, 14 Oct 2009 08:59:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.workflowfaq.com/?p=22#comment-52</guid>
		<description>Hi, Thanks for your post... I have faced this problem while developing a custom workflow for a client and since I was new to Workflow then, I dint know the cause of it....It took me quite some time to  realise the cause behind it ....</description>
		<content:encoded><![CDATA[<p>Hi, Thanks for your post&#8230; I have faced this problem while developing a custom workflow for a client and since I was new to Workflow then, I dint know the cause of it&#8230;.It took me quite some time to  realise the cause behind it &#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Graham Hotchkiss</title>
		<link>http://www.workflowfaq.com/invalid-package-error-for-a-valid-package/comment-page-1#comment-37</link>
		<dc:creator>Graham Hotchkiss</dc:creator>
		<pubDate>Tue, 19 May 2009 08:17:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.workflowfaq.com/?p=22#comment-37</guid>
		<description>I&#039;ve noticed some behaviour that may add to this topic.

Package header compilation does cause the Invalid Package error (reproducible).

Package body compilation sometimes causes the same error, but clearing all caches and logging out of eBusiness framework clears the error, even allowing successful retry of the function that is in error in Workflow Admin.

All errors disappear magically overnight! This is definitely reproducible in our system and allows workflows that have triggered the error to proceed in Workflow Admin. This might be something specific to our implementation (ie backup / bounce routines) but I suspect that one of the overnight Oracle maintenance requests is doing it. The test system I&#039;m using is on application version 10.5.10.2, DB version 10.2.0.2

If this works for others then I would strongly recommend that users roll-out package changes after close of business.

I hope this helps,

Graham Hotchkiss</description>
		<content:encoded><![CDATA[<p>I&#8217;ve noticed some behaviour that may add to this topic.</p>
<p>Package header compilation does cause the Invalid Package error (reproducible).</p>
<p>Package body compilation sometimes causes the same error, but clearing all caches and logging out of eBusiness framework clears the error, even allowing successful retry of the function that is in error in Workflow Admin.</p>
<p>All errors disappear magically overnight! This is definitely reproducible in our system and allows workflows that have triggered the error to proceed in Workflow Admin. This might be something specific to our implementation (ie backup / bounce routines) but I suspect that one of the overnight Oracle maintenance requests is doing it. The test system I&#8217;m using is on application version 10.5.10.2, DB version 10.2.0.2</p>
<p>If this works for others then I would strongly recommend that users roll-out package changes after close of business.</p>
<p>I hope this helps,</p>
<p>Graham Hotchkiss</p>
]]></content:encoded>
	</item>
</channel>
</rss>

