Re: NT/BMC/ORACLE Question

Hello, James...

I know about Oracle 8 and NT, but I don't know about SQL BackTack... Why dud U need to use svrmgr30 to shutdown and restart the database? What I usually do is that I stop the Oracle services using the NET STOP command and I start them using NET START command in my unattended backup scripts. The syntax would look like:
net stop OracleStartORCL -- Where ORCL is your SID here net stop OracleServiceORCL

---
Your backup script goes here
--
net start OracleStartORCL  -- Where ORCL is your SID here

You put this in a bat or cmd file... I didn't need to tamper with my
Internal passwords to do this... I'm not using backtrack, I'm using standard
NT backup... It works fine for me...
But from what I saw in your message, you're forced to use O/S authentication
on your server... Now this would really pose a security problem if NT admins
are not all DBAs...
Unless you SQL BackTrack needs to no avail to shutdown and restart the DB
with svrmgr30... If you didn't already try the workaround above, you can do
this... Tell me what happens...

Regards,

--
Salim J. Karam (aka Connector)
Computer Systems Engineer, Oracle DBA
Ain El Remmaneh, Pierre Gemayel Str.,
White Bldg
Beirut, Lebanon
E-mail: salim_at_sjkaram.com
Alt.: sjkaram_at_hotmail.com
Cece Russell <cecerussell_at_prodigy.net> wrote in message
news:8k5i12$2u9e$1_at_newssvr05-en0.news.prodigy.com...


>

> Please reply to my email address of jamesrussell_at_prodigy.net  .

> I used my wife's email account to post this.  Thanks.

>

> "Cece Russell" <cecerussell_at_prodigy.net> wrote in message

> news:8k5h7i$2gfa$1_at_newssvr05-en0.news.prodigy.com...

> >

> > I need the help of someone, anyone who is familiar with Oracle8 on NT.

 In


> > particular, I set up the environment on NT so that I could log onto

 svrmgr30


> > as internal without a password.  This was done so that a BMC product

> > (SQLBACKTRACK, used to backup Oracle) could use svrmgr30 to shutdown and

> > startup the database without having to supply a password for internal.

 This


> > was a requirement of the product.

> >

> > Now I am faced with a problem.  To do this I had to do three things:

 set
 a


> > parameter in the sqlnet.ora file, set a parameter in the init.ora file,

> > create an NT group called ora_dba and grant membership to the account

 that


> > owns the database to this group.  Now anyone with administrative

 privileges


> > on NT can place any NT account into this group.  Anyone who is a member

 of


> > this group (they do not need explicit privileges on the Oracle directory

 or


> > files) can execute svrmgr30 and log on as internal without a password.

 They


> > can do the same thing with sqlplus.

> >

> > How can I secure things on NT so that only the NT account that installed

 the


> > software can log on as internal without a password?  Any ideas?

> >

> > Please reply to my email account if at all possible.

> >

> > Thank you very much.

> >

> > Jim Russell

> >

> >

>

>