So what went wrong here? I feel I've set everything the way it needs to be, but just can't get it work.
FYI -- the Oracle was installed when I logged in as administrator to the local machine. And now I'm log in as a domain user. Of course, both local admin and the domain user are member of ora_dba and local admin group.
So what went wrong here? I feel I've set everything the way it needs to be, but just can't get it work.
FYI -- the Oracle was installed when I logged in as administrator to the local machine. And now I'm log in as a domain user. Of course, both local admin and the domain user are member of ora_dba and local admin group.
Any hint is greatly appreciated!
Try this may help you:
From Metalink Note:50507.1
OSDBA & OSOPER Groups on NT
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The 'OSDBA' and 'OSOPER' groups on NT are simply groups with the name "ORA_DBA", "ORA_OPER", "ORA_sid_DBA" or "ORA_sid_OPER", where 'sid' is the instance name.
Eg: To make a user an administrative user simply:
a) Ensure there is a line in the SQLNET.ORA file which reads: SQLNET.AUTHENTICATION_SERVICES = (NTS)
b) Create a LOCAL user
c) Create a local NT group ORA_DBA or ORA_sid_DBA where 'sid' is in upper case
d) Add the user to the ORA_DBA or ORA_sid_DBA group
e) That user should now be able to "connect / as sysdba"
Try and log in as administrator and bring up the database and re grant the privilages to user and then try doing what you are doing. Should work i suppose.
Originally posted by davey23uk what makes you think administrator will have the rights to start the databse?
I am not saying admin should have rights to start the database, what I said is the member belong to ora_dba group should have rights to start the database.
The reason for me to mention admin group is that you have to have admin privilege to install oracle on that server.
Try and log in as administrator and bring up the database and re grant the privilages to user and then try doing what you are doing. Should work i suppose.
What do you mean grant the privilege to the user?
What I tried is log in as administrator to the local machine, add domain user to the dba_user group, then log in as domain user. But that didn't help. Any other thoughts?
Thanks! I think I have everything mentioned in this KB note(see my original post), but it still doesn't work. Actually, you don't have to create ORA_DBA group manually (at least to me). It got created by installer when you install Oracle.
Originally posted by gnagesh Try this may help you:
From Metalink Note:50507.1
OSDBA & OSOPER Groups on NT
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The 'OSDBA' and 'OSOPER' groups on NT are simply groups with the name "ORA_DBA", "ORA_OPER", "ORA_sid_DBA" or "ORA_sid_OPER", where 'sid' is the instance name.
Eg: To make a user an administrative user simply:
a) Ensure there is a line in the SQLNET.ORA file which reads: SQLNET.AUTHENTICATION_SERVICES = (NTS)
b) Create a LOCAL user
c) Create a local NT group ORA_DBA or ORA_sid_DBA where 'sid' is in upper case
d) Add the user to the ORA_DBA or ORA_sid_DBA group
e) That user should now be able to "connect / as sysdba"
--------------------------------------------------------------------------------
Originally posted by davey23uk
what makes you think administrator will have the rights to start the databse?
--------------------------------------------------------------------------------
I am not saying admin should have rights to start the database, what I said is the member belong to ora_dba group should have rights to start the database.
The reason for me to mention admin group is that you have to have admin privilege to install oracle on that server
sorry my response wasn't aimed at your point, was aimed at the person who said log in as an administrator and start database up from there (which wont work)
ora-01031 insufficient privilege error
Reply With Quote
Bookmarks