ORA-08103: Object No Longer Exists During Engine Run (Doc ID 1517747.1)

Last updated on MARCH 20, 2025

Applies to:

Goal

Customer is on 7301

They run three engine profiles and thus three seperate engine runs each weekend. One profile, for our Shipment engine run, consistently gets the following error.

13:30:55:055 13:30:55:055 ERROR 13:30:55:055 13:30:55:055 ERROR Database Error http://EngDatabase.xxx,1065
13:30:55:055 13:30:55:055 ERROR - Source: OraOLEDB
13:30:55:055 13:30:55:055 ERROR - Description: ORA-08103: object no longer exists
13:30:55:055 13:30:55:055 ERROR - Message: Unspecified error
13:30:55:055 13:30:55:055 ERROR - Error Number: 0x80004005 - Unspecified error

13:30:55:055 13:30:55:055 ERROR
13:30:55:055 13:30:55:055 ERROR Caught exception in SetFieldValue()! IRL='5,295,354' AND KEY='2,3894,29698' Type-COEFFICIENTS
13:30:55:086 13:30:55:086 WARNING Caught exception at DmM3IRLTreeNode::WriteCoeffAndOtherToCache()
13:30:55:086 13:30:55:086 ERROR Post Process Forecast caught an exception for 2,3894,29698
13:31:19:501 Machine localhost (ID: 11) receiving branchID 28
13:32:11:184 13:32:11:184 ERROR 13:32:11:184 13:32:11:184 ERROR Database Error http://EngDatabase.xxx,1065
13:32:11:184 13:32:11:184 ERROR - Source: OraOLEDB
13:32:11:184 13:32:11:184 ERROR - Description: ORA-08103: object no longer exists
13:32:11:184 13:32:11:184 ERROR - Message: Unspecified error
13:32:11:184 13:32:11:184 ERROR - Error Number: 0x80004005 - Unspecified error

13:32:11:184 13:32:11:184 ERROR


Customer confirms that it happens no matter when the engine is run and DOES NOT appear for the same combination each week. The good news is that the branch does seem to be recovered later in the engine run and it does appear to be forecasted correctly. However, the cost of the error is that it slows down the overall engine run time which we can't afford.
 

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.