It will shutdown the instance specified in your ORACLE_SID environment
variable
chrisoc_at_ans.net wrote in message <86qe79$t1a$1_at_nnrp1.deja.com>...
>Out of curiosity, what would happen if I
>went into svrmgrl and typed "connect internal"
>and then "shutdown immediate"?
>
>I typically do that rather than sql*plus with
>system/manager -- although I guess I will have
>to change my habits with two SIDs around.
>
>I want to bullet-proof the installation so we
>never accidentally shut down the wrong SID along
>with the one we intended to.
>
>Chris O'Connor
>
>
>
>
>In article <86qcml$rn6$1_at_nnrp1.deja.com>,
> ed.stevens_at_home.com wrote:
>> Create entries for the second sid in your LISTENER.ORA and
>TNSNAMES.ORA
>> files and refresh the listener. Say your first instance was ORC1 and
>> your new, second is ORC2. Whenever you connect, use the connect
>string
>> in the form 'CONNECT userid/pwd_at_alias' where 'alias' is the alias in
>> TNSNAMES.ORA that specifies the sid you want to connect to. That will
>> be the sid you connect to and that will be the sid any commands you
>> issue will be performed against.
>>
>> In article <86q6nm$mvh$1_at_nnrp1.deja.com>,
>> chrisoc_at_ans.net wrote:
>> >
>> >
>> > I want the maximum independence in taking down one
>> > instance, modifying its storage etc. without affecting
>> > the other one.
>> >
>> > If I build the second instance with entirely distinct
>> > tablespaces and datafiles (including system, temp, rbs,
>> > redologs) and run the catproc etc. for it, I am still
>> > not certain how I will be able to connect as system or
>> > sys to just that instance and manage it without
>> > affecting the first one.
>> >
>> > Point me to a doc if the answer is complicated.
>> >
>> > Thank you,
>> > Chris O'Connor
>> >
>> > Sent via Deja.com http://www.deja.com/
>> > Before you buy.
>> >
>>
>> Sent via Deja.com http://www.deja.com/
>> Before you buy.
>>
>
>
>Sent via Deja.com http://www.deja.com/
>Before you buy.
Received on Thu Jan 27 2000 - 16:49:17 CST
