DP backup error ORA-19554: error allocating device, device type: SBT_TAPE ORA-27211, sbttape

Source: Internet
Author: User

DP backup error ORA-19554: error allocating device, device type: SBT_TAPE ORA-27211, sbttape

Environment: solaris 10, oracle 11.2.0.4 2 nodes rac

Symptom: rman backup reports the following error:

RMAN-00571: ========================================================== ==============================
RMAN-00569: ==================== error message stack follows ==========================
RMAN-00571: ========================================================== ==============================
RMAN-03009: failure of allocate command on dev_0 channel at 12/05/2014 10:25:25
The ORA-19554: error allocating device, device type: SBT_TAPE, device name:
ORA-27211: Failed to load Media Management Library
Additional information: 3986

1. Try to use the following method to configure the rman parameter.

Use configure channel device type 'sbt _ TAPE 'CLEAR;
Configure device type SBT_TAPE CLEAR; command;
As follows:
RMAN> configure channel device type 'sbt _ TAPE 'CLEAR;
Old RMAN configuration parameters are successfully deleted

RMAN> show all;
RMAN configuration parameters are:
Configure retention policy to redundancy 1;
Configure backup optimization off; # default
Configure default device type to 'sbt _ TAPE ';
Configure controlfile autobackup on;
Configure controlfile autobackup format for device type SBT_TAPE TO '% F'; # default
Configure controlfile autobackup format for device type disk to '% F'; # default
Configure device type SBT_TAPE PARALLELISM 1 backup type to backupset; # default
Configure device type disk parallelism 1 backup type to backupset; # default
Configure datafile backup copies for device type SBT_TAPE TO 1; # default
Configure datafile backup copies for device type disk to 1; # default
Configure archivelog backup copies for device type SBT_TAPE TO 1; # default
Configure archivelog backup copies for device type disk to 1; # default
Configure maxsetsize to unlimited; # default
Configure encryption for database off; # default
Configure encryption algorithm 'aes128 '; # default
Configure archivelog deletion policy to none; # default
Configure snapshot controlfile name to '/opt/oracle/product/10.2.0/dbs/snapcf_ge02.f'; # default

RMAN> configure default device type to Disk;
Old RMAN configuration parameters:
Configure default device type to 'sbt _ TAPE ';
New RMAN configuration parameters:
Configure default device type to disk;
New RMAN configuration parameters are successfully stored
Starting full resync of recovery catalog
Full resync complete

RMAN> configure device type SBT_TAPE CLEAR;
RMAN configuration parameters are successfully reset to default value

RMAN> show all;
RMAN configuration parameters are:
Configure retention policy to redundancy 1;
Configure backup optimization off; # default
Configure default device type to disk;
Configure controlfile autobackup on;
Configure controlfile autobackup format for device type disk to '% F'; # default
Configure device type disk parallelism 1 backup type to backupset; # default
Configure datafile backup copies for device type disk to 1; # default
Configure archivelog backup copies for device type disk to 1; # default
Configure maxsetsize to unlimited; # default
Configure encryption for database off; # default
Configure encryption algorithm 'aes128 '; # default
Configure archivelog deletion policy to none; # default
Configure snapshot controlfile name to '/opt/oracle/product/10.2.0/dbs/snapcf_ge02.f'; # default


Ii. Compare the AIX that can be backed up normally

Found the libobk file under $ ORACLE_HOME/lib /.

Sfc3rac1:/apps/oracle/product/10.2.0/lib $ ls-lrt | grep bobk
Lrwxrwxrwx 1 oracle oinstall 35 Jul 02 2010 libobk. a->/usr/omni/lib/libob2oracle8_64bit.a
Sfc3rac1:/apps/oracle/product/10.2.0/lib $

However, this soft connection file does not exist in oracle home under solaris.

There is a file in the DP installation path

[Root @ nsfc3rac2:/opt/omni/lib] # ls-lrt
Total 16200
-R-xr-x 1 root sys 9240 May 24 2013 libde_64bit.so
-R-xr-x 1 root sys 6508 May 24 2013 libde. so
-R-xr-x 1 root sys 19216 May 24 2013 libdc_64bit.so
-R-xr-x 1 root sys 14944 May 24 2013 libdc. so
-R-xr-x 1 root sys 590704 May 24 2013 libae_64bit.so
-R-xr-x 1 root sys 471768 May 24 2013 libae. so
-R-xr-x 1 root sys 22984 May 24 2013 libBrandChg_64bit.so
-R-xr-x 1 root sys 15452 May 24 2013 libBrandChg. so
-R-xr-x 1 root sys 41064 May 24 2013 libgcc_s.so.1
-R-xr-x 1 root sys 1314792 May 24 2013 libstdc ++. so.6.0.3
-R-xr-x 1 root sys 334632 May 24 2013 libssl. so.0.9.8
-R-xr-x 1 root sys 1664880 May 24 2013 libob2oracle8_64bit.so
-R-xr-x 1 root sys 1460060 May 24 2013 libob2oracle8. so
-R-xr-x 1 root sys 622436 May 24 2013 libcurl. so
-R-xr-x 1 root sys 1596784 May 24 2013 libcrypto. so.0.9.8
Drwxr-xr-x 2 root sys 512 Oct 30 build
Drwxr-xr-x 9 root sys 512 Oct 30 nls
Lrwxrwxrwx 1 root 13 Oct 30 :01 libgcc_s.so-> libgcc_s.so.1
Lrwxrwxrwx 1 root 18 Oct 30 :01 libstdc ++. so-> libstdc ++. so.6.0.3
Lrwxrwxrwx 1 root 18 Oct 30 :01 libstdc ++. so.6-> libstdc ++. so.6.0.3
Drwxr-xr-x 50 root sys 3584 Dec 3 perl
[Root @ nsfc3rac2:/opt/omni/lib] #

Manual soft connection

Ln-s/opt/omni/lib/libob2oracle8_64bit.so/u01/app/oracle/product/11.2.0/dbhome_1/lib/libobk. so

This file already exists in oracle-home

[Oracle @ nsfc3rac2:/u01/app/oracle/product/11.2.0/dbhome_1/lib] $ ls-lrt | grep bob
Lrwxrwxrwx 1 oracle oinstall 36 Dec 5 10:43 libobk. so->/opt/omni/lib/libob2oracle8_64bit.so
[Oracle @ nsfc3rac2:/u01/app/oracle/product/11.2.0/dbhome_1/lib] $


The backup can be backed up normally after the backup is restarted.

Related Article

E-Commerce Solutions

Leverage the same tools powering the Alibaba Ecosystem

Learn more >

Apsara Conference 2019

The Rise of Data Intelligence, September 25th - 27th, Hangzhou, China

Learn more >

Alibaba Cloud Free Trial

Learn and experience the power of Alibaba Cloud with a free trial worth $300-1200 USD

Learn more >

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.