Oracle Consulting Oracle Training Development

Remote DBA

Remote DBA Plans  

Remote DBA Service

Remote DBA RAC

Remote DBA Oracle Home
Remote DBA Oracle Training
Remote DBA SQL Tuning Consulting
Remote DBA Oracle Tuning Consulting
Remote DBA Data Warehouse Consulting
Remote DBA Oracle Project Management
Remote DBA Oracle Security Assessment
Remote DBA Unix Consulting
Burleson Books
Burleson Articles
Burleson Web Courses
Burleson Qualifications
Oracle Links
Remote DBA Oracle Monitoring
Remote DBA Support Benefits
Remote DBA Plans & Prices
Our Automation Strategy
What We Monitor
Oracle Apps Support
Print Our Brochure
Contact Us (e-mail)
Oracle Job Opportunities
Oracle Consulting Prices





Remote DBA services

Remote DBA Support

Remote DBA RAC

Remote DBA Reasons

Remote Oracle Tuning

Remote DBA Links

Oracle DBA Support

Oracle DBA Forum

Oracle Disaster

Oracle Training

Oracle Tuning

Oracle Training

 Remote DBA SQL Server

Remote MSSQL Consulting

Oracle DBA Hosting

Oracle License Negotiation







     Oracle orapwd to Connect Remotely as SYSRemote DBA

Using orapwd to Connect Remotely as SYSRemote DBA

The Oracle orapwd utility assists the Remote DBA with granting SYSRemote DBA and SYSOPER privileges to other users. By default, the user SYS is the only user that has these privileges. Creating a password file via orapwd enables remote users to connect with administrative privileges through SQL*Net.

The SYSOPER privilege allows instance startup, shutdown, mount, and dismount. It allows the Remote DBA to perform general database maintenance without viewing user data. The SYSRemote DBA privilege is the same as connect internal was in prior versions. It provides the ability to do everything, unrestricted.

If orapwd has not yet been executed, attempting to grant SYSRemote DBA or SYSOPER privileges will result in the following error:

SQL> grant sysRemote DBA to scott;
ORA-01994: GRANT failed: cannot add users to public password file

The following steps can be performed to grant other users these privileges:

1. Create the password file. This is done by executing the following command:
$ orapwd file=filename password=password entries=max_users

The filename is the name of the file that will hold the password information. The file location will default to the current directory unless the full path is specified. The contents are encrypted and are unreadable. The password required is the one for the SYS user of the database.

The max_users is the number of database users that can be granted SYSRemote DBA or SYSOPER. This parameter should be set to a higher value than the number of anticipated users to prevent having to delete and recreate the password file.

2. Edit the init.ora parameter remote_login_passwordfile. This parameter must be set to either SHARED or EXCLUSIVE. When set to SHARED, the password file can be used by multiple databases, yet only the SYS user is recognized. When set to EXCLUSIVE, the file can be used by only one database, yet multiple users can exist in the file. The parameter setting can be confirmed by:


To learn more about these techniques, see the book "Advanced Oracle Utilities: The Definitive Reference". 

You can buy it directly from the publisher and get instant access to the code depot of utilities scripts.




Remote DBA Service

Oracle Tuning Book


Advance SQL Tuning Book 

BC Oracle support

Oracle books by Rampant

Oracle monitoring software










BC Remote Oracle Support

Remote DBA

Remote DBA Services

Copyright © 1996 -  2013 by Burleson. All rights reserved.

Oracle® is the registered trademark of Oracle Corporation.