Sequence of start and stop for Golden Gate
===============================
Hint:-
1. If Linux Server needs to reboot then stop "Manager" process also.
2. If Patching, upgrades then stop manager also.
3. When stopping golden gate processes keep in mind always stop extract, replicat, pump first and then stop manager if server needs to reboot.
Hint:-
1. find the latest status of processes using :-- cat dirrpt/PROCESS_NAME.rpt or cat ggserr.log
2. dirprm---> parameter files
3. dirdat ---> data files trails files
4. dirchk --->
Stop Sequence:
==============================
= stop the extract process on the source
= wait for the pump process to catch up
= stop the pump process on the source
= wait for the replicat process to catch up
= stop the replicat process on the target
= optionally (because it does not belong to a specific GoldenGate replication) stop the manager and jagent process on both source and target
=========================================================================
Start Sequence:
===============================
= optionally start the manager and the jagent process
= start the replicat process on the target
= start the pump process on the source
= start the extract process on the source
=========================================================================
special commands >>
====================
GGSCI>
> stop extract extract_name; ------------------------if stop extr doesnt worked then move to send extract extract_name,forcestop
> send extract extract_name, forcestop; -----------if send extract extract_name, forcestop doesnt worked then move to kill extract extract_name
> kill extract extract_name; -------------------------final option that kill the process and ckpt will, stop mgr would not try to start kill process, no db loss
> alter extract extract_name, begin now; ............will alter the sequence no and bring the ckpt to current trail
> start extract extract_name; ...............................start the extract,
> alter extract extract_name, etrollover; .............will alter extract to new trail file;
Note: You can also apply above commands to replicate.
No comments:
Post a Comment