Backint Error BKI0062E

Hi All,
After this weekend, all our production servers have problems with archive backup scheduled via DB13 (SAP transaction). This has started happening from Monday onwards. Till then, all backups were running succefully via DB13.  On checking the logs, the following is the error:
BKI0062E: The input file /oracle/RP1/saparch/.adxgdwhd.lst is not valid.
On checking, BRTOOLS is not executable by <SID>adm whereas it is executable by ora<SID>.  But, proper permissions are required for <SID>adm as this is the user executing the backup from SAP (DB13).
In some of the servers, <SID> did not have write permissions on directory /oracle/<SID>/saparch (which was strange as backups till then were successful). In ECC however, the permissions were correct but still the error persists (even though I am able to manually create the file).
Any clues/suggestions?
Thanks
Siva

Hello Siva,
http://www.personal.psu.edu/dept/aset/ait/tsm/5.1docs/html/messages/anrcms34.htm
> BKI0062E     The input file filename is not valid.
> Explanation: Tivoli Data Protection for R/3 is not able to read the input file filename correctly.
> User Response: Check the path and name of the output file and the appropriate file access permission.
Please check the permissions for saparch.
If you are not sure about the rights of the BR*Tools... so please run the script saproot.sh as root in the folder /sapmnt/<SID>/exe
Regards
Stefan

