Table Of Contents

Exceptions and Errors

Log Levels

Status Codes

Client Exceptions

Server Exceptions

Debug Messages

DB Loader Exceptions

Exceptions and Errors

---

This appendix contains the WANDEST client and server exceptions and errors, debug messages, and DB Loader errors.

Log Levels

The various log levels and their definitions are listed in Table B-1.

Table B-1 Message Levels and Definitions

Severity	Numeric Value	Definition
LOG_EMERG	0	Panic condition.
LOG_ALERT	1	Condition that should be corrected immediately, for example a corrupted system database.
LOG_CRIT	2	Critical condition, for example hard device errors.
LOG_ERR	3	Error.
LOG_WARNING	4	Warning message.
LOG_NOTICE	5	Condition that is not an error condition but may require special handling.
LOG_INFO	6	Informational message.
LOG_DEBUG	7	Message containing debugging information.

Status Codes

The status codes and their corresponding titles are listed in Table B-2. A full explanation of each code also appears in the Server Exceptions.

Table B-2 Status Codes and Titles 

Status Code No.	Status Title
0	OK
998	A task was pending when the shutdown command was entered
999	All the queued tasks and aborting tasks return 999 when the shuti is entered
1000	UNCOMPRESS_ERROR
1001	LOAD_DB_ERROR
1002	WD_SRV_ERROR
1003	DIR_STATUS_ERROR
1004	FILE_MOVE_ERROR
1005	OPEN_DIR_ERRO
1006	CREATE_DIR_ERROR
1007	TB_DEL_ERROR
1008	CORBA_SYS_ERROR
1009	SEQ_TOO_BIG
1010	SEQORGROUP_NOT_AVAIL
1011	START_NEEDS_ISSUE
1012	CWM_VERSION_NOTMATCHED
1013	WANDEST_VERSION_NOTMATCHED
1014	INVALID_EVENT
1015	UNTAR_ERROR
1016	DIR_PERM_ERROR
1017	NO_DATA_FILE
1018	CONTROL_FILE_OPEN_ERROR
1019	WRONG_FILE_NAME
1020	INVALID_CONTROLFILE
1021	BIND_SERVER_FAIL
1022	REGISTER_SERVER_FAIL
1023	CORBA_COMM_FAILCorb
1024	Unknown exception

Client Exceptions

All WANDEST client exceptions are listed in Table B-3.

Table B-3 WANDEST Client Exceptions 

