Re: sapdb and backint for oracle

On Thu, Aug 14, 2003 at 11:07:29AM +0200, Heinrich, Tilo wrote:
> Hello Christian,
> 
> "BI_CALLER VALUE:" can only be set starting with 7.3.0 Build 29. With
> 7.3.0 Build 28 your Backint for Oracle should see a BI_CALLER with the
> value BACKINT. One Backint for Oracle implementation that does not
> like this value is the one for TSM, there may be others. Starting with
> 7.3.0 Build 29, BI_CALLER is unset in the environment by default (no
> more problems with TSM) and can be set explicitly via "BI_CALLER
> VALUE:" - to avoid problems with other Backint for Oracle
> implementations, that do not like an unset BI_CALLER variable.

Hi,

we had similar problems with our LiveCache on an AIX system (SAPDB is of
version 7.4.2) in combination with TSM and backint for Oracle.

We now use a simple wrapper script instead of calling the backint for
Oracle directly as a quick hack: 
--- cut here ---
#!/bin/ksh

unset BI_CALLER
exec path-to-backint-for-oracle/backint "$@"
--- cut here ---

This script lives in the wrk directory for the LiveCache db as
backint.wrapper and the backint of SAPDB gets the following definition
in its utl file:
BACKINT: path-for-wrk-dir/backint.wrapper

Regards
Holger

> 
> Best Regards,
> Tilo Heinrich
> SAP Labs Berlin
> 
> -----Original Message-----
> From: ramses_7 [mailto:[email protected]]
> Sent: Wednesday, August 13, 2003 5:28 PM
> To: [email protected]
> Subject: sapdb and backint for oracle
> 
> Hello,
> 
> I am using sapdb 7.3.00 build 28 and want to backup the database with 
> the backint(for sapdb) and backint(for oracle) solution. I managed to 
> configure backint (for sapdb) with an parameterfile, but after the 
> 1st temporary file for the backint( for oracle) is created the backup 
> fails. The log says that the environment variable BI_CALLER is not 
> set correctly (this mssg comes from the backint for oracle). I tried 
> to figure out to which value i have to set the BI_CALLER VALUE in the 
> parameter file for backint (for sapdb), but didnt succed. I think 
> that?s because backint (for sapdb) removes the BI_CALLER environment 
> variable, so backint (for oracle) isn?t able to get it. Tried several 
> values for the BI_CALLER VALUE in the config-file for backint(for 
> sapdb), but regardless what i put in it the backint (for oracle) 
> doesn?t recognize it.
> 
> Does anyone had such an experience ?
> 
> Regards,
> 
> Christian

-- 
Email: [email protected]
Web: http://www.is-4.de/