AHF - Autonomous Health Framework (TFA - ORACHK) (MOSC)

MOSC Banner

Falsely reported SCN limit for the database in Orachk 18.4

edited Mar 5, 2019 2:45AM in AHF - Autonomous Health Framework (TFA - ORACHK) (MOSC) 1 comment

I see the following falsely reported failure for most of the customers.

The database sequence control number (SCN) is near the maximum.

In some of the SRs Tier1 from the RDBMS team has provided the following justification -

"There are some sudden SCN increase spikes, but a very low value. This can make the orachk to interpret it as a SCN problem. The HEADROOM represents the maximum time of the database until it can function. When there are a lot of transactions, the SCN will increase at a high rate, so the HEADROOM will decrease. The HEADROOM can also increase in time, because the database heals the SCN. "

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center