Psuedo SIDs is this possible (help)

Here's a couple of (possible solutions).

1. Create a small database and experiment with changes to the initSID.ora file. AFAIK, the init.ora refers to the db_name, and SQL*Net (for example) refers to the SID. Therefore, it should be possible to ...
   • copy initPROD.ora to initX.ora
   • copy initDEV.ora to initPROD.ora
   • copy initX.ora to initDEV.ora

This means that when you start PROD it will point to the DEV database, and vice-versa. Internally the dbname (or global db name as it is now) will still be DEV. SQL*Net is only interested in the SID's referenced in tnsnames.ora (or topology.ora) on the client, but I haven't tried this so there maybe other reasons why it won't work.

2. If this isn't what you want, then you can try ...

• Close PROD
• Backup PROD
• Create a backup controlfile from DEV using something like "svrmgrl> backup controlfile to trace ;"
• Close DEV
• Backup DEV
• copy DEV's o/s files to new location (maybe over PROD's)
• Edit the controlfile to use the new dbname, and o/s files
• Copy DEV's init.ora and config.ora over PROD's
• Edit new init.ora with new name and o/s files
• Start (new) PROD

I did this recently, but don't know if this exactly right, however I will have access to my notes on Monday if you need further pointers.

Hope this helps.

Pete Gross
Contract UNIX System Admin and Oracle DBA UK

In article <6jv9ra$igh_at_gcsin3.geccs.gecm.com>, raymond.craig_at_gecm.com writes
>Im am currently about to run two databases
>one production other development
>the production one will be superceded by the dev one
>can i rename the production one to something else and
>rename the dev one to the production one.
>
>Reason is client server pc installation have a path
>to the production db name db_prod1 and this is on a
>raw partion the dev one db_dev1 is a file system
>is there a way to fix the SID conflict with regards to
>the dev database
>
>
>Thanks
> Raymie

--
Peter Gross Received on Fri Jun 05 1998 - 11:40:12 CDT