cancel
Showing results for 
Search instead for 
Did you mean: 

back up filed due to tape drive is not detected

Former Member
0 Kudos

hi Experts,

here iam facing a problem and i tried for that so much and i didn't get salvation ,please try to solve my problem if any body knows ..its requesting

that i want to take backup of my Dev system and i connect my tape drive to my system and i scheduled backup by DB13

but that back up was canceled and below are shown error report

19.07.2010 13:10:08 Job started

19.07.2010 13:10:08 Step 001 started (program RSDBAJOB, variant &0000000000070, user ID SAL_BASIS)

19.07.2010 13:10:08 Execute logical command BRBACKUP On host saldev

19.07.2010 13:10:08 Parameters:-u / -jid TAPIN20100719130920 -i force -c force -n 1 -v SCRATCH

19.07.2010 13:10:08 BR0051I BRBACKUP 7.00 (36)

19.07.2010 13:10:08 BR0055I Start of database backup: bedrzjlo.tib 2010-07-19 13.10.08

19.07.2010 13:10:08 BR0484I BRBACKUP log file: /oracle/DEV/sapbackup/bedrzjlo.tib

19.07.2010 13:10:08 BR0477I Oracle pfile /oracle/DEV/102_64/dbs/initDEV.ora created from spfile /oracle/DEV/102_64/dbs/spfileDEV.ora

19.07.2010 13:10:08 BR0205I Backup volume initialization

19.07.2010 13:10:08 BR0058I BRBACKUP action ID: bedrzjlo

19.07.2010 13:10:08 BR0059I BRBACKUP function ID: tib

19.07.2010 13:10:08 BR0102I Following backup device will be used: /dev/rmt0.1

19.07.2010 13:10:08 BR0131I All volumes get the name SCRATCH

19.07.2010 13:10:08 BR0129I Force option set - no label checking during initialization

19.07.2010 13:10:08 BR0134I Unattended mode with 'force' active - no operator confirmation allowed

19.07.2010 13:10:08 BR0207I Volume in device: /dev/rmt0.1 will be initialized with name: SCRATCH

19.07.2010 13:10:08 BR0280I BRBACKUP time stamp: 2010-07-19 13.10.08

19.07.2010 13:10:08 BR0226I Rewinding tape volume in device /dev/rmt0...

19.07.2010 13:10:08 BR0278E Command output of 'LANG=C tctl -f /dev/rmt0 rewind':

19.07.2010 13:10:08 /dev/rmt0: No such device or address

19.07.2010 13:10:08 BR0280I BRBACKUP time stamp: 2010-07-19 13.10.08

19.07.2010 13:10:08 BR0279E Return code from 'LANG=C tctl -f /dev/rmt0 rewind': 2

19.07.2010 13:10:08 BR0213E Winding tape volume in device /dev/rmt0.1failed

19.07.2010 13:10:08 BR0219E Initialization of volume SCRATCH in device /dev/rmt0.1 failed

19.07.2010 13:10:08 BR0206I End of backup volume initialization

19.07.2010 13:10:08 BR0280I BRBACKUP time stamp: 2010-07-19 13.10.08

19.07.2010 13:10:08 BR0054I BRBACKUP terminated with errors

19.07.2010 13:10:08 External program terminated with exit code 3

19.07.2010 13:10:08 BRBACKUP returned error status E

19.07.2010 13:10:08 Job finished

thanks in advance

Accepted Solutions (1)

Accepted Solutions (1)

JPReyes
Active Contributor
0 Kudos

Rewinding tape volume in device /dev/rmt0...

No such device or address

Theres something wrong with the tape config... if its working fin at OS then you need to check the init<sid>.sap and check that the profile tape_address is pointing to the correct device

Regards

Juan

Former Member
0 Kudos

hi juan,

thanks for your reply here how can i check at os level please reply me

thanks

JPReyes
Active Contributor
0 Kudos

I already told you... you need to check the config in init<sid>.sap thats located in your oracle dbs directory

Regards

Juan

Former Member
0 Kudos

Hi,

Check the correct device address at OS level...

