KB labels


Ticket Product Version

Ticket Category

Ticket Assignee


Hot Fixes

Published Fixes
Your Arcserve Support User Profile
First Name:
Last Name:
email:
Phone:
Company:*
Customer Type:
Language:

Country:
Region:

Time zone:
Follow

arcserve-KB : How to Troubleshoot Ehealth Principal Scenario Data Growth

Last Update: 2016-04-12 11:46:47 UTC

Description: This document  explains the steps to troubleshoot the E-Health spool folder growth on the master.

 

CA ARCserve RHA copies all eHealth, Oracle, and eHealth database files over the network from the active eHealth system to a standby system, often in another physical location. When you update a file or directory on the active system, the changes are automatically replicated to standby system.


During online Replication, if the network throughput between Master and Replica is not sufficient to keep up with the change rate on the master, then the spool on the master will grow. Ehealth scenairos usally generate large amount of changes.

 

Please follow the below Technical Document to identify the rate of changes
https://arcserve.zendesk.com/hc/en-us/articles/202807155

If the rate of changes is higher than the bandwidth available, the changes will be spooled on the master that prevents a successful failover.

These changes are likely caused by the following features in oracle:-
1. Archive logs
2. Flashback Folder
3. Temp files.

You can enable detailed report and check the per hour changes.  Please refer the following document to enable and review detail report.

https://arcserve.zendesk.com/hc/en-us/articles/202046019

 

Archive log folder generates large number of changes. The following is an extracted output from a detailed Report..

159541248           E:/Data/oradata/EHEALTH/ArchiveLogs/LOG125652736347122.ARC
156069888           E:/Data/oradata/EHEALTH/ArchiveLogs/LOG125651736347122.ARC
153625088           E:/Data/oradata/EHEALTH/ArchiveLogs/LOG125650736347122.ARC
153625088           E:/Data/oradata/EHEALTH/ArchiveLogs/LOG125653736347122.ARC
153625088           E:/Data/oradata/EHEALTH/ArchiveLogs/LOG125654736347122.ARC

 

Oracle does not use archived redo logs when Oracle instances are started. Only online redo log are used by instance recovery. Archived redo logs are only used by restore from backup. You can exclude the entire archive log folder from replication

< Drive letter >:/Data/oradata/EHEALTH/ArchiveLogs

Secondly flashback feature in oracle also generates large number of changes. This feature is similar to the undo feature in word. The following is an extract from detail report. This feature is on by default in Ehealth scenairo

25182208             E:/Data/oradata/EHEALTH/flashRecoveryArea/EHEALTH/FLASHBACK/O1_MF_6HCPFXPG_.FLB
25182208             E:/Data/oradata/EHEALTH/flashRecoveryArea/EHEALTH/FLASHBACK/O1_MF_6HCPRPD6_.FLB
25182208             E:/Data/oradata/EHEALTH/flashRecoveryArea/EHEALTH/FLASHBACK/O1_MF_6HCPS2C7_.FLB
25182208             E:/Data/oradata/EHEALTH/flashRecoveryArea/EHEALTH/FLASHBACK/O1_MF_6HCPSRL2_.FLB
25182208             E:/Data/oradata/EHEALTH/flashRecoveryArea/EHEALTH/FLASHBACK/O1_MF_6HCPT5SD_.FLB
25182208             E:/Data/oradata/EHEALTH/flashRecoveryArea/EHEALTH/FLASHBACK/O1_MF_6HCPTR8S_.FLB
25182208             E:/Data/oradata/EHEALTH/flashRecoveryArea/EHEALTH/FLASHBACK/O1_MF_6HCPVJWS_.FLB
25182208             E:/Data/oradata/EHEALTH/flashRecoveryArea/EHEALTH/FLASHBACK/O1_MF_6HCPVY6C_.FLB

 

Flash back folder can't be excluded from the Replication data set if they are enabled on the master , doing so results in the following error on the replica:-

 ORA-27041: unable to open file

OSD-04002: unable to open file

O/S-Error: (OS 2) The system cannot find the file specified.

 

You can turn off this feature  in ehealth scenairos if the change rate is higher than the bandwidth.

Please consult Ehealth support team to turn this feature off.

 

Temporary tablespaces are used for special operations, particularly for sorting data results on disk.Each database should have one temporary tablespace that is created when the database is created.The temporary tablespace is where SQL performs operation like Sort etc. This file generates large number of changes and should be excluded from the replication data set.

 

Please also refer the following document to troubleshoot spool folder growth and replication performance .

 

How to Use Iperf to fine tune the synchronization and replicaiton throughput:https://arcserve.zendesk.com/hc/en-us/articles/202042569

How to Monitor CA ARCserve RHA replication throughput: https://arcserve.zendesk.com/hc/en-us/articles/202042389

How to Monitor the CA ARCserve RHA scenario stastics:https://arcserve.zendesk.com/hc/en-us/articles/202807075

 

 

 

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments