The chart shows number of operations per detected client type, not the number of clients. With the database protocols, client is introducing itself at the beginning of the session, so if the session establishment sequence hasn't been seen by the AMD, client type won't be known for that session. Given that database sessions may last uninterrupted for days or even weeks if everything works fine, it's likely that large number of database operations will have no client type detected. Additionally, there is no obligation to introduce the client type when session is established, so it's also possible than one very active client pumps up the number. There's nothing worrying in here, it's how the database protocols work.
Hello @Kris Z.
Thank you for the answer and apologies for the type because I wanted to mention the operations instead of client.
What could be the reason in case of below statement and how to overcome?
If the session establishment sequence hasn't been seen by the AMD, client type won't be known for that session.
I'm afraid there may be no good workaround. If client-server session is already established when AMD boots up, there's no way to see client introducing himself again until this session is closed and client has to establish a new session. Database sever restart would help - all clients will have to re-establish their connections. But this advice is of course from the category of jokes:-)