If you face the above error,
You can safely ignore.
It was written in alertlog because of timed out sessions. If you dont want this in alertlog you may have to reset your idle time to unlimited which is not possible in huge environment. So it is better to ignore the above error message.
Thanks.
Experts comments welcome.
You can safely ignore.
It was written in alertlog because of timed out sessions. If you dont want this in alertlog you may have to reset your idle time to unlimited which is not possible in huge environment. So it is better to ignore the above error message.
Thanks.
Experts comments welcome.
Not necessarily a timed out session, it could also be a poorly disconnected session as with mine.
ReplyDelete