Re: OEM - won't startup database

As I said, I'm already able to connect remotely as SYSDBA and startup and shutdown the database using DBA Studio in stand-alone mode. I would not be able to do that if all that stuff hadn't already been done--you'd get a permissions error just trying to connect. The only difference here between starting the database through OEM vs. DBA Studio-SA, as far as I can tell, is the logging into the OMS on the solaris box.

In article <6724a51f.0109060538.5e33bf3e_at_posting.google.com>, empete2000_at_yahoo.com (Pete's) wrote:
>A couple of items to check, did you create an Oracle Password file
>using 'orapw' in the $ORACLE_HOME/bin directory? Also, did you set
>remote_login_passwordfile=exclusive in your init.ora file????? In
>order to use the OEM client to startup/shutdown DB's, these need to be
>setup. BTW, when you set the parameter, you will need to bounce the
>DB.
>
>HTH
>Pete's
>
>
>jeff_at_work.com (Jeff) wrote in message
> news:<9n5jkp$ntl$1_at_cronkite.cc.uga.edu>...
>> Consider this:
>> OEM 2.2.0.0.0 (NT Client, Solaris OMS)
>> Oracle 8.1.7 (two Solaris boxes, one holds repository for the other)
>>
>> I can startup and shutdown the database in stand-alone mode using DBA Studio.
>>
>> I can shutdown and startup the database in OEM as long as I don't disconnect
>> (either by using the disconnect option or restarting the OEM client).
>>
>> I can start the database using svrmgrl in nomount mode and OEM can mount
>> and open the database from there.
>>
>> I cannot shutdown the database, restart OEM (or disconnect), and startup the
>> database. I get no actual messages--the little gears just stop with an
>> exclamation point. It doesn't matter if I use the same local parameter file
>> that DBA Studio uses successfully in stand-alone mode. It also doesn't work
>> if I use DBA Studio logged into the OMS.
>>
>> Yes, I am connecting as SYSDBA (obviously, or I'd not be able to startup the
>> database remotely at all). I don't understand what's preventing OEM from
>> starting the database when DBA Studio (in stand-alone mode) starts it just
>> fine.
>>
>> Anyone have a clue as to what's preventing OEM from starting the database???
Received on Thu Sep 06 2001 - 10:27:16 CDT