Creating Replicat parallel process groups in Software Display barcode 3 of 9 in Software Creating Replicat parallel process groups

Creating Replicat parallel process groups use software 39 barcode implementation toembed 39 barcode in software ISSN -- config_ Software Code39 target.oby -- Login to Database dblogin userid ggs_admin@olap, password ggs_admin -- Adds Checkpoint Table add checkpointtable GGS_ADMIN.GGSCHKPT.

1. Use the following Obey file to prepare and configure your target system for multiple Replicat process groups:. -- Adding bar code 39 for None the replicat group for the delivery ADD REPLICAT replcat1, EXTTRAIL ./dirdat/ta, CHECKPOINTTABLE GGS_ ADMIN.GGSCHKPT -- Adding the replicat group for the delivery ADD REPLICAT replcat2, EXTTRAIL .

/dirdat/ta, CHECKPOINTTABLE GGS_ ADMIN.GGSCHKPT -- Adding the replicat group for the delivery ADD REPLICAT replcat3, EXTTRAIL ./dirdat/tb, CHECKPOINTTABLE GGS_ ADMIN.

GGSCHKPT -- Adding the replicat group for the delivery ADD REPLICAT replcat4, EXTTRAIL ./dirdat/tb, CHECKPOINTTABLE GGS_ ADMIN.GGSCHKPT.

[ 200 ]. 9 -- Star Software 3 of 9 ting the replicat groups START REPLICAT * -- Check status of all running processes INFO ALL. 2. Place t he config_target.oby file in the dirprm sub-directory of the GoldenGate home on the target system.

3. To execute the Obey file, call it from the GGSCI command line..

GGSCI (dbserver2) 1> obey ./dirprm/config_target.oby 4. Check if the Replicat processes are running. GGSCI (dbs 39 barcode for None erver2) 119> info all Program MANAGER REPLICAT REPLICAT REPLICAT REPLICAT Status RUNNING. RUNNING RUNNING RUNNING RUNNING REPLCAT1 REPLCAT2 REPLCAT3 REPLCAT4 00:00:00 00:00:00 00:00:00 00:00:00 00:00:06 00:00:06 00:00:06 00:00:06 Group Lag Time Since Chkpt. That concl udes the target system configuration. From the example output, we can see that the Replicat processes have been started and are running. You can now enjoy high performance data replication from the OLTP to OLAP databases.

. Improving Replicat throughput Replicat p erformance can be further improved by altering the way GoldenGate commits the transaction on the target database. By default, Oracle will wait for a commit to succeed before allowing the session to continue. However, this synchronous behavior can cause unnecessary delays when the workload is high.

To alleviate this bottleneck, we can configure our Replicat processes to commit asynchronously at session level by including the following SQLEXEC statement in each parameter file:. SQLEXEC "a Software Code 39 Full ASCII lter session set commit_wait = "NOWAIT"";. [ 201 ]. Performance Tuning Note that the specification of the NOWAIT allows a small window of vulnerability. These are as follows: If the database instance crashes, causing the database to lose redo that was buffered but not yet written to the online redo logs A file I/O problem prevents log writer from writing buffered redo to disk. Don"t be a Software Code 3 of 9 larmed; in both cases, GoldenGate will automatically "replay" the uncommitted transactions which would be driven by the information stored in the Checkpoint table, following database instance crash recovery.. New releases At the tim Software Code 3 of 9 e of writing this book, a new release of Oracle GoldenGate has become available: Version 11.1.1.

0.0 Build 078 for Oracle 11gR2 This version runs on the Oracle Sun Exadata2 Database Machine (11.2.

0.1), but is not without some performance issues. A known bug causes slow write performance to a Database file system (DBFS), which would typically be used to store the GoldenGate persistent files in a RAC environment.

During tests, the measured data pump write rate (with no Replicat processes running) into DBFS was 1.5 to 1.7 MB/sec.

For comparison, the Data Pump write rate into a regular Linux file system on the same server was in the 30 MB/sec range and simple writes using the Linux dd utility into the same DBFS mount produced rates in the 30 to 50 MB/sec range. Happily however, Oracle states this issue is fixed in the next release of GoldenGate: Version 11.1.

1.0.5 Build 003.

. DBFS enhancements When confi Software Code-39 guring DBFS, it is highly recommended to adopt the following options: Create a separate database instance running in NOARCHIVELOG mode to support the DBFS. Create a DBFS tablespace in the dedicated Database, configured with. NOLOGGING Create a S Code39 for None ecureFile LOB segment defined with NOCACHE NOLOGGING Create the file system with the PARTITION option. [ 202 ]. 9 . Mount the DBFS through /etc/fstab, using the following options: rw,user,direct_io,allow_other,wallet,noauto,max_.
Copyright © . All rights reserved.