8 Event Error and Warning Messages
- GGS-EVT-STARTUP-PARAM—101
-
Cause: Issued when an unrecognized, invalid, or missing parameter is encountered during program startup.
- GGS-EVT-AUDIT-MISSING—102
-
Cause: A TMF audit trail required by Extract is unavailable. Possibly the necessary audit was purged by TMF. If the audit file exists on tape, this can occur when specifying
NORESTORE
. Retrieval of data within the specified time period may not be possible. - GGS-EVT-FILE—103
-
Cause: A Guardian file error was encountered during an operation on the file or process.
- GGS-EVT-AUDIT-READ—104
-
Cause: Issued when an error is encountered while reading a TMF audit trail. This error is generally returned under unusual circumstances.
- GGS-EVT-MEM-ALLOC—105
-
Cause: Issued due to an internal problem allocating memory.
- GGS-EVT-SPI-PROCESS—107
-
Cause: An internal problem with an SPI procedure call or a problem starting a process. This error can also occur when the Audserv program is improperly secured. To secure Audserv, issue:
> LOGON SUPER.SUPER - FUP - GIVE AUDSERV, SUPER.SUPER - SECURE AUDSERV, "NUNU", PROGID - LICENSE (AUDSERV, TMFARUL2) - EXIT
- GGS-EVT-SQL—109
-
Cause: An error was encountered during an SQL operation.
- GGS-EVT-ABEND-RECOVERY—110
-
Cause: After restarting after a process
ABEND
, Extract encountered out-of-sync data since the last successful checkpoint. ATABLE
orFILE
entry has likely been added in the Extract parameter file since the last run, or a table catalog definition has changed. - GGS-EVT-EXTRACT-FILE—112
-
Cause: An error was encountered while processing a file in the Oracle GoldenGate trail. View the message in the event file for more information.
- GGS-EVT-GROUP-DU—113
-
Cause: Another process is already running with the checkpoint group indicated in the parameter file. This problem is often caused by mistakenly running the same job twice simultaneously.
- GGS-EVT-MAXFILES—115
-
Cause: The maximum files for an was reached during Extract processing.
- GGS-EVT-AUDIT-SERVER—116
-
Cause: Extract could not communicate with an Audserv process. The Audserv process may have been mistakenly stopped.
- GGS-EVT-USER-EXIT—117
-
Cause: A logic error probably exists when a user exit routine converts data to another format.
- GGS-EVT-RMT-FILE—118
-
Cause: A file error was encountered on a remote system while writing Extract data to disk.
- GGS-EVT-REP-NEW-COLUMN-ERR—119
-
Cause: Replicat encountered an SQL error delivering an
ADD
COLUMN
statement on a target table. - GGS-EVT-WRONG-VERSION—120
-
Cause: The version of Oracle GoldenGate is incompatible with the current operating system.
- GGS-EVT-MGR-CHILD-EXISTS—122
-
Cause: The Manager child process was not stopped.
- GGS-EVT-TCPIP—150
-
Cause: A TCP/IP error occurred while attempting to write Extract data to a remote system.
- GGS-EVT-SYNC-DUPPROC-ABEND—160
-
Cause: Syncfile abended.
- GGS-EVT-EXT-ABEND—190
-
Cause: The Extract process is ending abnormally.
- GGS-EVT-REP-ABEND—191
-
Cause: The Replicat process is ending abnormally.
- GGS-EVT-MGR-ABEND—192
-
Cause: The Manager process is ending abnormally.
- GGS-EVT-SERVER-ABEND—193
-
Cause: Collector abended.
- GGS-EVT-SYNC-ABEND—194
-
Cause: Syncfile abended.
- GGS-EVT-TMF-ERROR—195
-
Cause: Error occurred during the
ENDTRANSACTION
command to TMF. - GGS-EVT-FILE-ALTER—200
-
Cause: The program encountered a
FILE
ALTER
record in the audit trail affecting one of the files designated for extraction. The exact nature of what changed about the file is impossible to determine from this message. - GGS-EVT-AUDIT-COMPRESSED—204
-
Cause: The record encountered in the audit trail is compressed and missing a required column. This column may have been used in a
MAP
WHERE
clause. The record is discarded. - GGS-EVT-NO-CONTEXT-REC—207
-
Cause: The checkpoint database is out-of-sync.
- GGS-EVT-RECORD-VERSION—208
-
Cause: The record encountered in the audit trails is out of synchronization with the current version of the SQL table. Changed data is not output because the versions are different.
- GGS-EVT-DUP-ERROR—209
-
Cause: The Manager process could not
FUP DUP
an audit trail to a backup volume. - GGS-EVT-FILE-NO-AUDIT—210
-
Cause: The file or table is not audited. For Extract, this means that data could be missing (if capturing changes from the audit trail). For Replicat, this means that replicated operations to the file or table will occur without TMF protection.
- GGS-EVT-TAPE-RESTORE-NOW—211
-
Cause: An audit dump needs to be restored from tape in order for Extract to continue processing.
- GGS-EVT-TAPE-RESTORE—212
-
Cause: At some point, the specified audit file will need to be restored from tape. This message is issued at startup so that tapes can be restored before needed, enabling faster and more reliable processing.
- GGS-EVT-FETCH-RECORD—213
-
Cause: Extract encountered a compressed update record, attempted to retrieve the entire record from the file or table and it no longer exists.
- GGS-EVT-TRANS-ABORTED—220
-
Cause: An error occurred while Replicat was executing
REPERROR
,TRANSABORT
. - GGS-EVT-MISSING-TRANS-BEGIN—221
-
Cause: Replicat cannot process the current transaction in the Extract file because the beginning of the transaction is missing. Processing resumes at the next transaction. Possibly, a previous Extract file was purged.
- GGS-EVT-MAPPING-PROBLEM—222
-
Cause: A problem was encountered while mapping a source record to a target format. Usually this means that the source record has unexpected or incorrect data in it. The record is discarded. Depending on how error handling is configured in the parameter file, the process continues, aborts the transaction, or abends. See the Replicat
REPERROR
parameter. - GGS-EVT-ROLLOVER—224
-
Cause: Extract closed a file in an sequence and opened the next one.
- GGS-EVT-PURGE-EXTRACT—226
-
Cause: The Manager process purged an Extract file that is no longer required by any Replicat processes.
- GGS-EVT-PURGE-LOG—229
-
Cause: The Manager process recycled the oldest Logger trail file to make room for new log records.
- GGS-EVT-CREATE-LOG-FAILED—230
-
Cause: GGSCI or Manager failed to create a Logger trail file. This error can be caused by not enough disk space on a volume or de-allocated space in the trail files.
- GGS-EVT-MGR-STOPPED—231
-
Cause: The Manager process stopped gracefully, as requested using GGSCI. Manager operations are critical to logging and other functions, so should be restarted within a reasonable time frame, assuming other Oracle GoldenGate operations are continuing.
- GGS-EVT-NO-UPDATE-COLUMNS—232
-
Cause: No columns are specified for update in the
MAP
statement. Typically the data source is not a NonStop source, and has bad records - GGS-EVT-ABNORMAL-STOP—233
-
Cause: The user entered a
STOP
command from GGSCI usingFORCESTOP
. - GGS-EVT-SYNC-DUP-FILESET-ERR—252
-
Cause: The Syncfile program statistics are reporting errors. The message may be similar to:
GGS WARNING 252 Syncfile errors/warnings duplicating $data02.tssparm.* to $data01.tssparm.* (total=34, excluded=0, modified=34, attempted=34, failed=15).
- GGS-EVT-SYNC-DUP-FILE-ERR—253
-
Cause: Syncfile failed to duplicate the file.
- GGS-EVT-COLL-OPEN-FILE-ERR—261
-
Cause: A file error was encountered during an open of a file by the Collector.
- GGS-EVT-COLL-IO-ERR—262
-
Cause: Collector attempted to position in a disc file after
EOF
. - GGS-EVT-REP-WAIT-CANCELLED—280
-
Cause: The user requested, through GGSCI, to cancel waiting on a file event in Replicat (negating the
WAITFILEEVENT
parameter). - GGS-EVT-REP-WAIT-CRITICAL—281
-
Cause: Replicat has been waiting a significant amount of time for a file event (such as a
RENAME
orDUP
) to occur. - GGS-EVT-PROCESSED-MARKER—300
-
Cause: An audit marker record created by GGSCI was processed by Extract or Replicat.
- GGS-EVT-USER-CMD—301
-
Cause: A command was received by the Extract or Replicat process.
- GGS-EVT-REP-STARTED—302
-
Cause: The Replicat process started.
- GGS-EVT-EXT-STARTED—303
-
Cause: The Extract process started.
- GGS-EVT-FILE-ERR-RECOVERED—304
-
Cause: A file operation that previously encountered an error was retried successfully.
- GGS-EVT-TCP-ERR-RECOVERED—305
-
Cause: A TCP/IP operation that previously encountered an error was retried successfully.
- GGS-EVT-EXT-STOP-NORMAL—306
-
Cause: Extract processing terminated normally.
- GGS-EVT-EXT-STOP-USER—307
-
Cause: Extract processing was terminated from GGSCI by a user.
- GGS-EVT-REP-STOP-NORMAL—308
-
Cause: Replicat processing terminated normally.
- GGS-EVT-REP-STOP-USER—309
-
Cause: Replicat processing was terminated from GGSCI by a user.
- GGS-EVT-MGR-PROCESS-RUNNING—310
-
Cause: The Manager process is reporting that a process is alive.
- GGS-EVT-MGR-PROCESS-DOWN-OK—311
-
Cause: The Manager process is reporting that a process terminated normally and is down. The message is marked as critical when the
DOWNCRITICAL
Manager parameter is specified. - GGS-EVT-MGR-PROCESS-ABENDED—312
-
Cause: The Manager process is reporting that a process abended.
- GGS-EVT-MGR-STARTED—313
-
Cause: The Manager process started.
- GGS-EVT-MGR-MADE-AUDIT-COPY—314
-
Cause: The Manager process made a backup copy of an audit trail file.
- GGS-EVT-MGR-PURGED-AUDIT-COPY—315
-
Cause: The Manager process purged a backup copy of an audit trail file, probably to make room for a new copy.
- GGS-EVT-MGR-AT-THRESHOLD—316
-
Cause: Manager detected that an audit trail file required by Extract is in danger of being deleted by TMF. The
PCT LEFT
indicates the amount of audit remaining before TMF purges data that Extract has not yet processed. For example, if the percent left is 20, 80 percent of audit remains to be processed. - GGS-EVT-MGR-AT-DISK-THRESHOLD—317
-
Cause: Manager detected that audit on disk that is required by Extract is in danger of being deleted by TMF. The
PCT LEFT
figure indicates the amount of audit remaining before TMF purges data that Extract has not yet processed. For example, if the percentage left is 20, 80 percent of all audit currently on disk remains to be processed. - GGS-EVT-CREATE-LOG—318
-
Cause: Manager or GGSCI created a new log file for Logger.
- GGS-EVT-MGR-LOG-THRESHOLD—319
-
Cause: Manager is reporting that a Replicat or Extract process is falling a significant amount of log files behind the current file. If this problem persists, the Replicat or Extract process is in danger of losing data it needs to process since log data is eventually recycled. The message is reported only when
LOGFILESBEHIND
orLOGFILESBEHINDINFO
is set. - GGS-EVT-MGR-RESTARTED-PROCESS—320
-
Cause: Manager is restarting a Logger, Extract or Replicat process that abended, was stopped from
TACL
, or went down for some other re-tryable reason. - GGS-EVT-MGR-LAG-THRESHOLD—321
-
Cause: Generated by Manager whenever
LAGINFO
orLAGCRITICAL
has been specified and the lag for the process exceeds the configured threshold. This message warns that a problem may exist in the system. - GGS-EVT-REP-NEW-COLUMN—330
-
Cause: Generated when Replicat replicates an
ADD
COLUMN
statement to the target database. - GGS-EVT-MGR-SLAVE—332
-
Cause: A Manager reported error originating in the slave Manager process.
- GGS-EVT-MGR-CHILD—333
-
Cause: A Manager reported error originating in a child process.
- GGS-EVT-CHILD-ADDEDEXISTING—340
-
Cause: When Manager restarts it puts out an informational message indicating that it found an existing Replicat, Extract, or synchronization process running and will track it.
- GGS-EVT-CHILD-NOTADDED—341
-
Cause: A Manager reported error when a child process cannot be added to the child table.
- GGS-EVT-NONSTOP—350
-
Cause: Errors related to NonStop processing such as start back up, takeover checkpoint errors, etc.
- GGS-EVT-CPUUP—353
-
Cause: Manager is reporting CPU recovery messages to EMS/log file for reference.
- GGS-EVT-SYNC-STARTED—360
-
Cause: Indicates Syncfile has started.
- GGS-EVT-SYNC-STOP-USER—361
-
Cause: Syncfile was stopped by the user, via GGSCI.
- GGS-EVT-COLL-OPENING-FILE—370
-
Cause: Indicates that a Collector opened a file.
- GGS-EVT-COLL-CLOSING-FILE—371
-
Cause: Indicates that a Collector closed a file.
- GGS-EVT-COLL-TERMINATING—372
-
Cause: Indicates that a Collector is terminating normally (due to Extract stopping).
- GGS-EVT-COLL-LISTENING—373
-
Cause: Indicates that a Collector has been started and is waiting for incoming requests.
- GGS-EVT-REP-WAIT-FEVENT—380
-
Cause: Signals that Replicat is waiting on a file event such as
RENAME
orDUP
to occur against a specific file. Replicat suspends processing until the event has completed or been cancelled through GGSCI. - GGS-EVT-REP-WAIT-COMPLETED—381
-
Cause: Signals that a file event on which Replicat was waiting completed, and that Replicat will resume processing other transactions.
- GGS-EVT-OPENED-SOURCE-FILE—382
-
Cause: Issued by Extract when it opens a file that is not an Oracle GoldenGate trail or Logger trail file.
- GGS-EVT-CLOSED-SOURCE-FILE—383
-
Cause: Issued by Extract when it closes a file that is not an Oracle GoldenGate trail.
- GGS-EVT-GROUPLIST—384
-
Cause: Manager has filled its internal table of checkpoint groups and produced the error messaging:
*ERROR* group_list table limit reached
. - GGS-EVT-TASK—385
-
Cause: Indicates there are messages from an Extract or Replicat task.
- GGS-EVT-CHKPT-REC-DELETED—386
-
Cause: Result from a GGSCI
CLEANUP
command. - GGS-EVT--POS—387
-
Cause: Indicates if Extract and/or Replicat are started after a specified begin time. Message can be informational, if records are available to use for positioning, or a warning, if records are not available.
- GGS-EVT-CHKPT-REC-CORRUPT—389
-
Cause:
RESTARTCHECKPOINTS
checkpoint metadata is no longer valid. See the error detail in the message for more detail. - OGG ERROR TACLCMD—392
-
Cause: Invalid or missing input or error on attempted execution of the
TACLCMD
statement. See the data returned with the error for more information. - XR-FILE-ERR—500
-
Cause: This is an internal error code returned from the module that reads Oracle GoldenGate trails and does direct reads on user data files.
- XR-LOGIC-ERROR—514
-
Cause: Extract received an unexpected reply code from Replicat during direct load and generates the message:
Invalid reply code received
. - GGS-EVT-LOGR-FILE-ERR—1000
-
Cause: Logger experienced a Guardian file error. Message text describes exact problem.
- GGS-EVT-LOGR-SHUTDOWN-RQST—1008
-
Cause: Logger received a shutdown request from GGSCI.
- GGS-EVT-LOGR-SHUTDOWN-COMPLETE—1009
-
Cause: Logger completed a shutdown request from GGSCI.
- GGS-EVT-LOGR-ABEND—1010
-
Cause: Logger abended for reasons provided in another error message.
- GGS-EVT-LOGR-STARTED—1011
-
Cause: Logger startup message.
- WRN-FILTER-NOT-PASSED—1280
-
Cause: Replicat issues a warning that a filter did not pass the evaluation test for a record. This error may also generate other associated messages.
- GGS-EVT-POOL-CREATE-ERR—1500
-
Cause: Memory allocation problems.
- GGS-EVT-LOGR-LOGCONF-ERR—1600
-
Cause: The
LOGCONF
file may have been purged from configuration. - GGS-EVT-LOGR-TRAIL-OPEN—1800
-
Cause: Logger opened the next log file in the log trail.
- GGS-EVT-LOGR-TRAIL-SWITCH—1801
-
Cause: Logger will open the next log file in the log trail by request.
- GGS-EVT-LOGR-LOGGING-DISABLED—1802
-
Cause: Logger disabled logging by request.
- GGS-EVT-LOGR-LOGGING-ENABLED—1803
-
Cause: Logger enabled logging by request.
- GGS-EVT-INTERCEPT-NOTBOUND—2000
-
Cause: An application that opens a non-audited file for update access does not have the Oracle GoldenGate intercept library bound to it.
- ECONNABORTED—4119
-
Cause: A connection was closed by the internal software on your host computer.
- ECONNREFUSED—4127
-
Cause: The connect call failed because the remote host rejected the connection request. This error usually results from an attempt to connect to a service that is inactive on the remote host.
- ECONNRESET—4120
-
Cause: The connect call failed because the peer process reset the connection before the operation completed.
- ENETDOWN—4116
-
Cause: The call failed because the operation encountered a down network.
- ENETRESET—4118
-
Cause: The call failed, and all connections to the specified remote host were closed. The network dropped connection because of reset. The host you were connected to crashed and rebooted.
- ENOTCONN—4123
-
Cause: The call failed because the specified socket was not connected.
- EPIPE—4032
-
Cause: The call failed because a write or send call was attempted on a local socket that had been previously closed with the shutdown call.
- ESHUTDOWN—4124
-
Cause: The call failed because the specified socket was already shut down.
- ETIMEDOUT—4126
-
Cause: The connection timed out before the operation completed. The call failed.