Database Extract (DbXtract) failing with error 'Unable to find node in database' and SBL-SMI-00077
(Doc ID 1051234.1)
Last updated on NOVEMBER 14, 2019
Applies to:
Siebel Remote - Version 8.0 [20405] and laterInformation in this document applies to any platform.
Symptoms
Database Extract (DbXtract) tasks fail with errors. Reviewing detailed DbXtract*.log file following errors/messages can be noticed:
GenericLog GenericError 1 000000084b553068:0 2010-01-20 10:00:34 Unable to find node in database
...
GenericLog GenericError 1 000000084b553068:0 2010-01-20 10:00:35 Message: Internal error occurred in a procedure., Additional Message: Updated 0 rows
Trace TracingInfo 3 000000084b553068:0 2010-01-20 10:00:35 UTLNodeSetRouteActive
Trace TracingInfo 3 000000084b553068:0 2010-01-20 10:00:35 Error while processing client "SADMIN". Results may be incomplete.
...
Trace TracingInfo 3 000000084b553068:0 2010-01-20 10:00:35 Unable to find node in database
Trace TracingInfo 3 000000084b553068:0 2010-01-20 10:00:37 ERROR: 1 client(s) failed with errors, 0 client(s) successful
GenericLog GenericError 1 000000084b553068:0 2010-01-20 10:00:37 (smisched.cpp (894) err=1376333 sys=0) SBL-SMI-00077: Component error, see the trace file for more information
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |