Siebel Remote : Database Extract (DbXtract) tasks Fail With Error 'Node is currently being accessed by another processes'
(Doc ID 480997.1)
Last updated on JULY 29, 2021
Applies to:Siebel Remote - Version 220.127.116.11 SIA  to 18.104.22.168 [IP2013] [Release V7 to V8]
Oracle Solaris on SPARC (64-bit)
Solaris Operating System (SPARC 64-bit)
Product Release: V7 (Enterprise)
Version: 22.214.171.124  Life Sci
Database: Oracle 126.96.36.199
Application Server OS: Sun Solaris 5.8
Database Server OS: Sun Solaris 5.8
This document was previously published as Siebel SR 38-1138164818.
** Reviewed currency on 18 Nov 2013 **
DB Extract task exists with "Target client "xxxxx" is currently in use by another server process" error message.
It is not possible to re-extract a user because the user is locked by an other process:
Following error message was seen in DBxtract log:
Target client "SADMIN" is currently in use by another server process. Try again later.
Trace Trace 3 2003-12-08 17:38:52 DBXTRACT: Skipped "USERNAME": no lock
In current versions (i.e. 8.1.1.x) the wording of those messages in DbXtract logs has slightly changed:
GenericLog GenericError 1 000501ee53ff005a:0 2015-03-30 11:45:37 Node is currently being accessed by another processes
Trace TracingInfo 3 000501ee53ff005a:0 2015-03-30 11:45:37 DBXTRACT: Skipped "USERNAME": no lock
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