About the OracleGoldenGate parameter TRANLOGOPTIONSaltarchivelogdest

Our production system uses Oracle cluster software to achieve high availability of OGG. When an instance in the cluster goes down, OGG automatically restarts after abend. Strictly speaking, this high-availability setting

Our production system uses Oracle cluster software to achieve high availability of OGG. When an instance in the cluster goes down, OGG automatically restarts after abend. Strictly speaking, this high-availability setting

Our production system uses Oracle cluster software to achieve high availability of OGG. When an instance in the cluster goes down, OGG automatically restarts after abend. Strictly speaking, this high Availability design is also relative, because it cannot avoid unexpected interruptions of the OGG process when the node goes down. However, after vip and OGG are associated, OGG can automatically restart and continue to work within 30 seconds after unexpected interruptions.

In highly available configurations, you must note the following parameter: TRANLOGOPTIONS altarchivelogdest. The consequence of improper use of this parameter is that OGG remains abend until the instance recovers. Imagine that if the host where the instance is located is patched or time-consuming operations such as hardware replacement, OGG will keep waiting, completely without the significance of high availability.

Here is a case:

1. thread 2 of the dual-node RAC is shut down normally, resulting in abnormal OGG interruption. The default archiving path of thread 2 cannot be found.

The alarms and errors in the ggserr. log are as follows:

OGG-01423 No valid default archive log destination directory found for thread 2.

OGG-00868 failed to validate configuration on alternative log format and destination. User must either include thread specifier in the log format or specify unique destination for each and every thread.

2. The TRANLOGOPTIONS altarchivelogdest parameter is configured in the configuration file of the extract process.

EXTRACT ext1

Setenv (NLS_LANG = "AMERICAN_AMERICA.AL32UTF8 ")

Userid ogg @ RAC, password ogg

GETTRUNCATES

Reportcount every 1 MINUTES, RATE

Numfiles 5000

DISCARDFILE./dirrpt/extsym. dsc, APPEND, MEGABYTES 1024

Discardrolover

WARNLONGTRANS 2 h, CHECKINTERVAL 3 m

DBOPTIONS ALLOWUNUSEDCOLUMN

EXTTRAIL./dirdat/nd, MEGABYTES 500

DYNAMICRESOLUTION

Tranlogoptions excludeuser ogg

TRANLOGOPTIONS CONVERTUCS2CLOBS

TRANLOGOPTIONS altarchivelogdest primary instance orcl1/u02/Archive/ORCL/, altarchivelogdest instance orcl2/u03/Archive/ORCL/

Table hr. t1;

3. Cause and Solution

As shown in the preceding configuration file, the two instances have different log paths for archiving. OGG can find the specified archiving path only when both instances are active. If one of the instances goes down and becomes inactive, OGG does not know how to obtain the archive path. It looks silly, but it works like this.

The solution is as follows:

-You can archive two instances in the same path, either in/u02/archive/orcl or in/u03/archive/orcl.

-Add threadoptions processthreads into the parameter file

-Directly Delete this parameter.

I will select the last method to delete this parameter.

So what is the purpose of this parameter?

First, OGG knows the redo and archive log paths. It is clear from info extract * and detail that it does not need to specify where they are. If all archived logs are deleted after rman backup, and these archived logs are exactly what OGG needs, OGG will be interrupted. The remedy can restore the archived logs to their original locations or to other locations. With threadoptions processthreads release T, OGG can find the archived logs from other places.

I understand this. I don't know if it is correct.

Oracle GoldenGate tutorial 1: Introduction and Installation

Oracle GoldenGate tutorial 2. Configuration and usage

Oracle GoldenGate tutorial 3. Encryption

GoldenGate update loss

GoldenGate unidirectional table DML Synchronization

Oracle GoldenGate series: restoration principles of Extract processes

Oracle GoldenGate installation Configuration

OGG-01004 OGG-1296 error for Oracle goldengate

Oracle GoldenGate Quick Start Tutorial: Basic Concepts and configurations

Build a GoldenGate bidirectional replication environment from Oracle to Oracle

GoldenGate Security Configuration

Oracle GoldenGate (OGG) diagnostics

This article permanently updates the link address: