9 Event Error and Warning Messages

This chapter lists the cause and recommended action for error and warning messages generated by Oracle GoldenGate for HP NonStop on the Guardian platform.

GGS-EVT-STARTUP-PARAM—101: Cause: Issued when an unrecognized, invalid, or missing parameter is encountered during program startup.; Action: Correct the parameter file (the process IN file) and restart.

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.

Action: Examine the error message for more details. If NORESTORE was specified in the parameter file, and the missing file is on tape, consider eliminating this parameter. If the audit cannot be located either on disk or tape, other means of data extraction will be required for the given time period.

Tokens:

GGS-TKN-AUDIT-FILE

GGS-EVT-FILE—103

Cause: A Guardian file error was encountered during an operation on the file or process.

Action: Examine the Guardian error number to determine the exact nature of the error. Attempt to correct the error. In some instances, errors are automatically retried if corrected within a short period of time.

Tokens:

GGS-TKN-FILE 
GGS-TKN-GUARDIAN-ERR

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.

Action: Examine the audit error code. A -900, may indicate a problem restoring the tape (the restore may not have completed). If a FILEINFO on the restored audit trail indicates ?, refer to SNOOP documentation to turn the corrupt flag off. Restart if necessary. If the problem persists, contact Oracle GoldenGate Support.

Tokens:

GGS-TKN-AUDIT-FILE 
GGS-TKN-AR-ERR

GGS-EVT-MEM-ALLOC—105: Cause: Issued due to an internal problem allocating memory.; Action: Restart the program. If the problem persists, contact Oracle GoldenGate.

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

Action: Note error message and contact Oracle GoldenGate. If the problem is starting a TMFSERVE process, it may be necessary to FUP LICENSE TMFSERVE.

Tokens:

GGS-TKN-FILE (optional) 
GGS-TKN-GUARDIAN-ERR (optional)

GGS-EVT-SQL—109: Cause: An error was encountered during an SQL operation.; Action: Dependent on the type of error. If the error occurred during a replicated operation, error detail can be found in the Replicat discard file.

GGS-EVT-ABEND-RECOVERY—110: Cause: After restarting after a process ABEND, Extract encountered out-of-sync data since the last successful checkpoint. A TABLE or FILE entry has likely been added in the Extract parameter file since the last run, or a table catalog definition has changed.; Action: After an ABEND, the parameter file must be exactly the same as during the prior run. Restore the parameter file to its prior state. Otherwise, resetting checkpoints (using GGSCI) may be required (review the situation carefully before doing so).

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.; Action: Recovery depends on the error message. If this is a file error (such as a security violation), correct the problem and restart the process.

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.; Action: If the name of the Extract or Replicat parameter is incorrect, fix it. Otherwise, no recovery required.

GGS-EVT-MAXFILES—115

Cause: The maximum files for an EXTTRAIL was reached during Extract processing.

Action: Dependent on the situation. Possibilities include renaming or purging the oldest EXTTRAIL files, or increasing the MAXFILES option of the EXTTRAIL parameter using the GGSCI program. After taking one of these actions, restart the Extract program.

Tokens:

GGS-TKN-FILE

GGS-EVT-AUDIT-SERVER—116: Cause: Extract could not communicate with an Audserv process. The Audserv process may have been mistakenly stopped.; Action: Restart the Extract program. If the problem persists, contact Oracle Support.

GGS-EVT-USER-EXIT—117: Cause: A logic error probably exists when a user exit routine converts data to another format.; Action: Correct the application logic and rebind the user exit.

GGS-EVT-RMT-FILE—118

Cause: A file error was encountered on a remote system while writing Extract data to disk.

Action: Correct the problem and restart the program.

Tokens:

GGS-TKN-RMT-FILE

GGS-EVT-REP-NEW-COLUMN-ERR—119

Cause: Replicat encountered an SQL error delivering an ADD COLUMN statement on a target table.

Action: Correct the problem and restart Replicat.

Tokens:

GGS-TKN-FILE 
GGS-TKN-SQL-ERR 
GGS-TKN-GUARDIAN-ERR

GGS-EVT-WRONG-VERSION—120: Cause: The version of Oracle GoldenGate is incompatible with the current operating system.; Action: Install the correct version of Oracle GoldenGate.

GGS-EVT-MGR-CHILD-EXISTS—122: Cause: The Manager child process was not stopped.; Action: This is usually a warning message, but if this is a irrecoverable error, examine the error message to determine the exact nature of the error (such a security violation). Attempt to correct the error.

