Oracle goldengate parameter Finishing

Transferred from: http://blog.csdn.net/lemontree1123/article/details/46603549

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 in 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 over extract. Dynamicportlist 7840-7850 port: Specifies which TCP/IP port the goldengate MGR process uses to listen for requests. Port 7809 lagcritical: Specify the maximum delay value that is considered a critical error over this time.  If the delay reaches this time value, an error message is written in the Ggserr.log lagcriticalminutes lagreport: Specifies the time interval to report the delay 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 7Extracting 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 replication getruncates| 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  Disable extract interaction 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  define automatic timing reporting.  report at 01:59 statoptions  defines whether statistics need to be reset each time the stat is used reportcount  report the number of records that have been processed statistics tltrace  Open the trace log for the database log  TRACE/TRACE2  open 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 tables reserved for this extract, the default is 500, more than 500 tables need to set a value slightly larger than the actual number of tables Numfiles 3000PURGEOLDEXTRACTS   with MGR process, you can set the automatic deletion queue, it is recommended to switch the time and interval of one log in Mgr setting reportrollover   reportrollover at 02:00transmemory  Sets the amount of memory that can be used by the goldengate extraction process. 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 name, user name, and password of the database to be logged in. For Oracle, you can specify a user name and password directly without specifying Sourcedb. Userid goldengate, Password Goldengate tranlogoptions  Specifies the special parameters that are required to parse the database log. For example, for bare devices, you may need to add the following parameters tranlogoptions Rawdeviceoffset 0 tranlogoptions altarchivelogdest instance Sidname/arch  --specifies that the archive log is located warnlongtrans  specifies that a warning message can be written to Ggserr.log for long transactions that exceed a certain amount of time. For example, a long transaction is checked every 30 minutes, and alarms for more than 12 hours:--warnlongtrans 12h, checkintervals 30m   copy Parameters:checkparams  Check the parameter syntax and then stop comment  Comment Line replicat  define the process name userid  specify the user name and password to log in to the target database obey  To include an external file in the parameter file assumetargetdefs  assumes that the data structure is consistent with this parameter sourcedefs  assumes that the data structures are inconsistent, use this parameter to specify the data structure definition file for the source side. The file needs to be generated by the Goldengate tool mapexclude  used to remove the specified table when using * match in map, similar to Tablexcludemapexclude CTAIS2 on the source side. Jc_gy_swwswhmap ctais2.*, TARGET ctais2.*;  getdeletes | ignoredeletes  Copy delete operation, default is copy Getupdates | Ignoreupdates   Whether to copy the update operation, the 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 copy allownoopupdates  allow execution withoutThe actual change of the update. For example, update a=a will record an update, but there is no post-image to correctly construct a where statement reperror  the REPLICAT response after an error is generally defined as two: Abend, which stops copying once an error occurs, This is the default configuration; Discard, continue copying after an error, just put the wrong data into the Discard file.  DISCARDFILE  defines the output file for the error data. After the data error, can be used to find the cause of the error  discardfile/oradata/goldengate/dirrpt/repsz.dsc,append, megabytes 10HANDLECOLLISIONS   Automatic filtering of data conflicts for repeating periods, for no downtime to perform initialization. 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 tables  SQLEXEC  call stored procedures or Execute SQL statements each time it starts. 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  The big deal, each record is submitted once  maxtransops 1000batchsql  for batch processing in order to optimize the bulk of a table, to improve batch processing speed.  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 to define an automatic deletion queue for 500.purgeoldextracts , which is generally recommended in the MGR process configuration.   frequently use the following three parameters when locating errors: nodynsql
Nobinarychars
Showsyntax  dynsql | Nodynsqlvalid for Replicatuse the Dynsql and Nodynsql parameters to control the the-the-on-the-same-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 many times with Different bind variables.  Statement with Dynsql:update <table> ... WHERE ID =: B Statement with Nodynsql: update <table> ... WHERE ID = ' 1234 ' in more environments, using dynsql yields the best efficiency and most throughput. however, in Isola Ted Instances, using Nodynsql have proven faster and more efficient. Try nodynsql only if Replicat throughput appears unsatisfactory. Do not use the dynsql when replicating to target databases, that does not support dynamic SQL. When using the Nodynsql, you must also use The nobinarychars parameter. Oracle GoldenGate for MySQL does no 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 it is entered in the source table. This ensures proper processing in cases if a column in the source or target database is defined as a character Column and it is possible, that binary characters could are entered into that column. Binarychars isn't compatible with the Bulkload parameter (direct-bulk load); Use nobinarychars. Nobinarychars can cause Oracle GoldenGate to interpret a binary character to is the end of 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 is recommended So that Data is maintained the the-it was 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 an interactive session where can View Each replicat SQL statement before it is applied. By viewing the syntax of SQL statements that failed, you might is able to diagnose the cause of the problem. For example, you could find out the WHERE clause is using a non-indexed column. Requirements for using Showsyntax the first time so you use Showsyntax, request guidance from an Oracle Support an Alyst. It is a debugging paraMeter and can cause unwanted results if used improperly. It requires manual intervention, so automated processing are 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 Operating system. The Showsyntax if Replicat is started through ggsci.  use Showsyntax in a test environment. Create duplicates of your replicat groups And target 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 that causes Oracle goldengate to treat binary data as a nul l-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 SYN Tax shown here. Do not specify a reportfile option. output must go to Screen.replicat paramfile Dirprm/<replicat_name>.prm&nbs P;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. The Default nonesyntax showsyntax  11.1 version of the ogg bounded Recovery BR parameter may have many problems, preferably shut down, and then cooperate with the operating system to monitor long transactions, Kill long transactions regularly 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 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 connecting directly to The ora CLE 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&nbs P;is 28672 bytes. This was controlled by The asmbufsize option. A larger buffer may improve the performance of Extract when redo rate is high. when using Dblogreader, does not us E The Asmuser and asmpassword options of Tranlogoptions. The API uses The user and password specified with the USERID parameter。  

Oracle goldengate Parameter collation