I'd love to hear from anyone who has done this successfully and not had pain down the line. This was done at FAA, prior to my joining the team. Here are places we've found bad server references and God knows how many I haven't found -
*CAI:AppRegistry
*AR.conf
*Server Ranking (and all the server group tables)
*AST:ARServerConnection
*TMS:AppliationRegistry
*SYS:Escalations
*SYS:Attachments
** any work flow that didn't maintain it self server independent or where the Advanced option was used to purposely point to a specific server
Kelly Deaver
L-3 Stratis / FAA Contractor
Kelly Deaver
L-3 Stratis / FAA Contractor
_Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_-------- Original Message --------
Subject: server group config tables (ARS 7.1 patch04)
From: Frex Popo <[email protected]>
Date: Fri, February 26, 2010 6:45 am
To: [email protected]
**
Dear all,We sat up a preproduction remedy server (cloned from one of the production nodes in a server group) and we also copied the server group remedy database. We managed to get the preproduction server working along with EIE and the rest of the services.. However some of the objects (server group tables in particular) are still being references at server start up (at least). In the Admin tool, I still see the server group name being read fromservgrp_config table etc... I Did a select on sysobjects and saw the followings:servgrp_config
servgrp_applic
servgrp_board
servgrp_op_mstr
servgrp_userlicSo the question is which of the above 's data can be removed without compromising the system. Are there any other forms /tables e.g (server operation ranking) whose data needs to be updated to bear the new configuration for the new server.Many thanks
frex
_Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_