GGS-EVT-TCPIP—150

Cause: A TCP/IP error occurred while attempting to write Extract data to a remote system.

Action: If the error is "Connection Refused," start an Extract Collector process on the remote system. Also, check the RMTHOST and PORT parameters to make sure they match the Collector startup parameters. TCP/IP errors are frequently retried automatically for a period of time. For more information see TCPIPSWTICHERRS on "TCPIPSWITCHERRS".

Tokens:

GGS-TKN-RMT-HOST 
GGS-TKN-TCP-PORT 
GGS-TKN-TCP-ERR

GGS-EVT-SYNC-DUPPROC-ABEND—160: Cause: Syncfile abended.; Action: Examine the error message to determine the exact nature of the error. Attempt to correct the error.

GGS-EVT-EXT-ABEND—190: Cause: The Extract process is ending abnormally.; Action: Examine the previous error messages and the Extract report file to determine the exact cause.

GGS-EVT-REP-ABEND—191: Cause: The Replicat process is ending abnormally.; Action: Examine the previous error messages and the Replicat report file to determine the exact cause.

GGS-EVT-MGR-ABEND—192: Cause: The Manager process is ending abnormally.; Action: Examine the previous error messages in the log in order to determine the exact cause.

GGS-EVT-SERVER-ABEND—193: Cause: Collector abended.; Action: Examine the error message to determine the exact nature of the error. Attempt to correct the error.

GGS-EVT-SYNC-ABEND—194: Cause: Syncfile abended.; Action: Examine the error message to determine the exact nature of the error. Attempt to correct the error.

GGS-EVT-TMF-ERROR—195: Cause: Error occurred during the ENDTRANSACTION command to TMF.; Action: Examine the error message to determine the exact nature of the error. Attempt to correct the error. Contact Oracle GoldenGate Support if necessary.

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.

Action: If an extracted file or table definition was changed before all related audit was processed, you may need to re-synchronize data. If audit was turned off in the table or file, it is possible that updates to the table are not extracted. This message can also occur when changes that are not critical to extract are encountered.

Tokens:

GGS-TKN-FILE

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.

Action: Examine the compressed image in the discard file. The recovery is application-dependent.

Tokens:

GGS-TKN-FILE

GGS-EVT-NO-CONTEXT-REC—207: Cause: The checkpoint database is out-of-sync.; Action: Contact Oracle GoldenGate.

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.

Action: Manual re-synchronization (such as reload) may be required.

Tokens:

GGS-TKN-FILE

GGS-EVT-DUP-ERROR—209: Cause: The Manager process could not FUP DUP an audit trail to a backup volume.; Action: Free up disk space or specify a different ALTLOC option in the GGSCI ADD ATCONFIG command.

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.

Action: Use FUP or SQLCI to turn audit on the file or table. Data may be missing, if so, other means of data extract and replication may be required. There can also be legitimate reasons for temporarily turning audit off.

Tokens:

GGS-TKN-FILE

GGS-EVT-TAPE-RESTORE-NOW—211

Cause: An audit dump needs to be restored from tape in order for Extract to continue processing.

Action: Follow the instructions (displayed by SNOOP) on the operator console for restoring the tape.

Tokens:

GGS-TKN-AUDIT-FILE

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.

Action: None.

Tokens:

GGS-TKN-AUDIT-FILE

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.; Action: This is generally a tolerable condition that occurs when an update to a database record is followed by a delete.

GGS-EVT-TRANS-ABORTED—220: Cause: An error occurred while Replicat was executing REPERROR, TRANSABORT.; Action: Examine the error message to determine the exact nature of the error. Attempt to correct the error.

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.; Action: Examine the discard file for the rejected data and use manual procedures to recover the data.

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.

Action: Examine the discard record to determine what may have caused the mapping problem. Use manual procedures to extract or replicate the necessary data, or alter the mapping specification and restart.

Tokens:

GGS-TKN-SRC-FILE 
GGS-TKN-DST-FILE

GGS-EVT-ROLLOVER—224

Cause: Extract closed a file in an EXTTRAIL sequence and opened the next one.

Action: If this message is highlighted, take action before the next rollover to ensure that Extract processing continues smoothly. The oldest file in the sequence will need to be renamed or purged (use caution).

Tokens:

GGS-TKN-FILE

GGS-EVT-PURGE-EXTRACT—226

