[Critical] [90:63] Cannot load exchanger medium (Target drive is busy.)

It can be interesting in troubleshooting a device issue sometimes. Let's deal with the devices in this post..

Error Message:

[Normal] From: BMA@Mediasrv01.in.com "Drive01"  Time: 2/13/2014 5:41:04 PM

                By: UMA@Mediasrv01.in.com@Changer0:7:0:1

                Loading medium from slot 2 to device Tape0:7:0:0C

[Critical] From: BMA@Mediasrv01.in.com " Drive01"  Time: 2/13/2014 5:41:24 PM

[90:63]                  By: UMA@Mediasrv01.in.com@Changer0:7:0:1

                Cannot load exchanger medium (Target drive is busy.)

From the error message, we could find that the "Target drive is busy". 

>> Login to the media server from where the tape library/autoloader is connected

>> Run devbra -dev, the output would be the drives and exchanger detected from the device manager.

>> Use the uma along with the scsi path of exchanger (here it is Changer0:7:0:1) in cmd line (please see below).

>> Check if there is stuck tape in drive. Move the tape to a free slot either from GUI/CLI and run the backup.

>> there are chances that the library might be fully loaded and the drive too is holding a tape. So manually remove the tape from slot/drive.

Using UMA utility for device management:

Example of fully loaded autoloader which needs manually unload media from drive.

C:\uma -ioctl  Changer0:7:0:1

Changer0:7:0:1> stat d

          1 D1    Full  "" ""

Changer0:7:0:1> stat s

        1001 S1   Full  "" ""

        1002 S2   Full  "" ""

        1003 S3   Full  "" ""

        1004 S4   Full  "" ""

        1005 S5   Full  "" ""

        1006 S6   Full  "" ""

        1007 S7   Full  "" ""

        1008 S8   Full  "" ""

(OR)

Example of unloading media from drive to empty slot.

C:\uma -ioctl  Changer0:7:0:1

Changer0:7:0:1> stat d

          1 D1    Full  "" ""

Changer0:7:0:1> stat s

        1001 S1   Full  "" ""

        1002 S2   Full  "" ""

        1003 S3   Empty  "" ""

        1004 S4   Full  "" ""

        1005 S5   Full  "" ""

        1006 S6   Full  "" ""

        1007 S7   Full  "" ""

        1008 S8   Full  "" ""

Changer0:7:0:1> move D1 S3

Changer0:7:0:1> stat d

          1 D1    Empty  "" ""

>> This is one of many cases for 'Cannot load exchanger medium' error.

Oracle Errors 'ORA-01031' during backup

[Normal] From: BSM@cellserver01.co.in "Oraclespec01"  Time: 01/17/11 08:38:07

        OB2BAR application on "Oraserver01.co.in" successfully started.

[Normal] From: ob2rman@Oraserver01.co.in "Oradb01"  Time: 01/17/11 08:38:09

        Starting backup of target database.

[Major] From: ob2rman@Oraserver01.co.in "Oradb01"  Time: 01/17/11 08:38:10

        The database reported error while performing requested operation.

ERROR:

 ORA-01031: insufficient privileges

 CONNECT: dporadb01/*****@Oradb01

[Major] From: ob2rman@Oraserver01.co.in "Oradb01"  Time: 01/17/11 08:38:10

        Backup of target database failed.

[Normal] From: BSM@cellserver01.co.in "Oraclespec01"  Time: 01/17/11 08:38:11

        OB2BAR application on "Oraserver01.co.in" disconnected.

Reason :

This error message "ORA-01031: insufficient privileges" means the authentication failure to access the database for backup.

The password file must be the problem, if not the DB username is not removed. The password file might have expired or changed or do not have permissions.

Solution :

Please have your DB team to remove/recreate the password file.

Command would look like the below:

ORAPWD FILE=filename [ENTRIES=numusers] [FORCE={Y|N}] [IGNORECASE={Y|N}] [NOSYSDBA={Y|N}]

Reference:

http://docs.oracle.com/cd/B28359_01/server.111/b28310/dba007.htm#ADMIN10241

Hope this helps!

[90:54] Cannot unload medium, target slot (255) appears to be occupied

[Warning] From: BMA@server01.na.com "ESLE01_D1"  Time: 2/9/2014 1:13:44 PM
[90:54]   /dev/nst1
Cannot open device (Unit not ready.)

[Major] From: BMA@server01.na.com "ESLE01_D1"  Time: 2/9/2014 1:13:55 PM
[90:114]   By: UMA@cellserver01.na.com@/dev/autoch3
Cannot unload medium, target slot (255) appears to be occupied

> The above error is due to DP couldn't unload the media from where it was actually loaded to the drive.

> Move the tape manually from the drive using UMA
/dev/autoch3> move D3 S13

> Then retry the backup, which should be successful/the error will not repeat.

[Critical] [12:1051] Client security violation. Access denied.

Error:

[Warning] From: BSM@cellserver1.eu.pg.com "backup_spec_01"  Time: 1/28/2014 12:30:57 PM

            Cannot get the list of filesystems on host "winclient02.na.pg.com".

            Backup of this host will be retried at end of session.

[Critical] From: INET@winclient02.na.pg.com ""  Time: 1/28/2014 12:31:08 PM

[12:1051] Client security violation. Access denied.

[Normal] From: BSM@cellserver1.eu.pg.com "backup_spec_01"  Time: 1/28/2014 12:31:20 PM

Solution:

> Manually, edit the hosts file located under the path:

C:\WINNT\system32\drivers\etc\                  - Windows 2003

C:\Windows\system32\drivers\etc\                 - Later versions

Hosts File would look like the below, Add an entry in the file and save it. The client hosts file should contain the cell server/media server name/IP. This would let the BSM to start/end the DAs on the client machine with ease.

127.0.0.1           localhost

#178.11.4.38     abchpdp.ap.pg.com          abchpdp

#188.10.4.43     winclient01.eu.pg.com      winclient01

#199.19.4.24     winclient02.na.pg.com      winclient02

You may have to check the below hosts file for DP
/etc/opt/omni/client/allow_hosts

Have a Great Week!

Tip of the Day!

Hi there,

Good Morning!

Tip of the day is related to Data Protector (Session abort)

Scenario: If you happen to abort a backup session that was already started and running, do not abort the session directly. (Assuming the backup is copied to tape library.)

Follow the steps below:

> Cancel all the devices that are running
> Then abort the session (either from CLI/GUI)

After the media agents are aborted, you will see the message like below:

[Normal] From: BSM@server01.fp.sa.com "backup_spec01"  Time: 1/31/2014 10:28:03 PM
Device canceled by user dpuser1@mgmt01.fp.sa.com

[Normal] From: BMA@server01.fp.sa.com "ESL01_D01"  Time: 1/31/2014 10:29:11 PM
ABORTED Media Agent "ESL01_D01"

Reason:

Aborting the session directly would not allow the media agents to a clean exit, which might end in damaging the media headers, chances are there for the media to get stuck in drive, media might be marked as poor.

It is always wise to abort the media agents and then your session.

Have a Great day!