Errors in emoms.trc

Question

Hello getting following erros in emoms.trc can anyone help me to find a reason why this heppens?
Oms 10.2.0.3 on 2003 server
Agnet 10.2.0.3 on 2003 server
2007-10-18 11:53:00,056 [XMLLoader0 80000000327.xml] WARN eml.XMLLoader LoadFiles.682 - Marking the file for retry : 80000000327.xml after receiving exceptionjava.sql.SQLException: ORA-14400: inserted partition key does not map to any partition
2007-10-18 11:53:05,587 [XMLLoader0 80000000327.xml] ERROR eml.XMLLoader markFileAsError.826 - Failed to load 80000000327.xml even after 2 attempts; moving to errors directory. Error:
java.sql.SQLException: ORA-14400: inserted partition key does not map to any partition
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:137)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:304)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:271)
     at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:625)
     at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:181)
     at oracle.jdbc.driver.T4CPreparedStatement.execute_for_rows(T4CPreparedStatement.java:629)
     at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1153)
     at oracle.jdbc.driver.OraclePreparedStatement.sendBatch(OraclePreparedStatement.java:3207)
     at oracle.jdbc.driver.PhysicalConnection.commit(PhysicalConnection.java:1245)
     at oracle.jdbc.OracleConnectionWrapper.commit(OracleConnectionWrapper.java:87)
     at oracle.jdbc.OracleConnectionWrapper.commit(OracleConnectionWrapper.java:87)
     at oracle.sysman.emdrep.dbjava.loader.XMLLoaderContext.handleSubDocument(XMLLoaderContext.java:2272)
     at oracle.sysman.emdrep.dbjava.loader.XMLDocumentSplitter.endElement(XMLDocumentSplitter.java:893)
     at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1257)
     at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:314)
     at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:281)
     at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:196)
     at oracle.sysman.emdrep.dbjava.loader.XMLDocumentSplitter.split(XMLDocumentSplitter.java:466)
     at oracle.sysman.emdrep.dbjava.loader.XMLLoaderContext.loadFromStream(XMLLoaderContext.java:1817)
     at oracle.sysman.emdrep.dbjava.loader.XMLLoader.LoadFile(XMLLoader.java:576)
     at oracle.sysman.emdrep.dbjava.loader.XMLLoader.LoadFiles(XMLLoader.java:667)
     at oracle.sysman.emdrep.dbjava.loader.XMLLoader.run(XMLLoader.java:1314)
     at java.lang.Thread.run(Thread.java:534)

Answer 1

This may occur if the Repository has not been reorganized and if there are many truncated
partitions in the Grid Management Repository. SolutionTo fix this issue, please execute the following steps:
1. Stop the all the Management Agents until the problem is solved.
$ emctl stop agent
This step is recommended as this will stop the uploading of new files to the directories
$ORACLE_HOME/sysman/recv and $ORACLE_HOME/sysman/recv/errors.
A growing backlog of xml files in the OMS $ORACLE_HOME/sysman/recv sub-directory means a longer time for the OMS to insert the outstanding xml files in the repository. And as long as the upload issue is not fixed, the xml files will continue being moved to the $ORACLE_HOME/sysman/recv/errors sub-directory. Hence even if collected, data moved to the errors sub-directory will never be inserted into the repository, thus making the data collection useless.
2. Stop all the Management Servers and let the Management Repository Database up and running
$ emctl stop oms
3. Connect to the database hosting the Central Management Repository with the SYSMAN account
4. Execute the following SQL statement
SQL > exec emd_maintenance.analyze_emd_schema('SYSMAN')
SQL> exec emd_maintenance.partition_maintenance
Warning: depending of the amount of work to be done, exec emd_maintenance.partition_maintenance can take a while,
up to more than one hour. DO NOT cancel this procedure.
This procedure stops and restartds SYSMAN dbms_jobs. If it is cancelled or does not complete successfully
for any reason, you can hit the bug:
Bug 5231347 Running Emd_Maintenance.Partition_Maintenance Deletes Sysman Jobs
In that case, rerun exec emd_maintenance.partition_maintenance should fix the issue.
If you cannot run exec emd_maintenance.partition_maintenance and want to fix the dbms_job issue, check
Note 370695.1 Running EMD_MAINTENANCE.PARTITION_MAINTENANCE removes SYSMAN dbms_jobs
5. Restart the Management Servers
6. Restart the Management Agents
7. Verify that the issue is fixed.
kind regards
Terry