Re: Start a database as sysoper from DBA-Studio

You're right, it's important to know which versions we're talking about. So in our case it's Oracle 8.1.7, DBA Studio 2.2.0.0.0, WindowsNT 4.0 SP4, Compaq Tru64 4.0F.

Best regards,
Jan

"Sybrand Bakker" <postbus_at_sybrandb.demon.nl> schreef in bericht news:tkmmh28rifs461_at_beta-news.demon.nl...
>
> "Jan" <strik.j_at_planet.nl> wrote in message
> news:9ifilf$pg43$1_at_reader01.wxs.nl...
> > Can someone help with the following ?
> >
> > We want to start a database on Windows NT and/or UNIX from DBA-Studio on
> > (another) Windows NT.
> > We log in to the database with user sys as sysoper, right-mouse-click
 and
> > choose startup. We see a window with the message that the database is
> > started alright.
> > When we do a select from v$instance, we see that the database is in the
> > mounted-status, so it is not open.
> > The last entry in the alert.log : Completed: ALTER DATABASE MOUNT
> >
> > When we try the same thing as user sys as sysdba, the database starts
 and
> > opens alright.
> >
> > When we login on the UNIX-box, do sqlplus "sys/... as sysoper" and start
 the
> > database, the database starts and opens.
> > The same thing happens if we use sqlplus as sysoper from a DOS-box on
 the
> > Windows NT-machine where the DBA-Studio is. If we start the database on
 the
> > remote Windows NT-machine, the database starts and opens.
> >
> > We want to use sysoper to start the database from DBA-Studio.
> > How can we do that ?
> >
> >
> >
> >
> >
>
> This might well be a version specific bug. As you don't provide any
> information as to which version of the database and which version of DBA
> studio you are using, it is very unlikely you will get any adequate
> response.
>
> Regards,
>
> Sybrand Bakker, Senior Oracle DBA
>
>
>
Received on Wed Jul 11 2001 - 13:00:52 CDT