A19483 2

[ Pobierz całość w formacie PDF ]
.This message can occur only in SQL basedgateways.Action Do not use the view in a subquery.ORA 09110 view view_name defines operation not supported on the target systemCause In a user developed gateway, the implementor defined a view that defines anOracle table in terms of other data source tables, and this definition containsSQL 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 objectCause In an Oracle transparent gateway, the target system rejected an insert, delete, orupdate operation.This message is followed by a second message generated bythe target system.Action See the documentation for the target system for an explanation of thesecond message.ORA 09112 target system check constraint violatedCause The values being inserted or updated do not satisfy the check constraint in thetransparent gateway.This message is followed by a second message generatedby the target system or the gateway.Action See the documentation for the target system or your Oracle7 operatingsystem specific documentation for an explanation of the second message.ORA 09113 target system integrity constraint violatedCause The values being inserted, updated, or deleted do not satisfy the integrityconstraints defined in the target system in a transparent gateway.This messageis followed by a second message generated by the target system or the gateway.Action See the documentation for the target system or your Oracle7 operatingsystem specific documentation for an explanation of the second message.Oracle7 Server Messages 2 29909100 09199: Oracle GatewaysORA 09114 target system is out of memoryCause A target system being accessed by an Oracle gateway ran out of memory.Thismessage is followed by a second message generated by the target system.Action See the documentation for the target system for an explanation of thesecond message.ORA 09115 target system has timed outCause A target system being accessed by an Oracle gateway timed out.This erroroccurs when system resource usage is too high for the request to be served in areasonable time or when a deadlock, or some other wait condition, occurred inthe target system.This message is followed by a second message generated bythe target system or the gateway.Action See the documentation for the target system or your Oracle7 operatingsystem specific documentation for an explanation of the second message.ORA 09116 definition of target system data object is inconsistentCause In an Oracle transparent gateway, The target system was unable to perform theinitial operations necessary to access the mapped table.The GDDL sourcespecifies certain fields or options that are not supported for this gatewayconfiguration.Action Correct the GDDL source and issue the Transparent Gateway Administratorcommand to CREATE OR REPLACE or DROP the table.ORA 09117 bind value cannot be translated into SQL textCause For the SQL based transparent gateway, the target system does not supportbinds, or binds are disabled using the RESOLVE_BINDS gateway initializationparameter.Action Enable binds or do not bind using datatypes not supported in SQL text.ORA 09118 maximum number of savepoints exceededCause For the SQL based transparent gateway, the target system was unable to set thesavepoint because the maximum number of active savepoints was reached.Action Re organize the transaction so that this limit is not reached or increase themaximum in the target system if that is possible.2 300 Oracle7 Server Messages09100 09199: Oracle GatewaysORA 09119 initialization file contains errorCause An Oracle gateway server encountered an error in the gateway serverinitialization file.This message is followed by a second message.If the secondmessage 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 systemCause The Oracle Gateway request was not serviced within the specified time by thetarget system.Action See your Oracle7 operating system specific documentation for an explanationof when this error can occur.ORA 09121 fetch exceeds maximum number of records defined for tableCause The transparent gateway detected that a query will retrieve more rows than themaximum defined in the GDDL for mapped table.Action See your Oracle7 operating system specific documentation for an explanationof when this error can occur.ORA 09122 access to object name deniedCause 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 ofthe object.ORA 09123 ROWID not found in gateway rowid cacheCause For the transparent gateway, the ROWID cache holds no entry that correspondsto the specified ROWID.Possibly, the ROWID entry was overwritten in thegateway ROWID cache.Cause Increase the size of the gateway ROWID cache by setting the value of theROWID_CACHE_SIZE gateway initialization parameter to a higher value andrestart the gateway server.ORA 09124 in name argument name: Index out of rangeCause The transparent gateway server detected that the index for a mapped table isbigger than allowed by the definition in the GDDL source.Action Modify the query or the GDDL source so that the index is in range.Oracle7 Server Messages 2 30109200 09499: DOS, OS/2, and Novell09200 09499: DOS, OS/2, and NovellSee your operating system specific Oracle documentation.For a listing of otherOracle manuals containing operating system specific messages, see RelatedPublications in the Preface.09500 09699: MPE/XLSee your operating system specific Oracle documentation.For a listing of otherOracle manuals containing operating system specific messages, see RelatedPublications in the Preface.09700 09999: UNIXSee your operating system specific Oracle documentation.For a listing of otherOracle manuals containing operating system specific messages, see RelatedPublications in the Preface.10000 10999: Internal11000 11999: SQL*Net MVSSee your operating system specific Oracle documentation.For a listing of otherOracle manuals containing operating system specific messages, see RelatedPublications in the Preface.2 302 Oracle7 Server Messages12000 12014: Table Snapshots12000 12014: Table SnapshotsThis section lists messages generated when table snapshots are accessed.ORA 12000 a snapshot log already exists on table nameCause An attempt was made to create a snapshot log on a table that already has asnapshot log.Each master table can have only one snapshot log.Action All snapshots on a table can use the same snapshot log for that table.To makechanges to the existing log, use the ALTER SNAPSHOT LOG command ordrop the snapshot log and create it again.ORA 12001 cannot create log: table name already has a triggerCause An attempt was made to create a snapshot log on a table when the tablealready had an AFTER ROW trigger.Snapshot logs are filled by an AFTERROW trigger on the master table, so the trigger cannot be created.Action If it is necessary to create a snapshot log, drop the current trigger on themaster table [ Pobierz całość w formacie PDF ]