Database Administration (MOSC)

MOSC Banner

snipped sessions continue to lock objects

edited Dec 1, 2016 4:00AM in Database Administration (MOSC) 3 commentsAnswered

Hi.

If user lock object (table for instance) using LOCK TABLE command. Then session changes status to SNIPPED because profile IDLE_TIME was exceeded. Table remains locked while session will be disappeared or killed.

Is it normal behavior? SNIPPED session has not change to be ACTIVE again.

If this behavior is normal. Does  exist reliable mechanism for fast killing such sessions?

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

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center