Siebel Administration >  Database Extract 7.x and 8.x Failures

Database Extract 7.x and 8.x Failures

APPLIES TO:
Siebel Remote
Information in this document applies to any platform.
Area(s):Remote/Replication/Anywhere
Release(s):V7 (Enterprise), V7 (Professional), V7 (MidMarket), V8 (Enterprise), V8 (Professional)
Database(s):All Supported Databases
App Server OS(s):All Supported Platforms
Latest release tested against:V8 (Enterprise)
Keywords:repository merge, !!ERROR, CommitCopyInstance, REQUIRED, FKey, Ancestor, Obj., REPOSITION, PARENT

 


PURPOSE
This document provides troubleshooting information to diagnose database extract failures.

TROUBLESHOOTING STEPS
Symptom or Error Message
The Database Extract Siebel Remote server task may fail under certain conditions, which will mean that the node or nodes being extracted will not be able to be initialized until the extraction is successful.

Symptoms of a database extract failure are usually error messages on the Status field of the Server tasks applet, and the Task State field report that the task has exited with an error.

Task State: Exited with error
Status: ERROR: 1 client(s) failed with errors, 0 client(s) successful
GenericLog GenericError 1 2003-02-05 13:59:57 (smisched.cpp 17(791) err=2100077 sys=0) SMI-00077: Component error, see the trace file for more information

To generate more detailed trace information:

In Siebel applications version 7.x and 8.x, please review Document 477125.1, regarding component tracing for the database extract component, and Document 477003.1, regarding SQL-based event logging within the Siebel Remote components.

In Siebel applications versions 5.x and 6.x, run the database extract task with the following parameters set:

Sql flag = 4
Trace flag = 4
Error flag set = 4

Cause

At a high level there are three main causes of database extract failures:

Incorrect parameters specified for the database extract task

Connectivity and RDBMS issues

System and other issues

Diagnostic Steps

The first step in diagnosing a database extract failure issue is to try to determine whether the failure was a one-time occurrence or a persistent failure. This is easy to achieve by simply trying to restart the database extract task with the required parameters specified. If the task starts and continues processing without further error, then it is likely that the cause may be poor network connectivity, database connectivity or another intermittent system issue at the time of failure. If the database extract task has been running for a long period of time it is advised to investigate and correct the cause of the error before restarting. The majority of database extract failures are persistent and require some action to be taken before the task will run to completion. Typically the first step is to increase the tracing as detailed above, then restart the database extract task and review the more detailed log for the commonly seen issues as detailed below.

Incorrect Parameters Specified for the Database Extract Task


If incorrect parameters are specified, the database extract task will generally fail quickly. These parameters must be corrected before the task will run to completion. Following is a list of the most critical parameters and the accompanying errors that can occur if these parameters are incorrect:

Client Name

DBXTRACT: Target "VIAEXH" is not a child of "HQ".

DBXTRACT: Target node "VIAEXH" has expired.(SBL-DBX-00067)

DBXTRACT: Error while processing target node "VIAEXH"

GenericLog GenericError 1 2003-03-10 23:25:35 Target client "XXXX" is not a valid client.

Database Template File Name

DBXTRACT: Unable to locate template database

Database Init Method

This error is actually found in the upgrade wizard log file (UpgWiz.log) during a database initialization and can be caused by incorrect parameters specified when extracting a regional node:

