The application you can more or less port over, database you can import from database export dump file, what is more difficult and uncertain are all the little bits and pieces of scripts or programs and little customization here and there scattered all over and added by all the different past sys admins these are the real unknowns, there no way to know what is left out until you port over, thats why I advocate preserve the old disk or if possible build on another system, unless you are very confident of the upgrade that you are planning to do otherwise don't destroy the old system.
Another thing is you cannot expect people in this forum to migrate whole system for you, we are not your helpdesk many of us have our own systems to support. We can offer advise but the rest is up to you, you have to make it your own way.
If you think this migration is very difficult please get professional help, is not possible to migrate based on somebody advise from forum, somebody needs to be familiar with the system and If you say you are new to Unix, seriously I cannot think of a reason why you would agreed to do this in first place? If the system you migrated cannot startup have you thought about what will happen to you or your job?
---------- Post updated 08-10-09 at 10:16 AM ---------- Previous update was 08-09-09 at 10:45 PM ----------
I've been thinking about how you can try to do this. Since you dunno anything about unix can try this first.
Maybe as a trial for yourself, you can do a DR on your own server using seperate new hardisk to get a feel for what it is like and maybe build some confidence level in this and also treat it as a feasibility study.
Quote:
Preparation:
Take level 0 cold backup of database.
Take df -k output
Take ifconfig -a
Take netstat -rn
Take seperate backup of /etc
eg: (tar cvfp /tmp/etc.tar ./etc) <<-- relative tar using ./
Logon to your database
sqldba
connect internal
spool /tmp/listing.txt
select file_name from dba_data_files;
spool off
Quote:
Simulated DR
==========
Install on new hardisk or new system Solaris 2.6 with all the patches.
Use same IP address from ifconfig -a output
Create the filesystem based on df -k output and listings.txt
restore your database including the oracle_home, oracle binaries
move etc.tar to new server and place under /var/tmp
under /var/tmp run tar xvfp ./etc.tar so you will have /var/tmp/etc
copy in file by file from /var/tmp/etc to /etc on new system.
Files like passwd, shadow, hosts, resolv.conf, nsswitch.conf, system, services
Reboot the new system try to startup your database and use your application, does it comes up? does it works? What is missing, take note of what is missing what is giving error. Why is it giving error, take note of whatever is giving error and whatever it missing & refer to your old system for help.
You need to resolve all the errors before you proceed with any migration because the migration you gonna face these similar problems. If you cannot resolve don't do the migration, if you still want to do the migration without resolving these errors, go stick your head into the lions cage or stick your hand into the polar bear cage, it's a faster suicide.
That's why DO NOT DESTROY the old system.
Once you accomplished this DR you will have more confidence and can have better idea what the migration going to be like.
