E1: UPGTC: Issues with Upgrade Table Conversions And Oracle Databases - Separate DB servers / instances For Production And Development (Doc ID 647082.1)

Last updated on MAY 30, 2017

Applies to:

JD Edwards EnterpriseOne Tools - Version SP24 and later
Information in this document applies to any platform.


Symptoms

Customer doing an Upgrade on separate Database servers / instances for Production and Development environments. Windows platform - Oracle database.

When installing the Platform Pack, the process creates SY900, DD900, OL900 on both the servers as mandatory components.  When the Pristine and Development upgrade plan has been prepared, the production server is specified as Database server for System, OL and DD.

Everything with the upgrade works fine until you get to the table conversions.  When running Table Conversion Workbench, the table conversions start, but it prompts for the ID and password for Production Databases and populates "TESTDTA" in the ID field. 
For some reason it is trying to connect to SY900, DD900 and OL900 with the ID 'TESTDTA'.

Similarly it attempts to connect to the SY900 on Development Database Server with the 'SY900' ID, which we believe it is correct.

Changes

Customer doing an EnterpriseOne software upgrade on separate Database servers / instances for Production and Development environments.Running Table Conversion Workbench.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms