Migrate Rman Catalog over cross platform's

I need some suggestion for migrating Rman Catalog...
Current Rman Catalog: 10gR2 on HPUx and would like to migrate and upgrade to 11g on Linux....Any suggesions...
My thoughts: exp and import schemas from hpux to linux 10g -10g and upgrade 10g catalog to 11g on new linux server....
Any help would be appreciate.....

There is "NO UNREGISTER" option...
NO UNREGISTER Forces RMAN to keep imported database IDs in the source catalog schema. By default, the imported database IDs are unregistered from source recovery catalog schema.
-------------------------------------------------------------------------

Similar Messages

Can I use RMAN transportable database cross platform from 10g to 11g?

Hi,
I'm working on the migration plan, the source db server is solaris with 10g database while the destination server is AIX with 11g database.
Can I use RMAN transportable database for this purpose?
Coz I have read the restrictions on Cross-Platform Transportable Database, but it does not mention whether it can work for different version of database.
please help.

Hi,
Do you have metalink account? If yes please check : Cross-Platform Migration on Destination Host Using Rman Convert Database [ID 414878.1]*
RMAN Cross-Platform Transportable Databases and Tablespaces
Thank you

Third Party Tools for Database Migration of 10g between Cross Platform?

Hi,
Like to know any is there any third party tool
available in the market for cross platform EASY database migration
between AIX - 10g R2 to Windows - 10g R2.
Before there used be a third party tool called DBPUT which is no longer
available now.Looking for similar type.
Any Suggestion Please.
Regards,

why not using export/import (common Oracle tools) or use GoldenGate which allows you to migrate a production database w/o downtime.
- Klaus

E-business database migration to linux (Cross platform) using datapump

Have anyone used parallel=? option of datapump when migrating e-business database (cross platform) during export (expdp) and import (impdp).

174b0d50-0464-47ad-8831-22215fbc4bbe wrote:
Have anyone used parallel=? option of datapump when migrating e-business database (cross platform) during export (expdp) and import (impdp).
You can use this option, just consider not using a high number to avoid ORA-31693 errors.
Using Transportable Tablespaces for EBS 11i Using Database 11gR2 (Doc ID 1366265.1)
Using Transportable Tablespaces for EBS Release 12.0 or 12.1 Using Database 11gR2 (Doc ID 1311487.1)
Thanks,
Hussein

Cross platform migration from hp unix to sun

Hi
recently we have done cross platform migration from hp unix to sun (10g R2 RAC +ASM). It was a challenging experience to complete the migration in 8 hours downtime for a database of about 2 TB.
I would like to share the experience , so that it would be hepfull to others and i would learn more new techniques for improvement .
source environment:
HP-UX -ITANIUM - 2 node RAC - 10g R2 - Oracle clusterware - ASM - Heavily loaded all the time .
Destination Env:
Sun solaris 10 - 2 node RAC - 10g R2 - Oracle Clusterware - ASM
Total Downtime available : 6 hours.
Steps followed
1. snapshot backup of source database on a intermediate HP-Unix box. (stage area)
2. recover the database and start the rman image backup on to disk in stage area.
3. mount this filesystem locally (Veritas ) on to one of the node in the destination env.
4. Mount this filesystem as NFS on second node using a cross cable between both of them (we can use interconnect VLAN also here)
5. Keep applying the archive logs from source env till the downtime .
5. startup nomount the database , change the datafile names from ASM to RMAN image copy files and mount.
6. start rman convert statements and pump into the already exisitng ASM nodes with parallel sessions as much as possible (with 35 sets (513 datafiles) we were able to pump 2 TB data in 4.5 Hrs) - only system and undo datafiles need a convert statements (platform migration ) others would need a file system to ASM conversion only.
7. alter database open resetlogs in the destination environment.
8. create services manually and start the application.
we were given very less time to decide upon this stategy , By gods grace we were able to complete it .
I got a doubt while we are chalking out this plan .
can we connect to ASM instance remotely and pump data from one ASM to another ASM. It seems it is not possible , just a wild thought.
Let me know if you see any more improvements in this.
Thanks
Naveen samala

can we connect to ASM instance remotely and pump data from one ASM to another ASM. It seems it is not possible , just a wild thought.No. Thats not possible.

Oracle 10g - Cross-Platform Transportable Database (with or without RMAN?)