Heading	Content/Required Action
Message	CORBA_SYS_ERROR
Severity	L2
Format	CORBA System Error. Error number [%d].
Explanation	CORBA system has generated an exception.
Required Info	WANDEST log files.
Recommended Action	CORBA error. Refer to the Orbix documentation for more information. The included file is typically located in $ORBIXHOME/inc/corba/except.h
DDTS Component	CSC.wanbu.sv.
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	WANDESTSERVERERROR
Severity	L3
Format	WANDEST server error. Error number [%s].
Explanation	WANDEST server has generated an exception.
Required Info	WANDEST log files.
Recommended Action	WANDEST server has generated an exception. See Server Exceptions for the exception type.
DDTS Component	CSC.wanbu.sv.
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	UNCOMPRESS_ERROR
Severity	L3
Format	Uncompress error, errmsg =[%s].
Explanation	WANDEST client has failed to uncompress the data files sent by the server for either the full upload or incremental update.
Required Info	WANDEST log files.
Recommended Action	WANDEST client uses the uncompress program to uncompress the data files sent by the server. The uncompress might fail for many reasons. Uncompress the file manually by invoking uncompress on the file. If this action also fails, the problem is outside the WANDEST client and might be related to permissions or disk space. Contact the administrator for possible resolution. If the manual uncompress succeeds, please call Cisco Technical Support.
DDTS Component	CSC.wanbu.sv.
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	LOAD_DB_ERROR
Severity	L3
Format	Failed in loading, err msg =[%s].
Explanation	WANDEST client has failed to load the data files into the temporary database.
Required Info	WANDEST log files.
Recommended Action	The load process might fail because of system or Informix related problems. The query that the load executes is logged in the client log file. Execute this query manually, using the dbaccess program. If this action also fails, the problem is outside the WANDEST client. If using the dbaccess program is successful, call Cisco Technical Support.
DDTS Component	CSC.wanbu.sv.
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	DIR_STATUS_ERROR
Severity	L3
Format	Could not read the directory, error code [%d].
Explanation	WANDEST client has failed to check the directory status.
Required Info	WANDEST log files.
Recommended Action	WANDEST client has failed to check the status of the directory where the FTP data files reside for full upload or incremental update. Check the permission of the directory.
DDTS Component	CSC.wanbu.sv.
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	UNKNOWN_EXCEPTION
Severity	L1
Format	Program error. Unknown exception is caught in [%s].
Explanation	An unexpected exception was caught by the program.
Required Info	WANDEST log files.
Recommended Action	This error is due to programming. Copy the error message exactly as it appears on the console or in the system log. Call a Cisco Technical Support representative and provide error message.
DDTS Component	CSC.wanbu.sv.
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	CREATE_DIR_ERROR
Severity	L3
Format	Create Directory fail, directory name [%s].
Explanation	WANDEST client cannot create the directory.
Required Info	WANDEST log files.
Recommended Action	WANDEST client has failed to create the directory for the data files to be sent by the server for the full upload or incremental update request. Check the permission of the directory. Enter mkdir manually. If this command fails, check the reason for failure and correct it accordingly. If this command works, contact Cisco Technical Support.
DDTS Component	CSC.wanbu.sv.
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	OPEN_DIR_ERROR
Severity	L3
Format	Open directory error, directory name [%s].
Explanation	WANDEST client can not open the directory.
Required Info	WANDEST log files.
Recommended Action	WANDEST client has failed to open the directory for the data files to be sent by the server for the full upload or incremental update request. Check the permission of the directory.
DDTS Component	CSC.wanbu.sv.
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	FILE_MOVE_ERROR
Severity	L3
Format	Could not move file to other directory, error code [%d].
Explanation	WANDEST client cannot move the old files to the archive directory.
Required Info	WANDEST log files.
Recommended Action	WANDEST client cannot move the old files from the current directory to the archive directory. Check the permission of the archive directory and the disk space. Manually rename those files to the archive directory. If this action is successful, contact Cisco Technical Support.
DDTS Component	CSC.wanbu.sv.
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	NO_DATA_FILE
Severity	L3
Format	No data file exists to process.
Explanation	WANDEST client cannot find the data files from incremental update or full upload.
Required Info	WANDEST log files.
Recommended Action	WANDEST client cannot find the data files for the tables. Check that the data files exist for the table. If those data files exist, contact Cisco Technical Support.
DDTS Component	CSC.wanbu.sv.
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	TB_DEL_ERROR
Severity	L3
Format	Deleting database Table Failed. Table Name [%s].
Explanation	WANDEST client cannot delete the table from the database.
Required Info	WANDEST log files.
Recommended Action	WANDEST client cannot delete the table from the database. Use the dbaccess utility to manually delete the table. If this is successful, please contact Cisco Technical Support.
DDTS Component	CSC.wanbu.sv.
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	SEQORGROUP_NOT_AVAIL
Severity	L3
Format	Sequence number or group number not available, seq#=[%s].
Explanation	The sequence number or group number is missing from the FULL or INCR command.
Required Info	WANDEST log files.
Recommended Action	The sequence number or group number is missing from the FULL or INCR command, issued from either the OSS application or from the Admin Utility. Refer to the appropriate user manuals for the command syntax.
DDTS Component	CSC.wanbu.sv.
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	START_NEEDS_ISSUE
Severity	L3
Format	WANDEST Client error [%s].
Explanation	The start command must be issued.
Required Info	WANDEST log files.
Recommended Action	The start command must be issued before a FULL or INCR command. The start command must be the first command issued to the WANDEST client, or this command might be issued after WANDEST client generates an exception.
DDTS Component	CSC.wanbu.sv.
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	CWM_VERSION_NOTMATCHED
Severity	L3
Format	CWM version not matched.
Explanation	The CWM version between the WANDEST server and the client does not match.
Required Info	WANDEST log files.
Recommended Action	The CWM version number defined in the WANDEST client configuration file does not match the CWM version number on the server workstation. Upgrade the CWM version on the server side or change the version defined in the Client configuration file.
DDTS Component	CSC.wanbu.sv.
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	INVALID_EVENT
Severity	L3
Format	Invalid Event received, event= [%d].
Explanation	The WANDEST client is not in the right state to receive the command (event), or the event is not valid.
Required Info	WANDEST log files.
Recommended Action	WANDEST client keeps a state machine internally. Each state can only accept certain commands. For example, when a FULL command is issued without a previous start command, this exception is generated. Check the response code for the previous action and correct the problem.
DDTS Component	CSC.wanbu.sv.
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS.If a similar DDTS does not exist, log a new DDTS for this problem.
Message	WANDEST_VERSION_NOTMATCHED
Severity	L3
Format	WANDEST version not matched.
Explanation	The WANDEST version on the client does not match the WANDEST version on the server.
Required Info	WANDEST log files.
Recommended Action	WANDEST version on the client does not match the version on the server. Install a new version of WANDEST client or server to match the versions.
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	UNTAR_ERROR
Severity	L3
Format	Failed in attempting to untar [%s] Exit value = [%d].
Explanation	The WANDEST client failed to untar the data file from full upload or incremental update.
Required Info	WANDEST log files.
Recommended Action	The WANDEST client failed to untar the data file from full upload or incremental update. Untar the data file using tar xvf filename. If this action works, contact Cisco Technical Support.
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	WRONG_FILE_NAME
Severity	L2
Format	Data Files received for Incremental Update do not have valid name, fileName= [%s].
Explanation	WANDEST client cannot find the data files from incremental update or full upload.
Required Info	WANDEST log files.
Recommended Action	The data file that the WANDEST client requested for incremental upload has the wrong data file name. Check that the data files exist for the table with the name n_ <table name> or d_ <table name>. If those data files exist, contact Cisco Technical Support.
DDTS Component	CSC.wanbu.sv.
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	DIR_PERM_ERROR
Severity	L2
Format	Directory Permission Error: [%s].
Explanation	WANDEST server cannot FTP the data file to the specified directory on the client workstation.
Required Info	WANDEST log files.
Recommended Action	The output directory specified by the client to store the data files from the server contains the invalid permission for WANDEST to open or put files. Check the WANDEST process privilege and the file permission.
DDTS Component	CSC.wanbu.sv.
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	CONTROL_FILE_OPEN_ERROR
Severity	L2
Format	Could not open control file: [%s].
Explanation	WANDEST client could not open the control file.
Required Info	WANDEST log files.
Recommended Action	The control file specified in the configuration file could not be opened. Check that the file exists and has a valid permission. If the file is valid, contact Cisco Technical Support.
DDTS Component	CSC.wanbu.sv.
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	INVALID_CONTROLFILE
Severity	L2
Format	Control File contains no Group or Table, filename= [%s].
Explanation	The control file contains no group or table name.
Required Info	WANDEST log files.
Recommended Action	The control file specified in the configuration file contains no group or table name. Check the syntax for the control file. A default control file, wdclient.ctrl, is provided during installation. Refer to the syntax of that file for correction.
DDTS Component	CSC.wanbu.sv.
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	SEQ_TOO_BIG
Severity	L2
Format	The sequence number is greater than maximum allowed.
Explanation	The sequence number for full upload or incremental update is greater than maximum configured number.
Required Info	WANDEST log files.
Recommended Action	The sequence number passed in from the full upload or incremental update is greater than the maximum number configured in the configuration file. Raise the maximum number defined in the configuration file, WDCLIENT_MAXSEQDIR, or lower the sequence number passed in from the FULL or INCR command.
DDTS Component	CSC.wanbu.sv.
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	BIND_SERVER_FAIL
Severity	L1
Format	Cannot bind to server, servername [%s].
Explanation	The WANDEST client cannot bind to the specified server.
Required Info	WANDEST log files.
Recommended Action	The WANDEST client cannot bind to the specified server. Correct the server name or check whether the WANDEST server is running correctly on the server machine.
DDTS Component	CSC.wanbu.sv.
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	REGISTER_SERVER_FAIL
Severity	L1
Format	Cannot register to server, servername [%s].
Explanation	The WANDEST client cannot register to the specified server.
Required Info	WANDEST log files.
Recommended Action	The WANDEST client cannot register to the specified server. Correct the server name or check whether the WANDEST server is running correctly on the server machine.
DDTS Component	CSC.wanbu.sv.
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	CORBA_COMM_FAIL
Severity	L2
Format	CORBA communication failed, already retried times [%d].
Explanation	CORBA communication failed after the configured retry count.
Required Info	WANDEST log files.
Recommended Action	The WANDEST client cannot make a request to the server specified because CORBA communication failed. Check the CORBA daemon process on the server machine and that the WANDEST server is running properly.
DDTS Component	CSC.wanbu.sv.
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.

