Oracle migration in Different windows systems

Oracle migration in Different windows systems is an Oracle system running in a Windows operating system environment. Unfortunately, Oracle cannot be used when the Windows System of disk C is reinstalled. What will you do at this time. The most stupid and safe way is to reinstall the oracle system. As we all know, it is easy to copy the oracle System File and configure the environment variables in linux, but it is not that easy in windows. The Oracle database system is not only some oracle system files, but also some configuration information closely related to the Registry and windows Services. What's more, if the Windows system is upgraded instead of being reinstalled, for example, from Windows2003 to Windows2008, what should we do? Although the Windows version of www.2cto.com is upgraded, as long as the Oracle system runs normally on the new system, we can run ORACLE without reinstalling Oracle. In this case, oracle 10.2.0.4 running on Windows2003 needs to be migrated to a new purchase server. New servers, as you know, generally only the latest system can be installed. Here, Windows2008 is installed. What would you do if it was you? I first thought of installing oracle 10.2.0.1 on Windows and then upgrading to 10.2.0.4. Because you are not familiar with windows and cannot learn it well, use the most stupid but safe method. However, oracle 10.2.0.1cannot be installed on windows2008. if setup.exe is executed, it will be aborted and an unknown error will be reported. Oracle previously provided a version of 10.2.0.3 for vista. It is said that it can be installed on windows2008. However, it cannot be downloaded on the oracle website. This version of windows is R2. select the property at the right-click setup.exe and select the compatible mode, and it is not compatible with windows. There is no other way to configure it manually. Note: I have confirmed from the oracle document that Windows can run oracle 10.2.0.4, so I want to manually configure it. If you cannot run oracle 10.2.0.4, You Have To Upgrade oracle to 11 GB. At the beginning, I thought, referring to the migration method in linux, I would configure the environment variables, copy and copy the oracle system files, and see if the database instances in the Oracle system files can be started. Script code set PATH = D: \ oracle \ product \ 10.2.0 \ db_1 \ bin; % PATH % set ORACLE_HOME = D: \ oracle \ product \ 10.2.0 \ db_1 set ORACLE_SID = mikidb set these three environment variable values in cmd, connect using sqlplus/as sysdba, Trc code D: \ oracle \ product \ 10.2.0 \ db_1 \ database> sqlplus/as sysdba SQL * Plus: Release 10.2.0.4.0-Production on Wed Jan 9 11:18:23 2013 Copyright (c) 1982,200 7, Oracle. all Rights Reserved. ERROR: ORA-12560: TNS: protocol adapter error The result is a "ORA-12560: TNS: protocol adapter error" error reported directly to me. This error may occur because the operating system user does not belong to the ora_dba group, the listener is not started, the windows service is not configured or started, and the parameter configuration is incorrect. On Windows, the System user has already been in the ora_dba group because of the installation of 11 GB. Listening and windows services are not available yet. I also tested dbca database creation operations, in the database creation progress bar 2%, an error, reported ORA-12560. I searched metalink and said it was a bug. On windows 2008, oracle 10.2.0.4 may occur, so you have to download the patch package to apply. Because there is no oinventory, I applied opatch for a long time. Txt code Symptoms Install Oracle 10.2.0.3 (Vista/2008 version) on Windows 2008 Active Directory Controller. when trying to create the database, around 2% completion, the error ORA-12560 will occur. this Problem can occur on both 32bit and 64bit. this Problem does NOT reproduce on a Member server. only the Active Directory Controller. cause BUG 7263061. solution For Oracle 10.2.0.4: This issue has been Resolved in the Oracle 10.2.0.4 Patch 14 patch. patch number 7677780 (MS Windows 32bit), or Patch number 7677781 (MS Windows 64bit (x64 )). NOTE: You will need to be at the 10.2.0.4 version, before applying this patch. when opatch applied the patch package, I forged the oinventory information again. Copy the oracle directory of the program file of the C drive of windows2003. The opatch apply operation is successful. I will go back to the windows Service and create a new windows Service manually. But how to create a new one? No experience. google it. Oradim-new-sid mikidb-startmode auto-pfile d: \ oracle \ product \ 10.2.0 \ db_1 \ database \ INITmikidb. the ORA service is successfully created at once, but it cannot survive in the windows Service. The system cannot find the file. What is the file to be searched? You can add oracle information in the registry. Refer to the oracle software registry information on windows 2003 and add the record to it. After that, I exported a copy. Txt code Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE \ SOFTWARE \ ORACLE] @ = "" inst_loc "=" C: \ Program Files \ Oracle \ Inventory "[HKEY_LOCAL_MACHINE \ SOFTWARE \ ORACLE \ KEY_OraDb10g_home1]" ORACLE_BASE "=" d: \ oracle \ product \ 10.2.0 "" ORACLE_BUNDLE_NAME "=" Enterprise "" ORACLE_GROUP_NAME "=" Oracle-OraDb10g_home1 "" ORACLE_HOME "=" d: \ oracle \ product \ 10.2.0 \ db_1 "" ORACLE_HOME_KEY "=" SOFTWARE \ ORACLE \ \ Users "" ORACLE_HOME_NAME "=" OraDb10g_home1 "" ORACLE_SID "=" mikidb "" ORA_mikidb_AUTOSTART "= hex (2): 54,00, 52,00, 55,00, 45,00, "ORA_mikidb_SHUTDOWN" = hex (2): 54,00, 52,00, 55,00, 45,00, 00,00 "0000" = hex (2): 69,00, 6d, 00, 6d, 64,, 69, 00, \, 00, "ORA_mikidb_SHUTDOWN_TIMEOUT" = hex (2): 39,00, 30 ,00, "NLS_LANG" = "SIMPLIFIED timeout" and then use Oradim deletes and recreates the service. Www.2cto.com Trc code D: \ oracle \ product \ 10.2.0 \ db_1 \ database> SC delete OracleServicemikidb [SC] DeleteService success D: \ oracle \ product \ 10.2.0 \ db_1 \ database> oradim-new-sid mikidb-startmode auto-pfile d: \ oracle \ product \ 10.2.0 \ db_1 \ database \ INITmikidb. ORA Instance created. finally, I was given an instance created feedback. To the windows service, you can manually restart the service. After environment variables are configured in cmd, you can use sqlplus/as sysdba to connect to the instance. At this point, the oracle 10.2.0.4 instance can run on windows 2008 and the task is completed. Think about it. If you don't apply that patch, it won't work. I restored the oracle directory of drive d to no patch, and found that OK, no ORA-12560 error, the instance is normal. You can use dbca to create a database. It should be that this ORA-12560 problem has nothing to do with this bug, the root cause is that I am not configuring correctly at the beginning. To sum up, there are three main configurations during windows OS migration. 1. Whether the operating system user group has ora_dba; 2. Whether oracle items are configured in the registry; 3. Whether the windows Service has created a database instance service. These three items are all correct and generally can be successful. Other configurations, such as Listener Configuration, can be configured with netca. Source http://mikixiyou.iteye.com/blog/1766889