Author Topic: Oracle DBA Question 74  (Read 56 times)

0 Members and 1 Guest are viewing this topic.

Offline ralph0595

  • Full Member
  • *
  • Posts: 107
  • Karma: +0/-0
    • View Profile
Oracle DBA Question 74
« on: May 06, 2009, 06:22:54 AM »
Question:
You intend only to use password authentication and have used the password file utility to create a password as follows:

Sorapwd file=SORACLE_HOME/dbs/orapwDB01
password=orapass entries=5

The REMOTE_LOGIN_PASSWORDFILE initialization parameter is set to NONE. You created a user and granted only the SYSDBA privilege to that user as follows:

CREATE USER dba_user
            IDENTIFIED BY dba_pass;
GRANT sysdba TO dba_user;

The user attempts to connect to the database as follows:
       
        connect dba_user/dba_pass as sysdba;

Why does connection fail?

A. The DBA privilege was not granted to dba_user.
B. REMOTE_lOGIN_PASSWORDFILE is not set to EXCLUSIVE.
C. The password file has been created in the wrong directory
D. The user did not specify the password orapass to connect as SYSDBA

Answer: B

Techronnati | where technology never sleeps

Oracle DBA Question 74
« on: May 06, 2009, 06:22:54 AM »

Mountain View

 

Related Topics

  Subject / Started by Replies Last post
0 Replies
63 Views
Last post April 19, 2009, 06:01:21 AM
by ralph0595
0 Replies
64 Views
Last post April 19, 2009, 06:39:28 AM
by ralph0595
0 Replies
56 Views
Last post April 19, 2009, 06:41:37 AM
by ralph0595
0 Replies
59 Views
Last post April 19, 2009, 06:46:32 AM
by ralph0595
0 Replies
55 Views
Last post April 19, 2009, 06:51:28 AM
by ralph0595

Posting Disclaimer: Any individual may post a message in this forum and may do so anonymously. Therefore, the sole author is exclusively and entirely responsible for all opinions in that message. They do not represent the official opinions of Techronnati, its administrators or moderators or the Techronnati Management. Techronnati is merely acting as an impartial conduit for constitutionally protected free speech and is not responsible and will not be held liable for the content of such messages. All images and service logos are trademarks of their respective owners.