Server Exceptions

The WANDEST server exceptions are listed in Table B-4.

Table B-4 WANDEST Server Exceptions 

Heading	Content/Required Action
Message	UNKNOWN_TABLE
Severity	LOG_ERR
Format	Unknown or unsupported Table [%s] is found in the request.
Explanation	The requested table is not supported by the WANDEST server. A user or client programming error exists. Requests for getFullUpload() and getUpdates() support CWM tables except for dbrk_temp, all tables with <_data> suffix, and all Informix internal tables. Requests for waitForRowInsertion() support only the asi_port, ausm_port, frp and line tables. These tables are port-related.
Required Info	Table name.
Recommended Action	Ensure that the CWM database schema uses either the WanDest::Admin.getSchema() method or the Informix dbaccess or dbschema utilities. If using the dbaccess utility to determine Informix utility, exclude: •dbkr_temp •All tables with the <_data> suffix •All Informix system tables
DDTS Component	CSC.wanbu.sv.
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	UNKNOWN_COLUMN
Severity	LOG_ERR
Format	Unknown Column [%s] is found in the request.
Explanation	The column specified in the request is not a column of the specified table. A user or client programming error exists.
Required Info	Column name.
Recommended Action	Get the requested table schema using either the WanDest::Admin.getSchema() method or the Informix dbaccess or dbschema utilities.
DDTS Component	CSC.wanbu.sv.
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	UNKNOWN_KEYS
Severity	LOG_ERR
Format	Unknown Keys [%s] are found in the request.
Explanation	The primary keys for the requested table are not valid. A user or client programming error exists.
Required Info	Keys column names.
Recommended Action	Get the requested table schema using either the WanDest::Admin.getSchema() method or the Informix dbaccess or dbschema utilities.
DDTS Component	CSC.wanbu.sv.
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	UNSUPPORTED_PROCEDURE
Severity	LOG_ERR
Format	Unknown or unsupported stored procedure [%s] is found in the request.
Explanation	WANDEST does not support the requested stored procedure. WANDEST supports only the GetEndParam() stored procedure.
Required Info	—
Recommended Action	Correct the client program to use the supported procedure.
DDTS Component	CSC.wanbu.sv.
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	CWM_COLDSTARTING
Severity	LOG_ERR
Format	CWM is being cold started.
Explanation	CWM is still cold starting, and a WANDEST request during a CWM cold start is not allowed.
Required Info	—
Recommended Action	Wait until CWM has completed cold start, and repeat the request.
DDTS Component	CSC.wanbu.sv.
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	NO_SUCH_SERVER
Severity	LOG_ERR
Format	No server with [%s] name is found.
Explanation	The specified CORBA server marker name is not known. This problem is caused by a client program deregistering a server that has been deregistered.
Required Info	—
Recommended Action	Correct the client program.
DDTS Component	CSC.wanbu.sv.
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	FULLUPLOAD_REQUIRED
Severity	LOG_ERR
Format	Table [%s] requires a full upload.
Explanation	The request is not allowed before a full upload. An incremental update or revert sync time might be occurring before a full upload, or the time elapsed since the last incremental update has exceeded the maximum allowed by the server.
Required Info	—
Recommended Action	Do a full upload.
DDTS Component	CSC.wanbu.sv.
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	SYNCH_EXPIRED
Severity	LOG_ERR
Format	The table [%s] has not been synched for more than [%d] seconds. FullUpload Required.
Explanation	The table has not been synched for more than the SYNC_EXPIRATION_TIME server configuration parameter (set in the server configuration file) and must be fully uploaded again.
Required Info	—
Recommended Action	Do a full upload or adjust the SYNC_EXPIRATION_TIME parameter in the server configuration file (by default, it is wdserver.cf file). Note When increasing the parameter, the tracking tables in the WANDEST database grow larger before they can be cleaned up.
DDTS Component	CSC.wanbu.sv.
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	EMPTY_TABLE_LIST
Severity	LOG_ERR
Format	The request contains no tables.
Explanation	The client did not specify any tables in the request.
Required Info	—
Recommended Action	Correct the client program to include tables in the request.
DDTS Component	CSC.wanbu.sv.
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	EMPTY_KEY_VALUES
Severity	LOG_ERR
Format	The request contains no keys for the row.
Explanation	The call to waitForRowInsertion must provide the keys to the row.
Required Info	—
Recommended Action	Correct the client program to include keys.
DDTS Component	CSC.wanbu.sv.
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	EMPTY_PARAMETER_LIST
Severity	LOG_ERR
Format	The request did not contain any parameters for the stored procedure.
Explanation	The call to invokeStoredProc needs to provide parameters.
Required Info	—
Recommended Action	Correct the client program to include the parameters.
DDTS Component	CSC.wanbu.sv.
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	UNKNOWN_PARAMETER_TYPE
Severity	LOG_CRIT
Format	The request contains an unknown parameter type [%d].
Explanation	Server program does not process the data type specified in the IDL.
Required Info	—
Recommended Action	Server program must be corrected to handle the type.
DDTS Component	CSC.wanbu.sv.
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	INVALID_TYPE
Severity	LOG_ERR
Format	An invalid type [%s] for table [%s] column [%s] is received in the request. Type [%s] is expected.
Explanation	The specified column type is not valid.
Required Info	—
Recommended Action	Correct the client program to specify the proper column type.
DDTS Component	CSC.wanbu.sv.
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	INVALID_TYPE
Severity	LOG_ERR
Format	An invalid length [%d] for table [%s] column [%s] is received in the request. Length [%d] is expected.
Explanation	The specified column length is not the same as the length defined in the server.
Required Info	—
Recommended Action	Correct the client program to specify the proper column length.
DDTS Component	CSC.wanbu.sv
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	NO_MORE_THREADS
Severity	LOG_ERR
Format	The maximum number of threads allowed in [%s] is currently exceeded.
Explanation	The server sets a limit on the maximum total number of threads that can be active. The limit is currently exceeded, indicating that the server is busy.
Required Info	—
Recommended Action	The limit is placed to control the server load. This limit is set in the server configuration file by the MAX_THREADS parameter (default is 50). Depending on the host configuration, this number may be increased. However, if this exception continues to occur, too many clients might exist for that server, or the clients are make too many concurrent requests. To resolve these issues, either move some of the clients to another WANDEST server, or reduce the number of concurrent requests the clients make.
DDTS Component	CSC.wanbu.sv
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	DISKSPACE_LOW
Severity	LOG_ALERT
Format	The available space in [%s] directory falls below the limit [%d].
Explanation	The disk space in the server, where the server creates temporary files, has fallen below the low disk space threshold. This low disk space may cause future requests to fail.
Required Info	—
Recommended Action	Remove any unnecessary large files. The size of files the WANDEST server unloads depends on the size of the database. These files are reused in all requests for that client, so they should not accumulate. If the WANDEST log files go to the same file system, usage might be impacted. When no unnecessary files exist, WANDEST might have to be reinstalled on a larger disk.
DDTS Component	CSC.wanbu.sv.
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	UNLOAD_FAILED
Severity	LOG_ALERT
Format	The Full Upload dbaccess process failed to unload table [%s] with exit value [%d].
Explanation	The Informix dbaccess process, used to unload the full upload data, has failed.
Required Info	WANDEST log files.
Recommended Action	The unload process might fail due to a system Informix related problem. The query that the unload process executes is logged in the server log file. Execute this query manually using the dbaccess program. If a manual unload also fails, the problem is outside the WANDEST server. If the manual unload succeeds, copy the error message exactly as it appears on the console or in the system log. Call a Cisco Technical Support Representative, and provide the error information.
DDTS Component	CSC wanbu.wandest.
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	NEW_UNLOAD_FAILED
Severity	LOG_ALERT
Format	The incremental updates dbaccess process failed to unload new or updated records from table [%s] with exit value [%d].
Explanation	The Informix dbaccess process, used to unload the new or updated records for incremental updates, has failed.
Required Info	WANDEST log files.
Recommended Action	The unload process might fail because of a system or Informix related problem. The query that the unload process executes is logged in the server log file. Execute this query manually using the dbaccess program. If a manual unload also fails, the problem is outside the WANDEST server. If the manual unload succeeds, copy the error message exactly as it appears on the console or in the system log. Call a Cisco Technical Support Representative, and provide the error information.
DDTS Component	CSC.wanbu.sv.
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	DEL_UNLOAD_FAILED
Severity	LOG_ALERT
Format	The incremental updates dbaccess process failed to unload deleted records from table [%s] with exit value [%d].
Explanation	The Informix dbaccess process, used to unload the deleted records for incremental updates, has failed.
Required Info	WANDEST log files.
Recommended Action	The unload process might fail because of a system or Informix related problem. The query that the unload process executes is logged in the server log file. Execute this query manually using the dbaccess program. If a manual unload also fails, the problem is outside the WANDEST server. If the manual unload succeeds, copy the error message exactly as it appears on the console or in the system log. Call a Cisco Technical Support Representative, and provide the error information.
DDTS Component	CSC.wanbu.sv.
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	COMPRESS_FAILED
Severity	LOG_ALERT
Format	The compress process failed to compress table [%s] with exit value [%d].
Explanation	The compress program, used to compress the data file, has failed.
Required Info	WANDEST log files.
Recommended Action	WANDEST server uses the compress program to compress the unload file. The files the WANDEST server attempted to compress are stored in the WANDEST data directory specified by the OUT_DIR parameter in the WANDEST server configuration file. The compress process might fail for many reasons. Invoke compress on the file. If the manual compress also fails, the problem is outside the WANDEST server. If a manual compress succeeds, copy the error message exactly as it appears on the console or in the system log. Call a Cisco Technical Support Representative and provide the error information.
DDTS Component	CSC.wanbu.sv.
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	FTPLOGIN_FAILED
Severity	LOG_ALERT
Format	The wdftp process failed to login to host [%s] user [%s] password [%s].
Explanation	The wdftp process, used to send the data files to the client, has failed to log in to the client-specified host with the provided user name and password.
Required Info	—
Recommended Action	Log in to the client host from the server host using FTP. Correct the client program so that the program specifies the correct information. If a manual FTP succeeds, copy the error message exactly as it appears on the console or in the system log. Call a Cisco Technical Support Representative and provide the error information.
DDTS Component	CSC.wanbu.sv.
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	FTP_FAILED
Severity	LOG_ALERT
Format	The wdftp process failed to FTP table [%s] unload file with exit value [%d].
Explanation	The wdftp process, used to send the data files to the client, has failed to send the files to the client host.
Required Info	WANDEST log files.
Recommended Action	The WANDEST server uses the wdftp program (not the FTP program provided by the host). The wdftp process can fail to send the data because of a local problem in the WANDEST server host or a network problem or by a remote client host. FTP the file manually. Run wdftp, as follows: shell > wdftp <return> ftp > open <client host> <login> <password> <return> If the wdftp program exits at this point, a login error has occurred that should trigger the FTPLOGIN_FAILED exception. If the wdftp succeeds, continue sending the file, using the following command: ftp > put <local file name> <remote file name> <return> If a manual FTP fails, check the network or the remote host. If manual FTP succeeds, retry the full upload or incremental update. If the manual FTP consistently succeeds and the WANDEST request consistently fails, copy the error message exactly as it appears on the console or in the system log. Call a Cisco Technical Support Representative and provide the error information.
DDTS Component	CSC.wanbu.sv.
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	TAR_FAILED
Severity	LOG_ALERT
Format	The tar command [%s] failed with exit value [%d].
Explanation	The tar command is used to combine all the requested data files into a single file before sending it to the client. Entering tar is one option in the request; the second option is to have the server send individual unload files to the client.
Required Info	WANDEST log files.
Recommended Action	Copy the error message exactly as it appears on the console or in the system log. Call a Cisco Technical Support Representative and provide the error information.
DDTS Component	CSC.wanbu.sv.
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	SYSTEM_ERROR
Severity	LOG_ALERT
Format	UNIX system call error [%s].
Explanation	A UNIX system call or library call has returned an error.
Required Info	WANDEST log files.
Recommended Action	System call errors might be caused by various system problems, ranging from a directory permission problem to a disabled system. Call errors might also be caused by a WANDEST server process passing incorrect information or being in a corrupt state, for example a memory leak. In most cases, the error provides clues as to what failed. If the error is related to a file system or permissions, check the installation. If the problem cannot be corrected based on the error message, copy the error message exactly as it appears on the console or in the system log. Call a Cisco Technical Support Representative and provide the error information.
DDTS Component	CSC.wanbu.sv.
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	DATABASE_ERROR
Severity	LOG_ALERT
Format	Database error [%s].
Explanation	The Informix library has returned an error.
Required Info	WANDEST and Informix log files.
Recommended Action	This problem is an Informix error. Refer to the Informix documentation.
DDTS Component	CSC.wanbu.sv.
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	UNSUPPORTED_TYPE
Severity	LOG_CRIT
Format	Function [%s] encountered unsupported data type [%d].
Explanation	An unsupported Informix data type was found.
Required Info	Type number.
Recommended Action	Install a WANDEST software upgrade. Copy the error message exactly as it appears on the console or in the system log. Call a Cisco Technical Support Representative and provide the error information.
DDTS Component	CSC.wanbu.sv.
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	UNKNOWN_EXCEPTION
Severity	LOG_CRIT
Format	Program Error. Unknown Exception was caught in [%s].
Explanation	An unexpected exception was caught by the program.
Required Info	WANDEST log files.
Recommended Action	This problem is a programming error. Copy the error message exactly as it appears on the console or in the system log. Call a Cisco Technical Support Representative and provide the error information.
DDTS Component	CSC.wanbu.sv.
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	INVALID_FILE_DESCRIPTOR
Severity	LOG_CRIT
Format	Program or System Error. Function [%s] encounters bad file descriptor [%d].
Explanation	An invalid file descriptor was found while processing the Orbix connection.
Required Info	WANDEST log files.
Recommended Action	The error applies only to a file descriptor created by Orbix for the connection between the client and the server. This error indicates that Orbix has passed a file descriptor that is less than 0 or greater than 1024.
DDTS Component	CSC.wanbu.sv.
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	SUBSYSTEM_EXCEPTION
Severity	LOG_CRIT
Format	Program Error. Subsystem exception [%s] caught in [%s].
Explanation	A WANDEST subsystem (other than the database) has thrown the specified exception.
Required Info	WANDEST log files.
Recommended Action	The exception should indicate which subsystem has thrown the error. The string inside the [%s] should be in the standard error message format. Additionally, the explanation for the subsystem error should be described in the subsystem error description document. Copy the error message exactly as it appears on the console or in the system log. Call a Cisco Technical Support Representative and provide the error information.
DDTS Component	CSC.wanbu.sv.
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	INTERNAL_ERROR
Severity	LOG_CRIT
Format	Program or System Error. Function [%s] reports: [%s].
Explanation	An unexpected condition was found in the program. This may have been caused by a programming error or system problem.
Required Info	WANDEST log files.
Recommended Action	This problem indicates an unexpected error condition has been detected in the WANDEST server program. It can either be caused by a programming error or a corrupted process emanating from a bug in the program. Copy the error message exactly as it appears on the console or in the system log. Call a Cisco Technical Support representative and provide the error information.
DDTS Component	CSC.wanbu.sv.
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	CONNECTION_LOST
Severity	LOG_WARNING
Format	Connection from host [%s] application [%s] lost during request.
Explanation	This error is not thrown across the CORBA interface. The error is logged when the connection to the client is broken while the server processes client requests.
Required Info	WANDEST log files and client program logs.
Recommended Action	This problem is not a server exception. An error indicates that the server has detected a disconnection from the client during request processing. This error might be caused by client termination or a communication error. Check the client program.
DDTS Component	CSC.wanbu.sv.
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	TABLE_LOCKED
Severity	LOG_ERR
Format	A request is pending on table [%s].
Explanation	Only one request per client can be pending on a table.
Required Info	—
Recommended Action	Retry the request after the current request completes.
DDTS Component	CSC.wanbu.sv.
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.

