2/3/2020 Document 2215428.

1
Copyright (c) 2020, Oracle. All rights reserved. Oracle Confidential.

Oracle VM Manager Issues with Huge OVM_STATISTIC Table (Doc ID 2215428.1)

In this Document

Symptoms
Cause
Solution
References

APPLIES TO:

Oracle VM - Version 3.3.1 and later

Oracle Cloud Infrastructure - Version N/A and later
Private Cloud Appliance X5-2 Hardware - Version All Versions to All Versions [Release All Releases]
Linux x86-64

SYMPTOMS

VM Manager GUI is very slow on all operations, even failed login.

The AdminServer.log may shows some MySQL exception like

####<2016-11-07T08:16:39.005-0500> <Warning> <com.oracle.odof.util.PersistUtils> <ovmmgr.

<domain.name> <AdminServer> <[ACTIVE] ExecuteThread: '18' for queue: 'weblogic.kernel.Default
(self-tuning)'> <<anonymous>> <> <a5fed4f7-6dfb-4b3c-befd-ed62a6f7823c-0000055a> <1478524599005>
<BEA-000000> <Error executing query: select c from CertificateEntity c where c.fingerprint =
:fingerprint

javax.persistence.PersistenceException: Exception [EclipseLink-4002] (Eclipse Persistence Services

- 2.5.2.v20140319-9ad6abd): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: No
operations allowed after connection closed.
Error Code: 0
Call: SELECT ID, CERTIFICATE, FINGERPRINT, VERSION, USER FROM OVM_USER_CERTIFICATE WHERE
(FINGERPRINT = ?)
bind => [1 parameter bound]
Query: ReadAllQuery(referenceClass=CertificateEntity sql="SELECT ID, CERTIFICATE, FINGERPRINT,
VERSION, USER FROM OVM_USER_CERTIFICATE WHERE
(FINGERPRINT = ?)")
at org.eclipse.persistence.internal.jpa.QueryImpl.getDetailedException(QueryImpl.java:378)
at org.eclipse.persistence.internal.jpa.QueryImpl.executeReadQuery(QueryImpl.java:260)
at org.eclipse.persistence.internal.jpa.QueryImpl.getResultList(QueryImpl.java:469)

at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.provider.WlsSubjectHandle.run(WlsSubjectHandle.java:57)
at weblogic.servlet.internal.WebAppServletContext.doSecuredExecute(WebAppServletContext.java:2280)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2196)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2174)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1575)
at
weblogic.servlet.provider.ContainerSupportProviderImpl$WlsRequestExecutor.run(ContainerSupportProvid
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:311)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:263)
Caused By: Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.5.2.v20140319-9ad6abd):
org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: No
operations allowed after connection closed.
Error Code: 0
Call: SELECT ID, CERTIFICATE, FINGERPRINT, VERSION, USER FROM OVM_USER_CERTIFICATE WHERE
(FINGERPRINT = ?)

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=cjz2rbc4l_4&id=2215428.1 1/2
2/3/2020 Document 2215428.1
bind => [1 parameter bound]
Query: ReadAllQuery(referenceClass=CertificateEntity sql="SELECT ID, CERTIFICATE, FINGERPRINT,
VERSION, USER FROM OVM_USER_CERTIFICATE WHERE (FINGERPRINT = ?)")

CAUSE

Found file system in VM Manager server reached high usage, and OVM_STATISTIC.ibd of OVMM database is growning too
large

# du -hs /u01/app/oracle/mysql/data/ovs/OVM_STATISTIC*
16K /u01/app/oracle/mysql/data/ovs/OVM_STATISTIC.frm
62G /u01/app/oracle/mysql/data/ovs/OVM_STATISTIC.ibd <--- this file

Login MySQL, the table contains too many records.

# mysql ovs -u ovs -p -S /u01/app/oracle/mysql/data/mysqld.sock

mysql> select count(*) from OVM_STATISTIC;
+----------+
| count(*) |
+----------+
| 97147640 |
+----------+

Possibly something wrong happened in OVM Server side, like storage missing, storage path works unstable(patch up/down
event triggered frequently) will trigger huge entries been recorded in the statistic table.

SOLUTION

As a workaround, truncate the huge OVM_STATISTIC table.

# mysql ovs -u ovs -p -S /u01/app/oracle/mysql/data/mysqld.sock

mysql> truncate table OVM_STATISTIC;

By far there is no reported/known issue or side effect for truncating the table.

But if the table OVM_STATISTIC becomes huge size again quickly, or any other issue after truncated the table, please
contact Oracle support line for further analysis.

REFERENCES

Didn't find what you are looking for?

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=cjz2rbc4l_4&id=2215428.1 2/2