13.07.2015 Views

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

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

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

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 7FAQs113ER monitoring and managementThis section includes the following FAQs:1 What do you mean by ER monitoring?2 What do you mean by ER management?3 Which new alarms are introduced and how do I proceed if those alarms display in the AlarmMonitor?4 How can I tell if the ER database spaces are reaching capacity?1 What do you mean by ER monitoring?ER monitoring essentially means a mechanism in place to identify conditions that would impair thenormal functioning of "enterprise replication". These include the following:• ER has been stopped or suspended.• A host is unreachable.• A hosts has its clock out of sync.• A transaction has a conflict and needs manual intervention.• Sequence objects are nearing exhaustion.2 What do you mean by ER management?ER management essentially means allowing the operator to control certain aspects of the ER whenmanual intervention is needed or simply for diagnostic purposes:• View the status of synchronization.• View the discrepancies of data within the hosts.• Display the status of the servers.• <strong>Manual</strong>ly synchronize a table or a complete server.• Create a diagnostic tar file for customer support.3 Which new alarms are introduced and how do I proceed if those alarms display in theAlarm Monitor?• Aborted transaction (conflicts) reportedThis alarm indicates a conflict replicating a record. The target server receiving that recordrejects to commit it.- If this alarm occurs, look for recent ATS/RIS files in the /ats and /ris directories(located by default in the /ppbackup directory) and find out which records failed toreplicate and the failure reason.- In most cases, re-saving the record from the source server that originated the change willresolve the issue.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!