nobinarychars
showsyntax DYNSQL | NODYNSQL Valid for Replicat Use 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 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. 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. ? 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 None Syntax SHOWSYNTAX 11.1版本的OGG Bounded Recovery BR参数可能会有很多问题，最好关闭，然后配合操作系统监控长事务，定时杀掉长事务，避免出现问题。然后 配置CACHESZIE为一个值，避免影响系统性能。 tranlogoptions logretention disabled tranlogoptions dblogreader DBLOGREADER ： (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 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。
Oracle Goldengate参数整理
标签：