Did you link the TSM connectAgent with Oracle after all was installed? This
could cause the error (4110) BACKUP_DIR not set.
Honestly i cannot remember all the issues, but i do remember receiving the
BACKUP_DIR error (quite a bit ago), and i think that problem was fixed when
i worked out the parms for channel allocation. Make sure these are correct.
Here is some info from the docs:
In Oracle version 8.1, if the RMAN-8526 message states that the disk API
was used, then the BACKUP_DIR environment variable was successfully
resolved by the Oracle channel and RMAN made the backup using the disk API.
If you do not see the 4110 or RMAN-008526 errors, but RMAN is not making
backups to the media manager, then follow the procedure below to determine
whether Oracle is using the dummy API.
To determine whether Oracle is using the dummy API:
Navigate to $ORACLE_HOME/bin. For example, enter: % cd
$ORACLE_HOME/bin
List the dynamic dependencies, that is, the shared objects linked at
runtime when you execute Oracle. The command differs depending on your
version of UNIX. For example, on Solaris issue: % ldd oracle | grep
libobk.so
Examine the output to see whether libobk.so is symbolically linked to
libdsbtsh8.so: libobk.so -> libdsbtsh8.so
If so, then Oracle is linking to the dummy API instead of your media management
API.
Test further by trying a backup using the dummy API. Note that you must set
the parms parameter of the allocate command so that the ENV variable
specifies a valid pathname for the BACKUP_DIR destination.
For example, you can issue:
run {
allocate channel c1 type 'sbt_tape'
parms="ENV=(BACKUP_DIR=/oracle/work)";
backup tablespace system;
}
If you see RMAN-08526 and RMAN-08525 in the output, then the backup to disk
using the dummy API was successful:
RMAN-08526: channel c1: WARNING: Oracle Test Disk API
RMAN-08525: backup set complete, elapsed time: 00:00:25
If Oracle is linked to the dummy API instead of your media manager's shared
library, then you must tell Oracle to link to the media manager's shared
library instead.
To relink to your media management API:
Shut down all databases that are using the Oracle executable before removing
the old libobk.so link.
For example, enter: SQL> SHUTDOWN IMMEDIATE
Delete the old symbolic link for libobk.so: % rm $ORACLE_HOME/lib/libok.so
Create a symbolic link between libobk.so and the shared library that you
want to use. For example, on SunSolaris you can create the symbolic link
libobk.so to a shared library such as liblsm.so using the ln command:
% ln -s $ORACLE_HOME/lib/libobk.so $ORACLE_HOME/lib/liblsm.so
Check that the link is successful by using the sbttest test program to back up
a file. For example, enter: % sbttest -testfile
Hope this helps,
KRoshto
TSM TSM <tsmtsm AT HOTMAIL DOT COM>@VM.MARIST.EDU> on 09/28/2000 01:30:08 PM
Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Re: Incr. Online SAP backup
Thanks Keith for your clues.
I went through the sbtio.log and I saw an entry there which says BACKUP_DIR
is not defined. But do you what this should be so that it can send data to
TSM ? I tried putting some dir. to that env. variable the RMAN started
putting the data in to that dir. and not to TSM.
Thanks again for your help again.
Shanta
>From: Keith Roshto <keith-roshto AT RELIANTENERGY DOT COM>
>Reply-To: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>To: ADSM-L AT VM.MARIST DOT EDU
>Subject: Re: Incr. Online SAP backup
>Date: Thu, 28 Sep 2000 10:08:49 -0500
>
>First ensure your env parms are set correctly when you allocate channels.
>TDP or Connect agent doc can help you.
>
>ORA-19624 simply states there is an error. Usually you will find an
>accompanying OS error, ANS, or other Oracle errors (RMAN, ORA). Look this
>up in doc.
>Also check your RMAN logs and trace files, as well as the files from the
>database server:
> sbtio.log
> dsmerror.log
> dsierror.log
>
>
>In my environment (AIX) rman creates the snapshot controlfile by default
in
>$ORACLE_HOME/dbs as file snapcf_<$ORACLE_SID>.f
>To set the location of the snapshot controlfile, from RMAN :
>
> set snapshot controlfile name to '/path/snap_prod.ctl'; (From
>Oracle
>8i Recovery Manager User's Guide and Reference.)
>
>Of course use your own path and filename.
>
>Keith Roshto
>
>
>
>
>
>
>TSM TSM <tsmtsm AT HOTMAIL DOT COM>@VM.MARIST.EDU> on 09/28/2000 08:38:31 AM
>
>Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
>Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
>
>To: ADSM-L AT VM.MARIST DOT EDU
>cc:
>
>Subject: Incr. Online SAP backup
>
>
>Hi everybody,
>
>Did anyone of tried incrementally backing up SAP R/3 DB online to TSM ?
>
>I have been trying with rman_util as the backup_devtype and I am getting
>RMAN Errors which says can not create file (looks like control file) due
to
>RPC Error, and Oracle pops out a message ORA19624 which is I/O error. Do
>you
>where this RMAN is trying create a file(temp. control file) As I know it
>should create it in /tmp directory and this has proper write permission.
>
>Thanks for any clues on this.
>
>Shanta.
>
>_________________________________________________________________________
>Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
>
>Share information about yourself, create your own public profile at
>http://profiles.msn.com.
_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
Share information about yourself, create your own public profile at
http://profiles.msn.com.
|
