Re: create database by using hot backup

ibm_97_at_yahoo.com wrote:

See the Oracle Backup and Recovery Guide.

Below is some stuff in my shop. Ignore the custom scripts.

>Steps to create to clone a Oracle instance and rename the database name

1. Verify disk space: df -k
2. Create new initXXXX.ora file in $ORACLE_HOME/dbs and link with $ORACLE_BASE/admin/XXXX/pfile
3. Create backup control file in udump. ALTER DATABASE BACKUP CONTROLFILE TO TRACE;
4. Copy trace to CREATE subdirectory under $ORACLE_BASE/admin/XXXX/
5. Verify instance shutdown from SVRMGR if it already exist. If this box has the Sun HAC on consult the UNIX SYSADM before starting.
6. Run ofaren to rename files to new OFA standard: ofaren XXXX YYYY
7. Run ofaadd to create files to new OFA standard if they don't exist: ofaren XXXX
8. If needed copy cold DBF files to OFA libraries. /u*/oradata/XXXX
9. Update /var/opt/oratab
10. Update .profile with new ORACLE_SID; Issue .PROFILE and check via ENV command.
11. Modify trace control file. a) Update REUSE to SET and b) Verify RESETLOGs and Remove NOARCHIVELOG c) Remove comments; Verify ALTER commands for DATABASE are gone. d) Update XXXX to YYYY via substitute command.
12. Update Listener.ora and tnsnames.ora to point at YYYY Recycle listener: lsnrctl stop lsnrctl start
13. STARTUP DATABASE NOMOUNT after verifying proper directory from svrmgrl.
14. Run control file create. cntlXXXX.SQL
15. If this is a hot backup you will net to perform the following until to recovery point. a) Alter database recover until cancel using backup controfile; b) Alter database recover logfile ' /path/1_xxxx_YYYY.arc'; This one will prompt for the next archive. c) Alter database recover automatic logfile '/path/1_xxxx_YYYY.arc'; This one will not prompt for the next archive. d) Alter database recover cancel; e) Alter database open resetlogs.
16. Alter Database open resetlogs;
17. Commit;
18. Use SQLPLUS to verify via dual and query v$datafile on name and status.
19. Use client software to verify TNSNAMES.
20. Shutdown and startup the database again.
21. If possible use DBSHUT and DBSTART to verify oratabs.
22. Turnover to developers