Oracle7 Server Messages

Contents Index Home Previous Next

09100-09199: Oracle Gateways

ORA-09100 target system returned following message:

Cause:A target system being accessed by an Oracle gateway returned an error that could not be handled by the gateway server. This message is followed by a second message generated by the target system or the gateway.
Action:See the documentation for the target system for an explanation of the second message.
ORA-09101 target system communication error

Cause:The gateway encountered an error when communicating with the target system. This message will generally be followed by a second message generated either by the target system or the gateway.
Action:See the documentation for the target system for an explanation of the second message.
ORA-09102 gateway internal communication error

Cause:The Oracle gateway encountered an internal error during communication with a module that is part of the gateway.
Action:Contact customer support.
ORA-09103 gateway internal protocol error

Cause:The Oracle gateway encountered an internal error during communication with an internal module.
Action:Contact customer support.
ORA-09104 gateway internal cross-communication error

Cause:The Oracle gateway encountered an internal error during communication with a module that is part of the gateway but located in a different process.
Action:Contact customer support.
ORA-09105 failed to acquire storage space in target system

Cause:For an Oracle gateway, the amount of storage available within the target system was reached. This message is followed by a second message generated by the target system.
Action:See the documentation for the target system for an explanation of the second message.
ORA-09106 target system could not obtain IO resource

Cause:The target system was unable to open a file, data set, or other resource needed to perform the I/O. This message is followed by a second message generated by the target system.
Action:See the documentation for the target system for an explanation of the second message.
ORA-09107 definition of a target system object may have changed

Cause:In an Oracle transparent gateway, an attempt was made to execute a SQL statement whose definition in the GDDL source may be out of date. The timestamp in the gateway data dictionary is different from the timestamp in the target system.
Action:Use the Transparent Gateway Administrator utility to replace the table using the revised GDDL source.
ORA-09108 invalid record in target system

Cause:The Oracle gateway or the target system noticed that the record is not valid according to its definition. This message is followed by a second message generated by the gateway or the target system depending on the error.
Action:See the gateway documentation or the documentation for the target system for an explanation of the second error message.
ORA-09109 view "view_name" cannot be used in a subquery

Cause:The view definition contains a set operator, which makes it impossible to use that view definition in a subquery. This message can occur only in SQL-based gateways.
Action:Do not use the view in a subquery.
ORA-09110 view "view_name" defines operation not supported on the target system

Cause:In a user-developed gateway, the implementor defined a view that defines an Oracle table in terms of other data source tables, and this definition contains SQL elements not supported by that system.
Action:Contact the implementor to correct the view definition error.
ORA-09111 data manipulation operation not legal on this object

Cause:In an Oracle transparent gateway, the target system rejected an insert, delete, or update operation. This message is followed by a second message generated by the target system.
Action:See the documentation for the target system for an explanation of the second message.
ORA-09112 target system check constraint violated

Cause:The values being inserted or updated do not satisfy the check constraint in the transparent gateway. This message is followed by a second message generated by the target system or the gateway.
Action:See the documentation for the target system or your Oracle7 operating system-specific documentation for an explanation of the second message.
ORA-09113 target system integrity constraint violated

Cause:The values being inserted, updated, or deleted do not satisfy the integrity constraints defined in the target system in a transparent gateway. This message is followed by a second message generated by the target system or the gateway.
Action:See the documentation for the target system or your Oracle7 operating system-specific documentation for an explanation of the second message.
ORA-09114 target system is out of memory

Cause:A target system being accessed by an Oracle gateway ran out of memory. This message is followed by a second message generated by the target system.
Action:See the documentation for the target system for an explanation of the second message.
ORA-09115 target system has timed out

Cause:A target system being accessed by an Oracle gateway timed out. This error occurs when system resource usage is too high for the request to be served in a reasonable time or when a deadlock, or some other wait condition, occurred in the target system. This message is followed by a second message generated by the target system or the gateway.
Action:See the documentation for the target system or your Oracle7 operating system-specific documentation for an explanation of the second message.
ORA-09116 definition of target system data object is inconsistent

Cause:In an Oracle transparent gateway, The target system was unable to perform the initial operations necessary to access the mapped table. The GDDL source specifies certain fields or options that are not supported for this gateway configuration.
Action:Correct the GDDL source and issue the Transparent Gateway Administrator command to CREATE OR REPLACE or DROP the table.
ORA-09117 bind-value cannot be translated into SQL text

Cause:For the SQL-based transparent gateway, the target system does not support binds, or binds are disabled using the RESOLVE_BINDS gateway initialization parameter.
Action:Enable binds or do not bind using datatypes not supported in SQL text.
ORA-09118 maximum number of savepoints exceeded

Cause:For the SQL-based transparent gateway, the target system was unable to set the savepoint because the maximum number of active savepoints was reached.
Action:Re-organize the transaction so that this limit is not reached or increase the maximum in the target system if that is possible.
ORA-09119 initialization file contains error

Cause:An Oracle gateway server encountered an error in the gateway server initialization file. This message is followed by a second message. If the second message did not follow, it can be found in the gateway log file.
Action:Refer to the second message to fix the initialization file.
ORA-09120 gateway has timed out access to target system

Cause:The Oracle Gateway request was not serviced within the specified time by the target system.
Action:See your Oracle7 operating system-specific documentation for an explanation of when this error can occur.
ORA-09121 fetch exceeds maximum number of records defined for table

Cause:The transparent gateway detected that a query will retrieve more rows than the maximum defined in the GDDL for mapped table.
Action:See your Oracle7 operating system-specific documentation for an explanation of when this error can occur.
ORA-09122 access to object "name" denied

Cause:An Oracle transparent gateway denied access to the specified object.
Action:Log in as a user with access to the object or change the access permission of the object.
ORA-09123 ROWID not found in gateway rowid cache

Cause:For the transparent gateway, the ROWID cache holds no entry that corresponds to the specified ROWID. Possibly, the ROWID entry was overwritten in the gateway ROWID cache.
Cause:Increase the size of the gateway ROWID cache by setting the value of the ROWID_CACHE_SIZE gateway initialization parameter to a higher value and restart the gateway server.
ORA-09124 in name argument name: Index out of range

Cause:The transparent gateway server detected that the index for a mapped table is bigger than allowed by the definition in the GDDL source.
Action:Modify the query or the GDDL source so that the index is in range.


Contents Index Home Previous Next