1. edit params命令 2. DBLOGIN USERID <user>, PASSWORD <password> 3. ADD TRANDATA命令 4. ADD EXTRACT 命令 5. ADD EXTTRAIL命令 6. EXTFILESOURCE <file name>意思 7. ADD RMTTRAIL命令 8. ADD REPLICAT命令 9. PURGEOLDEXTRACTS 10. AUTOSTART参数 11. DYNAMICRESOLUTION 12. SOURCEDB 13. PASSTHRU 14. ASSUMETARGETDEFS 15. REPERROR 16. 使用通配符 (1) Overview of Extract The Extract process runs on the source system and is the capture mechanism of GoldenGate. You can configure Extract in one of the following ways: ● Initial loads: For initial data loads, Extract extracts a current set of data directly from their source objects. ● Change synchronization: To keep source data synchronized with another set of data, Extract extracts transactional changes made to data (inserts, updates, and deletes) after the initial synchronization has taken place. DDL changes and sequences are also extracted, if supported for the type of database being used. (2) Overview of Replicat The Replicat process runs on the target system. Replicat reads extracted data changes and DDL changes (if supported) that are specified in the Replicat configuration, and then it replicates them to the target database. You can configure Replicat in one of the following ways: (3) Overview of trails To support the continuous extraction and replication of supported database changes, GoldenGate stores those changes temporarily on disk in a series of files called a trail. A trail can exist on the source or target system, or on an intermediary system, depending on how you configure GoldenGate. On the local system it is known as an extract trail (or local trail). On a remote system it is known as a remote trail. By using a trail for storage, GoldenGate supports data accuracy and fault tolerance (see “Overview of checkpoints” on page 28). The use of a trail also allows extraction and replication activities to occur independently of each other. With these processes separated, you have more choices for how data is delivered. For example, instead of extracting and replicating changes continuously, you could extract changes continuously but store them in the trail for replication to the target later, whenever the target application needs them. 1. edit params命令 ================== Use EDIT PARAMS to create or change a parameter file. By default, this command launches Microsoft Notepad on Windows or the vi editor on UNIX systems. You can change the editor with the SET EDITOR command. Syntax: EDIT PARAMS {MGR | <group> | <file name>} MGR Opens a parameter file for the Manager process. <group> Opens a parameter file for the specified Extract or Replicat group. <file name> Opens the specified file. Use the full path name. Example 1: EDIT PARAMS finance Example 2: EDIT PARAMS c:\lpparms\replp.prm GGSCI (testdb11.zhyhl.com) 6> PORT <port_number> PORT defines the port number on which Manager runs on the local system. The default port is 7809. You must specify either the default port or another port. The port must be unreserved and unrestricted. GGSCI uses this port to request Manager to start processes. The Extract process uses this port to request Manager to start a remote Collector process or an initial-load Replicat process. PORT is the only required Manager parameter. Autostart parameters Use the AUTOSTART parameter to start Extract and Replicat processes when Manager starts. This can be useful, for example, if you want GoldenGate activities to begin immediately when you start the system, assuming Manager is part of the startup routine. You can use multiple AUTOSTART statements in the same parameter file. AUTOSTART {ER | EXTRACT | REPLICAT} {group name | wildcard} Use the AUTORESTART parameter to start Extract and Replicat processes again after abnormal termination. AUTORESTART {ER | EXTRACT | REPLICAT} {group name | wildcard} [, RETRIES <max retries>] [, WAITMINUTES <wait minutes>] [, RESETMINUTES <reset minutes>] 2. DBLOGIN USERID <user>, PASSWORD <password> ============================================= dblogin userid test,password test DBLOGIN USERID <user>, PASSWORD <password> Where: <user> is a database user who has privilege to create triggers or enable tablelevel supplemental logging, and <password> is that user’s password. 3. ADD TRANDATA命令 =================== Use the ADD TRANDATA command in GGSCI to configure the database to log the key values whenever it logs a row change, so that they are available to GoldenGate in the redo record. By default, the database only logs column values that are changed. ADD TRANDATA must be performed before you start GoldenGate processing. add trandata test.* To capture key values with ADD TRANDATA ADD TRANDATA <table> [, COLS <columns>] [, NOKEY] [, USETRIGGER] Where: ? <table> is the owner and name of the table. You can use a wildcard for the table name but not the owner name. ? COLS <columns> logs non-key columns that are specified with KEYCOLS. ? NOKEY prevents the logging of the primary key or unique key. Requires using a KEYCOLS clause in TABLE or MAP and logging the KEYCOLS columns with COL. ? USETRIGGER forces GoldenGate to install an update trigger instead of a supplemental log group. Required only if 8i compatibility is enabled on a 9i or later database. 4. ADD EXTRACT 命令 =================== add extract extzq, tranlog, begin now 解释： Use ADD EXTRACT to create an Extract group. Unless a SOURCEISTABLE task is specified, this command creates checkpoints so that processing continuity is maintained from run to run. ADD EXTRACT <group name> {, SOURCEISTABLE | , GGSLOG <ggslog table> | , TRANLOG [bsds name> | , VAM | , EXTFILESOURCE <file name> | , EXTTRAILSOURCE <trail name> | , VAMTRAILSOURCE <VAM trail name>} {, BEGIN <begin spec> | , EXTSEQNO <seqno>, EXTRBA <relative byte address> | , LOGNUM <log number>, LOGPOS <byte offset> | , LSN <value> | , EXTRBA <relative byte address> | , EOF | LSN <value> | , PAGE <data page>, ROW <row>} [, THREADS <n>] [, PASSIVE] [, PARAMS <parameter file>] [, REPORT <report file>] [, DESC <description> ] TRANLOG Specifies the transaction log as the data source. Use this option for log-based extraction. TRANLOG requires either the BEGIN or EXTSEQNO and EXTRBA options. The following are service options: BEGIN <begin spec> Specifies a timestamp in the data source at which to begin processing. Valid values: * NOW * A date and time in the format of: yyyy-mm-dd [hh:mi:[ss[.cccccc]]] Example 2: The following creates an Extract group named finance that extracts database changes from the transaction logs. Extraction starts with records generated at the time when the group was created. ADD EXTRACT finance, TRANLOG, BEGIN NOW 5. ADD EXTTRAIL命令 ==================== add exttrail /home/test/ggs95/dirdat/zq,extract extzq,megabytes 50 Use ADD EXTTRAIL to create a trail for online processing on the local system and: * Associate it with an Extract group. * Assign a maximum file size. Syntax: ADD EXTTRAIL <trail name>, EXTRACT <group name> [,MEGABYTES <n>] <trail name> The fully qualified path name of the trail. The actual trail name can contain only two characters. GoldenGate appends this name with a six-digit sequence number whenever a new file is created. For example, a trail named /ggs/dirdat/tr would have files named /ggs/dirdat/tr000001, /ggs/dirdat/tr000002, and so forth. <group name> The name of the Extract group to which the trail is bound. Only one Extract process can write data to a trail. MEGABYTES <n> The maximum size, in megabytes, of a file in the trail. The default is 10. Example: ADD EXTTRAIL c:\ggs\dirdat\aa, EXTRACT finance, MEGABYTES 20 6. EXTFILESOURCE <file name>意思 ================================ add extract dpezq,exttrailsource /home/test/ggs95/dirdat/zq EXTFILESOURCE <file name> Specifies an extract file as the data source. Use this option with a secondary Extract group (data pump) that acts as an intermediary between a primary Extract group and the target system. For <file name>, specify the fully qualified path name of the file, for example c:\ggs\dirdat\extfile. 7. ADD RMTTRAIL命令 =================== add rmttrail d:\ggs95\dirdat\zq ,extract dpezq,megabytes 50 Use ADD RMTTRAIL to create a trail for online processing on a remote system and: * Associate it with an Extract group. * Assign a maximum file size. In the parameter file, specify a RMTHOST entry before any RMTTRAIL entries to identify the remote system and TCP/IP port for the Manager process. Syntax: ADD RMTTRAIL <trail name>, EXTRACT <group name> [, MEGABYTES <n>] <trail name> The fully qualified path name of the trail. The actual trail name can contain only two characters. GoldenGate appends this name with a six- digit sequence number whenever a new file is created. For example, a trail named /ggs/dirdat/tr would have files named /ggs/dirdat/tr000001, /ggs/dirdat/tr000002, and so forth. <group name> The name of the Extract group to which the trail is bound. Only one Extract process can write data to a trail. MEGABYTES <n> The maximum size, in megabytes, of a file in the trail. The default is 10. Example: ADD RMTTRAIL c:\ggs\dirdat\aa, EXTRACT finance, MEGABYTES 20 8. ADD REPLICAT命令 =================== add replicat repzq, exttrail /home/gdora/ggs/dirdat/rt, nodbcheckpoint, begin now Use ADD REPLICAT to create a Replicat group. Unless a special run is specified, ADD REPLICAT creates checkpoints so that processing continuity is maintained from run to run. See the GoldenGate Operations Guide for Windows and UNIX for procedures that include creating Replicat groups. Syntax: ADD REPLICAT <group name> {, SPECIALRUN | , EXTFILE <full path name> | , EXTTRAIL <full path name>} [, BEGIN <start point> | , EXTSEQNO <seqno>, EXTRBA <relative byte address>] [, CHECKPOINTTABLE <owner.table> | NODBCHECKPOINT] [, PARAMS <parameter file>] [, REPORT <report file>] [, DESC <description> ] <group name> The name of the Replicat group. Follow these naming conventions: * You can use up to eight ASCII characters, including nonalphanumeric characters such as the underscore (_). Any ASCII character can be used, so long as the operating system allows that character to be in a filename. This is because a group is identified by its associated checkpoint file. * Group names are not case-sensitive. * Use only one word. * Do not use the word port as a group name. However, you can use the string port as part of the group name. * Do not place a numeric value at the end of a group name, such as fin1, fin10, and so forth. You can place a numeric value at the beginning of a group name, such as 1_fin, 1fin, and so forth. ext_1 ex+2t ex!2t EXTTRAIL <full path name> Specifies a trail that was created with the ADD RMTTRAIL or ADD EXTTRAIL command. NODBCHECKPOINT Specifies that this Replicat group will not write checkpoints to a checkpoint table. This argument overrides the default CHECKPOINTTABLE specification in the GLOBALS file. 9. PURGEOLDEXTRACTS =================== Trail maintenance parameter Use the PURGEOLDEXTRACTS parameter in a Manager parameter file to purge trail files when GoldenGate has finished processing them. Without using PURGEOLDEXTRACTS, no purging is performed, and trail files can consume significant disk space. Using PURGEOLDEXTRACTS as a Manager parameter is preferred over using the Extract or Replicat version of PURGEOLDEXTRACTS. As a Manager parameter, PURGEOLDEXTRACTS allows you to manage trail files in a centralized fashion and take into account multiple processes. NOTE When using this parameter, do not permit trail files to be deleted by any user or program other than GoldenGate. It will cause PURGEOLDEXTRACTS to function improperly purgeoldextracts /home/gdora/ggs/dirdat/*, usecheckpoints, minkeepdays 2 Use USECHECKPOINTS to purge when all processes are finished with a file as indicated by checkpoints. Use the MINKEEP rules to set a minimum amount of time to keep unmodified data: ? Use MINKEEPHOURS or MINKEEPDAYS to keep data for <n> hours or days. 10. AUTOSTART参数 ================= To auto-start a process ● Use AUTOSTART in the Manager parameter file to start one or more processes when Manager starts. ● Use AUTORESTART in the Manager parameter file to restart a process after a failure. Both of these parameters reduce the need to start a process manually with the START command. Syntax AUTOSTART <process type> <group name> <process type> Specify one of the following: EXTRACT REPLICAT ER (Extract and Replicat) <group name> A group name or wildcard specification for multiple groups. When wildcarding is used, GoldenGate starts all groups of the specified <process type> that satisfy the wildcard on the local system, except those in PASSIVE mode. Example AUTOSTART ER * 11. DYNAMICRESOLUTION ===================== DYNAMICRESOLUTION | NODYNAMICRESOLUTION Valid for Extract and Replicat Use the DYNAMICRESOLUTION and NODYNAMICRESOLUTION parameters to control how table names are resolved. Use DYNAMICRESOLUTION to make processing start sooner when there is a large number of tables specified in TABLE or MAP statements. By default, whenever a process starts, GoldenGate queries the database for the attributes of the tables and then builds an object record for them. The record is maintained in memory and on disk, and the process of building it can be time-consuming if the database is large. DYNAMICRESOLUTION causes the object record to be built one table at a time, instead of all at once. A table’s attributes are added to the record the first time its object ID enters the transaction log, which occurs with the first extracted transaction on that table. Recordbuilding for other tables is deferred until activity occurs. DYNAMICRESOLUTION is the same as WILDCARDRESOLVE DYNAMIC. NODYNAMICRESOLUTION causes the object record to be built at startup. This option is not supported for Teradata. NODYNAMICRESOLUTION is the same as WILDCARDRESOLVE IMMEDIATE. For more information about WILDCARDRESOLVE, see page 368. Default DYNAMICRESOLUTION Syntax DYNAMICRESOLUTION 12. SOURCEDB ============ Valid for Manager, Extract, DEFGEN, and DDLGEN Use the SOURCEDB parameter for databases that require a data source name as part of the connection information. Tables specified in TABLE statements that follow SOURCEDB are assumed to be from the specified data source. 其实是不管用，而且还会报错说不识别该参数 13. PASSTHRU ============ data-pump模式有的两种选择: PASSTHRU and NOPASSTHRU PASSTHRU: 不与数据库交互，前提是源库与目标库objects必须一致。 Use the PASSTHRU and NOPASSTHRU parameters to control whether a data-pump Extract processes tables in pass-through mode or normal mode. In pass-through mode, the Extract process does not look up table definitions, either from the database or from a datadefinitions file. Normally, the Extract process logs into the database to retrieve data definitions and, if the target is NonStop, reads a data-definitions file. The definitions are used to perform mapping and conversion functions. To use PASSTHRU mode, the names of the source and target objects must be identical. No column mapping, filtering, SQLEXEC functions, transformation, or other functions that require data manipulation can be specified in the parameter file. You can combine normal processing with pass-through processing by pairing PASSTHRU and NOPASSTHRU with different TABLE statements. 14. ASSUMETARGETDEFS ===================== 不查询主库的表结构信息，前提是：使用MAP statement时，原库和目标库的表的字段结构必须一致。 Valid for Replicat Use the ASSUMETARGETDEFS parameter when the source and target tables specified with a MAP statement have identical column structure, such as when synchronizing a hot site. It directs GoldenGate not to look up source structures from a source-definitions file. For structures to be identical, they must contain identical column names (including case, if applicable) and data types, and they must appear in the same order in each table. If source and target tables do not have the same structure, use the SOURCEDEFS parameter instead of ASSUMETARGETDEFS. See “SOURCEDEFS” on page 291. Default None Syntax ASSUMETARGETDEFS 15. REPERROR ============ REPERROR Valid for Replicat Use the REPERROR parameter to control how Replicat responds to errors. You can use one REPERROR statement to handle most errors in a default manner, while using one or more other REPERROR statements to handle specific errors differently. For example, you can ignore duplicate-record errors but abort processing in all other cases. DEFAULT Sets a global response to all errors except those for which explicit REPERROR statements are specified. DISCARD Log the error to the discard file but continue processing the transaction and subsequent transactions. DISCARDFILE Valid for Extract and Replicat Use the DISCARDFILE parameter to generate a discard file to which GoldenGate can log records that it cannot process. Records can be discarded for several reasons. For example, a record is discarded if the underlying table structure changed since the record was written to the trail. You can use the discard file to help you identify the cause of processing errors. Each entry in the discard file contains the discarded record buffer and an error code indicating the reason. GoldenGate creates the specified discard file in the dirrpt subdirectory of the GoldenGate installation directory. You can view it with a text editor or by using the following command in GGSCI. VIEW REPORT <file name> Where: <file name> is the fully qualified name of the discard file. GoldenGate creates the specified discard file in the dirrpt subdirectory of the GoldenGate installation directory. /* discard file的存放路径 */ APPEND Adds new content to existing content if the file already exists. MEGABYTES <n> Sets the maximum size of the file in megabytes. The valid range is from 1 to 2147. The default is 1 MB. 16. 使用通配符 ============== Using wildcards in command arguments You can use wildcards with certain GoldenGate commands to control multiple Extract and Replicat groups as a unit. The wildcard symbol that is supported by GoldenGate is the asterisk (*). An asterisk represents any number of characters. For example, to start all Extract groups whose names contain the letter X, issue the following command. START EXTRACT *X*
扫一扫
1924
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
