I would contact support. Playing with your SYS schema can render your
database unsupported.
Regards
On 06/19/2017 05:26 PM, Chris Taylor wrote:
Well, I went ahead and did a "create or replace public synonym..." and one of them resolved, but the other is still showing a mismatch.
Annoying.
Chris
On Mon, Jun 19, 2017 at 4:23 PM, Givens, Steven <sgivens@xxxxxxxx <mailto:sgivens@xxxxxxxx>> wrote:
I’ve had luck just doing a describe or selecting from the public
synonyms to get them validated.
*From:*oracle-l-bounce@xxxxxxxxxxxxx
<mailto:oracle-l-bounce@xxxxxxxxxxxxx>
[mailto:oracle-l-bounce@xxxxxxxxxxxxx
<mailto:oracle-l-bounce@xxxxxxxxxxxxx>] *On Behalf Of *Chris Taylor
*Sent:* Monday, June 19, 2017 4:16 PM
*To:* ORACLE-L
*Subject:* [External] 12.1 ORA-04023 - Not Fun
12.1.0.2
<https://urldefense.proofpoint.com/v2/url?u=http-3A__12.1.0.2&d=DwQFaQ&c=LkAXfnqL6_MvrMPL5JzdE3Ild0DUTpmjbCJvMv5_TcQ&r=p64P693r52tzs7tJCmFvOg&m=F9S541MtQ8HyADmSNyHC9Bq2XAAme-EExkx0GB1pFBI&s=5iKEXBzbqbgVF3KbhH7EYCOBXUxgpjIKUEneFlb38Y0&e=>
on Linux:
select * from < table_name > ;
ORA-04023: Object select * from <owner>.<table_name> could not be
validated or authorized
Metalink Note: 1610514.1 (Regarding Views) says its a timestamp
issue in the data dictionary.
The only results returned from the query (provided by support) are
2 SYS public synonyms.
What is the "best" way to fix SYS public synonyms?? Can you
recompile public synonyms? I was thinking they had to be dropped
and re-created.
Suggestions?
Chris
