Dimitre, thanks for your reply. I think I'm missing something. If I remember correctly OAS (in all honesty it's been about 5 years since I installed one). You have the three following "tiers". 1. Metadata Repository: This is a database that pretty much holds OID, SSO and Discoverer info. 2. Infra: SSO, OID, etc. These apps connect directly to the MR Database 3. Middle Tier: disco, forms, reports, etc. They connect to the db and infra services. The doc says that it's the MR that cannot change the hostname because there are a lot of places where the hostname is recorded (config files, tables, etc) and it would be "technically unfeasible to write a script to update all these locations". Cheers Alan.- On Tue, Oct 9, 2012 at 11:52 AM, Radoulov, Dimitre <cichomitiko@xxxxxxxxx>wrote: > On 09/10/2012 16:18, Guillermo Alan Bort wrote: > >> From what I understand from Oracle's Documentation, the only way to >> "move" a Metadata Repository for a OAS 10g (10.1.2.3.0) is to keep the >> hostname and that fay "fool" the infra and middle tiers (namely OID) to >> use >> the new machine, but with the same name. Now, my issue with this is that >> the original DB is in a RAC, and the nodes will be repurposed, so we can >> reuse the hostnames, but the new nodes already have hostnames... so they >> would have to be DNS aliases, really. >> >> Does anyone have experience moving the MR from a full OAS to another >> physical machine? Any experiences you care to share? >> > > Hi Alan, > _if I recall correctly_, the hostname constraint applies only to MR > node[s] (where the OID binaries reside). > Changing the hostname _of the database_ (the RAC nodes, in your case) > shouldn't be a problem. > > > > Regards > Dimitre > > > > > -- //www.freelists.org/webpage/oracle-l