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.

Moving the DE database to new hardware

book

Article ID: 41059

calendar_today

Updated On:

Products

DSERIES- SERVER CA Workload Automation DE - System Agent (dSeries)

Issue/Introduction

Introduction: 

We need to move the DE database to new hardware

Background:  

CAWA DE is configured for a database cluster. We are moving the databases to new hardware. We want to move the databases one at a time while CAWA is up. 
What should the behavior be when the DB is moved? 
Any watch out's? 
Any CAWA DE steps that should be done before the DBs are moved? 

Environment:  

A database cluster

Instructions: 

Due to the database is not in the scope of the DE maintenance responsibilities we do not have any requirements for the database itself however generally we strongly recommend to shut the DE server down prior any external manipulations with the database data. 

For the DE functionality it is an imperative to provide a stable connection to the database; by the concept of the clustering, we would expect that while moving the db nodes the DE will continue to be operational by proper switching its connection, and therefore no inordinate steps should be considered. 

But if the cluster moving also supposes a new connection url, the DE would require the restarting in order to activate this new url. 
NB. A connection url is set/updated with the setdbparm script.

Environment

Release: WKLOEB01300-11.3-Workload Automation-Agent for Oracle EBusiness Ste
Component: