Database Administration (MOSC)

MOSC Banner

Database gets terminated by error ASMB is stuck and VKTM detected a forward time drift.

edited Aug 26, 2018 5:05AM in Database Administration (MOSC) 2 commentsAnswered

Hi All

We have the  production database running in 12.2.0.1, recently databases are getting terminated automatically. Upon checking we found the below errors in the alert log and trace file. Automatic memory parameter is not been set. Please let us know what needs to be done to fix the same from occurring again.

Warning: VKTM detected a forward time drift.

Please see the VKTM trace file for more details:

/xxxxxx/xxxxxx/oracle12/diag/rdbms/xxxx/xxxxx/trace/xxxxx_vktm_12442.trc

2018-08-11T19:24:27.926082-05:00

ERROR: terminating instance because ASMB is stuck for 265 seconds

2018-08-11T19:24:41.611723-05:00

GEN0 (ospid: 12454): terminating the instance due to error 15082

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