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.

Datacom/AD: How to Fallback to 14.0 and when to run AXACTDDR

book

Article ID: 199604

calendar_today

Updated On:

Products

Datacom Datacom/AD

Issue/Introduction

We are reviewing the active upgrade process for CA Datacom/AD using an application like CA 11, CA 7, etc.

We have requirements to have a backout plan documented. The documentation states that running the back out job AXACTDDR is "rare"

What would be the "rare" circumstance that I would need backout and run AXACTDDR?   

Environment

Datacom/AD 14.0

Datacom/AD 15.0

Datacom/AD 15.1

Resolution

Once you have submitted the last two active upgrade jobs (AXACTDD1 & AXACTDD2) for 14.0 to 15.1, this would complete the active MUF upgrade process for one candidate version 14.0 MUF instance. Please look at the details down below if and when it would be necessary to run the fallback (AXACTDDR) job and reload the previous "old" Datadictionary 14.0. 

The DD upgrade is designed in such a way that even if the software needs to back out to the Version 14.0 level, it will run the same against a Version 15.x DD, and therefore this fallback job (AXACTDDR) is not required. At a high level, running AXACTDDR will only remove new entities created for Version 15.x, which the Version 14.0 software will not know about. There is less harm in leaving these new entities in place than in trying to fallback.

AXACTDDR is not necessary unless the Datacom/AD 15.1 DD is absolutely destroyed or if the DD/DDD gets corrupted somehow whether it would be through, bad DASD, user errors, or something unusual. Almost all AD clients only touch the DD when they create the database for their base application. After that, it is uncommon they touch the DD again.