GoldenGate fault Summary

User does not have Problem description: 2013-05-0210: 45: 20GGSERROR2001OracleGoldenGateDeliveryforOracle, rcrmheal. prm:

User does not have Problem description: 10:45:20 ggs error 2001 Oracle GoldenGate Delivery for Oracle, rcrmheal. prm:

User does not exist

Problem description:

10:45:20 ggs error 2001 Oracle GoldenGate Delivery for Oracle, rcrmheal. prm: Fatal error executing DDL replication: error [Error code [1918], ORA-01918: user 'pxboracle 'does not exist, SQL/* GOLDENGATE_DDL_REPLICATION */alter user pxboracle account unlock], no error handler present.

Problem Analysis:

According to the analysis log, it can be determined that the target end does not have the fault caused by this user.

Troubleshooting:

Method 1. If you do not need to synchronize the user, remove the ing user from the target end and restart the process.

For example, remove: MAP pxboracle. *, TARGET tpxboracle .*;

Method 2: manually create the user on the target end and restart the process.

The table does not exist.

Problem description:

15:02:12 ggs error 101 Oracle GoldenGate Delivery for Oracle, rcrmheal. prm: Table PXBORACLE. TB_USERS does not exist in target database.

Problem Analysis:

According to the analysis log, it can be determined that the table does not exist on the target end.

Troubleshooting:

Method 1: If you do not need to synchronize the table, you can exclude it from the target end and restart the process.

For example, mapexclude pxboracle. TB_USERS

Method 2: manually create the table on the target end. heterogeneous databases also need to regenerate the table structure definition file and restart the process.

Database index failure

Problem description

14:48:32 ggs warning 218 Oracle GoldenGate Delivery for Oracle, rapcaxht. prm: SQL error 1502 mapping TSM. DOCONTRACT to TTSM. docontract oci Error ORA-01502: index TSM. PK_SID 'or partition of such index is in unusable status (status = 1502), SQL .

Problem Analysis:

Database index failure.

Troubleshooting:

Rebuild the problematic index, restart the process, and troubleshoot the problem.

Inconsistent table structure

Problem description:

14:50:44 ggs error 218 Oracle GoldenGate Delivery for Oracle, rcrmheal. prm: Error mapping from OLAP. TB_FT_OFSTK_BAL_HIS to CRMOLAP. TB_FT_OFSTK_BAL_HIS.

Problem Analysis:

This problem occurs generally because the synchronization source and target table structures are inconsistent, including table fields and indexes.

Troubleshooting:

1. If the table fields are inconsistent, You need to modify the table fields. heterogeneous databases also need to regenerate the table structure definition file and restart the process.

2. If the index is inconsistent, you need to re-create the index. heterogeneous databases also need to re-generate the table structure definition file and restart the process.

Insufficient disk space

Problem description:

04:05:31 ggs error 103 Oracle GoldenGate Collector: Unable to write to file "./dirdat/crm/fl003629" (error 28, No space left on device ).

04:05:31 ggs error 190 process abending.

Problem Analysis:

Based on the analysis log, it can be determined that the fault is caused by insufficient disk space.

Troubleshooting:

Divide enough disk space and restart the process.

TCP/IP fault

Problem description:

21:06:04 ggs warning 150 Oracle GoldenGate Capture for Oracle, BSAIAXEC. prm: TCP/IP error 10060 .).

Problem Analysis:

According to the analysis log, it can be determined that the remote host cannot be connected, including the IP address or port number.

Troubleshooting:

Connect to the IP address and port of the remote host and restart the process.

The database cannot be connected.

Problem description:

18:25:13 ggs error 182 Oracle GoldenGate Delivery for Oracle, rtasaxta. prm: OCI Error during OCIServerAttach (status = 12154-ORA-12154: TNS: cocould not resolve the connect identifier specified ).

Problem Analysis:

This fault is caused by a goldengate process exception because the database cannot be connected.

Troubleshooting:

You need to solve the database exception before restarting the process.

Insufficient tablespace

Problem description: