ORA-01722 until shared pool is flushed 2006-03-31 - By JayMiller@(protected)
Thanks Dennis,
Several people have responded privately, including a few who experienced similar problems but everyone either upgraded or retired the database. One person had a resolution for the infrequent database link error that we experience (setting an event on the 9i side) but since I haven't seen that error in over 6 months I'm not going to bother implementing it.
I pinned the package two days ago and added it to our startup package pinning routine so I'll see if that helps. We don't usually get the error more than once every week or two so it will be a while before I can see if it helped and the database won't be restarted for another 6 weeks for it be pinned on startup (which I greatly prefer to pinning a package after the database has been open for a long time).
What I find most interesting from the article you linked to is "It generally happens in SQL only (during a query) not in plsql (plsql throws a different exception for this error). " since it's definitely happening from a pl/sql package.
Thanks,
Jay Miller
Sr. Oracle DBA
x68355
-- --Original Message-- -- From: Dennis Williams [mailto:oracledba.williams@(protected)] Sent: Friday, March 31, 2006 11:33 AM To: Miller, Jay Cc: oracle-l@(protected) Subject: Re: ORA-01722 (See ORA-01722.ora-code.com) until shared pool is flushed
Jay,
I don't see where anyone responded to your posting, so I'll give less than expert opinion.
So you're getting an "invalid number" error? Review this AskTom discussion. Apparently this ORA-01772 (See ORA-01772.ora-code.com) can occur in some strange ways.
http://asktom.oracle.com/pls/ask/f?p=4950:8:::::F4950_P8_DISPLAYID:45012 348053 Since you say that flushing the shared pool seems to alleviate the problem for awhile, this problem might somehow be related to the shared pool getting fragmented. You might consider pinning this stored procedure in memory.
Dennis Williams
-- ---- ---- ---- ---- ---- ---- ---- --- This message is confidential and sent by TD Waterhouse solely for use by the intended recipient. If you are not the intended recipient, you are hereby notified that any use, distribution or copying of this communication is strictly prohibited. This should not be deemed as an offer or solicitation, to buy or sell any product. Any 3rd party information contained herein was prepared by sources deemed reliable, but is not guaranteed. TD Waterhouse does not accept electronic instructions that would require an original signature. Information received by or sent from TD Waterhouse is stored, subject to review, and may be produced to regulatory authorities or others with a legal right to such.
<html>
<head> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 10 (filtered)">
<style> <!-- /* Font Definitions */ @(protected) {font-family:Tahoma; panose-1:2 11 6 4 3 5 4 4 2 4;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0in; margin-bottom:.0001pt; font-size:12.0pt; font-family:"Times New Roman";} a:link, span.MsoHyperlink {color:blue; text-decoration:underline;} a:visited, span.MsoHyperlinkFollowed {color:blue; text-decoration:underline;} p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig {margin:0in; margin-bottom:.0001pt; font-size:12.0pt; font-family:"Times New Roman";} pre {margin:0in; margin-bottom:.0001pt; font-size:10.0pt; font-family:"Courier New";} span.EmailStyle17 {font-family:Arial; color:navy;} @(protected) Section1 {size:8.5in 11.0in; margin:1.0in 1.25in 1.0in 1.25in;} div.Section1 {page:Section1;} --> </style>
</head>
<body lang=EN-US link=blue vlink=blue>
<div class=Section1>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size: 10.0pt;font-family:Arial;color:navy'>Thanks Dennis,</span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size: 10.0pt;font-family:Arial;color:navy'> </span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size: 10.0pt;font-family:Arial;color:navy'>Several people have responded privately, including a few who experienced similar problems but everyone either upgraded or retired the database. One person had a resolution for the infrequent database link error that we experience (setting an event on the 9i side) but since I haven’t seen that error in over 6 months I’m not going to bother implementing it.</span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size: 10.0pt;font-family:Arial;color:navy'> </span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size: 10.0pt;font-family:Arial;color:navy'>I pinned the package two days ago and added it to our startup package pinning routine so I’ll see if that helps. We don’t usually get the error more than once every week or two so it will be a while before I can see if it helped and the database won& #8217;t be restarted for another 6 weeks for it be pinned on startup (which I greatly prefer to pinning a package after the database has been open for a long time).< /span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size: 10.0pt;font-family:Arial;color:navy'> </span></font></p>
<pre><font size=2 color=navy face=Arial><span style='font-size:10.0pt; font-family:Arial;color:navy'>What I find most interesting from the article you linked to is “</span></font>It generally happens in SQL only </pre><pre> <font size=2 face="Courier New"><span style='font-size:10.0pt'>(during a query) not in plsql (plsql throws a different exception for this </span></font></pre><pre> <font size=2 face="Courier New"><span style='font-size:10.0pt'>error). </span>< /font><font color=navy face=Arial><span style='font-family:Arial;color:navy'>” since it’s definitely happening from a pl/sql package.</span></font></pre><pre> <font size=2 color=navy face=Arial><span style='font-size:10.0pt;font-family:Arial; color:navy'> </span></font></pre><pre><font size=2 color=navy face=Arial> <span style='font-size:10.0pt;font-family:Arial;color:navy'> </span></font></pre>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size: 10.0pt;font-family:Arial;color:navy'> </span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size: 10.0pt;font-family:Arial;color:navy'> </span></font></p>
<div>
<p class=MsoAutoSig><font size=2 color=navy face=Arial><span style='font-size: 10.0pt;font-family:Arial;color:navy'>Thanks,</span></font></p>
<p class=MsoAutoSig><font size=2 color=navy face=Arial><span style='font-size: 10.0pt;font-family:Arial;color:navy'>Jay Miller</span></font></p>
<p class=MsoAutoSig><font size=2 color=navy face=Arial><span style='font-size: 10.0pt;font-family:Arial;color:navy'>Sr. Oracle DBA</span></font></p>
<p class=MsoAutoSig><font size=2 color=navy face=Arial><span style='font-size: 10.0pt;font-family:Arial;color:navy'>x68355</span></font></p>
</div>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size: 10.0pt;font-family:Arial;color:navy'> </span></font></p>
<p class=MsoNormal style='margin-left:.5in'><font size=2 face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>-- --Original Message-- --<br> <b><span style='font-weight:bold'>From:</span></b> Dennis Williams [mailto:oracledba.williams@(protected)] <br> <b><span style='font-weight:bold'>Sent:</span></b> Friday, March 31, 2006 11:33 AM<br> <b><span style='font-weight:bold'>To:</span></b> Miller, Jay<br> <b><span style='font-weight:bold'>Cc:</span></b> oracle-l@(protected)<br> <b><span style='font-weight:bold'>Subject:</span></b> Re: ORA-01722 (See ORA-01722.ora-code.com) until shared pool is flushed</span></font></p>
<p class=MsoNormal style='margin-left:.5in'><font size=3 face="Times New Roman" ><span style='font-size:12.0pt'> </span></font></p>
<div>
<p class=MsoNormal style='margin-left:.5in'><font size=3 face="Times New Roman" ><span style='font-size:12.0pt'>Jay,</span></font></p>
</div>
<div>
<p class=MsoNormal style='margin-left:.5in'><font size=3 face="Times New Roman" ><span style='font-size:12.0pt'> </span></font></p>
</div>
<div>
<p class=MsoNormal style='margin-left:.5in'><font size=3 face="Times New Roman" ><span style='font-size:12.0pt'>I don't see where anyone responded to your posting, so I'll give less than expert opinion.</span></font></p>
</div>
<div>
<p class=MsoNormal style='margin-left:.5in'><font size=3 face="Times New Roman" ><span style='font-size:12.0pt'>So you're getting an "invalid number" error? Review this AskTom discussion. Apparently this ORA-01772 (See ORA-01772.ora-code.com) can occur in some strange ways. </span></font></p>
</div>
<div>
<p class=MsoNormal style='margin-left:.5in'><font size=3 face="Times New Roman" ><span style='font-size:12.0pt'><a href="http://asktom.oracle.com/pls/ask/f?p=4950:8:::::F4950_P8_DISPLAYID :45012348053">http://asktom.oracle.com/pls/ask/f?p=4950:8:::::F4950_P8_DISPLAYID :45012348053</a><br> Since you say that flushing the shared pool seems to alleviate the problem for awhile, this problem might somehow be related to the shared pool getting fragmented. You might consider pinning this stored procedure in memory. </span> </font></p>
</div>
<div>
<p class=MsoNormal style='margin-left:.5in'><font size=3 face="Times New Roman" ><span style='font-size:12.0pt'> </span></font></p>
</div>
<div>
<p class=MsoNormal style='margin-left:.5in'><font size=3 face="Times New Roman" ><span style='font-size:12.0pt'>Dennis Williams<br> </span></font></p>
</div>
</div>
</body>
</html>
<HTML><BODY><P><hr size=1></P><br> <P><STRONG><br> This message is confidential and sent by TD Waterhouse solely for<br> use by the intended recipient. If you are not the intended<br> recipient, you are hereby notified that any use, distribution or<br> copying of this communication is strictly prohibited. This should<br> not be deemed as an offer or solicitation, to buy or sell any<br> product. Any 3rd party information contained herein was prepared by<br> sources deemed reliable, but is not guaranteed. TD Waterhouse does<br> not accept electronic instructions that would require an original<br> signature. Information received by or sent from TD Waterhouse is<br> stored, subject to review, and may be produced to regulatory<br> authorities or others with a legal right to such.<br> </STRONG></P></BODY></HTML>
|
|