E1: PKG: Package Directory Not Created to \<PathCode>\bin64 After 9.2.6.x (Release 22) Upgrade from 32-Bit Tools Release
(Doc ID 2818530.1)
Last updated on APRIL 25, 2023
Applies to:
JD Edwards EnterpriseOne Tools - Version 9.2 and laterInformation in this document applies to any platform.
Symptoms
After Upgrading to Tools Release 9.2.6.x from prior 32-bit Tools Release, a <PackageName> directory is not created to \<PathCode\bin64 in Enterprise server when building a new full package.
NOTE: From tools 9.2.6, a new functionality called Zero Downtime Deployment for applications that allows customers being able to deploy application packages without a downtime event. This new functionality has to change path code directory structure on Enterprise server as following:
*Full Package Build creates <PackageName> directory under \<PathCode>\bin64 and copy dlls from \<PackageName\bin64 to \<PathCode>\bin64\<PackageName>
*Full Package Build creates <PackageName> directory under \<PathCode>\spec and also creates spec.ini with data source information under \<PathCode>\spec\<PackageName>
*Full Package Build creates <PackageName> directory under \<PathCode>\bin64 and copy dlls from \<PackageName\bin64 to \<PathCode>\bin64\<PackageName>
*Full Package Build creates <PackageName> directory under \<PathCode>\spec and also creates spec.ini with data source information under \<PathCode>\spec\<PackageName>
In the svrpkgbuild.log from the enterprise server, it contains the following but no indication of creating D:\JDEdwardsPPack\E920\DV920\bin64\<PackageName>:
Changes
Upgrading Tools Release to 9.2.6 from previous Tools Release with 32-bit foundation.
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |