Search

Wednesday, June 22, 2016

Planning to Renovate old Apps Server Hardware

Our some of the Sister's companies complaining since long time, they are facing frequent restart of server and very slow performance of database application and different type of issues. As we are having very old server based on Windows 2003 and Oracle 9i database with the patched version of 9.2.0.7. We have very limited disk capacity and memory size as well as hardware configuration is very old due to this we are facing issues. Finally we have made two plan to renovate the hardware of these server as well as decided to increase some database parameters. As we are not having the complete idea of different application running on the server as well as not having the same patched version of oracle binaries. So we decided not to go fresh installation of OS/Oracle binaries/Applications on some of the server. Here in this article you can find the plan and its steps. The detail working procedure you can find with my separate post of link below:
  1. Install the Oracle into New server and Restore and recover the full backup of old DBserver.
  2. Get the Oracle Environment from system restore and use RMAN and other process to synchronize the data after testing.
The actual process to prepare new sever is the Restore & Recover    the database after fresh installation of oracle software on destination server but if you are facing the complexity of running application as well as same patched version or if you do not have idea about Instillation process of any running software or facing any other complexity, we have another option to follow the System backup & Restore policy.
Plan A:
Consider the Drive structure and OS version is same. Perform fresh installation of oracle software and apply the required patch (if any) and use RMAN restore & recovery procedure to synchronizes the data. Check my other post “How to perform this plan: Plan A: Renovate old Apps Server Hardware
Steps:
  1. Install the Oracle software only in New server and Apply the related patch
  2. Take RMAN full Hot or Cold backup of source database and copy to the same location on destination server.
  3. Create PFILE from Production server and Copy to the destination server.
  4. Create required folder on destination drive.
  5. Create Oracle service for Windows.
  6. Configure TNS and Listener setting as you can access the Prod, TEST, RMAN database.
  7. Create Password file for New Server database.
  8. Use the RMAN Duplicate Database concept to duplicate the database.
  9. Compare the Test Database with Prod DB after successful.
  10. Create the Temp file and Activate Archivelog switch for New Database.
  11. Install the entire running application on the new server.
  12. Perform Tuning of Database and Application and keep it under testing process (7 days).
  13. After verification apply restore and recover procedure again.
  14. Change the port of new server same as previous DBserver.
  15. Make this server Active for end user.
Plan B:
Get the same oracle binaries from system Restore & Recovery Procedure and use RMAN and other recovery process to synchronize the data after testing. Check the other post how to manage successful system restore and how to perform this plan: Plan B Renovate old Apps Server Hardware
Steps:
  1. Create pfile from spfile on Prod database.
  2. Backup & Restore whole system of Prod DB on Destination Server.
  3. Make either RMAN HOT or COLD Backup of Prod Database and copy it to the destination server location.
  4. Make sure to check the exiting folder file, pwdfile, Windows services on the destination server.
  5. Configure the TNS and Listener for Prod/Test/RMAN database
  6. Start the database using Pfile in nomount phase and Restore the Spfile and Controlfile.
  7. Take the database in Mount phase and Restore & Recover the database.
  8. Open the database and verify the successful restore and recovery.
  9. Verify All the Application is running successfully with normal behavior by keeping the server under testing few days.
  10. If all are well, disconnect the original server and Restore & Recover the database with latest prod Backup.
  11. Switch the Production server IP and Name with the new server and activate for end user.
Follow the Link for Detail description of Plan: