Re: Implicitly created TYPE object comparison between 11g & 12c+
Date: Sat, 1 Apr 2023 11:56:23 -0700 (MST)
Message-ID: <1791139550.191156.1680375383678_at_myemail.cox.net>
No luck with either recommendation. I ran all of the SYS queries in the trace file that preceded the type creation statements, but none of them returned the value 8642B728.
Guess this will remain a mystery.
Thanks,
> On March 31, 2023 at 9:03 AM Jonathan Lewis <jlewisoracle_at_gmail.com> wrote:
Doug
>
>
> For this example, what's the object_id of the package?
>
> The hex might be a multi-part number from which you could split out the package id. Convert the object_id to hex then keep multiplying by 2 until you overshoot the hex.
> Alternatively, how about enabling tracing while you execute the package and create the objects - you might see a clue about the source of the hex - e.g. a call to a sequence.
>
>
> Regards
> Jonathan Lewis
>
>
>
> On Fri, 31 Mar 2023 at 16:38, DOUG KUSHNER <dougk5_at_cox.net mailto:dougk5_at_cox.net > wrote:
>
> > >
> > Our developers have created packages that define a type. Upon package creation, 3 type objects are implicitly created in the package owner's schema, all with name 'SYS_PLSQL%'.
> >
> > In 11.2.0.4, the names are similar to the following, where '3557076' is the package's object_id.
> >
> > SYS_PLSQL_3557076_DUMMY_1
> > SYS_PLSQL_3557076_27_1
> > SYS_PLSQL_3557076_9_1
> >
> > In 12.1, the type name does not contain the parent object's id, but some unknown hex value.
> >
> > SYS_PLSQL_8642B728_9_1
> > SYS_PLSQL_8642B728_DUMMY_1
> > SYS_PLSQL_8642B728_27_1
> >
> > Does anyone know how to find the parent package's object_id in 12.1 and later versions?
> >
> >
> > Regards,
> > Doug
> >
> > >
--
http://www.freelists.org/webpage/oracle-l
Received on Sat Apr 01 2023 - 20:56:23 CEST