MGMT_DB_SIZE_GTT trunc 10g

  • From: Barbara Baker <barb.baker@xxxxxxxxx>
  • To: oracle-l@xxxxxxxxxxxxx
  • Date: Thu, 8 Sep 2005 14:48:07 -0600

Solaris 9; Oracle 10.1.0.3 <http://10.1.0.3>

Now I remember some of the reasons why I detest OEM so very much.
User DBSNMP is truncating table MGMT_DB_SIZE_GTT twice every 30 minutes. 
The only reference I can find to this is metalink note 292280.1, which seems 
to indicate that this is expected behavior. (Gee, I didn't expect it!) I 
wouldn't think that truncating a global temp table every 30 minutes would be 
so very good for performance.

Anyone else seen this? Is it causing production problems for you? (We're not 
yet live with this system)
Thanks!
Barb

(Here's a snipet from my audit log:)

USERID TIMEST Action name Obj Name SES_ACTIONS
------------ ------------------ -------------- -------------------- 
-----------
DBSNMP 08-Sep-2005 10:54 TRUNCATE TABLE MGMT_DB_FILE_GTT
DBSNMP 08-Sep-2005 10:54 TRUNCATE TABLE MGMT_DB_SIZE_GTT
DBSNMP 08-Sep-2005 11:24 TRUNCATE TABLE MGMT_DB_FILE_GTT
DBSNMP 08-Sep-2005 11:24 TRUNCATE TABLE MGMT_DB_SIZE_GTT
DBSNMP 08-Sep-2005 11:54 TRUNCATE TABLE MGMT_DB_FILE_GTT
DBSNMP 08-Sep-2005 11:54 TRUNCATE TABLE MGMT_DB_SIZE_GTT
DBSNMP 08-Sep-2005 12:24 TRUNCATE TABLE MGMT_DB_FILE_GTT
DBSNMP 08-Sep-2005 12:24 TRUNCATE TABLE MGMT_DB_SIZE_GTT
DBSNMP 08-Sep-2005 12:54 TRUNCATE TABLE MGMT_DB_FILE_GTT
DBSNMP 08-Sep-2005 12:54 TRUNCATE TABLE MGMT_DB_SIZE_GTT

Other related posts: