Re: plsql nls-01890 version 8.1.6 error?

In article <b1855tkn23r0da8j7envr2gbp7psiuha6t_at_4ax.com>,   Dave Rawding <daverawding_at_mediaone.net> wrote:
> This strange problem began on the 8.1.6 version of Oracle when we
> compiled and ran plsql code that had been working fine on version
> 7.3.4.
>
> 64 bit HPUX is the platform.
>
> The 'code' is actually a series of procedures run one after the other.
> What happens is we run the sequence of procedures and get an nls-01890
> error at such and such a line of a procedure within the package (only
> happens in this one package).
>
> When we rerun from the start, it gets past the error, but then in
> another procedure in the same package, it gets another nls-01890
> error. This can be repeated five times and then it has run the entire
> series of procedures and the batch extract is successful.
>
> This particular plsql code is executed from inside a pro-iv program.
> Pro-iv is a language that can run plsql and is executed on the HP..
>
> We also get this nls-01890 error from plsql executed via OAS running
> on windows NT against the same database on HPUX. This time it is
> different packages and procedures than above. Again, if the same
> procedure is run a second time from the web, it is successful.
>
> At some point which we haven't identified, the situation will be
> 'reset' and the errors will begin again. It almost seems that as long
> as the same session is being used in Oracle, the programs can continue
> to progress, but at some point a new session fails from the beginning
> again.
>
> Wonder if anyone has had any experience with this problem. Just
> knowing if it is the plsql or an init.ora parameter would be helpful.
>
> thanks, Dave Rawding
>

One can only guess here: could it be that some "initializing" event in the batch for some reason has made the procedures/packages temporarily invalid, even though there is really nothing wrong with them?

--
Jining Han
Sallie Mae


Sent via Deja.com
http://www.deja.com/