UTF8 Migration and Virtual columns when using Oracle tools

Products

• CA Automic One Automation
• CA Automic Workload Automation - Automation Engine

Issue/Introduction

When running a migration from a non-UTF8 database to a UTF-8 database in preparation for the upgrade to version 24, the decision may be made to use Oracle tools instead of the provided UTF-8 DB Migration Action Pack workflow.  When reviewing the Oracle prerequisites for something like the Oracle DMU tool, a warning may come up about virtual columns.  Looking at the existing database, there are virtual columns with names like:

AH, SYS_NC00131$
OT, SYS_NC00005$
OVW, OVW_VALUEX
PMMA, SYS_NC00008$

What is Broadcom's recommendation for these columns?

Resolution

The Oracle database creates the virtual columns in the background rather than Automic doing so.  It looks like it will do this for blob columns or in some cases for indexes.  In order to find out how these are created and what to do with a migration tool, Oracle should be consulted; Broadcom will not be able to help with this. 

Broadcom does provide a tool for the migration through the UTF-8 DB Migration Action Pack.  This workflow will take the database table by table and row by row, moving them from the source (original) database to the destination or target (new) database, converting the data as it does so.