E1: UPG: How To - Users Are Not Able To Login To Standard Environments On Deployment Server - EnterpriseOne 9.0 - Environments Using PLANNER Specs
(Doc ID 781672.1)
Last updated on MAY 30, 2017
Applies to:JD Edwards EnterpriseOne Tools - Version 8.98 to 8.98 [Release 8.98]
Information in this document applies to any platform.
In this scenario here, this is an EnterpriseOne software upgrade from EnterpriseOne 8.12 to 9.0 application release level.
Customer is not able to use standard Environments on 9.0 deployment server with OEE.
They upgraded with OEE as local database on a new Deployment server.
Customer had just performed two different upgrades using OEE and tried to log into the standard environments on the new 9.0 Deployment server. The spec databases for these environments, schemas and tablespaces are not in the OEE structure. They are not able to login, they get an error messages as the spec files could not be found.
None of the non-Planner pathcodes have tables in EnterpriseOneLocal.
For this OEE install, checking the spec.ini, it is set to:
PLANNER_DataSource=Local - PLANNER Specs
DV900_DataSource=Local - PLANNER Specs
PD900_DataSource=Local - PLANNER Specs
PS900_DataSource=Local - PLANNER Specs
PY900_DataSource=Local - PLANNER Specs
For all the pathcodes, different than previous E1 application release installs, where it was set to the default FA package.
So, should all the pathcodes on the deployment server now use the planner specs, which this is set too?
Is this new for OEE local database and /or for EnterpriseOne 9.0? In either case, the OEE pathcode tablespaces are NOT in OEE, in either installation.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document