From: "Cece Russell" Subject: NT/BMC/ORACLE Question Date: 2000/07/07 Message-ID: <8k5h7i$2gfa$1@newssvr05-en0.news.prodigy.com>#1/1 X-Priority: 3 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 X-Complaints-To: abuse@prodigy.net X-Trace: newssvr05-en0.news.prodigy.com 963004467 2082749 63.254.79.78 (7 Jul 2000 21:14:27 GMT) Organization: Prodigy http://www.prodigy.com X-MSMail-Priority: Normal NNTP-Posting-Date: 7 Jul 2000 21:14:27 GMT Newsgroups: comp.databases.oracle.server 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