Picture Perfect 4.6 Enterprise Edition User Manual - UTCFS Global ...

90Picture Perfect 4.6 Enterprise EditionUser ManualNetwork outage on one hostIf a host is down for any reason, all changes destined for that host remain in queue. This means thatall changes are automatically applied when the host is restarted or brought back into the network.There is a limit to how long the host can be disconnected and yet have all its changes queued.The only limitations are the size of the queue (32 MB) and the size of the ER database spaces (whichare set to 40% of the base database sizes). Once the database spaces get filled to about 90%, analarm is raised and the host needs to be removed from the ER configuration using ercmd.sh.Based on our testing, the time a host can be disconnected and yet not have to be disconnected is inthe order of weeks.Note:This is a very rough estimation and depends a lot on the sizing of the database spaces and the number ofchanges being made.With an ER database space size of 200 MB, about 500K transactions can be made before 90%space is filled up. With 100 GB of ER database space, about 250M transactions can be made (giventhese transactions would have to be non-history related tables). It is very unlikely a host would haveto be removed from the ER, possibly for months.A customer can extend this time, by simply extending the size of the database space usingercmd.sh.Details of differences reported by ercmd.sh --statusUse cdr check with the -verbose option. See Informix Help for more information on cdr check.ATS/RIS alarmsIf ATS/RIS alarms are reported, check the /ppbackup/ris and /ppbackup/rts directories forthe files reporting the error(s). Depending on the error reported, a 'repair' command can be run fromthe nethost OR the system administrator may be able to decide which data should be 'winning' andtake action accordingly.Example of an ATS error that can be repaired by a cdr command:ATS output:root@bcteaglelake# cat ats.subhost_6.subhost_3.D_50.110531_14:40:28.1TXH Source ID:3 / Name:subhost_3 / CommitTime:11-05-31 14:40:27TXH Target ID:6 / Name:subhost_6 / ReceiveTime:11-05-31 14:40:28TXH Number of rows processed when transaction was aborted:1TXH Error: Dead lock encounteredTXH CDR:0 / SQL:-244 / ISAM:-143----------RRH Row:1 / Replicate Id: 65538 / Table: proteus@informix.badge / DbOp:DeleteRRS 3 (subhost_3)|1306867227 (11/05/31 14:40:27)RRD 268435458|Badge in bcthouston|0268435458||268435458||||||||||1|||||-1|20110531|144027In this case the deletion failed on subhost_3 because the badge table was in use (locked). To repairthis, run the following command on the nethost.root@bctcali# su - informix -c "cdr view -c subhost_6 atsdir -R -v"