[prev in list] [next in list] [prev in thread] [next in thread] 

List:       sapdb-general
Subject:    RE: BACKINT for SAPDB and BACKINT for Oracle
From:       "Heinrich, Tilo" <tilo.heinrich () sap ! com>
Date:       2005-01-25 12:25:02
Message-ID: CBA37975F4CFEB4D8EF145BE015569C90986E9 () dewdfe23 ! wdf ! sap ! corp
[Download RAW message or body]

Hello Andreas,

the environment variables BI_CALLER, BI_BACKUP and BI_REQUEST are indeed
part of the Backint for Oracle definition. The interface definition
states "In addition to the command line options, the interface also
supports some environment variables set by BRBACKUP or BRARCHIVE before
BACKINT is called." It does not say, that these variables are always set
(e.g. when Backint for Oracle is called manually) or that BI_CALLER is a
way of determining the current backup type (that is what BI_BACKUP was
invented for) or that the values of BI_CALLER are restricted to unset,
BRBACKUP, BRARCHIVE, BRRESTORE and BRRECOVER (it just states that the
last four values are the ones set by BRBACKUP and BRARCHIVE).

However, as arguably as IBM's interpretation of the Backint for Oracle
interface definition might be, you can force Backint for MaxDB to put
arbitrary values for BI_CALLER into the environment before Backint for
Oracle is called. This can be done with the help of option "BI_CALLER
VALUE:..." in Backint for MaxDB's configuration file (see also
http://dev.mysql.com/doc/maxdb/en/91/24b97d483411d5992500508b6b8b11/fram
eset.htm ,please note that there is currently a typo in that version of
the MaxDB documentation - it must be "BI_CALLER VALUE:" not
"BI_CALLER_VALUE:").

Best regards,
Tilo Heinrich
SAP Labs Berlin

>-----Original Message-----
>From: Vollmer Andreas [mailto:Andreas.Vollmer@asstec.com] 
>Sent: Monday, January 24, 2005 4:33 PM
>To: maxdb@lists.mysql.com
>Cc: Heinrich, Tilo
>Subject: AW: BACKINT for SAPDB and BACKINT for Oracle
>
>
>Hello Tilo,
>
>I verified, that the environment variable BI_BACKUP is set 
>correctly to FULL
>or ARCHIVE by SAPDB according to the type of backup (data or logs).
>
>I contacted IBM support and at last spoke with an IBM 
>developer who told me,
>that the environment variable BI_CALLER is also part of SAP's 
>BACKINT for
>Oracle interface description and is usually set by the calling 
>SAP programs
>BRARCHIVE.EXE and BRBACKUP.EXE to the appropriate values "BRARCHIVE" or
>"BRBACKUP".
>
>IBM's implementation relies on the value of the variable BI_CALLER. If
>BI_CALLER is set to "BRARCHIVE", TSM assumes that it should 
>perform a LOG
>backup and stores the files in the LOG management class. If 
>BI_CALLER is set
>to "BRBACKUP" or if the variable is empty, it assumes a DATA backup and
>stores the files in the DATA management class.
>
>I verified this by setting the BI_CALLER variable in the 
>parameter file of
>the SAPDB adapter program to "BRARCHIVE". TSM stores the files as LOGs,
>regardless of whether BI_BACKUP is set to "FULL" or "ARCHIVE".
>
>Why does the BI_CALLER variable default to empty in the SAPDB adapter
>program, although SAP's BACKINT for Oracle interface 
>specification (as of
>May 2003) includes the use of the BI_CALLER variable as 
>mentioned above?
>
>Is there a way to set the BI_CALLER variable dynamically during runtime
>through the SAPDB adapter program?
>
>
>Andreas Vollmer
>IBM Certified Deployment Professional
>Tivoli Storage Manager 5.2

-- 
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe:    http://lists.mysql.com/maxdb?unsub=sapdb-general@progressive-comp.com


[prev in list] [next in list] [prev in thread] [next in thread]