Unable to authenticate SYS/SYSTEM account while configuring the Remote Agent for Linux/Unix Servers (RALUS) for Oracle Backup.

Article: 100019743
Last Published: 2012-01-12
Ratings: 0 0
Product(s): Backup Exec

Problem

Unable to authenticate SYS/SYSTEM account while configuring the Remote Agent for Linux/Unix Servers (RALUS) for Oracle Backup.

Error Message

Validating Credentials... Failed to login

 

Attempt to configure Remote agent for Linux/Unix Servers (RALUS) for Oracle backup fails as the Backup Exec Oracle Agent configuration utility (AgentConfig) is not able to authenticate with the Oracle Instance while configuring Oracle Instance information.

 
Figure 1.
 
 

 

Cause

1. If 32 bit Oracle Application is running on the x64 bit Operating platform.
2. If IPv6 is enabled.
3. If the account does not have SYSOPER and SYSDBA rights.
4. If older version of RALUS is being used to configure the Oracle Application.
 

Solution

 
1. Ensure 32bit Oracle application is not running on the x64 bit Linux operating system as it is not compatible to be backed up.

Refer to following article for more information

  https://www.veritas.com/docs/000034587 

How to check the Linux Operating System Architecture.

1. Login to the system with root account.
2. At the prompt type # uname -a

Sample Uname -a Output

Linux localhost 2.6.22.17.tex2 #1 SMP Sun Feb 10 22:02:57 CST 2008 i686 Intel(R) Pentium(R) 4 CPU 3.06GHz GNU/Linux


How to check whether the Oracle Application is 32bit or 64bit.

1. Login to the system with root account.
2. Change the directory to Oracle Home directory

# cd $ORACLE_HOME/bin

3.  Type at the prompt

# file oracl*

This will display the file type of your oracle binaries.

For Example , If you are running 64 bit binaries, then the output will be as follow

oracle: ELF 64-bit MSB executable SPARCV9 Version 1, dynamically linked, not stripped



2. Ensure IPv6 is disabled.

How to check whether IPv6 is enabled or not.

Use the IFCONFIG command to see the INET6 entries. INET6 indicates that IPv6 is enabled.

The sample out of IFCONFIG

eth0
 
Link encap:Ethernet HWaddr 00:14:85:9C:CC:55
 
inet addr:192.168.0.12 Bcast:192.168.0.255 Mask:255.255.255.0
 
inet6 addr: fe80::214:85ff:fe9c:cc55/64 Scope:Link
 
UP LOOPBACK RUNNING MTU:16436 Metric:1
 
RX packets:7856 errors:0 dropped:0 overruns:0 frame:0
 
TX packets:7856 errors:0 dropped:0 overruns:0 carrier:0
 
RX bytes:492016 (480.4 KiB) TX bytes:398 (398.0 b)
 
Interrupt:201 Memory:e1000000-0
 

How to disable the IPv6.

 
1. Edit the modprobe.conf file on the Linux box.

# vi /etc/modprobe.conf

Add line: alias net-pf-10 off

2. Reboot the Linux server to ensure the changes take effect.



 
3. Ensure SYS /SYSTEM have both SYSDBA and SYSOPER rights.

How to ensure the SYS account has required privilege.

1. Login to the system with account ORACLE

2. Connect to Oracle Database using the following command.

#  sqlplus /nolog
#  connect / as sysdba
#  column sysoper format a10;
#  column sysdba format a10;
#  select * from v$pwfile_users;

This will the show the output as shown in the figure 2.

 
Figure 2.
 
 

Note : The Value FALSE indicates that the account does not have those rights.

How to give appropriate rights to the account.

1. Login to the system with account ORACLE
2. Connect to Oracle Database using the following command.
3. Type grant sysoper to system as shown in fig 3

 
Figure 3.
 
 


4. Ensure correct version of RALUS is running.

1. Login to the system
2. At the prompt type # cat /var/VRTSralus/ralus.ver

This will output the Build number. Compare the Build number with Backup Exec Media Server. Both Media server and RALUS should have the same build.  
 

Was this content helpful?