Re: oerr 6508

Originally posted by Sybrand Bakker
> On Sun, 08 Dec 2002 04:36:54 +0000, meekes_26
> wrote:
>
> > I have reproduced this case many times and
> >it always occurr when i compile something from one session and
> use that
> >compiled program on another session.
>
>
> This is *completely* normal. If you compile a dependent program unit
> (which is in already in memory) the program unit gets invalid. Your
> program will not be able to call it.
> Other than that the usual causes for 6508 are lacking privileges and
> lacking synonyms.
>
> No 'setting' necessary.
>
>
> Sybrand Bakker, Senior Oracle DBA
>
> To reply remove -verwijderdit from my e-mail address

Hi, thanks fo replying,

When you say it gets invalid, are you referring to the invalid status of the package? Because I have made sure that the packages are all valid and still this happens. I know the case of invalid packages, that it is normal for the package to fail at first try of executing it(after compilation), but on the second try, it should have validated itself. But this case is different in the sense that you would have to disconnect first then connect again for you to be able to properly execute the package.

With regards to the other usual causes of 6508, im using the same username/schema, with which that user is the owner of the package, but im using it on 2 windows of sqlplus, one i use to compile the packages, the other i use to execute the compiled package (both logged in as the same user).

And this does not occur on another environment that we have Oracle 8.1.7.0. I am sure of this because when ever we compile something, we never restart our tuxedo(were using tuxedo for middleware) and anything we execute after compiling would fail at first then properly execute on the second execution.

Any other suggestions on the probable cause?? Or may you could explain further?

Thanks, i really need the solution for this.

--
Posted via http://dbforums.com