Re: Stored PL/SQL and corruption

From: <stevec_at_zimmer.csufresno.edu>
Date: 1998/03/13
Message-ID: <6ec647$o1c$1@nnrp1.dejanews.com>#1/1

If your stored procedure uses the DBMS_SQL package, that is probably the reason. The package here sometimes seems to get corrupted for one or more sessions, and only after several days.

The following commands from a DBA level account clears it up when we have the problem:
  ALTER PACKAGE SYS.DBMS_SQL COMPILE BODY;   ALTER PACKAGE SYS.DBMS_SQL COMPILE; HTH
Steve Cosner
http://members.aol.com/stevec5088

Sure would be nice if you would use a real email address!

---

In article <6e31tl$c2h$2_at_vnetnews.value.net>,   twod_at_not.valid wrote:

> Odd one today, we have some stored PL/SQL that is used to insert data into
> a table.
>
> After having been run for a couple of days with no problems the PL/SQL
> started to fail with a 'value error' at run-time. The package status was
> valid according to dba_objects and the same source code on the test database
> did not fail in the same way for the same input data. The code was reviewed
> for any obvious (and subtle) value run-time errors that could arise and none
> were found.
>
> The PL/SQL source was reloaded into the production database with no changes
> and started to work - accepting the previously errored data with no problem.
>
> I seem to remember some posts from a while ago about this sort of thing, but
> always thought that the status was changed to 'invalid'.
>
> Version 7.3.2 RDBMS running under Solaris 2.5.1.
>
> Any ideas anyone ?
>
> IAP
> --
> I am using anti-spam measures, please replace 'not.valid' with 'value.net'
>

-----== Posted via Deja News, The Leader in Internet Discussion ==----- http://www.dejanews.com/ Now offering spam-free web-based newsreading Received on Fri Mar 13 1998 - 00:00:00 CST