Debug Messages

All WANDEST debug messages are listed in Table B-5.

Table B-5 WANDEST Debug Messages 

Heading	Content/Required Action
Message	IN_FUNC
Severity	LOG_DEBUG
Format	In [%s].
Explanation	Executing the function.
Required Info	—
Recommended Action	—
DDTS Component	—
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	INIT_STOREDPROC
Severity	LOG_INFO
Format	Initializing stored procedure using query [%s].
Explanation	Initializing stored procedure used to create and delete triggers.
Required Info	—
Recommended Action	—
DDTS Component	—
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	REQUESTED_TABLE
Severity	LOG_INFO
Format	Requested table [%s].
Explanation	Processing the requested table.
Required Info	—
Recommended Action	—
DDTS Component	—
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	CHECKING_CWM
Severity	LOG_INFO
Format	Checking CWM.
Explanation	Checking to see whether CWM is being cold started and the size of the CWM disk space.
Required Info	—
Recommended Action	—
DDTS Component	—
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	WAITING_FORCWM
Severity	LOG_INFO
Format	Waiting for CWM to finish cold start...
Explanation	CWM is being cold started. WANDEST cannot provide any services while a cold start is in progress.
Required Info	—
Recommended Action	—
DDTS Component	—
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	COLDSTART_COMPLETE
Severity	LOG_INFO
Format	CWM completed cold start. Reading all db indexes...
Explanation	CWM just completed a cold start. WANDEST re-reads all database indexes to capture the indexes created during a cold start.
Required Info	—
Recommended Action	—
DDTS Component	—
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	UPLOAD_QUERY
Severity	LOG_INFO
Format	Full Upload query [%s].
Explanation	This query is used for generating Full Upload data.
Required Info	—
Recommended Action	—
DDTS Component	—
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS.If a similar DDTS does not exist, log a new DDTS for this problem.
Message	UPDATES_QUERY
Severity	LOG_INFO
Format	Incremental Updates query [%s].
Explanation	This query is used for generating incremental update data.
Required Info	—
Recommended Action	—
DDTS_COMPONENT	—
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	FTP_COMMAND
Severity	LOG_INFO
Format	FTP command [%s].
Explanation	This command is sent to wdftp.
Required Info	—
Recommended Action	—
DDTS_COMPONENT	—
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS.If a similar DDTS does not exist, log a new DDTS for this problem.
Message	START_AUDITTRIG
Severity	LOG_INFO
Format	Starting audit trigger. Query = [%s].
Explanation	This query is used to start the audit trigger.
Required Info	—
Recommended Action	—
DDTS_COMPONENT	—
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	STOP_AUDITTRIG
Severity	LOG_INFO
Format	Stopping audit trigger. Query = [%s].
Explanation	This query is used to stop the audit trigger.
Required Info	—
Recommended Action	—
DDTS_COMPONENT	—
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	WAITROW_QUERY
Severity	LOG_INFO
Format	waitForRowInsertion method query = [%s].
Explanation	This query is used to service waitForRowInsertion request.
Required Info	—
Recommended Action	—
DDTS_COMPONENT	—
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	COLDSTART_CLEANUP
Severity	LOG_INFO
Format	CWM is cold started, cleaning up all synched tables.
Explanation	When CWM is cold started, all WANDEST clients must do a full upload. The server cleans up all synched_table entries.
Required Info	—
Recommended Action	—
DDTS_COMPONENT	—
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.

DB Loader Exceptions

All the exceptions associated with DB Loader are listed in Table B-6.

Table B-6 DB Loader Exceptions 

Heading	Content/Required Action
Message	CREATE_DB_FAIL
Severity	L2
Format	Create DataBase Fail, system exception [%s].
Explanation	Could not create the database.
Required Info	WANDEST log files.
Recommended Action	The DBLoader could not create the database specified in the command line argument. The DBLoader checks the following components: •Informix database is installed correctly. •Path contains the Informix executables. •The $INFORMIXSERVER is set. •Permissions of the users are correct.
DDTS Component	CSC.wanbu.sv
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	OPEN_DIR_ERROR
Severity	L2
Format	Could not open directory. directory [%s].
Explanation	Could not open the directory.
Required Info	WANDEST log files.
Recommended Action	DBLoader could not open the directory, specified in the command line arguments, to load the data files. Check that the directory exists and that the permissions are correct.
DDTS Component	CSC.wanbu.sv.
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.
Message	NO_FILE_LOADED
Severity	L4
Format	There are no data files loaded, dirname [%s].
Explanation	The DBLoader program cannot find any valid file to load within the directory.
Required Info	WANDEST log files.
Recommended Action	DBLoader could not file any valid files (<tablename>.new, <tablename>.del or <tablename>.unl) to load in to database under the directory that is specified by the command line arguments. Another possible cause might be an incorrect control file format or an incorrect delimiter. These errors might cause the Debater program to contain no valid tables. Check the control file format or the delimiter specified in the command line.
DDTS Component	CSC.wanbu.sv.
TAC Details	Report to Engineering. Use Topic to search for a similar DDTS. If a similar DDTS does not exist, log a new DDTS for this problem.