Re: Missing public synonyms in PDB for METADATA LINK objects

I didn't get any feedback on this inquiry, but thought I would close the loop on it nonetheless.

This issue was 100% caused by setting the parameter container_data=CURRENT_DICTIONARY in the PDBs. This was done for a reason, but we painted it with too wide a brush and used alter system instead of alter session or an opt_param hint.

> On May 3, 2023 at 7:16 AM DOUG KUSHNER <dougk5_at_cox.net> wrote:
>
>
> We have quite a few PDBs that were created on 19.10 and subsequently upgraded to 19.16 months ago. They are performing well, however I recently noticed that over half of these PDBs are missing the 4000+ public synonyms to metadata linked objects in the CDB. This issue appears to be related to the CDB. If these public synonyms are missing, they are missing for all PDBs of a given CDB. If the public synonyms exist, they will exist in all PDBs of a given CDB.
>
> Q1. Can anyone explain the process that creates these public synonyms?
>
> Q2. Can these metadata link public synonyms be recreated manually?
>
> For context, one of the many missing public synonyms is for the view AUDSYS.UNIFIED_AUDIT_TRAIL. There is a row in DBA_OBJECTS in the PDB for this synonym, but it is missing from dba_synonyms (when queried from the PDB). It is also missing from the CDB when querying cdb_synonyms for the respective con_id.
>
> The following query run on the CDB returns only 1 row (for the CDB$ROOT) on the problematic CDBs. On CDBs where the public synonyms exist in PDBs It returns a row for CDB$ROOT and one row for each PDB.
>
> > >
> > select *
> > from cdb_synonyms
> > where owner='PUBLIC'
> > and synonym_name = 'UNIFIED_AUDIT_TRAIL';
> >
> > >
> BTW, I have opened an SR, but still in the process of defining the problem with them after 5 days.
>
> Regards,
>
> Doug
>

--
http://www.freelists.org/webpage/oracle-l