best practice for swapping out a deployment server

Things are complicated.  New machine names, new operating systems, I want all of the EST

so install a new copy of JDE on your new deployment server, goto edelivery to get the media if you cannot locate it on your old deployment server.

Then, detach the planner and metadata databases on your OLD deployment server.  Make sure that activeConsole is not being used.  this is done from the planner\data directory and calling detach_planner.bat and detach_metadata.bat scripts.  These can take 30 minutes to run.

Copy the files from the old dep server planner\data and planner\spec dir to a new location

attach the original files on your original deployment server again by calling the attach_planner and attach_metadata scripts from the planner\data directory

Now you can synchronise your entire E910 dir from your old deployment server to the new one (I tend to create E910_vanilla and E910_client under the JDEdwards directory.

Now you need to detach the planner and metadata databases on your new deployment server before you do any folder renames.

Now you can rename the E910 dir’s above, replacing the vanilla with the one from your other server

Now you can attach the database files with the scripts in the new DIR structure.

Note also that attach is WAY quicker than detach!

Errors I had:

C:\Oracle\E1Local\database\oradim.log contained the following

Tue Sep 22 16:00:41 2015<BR>c:\Oracle\E1Local\bin\oradim.exe -startup -sid 
e1local -usrpwd *&nbsp; -log oradim.log -nocheck 0 <BR>Tue Sep 22 16:00:46 
2015<BR>ORA-01122: database file 12 failed verification check<BR>ORA-01110: data 
file 12: 'D:\JDEDWARDS\E910\PLANNER\SPEC\SPEC_E910.DBF'<BR>ORA-19734: wrong 
creation SCN - control file expects converted plugged-in datafile

C:\Oracle\diag\rdbms\e1local\e1local\trace

Read of datafile 'D:\JDEDWARDS\E910\PLANNER\SPEC\SPEC_E910.DBF' (fno 12) header 
failed with ORA-19734<BR>Rereading datafile 12 header failed with 
ORA-19734<BR>Errors in file 
c:\oracle\diag\rdbms\e1local\e1local\trace\e1local_ora_2068.trc:<BR>ORA-01122: 
database file 12 failed verification check<BR>ORA-01110: data file 12: 
'D:\JDEDWARDS\E910\PLANNER\SPEC\SPEC_E910.DBF'<BR>ORA-19734: wrong creation SCN 
- control file expects converted plugged-in datafile<BR>ORA-1122 signalled 
during: alter database open...

Note that the detach script for metadata at least probably will not work – yes this is a pain.  Reasons are simple.  You’ve just installed vanilla JDE and you want to attach your other dep server data files.  Of course you’ve not applied special instructions to the new dep server, as it’s new.  Therefore the fixes in the latest planner are not on your new dep server install – you have a problem.

Grab the script from your planner\data dir of your old deployment server (that has had planner ESU’s applied and also has had special instructions applied) – you’ll then be able to detach and attach.

How do you know this worked: login to planner and goto gh9612 – if you see ESU’s you know you are golden!

 

I’ll tell you more along the way, but above is good for getting your ESU history and architecture onto the new dep server.