Cause: The Manager process purged an Extract file that is no longer required by any Replicat processes.

Action: None required. Informational.

Tokens:

GGS-TKN-FILE

GGS-EVT-PURGE-LOG—229

Cause: The Manager process recycled the oldest Logger trail file to make room for new log records.

Action: None required. Informational.

Tokens:

GGS-TKN-LOG-FILE

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.

Action: This error is critical. To avoid it, do not deallocate unused extents in the Logger trail files. Log file space is pre-allocated to ensure availability when needed. Also, try purging other files in the system to make room for the newest log files. Reconfigure LOG space to use smaller extent sizes.

Tokens:

GGS-TKN-LOG-FILE 
GGS-TKN-GUARDIAN-ERR

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.; Action: None required. Informational.

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; Action: Check the remote Extract parameter file and TRANDATA for primary key logging.

GGS-EVT-ABNORMAL-STOP—233: Cause: The user entered a STOP command from GGSCI using FORCESTOP.; Action: Information only.

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).

Action: Warning only.

GGS-EVT-SYNC-DUP-FILE-ERR—253: Cause: Syncfile failed to duplicate the file.; Action: Warning. Make sure the file is available or named correctly. Re-run Syncfile if necessary.

GGS-EVT-COLL-OPEN-FILE-ERR—261: Cause: A file error was encountered during an open of a file by the Collector.; Action: Examine the error number to determine the exact nature of the error (for example, a security violation or disk is full). Attempt to correct the error and restart Extract on the source system.

GGS-EVT-COLL-IO-ERR—262: Cause: Collector attempted to position in a disc file after EOF.; Action: Extract will try to re-send the data. If the problem continues Extract abends and re-starts. If Extract exceeds the maximum restarts and the problem remains, delete the Extract and Replicat processes and re-add them.

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).; Action: None. Used to trace processing activity.

GGS-EVT-REP-WAIT-CRITICAL—281: Cause: Replicat has been waiting a significant amount of time for a file event (such as a RENAME or DUP) to occur.; Action: Waiting for a file event holds up Replicat processing. You can cancel the wait using the SEND REPLICAT group_name, BYPASSFILEEVENT GGSCI command. Deciding to cancel a wait is an application-specific issue and should be considered carefully.

GGS-EVT-PROCESSED-MARKER—300: Cause: An audit marker record created by GGSCI was processed by Extract or Replicat.; Action: None. Markers are used to mark application-specific points of interest within the audit trails. See discussions of markers elsewhere in this manual for more information.

GGS-EVT-USER-CMD—301: Cause: A command was received by the Extract or Replicat process.; Action: None. Used to trace processing activity.

GGS-EVT-REP-STARTED—302: Cause: The Replicat process started.; Action: None. Used to trace processing activity.

GGS-EVT-EXT-STARTED—303: Cause: The Extract process started.; Action: None. Used to trace processing activity.

GGS-EVT-FILE-ERR-RECOVERED—304

Cause: A file operation that previously encountered an error was retried successfully.

Action: None. Indicates that processing has resumed normally after problem correction.

Tokens:

GGS-TKN-FILE

GGS-EVT-TCP-ERR-RECOVERED—305

Cause: A TCP/IP operation that previously encountered an error was retried successfully.

Action: None. Indicates that processing has resumed normally after problem correction.

Tokens:

GGS-TKN-RMT-HOST 
GGS-TKN-TCP-PORT

GGS-EVT-EXT-STOP-NORMAL—306: Cause: Extract processing terminated normally.; Action: None. Used to trace processing activity.

GGS-EVT-EXT-STOP-USER—307: Cause: Extract processing was terminated from GGSCI by a user.; Action: None. Used to trace processing activity.

GGS-EVT-REP-STOP-NORMAL—308: Cause: Replicat processing terminated normally.; Action: None. Used to trace processing activity.

GGS-EVT-REP-STOP-USER—309: Cause: Replicat processing was terminated from GGSCI by a user.; Action: None. Used to trace processing activity.

GGS-EVT-MGR-PROCESS-RUNNING—310: Cause: The Manager process is reporting that a process is alive.; Action: None. Used to trace processing activity.

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.; Action: If this message is highlighted, restarting the process may be required. Otherwise no recovery action necessary.

GGS-EVT-MGR-PROCESS-ABENDED—312: Cause: The Manager process is reporting that a process abended.; Action: Investigate the reason for the abend, fix the problem and restart the program.

GGS-EVT-MGR-STARTED—313: Cause: The Manager process started.; Action: None. Used to trace processing activity.

GGS-EVT-MGR-MADE-AUDIT-COPY—314

Cause: The Manager process made a backup copy of an audit trail file.

Action: None. Informational.

Tokens:

GGS-TKN-AUDIT-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.

Action: None. Informational.

Tokens:

GGS-TKN-AUDIT-FILE

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.

Action: If Extract is down, start it. Otherwise, consider increasing priority for the Extract and Audserv processes.

Tokens:

GGS-TKN-AUDIT-FILE 
GGS-TKN-AT-PCT

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.

Action: If Extract is down, start it. Otherwise, consider increasing priority for the Extract and Audserv processes. Extract will request a tape restore if an audit dump is available.

Tokens:

GGS-TKN-AUDIT-FILE 
GGS-TKN-AT-DISK-PCT

GGS-EVT-CREATE-LOG—318

Cause: Manager or GGSCI created a new log file for Logger.

Action: None required. Informational.

Tokens:

GGS-TKN-LOG-FILE

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 or LOGFILESBEHINDINFO is set.

Action: Boost the priority of the Replicat or Extract process that is falling behind to let it catch up. You may also want to increase the NUMFILES parameter in the LOGPARM file, then use GGSCI ALTER LOGGER to increase the amount of available log space.

Tokens:

GGS-TKN-LOG-FILE 
GGS-TKN-FILES-BEHIND 
GGS-TKN-GROUP

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.

Action: None required. Informational.

Tokens:

GGS-TKN-GROUP

GGS-EVT-MGR-LAG-THRESHOLD—321: Cause: Generated by Manager whenever LAGINFO or LAGCRITICAL has been specified and the lag for the process exceeds the configured threshold. This message warns that a problem may exist in the system.; Action: Investigate possible performance problems (such as process running at low priority, or a faulty network).

GGS-EVT-REP-NEW-COLUMN—330: Cause: Generated when Replicat replicates an ADD COLUMN statement to the target database.; Action: None. Used to trace processing activity.

GGS-EVT-MGR-SLAVE—332: Cause: A Manager reported error originating in the slave Manager process.; Action: None. Used to trace processing activity.

GGS-EVT-MGR-CHILD—333: Cause: A Manager reported error originating in a child process.; Action: None. Used to trace processing activity.

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.; Action: None. Used to trace processing activity.

GGS-EVT-CHILD-NOTADDED—341: Cause: A Manager reported error when a child process cannot be added to the child table.; Action: None. Used to trace processing activity.

GGS-EVT-NONSTOP—350: Cause: Errors related to NonStop processing such as start back up, takeover checkpoint errors, etc.; Action: None. Used to trace processing activity.

GGS-EVT-CPUUP—353: Cause: Manager is reporting CPU recovery messages to EMS/log file for reference.; Action: None. Information only.

GGS-EVT-SYNC-STARTED—360: Cause: Indicates Syncfile has started.; Action: None. Informational only.

GGS-EVT-SYNC-STOP-USER—361: Cause: Syncfile was stopped by the user, via GGSCI.; Action: None. Information only.

GGS-EVT-COLL-OPENING-FILE—370: Cause: Indicates that a Collector opened a file.; Action: None. Used to trace processing activity.

GGS-EVT-COLL-CLOSING-FILE—371: Cause: Indicates that a Collector closed a file.; Action: None. Used to trace processing activity.

GGS-EVT-COLL-TERMINATING—372: Cause: Indicates that a Collector is terminating normally (due to Extract stopping).; Action: None. Used to trace processing activity.

GGS-EVT-COLL-LISTENING—373: Cause: Indicates that a Collector has been started and is waiting for incoming requests.; Action: None. Used to trace processing activity.

GGS-EVT-REP-WAIT-FEVENT—380: Cause: Signals that Replicat is waiting on a file event such as RENAME or DUP to occur against a specific file. Replicat suspends processing until the event has completed or been cancelled through GGSCI.; Action: None. Used to trace processing activity.

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.; Action: None. Used to trace processing activity.

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.; Action: None. Used to trace processing activity.

GGS-EVT-CLOSED-SOURCE-FILE—383: Cause: Issued by Extract when it closes a file that is not an Oracle GoldenGate trail.; Action: None. Used to trace processing activity.

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.

Action: Stop and re-start Manager. If the problem continues, you have reached the maximum number of groups, which is 200.

