10.1.0.4 patchset 2 catcpu.sql slop 2005-06-29 - By rjamya
That's not the point, Oracle states in Metalink note 3663846.8 proclaiming
that it is fixed in 10.1.0.4 <http://10.1.0.4> and is isn't. This works in
9ir2 but broke sometime in 10g. Can you spell regression?
Raj
On 6/29/05, Mladen Gogala <mgogala@(protected)> wrote:
>
> rjamya wrote:
>
> > One thing we found on 10.1.0.4 <http://10.1.0.4> <http://10.1.0.4> is
> large pl/sql
> > blocks don't compile. They fail with pls-123 Program too large error.
> > I am currently working on creating a test case for Support, since the
> > bug was closed as fixed in 10.1.0.4 <http://10.1.0.4> <http://10.1.0.4>.
> Ha !!
> >
> > Raj
> >
> One way of fixing this would be to make a recommendation not to use
> large PL/SQL blocks.
> That wouldn't be the first time that the problem is solved on the
> marketing level.
>
> --
> Mladen Gogala
> Oracle DBA
> Ext. 121
>
>
>
--
-- ---- ---- ---- ---- ---- --
select standard_disclaimer from company_requirements where category =
'MANDATORY';
That's not the point, Oracle states in Metalink note 3663846.8
proclaiming that it is fixed in <a href="http://10.1.0.4">10.1.0.4</a> and is
isn't. This works in
9ir2 but broke sometime in 10g. Can you spell regression?<br>
<br>
Raj<br><br><div><span class="gmail_quote">On 6/29/05, <b class="gmail
_sendername">Mladen Gogala</b> <<a href="mailto:mgogala@(protected)"
>mgogala@(protected)</a>> wrote:</span><blockquote class="gmail
_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0
.8ex; padding-left: 1ex;">
rjamya wrote:<br><br>> One thing we found on <a href="http://10.1.0.4">10.1
.0.4</a> <<a href="http://10.1.0.4">http://10.1.0.4</a>> is large pl/sql
<br>> blocks don't compile. They fail with pls-123 Program too large error.
<br>> I am currently working on creating a test case for Support, since the
<br>> bug was closed as fixed in <a href="http://10.1.0.4">10.1.0.4</a> <
<a href="http://10.1.0.4">http://10.1.0.4</a>>. Ha !!<br>>
<br>> Raj<br>><br>One way of fixing this would be to make a
recommendation not to use<br>large PL/SQL blocks.<br>That wouldn't be the first
time that the problem is solved on the<br>marketing level.<br><br>--<br>Mladen
Gogala
<br>Oracle DBA<br>Ext. 121<br><br><br></blockquote></div><br><br><br>-- <br>---
-- ---- ---- ---- ---- ----<br>select standard_disclaimer from company
_requirements where category = 'MANDATORY';<br>
|
|
