DBService does not Always Print Long Running Sql Commands in the Sql Command History
(Doc ID 2272273.1)
Last updated on MARCH 07, 2019
Applies to:Oracle Utilities Network Management System - Version 22.214.171.124 to 126.96.36.199.0 [Release 1.12 to 2.3]
Oracle Network Management for Utilities - DMS - Version 188.8.131.52 to 184.108.40.206.0 [Release 1.12 to 2.3]
Information in this document applies to any platform.
**Disclaimer:** This KM article may include the following abbreviations:
NMS - Oracle Network Management System
The NMS system appears to be hanging.
A 'cmd snapshot' was taken.
The ISIS dump for a specific service shows that it is waiting for a response from a DBService.
The ISIS dump for the corresponding DBService shows that it is waiting for a query task to finish.
However, all entries in 'SQL Command History' show that they have completed.
The issue can be reproduced at will with the following steps:
1. Run these commands in a terminal
Returns "250" ( the "select count(1) from dual" queries will completely fill up DBService's command history -- which stores only the most recent 250 commands. )
The Sql Command History will be filled with
sql command: 'select count(1) from dual' returned: 1 after 1 ms
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document