When using NetBackup for Oracle, the Recovery Manager script fails the "switch user" (su) command.

Article:TECH20582  |  Created: 2002-01-10  |  Updated: 2014-03-19  |  Article URL http://www.symantec.com/docs/TECH20582
Article Type
Technical Solution


Environment

Issue



When using NetBackup for Oracle, the Recovery Manager script fails the "switch user" (su) command.


Error



Status Code: 25 cannot connect on socket
A process timed out while connecting to another process for a particular operation. This problem can occur when a process tries to connect to the NetBackup Request Manager service or the NetBackup Database Manager service and the service is not running.


Solution



When using VERITAS NetBackup (tm) for Oracle, the Recovery Manager (RMAN) script fails the "switch user" (su) command.

In the problems log on the master server, the following appears:

Cannot become user Oracle and group DBA on client <name>.

listen for client protocol error - couldn't write necessary information on /usr/openv/netbackup/logs/user_ops/dbext/logs/3993.0.967125611

In the bpbrm log:

10:00:20 [25172] <16> bpbrm send_info_via_progress_file: cannot become user oracle and group dba on <client name>

The backup fails with a status 25.

The plus sign (+) had been removed from the last line of the /etc/group file. This "+" tells the system to look to NIS for a given users group. In this case, Oracle is a member of the group "dba." This prevents the backup script from executing the su - oracle command.

To fix this issue, add the plus sign (+) to last line of the /etc/group file.

 


Legacy ID



248067


Article URL http://www.symantec.com/docs/TECH20582


Terms of use for this information are found in Legal Notices