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 ...
112Picture Perfect 4.6 Enterprise EditionUser Manual23 hostconfig log file reported "SQL error" messagesThere are valid and benign SQL errors in the hostconfig.log file as a result of the serverconfiguration processes performed by hostconfig.Valid SQL error messages and explanations are listed below:908 - Cannot connect to local or remote database.This error can occur while starting the database and checking for its status during a subhost configuration.206 - Table does not exist.The error is commonly found when checking for Enterprise Replication status of a new subhost that is not yetconfigured in the system.674 - Dropping non-existent Stored Procedure.This error is found during installation of a new subhost, which is trying to create new a Stored Procedure, removingany previous record of the Stored Procedure in the database.634 - Dropping non-existent Trigger.This error is found during installation of a new subhost, which is trying to create new Trigger, removing any previousrecord of the Trigger in the database.8301 -Sequence object already exist.This error is reported in the hostconfig log, as a search for that particular error, to avoid creating a Sequenceobject that is already created in the database.Note:No other SQL error codes are allowed in the hostconfig.log.YYYYMMDDhhmmss file. If other errors are found, they should be reported for analysis.24 Do I have to change the Custom History Reports based on database schema changesmade in Picture Perfect 4.6?Yes, all Custom History Reports are affected and must be reviewed and changed according to theHistory table unified schema listed in Table 10:Table 10. Database Schema Changes in Picture Perfect 4.6Table Name OLD Column NEW Columnbadge_history area - integer area_desc - varchar(60)alarm_history input_group - integer ingrp_desc - varchar(60)micro - integermicro_desc - varchar(60)operator_his terminal - integer terminal_desc - varchar(60)tour_history tour_definition - integer definition_desc - varchar(60)alarm - integerarea - integertour_exception - integeralarm_desc - varchar(60)area_desc - varchar(60)exception_desc - varchar(60)
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.• Manually 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.
- Page 70 and 71: 62Picture Perfect 4.6 Enterprise Ed
- Page 72 and 73: 64Picture Perfect 4.6 Enterprise Ed
- Page 74 and 75: 66Picture Perfect 4.6 Enterprise Ed
- Page 76 and 77: 68Picture Perfect 4.6 Enterprise Ed
- Page 78 and 79: 70Picture Perfect 4.6 Enterprise Ed
- Page 80 and 81: 72Picture Perfect 4.6 Enterprise Ed
- Page 82 and 83: 74Picture Perfect 4.6 Enterprise Ed
- Page 84 and 85: 76Picture Perfect 4.6 Enterprise Ed
- Page 86 and 87: 78Picture Perfect 4.6 Enterprise Ed
- Page 88 and 89: 80Picture Perfect 4.6 Enterprise Ed
- Page 90 and 91: 82Picture Perfect 4.6 Enterprise Ed
- Page 92 and 93: 84Picture Perfect 4.6 Enterprise Ed
- Page 94 and 95: 86Picture Perfect 4.6 Enterprise Ed
- Page 96 and 97: 88Picture Perfect 4.6 Enterprise Ed
- Page 98 and 99: 90Picture Perfect 4.6 Enterprise Ed
- Page 100 and 101: 92Picture Perfect 4.6 Enterprise Ed
- Page 102 and 103: 94Picture Perfect 4.6 Enterprise Ed
- Page 104 and 105: 96Picture Perfect 4.6 Enterprise Ed
- Page 106 and 107: 98Picture Perfect 4.6 Enterprise Ed
- Page 108 and 109: 100Picture Perfect 4.6 Enterprise E
- Page 110 and 111: 102Picture Perfect 4.6 Enterprise E
- Page 112 and 113: 104Picture Perfect 4.6 Enterprise E
- Page 114 and 115: 106Picture Perfect 4.6 Enterprise E
- Page 116 and 117: 108Picture Perfect 4.6 Enterprise E
- Page 118 and 119: 110Picture Perfect 4.6 Enterprise E
- Page 122 and 123: 114Picture Perfect 4.6 Enterprise E
- Page 124 and 125: 116Picture Perfect 4.6 Enterprise E
- Page 126: 118Picture Perfect 4.6 Enterprise E
112<strong>Picture</strong> <strong>Perfect</strong> <strong>4.6</strong> <strong>Enterprise</strong> <strong>Edition</strong><strong>User</strong> <strong>Manual</strong>23 hostconfig log file reported "SQL error" messagesThere are valid and benign SQL errors in the hostconfig.log file as a result of the serverconfiguration processes performed by hostconfig.Valid SQL error messages and explanations are listed below:908 - Cannot connect to local or remote database.This error can occur while starting the database and checking for its status during a subhost configuration.206 - Table does not exist.The error is commonly found when checking for <strong>Enterprise</strong> Replication status of a new subhost that is not yetconfigured in the system.674 - Dropping non-existent Stored Procedure.This error is found during installation of a new subhost, which is trying to create new a Stored Procedure, removingany previous record of the Stored Procedure in the database.634 - Dropping non-existent Trigger.This error is found during installation of a new subhost, which is trying to create new Trigger, removing any previousrecord of the Trigger in the database.8301 -Sequence object already exist.This error is reported in the hostconfig log, as a search for that particular error, to avoid creating a Sequenceobject that is already created in the database.Note:No other SQL error codes are allowed in the hostconfig.log.YYYYMMDDhhmmss file. If other errors are found, they should be reported for analysis.24 Do I have to change the Custom History Reports based on database schema changesmade in <strong>Picture</strong> <strong>Perfect</strong> <strong>4.6</strong>?Yes, all Custom History Reports are affected and must be reviewed and changed according to theHistory table unified schema listed in Table 10:Table 10. Database Schema Changes in <strong>Picture</strong> <strong>Perfect</strong> <strong>4.6</strong>Table Name OLD Column NEW Columnbadge_history area - integer area_desc - varchar(60)alarm_history input_group - integer ingrp_desc - varchar(60)micro - integermicro_desc - varchar(60)operator_his terminal - integer terminal_desc - varchar(60)tour_history tour_definition - integer definition_desc - varchar(60)alarm - integerarea - integertour_exception - integeralarm_desc - varchar(60)area_desc - varchar(60)exception_desc - varchar(60)
Change language