Home
Forums
New posts
What's new
New posts
New profile posts
Latest activity
Advertise
Members
Current visitors
New profile posts
Resources
Log in
Register
What's new
New posts
Menu
Log in
Register
Install the app
Install
Home
Forums
JD Edwards® Enterprise One / One World Discussions
JD Edwards® EnterpriseOne Technical
Upgrade 9.1 to 9.2 on New Hardware
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="ajunker" data-source="post: 199780" data-attributes="member: 55156"><p>Hello,</p><p></p><p>I have performed several JDE upgrades on my own usually staying on the same hardware or using the swapping out server methods. Due to our old hardware being so behind, I installed a whole new 9.2 on new hardware. It is fully functional. I can log log in via web, build packages, and the fat client is working great. I plan to redo customizations or import them via .par files after the upgrade. I have created data sources to my old 9.1 system and I ran a test upgrade plan and it failed. I restored via snapshot and am going to give it another try. Before, I run through the process again, I see an error in my jde.log file "Error opening index file "C:\jdedwards\e920\dv910\spec\jdeblc.xdb" (and other files in this folder). The error is true because that folder doesn't exist. Do I need to copy my dv910's specs folder from the old servers to my new 9.2 servers and put them in this location? Also, do I have to copy the 910 databases to the 920 database server or can they just stay in place since I created the ODBC and data sources to the old 9.1 database server? I added database security etc. for the 9.2 accounts on the old 9.2 database server. I just don't understand why it is looking for the specs in this path. Could anyone explain? What else could I be missing before I run another upgrade plan? I don't see any other errors in the jde.log file for this run. I'm tempted to just copy the folder there and do another run and see what happens.</p><p></p><p>Thanks,</p><p>Amy</p></blockquote><p></p>
[QUOTE="ajunker, post: 199780, member: 55156"] Hello, I have performed several JDE upgrades on my own usually staying on the same hardware or using the swapping out server methods. Due to our old hardware being so behind, I installed a whole new 9.2 on new hardware. It is fully functional. I can log log in via web, build packages, and the fat client is working great. I plan to redo customizations or import them via .par files after the upgrade. I have created data sources to my old 9.1 system and I ran a test upgrade plan and it failed. I restored via snapshot and am going to give it another try. Before, I run through the process again, I see an error in my jde.log file "Error opening index file "C:\jdedwards\e920\dv910\spec\jdeblc.xdb" (and other files in this folder). The error is true because that folder doesn't exist. Do I need to copy my dv910's specs folder from the old servers to my new 9.2 servers and put them in this location? Also, do I have to copy the 910 databases to the 920 database server or can they just stay in place since I created the ODBC and data sources to the old 9.1 database server? I added database security etc. for the 9.2 accounts on the old 9.2 database server. I just don't understand why it is looking for the specs in this path. Could anyone explain? What else could I be missing before I run another upgrade plan? I don't see any other errors in the jde.log file for this run. I'm tempted to just copy the folder there and do another run and see what happens. Thanks, Amy [/QUOTE]
Verification
Post reply
Home
Forums
JD Edwards® Enterprise One / One World Discussions
JD Edwards® EnterpriseOne Technical
Upgrade 9.1 to 9.2 on New Hardware
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
Accept
Learn more…
Top