Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Using Messages With Identifiers : SK: ODBC Gateway/Oracle Gateway

SK: ODBC Gateway/Oracle Gateway
S6BSK001E
DBSource % in the definition of % does not match the gateway's TRXDB %
ODBC Gateway/Oracle Gateway
Under Security Level=1, an attempt was made to modify data via an SLK definition, referring to the data source, which is different from the gateway's Fail Safe transaction database (TRXDB).
Make sure the data source name in the definition matches the Fail Safe transaction database (TRXDB) in the gateway session configuration.
S6BSK002E
Unqualified delete request on the table %: %
ODBC Gateway/Oracle Gateway
An attempt was made to delete a row of a table, while no current occurrence was available and no WHERE clause was specified.
The occurrence cannot be deleted unless it has been read previously or specified by means of a WHERE clause in the delete statement.
S6BSK003E
% %: %
ODBC Gateway/Oracle Gateway
Either the client interface (ODBC or OCI) or the target DBMS has issued an error message. Depending on the nature of the error, this message may also refer to the table and field (in parentheses), which were being processed when the error occurred.
Refer to the Error Messages in your ODBC documentation, the documentation provided with your target DBMS, or your Oracle documentation.
S6BSK004E
Failed to initialize the gateway's Fail Safe DBSource %
ODBC Gateway/Oracle Gateway
At Fail Safe query time, the gateway failed to establish a connection to the Fail Safe transaction database (TRXDB).
Make sure the transaction database in the gateway session configuration (TRXDB, FSTABLENAME, RECOVERYID, RECOVERYPASSWORD) is properly set up.
S6BSK005E
Illegal attempt to update the table %
ODBC Gateway/Oracle Gateway
An attempt has been made to modify data via an SLK definition, while the definition is either reserved or maps a non-modifiable entity.
Make sure no attempts are made to modify data by means of this definition.
S6BSK006E
The DBSource % does not support %.
ODBC Gateway/Oracle Gateway
The operation was rejected. In most cases, a data modification request was submitted to a read-only external DBMS session.
Make sure your transaction mode (BROWSE, NOBROWSE) matches your target DBMS's mode of operation.
S6BSK007E
The versions of the DB and binary components do not match: % and % respectively
ODBC Gateway/Oracle Gateway
The version of the Object Service Broker database objects does not match that of the binary component (LIBHRNSQ.dll for ODBC Gateway on Windows, LIBHRNOR.dll for Oracle Gateway on Windows, LIBHRNOR for Oracle Gateway on Solaris).
Make sure the releases of the Object Service Broker software you are running are consistent. Run the rule @COMP_INSTALLED to verify the release information associated with the database objects.
S6BSK008E
% %: % (connection failure)
ODBC Gateway/Oracle Gateway
An error message has been issued either by the client interface (ODBC, OCI) you use or by the target DBMS. The connection was broken. If appropriate, the message also refers to the table, which was being processed when the error occurred.
Refer to the Error Messages in your ODBC documentation, the documentation provided with target DBMS, or your Oracle documentation.
S6BSK012E
An error has occurred at connection time: %
ODBC Gateway/Oracle Gateway
A connection attempt was rejected.
Test your ODBC data source for connectivity using any ODBC-compliant tool, or test your Oracle connectivity using Oracle's tools. Note that this error may occur because of invalid security information used by the gateway. Refer to the Object Service Broker ODBC/Oracle Gateway manual for information on security configuration.
S6BSK013E
GET (as opposed to FORALL) request on reserved table %: %
ODBC Gateway/Oracle Gateway
A GET request was issued against an interpreted (reserved) table. The data source name has been dynamically inserted in the definition. Only FORALL is allowed for this table. The Object Service Broker ODBC/Oracle Gateway recognizes the following reserved table names: @SLKTABLES, @SLKCOLUMNS, @SLKQUALIFIERS, @SLKOWNERS, @SLKPROCEDURES, @SLKPROCCOLUMNS.
Avoid accessing the above tables. If this error message occurs again, contact TIBCO Support.
S6BSK014E
Corrupted definition of reserved table % : %
ODBC Gateway/Oracle Gateway
The table is an interpreted (reserved) SLK table. The data source name was dynamically inserted in the definition. The definition was modified beyond usability.
Make sure no corruption has occurred in your database, as the definition is essential to the gateway.
S6BSK015E
Insert/update field list empty (table %) : %
ODBC Gateway/Oracle Gateway
The process of building an UPDATE/INSERT SQL statement for the table has resulted in an empty field list. This can occur if your definition declares all of its fields to be virtual.
Make sure your definition correctly reflects your view of the table it maps. If yes, INSERT/REPLACE is not allowed.
S6BSK018E
Invalid update request on table %: %
ODBC Gateway/Oracle Gateway
An invalid attempt was made to modify data.
Make sure this table is not modified by the application.
S6BSK019E
The server lost track of cursor on the table %: %
ODBC Gateway/Oracle Gateway
While performing a FORALL on the table, the gateway has lost its cursor position.
This situation indicates possible memory corruption. Contact TIBCO Support.
S6BSK021E
Unable to create an additional statement context: %
ODBC Gateway/Oracle Gateway
While accessing the table, the gateway failed to create an additional statement context.
Reduce the number of tables accessed that refer to the same data source within one transaction; this data source has exhausted the maximum number of statement contexts that the target DBMS allows to exist simultaneously.
S6BSK027E
Invalid HANDLE field value in WHERE clause: stored proc result set %: %
ODBC Gateway/Oracle Gateway
While processing a request to the stored procedure result set mapping, a value for @HANDLE@ was detected that points to no actual procedure execution context.
Review your WHERE clause and make sure it the value for @HANDLE@= refers to a handle returned by a CALL/EXECUTE/TRANSFERCALL statement previously issued against a stored procedure mapping.
S6BSK028E
"R" or "O" parameter in WHERE clause: stored proc %: %
ODBC Gateway/Oracle Gateway
While processing a request to the stored procedure mapping, references to return value and/or output parameters have been detected.
Review your parameter list (or WHERE clause) and make sure it references input and input/output parameters only.
S6BSK029E
DBSource or TableName missing at runtime (table %): %
ODBC Gateway/Oracle Gateway
The definition of the table contains empty DBSource and/or TableName server parameters.
Review your definition to make sure both values are specified. If you use the Dynamic Server Parameter facility, review your code to make sure the definition is complete at data request time.
S6BSK030E
Invalid WHERE clause (table %) : %
ODBC Gateway/Oracle Gateway
While processing a request to the table, an invalid WHERE clause was detected.
Review your WHERE clause and make sure it is correct.
S6BSK031E
Invalid field mapping or data corrupted/truncated (field %, table %) : %
ODBC Gateway/Oracle Gateway
While converting the field of the table, a data conversion error occurred.
Review your definition. Make sure the external and Object Service Broker syntaxes you specified are compatible.
S6BSK032E
No HANDLE field reference in WHERE clause: stored proc result set %: %
ODBC Gateway/Oracle Gateway
While processing a request to the stored procedure result set mapping, no reference to @HANDLE@ was detected.
Review your WHERE clause and make sure it unambiguously specifies the value for @HANDLE@.
S6BSK034E
DBSource not found (table %): %
ODBC Gateway/Oracle Gateway
The ODBC data source the definition of the table refers to does not exist.
Review your definition and make sure the data source name you specified is correct. If yes, run the ODBC Administrator and make sure this data source exists and is properly configured.
S6BSK036E
Illegal attempt to execute a catalog function (table %): %
ODBC Gateway/Oracle Gateway
An attempt has taken place to execute, as a stored procedure, the interpreted (reserved) table.
Review your application and make sure you are not attempting to CALL/EXECUTE/TRANSFERCALL one of the following: @SLKTABLES, @SLKCOLUMNS, @SLKQUALIFIERS, @SLKOWNERS, @SLKPROCEDURES, @SLKPROCCOLUMNS.
S6BSK037E
TIBCO Service Gateway for ODBC has not been installed
ODBC Gateway/Oracle Gateway
TIBCO Service Gateway for ODBC is a component of TIBCO Object Service Broker and has to be separately purchased and installed.
Obtain and install the Service Gateway for ODBC.
S6BSK038E
TIBCO Service Gateway for Oracle has not been installed
ODBC Gateway/Oracle Gateway
TIBCO Service Gateway for Oracle is a component of TIBCO Object Service Broker and has to be separately purchased and installed.
Obtain and install the Service Gateway for Oracle.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved