Home » RDBMS Server » Backup & Recovery » ORA-19554: error allocating device, device type: SBT_TAPE, device name
ORA-19554: error allocating device, device type: SBT_TAPE, device name [message #623342] Mon, 08 September 2014 16:56 Go to next message
martin1
Messages: 3
Registered: September 2014
Location: United States
Junior Member
I am having the same error when trying to allocate the SBT_TAPE. Sometimes I get: "ORA-19554: error allocating device, device type: SBT_TAPE, device name:
ORA-27211: Failed to load Media Management Library". Sometimes I can connect. I have to try several times before I am finally able to connect, which means I cannot run this as a batch file. When I do connect, it looks like I connect to a different tape each time. For example, sometimes I connect and I get: "allocated channel: ORA_MAINT_SBT_TAPE_2", sometimes I get "allocated channel: ORA_MAINT_SBT_TAPE_5".
We are using Veritas Netbackup. The soft link has been established on the server.

Report message to a moderator

Re: ORA-19554: error allocating device, device type: SBT_TAPE, device name [message #623344 is a reply to message #623342] Tue, 09 September 2014 00:19 Go to previous messageGo to next message
Michel Cadot
Messages: 68417
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator

Check the logs of Veritas Netbackup.
Oracle RMAN is the victim not the culprit.

Report message to a moderator

Re: ORA-19554: error allocating device, device type: SBT_TAPE, device name [message #623371 is a reply to message #623344] Tue, 09 September 2014 06:47 Go to previous messageGo to next message
martin1
Messages: 3
Registered: September 2014
Location: United States
Junior Member
Thank you. I will check with the Netbackup guys.

Report message to a moderator

Re: ORA-19554: error allocating device, device type: SBT_TAPE, device name [message #623486 is a reply to message #623371] Wed, 10 September 2014 10:01 Go to previous message
martin1
Messages: 3
Registered: September 2014
Location: United States
Junior Member
Found something that might correct the problem. Our databases are on the rac. When we logon to rman, we of course use the database name. We changed it to use the tape service name instead (which is what we use for our sweeper jobs) and it appears the problem was fixed.

Report message to a moderator

Previous Topic: resetlogs or noresetlogs
Next Topic: rman crosscheck
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ]

Current Time: Thu Mar 23 06:43:02 CDT 2023
.:: Forum Home :: Blogger Home :: Wiki Home :: Contact :: Privacy ::.