cancel
Showing results for 
Search instead for 
Did you mean: 

(29) failed trying to exec a command

rssk
Not applicable

Hi,

When i am trying to run an rman backup i am getting the error (29) failed trying to exec a command,

Client is windows 2003 and master is linux,

The backup is getting completed successfully in the DB logs but i am getting the error 29,

Is it the password issue on the DB server,

How to resolve the issue.

 

5 REPLIES 5

Tmy_70
Level 5
Partner Accredited Certified

Check This link:

<install_path>\veritas\netbackup\db\dbtemplates\oracle directory on a Windows master server and in the/usr/openv/netbackup/db/dbtemplates/oracle directory on a UNIX/Linux master server.

http://www.symantec.com/business/support/index?page=content&id=TECH51372

Baski
Level 5
Partner Certified

Hi Mate, 

Some time, these backups failing on windows servers. Try to restart it. if still failing. Try to start from client end using "bpbackup" command. Then you will come some conclusion where is the fault.

 

install_path\NetBackup\bin\bpbackup [-p policy] [-s schedule] [-S
master_server...] [-t policy_type] [-L progress_log [-en]] [-w
[hh:mm:ss]] [-help] [-k "keyword_phrase"] -f listfile | filenames
install_path\NetBackup\bin\bpbackup -i [-p policy] [-h hostname] [-s
schedule] [-S master_server...] [-t policy_type] [-L progress_log
[-en]] [-w [hh:mm:ss]] [-k "keyword_phrase"]
install_path\NetBackup\bin\bpbackup -dssu DSSUname

 

Nicolai
Moderator
Moderator
Partner    VIP   

if the script contain multiple commands and one of them fail you may encounter status 29.

I had a Oracle script for Windows where the date command failed resulting in status 29, but the Oracle database backup worked as intended. 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Problem with missing Archive logs?

See http://www.symantec.com/docs/TECH51347

Also have a look at this TN: http://www.symantec.com/docs/TECH32290

Michael_G_Ander
Level 6
Certified

The bphdb & dbclient folders under ..Netbackup\logs.. probably have indication of what the problem is.

Also try to run the cmd script from a command prompt, it often helps to figure ot what part of the script that fails

Regards

Michael

 

The standard questions: Have you checked: 1) What has changed. 2) The manual 3) If there are any tech notes or VOX posts regarding the issue