Sort goldengate parameters and goldengate Parameters

Sort goldengate parameters and goldengate Parameters
Manager parameter: AUTOSTART: Specifies the processes automatically started when mgr starts. autostart er * AUTOSTART extract extsz
AUTORESTART: Specifies the processes that can be restarted regularly on mgr. It can be automatically restarted after network interruption and other faults are restored to avoid manual intervention. autorestart er *, WAITMINUTES 5, RETRIES 3
DYNAMICPORTLIST: Specifies the ports that GoldenGate can use to receive data sent from extract. DYNAMICPORTLIST 7840-7850
PORT: Specifies the TCP/IP PORT used by the mgr process of GoldenGate to listen on request. PORT 7809.
LAGCRITICAL: specify the maximum latency that is considered to exceed this time as a serious error. If the latency reaches this time, an error message LAGCRITICALMINUTES 10 will be written in ggserr. log.
LAGREPORT: specify the time interval for reporting latency in ggserr. log. LAGREPORTHOURS 1
PURGEOLDEXTRACTS: defines automatic deletion of obsolete queues to save hard disk space. Generally, two rules are used for deletion. First, to meet the checkpoint requirements, a queue that has not been used cannot be deleted to ensure no data loss. Second, a certain number of days can be retained. The queue is automatically deleted only when it has been used and exceeds the specified number of days. Purgeoldextracts/backup/goldengate/dirdat/*, usecheckpoints, minkeepdays 7

Extraction parameter: CHECKPARAMS: If this parameter is added, it indicates that the next run only checks the syntax and does not actually run the process. Note: This command can only check some simple syntax, and cannot ensure that the parameter file is completely correct. COMMENT: COMMENT row, which can be replaced by two hyphens. -- checkparams indicates that the row has been commented out. EXTRACT: defines the name of the extraction process. OBEY: the content of the external file can be included in this parameter file. It is used to isolate some reusable parameter files to facilitate unified modification. Obey tables.txt TABLEEXCLUDE: defines the table to be excluded. If a wildcard is defined in the table, you can use this parameter to exclude some of the tables. For example, tableexclude ctais2.TMP _ *; tableexclude ctais2.TEMPTAB; GETUPDATEAFTERS | whether IGNOREUPDATEAFTERS writes post-image in the queue; GETUPDATEBEFORES | whether IGNOREUPDATEAFTERS writes pre-image in the queue, GETUPDATES is not copied by default. | whether to copy the update operation from IGNOREUPDATES. GETDELETES is copied by default. | whether to copy the delete operation from IGNOREDELETES. GETINSERTS is copied by default. | whether to copy the insert operation from IGNOREINSERTS, GETRUNCATES | whether to copy the truncate operation by default. RMTHOST specifies the port number of the target system and its GoldenGate Manager process. It is also used to define whether to use compression. For transmission. Rmthost 99.16.1.12, mgrport 7809, compressRMTTRAIL specifies the queue to which the data is written to the target end. EXTTRAIL specifies which queue to write to the local device. SQLEXEC first runs an SQL statement when running extract. Sqlexec "Alter session set constraints = deferred" PASSTHRU prohibits extract from interacting with the database. It is applicable to Data Pump Transfer Process (dpeXX) GETENV | SETENV sets system environment variables for extract processes. Setenv (NLS_LANG = AMERICAN_AMERICA.ZHS16GBK) REPORT defines automatic timing reports. Report at statoptions defines whether to reset the number of records processed in the reportcount report each time stat is used. Count the number TLTRACE to enable the TRACE log TRACE/TRACE2 to the database log to enable the tracking of the GoldenGate process. logs, it is generally used for debugging. DISCARDFILE defines the location of the discard file. If an error occurs during processing, it will be written to the discardfile/oradata/goldengate/repkj. dsc, append, megabytes 100 mNUMFILES defines the maximum number of tables reserved for this extract statement. The default value is 500, for more than 500 tables, you must set a value slightly greater than the actual number of tables. numfiles 3000 PURGEOLDEXTRACTS is the same as the mgr process. You can set automatic deletion of queues, we recommend that you set reportrolover in mgr to set the time and interval for switching a log. reportrolover at 02: 00 TRANSMEMORY to set the memory size available to the extraction process of GoldenGate. The following parameter specifies that the process can only occupy 2 GB of memory, and the maximum memory occupied by each transaction cannot exceed 500 mb. If the maximum memory occupied by each transaction is exceeded, the specified directory is used as the virtual memory, the size of a single file in this directory is 4 GB. A maximum of 8 GB space can be used as the cache. Transmemory directory (/backup/goldengate/dirtmp, 8G, 4G), ram 2G, transram 500 MDBOPTIONS specify the special parameters required for a specific database. [SOURCEDB,] USERID and PASSWORD: specify the name, user name, and PASSWORD of the database to be logged on. For oracle, you can directly specify the user name and password without specifying sourcedb. Userid goldengate and password goldengate TRANLOGOPTIONS specify the special parameters required for parsing database logs. For example, for bare devices, you may need to add the following parameter tranlogoptions rawdeviceoffset 0 tranlogoptions altarchivelogdest instance sidname/arch -- specify the WARNLONGTRANS where the archived logs are located and specify that long transactions that have been processed for a certain period of time can. write warning information in log. For example, if a long transaction is checked every 30 minutes, an alarm is triggered for more than 12 hours: -- warnlongtrans 12 h, checkintervals 30 m

Copy parameters: CHECKPARAMS checks the parameter syntax and then stops COMMENT row REPLICAT defines the process name USERID to specify the username and password for logging on to the target database. OBEY includes the external file to the parameter file. ASSUMETARGETDEFS assumes that the data structures at both ends use this parameter. SOURCEDEFS assumes that the data structures at both ends are inconsistent, use this parameter to specify the data structure definition file at the source end. This file needs to be generated by GoldenGate. MAPEXCLUDE is used to exclude the specified table when * matching is used in map, similar to tablexcludemapexclude CTAIS2.JC _ GY_SWWSWHMAP ctais2. *, TARGET ctais2 .*;
GETDELETES | whether IGNOREDELETES replicates the delete operation. The default value is GETUPDATES. | whether IGNOREUPDATES replicates the update operation. The default value is GETINSERTS. | whether IGNOREINSERTS replicates the insert operation, the default value is GETUPDATEAFTERS. | whether IGNOREUPDATEAFTERS reads post images. The default value is GETUPDATEBEFORES. | whether IGNOREUPDATEBEFORES reads pre-images. The default value is not GETTRUNCATES. | whether IGNORETRUNCATES replicates, the default value is not to copy allownoopupdates, which allows update without actual changes. For example, update a = a records an update record, but there is no post-image. The where statement REPERROR cannot be correctly constructed to define the replicat response after an error occurs. Generally, there are two types: Abend, that is, if an error occurs, the replication is stopped. This is the default configuration. If an error occurs, the system continues copying the data and only stores the error data in the Discard file. DISCARDFILE defines the output file of the error data. When an error occurs in the data, it can be used to find the cause of the error: discardfile/oradata/goldengate/dirrpt/repsz. dsc, append, and megabytes 10 HANDLECOLLISIONS automatically filter data conflicts in repeated time periods for initialization without stopping services. After this parameter is enabled, data errors are not reported to the discard file. DYNAMICRESOLUTION enables replicat to dynamically parse the table structure and speed up startup. By default, SQLEXEC calls the stored procedure or executes an SQL statement every time it starts parsing all the structures of the tables to be copied. The return value can be used as a filter condition, or the user can change the session variable. GROUPTRANSOPS combines small transactions into a large transaction for submission, reducing the number of submissions and reducing system IO consumption. MAXTRANSOPS splits large transactions and submits each batch of records at a time. maxtransops 1000 BATCHSQL optimizes the repeated operations on a table in batch processing to improve the processing speed of batch processing. DBOPTIONS defines special processing methods related to database types. NUMFILES defines the maximum data volume of tables in the process. The default value is 500. PURGEOLDEXTRACTS defines automatic deletion of queues. Generally, we recommend that you configure the queue in the mgr process.
The following three parameters are often used for error locating: nodynsql
Nobinarychars
Showsyntax
DYNSQL | NODYNSQLValid for ReplicatUse the DYNSQL and NODYNSQL parameters to control the way that SQL statements are formed. with NODYNSQL, Replicat uses literal SQL statements with the bind variables resolved. with DYNSQL, the default, Replicat uses dynamic SQL to compile a statement once, and then execute it usually times with different bind variables. ● Statement with DYNSQL: UPDATE <table>... WHER E id =: B ● Statement with NODYNSQL: UPDATE <table>... where id = '000000' 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 usin G NODYNSQL, you must also use the NOBINARYCHARS parameter. Oracle GoldenGate for MySQL does not support LOB replication in NODYNSQL mode. Default DYNSQLSyntax DYNSQL | NODYNSQL
BINARYCHARS | NOBINARYCHARSValid for Extract and ReplicatUse 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 cocould 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 BINARYCHARSSyntax BINARYCHARS | NOBINARYCHARS
SHOWSYNTAXValid for ReplicatUse 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 can 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 automatic processing is suincluded, 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 SHOWSYNTAX1. In the Replicat parameter file, include the following parameters in the order shown here, each on its own line: using NOBINARYCHARS using NODYNSQL using showsyntaxnote nobinarychars is an unformatted ented 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. 2. from the Oracle GoldenGate home directory, start Replicat from the command shell of the operating system using the syntax shown here. do not specify a reportfile option. output must go to screen. replicat paramfile dirprm/<Replicat_name>. prm 3. the first SQL statement is displayed with some prompts. please Choose Keep Displaying (the default) to execute the current statement and display the next one. explain Choose Stop Display to resume normal processing and stop printing SQL statements to screen.4. When finished viewing syntax, remove SHOWSYNTAX, NOBINARYCHARS, and NODYNSQL from the parameter file. default NoneSyntax SHOWSYNTAX

In version 11.1, the OGG Bounded Recovery BR parameter may have many problems. It is recommended that you close the parameter, and then cooperate with the operating system to monitor long transactions and regularly kill long transactions to avoid problems. Then configure CACHESZIE as a value to avoid affecting system performance.

Tranlogoptions logretention disabledtranlogoptions dblogreaderDBLOGREADER :( Oracle) Valid for Extract in classic capture mode. causes Extract to use a newer asm api that is available as 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 conne Cting 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 optionThe 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.