Migrate from 32 bit to 64 bit using RMAN

Tested: Oracle 9i R2

OS: Windows 2003 server

This article describes the very simple procedure to migrate a database from Windows 32 bit system to 64 bit using RMAN. Follow the steps below when the need arises to build a new Oracle Applications database instance (for a test migration or when re-organizing an existing production instance, for example). Before starting, plan carefully for such issues as the location of new DATAFILES and space considerations. The steps below specifically address the need to refresh a User-Test / Development instance with current production data.
Migrating through RMAN is much faster than Import/export but using the export/import utilities to rebuild your instance instead of cloning because an export/import rebuild provides the opportunity for clean-up and correction.

Step 1: Take a Backup on Source 32 Bit Server:

Connect the rman target to create a full backup of the database including all archivelogs:

CMD>RMAN TARGET SYS/*****@orcl3 CATALOG catalog/catalog@shaan

run {

Comments

Changing National Character Set AL16UTF16 to UTF8

Changing National Character Set AL16UTF16 to UTF8 The national character set is used for data that is stored in table columns of the types NCHAR, NVARCHAR2, and NCLOB. In contrast, the database character set is used for data stored in table columns of the types CHAR, VARCHAR2 and CLOB. Like the database character set, the national character set is defined when the database is initially created and can usually no longer be changed, at least not easily or without involving quite a lot of work (export, recreate database, import). Except when creating the database, where the national character set is defined explicitly, it can change implicitly even when upgrading the database from Oracle8i to Oracle9i (or Oracle10g). You require SYSDBA authorization to change the national character set. Changing the national character set means changing an Oracle Dictionary entry, but no data is changed. $sqlplus /nolog SQL> CONNECT / AS SYSDBA SQL> Select property_...

How to Monitor RMAN Backup through SQL Query

To Monitor RMAN you can use OEM or any other tools such as "Quest Backup Report for Oracle". You can also used following Views in oracle 9i to check the RMAN backup status: v$rman_configuration v$backup_set v$backup_piece v$backup_spfile v$session_longops Script to check RMAN Configuration: SELECT name "PARAMETERS", value "RMAN CONFIGURATION" FROM v$rman_configuration ORDER BY name; PARAMETERS RMAN CONFIGURATION BACKUP OPTIMIZATION ON CHANNEL DEVICE TYPE DISK FORMAT 'H:\ORABACK\%U' CONTROLFILE AUTOBACKUP ON CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'H:\ORABACK\%F' DEFAULT DEVICE TYPE TO DISK RETENTION POLICY TO RECOVERY WINDOW OF 30 DAYS Script to List RMAN Backup Piece: SELECT bs.recid, DECODE( bp.status, 'A', 'Available', 'D', 'De...

How to Remove Oracle services from Windows

How to Remove Oracle services from Windows If you have uninstall the Oracle software from your system, but, the services are not removed. This resulted, when you are trying to install oracle back and trying to configure your Instance as old name is not allowed. Method1: To remove OracleService , go to the command prompt and type: oradim -delete -sid <SID> where SID is the sid of your database, as it appears when you type net start | more (you should get an "OracleServiceSID") Method2: If you have the resource kit, you can use delsrv.exe to remove the listener service. If you don't have the resource kit, you can download delsrv.exe from Microsoft Support: http://www.microsoft.com/windows2000/tec… Method3: Go to Registry (Type regedit on RUN) Take a backup of Registry. (For the backup Click on file menu on Registry and export your registry backup any location so whenever required you can import your old registry.) Now go to registry HKEY_L...

Oracle Database

Search This Blog