SysDBA role\privileges 1

[THoey]

Can anyone tell me how to give an account SysDBA role\privileges? We have had a couple DBA's come and go, and along the line logins and passwords were forgotten.

Currently, the only way to bring down the database is to login to the Unix box as ROOT, SU to Oracle and then login to Oracle with an operating system authenticated account. Any of the accounts that I am able to login to Oracle DBA Studio, this option and others are grayed out.

I went in through Unix and the OPS$ORACLE account, created an account, gave it the DBA role, assigned every role and every system privilege, and still don't have this.

I changed the passwords on the SYSTEM and SYS logins and went in through Oracle DBA Studio with these accounts and still don't have these options.

BTW, the database is Oracle 7.3.4, and I have tried this using 8.1.6 DBA Studio and 7.3.4 Instance Manager.

Thanks in advance... Terry M. Hoey
th3856@txmail.sbc.com
While I don't mind e-mail messages, please post all questions in these forums for the benefit of all members.

 

[karluk]

Sysdba is a system privilege, so you should be able to issue

Grant sysdba to dba_id;

No doubt you will have to be logged on as sysdba to do this.

 

[THoey]

I will try it, but I do not believe we have access to any logins any more that have SysDBA... When I log in to DBA Studio with the accounts we have the passwords for, none of them will login if you choose SysDBA mode...

Thanks anyways... Terry M. Hoey
th3856@txmail.sbc.com
While I don't mind e-mail messages, please post all questions in these forums for the benefit of all members.

 

[karluk]

Please check out thread185-32102, which you opened some time ago. It discusses using ORAPWD to set the password for the INTERNAL id. Internal has sysdba privileges, so that should allow you to log on as sysdba.

 

[THoey]

Great!!! I remember that thread now and I remember having that problem then, I just couldn't remember enough to think about doing a search. Starting to get fried, need beer...

Thanks again Karluk Terry M. Hoey
th3856@txmail.sbc.com
While I don't mind e-mail messages, please post all questions in these forums for the benefit of all members.

 

[THoey]

BTW Karluk, if I do something like that again, instead of you taking the time to research it, please just remind me and I will do it. Might make me think and remember a bit better. Besides, your time is better used in helping others, than searching threads for me. Thanks again... Terry M. Hoey
th3856@txmail.sbc.com
While I don't mind e-mail messages, please post all questions in these forums for the benefit of all members.

 

[karluk]

Not at all. I just hope I'm giving you good advice. It makes me nervous, suggesting ways to modify these critical ids.

 

[THoey]

Just to add to what you gave me, this is what Oracle says:

Using ORAPWD
When you invoke the password file creation utility without supplying any parameters, you receive a message indicating the proper use of the command as shown in the following sample output: 

   orapwd
Usage: orapwd file=<fname> password=<password> entries=<users>
      where
        file - name of password file (mand),
        password - password for SYS and INTERNAL (mand),
        entries - maximum number of distinct DBAs and OPERs (opt),
      There are no spaces around the equal-to (=) character.


For example, the following command creates a password file named ACCT.PWD that allows up to 30 privileged users with different passwords. The file is initially created with the password SECRET for users connecting as SYSOPER or SYSDBA: 

    ORAPWD FILE=acct.pwd PASSWORD=secret ENTRIES=30

Following are descriptions of the parameters in the ORAPWD utility. 

FILE 
This parameter sets the name of the password file being created. You must specify the full pathname for the file. The contents of this file are encrypted, and the file is not user-readable. This parameter is mandatory. 

The types of file names allowed for the password file are operating system specific. Some platforms require the password file to be a specific format and located in a specific directory. Other platforms allow the use of environment variables to specify the name and location of the password file. See your operating system-specific Oracle documentation for the names and locations allowed on your platform. 

If you are running multiple instances of Oracle using the Oracle Parallel Server, the environment variable for each instance should point to the same password file. 

WARNING: 
It is critically important to the security of your system that you protect your password file and environment variables that identify the location of the password file. Any user with access to these could potentially compromise the security of the connection.   

PASSWORD 
This parameter sets the password for SYSOPER and SYSDBA. If you issue the ALTER USER command to change the password after connecting to the database, both the password stored in the data dictionary and the password stored in the password file are updated. The INTERNAL user is supported for backwards compatibility only. This parameter is mandatory. 

ENTRIES 
This parameter sets the maximum number of entries allowed in the password file. This corresponds to the maximum number of distinct users allowed to connect to the database as SYSDBA or SYSOPER. Entries can be reused as users are added to and removed from the password file. This parameter is required if you ever want this password file to be EXCLUSIVE. 

WARNING: 
If you ever need to exceed this limit, you must create a new password file. It is safest to select a number larger than you think you will ever need.   

See Also: Consult your operating system-specific Oracle documentation for the exact name of the password file or for the name of the environment variable used to specify this name for your operating system.

Terry M. Hoey
th3856@txmail.sbc.com
While I don't mind e-mail messages, please post all questions in these forums for the benefit of all members.