Golden Gate Related Components Description:

OGG components:

1. Manager: Start Other processes
2. Collector
3. Extract
4. Data Pump: Optional process, recommended use
5. Replicat
6. Trails: can be compressed, encrypted
7. Checkpoint

Ogg Process Group

1. Process Group:
1. Process
2. Parameter FILE:DIRPRM
3. Checkpoint File:dirchk
4. Additional Files: dirrpt (report file:. Rpt and Discard file:. DSC ogg12c Auto-created), Dirdef,dirpcs (Process run Status: Pcm-manager, Pcr-replicate,pce-extract )
5. Each process group is named unique: case blending is not recommended, Linux may be abend, and group is not recommended to end with a number.

Ogg Common directives:

1. Ggsci:
1. Obey
2. Help <command> <object>
3. !: repeatedly executes the previous command
4. Shell <os command>
5. View ggsevt (for Ggserr.log file content, remember to clean up regularly, do not delete files directly. )
6. History
7. Stats
8. Send
9. Kill

Common Goldengate directives:

2. Add Trandata vs Add schematrandata
2. Add Trandata: Trandata information is not automatically updated (Create table,update additional log column information, etc.)
4. Add schematrandata:

    command format: add  schematrandata <,  schemaname>  (do not use Schemaname.*   exec   Dbms_goldengate_auth.grant_admin_privilege (' goldengate '); check if enable: Query  select  *  from  table  (Logmnr$always_suplog_columns (' Schemaname  '   ); Info Trandata cannot be queried. Dba_log_groups and Dba_log_group_columns have no information  

6. CONVCHK: Convert checkpoint files to a new version
8. Defgen: When the source and target libraries are different types of databases, the definition of heterogeneous data is generated
10. Keygen: Generate an encrypted key
12. Extract:extract parameterfile <path> reportfile <path>
14. Replicat:replicat parameterfile <path> reportfile <path>
16. Oggerr: Query ogg error number, such as: Oggerr 1738

Goldengate directory structure:

Directory	Description
Br	Bounded recover needed checkpoint files
Cfg	Configure the property and XML files required for OGG monitoring
Dirchk	The checkpoint file created by the Extract or replicat process. CPE and CPR Suffixes
Dirdat	Default storage location for trial files, 2 user-defined characters + 6 digits
Dirdef	Heterogeneous data definition file, generated by Defgen
Dirjar	OGG Monitor-related jar packages
Dirpcs	Process Status File
Dirprm	Parameter file
Dirrpt	Storage directory for process reports
Dirsql	SQL script
Dirtmp	Temporary storage directory for transactions exceeding allocated memory

Golden Gate parameter file:

2. Global (Globals file)
1. Check Point table information: Checkpointtable goldengate.checkpoint
2. DDL: File information: Ggschema goldengate
3. Windows environment Registration MGR Services: Mgrservname ggmgr
1. ggsci> Install AddService addevents
4. Process parameter: DIRPRM/*.PRM
6. Mgr Parameters:
1. Port:mgr Listening Port
2. Dynamicportlist: The port range of the actual worker process used to receive data sent by the extract process.
3. Autostart:mgr which processes start automatically at startup
4. AutoRestart: In the case of a process failure, MGR can attempt to restart those processes, specifying the number of retries and the time interval
5. Lagcritical: Delay More than this time is a serious error, write an error message inside the Ggserr.log
6. Laginfo: If the delay reaches this time value will write an info message in Ggserr.log
7. Lagreporthours: Check the frequency of lag (here is the hour, also can lagreportminutes)
8. Purgeoldextracts: The policy for automatically deleting obsolete queues. It is recommended that you use relative or absolute paths uniformly.
8. Extract parameters:
2. Extract Group Name
4. Trial file information (Rmthost, Rmttrail, Exttrail)
6. Tables that need to be copied or excluded (tables, tableexclude)
8. Whether to specify column information
10. Which operations to extract (Getupdates)
12. What to capture (Getupdatebefores | Ignoreupdateafters)
14. You can specify filtering, mapping, converting
16. General Default Minimalist parameters:
1. All DML operations are captured:
1. Capture only commit operations
2. Insert operation: Full post mirror
3. Update operation: Append log columns and modify columns, do not capture pre-update mirror values
4. Delete action: Additional log columns
2. Do not convert
3. Cachemgr parameter control: 64bit default maximum can be used to 64g, so to control, otherwise memory consumption is too large: cachemgr cachesize 2048M, cachedirectory./dirtmp 4GB, Cachedirectory ./DIRTMP2 4GB
4. BR: Default 4 hours. BR Brinterval 20M, brdir br (20M means check interval is 20 minutes): Scene: Long transaction is not finished, log file is deleted, no need to restore log file, after receiving commit, write to trial file directly from file in BR directory.
18. Two extraction modes:
1. Classic: Extract based on an online log or archive log. No special requirements for database version
2. Consolidation: (11.2.1 or more)logmining Server is responsible for capturing data changes from the database log in the LCR format, and the extract process then stores the data in the trail file. Logical Change Records
3. Benefits of the integration model:
1. More data types are supported on compatibility (IOT, compression, XML, LOB)
2. No additional configuration required for RAC, ASM, TDE, Rman
3. Multi-threaded extraction (producer Thread:capture Redo;consumer thread:process Redo), the performance of the concurrent processing process improves.
4. OGG12C capture of Oracle 12c Multi-tenancy (must be integrated with extraction mode to support)
5. DDL without Trigger (OGG12C, DB11204)
6. It's closer to the database engine!
4. Integration Mode Deployment Method:
1. Local deployment: Source and log Mining server databases are the same database (source and integration extraction processes on the same host)
2. Downstream deployment: Source and log mining server databases are different databases (source libraries deliver archived logs to downstream databases) (source and integration extraction processes are not on the same host)

Golden Gate Related Components Description: