ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

ZDU - PWP is down after switching to the target version

book

Article ID: 187290

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine CA Automic One Automation

Issue/Introduction

During the ZDU in step 4 the PWP of the target version stops and a WP of the base version takes the role of PWP


In the logs you see the following

PWP switch is initiated here:

20200123/114014.737 - U00003316 Zero Downtime information: MixedMode='Y', base MQSet='1', active MQSet='1', own MQSet='1', MQSet PWP='1'.
20200123/121130.237 - U00011896 Zero_Downtime_Upgrade mode 'UPGRADE' initiated. Start of server-table (name, type, MQSet, host, port):
20200123/121130.371 - U00003316 Zero Downtime information: MixedMode='Y', base MQSet='1', active MQSet='2', own MQSet='1', MQSet PWP='1'.

PWP is switching to target but then back. As reported by the first WP of the target version:

20200123/121130.280 - U00003475 Server 'AUTOMIC#WP001' is the primary server of the system 'AUTOMIC'.
20200123/121130.297 - U00011818 Server 'AUTOMIC#WP001': Mode changes from 'NORMAL' to 'PRIMARY'.
20200123/121236.093 - U00003396 The Server did not respond for '10' seconds. Server 'AUTOMIC#WP002' is now the primary Server.
20200123/121246.119 - U00003491 There is a time difference of '0/00:00:00' or '0' seconds to the Primary Server.
20200123/121246.119 - U00003475 Server 'AUTOMIC#WP002' is the primary server of the system 'AUTOMIC'.
20200123/121246.128 - U00011818 Server 'AUTOMIC#WP001': Mode changes from 'PRIMARY' to 'NORMAL'.

A CP of the base version reports the switch back to the base version:

20200123/121130.290 - U00003475 Server 'AUTOMIC#WP001' is the primary server of the system 'AUTOMIC'.
20200123/121230.228 - U00003475 Server 'AUTOMIC#WP002' is the primary server of the system 'AUTOMIC'.
20200123/121230.380 - U00003475 Server 'AUTOMIC#WP001' is the primary server of the system 'AUTOMIC'.
20200123/121330.286 - U00003475 Server 'AUTOMIC#WP002' is the primary server of the system 'AUTOMIC'.

The PWP of the base version after switch to target and back to base version:

20200123/121230.413 - U00005145 MQSet ('2') of the data structure differs from the MQSet ('1') of the Automation Engine.
20200123/121230.413 - U00003422 WARNING: Cannot load conversation memory '002adca9' for server routine 'UCMAIN_R'.
20200123/121230.413 - U00009907 Memory dump 'Input memory' (Address='0x3ffb9e4d010', Length='116')
20200123/121230.413 -           00000000  5356435F 464E4441 30310000 00000000  >SVC_FNDA01......<
20200123/121230.413 -           00000010  000022A7 4155544F 4D494320 20202020  >.."§AUTOMIC     <
20200123/121230.413 -           00000020  20202020 55433420 43503120 20202020  >    UC4 CP1     <
20200123/121230.413 -           00000030= 20202020 20202020 20202020 20202020  >                <
20200123/121230.413 -           00000060  20202020 00000000 00000000 00000000  >    ............<
20200123/121230.413 -           00000070  00000000                             >....<
20200123/121230.416 - U00011801 Error in Server routine 'UCMAIN_R', Server: 'AUTOMIC#WP002' AE system: 'AUTOMIC'.
20200123/121230.416 - U00003422 WARNING: Cannot load conversation memory '002adca9' for server routine 'UCMAIN_R'.
20200123/121230.425 - U00015006 System forced memory trace dump.

 

Cause

This is an issue related to the inter action with the Service Manager

Environment

Base Release (initial version from which ZDU is being run): Less than 12.2.9

Target Release (version that ZDU is being use to update to): 12.3.x

Component : AUTOMATION ENGINE

Resolution

To avoid this 'SVC_FND' error, turn off the SMGR_AUTO_SCAN within UC_SYSTEM_SETTINGS before ZDU.

There have also been numerous fixes to ZDU that have resolved this in the past.  Make sure the base version is initially on 12.2.9 or higher before running the ZDU to go to 12.3.5

Additional Information

In general expertise team, commends to deactivate SMGR_AUTO_SCAN, because on huge system with many agents this can lead to a blockage of the CP sockets.

SMGR_AUTO_SCAN should only be temporarily activate when new Agents are introduced for their complete integration.