Hello guys,
i am currently on a project for migrating oracle databases from one platform to another platform (both platforms are on the same endianess):
-> From Linux 64-Bit to Windows 64-Bit
-> From HP-UX 64-Bit to AIX 64-Bit
All databases are on Oracle 10g (10.2.0.4) and i have tested two different ways:
1) The "official" way with RMAN CONVERT DATABASE
http://youngcow.net/doc/oracle10g/backup.102/b14191/dbxptrn002.htm#CHDEEEAG
2) "Copy & Paste"
- Copy & Paste of the database files
- Recreate controlfile manually on target platform (with help of "backup controlfile to trace" on source platform)
Both ways are working well and the migrated test databases are running fine.
Now i am wondering why there is a "RMAN CONVERT DATABASE" command, if it possible to copy and paste the data files and perform two steps manually afterwards.
The "RMAN CONVERT DATABASE" is time consuming and you still need to copy the RMAN output files to the target platform.
Is there any special reason, why you need the "RMAN CONVERT DATABASE"? Does the "RMAN CONVERT DATABASE" change some things in the database files internally?
Thanks and Regards

Hello,
Anurag Tibrewal wrote:
If the source platform and the target platform are of different endianness, then an additional step must be done on either the source or target platform to convert the tablespace being transported to the target format. Of course .. in this case you can not use the "Cross-Platform Transportable Database" - you have to use the "Cross-Platform Tranportable Tablespace" (with RMAN CONVERT DATAFILE or TABLESPACE).
Anurag Tibrewal wrote:
If they are of the same endianness, then no conversion is necessary and tablespaces can be transported as if they were on the same platform.Yes, but oracle provides this with RMAN and the command "RMAN CONVERT DATABASE" .. as i already wrote i have already performed the two ways "RMAN CONVERT DATABASE" and "just copy & paste" and both are working fine.
So my question is if there is any special case in which you should use the RMAN way with "RMAN CONVERT DATABASE" instead of just "copy & paste" if you stay on the same endianness?
Thanks and Regards

Grid Control for a cross-platform migration

Is it possible to use Enterprise Manager Grid Control to execute a cross-platform migration? A co-worker suggested checking this out, but he wasn't sure if it would work or not.

Cross-Platform transportation is a complex process and done by RMAN utility. Don't rely on GridControl, better follow the roadmap in
http://download-uk.oracle.com/docs/cd/B19306_01/backup.102/b14191/dbxptrn.htm#sthref1379
Werner

RMAN Full Database restore cross platforms

All
I have a database 10.2.0.3 running on Solaris 10 OS.
I have performed a full back up (level 0) of this database using rman utility with auto back up on. I am trying to worl on a scenario where I could restore this backup on another linux machine. so I copied over all the backup pieces into the target linux server. from a local RDBMS installation (10.2.0.3) on the linux machine I am trying to restore the database... but not successful yet..
when I issue restore spfile or restore control file from +<backup file name>+; the prompt continues to search in some location is responding back saying no back up piece found.. below is the sequece of step I am trying ..
1 set up env on the linux server
2 rman target /
(instance not started but rman allows connection)
3 set DBID=+<DB ID of the source database running on Solaris>+
it executes set dbid=
4 startup nomount
as the pfile/spfile is not available under $ORACLE_HOME/dbs on linux machine it picks up default pfile however but the instance stars no mount..
5 restore spfile from '/u01/app/oracle/product/10.2.0/rman_bkp/c-300009955'
here it is not able to restore any thing.same is the case with control file.
Any ideas please advice
Sarat

Sarat Chandra C wrote:
Thanks for the referance. I now understand that I may not be able to use transportable database command to transport the entire db. However there is a line in the +"Restrictions on Cross-Platform Transportable Database"+ which says +"The principal restriction on cross-platform transportable database is that the source and destination platform must share the same endian format. For example, while you can transport a database from Microsoft Windows to Linux for x86 (both little-endian), or from HP-UX to AIX (both big-endian), you cannot transport a whole database from HP_UX to Linux for x86 using this feature. You can, however, create a new database on a destination platform manually, and transport needed tablespaces from the source database using cross-platform transportable tablespace as described in "Cross-Platform Tranportable Tablespace: CONVERT DATAFILE or TABLESPACE"."+
I understand if we are ready to transport every tablespace from Source to Target individually, may then be able to replicate a transportable database. Does the transportable tablespace do not have any restrictions like the transport database has got in respect to Platforms and Endian? Please clarify.
Also is there a support matrix for thr transportable database and tablespaces which we could refer to ?
Regards!
SaratSarat,
The same restriction that is there for the transport of the whole database lies completely true for the transportable tablespace as well if you are going for the cross platform. Endian must match across the platforms than only you can do this otherwise, as like the database feature, you need to convert the source file to the target endian.
If you look at the reference doc for the Trasnport Tablespace command,
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14194/rcmsynta063.htm#RCMRF1919
This restriction is documented there besides other restrictions
>
Restrictions and Usage Notes
The limitations on creating transportable tablespace sets described in Oracle Database Administrator's Guide apply to transporting tablespaces from backup, with the exception of the requirement to make the tablespaces read-only.
TRANSPORT TABLESPACE does not perform endian format conversion. If the target platform has a different endian format, then you must use the RMAN CONVERT command to perform the separate step of converting the endian format of the datafiles in the transportable set.
>
HTH
Aman....