GGS-EVT-TASK—385: Cause: Indicates there are messages from an Extract or Replicat task.; Action: None. Informational only.

GGS-EVT-CHKPT-REC-DELETED—386: Cause: Result from a GGSCI CLEANUP command.; Action: None. Informational only.

GGS-EVT-EXTTRAIL-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.

Action: None. Informational only.

Informational:

GGS INGO 387 Positioning for Begin time search, using \NODE.$VOL.SUBVOL.AA000001.

Warning:

GGS WARNING 387 No data found in exttrail/logtrail for Begin time search, using \NODE.$VOL.SUBVOL.AA00009.

GGS-EVT-CHKPT-REC-CORRUPT—389: Cause: RESTARTCHECKPOINTS checkpoint metadata is no longer valid. See the error detail in the message for more detail.; Action: Correct the issue or delete the Extract group and re-add it.

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.; Action: XXXXX_NO_ACTION_or_"RECOVERY"_TEXT

XR-LOGIC-ERROR—514

Cause: Extract received an unexpected reply code from Replicat during direct load and generates the message:

Invalid reply code received.

Action: Examine the error message to determine the exact nature of the error.

GGS-EVT-LOGR-FILE-ERR—1000: Cause: Logger experienced a Guardian file error. Message text describes exact problem.; Action: Fix error and restart Logger. Resynchronization may be required.

GGS-EVT-LOGR-SHUTDOWN-RQST—1008: Cause: Logger received a shutdown request from GGSCI.; Action: None required. Informational.

GGS-EVT-LOGR-SHUTDOWN-COMPLETE—1009: Cause: Logger completed a shutdown request from GGSCI.; Action: None required. Informational.

GGS-EVT-LOGR-ABEND—1010: Cause: Logger abended for reasons provided in another error message.; Action: Manager may restart Logger in this situation depending on the reason Logger abended. Recovery depends on the conditions that caused Logger to abend.

GGS-EVT-LOGR-STARTED—1011: Cause: Logger startup message.; Action: None required. Informational.

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.; Action: Examine the FILTER clauses in the Replicat parameter file. Also examine the REPERROR parameter.

GGS-EVT-POOL-CREATE-ERR—1500: Cause: Memory allocation problems.; Action: Contact Oracle GoldenGate Support.

GGS-EVT-LOGR-LOGCONF-ERR—1600: Cause: The LOGCONF file may have been purged from configuration.; Action: Contact Oracle Support.

GGS-EVT-LOGR-TRAIL-OPEN—1800: Cause: Logger opened the next log file in the log trail.; Action: None required. Informational.

GGS-EVT-LOGR-TRAIL-SWITCH—1801: Cause: Logger will open the next log file in the log trail by request.; Action: None required. Informational.

GGS-EVT-LOGR-LOGGING-DISABLED—1802: Cause: Logger disabled logging by request.; Action: None required. Informational.

GGS-EVT-LOGR-LOGGING-ENABLED—1803: Cause: Logger enabled logging by request.; Action: None required. Informational.

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.; Action: Bind the Oracle GoldenGate intercept library to the application.

ECONNABORTED—4119: Cause: A connection was closed by the internal software on your host computer.; Action: Close the socket. Reestablish the connection using the socket, bind, and connect calls. If the problem persists, contact your Tandem representative.

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.; Action: Start the server on the remote host. Close the local socket. Reestablish the connection using the socket, bind, and connect calls.

ECONNRESET—4120: Cause: The connect call failed because the peer process reset the connection before the operation completed.; Action: Close the local socket. Reestablish the connection using the socket, bind, and connect calls.

ENETDOWN—4116: Cause: The call failed because the operation encountered a down network.; Action: Contact the network Manager.

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.; Action: Close the sockets using the close call. Reestablish the connections using the socket, bind, connect, and accept calls; then retry the call.

ENOTCONN—4123: Cause: The call failed because the specified socket was not connected.; Action: Ensure that the socket is connected, then retry the operation.

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.; Action: Reestablish the connection using the socket, bind, and connect calls. Retry the write or send call.

ESHUTDOWN—4124: Cause: The call failed because the specified socket was already shut down.; Action: Reopen the remote socket using the open, bind, and accept calls. Re-establish the connection, if desired, with a call to connect or connect_nw.

ETIMEDOUT—4126: Cause: The connection timed out before the operation completed. The call failed.; Action: Close the local socket. Rebuild the local socket using the socket and bind calls. Call connect or connect_nw to reestablish the connection.