DELETE FROM S_APP_VER
[ERR40] [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 'S_APP_VER'. [TRC35] UpgWiz-ERR-0004: [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 'S_APP_VER'.

NOTE: The above error messages may also appear under other circumstances. If you receive these errors, review the Regional Node initialization parameters in conjunction with checking the Database Init Method

Move Siebel Remote Client

Error: "Siebel Remote client "TEST" is registered on the application server "EMEA". You must specify the Move command-line option to move this client to application server "EMEA".

NOTE: In Siebel Applications version 8 there is no need to Database Extract a user in order to move the user. Siebel Bookshelf version 8 > Siebel Remote and Replication Guide > Moving Mobile Web Clients Between Servers.

CD Directory

DBXTRACT: No write access to file "C:\abbdata\SBL_DBX\".

SBL-DBX-00010: No write privileges on a file

Connectivity and RDBMS issues


Review the database extract log file for RDBMS and network related errors. The errors below are examples of RDBMS errors that have been seen in Database Extract log files:

Oracle

ORA-01000: maximum open cursors exceeded

ORA-03113: end-of-file on communication channel

ORA-01562: failed to extend rollback segment number 5

ORA-01628: max # extents (121) reached for rollback segment R04

DB2

[IBM][CLI Driver][DB2/NT] SQL1109N The specified DLL "siebproc" could not be loaded.

[IBM][CLI Driver][DB2/NT] SQL1109N The specific DLL "siebdbx" could not be loaded

[IBM][CLI Driver][DB2/NT] SQL1109N The specific DLL "nextseq2" could not be loaded

[IBM][CLI Driver][DB2/6000] SQL0911N The current transaction has been rolled back because of a deadlock or timeout. Reason code "68". SQLSTATE=40001

MS SQL Server

[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified

[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionRead (recv()).

[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionWrite (send())

[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]General network error.

[Microsoft][ODBC SQL Server Driver]Communication link failure

System and Other Issues


SBL-DBX-00083: Unable to start due to incorrect system preference setting

Integrity constraint violation: Index '<index name>' for table 'S_PARTY' would not be unique

SBL-DBX-00038: No DB template found

Invalid object name %Object_Name%

SBL-DBX-00080: Routing Model for the node is not defined

NOTE: The error numbers in Siebel applications version 7.5.2 and earlier are the same without the SBL prefix, namely DBX-00083 and DBX-00038.

Solution

Incorrect Parameters Specified for the Database Extract Task


Client Name

The only mandatory parameter that needs to be provided is the client name. Please ensure that the node is well defined and is not end dated.

Database Template File Name

Prior to running the database extract task, make sure that a Generate New Database task has been run successfully. For more information about generating a new database template, refer to Siebel Bookshelf > Siebel Remote and Replication Manager Administration Guide > Implementing Siebel Remote Server > Generating a New Database Template.

Database Init Method

When extracting mobile clients, keep the value for this parameter set to its default value, Sql Anywhere, which is the only supported local database engine.

When extracting Regional nodes set the database init method to DDL. If a database extract for a regional node is accidentally run with Database Init Method set to Sql Anywhere then initialization of the regional node (SRVRINIT) will fail.

Move Siebel Remote Client

The default for this parameter is FALSE. If your Siebel Enterprise has multiple Siebel Servers dedicated for Remote purposes, and the node being extracted is to be extracted on and moved to another Siebel Remote Server, then it is necessary to change this value to TRUE.

CD Directory

If the database extract task is run using the CD directory parameter that points to a directory, make sure that the correct privileges have been granted to allow the Siebel Server service owner to write to the specified directory.

Connectivity and RDBMS Issues


RDBMS errors are not generated by the Siebel application, but they are reported in the log files to aid with troubleshooting. The examples given above have all been caused by either underlying network issues, incorrect database configuration, or tuning issues. It is recommended to involve your DBA as many RDBMS errors can be resolved by database tuning alone. This should be done in conjunction with the recommendations made in Siebel Bookshelf.

In Siebel Bookshelf version 7.7 and above Siebel Installation Guide for (Microsoft Windows or UNIX): Servers, Mobile Web Clients, Tools, refer to the following chapter:

Guidelines for Configuring the RDBMS (Windows)
Guidelines for Configuring the RDBMS (UNIX)

In Siebel Bookshelf version 7.5.3 and above > Siebel Server Installation Guide for (Microsoft Windows or UNIX), refer to the appropriate chapter for your RDBMS:

Microsoft Windows

Creating the DB2 Universal Database for Windows and UNIX
Creating the Microsoft SQL Server Database
Creating the Oracle Database

UNIX

Creating the DB2 Universal Database for Windows and UNIX
Creating the Oracle Database

In Siebel Bookshelf version 7.0.x and above > Siebel Server Installation Guide for (Microsoft Windows or UNIX) review the appropriate chapter for your RDBMS on Creating and Optimizing the database for Siebel eBusiness Applications.

If the RDBMS error points to an underlying network issue then you should also involve appropriate networking resources to investigate the cause further.

In the case of a connectivity issue here are some initial basic checks that should be performed:

Verify that the database server is accessible from the Siebel application server machine by executing the ping command from a command prompt on the application server:

> ping %hostname_of_database_server%

If you are running against an Oracle database you should also test connectivity through the tnsping utility:

> tnsping <Oracle database tns alias>

Verify that the database server is running.

Verify that the ODBC connection strings are configured correctly. Please refer to Document 475610.1 for details on how to test connectivity through ODBC data sources created by the Siebel application.

If the database server is available, the database is up, and the ODBC data source connects, the connectivity problem may be intermittent.

NOTE: Not all RDBMS errors can be solved by database tuning alone. .If the error generated indicates a data integrity issue, log a Service Request with Oracle Technical Support and provide an associated database extract trace with increased logging enabled. Do not attempt to modify data in Siebel tables via direct SQL as this is not supported unless instructed to do so by Oracle Technical Support.

DB2

[IBM][CLI Driver][DB2/NT] SQL1109N The specified DLL "%dllname%" could not be loaded.

If you see the above referenced error in the database extract log file then these DLLs need to be installed. They contain user defined functions and stored procedures. For more information, please review the following section in the appropriate bookshelf guide for your operating system:

In Siebel Bookshelf version 7.7 and above > Siebel Installation Guide for (Microsoft Windows or UNIX): Servers, Mobile Web Clients, Tools, refer to the following chapter:

Installing the Stored Procedures and User-Defined Functions on DB2 (Windows)
Installing the Stored Procedures and User-Defined Functions on DB2 (UNIX)

In addition, please review Document 476994.1.

System and Other Issues


SBL-DBX-00083: Unable to start due to incorrect system preference setting

This error is generated if the System Preference Docking: Transaction Logging is set to False when the Database Extract task is run. This system preference must be set to True when extracting mobile clients or regional nodes.

Integrity constraint violation: Index '<index name>' for table 'S_PARTY' would not be unique

This error may be encountered during database initialization in the upgrade wizard log file (UpgWiz.log), but in Siebel 7 and Siebel 8 it normally indicates that there has been a problem with the data extracted by Database Extract, especially if S_PARTY is specifically mentioned. Please review Document 476949.1 for more information on how to resolve this error. Please note that this is most commonly experienced when upgrading from Siebel 2000 to Siebel 7 or Siebel 8, but there are other possible causes for initializations failing with this error.

SBL-DBX-00038: No DB template found

For further information on how to resolve this error please refer to Document 476320.1.

Invalid object name %Object_Name%

The above error is seen very frequently in database extract logs when changes to the physical database schema have not been applied and activated in Siebel Tools. For further information please refer to Siebel Bookshelf version 7.7 > Configuring Siebel eBusiness Applications > Configuring Tables and Columns > Applying Database Extensions to the Local Database
SBL-DBX-00080: Routing Model for the node is not defined

If the above error is seen in your database extract log file, please refer to Document 476628.1 for further information.

NOTE: If you are still experiencing database extract failures after following the recommendations above and the other referenced documents, please raise a Service Request providing as much information as possible about the failure, and include the database extract log file with the service request.

List of DBX Errors
SBL-DBX-00001 End of file
SBL-DBX-00002 Unspecified error
SBL-DBX-00003 Command line syntax error
SBL-DBX-00004 Memory allocation failure
SBL-DBX-00005 General file access error.
SBL-DBX-00006 General file access error: %1
SBL-DBX-00007 No out dir specified
SBL-DBX-00008 File does not exist
SBL-DBX-00009 No read privileges on a file
SBL-DBX-00010 No write privileges on a file
SBL-DBX-00011 No target node name specified
SBL-DBX-00012 No connect string specified
SBL-DBX-00013 No login name specified
SBL-DBX-00014 No password specified
SBL-DBX-00015 Error in SQL file, table name entry
SBL-DBX-00016 ODBC call returned error
SBL-DBX-00018 No SQL statement found following TABLE entry
SBL-DBX-00019 Failed to create directory
SBL-DBX-00020 Failed to remove files from directory
SBL-DBX-00021 Failed to create file for target node
SBL-DBX-00022 Error while writing to file
SBL-DBX-00023 Specified directory path too long
SBL-DBX-00024 Failed to read from file
SBL-DBX-00025 Failed to zip up files for target node
SBL-DBX-00026 Failed to change directory
SBL-DBX-00027 Failed to change drive
SBL-DBX-00028 Unable to find node for remote user or mobile user in database.
SBL-DBX-00029 Failed to get suffix, prefix from DB
SBL-DBX-00030 Failed to insert new node's prefix owner
SBL-DBX-00031 The node prefix has been incremented beyond legal value
SBL-DBX-00033 Unable to insert records for node in S_DOCK_STATUS table
SBL-DBX-00034 Unable to create lock for node
SBL-DBX-00035 Node is currently being accessed by another processes
SBL-DBX-00036 There are client data log files still in the client's inbox directory
SBL-DBX-00037 Verifying the existence of an up to date compressed template DB failed
SBL-DBX-00038 No local database template found.
SBL-DBX-00039 Unable to compress DB tmpl
SBL-DBX-00040 Unable to start ssa id API
SBL-DBX-00041 Unable to start dict API
SBL-DBX-00042 Unable to find table in dictionary
SBL-DBX-00043 Statement not found in common api sql file
SBL-DBX-00044 Unable to replace tokens in sql statement.
SBL-DBX-00045 Unable to generate DDL file
SBL-DBX-00046 Error while writing to toc file
SBL-DBX-00047 Error opening KDI
SBL-DBX-00048 Error inserting/updating KDI logging
SBL-DBX-00049 Unable to get repository id
SBL-DBX-00050 Failed to delete new node's prefix (%1)
SBL-DBX-00051 Failed to retrieve max transaction id
SBL-DBX-00052 Exception caught.
SBL-DBX-00053 Parent Node id is invalid
SBL-DBX-00054 Unable to get node information from db
SBL-DBX-00055 Unable to set app server in db for a node
SBL-DBX-00056 Target node has no employees
SBL-DBX-00057 Target node has no positions
SBL-DBX-00058 Error reading dock status from memory
SBL-DBX-00059 Error writing dock status to memory
SBL-DBX-00060 Error reading dock status from database
SBL-DBX-00061 Error writing dock status to database
SBL-DBX-00062 Error initializing dock status api
SBL-DBX-00063 Error getting next file num from dock status api
SBL-DBX-00064 Unable to build ordered list of visibility rules
SBL-DBX-00065 Unable to get system preference
SBL-DBX-00066 Unable to build member table sql statement
SBL-DBX-00067 Target node has expired
SBL-DBX-00068 Unable to transfer node to this application server. Please specify the Transfer option.
SBL-DBX-00069 Unable to get app server information from db (%1)
SBL-DBX-00070 Unable to set app server information from db (%1)
SBL-DBX-00071 App server %1 has expired
SBL-DBX-00072 Target node %1 is not qualified. Skipping this node.
SBL-DBX-00073 No nodes to extract after expanding wildcards
SBL-DBX-00074 Target node has no responsibilities
SBL-DBX-00076 Task context is invalid - (%s).
SBL-DBX-00077 No Message For DBX_THREAD_DEADLOCK_ERROR.
SBL-DBX-00078 Part 3: Extracted %ld member tables rows.
SBL-DBX-00079 DBXTRACT: Extracted %ld enterprise tables rows.
SBL-DBX-00080 Routing Model for the node is not defined
SBL-DBX-00081 DBXTRACT currently serves another request. Please try again later.
SBL-DBX-00082 The dbxtract request is invalid at this time due to another active dbxtract request being served. Please resubmit your request after the current request completes.
SBL-DBX-00083 Unable to start due to incorrect system preference setting
SBL-DBX-00084 Target node does not belong to database users of this database.
SBL-DBX-00085 Invalid value for Client Database encryption key (%1), please supply the file containing name/key pairs when extracting multiple users and strong encryption of Local Db is required.
SBL-DBX-00086 Local DB encryption method is set, but the key was not passed in, DbXtract will generate the key to encrypt Local DB.
SBL-DBX-00087 Note: You have requested the creation of a strongly encrypted Local database for the client. You must specify an unencrypted database template (not an encrypted template such as sse_encr.dbf), or Local database initialization will fail.
SBL-DBX-00088 Unable to find local database template or node for mobile user in database.