Manager Parameters:AUTOSTART:Specifies that those processes are started automatically when MGR is started.AUTOSTART ER *autostart Extract Extsz
AutoRestart: Specifies that those processes can be restarted periodically at Mgr. You can automatically restart after a failure such as a network outage to avoid manual intervention. AutoRestart ER *, waitminutes 5, retries 3
Dynamicportlist: Specifies that goldengate can use those ports to accept data sent by extract. Dynamicportlist 7840-7850
PORT: Establish the Goldengate MGR process to use which TCP/IP port to listen for requests. Port 7809
Lagcritical: Specifies the maximum delay value that is considered to be a critical error over this time, and an error message is written to the Ggserr.log if the delay reaches this time value lagcriticalminutes 10
Lagreport:Specifies the time interval for reporting delays in Ggserr.log. Lagreporthours 1
Purgeoldextracts: Defines automatic deletion of obsolete queues to conserve hard disk space. Generally in accordance with two rules to delete: First, to meet the checkpoint requirements, no used queue can not be deleted, ensure no data loss, and secondly, you can retain a certain number of days. Only queues that have been used and have exceeded the set number of days are automatically deleted. Purgeoldextracts/backup/goldengate/dirdat/*,usecheckpoints, Minkeepdays 7
Extracting parameters:Checkparams: If you add this parameter, it means that the next run is just checking the syntax and not actually running the process. Note: This command only checks for some simple syntax and does not guarantee that the parameter file is completely correct. COMMENT: Comment Line, can also use two underline--instead.--checkparams indicates that the bank has been commented out EXTRACT: Defines the name of the extraction process OBEY: You can include the contents of the external file in this parameter file. Used to isolate portions of the parameter file that can be reused for uniform modification. Obey tables.txttableexclude: Defines the tables that need to be excluded. If you define a wildcard character in the table, you can use this parameter to define some of the tables that are excluded from it. such as: Tableexclude Ctais2. Tmp_*;tableexclude Ctais2. Temptab; Getupdateafters | Ignoreupdateafters If the image is written in the queue, the default copy getupdatebefores | Ignoreupdateafters if the pre-image is written in the queue, Getupdates is not copied by default | Ignoreupdates Copy update operation, default copy Getdeletes | Ignoredeletes Copy delete operation, default copy Getinserts | Ignoreinserts whether to copy the insert operation, the default duplicatesystemgetruncates| Ignoretruncates whether the truncate operation is replicated, not copied by default. RMTHOST Specifies the port number of the target system and its Goldengate manager process, and also defines whether to use compression for transmission. Rmthost 99.16.1.12,mgrport 7809, compressrmttrail specifies which queue is written to the target end. EXTTRAIL Specifies which queue is written to local. SQLEXEC runs an SQL statement first while the extract is running. SqlExec "Alter session set constraints=deferred" PASSTHRU prohibits extract from interacting with the database for the data pump transfer process (Dpexx) GETENV | SETENV sets the system environment variables for the extract process. Setenv (Nls_lang = American_america. ZHS16GBK) report defines automatic timing reporting. The report at 01:59 Statoptions defines whether statistics need to be reset each time the stat is used Reportcount reports the number of records that have been processed statistics tltrace open the trace log for the database log Trace/trace2 Opens the trace log for the goldengate process, which is typically used for debugging. Discardfile defines the discard file location and writes to this file if there is a record error in processing discardfile/oradata/goldengate/repkj.dsc,append,megabytes 100mNUMFILES defines the maximum number of table extract to reserve space, the default is 500, more than 500 tables need to set a value slightly larger than the actual number of tables Numfiles 3000purgeoldextracts with the MGR process, you can set the automatic deletion queue, it is recommended to set the MgrReportrollover set the time and interval to toggle a log reportrollover at 02:00transmemory to set the amount of memory the goldengate extraction process can use. The following parameters specify that the process can only consume up to 2G of memory, where each transaction consumes no more than 500M, and if more than the specified directory is used as virtual memory, the single file size in this directory is 4G, which can only occupy 8G space as a cache in that directory. Transmemory directory (/backup/goldengate/dirtmp,8g,4g), Ram 2g,transram 500MDBOPTIONS Specifies the special parameters that are required for a particular database. [Sourcedb,] USERID, PASSWORD Specifies the database name, user name, and password to be logged in. For Oracle, you can specify a user name and password directly without specifying Sourcedb. Userid goldengate, Password goldengatetranlogoptions Specifies the special parameters that are required to parse the database log. For example, for bare devices, you may need to include the following parameterstranlogoptions Rawdeviceoffset 0Tranlogoptions Altarchivelogdest Instance Sidname/arch--Specify the archive log in Warnlongtrans specifies that a warning message can be written to the Ggserr.log for long transactions that exceed a certain amount of time. For example, check for a long transaction every 30 minutes and alarm for more than 12 hours:--warnlongtrans 12h, checkintervals 30m
Copy parameters:Checkparams Check the parameter syntax and then stop the comment comment line replicat define the process name UserID specifies the user name and password of the login target database obey to include the external file in the parameter fileAssumetargetdefs assumes that this parameter is used consistently on both data structuresSourcedefs assumes that the data structures on both ends are inconsistent, use this parameter to specify the data structure definition file on the source side. The file needs to be generated by the Goldengate toolMapexclude is used to remove the specified table when using * match in map, similar to the source-side TablexcludeMapexclude CTAIS2. Jc_gy_swwswhmap ctais2.*, TARGET ctais2.*;
Getdeletes | Ignoredeletes Copy delete operation, default is copy Getupdates | Ignoreupdates Copy update operation, default is copy Getinserts | Ignoreinserts If the insert operation is copied, the default is copy Getupdateafters | Ignoreupdateafters If the image is read, the default is read Getupdatebefores | Ignoreupdatebefores whether to read the pre-image, the default is not to read Gettruncates | Ignoretruncates whether to copy the truncate operation, the default is not to copyAllownoopupdates allows you to perform an update without actual changes. For example, update a=a will record an update, but without a post image, the where statement cannot be constructed correctlyReperror definition after the error replicat response, generally can be defined as two kinds: Abend, that is, once the error is stopped replication, this is the default configuration; Discard, continue copying after an error, just put the wrong data into the Discard file. Discardfile the output file that defines the error data. When data errors occur, you can use it to find the cause of the error discardfile/oradata/goldengate/dirrpt/repsz.dsc,append, megabytes 10Handlecollisions automatically filters for data collisions over a repeating period, which can be used to perform initialization without downtime. When this parameter is opened, data errors are not reported in the discard file. Dynamicresolution enables Replicat to dynamically parse the structure of the table to speed up startup. The default is to resolve all the structures to replicate the table every time you startSQLEXEC calls a stored procedure or executes an SQL statement. You can filter the return value as a basis, or the user changes the session variable.grouptransops the small transaction into a large transaction to commit, reduce the number of commits, and reduce the system IO consumption. Maxtransops to split the big deal and submit it once for each record maxtransopsbatchsql to improve batch processing speed by optimizing bulk repeat operations for a table in batch processing。 Dboptions defines special handling methods related to database types. Numfiles defines the maximum amount of data for a table in a process, the default is 500.PURGEOLDEXTRACTS to define the automatic deletion queue, which is generally recommended in the MGR process configuration.
The following three parameters are frequently used when locating errors:Nodynsql
Nobinarychars
Showsyntax
Dynsql | Nodynsqlvalid for Replicatuse the Dynsql and Nodynsql parameters to control the the-the-on-the-the-same-SQL statements is 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 many times with Diffe Rent 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 have proven faster and more efficient. TryNodynsql only if Replicat throughput appears unsatisfactory.Do is use dynsql when replicating to target databases , that does not support dynamic SQL. When using Nodynsql, you must also use theNobinarycharsParameter Oracle GoldenGate for MySQL does isn't 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 binarydata or null-terminated strings.Binarychars, the default, maintains data the it is entered in the source table. This ensures proper processing in cases when a column of the source or target database is defined as a character column an D It is possible this binary characters could be entered to that column. Binarychars is isn't compatible with the Bulkload parameter (direct-bulkload); useNobinarychars.Nobinarychars can cause Oracle GoldenGate to interpret a binary character to is the end of the the data in that column. If There was more data after the binary data, it was 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 are recommended so that data is MA Intained The It is entered in the source table. Before using Nobinarychars, contact Oracle Support.binarychars and Nobinarychars is 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 a interactive session where can view eachReplicat SQL Statement before it is applied. By viewing the syntax of SQL statements thatfailed, you might is able to diagnose the cause of the problem. For example, you could findThe The WHERE clause is using a non-indexed column.Requirements for using ShowsyntaxThe first time that's use Showsyntax, request guidance from a Oracle supportAnalyst. It is a debugging parameter and can cause unwanted results if usedimproperly. 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 is started from the command shell of the operatingSystem. The Showsyntax if Replicat is started through Ggsci. Use the Showsyntax in a test environment. Create duplicates of your replicat groups andtarget Tables So, the production environment is not affected.Using SHOWSYNTAX1. In the Replicat parameter file, include the "following parameters in the" order shown here, and each on its-own line:? Nobinarychars? Nodynsql? Showsyntaxnote Nobinarychars is an undocumented parameter the causes Oracle GoldenGate to treat binary data as a null-ter minated string. Contact Oracle support before using it. Nodynsql causes Replicat to use literal SQL statements instead of usingdynamic SQL with bind variables.2. From the Oracle GoldenGate home directory, start replicat from the command shell ofThe 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.? Choose Keep Displaying (the default) to execute the current statement and display the next one.? 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 NonesyntaxShowsyntax
The 11.1 version of the Ogg bounded Recovery BR parameter may have many problems, preferably shut down, and then coordinate with the operating system to monitor long transactions and regularly kill long transactions to avoid problems. Then Configure Cacheszie as a value to avoid impacting system performance.
Tranlogoptions logretention disabledtranlogoptions Dblogreaderdblogreader: (Oracle) Valid for Extract in classic capture Mode.causes Extract to use a newer ASM API which is available asof Oracle 10.2.0.5 and later 10g R2 versions, and Oracle11.2.0.2 and later 11g R2 versions (but not in Oracle 11g R1versions). This API uses the database server to access theRedo and archive logs, instead of connecting directly to theOracle ASM instance. The database must contain thelibraries that contain the API modules and must berunning.To use this feature, the Extract database user must has SELECT any TRANSACTIONprivilege. When used, Dblogreader enables Extract to use a read sizeof up to 4 MB in size. this was controlled with thedblogreaderbufsizeoptionThe maximum read size when using the default OCI bufferis 28672 bytes. this was controlled by the asmbufsize option. A larger buffer may improve the performance of ExtractWhen redo.When using Dblogreader, does not use the Asmuser andasmpassword options of Tranlogoptions. The API uses theuser and password specified with the USERID parameter.
Goldengate some parameter finishing
