Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Mailing Lists -> Oracle-L -> Grid Control (Rel 2) Question
Anyone ever have problems where an agent starts uploading data with a
bad COLLECTION_TIMESTAMP? We're getting ORA-14400 errors - "Inserted
Partition Key does not map to any partition".
The table involved is MGMT_METRICS_RAW which is partitioned by date. The XML files that are being uploaded by this agent contain a COLLECTION_TIMESTAMP of "2009-01-27". There is no partition in MGMT_METRICS_RAW that can handle this data. The agent on the affected box appears to be fine and shows the correct dates when doing a 'emctl status agent'. Does anyone know how the agent generates this 'COLLECTION_TIMESTAMP' when its monitoring a host and/or database.
Of course, it's one of our production servers so I can't just remove the monitored targets without a lot of pain of recreating the Grid Control jobs...ugh.
Thoughts?
Chris Taylor
Sr. Oracle DBA
Ingram Barge Company
Nashville, TN 37205
Office: 615-517-3355
Cell: 615-354-4799
Email: chris.taylor_at_ingrambarge.com
-- http://www.freelists.org/webpage/oracle-lReceived on Wed Nov 07 2007 - 08:21:29 CST
![]() |
![]() |