- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- ABS 4.5 configuring to work with RMAN not success...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-01-2010 09:52 AM
тАО03-01-2010 09:52 AM
Oracle 10gR2
I upgraded to ABS 4.5.
Configuring ABS/MDMS to work with RMAN.
Followed the direction in ABS/Guide to Operation Chapter 9 and the release notes, section 6.1
Below is a copy of the command procedure I ran several times.
I ran this under my ID and Oracle10 with same results.
After the procedures below is a screen print of the com file results run. It seems it ran correctly, but I cannot find the sbttest.trc. It is not created. I cannot verify the test was successful.
$ on error then goto error
$ on control_y then goto abort
$ ***********************************
$ Define /sys abs_sbt sys$share:mdms$sbtshr_ma64_9I2.exe
$ SBTTEST :== $SYS$SYSTEM:MDMS$SBTTEST_MA64.EXE
$ DEFINE MDMS$SBT_ARCHIVE ORACLE_DB_ARCHIVE
$ DEFINE MSMS$SBT_CATALOG ORACLE_DB
$ SBTTEST TESTFILE -TRACE SBTTEST.TRC
$ show sym $status
$ **********************************
$ EXIT:
$ exit
[ORACLE10]$@SBTTEST.COM
%DCL-I-SUPERSEDE, previous value of ABS_SBT has been superseded
%DCL-I-SUPERSEDE, previous value of MDMS$SBT_ARCHIVE has been superseded
%DCL-I-SUPERSEDE, previous value of MSMS$SBT_CATALOG has been superseded
MM software supports SBT API version 2.0
MM software is version 4.5.0.0
sbtinit, vendor description string="System Backup to Tape V4.5 (1200)"
sbtinit successful
sbtinit2 successful
sbtbackup successful
sbtwrite2 successful, wrote 100 blocks
sbtinfo2, SBTBFINFO_NAME=TESTFILE
sbtinfo2, SBTBFINFO_METHOD=stream
sbtinfo2, SBTBFINFO_COMMENT=Onsite:
sbtinfo2, SBTBFINFO_CRETIME=Mon Mar 1 12:17:07 2010
sbtinfo2, SBTBFINFO_EXPTIME=Sun May 30 14:17:07 2010
sbtinfo2, SBTBFINFO_SHARE=single user
sbtinfo2, SBTBFINFO_ORDER=sequential access
sbtinfo2, SBTBFINFO_LABEL=HA0782
sbtinfo2 successful
sbtrestore successful
file was created by this program; seed=1267463824, blk_size=16384, blk_count=100
sbtread2 successful, read 100 buffers
sbtclose2 successful
sbtremove2(remove_after) successful, remove "TESTFILE"
sbtend successful
*** The SBT API test was successful ***
$STATUS == "%X00000001"
When I test this with RMAN, It faileds. I changed the password in the text below
$rman target "RMAN/XXXXX"@bpfp nocatalog cmdfile=ora_root:[admin.rman.scripts]rman_inc2_tape.rcv
Recovery Manager: Release 10.2.0.2.0 - Production on Mon Mar 1 12:43:57 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: BPFP (DBID=2841763345)
using target database control file instead of recovery catalog
RMAN> # rman_inc2_tape.rcv
2> #
3> #
4> # allocate tape channel and do an incremental backup of db
5> #
6> run
7> {
8> CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 1;
9>
10>
11> allocate channel t1 type 'sbt_tape'
12> parms="SBT_LIBRARY=abs_sbt,
13> ENV=(MDMS$SBT_CATALOG=ORACLE_RMAN,
14> MDMS$SBT_ARCHIVE=ORACLE_RMAN_ARCHIVE,
15> MDMS$SBT_IO_BLOCKSIZE=65024)";
16>
17>
18> backup incremental level = 2
19> database
20> format '%d_inc_%U.bck'
21> filesperset = 100;
22>
23>
24> release channel t1;
25> }
26>
old RMAN configuration parameters:
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 6 BACKUP TYPE TO BACKUPSET;
new RMAN configuration parameters:
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 1 BACKUP TYPE TO BACKUPSET;
new RMAN configuration parameters are successfully stored
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of allocate command on t1 channel at 03/01/2010 12:44:08
ORA-19554: error allocating device, device type: SBT_TAPE, device name:
ORA-27212: some entrypoints in Media Management Library are missing
HP IPF VMS Error: 2: no such file or directory
Recovery Manager complete.
[ADMIN.RMAN.SCRIPTS]$
I am at a lost of what to do next. I think the test did not work. I cannot troubleshoot the problem because I did not create a sbttest.trc file.
Does anyone have a suggestion?
FYI - ABS/RMAN IS running fine on an alpha system es47 oracle version 9.2.0.8, OS OpenVMS 8.3a.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-01-2010 01:35 PM
тАО03-01-2010 01:35 PM
Re: ABS 4.5 configuring to work with RMAN not successful
I don't know anything about ABS or RMAN, but I'm wondering about this missing sbttest.trc file. Perhaps it's gone to an unexpected directory? Brute force approach is to search all devices:
$ DIR device:[000000...]sbttest /mod/since="-0-0:10:00.00"
(ie: look for all files created in the last 10 minutes)
repeat for each device on your system.
An even bigger hammer would be to use SET WATCH (privileged)
$ SET WATCH/CLASS=MAJ FILE
$ @SBTTEST.COM
$ SET WATCH/CLASS=NONE FILE
If a file is created you should see messages like this:
%XQP, Thread #0, Create/Access SBTTEST.TRC;1 (12530,6,0) Status: 00000001
%XQP, Thread #0, Control function (12530,6,0) Status: 00000001
%XQP, Thread #0, Lookup SBTTEST.TRC;1 (12530,6,0) Status: 00000001
%XQP, Thread #0, Lookup SBTTEST.TRC;1 (12530,6,0) Status: 00000001
aaa
%XQP, Thread #0, Modify SBTTEST.TRC;1 (12530,6,0) Status: 00000001
%XQP, Thread #0, Deaccess (12530,6,0) Reads: 0, Writes: 2, Status: 00000001
You can then look at the header using the FID, in this case 12530:
$ DUMP/HEADER/BLOCK=COUNT:0/IDENT=12530 device
This will give you the back link file identification, which you can dump with a similar DUMP command, giving you the next directory name, and its backlink. Chase to the top of the disk.
You other error:
>RMAN-03009: failure of allocate command on t1 channel at 03/01/2010 12:44:08
>ORA-19554: error allocating device, device type: SBT_TAPE, device name:
>ORA-27212: some entrypoints in Media Management Library are missing
>HP IPF VMS Error: 2: no such file or directory
Why is the device name blank? Where is SBT_TAPE defined? Is it a logical name, or in some other configuration file?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-02-2010 12:18 AM
тАО03-02-2010 12:18 AM
Re: ABS 4.5 configuring to work with RMAN not successful
the trace file will probably be setup to go into one of the dump directories for your database SID, on my system it is
sys$sysdevice:[oracle.admin.ORACLE_SID]
under there are the adump, bdump, cdump, udump etc trace output directories.
To me, this line is suspicious:
ORA-19554: error allocating device, device type: SBT_TAPE, device name:
it looks like there should be a device name output as well, which leads me to suspect that the backup device name isn't being set up properly. I'll have another look at your output, but this document
http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96566/rcmconc1.htm#430706
may shed some light on configuring channels and devices.
Regards
Patrick
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-02-2010 12:26 AM
тАО03-02-2010 12:26 AM
Re: ABS 4.5 configuring to work with RMAN not successful
could you type
SHOW ALL;
(including the semi-colon)
at the RMAN> prompt and post the output of the RMAN configuration parameters.
Thanks
Patrick
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-02-2010 06:38 AM
тАО03-02-2010 06:38 AM
Re: ABS 4.5 configuring to work with RMAN not successful
I looked in many directories and did not find anything. I will try your suggestions. The SBT_TAPE is defined in the procedure:
11> allocate channel t1 type 'sbt_tape'
12> parms="SBT_LIBRARY=abs_sbt,
13> ENV=(MDMS$SBT_CATALOG=ORACLE_RMAN,
14> MDMS$SBT_ARCHIVE=ORACLE_RMAN_ARCHIVE,
15> MDMS$SBT_IO_BLOCKSIZE=65024)";
Syntax is taken out exactly from chapter 9 abs ├в guide to operations and it works on another system.
**********************************
Patrick,
I looked in all *dump directories ├в nothing
Directory ORA_APPL3:[ORACLE10.oracle1020.admin.bpfp]
adump.DIR;1 0.50KB 6-DEC-2006 15:25:02.36
bdump.DIR;1 1KB 6-DEC-2006 15:25:02.37
cdump.DIR;1 0.50KB 6-DEC-2006 15:25:02.38
dpdump.DIR;1 0.50KB 6-DEC-2006 15:25:02.38
logs.DIR;1 0.50KB 17-JAN-2007 11:12:46.72
pfile.DIR;1 0.50KB 6-DEC-2006 15:25:02.38
scripts.DIR;1 1KB 6-DEC-2006 15:25:02.43
udump.DIR;1 9KB 6-DEC-2006 15:25:02.39
Total of 8 files, 15KB
[ORACLE10.ORACLE1020.ADMIN.BPFP]$dir [...]sbt*.trc;*
%DIRECT-W-NOFILES, no files found
RMAN> SHOW ALL;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 6 BACKUP TYPE TO BACKUPSET;
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 1 BACKUP TYPE TO BACKUPSET;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE MAXSETSIZE TO 256 G;
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'ora_appl3:[oracle10.oracle1020.oradata.bpfp]snapcf_bpfp.f';
I will configure the device sbt_tape in RMAN, allocate the device in my script, run to verify I receive the same error.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-07-2010 07:52 PM
тАО03-07-2010 07:52 PM
SolutionI observe that you are running Oracle 10gR2.
To use SBT feature of ABS, users of Oracle 10gR2 must change the path
of SBT_LIBRARY to SBT_LIBRARY=SYS$SHARE:MDMS$SBTSHR_MA64_9I2.EXE
instead of SBT_LIBRARY=├в abs_sbt├в , where ├в abs_sbt├в was a logical
defined (in file rdbms_logicals.com) for SBT library in the previous
versions of Oracle release.
Following is the RMAN script template:
RUN
{
allocate channel t1 type ├в sbt_tape├в
parms="SBT_LIBRARY=SYS$SHARE:MDMS$SBTSHR_MA64_9I2.EXE,
ENV=(MDMS$SBT_ARCHIVE=ORACLE_DB_ARCHIVE)";
backup <...>
<...>
<...>;
Restore <...>
<...>
<...>;
release channel t1;
}
Except the above changes, all the other procedures used for the Oracle 9iR2 are
applicable for Oracle 10gR2 as well.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-08-2010 05:25 AM
тАО03-08-2010 05:25 AM
Re: ABS 4.5 configuring to work with RMAN not successful
Thanks! That worked! I had defined a system logical "ABS_SBT" = "SYS$SHARE:MDMS$SBTSHR_MA64_9I2.EXE" and thought it would be passed through but RMAN does not pick up the logical.