in HPUX ( #ioscan -fnC tape)

in AIX (# lsdev -Cc tape)

Once you find correct device and its status available (in AIX), Configure the same address in ini<SID>.sap profile parameter tape_address and tape_address_rew as suggested by Juan...

Regards.

Rajesh Narkhede

Former Member
0 Kudos

hi rajesh

thanks for your reply

and i already checked before as juan suggested but their in os level when i tried # lsdev -Cc tape

-->it shows rmt0 defined 07-08-01-6,0 other scsi tape drive.

and in init<sid>.sap file

  1. tape_size_arch = 100G

  2. level of parallel execution

  3. default: 0 - set to number of backup devices

exec_parallel = 0

  1. address of backup device without rewind

  2. [<dev_address> | (<dev_address_list>)]

  3. no default

  4. operating system dependent, examples:

  5. HP-UX: /dev/rmt/0mn

  6. TRU64: /dev/nrmt0h

  7. AIX: /dev/rmt0.1

  8. Solaris: /dev/rmt/0mn

  9. Windows: /dev/nmt0

  10. Linux: /dev/nst0

#tape_address = /dev/rmt0

tape_address = /dev/rmt0.1

  1. address of backup device without rewind used by brarchive

  2. default: value of the tape_address parameter

  3. operating system dependent

  4. tape_address_arch = /dev/rmt0.1

  5. address of backup device with rewind

  6. [<dev_address> | (<dev_address_list>)]

  7. no default

  8. operating system dependent, examples:

  9. HP-UX: /dev/rmt/0m

  10. TRU64: /dev/rmt0h

  11. AIX: /dev/rmt0

  12. Solaris: /dev/rmt/0m

  13. Windows: /dev/mt0

  14. Linux: /dev/st0

#tape_address_rew = /dev/rmt0.1 - Ritesh

tape_address_rew = /dev/rmt0

  1. address of backup device with rewind used by brarchive

  2. default: value of the tape_address_rew parameter

  3. operating system dependent

  4. tape_address_rew_arch = /dev/rmt0

  5. address of backup device with control for mount/dismount command

  6. [<dev_address> | (<dev_address_list>)]

  7. default: value of the tape_address_rew parameter

  8. operating system dependent

  9. tape_address_ctl = /dev/...

  10. address of backup device with control for mount/dismount command

  11. used by brarchive

  12. default: value of the tape_address_rew_arch parameter

  13. operating system dependent

  14. tape_address_ctl_arch = /dev/...

  15. volumes for brarchive

  16. [<volume_name> | (<volume_name_list>) | SCRATCH]

means init<sid>.sap file contains that os level address only but error shows not detected.. why this error occured

please reply

thanks

Former Member
0 Kudos

Hi,

-->it shows rmt0 defined 07-08-01-6,0 other scsi tape drive.

Your tape device is detected by Operating System but still it is not ready for use...

Check with your H/w vendor or system administrator.

It should show status "Available" instead of "defined"...

Regards.

Rajesh Narkhede

Former Member
0 Kudos

hi Rajesh,

thanks for your valuable reply and we don't have any system administrator in aix level so i only need to solve this thing so please tel me how can we check status and set device status at available instead of defined

thanks

Former Member
0 Kudos

Hi,

In AIX, "cfgmgr" command use to automatically configure newly added devices.

try to run this command without arguments..

    1. cfgmgr*

or

    1. smit cfgmgr*

Then check the status of the device (tape), if it still in "defined" state, just reboot the system.

See the link below for more details about this command.

[http://www.chm.tu-dresden.de/edv/manuals/aix/cmds/aixcmds1/cfgmgr.htm|http://www.chm.tu-dresden.de/edv/manuals/aix/cmds/aixcmds1/cfgmgr.htm]

Regards.

Rajesh Narkhede

Former Member
0 Kudos

hi rajesh,

here i tried for that command

cfgmgr

and i get

rmt0 defined 07-08-01-6 ,0 other scsi tape drive

rmt1 available 06-08-00-6,0 other scsi tape drive

what can do for this please reply me

JPReyes
Active Contributor
0 Kudos

rmt1 available 06-08-00-6,0 other scsi tape drive

Do you have a second device?... or maybe you should be using rmt1?

Regards

Juan

Former Member
0 Kudos

hi juan,

tnks for your reply we don't have any second device and here we used only one tape drive

previously i checked for status it shows

rmt0 defined XXXXxxxxxx...after i executed command

cfgmgr

then it shows

rmt0 defined XXXXXXXX

rmt1 available XXXXXXX....how can i change the status of rmt0 as available instead of defined

some one suggest me that u remove that rmt0 and after you try again cfgmgr command then it will displayed with available status ,so can i remove that or if any other solution is their please suggest me

Former Member
0 Kudos

Did you replace the tape drive or parts of the cabling?

It seems cfgmgr detected a new drive, or a new path to the old drive.

So imho you may either:

1) dicuss with your operating system or hardware team how to undo that change.

or

2) happily use the new rmt1 instead of the old rmt0.

regards

Former Member
0 Kudos

hi joe,

how can we use that rmt1 tel me in process

Former Member
Former Member
0 Kudos

You know what init<SID>.sap file is for?

And you know that you are allowed to change it, using an editor of your choice?

(But create a safety copy first!!)

Former Member
0 Kudos

Hi,

rmt1 available 06-08-00-6,0 other scsi tape drive

Now you can use "rmt1" tape device as this one is in "Available" state.

Configure below parameters in your init<SID>.sap.

tape_address = /dev/rmt1.1
tape_address_rew = /dev/rmt1

It will solve your problem.

Regards.

Rajesh Narkhede

Former Member
0 Kudos

hi rajesh,

finally please tel me one thing in

init.<sid>.sap ........tape_address=/dev/rmt1.1

tape_address_rew=/dev/rmt1............these two are required to change

can i change these two when application server is in running status or we required to down the application server then after i change these values please tel me

thanks

Former Member
0 Kudos

Hi ,

I am also faced the same issue and i have corrected the parameter in initSID.sap .

tape_address=/dev/rmt1.1

tape_address_rew=/dev/rmt1

there is no down time required to change the parameter .

I hope u r backup will success after changing the aboveparameter .

Regards

Former Member
0 Kudos

Hi,

can i change these two when application server is in running status or we required to down the application server then after i change these values

You dont need to stop application server...

You can safely modify the parameter while SAP is running...

Regards.

Rajesh Narkhede

Former Member
0 Kudos

Hi Vijaya ,

Are you taken backup successfully ?

Regards

Former Member
0 Kudos

hi friends,

yes here i finished my system backup with successfully by following your suggestions

thank you very much for who are helping me

thanks

Answers (2)

Answers (2)

Former Member
0 Kudos

Log in as the root user and use the chdev command to change

the block size on the tape device from the command line:

chdev -1 rmt# -a block_size=0

You can also change and VIEW the block size by selecting the

SMIT Devices-> Tape Drive->Change/Show Characteristics of a Tape

Drive menu options. Select the appropriate drive and

change the block size.

To check the current blocksize of the tape device, enter:

tctl -f /dev/rmt0 status

OR

  1. chdev -l rmt0 -a block_size=512

  2. mt -f /dev/rmt0 rewind

  1. mt -f /dev/rmt0 status

rmt0 Available 10-60-00-5,0 5.0 GB 8mm Tape Drive

attribute value description user_settable

mode yes Use DEVICE BUFFERS during writes True

block_size 512 BLOCK size (0=variable length) True

extfm yes Use EXTENDED file marks True

density_set_1 140 DENSITY setting #1 True

density_set_2 20 DENSITY setting #2 True

compress yes Use data COMPRESSION True

ret_error no RETURN error on tape change or reset True

Try it. I hope problem will be sorted out. I have faced same problem in db2 environment.

rgds

DK

Former Member
0 Kudos

Hi,

First check if the tape and tape drive are working fine by taking any small file backup at OS level. After that before starting the backup initialize the tape first and after that start the backup. Please refer the below link where it explains how to schedule backup.

https://cw.sdn.sap.com/cw/docs/DOC-10466

Regards,

Sharath

Former Member
0 Kudos

hi sharat,

thanks for reply

and here my tape and tape drive is working fine and

this my problem occurs at the time of initialize tape (not in backup time)

so please check and reply what hapen