goldengate some parameters finishing
https://www.cnblogs.com/tlnshuju/p/7372779.html
manager parameters: AUTOSTART: specify your own initiative to start the process that started at the mgr. AUTOSTART ER * AUTOSTART Extract extsz AUTORESTART: can specify the timing to restart those processes mgr. On their own initiative can restart after a network interruption recovery. Avoid manual intervention. AUTORESTART ER * , WAITMINUTES 5 , RETRIES 3 DYNAMICPORTLIST: GoldenGate can be used to specify that port accepts data sent from the extract. DYNAMICPORTLIST 7840 - 7850 PORT: GoldenGate developed mgr process which use TCP / ipport listens for requests. PORT 7809 LAGCRITICAL: Specifies the think beyond this time is the maximum delay serious mistakes, assuming that the delay time to reach this value will be written to an error message ggserr.log inside LAGCRITICALMINUTES 10 LAGREPORT: Specifies ggserr.log reported delay time interval. LAGREPORTHOURS 1 PURGEOLDEXTRACTS: define your own initiative to remove obsolete queue to save hard disk space. In accordance with the general rule to delete two: first of all. To meet the requirements of the checkpoint, did not use the queue can not be deleted to ensure that no data loss; secondly, to retain a certain number of days. When there are only a few days after the queue has been used over and set their own initiative will be deleted. purgeoldextracts / Backup / GoldenGate / dirdat / * , usecheckpoints, minkeepdays 7 extraction parameters: CHECKPARAMS: assume increased this argument, the next performance is just to check the syntax, not the actual implementation process. Note: This command can only check some simple grammar does not guarantee parameter file is completely correct. COMMENT: staring line. Can also be crossed with two in - replace .-- checkparams represent the Bank has been staring out EXTRACT: custom extraction process name OBEY: external file's contents to be able to include this parameter file to. Some can be used to isolate the parameter file used repeatedly part, facilitates uniform changes. Tables.txt Obey, TABLEEXCLUDE: definition table need excluded. Assuming table which defines the use of wildcards, it can use the parameters defined among the excluded parts table. Such as: tableexclude ctais2.TMP_ *; ctais2.TEMPTAB tableexclude; GETUPDATEAFTERS | IGNOREUPDATEAFTERS whether the image is written in the queue, the default copy GETUPDATEBEFORES | whether IGNOREUPDATEAFTERS before writing the image in the queue, the default is not copied getUpdates | whether IGNOREUPDATES copy update operation. The default copy GETDELETES | IGNOREDELETES whether to copy delete operation, the default copy GETINSERTS | IGNOREINSERTS whether copy insert operation. The default copy GETRUNCATES | IGNORETRUNCATES whether to copy truncate operation, the default is not copied. RMTHOST target system and port number GoldenGate Manager process. Also used to define whether compression is used for transmission. 99.16.1.12 rmthost, mgrport 7809, the compress RMTTRAIL specify which queue written to the target terminal. EXTTRAIL specify which local queue to be written. SQLEXEC first perform a sql statement when the extract execution. the SQLEXEC "Alter the session the SET deferreds the Constraints =" PASSTHRU prohibit extract interact with the database for Data Pump transfer process (dpeXX) GETENV | SETENV set system environment variables for the extract process. setenv (the NLS_LANG = AMERICAN_AMERICA.ZHS16GBK) the REPORT define their own initiative scheduled reports. REPORT AT 01:59 STATOPTIONS define whether the statistics are reset each time you need to use the stat number of records have been processed article REPORTCOUNT report statistics TLTRACE open for database log trace log TRACE / TRACE2 open the trace log on GoldenGate process, generally used for debugging. DISCARDFILE defined discard file location. Suppose there is a record processing error will be written to this file DISCARDFILE /oradata/goldengate/repkj.dsc,append,megabytes 100m NumFiles this extract is defined as the maximum number of tables reserved space, the default is 500, more than 500 tables need a table set slightly larger than the actual number of value NumFiles 3000 PURGEOLDEXTRACTS with mgr process. Delete the queue can be provided on their own initiative, recommended mgr provided REPORTROLLOVER setting switching time and a log interval AT 02:00 reportrollover [SOURCEDB,] USERID, PASSWORD specifies the name of the database to be landing. username and password. For the oracle without specifying sourcedb. Directly specify the username and password on it. Userid goldengate, password goldengate TransMemory set GoldenGate extraction process can be used memory size. For example the following parameter specifies the maximum occupancy of this process can only 2G of memory, of which the largest memory for each transaction can not exceed 500M. Assuming that exceed the specified folder as virtual memory, this folder under a single file size is 4G, can at most only as a cache folder in the occupied 8G space. Directory TransMemory (/ Backup / GoldenGate / dirtmp, 8G, 4G), 2G RAM, 500M transram DBOPTIONS specify parameters for a specific need of a particular database. TRANLOGOPTIONS specify a particular parameter when the need of parsing the database log. For example, for the bare device, you may need to increase the following parameters tranlogoptions rawdeviceoffset 0 tranlogoptions altarchivelogdest instance sidname / Arch - specify the archive log is located WARNLONGTRANS specified can be written warnings in ggserr.log there for more than a certain length of time of the transaction. such as. Inspected once every 30 minutes long transaction, for more than 12 hours of an alarm: - warnlongtrans 12h, checkintervals 30m replication parameters: CHECKPARAMS parameter syntax checking and then stop COMMENT gaze line REPLICAT defined process name USERID designated landing target database username and password OBEY parameters to an external file comprises file ASSUMETARGETDEFS assumed that ends consistent with this data structure parameter SOURCEDEFS assumed that ends inconsistent data structure. This parameter is used to specify the source data structure definition file. The document produced by the need GoldenGate tool the MAP ctais2 *, the TARGET ctais2 *..; MAPEXCLUDE using the map used in the specified table * excluded match, similar to the source terminal tablexclude mapexclude CTAIS2.JC_GY_SWWSWH discardfile /oradata/goldengate/dirrpt/repsz.dsc,append, megabytes 10 GETDELETES | IGNOREDELETES whether to copy delete operation, the default is to copy GETUPDATES | IGNOREUPDATES whether the copy operations update. Default is to copy GETINSERTS | IGNOREINSERTS whether to insert copy operations, default is to copy GETUPDATEAFTERS | whether IGNOREUPDATEAFTERS after reading the image, the default is read GETUPDATEBEFORES | whether IGNOREUPDATEBEFORES read the first image, the default is not read GETTRUNCATES | IGNORETRUNCATES whether to copy truncate operation, the default is not copied allownoopupdates agree to run no actual change update. For example, update a = a record of an update. But no after image, you can not build where the statement correct response after REPERROR defined error replicat, generally can be defined as two kinds: Abend, that is, once the errors stop replication. This is the default; Discard, after continued replication errors. Just the wrong data into the discard file. DISCARDFILE define the output file error data. When the data error. It can be used to find the cause of the error HANDLECOLLISIONS filter the data on their own initiative repeated periods of conflict, can not stop running for initialization. After opening this parameter does not report data errors discard file. DYNAMICRESOLUTION the structure replicat dynamic analysis table, faster boot. The default is every time you start parsing the entire structure of the table you want to copy SQLEXEC call a stored procedure or run sql statement. The return value can be used as filter conditions. Or the user changes the session variable. GROUPTRANSOPS small transactions merged into a big deal submit, submit to reduce the number of times, reduce system IO consumption. MAXTRANSOPS will split the large transaction. Article submitted once every several record 1000 maxtransops BATCHSQL for batch optimized for large quantities of a table of repeated operations, improve processing speed batch processing. DBOPTIONS defining special handling type associated with the database. NUMFILES maximum amount of data tables in the definition process, the default is 500. The PURGEOLDEXTRACTS define their own initiative delete queue is generally recommended configuration mgr process. Often use incorrect positioning of the following three parameters: nodynsql nobinarychars showsyntax DYNSQL | NODYNSQL ! Valid for Replicat the Use at The DYNSQL and NODYNSQL the Parameters at The Way to Control SQL statements that are . Formed With NODYNSQL, Replicat uses the bind at The literal SQL statements with the Variables resolved With DYNSQL, at The default, Replicat uses Dynamic SQL to the compile A of Statement. once, and then execute it many times with different bind variables. ● Statement with DYNSQL: UPDATE <table> ... WHERE ID = :B ● Statement with NODYNSQL: UPDATE <table> ... WHERE ID = ‘1234’ In most environments, using DYNSQL yields the best efficiency and most throughput. However, in isolated instances, using NODYNSQL has proven faster and more efficient. Try NODYNSQL only if Replicat throughput appears unsatisfactory. Do not use DYNSQL when replicating to target databases that do not support dynamic SQL. When using NODYNSQL, you must also use the NOBINARYCHARS parameter。 Oracle GoldenGate for MySQL does not support LOB replication in NODYNSQL mode. Default DYNSQL Syntax DYNSQL | NODYNSQL BINARYCHARS | NOBINARYCHARS Valid for Extract and Replicat Use BINARYCHARS and NOBINARYCHARS to control whether character data is treated as binary data or null-terminated strings. BINARYCHARS, the default, maintains data the way it was entered in the source table. This ensures proper processing in cases when a column in the source or target database is defined as a character column and it is possible that binary characters could be entered into that column. BINARYCHARS is not compatible with the BULKLOAD parameter (direct-bulk load); use NOBINARYCHARS. NOBINARYCHARS can cause Oracle GoldenGate to interpret a binary character to be the end of the data in that column. If there is more data after the binary data, it is not processed by Oracle GoldenGate, compromising data integrity. NULL characters cause this to happen, as well as any character defined with the DELIMITER option of FORMATASCII. Unless there is good reason to use NOBINARYCHARS, leaving the default set to BINARYCHARS is recommended so that data is maintained the way it was entered in the source table. Before using NOBINARYCHARS, contact Oracle Support. BINARYCHARS and NOBINARYCHARS are table-specific. One parameter remains in effect for all subsequent TABLE or MAP statements until the other is encountered. Default BINARYCHARS Syntax BINARYCHARS | NOBINARYCHARS SHOWSYNTAX Valid for Replicat Use the SHOWSYNTAX parameter to start an interactive session where you can view each Replicat SQL statement before it is applied. By viewing the syntax of SQL statements that failed, you might be able to diagnose the cause of the problem. For example, you could find out that the WHERE clause is using a non-indexed column.Requirements for using SHOWSYNTAX ● The first time that you use SHOWSYNTAX, request guidance from an Oracle Support analyst. It is a debugging parameter and can cause unwanted results if used improperly. It requires manual intervention, so automated processing is suspended, and it slows down processing, which can cause backlogs and latency. ● To use SHOWSYNTAX, Replicat must be started from the command shell of the operating system. Do not use SHOWSYNTAX if Replicat is started through GGSCI. ● Use SHOWSYNTAX in a test environment. Create duplicates of your Replicat groups and target tables so that the production environment is not affected. Using SHOWSYNTAX 1. In the Replicat parameter file, include the following parameters in the order shown here, each on its own line: ❍ NOBINARYCHARS ❍ NODYNSQL ❍ SHOWSYNTAX NOTE NOBINARYCHARS is an undocumented parameter that causes Oracle GoldenGate to treat binary data as a null-terminated string. Contact Oracle Support before using it. NODYNSQL causes Replicat to use literal SQL statements instead of using dynamic SQL with bind variables. The Home the From the Oracle GoldenGate 2. Directory, Start Command The Replicat from the shell of the using The Operating System Shown here Wallpaper The syntax. A ReportFile the Specify the Do Not Option. The Output MUST Go to Screen. replicat paramfile dirprm/<Replicat_name>.prm 3. The first SQL statement is displayed with some prompts. ❍ the Choose the Keep the Displaying (The default) to Execute The Current and at the Run the display of Statement the Next One. ❍ Stop the Choose Display to Resume Normal STOP Processing and Printing SQL statements to Screen. 4. Viewing the When Finished syntax, the Remove SHOWSYNTAX, NOBINARYCHARS, and NODYNSQL from at the the Parameter File. the Default None syntax SHOWSYNTAX 11.1 version number OGG Bounded Recovery BR parameters may have very many problems. Preferably closed, and then with Caozuojitong long transaction monitoring, the timing of long transaction kill. Avoid failure. Then configure CACHESZIE to a value. To avoid affecting system performance. tranlogoptions logretention disabled dblogreader tranlogoptions
DBLOGREADER: (the Oracle)! Valid for Extract Extract in Classic Capture mode.Causes A newer ASM to use API that the Available AS IS of Oracle 10.2.0.5 and later 10g R2 versions, and Oracle 11.2.0.2 and later 11g R2 versions (but not in Oracle 11g R1 versions).
This API uses the database server to access the redo and archive logs, instead of connecting directly to the Oracle ASM instance.
The database must contain the libraries that contain the API modules and must be running.To use this feature, the Extract database user must have SELECT ANY TRANSACTIONprivilege.
When used, DBLOGREADER enables Extract to use a read size of up to 4 MB in size. This is controlled with the DBLOGREADERBUFSIZE option The maximum read size when using the default OCI buffer is 28672 bytes. This is controlled by the ASMBUFSIZE option. A larger buffer may improve the performance of Extract when redo rate is high. When using DBLOGREADER, do not use the ASMUSER and ASMPASSWORD options of TRANLOGOPTIONS.
The API uses the user and password specified with the USERID parameter。