Database-specific adapter messages
After database adapter activity completes, messages display indicating the results. These messages may also be recorded in the appropriate files as specified, which may include audit logs, trace files, and execution summary. These codes and messages can be returned for the following database adapters:
- DB2® (z/OS® ODBC)
- DB2 (z/OS)
- DB2 (Windows/UNIX)
- Informix®
- Microsoft SQL Server
- ODBC
- OLE DB
- Oracle
- SQL/MP
- SQL/MX
- Sybase SQL Server
The following is a listing of all the codes and messages that can be returned as a result of using the database adapters for sources or targets.
You can also troubleshoot database-specific adapters by using the adapter Trace (-T or -TRACE) or the Trace Error (-TE or -TRACEERR) command.
Adapter return codes with positive numbers are warning codes that indicate a successful operation. Adapter return codes with negative numbers are error codes that indicate a failed operation.
- Return Code
- Message
- 0
- Success
- 12
- Database -b argument is required with arguments mdqfile -m and query -q
- 1001
- One or more records could not be processed
- 1002
- No data found
- -1001
- Memory allocation error
- -1002
- Failed to allocate ODBC environment
- -1003
- Failed to allocate ODBC statement
- -1004
- Failed to allocate ODBC connection
- -1005
- Failed to connect to the database
- -1006
- Failed to prepare the SQL statement
- -1007
- Failed to obtain definition of column
- -1008
- Failed to bind parameters to the SQL statement
- -1009
- Failed to execute the SQL statement
- -1010
- Failed to open a cursor
- -1011
- Failed to insert a row into the database
- -1012
- Failed to read file
- -1013
- Failed to open file
- -1014
- The input buffer was of incorrect form
- -1015
- Failed to write to file
- -1016
- Database type is unknown
- -1017
- Failed to parse SQL statement
- -1018
- Failed to define host variables
- -1019
- Failed to logoff the database
- -1020
- Failed to close the cursor
- -1021
- Failed to bind parameters to the SQL statement
- -1022
- Failed to fetch a long data value
- -1023
- Failed to perform a file seek
- -1024
- Failed to create file
- -1025
- The specified query could not be found
- -1026
- The specified database could not be found
- -1027
- Failed to load DLL
- -1028
- Failed to get address of function
- -1029
- Failed to fetch a row of data
- -1030
- Failed to get data from the database
- -1031
- Failed to get data from the database
- -1032
- No rows were updated
- -1033
- The number of rows affected was undeterminable
- -1034
- The supplied statement was syntactically invalid
- -1035
- Failed to create an execution thread
- -1036
- Failed to get extended error text
- -1037
- Table is not accessible
- -1038
- Failed to disconnect from the database
- -1039
- Failed to free the database connection
- -1040
- Failed to free the environment
- -1041
- MDQ file is invalid
- -1042
- Failed to close file
- -1043
- No database connection could be found
- -1044
- No database type was specified with -DBTYPE
- -1045
- Failed to find column attributes
- -1046
- Failed to get the number of result columns
- -1047
- Failed to get large data
- -1048
- Failed to cleanup the database connection
- -1049
- Databases are not supported
- -1050
- Failed to load DLL
- -1051
- Failed to get address of function
- -1052
- Failed to commit or rollback the transaction
- -1053
- Failed to free the statement
- -1054
- Insufficient data was provided
- -1055
- Failed to bind parameters to the SQL statement
- -1056
- Failed to define large data value
- -1057
- Failed to put large data value
- -1058
- Failed to commit the transaction
- -1059
- Failed to rollback the transaction
- -1060
- The update statement was invalid
- -1061
- No type could be found to match column name
- -1062
- No suitable presentation could be found for a column
- -1063
- No suitable presentation could be found for a column
- -1064
- No suitable presentation could be found for a column
- -1065
- Internal error
- -1066
- No more rows were returned
- -1067
- No trigger was defined for the input
- -1068
- Data was unexpectedly terminated
- -1069
- Required command line options missing
- -1070
- The database command line was invalid
- -1071
- Could not find environment variable
- -1072
- Failed to attach to database
- -1073
- Failed to convert datatype to native database type
- -1074
- Failed to get list of SQL servers
- -1075
- Failed to get list of databases
- -1076
- Failed to initialize stored procedure
- -1077
- Failed to set parameter to stored procedure
- -1078
- Failed to execute stored procedure
- -1079
- Failed to get column information
- -1080
- Failed to declare host variables
- -1081
- Command line token could not be found
- -1082
- Failed to create an event
- -1083
- The command line is too long
- -1084
- The function/procedure has no return value
- -1085
- A variable length binary column is not permitted
- -1086
- Error occurred writing to a LOB column
- -1087
- Error occurred reading from a LOB column
- -1088
- Connection to Open Server failed
- -1089
- Poll to Open Server failed
- -1090
- The map contains outdated DB parameters. Rebuild the map
- -1091
- An output date was of an incorrect format
- -1092
- Internal error occurred
- -1093
- Burst complete
- -1094
- Type already exists and override was not specified
- -1095
- No Row or ProcedureCall group can be found
- -1096
- Failed to format output from an object type
- -1097
- Failed to create an object
- -1098
- An object is not permitted in fixed schema
- -1099
- Failed to convert database parameters from ASCII to EBCDIC
- -1100
- One or more columns/parameters are of an unsupported datatype
- -1101
- Failed to configure run-time environment.
- -1102
- Failed to Allocate context structure, unknown reason or not enough memory
- -1103
- A trigger could not be defined for a watch event
- -1104
- Unique table columns are required for row-based watch events
- -1105
- Procedure is not accessible
- -1106
- The configured transaction manager is not supported
- -1107
- System error occurred while waiting for a watch event
- -1108
- Triggering is not supported for this adapter.
- -1109
- User terminated database access
- -1110
- The trace file name is too long, or the running directory is too deep
The database trace file name and/or the directory name in which the failed map is located, may be longer than 128 characters.
Ensure the file and directory name are shorter than 128 characters.
- -1302
- A trigger event could not be registered
- -2002
- Insufficient data passed to output card