Cross platform migration question.

I have a customer that is currently runnning oracle 10g databases on solaris 64 bit operating system on sun m4000 and m5000 hardware. The customer is looking to move to the redhat 6 operating system.
I am wanting to know what method will be available for me to migrate the databases as the endian on the files are different? Will transportable tablespaces work with the different endian?
Thanks.

Hi;
I suggest please also see:
How To Use RMAN CONVERT DATABASE on Source Host for Cross Platform Migration [ID 413586.1]
Master Note For Oracle Database Upgrades and Migrations [ID 1152016.1]
PS:Please dont forget to change thread status to answered if it possible when u belive your thread has been answered, it pretend to lose time of other forums user while they are searching open question which is not answered,thanks for understanding
Regard
Helios

Cross platform migrate repository and oms, gets "EM Key Verification Error"

Hello,
I am trying to cross platform migrate repository and oms from Sun Solaris Sparc 64 bit to Linux x86-64bit.
Environment:
Original repository Oracle 10.2.0.3, OMS 10.2.0.5, Sun Solaris Sparc 64 bit
New repositoy Oracle 10.2.0.3, OMS 10.2.0.5, Linux x86-64bit
Following metalink note:
Subject: How To Move Grid Control Oms & Repository To Another Server
Doc ID: 853293.1
to step 4:
4. Point the new OMS to the new repository
can't get over emkey corrupt issue, gets error:
2009-10-13 14:07:24,570 [AJPRequestHandler-ApplicationServerThread-11] ERROR conn.ConnectionService verifyRepositoryEx.918 - EM Key Verification Error = Em key does not match with repos verifier
2009-10-13 14:07:27,910 [Shutdown] ERROR em.notification unregisterOMS.2573 - Error unregistering: EM Key is Missing java.sql.SQLException: EM Key is Missing
The newly installed additional OMS can only point to the original repository and can't point to the newly migrated repository.
Steps I did:
Install an addition OMS to point to original repository (make sure emkey is in repository)
create a new empty database on new host with a new name (is new name caused problem?)
migrate old repository to new (use export/import)
point new OMS to new repository by modifing emoms.properties
startup oms and gets emkey corrupt error
This metalink note does not help either:
Subject: The Em Key is not configured properly. Run "emctl status emkey" for more details.
Doc ID: 817035.1
I also have a SR open but still have no help from Oracle support. I did make sure the emkey is in the repository before migrate. There may be tricks that I don't know.
Can anyone shed some light on this?
Thank you for your help in advance.
Edited by: user1062137 on Oct 16, 2009 2:14 PM

Hi, I'm having the same issue.
Our original installation was on Windows 32bit with the repository and OMS on the same host. I want to move the repository to a linux 64bit host to make more resource available for everything. The new database is 11.1.0.7 though. As the Grid control release is 10.2.0.5 Oracle Support have confirmed that the 11g database is OK to use.
In the log I see a lot of this:
[AJPRequestHandler-ApplicationServerThread-5] ERROR conn.ConnectionService verifyRepositoryEx.911 - Invalid Connection Pool. ERROR = ORA-01031: insufficient privileges
ORA-06512: at "SYSMAN.MGMT_USER", line 10296
ORA-06512: at "SYSMAN.SETEMUSERCONTEXT", line 17
ORA-06512: at line 1
2009-11-05 18:54:57,254 [AJPRequestHandler-ApplicationServerThread-7] ERROR conn.FGAConnection _setConnContext.326 - java.sql.SQLException: ORA-01031: insufficient privileges
ORA-06512: at "SYSMAN.MGMT_USER", line 10296
ORA-06512: at "SYSMAN.SETEMUSERCONTEXT", line 17
ORA-06512: at line 1
java.sql.SQLException: ORA-01031: insufficient privileges
ORA-06512: at "SYSMAN.MGMT_USER", line 10296
ORA-06512: at "SYSMAN.SETEMUSERCONTEXT", line 17
ORA-06512: at line 1
2009-11-05 18:54:59,973 [Shutdown] ERROR em.notification unregisterOMS.2573 - Error unregistering: EM Key is Missing
java.sql.SQLException: EM Key is Missing
Unfortunately that package is wrapped so I can't see what privs are required.
The instructions say (simplified here) either datapump or exp/imp to the new database, run some admin scripts, then update the emoms.properties with the new connection information. Thats it - start OMS again and it should work.
Thankfully I can turn the old repository back on while I sift through these logs.

Cross Platform migration employing Incremental Transportable Tablespaces

We have a VLDB that needs to be converted from a Sparc T3 Solaris Big endian to Linux small endian and there are over 6000 tables and the GoldenGate method to reduce downtime was attempted n dev and was an utter failure. Then I read in several places including metalink ( My Oracle Support ) in DOC ID 1644693.1 Entitiled "How to restore a pre 12c database backup to a cross platform cross endian 12c database", Bug 13335722 and many Oracle 12c Brochures all state that the cross platform cross endian method of using Incremental Transportable Tablespaces which used to be only supported for Exadata is now supported for ALL 12c platforms. Can anyone veriffy this and has employed this technique to migrate from Sun to Linux by first upgrading the source database to 12c then employing Incremental Transportable Tablespaces capabilities of 12c to migrate cross platform cross endian from Sun Sparc big endian 64 bit word to Linux Intel little endian 64 word. Otherwise if we migrate from 11GR2 Sun to Intel we are looking at least 5 days of Read Only downtime.
Thanks

You can also refer to Metalink note
Reduce Transportable Tablespace Downtime using Cross Platform Incremental Backup (Doc ID 1389592.1)

Need Help in Cross Platform Migration

Hi Gurus,
can you please tell me best way to do Corss Platform Migration with minimum down time and we are planning to do from AIX TO HP-UX.
oracle version is 10g
and can we do the data sync using streems if it is can you give the steps to configure streems in cross platform.
Thanks in advance.

High Availability Customer Case Studies, Presentations, Profiles, Analyst Reports, and Press Releases
[http://www.oracle.com/technology/deploy/availability/htdocs/HA_CaseStudies.html?_template=/ocom/print]
Check under Transportable Tablespace at the bottom
[Multi Terabyte Database Migration|http://www.oracle.com/technology/deploy/availability/pdf/TheHartfordProfile_XTTS.pdf]
HTH
Anantha

Oracle Database Migration 10g between Cross Platform...!

Hi,
Like to know any is there any third party tool
available in the market for cross platform EASY database migration
between AIX - 10g R2 to Windows - 10g R2.
Before there used be a third party tool called DBPUT which is no longer
available now.Looking for similar type.
Any Suggestion Please.
Regards,

Hi ,
Do it yourself , I suggest you to use export/import .
Master Note For Oracle Database Upgrades and Migrations (Doc ID 1152016.1)
Export/Import DataPump: The Minimum Requirements to Use Export DataPump and Import DataPump (System Privileges) (Doc ID 351598.1)

Cross Platform migration AIX to linux (ERROR IN CONVERSION ORA-19994: Message 19994 not found)

I am performing a cross platform migration aix to Linux from release 11.2.0.2 to 11.2.0.4. I am using this doc
Reduce Transportable Tablespace Downtime using Cross Platform Incremental Backup (Doc ID 1389592.1).
I am using the db_file_transer method and I have hit this error
Error:
/home/oracle/local/db_convert/dest_rman/xxttconv_i3q0t1ha_1_1_4.sql execution failed
ERROR IN CONVERSION ORA-19994: Message 19994 not found; product=RDBMS;
facility=ORA
ORA-19600: input file is backup piece
(/oraback/nfclpat1/i2q0t1ha_1_1)
ORA-19601: output file is backup piece
(/oraback/nfclpat1_tmp/xib_i2q0t1ha_1_1_5_28)
CONVERTED BACKUP PIECE/oraback/nfclpat1_tmp/xib_i2q0t1ha_1_1_5_28
PL/SQL procedure successfully completed.
I have searched and do not have anything to go on.
Can anyone who has seen this give me some direction?

As per Oracle documentation on given error code, Please see if following action helps.
ORA-19994: cross-platform backup of compressed backups to different endianess is not supported
Cause: A cross-platform backup was requested for a compressed backup to a different endianess from the current platform.
Action: Do not specify a compressed backup or specify the same endian platform.

How to upgrade the oracle RDBMS and migrate cross platform

Hi ,
I would like to migrate my database from solaris 5.10 to linux. Simultaneously upgrade my RDBMS database from 10g to 11gR2.
Can you please suggest
Thanks
Naveen

My present database is 10.2 and new target database is 11.2.0.1.
cross platform is from solaris to linux.
Size of the database is 2.5TB . Does datapump a viable solution? Any alternative methods.
We do not get any down time. I am figuring out a solution for initial lot and migation. Thereafter i can use golden to sync up and do the cutover
Thanks
Naveen.
Edited by: 949870 on Jul 30, 2012 4:53 PM

Migrate Rman Catalog over cross platform's

Similar Messages

Maybe you are looking for