Timestamp Mismatch Between Java Class and Its PUBLIC Synonym
Last updated on JULY 05, 2017
Applies to:Oracle Database - Enterprise Edition - Version 10.2.0.1 and later
Information in this document applies to any platform.
***Checked for relevance on 22-Jun-2017***
Concern may be raised in cases where a mismatch is discovered in the timestamp values between java classes and their associated PUBLIC synonyms.
For example such information may be displayed in output from using,
Note: 781959.1 Health Check Reports Problem: Dependency$ p_timestamp mismatch for VALID objects
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms