![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
DBSource % in the definition of % does not match the gateway's TRXDB %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.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.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.Failed to initialize the gateway's Fail Safe DBSource %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.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.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.The versions of the DB and binary components do not match: % and % respectivelyThe 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.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.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.GET (as opposed to FORALL) request on reserved table %: %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.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.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.An invalid attempt was made to modify data.Make sure this table is not modified by the application.While performing a FORALL on the table, the gateway has lost its cursor position.This situation indicates possible memory corruption. Contact TIBCO Support.Unable to create an additional statement context: %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.Invalid HANDLE field value in WHERE clause: stored proc result set %: %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.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.DBSource or TableName missing at runtime (table %): %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.While processing a request to the table, an invalid WHERE clause was detected.Review your WHERE clause and make sure it is correct.Invalid field mapping or data corrupted/truncated (field %, table %) : %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.No HANDLE field reference in WHERE clause: stored proc result set %: %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@.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.Illegal attempt to execute a catalog function (table %): %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.TIBCO Service Gateway for ODBC has not been installedTIBCO 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.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 |