1. Support
  2. Knowledge base
  3. 100000903

Configuration fails with the error "This user account does not have the privileges that are required to log on to the oracle database"

Article: 100000903
Last Published: 2014-01-14
Ratings: 0 1
Product(s): Backup Exec

Problem

Unable to configure an Oracle instance in the Backup Exec Remote Agent for Linux and Unix Servers (RALUS) AgentConfig. Configuration fails with the error "This user account does not have the privileges that are required to log on to the oracle database"

Error Message

"This user account does not have the privileges that are required to log on to the oracle database"

Solution

Ensure that the Oracle user has the appropriate rights to connect to the database and is a member of the sysdba group. To verify the same, please refer to the Document in the related section of this article. 
 
If the user is properly created and has the required permissions but the error still occurs, check for the following:
 
  1. TNSNames.ora has the correct information related to this instance (IP address and port) and TNSPing resolves correctly to the name of the database instance. Example of an ideal TNSNAMES.ORA file:
# Generated by Oracle configuration tools.
 
instance1 =
 
(DESCRIPTION =
 (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.1.111)(PORT = 1111))
 (CONNECT_DATA =
 (SERVICE_NAME = instance1)
  )
 )
 
CAUTION: The TNSNAMES.ORA file is used both internally by Oracle and by applications which interface with the Oracle databases. The TNSNAMES.ORA file should only be modified by an Oracle DBA. Veritas Corporation strongly recommends backing up the TNSNAMES.ORA file before attempting any modification to it.
 
  1. Check in the /etc/oratab file that the path to the oracle home is properly set for the instance being configured.
  2. Check if the password file is missing or is corrupt. Search for the orapw<sid_name> password file. If it is not present, it can be created or recreated using the orapwd utility.
     
Use the orapwd to create a password file as follows:
orapwd file=orapw<sid_name> password=<passwd> entries=5
 
  1. Check that the following parameter is present in the init<sid>.ora file:
REMOTE_LOGIN_PASSWORDFILE=EXCLUSIVE
 
If it is not, or if it is set to NONE, change it to EXCLUSIVE and bounce the database.
 
AgentConfig utility should work properly if this is correctly configured. If the error persist, please contact Oracle Support and Veritas Support Services to continue investigating connection problems.
 

 

Was this content helpful?

Article Languages