This topic lists errors you may encounter when accessing data from an ODBC-enabled application. For an illustration of where the different types of error occur in the data access process, see figure 1.
Synergy DBMS errors are returned as the message part of some Synergy driver error messages.
If you’re using system catalog caching, see Troubleshooting system catalog caching for additional errors you may encounter.
number: Unknown node (type: name)
(Synergy driver) This is an internal error. Turn on Vortex API logging (Windows) (use the FULL option) and SET OPTION logging (use the LOGFILE, PLAN, and TRACE options), repeat the steps that caused the error, and then contact Synergy/DE Developer Support.
AUTHBAD: Invalid authentication syntax
(SQL OpenNet) The connect string syntax is invalid. Make sure that the username and password follow the host name. Note that this user ID and password are for the host machine, not the database. See Adding a user or system DSN for more information.
Authentication failed
(SQL OpenNet) User and password authentication failed on the server. If you’re using a Windows server, make sure the user has “log on as a batch job” privileges on the server. In addition, make sure the user and password are correct in the connect string and encryption is set to the same value on both the client and the server.
AUTHFAIL: Authentication on service failed
(SQL OpenNet) You are not authorized to run the requested host service. Make sure the username and password follow the host name, or contact your system administrator. Note that this user ID and password are for the host machine, not the database. See Adding a user or system DSN for more information.
AUTHREQ: Host ‘host_name’ requires authentication
(SQL OpenNet) The host you are connecting to requires additional authentication. If the -a option is set for vtxnetd or vtxnet2, you must specify a username and password for an account on the machine or an account for a domain that the machine is part of (in addition to any database log-in information). If you’ve done this, make sure the username and password are correct. See Adding a user or system DSN for information.
BADCONV: Data conversion failed (hostvar : number)
(xfODBC and Vortex API) The requested data conversion failed (where number is the number of the host variable — e.g., if number is 3, there is a data conversion problem with the third host variable). Check that the requested data is of the appropriate type. For example, this error occurs if you request a character column to be fetched into an integer and the column includes characters that are not numbers.
BADINI: Filename is either missing or invalid
(xfODBC and SQL OpenNet) The .ini file is missing or its contents are invalid. Make sure the file exists and that it’s correct.
BLOBCOL: Invalid BLOB column ID
(SQL OpenNet) The specified column is not a BLOB column. Check the SQL statement.
BLOBFILE: BLOB file operation (name) failed
(SQL OpenNet) I/O error processing BLOB column. This usually occurs on an insert or update.
Buffer overflow, message
(Synergy driver) The SQL UPDATE statement caused a buffer overflow. Check message for Synergy DBMS error information. For example, if there is a discrepancy between the Synergy Repository structure length and the file record length, an UPDATE will cause Synergy DBMS error 24, and message will be the text for this error: “Input size exceeds destination size”.
CANCEL: Operation canceled
(xfODBC) The operation was canceled by the driver manager. (This is an informational message.)
CANFREE: Cancel treated as SQLFreeStmt with SQL_CLOSE
(xfODBC) No processing was being done on the statement, so the call was treated as a call to SQLFreeStmt with the SQL_CLOSE option. Function returns SQL_SUCCESS_WITH_INFO. (This is an informational message.)
Cannot add temporary index
(Synergy driver) Attempt to create a temporary index to optimize a table join operation failed. Make sure you have write permission and enough available disk space.
Cannot allocate context: message
(Synergy driver) The SQL statement could not allocate a Synergy DBMS context. Contact Synergy/DE Developer Support.
Cannot begin transaction: message
(Synergy driver) The SQL COMMIT/ROLLBACK statement cannot be performed. Check message for Synergy DBMS error information.
Cannot create ‘name’: message
(Synergy driver) The specified file cannot be created. Check message for Synergy DBMS error information.
Cannot define default_index: message
(Synergy driver) The SQL statement references a table whose file creation failed. Check message for Synergy DBMS error information.
Cannot delete from ‘name’: message
(Synergy driver) The SQL DELETE statement cannot be performed. Check message for Synergy DBMS error information.
Cannot drop system tables
(Synergy driver) The system tables, tables that begin with GENESIS_, cannot be dropped. For a list of the system tables, see System catalog. Make sure the table in the DROP TABLE statement is not a system table.
Cannot end transaction: message
(Synergy driver) The SQL COMMIT statement cannot be performed. Check message for Synergy DBMS error information.
Cannot insert into ‘name’: message
(Synergy driver) The SQL INSERT statement failed. Check message for Synergy DBMS error information.
Cannot open ‘name’ for update: message
(Synergy driver) The specified file cannot be opened for update. Check message for Synergy DBMS error information.
Cannot open file filename error_message
(Synergy driver) The xfODBC driver can’t open the specified file. The path may be wrong, or the file specification may include a missing environment variable or an environment variable with an invalid setting. Alternatively, the file may not exist, permissions may not be set correctly, or the repository file definition may include an invalid character. Be sure to check the spelling and location of filename.
Cannot update ‘name’: message
(Synergy driver) The SQL UPDATE statement failed. Check message for Synergy DBMS error information.
Catalog table ‘name’ corrupted or out of date
(Synergy driver) The specified GENESIS catalog table cannot be read. It has either been modified directly, or it was created from an unsupported version of dbcreate. Regenerate the system catalog with the current version of dbcreate.
Character array too big (max: size)
(Synergy driver) The SQL statement contains a character array that is too big. The maximum size is size. Correct the statement.
Column (#) out of range
(Synergy driver) This may indicate that a GROUP BY clause doesn’t include all columns in the select list. Correct the GROUP BY clause to include all columns in the select list.
Column ‘name’, 8 byte integer not supported on this platform
(Synergy driver) The platform does not support 8-byte integers. Remove any reference to 8-byte integers from the system catalog.
Column name already defined
(Synergy driver) The SQL CREATE TABLE/VIEW statement has duplicate column names. Correct the statement.
Column: ‘name’, DBL decimal overflow
(Synergy driver) The SQL statement is attempting to join a decimal column to a column whose value is too large for the decimal column. (For example, you’ll see this error if you try to join a d1 column to a column with the value 45; this value is too large for a d1 column.) Correct the statement.
Column: ‘name’, integer overflow
(Synergy driver) An overflow occurred while converting a number to an integer. Correct the system catalog entry for the column.
Column ‘name’, invalid date data: data
(Synergy driver) The date is not valid. Correct this in your data file.
Column ‘name’ not deleted from catalog: message
(Synergy driver) The specified column cannot be deleted from the catalog. Check message for Synergy DBMS error information.
Column name undefined
(Synergy driver) The SQL statement references a column that is not defined in the system catalog. Correct the statement or define the column/table in the system catalog. Note that this can happen a GROUP BY clause includes an alias for a column in an inline view.
Column: ‘name’, Unsupported data type: type
(Synergy driver) The system catalog has an unsupported data type entry for column name. Check the system catalog definition for this column.
CONFIG: Expected a CONFIG call
(SQL OpenNet) This is an internal error that typically indicates that the vtx4 process terminated abnormally. Collect any relevant information from the event log (Windows), syslog (UNIX), or the operator console (OpenVMS), and then contact Synergy/DE Developer Support. You may be asked you to use Vortex host logging and/or Synergy DBMS logging to assist. (See Vortex host logging and Synergy DBMS logging.)
Connect: Unknown Error
(TCP/IP socket error) Although a connection was gracefully closed by the server, the client was not prepared for the closing of the connection. This is generally caused either by a version mismatch or by network latency issues where the final packet sent by the server is not received before the default server socket shutdown is initiated. This might occur, for example, if the initial connect fails with an error. See the event log (Windows), syslog (UNIX), or the operator console (OpenVMS) for information on the problem.
Connect:errno:error
(TCP/IP socket error) This error indicates either that the connection to the server has been closed, or that the xfODBC driver can’t make a connection to the SQL OpenNet server. See Connection reset by peer (10054 or 54) and Connection refused (10061 or 61).
CONNECT-1: Authorization failure
(Synergy driver) The connection failed because of the user’s security level, the length of the username, a user or group authentication failure, the length of the password, or because the password is missing.
CONNECT-2: Dictionary access failure
(Synergy driver) The connection failed because the driver was unable to read the system catalog. Check the GENESIS_HOME setting and the path specified in the connect file.
CONNECT-3: No license available
(Synergy driver) Connectivity Series is not licensed.
CONNECT-4: Init failure see logfile
(Synergy driver) There is an error in the connect file syntax. For information on the cause, create a Synergy DBMS log file by setting the SDMS_AUDIT and SDMS2_FULL environment variables. For more information, see Synergy DBMS logging.
Could not open INITSQL file ‘file_name’
(xfODBC) xfODBC could not locate the file file_name, w0hich contains SQL statements.
‘CREATE INDEX’ not valid for this table type
(Synergy driver) The SQL CREATE INDEX statement is valid only for ISAM files. Make sure the table specified in the CREATE INDEX statement is an ISAM file.
Create view column count mismatch (create: number, select number)
(Synergy driver) The SQL CREATE VIEW statement’s column list does not match the number of columns in the SELECT statement’s select list. Correct the statement.
CURDUP: Duplicate cursor name
(xfODBC) The cursor name is already in use. Specify a different name.
Data Source name is missing
(xfODBC) The specified DSN does not exist, or there is a problem with the DSN or the connect file.
Data source name not found and no default driver specified
(xfODBC) The specified DSN doesn’t exist, or there is a problem with it. Open the Microsoft ODBC Administrator and make sure the DSN exists and is configured correctly.
Note that if you are on a 64-bit Windows machine, it could be that the DSN has not been defined by the right version of the Microsoft ODBC Administrator. For example, if a 32-bit application is accessing your Synergy database via xfODBC, and the system has both 32-bit and 64-bit Synergy/DE, the DSN must be created by the 32-bit ODBC Administrator. And if Visual Studio or an application that’s part of or based on Visual Studio (such as Business Intelligence Developer Studio for SQL Server) is accessing your Synergy database, you’ll need identical 32-bit and 64-bit DSNs. See Adding a user or system DSN.
Data truncation (max: size)
(Synergy driver) Data has been truncated. Call Synergy/DE Developer Support.
DATATRUNC: Data truncated
(xfODBC) The data has been truncated. Either the data specified is too long or supplied output buffers are too small. Modify the size of the output buffers. (You can do this with the “Fetch buffer size” field in the xfODBC Setup window. See Adding a user or system DSN for information.)
DB error: error_name
(Synergy driver) This error is reported by the database. See your database documentation for more information.
DIALOG: Dialog box failed
(xfODBC) The connect dialog box failed. Notify your system administrator.
Divide by ZERO
(Synergy driver) An expression in the SQL statement caused division by zero.
DLLENTRY: Could not find DB driver entry point
(SQL OpenNet) The loaded DLL or shared library does not contain the expected entry point. This typically happens when the wrong DLL or shared library has been loaded and occurs only on machines that support DLLs or shared libraries. Call Synergy/DE Developer Support.
DLLLOAD: Could not load name
(SQL OpenNet and Vortex API) One of the Connectivity Series components can’t load a needed DLL or shared library. The specified DLL or shared library may be missing, it may be invalid (incorrectly named or an incorrect version), its file specification may be missing from PATH (on Windows) or from the library path (on UNIX), it may not be able to access third-party DLLs or shared libraries it needs, or if you’re on UNIX, the setuid (+s) bit may be set for vtxnetd or VTX4. DLLLOAD errors occur only on machines that support either DLLs or shared libraries, and these errors are generally caused by a problem with the way Connectivity Series is installed or, on UNIX, by a failure to source setsde correctly.
To troubleshoot, run the dltest utility from the command line. This utility indicates whether needed Connectivity Series DLLs or shared libraries can be accessed. On UNIX, it also tells you the name of the library path environment variable (for example, LIBPATH on AIX).
If you are on UNIX, make sure the setuid (+s) bit is not set for vtxnetd or VTX4. The setuid bit prevents the library path environment variable from being used. This will cause DLLLOAD errors — though it won’t affect the ability of dltest to access needed .so files. (Note that as distributed, the setuid bit is not set for vtxnetd and VTX4, so this won’t be a problem unless you’ve added it.)
Make sure all the resources that the DLL or shared library needs are available. For example, if you get a DLLLOAD error for GDS0.dll, it may be that Connectivity Series can’t find one of the DLLs required by GDS0.dll. (These include SDMS22.dll and VTXIPC.dll.) On Windows, you can use the Dependency Walker utility (depends.exe) to determine which resources are required for a DLL. (You can download Dependency Walker from www.dependencywalker.com.) On most UNIX systems, you can use the ldd command to determine which resources are required for a shared library.
For SQL OpenNet, it may be that setsde isn’t used before vtxnetd attempts to implement the SQL OpenNet server. Check the rc file and make sure setsde is used before startnet. For information on which Synergy shared libraries are causing the error, run dltest from the rc file (directly before the startnet command).
DLLLOAD: Invalid client DLL version. (expected version#, found version#)
(xfODBC, SQL OpenNet) A DLL on the client machine is out of date — for example, you could get this error if you have an outdated version of tod32.dll.
DRVCONF: Driver not configured
(SQL OpenNet) This is an internal error that typically indicates that the vtx4 process terminated abnormally. Collect any relevant information from the event log (Windows), syslog (UNIX), or the operator console (OpenVMS), and then call Synergy/DE Developer Support.
Error: 8 byte integer not supported on this platform
(Synergy driver) Your platform does not support 8-byte integers. Remove the 8-byte field definition from your repository and regenerate your system catalog.
Error: Could not connect to request pipe (Error:6)
(SQL OpenNet, Windows only) The system catalog you are attempting to load into memory has already been cached.
EXECFAIL: Exec program_name failed on host host_name
(SQL OpenNet) The service (program) specified in the network connection string could not be started. This occurs when the service cannot be found, does not have the correct permissions, or is not listed as a valid service.
Make sure the service exists, is listed as a valid service, and that you are connecting with the correct username and password. Use vtxnetd/vtxnet2 logging and check the resulting tcm_pid.log file. See vtxnetd and vtxnet2 programs for information. Check your operating system documentation for information on the error number (nnn).
Fetch error: message
(Synergy driver) The SQL statement caused a fetch error. Check message for Synergy DBMS error information.
File ‘file_name’ already exists
(Synergy driver) The SQL CREATE TABLE statement references a table that is already created. Make sure the specified table does not already exist.
File ‘file_name’ cannot be removed: message
(Synergy driver) The specified file cannot be removed. Check message for Synergy DBMS error information.
File file_name could not be opened
(Synergy driver) The file file_name was not found. If file_name is synodbccache.dat, this error may indicate that the account you’re using can’t be used to unload the system catalog from the cache. A system catalog can be unloaded only by the user (account) that cached it.
File ‘file_name’ does not exist
(Synergy driver) The SQL statement references a table stored in a file that does not exist. It may have been deleted by another user using a different system catalog. Disconnect and then reconnect.
File error TRIWRT ‘No space left on device’
(Synergy driver) The sort (order by) work file is out of disk space. Allocate more space on your disk drive.
FLIPOVER: Flip buffer overflow
(SQL OpenNet) This error occurs if too many parameters are specified. The current limit is approximately 250 parameters. Note that multiple dimensions are not included in this limit.
Format error in ‘datafiles’
(Synergy driver) The datasource line of the connect file is not defined correctly. See Setting Up a Connect File.
FUNCSEQ: Function sequence error
(xfODBC) The sequence of function calls is invalid. Make sure you follow the sequence specified in Microsoft’s ODBC Programmer’s Reference. (See the section on ODBC state transition.)
Function function_name not implemented yet
(Synergy driver) The function has not been implemented. Call Synergy/DE Developer Support.
‘GENESIS_HOME’ environment variable not found
(Synergy driver) The GENESIS_HOME environment variable is not set. For information on setting this variable, see Specifying the connect file location (GENESIS_HOME).
HOSTNOTFOUND: Host host_name not found
(SQL OpenNet) The host you’re trying to connect to has not been found. Make sure the spelling of the host name is correct.
If any numeric operand is NULL then only ‘==’ and ‘!=’ are valid
(Synergy driver) The SQL statement’s WHERE clause uses and invalid operator with a null value. When comparing a null value, only IS NULL, =NULL, IS NOT NULL, and <>NULL are valid. (For example, SALARY > NULL is invalid.) Correct the statement.
Illegal data: data. Expected format: format
(Synergy driver) Data is not correctly formatted. For example, the message “Expected format: ‘Default Datetime Mask’” indicates that a datetime conversion did not match the default datetime mask (see Masks for dates and times in SQL statements).
Illegal DECODE format (from,val,code,val,code...[,default])
(Synergy driver) DECODE format is incorrect. Check the DECODE syntax in your Oracle documentation.
Illegal format specification: ‘format_qualifier’
(Synergy driver) The format qualifier format_qualifier is not correct.
Illegal number of parameters for builtin function
(Synergy driver) The SQL statement has the wrong number of parameters for the built-in function. Correct the statement.
Illegal parameters for function function_name
(Synergy driver) Call Synergy/DE Developer Support.
Index ‘name’ not deleted from catalog: message
(Synergy driver) The specified index cannot be deleted from the system catalog. Check message for Synergy DBMS error information.
Index column ‘column_name’ not deleted from catalog: message
(Synergy driver) The specified index column cannot be deleted from the system catalog. Check message for Synergy DBMS error information.
INTERNAL: operation_number
(Synergy driver) Call Synergy/DE Developer Support with the operation_number.
Invalid connect syntax (uid/pwd/datasource)
(SQL OpenNet) The DSN is invalid or there’s a problem with encryption. In addition to a misconfigured DSN or a corrupt net.ini file, there are a number of things that can cause this error. Check the following:
- Verify that the key_connect setting in the net.ini file (on the client) matches the setting on the server (set with the vtxnetd/vtxnet2 -k option; see vtxnetd and vtxnet2 programs for details).
- Verify that the net.ini file is in the connect\synodbc\lib directory and that VORTEX_HOME is set to the connect\synodbc directory. (On Windows, if you install both 32-bit and 64-bit Connectivity Series on a 64-bit machine, the last version installed determines the VORTEX_HOME setting by overwriting the previous setting.)
- Verify that there is only one net.ini file on the client machine. Although the net.ini file should be located in the VORTEX_HOME\net directory, xfODBC looks in the current directory first, so multiple net.ini files may result in an error.
For additional information, see Setting SQL OpenNet client options in net.ini.
Invalid integer
(SQL OpenNet, xfODBC) The number specified for the encryption key is invalid or the net.ini file is corrupt. Verify that the key is set to an integer value in the correct range, and make sure the net.ini file has no control characters.
Invalid parameter
(Synergy driver) An invalid parameter was sent for the command. Make sure the parameters you use are valid.
Invalid password
(Synergy driver) The password is incorrect. Note that passwords are case sensitive. Make sure the spelling and case are correct.
Invalid predicate result (NULL or invalid datatype)
(Synergy driver) The SQL statement’s WHERE clause returned a null or a result with an invalid data type. Correct the statement.
Invalid USERID and/or PASSWORD
(xfODBC) This indicates that you’ve entered an invalid username or password or that there may be a problem with the users in your system catalog. Start by checking the spelling and case of the username and password you used to access the database. If that isn’t the problem, make sure the users are set up correctly (see Managing access with users, groups, and table settings). If this doesn’t uncover the problem, check encryption settings on the server and the client and make sure VORTEX_HOME is set to the correct directory (see Setting SQL OpenNet client options in net.ini).
INVARG: Invalid argument
(xfODBC) An argument specified for an ODBC API function is invalid. Consult your ODBC documentation for the correct syntax.
INVAUTH: Invalid authorization
(xfODBC) The user is not authorized to connect to the specified data source. Check your username and password.
INVBUFLEN: Invalid string or buffer length
(xfODBC) The length specified is invalid. Negative values, such as SQL_NTS, have special meaning, but not all negative values are valid. Check your ODBC documentation for valid length specifiers.
INVCOLNUM: Invalid column number
(xfODBC) The specified column number is out of range. Use the correct column number.
INVCURNAM: Invalid cursor name
(xfODBC) The specified cursor name is invalid. Refer to your ODBC documentation for the maximum allowed length.
INVCURSTA: Invalid cursor state
(xfODBC) The state of the cursor (opened, closed, and so forth) is not valid for the current operation. Make sure you’ve followed the necessary steps before calling this function. See the ODBC state transition section of Microsoft’s ODBC Programmer’s Reference for information.
INVDATA: Invalid data
(xfODBC) The data for the specified operation is invalid. Verify the data.
INVDATE: Invalid date/time
(SQL OpenNet) The format of the date and/or time data is invalid. Verify the data. See Default formats and types for returned dates and times for information.
INVDRVVER: DB version mismatch (expected: driver_name, found version_number)
(SQL OpenNet) The version of the database driver is not at the same level as the SQL OpenNet runtime library. This error is most common when SQL OpenNet client/server is being used, but can also occur if an older driver has been linked with a newer runtime library. Make sure the client and the server are running the same version of Connectivity Series.
INVHOSTSYN: Invalid host/service name syntax
(SQL OpenNet) The host/service syntax is incorrect. Correct the syntax.
INVNUM: Invalid (internal) number
(SQL OpenNet) The data being converted is invalid. Check the data.
INVVER: NET version mismatch (host: host_ver, client: client_ver)
(SQL OpenNet) The version of SQL OpenNet on the server is different than the version on the client. Make sure both client and server use the same version of Connectivity Series.
KEEPALIVE: Setting SO_KEEPALIVE failed
(SQL OpenNet) This indicates that the socket option keepalive failed or was not set. Call Synergy/DE Developer Support.
(xfODBC) On OpenVMS, this error may indicate that there is insufficient memory or other resources. Open STARTNET.COM and make sure that the buffer, file_limit, page_file, queue_limit, and subprocess options are set according to the recommendations in STARTNET.COM. Or, as an alternative, you can check the following OpenVMS SYSGEN parameters and make sure their settings are equal to or greater than the settings listed below. (Note, though, that we recommend using the STARTNET.COM settings.)
PQL_DPGFLQUOTA 164593
PQL_DENQLM 800
PQL_DASTLM 256
PQL_DBIOLM 128
PQL_DDIOLM 128
If one of these parameter settings is missing, or if any of the settings don’t meet these minimums, add a MIN_xxx setting or modify the setting in MODPARAMS.DAT for your system. For example, set
MIN_PQL_DENQLM=800
Then use AUTOGEN.COM to re-configure your system and re-boot.
LINGER: Setting SO_LINGER failed
(SQL OpenNet) This indicates that the socket option LINGER failed or was not set. Call Synergy/DE Developer Support.
MANYCONN: Too many connections
(xfODBC and SQL OpenNet) The limit for concurrent ODBC handles has been exceeded. xfODBC supports a maximum of 1024 concurrent ODBC handles. However, system limitations may reduce the number xfODBC can use. (Handles are typically have a one-to-one correspondence with connections. However, and ODBC program could incorrectly close connections without deallocating handles.)
For OpenVMS systems, STARTNET.COM is distributed with settings that allow approximately 10 concurrent handles (which are processes on OpenVMS). For information on changing these settings, see the comments in STARTNET.COM.
MANYSTMT: Too many statements
(xfODBC) The number of allowable statements has been exceeded. Either increase the limit in the Statements field in the xfODBC Setup dialog box or free any statements you are not using or do not need.
MISSENV: Missing environment variable
(xfODBC) The GENESIS_HOME or VORTEX_HOME environment variable is missing. Make sure these environment variables are set. For more information, see Specifying the connect file location (GENESIS_HOME) and Other environment variables used by xfODBC.
Missing column separator (row: row_number, col: column_number)
(Synergy driver) A column separator is missing at row row_number, column column_number.
Missing string delimiter (row: row_number, col: column_number)
(Synergy driver) A string delimiter is missing at row row_number, column column_number.
No data source
(Synergy driver) The connect string does not specify a connect file. For information on connection strings, see Building connect strings.
No datasource specified
(Synergy driver) The connect file does not contain a datasource specification (which specifies the location of the data files). For information, see Setting Up a Connect File.
No dictionary source directory defined
(Synergy driver) The connect file does not contain a dictsource definition. For information, see Setting Up a Connect File.
No directory defined
(Synergy driver) The connect file does not contain a datasource definition. For information, see Setting Up a Connect File.
NOCONN: Not connected
(xfODBC and SQL OpenNet) A connection must be performed before any other operation.
NOCURNAM: No cursor name available
(xfODBC) A cursor name has not been assigned. Assign a cursor name.
NODSN: No DSN specified
(xfODBC) No data source name (DSN) was specified. Make sure the connect string specifies a DSN.
NOINTR: Host cannot be interrupted
(Synergy driver) Your ODBC-enabled application called SQLCancel, but the xfODBC driver is not in a position to cancel its operation.
NOMEM: Out of memory
(SQL OpenNet and xfODBC) This is a fatal error. Either there is no more heap memory available (which is rare), or the heaps have been corrupted. Notify your system administrator.
Non aggregates require a GROUP BY expression
(Synergy driver) This generally indicates that the SELECT statement contains aggregate and non-aggregate select list items, which requires a GROUP BY expression. Use GROUP BY or change the statement’s structure.
If the statement has a GROUP BY clause, this could indicate that a column specified in the GROUP BY isn’t in the select list. All columns in a GROUP BY expression must be in the select list for the statement.
Not implemented yet
(Synergy driver) The function, statement, or subroutine has not been implemented.
NOTCAP: Driver not capable
(xfODBC) xfODBC does not support the requested capability.
NOTIMP: feature_name not implemented
(xfODBC) The feature has not been implemented yet. Use ODBC API logging to find out more about the missing feature, and then call Synergy/DE Developer Support.
NOWHDL: No window handle available
(xfODBC) No window handle is available to open the connect dialog. Notify your system administrator.
NULL not allowed for column
(Synergy driver) Either the SQL statement (INSERT or UPDATE) specifies a null value for a column that cannot accept null values, or a column that cannot accept null values has been omitted from an INSERT statement that affects that column’s table. Correct the statement. (Note that omitting a column from an INSERT statement is equivalent to specifying a null value for the column.)
Number of columns does not match number of values
(Synergy driver) The SQL INSERT statement’s values do not match the number of columns defined for the table or listed in the column list of the SQL statement. Correct the statement.
ODBC call failed, [TOD] [ODBC] [GENESIS] Synergy DBMS: Table
‘DBA.GENESIS_COLUMNS’ not found [ #31 ]
or
ODBC call failed, [TOD] [ODBC] [GENESIS] Synergy DBMS: Fetch error, Insufficient memory for attempted operation
(xfODBC) This error indicates that there is insufficient memory or other resources on OpenVMS. For example, when trying to access data from a client machine with an ODBC application, such as Microsoft Access, you may be able to link to the first table you select, but get this error when you select a second table. Or you may get this error on subsequent attempts to link to the tables you’ve selected. See Licensing error for information on resolving this.
Only ‘=’ is allowed with ROWID
(Synergy driver) The SQL statement’s WHERE clause contains an invalid ROWID predicate. Correct the statement.
Operands not compatible
(Synergy driver) The specified operands cannot be used together and/or cannot be used on this type of data. Correct the statement.
Operation requires named authorization
(Synergy driver) The SQL statement requires the specified authorization. Make sure you have the authority to issue the statement.
OPTCHG: Option value changed
(xfODBC) The value of an option has been changed by the driver to a supported value (as allowed by the ODBC specification). This is an informational message for behavior that is generally benign. If the application quits when this is reported, there is probably another cause. Use ODBC trace logging to find the underlying cause.
Out of memory (Save all work then exit and restart)
(Synergy driver) There is insufficient system memory available for the requested operation. Save all work; then exit and restart.
PARMCNT: Wrong number of parameters
(xfODBC) The number of parameters specified does not match the number of parameters required by the statement. Modify your program to use the correct number of parameters for the statement.
PARMDTY: Invalid parameter data type
(xfODBC) The data type specified for the parameter is unknown. Consult the ODBC documentation for valid data types.
PARMNUM: Invalid parameter number
(xfODBC) The parameter number specified is out of range. Verify that your program uses the correct parameter number.
(pos: position_number) - End of buffer reached
(Synergy driver) The SQL statement ended prematurely. Check the syntax for the command you are using.
(pos: position_number) - Ending quote missing
(Synergy driver) The ending quotation mark is missing at position position_number in the SQL statement. Add the missing quotation mark.
(pos: position_number) - Identifier too long
(Synergy driver) The SQL statement contains an identifier at position position_number that is too long. Identifiers are limited to 30 characters. Rename the identifier.
(pos: position_number) - Illegal character
(Synergy driver) The SQL statement contains an illegal character at the given position. Check the statement.
(pos: position_number) - String too long
(Synergy driver) The SQL statement contains a string that is too long at position position_number. Use a bind variable.
Premature end of line (row: row_number)
(Synergy driver) There is a premature end of line at row row_number.
Read error: message
(Synergy driver) The SQL statement caused a read error. Check message for Synergy DBMS error information.
RECEIVE INFO ERROR: No such file or directory
(SQL OpenNet) The socket connection disappeared. The server database component crashed or has been terminated. Call Synergy/DE Developer Support.
Recv:errno:error
(TCP/IP socket error) This error indicates either that the connection to the server has been closed, or that the xfODBC driver can’t make a connection to the SQL OpenNet server. See Connection reset by peer (10054 or 54).
Recv: Unknown Error
(TCP/IP socket error) Although a connection was gracefully closed by the server, the client was not prepared for the closing of the connection. This is generally caused either by a version mismatch or by network latency issues where the final packet sent by the server is not received before the default server socket shutdown is initiated. This might occur, for example, if the initial connect fails with an error. See the event log (Windows), syslog (UNIX), or the operator console (OpenVMS) for information on the problem.
Server is not running in SSL mode
(Synergy driver) The DSN specifies that data packet encryption (SSL) is required, but the SQL OpenNet service is not configured to use data packet encryption. See vtxnetd and vtxnet2 programs and Using data packet encryption for SQL OpenNet.
SERVNOTFOUND: Service/Protocol name not found
(SQL OpenNet) The service or protocol cannot be found. Ensure that vtxnetd or vtxnet2 is specified in your services file. If it isn’t, you must either add it to the services file or specify the port number in the xfODBC Setup window. See Adding a user or system DSN and Configuring SQL Connection (client) for details.
SOCKET: Socket() failed
(SQL OpenNet) xfODBC is unable to open a socket. The operating system may have run out of descriptors. Notify your system administrator.
Sort column name out of range (1 - number)
(Synergy driver) The ORDER BY clause for the SELECT statement references a column number that is out of range. Correct the statement.
Sub-query must return a single column
(Synergy driver) The SQL statement contains a subquery whose result set has more than one column. Correct the statement.
Synergy DBMS: ‘column_name’, invalid data: ‘date_data’
(Synergy driver) This indicates that an operation has attempted to write an invalid date (date_data) to a timestamp key field (column_name).
Synergy DBMS: File ‘GENESIS_USERS’ does not exist
(Synergy driver) This indicates that although the system catalog describes GENESIS_USERS, no GENESIS_USERS.ISM file exists for the catalog. To resolve this, regenerate your system catalog. The dbcreate utility no longer describes GENESIS_USERS or creates this file, so regenerating the system catalog prevents this situation.
Synergy DBMS: Cannot open “Filename”, No privilege to this directory
(Synergy driver) This may indicate that security levels will not allow the operation. Check access levels for tables and the user’s group to make sure the user has read and (if necessary) write access to the tables. See Managing access with users, groups, and table settings.
Synergy DBMS: LIST error. Index index_number not created
(SQL OpenNet) Syngenload did not create the system catalog cache correctly. To fix this, follow the instructions in Correcting other caching problems.
SYNLEV: Insufficient GENESIS syntax level
(Synergy driver) There is a version mismatch between the client and the server at the Synergy database driver (VTX4) level. Make sure that both sides of the network connection use the same version.
Table ‘name’ not deleted from catalog
(Synergy driver) The SQL DROP TABLE statement failed due to a Synergy DBMS error. Call Synergy/DE Developer Support.
Table ‘name’ still open by other cursors
(Synergy driver) The DROP TABLE statement references a table that is still being accessed by other cursors. Make sure all cursors that use the table are closed before issuing the DROP TABLE statement.
Table name undefined
(Synergy driver) The SQL statement references a table that is not defined in the system catalog. Correct the statement to reference a defined table or define the table in the system catalog.
Table/View ‘name’ already in catalog
(Synergy driver) The SQL CREATE TABLE/VIEW statement references a table or view that is already defined. Check the tables/views specified in the statement.
TIDUSED: Statement already in use
(xfODBC) Another thread is currently using the statement. Make sure your program is not using a statement that’s used by another thread.
to_char/date/number’s format mask must be a constant string
(Synergy driver) The SQL statement uses a data conversion function with a non-constant format mask string. Correct the statement.
Too many columns number (max: max_number)
(Synergy driver) The SQL statement references a table which exceeds the maximum number of columns. (Number is the number of columns in your system catalog, plus one for ROWID.) You can increase the maximum number of columns that xfODBC allows by changing the Columns setting in the xfODBC Setup dialog box. Note that changing the Columns setting does not affect the number of columns your ODBC-enabled application can handle.
Too many columns specified
(Synergy driver) The SQL statement has too many columns defined. Correct the statement.
Too many cursors opened
(Synergy driver) Too many cursors are open at once. Close some cursors and retry.
Too many sort columns (max: number)
(Synergy driver) The SQL SELECT statement has too many columns in the ORDER BY clause. Reduce the number of columns in the ORDER BY clause.
Too many sub-queries at level level_number (max: max_number)
(Synergy driver) The SQL statement contains too many subqueries. Correct the statement.
Too many tables in SELECT (max: size)
(Synergy driver) The SQL SELECT statement contains too many tables. Correct the statement.
UNDESTYP: Unknown descriptor type
(xfODBC) The fDescType for SQLColAttributes( ) is unknown. Modify your program to use the correct descriptor.
UNFETTYP: Unknown fetch type
(xfODBC) Currently, only SQL_FETCH_NEXT is supported. Modify your program to use only SQL_FETCH_NEXT.
UNINTYP: Unsupported InfoType: type
(xfODBC) Type is not supported. Consult your ODBC documentation for valid values.
Unknown command
(Synergy driver) You’ve used an unrecognized command.
Unknown error code
(Synergy driver) This is an internal error. Turn on Synergy DBMS logging and Synergy driver logging (see Enabling Synergy driver logging), repeat the steps that caused the error, and then call Synergy/DE Developer Support.
Unknown executable node (type: $1)
(Synergy driver) Unexpected virtual machine code. This is an internal error and shouldn’t occur. If it does, turn on Synergy driver logging and SET OPTION logging, repeat the steps that caused the error, and then call Synergy/DE Developer Support. (For information on Synergy driver logging, see Using logging to determine if a system catalog is cached.)
UNOPT: Unknown option
(xfODBC) The xfODBC driver doesn’t recognize the option. Consult your ODBC documentation for valid options.
UNUNOPT: Unknown Uniqueness option
(xfODBC) The xfODBC driver doesn’t recognize the uniqueness option. Consult your ODBC documentation for valid values.
UNXACOPR: Unknown transaction operation
(xfODBC) The xfODBC driver doesn’t recognize the transaction operation. Consult your ODBC documentation for valid values.
User does not have drop table permission
(Synergy driver) The SQL DROP TABLE statement cannot be performed by this user. Check the table specified in the statement.
VM Error: Virtual memory space exceeded
(Synergy driver) This generally indicates that the amount of memory available for SQL sort operations is insufficient. Use SET OPTION SORTPAGES to increase this amount.
ZEXMAIN: Multi RID overflow
(xfODBC) This generally indicates that MERGESIZE is set too a value that’s too small for the query. Increase this setting by using SET OPTION or the “Max number of rows” field in the xfODBC Setup dialog box (the dialog box that enables you to add and configure xfODBC DSNs). Then try the query again. See Notes on MERGESIZE for more information.
ZEXMAIN: Sort buffer overflow
(Synergy driver) This generally indicates that the memory available for SQL sort operations (ORDER BY, GROUP BY, or DISTINCT) is insufficient. Use SET OPTION SORTPAGES or the “Total” and “In memory” settings in the xfODBC Setup dialog box to increase the available memory. (A SET OPTION SORTPAGES command overrides the “Total” and “In memory” settings for a DSN.) See Setting up access with DSNs for additional information.
