Receiving the error code 202 in netbackup
Updated: 27 Oct 2010 | 3 comments
Dear All,
We are using the Netbackup 5.x on Solaris & having the problem by getting the error code 202 " unable to sense the robot device"
Can anyone please give me the quick response.
Thanks.
For reference log is below
Script /usr/openv/netbackup/ext/db_ext/oracle/samples/rman/hot_database_backup.sh
==== started on Sun Apr 18 18:43:08 GMT 2010 ====
RMAN: /pd01/oracle/proddb/9.2.0/bin/rman
ORACLE_SID: PROD
ORACLE_USER: oraprod
ORACLE_HOME: /pd01/oracle/proddb/9.2.0
NB_ORA_FULL: 0
NB_ORA_INCR: 1
NB_ORA_CINC: 0
NB_ORA_SERV: aqsbkp01
NB_ORA_POLICY: oracle_database
Differential incremental backup requested
Sun Microsystems Inc. SunOS 5.9 Generic May 2002
You have mail.
RMAN> 2> 3> 4> 5> 6> 7> 8> 9> 10> 11> 12> 13> 14> 15> 16> 17> 18> 19> 20> 21> 22> 23> 24> 25> 26> 27> 28> 29> 30> 31> 32> 33> 34> 35> 36> 37> 38> RMAN> se: PROD (DBID=3464911)
using target database controlfile instead of recovery catalog
RMAN> 2> 3> 4> 5> 6> 7> 8> 9> 10> 11> 12> 13> 14> 15> 16> 17> 18> 19> 20> 21> 22> 23> 24> 25> 26> 27> 28> 29> 30> 31> 32> 33> 34> 35> 36> 37> 38>
allocated channel: ch00
channel ch00: sid=218 devtype=SBT_TAPE
channel ch00: VERITAS NetBackup for Oracle - Release 5.1 (2004043016)
sent command to channel: ch00
Starting backup at 18-APR-10
channel ch00: starting incremental level 1 datafile backupset
channel ch00: specifying datafile(s) in backupset
input datafile fno=00052 name=/pd01/oracle/proddata/undo03.dbf
input datafile fno=00065 name=/pd01/oracle/proddata/undo06.dbf
input datafile fno=00012 name=/pd01/oracle/proddata/undo01.dbf
input datafile fno=00059 name=/pd01/oracle/proddata/a_txn_ind11.dbf
input datafile fno=00025 name=/pd01/oracle/proddata/a_txn_ind01.dbf
input datafile fno=00019 name=/pd01/oracle/proddata/a_ref01.dbf
input datafile fno=00054 name=/pd01/oracle/proddata/a_txn_ind09.dbf
input datafile fno=00015 name=/pd01/oracle/proddata/a_media01.dbf
input datafile fno=00021 name=/pd01/oracle/proddata/a_summ01.dbf
input datafile fno=00004 name=/pd01/oracle/proddata/system04.dbf
input datafile fno=00020 name=/pd01/oracle/proddata/a_ref02.dbf
input datafile fno=00055 name=/pd01/oracle/proddata/a_txn_data06.dbf
input datafile fno=00007 name=/pd01/oracle/proddata/system07.dbf
input datafile fno=00017 name=/pd01/oracle/proddata/a_queue01.dbf
input datafile fno=00031 name=/pd01/oracle/proddata/odm.dbf
input datafile fno=00032 name=/pd01/oracle/proddata/olap.dbf
input datafile fno=00037 name=/pd01/oracle/proddata/xxaqsd01.dbf
input datafile fno=00016 name=/pd01/oracle/proddata/a_nolog01.dbf
input datafile fno=00039 name=/pd01/oracle/proddata/a_apps_ts_tools01.dbf
channel ch00: starting piece 1 at 18-APR-10
channel ch00: finished piece 1 at 18-APR-10
piece handle=bk_15011_1_716668991 comment=API Version 2.0,MMS Version 5.0.0.0
channel ch00: backup set complete, elapsed time: 00:07:55
channel ch00: starting incremental level 1 datafile backupset
channel ch00: specifying datafile(s) in backupset
input datafile fno=00041 name=/pd01/oracle/proddata/a_txn_data04.dbf
input datafile fno=00062 name=/pd01/oracle/proddata/undo05.dbf
input datafile fno=00067 name=/pd01/oracle/proddata/a_txn_data10.dbf
input datafile fno=00058 name=/pd01/oracle/proddata/undo04.dbf
input datafile fno=00023 name=/pd01/oracle/proddata/a_txn_data02.dbf
input datafile fno=00029 name=/pd01/oracle/proddata/a_txn_ind05.dbf
input datafile fno=00046 name=/pd01/oracle/proddata/a_queue04.dbf
input datafile fno=00061 name=/pd01/oracle/proddata/a_queue06.dbf
input datafile fno=00050 name=/pd01/oracle/proddata/a_media02.dbf
input datafile fno=00003 name=/pd01/oracle/proddata/system03.dbf
input datafile fno=00011 name=/pd01/oracle/proddata/system11.dbf
input datafile fno=00053 name=/pd01/oracle/proddata/a_queue05.dbf
input datafile fno=00006 name=/pd01/oracle/proddata/system06.dbf
input datafile fno=00009 name=/pd01/oracle/proddata/system09.dbf
input datafile fno=00045 name=/pd01/oracle/proddata/a_archive02.dbf
input datafile fno=00030 name=/pd01/oracle/proddata/ctxd01.dbf
channel ch00: starting piece 1 at 18-APR-10
channel ch00: finished piece 1 at 18-APR-10
piece handle=bk_15012_1_716669466 comment=API Version 2.0,MMS Version 5.0.0.0
channel ch00: backup set complete, elapsed time: 00:09:05
channel ch00: starting incremental level 1 datafile backupset
channel ch00: specifying datafile(s) in backupset
input datafile fno=00044 name=/pd01/oracle/proddata/a_summ02.dbf
input datafile fno=00063 name=/pd01/oracle/proddata/a_txn_data09.dbf
input datafile fno=00022 name=/pd01/oracle/proddata/a_txn_data01.dbf
input datafile fno=00048 name=/pd01/oracle/proddata/a_txn_data05.dbf
input datafile fno=00068 name=/pd01/oracle/proddata/a_queue08.dbf
input datafile fno=00026 name=/pd01/oracle/proddata/a_txn_ind02.dbf
input datafile fno=00043 name=/pd01/oracle/proddata/a_nolog02.dbf
input datafile fno=00057 name=/pd01/oracle/proddata/a_txn_ind10.dbf
input datafile fno=00049 name=/pd01/oracle/proddata/a_ref03.dbf
input datafile fno=00002 name=/pd01/oracle/proddata/system02.dbf
input datafile fno=00010 name=/pd01/oracle/proddata/system10.dbf
input datafile fno=00040 name=/pd01/oracle/proddata/a_queue03.dbf
input datafile fno=00036 name=/pd01/oracle/proddata/a_int02.dbf
input datafile fno=00013 name=/pd01/oracle/proddata/a_archive01.dbf
input datafile fno=00066 name=/pd01/oracle/proddata/a_queue07.dbf
channel ch00: starting piece 1 at 18-APR-10
channel ch00: finished piece 1 at 18-APR-10
piece handle=bk_15013_1_716670011 comment=API Version 2.0,MMS Version 5.0.0.0
channel ch00: backup set complete, elapsed time: 00:08:45
channel ch00: starting incremental level 1 datafile backupset
channel ch00: specifying datafile(s) in backupset
input datafile fno=00051 name=/pd01/oracle/proddata/undo02.dbf
input datafile fno=00064 name=/pd01/oracle/proddata/a_txn_ind12.dbf
input datafile fno=00024 name=/pd01/oracle/proddata/a_txn_data03.dbf
input datafile fno=00047 name=/pd01/oracle/proddata/a_txn_ind07.dbf
input datafile fno=00060 name=/pd01/oracle/proddata/a_txn_data08.dbf
input datafile fno=00028 name=/pd01/oracle/proddata/a_txn_ind04.dbf
input datafile fno=00042 name=/pd01/oracle/proddata/a_txn_ind06.dbf
input datafile fno=00056 name=/pd01/oracle/proddata/a_txn_data07.dbf
input datafile fno=00027 name=/pd01/oracle/proddata/a_txn_ind03.dbf
input datafile fno=00001 name=/pd01/oracle/proddata/system01.dbf
input datafile fno=00005 name=/pd01/oracle/proddata/system05.dbf
input datafile fno=00035 name=/pd01/oracle/proddata/discoverer01.dbf
input datafile fno=00014 name=/pd01/oracle/proddata/a_int01.dbf
input datafile fno=00008 name=/pd01/oracle/proddata/system08.dbf
input datafile fno=00018 name=/pd01/oracle/proddata/a_queue02.dbf
input datafile fno=00034 name=/pd01/oracle/proddata/portal01.dbf
input datafile fno=00038 name=/pd01/oracle/proddata/xxaqsx01.dbf
input datafile fno=00033 name=/pd01/oracle/proddata/owad01.dbf
channel ch00: starting piece 1 at 18-APR-10
channel ch00: finished piece 1 at 18-APR-10
piece handle=bk_15014_1_716670536 comment=API Version 2.0,MMS Version 5.0.0.0
channel ch00: backup set complete, elapsed time: 00:08:45
Finished backup at 18-APR-10
Starting Control File Autobackup at 18-APR-10
released channel: ch00
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of Control File Autobackup command on ch00 channel at 04/18/2010 19:17:42
ORA-01580: error creating control backup file /pd01/backups/BKUP160210/snapcf_PROD.f
ORA-27040: skgfrcre: create error, unable to create file
SVR4 Error: 2: No such file or directory
RMAN>
Recovery Manager complete.
Script /usr/openv/netbackup/ext/db_ext/oracle/samples/rman/hot_database_backup.sh
==== ended in error on Sun Apr 18 19:17:44 GMT 2010 ====
Discussion Filed Under:
Comments
Check robot for errors.
Check robot for errors. Ensure robot door is properly closed. Check scsi and/or fibre connections.
If no obvious problem, try to reboot the robot.
Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows.
Handy NBU links
robtest
From the server where robot is connected run the /usr/openv/volmgr/bin/robtest (hmm on Solaris it could be actually in /opt/openv/volmgr/bin).
Once you will pick the selection for your device enter such command
s d
if it does not return any issue you should be set. if anything would be NOK then it will tell you.
for help run enter ?
keep in mind that when robtest is running NBU can't manage robotic device.
Where abouts & when are you seeing the error code?
It's not in the RMAN log you provided.
A few other things to check maybe:
From T/N GENERAL ERROR: How to troubleshoot robot communication issues in Windows
I know this is Windows & you're running Solaris, but there are a still a few valid points e.g.
"
...
1. Ensure the robot is supported by NetBackup
2.......
3. Ensure robtest isn't already open
If there are no errors in the System Event Log or indicated by the robot itself, the configured device path for the robot may be incorrect. In this case, it should be reconfigured. This can be done either manually or by running the Device Configuration Wizard. Please see the NetBackup Media Manager System Administrator's Guide for assistance on configuring robots.
6.....
..."
There are also possible issues with "sequential" settings on specific robots per the follwoing T/N's:
Details: HP MSL 6000 library Using Library mode "sequential" for Netbackup Library configuration.
Compaq Robot TL891 generates an error during the robot inventory.
Lastly, a supporting document for the robtest commands:
Robtest commands that can be used to test the SCSI functionality of a robot
Regards Andy
"It's not too late to panic ..."
Would you like to reply?
Login or Register to post your comment.