select a.empl_id, a.ssn_id, a.orig_hire_dt, a.term_dt, a.spvsr_name, a.first_name, a.last_name, a.birth_dt, a.visa_type_cd, b.annl_amt, b.sal_amt, b.hrly_amt, b.title_desc from deltek.empl a, deltek.EMPL_LAB_INFO_ADT b where a.empl_id=b.empl_id order by b.annl_amt;

Steps to migrate 32 bit oracle 9i database to 64 bit 10g database:

1, Make backups of 32 bit 9i database. Cold backup, export, RMAN, etc. You need to have export file for migration. You can use user system to export entire database.

2, Install 64 bit Oracle 10g.

3, Create required tablespace, users etc.

4, Import 9i export dump file to 10g (fromuser=user1 touser=user1).

5, Check archive log.

PURPOSE

The purpose of this document is to demonstrate a restore of an RMAN cold backup to a different host than the original target.

SCOPE & APPLICATION

This note is intended for DBAs and Support Personnel.

NOTE: This document is using a MS Windows server, for a Liunx server, certain commands might have a different syntax.

Restoring an RMAN Backup to Another Node (server)
————————————————-

In certain circumstances, it may be desirable to restore a database from an RMAN backup onto a machine other than the original host.
* to recover data at a given point in time
* to duplicate a production instance
* to verify RMAN backup

Example
——–
Restore RMAN backup from Costpoint production server on us01ap18 to standby database server on us01ap19

The example assumes:

- the target database is on us01ap18
- the database is to be restored onto tus01ap19
- the RMAN catalog is installed on us01ap19.
- the directory structure of us01ap18 is the same as us01ap19
- the ORACLE_SID will not change for the restored database
- a recovery catalog is being used
- the backups were carried out to disk (for illustrative purposes, and to disassociate from any media manager specific issues)