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

Picture Perfect 4.6 Enterprise EditionUser ManualP/N 460234010B • 3 November 2011

iiPicture Perfect 4.6 Enterprise EditionUser ManualChapter 4. Managing your network database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47Network host operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48Data synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48Subhost operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48Synchronizing the time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49Refreshing the database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50Refreshing database history tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51Enterprise Replication (ER) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51Enterprise Replication configuration and administration permissions . . . . . . . . . . . . . . . . . . . . . . .53Enterprise Replication installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53Enterprise Replication scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54Enterprise Replication conflict resolution and spooling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59Enterprise Replication backup/restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60Network alarm monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61Chapter 5. Verifying the configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63Verifying /etc/hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64Running chkenterprise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65Verifying permissions on nethost and subhosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68Verifying communications on the nethost . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69Verifying Picture Perfect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70Verifying Enterprise system setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73Verifying table IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75Verifying remote database access configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77Verifying hosts time synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79Running chkdbsync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79Running ercmd.sh --status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80Running ercmd.sh --list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84

iiiChapter 6. Troubleshooting and support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Remote database access diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Corrupted shared memory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Informix error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Enterprise Replication troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Troubleshooting a failed installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Failed synchronization after installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Incomplete synchronization due to a network outage during hostconfig . . . . . . . . . . . . . . . . . . . . . 89Network outage on one host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Details of differences reported by ercmd.sh --status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90ATS/RIS alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Alarm indicating ER database spaces at 90% capacity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Removal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Contacting technical support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Chapter 7. FAQs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Replication concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Installation and upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101ER monitoring and management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113Miscellaneous . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

ivPicture Perfect 4.6 Enterprise EditionUser Manual

iPrefaceThis document is designed to assist in the creation of a Picture Perfect TM Enterprise (network) systemfor your site. It includes information regarding the installation and configuration of the Enterprisenetwork host (also referred to as nethost, top level host, or master server) and subhosts, as well asmanagement of the Enterprise system.This document is intended for system administrators, business partners, or any personnelresponsible for installing Picture Perfect. The material in this document has been prepared forpersons responsible for system installation.These procedures should be performed by someone who has completed the Picture Perfect trainingcourse.Read these instructions and all ancillary documentation entirely before installing or operating thisproduct. The most current versions of this and related documentation may be found on our website.Note:A qualified service person, complying with all applicable codes should perform all required hardwareinstallation.Conventions used in this documentThe following conventions are used in this document:BoldItalicMenu items and buttons.Emphasis of an instruction or point; special terms.File names, path names, windows, panes, tabs, fields, variables, and other GUI elements.Titles of books and various documents.Blue italicMonospaceHyperlinks to cross-references, related topics, and URL addresses.Text that displays on the computer screen.Programming or coding sequences.Safety terms and symbolsThese terms may appear in this manual:CAUTION: Cautions identify conditions or practices that may result in damage to the equipment or other property.WARNING: Warnings identify conditions or practices that could result in equipment damage or serious personalinjury.

iiPicture Perfect 4.6 Enterprise EditionUser ManualRelated documentation• Picture Perfect 4.6 User Manual• Picture Perfect 4.6 Release Notes• Picture Perfect 4.6 Installation Manual• Picture Perfect 4.6 External Interface User Manual• Picture Perfect 4.6 Interface User Manual• Picture Perfect 4.6 Tables and Fields• Picture Perfect 4.6 Import/Export User Manual• Picture Perfect 4.6 Guard Tours User Manual• Picture Perfect 4.6 Redundant Edition User Manual• Picture Perfect 4.6 Imaging Installation Manual• Universal Badge Format (UBF) for Picture Perfect• Graphics Monitoring and Control User Manual• Credential Designer User Manual• Card Access Report Management Application (CARMA) for Picture Perfect 4.6

Chapter 1 Enterprise system overviewThis chapter includes information needed to plan and document theconfiguration of your Picture Perfect Enterprise system.In this chapter:Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Enterprise system configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 3

2Picture Perfect 4.6 Enterprise EditionUser ManualIntroductionA Picture Perfect Enterprise access control and security management system provides virtuallyunlimited scalability. It is a multi-server system, which consists of one network host (i.e., nethost) andtwo or more subhosts, up to a maximum of 31 subhosts. The server computers may be IBM pSeriesservers running the AIX operating system, or Intel/AMD PCs running the Red Hat Linux operatingsystem. They communicate over an Ethernet network using TCP/IP protocol. While all servers in thenetwork are on a LAN/WAN, the nethost communicates with each subhost, but subhosts do notcommunicate with each other.The nethost provides central administration and stores the history transactions for the entire system.Micro controllers are not attached to the nethost.The subhosts are essentially identical to normal stand-alone Picture Perfect systems except thatthey communicate with and can be configured from the nethost. Categories, Departments,Permission Group, Personnel Type, Facility, Badge Formats, etc., can be inserted/updated/deletedfrom any subhost. The modified data is saved to the local subhost and replicated to other subhoststhrough the nethost. If the nethost is down, data saved on the subhosts cannot be replicated to otherhosts, however, the data is still saved on the subhosts and the databases can be synchronized oncethe nethost is back in service.Note:If the nethost is not available and an end user wants to insert a Category in any subhost, an errordisplays indicating that the new Category cannot be inserted. Since the nethost provides new ids fornew category records, the insert cannot be completed if the nethost cannot be reached.An Enterprise system offers the following benefits:1. Centralized badge, person, and photo database2. Both local and centralized history transaction database for reporting3. Both local and centralized alarm monitoring4. Virtually unlimited reader capacity by adding subhosts as needed5. Geographic distribution and control of micro controllers, readers, and alarmsThe location of the servers (nethost, subhosts) can be determined by the customer. Some customerslocate the subhosts in geographically distributed areas. This is sometimes necessary if the networkhas limited bandwidth or weak points, and it is critical that the subhosts be located close to the microcontrollers. Other customers with very robust networks locate all the subhosts in one data centerbecause this makes IT maintenance and system upgrades easier.The installation procedures for a nethost, subhost, or a stand-alone system are similar. The key to asuccessful Enterprise system installation is planning and documenting your Enterprise systemtopology (the physical layout of your network, including the host names and addresses) andconfiguring the host with the same records on the nethost and on all subhosts. Some of the fieldswithin the records differ depending on whether the host is the nethost or a subhost.Note:Install and configure your Picture Perfect Enterprise system before installing any optional packages onthe subhosts and/or nethost. Some of the optional software packages perform special configurationsteps for Enterprise systems and require that the Enterprise system be operational before they areinstalled.

Chapter 1Enterprise system overview3Figure 1. Sample Enterprise system network diagramEnterprise system configurationBefore installing your Enterprise system, you should plan and document the configuration. The itemsthat must be considered for a successful configuration are described below.• Determine the number of subhosts required for your system. Assign host names and IPaddresses for all subhosts and for the nethost, and record this information. This information isrequested during the installation and configuration of the system.• Determine the number of workstations required for your system. At least one graphicalterminal is required. Assign host names and IP addresses for each workstation and recordthis information. For information on setting up your workstations, refer to the Picture Perfect4.6 User Manual.• Assess the needs of your system, determine the optimum sizes for the various databasetables, and document the information. Refer to the Picture Perfect 4.6 Installation Manual forinformation on database table sizing. In a Picture Perfect Enterprise system, the databaseson the nethost and all subhosts must be defined consistently. For example, parametersconcerning the use of features such as seed counter, must be the same on the nethost andall subhosts. The size of the badge and person tables on all hosts must be large enough tohold all badges and badge holders (persons) in the system. For each history table (alarm,badge, operator, and other optional packages), the size of the table on the nethost should, ata minimum, be larger than the largest subhost table and should be sized to maintain thecombined online history information from all subhosts for the desired time period (days,weeks, or months).

4Picture Perfect 4.6 Enterprise EditionUser Manual

Chapter 2 Installing the Picture PerfectEnterprise systemThis chapter covers the information needed to install your Picture PerfectEnterprise system.In this chapter:Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Installation overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Enterprise system software installation . . . . . . . . . . . . . . . . . . . . 7Installing the nethost. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Installing subhosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Configuring the system to recognize the subhosts . . . . . . . . 19Adding a new subhost or adding back a crashed or removed subhost after the network is configured . . . . . . . . . 23Enterprise system printer installation . . . . . . . . . . . . . . . . . . . . . 23

6Picture Perfect 4.6 Enterprise EditionUser ManualOverviewThe installation of a Picture Perfect Enterprise system is performed in two phases. First, a minimalset of packages is installed and configured to achieve a functional network environment based onthe planned configuration. Then, the optional add-on packages are installed on the subhosts and/orthe network host (i.e., nethost) as appropriate to provide the full capabilities of the system.Installation of optional add-on packages is covered in the respective manuals for those packages.This chapter covers the first phase of the installation and includes the following:• Installation overview• Enterprise system software installation• Enterprise system printer installationPrerequisitesVerify that the following prerequisites have been met. If necessary, refer to the Picture Perfect 4.6Installation Manual for instructions.• The Picture Perfect base package is installed on the nethost and all subhosts.- Refer to Prerequisites on page 7 before installing the base package on the nethost.• Additional software required:- netlan for the Enterprise system nethost only- subhost for the subhosts onlyInstallation overviewThe Enterprise system installation involves the following steps:1. Installing the nethosta. Install the netlan package on the nethost.b. Shut down and reboot the nethost.c. Update the host table on the nethost with subhost information.2. Installing subhostsa. Install the subhost package on each subhost.b. Shut down and reboot all subhosts.3. Configuring the system to recognize the subhostsa. Stop Picture Perfect on the subhost(s) being added to the network.b. Use the hostconfig utility on the nethost to add the subhosts to the network.c. Restart Picture Perfect (if it is down) on the nethost and all newly configured subhosts.d. Run chkenterprise on the nethost. Check the integrity of the installation using theother tools described in the Installation and upgrades section of Chapter 7, FAQs.

Chapter 2Installing the Picture Perfect Enterprise system74. Adding a new subhost or adding back a crashed or removed subhost after the networkis configureda. Update the host table on the nethost with subhost information.b. Install the subhost package on the new subhost.c. Shut down and reboot the new subhost.d. Stop Picture Perfect on the subhost and nethost.e. Use the hostconfig utility on the nethost to add the new subhost to the network.f. Restart Picture Perfect (if it is down) on the nethost and the new subhost.g. Run chkenterprise on the nethost.Enterprise system software installationInstalling the nethostPrerequisites• Before installing netlan, the Picture Perfect base package must be installed on the nethost.• Micro Table Settings: During the base installation, select the following settings at the prompts:The MICRO table can grow from 70 to 78 records.Is this acceptable (y/n)? [y]You need to change these settings. Type: nThe following message displays:Enter the initial number of records:Enter: 1The following message displays:Enter the maximum number of records:Enter: 1• Micro Relation Table Settings: During the base installation, select the following settings at theprompts:The MICRO RELATION table can grow from 6000 to 10000 records.Is this acceptable (y/n)? [y]You need to change these settings. Type: nThe following message displays:Enter the initial number of records:Enter: 100The following message displays:Enter the maximum number of records:Enter: 100

8Picture Perfect 4.6 Enterprise EditionUser ManualInstall the nethost after the base package has been installedTo install the netlan package on the nethost:1. Log on as ppadmin and open a terminal window.2. Type the following to shut down Picture Perfect:. /cas/bin/profilerc.pperf -k EnterEnter3. Switch users to root by typing the following command.su -EnterEnter your root password, and then press Enter .4. Insert the Picture Perfect 4.6 Installation DVD into your server. Wait for the DVD LED to stopblinking before proceeding.LinuxUnmount the DVD by typing the following command:umount /media/pp46EnterMount the DVD by typing the following command:mount /dev/dvd /mediaEnterAIXMount the DVD by typing the following command:mount -v cdrfs -r /dev/cd0 /mntEnter5. Change to the root directory by typing cd / Enter .6. To display a list of installation options, type:Linux/media/Linux/INSTALL -oEnterAIX/mnt/AIX/INSTALL -oEnterMessages similar to those shown below display, followed by a list of packages:----------------------------------------------------------------------Picture Perfect CD-ROM Installation - 4.6 04/01/11Copyright (C) 1989-2011 UTC Fire & Security Americas Corporation, Inc.----------------------------------------------------------------------The following BASE OPTIONS product(s) are available:Prod # Name and Descriptions------ ---------------------

Chapter 2Installing the Picture Perfect Enterprise system90 base Picture Perfect Base package1 graph Picture Perfect Graphics Monitoring and Control package2 image Picture Perfect Imaging package3 impexp Picture Perfect Import/Export package4 netlan Picture Perfect Network System - Host package5 pprs Picture Perfect Redundant System package6 subhost Picture Perfect Network System - Subhost package7 tours Picture Perfect Guard Tours packageEnter product number(s), separated by ',' to select, 'q' to quit:7. Type the corresponding product number, for example 4, to install the netlan package, andthen press Enter .You are asked to confirm your choice.You have selected the following product(s):4 netlan Picture Perfect Network System - Host packageIs this correct (y/n)? [y]8. To confirm, type: yEnterYou are asked to confirm the package.Installing netlan...Picture Perfect Multi-package Installation - 4.6 04/10/11Copyright (C) 1989-2011 UTC Fire & Security Americas Corporation, Inc.Installing from image in /media/Linux/pp ...Do you want to install the Picture Perfect NETLAN Package (y/n)? [y]9. To confirm, type: yEnterYou are asked to confirm the installation.Picture Perfect NLS Text Save - 4.6 01/16/11Copyright (C) 2000-2011 UTC Fire & Security Americas Corporation, Inc.Mon Aug 17 07:56:55 EDT 2011This package has no nls or help files to save...----------------------------------------------------------------------Picture Perfect Netlan Installation - 4.6 04/01/11Copyright (C) 1989-2011 UTC Fire & Security Americas Corporation, Inc.----------------------------------------------------------------------Installing this package will configure this server as a 'Network Host'.If this server is part of a Picture Perfect Enterprise System and thisserver is the network host, you should install this package.Are you sure you want to install the Netlan package (y/n)? [y]Type y Enter to continue or n Enter to abort the installation.Messages similar to the following are displayed as part of the installation process:Loading Picture Perfect Netlan files from /media/Linux/pp/packages/netlan...This may take a few minutes.Extracting files from media...

10Picture Perfect 4.6 Enterprise EditionUser ManualThe files have been read from the media.Generating RSA key, Enter 'y' for any overwrite prompts:Please keep the default file location when asked:Generating public/private rsa key pair.Your identification has been saved in /root/.ssh/id_rsa.Your public key has been saved in /root/.ssh/id_rsa.pub.The key fingerprint is:7b:bb:d6:17:ce:71:5d:2a:b8:fb:65:10:97:b1:2b:4f root@bctdoverStarting the Informix database.. DoneUpdating dictionary for network host version...Loaded report 'Netlan Operator History Report'.Loaded report 'Netlan Alarm History Report'.Loaded report 'Netlan Badge History Report'.Loaded report 'Netlan Operator History Archive Report'.Loaded report 'Netlan Badge History Archive Report'.Loaded report 'Netlan Alarm History Archive Report'.Inserting alarm entries for the host table...Updating System Administrator permission record...---- < additional output > ---[Done].[Done].Log Directories... o Creating ER Log directories ... [Done].[Done].Setting ‘sysadmin’ database connection...[Done].Setting up ntp Server to keep the hosts time in sync...The Netlan installation has completed successfully.Checking if need to update nls files...Picture Perfect NLS Check - 4.6 01/16/11Copyright (C) 2000-2011 UTC Fire & Security Americas Corporation, Inc.Mon Aug 17 07:58:49 EDT 2011No nls files for netlan packageRunning /cas/bin/fixperm on /tmp/netlan.perm file...No errors detected/cas/bin/fixperm finished.Installing desired BASE_OPTIONS product(s) was successful.The INSTALLation has completed.The system needs to be rebooted for the changes to take effect.Reboot the system (y/n)? [y]The host installation of netlan is now complete.Note:Permissions for the default System Administrator record are automatically set up during installation. Ifyou have additional records requiring system administrator permissions, refer to Chapter 5, Verifying theconfiguration to verify the settings.

Chapter 2Installing the Picture Perfect Enterprise system11Update the host table on the nethost with subhost informationThe host table is the main feature of the Enterprise system. Each host in the system must have ahost record for itself and for each subhost. Use the Hosts form to create these records.The host table has a default host entry. Modify the host table entries only on the nethost. Thehostconfig program (described in Configuring the system to recognize the subhosts on page 19)automates this process for the subhosts.To create host records:1. If you are currently logged on as ppadmin and Picture Perfect is not running, from thecommand prompt, type the following to start Picture Perfect:rc.pperfEnter2. From a client workstation, log on to Picture Perfect as install.3. From the Picture Perfect primary navigation menu, select Control, then Hosts.4. Complete the Hosts form for the nethost and each subhost in the Enterprise system.Figure 2. Sample Hosts FormThe Hosts form should be completed on the nethost and should include entries for itself and eachsubhost in the system. For instance, if you have a nethost and two subhosts, the host table shouldhave three Hosts records. Some fields on the Hosts form are completed differently when the formrefers to the nethost rather than to the subhosts. Refer to Table 2, Control Host Settings on page 13.

12Picture Perfect 4.6 Enterprise EditionUser ManualTable 1.FieldHosts Form Fields and ControlsDescriptionHost NamePort AddressIP AddressAlternate IP AddressRetriesRetry IntervalPoll PeriodStartup ModeConfigure HostFacilityType the Internet host name for the host. Since this field is case-sensitive and must match theTCP/IP entry, be consistent with your capitalization. Use lowercase characters; up to 64alphanumeric characters are permitted to allow for full domain names. For example, the following line would appear in the /etc/hosts file:192.9.200.1 zeus zeus.support.casi.com #Network Host in supportThis example sets up the alias zeus.support.casi.com for the nethost zeus found ataddress 192.9.200.1.In this case, either zeus or zeus.support.casi.com could be used for the host name entry.Enter a unique number, in the range of 6101 to 9999, for each host. The number must be the samefor a given host across the entire Enterprise system. Numbers below 6101 are reserved.The port address entered is validated against the ports already in use in the /etc/servicesfile.• If the port is available, it is entered into the /etc/services file.• If it is in use, the host record save will fail.This is the Internet address as defined in the /etc/hosts file. For example:192.9.200.1 zeus zeus.support.casi.com #Network Host in supportIn the example above, 192.9.200.1 is the IP address.This field is used for Redundant systems. It must be left blank for Enterprise systems.Enter the number of times a message between hosts will be sent before a host-to-host alarm isgenerated.Recommendation: Enter 3.Enter the number of seconds Picture Perfect waits before retrying a message between the hostand subhost.Recommendation: Enter 20.Enter the number of seconds Picture Perfect waits between polls. If this is set to 0, TPS neverpolls this host and host-to-host communication failures may not be detected.Recommendation: Enter 60.Click the appropriate radio button:• On the nethost, select Listen for all subhost records.• For its own nethost record, this field should be set to Disable.For more information, refer to Table 2 on page 13.This field determines whether a subhost will attempt to talk to the host. Click the appropriate radiobutton:• On the nethost, select Online for all subhost records.• For its own nethost record, this field should be set to Offline.For more information, refer to Table 2 on page 13.Click Facility to display the facilities list box. This field reflects the facility to which this record isassigned.

Chapter 2Installing the Picture Perfect Enterprise system13Table 1.FieldHosts Form Fields and Controls (continued)DescriptionHost to HostCommunicationsFailureRemote DatabaseAccess Error InputGroupIf you want to be notified of host-to-host communication failures, an input group must be assignedfor each of the subhost records on the nethost. Click Host-Host Comm Failure to display a list boxof input groups. Select the default input group created for you during installation, then click Close.Note: An input group should be assigned only for the subhost records, not for the nethostrecord.This step should be performed on the nethost, not on the subhost.For more information, refer to Table 2 on page 13.If you want to be notified of a remote database access error, an input group must be assigned foreach of the subhost records on the nethost. Click Remote Database Connectivity Error to display alist box of input groups. Select the default input group created for you during installation, then clickClose.Note: An input group should be assigned only for the subhost records, not for the nethostrecord.This step should be performed only on the nethost, not on the subhost.For more information, refer to Table 2 on page 13.5. Click Save.6. Click New and complete the form to add each subhost record.7. When you have finished, log off of Picture Perfect.Table 2.Control Host SettingsWhen Performed from: Host Record Startup Mode Configure HostHost-to-Host Comm FailureRemote DatabaseConnection ErrorNethost own Disable Offline Blank BlankSubhosts Listen Online Assign Input Group Assign Input GroupSubhost own Disable Offline Blank BlankOther subhosts Disable Offline Blank BlankNethost Connect Online Blank or Assign Input GroupBlankShut down and reboot the nethostTo shut down and reboot the nethost:1. Log on to the nethost as root, and then open a terminal window.2. From the command prompt, type:AIXshutdown -Fr nowEnterLinuxrebootEnter

14Picture Perfect 4.6 Enterprise EditionUser ManualInstalling subhostsPrerequisitesBefore installing the subhost package, the Picture Perfect base package must be installed on thesubhost.Install the subhost package on each subhost after the base package has been installedTo install the subhost package on a subhost:1. Log on as ppadmin and open a terminal window.2. Type the following to shut down Picture Perfect:. /cas/bin/profilerc.pperf -k EnterEnter3. Switch users to root by typing the following command.su -Enter your root password and then press Enter .4. Insert the Picture Perfect 4.6 Installation DVD into your server. Wait for the DVD LED to stopblinking before proceeding.LinuxUnmount the DVD by typing the following command:umount /media/pp46EnterMount the DVD by typing the following command:mount /dev/dvd /mediaEnterAIXMount the DVD by typing the following command:mount -v cdrfs -r /dev/cd0 /mntEnter5. Change to the root directory by typing cd / Enter .6. To display a list of installation options, type:Linux/media/Linux/INSTALL -oEnterAIX/mnt/AIX/INSTALL -oEnterMessages similar to those shown below display, followed by a list of packages:

Chapter 2Installing the Picture Perfect Enterprise system15----------------------------------------------------------------------Picture Perfect CD-ROM Installation - 4.6 04/01/11Copyright (C) 1989-2011 UTC Fire & Security Americas Corporation, Inc.----------------------------------------------------------------------The following BASE OPTIONS product(s) are available:Prod # Name and Descriptions------ ---------------------0 base Picture Perfect Base package1 graph Picture Perfect Graphics Monitoring and Control package2 image Picture Perfect Imaging package3 impexp Picture Perfect Import/Export package4 netlan Picture Perfect Network System - Host package5 pprs Picture Perfect Redundant System package6 subhost Picture Perfect Network System - Subhost package7 tours Picture Perfect Guard Tours packageEnter product number(s), separated by ',' to select, 'q' to quit: 7. Type the corresponding product number, for example 6, to install the subhost package andpress Enter .You are asked to confirm your choice.You have selected the following product(s):6 subhost Picture Perfect Network System - Subhost packageIs this correct (y/n)? [y]8. To confirm, type: yEnterYou are asked to confirm the installation.Installing subhost...Picture Perfect Multi-package Installation - 4.6 04/10/11Copyright (C) 1989-2011 UTC Fire & Security Americas Corporation, Inc.Installing from image in /media/Linux/pp ...Do you want to install the Picture Perfect SUBHOST Package (y/n)? [y]9. To confirm, type: yEnterMessages similar to the following display and you are asked if you wish to continue theinstallation:Picture Perfect NLS Text Save - 4.6 01/16/11Copyright (C) 2000-2011 UTC Fire & Security Americas Corporation, Inc.Mon Aug 17 09:59:21 EDT 2011This package has no nls or help files to save...----------------------------------------------------------------------The Picture Perfect Subhost Installation - 4.6 04/10/11Copyright (C) 1989-2011 UTC Fire & Security Americas Corporation, Inc.----------------------------------------------------------------------Installing this package will configure this server as a 'Network Subhost'.If this server is part of a Picture Perfect Enterprise system and this

16Picture Perfect 4.6 Enterprise EditionUser Manualserver is not the network host, you should install this package.Are you sure you want to install the Subhost package (y/n)? [y]10. Type y Enter to continue or n Enter to abort the installation.The following messages are displayed as part of the installation process:Loading Picture Perfect Subhost files from /media/Linux/pp/packages/subhost...This may take a few minutes.Extracting files from media...The files have been read from the media.Starting the Informix database.. Done.Enter the hostname of the network host ..........: bctdoverNetwork host name is.............................: bctdoverIs this correct (y/n)? [y]11. As prompted, enter the host name for the nethost.Messages similar to the following display:Enter the IP address for the network host.....: [192.9.200.100]Network host IP address is....................: 192.9.200.100Is this OK (y/n)? [y]12. As prompted, enter the IP address for the nethost.Messages similar to the following display:You specified:==============Host name of Network Host............: bctdoverIP address of Network Host...........: 192.9.200.100Is this correct (y/n)? [y]13. Type y to confirm the IP address and the nethost name.Depending on the SSH configuration of your network, steps 16 – 19 may or may not be needed.14. A message similar to the following displays:The authenticity of host ‘bctdover (192.9.200.100’ can’t be established.RSA key fingerprint is f4:b0:ca:d6:2e:c0:44:ff:a9:85:ce:0c:e3:40:8a:7b.Are you sure you want to continue connecting (yes/no)?15. Type yes Enter to continue. You are prompted with the following:root@bctdover's password:16. As prompted, enter the root password of the nethost.Messages similar to the following display:

Chapter 2Installing the Picture Perfect Enterprise system17Starting Secure Shell (SSH) configuration...Generating RSA key, Enter ‘y’ for any overwrite prompts:Please keep the default file location when asked:Generating public/private rsa key pair.Your identification has been saved in /root/.ssh/id_rsa.Your public key has been saved in /root/.ssh/id_ras.pub.The key fingerprint is:e(:a3:e0:b3:56:35:1b:fa:0d:cd:22:1c:09:28:f5:ed root@bctalfordTransferring public key to remote host bctdoverKey in ‘yes’ for ‘continue connecting’ promptsEnter root password for ‘bctdover, when asked for it.root@bctdover’s password:17. As prompted, enter the root password of the nethost.Messages similar to the following display:Transferring and enable remote host bctdover public key to local hostbctalfordSecure Shell (SSH) has been configured successfullyNOTE: Please run “. /cas/bin/profile” after installation has completed.Make sure you do this before running any commands.Press enter to continue...18. As prompted, press Enter .Messages similar to the following display:Inserting alarm entries for the host table...Updating System Administrator permission record...Setting up ntp client to keep the hosts time in sync...Informix onconfig file... [Done].ER database spaces... o Configuring ER DB Space in [rootvg]...Creating entrepdbs logical volume.... [Done].Adding entrepdbs to the database... [Done].Creating entrepsbs logical volume.... [Done].Adding entrepsbs to the database... [Done].[Done].[Done].Log Directories... o Creating ER Log directories ... [Done].[Done].Setting ‘sysadmin’ database connection...[Done].Updating Stats for alarm table ... [Done]Updating Stats for facility_rec_prof table ... [Done]Updating Stats for input_group table ... [Done]Updating Stats for operator table ... [Done]Updating Stats for permission table ... [Done]Updating Stats for system_config table ... [Done]Updating Stats for tps_daemons table ... [Done]Shutting down the Informix database. Done.The Subhost package has been successfully installed.

18Picture Perfect 4.6 Enterprise EditionUser ManualTo complete the installation, this Subhost must be added to thePicture Perfect Enterprise system by running the '/cas/bin/hostconfig'utility on Network host.Checking if need to update nls files...Picture Perfect NLS Check - 4.6 04/25/11Copyright (C) 1989-2011 UTC Fire & Security Americas Corporation, Inc.Thu May 26 13:23:39 EDT 2011Picture Perfect NLS Text Update - 4.6 04/16/06Copyright (C) 1989-2011 UTC Fire & Security Americas Corporation, Inc.Thu May 26 13:23:39 EDT 2011This package has no nls or help files to update, so going to buildlanguage resourcesBuilding en_US ...NLS Text Update FinishedRunning /cas/bin/fixperm on /tmp/subhost.perm file...No errors detected/cas/bin/fixperm finished.Installing desired BASE_OPTIONS product(s) was successful.The INSTALLation has completed.The system needs to be rebooted for the changes to take effect.Reboot the system (y/n)? [y] 19. To reboot, type: y Enter Remember to remove the installation media following the reboot.The installation of the subhost package is now complete.Note:Permissions for the default System Administrator record are automatically set up during installation. Ifyou have additional records requiring system administrator permissions, refer to Chapter 5, Verifying theconfiguration to verify the settings.Shut down and reboot all subhostsTo shut down and reboot:1. Log on to the system as root and open a new terminal window.2. From the command prompt, type:AIXshutdown -Fr nowEnterLinuxrebootEnter

Chapter 2Installing the Picture Perfect Enterprise system19Configuring the system to recognize the subhostsAfter installing the Picture Perfect subhost package and rebooting the subhost, the Enterprisesystem must be configured to include this subhost. This is done from the nethost.Prerequisites• The netlan package must be installed on the nethost.See Installing the nethost on page 7.• The subhost package must be installed on the subhosts.See Installing subhosts on page 14.• Make sure that all subhost records have been created on the Hosts form. See Update thehost table on the nethost with subhost information on page 11.Using the hostconfig utility on the nethost to add the subhosts to the networkNote: Picture Perfect must NOT be running on the subhosts before running the hostconfig utility.To add the subhosts to the network:1. As user ppadmin, stop Picture Perfect on all subhosts being added to the network by typing:rc.pperf -kEnter2. If not already logged on, log on as ppadmin on the nethost and open a new terminalwindow.3. If this is a new installation, stop Picture Perfect by typing:rc.pperf -kEnterIf you already have your system configured and are running hostconfig again toreconfigure a subhost (for example, after a crash), you might not need to stop PicturePerfect. In this case, perform this step only if requested by hostconfig.4. Switch users to root by typing the following command.su -Enter your root password and then press Enter .5. At the command prompt, type:. /cas/bin/profilehostconfig EnterEnterThe nethost and all subhosts are updated. Messages similar to the following display:----------------------------------------------------------------------Picture Perfect hostconfig utility - Version 4.6 04/10/11Copyright (C) 1989-2011 UTC Fire & Security Americas Corporation, Inc.----------------------------------------------------------------------Starting the Informix database.. Done.Checking sqlhosts file... Processing [bctdover]

20Picture Perfect 4.6 Enterprise EditionUser ManualUpdating sqlhosts file for [bctdover]...dbservername bctdover already in sqlhosts fileUpdating hcomm_ingrp field on host table... [Done].Updating istar_ingrp field on host table...Checking for replication status... [Done].Configuring sqlhost file for ER... [Done].Configuring remote sqlhosts file(s) for ER... [Done].Configuring Sequence Objects.... [Done].Initializing ‘currseq’ table.... [Done].Configuring Primary Keys and CR Column.... [Done].Configuring Stored Procedures for ER... [Done].Configuring Triggers for ER... [Done].Configuring Enterprise Replication Server.... [Done].Configuring Enterprise Replication Replicates.... [Done].Configuring Enterprise Replication Schedules Task(s)... [Done].Processing [bctalford]The authenticity of host ‘bctalford (192.9.200.100’ can’t be established.RSA key fingerprint is e9:8c:d6:ba:4e:50:aa:c1:39:88:47:21:87:92:93:67.Are you sure you want to continue connecting (yes/no)?6. Type yes Enter to continue.If SSH is not configured for any of the subhosts being configured, a message similar tothe following displays:.WARNING:SSH is not set up between Net Host [bctdover] and [bctalford].o Please run ‘config_ssh bctalford’ from bctdover server and run hostconfig one more time.[FAILED] to process hostconfig on [bctalford’ sever.Process of database synchronization...WARNING: Depending on the server database synchronizationstatus, this process can take several minutes.Please wait...o Processing [bctdover]... [Skipping] nethost.[Done] Synchronizing databases.There were problems configuring hosts. Check /cas/log/hostconfig.log[root@bctdover ~]#7. Type the config_ssh command as instructed in the warning message above:config_ssh bctalfordMessages similar to the following display:Starting Secure Shell (SSH) configuration...Generating RSA key, Enter ‘y’ for any overwrite prompts:Please keep the default file location when asked:Transferring public key to remote host bctalfordKey in ‘yes’ for ‘continue connecting’ promptsEnter root password for bctalford, when asked for it.id_rsa.pub 100% 395 0.4KB/s 00:00Enabling public key on remote host bctalfordEnter root password for bctalford, when asked for it.

Chapter 2Installing the Picture Perfect Enterprise system21Transferring and enabling remote host bctalford public key to local hostbctdoverSecure Shell (SSH) has been configured successfullyNOTE: Please run “. /cas/bin/profile” after installation has completed.Make sure you do this before running any commands.Press enter to continue...8. Press Enter and type the following commands:. /cas/bin/profilehostconfig EnterEnterMessages similar to the following display:----------------------------------------------------------------------Picture Perfect hostconfig utility - Version 4.6 04/25/2011Copyright (C) 1989-2011 UTC Fire & Security Americas Corporation, Inc.----------------------------------------------------------------------Checking sqlhosts file... bctalford[*]Processing [bctdover]Server [bctdover] already set up for ER... [skipping].Processing [bctalford]Service and port were okayChecking for [bctalford] database.... Starting up, please wait .... [Done].Updating sqlhosts file for [bctalford]...Stopping Informix database to update sqlhosts with subhost‘bctalford’..[Done].Starting the Informix database.. [Done].Copying .netrc to bctalford ppadmin and ppapp home directories [Done].Updating hcomm_ingrp field on host table...Checking for replication status... [Done}.Configuring sqlhost file for ER... [Done].Configuring remote sqlhosts file(s) for ER... [Done].Configuring Sequence Objects.... [Done].Initializing ‘currseq’ table.... [Done].Configuring Primary Keys and CR Column.... [Done].Configuring Stored Procedures for ER... [Done].Configuring Triggers for ER... [Done].Bouncing bctdover and bctalford databases to set changes. Please wait......[Done].Configuring Enterprise Replication Server... [Done].Configuring Enterprise Replication Replicates.... [Done].Configuring Enterprise Replication Scheduled Task(s).... [Done].Process of database synchronization...WARNING: Depending on the each server database synchronizationstatus, this process can take several minutes.please wait...o Processing [bctdover]... Already setup for ER [Skipping]o Processing [bctalford]...Recovering [bctalford] server... [FLAGS: SD SD SK]Table Name Records Rem. Time================================= ========== ==========o category: ....................... [ 2] 11:17:52 11:17:53o facility: ....................... [ 1] 11:17:53 11:17:54o person_type: .................... [ 4] 11:17:54 11:17:55

22Picture Perfect 4.6 Enterprise EditionUser Manualo department: ..................... [ 0] 11:17:55 11:17:55o permission_group: ............... [ 2] 11:17:55 11:17:58o host_bid_format: ................ [ 3] 11:17:58 11:17:59o custom_form: .................... [ 85] 11:17:59 11:18:01o custom_list_elem: ............... [ 0] 11:18:01 11:18:02o site_lists: ..................... [ 0] 11:18:02 11:18:03o form_tab: ....................... [ 164] 11:18:03 11:18:05o custom_control: ................. [ 816] 11:18:05 11:18:06o custom_control_arg: ............. [ 5237] 11:18:06 11:18:08o time_zone: ...................... [ 504] 11:18:08 11:18:10o time_zone_dst: .................. [ 1381] 11:18:10 11:18:11o notes: .......................... [ 0] 11:18:11 11:18:12o temp_category: .................. [ 0] 11:18:12 11:18:13o person_category: ................ [ 0] 11:18:13 11:18:14o person_user: .................... [ 0] 11:18:14 11:18:15o badge: .......................... [ 0] 11:18:15 11:18:16o person: ......................... [ 0] 11:18:16 11:18:17Resynching sequences at [bctalford] server... [Done]>[bctalford] synch. process [Done] [Done] Synchronizing databases.All host configured successfully.Note:The hostconfig command updates the nethost and all subhosts, including the one just installed. If anyhosts cannot be reached over the Enterprise system, the problems are recorded in the file /cas/log/hostconfig.log.. If hostconfig reports success, all hosts now contain theinformation about the new host and the Enterprise system can communicate with the new host.Restart Picture Perfect on the nethost and all subhostsTo restart Picture Perfect:1. Log on to each host as ppadmin and open a new terminal window.2. From the command prompt, type:. /cas/bin/profilerc.pperf EnterEnterThe following messages display:Picture Perfect - starting database... [OK].Picture Perfect - starting transaction processor...Using CATALINE_BASE: /var/www/apache-tomcatUsing CATALINE_HOME: /var/www/apache-tomcatUsing CATALINE_TMPDIR: /var/www/apache-tomcat.tempUsing JRE_HOME:/usr/java/defaultUsing CLASSPATH: /var/www/apache-tomcat/bin/bootstrap.jarYour system should now be ready. Your nethost and subhost should be communicating.To verify the Picture Perfect Enterprise configuration, refer to Chapter 5, Verifying the configurationand run the Running chkenterprise utility.

Chapter 2Installing the Picture Perfect Enterprise system23Adding a new subhost or adding back a crashed or removed subhost after the network is configuredWhen a new subhost is added to an existing network configuration, the subhost package isinstalled on the new subhost. Then the Enterprise system is configured to include this subhost.PrerequisitesBefore installing subhost, the Picture Perfect base package must be installed on the subhost.Update the host table on the nethost with subhost informationRefer to Update the host table on the nethost with subhost information on page 11.Install the subhost package on the new subhostRefer to Install the subhost package on each subhost after the base package has been installed onpage 14.Shut down and reboot the new subhostRefer to Shut down and reboot all subhosts on page 18.Use the hostconfig utility on the nethost to add the new subhost to the networkRefer to Using the hostconfig utility on the nethost to add the subhosts to the network on page 19.Restart Picture Perfect on the nethost and all subhostsRefer to Restart Picture Perfect on the nethost and all subhosts on page 22.Your system should now be ready. Your nethost and subhost should be communicating.To verify the Picture Perfect Enterprise configuration, refer to Chapter 5, Verifying the configurationand run the Running chkenterprise utility.Enterprise system printer installationIn an Enterprise system with more than one host, AIX and Linux can be configured to forward printrequests from one host to another. This makes it possible for all hosts to use a single printer attachedto one host, or for a single host to print to many printers attached to different hosts. Before setting upEnterprise system printing, define all printers locally, at the host to which they are physicallyattached.Refer to the Picture Perfect 4.6 Installation Manual for instructions on configuring your system forprinters.

24Picture Perfect 4.6 Enterprise EditionUser Manual

26Picture Perfect 4.6 Enterprise EditionUser ManualIntroductionThe purpose of the process described in the following sections is to upgrade a Picture PerfectEnterprise Edition version 4.0 or 4.5.1 to version 4.6. At the end of the process, all servers areinstalled with the new version, are communicating, and are synchronizing global data records withthe network host server (also referred to as nethost, top level host, or master server).PrerequisitesThe following items have to be in place before proceeding with the upgrade of Picture Perfect 4.0/4.5.1 to 4.6 (also refer to Picture Perfect 4.6 Installation Manual, Chapter 3, “Upgrade checklist forPicture Perfect v4.0 to v4.6”):1 Media kit Picture Perfect media kit 4.6.2 Licenses Save a copy of the Picture Perfect 4.0 or 4.5.1 licenses (/cas/.PP.key) for those serversthat need to be upgraded and request new Picture Perfect 4.6 licenses from UTC Fire &Security. If you are currently running Picture Perfect 4.5.1, you can re-use the licenses forPicture Perfect 4.6; no new licenses are required.3 Database table sizes Keep a copy of the database sizes as a reference and to serve as a foundation to grow thesystem. The table size information can be found in the following files:/cas/db/backup/table_size.dat (table sizes with reference to table IDs)/cas/db/backup/table_desc.dat (table names with reference of table IDs).4 Database and microcontroller dataintegrity5 Target server OSinstallationTo expedite the upgrade and avoid any inconvenience during the database conversionprocess, we recommend running the following utilities:/cas/bin/chkchars.sh This utility reports any Picture Perfect illegal characters./cas/bin/vmicroThis utility reports any micro table misconfigurations.If you are planning to reuse or provide new servers to install Picture Perfect 4.6, make surethe operating system version installed is Linux Red Hat 5.6 for Dell servers or AIX version 6.1TL6 for IBM RISC servers.6 Server connectivity Make sure all servers participating in the upgrade process are connected to the network andreachable from each other.If optional spare servers are used, make sure they can connect to the source (old version)and target (new version) servers, since we will be transferring data files back and forth.7 Database freeze Once the upgrade process has begun, we strongly recommend to stop making changes tothe database servers. This assures minimum impact to database synchronization between allservers during the installation. If, however, database changes (not related to Historytransactions) are required during the upgrade time, these changes must be written down sothat they can be applied in the new system with replication and synchronization.Note: Please see section FAQs on page 97 for more detail.8 Micro controllermaintenanceThe minimum micro firmware versions required with Picture Perfect 4.6 are as follows:Micro 5/PXN: 4.0.3Micro 5/PXN+: R113Direct Door: R113Note: We strongly recommend using the currently shipped micro controller hex codeversion.

Chapter 3Upgrading Picture Perfect version 4.0/4.5.1 to 4.6279 Optional:RecommendedSpare servers fordatabase conversion10 Optional:Upgrade from AIX toLinuxTo allow the current system to continue in production, expedite the conversion process, andminimize down time, two Spares, properly sized to hold the current databases, are highlyrecommended.For this item, Picture Perfect 4.0 Service Pack 3 Quick Fix 9 must be available.Check the port table max(id) values. The limits are 2000 for AIX and 1024 for Linux.11 Server readiness After nethost and subhosts are installed with netlan and subhost respectively, all serversconfigured in the host table (GUI host form), must be available (ping, ssh and databaseready), before running hostconfig. Otherwise, hostconfig will not let you proceed.Note:If there is a reason to have a server down while running hostconfig, remove thatserver from the installation by removing it temporarily from the host table (GUI hostform).System layoutFigure 3. Picture Perfect Enterprise System Layout

28Picture Perfect 4.6 Enterprise EditionUser ManualUpgrade version 4.0 to 4.6 with no spare serversOnce all item listed under Prerequisites are in place, follow the steps below to upgrade your PicturePerfect 4.0 Enterprise system to version 4.6.Note:The nethost server must be the first server to be upgraded to the new version.A. Determine the downtime schedule and inform all operators of the downtime schedule(database freeze schedule)The downtime can be estimated based on the size of the database to be converted and otherfactors, such as the time to reinstall the new OS version if reusing the same servers and latencybetween nethost and subhost to be configured.In a scenario with a database containing 500K person records, no network latency, re-using thesame servers requiring OS installation, we can calculate a downtime between 4 to 6 hours perserver. For a server experiencing network latency, add two to four hours to this time. For AIXservers, add at least one hour.Note:This estimate does not include getting the micro controllers back online with the server.B. Picture Perfect nethostB.1 Database conversion process1. Log in to the current Picture Perfect 4.0 nethost server.2. Record the old server database sizes (person, badge, notes, all history, micro, category,department, and micro_relation tables).This information can be compiled from the following files:/cas/db/backup/table_desc.dat (for references to table name and id)/cas/db/backup/table_size.dat (for table record sizes based on table id)3. Check the database for illegal characters and fix any reported issues.Follow the instructions in Picture Perfect 4.0 Installation Manual, Chapter 3, “Verify theExisting Database".4. Back up the database in the current production system before the upgrade of base, badgeand other packages where applicable (image, tours, graph) with contents verification.Preferably, back up in separate files for each item (for example, one file with base and badge,one file with images, etc.).Follow the instructions in Picture Perfect 4.0 Installation Manual, Chapter 3, “Back upDatabase, Configuration, and Custom Files".5. Perform the Backup > History archive to Disk File task and then repeat the same scenariowith Force Roll Over option into another file to capture all existing history data.Follow instructions in Picture Perfect 4.0 Installation Manual, Chapter 3, “Back upDatabase, Configuration, and Custom Files”, section “Archive History and ForceRollover".

Chapter 3Upgrading Picture Perfect version 4.0/4.5.1 to 4.6296. Back up the information needed by the OS, such as server IP addresses in files like /etc/hosts.7. Stop Picture Perfect.Follow the instructions in Picture Perfect 4.0 Installation Manual, Chapter 3, “Verify theExisting Database”, section “Shut Down Picture Perfect".8. Start the database conversion processNote:Be aware that after the conversion is done, Picture Perfect will not be able to communicate with thedatabase.a. Install the Picture Perfect 4.6 conversion utilities (INSTALL -c).Follow the instructions in Picture Perfect 4.6 Installation Manual, Chapter 3,“Upgrade”, section “Installing the database conversion utility".b. Execute the database conversion and follow the instructions to perform a backup for thetarget-converted database.Follow the instructions in the Picture Perfect 4.6 Installation Manual, Chapter 3,“Upgrade”, section “Running the conversion utility".c. Transfer the converted database to a safe place (PC or another server), since the currentserver will be used for the target installation.B.2 Picture Perfect 4.6 server installation1. Log in to the target server.2. Install the OS (AIX or Linux).Follow the instructions in Picture Perfect 4.6 Installation Manual, Chapter 4 or 5,depending on your server type (AIX or Linux).3. Prepare the server for Picture Perfect 4.6 (phase 2).Follow the instructions in Picture Perfect 4.6 Installation Manual, Chapter 6, “InstallingPicture Perfect 4.6”, section “Running the pre-installation setup".4. Find out if the customer requires installation of IT security/OS hardening tools and proceedaccordingly.5. Perform the Picture Perfect base package installation.Follow the instructions in Picture Perfect 4.6 Installation Manual, Chapter 6, “InstallingPicture Perfect 4.6”, section “Installing the Picture Perfect base package".Note 1: Set up database sizes according to old retrieved sizes as described in Prerequisites on page 26, item 3,Database table sizes, plus expected growth and new history sizes where applicable.Note 2: Restore the base and badge converted database.6. License the system.7. DO NOT REBOOT. This prevents Picture Perfect from starting up and attempting to connectto other servers.

30Picture Perfect 4.6 Enterprise EditionUser Manual8. Perform a database cleanup to remove old host records and make sure the id of the systemconfiguration record is correct. Use the following steps:a. Set the Picture Perfect 4.6 profile.. /cas/bin/profileb. Start up the database by running the command:su - ppadmin -c oninitc. Remove all host records by running the command:/cas/bin/sqlstmt "DELETE FROM host"d. Reset the system config record id to 1:/cas/bin/sqlstmt "UPDATE system_config SET id = 1"e. Stop the database by running the command:su - ppadmin -c "onmode -ky"9. Perform the optional package installation (netlan, impexp, image), restore the database(s)where applicable, and reboot the server when requested.Follow the instructions in Picture Perfect 4.6 Installation Manual, Chapter 6, “InstallingPicture Perfect 4.6”, section “Installing optional packages and interfaces".C. Picture Perfect subhost(s)C.1 Database conversion process1. Log in to the current Picture Perfect 4.0 subhost server.2. Record the old server database sizes (person, badge, notes, all history, micro, category,department, and, micro_relation tables).This information can be compiled from the following files:/cas/db/backup/table_desc.dat (for reference to table name and id)/cas/db/backup/table_size.dat (for table record sizes based on table id)3. Check the database for illegal characters and fix any reported issues.Follow the instructions in Picture Perfect 4.0 Installation Manual, Chapter 3, “Verify theExisting Database”, section “Check for Illegal Characters in the Database".4. Check the micro configuration and fix any reported issues.Follow the instructions in Picture Perfect 4.0 Installation Manual, Chapter 3, “Verify theExisting Database”, section “Check Micro Configuration".5. Back up the database in the current production system before the upgrade of base, badge,and other packages where applicable (image, tours, graph) with contents verification.Preferably, back up in separate files for each item (one file with base and badge, one file withimages, etc.).Follow the instructions in Picture Perfect 4.0 Installation Manual, Chapter 3, “Back upDatabase, Configuration, and Custom Files”, section “Back up Database.”

Chapter 3Upgrading Picture Perfect version 4.0/4.5.1 to 4.6316. Perform the Backup > History archive to Disk File task and then repeat the same scenariowith Force Roll Over option into another file to capture all existing history data.Follow the instructions in Picture Perfect 4.0 Installation Manual, Chapter 3, “Back upDatabase, Configuration, and Custom Files”, section “Archive History and ForceRollover.”7. Back up the information needed by the OS, such as micro and server IP addresses in fileslike /etc/hosts.8. Back up the tty configuration for interfaces, if any.To perform this task, back up the map files located in the /cas/db/text directory.9. Stop Picture Perfect.Follow the instructions in Picture Perfect 4.0 Installation Manual, Chapter 3, “Verify theExisting Database”, section “Shut Down Picture Perfect.”10. Start the database conversion process:Note:Be aware that after the conversion is done, Picture Perfect will not be able to communicate with thedatabase.a. Install the Picture Perfect 4.6 conversion utilities (INSTALL -c).Follow the instructions in Picture Perfect 4.6 Installation Manual, Chapter 3,“Upgrade”, section “Installing the database conversion utility".b. Execute the database conversion and follow instructions to perform a backup for thetarget-converted database.Follow the instructions in Picture Perfect 4.6 Installation Manual, Chapter 3,“Upgrade”, section “Running the conversion utility.”c. Back up the converted database as required by the conversion utility (two copiesrecommended).IMPORTANT: If this is a subhost with high-level latency (>150 ms, overseas server)and you do not mind resetting the subhost person and badge record access date andaccess time fields, perform an additional backup of the converted base database onlyto a separate file. To perform an additional backup for only the converted basedatabase, please follow the steps below from the command line:• Log in to a terminal session and log in as ppadmin.• Set Picture Perfect profile by running:. /cas/bin/profile• Start up the database by running:oninit• Perform converted database backup by running:cba -c -b -v -d -baseNote:This will create a backup o the converted base database to the file named in the command.Use that backup during the installation of the subhost with high-level network latency.d. Transfer the converted database file(s) to safe place (PC or another server), since currentserver will be used for the target installation.

32Picture Perfect 4.6 Enterprise EditionUser ManualC.2 Picture Perfect 4.6 server installation1. Log in to the target server.2. Install the OS (AIX or Linux).Follow the instructions in Picture Perfect 4.6 Installation Manual, Chapter 4 or 5,depending on your server type (AIX or Linux).3. Prepare the server for Picture Perfect 4.6 (phase 2).Follow the instructions in Picture Perfect 4.6 Installation Manual, Chapter 6, “InstallingPicture Perfect 4.6”, section “Running the pre-installation setup".4. Find out if the customer requires installation of IT security/OS hardening tools and proceedaccordingly.5. Perform the Picture Perfect base package installation.Follow the instructions in Picture Perfect 4.6 Installation Manual, Chapter 6, “InstallingPicture Perfect 4.6”, section “Installing Picture Perfect base package".Note 1: Set up database sizes according to old retrieved sizes as described in Prerequisites on page 26, (item 3,Database table sizes), plus expected growth and new History sizes where applicable.Note 2: Restore the base and badge converted database.IMPORTANT: If this is a subhost with high level latency (>150 ms, overseas server),restore the base converted database only.Note:APB status, Last Access data will be lost since that data is not replicated and is being recovered in thisprocess from the nethost.6. License the system.7. DO NOT REBOOT. This prevents Picture Perfect from starting up and attempting to connectto the micro controllers.8. Perform a database cleanup to remove old host records and make sure the id of the systemconfiguration record is correct. Use the following steps:a. Set Picture Perfect profile:. /cas/bin/profileb. Start up the database by running the command:su - ppadmin -c oninitc. Remove all host records by running the command:/cas/bin/sqlstmt "DELETE FROM host"d. Reset the system config record id to 1:/cas/bin/sqlstmt "UPDATE system_config SET id = 1"e. Stop the database by running the command:su - ppadmin -c "onmode -ky"9. Perform the optional package installation (subhost, impexp, image) and restore thedatabase(s) where applicable.Follow the instructions in Picture Perfect 4.6 Installation Manual, Chapter 6, “InstallingPicture Perfect 4.6”, section “Installing optional packages and interfaces".

Chapter 3Upgrading Picture Perfect version 4.0/4.5.1 to 4.63310. DO NOT REBOOT. This prevents Picture Perfect from starting up and attempting to connectto the micro controllers.Note:Before proceeding with the next section to configure the new subhost into the system, check for primary keyconditions using the following command: /cas/er/bin/chkpk.shIf any issues are detected, contact UTC Fire & Security Customer Support.D. Configuring the system1. Add the target Picture Perfect 4.6 subhost to the system.Follow the instructions in Picture Perfect 4.6 Enterprise Edition User Manual, Chapter 2,“Installing the network host”, section "Update the host table on the nethost with subhostinformation”.Note:Make sure the subhost to configure at this time has Picture Perfect stopped as well, if not, please log into that server and stop it.2. From the command line, initiate the final configuration process by running hostconfig.Follow the instructions in Picture Perfect 4.6 Enterprise Edition User Manual, Chapter 2,“Configuring the system to recognize the subhosts”.Note:This process can take several minutes, and in some cases, depending on database size and server toserver network latency, it can take hours to finish. Therefore, we recommend running hostconfig from aconsole or a session that ensures it will not be stopped at any time.3. If re-using the same PP 4.0 server to do the PP 4.6 upgrade, this step does not apply.Perform the Backup > History archive to Disk File task and then repeat the same scenariowith Force Roll Over option into another file to capture all existing history data.Follow the instructions in Picture Perfect 4.6 Installation Manual, Chapter 3, “Backing updatabase, configuration, and custom files”, section “Archiving history and forcing rolloversection".4. Start Picture Perfect in the target subhost 4.6 server. Run the following command:su - ppadmin -c rc.pperf5. If the host IP address is different from the original PP 4.0 subhost IP, update the micros withthis information. Bring micros online few at the time.6. Repeat the steps in sections C.1, C.2, and C.3 for the next subhost to be configured.7. Once all servers are configured, start Picture Perfect on the nethost.

34Picture Perfect 4.6 Enterprise EditionUser ManualUpgrade version 4.0 to 4.6 with spare serversOnce all items listed under Prerequisites on page 26 are in place, follow the steps below to upgradeyour Picture Perfect 4.0 Enterprise system to version 4.6.Note:The nethost server must be the first server to be upgraded to the new version.A. Determine the downtime schedule and inform all operators of the downtime schedule(database freeze schedule)The downtime can be estimated based on the size of the database to be converted and otherfactors, such as the time to reinstall the new OS version, reusing the same servers, and latencybetween nethost and subhost to be configured.In a scenario with a database containing 500K person records, no network latency, re-using thesame servers requiring OS installation, we can calculate a downtime between 4 to 6 hours perserver. For a server experiencing network latency, please add 2 to 4 hours to this time. For AIXservers, add at least 1 hour.Note:This estimate does not include getting the micro controllers back online with the server.B. Install the Picture Perfect nethostB.1 Database conversion process1. Log in to the current Picture Perfect 4.0 nethost server.2. Record the old server database sizes (person, badge, notes, all history, micro, category,department, and micro_relation tables).This information can be compiled from the following files:/cas/db/backup/table_desc.dat (for references to table name and id)/cas/db/backup/table_size.dat (for table record sizes based on table id)3. Check the database for illegal characters and fix any reported issues.Follow the instructions in Picture Perfect 4.0 Installation Manual, Chapter 3, “Verify theexisting database", section “Check for Illegal Characters in the Database”.4. Back up the database in the current production system before the upgrade of base, badgeand other packages where applicable (image, tours, graph) with contents verification.Preferably, back up in separate files for each item (for example, one file with base and badge,one file with images, etc.).Follow the instructions in Picture Perfect 4.0 Installation Manual, Chapter 3, “Back upDatabase, Configuration, and Custom Files”, section “Back up Database".5. Perform the Backup > History archive to Disk File task; DO NOT perform scenario with ForceRoll Over option, since the source Picture Perfect 4.0 server might still be running andinserting history records, which will be archived when the Picture Perfect 4.6 target server iscompletely installed and ready to run.Follow the instructions in Picture Perfect 4.0 Installation Manual, Chapter 3, “Back upDatabase, Configuration, and Custom Files”, section “Archive History and ForceRollover". Remember not to run the …forcing rollover… option yet.

Chapter 3Upgrading Picture Perfect version 4.0/4.5.1 to 4.6356. Back up the information needed by the OS, such as server IP addresses in files like /etc/hosts.7. Start the database conversion processa. Transfer database backup files, compiled in step 4. in this section to the spare server.b. Log into the spare server.c. Remove Picture Perfect 4.0 if it is already installed.Follow the instructions in Picture Perfect 4.0 Installation Manual, Appendix C,Removing Picture Perfect".d. Install Picture Perfect 4.0.Follow the instructions in Picture Perfect 4.0 Installation Manual, Chapter 6, “InstallingPicture Perfect”, section “Install Picture Perfect 4.0".Note 1: Set up database sizes according to old retrieved sizes as described in Prerequisites on page 26,item 3, Database table sizes, plus expected growth and new History sizes where applicable.Note 2: Restore the Picture Perfect 4.0 database backup from step 4 in this section.e. Perform the optional package installation (netlan, impexp, image), restore thedatabase(s) where applicable, and reboot the server when requested.Follow the instructions in Picture Perfect 4.0 Installation Manual, Chapter 6, “InstallingPicture Perfect”, section “Installing Optional Packages and Interfaces".f. Execute the database conversion and follow instructions to perform a backup for thetarget-converted database.Follow the instructions in Picture Perfect 4.6 Installation Manual, Chapter 3,“Upgrade”, section “Running the conversion utility".g. Transfer the converted database file to a safe place (PC or the target server), sincecurrent server could be used for other conversions.B.2 Picture Perfect 4.6 server installation1. Log in to the target server.2. Install the OS (AIX or Linux).Follow the instructions in Picture Perfect 4.6 Installation Manual, Chapter 4 or 5,depending on your server type (AIX or Linux).3. Prepare the server for Picture Perfect 4.6 (phase 2).Follow the instructions in Picture Perfect 4.6 Installation Manual, Chapter 6, “InstallingPicture Perfect 4.6”, section “Running the pre-installation setup".4. Find out if the customer requires installation of IT security/OS hardening tools and proceedaccordingly.

36Picture Perfect 4.6 Enterprise EditionUser Manual5. Perform the Picture Perfect base package installation.Follow the instructions in Picture Perfect 4.6 Installation Manual, Chapter 6, “InstallingPicture Perfect 4.6”, section “Installing the Picture Perfect base package".Note 1: Set up database sizes according to old retrieved sizes as described in Prerequisites on page 26, item 3,Database table sizes, plus expected growth and new History sizes where applicable.Note 2: Restore the base and badge converted database.6. License the system.7. DO NOT REBOOT. This prevents Picture Perfect from starting up and attempting to connectto other servers.8. Perform a database cleanup to remove old host records and make sure the id of the systemconfiguration record is correct. Use the following steps:a. Set Picture Perfect profile:. /cas/bin/profileb. Start up the database by running the command:su - ppadmin -c oninitc. Remove all host records by running the command:/cas/bin/sqlstmt "DELETE FROM host"d. Reset system the config record id to 1:/cas/bin/sqlstmt "UPDATE system_config SET id = 1"e. Stop the database by running the command:su - ppadmin -c "onmode -ky"9. Perform the optional package installation (netlan, impexp, image), restore the database(s)where applicable, and reboot the server when requested.Follow the instructions in Picture Perfect 4.6 Installation Manual, Chapter 6, “InstallingPicture Perfect 4.6”, section “Installing optional packages and interfaces".10. If re-using the same PP 4.0 server to do the PP 4.6 upgrade, this step does not apply.Perform the Backup > History archive to Disk File task and then repeat the same scenariowith Force Roll Over option into another file to capture all existing history data.Follow the instructions in Picture Perfect 4.6 Installation Manual, Chapter 3, “Backing updatabase, configuration, and custom files”, section “Archiving history and forcing rollover".C. Picture Perfect subhost(s)C.1 Database conversion process1. Log in to the current Picture Perfect 4.0 subhost server.2. Record the old server database sizes (person, badge, notes, all history, micro, category,department, and, micro_relation tables).

Chapter 3Upgrading Picture Perfect version 4.0/4.5.1 to 4.637This information can be compiled from the following files:/cas/db/backup/table_desc.dat (for references to table name and id)/cas/db/backup/table_size.dat (for table record sizes based on table id)3. Check the database for illegal characters and fix any reported issues.Follow the instructions in Picture Perfect 4.6 Installation Manual, Chapter 3, “Verifying theexisting database”, section “Checking for illegal characters in the database".4. Check the micro configuration and fix any reported issues.Follow the instructions in Picture Perfect 4.6 Installation Manual, Chapter 3, “Verifying theexisting database”, section “Checking Micro configurations".5. Back up the database in the current production system before the upgrade of base, badgeand other packages where applicable (image, tours, graph) with contents verification.Preferably, back up in separate files for each item (one file with base and badge, one file withimages, etc.).Follow the instructions in Picture Perfect 4.6 Installation Manual, Chapter 3, “Backing updatabase, configuration, and custom files”, section “Backing up the database.”6. Perform the Backup > History archive to Disk File task; DO NOT perform scenario with ForceRoll Over option, since the source Picture Perfect 4.0 server might still be running andinserting history records, which will be archived when the Picture Perfect 4.6 target server iscompletely installed and ready to run.Follow the instructions in Picture Perfect 4.6 Installation Manual, Chapter 3, “Backing updatabase, configuration, and custom files”, section “Archiving history and forcing rollover.”7. Back up the information needed by the OS, such as micro and server IP addresses in fileslike /etc/hosts.8. Back up the tty configuration for interfaces, if any.To perform this task backup map files located in the /cas/db/text directory9. Start the database conversion process:a. Transfer database backup files, compiled in step 5 in this section, to the Spare server.b. Log into the Spare server.c. Remove Picture Perfect if it is already pre-installed.Follow the instructions in Picture Perfect 4.6 Installation Manual, Appendix C,“Removing Picture Perfect".d. Install Picture Perfect 4.0.Follow the instructions in Picture Perfect 4.0 Installation Manual, Chapter 6, “InstallingPicture Perfect”, section “Install Picture Perfect 4.0.”Note 1: Set up database sizes according to old retrieved sizes as described in Prerequisites on page 26,item 3, Database table sizes, plus expected growth and new History sizes where applicable.Note 2: Restore the Picture Perfect 4.0 database backup from step 5 in this section.

38Picture Perfect 4.6 Enterprise EditionUser Manuale. Perform the optional package installation (netlan, impexp, image), restore thedatabase(s) where applicable, and reboot the server when requested.Follow the instructions in Picture Perfect 4.0 Installation Manual, Chapter 6, “InstallingPicture Perfect”, section “Installing optional packages and interfaces".f. Execute the database conversion and follow instructions to perform a backup for thetarget-converted database.Follow the instructions in Picture Perfect 4.6 Installation Manual, Chapter 3, “Runningthe conversion utility”.g. Back up the converted database as required by the conversion utility (two copiesrecommended).IMPORTANT: If this is a subhost with high-level latency (>150 ms, overseas server),perform an additional backup of the converted base database only to a separate file.To perform an additional backup for only the converted base database, please followthe steps below from the command line:• Login into a terminal session and login as ppadmin.• Set Picture Perfect profile by running:. /cas/bin/profile• Start up the database by running:oninit• Perform the converted database backup by running:cba -c -b -v -d -baseNote:This will create a backup o the converted base database to the file named in thecommand. Use that backup during the installation of the subhost with high-level network latency.h. Transfer the converted database file to a safe place (PC or the target server), since thecurrent server could be used for other conversions.C.2 Picture Perfect 4.6 server installation1. Log in to the target server.2. Install the OS (AIX or Linux).Follow the instructions in Picture Perfect 4.6 Installation Manual, Chapter 4 or 5,depending on your server type (AIX or Linux).3. Prepare the server for Picture Perfect 4.6 (phase 2).Follow the instructions in Picture Perfect 4.6 Installation Manual, Chapter 6, “InstallingPicture Perfect 4.6”, section “Running the pre-installation setup".4. Find out if the customer requires installing IT security/OS hardening tools and proceedaccordingly.5. Perform the Picture Perfect base package installation.

Chapter 3Upgrading Picture Perfect version 4.0/4.5.1 to 4.639Follow the instructions in Picture Perfect 4.6 Installation Manual, Chapter 6, “InstallingPicture Perfect 4.6”, section “Installing the Picture Perfect base package".Note 1: Set up database sizes according to old retrieved sizes as described in Prerequisites on page 26, item 3,Database table sizes, plus expected growth and new History sizes where applicable.Note 2: Restore the base and badge converted database.IMPORTANT: If this is a subhost with high level latency (>150 ms, overseas server),restore base converted database only.Note:APB status, Last Access data will be lost since that data is not replicated and is being recovered in thisprocess from the nethost6. License the system.7. DO NOT REBOOT. This prevents Picture Perfect from starting up and attempting to connectto the micro controllers.8. Perform a database cleanup to remove old host records and make sure the id of the systemconfiguration record is correct. Use the following steps:a. Set Picture Perfect profile:. /cas/bin/profileb. Start up the database by running the command:su - ppadmin -c oninitc. Remove all host records by running the command:/cas/bin/sqlstmt "DELETE FROM host"d. Reset system the config record id to 1:/cas/bin/sqlstmt "UPDATE system_config SET id = 1"e. Stop the database by running the command:su - ppadmin -c "onmode -ky"9. Perform the optional package installation (subhost, impexp, image), restore the database(s)where applicable, and reboot the server when requested.Follow the instructions in Picture Perfect 4.6 Installation Manual, Chapter 6, “InstallingPicture Perfect 4.6”, section “Installing optional packages and interfaces".10. DO NOT REBOOT. This prevents Picture Perfect from starting up and attempting to connectto the micro controllers.Note:Before proceeding with the next section to configure the new subhost into the system, check for primary keyconditions using the following command: /cas/er/bin/chkpk.shIf any issues are detected, contact UTC Fire & Security Customer Support.

40Picture Perfect 4.6 Enterprise EditionUser ManualD. Configuring the system1. Add the target Picture Perfect 4.6 subhost to the system.Follow the instructions in Picture Perfect 4.6 Enterprise Edition User Manual, Chapter 2,“Installing the network host”, section “Update the host table on the nethost with subhostinformation".Note:Make sure the subhost to configure at this time has Picture Perfect stopped as well. If not, please log into that server and stop it.2. From the command line, initiate the final configuration process by running hostconfig.Follow the instructions in Picture Perfect 4.6 Enterprise Edition User Manual, Chapter 2,Installing the Picture Perfect Enterprise system”, section “Configuring the system torecognize the subhosts".Note:This process can take several minutes. In some cases, depending on database size and server-to-servernetwork latency, it can take hours to finish. Therefore, we recommend running hostconfig from a consoleor a session that ensures it will not be stopped at any time.3. If re-using the same PP 4.0 server to do the PP 4.6 upgrade, this step does not apply.Perform the Backup > History archive to Disk File task and then repeat the same scenariowith Force Roll Over option into another file to capture all existing history data.Follow the instructions in Picture Perfect 4.6 Installation Manual, Chapter 3, “Backing updatabase, configuration, and custom files”, section “Archiving history and forcing rollover".4. Start Picture Perfect in the target 4.6 server.su - ppadmin -c rc.pperf5. If the host IP address is different from the original PP 4.0 subhost IP, update the micros withthis information.Bring micros online a few at a time.6. Repeat the steps in sections C.1, C.2 and C.3 for the next subhost to be configured.7. Once all servers are configured, start Picture Perfect on the nethost.

Chapter 3Upgrading Picture Perfect version 4.0/4.5.1 to 4.641Upgrade version 4.5.1 to 4.6Once all items listed under Prerequisites are in place, follow the steps below to upgrade your PicturePerfect 4.5.1 Enterprise system to version 4.6.Note 1: The nethost server must be the first server to be upgraded to the new version.Note 2: Remember to back up your Picture Perfect 4.5.1 licenses. The licenses are valid and can be used in version 4.6.A. Determine the downtime schedule and inform all operators of the downtime schedule(database freeze schedule)The downtime can be estimated based on the size of the database to be converted and otherfactors, such as the time to reinstall the new OS version, reusing the same servers, and latencybetween nethost and subhost to be configured.In a scenario with a database containing 500K person records, no network latency, and re-usingthe same servers requiring OS installation, we can calculate a downtime between 4 to 6 hoursper server. For a server experiencing network latency, please add 2 to 4 hours to this time. ForAIX servers, add at least 1 hour.Note:This estimate does not include getting the micro controllers back online with the server.B. Picture Perfect nethostB.1 Database conversion process1. Log in to the current Picture Perfect 4.5.1 nethost server.2. Record the old server database sizes (person, badge, notes, all history, micro, category,department, and micro_relation tables).This information can be compiled from the following files:/cas/db/backup/table_desc.dat (for reference to table name and id)/cas/db/backup/table_size.dat (for table record sizes based on table id)3. Check the database for illegal characters and fix any reported issues.Follow the instructions in Picture Perfect 4.5 Installation Manual, Chapter 3, “Verify theexisting database".4. Back up the database in the current production system before the upgrade of base, badgeand other packages where applicable (image, tours, graph) with contents verification.Preferably, back up in separate files for each item (for example, one file with base and badge,one file with images, etc.).Follow the instructions in Picture Perfect 4.5 Installation Manual, Chapter 3, “Back updatabase, configuration, and custom files”, section “Back up database”.5. Perform the Backup > History archive to Disk File task and then repeat the same scenariowith Force Roll Over option into another file to capture all existing history data.Follow the instructions in Picture Perfect 4.5 Installation Manual, Chapter 3, “Backing updatabase, configuration, and custom files”, section “Archive history and force rollover".

42Picture Perfect 4.6 Enterprise EditionUser Manual6. Back up the information needed by the OS, such as server IP addresses in files like /etc/hosts.7. Back up the Picture Perfect license located in file /cas/.PP.key.8. Stop Picture Perfect.Follow the instructions in Picture Perfect 4.5 Installation Manual, Chapter 3, “Verify theexisting database”, section “Shut down Picture Perfect".9. The database conversion process is NOT needed since the current version is Picture Perfect4.5.1.B.2 Picture Perfect 4.6 server installation1. Log in to the target server.2. Install the OS (AIX or Linux).Follow the instructions in Picture Perfect 4.6 Installation Manual, Chapter 4 or 5,depending on your server type (AIX or Linux).3. Prepare the server for Picture Perfect 4.6 (phase 2).Follow the instructions in Picture Perfect 4.6 Installation Manual, Chapter 6, “InstallingPicture Perfect 4.6 - Running the pre-installation setup".4. Find out if the customer requires installing IT security/OS hardening tools and proceedaccordingly.5. Perform the Picture Perfect base package installation.Follow the instructions in Picture Perfect 4.6 Installation Manual, Chapter 6, “InstallingPicture Perfect 4.6”, section “Installing the Picture Perfect base package".Note 1: Set up database sizes according to old retrieved sizes as described in Prerequisites on page 26, item 3,Database table sizes, plus expected growth and new History sizes where applicable.Note 2: Restore the base and badge database that was backed up in the previous section.6. License the system.7. DO NOT REBOOT. This prevents Picture Perfect from starting up and attempting to connectto other servers.8. Perform a database cleanup to remove old host records and make sure the id of the systemconfiguration record is correct. Use the following steps:a. Set Picture Perfect profile:. /cas/bin/profileb. Start up the database by running the command:su - ppadmin -c oninitc. Remove all host records by running the command:/cas/bin/sqlstmt "DELETE FROM host"

Chapter 3Upgrading Picture Perfect version 4.0/4.5.1 to 4.643d. Reset system the config record id to 1:/cas/bin/sqlstmt "UPDATE system_config SET id = 1"e. Stop the database by running the command:su - ppadmin -c "onmode -ky"9. Perform the optional package installation (netlan, impexp, image), restore the database(s)where applicable, and reboot the server when requested.Follow the instructions in Picture Perfect 4.6 Installation Manual, Chapter 6, “InstallingPicture Perfect 4.6”, section “Installing optional packages and interfaces".C. Picture Perfect subhost(s)C.1 Database conversion process1. Log in to the current Picture Perfect 4.5.1 subhost server.2. Record the old server database sizes (person, badge, notes, all history, micro, category,department, and micro_relation tables).This information can be compiled from the following files:/cas/db/backup/table_desc.dat (for references to table name and id)/cas/db/backup/table_size.dat (for table record sizes based on table id)3. Check the database for illegal characters and fix any reported issues.Follow the instructions in Picture Perfect 4.5 Installation Manual, Chapter 3, “Verify theexisting database”, section “Check for illegal character in the database".4. Check the micro configuration and fix any reported issues.Follow the instructions in Picture Perfect 4.5 Installation Manual, Chapter 3, “Verifying theexisting database”, section “Check Micro configuration".5. Back up the database in the current production system before the upgrade of base, badgeand other packages where applicable (image, tours, graph) with contents verification.Preferably, back up in separate files for each item (one file with base and badge, one file withimages, etc.).Follow the instructions in Picture Perfect 4.5 Installation Manual, Chapter 3, “Back updatabase, configuration, and custom files”, section “Back up the database".6. Perform the Backup > History archive to Disk File task and then repeat the same scenariowith Force Roll Over option into another file to capture all existing history data.Follow the instructions in Picture Perfect 4.5 Installation Manual, Chapter 3 “Back updatabase, configuration, and custom files”, section “Archive history and force rollover.”7. Back up the information needed by the OS, such as micro and server IP addresses in fileslike /etc/hosts.8. Back up the tty configuration for interfaces, if any.To perform this task, back up the map files located in the /cas/db/text directory.

44Picture Perfect 4.6 Enterprise EditionUser Manual9. Stop Picture Perfect.Follow the instructions in Picture Perfect 4.5 Installation Manual, Chapter 3, “Verify theexisting database”, section “Shut down Picture Perfect".10. The database conversion process is NOT needed since the current version is PP 4.5.1.C.2 Picture Perfect 4.6 server installation1. Log in to the target server.2. Install the OS (AIX or Linux).Follow the instructions in Picture Perfect 4.6 Installation Manual, Chapter 4 or 5,depending on your server type (AIX or Linux).3. Prepare the server for Picture Perfect 4.6 (phase 2).Follow the instructions in Picture Perfect 4.6 Installation Manual, Chapter 6, “InstallingPicture Perfect 4.6”, section “Running the pre-installation setup.”4. Find out if the customer requires installing IT security/OS hardening tools and proceedaccordingly.5. Perform the Picture Perfect base package installation.Follow the instructions in Picture Perfect 4.6 Installation Manual, Chapter 6, “InstallingPicture Perfect 4.6”, “Installing the Picture Perfect base package".Note 1: Set up database sizes according to old retrieved sizes as described in Prerequisites on page 26, item 3,Database table sizes, plus expected growth and new History sizes where applicable.Note 2: Restore the base and badge database that was backed up in the previous section.IMPORTANT: If this is a subhost with high level latency (>150 ms, overseas server),restore the base converted database only.Note:APB status, Last Access data will be lost since that data is not replicated and is being recovered in thisprocess from the nethost6. License the system.7. DO NOT REBOOT. This prevents Picture Perfect from starting up and attempting to connectto the micro controllers.8. Perform a database cleanup to remove old host records and make sure the id of the systemconfiguration record is correct. Use the following steps:a. Set Picture Perfect profile:. /cas/bin/profileb. Start up the database by running the command:su - ppadmin -c oninitc. Remove all host records by running the command:/cas/bin/sqlstmt "DELETE FROM host"d. Reset system the config record id to 1:/cas/bin/sqlstmt "UPDATE system_config SET id = 1"

Chapter 3Upgrading Picture Perfect version 4.0/4.5.1 to 4.645e. Stop the database by running the command:su - ppadmin -c "onmode -ky"9. Perform the optional package installation (subhost, impexp, image) and restore thedatabase(s) where applicable.Follow the instructions in Picture Perfect 4.6 Installation Manual, Chapter 6, “InstallingPicture Perfect 4.6”, section “Installing optional packages and interfaces".10. DO NOT REBOOT. This prevents Picture Perfect from starting up and attempting to connectto the micro controllers.Note:Before proceeding with the next section to configure the new subhost into the system, check for primary keyconditions using the following command: /cas/er/bin/chkpk.shIf any issues are detected, contact UTC Fire & Security Customer Support.D. Configuring the system1. Add the target Picture Perfect 4.6 subhost to the system.Follow the instructions in Picture Perfect 4.6 Enterprise Edition User Manual, Chapter 2,“Installing the Picture Perfect Enterprise system”, section “Update the host table on thenethost with subhost information.Note:Make sure the subhost to configure at this time has Picture Perfect stopped as well, if not, please log into that server and stop it.2. From the command line, initiate the final configuration process by running hostconfig.Follow the instructions in Picture Perfect 4.6 Enterprise Edition User Manual, Chapter 2,“Installing the Picture Perfect Enterprise system”, section “Configuring the system torecognize the subhosts”Note:This process can take several minutes. In some cases, depending on database size and server-to-servernetwork latency, it can take hours to finish. Therefore, we recommend running hostconfig from a consoleor a session that ensures it will not be stopped at any time.3. Start Picture Perfect in the target 4.6 server.su - ppadmin -c rc.pperf4. If the host IP address is different from the original PP 4.0 subhost IP, update the micros withthis information. Bring micros online a few at the time.5. Repeat steps in sections C.1, C.2, and C.3 for the next subhost to be configured.6. Once all servers are configured, start Picture Perfect on the nethost.

46Picture Perfect 4.6 Enterprise EditionUser Manual

Chapter 4 Managing your networkdatabaseThis chapter includes processes and rules required to keep your networkfunctioning properly. Guidelines on procedures to be performed on thenethost versus the subhost are included.In this chapter:Network host operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Subhost operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Synchronizing the time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Refreshing the database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Enterprise Replication (ER) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Network alarm monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

48Picture Perfect 4.6 Enterprise EditionUser ManualNetwork host operationData synchronizationThe network host (also referred to as nethost) provides centralized badge administration and storesthe history transactions for the entire system for centralized reporting. It contains the global tablesand the badge, alarm, and operator history tables of itself and each of the subhosts. The nethostdoes not support micro controllers. The nethost maintains database synchronization via the use ofInformix database replication (see Enterprise Replication (ER)) and the history refresher programdbrfsh (see Refreshing the database), which run continuously, and independently of each other.The ER and refresher programs keep track of when the nethost last talked to each of the subhosts,and what records have already been synchronized. The ER and refresher programs perform thefollowing functions:• Send modified person and badge record data from the nethost to each subhost, and fromeach subhost to the nethost.• Send new and modified global table records from the nethost to each subhost, and from eachsubhost to the nethost.• Send badge history records from each subhost to the nethost.• Send alarm history records from each subhost to the nethost.• Send operator history records from each subhost to the nethost.ImagesThe image database is normally installed and stored on the nethost. All badging workstations mustconnect to the nethost to perform badge production. This is the typical configuration.Note:If desired, a subhost can be installed to store the imaging database for local access to imaging data. However, thesubhost cannot be used as the Imaging host for the entire Enterprise system.Photos can be inserted via live capture (USB camera with TWAIN interface) or by importing JPGphoto files. Photos can be viewed at any workstation – connected to the nethost or any subhost.Image data is not replicated across the Enterprise system installation. It is accessed remotely fromthe Imaging server that holds that type of data.Subhost operationThe subhosts receive real-time badge and alarm transactions from their micro controllers and displaythese transactions in the Badge and Alarm Monitor windows. Operators manage their own regionsby logging into their subhosts. Subhosts contain all global tables and their own local tables. Microcontrollers, readers, alarms, and other devices are defined only on subhosts. Subhosts do notcontain the local database of any other subhost. Each subhost contains its own history tables forbadge, alarm, and operator transactions. This information is also sent to the nethost by theEnterprise Replication (ER) and history refresher programs.Subhosts can save changes to person, badge, and global tables. The changes are sent to thenethost through Enterprise Replication.

Chapter 4Managing your network database49Optional software packages, such as Alarm Graphics, Guard Tours, and interfaces to other hardwaresystems, are installed on the subhost because the software of optional packages interacts withdevices installed on a subhost (e.g., input points, readers).Synchronizing the timeDatabase synchronization requires all servers in a Picture Perfect Enterprise system to have thesame time relative to UTC (Coordinated Universal Time). The Network Time Protocol (NTP) processon the nethost is the master time server and is responsible for maintaining the system clocks oneach machine. Each server in an Enterprise system is configured with NTP time synchronizationmechanism. If the times differ, then the subhost adjusts its clock to be synchronized with that of thenethost. If the nethost goes down for a period of time, the subhosts have to wait until the nethostcomes back on-line in order to synchronize their clocks. If a subhost goes down, then it synchronizesits clock when it comes back on-line.Note:The NTP server does not synchronize a drift in time greater than 1000 seconds.Refreshing the databaseIf the nethost goes down, each subhost continues to function normally, with the exception that thedata does not get replicated anywhere. New category records cannot be added to the system, butexisting categories can be added or removed from person records. Records of all tables can beadded, modified, or deleted by workstations connected to the subhosts, and alarms continue to bereported to the alarm monitor on the subhosts. When communication to the nethost is restored, theEnterprise Replication (ER) and refresher programs automatically synchronize the nethost andsubhosts’ global database tables and history tables.If a subhost goes down, the nethost and other subhosts continue to function normally. The microcontrollers connected to the non-operational subhost go into offline mode and continue to grantaccess based on the badge database in the micro. While a micro is offline, up to 5,000 badgetransactions and 2,500 alarm transactions can be stored locally in the micro. Alarms from thatsubhost are not reported to the user because there is no subhost workstation to which they can bereported. Once the subhost is operational, the offline micro transactions are uploaded to the subhost,stored in the history tables, and the history tables are refreshed to the nethost.The database refresher process dbrfsh is used as indicated in the table below:Table 3.Refresh TablesFunction and Table Name Refresh Process Name Refresher DirectionInsert alarm_historyInsert badge_historyInsert operator_hisInsert tour_historydbrfsh -adbrfsh -bdbrfsh -odbrfsh -uSubhost to Host

50Picture Perfect 4.6 Enterprise EditionUser ManualConfigurationThe refresh program knows what databases are in the network and where they are located.The refresh_config table contains an entry for each history table to be refreshed on eachsubhost. The entries are created automatically whenever a subhost is defined using theControl/Hosts form. This table is for internal use by the refresh programs and is not accessible froma user interface. You do not need to change it.Table 4.Refresh Configuration TableColumn Name Type Descriptionid integer Unique row idhost_id integer Foreign Key - host tabletable_name varchar(19) table to be refreshedpoll_interval integer seconds to waitlast_poll_date integer yyyymmdd used for non-history refreshlast_poll_time integer hhmmss used for non-history refreshcurrent_id integer history subhost idmodify_datemodify_timeinteger yyyymmddinteger hhmmssRemote database access configurationThe hostname in the host table allows up to 64 alphanumeric characters. The hostname in the hosttable and the DBSERVERNAME in the Informix config file $INFORMIXDIR/etc/onconfig and the $INFORMIXDIR/etc/sqlhosts file must be identical. You do not need to edit onconfig orsqlhosts. Data is automatically written to these files during the Picture Perfect installation. It is forinformation purposes only.Polling intervalThe word “poll” refers to detecting changes between the nethost and the subhosts. Every machine inthe host table is polled for database refresh data based on a configurable time interval in therefresh_config table. Polling is configured only for history tables. The refresher executes for eachsubhost in the network, then sleeps for the poll interval and then begins again. Only subhosts thatare set up in the nethost with configure_online = ‘Y’ are refreshed.Note: Global tables other than history tables are immediately refreshed by Informix ER and do notuse poll interval times.Log file message layoutThe refresher log file is /cas/log/rfs.. Each entry indicates which table it is refreshingon the subhost as needed. Informix SQL and ISAM error codes are used for logging error messagesinstead of the full Informix textual error message.

Chapter 4Managing your network database51To get an explanation of the error codes, use the Informix program finderr followed by the errorcode. For example:$ finderr -908-908 Attempt to connect to database server (servername) failed.The program or application is trying to access another database server but hasfailed. Note the server name in the current statement.The desired database server is unavailable, or the network is down or iscongested. Ask your DBA and system administrator to verify that the server andnetwork are operational. If the network is congested, use the environmentvariables INFORMIXCONTIME and INFORMIXCONRETRY to tune connection timing. Forinformation on setting these environment variables, see the Informix Guide toSQL: Reference.Refreshing database history tablesThree history tables are stored on each Picture Perfect system. The nethost collects alarm history,badge history, and operator history by polling each subhost for newly created history data. This datais transferred to the nethost and inserted into the nethost alarm history, badge history, or operatorhistory tables. The poll time is a predetermined time interval setup automatically during installation.This information is stored in the poll_interval column of the refresh_config table. The nethostitself may generate alarms and operator activity, which are also inserted into the nethost historytables. The nethost does not generate badge activity since micros cannot be connected to it. Thecurrent_id column in the refresh_config table keeps track of the last history record ID fetchedand inserted from a subhost on a per-table, per-subhost basis.Enterprise Replication (ER)Picture Perfect Enterprise Edition 4.6 uses the IBM Informix ER tool to replicate database tableinformation between geographically distributed servers. This tool is an enhancement/replacement forthe Personnel/Badge and Categories "refreshers" technique used in previous Picture Perfectversions. Informix ER provides high availability and improved performance for high volume datatransfers at network latency limited to 300 ms. The benefits of Enterprise Replication include:• Updates from any host are now supported (as opposed to allowing changes only on thenethost).• Latency on one subhost no longer affects the refresh time on other subhosts.• Significantly improved performance.Note:The Notes are replicated for badge and person only.The Informix ER hierarchical tree topology preserves the current Picture Perfect configurationwherein the nethost is the master server (top level host) and the subhosts are subordinates. In theER topology, the nethost is the "root" server (database) and the subhosts are "non-root" servers forreplication. The servers continue to run in nethost and subhost modes (tps mode). The nethostserver has to be running for data changes done at any subhost to be replicated to the wholeinstallation.

52Picture Perfect 4.6 Enterprise EditionUser ManualER is applied to the following Picture Perfect tables (see Figure 4):• person• badge• person_user• person_category• temp_category• notes (only for person/badge)• category• facility• person_type• department• permission_group• host_bid_format• custom_form• custom_list_elem• site_lists• form_tab• custom_control• custom_control_arg• time_zone• time_zone_dstFor person-related and global tables, replication is applied in both directions between nethost andsubhosts (up to 31 subhosts).Note:Although part of the Facility form, facility_email and email_ran tables are not replicated. In PicturePerfect 4.5.1 and 4.6, the facility email feature is managed locally for each server. Every server needsto manage its own list of facility emails.In an Enterprise system environment, there are some hardware-dependent fields that are notrefreshed by networking to other subhosts. These fields include antipassback (APB), lastaccess reader, last access date, last access time, last access area, usagecount, download upon save, card trace, and keypad response. If the optional GuardTours package is installed, the field tour badge is also not refreshed. Due to the site-dependentinformation found in these fields, you would not want them to be refreshed. For example, subhost 1reader 1 is located at the back door. Subhost 2 reader 1 is located at the side door. To send theinformation in the field last access reader from subhost 1 reader 1 to subhost 2 reader 1 would notbe useful to an operator on subhost 2.The dbrfsh refresh process is applied to the following Picture Perfect tables (see Figure 4):• badge_history• alarm_history• operator_his• tour_history (optional package)For history tables, the refresh process is applied in one direction from subhosts to nethost.Note:Picture Perfect 4.6 introduces database schema changes for history tables to unify their layout acrossthe Enterprise configuration (see the Picture Perfect 4.6 Tables and Fields Reference Manual).

Chapter 4Managing your network database53Figure 4. Hierarchical Topology of Enterprise Replication and Refresher ProcessEnterprise Replication configuration and administration permissionsDuring the initial setting of Enterprise Replication, the informix user is required to perform theconfiguration of this feature. On an installed system, some tasks, such as adding a new server to thesystem, adding a new table for replication, synchronizing tables using Informix native technology,also require the informix user. Most of the administration, monitoring, and data recovery tasks aredone by the ppadmin user. For more information about the Picture Perfect user accounts, seeChapter 6 in the Picture Perfect Installation Manual.Enterprise Replication installationThe netlan and subhost packages were re-factored for the configuration of Enterprise Replicationand to remove previous data replication technology, such as the badge and category refresherdaemons /cas/bin/bdrfsh and /cas/bin/catrfsh and other mechanisms that werepreviously used to synchronize data between nethost and subhosts.Note:The history refresher daemon /cas/bin/dbrfsh continues to be used to refresh history tables.Shell scripts called by netlan.inst and subhost.inst make sure that all necessary files anddirectories are set up properly for Enterprise Replication.Two new database spaces (entrepdbs and entrepsbs) are required by the ER technology to definethe database to manage replication and queuing all data information that is being replicated to otherserver(s) or received from them. These DB spaces are configured to be set at 75% of the size of thebasedbs DB space.• entrepdbs (Enterprise Replication Database Space) defines the location for the syscdrdatabase, which is created during ER server definition (ER initialization) and internalinformation for the spooled send transaction data.• entrepsbs (Enterprise Replication Smart Blob Space) defines the location of the spooledtransaction information. This is stored in an SBlob.

54Picture Perfect 4.6 Enterprise EditionUser ManualThe syscdr database is added to the installation. This database resides in the entrepdbs DB spaceand is required by the ER technology to administer the replication in every participant server.The table currseq (server_id int, table_name varchar(64), currseq int) is added to the installation.This table is populated with default records that have the server_name of that server, records foreach of the global tables that will have sequences (excluding history tables), and the value of currseqset to 0 or max(id) if there are records already on that host for that table.The table host_time (id int, hostname varchar(64), utc_timestamp date_time) is added duringnetlan/subhost installation. This table is populated with the current UTC time on each server for itself.The subhost records are replicated to the nethost. So, the host_time table on the subhost has one(1) record, and on the nethost the host_time table has a record for itself and records for all subhosts.The directories /ats (Aborted Transaction Spooling) and /ris (Row Information Spooling) arerequired by the table replicate definition which maintains log data about failed replicated records.The /ats and /ris directories are created in the Picture Perfect /ppbackup directory that isdefined in the Parameters UI (system_config table).The /ppbackup directory must have reserved enough space to keep log data from the /ats and/ris directories in addition to the recommended 25 to 35 Gb (additional minimum suggested for ERis 5 GB).ER configures and manages all servers in the installation by group names to allow space for serveraliases, server names for encrypted database communication or disaster/recovery servers, as inbackup/secondary (High-Availability Data Replication (HDR) servers.In ER configuration, the nethost is referred to as “nethost_1”. The first subhost is referred to as“subhost_2”, the second as “subhost_3”, and so on. The suffix number of the nethost or subhostrefers to the “id” of the corresponding server in the host table in the database.Enterprise Replication scriptsWith the introduction of ER, several existing installation, database management and monitoringscripts/tools have been modified and new tools have been introduced.The following sections describe new and modified ER monitoring and management tools:• ercmd.sh• hostconfig• cdr_er_cleanup.sh

Chapter 4Managing your network database55ercmd.shHealth checks and other monitoring and management tasks that are specific to ER can be performedwith the command line function /cas/er/bin/ercmd.sh. The ercmd.sh script can be used to:• Get replication participating server information (list of servers)• Get table synchronization status• Get table replicating status• Manually re-synchronize table data• Manually re-synchronize data on a server• Extend the size of the ER database spaces when a new subhost is added to the configuration• Create a tar file with diagnostic information from all ER logs created on the system• Remove ER from the serverThe script can be run as root or ppadmin user.In addition, cronjobs, database tasks, and database issued events are used to monitor the ERsystem for:• ER database space at 90%• Server times being out of synch• Running out of sequences• ER errors (ATS/RIS files)• ER internal failureNote: Failed ER transactions are logged to files in the /ppbackup/ats and /ppbackup/ris directories.Table 5 lists the command options and arguments for ercmd.sh.Table 5.ercmd.sh optionsOptionDescription--list This option displays the names of the hosts participating in ER. See Chapter 5,Running ercmd.sh --list.--status [-b table_name]--createsupportfile--addchunks -d dbspace_name -n sizeThis option displays the replication status for replicated tables; optionally takesthe table_name argument to display the replication status for the specifiedtable.• When run on the nethost, shows the replication status for all tables on allhosts. See Chapter 5, Running ercmd.sh --status.• When run on a subhost, shows the replication status for itself and nethost.Note: The cdr_er_display_config.sh script can also be used to displaythe ER configuration and current state. This script displays 'cdr list server' datain a user-friendly manner with hostnames instead of group names (groupnames are not indicative of the host.)This option creates a tar file that contains ER diagnostic information forCustomer Support for troubleshooting purposes.The tar file is stored in /cas/log/pp_er_diag_data.tarThis option extends the ER database space. The addchunks option callscdr_er_ext_dbspace.sh to add new a new chunk (in MB) of databasespace for ER.

56Picture Perfect 4.6 Enterprise EditionUser ManualTable 5.ercmd.sh optionsOptionDescription--recover_table -b table_name -s source_host [-a action ] [-g triggeraction ]--recover_allhosts -s [-a action ] [-g triggeraction ]--recover_subhost -t [-a action ] [-g triggeraction ]This option calls cdr_er_recover_table.sh according to the parametersentered.• (required parameter) - name of the table to recover• (required parameter) - master server name to recover from- When run on nethost, must be specified (must be oneof the subhosts).- When run on subhost, defaults to nethost. If is specified, it must be the nethost.• [- a action d|m] (optional) - ‘d’ for deleting records on the target server;‘m’ for merging those records back to the server.If no action is specified, it defaults to 'm' - merge.• [-g triggeraction ] (optional) - ‘on’ to indicate triggers are fired on the target server; ‘off’ to indicate triggers are not fired on the target server.The trigger action (sync or check) is determined per table, based on dataon the target server for base/badge data and based on the number ofdifferences.- If there is no data on the target or if the number of differences betweensource and target server for given table is >= 100000, then sync is used.- If there is data on the target with < 100000 diffs, then check is used.Note: When the triggers do not fire, depending on the table that is beingrecovered, the micros will not get the changes or cache will not be updated.This option is available only on the nethost. It recovers all hosts.This option calls cdr_er_recover_table.sh for each target host and foreach replicated table.The argument can be the nethost or any one of the subhosts.The other parameters have same defaults and meaning, as described for therecover_table option above.This option is available on nethost and subhosts. It recovers replicated tables.• If run on the nethost, for each of the replicated tables, callscdr_er_recover_table.sh with subhost hostname.• If run on the subhost, for each of the replicated tables, callscdr_er_recover_table.sh with the local hostname as target.The other parameters have same defaults and meaning as described for therecover_table option above.--recover_status [-b table_name]--remove_ERThis option displays the recovery status for replicated tables; it optionally takesthe table_name argument to display the recovery status for the specifiedtable.• If a table is currently being recovered, the status shows Started. Whendone, it shows Completed.• The recovery status on a host (nethost or subhost) shows data for itselfonly if a recovery was run on that host.This option is available on the nethost and subhosts.• When run on the nethost, it removes ER from the whole Enterprise system.• When run on a subhost, it removes that subhost from ER.

Chapter 4Managing your network database57hostconfigWith the introduction of ER, the existing /cas/bin/hostconfig script is given additionalfunctionality.During initial installation, hostconfig adds the subhosts to the ER configuration. The script readsthe host table on the nethost and defines every subhost in the installation.The hostconfig script performs the following tasks:• Starts up the database on the nethost• Checks if it is necessary to stop Picture Perfect on the nethost• Checks if all subhosts configured in the host table are reachable through the network• Checks if SSH is properly configured for all subhosts• Enters a loop on all subhosts to configure services and Informix sqlhosts files• Checks the UTC time configuration• Starts up the subhost database• Begins setting all items needed by ER:- Informix sqlhosts file- Sequence objects- Primary keys and shadow columns- Triggers and stored procedures- ER server and table replicates• Synchronizes all servers• Shows a report of final statusWhile hostconfig is running, all new (except nethost) or recovered servers automatically enter in aprocess of database synchronization, depending on the database restore status. Since the processof synchronizing a database can take several minutes, depending on the number of records in thereplicated tables, a progress report is shown on the screen. The progress report indicates the currenttable, number of records to synchronize, start time and expected time to finish the process as shownin the example below:----------------------------------------------------------------------Picture Perfect hostconfig utility - Version 4.6 04/25/2011Copyright (C) 1989-2011 UTC Fire & Security Americas Corporation, Inc.----------------------------------------------------------------------Checking sqlhosts file... bctalford[*]Processing [bctdover]Server [bctdover] already set up for ER... [skipping].Processing [bctalford]Service and port were okayChecking for [bctalford] database.... Starting up, please wait .... [Done].Updating sqlhosts file for [bctalford]...Stopping Informix database to update sqlhosts with subhost‘bctalford’..[Done].Starting the Informix database.. [Done].Copying .netrc to bctalford ppadmin and ppapp home directories [Done].Updating hcomm_ingrp field on host table...Checking for replication status... [Done}.Configuring sqlhost file for ER... [Done].Configuring remote sqlhosts file(s) for ER... [Done].

58Picture Perfect 4.6 Enterprise EditionUser ManualConfiguring Sequence Objects.... [Done].Initializing ‘currseq’ table.... [Done].Configuring Primary Keys and CR Column.... [Done].Configuring Stored Procedures for ER... [Done].Configuring Triggers for ER... [Done].Bouncing bctdover and bctalford databases to set changes. Please wait......[Done].Configuring Enterprise Replication Server... [Done].Configuring Enterprise Replication Replicates.... [Done].Configuring Enterprise Replication Scheduled Task(s).... [Done].Process of database synchronization...WARNING: Depending on the each server database synchronizationstatus, this process can take several minutes.please wait...o Processing [bctdover]... Already setup for ER [Skipping]o Processing [bctalford]...Recovering [bctalford] server... [FLAGS: SD SD SK]Table Name Records Rem. Time================================= ========== ==========o category: ....................... [ 2] 11:17:52 11:17:53o facility: ....................... [ 1] 11:17:53 11:17:54o person_type: .................... [ 4] 11:17:54 11:17:55o department: ..................... [ 0] 11:17:55 11:17:55o permission_group: ............... [ 2] 11:17:55 11:17:58o host_bid_format: ................ [ 3] 11:17:58 11:17:59o custom_form: .................... [ 85] 11:17:59 11:18:01o custom_list_elem: ............... [ 0] 11:18:01 11:18:02o site_lists: ..................... [ 0] 11:18:02 11:18:03o form_tab: ....................... [ 164] 11:18:03 11:18:05o custom_control: ................. [ 816] 11:18:05 11:18:06o custom_control_arg: ............. [ 5237] 11:18:06 11:18:08o time_zone: ...................... [ 504] 11:18:08 11:18:10o time_zone_dst: .................. [ 1381] 11:18:10 11:18:11o notes: .......................... [ 0] 11:18:11 11:18:12o temp_category: .................. [ 0] 11:18:12 11:18:13o person_category: ................ [ 0] 11:18:13 11:18:14o person_user: .................... [ 0] 11:18:14 11:18:15o badge: .......................... [ 0] 11:18:15 11:18:16o person: ......................... [ 0] 11:18:16 11:18:17Resynching sequences at [bctalford] server... [Done]>[bctalford] synch. process [Done] [Done] Synchronizing databases.All host configured successfully.In addition to being run during initial setup of a Picture Perfect Enterprise system, there arescenarios when hostconfig needs to be run. These scenarios include:• after a dropreloaddb.sh,• after a remove_ER (from ercmd.sh) and adding back ER, and• after a server crash and reinstall/reconfigure.Notes: hostconfig after dropreloaddb.sh requires Picture Perfect (tps) to be stopped only on the server where thedropreloaddb.sh was done. hostconfig after remove_ER and adding back ER does not require Picture Perfect (tps) to be stopped on anyserver.hostconfig calls the cdr_er_recover_server.sh script to perform the synchronization/recovery processes. (The recovery script is also called from ercmd.sh.)

Chapter 4Managing your network database59cdr_er_cleanup.shThis script:• Removes a subhost from Enterprise Replication when run on the subhost.• Removes ER completely when run on the nethost with no arguments.• Removes a subhost when run from the nethost using the -s argument accompanied by thename of the server to be removed. If the server name provided is the nethost, the result is thesame as if the script was run from the nethost with no arguments.The script must be run on every subhost or from the nethost to perform a complete ER removalbefore the system can be brought up again.The cdr_er_cleanup.sh script can be run from the command line or from ercmd.sh. The usermust be root or ppadmin.Enterprise Replication conflict resolution and spoolingWhen conflicting data is encountered during ER between source and target servers, Picture Perfectapplies the following rules for conflict resolution:• Time stamp The row or transaction with the most recent time stamp is applied. This rule is used for bi-directional replicate tables (person/base).• Always-apply ER does not attempt to resolve conflicts, but always applies source datato the target. This rule is used for uni-directional replicate tables(host_time).To implement conflict resolution, two types of shadow objects are used in ER: shadow columns andshadow tables.Enterprise Replication backup/restoreEnterprise Replication does not impact the current database backup functionality. However, thedatabase recovery/restore functionality has some new constraints:• The Recovery option is no longer available from the client GUI. Recovery must be performedusing the restore.sh command line option.• Recovery cannot be performed while TPS is running.• The cbr command may be used on a running system only when history restoring data fromarchives for reporting purposes (see Picture Perfect 4.6 User Manual, Chapter 15).• When restoring from backups on an Enterprise system, replication is stopped, triggers aredisabled, data is restored, replication is restarted, and triggers are re-enabled.• Enterprise Replication is turned off when modifying the database during a restore operation.- Restore is normally done during installation. After installation all the hosts are resynchronizedusing hostconfig.- Restore is also done via dropreloaddb, in which case hostconfig also resynchronizesthe hosts.- If Restore is called outside of these two scenarios, the ercmd.sh (restore table)command should be used to manually synchronize the database tables.

60Picture Perfect 4.6 Enterprise EditionUser ManualAlarmsThe Picture Perfect Enterprise configuration provides the following alarms on the nethost:• Host to Host Comm Fail: Occurs when the network connection between the nethost and asubhost is broken, or when a host goes down.• Remote Database Connect Error: Occurs when the remote Informix databases cannot bereached.All alarms that are routed to the Alarm Monitor on each of the subhosts are also automaticallyforwarded to the nethost’s Alarm Monitor. Therefore the nethost’s Alarm Monitor displays all activeand pending alarms for the entire system.Enterprise Replication introduces four pre-defined logical alarms and associated input groups:• Sequence Object 90% full• Aborted Transaction (conflicts) reported• ER Server stopped or suspended• Server clock out of syncFor more information about these alarms, see Which new alarms are introduced and howdo I proceed if those alarms display in the Alarm Monitor? on page 113The alarm for exceeding 90% of database space now includes a check for the ER database spaces(entrepdbs and entrepsbs).Database scheduled jobs (tasks/sensor), cron jobs, or the database itself catch these conditions andtrigger the alarms. The new alarms and input_group data are added to the system during netlanand subhost installation.These alarms do not have a reset state because it is not possible to detect a "resolved" state versusa "normal good" state. Once the alarmed issue has been resolved, the operator has to respond tothe alarm and/or delete the alarm manually.

Chapter 4Managing your network database61Network alarm monitorThe Network Alarm Monitor feature allows the operator to view and respond to local and remotealarms on the nethost. The Network Alarm Monitor does not require any type of specialconfiguration. All the subhosts that are in the network must be defined in the Hosts table of PicturePerfect and in the /etc/hosts file. See Enterprise system software installation on page 7 fordetails.All alarms that are routed to the Alarm Monitor on each of the subhosts are forwarded automaticallyto the nethost. An operator on the nethost can respond to remote alarms as well as to local alarms.For remote alarms, the Network Alarm Monitor obtains the alarm instructions and responses from thesubhosts.Notes: To view Alarm Instructions, for alarms originated at a subhost, the operator must be defined as anoperator on the subhost as well. Alarms are filtered to the display based on facilities. For furtherinformation on Alarm Filtering, refer to the Picture Perfect 4.6 User Manual, System Parameters Form.The Network Alarm Monitor indicates that the operator is responding to a remote alarm, and theRSVP button can be used to respond. All responses entered on the nethost are sent to the subhostwhere the alarm originated. Remote responses are logged to alarm history on the subhost.All alarm history from all subhosts is uploaded to the nethost alarm history after a predetermined timeinterval. This is accomplished using subhost polling (see Refreshing database history tables onpage 51 for more information).If any subhost is not online with the nethost, its alarms are not reflected on the Network AlarmMonitor as they occur. When the subhost is restarted and is back online with the nethost, all subhostalarms are forwarded to the Network Alarm Monitor. When the nethost recovers from acommunications failure, it queries the subhosts for their alarms and displays them on the NetworkAlarm Monitor.Notes: Define each subhost’s alarms with a description of the alarm origin on the Network Alarm Monitor.Alarm instructions and responses should be defined for subhost operators and nethost operators.Figure 5. Remote Alarm-Response Window

62Picture Perfect 4.6 Enterprise EditionUser Manual

Chapter 5 Verifying the configurationThis chapter includes information needed to verify that all the variousprocesses in your Enterprise system are running properly and to verify theintegrity of your database.In this chapter:Verifying /etc/hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Running chkenterprise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Verifying permissions on nethost and subhosts . . . . . . . . . . . . . 68Verifying communications on the nethost . . . . . . . . . . . . . . . . . . 69Verifying Picture Perfect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Verifying Enterprise system setup . . . . . . . . . . . . . . . . . . . . . . . 73Verifying table IDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Verifying remote database access configuration . . . . . . . . . . . . 77Verifying hosts time synchronization . . . . . . . . . . . . . . . . . . . . . 79Running chkdbsync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Running ercmd.sh --status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Running ercmd.sh --list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

64Picture Perfect 4.6 Enterprise EditionUser ManualVerifying /etc/hostsThe aa (add address utility) can be used to edit the /etc/hosts file (instead of using the vi editor).To verify /etc/hosts:1. If not already logged on, log on as root and open a new terminal window.2. At the command prompt, type:. /cas/bin/profile Enter3. Type the following command:more /etc/hosts Enter4. Inspect the output for any host names you specified and verify that the Internet addresses arecorrect.If you need to add an entry to the hosts table, follow this procedure:a. Type the following command: aaThe following menu displays:Enter----------------------------------------------------------------------aa - add address utility version - 1.2 01/29/03Copyright (C) 1989-2011 UTC Fire & Security Americas Corporation, Inc.----------------------------------------------------------------------(a)dd address(d)elete address(l)ist addresses(e)xit(?)help(!)shell escapeAction:At the Action: prompt, type a to add an address.b. At the Name of host or terminal? prompt, type the name of the missing machine,then press Enter .c. At the Internet Address: prompt, type the address of the missing machine, thenpress Enter .d. When the menu displays, type l, then press Enter at the Action: prompt to list theaddresses. Make sure the machine you added appears on the list.e. When the menu displays, type e at the Action: prompt to exit this program.f. Shut down, and then restart the system.

Chapter 5Verifying the configuration65Running chkenterpriseTo verify that the Enterprise system is configured properly, run the chkenterprise utility on thenethost. The SSH trust on each subhost must be available.Note:Run chkenterprise as root with all hosts up and running Picture Perfect to ensure all checks areexecuted.To verify the Enterprise configuration:1. Log onto the nethost as root.2. At the command prompt, type:. /cas/bin/profilechkenterprise EnterEnterMessages similar to the following display:Verifying Enterprise System Configuration...Network Host [bctdover]:Verifying Operating System Type... [ Linux ]Verifying TPS is running... [ OK ]Verifying Informix is running... [ OK ]Verifying /etc/hosts...bctdover [ OK ]bctalford [ OK ]Verifying /cas/.netrc ...bctalford [ OK ]Verifying system_config count... [ OK ]Verifying Table ID Consistency... [ OK ]Verifying host count... [ OK ]Verifying Host Record Consistency...bctdover Startup Mode... [ OK ]Configure Host... [ OK ]bctalford Startup Mode... [ OK ]Configure Host... [ OK ]Verifying Increased Categories Settings... [ ENABLED ]Verifying Seed Counter Settings... [ DISABLED ]Verifying /etc/services...bctdover [ OK ]bctalford [ OK ]Verifying NTP config file exists... [ OK ]Verifying Nethost configured in /etc/ntp.conf... [ OK ]Verifying NTP daemon is running... [ OK ]Verifying Informix ER configuration... [ OK ]Network Subhost [bctalford]:Verifying Network Connection... [ OK ]Verifying Remote Connectivity via ssh... [ OK ]Verifying Operating System Type... [ Linux ]Verifying TPS is running... [ OK ]Verifying Informix is running... [ OK ]

66Picture Perfect 4.6 Enterprise EditionUser ManualVerifying Remote Database Connectivity... [ OK ]Verifying /etc/hosts...bctdover [ OK ]bctalford [ OK ]Verifying /cas/.netrc ...bctdover [ OK ]Verifying /cas/ppapp/.netrc ...bctdover [ OK ]Verifying system_config count... [ OK ]Verifying Table ID Consistency... [ OK ]Verifying host count... [ OK ]Verifying Host Record Consistency...bctdover Startup Mode... [ OK ]Configure Host... [ OK ]bctalford Startup Mode... [ OK ]Configure Host... [ OK ]Verifying Increased Categories Settings... [ ENABLED ]Verifying Seed Counter Settings... [ DISABLED ]Verifying /etc/services...bctdover [ OK ]bctalford [ OK ]Verifying NTP config file exists... [ OK ]Verifying Nethost configured in /etc/ntp.conf... [ OK ]Verifying NTP daemon is running... [ OK ]Verifying Informix ER configuration... [ OK ]Results: Passed [ 45 ], Failed [ 0 ], Blocked [ 0 ]Note the Results line listed at the end of the output.• If the Failed column lists 0, then the installation is successful.• If the Failed column lists a number greater than 0, then problems have been detected in yourconfiguration. Refer to Table 6, Verification Tests and see the sections referenced by eachtest for troubleshooting details.Table 6.Verification TestsTestVerifying Network ConnectionVerifying Remote Connectivity by SSHVerifying Operating System TypeResultThis test fails if a subhost cannot be reached using the ping command. If thistest fails, then there is either a networking configuration problem on thenethost or on the target subhost or both.This test fails if a subhost cannot be reached by SSH. SSH access is requiredfor chkenterprise to verify conditions on a subhost. Enable SSH access tothe subhost and try again.This test can fail only if chkenterprise is being executed on a system thatis neither Linux nor AIX. Currently, Enterprise system is supported only on theLinux and AIX operating systems.Verifying TPS is running Please see Verifying Picture Perfect on page 70.Verifying Informix is running Please see Verifying Picture Perfect on page 70.

Chapter 5Verifying the configuration67Table 6.Verification Tests (continued)TestVerifying Remote Database ConnectivityResultThis test can fail only if either the /cas/db/etc/sqlhosts file or the /etc/services file is configured incorrectly. Failure indicates that the nethostcannot remotely access the subhost database.Please see Verifying remote database access configuration on page 77.Verifying /etc/hosts Please see Verifying Enterprise system setup on page 73 and File setup of /etc/hosts on page 73.Verifying .netrcPlease see Verifying Enterprise system setup on page 73 and File check of.netrc on page 73.Verifying system_config count Please see Verifying table IDs on page 75.Verifying Table ID consistency Please see Verifying table IDs on page 75.Verifying Host Record consistencyVerifying Seed Counter SettingsThis test can fail only if either the Startup Mode or Configure Host field for aparticular host record have been misconfigured. Refer to page 12, StartupMode, and page 12, Configure Host, for information on how to properlyconfigure these fields of the Hosts form for a nethost or subhost record.This test determines whether or not Seed Counter is enabled or disabled. Allsystems in an Enterprise system must have the same Seed Counter settings.If a mismatch is detected, a warning is displayed indicating that all hosts in anEnterprise system must have identical Seed Counter settings. To correct thisproblem, reinstall the mismatched host or hosts.Verifying /etc/services Please see Verifying remote database access configuration on page 77.Verifying of hosts time synchronization Please see Verifying hosts time synchronization on page 79.Verifying Informix ER configurationThis test verifies the ER related configuration for all configured ER hosts fromnethost, namely:• replicate definition• ER sever state• host_time table entries• ER log directory• ER cron job• ER Db space• ER Db task• ER sysadmin procedures• ER store procedures• ER Db triggers• ER Db syssequences for ER related tablesIf chkenterprise fails during Verifying Informix ER configuration for asingle host, then we recommend running the /cas/er/bin/er_verify_install_on_nethost.sh -s hostname script to identifythe ER configuration problem for this host.If chkenterprise fails during Verifying Informix ER configuration for allconfigured ER hosts, then we recommend running /cas/er/bin/er_verify_install_on_nethost.sh to identify the ER configurationproblem.A log file named erVerifyInstall.log is generated in the /cas/log/directory. Refer to this log file for more details.

68Picture Perfect 4.6 Enterprise EditionUser ManualVerifying permissions on nethost and subhostsTo ensure database integrity on the Enterprise system, the permissions for the system must be setcarefully.To verify permissions on the system:1. From a client workstation, log on to Picture Perfect as install.2. Select Control, Operators, then click the Permissions tab.3. Click Find and select the System Administrator record.Figure 6. Permissions Form4. By default the Global facility is assigned the Facility Permission: All Facility Permissions. Foreach additional facility to which this record is assigned, click the Permission Profile box andassign the appropriate Facility Permission.5. Click the Permission Group tab and verify that the Category and Area Permission Groups areset to: ALL GROUPS ALLOWED6. Click Save.Notes:• Any additional operator permission records should be a subset of the System Administrator permissions.• For the changes to take place, you must log off and log on again.7. In addition, follow the Configuration Steps as described in the Picture Perfect 4.6 UserManual. Omit steps that relate to micro hardware because there will be no micro hardware onthe nethost.

Chapter 5Verifying the configuration69Verifying communications on the nethostTo verify communications on the nethost, check the current log.mmdd file where mmdd is thecreation month and date. For example, the file log.1102 was created on November 2. The log fileis located in the /cas/log directory. The following is a typical entry displaying the communicationsbetween the nethost and the subhost:15:30:45.012 netdrv: I - pid 15139 is alive15:30:45.014 netdrv: I - listening for connect with subhost1 - 192.9.200.5015:30:45.019 netdrv: I - pid 14116 is alive15:30:45.021 netdrv: I - listening for connect with subhost2 - 192.9.200.7015:30:45.040 T P S : I - daemon 'tcmgr ' started15:30:45.070 T P S : I - daemon 'dbrfsh -bdg' started15:30:45.105 T P S : I - daemon 'dbrfsh -a' started15:30:45.124 T P S : I - daemon 'dbrfsh -b' started15:30:45.142 T P S : I - daemon 'dbrfsh -list' started15:30:45.176 T P S : I - daemon 'dbrfsh -o' started15:30:45.401 netdrv: I - obtained a connection from '192.9.200.70'15:30:45.413 netdrv: I - obtained a connection from '192.9.200.50'15:30:47.000 rcvdrv: I - pid 14139 is alive15:30:47.001 rcvdrv: I - pid 14139 opened port 9070 to subhost215:30:47.008 rcvdrv: I - pid 15164 is alive15:30:47.009 rcvdrv: I - pid 15164 opened port 9050 to subhost115:30:47.016 snddrv: I - pid 32061 is alive15:30:59.235 rsndmg: I - starting polling loop

70Picture Perfect 4.6 Enterprise EditionUser ManualVerifying Picture PerfectVerify that Picture Perfect is running on the nethost and all subhosts by using the ipcs command.This command verifies that Informix and TPS are running (attached to shared memory.)AIXTo verify Picture Perfect, type: ipcsEnterIf Informix and TPS are running, the output would appear similar to the following:Note:TPS is recognized by the KEY ending in 400 for shared memory and 401 for semaphore. For example: 0x00000400 and 0x00000401IPC status from /dev/mem as of Wed Sep 12 16:15:52 2002T ID KEY MODE OWNERGROUPMessage Queues:q 524288 0x00000414-Rrw-rw-rw-rootsystemq 524289 0x00000405-Rrw-rw-rw-rootsystemq 524290 0x00000407--rw-rw-rw-rootsystemq 524291 0x00000404--rw-rw-rw-rootsystemq 524292 0x00000415--rw-rw-rw-rootsystemq 524293 0x0000040d-Rrw-rw-rw-rootsystemq 524294 0x0000040e-Rrw-rw-rw-rootsystemq 524295 0x00000413-Rrw-rw-rw-rootsystemq 524296 0x00000403--rw-rw-rw-rootsystemq 524297 0x0000040a-Rrw-rw-rw-rootsystemq 524298 0x00000411-Rrw-rw-rw-rootsystemq 524299 0x00000402-Rrw-rw-rw-rootsystemq 524300 0x00000401-Rrw-rw-rw-rootsystemq 524301 0x0000040c-Rrw-rw-rw-rootsystemq 524302 0x00000406-Rrw-rw-rw-rootsystemq 524303 0x00000412-Rrw-rw-rw-rootsystemq 524304 0x0000040f--rw-rw-rw-rootsystemq 524305 0x00000410-Rrw-rw-rw-rootsystemq 524306 0x0000040b-Rrw-rw-rw-rootsystemq 19 0x4107001c-Rrw-rw-rw-rootprintqShared Memory:m 0 0x58059040--rw-rw--rwrootsystemm 524289 0x52564801--rw-rw----rootinformixm 524290 0x52564802--rw-rw----rootinformixm 524291 0x52564803--rw-rw----rootinformixm 262148 0xffffffffD-rw-rw-rw-rootsystemm 5 0x0d0501fc--rw-rw-rw-rootsystemm 131078 0x000000400--rw-rw-rw-rootsystemSemaphores:s 262144 0x58059040--ra-ra-ra-rootsystems 1 0x4d080035--ra-ra----rootsystems 655362 0xffffffff--ra-ra----rootinformixs 3 0x62050049--ra-r--r--rootsystems 524292 0xffffffff--ra-ra----rootinformixs 524293 0xffffffff--ra-ra----rootinformixs 524294 0xffffffff--ra-ra----rootinformixs 524295 0x00000401--ra-ra-ra-rootsystems 8 0x010500d6--ra-------rootsystemTPSInformixTPSInformixInformixTPS

Chapter 5Verifying the configuration71LinuxTo verify Informix, type: ipcs -cEnterIf Informix is running, the output would appear similar to the following:------ Shared Memory Segment Creators/Owners --------schmid permscuid cgid uid gid0 600 root root rootroot32769 600 root root rootroot1507330 600 root root rootroot98307 600 root root rootroot3244036 660 root informix rootinformix3276805 660 root informix rootinformix3309574 660 root informix rootinformix3242343 660 root informix rootinformix3375112 660 root informix rootinformix3407881 660 root informix rootinformix3240650 666 root root rootroot3473419 644 root root rootroot------ Semaphore Arrays Creators/Owners --------semid permscuid cgid uid gid0 600 root root apacheroot32769 600 root root apacheroot65538 600 root root rootroot98307 600 root root rootroot622596 600 root root rootroot655365 600 root root rootroot688134 600 root root apacheapache1114119 660 root informix rootinformix1146888 666 root root rootrootInformixInformix------ Message Queues: Creators/Owners --------msqid permscuid cgid uid gid6258688 666 root root rootroot6291457 666 root root rootroot6324226 666 root root rootroot6356995 666 root root rootroot6389764 666 root root rootroot6422533 660 root root rootroot6455302 660 root root rootroot6488071 660 root root rootroot6520840 660 root root rootroot6553609 660 root root rootroot6586378 666 root root rootroot6619147 644 root root rootroot6651916 644 root root rootroot6684685 644 root root rootroot6717454 644 root root rootroot6750223 644 root root rootroot6782992 644 root root rootroot6815761 644 root root rootroot6848530 644 root root rootroot622611 644 root root rootroot

72Picture Perfect 4.6 Enterprise EditionUser ManualTo verify TPS, type: ipcsEnterIf TPS is running, the output would appear similar to the following:------ Shared Memory Segments --------key shmidowner permsbytesnattch status0x00000000 0 root 600 10526729 dest0x00000000 32769root 600 335544329 dest0x00000000 1507330root 600 335544329 dest0x00000000 98307apache 600 46084 9 dest0x52564801 3244036root 660 3355443260x52564802 3276805root 660 3355443260x52564803 3309574root 660 3355443260x52564804 3342343root 660 3040051260x52564805 3375112root 660 3355443260x52564806 3407881root 660 3355443260x00000400 3440650root 666 16384000300x00000402 3473419root 644 20 0------ Semaphore Arrays --------key semidowner permsnsems0x00000000 0 apache 600 1 0x00000000 32769apache 600 1 0x00000000 65538root 600 1 0x00000000 98307root 600 1 0x00000000 622596root 600 1 0x00000000 655365root 600 1 0x00000000 688134apache 600 1 0x00000000 1114119root 660 7 0x00000401 1146888root 666 18 ------ Message Queues --------key msqidowner permsused-bytesmessages0x00000401 6258688root 666 0 00x00000402 6291457root 666 0 00x00000403 6324226root 666 0 00x00000404 6356995root 666 0 00x00000405 6389764root 666 0 00x00000406 6422533root 666 0 00x00000407 6455302root 666 0 00x0000040a 6488071root 666 0 00x0000040b 6520840root 666 0 00x0000040c1 6553609root 666 0 00x0000040d 6586378root 666 0 00x0000040e 6619147root 666 0 00x0000040f 6651916root 666 0 00x00000410 6684685root 666 0 00x00000411 6717454root 666 0 00x00000412 6750223root 666 0 00x00000413 6782992root 666 0 00x00000414 6815761root 666 0 00x00000415 6848530root 666 0 00x00000416 622611root 666 0 0TPSTPSTPSWhen Picture Perfect is not running, there should be no Message Queues, Shared Memory, andSemaphores for TPS or Informix. If there are entries, then Shared Memory is corrupted. SeeCorrupted shared memory on page 88 for more information.

Chapter 5Verifying the configuration73Verifying Enterprise system setupThis configuration requires some or all of the following verification procedures and modification of the /etc/hosts and .netrc files. The following sections provide file setup information for these filesalong with an example site. If you need to modify these files, use the vi or emacs editor.File setup of /etc/hostsIn an Enterprise system configuration, each system requires two or more host names (such asnethost and subhost1).The file setup of /etc/hosts is done during installation. The following table shows a typical entryin the /etc/hosts file for a nethost, subhosts, and X-Terminals or X-stations. Each line requires anentry for Internet address and host name. The alias and comment are optional.Table 7.Required Host and Subhost entries for /etc/hosts FileInternet Address Host Name Alias Comment192.9.200.100 nethost # Network Host in Boston192.9.200.50 subhost1 # Network Subhost1 in Chicago192.9.200.70 subhost2.support.ge.com subhost2 # Network Subhost2 in Boca Raton192.9.200.56 delta # Xstation in lobby in BostonFile check of .netrcThe .netrc is a file used to configure secured database communication between remote servers.Perform the following checks to ensure your configuration is properly setup.Note:The /root/.netrc (or /.netrc for AIX), and /cas/ppapp/.netrc files must be same. If theyare not the same, edit the files using an editor such as vi. The /cas/.netrc file has additionalentries for user ppadmin.To verify the /cas/.netrc file:1. Log on to the nethost and subhosts as root.2. Type the following command on the nethost:cat /cas/.netrc EnterOutput similar to the following displays:machine bctalfordlogin ppadminpassword ppadminmachine bctalfordlogin ppapppassword ppapp1

74Picture Perfect 4.6 Enterprise EditionUser Manual3. Type the following command on all subhosts:cat /cas/db/.netrc EnterOutput similar to the following displays:machine bctdoverlogin informixpassword informixTo verify the ppapp/.netrc file:1. Type the following command on the nethost:cat /cas/ppapp/.netrc Enter2. Output similar to the following displays:machine bctalfordlogin ppapppassword ppapp13. Type the following command on all subhosts:cat /cas/.netrc Enter4. Output similar to the following displays:machine bctdoverlogin ppadminpassword ppadminmachine bctdoverlogin ppapppassword ppapp1To verify the root .netrc file:1. Type the following command on the nethost:Linuxcat /root/.netrc EnterOutput similar to the following displays:machine bctalfordlogin ppapppassword ppapp1AIXcat /.netrc EnterOutput similar to the following displays:machine bctalfordlogin ppapppassword ppapp1

Chapter 5Verifying the configuration752. Type the following command on all subhosts:Linuxcat /root/.netrc EnterOutput similar to the following displays:machine bctdoverlogin ppapppassword ppapp1AIXcat /.netrc EnterOutput similar to the following displays:machine bctdoverlogin ppapppassword ppapp1Verifying table IDsMake sure the database is running before checking these tables. See Verifying Picture Perfect onpage 70 for details.1. Follow these steps to start the database on the nethost if it is not running:a. Log onto the nethost as ppadmin.b. Type the following command: oninit2. The host table ID and the system_config table ID must be identical on the nethost.Type these commands consecutively on the nethost:query system_configquery host EnterEnter3. Compare both outputs for the numbers circled in Figure 7. The ID numbers in these twopositions must match.Enter

76Picture Perfect 4.6 Enterprise EditionUser ManualFigure 7. Sample Query: Node 1[ppadmin@bctdover ~]$ query system_config1 NODE 1 0 65535 5250 6000 16000 805306368 805343248 256 100000100000 200 50000 1000 50000 2 1 2 2 2 2 2 2 3 0 1 00000 59 -99 2550 eirs2cr -t0 -c180 -k Y Y Y Y Y Y Y 500 6 64 96 1 500 1 40,, 0 0 0 96 32 1 1 /ppbackup 60 /cas/flash/eflash 6 1 1 0 0 0 1 1 1 1 1 1 /ppbackup 0 0 1 0 20081114120000[ppadmin@bctdover ~]$ query host1 6114 bctdover 3.137.174.215 2 3 5 60 N -1 20090817 756552 9004 bctalford 3.137.174.214 1 3 20 60 29 30 Y -1 200908181104173 6117 bctnaples 3.137.174.212 1 3 20 60 29 30 Y -1 200908191551324. Type the following command to stop the database if you had started it in step 1:onmode -kyEnter5. Follow these steps to start the database on the subhost if it is not running:a. Log onto the subhost as ppadmin.b. Type the following command: oninitEnter6. The host table ID and the system_config table ID must be identical on the subhost.Type these commands consecutively on the subhost:query system_configquery host EnterEnter7. Compare both outputs for the numbers circled in Figure 8. The ID numbers in these twopositions must match.Figure 8. Sample Query: Node 2[ppadmin@bctalford ~]$ query system_config2 NODE 1 0 65535 5250 6000 16000 805306368 805343248 256 100000100000 200 50000 1000 50000 2 1 2 2 2 2 2 2 3 0 1 00000 59 -99 25 50eirs2cr -t0 -c180 -k Y Y Y Y Y Y Y 500 6 64 96 1 500 1 40,, 0 0 0 96 32 1 1 /ppbackup 60 /cas/flash/eflash 6 1 1 0 0 0 1 1 1 1 1 1 /ppbackup 0 0 1 0 20081114120000[ppadmin@bctalford ~]$ query host1 6114 bctdover 3.137.174.215 0 3 5 60 Y -1 20090817 756552 9004 bctalford 3.137.174.214 2 3 20 60 N -1 20090818 1104173 6117 bctnaples 3.137.174.212 2 3 20 60 N -1 20090819 1551328. Type the following command to stop the database if you had started it in step 5:onmode -ky EnterIf the IDs of either system do not match, execute the hostconfig program. If this doesnot correct the problem, modify the ID manually.

Chapter 5Verifying the configuration77Verifying remote database access configurationTo refresh the data from one host to the other hosts, the database must be configured correctly.Check the following files on all hosts to verify the configurations.Required file entries for remote database access:Make sure that the following entry appears in the /etc/services file for each host. (If the entry ismissing, type it in manually by using the vi or emacs editor.)Table 8.Required entries for /etc/servicesService Name Port Number/Protocol Name Aliases Comments_star 9088/tcp star1 star2 # local_host Informix istar Port_star 9088/tcp # remote_host Informix istar PortThe Informix /cas/db/etc/sqlhosts configuration file must have an entry for each serverordered under the ER group the server(s) belong to as shown below:To verify the database configuration, enter the following command on the nethost:# cat /cas/db/etc/sqlhostsOutput similar to the following displays. (In this example, bctdover is the nethost and bctalford is a subhost.)#demo_on onipcshm on_hostname on_servername#demo_se seipcpip se_hostname sqlexecnethost_1 group - - i=1bctdover onsoctcp bctdover bctdover_star g=nethost_1bctdover _e onsoctcp bctdover bctdover_e_star #csm=(PPENCCSM),g=nethost_1subhost_2 group - - i=2bctalford onsoctcp bctalford bctalford_star g=subhost_2After the Enterprise system installation procedures are complete, follow these steps:1. Log on as root on the nethost console.2. Use the ping command from each host to check the Enterprise system connection of theremote host:ping remote hostname EnterYou should see output similar to the following:PING bctnaples (3.137.100.100) 56(84) bytes of data.64 bytes from bctnaples (3.137.100.100): icmp_seq=1 ttl=64 time=0.127 ms64 bytes from bctnaples (3.137.100.100): icmp_seq=2 ttl=64 time=0.182 ms64 bytes from bctnaples (3.137.100.100): icmp_seq=3 ttl=64 time=0.269 ms64 bytes from bctnaples (3.137.100.100): icmp_seq=4 ttl=64 time=0.199 ms64 bytes from bctnaples (3.137.100.100): icmp_seq=5 ttl=64 time=0.176 ms64 bytes from bctnaples (3.137.100.100): icmp_seq=6 ttl=64 time=0.154 ms

78Picture Perfect 4.6 Enterprise EditionUser Manual3. Press Ctrl -C to stop the ping command and display the ping statistics:--- bctnaples ping statistics ---6 packets transmitted, 6 received, 0% packet loss, time 5003msrtt min/avg/max/mdev = 0.127/0.184/0.269/0.046 msYou should see 0% packet loss. If packet loss is higher than this, troubleshoot yourEnterprise system.4. Execute the following command on the nethost to verify remote database access:/cas/bin/chkistar EnterIf all the subhosts and the nethost have been configured correctly, the output lists all thehosts in the Enterprise system and their remote database access status. This is a sampleoutput:nethost permits remote database accesssubhost1 permits remote database accesssubhost2 permits remote database accessWhere nethost is the name of the nethost and subhost1 and subhost2 are thenames of the network subhosts.If you receive a message similar to the following:Attempt to connect to database server (subhost2) failed.This is a failure message. Refer to the Informix error messages issued on the commandline. For information on determining the error represented by the error number, seeInformix error messages on page 88.5. Execute the following command on all subhosts to verify nethost database access:/cas/bin/chkistarhost EnterIf the nethost has been configured correctly, output similar to the following displays:Verifying remote database connection to nethostnethost permits remote database accessWhere nethost is the name of the nethost.If you receive a message similar to the following:Verifying remote database connection to nethost.Attempt to connect to database server (nethost) failed.This is a failure message. Refer to the Informix error messages issued on the commandline. For information on determining the error represented by the error number, seeInformix error messages on page 88.

Chapter 5Verifying the configuration79Verifying hosts time synchronizationPicture Perfect uses Network Time Protocol (NTP) to synchronize computer clock times in a networkof computers. NTP services are configured during the installation of the netlan or subhost packages.NTP services are started when the operating system boots up. The Picture Perfect nethost server isdesignated as the master time-keeper and runs the NTP service as Server.Note:The NTP service does synchronize server times if the server times are more than 1000 seconds apart.Running chkdbsyncThis utility lists the tables on the nethost and subhosts that are refreshed by the system. For eachtable, it lists the record count (COUNT) and the maximum value in the id field (MAXID). Therespective numbers should be the same. For example, if the COUNT is 5001 on the host, it shouldbe 5001 on the subhosts. If there is a discrepancy, then that table is not in sync.To run the chkdbsync utility:1. Log onto the nethost as ppadmin.2. At the command prompt, type:. /cas/bin/profilechkdbsync EnterEnterOutput similar to the following displays:Checking database refresher synchronization on Enterprise System...----------------------------------------------------------------TABLE COUNT MAXID----------------------------------------------------------------Number of badges on bctmonty [Host] 5001 5004 Number of badges on bcthomer [Subhost] 5001 5004 Number of badges on bctmaggie [Subhost] 5001 5004 ----------------------------------------------------------------Number of categories on bctmonty [Host] 105 104 Number of categories on bcthomer [Subhost] 105 104 Number of categories on bctmaggie [Subhost] 105 104 ----------------------------------------------------------------Number of departments on bctmonty [Host] 10 10 Number of departments on bcthomer [Subhost] 10 10 Number of departments on bctmaggie [Subhost] 19 10 ----------------------------------------------------------------Number of permission_groups on bctmonty [Host] 4 2 Number of permission_groups on bcthomer [Subhost] 4 2 Number of permission_groups on bctmaggie [Subhost] 4 2 ----------------------------------------------------------------Number of facilities on bctmonty [Host] 3 3 Number of facilities on bcthomer [Subhost] 3 3 Number of facilities on bctmaggie [Subhost] 6 5

80Picture Perfect 4.6 Enterprise EditionUser ManualNumber of host_bid_formats on bcthomer [Subhost] 2 2 Number of host_bid_formats on bctmaggie [Subhost] 2 2 ----------------------------------------------------------------Number of site_forms on bctmonty [Host] 1 1 Number of site_forms on bcthomer [Subhost] 1 1 Number of site_forms on bctmaggie [Subhost] 1 1 ----------------------------------------------------------------Number of site_lists on bctmonty [Host] 2 2 Number of site_lists on bcthomer [Subhost] 2 2 Number of site_lists on bctmaggie [Subhost] 2 2 ----------------------------------------------------------------Running ercmd.sh --statusThis command lists all differences (extra rows, missing rows, mismatches) for each of the replicatingtables on all hosts.To run the ercmd.sh --status utility:1. Log onto the nethost as ppadmin.2. At the command prompt, type:. /cas/bin/profileercmd.sh --statusEnterEnterOutput similar to the following displays:nethost_1=bctdoversubhost_3=bctalfordTable: personMay 23 2011 16:10:38 ------ Table scan for person_repl start -------------Node Rows Extra Missing Mismatch Processed----------------- -------- --------- --------- --------- ---------nethost_1 0 0 0 0 0subhost_3 0 0 0 0 0May 23 2011 16:10:38 ------ Table scan for person_repl end ---------------Table: badgeMay 23 2011 16:10:38 ------ Table scan for badge_repl start --------------Node Rows Extra Missing Mismatch Processed----------------- -------- --------- --------- --------- ---------nethost_1 0 0 0 0 0subhost_3 0 0 0 0 0May 23 2011 16:10:38 ------ Table scan for badge_repl end ----------------Table: person_userMay 23 2011 16:10:38 ------ Table scan for person_user_repl start --------

Chapter 5Verifying the configuration81Node Rows Extra Missing Mismatch Processed----------------- -------- --------- --------- --------- ---------nethost_1 0 0 0 0 0subhost_3 0 0 0 0 0May 23 2011 16:10:38 ------ Table scan for person_user_repl end ---------Table: person_categoryMay 23 2011 16:10:38 ------ Table scan for person_category_repl start ----Node Rows Extra Missing Mismatch Processed----------------- -------- --------- --------- --------- ---------nethost_1 0 0 0 0 0subhost_3 0 0 0 0 0May 23 2011 16:10:38 ------ Table scan for person_category_repl end ------Table: temp_categoryMay 23 2011 16:10:39 ------ Table scan for temp_category_repl start ------Node Rows Extra Missing Mismatch Processed----------------- -------- --------- --------- --------- ---------nethost_1 0 0 0 0 0subhost_3 0 0 0 0 0May 23 2011 16:10:39 ------ Table scan for temp_category_repl end --------Table: notesMay 23 2011 16:10:39 ------ Table scan for notes_repl start --------------Node Rows Extra Missing Mismatch Processed----------------- -------- --------- --------- --------- ---------nethost_1 0 0 0 0 0subhost_3 0 0 0 0 0May 23 2011 16:10:39 ------ Table scan for notes_repl end ----------------Table: categoryMay 23 2011 16:10:39 ------ Table scan for category_repl start -----------Node Rows Extra Missing Mismatch Processed----------------- -------- --------- --------- --------- ---------nethost_1 2 0 0 0 0subhost_3 2 0 0 0 0May 23 2011 16:10:39 ------ Table scan for category_repl end -------------Table: departmentMay 23 2011 16:10:39 ------ Table scan for department_repl start ---------Node Rows Extra Missing Mismatch Processed----------------- -------- --------- --------- --------- ---------

82Picture Perfect 4.6 Enterprise EditionUser Manualnethost_1 0 0 0 0 0subhost_3 0 0 0 0 0May 23 2011 16:10:39 ------ Table scan for department_repl end -----------Table: person_typeMay 23 2011 16:10:39 ------ Table scan for person_type_repl start --------Node Rows Extra Missing Mismatch Processed----------------- -------- --------- --------- --------- ---------nethost_1 4 0 0 0 0subhost_3 4 0 0 0 0May 23 2011 16:10:39 ------ Table scan for person_type_repl end ----------Table: host_bid_formatMay 23 2011 16:10:40 ------ Table scan for host_bid_format_repl start ----Node Rows Extra Missing Mismatch Processed----------------- -------- --------- --------- --------- ---------nethost_1 3 0 0 0 0subhost_3 3 0 0 0 0May 23 2011 16:10:40 ------ Table scan for host_bid_format_repl end ------Table: permission_groupMay 23 2011 16:10:40 ------ Table scan for permission_group_repl start ---Node Rows Extra Missing Mismatch Processed----------------- -------- --------- --------- --------- ---------nethost_1 2 0 0 0 0subhost_3 2 0 0 0 0May 23 2011 16:10:40 ------ Table scan for permission_group_repl end -----Table: custom_formMay 23 2011 16:10:40 ------ Table scan for custom_form_repl start --------Node Rows Extra Missing Mismatch Processed----------------- -------- --------- --------- --------- ---------nethost_1 85 0 0 0 0subhost_3 85 0 0 0 0May 23 2011 16:10:40 ------ Table scan for custom_form_repl end ----------Table: custom_controlMay 23 2011 16:10:40 ------ Table scan for custom_control_repl start -----Node Rows Extra Missing Mismatch Processed----------------- -------- --------- --------- --------- ---------nethost_1 816 0 0 0 0subhost_3 816 0 0 0 0

Chapter 5Verifying the configuration83May 23 2011 16:10:40 ------ Table scan for custom_control_repl end -------Table: custom_control_argMay 23 2011 16:10:40 ------ Table scan for custom_control_arg_repl start -Node Rows Extra Missing Mismatch Processed----------------- -------- --------- --------- --------- ---------nethost_1 5237 0 0 0 0subhost_3 5237 0 0 0 0May 23 2011 16:10:40 ------ Table scan for custom_control_arg_repl end ---Table: form_tabMay 23 2011 16:10:41 ------ Table scan for form_tab_repl start -----------Node Rows Extra Missing Mismatch Processed----------------- -------- --------- --------- --------- ---------nethost_1 164 0 0 0 0subhost_3 164 0 0 0 0May 23 2011 16:10:41 ------ Table scan for form_tab_repl end -------------Table: site_listsMay 23 2011 16:10:41 ------ Table scan for site_lists_repl start ---------Node Rows Extra Missing Mismatch Processed----------------- -------- --------- --------- --------- ---------nethost_1 0 0 0 0 0subhost_3 0 0 0 0 0May 23 2011 16:10:41 ------ Table scan for site_lists_repl end -----------Table: custom_list_elemMay 23 2011 16:10:41 ------ Table scan for custom_list_elem_repl start ---Node Rows Extra Missing Mismatch Processed----------------- -------- --------- --------- --------- ---------nethost_1 0 0 0 0 0subhost_3 0 0 0 0 0May 23 2011 16:10:41 ------ Table scan for custom_list_elem_repl end -----Table: time_zoneMay 23 2011 16:10:41 ------ Table scan for time_zone_repl start ----------Node Rows Extra Missing Mismatch Processed----------------- -------- --------- --------- --------- ---------nethost_1 504 0 0 0 0subhost_3 504 0 0 0 0May 23 2011 16:10:41 ------ Table scan for time_zone_repl end ------------

84Picture Perfect 4.6 Enterprise EditionUser ManualTable: time_zone_dstMay 23 2011 16:10:41 ------ Table scan for time_zone_dst_repl start ------Node Rows Extra Missing Mismatch Processed----------------- -------- --------- --------- --------- ---------nethost_1 1381 0 0 0 0subhost_3 1381 0 0 0 0May 23 2011 16:10:41 ------ Table scan for time_zone_dest_repl end -------Table: facilityMay 23 2011 16:10:42 ------ Table scan for facility_repl start -----------Node Rows Extra Missing Mismatch Processed----------------- -------- --------- --------- --------- ---------nethost_1 1 0 0 0 0subhost_3 1 0 0 0 0May 23 2011 16:10:42 ------Table scan for facility_repl end -------------Running ercmd.sh --listThis command lists the ER status (local, connected, dropped, disconnected) of each of theparticipating servers.To run the ercmd.sh --list utility:1. Log onto the nethost as ppadmin.2. At the command prompt, type:. /cas/bin/profileercmd.sh --listEnterEnterOutput similar to the following displays:SERVER ID STATE STATUS QUEUE CONNECTION CHANGED-----------------------------------------------------------------------nethost_1 1 Active Local 0 subhost_3 3 Active Connected 0 May 12 14:05:25nethots_1=bctdoversubhost_3=bctalford

Chapter 6 Troubleshooting and supportThis chapter includes information helpful in troubleshooting yourEnterprise system and offers technical support contacts in case you needassistance.In this chapter:Remote database access diagnostics . . . . . . . . . . . . . . . . . . . . 86Corrupted shared memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Informix error messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Enterprise Replication troubleshooting. . . . . . . . . . . . . . . . . . . . 89Removal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Contacting technical support . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

86Picture Perfect 4.6 Enterprise EditionUser ManualRemote database access diagnosticsThe database connection must be valid from the nethost to each subhost and from each subhost tothe nethost.To verify the database connection:1. Log on the main host as root.2. Verify that all subhosts are working by typing: chkistarEnterThe following should display:host permits remote database access.subhost1: permits remote database access.subhost2: permits remote database access.You do not need to proceed with the remainder of the steps.3. If you receive the message:attempt to connect to database server (host) failedping the subhost in question, by typing:ping subhost1 EnterThe following should display:PING subhost1.xxxxx.yyyyy.zzz (192.9.200.40): 56 data bytes64 bytes from 192.9.220.40:icmp_seq=0 ttl=255 time=2 ms64 bytes from 192.9.220.40:icmp_seq=1 ttl=255 time=2 ms64 bytes from 192.9.220.40:icmp_seq=2 ttl=255 time=2 ms64 bytes from 192.9.220.40:icmp_seq=3 t^C--- subhost1.xxxxx.yyyyy.zzz ping statistics ---4 packets transmitted, 4 packets received, 0% packet lossround-trip min/avg/max=2/2/2 ms4. Break from the operation by pressingOr type: ping -c4 subhost1CtrlCThis command performs four pings and automatically stops without pressing Ctrl C .5. Use ssh to log on to the subhost that failed chkistar.6. From the failing subhost, verify that it has database connectivity to the nethost by typing:/cas/bin/chkistarhost EnterThe following messages should display:Verifying remote database connection to nethost.nethost permits remote database access7. If the database refreshers on the main host have to be restarted, type:ps -ef | grep rfshThe following displays:Enter

Chapter 6Troubleshooting and support87root 16019 9841 0 May 11 console/0 0:59 dbrfsh -aroot 16273 9841 0 May 11 console/0 1:04 dbrfsh -broot 17046 9841 0 May 11 console/0 0:54 dbrfsh -oroot 21428 32145 1 15:33:14 1 0:00 grep rfsh8. To stop the database refreshers, type: kill -15 etc.where is the processing identification number as marked in the example above.9. Using the result from the previous step, type:kill -15 15762 16019 16273 16789 17046 17304 1781710. Turn on the database manager diagnostics by typing: setdiag 811. Check the rfs log file in the /cas/log directory and verify that the database refreshersare working by typing: rfstail EnterThe following should display:15:35:02.985 oprhis: I - subhost subhost1 oprhis row cnt = 226315:35:03.345 oprhis: I - subhost subhost2 oprhis row cnt = 888115:35:07.049 bdghis: I - subhost1 cur id 158 max shost id 15815:35:07.050 bdghis: I - poll subhost1 badge_history, id>158 and 5898 and = 19940513 and >15303412. If the log file looks OK, then turn off diagnostics by typing:setdiag 0Enterpid13. If the network fails to find a subhost, then check the remote database connection from thesubhost to the nethost by typing following command from the /cas/bin directory:EnterEnterchkistarhostEnterYou will either receive a message similar to the following:nethost permits remote database accessorAttempt to connect to database server failed14. If the connection fails, reboot the nethost and the appropriate subhost. To reboot, type:AIXshutdown -Fr nowEnterLinuxrebootEnter

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.

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"

Chapter 6Troubleshooting and support91ATSDIRServer File Size CreateNameTime---------------------------------------------------------------------------subhost_6 ats.subhost_6.subhost_3.D_50.110531_14:40:28.1 483 2011-05-3114:40:28Attempting connection to syscdr@bctcali...Using syscdr@bctcali.Source ID:3 / Name:subhost_3Target ID:6 / Name:subhost_6(1) [bid = "0268435458"]: Row not found on the source for replicate (1) [bid = "0268435458"]: Row will be deleted on the target for replicateSample output of ATS/RIS files for errors that require the system administrator to take action:root@bctlesabre3# cat /ppbackup/ats/ats.nethost_1.subhost_3.D_104.110510_01:3TXH RIS file:/ppbackup/ris/ris.nethost_1.subhost_3.D_104.110510_01:39:23.1 hasalso been created for this transaction==========TXH Source ID:3 / Name:subhost_3 / CommitTime:11-05-10 01:39:23TXH Target ID:1 / Name:nethost_1 / ReceiveTime:11-05-10 01:39:23TXH Number of rows processed when transaction was aborted:1TXH All rows in a transaction defined with row scope were rejected----------RRH Row:1 / Replicate Id: 65547 / Table: proteus@informix.host_bid_format /DbOp:UpdateRRS 3 (subhost_3)|1305005963 (11/05/10 01:39:23)RRD 3|Facility2 String10|00%10s|-1|20040202|161751root@bctlesabre3# cat ris.nethost_1.subhost_3.D_104.110510_01:39:23.1TXH Source ID:3 / Name:subhost_3 / CommitTime:11-05-10 01:39:23TXH Target ID:1 / Name:nethost_1 / ReceiveTime:11-05-10 01:39:23----------RRH Row:1 / Replicate Id: 65547 / Table: proteus@informix.host_bid_format /DbOp:UpdateRRH CDR:0 / SQL:-239 / ISAM:-100RRS 3 (subhost_3)|1305005963 (11/05/10 01:39:23)RRD 3|Facility2 String10|00%10s|-1|20040202|161751==========TXH Transaction abortedTXH ATS file:/ppbackup/ats/ats.nethost_1.subhost_3.D_104.110510_01:39:23.2 hasalso been created for this transactionIn the above example, the reason for the failure to insert a record from subhost to nethost is thatthere was a unique index violation. Depending on whether this is the primary key or not, the actionrequired would be different.• If this is the primary key, then delete the records from both hosts and recreate the record fromone of the hosts.• If the unique index violation is not on the primary key, then delete the record from one of thehosts (this decision is based on data in other fields of the record) and let the other recordreplicate.If the error cannot be handled, please contact Technical Support.

92Picture Perfect 4.6 Enterprise EditionUser ManualAlarm indicating ER database spaces at 90% capacity• Check /cas/log/chkdbspace.log for additional information.• Use ercmd.sh --status to get more information on the offending host.• Check network connectivity from the nethost to this host.• Run the cdr stats rqm command on this host to get the ER queues information.• If everything is good and it just happens to be that the amount of data being pumped to orfrom that host is very high, then the ER database spaces can be extended by using theercmd.sh --addchunks command.

Chapter 6Troubleshooting and support93RemovalThe following is a sample removal of the subhost package. The netlan package can be removedonly by removing the base package.1. Log on as ppadmin and open a terminal window.2. Type the following to shut down Picture Perfect:. /cas/bin/profile Enter rc.pperf -k Enter3. Switch to root user by typing the following command.su -Enter your root password and then press Enter .4. Start the removal program by typing:. /cas/bin/profile Enter ppr EnterOutput similar to the following displays:Picture Perfect Package Removal - /custom_pp/bin/ppr 4.6 04/25/11Copyright (C) 1989-2011 UTC Fire & Security Americas Corporation, Inc.WARNING:THIS PROGRAM WILL COMPLETELY REMOVE PICTURE PERFECT PACKAGESAND ANY DATABASES USED BY THE PACKAGE.SELECTING 'base' OR 'all' WILL REMOVE PICTURE PERFECT ENTIRELY.ARE YOU SURE YOU WANT TO PROCEED?(Type 'yes' and press the key to proceed)5. To continue, type: yesEnterIf you entered yes, a list of the Picture Perfect packages currently installed is displayed.You are then asked which package to remove. For example:The following Picture Perfect packages are currently installed:basesubhostEnter the name of the package to remove:6. Type: subhostEnterOutput similar to the following displays:Removing the subhost package.Picture Perfect Subhost package removal - Version 4.6 04/25/2011.Starting the Informix database.. Done.ER configuration cleanup process.

94Picture Perfect 4.6 Enterprise EditionUser ManualChecking for [bctdover] database ... [Done].Removing ER server from Net host.Processing [bctalford].Removing ER Local sever. [Done].Removing ER Tasks. [Done].Removing ER Stored Procedures. [Done].Removing ER Triggers. [Done].Removing Primary Keys and CRCols. [Done].Removing Sequence Objects. [Done].Removing sqlhosts group. ..[Done].Removing port from [bctdover] services fileRemoving host and refresh_config table records. [Done].Undoing hostconfig changes made by network host... [Done].Updating system_config record... [Done].Deleting pptimed entries from tps_daemons...[Done].Resetting System Administrator permissions to standalone...{Done].Removing subhost files... [Done].Removing ER Log directories {done].Removing ER DBSpaces and Logical Volumes. [Done].Removing ER onconfig parameters [Done].Shutting down the Informix database. Done.Renaming standalone files back to original names...Starting the Informix database.. Done.The Subhost package has been successfully removed.The removal process has completed. Program Exiting.The system needs to be rebooted for the changes to take affect.Reboot the system (y/n)? [y]

Chapter 6Troubleshooting and support95Contacting technical supportFor assistance installing, operating, maintaining, and troubleshooting this product, refer to thisdocument and any other documentation provided. If you still have questions, you may contacttechnical support during normal business hours (Monday through Friday, excluding holidays,between 8 a.m. and 7 p.m. Eastern Time).North AmericaT 888 437 3287F 561 998 6224AsiaT 65 639 19314F 65 639 19306AustraliaT 61 3 9239 1200F 61 3 9239 1299CanadaT 800 267 6317F 613 737 5517EMEAT 48 58 326 22 40F 48 58 326 22 41Latin AmericaT 503 691 7294F 561 994 6572Email: rs-bctsupport@fs.utc.comWeb site: www.utcfireandsecurity.com

96Picture Perfect 4.6 Enterprise EditionUser Manual

Chapter 7 FAQsThis chapter includes Frequently Asked Questions (FAQs) and answersrelated to Enterprise Replication (ER) in Picture Perfect 4.6.The FAQs are grouped under the following headings:Replication concepts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Installation and upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101ER monitoring and management . . . . . . . . . . . . . . . . . . . . . . . .113Miscellaneous. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115

98Picture Perfect 4.6 Enterprise EditionUser ManualReplication conceptsThis section includes the following FAQs:1 What is the difference between the ‘old’ refreshers and Enterprise Replication (ER)?2 Previously, changes to global replicated tables and inserts/deletes of person/badge were allowedfrom the nethost only. Is this still true?3 How are id conflicts handled when inserts are allowed from all hosts?4 Can we use max(id) to get the next id value when inserting to replicated tables?5 Are changes from a subhost propagated to other subhosts even when the nethost is not up?6 Are all tables replicated?7 Is native Informix replication used for all the tables?8 Does ER need the modify date/time information to be maintained?9 How are conflicts handled when changes are made on two hosts at the same time?10 What happens if the same table record (same primary key value) is updated from two hosts atthe same time (same timestamp)?1 What is the difference between the ‘old’ refreshers and Enterprise Replication (ER)?• The refreshers used in previous Picture Perfect versions synchronized between nethost andsubhost sequentially. Any synchronization delay with a single subhost affected all subhosts.With Informix ER in Picture Perfect 4.6, synchronization is done in parallel and is not affectedby latency to one or more hosts.• The refreshers are considerably slower than the native Informix ER.2 Previously, changes to global replicated tables and inserts/deletes of person/badge wereallowed from the nethost only. Is this still true?• Department, Personnel Type, BID format, Category, Facility, Permission Group, Time Zone,Custom List, and Custom Form records can be inserted/updated/deleted from all hosts.• Person and Badge records can be inserted and deleted from all hosts.3 How are id conflicts handled when inserts are allowed from all hosts?Each host is allocated a set of id values (sequences). The sequence ranges are as follows:• Nethost: 1 to 134 million• Subhost 1: 134 million + 1 to 268 million. . . . . .• Subhost 31: 134 million + 31 to 268 millionEach host uses a sequence value when assigning a value to an id field in replicated tables. Thesesequences need to be used during insertion to replicated tables. The stored proceduregetnextseqval('table_name') ensures the appropriate sequence and its maintenance per

Chapter 7FAQs99host. The client user interfaces and the import software provided with Picture Perfect use this storedprocedure. We recommend that all third parties also use this stored procedure.Note:Category inserts are allowed at subhosts only when the nethost database is up. The reason for this exception isthat only 64K categories are supported. Instead of partitioning the 64K between 31 subhosts, a design decisionwas made to keep track of the category count on the nethost and use a sequence object to control the creation.4 Can we use max(id) to get the next id value when inserting to replicated tables?No, the client user interfaces and the import software provided with Picture Perfect use sequences.We recommend that any third party software used to insert data to these tables also use thegetnextseqval() stored procedure. If max(id) is used, an error (SQL error -746) is returned.5 Are changes from a subhost propagated to other subhosts even when the nethost is notup?No, the nethost database needs to be up for the changes from a subhost to be propagated to othersubhosts.6 Are all tables replicated?Not all tables are replicated. Only person-related and global tables are replicated. The replicatedtables are:• person• badge• person_user• person_category• temp_category• notes (for person/badge only)• category• facility• person_type• department• permission_group• host_bid_format• custom_form• custom_list_elem• site_lists• form_tab• custom_control• custom_control_arg• time_zone• time_zone_dst

100Picture Perfect 4.6 Enterprise EditionUser Manual7 Is native Informix replication used for all the tables?Native information replication is used for all tables listed above. The history tables continue to usethe database refreshers.8 Does ER need the modify date/time information to be maintained?The main purpose of modify date/time was for the refreshers to determine which record was morerecent and refresh accordingly. Informix ER has its own timestamp column and rules to determinethis. Even though we are continuing the maintenance of the modify date/time fields, there is no needfor this information anymore.9 How are conflicts handled when changes are made on two hosts at the same time?There are two cases when conflicts may arise:• Conflicts during normal ER operation are resolved with the timestamp rule: the last change"wins". See Table 9 for a more detailed explanation.Table 9.Conflict Resolution Based on the Time StampRow exists onthe target?Time StampDatabase OperationInsert Update DeleteNo n/a Apply row Apply row (ConvertUPDATE to INSERT)Yes T last_update< T replApply row (ConvertINSERT to UPDATE)T last_update> T replDiscard rowApply rowApply row (INSERT intoER delete table)Apply rowT last_update= T replApply row if no routine is defined as a secondary conflict resolution rule.Otherwise, invoke the routine.• Conflicts during a subhost recovery or using ercmd.sh are resolved with a "master" host.This means that if records are identical with the master, even though they have a greatertimestamp, the master record always wins.There are only 2 cases when this comes into play:- If changes are made on a subhost while an upgrade is in progress (that is, the subhostwas acting as a standalone), the changes will be lost.- If a subhost was removed from the ER configuration and changes were made locally, thechanges are lost when the subhost is added back into the ER.Note: Inserts will be preserved.10 What happens if the same table record (same primary key value) is updated from two hosts at the same time (same timestamp)?In this case, the host with the lower group id' wins. In our configuration, the nethost always has thelowest (group id=1) and the subhosts have ids in the order that they were added to the system.You can see the group id information in the /cas/db/etc/sqlhosts file.

Chapter 7FAQs101Installation and upgradesThis section includes the following FAQs:1 How do I verify the installation/configuration of ER was successful?2 How long can I expect the installation/configuration to take?3 How does latency affect the configuration process?4 What is the algorithm of the initial data synchronization?5 How is hostconfig different in Picture Perfect 4.6 compared to previous versions?6 If hostconfig needs to be run multiple times to configure additional subhosts, will it reconfigureor resynchronize the already configured/synchronized hosts?7 What do I do if the hostconfig process fails?8 Why does the initial synchronization take so long?9 Will the initial synchronization be faster if I restore the same database on all hosts?10 Can the restore of data from a previous version of Picture Perfect impact the ER configuration?11 Is it possible to lose data during an installation?12 How do I check the synchronization progress?13 I have a new host to be added to ER. The new host is configured with a core or sample database.Will that be a problem when adding the host to the ER?14 I have a new host to be added to ER. I am restoring only the base data. Is this a problem?15 Will person/badge notes be synchronized? If so, since they were not synchronized in previousPicture Perfect versions, is there anything special about handling the initial synchronization?16 Why is there a new index on tables, which always includes a ifx_replcheck column?17 What is the purpose of the new database spaces (entrepdbs and entrepsbs)?18 Why were the new tables host_time and currseq added to the proteus database?19 Why do chkpptriggers and chkppprocedures list some duplicates, additional triggers, andstored procedures from standalone on the ER system?20 What if I need to make a change to the database during the upgrade?21 At what point is it not recommended to fall back to Picture Perfect 4.0?22 Can I add an existing Picture Perfect standalone server as a subhost?23 hostconfig log file reported "SQL error" messages24 Do I have to change the Custom History Reports based on database schema changes made inPicture Perfect 4.6?

102Picture Perfect 4.6 Enterprise EditionUser Manual1 How do I verify the installation/configuration of ER was successful?Once all servers are configured and up and running, use the following tools to verify that the systemis set up properly:• chkenterpriseExpected result: No errors• chkdbsyncExpected result: All global tables (person, badge, person_user, person_category, notes,department, facility, etc.) are synchronized.• ercmd.sh --listExpected result: The Status is Local or Connected (for remote servers) as shown below:Server Peer ID State Status Queue Connection Changed---------------------------------------------------------------------------nethost_1 nethost_1 1 Active Local 0subhost_2 2 Active Connected 0 May 23 11:04:11subhost_2 nethost_1 1 Active Connected 0 May 23 11:04:11subhost_2 2 Active Local 0• ercmd.sh --status [-b table_name]Expected result: The Extra, Missing, and Mismatch columns show a value of 0.nethost_1=bctdelhisubhost_2=bcthydTable: personMay 24 2011 12:19:37 ------ Table scan for person_repl start --------Node Rows Extra Missing Mismatch Processed---------------- --------- --------- --------- --------- ---------nethost_1 288734 0 0 0 0subhost_2 288734 0 0 0 0May 24 2011 12:19:42 ------ Table scan for person_repl end ---------Table: badgeMay 24 2011 12:19:42 ------ Table scan for badge_repl start --------Node Rows Extra Missing Mismatch Processed---------------- --------- --------- --------- --------- ---------nethost_1 203839 0 0 0 0subhost_2 203839 0 0 0 0May 24 2011 12:19:45 ------ Table scan for badge_repl end ---------Table: notesMay 24 2011 12:20:19 ------ Table scan for notes_repl start --------Node Rows Extra Missing Mismatch Processed---------------- --------- --------- --------- --------- ---------nethost_1 50 0 0 0 0subhost_2 50 0 0 0 0

Chapter 7FAQs103May 24 2011 12:20:19 ------ Table scan for notes_repl end ---------Table: categoryMay 24 2011 12:20:19 ------ Table scan for category_repl start --------Node Rows Extra Missing Mismatch Processed---------------- --------- --------- --------- --------- ---------nethost_1 1602 0 0 0 0subhost_2 1602 0 0 0 0May 24 2011 12:20:19 ------ Table scan for category_repl end ---------Table: departmentMay 24 2011 12:20:19 ------ Table scan for department_repl start -------Node Rows Extra Missing Mismatch Processed---------------- --------- --------- --------- --------- ---------nethost_1 60 0 0 0 0subhost_2 60 0 0 0 0May 24 2011 12:20:19 ------ Table scan for department_repl end -------.• cdr list repl [-c group_name] [replicate_name]Note:The command can be entered from any server. The group_name is the name of the group to which theserver belongs to (for example: nethost_1 for nethost, subhost_2 for the first subhost, subhost_3 for thesecond subhost, etc.). The replicate_name is the table name with the _repl suffix (for example:person_repl for the person table).Expected result: The State is Active on all servers where the command is run and forevery table replicate defined.CURRENTLY DEFINED REPLICATES-------------------------------REPLICATE: person_category_replSTATE:Active ON:nethost_1CONFLICT:TimestampFREQUENCY: immediateQUEUE SIZE: 0PARTICIPANT: proteus:informix.person_categoryOPTIONS:row,ris,ats,floatieee,triggers,fullrowREPLID:65539 / 0x10003REPLMODE:PRIMARY ON:nethost_1APPLY-AS:INFORMIX ON:nethost_1REPLICATE: custom_list_elem_replSTATE:Active ON:nethost_1CONFLICT:TimestampFREQUENCY: immediateQUEUE SIZE: 0PARTICIPANT: proteus:informix.custom_list_elemOPTIONS:row,ris,ats,floatieee,triggers,fullrowREPLID:65549 / 0x1000dREPLMODE:PRIMARY ON:nethost_1APPLY-AS:INFORMIX ON:nethost_1REPLICATE: time_zone_dst_replSTATE:Active ON:nethost_1

104Picture Perfect 4.6 Enterprise EditionUser ManualCONFLICT:FREQUENCY:QUEUE SIZE:PARTICIPANT:OPTIONS:REPLID:REPLMODE:APPLY-AS:.Timestampimmediate0proteus:informix.time_zone_dstrow,ris,ats,floatieee,triggers,fullrow65555 / 0x10013PRIMARY ON:nethost_1INFORMIX ON:nethost_12 How long can I expect the installation/configuration to take?For a database containing about 500K person and badge records, the approximate Enterpriseinstallation/configuration times are as follows:• Netlan and subhost packages:- < 5 min• Initial data synchronization (done as part of hostconfig):- AIX – First subhost < 90 min. Subsequent subhost < 60 min (assuming no latency).- ercmd.sh --recover_status -b can be used to monitor thesynchronization progress.3 How does latency affect the configuration process?If a subhost connection has a high latency (>150ms, overseas server), the server configurationprocess could take several hours due to the database mechanism used to synchronize the databasewith the nethost.In this case, we strongly recommend an individual backup of the converted base database into anindependent file in addition to the regular converted database backup(s).To perform an additional backup for only the converted database, please follow the steps below fromthe command line:1. Log in to a terminal session as ppadmin.2. Set the Picture Perfect profile by running:./cas/bin/profile3. Start up the database by running:oninit4. Perform the converted database backup by running:cba -c -b -v -d -baseNote:This creates a backup of the converted base database to the file named . Use that backup during the installation of the subhost with high-level network latency.Then ONLY that converted base database file must be used during the "base" package installation ofthat subhost. This method greatly reduces the time required to synchronize the high volume of datain the badge/person section of the database with its counterpart on the nethost.

Chapter 7FAQs1054 What is the algorithm of the initial data synchronization?It is very important to understand that the native Informix ER synchronization depends on somethingcalled the "master". This is the host whose data is trusted and should be used in case of anyconflicts.During the initial installation, the nethost is always the master. This means, if a subhost acting as astandalone was making changes, those changes would be lost. Thus, it is very important that whenupgrades are going on no data changes are made. However, new records can be added. Newrecords are preserved during the upgrade.5 How is hostconfig different in Picture Perfect 4.6 compared to previous versions?In addition to its functions in previous versions, in Picture Perfect 4.6 hostconfig performs thefollowing functions:• configures all necessary items for Informix Enterprise Replication (sqlhosts, sequenceobjects, primary keys, stored procedures and triggers, server and tables replication definition)on the nethost and on each subhost (as defined in the host table)• synchronizes the replicated table data on the nethost and subhost(s)• checks minimum settings for the new server in advance to prevent any issues during theprocess synchronization processThe nethost is treated as the master for data synchronization. The only exception to this rule occurswhen the nethost crashes and is reinstalled and added back to the Enterprise system. In this case,hostconfig determines that ER is already configured on the subhost(s) and uses the first subhostas master and synchronizes the data to the nethost. For the rest of the subhosts, the nethostbecomes master and synchronizes to them.An example of the hostconfig output is shown below. Note the report showing the final serverconfiguration status at the end of the output.-----------------------------------------------------------------------------Picture Perfect hostconfig utility - Version 4.6 05/15/2011Copyright (C) 1989-2011 UTC Fire & Security Americas Corporation, Inc.-----------------------------------------------------------------------------Starting the Informix database.. [Done].Checking sqlhosts file... bctdelhi[*]Checking Subhosts availability...o Processing [bcthyd]... [OK]Checking SSH configuration...o Processing [bcthyd]... [OK]Processing [bctdelhi]Updating sqlhosts file for [bctdelhi]...dbservername bctdelhi already in sqlhosts file [Done]Updating hcomm_ingrp field on host table... [Done].Updating istar_ingrp field on host table...Checking for replication status... [Done]Configuring sqlhost file for ER... [Done].Configuring remote sqlhosts file(s) for ER... [Done].Configuring Sequence Objects.... [Done].Initializing 'currseq' table.... [Done].Configuring Primary Keys and CR Column.......................... [Done].Configuring Stored Procedures for ER... [Done].

106Picture Perfect 4.6 Enterprise EditionUser ManualConfiguring Triggers for ER... [Done].Configuring Enterprise Replication Server... [Done].Configuring Enterprise Replication Replicates.... [Done].Configuring Enterprise Replication Scheduled Task(s)... [Done].Processing [bcthyd]Adding service bcthyd with port 6115.Checking for [bcthyd] database.... Starting up, please wait .... [Done].Stopping Informix database to update sqlhosts with subhost 'bcthyd'.. [Done].Starting the Informix database.. [Done].Copying .netrc to bcthyd ppadmin and ppapp homedirectories [Done].Updating hcomm_ingrp field on host table...Checking for replication status... [Done]Configuring sqlhost file for ER... [Done].Configuring remote sqlhosts file(s) for ER... [Done].Configuring Sequence Objects.... [Done].Initializing 'currseq' table.... [Done].Configuring Primary Keys and CR Column.... [Done].Configuring Stored Procedures for ER... [Done].Configuring Triggers for ER... [Done].Bouncing bctdelhi and bcthyd databases to set changes. Please wait......... [Done].Configuring Enterprise Replication Server... [Done].Configuring Enterprise Replication Replicates..... [Done].Configuring Enterprise Replication Scheduled Task(s)... [Done].Process for database synchronization...----------------------------------------------------------------NOTE: Depending on each server database synchronization status,this process can take several minutes. Please wait...o Processing [bctdelhi]... [Skipping] nethost.o Processing [bcthyd]...Recovering [bcthyd] server... [FLAGS: SD SD SK]Table Name Records Start-End Time================================= ========= =================o category: ....................... [ 1601] 14:05:39 14:05:41o facility: ....................... [ 728] 14:05:41 14:05:42o person_type: .................... [ 48] 14:05:42 14:05:43o department: ..................... [ 60] 14:05:44 14:05:45o permission_group: ............... [ 335] 14:05:45 14:05:46o host_bid_format: ................ [ 9] 14:05:46 14:05:47o custom_form: .................... [ 183] 14:05:47 14:05:49o custom_list_elem: ............... [ 1289] 14:05:49 14:05:51o site_lists: ..................... [ 106] 14:05:51 14:05:53o form_tab: ....................... [ 577] 14:05:53 14:05:54o custom_control: ................. [ 3441] 14:05:54 14:05:56o custom_control_arg: ............. [ 22916] 14:05:56 14:06:00o time_zone: ...................... [ 517] 14:06:00 14:06:02o time_zone_dst: .................. [ 1537] 14:06:02 14:06:03o notes: .......................... [ 29] 14:06:03 14:06:06o temp_category: .................. [ 23] 14:06:06 14:06:08o person_category: ................ [ 254612] 14:06:08 14:06:36o person_user: .................... [2011583] 14:06:36 14:10:06o badge: .......................... [ 203839] 14:10:06 14:10:37o person: ......................... [ 288734] 14:10:37 14:11:20Resynching sequences at [bcthyd] server... [Done]Resynching sequences at [bctdelhi] server... [Done]>[bcthyd] synch. process [Done]

Chapter 7FAQs107Enterprise Configuration Status Report.=========================================SERVER NAMESTATUS ACTION TO DO=================================================== ====== ============o bctdelhi........................................... [ OK][ ]o bcthyd............................................. [ OK][Reset micros]=================================================== ====== ============All hosts configured successfully.6 If hostconfig needs to be run multiple times to configure additional subhosts, will itreconfigure or resynchronize the already configured/synchronized hosts?No, hostconfig will skip over the already configured hosts.7 What do I do if the hostconfig process fails?The recommended upgrade process is to migrate the nethost first. Once the nethost is upgraded,migrate one subhost at the time and run hostconfig for each subhost.This migration method ensures that the synchronization is finalized for each new subhost and theoutcome of each step determines how to proceed next:• If the migration succeeds, continue with next server.• If the migration fails, correct the issues with current server being processed or continue withnext server while previous one is being fixed.If hostconfig fails for a subhost, take the following steps:1. Take note of the "error message".2. Review the current /cas/log/hostconfig.log. file and look forthe "error message".3. Review the /cas/log/er.log file and look for the "error message".4. Locate the problem, correct it, and run hostconfig one more time.Common problems are:- Subhost is not reachable; no response to ping.- Subhost is not configured for SSH connection with the nethost.- Subhost is not installed with subhost package.- Subhost is currently running Picture Perfect.Another cause for hostconfig to fail is an accidental stop of the process by pressingCtrl+C. In this case, we recommend removing the server from the configuration byentering the following command and then running hostconfig again:/cas/er/bin/ercmd.sh --remove_ER # No arguments required.

108Picture Perfect 4.6 Enterprise EditionUser Manual8 Why does the initial synchronization take so long?During initial synchronization, in addition to the regular data being synchronized, the ifx_replcheckcolumn is populated on each record. Informix requires the ifx_replcheck column to compare datausing the cdr check command. This is very time consuming; hence the delay.9 Will the initial synchronization be faster if I restore the same database on all hosts?No, in fact it may be slower!Synchronization could be done using two different Informix cdr processes, either sync or check.• sync is chosen if there is no data on the target server or if the differences are > 100000.- sync transfers all record data and populates the ifx_replcheck column. It does not use logical logs; therefore, it is not I/O bound.• check is chosen if the number of record differences is > 0 and < 100000.- During initial synchronization (no data in ifx_replcheck column), check updates theifx_replcheck column for each record using logical logs.- check then compares data on both servers (using ifx_replcheck) and synchronizes anydata differences.This additional step and the fact that it is I/O bound (usage of logical logs) are the reasonswhy check is much slower than sync.For the above reasons, if the person/badge database is large or if a subhost has high latency, werecommend that you do not restore person/badge data on the subhosts and let the initialsynchronization restore that data from nethost to subhosts.10 Can the restore of data from a previous version of Picture Perfect impact the ERconfiguration?Yes, it can. ER cannot be configured if there is a violation of primary keys on the replicated tables.During ER configuration, primary keys (unique non-null data in those fields is required) are added toeach of the replicated tables. If there is null data in these fields that is not unique, the ERconfiguration (hostconfig) fails.Example: When we restored customer data with null data in the person_id + slot number (primarykey on person_category table) field, the ER configuration failed.Run the chkpk.sh script to validate the data for any primary key violations.Refer to section “Picture Perfect 4.6 database interface changes” in the Picture Perfect 4.6 Tablesand Fields Reference Manual for primary key definitions for each of the replicated tables.

Chapter 7FAQs10911 Is it possible to lose data during an installation?Yes, it is possible that changes made on the subhost are lost while an upgrade is underway.An upgrade means that a subhost has been installed, but ER has not been configured on it yet. Thesubhost is functioning as a standalone server and data changes are being made.During the initial ER configuration, the nethost acts as the 'master' and data changes (updates on thesubhost) are lost.The recommendation is to have a data freeze while the upgrade is underway.12 How do I check the synchronization progress?• Use ercmd.sh --recover_status to check the synchronization progress (time left forsynchronization to complete).• User ercmd.sh --status to check the differences in records for each of the replicatingtables.If you know (from hostconfig output) which table is getting synchronized at the time, you cancheck for synchronization progress using the commands:• ercmd.sh --status -b and• ercmd.sh --recover_status -b 13 I have a new host to be added to ER. The new host is configured with a core or sampledatabase. Will that be a problem when adding the host to the ER?We do not recommend using the core or sample database because there could be several tables(host_bid_format, time_zone_dst, etc.) with default records that could conflict with records at thenethost that may have been changed. Even though the nethost is the master, if there is a dataconflict on primary key data, then synchronization does not occur.We recommend restoring the base data on all hosts and badge data as appropriate. However, do notrestore badge data on a subhost if the badge database is large or if the subhost has high latency.14 I have a new host to be added to ER. I am restoring only the base data. Is this a problem?If the base data restored on the new host has primary key data that clashes with the nethost data,then there will be synchronization issues on those records. To repair this, perform the followingsteps:• Delete the record with the synchronization issue from the server where the data is incorrect/old.• Then, run ercmd.sh --recover_table on the table with the issue on the server wherethe delete was done.

110Picture Perfect 4.6 Enterprise EditionUser Manual15 Will person/badge notes be synchronized? If so, since they were not synchronized inprevious Picture Perfect versions, is there anything special about handling the initialsynchronization?Yes, person/badge notes will be synchronized/replicated with ER.As person/badge notes were independent (not replicated) in previous versions, they would probablyhave same id values on the different hosts. During initial synchronization (hostconfig), the idvalues of the notes records on the different hosts are reset using the sequence number in the rangefor that host. The person/badge notes are then merged and synchronized across the entire system.16 Why is there a new index on tables, which always includes a ifx_replcheck column?This is an Informix ER requirement for the command cdr check to run efficiently. This commandchecks differences in the data on the hosts.17 What is the purpose of the new database spaces (entrepdbs and entrepsbs)?These are new database spaces used by Informix ER to hold transactions when the memory queuefills up and spooling starts. They are sized to 40% of the base database space size. When this spacefills up to 90%, an alarm is generated. Under normal conditions, this should never occur. If it does, itimplies that a host in the ER setup is offline and should be disconnected from ER (by usingercmd.sh). An option also exists within ercmd.sh to extend this database space.18 Why were the new tables host_time and currseq added to the proteus database?The host_time table keeps the times on each of the hosts and is replicated from subhosts to nethost.The nethost has the times of all the hosts. The table is used to determine which subhost is the causeof ER database spaces being filled up.The currseq table ensures that max(id) is not used during inserts of records to the replicating tables.19 Why do chkpptriggers and chkppprocedures list some duplicates, additional triggers,and stored procedures from standalone on the ER system?To ensure the usage of sequence values and prevent usage of max(id) for id values during inserts toreplicating tables, some standalone triggers/stored procedures have been modified and some newones have been added.20 What if I need to make a change to the database during the upgrade?Once the upgrade process has begun, we strongly recommend freezing the database to ensureminimum impact to database synchronization between all servers in the installation.If a change is required during the upgrade, any changes to the database (not related to Historytransactions) must be written down so that they can be applied to the new system once it is up andrunning (replicating, databases synchronized).Usually, person-related data is changed on the nethost (person/badge/category or anything accessrelated), and device-related data (micro/reader/door) is changed on the subhost.If both the old and new systems up and running (that is, both nethosts are running), changes can bemade on both systems without waiting for the upgrade to finish.

Chapter 7FAQs11121 At what point is it not recommended to fall back to Picture Perfect 4.0?A fallback to the old version is not recommended when the nethost and the first subhost are installed,their databases are completely synchronized, and the micros start communicating with the subhost.The following scenarios illustrate how a fallback could be managed:A. Existing Picture Perfect 4.0 production servers are upgradedIf the existing Picture Perfect 4.0 servers match the minimum system requirements for PicturePerfect 4.6 and the end user plans to use them for the upgrade, the database must be convertedon the production servers. Once the conversion is done, the database is no longer functional in aPicture Perfect 4.0 environment. If a fallback to version 4.0 is needed, it may be necessary toreinstall the operating system and Picture Perfect 4.0 software on the production servers.In this scenario, we recommend a fallback to version 4.0 before upgrading the first subhost.B. Spare servers are available for database conversion; existing servers are upgradedWhen spare servers are available, the database can be converted and validated on the spareservers before reinstalling the production servers. The old system continues to control theEnterprise installation during the conversion process. The conversion will not damage theproduction servers.In this scenario, a fallback is not recommended after the production nethost and first subhost areconfigured and the databases are synchronized.C. New servers are provided; spare servers are not available for database conversionThis scenario is similar to scenario A, except that the old Picture Perfect 4.0 servers are stillavailable and can be brought back online easily by performing a drop-reload of the database.The OS does not need to be reinstalled.In this scenario, a fallback is not recommended after the new nethost and first subhost areconfigured, the databases are synchronized, and the micros start communicating with the newsubhost.22 Can I add an existing Picture Perfect standalone server as a subhost?An existing Picture Perfect Standalone server cannot be migrated easily to a Picture PerfectEnterprise 4.6 system. The main constraint is that the global tables must be synchronized with thenethost. For global tables, the standalone may have already used same range of record ids withdifferent data, which can cause loss of records when the tables are synchronized with the nethost(master).In this case, please contact UTC Fire & Security Enterprise Consulting to estimate the work requiredto merge the data from the Picture Perfect standalone server in the Enterprise Replication system.

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.

114Picture Perfect 4.6 Enterprise EditionUser Manual- If the problem persist, use the ercmd.sh command with --recover_table argumentto synchronize the record(s).• ER server stopped or suspendedThis alarm may appear in different conditions, for example, when the server is processingtoo many transactions at the time, or the network connection is down and the replicationqueues are backing up,- If this alarm occurs, use the ercmd.sh command with --list argument to check thestatus of all servers in the configuration.- If you see a server that is disconnected from the nethost, execute the cdr startcommand from the servers reporting the issue.- If the problem persists, please contact UTC Fire & Security Customer Support for furtherassistance.• Server clock out of syncThis alarm displays when there is a difference of 16 or more seconds in the clocksbetween the nethost and any subhost.- Run the date command on the servers and adjust the clocks accordingly.• Sequence object 90% full (The maximum of allowed ids per host is 134M.)This alarm indicates that a sequence object that maintains the current id for a replicatedtable exceeds 90% of its defined limit.- This is not a trivial issue. Please call UTC Fire & Security Customer Support for furtherinvestigation.4 How can I tell if the ER database spaces are reaching capacity?The alarm that is raised when the base database reaches 90% capacity is also raised when the ERdatabase spaces reach 90% capacity.Additional information on the reason why the database space is getting filled up is provided in /cas/log/chkdbspace.log.

Chapter 7FAQs115MiscellaneousThis section includes the following FAQs:1 In what scenarios will I lose data?2 In what scenarios will the hosts be out of sync?3 In what scenarios will the micros and the hosts be out of sync?1 In what scenarios will I lose data?During normal ER operations, you will not lose any data.Data (especially updates and sometimes deletes) can be lost during the following scenarios:• If an older subhost is switched to a standalone server running Picture Perfect 4.6 and localchanges are made. These changes are lost when the subhost package is installed and thehost is added to the ER configuration.• If a subhost is removed from the ER configuration and changes are made on the subhost.When the subhost is added back to the ER configuration, the local updates and deletes willbe lost.• If a nethost is removed from the ER configuration and changes are made on the nethost andsubhosts. When ER is added back on the nethost, the updates on the subhosts will be lostand the deletes on all hosts may be lost.• If the nethost crashes and is reinstalled. While the nethost is down, changes are made on thesubhosts. After nethost is reinstalled and hostconfig is run to reconfigure ER on it,hostconfig detects that ER is configured on the subhosts and uses subhost1 as themaster. hostconfig re synchronizes the data to nethost and then the nethost becomes themaster. The data from the nethost is then synchronized to the subhosts. In this case, allchanges from subhost1 are included in the ER, but updates and deletes from other subhostsare lost.2 In what scenarios will the hosts be out of sync?• If you make a large number of changes on a host and the host is shut down before itpropagates the changes to other hosts, data will be out of sync.• If the initial hostconfig does not complete, the hosts will be out of sync.• If ATS/RIS conflicts arise, hosts can be out of sync.• During installation, if different databases are restored, even after initial synchronization giventhat records will have the same ID, but different content (including content of primary keys)data will be out of sync, since ER cannot resolve them. This applies if one host uses acustomer database and the other uses a sample database.• Restore of data disables ER. This is intentional. The restored data is usually older data and isnot intended to be synchronized to all hosts. Thus, after an restore.sh, hosts could be outof sync.

116Picture Perfect 4.6 Enterprise EditionUser Manual• If a subhost has been removed from ER (using ercmd.sh --remove_ER), the database willbe out of sync.• If a host has a high latency, it is possible that the data has not made it to the host andinconsistencies may be reported.3 In what scenarios will the micros and the hosts be out of sync?When person-related data (badge, person, person_category, temp_category) is synchronized(through hostconfig or ercmd.sh --recover*) and triggers are not fired, the data changes arenot sent to the micro. In this case, the system administrator has to determine the changes madeduring the synchronization and decide which micros need resetting. Therefore, it is important for theadministrator to know about the differences (that is, to know which data will be synchronized) beforethe synchronization command is run.

117IndexAAIX .....................................................................................................2, 66Bbadge table..............................................................................................3Cchkdbsync..............................................................................................79conventions ............................................................................................. iCorrupted Shared Memory .................................................................88DDatabase synchronization ..................................................................49database table sizes ..............................................................................3EEnterprise ................................................................................................2IInformix ...................................................................... 70, 71, 77, 78, 88Informix Error Messages.....................................................................88IP addresses ...........................................................................................3ipcs ........................................................................................... 70, 71, 72LLinux........................................................................................... 2, 23, 66Nnethost ................................................................................................2, 6network host............ 2, 6, 19, 22, 23, 49, 50, 51, 61, 65, 69, 73, 80Pparameters ..............................................................................................3ping........................................................................................... 66, 77, 86ppadmin ................................................................................... 11, 19, 22RRemote Database Access ..................................................................77Ssafety terms and symbols ......................................................................iseed counter ...........................................................................................3subhost ........................... 2, 6, 14, 19, 23, 47, 52, 61, 65, 67, 69, 73subhost, Removal ................................................................................93system topology......................................................................................2Ttechnical support ..................................................................................95TPS..............................................................................12, 66, 70, 72, 88VVerifycommunications on the network host ...........................................69Enterprise System Setup................................................................73Host Record consistency................................................................67host times..........................................................................................67Informix is running ...........................................................................66Network Connection........................................................................66Operating System Type..................................................................66Picture Perfect..................................................................................70Remote Connectivity by rsh ...........................................................66Remote Database Access Configuration.....................................77Seed Counter Settings....................................................................67system_config count .......................................................................67Table ID consistency.......................................................................67Table IDs...........................................................................................75TPS is running..................................................................................66/etc/hosts...........................................................................................67/etc/services......................................................................................67/root/.rhosti........................................................................................67Symbols.netrc ......................................................................................................73/etc/hosts ...............................................................................................73/etc/services ..........................................................................................77

118Picture Perfect 4.6 Enterprise EditionUser Manual