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 ...
88Picture Perfect 4.6 Enterprise EditionUser ManualCorrupted shared memoryWhen Picture Perfect is not running, there should be no message queues, shared memory, andsemaphores for TPS or Informix. If there are entries, then the shared memory is corrupted. Use thefollowing commands to clear the shared memory, semaphores, and message queues:ipcrm -q (removes Message Queue)ipcrm -m (removes Shared Memory)ipcrm -s (removes Semaphores)or ipcrm -q -m -s Informix error messagesFor more information regarding Informix error messages, use the command finderr. The syntaxof the command is:finderr -errornumberwhere errornumber is the number of the error message you received. You will thenreceive a short description of the problem which caused the error message.For example, you received the error number -908. Follow the steps below to determine the meaningof this error.1. At the # prompt, type: finderr -908The following message is displayed:-908 Attempt to connect to database server (servername) failed.The program or application is trying to access another database serverbut has failed. Note the server name in the current statement.The desired database server is unavailable, or the network is down oris congested. Ask your DBA and system administrator to verify that theserver and network are operational. If the network is congested, usethe environment variables INFORMIXCONTIME and INFORMIXCONRETRY to tuneconnection timing. For information on setting these environment variables,see the IBM Informix Guide to SQL: Reference.This message appears in Version 6.0 and later versions.
Chapter 6Troubleshooting and support89Enterprise Replication troubleshootingTroubleshooting a failed installationIf the installation of the Picture Perfect 4.6 Enterprise Edition failed, initiate troubleshooting byperforming the following steps:1. Pay attention to the messages printed on the screen.2. Check the following log files on the server that had a problem:- /custom_pp/log/latest.- /cas/log/hostconfig.log..3. Check the following log files on the nethost and the subhost that had a problem.- /cas/log/er.log- /cas/db/log/online.logFailed synchronization after installationUnder normal conditions, all hosts should be synchronized after installation. If chkdbsync reportsindicating that all hosts do not have identical data, perform the following steps:1. Look at the log files:- /cas/log/hostconfig.log.- /cas/db/log/online.log.Check if the host had a network disconnect or the host/database was down in the middleof the synchronization.2. Look for any collisions in the ATS/RIS directories /ppbackup/ats and /ppbackup/ris.Collisions may indicate that the initial synchronization was not successful.3. Run ercmd.sh --recover_allhosts using nethost as master.If this does not synchronize the data either, contact Customer Support.Incomplete synchronization due to a network outage during hostconfigIf a network outage occurred while hostconfig was running and the synchronization did notcomplete, run the command /cas/er/bin/ercmd.sh --removER on all subhosts that did notcomplete synchronization and then repeat the hostconfig.
- Page 46 and 47: 38Picture Perfect 4.6 Enterprise Ed
- Page 48 and 49: 40Picture Perfect 4.6 Enterprise Ed
- Page 50 and 51: 42Picture Perfect 4.6 Enterprise Ed
- Page 52 and 53: 44Picture Perfect 4.6 Enterprise Ed
- Page 54 and 55: 46Picture Perfect 4.6 Enterprise Ed
- Page 56 and 57: 48Picture Perfect 4.6 Enterprise Ed
- Page 58 and 59: 50Picture Perfect 4.6 Enterprise Ed
- Page 60 and 61: 52Picture Perfect 4.6 Enterprise Ed
- Page 62 and 63: 54Picture Perfect 4.6 Enterprise Ed
- Page 64 and 65: 56Picture Perfect 4.6 Enterprise Ed
- Page 66 and 67: 58Picture Perfect 4.6 Enterprise Ed
- Page 68 and 69: 60Picture Perfect 4.6 Enterprise Ed
- 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 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 120 and 121: 112Picture 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
Chapter 6Troubleshooting and support89<strong>Enterprise</strong> Replication troubleshootingTroubleshooting a failed installationIf the installation of the <strong>Picture</strong> <strong>Perfect</strong> <strong>4.6</strong> <strong>Enterprise</strong> <strong>Edition</strong> failed, initiate troubleshooting byperforming the following steps:1. Pay attention to the messages printed on the screen.2. Check the following log files on the server that had a problem:- /custom_pp/log/latest.- /cas/log/hostconfig.log..3. Check the following log files on the nethost and the subhost that had a problem.- /cas/log/er.log- /cas/db/log/online.logFailed synchronization after installationUnder normal conditions, all hosts should be synchronized after installation. If chkdbsync reportsindicating that all hosts do not have identical data, perform the following steps:1. Look at the log files:- /cas/log/hostconfig.log.- /cas/db/log/online.log.Check if the host had a network disconnect or the host/database was down in the middleof the synchronization.2. Look for any collisions in the ATS/RIS directories /ppbackup/ats and /ppbackup/ris.Collisions may indicate that the initial synchronization was not successful.3. Run ercmd.sh --recover_allhosts using nethost as master.If this does not synchronize the data either, contact Customer Support.Incomplete synchronization due to a network outage during hostconfigIf a network outage occurred while hostconfig was running and the synchronization did notcomplete, run the command /cas/er/bin/ercmd.sh --removER on all subhosts that did notcomplete synchronization and then repeat the hostconfig.
Change language