Jump to main content
Product Documentation
Customer Support
HCL OneDB V 1.0.1.0
What's new in
HCL OneDB™
1.0.1.0
Getting Started
Installing
Administering
Security
Client APIs and tools
SQL programming
JSON compatibility
Extending
HCL OneDB™
Designing databases
Embedding
HCL OneDB™
Release information
Search
Home
Client APIs and tools
You can use the
HCL OneDB™
implementation of client APIs to develop applications for
HCL OneDB™
database servers.
HCL OneDB™
JDBC Driver Guide
The
HCL OneDB™ JDBC Driver Programmer's Guide
describes how to install, load, and use
HCL OneDB™ JDBC Driver
to connect to the
HCL OneDB™
database from within a Java™ application.
Appendixes
Error messages
-79702
Cannot create new object
Client APIs and tools
You can use the
HCL OneDB™
implementation of client APIs to develop applications for
HCL OneDB™
database servers.
Change Data Capture API Programmer's Guide
These topics describe how to program applications to process changed data from
HCL OneDB™
databases using the
HCL® OneDB® Change Data Capture API
.
The
HCL OneDB™
Change Data Capture API Programmer's Guide
describes how to program applications to process changed data from
HCL OneDB™
databases using the
HCL® OneDB® Change Data Capture API
.
ESQL/C Guide
The
HCL OneDB™
ESQL/C Programmer's Manual
explains how to use , the
HCL OneDB™
implementation of Embedded Structured Query Language (SQL) for C (ESQL/C), to create client applications with database-management capabilities.
GLS User's Guide
These topics describe the Global Language Support (GLS) feature available in
HCL® OneDB®
products.
The
HCL OneDB™
GLS User's Guide
describes the Global Language Support (GLS) feature available in
HCL® OneDB®
products.
HCL OneDB™
ODBC Driver Guide
The
HCL OneDB™ ODBC Driver Programmer's Manual
serves as a user guide and reference for
HCL OneDB™ ODBC Driver
, which is the
HCL OneDB™
implementation of the Microsoft™ Open Database Connectivity (ODBC) interface, Version
3.0
.
OneDB .NET Core Provider
The
.NET Core Provider
for OneDB® is used for developing .NET applications.
HCL OneDB™
JDBC Driver Guide
The
HCL OneDB™ JDBC Driver Programmer's Guide
describes how to install, load, and use
HCL OneDB™ JDBC Driver
to connect to the
HCL OneDB™
database from within a Java™ application.
Getting started
Connect to the database
Encryption options
PAM authentication method
Perform database operations
Update the database
Parameters, escape syntax, and unsupported methods
Handle transactions
Handle errors
Access database metadata
Other
HCL OneDB™
extensions to the JDBC API
Store and retrieve XML documents
Work with
HCL OneDB™
types
Work with opaque types
Globalization and date formats
Smart trigger feature
Tuning and troubleshooting
Appendixes
Sample code files
DataSource extensions
Mapping data types
Convert internal
HCL OneDB™
data types
For your Java™ application to work with the internal server representation of
HCL OneDB™
data types, use the
IfxToJavaType
class. For example, if your application is using the
HCL® OneDB® Change Data Capture API
, you can use the
IfxToJavaType
class to interpret the byte stream.
Error messages
-79700
Method not supported
-79702
Cannot create new object
-79703
Row/column index out of range
-79704
Cant load driver
-79705
Incorrect URL format
-79706
Incomplete input
-79707
Invalid qualifier
-79708
Cannot take null input
-79709
Error in date format
-79710
Syntax error in SQL escape clause
-79711
Error in time format
-79712
Error in timestamp format
-79713
Incorrect number of arguments
-79714
Type not supported
-79715
Syntax error
-79716
System or internal error
-79717
Invalid qualifier length
-79718
Invalid qualifier start code
-79719
Invalid qualifier end code
-79720
Invalid qualifier start or end code
-79721
Invalid interval string
-79722
Numeric character(s) expected
-79723
Delimiter character(s) expected
-79724
Character(s) expected
-79725
Extra character(s) found
-79726
Null SQL statement
-79727
Statement was not prepared
-79728
Unknown object type
-79729
Method cannot take argument
-79730
Connection not established
-79731
MaxRows out of range
-79732
Illegal cursor name
-79733
No active result
-79734
INFORMIXSERVER has to be specified
-79735
Cant instantiate protocol
-79736
No connection/statement establish yet
-79737
No metadata
-79738
No such column name
-79739
No current row
-79740
No statement created
-79741
Cannot convert to
-79742
Cannot convert from
-79744
Transactions not supported
-79745
Read only mode not supported
-79746
No Transaction Isolation on non-logging db's
-79747
Invalid transaction isolation level
-79748
Cannot lock the connection
-79749
Number of input values does not match number of question marks
-79750
Method only for queries
-79755
Object is null
-79756
Must start with 'jdbc'
-79757
Invalid subprotocol
-79758
Invalid IP address
-79759
Invalid port number
-79760
Invalid database name
-79761
Invalid property format
-79762
Attempt to connect to a non 5.x server
-79764
Invalid fetch direction value
-79765
ResultSet type is TYPE_FETCH_FORWARD, direction can only be FETCH_FORWARD
-79766
Incorrect fetch size value
-79767
ResultSet type is TYPE_FORWARD_ONLY
-79768
Incorrect row value
-79769
A customized type map is required for this data type
-79770
Cannot find the SQLTypeName specified in the SQLData or Struct
-79771
Input value is not valid
-79772
No more data to read or write. Verify your SQLData class or getSQLTypeName()
-79774
Unable to create local file
-79775
Only TYPE_SCROLL_INSENSITIVE and TYPE_FORWARD_ONLY are supported
-79776
Type requested (%s) does not match row type information (%s) type
-79777
readObject/writeObject() only supports UDTs, Distincts, and complex types
-79778
Type mapping class must be a java.util.Collection implementation
-79780
Data within a collection must all be the same Java™ class and length
-79781
Index/Count out of range
-79782
Method can be called only once
-79783
Encoding or code set not supported
-79784
Locale not supported
-79785
Unable to convert JDBC escape format date string to localized date string
-79786
Unable to build a Date object based on localized date string representation
-79788
User name must be specified
-79789
Server does not support GLS variables DB_LOCALE, CLIENT_LOCALE or GL_DATE
-79790
Invalid complex type definition string
-79792
Row must contain data
-79793
Data in array does not match getBaseType() value
-79794
Row length provided (%s) does not match row type information (%s)
-79795
Row extended ID provided (%s) does not match row type information (%s)
-79796
Cannot find UDT, distinct, or named row (%s) in database
-79797
DBDATE setting must be at least four characters and no longer than six characters
-79798
A numeric year expansion is required after 'Y' character in DBDATE string
-79799
An invalid character is found in the DBDATE string after the 'Y' character
-79800
No 'Y' character is specified before the numeric year expansion value
-79801
An invalid character is found in DBDATE format string
-79802
Not enough tokens are specified in the string representation of a date value
-79803
Date string index out of bounds during date format parsing to build Date object
-79804
No more tokens are found in DBDATE string representation of a date value
-79805
No era designation found in DBDATE/GL_DATE string representation of date value
-79806
Numerical day value can not be determined from date string based on DBDATE
-79807
Numerical month value can not be determined from date string based on DBDATE
-79808
Not enough tokens specified in %D directive representation of date string
-79809
Not enough tokens specified in %x directive representation of date string
-79811
Connection without user/password not supported
-79812
User/Password does not match with datasource
-79814
Blob/Clob object is either closed or invalid
-79815
Not in Insert mode. Need to call moveToInsertRow() first
-79816
Cannot determine the table name
-79817
No serial, rowid, or primary key specified in the statement
-79818
Statement concurrency type is not set to CONCUR_UPDATABLE
-79819
Still in Insert mode. Call moveToCurrentRow() first
-79820
Function contains an output parameter
-79821
Name unnecessary for this data type
-79822
OUT parameter has not been registered
-79823
IN parameter has not been set
-79824
OUT parameter has not been set
-79825
Type name is required for this data type
-79826
Ambiguous java.sql.Type, use IfxRegisterOutParameter()
-79827
Function doesn't have an output parameter
-79828
Function parameter specified isnt an OUT parameter
-79829
Invalid directive used for the GL_DATE environment variable
-79830
Insufficient information given for building a time or timestamp Java™ object.
-79831
Exceeded maximum no. of connections configured for Connection Pool Manager
-79834
Distributed transactions (XA) are not supported by this database server.
-79836
Proxy Error: No database connection
-79837
Proxy Error: Input/output error while communicating with database
-79838
Cannot execute change permission command (chmod/attrib)
-79839
Same Jar SQL name already exists in the system catalog
-79840
Unable to copy jar file from client to server
-79842
No UDR information was set in UDRMetaData
-79843
SQL name of the jar file was not set in UDR/UDT MetaData
-79844
Cant create/remove UDT/UDR as no database is specified in the connection
-79845
JAR file on the client does not exist or cant be read
-79846
Invalid JAR file name
-79847
The 'javac' or 'jar' command failed
-79848
Same UDT SQL name already exists in the system catalog
-79849
UDT SQL name was not set in UDTMetaData
-79850
UDT field count was not set in UDTMetaData
-79851
UDT length was not set in UDTMetaData
-79852
UDT field name or field type was not set in UDTMetaData
-79853
No class files to be put into the jar
-79854
UDT java class must implement java.sql.SQLData interface
-79855
Specified UDT java class is not found
-79856
Specified UDT does not exists in the database.
-79857
Invalid support function type
-79858
The command to remove file on the client failed
-79859
Invalid UDT field number
-79860
Ambiguous java type(s) - can't use Object/SQLData as method argument(s)
-79861
Specified UDT field type has no Java™ type match
-79862
Invalid UDT field type
-79863
UDT field length was not set in UDTMetaData
-79864
Statement length exceeds the maximum
-79865
Statement already closed
-79868
Result set not open, operation not permitted
-79877
Invalid parameter value for setting maximum field size to a value less than zero
-79878
Result set not open, operation next not permitted. Verify that autocommit is OFF
-79879
An unexpected exception was thrown. See next exception for details
-79880
Unable to set JDK Version for the Driver
-79881
Already in local transaction, so cannot start XA transaction
53 more
HCL OneDB™
REST API Guide
The
HCL OneDB™
REST API allows application developers to access data in their
HCL OneDB™
database server through simple HTTP requests. Applications can query, insert, load, update, and delete data in relational tables, in JSON collections, or in TimeSeries tables all through simple, JSON-based REST requests.
-79702
Cannot create new object
The software could not allocate memory for a new
String
object.