Verify that there is a project in TAR Oracle deployment that may require downtime and maintenance, and the host may fail to be started due to host faults. In case of temporary backup, the data volume is huge, TB-level backup cannot be performed in conventional mode. Therefore, the method of storage copy is considered to verify the deployment scheme using tar. Although the use of cold backup is very limited and seems to be invisible to many people, the conventional migration method is intolerable when archiving is not enabled and the data is huge, direct Copy is an option when storage and Gigabit bandwidth are used. The environment is Linux 5 + Oracle 10201 0. stop the application and database emctl stop dbconsoleshutdown immediate; lsnrctl stop listener1. package tar-zcpf u01.tar.gz u01 #/u01 as the oracle installation directory 2. transmit scp u01.tar.gz root@192.168.56.102: u01.tar.gz 3. decompress tar-zxf u01.tar.gz-C/4. permission package includes permissions. You can also manually modify the permission chown-R oracle: oinstall/u015. run the script/u01/oracle/oraInventory/orainstRoot. sh/u01/oracle/product/10.2.0/db_1/root. sh6. oracle user environment variable scp. bash_profile oracle @ 19 Listen 56.102:. bash_profilesource. bash_profile 7. Configure oratab. By default, it will be automatically created after the above script is executed. If it is not manually added, you can. Cat/etc/oratabGT10G:/u01/oracle/product/10.2.0/db_1: N 8. modify the listening address and tns address. If the host name is used, remember to change the address to the local machine. Vi $ ORACLE_HOME/network/admin/listener. oravi $ ORACLE_HOME/network/admin/tnsnames. ora9. start the instance and open the Database startup SQL> select * from v $ version; BANNER restart Oracle Database 10g Enterprise Edition Release 10.2.0.1.0-64 biPL/SQL Release 10.2.0.1.0-ProductionCORE 10.2.0.1.0 ProductionTNS for Linux: version 10.2.0.1.0-ProductionNLSRTL Version 10.2.0.1.0-Production-EOF-