As i said my earlier post, init<sid>.ora files knows where all your
control files are and control files knows where all your datafiles, redo
logs....
so, when you set ORACLE_SID=myDB, and startup via sqlplus /nolog,
connect / as sysdba then your initmyDB.ora file is read and it opens the
database for you.
hth,
-Stan
abc_at_iom.com wrote:
> On Sun, 18 Aug 2002 18:36:04 GMT, Ban Spam <ban-spam_at_operamail.com>
> wrote:
>
>
>>abc_at_iom.com wrote in news:3d5fd811.325087451_at_news.sf.sbcglobal.net:
>>
>>
>>>Ok, here's a scenario:
>>>
>>>There is a database--call it "MyDB" on server "A" Server A is Oracle
>>>9i, Release 2 MyDb has never been backed up.
>>>However, all the files pertaining to that database (control, data,
>>>redo) have been copied to a safe place in another folder on that
>>>server.
>>>
>>>Disaster strikes. The database server software installation is
>>>hopelessly screwed. No hope in hell of getting it reinstalled on that
>>>server.
>>>
>>>Fortunately, there's Server B! It has Oracle 9i Release 2 as well.
>>>In fact, it's the exact same installation as Server A--only this
>>>server works. The only instance running on Server B is some test db.
>>>I want Server B to "See" my original database, "MyDB". I copy the
>>>original physical files from the original database in question over to
>>>this new Server B.
>>>
>>>Now the question: How do I get Server B to recognize this new
>>>database? I'm sure it has something to do with RECOVER, RMAN, etc.
>>>
>>While you might be "sure", you'd still be WRONG.
>>
>>ORACLE_SID=MyDB
>>
>>Then simply issue the STARTUP command.
>>
>>The two instances, test & MyDB, are 100% separate entities
>>and are managed & controlled separately.
>>
>>
>>HTH & YMMV
>>
>>
>>
>>HAND!
>>
>>
>>
>>
>>
> STARTUP <What> ?
>
> As I wrote, MyDb has never been configured on server B. Server B
> doesn't know that MyDB exists. All I have on Server B are some
> data/control files in a folder somewhere. How would startup know what
> to do?
>
>
>
>
Received on Sun Aug 18 2002 - 14:23:41 CDT