Similar Messages

  • Veritas NetBackup using backint: error -8020 Reply buffer filled

    Hi All
    I'm trying to configure NetBackup on one of our SAP BW 7.0 system with MaxDB 7.6.00.35 running on Linux. I followed sap help and configure the backint. But when I execute the backup I'm getting the following error.
    Constructed the following reply:
    ERR
    -24920,ERR_BACKUPOP: backup operation was unsuccessful
    The backup tool failed with 2 as sum of exit codes. The database request failed with error -8020.
    Reply buffer filled.
    following is the dbm.ebp
    2007-06-26 21:35:40
    Setting environment variable 'TEMP' for the directory for temporary files and pipes to default ''.
    Setting environment variable 'TMP' for the directory for temporary files and pipes to default ''.
    Using connection to Backint for MaxDB Interface.
    2007-06-26 21:35:40
    Checking existence and configuration of Backint for MaxDB.
    Using configuration variable 'BSI_ENV' = '/sapdb/data/wrk/BWA/backint/config' as path of the configuration file of Backint for MaxDB.
    Setting environment variable 'BSI_ENV' for the path of the configuration file of Backint for MaxDB to configuration value '/sapdb/data/wrk/BWA/backint/config'.
    Reading the Backint for MaxDB configuration file '/sapdb/data/wrk/BWA/backint/config'.
    Found keyword 'BACKINT' with value '/sapdb/BWA/db/bin/backint'.
    Found keyword 'INPUT' with value '/sapdb/data/wrk/BWA/backint/backint4MAXDB.in'.
    Found keyword 'OUTPUT' with value '/sapdb/data/wrk/BWA/backint/backint4MAXDB.out'.
    Found keyword 'ERROROUTPUT' with value '/sapdb/data/wrk/BWA/backint/backint4MAXDB.err'.
    Found keyword 'PARAMETERFILE' with value '/sapdb/data/wrk/BWA/backint/adapter.para'.
    Found keyword 'TIMEOUT_SUCCESS' with value '600'.
    Found keyword 'TIMEOUT_FAILURE' with value '300'.
    Found keyword 'ORIGINAL_RUNDIRECTORY' with value '/sapdb/data/wrk/BWA/'.
    Finished reading of the Backint for MaxDB configuration file.
    Using '/sapdb/BWA/db/bin/backint' as Backint for MaxDB program.
    Using '/sapdb/data/wrk/BWA/backint/backint4MAXDB.in' as input file for Backint for MaxDB.
    Using '/sapdb/data/wrk/BWA/backint/backint4MAXDB.out' as output file for Backint for MaxDB.
    Using '/sapdb/data/wrk/BWA/backint/backint4MAXDB.err' as error output file for Backint for MaxDB.
    Using '/sapdb/data/wrk/BWA/backint/adapter.para' as parameter file for Backint for MaxDB.
    Using '600' seconds as timeout for Backint for MaxDB in the case of success.
    Using '300' seconds as timeout for Backint for MaxDB in the case of failure.
    Using '/sapdb/data/wrk/BWA/dbm.knl' as backup history of a database to migrate.
    Using '/sapdb/data/wrk/BWA/dbm.ebf' as external backup history of a database to migrate.
    Checking availability of backups using backint's inquire function.
    Check passed successful.
    2007-06-26 21:35:40
    Checking medium.
    Check passed successfully.
    2007-06-26 21:35:40
    Preparing backup.
    Setting environment variable 'BI_CALLER' to value 'DBMSRV'.
    Setting environment variable 'BI_REQUEST' to value 'NEW'.
    Setting environment variable 'BI_BACKUP' to value 'FULL'.
    Constructed Backint for MaxDB call '/sapdb/BWA/db/bin/backint -u BWA -f backup -t file -p /sapdb/data/wrk/BWA/backint/adapter.para -i /sapdb/data/wrk/BWA/backint/backint4MAXD
    B.in -c'.
    Created temporary file '/sapdb/data/wrk/BWA/backint/backint4MAXDB.out' as output for Backint for MaxDB.
    Created temporary file '/sapdb/data/wrk/BWA/backint/backint4MAXDB.err' as error output for Backint for MaxDB.
    Writing '/backup/BWA/BWAPIPE #PIPE' to the input file.
    Prepare passed successfully.
    2007-06-26 21:35:40
    Creating pipes for data transfer.
    Creating pipe '/backup/BWA/BWAPIPE' ... Done.
    All data transfer pipes have been created.
    2007-06-26 21:35:40
    Starting database action for the backup.
    Requesting 'SAVE DATA QUICK TO '/backup/BWA/BWAPIPE' PIPE BLOCKSIZE 8 NO CHECKPOINT MEDIANAME 'BWAPIPE'' from db-kernel.
    The database is working on the request.
    2007-06-26 21:35:40
    Waiting until database has prepared the backup.
    Asking for state of database.
    2007-06-26 21:35:40 Database is still preparing the backup.
    Waiting 1 second ... Done.
    Asking for state of database.
    2007-06-26 21:35:41 Database is still preparing the backup.
    Waiting 2 seconds ... Done.
    Asking for state of database.
    2007-06-26 21:35:43 Database has finished preparation of the backup.
    The database has prepared the backup successfully.
    2007-06-26 21:35:43
    Starting Backint for MaxDB.
    Starting Backint for MaxDB process '/sapdb/BWA/db/bin/backint -u BWA -f backup -t file -p /sapdb/data/wrk/BWA/backint/adapter.para -i /sapdb/data/wrk/BWA/backint/backint4MAXD
    B.in -c >>/sapdb/data/wrk/BWA/backint/backint4MAXDB.out 2>>/sapdb/data/wrk/BWA/backint/backint4MAXDB.err'.
    Process was started successfully.
    Backint for MaxDB has been started successfully.
    2007-06-26 21:35:44
    Waiting for end of the backup operation.
    2007-06-26 21:35:44 The backup tool is running.
    2007-06-26 21:35:44 The database is working on the request.
    2007-06-26 21:35:49 The backup tool is running.
    2007-06-26 21:35:49 The database is working on the request.
    2007-06-26 21:35:59 The backup tool is running.
    2007-06-26 21:35:59 The database is working on the request.
    2007-06-26 21:36:14 The backup tool is running.
    2007-06-26 21:36:14 The database is working on the request.
    2007-06-26 21:36:34 The backup tool is running.
    2007-06-26 21:36:34 The database is working on the request.
    2007-06-26 21:36:41 The backup tool process has finished work with return code 2.
    2007-06-26 21:36:41 The database has finished work on the request.
    Receiving a reply from the database kernel.
    Got the following reply from db-kernel:
    SQL-Code :-8020
    Date :20070626
    Time :00213542
    Database :BWA
    Server :s254176rg04
    KernelVersion :Kernel 7.6.00 Build 035-123-139-084
    PagesTransfered :131072
    PagesLeft :2847194
    MediaName :BWAPIPE
    Location :/backup/BWA/BWAPIPE
    Errortext :end of file
    Label :DAT_000000025
    IsConsistent :true
    FirstLogPageNo :1777329
    DBStamp1Date :20070626
    DBStamp1Time :00213541
    BDPageCount :2978242
    DevicesUsed :1
    DatabaseID :s254176rg04:BWA_20070605_123955
    Max Used Data Page
    Converter Page Count :1604
    The backup operation has ended.
    2007-06-26 21:36:41
    Filling reply buffer.
    Have encountered error -24920:
    The backup tool failed with 2 as sum of exit codes. The database request failed with error -8020.
    Constructed the following reply:
    ERR
    -24920,ERR_BACKUPOP: backup operation was unsuccessful
    The backup tool failed with 2 as sum of exit codes. The database request failed with error -8020.
    Reply buffer filled.
    2007-06-26 21:36:41
    Cleaning up.
    Removing data transfer pipes.
    Removing data transfer pipe /backup/BWA/BWAPIPE ... Done.
    Removed data transfer pipes successfully.
    Copying output of Backint for MaxDB to this file.
    Begin of output of Backint for MaxDB (/sapdb/data/wrk/BWA/backint/backint4MAXDB.out)----
    Reading parameter file /sapdb/data/wrk/BWA/backint/adapter.para.
    Using staging area /sapdb/BWA/backintstage/stage1 with a size of 1073741824 bytes.
    Using staging area /sapdb/BWA/backintstage/stage2 with a size of 1073741824 bytes.
    Using staging area /sapdb/BWA/backintstage/stage3 with a size of 1073741824 bytes.
    Using staging area /sapdb/BWA/backintstage/stage4 with a size of 1073741824 bytes.
    Using 2 file per Backint for Oracle call.
    Using /sapdb/BWA/db/bin/backint as Backint for Oracle.
    Using /sapdb/data/wrk/BWA/backint/initBWA.utl as parameterfile of Backint for Oracle.
    Using /sapdb/data/wrk/BWA/backint/BackintHistory as history file.
    Using /sapdb/data/wrk/BWA/backint/backint4Oracle.in as input of Backint for Oracle.
    Using /sapdb/data/wrk/BWA/backint/backint4Oracle.out as output of Backint for Oracle.
    Using /sapdb/data/wrk/BWA/backint/backint4Oracle.err as error output of Backint for Oracle.
    Reading input file /sapdb/data/wrk/BWA/backint/backint4MAXDB.in.
    Backing up pipe /backup/BWA/BWAPIPE.
    Found 1 entry in the input file.
    Starting the backup.
    Starting pipe2file program(s).
    Waiting for creation of temporary files.
    1 temporary file is available for backup.
    Calling Backint for Oracle at 2007-06-26 21:36:40.
    Calling '/sapdb/BWA/db/bin/backint -u BWA -f backup -t file -p /sapdb/data/wrk/BWA/backint/initBWA.utl -i /sapdb/data/wrk/BWA/backint/backint4Oracle.in -c' .
    Backint for Oracle ended at 2007-06-26 21:36:40 with return code 2.
    Backint for Oracle output: Reading parameter file /sapdb/data/wrk/BWA/backint/initBWA.utl.
    Backint for Oracle output:
    Backint for Oracle output:
    Backint for Oracle error output: No staging area is defined in the parameter file.
    Backint for Oracle error output: The path of Backint for Oracle is not defined in the parameter file.
    Backint for Oracle error output: The name of the history file is not defined in the parameter file.
    Backint for Oracle error output: The name of the input file of Backint for Oracle is not defined in the parameter file.
    Backint for Oracle error output: The name of the output file of Backint for Oracle is not defined in the parameter file.
    Backint for Oracle error output: The name of the error output file of Backint for Oracle is not defined in the parameter file.
    Backint for Oracle error output:
    Finished the backup unsuccessfully.
    #ERROR /backup/BWA/BWAPIPE
    End of output of Backint for MaxDB (/sapdb/data/wrk/BWA/backint/backint4MAXDB.out)----
    Removed Backint for MaxDB's temporary output file '/sapdb/data/wrk/BWA/backint/backint4MAXDB.out'.
    Copying error output of Backint for MaxDB to this file.
    Begin of error output of Backint for MaxDB (/sapdb/data/wrk/BWA/backint/backint4MAXDB.err)----
    Backint for Oracle was unsuccessful.
    End of error output of Backint for MaxDB (/sapdb/data/wrk/BWA/backint/backint4MAXDB.err)----
    Removed Backint for MaxDB's temporary error output file '/sapdb/data/wrk/BWA/backint/backint4MAXDB.err'.
    Removed the Backint for MaxDB input file '/sapdb/data/wrk/BWA/backint/backint4MAXDB.in'.
    Have finished clean up successfully.
    Please help
    Thanks
    Andy

    Hi Natalia
    Thanks for the reply. Below is initBWA.utl file. At this stage The first staging file is successfully written to the tape and the backup fails after that. The problem I guess is the staging file is not getting deleted or over written after it is written to the tape. Thanks   
    backint parameters
    switch_list: is required and is used as a control file to communicate with
    BACKINT and BRBACKUP for online backups.  A switch list file is created
    every time BRBACKUP wants to backup a file or when it wants to indicate that
    a backup is finished.  The switch_list parameter must be set to a file path
    that is located in: $ORACLE_HOME/sapbackup/.switch.lis.
    switch_list /sapdb/BWA/backintstage/.switch.lis
    switch_sem: is required and is used as a control file which is used between
    BACKINT and BRBACKUP to communicate.  After the switch list file has been
    created and closed, BACKINT creates the switch semaphore file and waits until
    it is deleted by BRBACKUP.  The switch_sem parameter must be set to a file
    path that is located in: $ORACLE_HOME/sapbackup/.switch.sem.
    switch_sem /sapdb/BWA/backintstage/.switch.sem
    switch_log: is required and is used as a control file which is used between
    BACKINT and BRBACKUP to communicate.  After the switch semaphore file has
    been deleted, BACKINT opens and reads the switch log file to determine if
    the process is successful.  The switch log file is created by BRBACKUP.  The
    switch_log parameter must be set to a file path that is located in:
    $ORACLE_HOME/sapbackup/.switch_log.
    switch_log /sapdb/BWA/backintstage/.switch.log
    backint_dir: is an optional parameter and must be set to a directory that is
    public.  BACKINT uses this directory for work space and to store files called
    backint.times, which keeps track of backup information.
    #backint_dir /oracle/SAP/sapscript/backint_dir
    server: is an optional parameter and is the machine name of the NetBackup
    Master server.   The NetBackup Master server is the name of the machine that
    provides most of the administration and control for Netbackup operations and
    contains the NetBackup database.  If BACKINT finds a $SAP_SERVER environment
    variable, the server parameter's value will be overriden by the value of
    $SAP_SERVER.  Also, if the server parameter is not specified and there is no
    environment variable then the server parameter value will default to the
    SERVER option specified in the Netbackkup bp.conf file.
    #server jupiter
    client: is an optional parameter and must be set to a machine name that has
    the NetBackup client software, an Oracle database, and a SAP environment.
    In some cases the server and client machine will be the same machine.  If
    BACKINT finds a $SAP_CLIENT environment variable, the client parameter value
    will be overriden by the assigned environment variable.  If the client
    parameter is not specified and there is no environment variable, then the
    client parameter value will default to the CLIENT_NAME specified in the
    Netbackkup bp.conf file.  If the value is not in bp.conf, BACKINT uses the
    value returned by the gethostname() libary function.
    #client jupiter
    drives: is an optional parameter and should be set to the number of
    simultaneous tape drives to kickoff backup. Set NetBackup Server to support
    multiple simultaneous client backups and the number of storage units/tape
    drives for this backup policy.  Based on the number of drives specified
    BACKINT will simultaneously run the same number of bpbackup/bprestore
    commands.  So for example, if the drives parameter is set to 5, then 5
    bpbackup/bprestore jobs will run at the same time.  The drives parameter
    should be set to the following rule:
    drives = Number of storage units per policy  X  MPX number
    The drives parameter value should not exceed the Set Maxium Jobs per Client
    global attribute.  If BACKINT finds a $SAP_DRIVES environment variable, the
    drive parameter value will be overriden by the value of the $SAP_DRIVES
    variable.  If the drive parameter is not specified and there is no
    environment variable, then BACKINT will exit with an error.
    #drives 1
    policy: is an optionl parameter and should be set to the name of a SAP policy
    type that has been defined in Netbackup.  The SAP policy must have a schedule
    type of Application Backup defined in order for BACKINT to work.  If BACKINT finds
    a $SAP_POLICY environment variable, the policy parameter value will be
    overriden by the value of the $SAP_POLICY variable.  If the policy parameter
    is not specified and there is no environment variable, then the policy
    parameter value will default to the BPBACKUP_POLICY option in the NetBackup
    bp.conf file.  By default, BPBACKUP_POLICY is not in any bp.conf file, then
    NetBackup uses the first SAP policy type that it finds that has the client
    and a user-directed backup schedule.
    policy AXON2541766-SAP
    schedule: Is optional and must be set to the name of type  Application Backup
    schedule that is associates with a SAP policy type.  The schedule can
    define aspects of the backup such as how long Netbackup retains images,
    maximum MPX per drive, storage unit, and volume pool.  If BACKINT finds a
    $SAP_SCHED environment variable, the schedule parameter value will be
    overriden by the value of the $SAP_SCHED environment variable.  If the
    schedule parameter is not specified and there is no environment variable,
    then the schedule parameter value will default to the BPBACKUP_SCHED option
    in the NetBackup bp.conf file.  By default BPBACKUP_SCHED is not in any
    bp.conf file then, NetBackup uses the first schedule of type Application Backup
    that it finds. It is higly recommended to set schedule parameter in *.utl file.
    #schedule Default-Application-Backup
    policy2: is optional and is the name of a policy to be used for the
    secondary SAP backup.  The secondary backup is performed for each SAP
    database backup on files that are needed to track SAP backup information.
    This option would be used to save the backup information on a different
    media.  If policy2 is not specified, then the policy parameter value is used.
    #policy2 sap_sec_backup
    schedule2: is optional and is the name of a Application Backup schedule to be
    used for the secondary SAP  backup.  The secondary backup is performed for
    each SAP database backup on files that are needed to track SAP backup
    information.  This option would be used to save the backup information on a
    different media.  If schedule2 is not specified, then the schedule parameter
    value is used.
    #schedule2 userbkps
    sort_backup_type: [size | custom | device | drive ]
    This parameter is optional and is used to specify four different backup
    sort option.  If sort_backup_type is not specified it will default to
    the size option.
    #sort_backup_type size
    sort_backup_type: [image | custom | drive ]
    This parameter is optional and is used to specify three different restore
    sort option.  If sort_restore_type is not specified it will default to
    the image option.
    #sort_restore_type image
    custom_sort_file: is optional and is used in conjunction with the
    sort_backup_type and sort_restore_type parameter.  If the custom option is
    specified on either the sort_backup_type or sort_restore_type parameter,
    then the custom_sort_file parameter needs to be set to a valid file.  The
    value for this parameter must be a full path name to a custom sort file and
    must have public permissions.
    #custom_sort_file /oracle/SAP/sapscripts/custom_sort_file
    master_time_offset:  is an option parameter used to restore old backups
    if there was a time difference between the master and client machines.
    This option should only be used for restoring 3.0 or older backup or if a
    backint restore can't find a specified backup.  The master_time_offset is
    specified in minutes.  The value will be subtract from the start time and
    added to the end time for a restore or inquire.
    #master_time_offset 2
    #sleep: is optional and is used to specify a sleep time to monitor the
    bpbackup or bprestore logs.  The default is 5 seconds.  When BACKINT is
    called a number of bpbackup/bprestore commands can be running at the
    sametime.  BACKINT monitors each command and display the information to the
    -o parameter.  In some cases bpbackup/bprestore information is not displayed
    because of the monitoring cycle.  Therefore this option is used mainly for
    debug reasons.
    #sleep 5
    policy_log: is optional and is the name of a policy to be used for
    backing up a second copy of an archive log.  If this option is specified
    then two backups will be performed on the same archive log.  The first
    backup will go to the "policy" name option and the second backup will go
    to the "policy_log" name option.
    #policy_log sap_archive_logs
    sched_log: is optional and is the name of a schedule to create a second
    backing up of an archive log.  If this option is specified then two backup
    will be performed on the same archive log.  The first backup will go to the
    "schedule" option and the second backup will be go to the "sched_log" and
    option.  The "sched_log" name must be a valid schedule name under the
    "policy_log" name option, otherwise it must be a valid schedule name under
    the "policy" name option.
    #sched_log Default-Application-Backup
    retry_backup: is an optional parameter and should be set to the number of
    retries for a failed backup.  If this option is specified BACKINT will
    retry a failed bpbackup job.  The number of retries is determine by the
    value on the retry_backup parameter.
    #retry_backup 2
    fail_backup: is optional and is used to stop the backup process immediately
    when an error occurs.  The standard behavior of BACKINT is to continue
    processing even in the event of an error and then report what files failed
    and what files were successful.  If this parameter is specified then BACKINT
    will stop process on the first error and report failures for all the
    files that were not backed up.
    #fail_backup
    media_notify_script: is optional and is used to call a script when a
    "Waiting mount" is displayed in a bpbackup/bprestore log.  The value for this
    option must be the full path name to a script.  The script should also have
    the right file permissions and should be tested before implementation.  If
    the message is encountered and this optional is specified, then the
    following commands will be executed from BACKINT:
      MEDIA_ID=A001;export MEDIA_ID
      NETBACKUP_SERVER=saturn;export NETBACKUP_SERVER
      /oracle/SAP/sapscripts/sap_media_notify
    #media_notify_script /oracle/SAP/sapscripts/sap_media_notify
    restore_filter: is optional and is used to resolve linked file paths on a
    restore.  This parameter should be commented out and should be used only on
    rare occassions.  The following are the cases were this parameter is needed:
      1) Oracle table spaces use file paths
      2) The directory paths to the Oracle table spaces are linked paths
      3) The linked directory paths don't exist at restore time
    The value for this parmater must be a fully qualified file path name to a
    script, which has the right permissions and has been tested before being
    implemented.  The script must have an input and output parameter and be able
    to modify the contents of a text file which contains file paths.  The script
    is responsible for converting linked directory paths into absolute directory
    paths. See /usr/openv/netbackup/ext/db_ext/sap/scripts/restore_filter for
    an example.
    #restore_filter /oracle/SAP/sapscripts/restore_filter.sh
    bplist_filter: is optional and is used to resolve linked file passes on an
    inquire.  This parameter should be commented out and should be used only on
    rare occassions.  Like the restore_filter_script parameter this is needed
    for the following cases:
      1) Oracle table spaces use file paths
      2) The directory paths to the Oracle table spaces are linked paths
      3) The linked directory paths don't exist at restore time
    The value for this option must be a fully qualified path name to a script,
    which has the right file permission and has been tested before being
    implemented.  The script must have an input and output parameter and be able
    to modify the contents of a text file, which contains file paths.  The script
    is responsible for converting absolute directory paths into linked directory
    paths.  This is just the opposite of the restore filter script. See
    /usr/openv/netbackup/ext/db_ext/sap/scripts/bplist_filter for an example.

  • Backint Error - BKIERR: Product grace period expired.

    Hello SDN Community.
    I have the following error when I try to perform a Backup Full (SAP-ORACLE-ARCserver).
    Program:          BACKINT                                            
    Parameters:                                                          
    Nodename:         AZANT03                                            
    Function:         BACKUP                                             
    BackupType:       file                                               
    Input File:       H:\oracle\AZD\sapbackup\.bdvykfov.lst              
    Output File:                                                         
    Parameter File:   E:\ORACLE\AZD\DATABASE\dia01A.utl                  
    Parallel sessions:1                                                  
    BKIERR: Product grace period expired.                                
    BR232E 0 of 83 files saved by backup utility                         
    BR280I Time stamp 2007-08-17 22.13.28                                
    BR231E Backup utility call failed                                    
    I tried copiying the BACKINT.EXE file from other site, but the problem continues.
    Do you know, how can I solve the problem?
    Thanks.
    David

    You downloaded it somewhere, right?
    ARCserve is nowadays CA, I think you can just call them - see the page here:
    http://ca.com/products/product.aspx?ID=4536
    Look in the upper right corner for a phone number.
    Markus

  • Got the following reply from db-kernel: SQL-Code :-903

    Dear Experts,
    I am having a problem running MaxDB Data backup on Netbackup.... Please se log below and suggest.
    2011-04-11 13:30:38
    Using environment variable 'TEMP' with value 'C:\Windows\TEMP' as directory for temporary files and pipes.
    Using connection to Backint for MaxDB Interface.
    2011-04-11 13:30:39
    Checking existence and configuration of Backint for MaxDB.
        Using configuration variable 'BSI_ENV' = 'C:\Netbackup_Script\bsi_backint_daily.env' as path of the configuration file of Backint for MaxDB.
        Setting environment variable 'BSI_ENV' for the path of the configuration file of Backint for MaxDB to configuration value 'C:\Netbackup_Script\bsi_backint_daily.env'.
        Reading the Backint for MaxDB configuration file 'C:\Netbackup_Script\bsi_backint_daily.env'.
            Found keyword 'BACKINT' with value 'D:\sapdb\KGP\db\bin\backint.exe'.
            Found keyword 'INPUT' with value 'E:\sapdb\data\wrk\KGP\backint.input'.
            Found keyword 'OUTPUT' with value 'E:\sapdb\data\wrk\KGP\backint.output'.
            Found keyword 'ERROROUTPUT' with value 'E:\sapdb\data\wrk\KGP\backint.error'.
            Found keyword 'PARAMETERFILE' with value 'C:\Netbackup_Script\backint_parameter_daily.txt'.
        Finished reading of the Backint for MaxDB configuration file.
        Using 'D:\sapdb\KGP\db\bin\backint.exe' as Backint for MaxDB program.
        Using 'E:\sapdb\data\wrk\KGP\backint.input' as input file for Backint for MaxDB.
        Using 'E:\sapdb\data\wrk\KGP\backint.output' as output file for Backint for MaxDB.
        Using 'E:\sapdb\data\wrk\KGP\backint.error' as error output file for Backint for MaxDB.
        Using 'C:\Netbackup_Script\backint_parameter_daily.txt' as parameter file for Backint for MaxDB.
        Using '300' seconds as timeout for Backint for MaxDB in the case of success.
        Using '300' seconds as timeout for Backint for MaxDB in the case of failure.
        Using 'E:\sapdb\data\wrk\KGP\dbm.knl' as backup history of a database to migrate.
        Using 'E:\sapdb\data\wrk\KGP\dbm.ebf' as external backup history of a database to migrate.
        Checking availability of backups using backint's inquire function.
    Check passed successful.
    2011-04-11 13:30:39
    Checking medium.
    Check passed successfully.
    2011-04-11 13:30:39
    Preparing backup.
        The environment variable 'BSI_ENV' has already the value 'C:\Netbackup_Script\bsi_backint_daily.env'.
        Setting environment variable 'BI_CALLER' to value 'DBMSRV'.
        Setting environment variable 'BI_REQUEST' to value 'NEW'.
        Setting environment variable 'BI_BACKUP' to value 'FULL'.
        Constructed Backint for MaxDB call 'D:\sapdb\KGP\db\bin\backint.exe -u KGP -f backup -t file -p C:\Netbackup_Script\backint_parameter_daily.txt -i E:\sapdb\data\wrk\KGP\backint.input -c'.
        Created temporary file 'E:\sapdb\data\wrk\KGP\backint.output' as output for Backint for MaxDB.
        Created temporary file 'E:\sapdb\data\wrk\KGP\backint.error' as error output for Backint for MaxDB.
        Writing 'D:\sapdb\pipe2 #PIPE' to the input file.
    Prepare passed successfully.
    2011-04-11 13:30:39
    Starting database action for the backup.
        Requesting 'SAVE DATA QUICK TO 'D:\sapdb\pipe2' PIPE BLOCKSIZE 8 NO CHECKPOINT MEDIANAME 'BACKDBFULL'' from db-kernel.The database is working on the request.
    2011-04-11 13:30:39
    Waiting until database has prepared the backup.
        Asking for state of database.
        2011-04-11 13:30:39 Database is still preparing the backup.
        Waiting 1 second ... Done.
        Asking for state of database.
        2011-04-11 13:30:41 Database has finished preparation of the backup.
    The database has prepared the backup successfully.
    2011-04-11 13:30:41
    Starting Backint for MaxDB.
        Starting Backint for MaxDB process 'D:\sapdb\KGP\db\bin\backint.exe -u KGP -f backup -t file -p C:\Netbackup_Script\backint_parameter_daily.txt -i E:\sapdb\data\wrk\KGP\backint.input -c >>E:\sapdb\data\wrk\KGP\backint.output 2>>E:\sapdb\data\wrk\KGP\backint.error'.
        Process was started successfully.
    Backint for MaxDB has been started successfully.
    2011-04-11 13:30:41
    Waiting for end of the backup operation.
        2011-04-11 13:30:41 The backup tool is running.
        2011-04-11 13:30:41 The database is working on the request.
        2011-04-11 13:30:43 The database has finished work on the request.
        Receiving a reply from the database kernel.
        Got the following reply from db-kernel:
            SQL-Code              :-903
        2011-04-11 13:30:43 The backup tool is running.
        2011-04-11 13:30:44 The backup tool process has finished work with return code 2.
    The backup operation has ended.
    2011-04-11 13:30:44
    Filling reply buffer.
        Have encountered error -24920:
            The backup tool failed with 2 as sum of exit codes. The database request failed with error -903.
        Constructed the following reply:
            ERR
            -24920,ERR_BACKUPOP: backup operation was unsuccessful
            The backup tool failed with 2 as sum of exit codes. The database request failed with error -903.
    Reply buffer filled.
    2011-04-11 13:30:44
    Cleaning up.
        Copying output of Backint for MaxDB to this file.
    Begin of output of Backint for MaxDB (E:\sapdb\data\wrk\KGP\backint.output)----
            Reading parameter file C:\Netbackup_Script\backint_parameter_daily.txt.
            Using D:\sapdb\KGP\db\bin\backint.exe as Backint for Oracle.
            Using C:\Netbackup_Script\nt_initKGPdaily.utl as parameterfile of Backint for Oracle.
            Using E:\sapdb\data\wrk\KGP\backinthistory.log as history file.
            Using E:\sapdb\data\wrk\KGP\backintoracle.in as input of Backint for Oracle.
            Using E:\sapdb\data\wrk\KGP\backintoracle.out as output of Backint for Oracle.
            Using E:\sapdb\data\wrk\KGP\backintoracle.err as error output of Backint for Oracle.
            Using staging area D:\sapdb\Stage1 with a size of 2147483648 bytes.
            Reading input file E:\sapdb\data\wrk\KGP\backint.input.
            Backing up pipe D:\sapdb\pipe2.
            Found 1 entry in the input file.
            Starting the backup.
            Starting pipe2file program(s).
            Waiting for creation of temporary files.
            1 temporary file is available for backup.
            Calling Backint for Oracle at 2011-04-11 13:30:43.
            Calling 'D:\sapdb\KGP\db\bin\backint.exe -u KGP -f backup -t file -p C:\Netbackup_Script\nt_initKGPdaily.utl -i E:\sapdb\data\wrk\KGP\backintoracle.in -c' .
            Backint for Oracle ended at 2011-04-11 13:30:43 with return code 2.
            Backint for Oracle output: Reading parameter file C:\Netbackup_Script\nt_initKGPdaily.utl.
            Backint for Oracle output: Using E:\sapdb\data\wrk\KGP\backint4oracle.in as input of Backint for Oracle.
            Backint for Oracle output: Using E:\sapdb\data\wrk\KGP\backint4oracle.out as output of Backint for Oracle.
            Backint for Oracle output: Using E:\sapdb\data\wrk\KGP\backint4oracle.err as error output of Backint for Oracle.
            Backint for Oracle output: Using staging area D:\sapdb\Stage1 with a size of 2147483648 bytes.
            Backint for Oracle output: Using E:\sapdb\data\wrk\KGP\backinthistory.log as history file.
            Backint for Oracle output: Using D:\sapdb\KGP\db\bin\backint.exe as Backint for Oracle.
            Backint for Oracle output:
            Backint for Oracle output: Reading input file E:\sapdb\data\wrk\KGP\backintoracle.in.
            Backint for Oracle output: Backing up file D:\sapdb\Stage1.0.
            Backint for Oracle output: Found 1 entry in the input file.
            Backint for Oracle output:
            Backint for Oracle output: Starting the backup.
            Backint for Oracle output: Starting pipe2file program(s).
            Backint for Oracle output:
            Backint for Oracle output: Calling Backint for Oracle at 2011-04-11 13:30:43.
            Backint for Oracle output: Calling 'D:\sapdb\KGP\db\bin\backint.exe -u KGP -f backup -t file -i E:\sapdb\data\wrk\KGP\backint4oracle.in -c' .
            Backint for Oracle output: Backint for Oracle ended at 2011-04-11 13:30:43 with return code 2.
            Backint for Oracle output: Backint for Oracle output: Reading parameter file .
            Backint for Oracle output: Backint for Oracle output:
            Backint for Oracle output: Backint for Oracle output:
            Backint for Oracle output: Backint for Oracle error output: No staging area is defined in the parameter file.
            Backint for Oracle output: Backint for Oracle error output: The path of Backint for Oracle is not defined in the parameter file.
            Backint for Oracle output: Backint for Oracle error output: The name of the history file is not defined in the parameter file.
            Backint for Oracle output: Backint for Oracle error output: The name of the input file of Backint for Oracle is not defined in the parameter file.
            Backint for Oracle output: Backint for Oracle error output: The name of the output file of Backint for Oracle is not defined in the parameter file.
            Backint for Oracle output: Backint for Oracle error output: The name of the error output file of Backint for Oracle is not defined in the parameter file.
            Backint for Oracle output: Backint for Oracle error output:
            Backint for Oracle output:
            Backint for Oracle output: Finished the backup unsuccessfully.
            Backint for Oracle output:
            Backint for Oracle output: #ERROR D:\sapdb\Stage1.0
            Backint for Oracle output:
            Backint for Oracle error output: Backint for Oracle was unsuccessful.
            Backint for Oracle error output:
            Finished the backup unsuccessfully.
            #ERROR D:\sapdb\pipe2
    End of output of Backint for MaxDB (E:\sapdb\data\wrk\KGP\backint.output)----
        Removed Backint for MaxDB's temporary output file 'E:\sapdb\data\wrk\KGP\backint.output'.
        Copying error output of Backint for MaxDB to this file.
    Begin of error output of Backint for MaxDB (E:\sapdb\data\wrk\KGP\backint.error)----
            Backint for Oracle was unsuccessful.
    End of error output of Backint for MaxDB (E:\sapdb\data\wrk\KGP\backint.error)----
        Removed Backint for MaxDB's temporary error output file 'E:\sapdb\data\wrk\KGP\backint.error'.
        Removed the Backint for MaxDB input file 'E:\sapdb\data\wrk\KGP\backint.input'.
    Have finished clean up successfully.

    >     Requesting 'SAVE DATA QUICK TO 'D:\sapdb\pipe2' PIPE BLOCKSIZE 8 NO CHECKPOINT MEDIANAME 'BACKDBFULL'' from db-kernel.The database is working on the request.
    This seems to be your problem, the pipe is wrongly defined. On Windows it looks like
    \\.\pipe1
    see
    http://msdn.microsoft.com/en-us/library/aa365783.aspx
    Markus

  • Change DB13 BRBACKUP parameter

    Hi everyone, I have an issue I hope somebody have the answer.
    Scenario Description
    My SAP platform is SAP ECC 5.0 / Windows 2003 SP2 IA64 / Oracle 10G + RAC
    I configured a new tape library for backups using HP Dataprotector 6.0
    We have some problems first with de DP SAP integration, but we solved them.
    So, first I succesfully run the backup from BRTOOLS using the command 
    F:\usr\sap\PRD\SYS\exe\run\brbackup.exe -u system/********* -p brtools_rman.sap -c -m all
    Then we run succesfully the backup from DP setting in the backup the user system
    and setting the integration specific option "-p brtools_rman.sap -c" .
    With this backups there is no problem, they ran succesfully and in TCODE DB12 are green.
    The PROBLEM
    Ok the issue is when trying to schedule a backup from TCODE DB13, in some point ther is the an error with the backint (end of message).
    The only difference is the way they start brtools
    Succesfull command:
    F:\usr\sap\PRD\SYS\exe\run\brbackup.exe -u system/********* -p brtools_rman.sap -c -m all
    Error command:
    brbackup -u / -jid PRTON20081125194451 -c force -t online -p brtools_rman.sap -w use_dbv -m all
    The question is how do I modify brbackup parameter in DB13, so I can set the user system?
    Thanks for your help.
    Franklin
    THE ERROR IN BRBACKUP LOG (backint error)
    BR0278I Command output of 'F:\usr\sap\PRD\SYS\exe\run\backint.exe -u PRD2 -f backup -i D:\ORACLE\PRD\sapbackup\.bdzimrol.lst -t file -c':                         
    [Normal] From: OB2BAR_BACKINT @ sapprddb02.plasticaucho.int "PRD2"  Time: 11/25/2008 8:32:54 PM                                                                     
    #Backint is started with the following parameters  F:\usr\sap\PRD\SYS\exe\run\backint.exe -u PRD2 -f backup -i D:\ORACLE\PRD\sapbackup\.bdzimrol.lst -t file -c.  
    ritical] From: OB2BAR_SAPBACK @ sapprddb02.plasticaucho.int "DEFAULT"  Time: 11/25/2008 8:32:54 PM                                                                  
    ailed to start backup of object PRD2.0. Error: Details unknown.                                                                               
    ?15# ##[139:234]# "##[7600]"                                                                               
    [Normal] From: OB2BAR_BACKINT @ sapprddb02.plasticaucho.int "PRD2"  Time: 11/25/2008 8:32:57 PM                                                                     
    #Backint exits with the code (2).                                                                               
    BR0280I BRBACKUP time stamp: 2008-11-25 20.32.57                                                                               
    BR0279E Return code from 'F:\usr\sap\PRD\SYS\exe\run\backint.exe -u PRD2 -f backup -i D:\ORACLE\PRD\sapbackup\.bdzimrol.lst -t file -c': 2                        
    BR0232E 0 of 1 file saved by backup utility                                                                               
    BR0280I BRBACKUP time stamp: 2008-11-25 20.32.57                                                                               
    BR0231E Backup utility call failed                                                                               
    BR0056I End of database backup: bdzimrol.pnr 2008-11-25 20.32.57                                                                               
    BR0280I BRBACKUP time stamp: 2008-11-25 0.32.58

    Hello,
    the SAP way of doing a backup is not to modify DB13, but to make brbackup -u / work.
    For a start, I would check permissions of brbackup program, according to SAP note 113747.
    hope this helps
    PS: sorry, SAP note 113747 is for Unix.
    Please check for similar approach in Windows!
    Edited by: Joe Bo. on Nov 26, 2008 10:53 AM

  • How lot take log backup using script in HANA

    We have SAP HANA SPS09.
    1) We are using script provided by SAP Note#1651055 to take the data backup.But it seems it is not taking log backup.HOw can we schedule logbackup ? or we have to use DBACOCKPIT or Studio only?
    2) My DB is log_mode OVERWRITE.I have taken backup using script.But when I tried to check the backup using below command
    hdbbackupdiag --check -f -d /mnt/resource/backup/xb8_bkp_19022015/ --logDirs  /mnt/resource/logbackup/,/usr/sap/XB8/HDB00/backup/log
    ERROR: [110081] Catalog backup log_backup_0_0_0_0 not found
    goazr1app904d:/usr/sap/XB8/HDB00>
    Is it like we have the DB in OVERWRITE mode thats why we are getting this error?Will my recovery work ?
    Thanks,
    Mofizur

    Did your issue got resolved?
    We are having same issue. We are on Rev 82 and using DD Boost EMC to take the backup using BACKINT.
    Though we are on Rev 82 I tried option provided by Pavan which didn't worked for me.
    hdbbackupdiag --check --useBackintForCatalog --backintDataParamFile /opt/ddbda/config/sap_hana_ddbda.utl -d /usr/sap/A0T/SYS/global/hdb/backint
    ERROR: [110081] Catalog backup log_backup_0_0_0_0 not found
    Regards,
    Nitin

  • Error BACKINT for Oracle Connection

    hi @ maxdb gurus...
    i have a problem backing up my maxdb 7.6.0.033 (serving for a mysap.erp2005 on aix 5.3) using the backint mechanism.
    -> backup media created: two pipes and one parallel medium containing these pipes
    -> bsi.env has been created
    -> backint4sapdb.sar contains
       4 staging areas each with 4096 MB
       files per backint call 2
    -> maxdb is about 57 gb perm. data area (and 6 gb temp.)
    i use the backup wizard (dbmgui) to invoke a complete data backup which starts (pipes are created in the file system) and runs until approx. 4 gb...then the backup terminates with error "-24920 backup operation was unsuccesful. The database request failed with error -8020"
    what might be the problem? are the staging areas too small? is says that when using only one stage area it must hold the complete database...can i then conclude that 4 staging areas must hold the database as well - meaning they must be around 15 gb each?
    GreetZ, AH

    yup...but that also means that the sum of the staging areas need as much space as the database ie. around 70 gigs netto! the staging files will be filled and thus grow until the defined size, meaning that the file system(s) need to be big enough!
    everything works fine until the stage files are filled (up to the defined size) and then stops...when i change the sizes of the staging areas i can reproduce the error!
    i compared the tsm implementation of that system with another system (live cache...kind of small regarding db size...) and found nothing serious...
    -> dbm.ebp (AIX 5.3, MaxDB 7.6.0.033, ERP2005, TSM 5.3.3.0)
    2006-11-09 13:56:50
    Using environment variable 'TEMP' with value '' as directory for temporary files and pipes.
    Using environment variable 'TMP' with value '' as directory for temporary files and pipes.
    Using connection to Backint for MaxDB Interface.
    2006-11-09 13:56:50
    Checking existence and configuration of Backint for MaxDB.
        Using configuration variable 'BSI_ENV' = '/sapdb/data/wrk/TDV/bsi.env' as path of the configuration file of Backint for MaxDB.
        Setting environment variable 'BSI_ENV' for the path of the configuration file of Backint for MaxDB from '/sapdba/data/wrk/TDV/bsi.env' to configuration value '/sapdb/data/wrk/TDV/bsi.env'.
        Reading the Backint for MaxDB configuration file '/sapdb/data/wrk/TDV/bsi.env'.
            The following line of the Backint for MaxDB configuration file does not start with a proper keyword and is ignored:
            The following line of the Backint for MaxDB configuration file does not start with a proper keyword and is ignored:
            The following line of the Backint for MaxDB configuration file does not start with a proper keyword and is ignored:
            The following line of the Backint for MaxDB configuration file does not start with a proper keyword and is ignored:
            Found keyword 'BACKINT' with value '/sapdb/TDV/db/bin/backint'.
            The following line of the Backint for MaxDB configuration file does not start with a proper keyword and is ignored:
            Found keyword 'INPUT' with value '/sapdb/TDV/backup/backint4sapdb.in'.
            Found keyword 'OUTPUT' with value '/sapdb/TDV/backup/backint4sapdb.out'.
            Found keyword 'ERROROUTPUT' with value '/sapdb/TDV/backup/backint4sapdb.err'.
            The following line of the Backint for MaxDB configuration file does not start with a proper keyword and is ignored:
            Found keyword 'PARAMETERFILE' with value '/sapdb/data/wrk/TDV/backint4sapdb.par'.
            Found keyword 'TIMEOUT_SUCCESS' with value '6000'.
            Found keyword 'TIMEOUT_FAILURE' with value '300'.
        Finished reading of the Backint for MaxDB configuration file.
        Using '/sapdb/TDV/db/bin/backint' as Backint for MaxDB program.
        Using '/sapdb/TDV/backup/backint4sapdb.in' as input file for Backint for MaxDB.
        Using '/sapdb/TDV/backup/backint4sapdb.out' as output file for Backint for MaxDB.
        Using '/sapdb/TDV/backup/backint4sapdb.err' as error output file for Backint for MaxDB.
        Using '/sapdb/data/wrk/TDV/backint4sapdb.par' as parameter file for Backint for MaxDB.
        Using '6000' seconds as timeout for Backint for MaxDB in the case of success.
        Using '300' seconds as timeout for Backint for MaxDB in the case of failure.
        Using '/sapdb/data/wrk/TDV/dbm.knl' as backup history of a database to migrate.
        Using '/sapdb/data/wrk/TDV/dbm.ebf' as external backup history of a database to migrate.
        Checking availability of backups using backint's inquire function.
    Check passed successful.
    2006-11-09 13:56:50
    Checking medium.
    Check passed successfully.
    2006-11-09 13:56:50
    Preparing backup.
        Setting environment variable 'BI_CALLER' to value 'DBMSRV'.
        Setting environment variable 'BI_REQUEST' to value 'NEW'.
        Setting environment variable 'BI_BACKUP' to value 'FULL'.
        Constructed Backint for MaxDB call '/sapdb/TDV/db/bin/backint -u TDV -f backup -t file -p /sapdb/data/wrk/TDV/backint4sapdb.par -i /sapdb/TDV/backup/backint4sapdb.in -c'.
        Created temporary file '/sapdb/TDV/backup/backint4sapdb.out' as output for Backint for MaxDB.
        Created temporary file '/sapdb/TDV/backup/backint4sapdb.err' as error output for Backint for MaxDB.
        Writing '/sapdb/TDV/backup/back-tdv-data-m10.pipe #PIPE' to the input file.
        Writing '/sapdb/TDV/backup/back-tdv-data-m11.pipe #PIPE' to the input file.
    Prepare passed successfully.
    2006-11-09 13:56:51
    Creating pipes for data transfer.
        Creating pipe '/sapdb/TDV/backup/back-tdv-data-m10.pipe' ... Done.
        Creating pipe '/sapdb/TDV/backup/back-tdv-data-m11.pipe' ... Done.
    All data transfer pipes have been created.
    2006-11-09 13:56:51
    Starting database action for the backup.
        Requesting 'SAVE DATA QUICK TO '/sapdb/TDV/backup/back-tdv-data-m10.pipe' PIPE,'/sapdb/TDV/backup/back-tdv-data-m11.pipe' PIPE BLOCKSIZE 8 NO CHECKPOINT MEDIANAME 'BACK-TDV-DATA-G1'' from db-kernel.
    The database is working on the request.
    2006-11-09 13:56:51
    Waiting until database has prepared the backup.
        Asking for state of database.
        2006-11-09 13:56:51 Database is still preparing the backup.
        Waiting 1 second ... Done.
        Asking for state of database.
        2006-11-09 13:56:52 Database is still preparing the backup.
        Waiting 2 seconds ... Done.
        Asking for state of database.
        2006-11-09 13:56:54 Database is still preparing the backup.
        Waiting 3 seconds ... Done.
        Asking for state of database.
        2006-11-09 13:56:57 Database is still preparing the backup.
        Waiting 4 seconds ... Done.
        Asking for state of database.
        2006-11-09 13:57:01 Database is still preparing the backup.
        Waiting 5 seconds ... Done.
        Asking for state of database.
        2006-11-09 13:57:06 Database has finished preparation of the backup.
    The database has prepared the backup successfully.
    2006-11-09 13:57:06
    Starting Backint for MaxDB.
        Starting Backint for MaxDB process '/sapdb/TDV/db/bin/backint -u TDV -f backup -t file -p /sapdb/data/wrk/TDV/backint4sapdb.par -i /sapdb/TDV/backup/backint4sapdb.in -c >>/sapdb/TDV/backup/backint4sapdb.out 2>>/sapdb/TDV/backup/backint4sapdb.err'.
        Process was started successfully.
    Backint for MaxDB has been started successfully.
    2006-11-09 13:57:06
    Waiting for end of the backup operation.
        2006-11-09 13:57:06 The backup tool is running.
        2006-11-09 13:57:06 The database is working on the request.
        2006-11-09 13:57:11 The backup tool is running.
        2006-11-09 13:57:11 The database is working on the request.
        2006-11-09 13:57:21 The backup tool is running.
        2006-11-09 13:57:21 The database is working on the request.
        2006-11-09 13:57:36 The backup tool is running.
        2006-11-09 13:57:36 The database is working on the request.
        2006-11-09 13:57:56 The backup tool is running.
        2006-11-09 13:57:56 The database is working on the request.
        2006-11-09 13:58:21 The backup tool is running.
        2006-11-09 13:58:21 The database is working on the request.
        2006-11-09 13:58:51 The backup tool is running.
        2006-11-09 13:58:51 The database is working on the request.
        2006-11-09 13:59:21 The database has finished work on the request.
        Receiving a reply from the database kernel.
        Got the following reply from db-kernel:
            SQL-Code              :-8020
            Date                  :20061109
            Time                  :00135703
            Database              :TDV
            Server                :r4335
            KernelVersion         :Kernel    7.6.00   Build 033-123-130-873
            PagesTransfered       :377688
            PagesLeft             :6903331
            MediaName             :BACK-TDV-DATA-G1
            Location              :/sapdb/TDV/backup/back-tdv-data-m10.pipe
            Errortext             :end of file
            Label                 :DAT_000000017
            IsConsistent          :true
            FirstLogPageNo        :247812
            DBStamp1Date          :20061109
            DBStamp1Time          :00135651
            BDPageCount           :7280971
            DevicesUsed           :2
            DatabaseID            :r4335:TDV_20061109_135703
            Max Used Data Page    :0
            Converter Page Count  :5201
        2006-11-09 13:59:21 The backup tool is running.
        2006-11-09 13:59:22 The backup tool process has finished work with return code 2.
        2006-11-09 13:59:22 The backup tool is not running.
    The backup operation has ended.
    2006-11-09 13:59:22
    Filling reply buffer.
        Have encountered error -24920:
            The backup tool failed with 2 as sum of exit codes. The database request failed with error -8020.
        Constructed the following reply:
            ERR
            -24920,ERR_BACKUPOP: backup operation was unsuccessful
            The backup tool failed with 2 as sum of exit codes. The database request failed with error -8020.
    Reply buffer filled.
    2006-11-09 13:59:22
    Cleaning up.
        Removing data transfer pipes.
            Removing data transfer pipe /sapdb/TDV/backup/back-tdv-data-m11.pipe ... Done.
            Removing data transfer pipe /sapdb/TDV/backup/back-tdv-data-m10.pipe ... Done.
        Removed data transfer pipes successfully.
        Copying output of Backint for MaxDB to this file.
        ---------- Begin of output of Backint for MaxDB (/sapdb/TDV/backup/backint4sapdb.out)----------
            Reading parameter file /sapdb/data/wrk/TDV/backint4sapdb.par.
            Using staging area /sapdb/TDV/backup/stage1 with a size of 1585446912 bytes.
            Using staging area /sapdb/TDV/backup/stage2 with a size of 1585446912 bytes.
            Using 1 file per Backint for Oracle call.
            Using /sapdb/TDV/dbs/backint as Backint for Oracle.
            Using /sapdb/TDV/dbs/initTDV.utl as parameterfile of Backint for Oracle.
            Using /sapdb/data/wrk/TDV/backint4oracle.his as history file.
            Using /sapdb/TDV/backup/backint4oracle.in as input of Backint for Oracle.
            Using /sapdb/TDV/backup/backint4oracle.out as output of Backint for Oracle.
            Using /sapdb/TDV/backup/backint4oracle.err as error output of Backint for Oracle.
            Using a maximal delay for a Backint for Oracle call of 60 seconds.
            Reading input file /sapdb/TDV/backup/backint4sapdb.in.
            Backing up pipe /sapdb/TDV/backup/back-tdv-data-m10.pipe.
            Backing up pipe /sapdb/TDV/backup/back-tdv-data-m11.pipe.
            Found 2 entries in the input file.
            Starting the backup.
            Starting pipe2file program(s).
            Waiting for creation of temporary files.
            1 temporary file is available for backup.
            Calling Backint for Oracle at 2006-11-09 13:59:20.
            Calling '/sapdb/TDV/dbs/backint -u TDV -f backup -t file -p /sapdb/TDV/dbs/initTDV.utl -i /sapdb/TDV/backup/backint4oracle.in -c' .
            Backint for Oracle ended at 2006-11-09 13:59:20 with return code 2.
            Backint for Oracle output:
            Backint for Oracle output:                          Data Protection for mySAP(R)
            Backint for Oracle output:
            Backint for Oracle output:              Interface between BR*Tools and Tivoli Storage Manager
            Backint for Oracle output:              - Version 5, Release 3, Modification 2.0  for AIX LF 64-bit -
            Backint for Oracle output:                    Build: 275  compiled on Nov 20 2005
            Backint for Oracle output:         (c) Copyright IBM Corporation, 1996, 2005, All Rights Reserved.
            Backint for Oracle output:
            Backint for Oracle output: BKI2027I: Using TSM-API version 5.3.3.0 (compiled with 5.3.0.0).
            Backint for Oracle output: BKI2000I: Successfully connected to ProLE on port tdpr3ora64.
            Backint for Oracle output: BKI0005I: Start of program at: Thu Nov  9 13:59:20 MEZ 2006 .
            Backint for Oracle output: BKI5014E: Tivoli Storage Manager Error:
            Backint for Oracle output: ANS1035S (RC406)  Options file '*' could not be found.
            Backint for Oracle output:
            Backint for Oracle output: BKI0020I: End of program at: Thu Nov  9 13:59:20 MEZ 2006 .
            Backint for Oracle output: BKI0021I: Elapsed time: 00 sec .
            Backint for Oracle output: BKI0024I: Return code is: 2.
            Backint for Oracle output:
            Backint for Oracle error output:
            Finished the backup unsuccessfully.
            #ERROR /sapdb/TDV/backup/back-tdv-data-m10.pipe
            #ERROR /sapdb/TDV/backup/back-tdv-data-m11.pipe
        ---------- End of output of Backint for MaxDB (/sapdb/TDV/backup/backint4sapdb.out)----------
        Removed Backint for MaxDB's temporary output file '/sapdb/TDV/backup/backint4sapdb.out'.
        Copying error output of Backint for MaxDB to this file.
        ---------- Begin of error output of Backint for MaxDB (/sapdb/TDV/backup/backint4sapdb.err)----------
            Backint for Oracle was unsuccessful.
        ---------- End of error output of Backint for MaxDB (/sapdb/TDV/backup/backint4sapdb.err)----------
        Removed Backint for MaxDB's temporary error output file '/sapdb/TDV/backup/backint4sapdb.err'.
        Removed the Backint for MaxDB input file '/sapdb/TDV/backup/backint4sapdb.in'.
    Have finished clean up successfully.
    i invoke the backup through dbmgui, not dbmcli!
    any clues? thx in advance!
    GreetZ, AH

  • Backint failed "ERROR: unable to find file "

    Hello
    I try to backup Oracle database 10.2 with netbackup tools on Redhat 2.6.18-53
    I got errror:
    BR0231E Backup utility call failed
    ERROR: unable to find file /oracle/BWP/sapdata4
    Can u help me
    Regards
    Fethi

    This is the backup logfile:
    BR0477I Oracle pfile /oracle/BWP/102_64/dbs/initBWP.ora created from spfile /oracle/BWP/102_64/dbs/spfileBWP.ora
    BR0101I Parameters
    Name                           Value
    oracle_sid                     BWP
    oracle_home                    /oracle/BWP/102_64
    oracle_profile                 /oracle/BWP/102_64/dbs/initBWP.ora
    sapdata_home                   /oracle/BWP
    sap_profile                    /oracle/BWP/102_64/dbs/initBWP_sapdata_offline.sap
    backup_mode                    ALL
    backup_type                    offline
    backup_dev_type                util_file
    util_par_file                  /oracle/BWP/102_64/dbs/initBWP_sapdata_offline.utl
    system_info                    orabwp/orabwp hpbwpdb2 Linux 2.6.18-53.1.19.el5 #1 SMP Tue Apr 22 03:01:10 EDT 2008 x86_64
    oracle_info                    BWP 10.2.0.2.0 8192 30 88160883 hpbwpdb2 WE8DEC UTF8
    sap_info                       700 SAPSR3 BWP S1329078236 R3_ORA 0020159289
    make_info                      linuxx86_64 OCI_102 Feb  8 2008
    command_line                   brbackup -c force -p initBWP_sapdata_offline.sap
    BR0116I ARCHIVE LOG LIST before backup for database instance BWP
    Parameter                      Value
    Database log mode              No Archive Mode
    Automatic archival             Disabled
    Archive destination            /oracle/BWP/oraarch/BWParch
    Archive format                 %t_%s_%r.dbf
    Oldest online log sequence     27
    Next log sequence to archive   30
    Current log sequence           30               SCN: 88160883
    Database block size            8192             Thread: 1
    Current system change number   88168768         ResetId: 655409152
    BR0118I Tablespaces and data files
    Tablespace     TS-Status  F-Status  File                                                       Size   Id.     Device  Link    Type       MaxSize     IncrSize  BlkSize
    PSAPBWP        ONLINE*    ONLINE+   /oracle/BWP/sapdata4/BWM.data1                      17498636288    4       64785  NOLINK  FILE   34359721984    104857600     8192
    PSAPBWP        ONLINE*    ONLINE+   /oracle/BWP/sapdata4/BWM.data2                      16450060288    5       64785  NOLINK  FILE   34359721984    104857600     8192
    PSAPBWP        ONLINE*    ONLINE+   /oracle/BWP/sapdata4/BWM.data3                      15820914688    6       64785  NOLINK  FILE   34359721984    104857600     8192
    PSAPBWP700     ONLINE*    ONLINE+   /oracle/BWP/sapdata2/BWM700.data1                   15128862720   11       64784  NOLINK  FILE   34359721984    104857600     8192
    PSAPBWP700     ONLINE*    ONLINE+   /oracle/BWP/sapdata4/BWM700.data2                    4132511744   12       64785  NOLINK  FILE   34359721984         8192     8192
    PSAPBWPDIM     ONLINE*    ONLINE+   /oracle/BWP/sapdata1/BWMdim.data1                    4202700800    7       64770  NOLINK  FILE   10485760000     20971520     8192
    PSAPBWPFACT    ONLINE*    ONLINE+   /oracle/BWP/sapdata1/BWMfact.data1                   6719283200    8       64770  NOLINK  FILE   34359721984     20971520     8192
    PSAPBWPODS     ONLINE*    ONLINE+   /oracle/BWP/sapdata2/BWMods.data1                   19868426240    9       64784  NOLINK  FILE   34359721984     20971520     8192
    PSAPBWPUSR     ONLINE*    ONLINE+   /oracle/BWP/sapdata1/BWMusr.data1                     239083520   10       64770  NOLINK  FILE   10485760000     20971520     8192
    PSAPSR3USR     ONLINE+    ONLINE+   /oracle/BWP/sapdata4/sr3usr_1/sr3usr.data1            134225920   20       64785  NOLINK  FILE   10485760000     20971520     8192
    PSAPTEMP       ONLINE#    ONLINE+   /oracle/BWP/sapdata1/temp_1/temp.data1              10485768192   -1       64770  NOLINK  FILE   34358689792     20971520     8192
    PSAPUNDO       ONLINE-    ONLINE+   /oracle/BWP/sapdata1/undo_1/undo.data1               1073750016    2       64770  NOLINK  FILE   34359721984     20971520     8192
    SYSAUX         ONLINE*    ONLINE+   /oracle/BWP/sapdata1/sysaux_1/sysaux.data1            671096832    3       64770  NOLINK  FILE   10485760000     20971520     8192
    SYSTEM         ONLINE*    SYSTEM+   /oracle/BWP/sapdata1/system_1/system.data1            838868992    1       64770  NOLINK  FILE   10485760000     20971520     8192
    BR0119I Redo log files
    File                                                Size  Group     Device  Status    Link    Type
    /oracle/BWP/origlogA/log_g11m1.dbf              52429312    1        64774  INUSE     NOLINK  FILE
    /oracle/BWP/mirrlogA/log_g11m2.dbf              52429312    1        64776  INUSE     NOLINK  FILE
    /oracle/BWP/origlogB/log_g12m1.dbf              52429312    2        64775  INUSE     NOLINK  FILE
    /oracle/BWP/mirrlogB/log_g12m2.dbf              52429312    2        64777  INUSE     NOLINK  FILE
    /oracle/BWP/origlogA/log_g13m1.dbf              52429312    3        64774  INUSE     NOLINK  FILE
    /oracle/BWP/mirrlogA/log_g13m2.dbf              52429312    3        64776  INUSE     NOLINK  FILE
    /oracle/BWP/origlogB/log_g14m1.dbf              52429312    4        64775  INUSE     NOLINK  FILE
    /oracle/BWP/mirrlogB/log_g14m2.dbf              52429312    4        64777  INUSE     NOLINK  FILE
    BR0120I Control files
    File                                                Size   Id.      Device  Link    Type
    /oracle/BWP/origlogA/cntrl/cntlrBWP.dbf         34979840    0        64774  NOLINK  FILE
    /oracle/BWP/origlogB/cntrl/cntrlBWP.dbf         34979840    0        64775  NOLINK  FILE
    /oracle/BWP/sapdata1/cntrl/cntrlBWP.dbf         34979840    0        64770  NOLINK  FILE
    BR0616I Tablespaces in table TSORA for SAP owner SAPSR3:
    PSAPBWP, PSAPBWP700, PSAPBWPDIM, PSAPBWPFACT, PSAPBWPODS,
    PSAPBWPUSR
    BR0280I BRBACKUP time stamp: 2008-05-23 15.59.26
    BR0057I Backup of database: BWP
    BR0058I BRBACKUP action ID: bdxzgdlt
    BR0059I BRBACKUP function ID: aff
    BR0110I Backup mode: ALL
    BR0077I Database files for backup:
    /oracle/BWP/origlogA/log_g11m1.dbf
    /oracle/BWP/origlogB/log_g12m1.dbf
    /oracle/BWP/origlogA/log_g13m1.dbf
    /oracle/BWP/origlogB/log_g14m1.dbf
    /oracle/BWP/origlogA/cntrl/cntlrBWP.dbf
    BR0061I 19 files found for backup, total size 108250.510 MB
    BR0143I Backup type: offline
    BR0130I Backup device type: util_file
    BR0109I Files will be saved by backup utility
    BR0134I Unattended mode with 'force' active - no operator confirmation allowed
    BR0280I BRBACKUP time stamp: 2008-05-23 15.59.26
    BR0307I Shutting down database instance BWP ...
    BR0280I BRBACKUP time stamp: 2008-05-23 15.59.33
    BR0308I Shutdown of database instance BWP successful
    BR0280I BRBACKUP time stamp: 2008-05-23 15.59.33
    BR0229I Calling backup utility with function 'backup'...
    BR0278I Command output of '/usr/sap/BWP/SYS/exe/run/backint -u BWP -f backup -i /oracle/BWP/sapbackup/.bdxzgdlt.lst -t file -p /oracle/BWP/102_64/dbs/initBWP_sapdata_offline.utl -c':
    WARNING: unknown parameter: print_log_flag 1
    WARNING: sort_backup_type not specified in .utl file
    WARNING: default sort_backup_type to <size> for restore
    Program:                /usr/sap/BWP/SYS/exe/run/backint 5.1
    Input File:             /oracle/BWP/sapbackup/.bdxzgdlt.lst
    Profile:                /oracle/BWP/102_64/dbs/initBWP_sapdata_offline.utl
    Function:               BACKUP
    Backup Type:            BACKUP_FILE
    ERROR: unable to find file /oracle/BWP/sapdata4/BWM.data1
    ERROR: unable to find file /oracle/BWP/sapdata4/BWM.data2
    ERROR: unable to find file /oracle/BWP/sapdata4/BWM.data3
    ERROR: unable to find file /oracle/BWP/sapdata2/BWM700.data1
    ERROR: unable to find file /oracle/BWP/sapdata4/BWM700.data2
    ERROR: unable to find file /oracle/BWP/sapdata1/BWMdim.data1
    ERROR: unable to find file /oracle/BWP/sapdata1/BWMfact.data1
    ERROR: unable to find file /oracle/BWP/sapdata2/BWMods.data1
    ERROR: unable to find file /oracle/BWP/sapdata1/temp_1/temp.data1
    BR0280I BRBACKUP time stamp: 2008-05-23 15.59.33
    BR0279E Return code from '/usr/sap/BWP/SYS/exe/run/backint -u BWP -f backup -i /oracle/BWP/sapbackup/.bdxzgdlt.lst -t file -p /oracle/BWP/102_64/dbs/initBWP_sapdata_offline.utl -c': 2
    BR0232E 0 of 19 files saved by backup utility
    BR0280I BRBACKUP time stamp: 2008-05-23 15.59.33
    BR0231E Backup utility call failed
    BR0280I BRBACKUP time stamp: 2008-05-23 15.59.35
    BR0304I Starting and opening database instance BWP ...
    BR0280I BRBACKUP time stamp: 2008-05-23 15.59.42
    BR0305I Start and open of database instance BWP successful
    BR0056I End of database backup: bdxzgdlt.aff 2008-05-23 15.59.33
    Thank you
    Regards

  • BKI0062E: The input file /oracle/SID/sapbackup/.file.lst is not valid.

    Hi all,
       It has the following platform: SAP ECC6 in AIX 6.1 with Oracle Database
    My question is: When I run a online backup from DB13 with util_file I have this error message :
    BKI0062E: The input file /oracle/SID/sapbackup/.file.lst is not valid.
    Knowing when I launch from the standard profile on Disk initSID.sap it works without problem
    When we test manually with oraSID it works but by SIDadm its not work
    Then you can mention or in configuration files BACKINT both users oraSID & SIDadm have rights to use
    Many Thanks
    AT

    > # ls -l /sapmnt/X21/exe/br*
    > -rwxrwxr-x    1 oraX21   dba         5002624 Feb 06 2008  /sapmnt/X21/exe/brarchive
    > -rwsrwxr-x    1 oraX21   dba         5129705 Feb 06 2008  /sapmnt/X21/exe/brbackup
    > -rwsrwxr-x    1 oraX21   dba         6659409 Feb 06 2008  /sapmnt/X21/exe/brconnect
    > -rwxrwxr-x    1 oraX21   dba         5594679 Feb 06 2008  /sapmnt/X21/exe/brrecover
    > -rwxrwxr-x    1 oraX21   dba         2100833 Feb 06 2008  /sapmnt/X21/exe/brrestore
    > -rwxrwxr-x    1 oraX21   dba         6882272 Feb 06 2008  /sapmnt/X21/exe/brspace
    > -rwsrwxr-x    1 oraX21   dba         2729734 Feb 06 2008  /sapmnt/X21/exe/brtools
    As you see - your br*tools are more than two years old, many many errors have been fixed since. I would install the latest tools and try if the error is still there. You can even do that when the system is running.
    Markus

  • Error in installation of Java EE 5 Application Server

    I am getting error in the installation of "Java EE 5 Application Server". When I checked the log file it is showing as follows:
    (Oct 9, 2006 9:55:21 AM), Install, com.sap.installshield.maxdb.maxdb_call_sdbinst, err, An error occurred and product installation failed.  Look at the log file C:\sapdb\JP1\log.txt for details.
    (Oct 9, 2006 9:55:21 AM), Install, com.sap.installshield.maxdb.maxdb_call_sdbinst, err, ProductException: (error code = 601; message="Mon Oct 09 09:55:20 IST 2006 An Error happened during the Change of the MaxDB Database passwords. Check end of Logfile C:/DOCUME1/162492/LOCALS1/Temp/MaxDBSAPNWPREV.log")
    STACK_TRACE: 22
    ProductException: (error code = 601; message="Mon Oct 09 09:55:20 IST 2006 An Error happened during the Change of the MaxDB Database passwords. Check end of Logfile C:/DOCUME1/162492/LOCALS1/Temp/MaxDBSAPNWPREV.log")
         at com.sap.installshield.maxdb.maxdb_call_sdbinst.install(maxdb_call_sdbinst.java:247)
         at com.installshield.product.service.product.PureJavaProductServiceImpl.installProductAction(Unknown Source)
         at com.installshield.product.service.product.PureJavaProductServiceImpl$InstallProduct.getResultForProductAction(Unknown Source)
         at com.installshield.product.service.product.InstallableObjectVisitor.visitComponent(Unknown Source)
         at com.installshield.product.service.product.InstallableObjectVisitor.visitInstallableComponents(Unknown Source)
         at com.installshield.product.service.product.InstallableObjectVisitor.visitProductBeans(Unknown Source)
         at com.installshield.product.service.product.PureJavaProductServiceImpl$InstallProduct.install(Unknown Source)
         at com.installshield.product.service.product.PureJavaProductServiceImpl.installProduct(Unknown Source)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
         at java.lang.reflect.Method.invoke(Unknown Source)
         at com.installshield.wizard.service.LocalImplementorProxy.invoke(Unknown Source)
         at com.installshield.wizard.service.AbstractService.invokeImpl(Unknown Source)
         at com.installshield.product.service.product.GenericProductService.installProduct(Unknown Source)
         at com.installshield.product.service.product.PureJavaProductServiceImpl.installAssembly(Unknown Source)
         at com.installshield.product.service.product.PureJavaProductServiceImpl.access$900(Unknown Source)
         at com.installshield.product.service.product.PureJavaProductServiceImpl$Installer.execute(Unknown Source)
         at com.installshield.wizard.service.AsynchronousOperation.run(Unknown Source)
         at java.lang.Thread.run(Unknown Source)
    When I checked C:/DOCUME1/162492/LOCALS1/Temp/MaxDBSAPNWPREV.log file it is showing as follows :
    Mon Oct 09 09:51:52 IST 2006 MaxDB: Start SoftwareCheck
    Mon Oct 09 09:51:52 IST 2006 MaxDB: IndepProgPath:
    Mon Oct 09 09:51:52 IST 2006 MaxDB: IndepDataPath:
    Mon Oct 09 09:51:52 IST 2006 MaxDB: Software doesn't exist, Variable MAXDB_SOFTW_EXISTS set to NO
    Mon Oct 09 09:51:52 IST 2006 MaxDB: end of Check Section!
    Mon Oct 09 09:51:52 IST 2006 MaxDB: Password confirmation: 3-9 characters necessary
    Mon Oct 09 09:52:15 IST 2006 MaxDB: Start of Extracting Software and Backup.
    Mon Oct 09 09:52:45 IST 2006 MaxDB: End of Extracting Software and Backup.
    Mon Oct 09 09:52:45 IST 2006 MaxDB: Start of CallSdbinst
    Mon Oct 09 09:52:45 IST 2006 MaxDB: IndepProgPath = C:/sapdb/programs
    Mon Oct 09 09:52:45 IST 2006 MaxDB: inst_type = :restore:
    Mon Oct 09 09:52:45 IST 2006 MaxDB: Calling sdbinst with template option sapmds
    Mon Oct 09 09:52:45 IST 2006 MaxDB SID: JP1
    Mon Oct 09 09:52:45 IST 2006 MaxDB drive: C:\
    Mon Oct 09 09:52:45 IST 2006 MaxDB softwarepath: C:/sapdb
    Mon Oct 09 09:52:45 IST 2006 MaxDB Software location: C:/sapdb/JP1/_tempLocation
    Mon Oct 09 09:52:45 IST 2006 MaxDB backup_loc: C:/sapdb/JP1/_tempLocation/load_datasave
    Mon Oct 09 09:52:45 IST 2006 MaxDB program: C:/sapdb/JP1/_tempLocation/sdbinst.exe
    Mon Oct 09 09:52:45 IST 2006 MaxDB paramfile: C:/sapdb/JP1/_tempLocation/sapmds.txt
    Mon Oct 09 09:52:45 IST 2006MaxDB found sdbinst
    Mon Oct 09 09:52:45 IST 2006 MaxDB: Calling: C:/sapdb/JP1/_tempLocation/sdbinst.exe -t sapmds -f "C:/sapdb/JP1/_tempLocation/sapmds.txt" -p DBNAME=JP1 -p SOFTWAREPATH="C:/sapdb" -p INSTANCEBACKUP="C:/sapdb/JP1/_tempLocation/load_datasave"
    Mon Oct 09 09:52:50 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:52:51 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:52:51 IST 2006 MaxDB sdbinst:      Installation of MaxDB Software
    Mon Oct 09 09:52:51 IST 2006 MaxDB sdbinst:      *******************************
    Mon Oct 09 09:52:51 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:52:51 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:52:51 IST 2006 MaxDB sdbinst: starting installation Mo, Oct 09, 2006 at 09:52:50
    Mon Oct 09 09:52:51 IST 2006 MaxDB sdbinst: operating system: Windows I386 NT 5.1 Service Pack 2
    Mon Oct 09 09:52:51 IST 2006 MaxDB sdbinst: callers working directory: C:/Documents and Settings/162492/Desktop/SAPNWAS_JAVAEE5_T06
    Mon Oct 09 09:52:51 IST 2006 MaxDB sdbinst: installer directory: C:/sapdb/JP1/_tempLocation
    Mon Oct 09 09:52:52 IST 2006 MaxDB sdbinst: archive directory: C:/sapdb/JP1/_tempLocation
    Mon Oct 09 09:52:52 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:52:52 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:52:53 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:52:53 IST 2006 MaxDB sdbinst: starting preparing phase of package Base 7.6.00.33 32 bit
    Mon Oct 09 09:52:53 IST 2006 MaxDB sdbinst: -
    Mon Oct 09 09:52:54 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:52:54 IST 2006 MaxDB sdbinst: checking interferences to other packages... ok
    Mon Oct 09 09:52:54 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:52:54 IST 2006 MaxDB sdbinst: collecting data finished:
    Mon Oct 09 09:52:54 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:52:54 IST 2006 MaxDB sdbinst: independent data path: c:/sapdb/data
    Mon Oct 09 09:52:54 IST 2006 MaxDB sdbinst: independent program path: c:/sapdb/programs
    Mon Oct 09 09:52:54 IST 2006 MaxDB sdbinst: start extraction test run of "C:/sapdb/JP1/_tempLocation/SDBBAS.TGZ"
    Mon Oct 09 09:52:55 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:52:55 IST 2006 MaxDB sdbinst: package Base successfully checked
    Mon Oct 09 09:52:55 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:52:55 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:52:55 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:52:55 IST 2006 MaxDB sdbinst: starting preparing phase of package SAP Utilities 7.6.00.33 32 bit
    Mon Oct 09 09:52:55 IST 2006 MaxDB sdbinst: -
    Mon Oct 09 09:52:55 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:52:55 IST 2006 MaxDB sdbinst: checking interferences to other packages... ok
    Mon Oct 09 09:52:56 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:52:56 IST 2006 MaxDB sdbinst: collecting data finished:
    Mon Oct 09 09:52:56 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:52:56 IST 2006 MaxDB sdbinst: : c:/sapdb/data
    Mon Oct 09 09:52:56 IST 2006 MaxDB sdbinst: independent program path: c:/sapdb/programs
    Mon Oct 09 09:52:56 IST 2006 MaxDB sdbinst: start extraction test run of "C:/sapdb/JP1/_tempLocation/SAPUTL.TGZ"
    Mon Oct 09 09:52:56 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:52:56 IST 2006 MaxDB sdbinst: package SAP Utilities successfully checked
    Mon Oct 09 09:52:56 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:52:57 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:52:57 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:52:57 IST 2006 MaxDB sdbinst: starting preparing phase of package JDBC 7.6.00.30
    Mon Oct 09 09:52:57 IST 2006 MaxDB sdbinst: -
    Mon Oct 09 09:52:57 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:52:57 IST 2006 MaxDB sdbinst: checking interferences to other packages... ok
    Mon Oct 09 09:52:57 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:52:57 IST 2006 MaxDB sdbinst: collecting data finished:
    Mon Oct 09 09:52:57 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:52:58 IST 2006 MaxDB sdbinst: java driver path: c:/sapdb/programs
    Mon Oct 09 09:52:58 IST 2006 MaxDB sdbinst: start extraction test run of "C:/sapdb/JP1/_tempLocation/SDBJDBC.TGZ"
    Mon Oct 09 09:52:58 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:52:58 IST 2006 MaxDB sdbinst: package JDBC successfully checked
    Mon Oct 09 09:52:58 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:52:58 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:52:58 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:52:58 IST 2006 MaxDB sdbinst: starting preparing phase of package Server Utilities 7.6.00.33 32 bit
    Mon Oct 09 09:52:58 IST 2006 MaxDB sdbinst: -
    Mon Oct 09 09:52:58 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:52:59 IST 2006 MaxDB sdbinst: checking interferences to other packages... ok
    Mon Oct 09 09:52:59 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:52:59 IST 2006 MaxDB sdbinst: collecting data finished:
    Mon Oct 09 09:52:59 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:52:59 IST 2006 MaxDB sdbinst: independent program path: c:/sapdb/programs
    Mon Oct 09 09:52:59 IST 2006 MaxDB sdbinst: start extraction test run of "C:/sapdb/JP1/_tempLocation/SDBUTL.TGZ"
    Mon Oct 09 09:52:59 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:52:59 IST 2006 MaxDB sdbinst: package Server Utilities successfully checked
    Mon Oct 09 09:52:59 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:53:00 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:53:00 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:53:00 IST 2006 MaxDB sdbinst: starting preparing phase of package Database Kernel 7.6.00.33 32 bit
    Mon Oct 09 09:53:00 IST 2006 MaxDB sdbinst: -
    Mon Oct 09 09:53:00 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:53:00 IST 2006 MaxDB sdbinst: checking interferences to other packages... ok
    Mon Oct 09 09:53:00 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:53:00 IST 2006 MaxDB sdbinst: collecting data finished:
    Mon Oct 09 09:53:00 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:53:00 IST 2006 MaxDB sdbinst: dependent path: c:/sapdb/jp1/db
    Mon Oct 09 09:53:01 IST 2006 MaxDB sdbinst: start extraction test run of "C:/sapdb/JP1/_tempLocation/SDBKRN.TGZ"
    Mon Oct 09 09:53:01 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:53:01 IST 2006 MaxDB sdbinst: package Database Kernel successfully checked
    Mon Oct 09 09:53:01 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:53:01 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:53:01 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:53:01 IST 2006 MaxDB sdbinst: starting preparing phase of package Messages MSG 0.3951
    Mon Oct 09 09:53:01 IST 2006 MaxDB sdbinst: -
    Mon Oct 09 09:53:01 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:53:01 IST 2006 MaxDB sdbinst: checking interferences to other packages... ok
    Mon Oct 09 09:53:02 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:53:02 IST 2006 MaxDB sdbinst: collecting data finished:
    Mon Oct 09 09:53:02 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:53:02 IST 2006 MaxDB sdbinst: messages path: c:/sapdb/programs
    Mon Oct 09 09:53:02 IST 2006 MaxDB sdbinst: start extraction test run of "C:/sapdb/JP1/_tempLocation/SDBMSG.TGZ"
    Mon Oct 09 09:53:02 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:53:02 IST 2006 MaxDB sdbinst: package Messages successfully checked
    Mon Oct 09 09:53:02 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:53:02 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:53:02 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:53:03 IST 2006 MaxDB sdbinst: starting preparing phase of package ODBC 7.6.00.33 32 bit
    Mon Oct 09 09:53:03 IST 2006 MaxDB sdbinst: -
    Mon Oct 09 09:53:03 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:53:03 IST 2006 MaxDB sdbinst: checking interferences to other packages... ok
    Mon Oct 09 09:53:03 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:53:03 IST 2006 MaxDB sdbinst: collecting data finished:
    Mon Oct 09 09:53:03 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:53:03 IST 2006 MaxDB sdbinst: odbc path: c:/sapdb/programs
    Mon Oct 09 09:53:03 IST 2006 MaxDB sdbinst: start extraction test run of "C:/sapdb/JP1/_tempLocation/SDBODBC.TGZ"
    Mon Oct 09 09:53:03 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:53:04 IST 2006 MaxDB sdbinst: package ODBC successfully checked
    Mon Oct 09 09:53:04 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:53:04 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:53:04 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:53:04 IST 2006 MaxDB sdbinst: starting preparing phase of package Webtools 7.6.00.33 32 bit
    Mon Oct 09 09:53:04 IST 2006 MaxDB sdbinst: -
    Mon Oct 09 09:53:04 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:53:04 IST 2006 MaxDB sdbinst: checking interferences to other packages... ok
    Mon Oct 09 09:53:04 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:53:04 IST 2006 MaxDB sdbinst: collecting data finished:
    Mon Oct 09 09:53:05 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:53:05 IST 2006 MaxDB sdbinst: webtools path: c:/sapdb/programs/web
    Mon Oct 09 09:53:05 IST 2006 MaxDB sdbinst: start extraction test run of "C:/sapdb/JP1/_tempLocation/SDBWEB.TGZ"
    Mon Oct 09 09:53:05 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:53:05 IST 2006 MaxDB sdbinst: package Webtools successfully checked
    Mon Oct 09 09:53:05 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:53:05 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:53:05 IST 2006 MaxDB sdbinst: checking filesystem "C:"... free disk space ok
    Mon Oct 09 09:53:06 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:53:06 IST 2006 MaxDB sdbinst: starting installation phase of package Base 7.6.00.33 32 bit
    Mon Oct 09 09:53:06 IST 2006 MaxDB sdbinst: -
    Mon Oct 09 09:53:06 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:53:06 IST 2006 MaxDB sdbinst: start real extraction of "C:/sapdb/JP1/_tempLocation/SDBBAS.TGZ"
    Mon Oct 09 09:53:06 IST 2006 MaxDB sdbinst: extracting: drwxr-xr-x            0 2006-07-18 06:34:08 bin/
    Mon Oct 09 09:53:06 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x       786432 2006-07-18 04:47:21 bin/dbmevtdisp.exe
    Mon Oct 09 09:53:06 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x       294912 2006-07-18 04:45:11 bin/protconv.exe
    Mon Oct 09 09:53:06 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x       147456 2006-07-18 03:26:11 bin/sdbconfig.exe
    Mon Oct 09 09:53:07 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x         7168 2006-07-18 06:32:29 bin/SDBINST.EXE
    Mon Oct 09 09:53:07 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x         6144 2006-07-18 06:32:29 bin/sdbpack.exe
    Mon Oct 09 09:53:07 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x         7680 2006-07-18 06:32:29 bin/sdbreg.exe
    Mon Oct 09 09:53:07 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x         7680 2006-07-18 06:32:29 bin/sdbregview.exe
    Mon Oct 09 09:53:07 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x        13824 2006-07-18 06:32:29 bin/SDBSETUP.EXE
    Mon Oct 09 09:53:07 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x         7680 2006-07-18 06:32:29 bin/sdbuninst.exe
    Mon Oct 09 09:53:07 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x         7168 2006-07-18 06:32:29 bin/sdbverify.exe
    Mon Oct 09 09:53:07 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x      1142784 2006-07-18 06:17:15 bin/sqlcli.exe
    Mon Oct 09 09:53:07 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x        40960 2006-07-18 05:57:55 bin/xsysrc.exe
    Mon Oct 09 09:53:07 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x       315392 2006-07-18 03:42:35 bin/xtcpupd.exe
    Mon Oct 09 09:53:08 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x       290816 2006-07-18 03:06:45 bin/xuser.exe
    Mon Oct 09 09:53:08 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x        40960 2006-07-18 05:57:55 bin/x_ping.exe
    Mon Oct 09 09:53:08 IST 2006 MaxDB sdbinst: extracting: drwxr-xr-x            0 2006-07-18 06:34:08 install/
    Mon Oct 09 09:53:08 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x       192512 2006-07-18 06:30:11 install/Grid.dll
    Mon Oct 09 09:53:08 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x       757760 2006-07-18 06:20:57 install/perl58.dll
    Mon Oct 09 09:53:08 IST 2006 MaxDB sdbinst: extracting: -rw-rr        66953 2006-07-18 06:32:29 install/RESOURCES.TGZ
    Mon Oct 09 09:53:08 IST 2006 MaxDB sdbinst: extracting: -rw-rr       447273 2006-07-18 06:32:28 install/SDBINST.TGZ
    Mon Oct 09 09:53:08 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x       413696 2006-07-18 06:32:22 install/sdbrun.dll
    Mon Oct 09 09:53:08 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x      1245184 2006-07-18 06:31:44 install/Wx.dll
    Mon Oct 09 09:53:09 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x      2265088 2006-07-18 06:29:53 install/wxmsw24.dll
    Mon Oct 09 09:53:09 IST 2006 MaxDB sdbinst: extracting: -rw-rr        64320 2006-07-18 06:32:30 install/WXPERL.TGZ
    Mon Oct 09 09:53:09 IST 2006 MaxDB sdbinst: extracting: drwxr-xr-x            0 2006-07-18 06:34:09 pgm/
    Mon Oct 09 09:53:09 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x      1966080 2006-07-18 04:45:17 pgm/dbmcli.exe
    Mon Oct 09 09:53:09 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x      1966080 2006-07-18 04:45:17 pgm/dbmcli_HelpInst.exe
    Mon Oct 09 09:53:09 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x       212992 2006-07-18 05:00:37 pgm/regupd.exe
    Mon Oct 09 09:53:09 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x       303104 2006-07-18 03:43:05 pgm/sqlping.exe
    Mon Oct 09 09:53:09 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x        49152 2006-07-18 02:54:49 pgm/sqltcp.dll
    Mon Oct 09 09:53:09 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x        49152 2006-07-18 02:54:51 pgm/sqltcp1.dll
    Mon Oct 09 09:53:09 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x        49152 2006-07-18 02:54:55 pgm/sqltcp2.dll
    Mon Oct 09 09:53:10 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x        45056 2006-07-18 02:54:59 pgm/sqltcpn.dll
    Mon Oct 09 09:53:10 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x       281952 2006-07-18 06:32:55 pgm/sqluser72.dll
    Mon Oct 09 09:53:10 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x       372656 2006-07-18 06:33:13 pgm/sqluser73.dll
    Mon Oct 09 09:53:10 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x       393216 2006-07-18 06:33:34 pgm/sqluser74.dll
    Mon Oct 09 09:53:10 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x       438272 2006-07-18 06:33:53 pgm/sqluser74n.dll
    Mon Oct 09 09:53:10 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x       516096 2006-07-18 06:05:41 pgm/sqluser76.dll
    Mon Oct 09 09:53:10 IST 2006 MaxDB sdbinst: checking unpacked archive... ok
    Mon Oct 09 09:53:11 IST 2006 MaxDB sdbinst: checking system libraries... ok
    Mon Oct 09 09:53:11 IST 2006 MaxDB sdbinst: system path updated successfully
    Mon Oct 09 09:53:11 IST 2006 MaxDB sdbinst: please reboot your system after installation to take effect changes
    Mon Oct 09 09:53:12 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:53:12 IST 2006 MaxDB sdbinst: starting installation phase of package SAP Utilities 7.6.00.33 32 bit
    Mon Oct 09 09:53:12 IST 2006 MaxDB sdbinst: -
    Mon Oct 09 09:53:12 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:53:12 IST 2006 MaxDB sdbinst: start real extraction of "C:/sapdb/JP1/_tempLocation/SAPUTL.TGZ"
    Mon Oct 09 09:53:12 IST 2006 MaxDB sdbinst: extracting: drwxr-xr-x            0 2006-07-18 06:34:28 bin/
    Mon Oct 09 09:53:13 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x       602112 2006-07-18 04:45:33 bin/dbmrfc.exe
    Mon Oct 09 09:53:13 IST 2006 MaxDB sdbinst: extracting: drwxr-xr-x            0 2006-07-18 06:34:29 lib/
    Mon Oct 09 09:53:13 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x      8572928 2006-07-18 02:52:01 lib/icudt30.dll
    Mon Oct 09 09:53:13 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x       692224 2006-07-18 02:52:01 lib/icuin30.dll
    Mon Oct 09 09:53:13 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x       602112 2006-07-18 02:52:01 lib/icuuc30.dll
    Mon Oct 09 09:53:13 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x      5562368 2006-07-18 03:01:17 lib/librfc32u.dll
    Mon Oct 09 09:53:13 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x       102400 2006-07-18 02:52:01 lib/libsapu16vc71.dll
    Mon Oct 09 09:53:13 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x       249856 2006-07-18 02:52:01 lib/libsapucum.dll
    Mon Oct 09 09:53:13 IST 2006 MaxDB sdbinst: extracting: drwxr-xr-x            0 2006-07-18 06:34:29 pgm/
    Mon Oct 09 09:53:13 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x       507904 2006-07-18 04:45:15 pgm/dbmgetf.exe
    Mon Oct 09 09:53:14 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x      1167360 2006-07-18 02:54:43 pgm/sapni.dll
    Mon Oct 09 09:53:14 IST 2006 MaxDB sdbinst: extracting: drwxr-xr-x            0 2006-07-18 06:34:29 Support/
    Mon Oct 09 09:53:14 IST 2006 MaxDB sdbinst: extracting: drwxr-xr-x            0 2006-07-18 06:34:30 Support/Mapfiles/
    Mon Oct 09 09:53:14 IST 2006 MaxDB sdbinst: extracting: -rw-rr       883889 2006-07-18 04:45:14 Support/Mapfiles/dbmgetf.map
    Mon Oct 09 09:53:14 IST 2006 MaxDB sdbinst: extracting: -rw-rr      1007259 2006-07-18 04:45:33 Support/Mapfiles/dbmrfc.map
    Mon Oct 09 09:53:14 IST 2006 MaxDB sdbinst: extracting: -rw-rr       440451 2006-07-18 02:54:42 Support/Mapfiles/sapni.map
    Mon Oct 09 09:53:14 IST 2006 MaxDB sdbinst: extracting: drwxr-xr-x            0 2006-07-18 06:34:30 symbols/
    Mon Oct 09 09:53:14 IST 2006 MaxDB sdbinst: extracting: -rw-rr      1010688 2006-07-18 02:54:42 symbols/sapni.pdb
    Mon Oct 09 09:53:15 IST 2006 MaxDB sdbinst: checking unpacked archive... ok
    Mon Oct 09 09:53:15 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:53:15 IST 2006 MaxDB sdbinst: starting installation phase of package JDBC 7.6.00.30
    Mon Oct 09 09:53:15 IST 2006 MaxDB sdbinst: -
    Mon Oct 09 09:53:15 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:53:15 IST 2006 MaxDB sdbinst: start real extraction of "C:/sapdb/JP1/_tempLocation/SDBJDBC.TGZ"
    Mon Oct 09 09:53:15 IST 2006 MaxDB sdbinst: extracting: drwxr-xr-x            0 2006-07-18 06:36:51 runtime/
    Mon Oct 09 09:53:15 IST 2006 MaxDB sdbinst: extracting: drwxr-xr-x            0 2006-07-18 06:36:51 runtime/7600/
    Mon Oct 09 09:53:15 IST 2006 MaxDB sdbinst: extracting: drwxr-xr-x            0 2006-07-18 06:36:51 runtime/7600/pgm/
    Mon Oct 09 09:53:15 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x       540672 2006-07-18 03:25:25 runtime/7600/pgm/sapdbcbin.dll
    Mon Oct 09 09:53:16 IST 2006 MaxDB sdbinst: extracting: drwxr-xr-x            0 2006-07-18 06:36:51 runtime/jar/
    Mon Oct 09 09:53:16 IST 2006 MaxDB sdbinst: extracting: -rw-rr       489216 2006-07-18 03:01:17 runtime/jar/sapdbc.jar
    Mon Oct 09 09:53:16 IST 2006 MaxDB sdbinst: checking unpacked archive... ok
    Mon Oct 09 09:53:16 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:53:16 IST 2006 MaxDB sdbinst: starting installation phase of package Server Utilities 7.6.00.33 32 bit
    Mon Oct 09 09:53:16 IST 2006 MaxDB sdbinst: -
    Mon Oct 09 09:53:16 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:53:16 IST 2006 MaxDB sdbinst: start real extraction of "C:/sapdb/JP1/_tempLocation/SDBUTL.TGZ"
    Mon Oct 09 09:53:16 IST 2006 MaxDB sdbinst: extracting: drwxr-xr-x            0 2006-07-18 06:34:40 bin/
    Mon Oct 09 09:53:16 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x        65536 2006-07-18 04:46:49 bin/sdbinfo.exe
    Mon Oct 09 09:53:17 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x       348160 2006-07-18 05:57:53 bin/sqlrun.dll
    Mon Oct 09 09:53:17 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x        40960 2006-07-18 05:57:55 bin/sysmon.exe
    Mon Oct 09 09:53:17 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x        40960 2006-07-18 05:57:55 bin/xbackup.exe
    Mon Oct 09 09:53:17 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x        40960 2006-07-18 05:57:55 bin/xinstinfo.exe
    Mon Oct 09 09:53:17 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x        40960 2006-07-18 05:57:55 bin/xpu.exe
    Mon Oct 09 09:53:17 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x        40960 2006-07-18 05:57:55 bin/x_analys.exe
    Mon Oct 09 09:53:17 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x        40960 2006-07-18 05:57:55 bin/x_cons.exe
    Mon Oct 09 09:53:17 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x        40960 2006-07-18 05:57:55 bin/x_server.exe
    Mon Oct 09 09:53:17 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x        40960 2006-07-18 05:57:55 bin/x_show.exe
    Mon Oct 09 09:53:17 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x        40960 2006-07-18 05:57:55 bin/x_start.exe
    Mon Oct 09 09:53:18 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x        40960 2006-07-18 05:57:55 bin/x_stop.exe
    Mon Oct 09 09:53:18 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x        40960 2006-07-18 05:57:55 bin/x_wiz.exe
    Mon Oct 09 09:53:18 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x        40960 2006-07-18 05:57:55 bin/x_wizard.exe
    Mon Oct 09 09:53:18 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x        40960 2006-07-18 05:57:55 bin/x_wizstop.exe
    Mon Oct 09 09:53:18 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x        40960 2006-07-18 05:57:55 bin/x_wiztrc.exe
    Mon Oct 09 09:53:18 IST 2006 MaxDB sdbinst: extracting: drwxr-xr-x            0 2006-07-18 06:34:40 env/
    Mon Oct 09 09:53:18 IST 2006 MaxDB sdbinst: extracting: -rw-rr          122 2006-07-18 04:52:54 env/serv.use
    Mon Oct 09 09:53:18 IST 2006 MaxDB sdbinst: extracting: -rw-rr          245 2006-07-18 04:52:54 env/xstart.use
    Mon Oct 09 09:53:18 IST 2006 MaxDB sdbinst: extracting: -rw-rr          542 2006-07-18 04:52:54 env/xstop.use
    Mon Oct 09 09:53:18 IST 2006 MaxDB sdbinst: extracting: drwxr-xr-x            0 2006-07-18 06:34:40 etc/
    Mon Oct 09 09:53:19 IST 2006 MaxDB sdbinst: extracting: -rw-rr          207 2006-07-18 02:50:43 etc/VERSIONS
    Mon Oct 09 09:53:19 IST 2006 MaxDB sdbinst: extracting: drwxr-xr-x            0 2006-07-18 06:34:40 pgm/
    Mon Oct 09 09:53:19 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x       466944 2006-07-18 03:26:59 pgm/serv.exe
    Mon Oct 09 09:53:19 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x       270336 2006-07-18 03:26:13 pgm/show.exe
    Mon Oct 09 09:53:19 IST 2006 MaxDB sdbinst: checking unpacked archive... ok
    Mon Oct 09 09:53:20 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:53:21 IST 2006 MaxDB sdbinst: starting installation phase of package Database Kernel 7.6.00.33 32 bit
    Mon Oct 09 09:53:21 IST 2006 MaxDB sdbinst: -
    Mon Oct 09 09:53:21 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:53:21 IST 2006 MaxDB sdbinst: start real extraction of "C:/sapdb/JP1/_tempLocation/SDBKRN.TGZ"
    Mon Oct 09 09:53:21 IST 2006 MaxDB sdbinst: extracting: drwxr-xr-x            0 2006-07-18 06:34:52 bin/
    Mon Oct 09 09:53:21 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x       266240 2006-07-18 04:45:47 bin/backint.exe
    Mon Oct 09 09:53:21 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x       786432 2006-07-18 04:47:21 bin/dbmevtdisp.exe
    Mon Oct 09 09:53:21 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x       540672 2006-07-18 04:47:29 bin/dbmevthndl_display.exe
    Mon Oct 09 09:53:21 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x       552960 2006-07-18 04:47:37 bin/dbmevthndl_winlog.exe
    Mon Oct 09 09:53:22 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x       282624 2006-07-18 04:44:23 bin/dbmsrvctl.exe
    Mon Oct 09 09:53:22 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x        42418 2006-07-18 03:01:17 bin/ireport.py
    Mon Oct 09 09:53:22 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x       245760 2006-07-18 04:46:43 bin/pipe2file.exe
    Mon Oct 09 09:53:22 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x      1114112 2006-07-18 04:46:05 bin/sdbfill.exe
    Mon Oct 09 09:53:22 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x       348160 2006-07-18 05:57:53 bin/sqlrun.dll
    Mon Oct 09 09:53:22 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x        53248 2006-07-18 03:06:39 bin/sqlver.exe
    Mon Oct 09 09:53:22 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x        53248 2006-07-18 03:06:37 bin/sqlwhat.exe
    Mon Oct 09 09:53:22 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x        40960 2006-07-18 05:57:55 bin/xci.exe
    Mon Oct 09 09:53:22 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x        40960 2006-07-18 05:57:55 bin/xkernprot.exe
    Mon Oct 09 09:53:23 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x        40960 2006-07-18 05:57:55 bin/xoldci.exe
    Mon Oct 09 09:53:23 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x        40960 2006-07-18 05:57:55 bin/xservice.exe
    Mon Oct 09 09:53:23 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x        40960 2006-07-18 05:57:55 bin/xsql.exe
    Mon Oct 09 09:53:23 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x        40960 2006-07-18 05:57:55 bin/xsqlro.exe
    Mon Oct 09 09:53:23 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x        40960 2006-07-18 05:57:55 bin/xtracesort.exe
    Mon Oct 09 09:53:23 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x        40960 2006-07-18 05:57:55 bin/x_diagnose.exe
    Mon Oct 09 09:53:23 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x       323584 2006-07-18 04:47:47 bin/x_python.exe
    Mon Oct 09 09:53:23 IST 2006 MaxDB sdbinst: extracting: drwxr-xr-x            0 2006-07-18 06:34:47 cluster/
    Mon Oct 09 09:53:23 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x      1982464 2006-07-18 03:41:59 cluster/dbmsrv_clu.exe
    Mon Oct 09 09:53:23 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x        77824 2006-07-18 03:27:57 cluster/SAPDBMSCSEx.dll
    Mon Oct 09 09:53:24 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x       122880 2006-07-18 03:28:09 cluster/sapdbmscsman.dll
    Mon Oct 09 09:53:24 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x        73728 2006-07-18 03:27:27 cluster/SAPDBMSCSMan.exe
    Mon Oct 09 09:53:24 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x        57344 2006-07-18 03:27:19 cluster/SAPDBMSCSRes.dll
    Mon Oct 09 09:53:24 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x       303104 2006-07-18 03:28:29 cluster/service_clu.exe
    Mon Oct 09 09:53:24 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x       483328 2006-07-18 03:28:27 cluster/serv_clu.exe
    Mon Oct 09 09:53:24 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x       331776 2006-07-18 03:28:23 cluster/stop_clu.exe
    Mon Oct 09 09:53:24 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x       335872 2006-07-18 03:28:21 cluster/strt_clu.exe
    Mon Oct 09 09:53:24 IST 2006 MaxDB sdbinst: extracting: drwxr-xr-x            0 2006-07-18 06:34:47 demo/
    Mon Oct 09 09:53:24 IST 2006 MaxDB sdbinst: extracting: -rw-rr      3111624 2006-07-18 03:01:17 demo/HOTEL.py
    Mon Oct 09 09:53:24 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x         1080 2006-07-18 03:01:17 demo/ltutorial.py
    Mon Oct 09 09:53:25 IST 2006 MaxDB sdbinst: extracting: -rw-rr        12046 2006-07-18 03:01:17 demo/tutoriallib.py
    Mon Oct 09 09:53:25 IST 2006 MaxDB sdbinst: extracting: drwxr-xr-x            0 2006-07-18 06:34:53 doc/
    Mon Oct 09 09:53:25 IST 2006 MaxDB sdbinst: extracting: drwxr-xr-x            0 2006-07-18 06:34:54 doc/FirstSteps/
    Mon Oct 09 09:53:25 IST 2006 MaxDB sdbinst: extracting: -rw-rr         4158 2006-07-18 03:01:17 doc/FirstSteps/index.html
    Mon Oct 09 09:53:25 IST 2006 MaxDB sdbinst: extracting: drwxr-xr-x            0 2006-07-18 06:34:53 doc/FirstSteps/Java/
    Mon Oct 09 09:53:25 IST 2006 MaxDB sdbinst: extracting: -rw-rr         1019 2006-07-18 03:01:17 doc/FirstSteps/Java/DemodbData.class
    Mon Oct 09 09:53:25 IST 2006 MaxDB sdbinst: extracting: -rw-rr         2239 2006-07-18 03:01:17 doc/FirstSteps/Java/DemodbData.java
    Mon Oct 09 09:53:25 IST 2006 MaxDB sdbinst: extracting: -rw-rr         1599 2006-07-18 03:01:17 doc/FirstSteps/Java/HelloMaxDB.class
    Mon Oct 09 09:53:25 IST 2006 MaxDB sdbinst: extracting: -rw-rr         2162 2006-07-18 03:01:17 doc/FirstSteps/Java/HelloMaxDB.java
    Mon Oct 09 09:53:25 IST 2006 MaxDB sdbinst: extracting: -rw-rr         2662 2006-07-18 03:01:17 doc/FirstSteps/Java/HowToJava.html
    Mon Oct 09 09:53:26 IST 2006 MaxDB sdbinst: extracting: -rw-rr         1305 2006-07-18 03:01:17 doc/FirstSteps/Java/StateMaxDB.class
    Mon Oct 09 09:53:26 IST 2006 MaxDB sdbinst: extracting: -rw-rr         1767 2006-07-18 03:01:17 doc/FirstSteps/Java/StateMaxDB.java
    Mon Oct 09 09:53:26 IST 2006 MaxDB sdbinst: extracting: -rw-rr          227 2006-07-18 03:01:17 doc/FirstSteps/maxdbenv.cmd
    Mon Oct 09 09:53:26 IST 2006 MaxDB sdbinst: extracting: drwxr-xr-x            0 2006-07-18 06:34:53 doc/FirstSteps/ODBC/
    Mon Oct 09 09:53:26 IST 2006 MaxDB sdbinst: extracting: -rw-rr         5213 2006-07-18 03:01:17 doc/FirstSteps/ODBC/HelloMaxDB.c
    Mon Oct 09 09:53:26 IST 2006 MaxDB sdbinst: extracting: -rw-rr         1996 2006-07-18 03:01:17 doc/FirstSteps/ODBC/HowToODBC.html
    Mon Oct 09 09:53:26 IST 2006 MaxDB sdbinst: extracting: -rw-rr         1101 2006-07-18 03:01:17 doc/FirstSteps/ODBC/Makefile
    Mon Oct 09 09:53:26 IST 2006 MaxDB sdbinst: extracting: drwxr-xr-x            0 2006-07-18 06:34:54 doc/FirstSteps/Perl/
    Mon Oct 09 09:53:26 IST 2006 MaxDB sdbinst: extracting: -rw-rr         1686 2006-07-18 03:01:17 doc/FirstSteps/Perl/demodbData.pm
    Mon Oct 09 09:53:26 IST 2006 MaxDB sdbinst: extracting: -rw-rr         2597 2006-07-18 03:01:17 doc/FirstSteps/Perl/HowToPerl.html
    Mon Oct 09 09:53:27 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x         1673 2006-07-18 03:01:17 doc/FirstSteps/Perl/StateMaxDB.pl
    Mon Oct 09 09:53:27 IST 2006 MaxDB sdbinst: extracting: drwxr-xr-x            0 2006-07-18 06:34:54 doc/FirstSteps/Python/
    Mon Oct 09 09:53:27 IST 2006 MaxDB sdbinst: extracting: -rw-rr         1584 2006-07-18 03:01:17 doc/FirstSteps/Python/demodbData.py
    Mon Oct 09 09:53:27 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x         1572 2006-07-18 03:01:17 doc/FirstSteps/Python/HelloMaxDB-API.py
    Mon Oct 09 09:53:27 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x         1572 2006-07-18 03:01:17 doc/FirstSteps/Python/HelloMaxDB.py
    Mon Oct 09 09:53:27 IST 2006 MaxDB sdbinst: extracting: -rw-rr         3746 2006-07-18 03:01:17 doc/FirstSteps/Python/HowToPython.html
    Mon Oct 09 09:53:27 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x         1578 2006-07-18 03:01:17 doc/FirstSteps/Python/StateMaxDB.py
    Mon Oct 09 09:53:27 IST 2006 MaxDB sdbinst: extracting: drwxr-xr-x            0 2006-07-18 06:34:54 doc/FirstSteps/SQLDBC/
    Mon Oct 09 09:53:27 IST 2006 MaxDB sdbinst: extracting: -rw-rr         4225 2006-07-18 03:01:17 doc/FirstSteps/SQLDBC/HelloMaxDB.cpp
    Mon Oct 09 09:53:27 IST 2006 MaxDB sdbinst: extracting: -rw-rr         2032 2006-07-18 03:01:17 doc/FirstSteps/SQLDBC/HowToSQLDBC.html
    Mon Oct 09 09:53:28 IST 2006 MaxDB sdbinst: extracting: -rw-rr         1276 2006-07-18 03:01:17 doc/FirstSteps/SQLDBC/Makefile
    Mon Oct 09 09:53:28 IST 2006 MaxDB sdbinst: extracting: drwxr-xr-x            0 2006-07-18 06:34:49 env/
    Mon Oct 09 09:53:28 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x         6940 2006-07-18 04:47:37 env/APPS.py
    Mon Oct 09 09:53:28 IST 2006 MaxDB sdbinst: extracting: -rw-rr         4513 2006-07-18 04:47:37 env/CNR3DATA.py
    Mon Oct 09 09:53:28 IST 2006 MaxDB sdbinst: extracting: -rw-rr         8929 2006-07-18 04:47:37 env/CNR3TAB.py
    Mon Oct 09 09:53:28 IST 2006 MaxDB sdbinst: extracting: -rw-rr       194089 2006-07-18 04:52:54 env/cserv.pcf
    Mon Oct 09 09:53:28 IST 2006 MaxDB sdbinst: extracting: -rw-rr        18587 2006-07-18 04:47:37 env/DBMVIEWS.py
    Mon Oct 09 09:53:28 IST 2006 MaxDB sdbinst: extracting: drwxr-xr-x            0 2006-07-18 06:34:48 env/en/
    Mon Oct 09 09:53:28 IST 2006 MaxDB sdbinst: extracting: -rw-rr         7609 2006-07-18 04:52:54 env/en/DBM.en
    Mon Oct 09 09:53:28 IST 2006 MaxDB sdbinst: extracting: -rw-rr        16426 2006-07-18 04:47:37 env/GARBAGE.py
    Mon Oct 09 09:53:29 IST 2006 MaxDB sdbinst: extracting: -rw-rr          249 2006-07-18 04:52:54 env/general.use
    Mon Oct 09 09:53:29 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x         2017 2006-07-18 04:47:41 env/getpackages.py
    Mon Oct 09 09:53:29 IST 2006 MaxDB sdbinst: extracting: -rw-rr         1857 2006-07-18 04:47:37 env/INFO.py
    Mon Oct 09 09:53:29 IST 2006 MaxDB sdbinst: extracting: -rw-rr        14835 2006-07-18 04:47:41 env/installib.py
    Mon Oct 09 09:53:29 IST 2006 MaxDB sdbinst: extracting: -rw-rr        74105 2006-07-18 04:47:39 env/JDBC.py
    Mon Oct 09 09:53:29 IST 2006 MaxDB sdbinst: extracting: -rw-rr          396 2006-07-18 04:52:54 env/kernprot.use
    Mon Oct 09 09:53:29 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x         1662 2006-07-18 04:47:43 env/lapps.py
    Mon Oct 09 09:53:29 IST 2006 MaxDB sdbinst: extracting: -rw-rr         8840 2006-07-18 03:01:17 env/lsystab.py
    Mon Oct 09 09:53:29 IST 2006 MaxDB sdbinst: extracting: -rw-rr        19212 2006-07-18 04:47:39 env/ODBC.py
    Mon Oct 09 09:53:29 IST 2006 MaxDB sdbinst: extracting: -rw-rr         1954 2006-07-18 04:47:39 env/ORADD.py
    Mon Oct 09 09:53:30 IST 2006 MaxDB sdbinst: extracting: -rw-rr       267134 2006-07-18 04:47:39 env/ORADDCOM.py
    Mon Oct 09 09:53:30 IST 2006 MaxDB sdbinst: extracting: -rw-rr        10299 2006-07-18 04:47:39 env/ORADDSYN.py
    Mon Oct 09 09:53:30 IST 2006 MaxDB sdbinst: extracting: -rw-rr       159113 2006-07-18 04:47:39 env/ORADDV.py
    Mon Oct 09 09:53:30 IST 2006 MaxDB sdbinst: extracting: -rw-rr         2113 2006-07-18 04:47:39 env/PRECOM.py
    Mon Oct 09 09:53:30 IST 2006 MaxDB sdbinst: extracting: -rw-rr        49168 2006-07-18 04:47:43 env/REPOSITORY.py
    Mon Oct 09 09:53:30 IST 2006 MaxDB sdbinst: extracting: -rw-rr        62152 2006-07-18 04:47:37 env/SAPDBLOADER.py
    Mon Oct 09 09:53:30 IST 2006 MaxDB sdbinst: extracting: -rw-rr         5196 2006-07-18 04:47:39 env/SHOWCMD.py
    Mon Oct 09 09:53:30 IST 2006 MaxDB sdbinst: extracting: -rw-rr        47440 2006-07-18 04:47:39 env/SQLDBC.py
    Mon Oct 09 09:53:30 IST 2006 MaxDB sdbinst: extracting: -rw-rr        47024 2006-07-18 04:47:41 env/SYSDBA.py
    Mon Oct 09 09:53:30 IST 2006 MaxDB sdbinst: extracting: -rw-rr        58248 2006-07-18 04:47:41 env/SYSDBACOM.py
    Mon Oct 09 09:53:31 IST 2006 MaxDB sdbinst: extracting: -rw-rr        17897 2006-07-18 04:47:41 env/SYSINFO.py
    Mon Oct 09 09:53:31 IST 2006 MaxDB sdbinst: extracting: -rw-rr       106735 2006-07-18 04:47:41 env/SYSINFOCOM.py
    Mon Oct 09 09:53:31 IST 2006 MaxDB sdbinst: extracting: -rw-rr        10964 2006-07-18 04:47:41 env/TRIGGER.py
    Mon Oct 09 09:53:31 IST 2006 MaxDB sdbinst: extracting: -rw-rr         3916 2006-07-18 04:47:41 env/UDE.py
    Mon Oct 09 09:53:31 IST 2006 MaxDB sdbinst: extracting: -rw-rr         7309 2006-07-18 04:47:43 env/WA.py
    Mon Oct 09 09:53:31 IST 2006 MaxDB sdbinst: extracting: -rw-rr        54557 2006-07-18 04:47:41 env/XDD.py
    Mon Oct 09 09:53:31 IST 2006 MaxDB sdbinst: extracting: -rw-rr       105718 2006-07-18 04:47:41 env/XDDCOM.py
    Mon Oct 09 09:53:31 IST 2006 MaxDB sdbinst: extracting: drwxr-xr-x            0 2006-07-18 06:34:49 lib/
    Mon Oct 09 09:53:31 IST 2006 MaxDB sdbinst: extracting: drwxr-xr-x            0 2006-07-18 06:34:49 lib/python2.3/
    Mon Oct 09 09:53:31 IST 2006 MaxDB sdbinst: extracting: -rw-rr         7577 2006-07-18 03:01:17 lib/python2.3/optlib.py
    Mon Oct 09 09:53:32 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x       135234 2006-07-18 03:01:17 lib/python2.3/pyexpat.pyd
    Mon Oct 09 09:53:32 IST 2006 MaxDB sdbinst: extracting: drwxr-xr-x            0 2006-07-18 06:34:49 lib/python2.3/sdb/
    Mon Oct 09 09:53:32 IST 2006 MaxDB sdbinst: extracting: -rw-rr        15565 2006-07-18 03:01:17 lib/python2.3/sdb/dbapi.py
    Mon Oct 09 09:53:32 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x       503808 2006-07-18 04:47:51 lib/python2.3/sdb/dbm.pyd
    Mon Oct 09 09:53:32 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x       483328 2006-07-18 04:47:55 lib/python2.3/sdb/loader.pyd
    Mon Oct 09 09:53:32 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x       458752 2006-07-18 04:47:59 lib/python2.3/sdb/sql.pyd
    Mon Oct 09 09:53:32 IST 2006 MaxDB sdbinst: extracting: -rw-rr          921 2006-07-18 03:01:17 lib/python2.3/sdb/__init__.py
    Mon Oct 09 09:53:32 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x        61503 2006-07-18 03:01:17 lib/python2.3/zlib.pyd
    Mon Oct 09 09:53:32 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x        49218 2006-07-18 03:01:17 lib/python2.3/_socket.pyd
    Mon Oct 09 09:53:32 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x        57407 2006-07-18 03:01:17 lib/python2.3/_sre.pyd
    Mon Oct 09 09:53:33 IST 2006 MaxDB sdbinst: extracting: drwxr-xr-x            0 2006-07-18 06:34:49 misc/
    Mon Oct 09 09:53:33 IST 2006 MaxDB sdbinst: extracting: -rw-rr         2437 2006-07-18 06:18:47 misc/create_demo_db.cmd
    Mon Oct 09 09:53:33 IST 2006 MaxDB sdbinst: extracting: -rw-rr          417 2006-07-18 06:18:47 misc/drop_demo_db.cmd
    Mon Oct 09 09:53:33 IST 2006 MaxDB sdbinst: extracting: drwxr-xr-x            0 2006-07-18 06:34:53 pgm/
    Mon Oct 09 09:53:33 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x       200704 2006-07-18 04:46:45 pgm/backup.exe
    Mon Oct 09 09:53:33 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x       372736 2006-07-18 03:25:55 pgm/cons.exe
    Mon Oct 09 09:53:33 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x        45056 2006-07-18 03:25:29 pgm/cr_param.exe
    Mon Oct 09 09:53:33 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x       940032 2006-07-18 03:01:17 pgm/dbghelp.dll
    Mon Oct 09 09:53:33 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x       294912 2006-07-18 04:44:33 pgm/dbmreg.exe
    Mon Oct 09 09:53:34 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x       405504 2006-07-18 04:45:05 pgm/dbmshm.exe
    Mon Oct 09 09:53:34 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x      1966080 2006-07-18 04:44:17 pgm/dbmsrv.exe
    Mon Oct 09 09:53:34 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x      1748992 2006-07-18 04:44:49 pgm/dbmsrvscd.exe
    Mon Oct 09 09:53:34 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x       294912 2006-07-18 04:44:27 pgm/dbmstart.exe
    Mon Oct 09 09:53:34 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x       294912 2006-07-18 04:44:29 pgm/dbmstop.exe
    Mon Oct 09 09:53:34 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x       294912 2006-07-18 04:44:35 pgm/dbmunreg.exe
    Mon Oct 09 09:53:34 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x        69632 2006-07-18 06:05:39 pgm/dbpinstall.dll
    Mon Oct 09 09:53:34 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x      1060864 2006-07-18 03:46:37 pgm/diagnose.exe
    Mon Oct 09 09:53:34 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x      6971392 2006-07-18 04:44:09 pgm/kernel.exe
    Mon Oct 09 09:53:34 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x       118784 2006-07-18 03:43:13 pgm/libhsscopy.dll
    Mon Oct 09 09:53:35 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x      1134592 2006-07-18 06:02:21 pgm/liboms.dll
    Mon Oct 09 09:53:35 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x       151552 2006-07-18 06:06:13 pgm/libsqlcls.dll
    Mon Oct 09 09:53:35 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x      1073152 2006-07-18 06:06:55 pgm/libSQLDBC.dll
    Mon Oct 09 09:53:35 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x      1155072 2006-07-18 06:14:13 pgm/libSQLDBC_C.dll
    Mon Oct 09 09:53:35 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x      2953216 2006-07-18 04:52:33 pgm/lserver.exe
    Mon Oct 09 09:53:35 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x        20545 2006-07-18 03:01:17 pgm/pysapdb.exe
    Mon Oct 09 09:53:35 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x       974915 2006-07-18 03:01:17 pgm/python23.dll
    Mon Oct 09 09:53:35 IST 2006 MaxDB sdbinst: extracting: -rw-rr      2071185 2006-07-18 03:01:17 pgm/python23.zip
    Mon Oct 09 09:53:35 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x        45056 2006-07-18 03:25:27 pgm/renparam.exe
    Mon Oct 09 09:53:36 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x       290816 2006-07-18 03:27:05 pgm/service.exe
    Mon Oct 09 09:53:36 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x      1097728 2006-07-18 03:45:19 pgm/slowci.exe
    Mon Oct 09 09:53:36 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x       405504 2006-07-18 03:27:09 pgm/sqlinst.dll
    Mon Oct 09 09:53:36 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x      1359872 2006-07-18 03:27:15 pgm/sqlmsg.dll
    Mon Oct 09 09:53:36 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x       315392 2006-07-18 03:26:03 pgm/stop.exe
    Mon Oct 09 09:53:36 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x       319488 2006-07-18 03:25:59 pgm/strt.exe
    Mon Oct 09 09:53:36 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x        98304 2006-07-18 05:00:41 pgm/StudioUtil.dll
    Mon Oct 09 09:53:36 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x        49152 2006-07-18 03:43:07 pgm/sysrc.exe
    Mon Oct 09 09:53:36 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x        73728 2006-07-18 03:27:13 pgm/systemrc.exe
    Mon Oct 09 09:53:36 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x       221184 2006-07-18 05:00:47 pgm/TableDefC.dll
    Mon Oct 09 09:53:37 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x        45056 2006-07-18 04:47:31 pgm/Tools_WinEvtLog.dll
    Mon Oct 09 09:53:37 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x        73728 2006-07-18 04:52:43 pgm/tracesort.exe
    Mon Oct 09 09:53:37 IST 2006 MaxDB sdbinst: extracting: drwxr-xr-x            0 2006-07-18 06:34:53 sap/
    Mon Oct 09 09:53:37 IST 2006 MaxDB sdbinst: extracting: -rw-rr          147 2006-07-18 03:01:17 sap/dbpinstall.lst
    Mon Oct 09 09:53:37 IST 2006 MaxDB sdbinst: extracting: -rw-rr         1474 2006-07-18 04:45:33 sap/grantxdb.dbm
    Mon Oct 09 09:53:37 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x        18192 2006-07-18 03:01:17 sap/lcinit.bat
    Mon Oct 09 09:53:37 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x       126976 2006-07-18 06:05:31 sap/lvcbench.dll
    Mon Oct 09 09:53:37 IST 2006 MaxDB sdbinst: extracting: -rw-rr           89 2006-07-18 03:01:17 sap/saprfc.ini
    Mon Oct 09 09:53:37 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x        86016 2006-07-18 05:02:09 sap/sphsapdb.dll
    Mon Oct 09 09:53:37 IST 2006 MaxDB sdbinst: extracting: -rw-rr           12 2006-07-18 03:01:17 sap/sphsapdb.lst
    Mon Oct 09 09:53:38 IST 2006 MaxDB sdbinst: checking unpacked archive... ok
    Mon Oct 09 09:53:42 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:53:42 IST 2006 MaxDB sdbinst: starting installation phase of package Messages MSG 0.3951
    Mon Oct 09 09:53:42 IST 2006 MaxDB sdbinst: -
    Mon Oct 09 09:53:42 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:53:43 IST 2006 MaxDB sdbinst: start real extraction of "C:/sapdb/JP1/_tempLocation/SDBMSG.TGZ"
    Mon Oct 09 09:53:43 IST 2006 MaxDB sdbinst: extracting: drwxr-xr-x            0 2006-07-18 06:37:08 msg/
    Mon Oct 09 09:53:43 IST 2006 MaxDB sdbinst: extracting: -rw-rr          846 2006-07-18 03:01:17 msg/SDBMsg_Admin.xml
    Mon Oct 09 09:53:43 IST 2006 MaxDB sdbinst: extracting: -rw-rr         1107 2006-07-18 03:01:17 msg/SDBMsg_Backup.xml
    Mon Oct 09 09:53:43 IST 2006 MaxDB sdbinst: extracting: -rw-rr         3255 2006-07-18 03:01:17 msg/SDBMsg_Catalog.xml
    Mon Oct 09 09:53:43 IST 2006 MaxDB sdbinst: extracting: -rw-rr         4595 2006-07-18 03:01:17 msg/SDBMsg_Converter.xml
    Mon Oct 09 09:53:43 IST 2006 MaxDB sdbinst: extracting: -rw-rr        13936 2006-07-18 03:01:17 msg/SDBMsg_Data.xml
    Mon Oct 09 09:53:43 IST 2006 MaxDB sdbinst: extracting: -rw-rr          333 2006-07-18 03:01:17 msg/SDBMsg_DBMCLI.xml
    Mon Oct 09 09:53:43 IST 2006 MaxDB sdbinst: extracting: -rw-rr         5254 2006-07-18 03:01:17 msg/SDBMsg_DBMEd.xml
    Mon Oct 09 09:53:43 IST 2006 MaxDB sdbinst: extracting: -rw-rr          328 2006-07-18 03:01:17 msg/SDBMsg_DBMLog.xml
    Mon Oct 09 09:53:44 IST 2006 MaxDB sdbinst: extracting: -rw-rr         3179 2006-07-18 03:01:17 msg/SDBMsg_DBMScd.xml
    Mon Oct 09 09:53:44 IST 2006 MaxDB sdbinst: extracting: -rw-rr        75397 2006-07-18 03:01:17 msg/SDBMsg_DBMSrv.xml
    Mon Oct 09 09:53:44 IST 2006 MaxDB sdbinst: extracting: -rw-rr         1071 2006-07-18 03:01:17 msg/SDBMsg_DBMSrvTest.xml
    Mon Oct 09 09:53:44 IST 2006 MaxDB sdbinst: extracting: -rw-rr         1321 2006-07-18 03:01:17 msg/SDBMsg_DBProc.xml
    Mon Oct 09 09:53:44 IST 2006 MaxDB sdbinst: extracting: -rw-rr          553 2006-07-18 03:01:17 msg/SDBMsg_DIAGNOSE.xml
    Mon Oct 09 09:53:44 IST 2006 MaxDB sdbinst: extracting: -rw-rr         7818 2006-07-18 03:01:17 msg/SDBMsg_FileDir.xml
    Mon Oct 09 09:53:44 IST 2006 MaxDB sdbinst: extracting: -rw-rr          477 2006-07-18 03:01:17 msg/SDBMsg_Index.xml
    Mon Oct 09 09:53:44 IST 2006 MaxDB sdbinst: extracting: -rw-rr         3461 2006-07-18 03:01:17 msg/SDBMsg_IOMan.xml
    Mon Oct 09 09:53:44 IST 2006 MaxDB sdbinst: extracting: -rw-rr         1384 2006-07-18 03:01:17 msg/SDBMsg_Join.xml
    Mon Oct 09 09:53:44 IST 2006 MaxDB sdbinst: extracting: -rw-rr          697 2006-07-18 03:01:17 msg/SDBMsg_JoinPathOptimizer.xml
    Mon Oct 09 09:53:45 IST 2006 MaxDB sdbinst: extracting: -rw-rr         2112 2006-07-18 03:01:17 msg/SDBMsg_KernelCommon.xml
    Mon Oct 09 09:53:45 IST 2006 MaxDB sdbinst: extracting: -rw-rr         1035 2006-07-18 03:01:17 msg/SDBMsg_KSQL.xml
    Mon Oct 09 09:53:45 IST 2006 MaxDB sdbinst: extracting: -rw-rr          801 2006-07-18 03:01:17 msg/SDBMsg_LiveCache.xml
    Mon Oct 09 09:53:45 IST 2006 MaxDB sdbinst: extracting: -rw-rr          172 2006-07-18 03:01:17 msg/SDBMsg_Loader.xml
    Mon Oct 09 09:53:45 IST 2006 MaxDB sdbinst: extracting: -rw-rr         5443 2006-07-18 03:01:17 msg/SDBMsg_Log.xml
    Mon Oct 09 09:53:45 IST 2006 MaxDB sdbinst: extracting: -rw-rr         3154 2006-07-18 03:01:17 msg/SDBMsg_Messages.xml
    Mon Oct 09 09:53:45 IST 2006 MaxDB sdbinst: extracting: -rw-rr          369 2006-07-18 03:01:17 msg/SDBMsg_ObjectContainer.xml
    Mon Oct 09 09:53:45 IST 2006 MaxDB sdbinst: extracting: -rw-rr         3159 2006-07-18 03:01:17 msg/SDBMsg_OMS.xml
    Mon Oct 09 09:53:45 IST 2006 MaxDB sdbinst: extracting: -rw-rr          172 2006-07-18 03:01:17 msg/SDBMsg_OPMSG.xml
    Mon Oct 09 09:53:45 IST 2006 MaxDB sdbinst: extracting: -rw-rr          172 2006-07-18 03:01:17 msg/SDBMsg_Optimizer.xml
    Mon Oct 09 09:53:46 IST 2006 MaxDB sdbinst: extracting: -rw-rr          435 2006-07-18 03:01:17 msg/SDBMsg_Query.xml
    Mon Oct 09 09:53:46 IST 2006 MaxDB sdbinst: extracting: -rw-rr          442 2006-07-18 03:01:17 msg/SDBMsg_QueryRewrite.xml
    Mon Oct 09 09:53:46 IST 2006 MaxDB sdbinst: extracting: -rw-rr         2021 2006-07-18 03:01:17 msg/SDBMsg_Recovery.xml
    Mon Oct 09 09:53:46 IST 2006 MaxDB sdbinst: extracting: -rw-rr         5220 2006-07-18 03:01:17 msg/SDBMsg_Rst.xml
    Mon Oct 09 09:53:46 IST 2006 MaxDB sdbinst: extracting: -rw-rr         2472 2006-07-18 03:01:17 msg/SDBMsg_RTEComm.xml
    Mon Oct 09 09:53:46 IST 2006 MaxDB sdbinst: extracting: -rw-rr         1406 2006-07-18 03:01:17 msg/SDBMsg_RTEConf.xml
    Mon Oct 09 09:53:46 IST 2006 MaxDB sdbinst: extracting: -rw-rr          889 2006-07-18 03:01:17 msg/SDBMsg_RTEDBState.xml
    Mon Oct 09 09:53:46 IST 2006 MaxDB sdbinst: extracting: -rw-rr         5001 2006-07-18 03:01:17 msg/SDBMsg_RTEDiag.xml
    Mon Oct 09 09:53:46 IST 2006 MaxDB sdbinst: extracting: -rw-rr        14767 2006-07-18 03:01:17 msg/SDBMsg_RTEIO.xml
    Mon Oct 09 09:53:46 IST 2006 MaxDB sdbinst: extracting: -rw-rr         3625 2006-07-18 03:01:17 msg/SDBMsg_RTEMem.xml
    Mon Oct 09 09:53:47 IST 2006 MaxDB sdbinst: extracting: -rw-rr          511 2006-07-18 03:01:17 msg/SDBMsg_RTESec.xml
    Mon Oct 09 09:53:47 IST 2006 MaxDB sdbinst: extracting: -rw-rr         1808 2006-07-18 03:01:17 msg/SDBMsg_RTESys.xml
    Mon Oct 09 09:53:47 IST 2006 MaxDB sdbinst: extracting: -rw-rr         3550 2006-07-18 03:01:17 msg/SDBMsg_RTETask.xml
    Mon Oct 09 09:53:47 IST 2006 MaxDB sdbinst: extracting: -rw-rr         4541 2006-07-18 03:01:17 msg/SDBMsg_RunTime.xml
    Mon Oct 09 09:53:47 IST 2006 MaxDB sdbinst: extracting: -rw-rr         1653 2006-07-18 03:01:17 msg/SDBMsg_SAPDBAlgo.xml
    Mon Oct 09 09:53:47 IST 2006 MaxDB sdbinst: extracting: -rw-rr          562 2006-07-18 03:01:17 msg/SDBMsg_SAPDBMem.xml
    Mon Oct 09 09:53:47 IST 2006 MaxDB sdbinst: extracting: -rw-rr         1718 2006-07-18 03:01:17 msg/SDBMsg_Savepoint.xml
    Mon Oct 09 09:53:47 IST 2006 MaxDB sdbinst: extracting: -rw-rr         5909 2006-07-18 03:01:17 msg/SDBMsg_SharedSQL.xml
    Mon Oct 09 09:53:47 IST 2006 MaxDB sdbinst: extracting: -rw-rr        26284 2006-07-18 03:01:17 msg/SDBMsg_SQLMan.xml
    Mon Oct 09 09:53:47 IST 2006 MaxDB sdbinst: extracting: -rw-rr         9419 2006-07-18 03:01:17 msg/SDBMsg_SrvTasks.xml
    Mon Oct 09 09:53:48 IST 2006 MaxDB sdbinst: extracting: -rw-rr         3638 2006-07-18 03:01:17 msg/SDBMsg_Table.xml
    Mon Oct 09 09:53:48 IST 2006 MaxDB sdbinst: extracting: -rw-rr          883 2006-07-18 03:01:17 msg/SDBMsg_ToolsCommon.xml
    Mon Oct 09 09:53:48 IST 2006 MaxDB sdbinst: extracting: -rw-rr         1186 2006-07-18 03:01:17 msg/SDBMsg_Transaction.xml
    Mon Oct 09 09:53:48 IST 2006 MaxDB sdbinst: extracting: -rw-rr         4883 2006-07-18 03:01:17 msg/SDBMsg_ZZZTest.xml
    Mon Oct 09 09:53:48 IST 2006 MaxDB sdbinst: checking unpacked archive... ok
    Mon Oct 09 09:53:48 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:53:48 IST 2006 MaxDB sdbinst: starting installation phase of package ODBC 7.6.00.33 32 bit
    Mon Oct 09 09:53:48 IST 2006 MaxDB sdbinst: -
    Mon Oct 09 09:53:48 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:53:48 IST 2006 MaxDB sdbinst: start real extraction of "C:/sapdb/JP1/_tempLocation/SDBODBC.TGZ"
    Mon Oct 09 09:53:49 IST 2006 MaxDB sdbinst: extracting: drwxr-xr-x            0 2006-07-18 06:36:55 incl/
    Mon Oct 09 09:53:49 IST 2006 MaxDB sdbinst: extracting: -rw-rr        11380 2006-07-18 03:01:17 incl/SDBBOS.h
    Mon Oct 09 09:53:49 IST 2006 MaxDB sdbinst: extracting: -rw-rr        31567 2006-07-18 03:06:19 incl/sql.h
    Mon Oct 09 09:53:49 IST 2006 MaxDB sdbinst: extracting: -rw-rr        81467 2006-07-18 03:06:19 incl/sqlext.h
    Mon Oct 09 09:53:49 IST 2006 MaxDB sdbinst: extracting: -rw-rr         9534 2006-07-18 03:06:19 incl/sqltypes.h
    Mon Oct 09 09:53:49 IST 2006 MaxDB sdbinst: extracting: -rw-rr        24313 2006-07-18 03:06:20 incl/sqlucode.h
    Mon Oct 09 09:53:49 IST 2006 MaxDB sdbinst: extracting: drwxr-xr-x            0 2006-07-18 06:36:56 pgm/
    Mon Oct 09 09:53:49 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x       487424 2006-07-18 05:02:43 pgm/libSDBBOS.dll
    Mon Oct 09 09:53:49 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x        12288 2006-07-18 03:01:39 pgm/odbcreg.exe
    Mon Oct 09 09:53:49 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x      1073152 2006-07-18 03:05:47 pgm/sqlod32.dll
    Mon Oct 09 09:53:50 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x      1130496 2006-07-18 03:06:19 pgm/sqlod32w.dll
    Mon Oct 09 09:53:50 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x        45056 2006-07-18 03:06:35 pgm/sqlodext.dll
    Mon Oct 09 09:53:50 IST 2006 MaxDB sdbinst: extracting: -rwxr-xr-x        73728 2006-07-18 03:06:31 pgm/sqlsp32.dll
    Mon Oct 09 09:53:50 IST 2006 MaxDB sdbinst: checking unpacked archive... ok
    Mon Oct 09 09:53:50 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:53:50 IST 2006 MaxDB sdbinst: starting installation phase of package Webtools 7.6.00.33 32 bit
    Mon Oct 09 09:53:50 IST 2006 MaxDB sdbinst: -
    Mon Oct 09 09:53:50 IST 2006 MaxDB sdbinst:
    Mon Oct 09 09:53:50 IST 2006 MaxDB sdbinst: start real extraction of "C:/sapdb/JP1/_tempLocation/SDBWEB.TGZ"
    Mon Oct 09 09:53:51 IST 2006 MaxDB sdbinst: extracting: drwxr-xr-x            0 2006-07-18 06:37:19 config/
    Mon Oct 09 09:53:51 IST 2006 MaxDB sdbinst: extracting: -rw-rr         3090 2006-07-18 04:53:47 config/mime.types
    Mon Oct 09 09:53:51 IST 2006 MaxDB sdbinst: extracting: -rw-rr         3167 2006-07-18 03:01:17 config/wa.reg
    Mon Oct 09 09:53:51 IST 2006 MaxDB sdbinst: extracting: drwxr-xr-x            0 2006-07-18 06:37:19 Documents/
    Mon Oct 09 09:53:51 IST 2006 MaxDB sdbinst: extracting: -rw-rr         1203 2006-07-18 03:01:17 Documents/index.html
    Mon Oct 09 09:53:51 IST 2006 MaxDB sdbinst: extracting: drwxr-xr-x            0 2006-07-18 06:37:19 Documents/WARoot/
    Mon Oct 09 09:53:51 IST 2006 MaxDB sdbinst: extracting: drwxr-xr-x            0 2006-07-18 06:37:14 Documents/WARoot/HTML/
    Mon Oct 09 09:53:51 IST 2006 MaxDB sdbinst: extracting: -rw-rr        39553 2006-07-18 04:53:35 Documents/WARoot/HTML/DBMBackup.htm
    Mon Oct 09 09:53:51 IST 2006 MaxDB sdbinst: extracting: -rw-rr         5313 2006-07-18 04:53:37 Documents/WARoot/HTML/DBMBadDevspaces.htm
    Mon Oct 09 09:53:51 IST 2006 MaxDB sdbinst: extracting: -rw-rr         3586 2006-07-18 04:53:35 Documents/WARoot/HTML/DBMCommand.htm
    Mon Oct 09 09:53:52 IST 2006 MaxDB sdbinst: extracting: -rw-rr         3756 2006-07-18 04:53:33 Documents/WARoot/HTML/DBMDatabases.htm
    Mon Oct 09 09:53:52 IST 2006 MaxDB sdbinst: extracting: -rw-rr        13373 2006-07-18 04:53:33 Documents/WARoot/HTML/DBMDevspace.htm
    Mon Oct 09 09:53:52 IST 2006 MaxDB sdbinst: extracting: -rw-rr        21425 2006-07-18 04:53:33 Documents/WARoot/HTML/DBMDevspaces.htm
    Mon Oct 09 09:53:52 IST 2006 MaxDB sdbinst: extracting: -rw-rr          568 2006-07-18 04:53:29 Documents/WARoot/HTML/DBMEmpty.htm
    Mon Oct 09 09:53:52 IST 2006 MaxDB sdbinst: extracting: -rw-rr         1596 2006-07-18 04:53:31 Documents/WARoot/HTML/DBMFile.htm
    Mon Oct 09 09:53:52 IST 2006 MaxDB sdbinst: extracting: -rw-rr        16387 2006-07-18 04:53:31 Documents/WARoot/HTML/DBMFiles.htm
    Mon Oct 09 09:53:52 IST 2006 MaxDB sdbinst: extracting: -rw-rr     

    Hi,
    this problem seems to be general. You will get every time the error in the Step if the password specified by user is longer as 9 characters.
    Updating password of SAP<SID>DB in UM_OBJECTS
    Updating OS username to 162492 in UM_OBJECTS
    1
    2
    3
    4
    5
    done with AP7 stuff
    MaxDB: Setting password for user CONTROL
    done
    MaxDB: Setting password for user SUPERDBA
    MaxDB: command failed: <DBMException -24988 ERR_UNKNOWN unknown error>
    Mon Oct 09 09:55:20 IST 2006 MaxDB: rc of changing passwords = 1
    The error has nothing to do with already installed instances ... The password may not be longer as 9 chars!
    Regards Galin

  • MaxDB backup through Backint on Oracle for TSM

    Hello Gurus:
    We are using TSM backint interface for Oracle database. We are in the process of implementing SCM. We would like to schedule MaxDB backup through backint interface for Oracle.
    I checked some forums and configured but backint is not recognizing MaxDB parameter file. Please see below parameter file and error logs.
    *BSI File:*
    BACKINT D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe
    INPUT D:\sapdb\data\wrk\backint\sapdb.in
    OUTPUT D:\sapdb\data\wrk\backint\sapdb.out
    ERROROUTPUT D:\sapdb\data\wrk\backint\sapdb.err
    PARAMETERFILE D:\sapdb\data\wrk\LCD\maxdb_config.par
    ORIGINAL_RUNDIRECTORY L:\sapdb\LCD\sapdata
    *Parameter File - MaxDB_config*
    STAGING AREA:     D:\TEMP\STAGE1 1024000 KB
    FILES PER BACKINT CALL:     2
    BACKINT:     D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe
    PARAMETERFILE OF BACKINT:     D:\oracle\SCD\102\database\initSCD.utl
    HISTORY FILE:     D:\sapdb\data\wrk\BackintHistory
    INPUTFILE OF BACKINT:     D:\sapdb\data\wrk\backint\backint.in
    OUTPUTFILE OF BACKINT:     D:\sapdb\data\wrk\backint\backint.out
    ERRORFILE OF BACKINT:     D:\sapdb\data\wrk\backint\backint.err
    MAXIMAL DELAY OF BACKINT CALL:     30
    Error Logs:
    2010-03-30 17:38:35
    Using environment variable 'TEMP' with value 'C:\Windows\TEMP' as directory for temporary files and pipes.
    Using connection to Backint for MaxDB Interface.
    2010-03-30 17:38:35
    Checking existence and configuration of Backint for MaxDB.
        Using environment variable 'BSI_ENV' with value 'D:\sapdb\data\wrk\LCD\bsi.env' as path of the configuration file of Backint for MaxDB.
        Reading the Backint for MaxDB configuration file 'D:\sapdb\data\wrk\LCD\bsi.env'.
            Found keyword 'BACKINT' with value 'D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe'.
            Found keyword 'INPUT' with value 'D:\sapdb\data\wrk\backint\sapdb.in'.
            Found keyword 'OUTPUT' with value 'D:\sapdb\data\wrk\backint\sapdb.out'.
            Found keyword 'ERROROUTPUT' with value 'D:\sapdb\data\wrk\backint\sapdb.err'.
            Found keyword 'PARAMETERFILE' with value 'D:\sapdb\data\wrk\LCD\maxdb_config.par'.
            Found keyword 'ORIGINAL_RUNDIRECTORY' with value 'L:\sapdb\LCD\sapdata'.
        Finished reading of the Backint for MaxDB configuration file.
        Using 'D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe' as Backint for MaxDB program.
        Using 'D:\sapdb\data\wrk\backint\sapdb.in' as input file for Backint for MaxDB.
        Using 'D:\sapdb\data\wrk\backint\sapdb.out' as output file for Backint for MaxDB.
        Using 'D:\sapdb\data\wrk\backint\sapdb.err' as error output file for Backint for MaxDB.
        Using 'D:\sapdb\data\wrk\LCD\maxdb_config.par' as parameter file for Backint for MaxDB.
        Using '300' seconds as timeout for Backint for MaxDB in the case of success.
        Using '300' seconds as timeout for Backint for MaxDB in the case of failure.
        Using 'L:\sapdb\LCD\sapdata\dbm.knl' as backup history of a database to migrate.
        Using 'L:\sapdb\LCD\sapdata\dbm.ebf' as external backup history of a database to migrate.
        Checking availability of backups using backint's inquire function.
    Check passed successful.
    2010-03-30 17:38:35
    Checking medium.
    Check passed successfully.
    2010-03-30 17:38:35
    Preparing backup.
        Setting environment variable 'BI_CALLER' to value 'DBMSRV'.
        Setting environment variable 'BI_REQUEST' to value 'NEW'.
        Setting environment variable 'BI_BACKUP' to value 'FULL'.
        Constructed Backint for MaxDB call 'D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe -u LCD -f backup -t file -p D:\sapdb\data\wrk\LCD\maxdb_config.par -i D:\sapdb\data\wrk\backint\sapdb.in -c'.
        Created temporary file 'D:\sapdb\data\wrk\backint\sapdb.out' as output for Backint for MaxDB.
        Created temporary file 'D:\sapdb\data\wrk\backint\sapdb.err' as error output for Backint for MaxDB.
        Writing '
    .\pipe\BACKscd #PIPE' to the input file.
    Prepare passed successfully.
    2010-03-30 17:38:35
    Starting database action for the backup.
        Requesting 'SAVE DATA QUICK TO '
    .\pipe\BACKscd' PIPE BLOCKSIZE 8 NO CHECKPOINT MEDIANAME 'Back123'' from db-kernel.
    The database is working on the request.
    2010-03-30 17:38:35
    Waiting until database has prepared the backup.
        Asking for state of database.
        2010-03-30 17:38:35 Database is still preparing the backup.
        Waiting 1 second ... Done.
        Asking for state of database.
        2010-03-30 17:38:36 Database has finished preparation of the backup.
    The database has prepared the backup successfully.
    2010-03-30 17:38:36
    Starting Backint for MaxDB.
        Starting Backint for MaxDB process 'D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe -u LCD -f backup -t file -p D:\sapdb\data\wrk\LCD\maxdb_config.par -i D:\sapdb\data\wrk\backint\sapdb.in -c >>D:\sapdb\data\wrk\backint\sapdb.out 2>>D:\sapdb\data\wrk\backint\sapdb.err'.
        Process was started successfully.
    Backint for MaxDB has been started successfully.
    2010-03-30 17:38:36
    Waiting for end of the backup operation.
        2010-03-30 17:38:36 The backup tool process has finished work with return code 2.
        2010-03-30 17:38:36 The backup tool is not running.
        2010-03-30 17:38:36 The database is working on the request.
        2010-03-30 17:38:36 The database is working on the request.
        2010-03-30 17:38:41 The database is working on the request.
        2010-03-30 17:38:51 The database is working on the request.
        2010-03-30 17:39:06 The database is working on the request.
        2010-03-30 17:39:26 The database is working on the request.
        2010-03-30 17:39:37 Canceling Utility-task after a timeout of 60 seconds elapsed ... OK.
        2010-03-30 17:39:38 The database has finished work on the request.
        Receiving a reply from the database kernel.
        Got the following reply from db-kernel:
            SQL-Code              :-903
    The backup operation has ended.
    2010-03-30 17:39:38
    Filling reply buffer.
        Have encountered error -24920:
            The backup tool failed with 2 as sum of exit codes. The database request was canceled and ended with error -903.
        Constructed the following reply:
            ERR
            -24920,ERR_BACKUPOP: backup operation was unsuccessful
            The backup tool failed with 2 as sum of exit codes. The database request was canceled and ended with error -903.
    Reply buffer filled.
    2010-03-30 17:39:38
    Cleaning up.
        Copying output of Backint for MaxDB to this file.
        **-- Begin of output of Backint for MaxDB (D:\sapdb\data\wrk\backint\sapdb.out)--**
                                     **Data Protection for SAP(R)**
                         **Interface between BRTools and Tivoli Storage Manager***
                         **- Version 6, Release 1, Modification 0.0  for Win x64 -**
                               **Build: 358  compiled on Nov  4 2008**
                    **(c) Copyright IBM Corporation, 1996, 2008, All Rights Reserved.**
            **BKI8310E: The keyword MAXIMAL is not allowed.**
            **BKI1001E: syntax error in file 'D:\sapdb\data\wrk\LCD\maxdb_config.par'. Exiting program.**
            **BKI0020I: End of program at: 03/30/10 17:38:36 .**
            **BKI0021I: Elapsed time: 00 sec .**
            **BKI0024I: Return code is: 2.**       
    End of output of Backint for MaxDB (D:\sapdb\data\wrk\backint\sapdb.out)----
        Removed Backint for MaxDB's temporary output file 'D:\sapdb\data\wrk\backint\sapdb.out'.
        Copying error output of Backint for MaxDB to this file.
    Begin of error output of Backint for MaxDB (D:\sapdb\data\wrk\backint\sapdb.err)----
    End of error output of Backint for MaxDB (D:\sapdb\data\wrk\backint\sapdb.err)----
        Removed Backint for MaxDB's temporary error output file 'D:\sapdb\data\wrk\backint\sapdb.err'.
        Removed the Backint for MaxDB input file 'D:\sapdb\data\wrk\backint\sapdb.in'.
    Have finished clean up successfully.
    Any help will be appreciated.
    Thanks,
    Miral.

    > We are using TSM backint interface for Oracle database. We are in the process of implementing SCM. We would like to schedule MaxDB backup through backint interface for Oracle.
    > *BSI File:*
    >
    > BACKINT D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe
    > *Parameter File - MaxDB_config*
    > STAGING AREA:     D:\TEMP\STAGE1 1024000 KB
    > FILES PER BACKINT CALL:     2
    > BACKINT:     D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe
    >
    >     Using 'D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe' as Backint for MaxDB program.
    > 2010-03-30 17:39:38
    > Cleaning up.
    >     Copying output of Backint for MaxDB to this file.
    >                                  **Data Protection for SAP(R)**
    >                      **Interface between BRTools and Tivoli Storage Manager***
    >                      **- Version 6, Release 1, Modification 0.0  for Win x64 -**
    >         **BKI8310E: The keyword MAXIMAL is not allowed.**
    >         **BKI1001E: syntax error in file 'D:\sapdb\data\wrk\LCD\maxdb_config.par'. Exiting program.**
    >         **BKI0020I: End of program at: 03/30/10 17:38:36 .**
    >         **BKI0021I: Elapsed time: 00 sec .**
    >         **BKI0024I: Return code is: 2.**       
    >
    >     -
    End of output of Backint for MaxDB (D:\sapdb\data\wrk\backint\sapdb.out)----
    >     Removed Backint for MaxDB's temporary output file 'D:\sapdb\data\wrk\backint\sapdb.out'.
    >     Copying error output of Backint for MaxDB to this file.
    >     -
    Begin of error output of Backint for MaxDB (D:\sapdb\data\wrk\backint\sapdb.err)----
    @Markus: thanks for the hint with the quote-formatting option!
    Concerning the issue:
    Sorry, but you misunderstood the way how the general BACKINT for Oracle interface is used with MaxDB.
    See, MaxDB comes with a own BACKINT executable.
    This is a enhanced BACKINT tools that allows pipes as data input channels - which is not supported by the Backint for Oracle.
    The MaxDB Backint serves as a adapter program between the MaxDB Kernel and the backint for Oracle program.
    So instead of
    BACKINT:     D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe
    you should point it to the MaxDB provided adapater program.
    I propose to revisit the documentation on that topic [Connecting to a Backint for Oracle Interface |http://maxdb.sap.com/doc/7_7/45/746a5712e14022e10000000a1553f6/content.htm].
    best regards,
    Lars

  • Backup error occured, Error code 3700 "hostfile_error"

    HI,
    We are trying to MaxDB database backup to tape and getting below error.
    ===================================================================================================
    ERR
    -24988,ERR_SQL: SQL error
    -104,DBM command impossible at this time
    3,Data backup failed
    Servertask Info: because Error in backup task occured
    Job 1 (Backup / Restore Medium Task) [executing] WaitingT204 Result=3700
    Error in backup task occured, Error code 3700 "hostfile_error"
    Backupmedium #1 (
    .\pipe\backup) I/O Error
    Backup error occured, Error code 3700 "hostfile_error"
    ===================================================================================================
    I went through the previous threads regarding the same error but couldn't find a solution.
    System Info is Win 2008, MaxDB version 7.7.07.14.
    Here is the complete log, please suggest what can be done.
    ===================================================================================================
    DBA Action starts:
    Timestamp: 20110831100408   Function: sda   Object: DATA
    2011-08-31 10:04:08
    Using environment variable 'TEMP' with value 'C:\Windows\TEMP' as directory for temporary files and pipes.
    Using connection to Backint for MaxDB Interface.
    2011-08-31 10:04:09
    Checking existence and configuration of Backint for MaxDB.
        Using environment variable 'BSI_ENV' with value 'G:\sapdb\data\wrk\MXP\bsi.env' as path of the configuration file of Backint
        Reading the Backint for MaxDB configuration file 'G:\sapdb\data\wrk\MXP\bsi.env'.
            Found keyword 'BACKINT' with value 'D:\sapdb\MXP\db\bin\backint.exe'.
            Found keyword 'INPUT' with value 'G:\sapdb\data\wrk\backint\sapdb.in'.
            Found keyword 'OUTPUT' with value 'G:\sapdb\data\wrk\backint\sapdb.out'.
            Found keyword 'ERROROUTPUT' with value 'G:\sapdb\data\wrk\backint\sapdb.err'.
            Found keyword 'PARAMETERFILE' with value 'G:\sapdb\data\wrk\MXP\maxdb_config.par'.
            Found keyword 'ORIGINAL_RUNDIRECTORY' with value 'G:\sapdb\MXP\sapdata'.
        Finished reading of the Backint for MaxDB configuration file.
        Using 'D:\sapdb\MXP\db\bin\backint.exe' as Backint for MaxDB program.
        Using 'G:\sapdb\data\wrk\backint\sapdb.in' as input file for Backint for MaxDB.
        Using 'G:\sapdb\data\wrk\backint\sapdb.out' as output file for Backint for MaxDB.
        Using 'G:\sapdb\data\wrk\backint\sapdb.err' as error output file for Backint for MaxDB.
        Using 'G:\sapdb\data\wrk\MXP\maxdb_config.par' as parameter file for Backint for MaxDB.
        Using '300' seconds as timeout for Backint for MaxDB in the case of success.
        Using '300' seconds as timeout for Backint for MaxDB in the case of failure.
        Using 'G:\sapdb\MXP\sapdata\dbm.knl' as backup history of a database to migrate.
        Using 'G:\sapdb\MXP\sapdata\dbm.ebf' as external backup history of a database to migrate.
        Checking availability of backups using backint's inquire function.
    Check passed successful.
    2011-08-31 10:04:09
    Checking medium.
    Check passed successfully.
    2011-08-31 10:04:09
    Preparing backup.
        Setting environment variable 'BI_CALLER' to value 'DBMSRV'.
        Setting environment variable 'BI_REQUEST' to value 'NEW'.
        Setting environment variable 'BI_BACKUP' to value 'FULL'.
        Constructed Backint for MaxDB call 'D:\sapdb\MXP\db\bin\backint.exe -u MXP -f backup -t file -p G:\sapdb\data\wrk\MXP\maxdb_
        Created temporary file 'G:\sapdb\data\wrk\backint\sapdb.out' as output for Backint for MaxDB.
        Created temporary file 'G:\sapdb\data\wrk\backint\sapdb.err' as error output for Backint for MaxDB.
        Writing '
    .\pipe\backup #PIPE' to the input file.
    Prepare passed successfully.
    2011-08-31 10:04:09
    Starting database action for
         the backup.
        Requesting 'SAVE DATA QUICK TO '
    .\pipe\backup' PIPE BLOCKSIZE 8 NO CHECKPOINT MEDIANAME 'BackupMXP'' from db-kernel.
    The database is working on the request.
    2011-08-31 10:04:09
    Waiting until database has prepared the backup.
        Asking for state of database.
        2011-08-31 10:04:09 Database is still preparing the backup.
        Waiting 1 second ...
        Done.
        Asking for state of database.
        2011-08-31 10:04:10 Database has finished preparation of the backup.
    The database has prepared the backup successfully.
    2011-08-31 10:04:10
    Starting Backint for MaxDB.
        Starting Backint for MaxDB process 'D:\sapdb\MXP\db\bin\backint.exe -u MXP -f backup -t file -p G:\sapdb\data\wrk\MXP\maxdb_
        Process was started successfully.
    Backint for MaxDB has been started successfully.
    2011-08-31 10:04:10
    Waiting for end of the backup operation.
        2011-08-31 10:04:10 The backup tool is running.
        2011-08-31 10:04:10 The database is working on the request.
        2011-08-31 10:04:15 The backup tool is running.
        2011-08-31 10:04:15 The database is working on the request.
        2011-08-31 10:04:25 The backup tool is running.
        2011-08-31 10:04:25 The database is working on the request.
        2011-08-31 10:04:40 The backup tool is running.
        2011-08-31 10:04:40 The database is working on the request.
        2011-08-31 10:05:00 The backup tool is running.
        2011-08-31 10:05:00 The database is working on the request.
        2011-08-31 10:05:13 The backup tool process has finished work with return code 2.
        2011-08-31 10:05:13 The database has finished work on the request.
        Receiving a reply from the database kernel.
        Got the following reply from db-kernel:
            SQL-Code              :-903
    The backup operation has ended.
    2011-08-31 10:05:13
    Filling reply buffer.
        Have encountered error -24920:
            The backup tool failed with 2 as sum of exit codes. The database request failed with error -903.
        Constructed the following reply:
            ERR
            -24920,ERR_BACKUPOP: backup operation was unsuccessful
            The backup tool failed with 2 as sum of exit codes. The database request failed with error -903.
    Reply buffer filled.
    2011-08-31 10:05:13
    Cleaning up.
        Copying output of Backint for MaxDB to this file.
    Begin of output of Backint for MaxDB (G:\sapdb\data\wrk\backint\sapdb.out)----
            Reading parameter file G:\sapdb\data\wrk\MXP\maxdb_config.par.
            Using staging area D:\TEMP\STAGE1 with a size of 1048576000 bytes.
            Using staging area D:\TEMP\STAGE2 with a size of 1048576000 bytes.
            Using 2 file per Backint for Oracle call.
            Using C:\Program Files\Tivoli\TSM\tdp_r3\ora64\backint.exe as Backint for Oracle.
            Using G:\sapdb\data\wrk\MXP\initMXP.utl as parameterfile of Backint for Oracle.
            Using G:\sapdb\data\wrk\MXP\BackintHistory.txt as history file.
            Using G:\sapdb\data\wrk\backint\backint1.in as input of Backint for Oracle.
            Using G:\sapdb\data\wrk\backint\backint1.out as output of Backint for Oracle.
            Using G:\sapdb\data\wrk\backint\backint1.err as error output of Backint for Oracle.
            Using a maximal delay for a Backint for Oracle call of 3600 seconds.
            Reading input file G:\sapdb\data\wrk\backint\sapdb.in.
            Backing up pipe
    .\pipe\backup.
            Found 1 entry in the input file.
            Starting the backup.
            Starting pipe2file program(s).
            Waiting for creation of temporary files.
            1 temporary file is available for backup.
            Calling Backint for Oracle at 2011-08-31 10:05:12.
            Calling 'C:\Program Files\Tivoli\TSM\tdp_r3\ora64\backint.exe -u MXP -f backup -t file -p G:\sapdb\data\wrk\MXP\initMXP.
            Backint for Oracle ended at 2011-08-31 10:05:13 with return code 2.
            Backint for Oracle output:
            Backint for Oracle output:                          Data Protection for SAP(R)
            Backint for Oracle output:
            Backint for Oracle output:              Interface between BR*Tools and Tivoli Storage Manager
            Backint for Oracle output:              - Version 6, Release 1, Modification 0.0  for Win x64 -
            Backint for Oracle output:                    Build: 358  compiled on Nov  4 2008
            Backint for Oracle output:         (c) Copyright IBM Corporation, 1996, 2008, All Rights Reserved.
            Backint for Oracle output:
            Backint for Oracle output: BKI2027I: Using TSM-API version 6.2.3.1 (compiled with 5.3.2.0).
            Backint for Oracle output: BKI2000I: Successfully connected to ProLE on port tdpr3ora64.
            Backint for Oracle output: BKI0005I: Start of program at: 08/31/11 10:05:12 .
            Backint for Oracle output: BKI1216E: There are no backup management classes available.
            Backint for Oracle output: BKI1215I: Average transmission rate was 0.000 GB/h (0.000 MB/sec).
            Backint for Oracle output: BKI1227I: Average compression factor was 1.000.
            Backint for Oracle output: BKI0020I: End of program at: 08/31/11 10:05:13 .
            Backint for Oracle output: BKI0021I: Elapsed time: 01 sec .
            Backint for Oracle output: BKI0024I: Return code is: 2.
            Backint for Oracle output:
            Backint for Oracle error output:
            Finished the backup unsuccessfully.
            #ERROR
    .\pipe\backup
    End of output of Backint for MaxDB (G:\sapdb\data\wrk\backint\sapdb.out)----
        Removed Backint for MaxDB's temporary output file 'G:\sapdb\data\wrk\backint\sapdb.out'.
        Copying error output of Backint for MaxDB to this file.
    Begin of error output of Backint for MaxDB (G:\sapdb\data\wrk\backint\sapdb.err)----
            Backint for Oracle was unsuccessful.
    End of error output of Backint for MaxDB (G:\sapdb\data\wrk\backint\sapdb.err)----
        Removed Backint for MaxDB's temporary error output file 'G:\sapdb\data\wrk\backint\sapdb.err'.
        Removed the Backint for MaxDB input file 'G:\sapdb\data\wrk\backint\sapdb.in'.
    Have finished clean up successfully.
    SAVE/RESTORE request:
    SAVE DATA CANCEL
    SAVE/RESTORE request accepted:
    OK
    SAVE/RESTORE result:
    ERR
    -24988,ERR_SQL: SQL error
    -104,DBM command impossible at this time
    3,Data backup failed
    Servertask Info: because Error in backup task occured
    Job 1 (Backup / Restore Medium Task) [executing] WaitingT204 Result=3700
    Error in backup task occured, Error code 3700 "hostfile_error"
    Backupmedium #1 (
    .\pipe\backup) I/O Error
    Backup error occured, Error code 3700 "hostfile_error"
    DBA Action ends:
    Timestamp: 20110831100513   State:    Failure
    ===================================================================================================

    Hi Markus,
    Thanks for quick response. I did checked KNLMSG file and it has XML file kind of information where as dbm.prt has some information and here it is
    =================================================================================================
    2011-08-31 10:18:30 0x00009ecc INF          1 DBMSrvCo A DBM Server client connection was established at 2011-08-31 10:18:29 (client process has process ID 24352 on computer 10.1.47.21).
    2011-08-31 10:18:30 0x00009ecc INF        283 DBMSrv   Command 'auto_extend show' is being executed.
    2011-08-31 10:18:30 0x00009ecc INF        419 DBMSrv   Command 'auto_extend' has ended with return code 0.
    2011-08-31 10:18:30 0x00009ecc INF        283 DBMSrv   Command 'auto_update_statistics show' is being executed.
    2011-08-31 10:18:31 0x00009ecc INF        419 DBMSrv   Command 'auto_update_statistics' has ended with return code 0.
    2011-08-31 10:18:41 0x00009ecc INF        283 DBMSrv   Command 'backup_save "Backup" DATA RECOVERY' is being executed.
    2011-08-31 10:18:42 0x00009ecc INF          1 DBMKnl   Sending an administrative statement to the database
                        0x00009ecc INF          8 DBMKnl   Statement:  SAVE DATA QUICK TO '
    .\pipe\backup' PIPE BLOCKSIZE 8 NO CHECKPOINT MEDIANAME 'Backup'
    2011-08-31 10:19:47 0x00009ecc ERR          3 DBMKnl   Received the result of an administrative statement from the database
                        0x00009ecc ERR          9 DBMKnl   Statement:  SAVE DATA QUICK TO '
    .\pipe\backup' PIPE BLOCKSIZE 8 NO CHECKPOINT MEDIANAME 'Backup'
                        0x00009ecc ERR         10 DBMKnl   Returncode: -903
                        0x00009ecc ERR          5 DBMKnl   Errortext:  Host file I/O error
    2011-08-31 10:19:47 0x00009ecc ERR     -24580 DBMSrv   ERR_COMMAND_FAILED: Command 'backup_save' has ended and failed with return code -24920.
                        0x00009ecc ERR     -24920 DBMSrv   ERR_BACKUPOP: backup operation was unsuccessful
                        0x00009ecc ERR     -24778 DBMSrv   The backup tool failed with 2 as sum of exit codes. The database request failed with error -903.
    2011-08-31 10:19:53 0x00009ecc INF          2 DBMSrvCo A DBM Server client connection was released (client process has process ID 24352 on computer 10.1.47.21).
    2011-08-31 10:19:53 0x00009ecc INF          1 DBMKnl   Sending an administrative statement to the database
                        0x00009ecc INF          8 DBMKnl   Statement:  SAVE DATA CANCEL
    2011-08-31 10:19:53 0x00009ecc ERR          3 DBMKnl   Received the result of an administrative statement from the database
                        0x00009ecc ERR          9 DBMKnl   Statement:  SAVE DATA CANCEL
                        0x00009ecc ERR         10 DBMKnl   Returncode: -104
                        0x00009ecc ERR          5 DBMKnl   Errortext:  DBM command impossible at this time

  • Backint - MaxDB

    Hello all,
    we are trying to backup our MaxDB using the backint interface. Unfortunately, the backup process fails with the error messages shown in the appended KNLDIAG log and EXTERNAL BACKUP log
    KNLDIAG
    0:32:53 31276     11560 COMMUNIC Releasing  T132
    2008-07-31 20:32:53 31276     12827 COMMUNIC wait for connection T132
    2008-07-31 20:32:54 31258     11561 COMMUNIC Connecting T125 local 3626
    2008-07-31 20:32:54 31276     12929 TASKING  Task T125 started
    2008-07-31 20:32:54 31276     11007 COMMUNIC wait for connection T125
    2008-07-31 20:32:54 31276     11561 COMMUNIC Connected  T125 local 3626
    2008-07-31 20:32:54 31276     11560 COMMUNIC Releasing  T125
    2008-07-31 20:32:54 31276     12827 COMMUNIC wait for connection T125
    2008-07-31 20:32:55  3634 ERR 11000 devio    write error (fd = 54): Broken pipe
    2008-07-31 20:32:55 31272     11000 vasynclo '/tmp/backintdb-pipe' devno 34 T72
    2008-07-31 20:32:55 31259     12822 TASKING  Thread 3634 joining
    2008-07-31 20:32:55  3634     11566 stop     DEVi stopped
    2008-07-31 20:32:55 31272     52024 SAVE     63992 pages -> "/tmp/backintdb-pipe"
    2008-07-31 20:32:55 31276     52012 SAVE     new tape required 4300
    2008-07-31 20:32:55 31276         1 Backup   Backupmedium #1 (/tmp/backintdb-pipe) end of file
    2008-07-31 20:32:55 31276         6 KernelCo  +   Backup error occured, Errorcode 4300 "new_hostfile_required"
    2008-07-31 20:32:56 31276     12929 TASKING  Task T142 started
    2008-07-31 20:32:56 31258     11561 COMMUNIC Connecting T142 local 3626
    2008-07-31 20:32:56 31276     11007 COMMUNIC wait for connection T142
    2008-07-31 20:32:56 31276     11561 COMMUNIC Connected  T142 local 3626
    2008-07-31 20:32:56 31276     11560 COMMUNIC Releasing  T142
    2008-07-31 20:32:56 31276     12827 COMMUNIC wait for connection T142
    2008-07-31 20:36:23 31276     11000 vasynclo '/sapdata/SOM/DISKD0001' devno 17 T143
    2008-07-31 20:36:23 31259     12822 TASKING  Thread 3629 joining
    EXTERNAL BACKUP
    2008-07-31 20:32:36
    Setting environment variable 'TEMP' for the directory for temporary files and pipes to default ''.
    Setting environment variable 'TMP' for the directory for temporary files and pipes to default ''.
    Using connection to Backint for MaxDB Interface.
    2008-07-31 20:32:36
    Checking existence and configuration of Backint for MaxDB.
        Reading the Backint for MaxDB configuration file '/sapdb/data/wrk/SOM/bsi.env'.
            Found keyword 'BACKINT' with value '/sapdb/SOM/db/bin/backint'.
            Found keyword 'INPUT' with value '/tmp/tsm-logs/som-backint4maxdb.in'.
            Found keyword 'OUTPUT' with value '/tmp/tsm-logs/som-backint4maxdb.out'.
            Found keyword 'ERROROUTPUT' with value '/tmp/tsm-logs/som-backint4maxdb.err'.
            Found keyword 'PARAMETERFILE' with value '/sapdb/SOM/db/bin/backintmaxdbconfig.par'.
            Found keyword 'TIMEOUT_SUCCESS' with value '600'.
            Found keyword 'TIMEOUT_FAILURE' with value '300'.
            Found keyword 'ORIGINAL_RUNDIRECTORY' with value '/sapdb/data/wrk/SOM'.
        Finished reading of the Backint for MaxDB configuration file.
        Using '/sapdb/SOM/db/bin/backint' as Backint for MaxDB program.
        Using '/tmp/tsm-logs/som-backint4maxdb.in' as input file for Backint for MaxDB.
        Using '/tmp/tsm-logs/som-backint4maxdb.out' as output file for Backint for MaxDB.
        Using '/tmp/tsm-logs/som-backint4maxdb.err' as error output file for Backint for MaxDB.
        Using '/sapdb/SOM/db/bin/backintmaxdbconfig.par' as parameter file for Backint for MaxDB.
        Using '600' seconds as timeout for Backint for MaxDB in the case of success.
        Using '300' seconds as timeout for Backint for MaxDB in the case of failure.
        Using '/sapdb/data/wrk/SOM/dbm.knl' as backup history of a database to migrate.
        Using '/sapdb/data/wrk/SOM/dbm.ebf' as external backup history of a database to migrate.
        Checking availability of backups using backint's inquire function.
    Check passed successful.
    2008-07-31 20:32:36
    Checking medium.
    Check passed successfully.
    2008-07-31 20:32:36
    Preparing backup.
        Setting environment variable 'BI_CALLER' to value 'DBMSRV'.
        Setting environment variable 'BI_REQUEST' to value 'NEW'.
        Setting environment variable 'BI_BACKUP' to value 'FULL'.
        Constructed Backint for MaxDB call '/sapdb/SOM/db/bin/backint -u SOM -f backup -t file -p /sapdb/SOM/db/bin/backintmaxdbconfig.par -i /tmp/tsm-logs/som-backint4maxdb.in -c'.
        Created temporary file '/tmp/tsm-logs/som-backint4maxdb.out' as output for Backint for MaxDB.
        Created temporary file '/tmp/tsm-logs/som-backint4maxdb.err' as error output for Backint for MaxDB.
        Writing '/tmp/backintdb-pipe #PIPE' to the input file.
    Prepare passed successfully.
    2008-07-31 20:32:36
    Creating pipes for data transfer.
        Creating pipe '/tmp/backintdb-pipe' ... Done.
    All data transfer pipes have been created.
    2008-07-31 20:32:36
    Starting database action for the backup.
        Requesting 'SAVE DATA QUICK TO '/tmp/backintdb-pipe' PIPE BLOCKSIZE 8 NO CHECKPOINT MEDIANAME 'backindb'' from db-kernel.
    The database is working on the request.
    2008-07-31 20:32:36
    Waiting until database has prepared the backup.
        Asking for state of database.
        2008-07-31 20:32:36 Database is still preparing the backup.
        Waiting 1 second ... Done.
        Asking for state of database.
        2008-07-31 20:32:37 Database is still preparing the backup.
        Waiting 2 seconds ... Done.
        Asking for state of database.
        2008-07-31 20:32:39 Database is still preparing the backup.
        Waiting 3 seconds ... Done.
        Asking for state of database.
        2008-07-31 20:32:42 Database is still preparing the backup.
        Waiting 4 seconds ... Done.
        Asking for state of database.
        2008-07-31 20:32:46 Database is still preparing the backup.
        Waiting 5 seconds ... Done.
        Asking for state of database.
        2008-07-31 20:32:51 Database has finished preparation of the backup.
    The database has prepared the backup successfully.
    2008-07-31 20:32:51
    Starting Backint for MaxDB.
        Starting Backint for MaxDB process '/sapdb/SOM/db/bin/backint -u SOM -f backup -t file -p /sapdb/SOM/db/bin/backintmaxdbconfig.par -i /tmp/tsm-logs/som-backint4maxdb.in -c >>/tmp/tsm-logs/som-backint4maxdb.out 2>>/tmp/tsm-logs/som-backint4maxdb.err'.
        Process was started successfully.
    Backint for MaxDB has been started successfully.
    2008-07-31 20:32:51
    Waiting for end of the backup operation.
        2008-07-31 20:32:51 The backup tool is running.
        2008-07-31 20:32:51 The database is working on the request.
        2008-07-31 20:32:56 The backup tool process has finished work with return code 2.
        2008-07-31 20:32:56 The backup tool is not running.
        2008-07-31 20:32:56 The database has finished work on the request.
        Receiving a reply from the database kernel.
        Got the following reply from db-kernel:
            SQL-Code              :-8020
            Date                  :20080731
            Time                  :00203248
            Database              :SOM
            Server                :bssomp02
            KernelVersion         :Kernel    7.6.00   Build 035-123-139-084
            PagesTransfered       :64000
            PagesLeft             :4907326
            MediaName             :backindb
            Location              :/tmp/backintdb-pipe
            Errortext             :end of file
            Label                 :DAT_000000055
            IsConsistent          :true
            FirstLogPageNo        :3321207
            DBStamp1Date          :20080731
            DBStamp1Time          :00203244
            BDPageCount           :4971302
            DevicesUsed           :1
            DatabaseID            :bssomp02:SOM_20070910_162640
            Max Used Data Page   
            Converter Page Count  :2676
    The backup operation has ended.
    2008-07-31 20:32:56
    Filling reply buffer.
        Have encountered error -24920:
            The backup tool failed with 2 as sum of exit codes. The database request failed with error -8020.
        Constructed the following reply:
            ERR
            -24920,ERR_BACKUPOP: backup operation was unsuccessful
            The backup tool failed with 2 as sum of exit codes. The database request failed with error -8020.
    Reply buffer filled.
    It seem to me that it is a MUST to use the Tivoli Data Protection for the MaxDB. Is anybody out there to tell me if this is right? Or ist it possible to directly transfer backup data from MaxDB to Tivoli Storage Manager (TSM) via a pipe?
    Thanks and kind regards
    Anette Feierabend

    > 2008-07-31 20:32:55  3634 ERR 11000 devio    write error (fd = 54): Broken pipe
    > 2008-07-31 20:32:55 31272     11000 vasynclo '/tmp/backintdb-pipe' devno 34 T72
    > 2008-07-31 20:32:55 31259     12822 TASKING  Thread 3634 joining
    > 2008-07-31 20:32:55  3634     11566 stop     DEVi stopped
    > 2008-07-31 20:32:55 31272     52024 SAVE     63992 pages -> "/tmp/backintdb-pipe"
    > 2008-07-31 20:32:55 31276     52012 SAVE     new tape required 4300
    > 2008-07-31 20:32:55 31276         1 Backup   Backupmedium #1 (/tmp/backintdb-pipe) end of file
    > 2008-07-31 20:32:55 31276         6 KernelCo  +   Backup error occured, Errorcode 4300 "new_hostfile_required"
    >     Receiving a reply from the database kernel.
    >     Got the following reply from db-kernel:
    >         SQL-Code              :-8020
    >         KernelVersion         :Kernel    7.6.00   Build 035-123-139-084
    > PagesTransfered       :64000
    > PagesLeft             :4907326
    >         MediaName             :backindb
    >         Location              :/tmp/backintdb-pipe
    >         Errortext             :end of file
    >         Label                 :DAT_000000055
    >         IsConsistent          :true
    >         FirstLogPageNo        :3321207
    >         DBStamp1Date          :20080731
    >         DBStamp1Time          :00203244
    >         BDPageCount           :4971302
    >         DevicesUsed           :1
    >         DatabaseID            :bssomp02:SOM_20070910_162640
    >         Max Used Data Page   
    >         Converter Page Count  :2676
    > The backup operation has ended.
    >
    > 2008-07-31 20:32:56
    > Filling reply buffer.
    >     Have encountered error -24920:
    >         The backup tool failed with 2 as sum of exit codes. The database request failed with error -8020.
    >
    >     Constructed the following reply:
    >         ERR
    >         -24920,ERR_BACKUPOP: backup operation was unsuccessful
    >         The backup tool failed with 2 as sum of exit codes. The database request failed with error -8020.
    > Reply buffer filled.
    Hi Anette,
    it looks pretty much as if the backup medium definition for the MaxDB contains a maximum size. Thus the database will request a new medium once the setup maximum pages for the medium (64000 in your case) are reached.
    Error -8020 says exactly this: "Next medium needed"
    Therefore I would propose to check the backup medium.
    > It seem to me that it is a MUST to use the Tivoli Data Protection for the MaxDB. Is anybody out there to tell me if this is right? Or ist it possible to directly transfer backup data from MaxDB to Tivoli Storage Manager (TSM) via a pipe?
    No, that's wrong - once you setup the backup medium correctly it will work.
    Best regards,
    Lars
    p.s.
    If you're an SAP customer -> open a support message.
    And - of course - you're using a very old version of MaxDB. Get the current patch here in the SDN download area or via SAP Service Marketplace!

  • Backup using backint fails for maxdb

    Hi All, I have configured backint for backup of maxdb for content server 640. I configured it as per the documents available, created the configuration fiale and the parameter file. Created the backup medium in dbmgui. Now when i try to run the backup using the pipe am getting the above mentioned error. Please find below the dbm.ebp log for the same...
    more dbm.ebp 2009-10-22 02:06:08 Setting environment variable 'TEMP' for the directory for temporary files and pi pes to default ''. Setting environment variable 'TMP' for the directory for temporary files and pip es to default ''. Using connection to Backint for MaxDB Interface. 2009-10-22 02:06:08 Checking existence and configuration of Backint for MaxDB. Using configuration variable 'BSI_ENV' = '/sapdb/CFC/lcbackup/apoatlas.env' as path of the configuration file of Backint for MaxDB. Setting environment variable 'BSI_ENV' for the path of the configuration fil e of Backint for MaxDB to configuration value '/sapdb/CFC/lcbackup/apoatlas.env' . Reading the Backint for MaxDB configuration file '/sapdb/CFC/lcbackup/apoatl as.env'. Found keyword 'BACKINT' with value '/sapdb/CFC/db/bin/backint'. Found keyword 'INPUT' with value '/tmp/backint4sapdbCFC.in'. Found keyword 'OUTPUT' with value '/tmp/backint4sapdbCFC.out'. Found keyword 'ERROROUTPUT' with value '/tmp/backint4sapdbCFC.err'. Found keyword 'PARAMETERFILE' with value '/sapdb/CFC/lcbackup/param.cfg' . Found keyword 'TIMEOUT_SUCCESS' with value '1800'. Found keyword 'TIMEOUT_FAILURE' with value '1800'. Finished reading of the Backint for MaxDB configuration file. Using '/sapdb/CFC/db/bin/backint' as Backint for MaxDB program. Using '/tmp/backint4sapdbCFC.in' as input file for Backint for MaxDB. Using '/tmp/backint4sapdbCFC.out' as output file for Backint for MaxDB. Using '/tmp/backint4sapdbCFC.err' as error output file for Backint for MaxDB . Using '/sapdb/CFC/lcbackup/param.cfg' as parameter file for Backint for MaxD B. Using '1800' seconds as timeout for Backint for MaxDB in the case of success . Using '1800' seconds as timeout for Backint for MaxDB in the case of failure . Using '/sapdb/data/wrk/CFC/dbm.knl' as backup history of a database to migra te. Using '/sapdb/data/wrk/CFC/dbm.ebf' as external backup history of a database to migrate. Checking availability of backups using backint's inquire function. Check passed successful. 2009-10-22 02:06:08 Checking medium. Check passed successfully. 2009-10-22 02:06:08 Preparing backup. Setting environment variable 'BI_CALLER' to value 'DBMSRV'. Setting environment variable 'BI_REQUEST' to value 'NEW'. Setting environment variable 'BI_BACKUP' to value 'FULL'. Constructed Backint for MaxDB call '/sapdb/CFC/db/bin/backint -u CFC -f back up -t file -p /sapdb/CFC/lcbackup/param.cfg -i /tmp/backint4sapdbCFC.in -c'. Created temporary file '/tmp/backint4sapdbCFC.out' as output for Backint for MaxDB. Created temporary file '/tmp/backint4sapdbCFC.err' as error output for Backi nt for MaxDB. Writing '/sapdb/CFC/lcbackup/pipe1 #PIPE' to the input file. Writing '/sapdb/CFC/lcbackup/pipe2 #PIPE' to the input file. Prepare passed successfully. 2009-10-22 02:06:08 Creating pipes for data transfer. Creating pipe '/sapdb/CFC/lcbackup/pipe1' ... Done. Creating pipe '/sapdb/CFC/lcbackup/pipe2' ... Done. All data transfer pipes have been created. 2009-10-22 02:06:08 Starting database action for the backup. Requesting 'SAVE DATA QUICK TO '/sapdb/CFC/lcbackup/pipe1' PIPE,'/sapdb/CFC/ lcbackup/pipe2' PIPE BLOCKSIZE 8 NO CHECKPOINT MEDIANAME 'BACKINT_ONLINE1'' from db-kernel. The database is working on the request. 2009-10-22 02:06:09 Waiting until database has prepared the backup. Asking for state of database. 2009-10-22 02:06:09 Database is still preparing the backup. Waiting 1 second ... Done. Asking for state of database. 2009-10-22 02:06:10 Database is still preparing the backup. Waiting 2 seconds ... Done. Asking for state of database. 2009-10-22 02:06:12 Database has finished preparation of the backup. The database has prepared the backup successfully. 2009-10-22 02:06:12 Starting Backint for MaxDB. Starting Backint for MaxDB process '/sapdb/CFC/db/bin/backint -u CFC -f back up -t file -p /sapdb/CFC/lcbackup/param.cfg -i /tmp/backint4sapdbCFC.in -c >>/tm p/backint4sapdbCFC.out 2>>/tmp/backint4sapdbCFC.err'. Process was started successfully. Backint for MaxDB has been started successfully. 2009-10-22 02:06:12 Waiting for end of the backup operation. 2009-10-22 02:06:12 The backup tool is running. 2009-10-22 02:06:12 The database is working on the request. 2009-10-22 02:06:14 The backup tool process has finished work with return co de 2. 2009-10-22 02:06:17 The database is working on the request. 2009-10-22 02:06:27 The database is working on the request. 2009-10-22 02:06:42 The database is working on the request. 2009-10-22 02:07:02 The database is working on the request. 2009-10-22 02:07:15 Canceling Utility-task after a timeout of 60 seconds ela psed ... OK. 2009-10-22 02:07:17 The database has finished work on the request. Receiving a reply from the database kernel. Got the following reply from db-kernel: SQL-Code :-903 The backup operation has ended. 2009-10-22 02:07:17 Filling reply buffer. Have encountered error -24920: The backup tool failed with 2 as sum of exit codes. The database request was canceled and ended with error -903. Constructed the following reply: ERR -24920,ERR_BACKUPOP: backup operation was unsuccessful The backup tool failed with 2 as sum of exit codes. The database request was canceled and ended with error -903. Reply buffer filled. 2009-10-22 02:07:17 Cleaning up. Removing data transfer pipes. Removing data transfer pipe /sapdb/CFC/lcbackup/pipe2 ... Done. Removing data transfer pipe /sapdb/CFC/lcbackup/pipe1 ... Done. Removed data transfer pipes successfully. Copying output of Backint for MaxDB to this file. -
    Begin of output of Backint for MaxDB (/tmp/backint4sapdbCFC.out)- -
    Data Protection for mySAP(R) Interface between BR*Tools and Tivoli Storage Manager - Version 5, Release 4, Modification 0.0 for Linux x86_64 - Build: 303 compiled on Nov 16 2006 (c) Copyright IBM Corporation, 1996, 2006, All Rights Reserved. BKI0008E: The environment variable BI_CALLER is not set correctely. The current value is "DBMSRV" usage: backint -p  [-u ] [-f ] [-t ] [-i ] [-o ] [-c] where:  backint utility user  backup | restore | inquire | password | delete  file | file_online  parameter file for backup utility  name of a text file that defines the objects default: STDIN  Pool for processing messages and the results of the executed function. default: STOUT BKI0020I: End of program at: Thu 22 Oct 2009 02:06:14 AM EDT . BKI0021I: Elapsed time: 01 sec . BKI0024I: Return code is: 2. -
    End of output of Backint for MaxDB (/tmp/backint4sapdbCFC.out)- - Removed Backint for MaxDB's temporary output file '/tmp/backint4sapdbCFC.out '. Copying error output of Backint for MaxDB to this file. - Begin of error output of Backint for MaxDB (/tmp/backint4sapdbCFC .err) - End of error output of Backint for MaxDB (/tmp/backint4sapdbCFC.e rr)--
    Removed Backint for MaxDB's temporary error output file '/tmp/backint4sapdbC FC.err'. Removed the Backint for MaxDB input file '/tmp/backint4sapdbCFC.in'. Have finished clean up successfully.
    Also, is there any specification about the user permissions and about how the backup should be run?

    Hi Lars,
    I understand that its a clumpsy over here, but i already have raised an OSS message and SAP said, that they cannot support this issue with backint. If you can provide me with an email id, i can send you the log files which would be easy to read.
    My issue is that am not able run backup for maxdb of content server 640 using the backint tool.
    I have created the configuration file and the parameter file as per the specifications from http://maxdb.sap.com/doc/7_7/a9/8a1ef21e4b402bb76ff75bb559a98a/content.htm and http://maxdb.sap.com/doc/7_7/50/075205962843f69b9ec41f34427be7/content.htm.
    THe server is registered to the TSM server. Now when i run the wizard to take the backup using the backint tool, it gives the error "Begin of output of Backint for MaxDB (/tmp/backint4sapdbCFC.out)- -
    Data Protection for mySAP(R) Interface between BR*Tools and Tivoli Storage Manager - Version 5, Release 4, Modification 0.0 for Linux x86_64 - Build: 303 compiled on Nov 16 2006 (c) Copyright IBM Corporation, 1996, 2006, All Rights Reserved. BKI0008E: The environment variable BI_CALLER is not set correctely. The current value is "DBMSRV" usage: backint -p  [-u ] [-f ] [-t ] [-i ] [-o ] [-c] where:  backint utility user  backup | restore | inquire | password | delete  file | file_online  parameter file for backup utility  name of a text file that defines the objects default: STDIN  Pool for processing messages and the results of the executed function. default: STOUT BKI0020I: End of program at: Thu 22 Oct 2009 02:06:14 AM EDT . BKI0021I: Elapsed time: 01 sec . BKI0024I: Return code is: 2. -
    End of output of Backint for MaxDB (/tmp/backint4sapdbCFC.out)- - Removed Backint for MaxDB's temporary output file '/tmp/backint4sapdbCFC.out '. Copying error output of Backint for MaxDB to this file. - Begin of error output of Backint for MaxDB (/tmp/backint4sapdbCFC .err) - End of error output of Backint for MaxDB (/tmp/backint4sapdbCFC.e rr)--
    Removed Backint for MaxDB's temporary error output file '/tmp/backint4sapdbC FC.err'. Removed the Backint for MaxDB input file '/tmp/backint4sapdbCFC.in'. Have finished clean up successfully."
    I think this should be fine to read...
    Krishna KK

  • Error while taking a backup

    Dear Experts,
    I have facing a problem since 3 days while i am taking a full offline backup.
    This was noticed thru db12.
    We take our backup using Tivoli backup manager.
    We are facing this problem on our XI production server.
    When i observed the logs i found and understood that it had problems with backing up the datafiles 7, 8, 27, 28, 29, 32, 33 and 35.
    But i have no clue why it is happening suddenly..
    I have copied the detailed log here in below for your reference.
    I request everyone to suggest me on this...
    Points for sure...
    The log is as follows
    *BR0051I BRBACKUP 7.00 (28)*
    *BR0055I Start of database backup: bdxqpyuy.aff 2008-04-08 05.00.00*
    *BR0484I BRBACKUP log file: F:/ORACLE/XIP\sapbackup\bdxqpyuy.aff*
    *BR0477I Oracle pfile F:\oracle\product\10.2.0\db_1\database\initXIP.ora created from spfile F:\oracle\product\10.2.0\db_1\database\spfileXIP.ora*
    *BR0101I Parameters*
    *Name                           Value*
    *oracle_sid                     XIP*
    *oracle_home                    F:\oracle\product\10.2.0\db_1*
    *oracle_profile                 F:\oracle\product\10.2.0\db_1\database\initXIP.ora*
    *sapdata_home                   F:/ORACLE/XIP*
    *sap_profile                    F:\oracle\product\10.2.0\db_1\database\initXIP.sap*
    *backup_mode                    ALL*
    *backup_type                    offline_force*
    *backup_dev_type                util_file*
    *util_par_file                  F:\oracle\product\10.2.0\db_1\database\offline_initXIP.utl*
    *system_info                    Administrator ATHOMEXIPRD Windows 5.2 Build 3790 Service Pack 1 Intel*
    *oracle_info                    XIP 10.2.0.2.0 8192 11243 159240520 ATHOMEXIPRD UTF8 UTF8*
    *sap_info                       700 SAPSR3 0002LK0003XIP0011N20363738850013NetWeaver_ORA*
    *make_info                      NTintel OCI_10201_SHARE Oct 23 2007*
    *command_line                   brbackup -u system/********* -c force -t offline_force -m all -p initXIP.sap -r F:\oracle\product\10.2.0\db_1\database\offline_initXIP.utl*
    *BR0116I ARCHIVE LOG LIST before backup for database instance XIP*
    *Parameter                      Value*
    *Database log mode              Archive Mode*
    *Automatic archival             Enabled*
    *Archive destination            F:\oracle\XIP\oraarch\XIParch*
    *Archive format                 ARC%S_%R.%T*
    *Oldest online log sequence     11240*
    *Next log sequence to archive   11243*
    *Current log sequence           11243            SCN: 159240520*
    *Database block size            8192             Thread: 1*
    *Current system change number   159255509        ResetId: 620435934*
    *BR0118I Tablespaces and data files*
    *Tablespace     TS-Status  F-Status  File                                                       Size   Id.     Device  Link    Type       MaxSize     IncrSize  BlkSize*
    *PSAPSR3        ONLINE*    ONLINE    C:\ORACLE\XIP\SAPDATA8\SR3_35\SR3.DATA35             3145736192   46           2  NOLINK  FILE             0            0     8192*
    *PSAPSR3        ONLINE*    ONLINE    C:\ORACLE\XIP\SAPDATA8\SR3_36\SR3.DATA36             2147491840   47           2  NOLINK  FILE             0            0     8192*
    *PSAPSR3        ONLINE*    ONLINE    C:\ORACLE\XIP\SAPDATA8\SR3_37\SR3.DATA37              524296192   48           2  NOLINK  FILE             0            0     8192*
    *PSAPSR3        ONLINE*    ONLINE    D:\ORACLE\XIP\SAPDATA7\SR3_28\SR3.DATA28             4294975488   39           3  NOLINK  FILE             0            0     8192*
    *PSAPSR3        ONLINE*    ONLINE    D:\ORACLE\XIP\SAPDATA7\SR3_29\SR3.DATA29             4294975488   40           3  NOLINK  FILE             0            0     8192*
    *PSAPSR3        ONLINE*    ONLINE    D:\ORACLE\XIP\SAPDATA7\SR3_30\SR3.DATA30             4294975488   41           3  NOLINK  FILE             0            0     8192*
    *PSAPSR3        ONLINE*    ONLINE    D:\ORACLE\XIP\SAPDATA7\SR3_31\SR3.DATA31             4294975488   42           3  NOLINK  FILE             0            0     8192*
    *PSAPSR3        ONLINE*    ONLINE    D:\ORACLE\XIP\SAPDATA7\SR3_32\SR3.DATA32             3932168192   43           3  NOLINK  FILE             0            0     8192*
    *PSAPSR3        ONLINE*    ONLINE    D:\ORACLE\XIP\SAPDATA7\SR3_33\SR3.DATA33             3670024192   44           3  NOLINK  FILE             0            0     8192*
    *PSAPSR3        ONLINE*    ONLINE    D:\ORACLE\XIP\SAPDATA7\SR3_34\SR3.DATA34             2097160192   45           3  NOLINK  FILE             0            0     8192*
    *PSAPSR3        ONLINE*    ONLINE    E:\ORACLE\XIP\SAPDATA5\SR3_10\SR3.DATA10             2147491840   21           4  NOLINK  FILE             0            0     8192*
    *PSAPSR3        ONLINE*    ONLINE    E:\ORACLE\XIP\SAPDATA5\SR3_11\SR3.DATA11             2147491840   22           4  NOLINK  FILE             0            0     8192*
    *PSAPSR3        ONLINE*    ONLINE    E:\ORACLE\XIP\SAPDATA5\SR3_12\SR3.DATA12             2097160192   23           4  NOLINK  FILE             0            0     8192*
    *PSAPSR3        ONLINE*    ONLINE    E:\ORACLE\XIP\SAPDATA5\SR3_13\SR3.DATA13             2097160192   24           4  NOLINK  FILE             0            0     8192*
    *PSAPSR3        ONLINE*    ONLINE    E:\ORACLE\XIP\SAPDATA5\SR3_14\SR3.DATA14             2097160192   25           4  NOLINK  FILE             0            0     8192*
    *PSAPSR3        ONLINE*    ONLINE    E:\ORACLE\XIP\SAPDATA5\SR3_15\SR3.DATA15             2097160192   26           4  NOLINK  FILE             0            0     8192*
    *PSAPSR3        ONLINE*    ONLINE    E:\ORACLE\XIP\SAPDATA5\SR3_16\SR3.DATA16             2097160192   27           4  NOLINK  FILE             0            0     8192*
    *PSAPSR3        ONLINE*    ONLINE    E:\ORACLE\XIP\SAPDATA5\SR3_17\SR3.DATA17             2097160192   28           4  NOLINK  FILE             0            0     8192*
    *PSAPSR3        ONLINE*    ONLINE    E:\ORACLE\XIP\SAPDATA5\SR3_18\SR3.DATA18             2097160192   29           4  NOLINK  FILE             0            0     8192*
    *PSAPSR3        ONLINE*    ONLINE    E:\ORACLE\XIP\SAPDATA5\SR3_19\SR3.DATA19             2147491840   30           4  NOLINK  FILE             0            0     8192*
    *PSAPSR3        ONLINE*    ONLINE    E:\ORACLE\XIP\SAPDATA5\SR3_20\SR3.DATA20             2147491840   31           4  NOLINK  FILE             0            0     8192*
    *PSAPSR3        ONLINE*    ONLINE    E:\ORACLE\XIP\SAPDATA5\SR3_8\SR3.DATA8               4194312192   19           4  NOLINK  FILE             0            0     8192*
    *PSAPSR3        ONLINE*    ONLINE    E:\ORACLE\XIP\SAPDATA5\SR3_9\SR3.DATA9              10737426432   20           4  NOLINK  FILE             0            0     8192*
    *PSAPSR3        ONLINE*    ONLINE+   F:\ORACLE\XIP\SAPDATA2\SR3_1\SR3.DATA1              10485768192    4           5  NOLINK  FILE   10485760000     20971520     8192*
    *PSAPSR3        ONLINE*    ONLINE+   F:\ORACLE\XIP\SAPDATA2\SR3_2\SR3.DATA2              10485768192    5           5  NOLINK  FILE   10485760000     20971520     8192*
    *PSAPSR3        ONLINE*    ONLINE+   F:\ORACLE\XIP\SAPDATA2\SR3_3\SR3.DATA3              10485768192    6           5  NOLINK  FILE   10485760000     20971520     8192*
    *PSAPSR3        ONLINE*    ONLINE+   F:\ORACLE\XIP\SAPDATA2\SR3_4\SR3.DATA4              10485768192    7           5  NOLINK  FILE   10485760000     20971520     8192*
    *PSAPSR3        ONLINE*    ONLINE+   F:\ORACLE\XIP\SAPDATA2\SR3_5\SR3.DATA5              10485768192   16           5  NOLINK  FILE   10485760000     20971520     8192*
    *PSAPSR3        ONLINE*    ONLINE+   F:\ORACLE\XIP\SAPDATA2\SR3_6\SR3.DATA6              10485768192   17           5  NOLINK  FILE   10485760000     20971520     8192*
    *PSAPSR3        ONLINE*    ONLINE    F:\ORACLE\XIP\SAPDATA2\SR3_7\SR3.DATA7               4194312192   18           5  NOLINK  FILE             0            0     8192*
    *PSAPSR3        ONLINE*    ONLINE    G:\ORACLE\XIP\SAPDATA6\SR3_21\SR3.DATA21             2147491840   32           6  NOLINK  FILE             0            0     8192*
    *PSAPSR3        ONLINE*    ONLINE    G:\ORACLE\XIP\SAPDATA6\SR3_22\SR3.DATA22             2147491840   33           6  NOLINK  FILE             0            0     8192*
    *PSAPSR3        ONLINE*    ONLINE    G:\ORACLE\XIP\SAPDATA6\SR3_23\SR3.DATA23             2147491840   34           6  NOLINK  FILE             0            0     8192*
    *PSAPSR3        ONLINE*    ONLINE    G:\ORACLE\XIP\SAPDATA6\SR3_24\SR3.DATA24             2147491840   35           6  NOLINK  FILE             0            0     8192*
    *PSAPSR3        ONLINE*    ONLINE    G:\ORACLE\XIP\SAPDATA6\SR3_25\SR3.DATA25             2147491840   36           6  NOLINK  FILE             0            0     8192*
    *PSAPSR3        ONLINE*    ONLINE    G:\ORACLE\XIP\SAPDATA6\SR3_26\SR3.DATA26             4294975488   37           6  NOLINK  FILE             0            0     8192*
    *PSAPSR3        ONLINE*    ONLINE    G:\ORACLE\XIP\SAPDATA6\SR3_27\SR3.DATA27             3145736192   38           6  NOLINK  FILE             0            0     8192*
    *PSAPSR3700     ONLINE*    ONLINE+   F:\ORACLE\XIP\SAPDATA3\SR3700_1\SR3700.DATA1         2537562112    8           5  NOLINK  FILE   10485760000     20971520     8192*
    *PSAPSR3700     ONLINE*    ONLINE+   F:\ORACLE\XIP\SAPDATA3\SR3700_2\SR3700.DATA2         2600476672    9           5  NOLINK  FILE   10485760000     20971520     8192*
    *PSAPSR3700     ONLINE*    ONLINE+   F:\ORACLE\XIP\SAPDATA3\SR3700_3\SR3700.DATA3         2516590592   10           5  NOLINK  FILE   10485760000     20971520     8192*
    *PSAPSR3700     ONLINE*    ONLINE+   F:\ORACLE\XIP\SAPDATA3\SR3700_4\SR3700.DATA4         2537562112   11           5  NOLINK  FILE   10485760000     20971520     8192*
    *PSAPSR3DB      ONLINE*    ONLINE+   F:\ORACLE\XIP\SAPDATA4\SR3DB_1\SR3DB.DATA1           2181046272   13           5  NOLINK  FILE   10485760000     20971520     8192*
    *PSAPSR3DB      ONLINE*    ONLINE+   F:\ORACLE\XIP\SAPDATA4\SR3DB_2\SR3DB.DATA2           2222989312   14           5  NOLINK  FILE   10485760000     20971520     8192*
    *PSAPSR3DB      ONLINE*    ONLINE+   F:\ORACLE\XIP\SAPDATA4\SR3DB_3\SR3DB.DATA3           1132470272   15           5  NOLINK  FILE   10485760000     20971520     8192*
    *PSAPSR3USR     ONLINE*    ONLINE+   F:\ORACLE\XIP\SAPDATA4\SR3USR_1\SR3USR.DATA1           20979712   12           5  NOLINK  FILE   10485760000     20971520     8192*
    *PSAPTEMP       ONLINE#    ONLINE+   F:\ORACLE\XIP\SAPDATA1\TEMP_1\TEMP.DATA1             1048584192   -1           5  NOLINK  FILE   10485760000     20971520     8192*
    *PSAPUNDO       ONLINE-    ONLINE+   F:\ORACLE\XIP\SAPDATA1\UNDO_1\UNDO.DATA1             4294975488    2           5  NOLINK  FILE   10485760000     20971520     8192*
    *SYSAUX         ONLINE*    ONLINE+   F:\ORACLE\XIP\SAPDATA1\SYSAUX_1\SYSAUX.DATA1          251666432    3           5  NOLINK  FILE   10485760000     20971520     8192*
    *SYSTEM         ONLINE*    SYSTEM+   F:\ORACLE\XIP\SAPDATA1\SYSTEM_1\SYSTEM.DATA1          524296192    1           5  NOLINK  FILE   10485760000     20971520     8192*
    *BR0119I Redo log files*
    *File                                                Size  Group     Device  Status    Link    Type*
    *E:\ORACLE\XIP\ORIGLOGA\LOG_G11M1.DBF            52429312    1            4  INUSE     NOLINK  FILE*
    *E:\ORACLE\XIP\MIRRLOGA\LOG_G11M2.DBF            52429312    1            4  INUSE     NOLINK  FILE*
    *E:\ORACLE\XIP\ORIGLOGB\LOG_G12M1.DBF            52429312    2            4  INUSE     NOLINK  FILE*
    *E:\ORACLE\XIP\MIRRLOGB\LOG_G12M2.DBF            52429312    2            4  INUSE     NOLINK  FILE*
    *E:\ORACLE\XIP\ORIGLOGA\LOG_G13M1.DBF            52429312    3            4  INUSE     NOLINK  FILE*
    *E:\ORACLE\XIP\MIRRLOGA\LOG_G13M2.DBF            52429312    3            4  INUSE     NOLINK  FILE*
    *E:\ORACLE\XIP\ORIGLOGB\LOG_G14M1.DBF            52429312    4            4  INUSE     NOLINK  FILE*
    *E:\ORACLE\XIP\MIRRLOGB\LOG_G14M2.DBF            52429312    4            4  INUSE     NOLINK  FILE*
    *BR0120I Control files*
    *File                                                Size   Id.      Device  Link    Type*
    *E:\oracle\XIP\origlogA\cntrl\cntlrXIP.dbf       16596992    0            4  NOLINK  FILE*
    *E:\oracle\XIP\origlogB\cntrl\cntrlXIP.dbf       16596992    0            4  NOLINK  FILE*
    *F:\oracle\XIP\sapdata1\cntrl\cntrlXIP.dbf       16596992    0            5  NOLINK  FILE*
    *BR0616I Tablespaces in table TSORA for SAP owner SAPSR3:*
    *PSAPSR3, PSAPSR3700, PSAPSR3USR*
    *BR0280I BRBACKUP time stamp: 2008-04-08 05.00.03*
    *BR0057I Backup of database: XIP*
    *BR0058I BRBACKUP action ID: bdxqpyuy*
    *BR0059I BRBACKUP function ID: aff*
    *BR0110I Backup mode: ALL*
    *BR0077I Database files for backup:*
    *E:\ORACLE\XIP\ORIGLOGA\LOG_G11M1.DBF*
    *E:\ORACLE\XIP\ORIGLOGB\LOG_G12M1.DBF*
    *E:\ORACLE\XIP\ORIGLOGA\LOG_G13M1.DBF*
    *E:\ORACLE\XIP\ORIGLOGB\LOG_G14M1.DBF*
    *E:\oracle\XIP\origlogA\cntrl\cntlrXIP.dbf*
    *BR0061I 54 files found for backup, total size 170022.213 MB*
    *BR0143I Backup type: offline_force*
    *BR0130I Backup device type: util_file*
    *BR0109I Files will be saved by backup utility*
    *BR0134I Unattended mode with 'force' active - no operator confirmation allowed*
    *BR0280I BRBACKUP time stamp: 2008-04-08 05.00.03*
    *BR0307I Shutting down database instance XIP ...*
    *BR0280I BRBACKUP time stamp: 2008-04-08 05.01.36*
    *BR0308I Shutdown of database instance XIP successful*
    *BR0280I BRBACKUP time stamp: 2008-04-08 05.01.37*
    *BR0229I Calling backup utility with function 'backup'...*
    *BR0278I Command output of 'backint -u XIP -f backup -i F:/ORACLE/XIP\sapbackup\.bdxqpyuy.lst -t file -p F:\oracle\product\10.2.0\db_1\database\offline_initXIP.utl -c':*
                             *Data Protection for mySAP(R)*
                 *Interface between BR*Tools and Tivoli Storage Manager*
                 *- Version 5, Release 4, Modification 0.0  for WinNT -*
                       *Build: 303  compiled on Nov 16 2006*
            *(c) Copyright IBM Corporation, 1996, 2006, All Rights Reserved.*
    *BKI2027I: Using TSM-API version 5.4.0.2 (compiled with 5.3.0.0).*
    *BKI2000I: Successfully connected to ProLE on port tdpr3ora.*
    *BKI0005I: Start of program at: 04/08/08 05:01:37 .*
      *-- Parameters --*
    Input File            : F:\ORACLE\XIP\sapbackup\.bdxqpyuy.lst
    Profile               : F:\oracle\product\10.2.0\db_1\database\offline_initXIP.utl
    Configfile            : F:\oracle\product\10.2.0\db_1\database\initXIP.bki
    Manual sorting file   : disabled
    Tracefile             : disabled
    Traceflags            : disabled
    Parallel sessions     : 1
    Multiplexed files     : 1
    RL compression        : 0
    Exit on error         : disabled
    BATCH                 : enabled
    Buffer size           : 32768
    Buffer Copy Mode      : SIMPLE
    Redologcopies         : disabled
    Versioning            : enabled
    Current Version      : 74
    Versions to keep     : 4
    Delete Versions      : <= 70
    Backup Type           : file
    TSM log server        : disabled
    TSM server            : 172.16.1.8:NLKSRVR08 with 2 sessions configured, using 1 session
    TSM client node      :
    Days for backup      : Sun Mon Tue Wed Thu Fri Sat
    Backup mgmt class    : OFFLINE_ATHOMEXIPRD
    Archiv mgmt class    : OFFLINE_ATHOMEXIPRD
    BKI2017I: Blocksize is set to 32768 bytes
    BKI5016I: Time: 04/08/08 05:01:37 New TSM session created: MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08, type: SIMPLE
    BKI0027I: Time: 04/08/08 05:01:37 Object: 1 of 54 in process: E:\ORACLE\XIP\SAPDATA5\SR3_9\SR3.DATA9 Size: 10.000 GB, MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08 .
    BKI0023I: Time: 04/08/08 05:06:51 Done: 10.000 GB (6.0 %) of 166.037 GB. Estimated end time: 04/08/08 06:28:30.
    BKI0053I: Time: 04/08/08 05:06:51 Object: 1 of 54 done: E:\ORACLE\XIP\SAPDATA5\SR3_9\SR3.DATA9 with: 10.000 GB saved with description XIPOF_A0FEROGUNL.
    BR0280I BRBACKUP time stamp: 2008-04-08 05.06.51
    #FILE..... E:\ORACLE\XIP\SAPDATA5\SR3_9\SR3.DATA9
    #SAVED.... XIPOF_A0FEROGUNL
    BKI0027I: Time: 04/08/08 05:06:51 Object: 2 of 54 in process: F:\ORACLE\XIP\SAPDATA2\SR3_6\SR3.DATA6 Size: 9.766 GB, MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08 .
    BKI0023I: Time: 04/08/08 05:22:13 Done: 19.766 GB (11.9 %) of 166.037 GB. Estimated end time: 04/08/08 07:54:39.
    BKI0053I: Time: 04/08/08 05:22:13 Object: 2 of 54 done: F:\ORACLE\XIP\SAPDATA2\SR3_6\SR3.DATA6 with: 9.766 GB saved with description XIPOF_A0FEROGUNL.
    BR0280I BRBACKUP time stamp: 2008-04-08 05.22.13
    #FILE..... F:\ORACLE\XIP\SAPDATA2\SR3_6\SR3.DATA6
    #SAVED.... XIPOF_A0FEROGUNL
    BKI0027I: Time: 04/08/08 05:22:13 Object: 3 of 54 in process: F:\ORACLE\XIP\SAPDATA2\SR3_5\SR3.DATA5 Size: 9.766 GB, MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08 .
    BKI0023I: Time: 04/08/08 05:40:21 Done: 29.531 GB (17.8 %) of 166.037 GB. Estimated end time: 04/08/08 08:39:23.
    BKI0053I: Time: 04/08/08 05:40:21 Object: 3 of 54 done: F:\ORACLE\XIP\SAPDATA2\SR3_5\SR3.DATA5 with: 9.766 GB saved with description XIPOF_A0FEROGUNL.
    BR0280I BRBACKUP time stamp: 2008-04-08 05.40.21
    #FILE..... F:\ORACLE\XIP\SAPDATA2\SR3_5\SR3.DATA5
    #SAVED.... XIPOF_A0FEROGUNL
    BKI0027I: Time: 04/08/08 05:40:21 Object: 4 of 54 in process: F:\ORACLE\XIP\SAPDATA2\SR3_4\SR3.DATA4 Size: 9.766 GB, MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08 .
    BKI0023I: Time: 04/08/08 05:45:30 Done: 39.297 GB (23.7 %) of 166.037 GB. Estimated end time: 04/08/08 08:07:01.
    BKI0053I: Time: 04/08/08 05:45:30 Object: 4 of 54 done: F:\ORACLE\XIP\SAPDATA2\SR3_4\SR3.DATA4 with: 9.766 GB saved with description XIPOF_A0FEROGUNL.
    BR0280I BRBACKUP time stamp: 2008-04-08 05.45.30
    #FILE..... F:\ORACLE\XIP\SAPDATA2\SR3_4\SR3.DATA4
    #SAVED.... XIPOF_A0FEROGUNL
    BKI0027I: Time: 04/08/08 05:45:30 Object: 5 of 54 in process: F:\ORACLE\XIP\SAPDATA2\SR3_3\SR3.DATA3 Size: 9.766 GB, MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08 .
    BKI0023I: Time: 04/08/08 05:50:05 Done: 49.063 GB (29.5 %) of 166.037 GB. Estimated end time: 04/08/08 07:45:38.
    BKI0053I: Time: 04/08/08 05:50:05 Object: 5 of 54 done: F:\ORACLE\XIP\SAPDATA2\SR3_3\SR3.DATA3 with: 9.766 GB saved with description XIPOF_A0FEROGUNL.
    BR0280I BRBACKUP time stamp: 2008-04-08 05.50.05
    #FILE..... F:\ORACLE\XIP\SAPDATA2\SR3_3\SR3.DATA3
    #SAVED.... XIPOF_A0FEROGUNL
    BKI0027I: Time: 04/08/08 05:50:05 Object: 6 of 54 in process: F:\ORACLE\XIP\SAPDATA2\SR3_2\SR3.DATA2 Size: 9.766 GB, MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08 .
    BKI0023I: Time: 04/08/08 05:54:29 Done: 58.828 GB (35.4 %) of 166.037 GB. Estimated end time: 04/08/08 07:30:49.
    BKI0053I: Time: 04/08/08 05:54:29 Object: 6 of 54 done: F:\ORACLE\XIP\SAPDATA2\SR3_2\SR3.DATA2 with: 9.766 GB saved with description XIPOF_A0FEROGUNL.
    BR0280I BRBACKUP time stamp: 2008-04-08 05.54.29
    #FILE..... F:\ORACLE\XIP\SAPDATA2\SR3_2\SR3.DATA2
    #SAVED.... XIPOF_A0FEROGUNL
    BKI0027I: Time: 04/08/08 05:54:29 Object: 7 of 54 in process: F:\ORACLE\XIP\SAPDATA2\SR3_1\SR3.DATA1 Size: 9.766 GB, MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08 .
    BKI0023I: Time: 04/08/08 06:01:46 Done: 68.594 GB (41.3 %) of 166.037 GB. Estimated end time: 04/08/08 07:27:12.
    BKI0053I: Time: 04/08/08 06:01:46 Object: 7 of 54 done: F:\ORACLE\XIP\SAPDATA2\SR3_1\SR3.DATA1 with: 9.766 GB saved with description XIPOF_A0FEROGUNL.
    BR0280I BRBACKUP time stamp: 2008-04-08 06.01.46
    #FILE..... F:\ORACLE\XIP\SAPDATA2\SR3_1\SR3.DATA1
    #SAVED.... XIPOF_A0FEROGUNL
    BKI0027I: Time: 04/08/08 06:01:46 Object: 8 of 54 in process: F:\ORACLE\XIP\SAPDATA1\UNDO_1\UNDO.DATA1 Size: 4.000 GB, MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08 .
    BKI0023I: Time: 04/08/08 06:04:47 Done: 72.594 GB (43.7 %) of 166.037 GB. Estimated end time: 04/08/08 07:26:05.
    BKI0053I: Time: 04/08/08 06:04:47 Object: 8 of 54 done: F:\ORACLE\XIP\SAPDATA1\UNDO_1\UNDO.DATA1 with: 4.000 GB saved with description XIPOF_A0FEROGUNL.
    BR0280I BRBACKUP time stamp: 2008-04-08 06.04.47
    #FILE..... F:\ORACLE\XIP\SAPDATA1\UNDO_1\UNDO.DATA1
    #SAVED.... XIPOF_A0FEROGUNL
    BKI0027I: Time: 04/08/08 06:04:47 Object: 9 of 54 in process: G:\ORACLE\XIP\SAPDATA6\SR3_26\SR3.DATA26 Size: 4.000 GB, MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08 .
    BKI0023I: Time: 04/08/08 06:06:06 Done: 76.594 GB (46.1 %) of 166.037 GB. Estimated end time: 04/08/08 07:21:24.
    BKI0053I: Time: 04/08/08 06:06:06 Object: 9 of 54 done: G:\ORACLE\XIP\SAPDATA6\SR3_26\SR3.DATA26 with: 4.000 GB saved with description XIPOF_A0FEROGUNL.
    BR0280I BRBACKUP time stamp: 2008-04-08 06.06.06
    #FILE..... G:\ORACLE\XIP\SAPDATA6\SR3_26\SR3.DATA26
    #SAVED.... XIPOF_A0FEROGUNL
    BKI0027I: Time: 04/08/08 06:06:06 Object: 10 of 54 in process: D:\ORACLE\XIP\SAPDATA7\SR3_31\SR3.DATA31 Size: 4.000 GB, MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08 .
    BKI0023I: Time: 04/08/08 06:07:19 Done: 80.594 GB (48.5 %) of 166.037 GB. Estimated end time: 04/08/08 07:16:58.
    BKI0053I: Time: 04/08/08 06:07:19 Object: 10 of 54 done: D:\ORACLE\XIP\SAPDATA7\SR3_31\SR3.DATA31 with: 4.000 GB saved with description XIPOF_A0FEROGUNL.
    BR0280I BRBACKUP time stamp: 2008-04-08 06.07.19
    #FILE..... D:\ORACLE\XIP\SAPDATA7\SR3_31\SR3.DATA31
    #SAVED.... XIPOF_A0FEROGUNL
    BKI0027I: Time: 04/08/08 06:07:19 Object: 11 of 54 in process: D:\ORACLE\XIP\SAPDATA7\SR3_30\SR3.DATA30 Size: 4.000 GB, MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08 .
    BKI0023I: Time: 04/08/08 06:08:30 Done: 84.594 GB (50.9 %) of 166.037 GB. Estimated end time: 04/08/08 07:12:53.
    BKI0053I: Time: 04/08/08 06:08:30 Object: 11 of 54 done: D:\ORACLE\XIP\SAPDATA7\SR3_30\SR3.DATA30 with: 4.000 GB saved with description XIPOF_A0FEROGUNL.
    BR0280I BRBACKUP time stamp: 2008-04-08 06.08.30
    #FILE..... D:\ORACLE\XIP\SAPDATA7\SR3_30\SR3.DATA30
    #SAVED.... XIPOF_A0FEROGUNL
    BKI0027I: Time: 04/08/08 06:08:30 Object: 12 of 54 in process: D:\ORACLE\XIP\SAPDATA7\SR3_29\SR3.DATA29 Size: 4.000 GB, MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08 .
    BKI4007E: File 'D:\ORACLE\XIP\SAPDATA7\SR3_29\SR3.DATA29' cannot be read Reason:  errno(1450)  Insufficient system resources exist to complete the requested service.
    BKI1208W: The object 'D:\ORACLE\XIP\SAPDATA7\SR3_29\SR3.DATA29' will be retried [2].
    BKI0027I: Time: 04/08/08 06:09:36 Object: 12 of 54 in process: D:\ORACLE\XIP\SAPDATA7\SR3_29\SR3.DATA29 Size: 4.000 GB, MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08 .
    BKI4007E: File 'D:\ORACLE\XIP\SAPDATA7\SR3_29\SR3.DATA29' cannot be read Reason:  errno(1450)  Insufficient system resources exist to complete the requested service.
    BKI1208W: The object 'D:\ORACLE\XIP\SAPDATA7\SR3_29\SR3.DATA29' will be retried [3].
    BKI0027I: Time: 04/08/08 06:16:11 Object: 12 of 54 in process: D:\ORACLE\XIP\SAPDATA7\SR3_29\SR3.DATA29 Size: 4.000 GB, MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08 .
    BKI4007E: File 'D:\ORACLE\XIP\SAPDATA7\SR3_29\SR3.DATA29' cannot be read Reason:  errno(1450)  Insufficient system resources exist to complete the requested service.
    BKI1208W: The object 'D:\ORACLE\XIP\SAPDATA7\SR3_29\SR3.DATA29' will be retried [4].
    BKI0027I: Time: 04/08/08 06:17:26 Object: 12 of 54 in process: D:\ORACLE\XIP\SAPDATA7\SR3_29\SR3.DATA29 Size: 4.000 GB, MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08 .
    BKI4007E: File 'D:\ORACLE\XIP\SAPDATA7\SR3_29\SR3.DATA29' cannot be read Reason:  errno(1450)  Insufficient system resources exist to complete the requested service.
    BKI1231E: Maximum number of retries for file D:\ORACLE\XIP\SAPDATA7\SR3_29\SR3.DATA29 exceeded.
    BR0233E Backup utility has reported an error while saving file D:\ORACLE\XIP\SAPDATA7\SR3_29\SR3.DATA29
    BKI0027I: Time: 04/08/08 06:18:46 Object: 13 of 54 in process: D:\ORACLE\XIP\SAPDATA7\SR3_28\SR3.DATA28 Size: 4.000 GB, MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08 .
    BKI4007E: File 'D:\ORACLE\XIP\SAPDATA7\SR3_28\SR3.DATA28' cannot be read Reason:  errno(1450)  Insufficient system resources exist to complete the requested service.
    BKI1208W: The object 'D:\ORACLE\XIP\SAPDATA7\SR3_28\SR3.DATA28' will be retried [2].
    BKI0027I: Time: 04/08/08 06:19:04 Object: 13 of 54 in process: D:\ORACLE\XIP\SAPDATA7\SR3_28\SR3.DATA28 Size: 4.000 GB, MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08 .
    BKI4007E: File 'D:\ORACLE\XIP\SAPDATA7\SR3_28\SR3.DATA28' cannot be read Reason:  errno(1450)  Insufficient system resources exist to complete the requested service.
    BKI1208W: The object 'D:\ORACLE\XIP\SAPDATA7\SR3_28\SR3.DATA28' will be retried [3].
    BKI0027I: Time: 04/08/08 06:19:07 Object: 13 of 54 in process: D:\ORACLE\XIP\SAPDATA7\SR3_28\SR3.DATA28 Size: 4.000 GB, MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08 .
    BKI4007E: File 'D:\ORACLE\XIP\SAPDATA7\SR3_28\SR3.DATA28' cannot be read Reason:  errno(1450)  Insufficient system resources exist to complete the requested service.
    BKI1208W: The object 'D:\ORACLE\XIP\SAPDATA7\SR3_28\SR3.DATA28' will be retried [4].
    BKI0027I: Time: 04/08/08 06:19:12 Object: 13 of 54 in process: D:\ORACLE\XIP\SAPDATA7\SR3_28\SR3.DATA28 Size: 4.000 GB, MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08 .
    BKI4007E: File 'D:\ORACLE\XIP\SAPDATA7\SR3_28\SR3.DATA28' cannot be read Reason:  errno(1450)  Insufficient system resources exist to complete the requested service.
    BKI1231E: Maximum number of retries for file D:\ORACLE\XIP\SAPDATA7\SR3_28\SR3.DATA28 exceeded.
    BR0233E Backup utility has reported an error while saving file D:\ORACLE\XIP\SAPDATA7\SR3_28\SR3.DATA28
    BKI0027I: Time: 04/08/08 06:19:16 Object: 14 of 54 in process: F:\ORACLE\XIP\SAPDATA2\SR3_7\SR3.DATA7 Size: 3.906 GB, MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08 .
    BKI4007E: File 'F:\ORACLE\XIP\SAPDATA2\SR3_7\SR3.DATA7' cannot be read Reason:  errno(1450)  Insufficient system resources exist to complete the requested service.
    BKI1208W: The object 'F:\ORACLE\XIP\SAPDATA2\SR3_7\SR3.DATA7' will be retried [2].
    BKI0027I: Time: 04/08/08 06:19:20 Object: 14 of 54 in process: F:\ORACLE\XIP\SAPDATA2\SR3_7\SR3.DATA7 Size: 3.906 GB, MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08 .
    BKI4007E: File 'F:\ORACLE\XIP\SAPDATA2\SR3_7\SR3.DATA7' cannot be read Reason:  errno(1450)  Insufficient system resources exist to complete the requested service.
    BKI1208W: The object 'F:\ORACLE\XIP\SAPDATA2\SR3_7\SR3.DATA7' will be retried [3].
    BKI0027I: Time: 04/08/08 06:19:50 Object: 14 of 54 in process: F:\ORACLE\XIP\SAPDATA2\SR3_7\SR3.DATA7 Size: 3.906 GB, MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08 .
    BKI4007E: File 'F:\ORACLE\XIP\SAPDATA2\SR3_7\SR3.DATA7' cannot be read Reason:  errno(1450)  Insufficient system resources exist to complete the requested service.
    BKI1208W: The object 'F:\ORACLE\XIP\SAPDATA2\SR3_7\SR3.DATA7' will be retried [4].
    BKI0027I: Time: 04/08/08 06:20:51 Object: 14 of 54 in process: F:\ORACLE\XIP\SAPDATA2\SR3_7\SR3.DATA7 Size: 3.906 GB, MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08 .
    BKI4007E: File 'F:\ORACLE\XIP\SAPDATA2\SR3_7\SR3.DATA7' cannot be read Reason:  errno(1450)  Insufficient system resources exist to complete the requested service.
    BKI1231E: Maximum number of retries for file F:\ORACLE\XIP\SAPDATA2\SR3_7\SR3.DATA7 exceeded.
    BR0233E Backup utility has reported an error while saving file F:\ORACLE\XIP\SAPDATA2\SR3_7\SR3.DATA7
    BKI0027I: Time: 04/08/08 06:22:02 Object: 15 of 54 in process: E:\ORACLE\XIP\SAPDATA5\SR3_8\SR3.DATA8 Size: 3.906 GB, MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08 .
    BKI4007E: File 'E:\ORACLE\XIP\SAPDATA5\SR3_8\SR3.DATA8' cannot be read Reason:  errno(1450)  Insufficient system resources exist to complete the requested service.
    BKI1208W: The object 'E:\ORACLE\XIP\SAPDATA5\SR3_8\SR3.DATA8' will be retried [2].
    BKI0027I: Time: 04/08/08 06:22:33 Object: 15 of 54 in process: E:\ORACLE\XIP\SAPDATA5\SR3_8\SR3.DATA8 Size: 3.906 GB, MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08 .
    BKI4007E: File 'E:\ORACLE\XIP\SAPDATA5\SR3_8\SR3.DATA8' cannot be read Reason:  errno(1450)  Insufficient system resources exist to complete the requested service.
    BKI1208W: The object 'E:\ORACLE\XIP\SAPDATA5\SR3_8\SR3.DATA8' will be retried [3].
    BKI0027I: Time: 04/08/08 06:22:48 Object: 15 of 54 in process: E:\ORACLE\XIP\SAPDATA5\SR3_8\SR3.DATA8 Size: 3.906 GB, MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08 .
    BKI4007E: File 'E:\ORACLE\XIP\SAPDATA5\SR3_8\SR3.DATA8' cannot be read Reason:  errno(1450)  Insufficient system resources exist to complete the requested service.
    BKI1208W: The object 'E:\ORACLE\XIP\SAPDATA5\SR3_8\SR3.DATA8' will be retried [4].
    BKI0027I: Time: 04/08/08 06:23:04 Object: 15 of 54 in process: E:\ORACLE\XIP\SAPDATA5\SR3_8\SR3.DATA8 Size: 3.906 GB, MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08 .
    BKI4007E: File 'E:\ORACLE\XIP\SAPDATA5\SR3_8\SR3.DATA8' cannot be read Reason:  errno(1450)  Insufficient system resources exist to complete the requested service.
    BKI1231E: Maximum number of retries for file E:\ORACLE\XIP\SAPDATA5\SR3_8\SR3.DATA8 exceeded.
    BR0233E Backup utility has reported an error while saving file E:\ORACLE\XIP\SAPDATA5\SR3_8\SR3.DATA8
    BKI0027I: Time: 04/08/08 06:23:21 Object: 16 of 54 in process: D:\ORACLE\XIP\SAPDATA7\SR3_32\SR3.DATA32 Size: 3.662 GB, MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08 .
    BKI4007E: File 'D:\ORACLE\XIP\SAPDATA7\SR3_32\SR3.DATA32' cannot be read Reason:  errno(1450)  Insufficient system resources exist to complete the requested service.
    BKI1208W: The object 'D:\ORACLE\XIP\SAPDATA7\SR3_32\SR3.DATA32' will be retried [2].
    BKI0027I: Time: 04/08/08 06:23:31 Object: 16 of 54 in process: D:\ORACLE\XIP\SAPDATA7\SR3_32\SR3.DATA32 Size: 3.662 GB, MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08 .
    BKI4007E: File 'D:\ORACLE\XIP\SAPDATA7\SR3_32\SR3.DATA32' cannot be read Reason:  errno(1450)  Insufficient system resources exist to complete the requested service.
    BKI1208W: The object 'D:\ORACLE\XIP\SAPDATA7\SR3_32\SR3.DATA32' will be retried [3].
    BKI0027I: Time: 04/08/08 06:23:35 Object: 16 of 54 in process: D:\ORACLE\XIP\SAPDATA7\SR3_32\SR3.DATA32 Size: 3.662 GB, MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08 .
    BKI4007E: File 'D:\ORACLE\XIP\SAPDATA7\SR3_32\SR3.DATA32' cannot be read Reason:  errno(1450)  Insufficient system resources exist to complete the requested service.
    BKI1208W: The object 'D:\ORACLE\XIP\SAPDATA7\SR3_32\SR3.DATA32' will be retried [4].
    BKI0027I: Time: 04/08/08 06:23:39 Object: 16 of 54 in process: D:\ORACLE\XIP\SAPDATA7\SR3_32\SR3.DATA32 Size: 3.662 GB, MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08 .
    BKI4007E: File 'D:\ORACLE\XIP\SAPDATA7\SR3_32\SR3.DATA32' cannot be read Reason:  errno(1450)  Insufficient system resources exist to complete the requested service.
    BKI1231E: Maximum number of retries for file D:\ORACLE\XIP\SAPDATA7\SR3_32\SR3.DATA32 exceeded.
    BR0233E Backup utility has reported an error while saving file D:\ORACLE\XIP\SAPDATA7\SR3_32\SR3.DATA32
    BKI0027I: Time: 04/08/08 06:23:43 Object: 17 of 54 in process: D:\ORACLE\XIP\SAPDATA7\SR3_33\SR3.DATA33 Size: 3.418 GB, MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08 .
    BKI4007E: File 'D:\ORACLE\XIP\SAPDATA7\SR3_33\SR3.DATA33' cannot be read Reason:  errno(1450)  Insufficient system resources exist to complete the requested service.
    BKI1208W: The object 'D:\ORACLE\XIP\SAPDATA7\SR3_33\SR3.DATA33' will be retried [2].
    BKI0027I: Time: 04/08/08 06:23:47 Object: 17 of 54 in process: D:\ORACLE\XIP\SAPDATA7\SR3_33\SR3.DATA33 Size: 3.418 GB, MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08 .
    BKI4007E: File 'D:\ORACLE\XIP\SAPDATA7\SR3_33\SR3.DATA33' cannot be read Reason:  errno(1450)  Insufficient system resources exist to complete the requested service.
    BKI1208W: The object 'D:\ORACLE\XIP\SAPDATA7\SR3_33\SR3.DATA33' will be retried [3].
    BKI0027I: Time: 04/08/08 06:23:52 Object: 17 of 54 in process: D:\ORACLE\XIP\SAPDATA7\SR3_33\SR3.DATA33 Size: 3.418 GB, MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08 .
    BKI4007E: File 'D:\ORACLE\XIP\SAPDATA7\SR3_33\SR3.DATA33' cannot be read Reason:  errno(1450)  Insufficient system resources exist to complete the requested service.
    BKI1208W: The object 'D:\ORACLE\XIP\SAPDATA7\SR3_33\SR3.DATA33' will be retried [4].
    BKI0027I: Time: 04/08/08 06:23:56 Object: 17 of 54 in process: D:\ORACLE\XIP\SAPDATA7\SR3_33\SR3.DATA33 Size: 3.418 GB, MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08 .
    BKI4007E: File 'D:\ORACLE\XIP\SAPDATA7\SR3_33\SR3.DATA33' cannot be read Reason:  errno(1450)  Insufficient system resources exist to complete the requested service.
    BKI1231E: Maximum number of retries for file D:\ORACLE\XIP\SAPDATA7\SR3_33\SR3.DATA33 exceeded.
    BR0233E Backup utility has reported an error while saving file D:\ORACLE\XIP\SAPDATA7\SR3_33\SR3.DATA33
    BKI0027I: Time: 04/08/08 06:24:00 Object: 18 of 54 in process: G:\ORACLE\XIP\SAPDATA6\SR3_27\SR3.DATA27 Size: 2.930 GB, MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08 .
    BKI4007E: File 'G:\ORACLE\XIP\SAPDATA6\SR3_27\SR3.DATA27' cannot be read Reason:  errno(1450)  Insufficient system resources exist to complete the requested service.
    BKI1208W: The object 'G:\ORACLE\XIP\SAPDATA6\SR3_27\SR3.DATA27' will be retried [2].
    BKI0027I: Time: 04/08/08 06:24:05 Object: 18 of 54 in process: G:\ORACLE\XIP\SAPDATA6\SR3_27\SR3.DATA27 Size: 2.930 GB, MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08 .
    BKI4007E: File 'G:\ORACLE\XIP\SAPDATA6\SR3_27\SR3.DATA27' cannot be read Reason:  errno(1450)  Insufficient system resources exist to complete the requested service.
    BKI1208W: The object 'G:\ORACLE\XIP\SAPDATA6\SR3_27\SR3.DATA27' will be retried [3].
    BKI0027I: Time: 04/08/08 06:24:13 Object: 18 of 54 in process: G:\ORACLE\XIP\SAPDATA6\SR3_27\SR3.DATA27 Size: 2.930 GB, MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08 .
    BKI4007E: File 'G:\ORACLE\XIP\SAPDATA6\SR3_27\SR3.DATA27' cannot be read Reason:  errno(1450)  Insufficient system resources exist to complete the requested service.
    BKI1208W: The object 'G:\ORACLE\XIP\SAPDATA6\SR3_27\SR3.DATA27' will be retried [4].
    BKI0027I: Time: 04/08/08 06:24:23 Object: 18 of 54 in process: G:\ORACLE\XIP\SAPDATA6\SR3_27\SR3.DATA27 Size: 2.930 GB, MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08 .
    BKI4007E: File 'G:\ORACLE\XIP\SAPDATA6\SR3_27\SR3.DATA27' cannot be read Reason:  errno(1450)  Insufficient system resources exist to complete the requested service.
    BKI1231E: Maximum number of retries for file G:\ORACLE\XIP\SAPDATA6\SR3_27\SR3.DATA27 exceeded.
    BR0233E Backup utility has reported an error while saving file G:\ORACLE\XIP\SAPDATA6\SR3_27\SR3.DATA27
    BKI0027I: Time: 04/08/08 06:24:34 Object: 19 of 54 in process: C:\ORACLE\XIP\SAPDATA8\SR3_35\SR3.DATA35 Size: 2.930 GB, MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08 .
    BKI4007E: File 'C:\ORACLE\XIP\SAPDATA8\SR3_35\SR3.DATA35' cannot be read Reason:  errno(1450)  Insufficient system resources exist to complete the requested service.
    BKI1208W: The object 'C:\ORACLE\XIP\SAPDATA8\SR3_35\SR3.DATA35' will be retried [2].
    BKI0027I: Time: 04/08/08 06:24:41 Object: 19 of 54 in process: C:\ORACLE\XIP\SAPDATA8\SR3_35\SR3.DATA35 Size: 2.930 GB, MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08 .
    BKI4007E: File 'C:\ORACLE\XIP\SAPDATA8\SR3_35\SR3.DATA35' cannot be read Reason:  errno(1450)  Insufficient system resources exist to complete the requested service.
    BKI1208W: The object 'C:\ORACLE\XIP\SAPDATA8\SR3_35\SR3.DATA35' will be retried [3].
    BKI0027I: Time: 04/08/08 06:24:45 Object: 19 of 54 in process: C:\ORACLE\XIP\SAPDATA8\SR3_35\SR3.DATA35 Size: 2.930 GB, MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08 .
    BKI4007E: File 'C:\ORACLE\XIP\SAPDATA8\SR3_35\SR3.DATA35' cannot be read Reason:  errno(1450)  Insufficient system resources exist to complete the requested service.
    BKI1208W: The object 'C:\ORACLE\XIP\SAPDATA8\SR3_35\SR3.DATA35' will be retried [4].
    BKI0027I: Time: 04/08/08 06:25:05 Object: 19 of 54 in process: C:\ORACLE\XIP\SAPDATA8\SR3_35\SR3.DATA35 Size: 2.930 GB, MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08 .
    BKI4007E: File 'C:\ORACLE\XIP\SAPDATA8\SR3_35\SR3.DATA35' cannot be read Reason:  errno(1450)  Insufficient system resources exist to complete the requested service.
    BKI1231E: Maximum number of retries for file C:\ORACLE\XIP\SAPDATA8\SR3_35\SR3.DATA35 exceeded.
    BR0233E Backup utility has reported an error while saving file C:\ORACLE\XIP\SAPDATA8\SR3_35\SR3.DATA35
    BKI0027I: Time: 04/08/08 06:25:38 Object: 20 of 54 in process: F:\ORACLE\XIP\SAPDATA3\SR3700_2\SR3700.DATA2 Size: 2.422 GB, MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08 .
    BKI4007E: File 'F:\ORACLE\XIP\SAPDATA3\SR3700_2\SR3700.DATA2' cannot be read Reason:  errno(1450)  Insufficient system resources exist to complete the requested service.
    BKI1208W: The object 'F:\ORACLE\XIP\SAPDATA3\SR3700_2\SR3700.DATA2' will be retried [2].
    BKI0027I: Time: 04/08/08 06:25:58 Object: 20 of 54 in process: F:\ORACLE\XIP\SAPDATA3\SR3700_2\SR3700.DATA2 Size: 2.422 GB, MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08 .
    BKI4007E: File 'F:\ORACLE\XIP\SAPDATA3\SR3700_2\SR3700.DATA2' cannot be read Reason:  errno(1450)  Insufficient system resources exist to complete the requested service.
    BKI1208W: The object 'F:\ORACLE\XIP\SAPDATA3\SR3700_2\SR3700.DATA2' will be retried [3].
    BKI0027I: Time: 04/08/08 06:26:25 Object: 20 of 54 in process: F:\ORACLE\XIP\SAPDATA3\SR3700_2\SR3700.DATA2 Size: 2.422 GB, MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08 .
    BKI0023I: Time: 04/08/08 06:27:33 Done: 87.016 GB (52.4 %) of 166.037 GB. Estimated end time: 04/08/08 07:45:35.
    BKI0053I: Time: 04/08/08 06:27:33 Object: 20 of 54 done: F:\ORACLE\XIP\SAPDATA3\SR3700_2\SR3700.DATA2 with: 2.422 GB saved with description XIPOF_A0FEROGUNL.
    BR0280I BRBACKUP time stamp: 2008-04-08 06.27.33
    #FILE..... F:\ORACLE\XIP\SAPDATA3\SR3700_2\SR3700.DATA2
    #SAVED.... XIPOF_A0FEROGUNL
    BKI0027I: Time: 04/08/08 06:27:33 Object: 21 of 54 in process: F:\ORACLE\XIP\SAPDATA3\SR3700_4\SR3700.DATA4 Size: 2.363 GB, MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08 .
    BKI4007E: File 'F:\ORACLE\XIP\SAPDATA3\SR3700_4\SR3700.DATA4' cannot be read Reason:  errno(1450)  Insufficient system resources exist to complete the requested service.
    BKI1208W: The object 'F:\ORACLE\XIP\SAPDATA3\SR3700_4\SR3700.DATA4' will be retried [2].
    BKI0027I: Time: 04/08/08 06:27:54 Object: 21 of 54 in process: F:\ORACLE\XIP\SAPDATA3\SR3700_4\SR3700.DATA4 Size: 2.363 GB, MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08 .
    BKI4007E: File 'F:\ORACLE\XIP\SAPDATA3\SR3700_4\SR3700.DATA4' cannot be read Reason:  errno(1450)  Insufficient system resources exist to complete the requested service.
    BKI1208W: The object 'F:\ORACLE\XIP\SAPDATA3\SR3700_4\SR3700.DATA4' will be retried [3].
    BKI0027I: Time: 04/08/08 06:28:32 Object: 21 of 54 in process: F:\ORACLE\XIP\SAPDATA3\SR3700_4\SR3700.DATA4 Size: 2.363 GB, MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08 .
    BKI0023I: Time: 04/08/08 06:29:53 Done: 89.379 GB (53.8 %) of 166.037 GB. Estimated end time: 04/08/08 07:45:35.
    BKI0053I: Time: 04/08/08 06:29:53 Object: 21 of 54 done: F:\ORACLE\XIP\SAPDATA3\SR3700_4\SR3700.DATA4 with: 2.363 GB saved with description XIPOF_A0FEROGUNL.
    BR0280I BRBACKUP time stamp: 2008-04-08 06.29.53
    #FILE..... F:\ORACLE\XIP\SAPDATA3\SR3700_4\SR3700.DATA4
    #SAVED.... XIPOF_A0FEROGUNL
    BKI0027I: Time: 04/08/08 06:29:53 Object: 22 of 54 in process: F:\ORACLE\XIP\SAPDATA3\SR3700_1\SR3700.DATA1 Size: 2.363 GB, MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08 .
    BKI4007E: File 'F:\ORACLE\XIP\SAPDATA3\SR3700_1\SR3700.DATA1' cannot be read Reason:  errno(1450)  Insufficient system resources exist to complete the requested service.
    BKI1208W: The object 'F:\ORACLE\XIP\SAPDATA3\SR3700_1\SR3700.DATA1' will be retried [2].
    BKI0027I: Time: 04/08/08 06:30:14 Object: 22 of 54 in process: F:\ORACLE\XIP\SAPDATA3\SR3700_1\SR3700.DATA1 Size: 2.363 GB, MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08 .
    BKI4007E: File 'F:\ORACLE\XIP\SAPDATA3\SR3700_1\SR3700.DATA1' cannot be read Reason:  errno(1450)  Insufficient system resources exist to complete the requested service.
    BKI1208W: The object 'F:\ORACLE\XIP\SAPDATA3\SR3700_1\SR3700.DATA1' will be retried [3].
    BKI0027I: Time: 04/08/08 06:37:59 Object: 22 of 54 in process: F:\ORACLE\XIP\SAPDATA3\SR3700_1\SR3700.DATA1 Size: 2.363 GB, MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08 .
    BKI0023I: Time: 04/08/08 06:39:45 Done: 91.742 GB (55.3 %) of 166.037 GB. Estimated end time: 04/08/08 07:59:13.
    BKI0053I: Time: 04/08/08 06:39:45 Object: 22 of 54 done: F:\ORACLE\XIP\SAPDATA3\SR3700_1\SR3700.DATA1 with: 2.363 GB saved with description XIPOF_A0FEROGUNL.
    BR0280I BRBACKUP time stamp: 2008-04-08 06.39.45
    #FILE..... F:\ORACLE\XIP\SAPDATA3\SR3700_1\SR3700.DATA1
    #SAVED.... XIPOF_A0FEROGUNL
    BKI0027I: Time: 04/08/08 06:39:45 Object: 23 of 54 in process: F:\ORACLE\XIP\SAPDATA3\SR3700_3\SR3700.DATA3 Size: 2.344 GB, MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08 .
    BKI0023I: Time: 04/08/08 06:40:53 Done: 94.086 GB (56.7 %) of 166.037 GB. Estimated end time: 04/08/08 07:56:47.
    BKI0053I: Time: 04/08/08 06:40:53 Object: 23 of 54 done: F:\ORACLE\XIP\SAPDATA3\SR3700_3\SR3700.DATA3 with: 2.344 GB saved with description XIPOF_A0FEROGUNL.
    BR0280I BRBACKUP time stamp: 2008-04-08 06.40.53
    #FILE..... F:\ORACLE\XIP\SAPDATA3\SR3700_3\SR3700.DATA3
    #SAVED.... XIPOF_A0FEROGUNL
    BKI0027I: Time: 04/08/08 06:40:53 Object: 24 of 54 in process: F:\ORACLE\XIP\SAPDATA4\SR3DB_2\SR3DB.DATA2 Size: 2.070 GB, MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08 .
    BKI0023I: Time: 04/08/08 06:41:38 Done: 96.156 GB (57.9 %) of 166.037 GB. Estimated end time: 04/08/08 07:54:19.
    BKI0053I: Time: 04/08/08 06:41:38 Object: 24 of 54 done: F:\ORACLE\XIP\SAPDATA4\SR3DB_2\SR3DB.DATA2 with: 2.070 GB saved with description XIPOF_A0FEROGUNL.
    BR0280I BRBACKUP time stamp: 2008-04-08 06.41.38
    #FILE..... F:\ORACLE\XIP\SAPDATA4\SR3DB_2\SR3DB.DATA2
    #SAVED.... XIPOF_A0FEROGUNL
    BKI0027I: Time: 04/08/08 06:41:38 Object: 25 of 54 in process: F:\ORACLE\XIP\SAPDATA4\SR3DB_1\SR3DB.DATA1 Size: 2.031 GB, MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08 .
    BKI0023I: Time: 04/08/08 06:42:18 Done: 98.188 GB (59.1 %) of 166.037 GB. Estimated end time: 04/08/08 07:51:52.
    BKI0053I: Time: 04/08/08 06:42:18 Object: 25 of 54 done: F:\ORACLE\XIP\SAPDATA4\SR3DB_1\SR3DB.DATA1 with: 2.031 GB saved with description XIPOF_A0FEROGUNL.
    BR0280I BRBACKUP time stamp: 2008-04-08 06.42.18
    #FILE..... F:\ORACLE\XIP\SAPDATA4\SR3DB_1\SR3DB.DATA1
    #SAVED.... XIPOF_A0FEROGUNL
    BKI0027I: Time: 04/08/08 06:42:18 Object: 26 of 54 in process: G:\ORACLE\XIP\SAPDATA6\SR3_25\SR3.DATA25 Size: 2.000 GB, MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08 .
    BKI0023I: Time: 04/08/08 06:42:55 Done: 100.188 GB (60.3 %) of 166.037 GB. Estimated end time: 04/08/08 07:49:29.
    BKI0053I: Time: 04/08/08 06:42:55 Object: 26 of 54 done: G:\ORACLE\XIP\SAPDATA6\SR3_25\SR3.DATA25 with: 2.000 GB saved with description XIPOF_A0FEROGUNL.
    BR0280I BRBACKUP time stamp: 2008-04-08 06.42.55
    #FILE..... G:\ORACLE\XIP\SAPDATA6\SR3_25\SR3.DATA25
    #SAVED.... XIPOF_A0FEROGUNL
    BKI0027I: Time: 04/08/08 06:42:55 Object: 27 of 54 in process: G:\ORACLE\XIP\SAPDATA6\SR3_24\SR3.DATA24 Size: 2.000 GB, MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08 .
    BKI0023I: Time: 04/08/08 06:43:33 Done: 102.188 GB (61.5 %) of 166.037 GB. Estimated end time: 04/08/08 07:47:14.
    BKI0053I: Time: 04/08/08 06:43:33 Object: 27 of 54 done: G:\ORACLE\XIP\SAPDATA6\SR3_24\SR3.DATA24 with: 2.000 GB saved with description XIPOF_A0FEROGUNL.
    BR0280I BRBACKUP time stamp: 2008-04-08 06.43.33
    #FILE..... G:\ORACLE\XIP\SAPDATA6\SR3_24\SR3.DATA24
    #SAVED.... XIPOF_A0FEROGUNL
    BKI0027I: Time: 04/08/08 06:43:33 Object: 28 of 54 in process: G:\ORACLE\XIP\SAPDATA6\SR3_23\SR3.DATA23 Size: 2.000 GB, MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08 .
    BKI0023I: Time: 04/08/08 06:44:07 Done: 104.188 GB (62.7 %) of 166.037 GB. Estimated end time: 04/08/08 07:44:57.
    BKI0053I: Time: 04/08/08 06:44:07 Object: 28 of 54 done: G:\ORACLE\XIP\SAPDATA6\SR3_23\SR3.DATA23 with: 2.000 GB saved with description XIPOF_A0FEROGUNL.
    BR0280I BRBACKUP time stamp: 2008-04-08 06.44.07
    #FILE..... G:\ORACLE\XIP\SAPDATA6\SR3_23\SR3.DATA23
    #SAVED.... XIPOF_A0FEROGUNL
    BKI0027I: Time: 04/08/08 06:44:07 Object: 29 of 54 in process: G:\ORACLE\XIP\SAPDATA6\SR3_22\SR3.DATA22 Size: 2.000 GB, MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08 .
    BKI0023I: Time: 04/08/08 06:44:47 Done: 106.188 GB (64.0 %) of 166.037 GB. Estimated end time: 04/08/08 07:42:55.
    BKI0053I: Time: 04/08/08 06:44:47 Object: 29 of 54 done: G:\ORACLE\XIP\SAPDATA6\SR3_22\SR3.DATA22 with: 2.000 GB saved with description XIPOF_A0FEROGUNL.
    BR0280I BRBACKUP time stamp: 2008-04-08 06.44.48
    #FILE..... G:\ORACLE\XIP\SAPDATA6\SR3_22\SR3.DATA22
    #SAVED.... XIPOF_A0FEROGUNL
    BKI0027I: Time: 04/08/08 06:44:48 Object: 30 of 54 in process: G:\ORACLE\XIP\SAPDATA6\SR3_21\SR3.DATA21 Size: 2.000 GB, MGMNT-CLASS: OFFLINE_ATHOMEXIPRD, TSM-Server: 172.16.1.8:NLKSRVR08 .
    BKI0023I: Time: 04/08/08 06:45:27 Done: 108.188 GB (65.2 %) of 166.037 GB. Estimated end time: 04/08/08 07:40:58.
    BKI0053I: Time: 04/08/08 06:45:27 Object: 30 of 54 done: G:\ORACLE\XIP\SAPDATA6\SR3_21\SR3.DATA21 with: 2.000 GB saved with description XIPOF_A0FEROGUNL.

    On another link I found the following :
    BKI4007E
    File filename cannot be read. Reason: errno(errno number) errno text.
    Explanation:
    Data could not be read due to some system error. Check errno text for further information. If this error recurs, this might indicate some hardware problems.
    User response:
    Contact your system administrator.
    The Link:
    http://ezbackup.cornell.edu/techsup-v5.4/ibmdocs/messages/html/anrcms5878.htm
    Regards,
    Siddhesh

Maybe you are looking for