Golden Gate and Streams

Question

Oracle 11.1.0.7:
Before I ask my simple question. Is there a place I can get detailed documentation of Golden Gate? I got some documentation but that is very high level. I am looking for some document or tutorial like the ones Oracle has on tahiti.oracle.com.
We are currently using streams and personally worked on it. I see following issues:
1. When some errors occur in dba_apply_error it's really slow to re-execute them. Recovery is very slow
2. Streaming the LOBs over of just 512 bytes makes the CCA very slow
3. Manageability of scripts, configuration etc. is a headache
4. Come accross streams bugs all the time
From what I have read about golden gate is that is super fast and better than streams. I haven't read about it so I don't have complete comparision. Could someone with similar experience provide the insight.
Also, if someone can please help me get right detailed documents would be really great.

Answer 1

Hi,
Think the goldengate documentation provide adequate help to install and configure oracle goldengate process. I can put down a sample configuration for you to get started.
Installing GoldenGate and configuring a extract replicat process.
First FTP the installation zip in binary mode from the PC to the installation directory on machine where Oracle GoldenGate suppose to be installed.
Use gzip to decompress the file.
gzip –d <file_name>.gz
Extract the files
Use tar to extract the files. All GoldenGate files will be placed in the current subdirectory.
tar –xvf <file_name>.tar
Create folders
Create the required sub-directories in the installation directory by using
Shell> cd <install location>
Shell> ggsci
GGSCI> create subdirs
GGSCI> exit
Oracle-specific installation steps
The below steps are only required when GoldenGate will be capturing data from the server. Therefore it is only needed when you are installing GoldenGatef or Oracle as your <source> environment.
You need to turn on supplemental logging at the database level. This command requires the ALTER DATABASE permissions.
Shell> sqlplus <login>/<password>
SQL> alter database add supplemental log data;
Now Switch to the next redo log file.
SQL> alter system switch logfile;
SQL> exit
Then now configure manager parameter file.
GGSCI> EDIT PARAMS MGR
•     Use the editor to assign a port
--GoldenGate Manager parameter file
PORT <port>
example: PORT 7840
•     To Start the Manager, issue following command
GGSCI> START MGR
•     To Verify that the Manager has started, issue the following command
GGSCI> INFO MGR
Now Configure Supplemental logging.
By default, if not supplimentory logging enabled , only the change vectors will be logged in redo logs So inorder to get the columns required for constructing the image by replicat in target we require atleast minimum supplimentory logging enabled in database level and table level logging required for proper functioning of Oracle Goldengate Software.
Using GGSCI, log in to the database on the <source> and turn on supplemental logging for the the tables configured for replication
Shell> ggsci
GGSCI> DBLOGIN USERID <login>
GGSCI> ADD TRANDATA <owner/schema>.<table-name>
Do this for all the tables.
Configure change capture
1. Add the Extract group
Execute the following command on the <source> system to add an Extract group
GGSCI> ADD EXTRACT <extract-name>, TRANLOG, BEGIN NOW
Verify the results:
GGSCI> INFO EXTRACT <extract-name>
Create the Extract parameter file
Execute the following commands on the <source> system.
GGSCI> EDIT PARAM <extract-name>
EXTRACT <extract-name>
USERID <login>, PASSWORD <password>
RMTHOST <target>, MGRPORT <port>
RMTTRAIL ./dirdat/<trail id>
TABLE <owner/schema>.<table-name>
TABLE <owner/schema>.<table-name>
for example
extract testext
userid ggs password ggs
rmthost 172.25.25.177
rmttrail ./dirdat/tr
table scott.mytable;
table scott.yourtable;
Define the GoldenGate trail
Execute the following command on the <source> to add the trail that will store the changes on the <target>.
GGSCI> ADD RMTTRAIL ./dirdat/<trail id>, EXTRACT <extract-name>
Verify the results:
GGSCI> INFO RMTTRAIL *
Start the capture process
GGSCI> START EXTRACT <extract-name>
Configure Change Delivery or replicat
we have to do the following
•     Set up the checkpoint table on the target system.(this is optional)
•     Create a named group that includes the Replicat process and the checkpoint tables.
•     Configure the Replicat group by adding parameters.
•     Start the Replicat group.
Now we will check how to set up the checkpoint table (this is a optional settings)
Create a GLOBALS file on the target system
Execute the following commands on the <target> system.
Create and edit the GLOBALS parameter file to add the checkpoint table.
Shell> cd <install location>
Shell> ggsci
GGSCI> EDIT PARAMS ./GLOBALS
In the text editor, type:
CHECKPOINTTABLE <owner/schema>.ggschkpt
•     Record the checkpoint table owner and name, then save and close the file.
Please Note: You could name the table anything you want
•     Verify that the GLOBALS file was created in the root GoldenGate directory, and remove any file extension that was added.
Activate the GLOBALS parameters
For the GLOBALS configuration to take effect, you must exit the session in which
the changes were made. Execute the following command to exit GGSCI.
GGSCI> EXIT
Add a Replicat checkpoint table     
On the <target> system, execute the following commands in GGSCI:
Shell> cd <install location>
Shell> ggsci
GGSCI> DBLOGIN USERID <login>, PASSWORD <password>
GGSCI> ADD CHECKPOINTTABLE
Configure Change Delivery
Add the Replicat group
Execute the following command on the <target> system to add a delivery group
named <replicat-name>
GGSCI> ADD REPLICAT <replicat-name>, EXTTRAIL ./dirdat/<trail id>
Note: Refer to your Extract set up for the correct two-character <trail id>.
Create Replicat parameter file
Execute the following commands on the <target> system to bring up the parameter
file in the editor.
GGSCI> EDIT PARAM <replicat-name>
-Type in the following parameters
REPLICAT <replicat-name>
USERID <login>, PASSWORD <password>
HANDLECOLLISIONS
ASSUMETARGETDEFS
DISCARDFILE ./dirrpt/RORA<unique id>.DSC, PURGE
MAP <owner/schema>.<source table-name>, TARGET <owner/schema>.<target table-name>;
Start the Replicat process
GGSCI> START REPLICAT <replicat-name>
Verify the results:
GGSCI> INFO REPLICAT <replicat-name>
The above i scrapped is a basic extract-replication process which you can scale up once you get accustomed with this beautiful product.
Thanks & Regards,
Antony Joseph Jethu.