Sybase Error Messages

The last error detected by the connector is available in $dberror. The connector can detect errors raised by the SYB connector, Sybase Client-Library, and the Sybase SQL Server. For more information on the Sybase SQL Server and Sybase Client-Library errors, refer to your Sybase documentation.

The values of $dberror are shown in the table:

Values returned by $dberror for the SYB connector
$dberror value	Meaning
0	Success, no error.
1 - 30000	Error detected by Sybase Client-Library or SQL Server.
30001-31000	Error raised in a Uniface trigger.
> 31000	Your own definitions.
-1	Information request: could not report the login information.
-2	Information request: Invalid mode.
-3	Invalid mode for open table.
-4	Invalid mode for select.
-5	Fetch: Invalid mode.
-6	Fetch: did not return any rows.
-7	Fetch: returned more than one row.
-8	Update: affected more than one row.
-9	Update: did not modify any rows.
-10	Delete: more than one row affected.
-11	Delete: did not delete any rows.
-12	SQL request: Invalid mode.
-13	Wild request: Invalid mode for wildcard delete nullify.
-14	UDBSYB: Invalid mode for the main connector routine.
-15	Login: a username must be given.
-16	Selectdb requested without any aggregates.
-17	Selectdb: incorrect number of aggregates returned.
-18	Execute: Invalid mode for get_results.
-19	Execute: Invalid mode.
-20	Path Manager: Maximum logon paths have been exceeded.
-21	Path Manager: The process ID is not allocated.
-22	Path Manager: Invalid process ID.
-23	Path Manager: Invalid mode.
-24	Build SQL: Invalid mode for UsybBldSelect.
-25	Build SQL: Buffer overflow, the query was not executed.
-26	Datatype: invalid datatype in result structure.
-27	Build: The user in the table name does not match the current user.
-28	Configuration Manager: udgetasn could not read the assignment file.
-29	Transaction Manager: bad mode send to UsybTranManager.
-30	The stored procedure information structure is incorrect.
-31	Due to Deadlock: the transaction must be ended before work can continue.
-32	Build SQL: The call to unloadcb failed.
-33	Write / Read Segmented Field: text information structure error.
-34	The index information structure or the index number is incorrect.
-35	The result information structure is incorrect.
-36	Build SQL: The kernel produced an incorrect orderby list
-37	Get textpointer: could not retrieve textpointers.
-38	Configuration Manager: invalid Sybase User Option.
-39	Build SQL: error in the result structure.
-40	Open Table: Invalid table name.
-41	Memory allocation failed.
-42	The kernel sent an incorrect where list.
-43	The kernel sent an incorrect orderby list.
-44	The kernel sent an incorrect field list.
-45	The kernel sent an incorrect aggregate list.
-46	Multi-table View: base table names cannot be determined.
-47	When running with the Uniface RI option not set, overflow tables cannot be created on the fly.
-48	Run the Create Script Utility to create the overflow control.
-49	SetAggName: Illegal mode
-50	FetchRows: Incorrect number of rows.
-51	ct_results returned an illegal status
-52	ct_fetch returned an unexpected value
-53	Illegal data conversion
-54	Illegal datatype value
-55	SQL Request: Buffer overflow.
-56	Fetch: Invalid field information.
-57	Cursor Manager: cursor error detected.
-58	Cursor Manager: Illegal mode sent.
-59	Configuration: Illegal SYB connector option.
-60	Identity fields are not allowed as primary keys in entities which require overflow tables.
-61	`tdspacketsize` connector option not allowed on TM-enabled paths.
-62	`timeout` connector option not allowed on TM-enabled paths.
-63	`commit` or `rollback` request issued on TM-enabled path.
-64	Global Tran (G): unsupported TM protocol.
-65	Illegal logon path: Sybase LRM name is mandatory.
-66	`Locklevel` connector option not allowed on TM-enabled paths.
-67	Create table on the fly not allowed on TM-enabled paths.
-200	CS-LIB error: cs_convert failed
-201	CS-LIB error: cs_ctx_alloc failed
-202	CS-LIB error: cs_ctx_drop failed
-203	CT-LIB error: ct_init failed
-204	CT-LIB error: ct_debug failed
-205	CT-LIB error: ct_callback failed
-206	CT-LIB error: ct_config failed
-207	CT-LIB error: ct_con_alloc failed
-208	CT-LIB error: ct_con_props failed
-209	CT-LIB error: ct_con_drop failed
-210	CT-LIB error: ct_connect failed
-211	CT-LIB error: ct_cmd_alloc failed
-212	CT-LIB error: ct_cmd_drop failed
-213	CT-LIB error: ct_close failed
-214	CT-LIB error: ct_exit failed
-215	CT-LIB error: ct_command failed
-216	CT-LIB error: ct_cursor declare failed
-217	CT-LIB error: ct_cursor set rows failed
-218	CT-LIB error: ct_cursor open failed
-219	CT-LIB error: ct_cursor close failed
-220	CT-LIB error: ct_cursor dealloc failed
-221	CT-LIB error: ct_send failed
-222	CT-LIB error: ct_compute_info failed
-223	CT-LIB error: ct_get_data failed
-224	CT-LIB error: ct_bind failed
-225	CT-LIB error: ct_describe failed.
-226	CT-LIB error: ct_res_info failed
-227	CT-LIB error: ct_results failed
-228	CT-LIB error: ct_fetch failed
-229	CT-LIB error: ct_fetch rows failed
-230	CT-LIB error: ct_cancel failed
-231	CT-LIB error: ct_options failed
-232	CT-LIB error: ct_get_data failed
-233	CT-LIB error: ct_data_info failed
-234	CT-LIB error: ct_send_data failed
-235	CT-LIB error: ct_param failed
-236	CT-LIB Error: ct_cmd_pops failed
-239	CT-LIB error: ct_objects failed
-238	CT-LIB error: ct_ctx_global failed
-9999	Unknown connector error message

User-defined errors

The Sybase SQL statement raiserror can be used in SQL instructions to define a user error. Also, the Uniface stored procedures can be modified so they execute a raiserror statement. User-defined errors should have a value greater than 31000.

Illegal options cause logon failure

If an illegal SYB connector option is entered, the SYB connector does not allow the user to log on, and an error is raised.