Buffer fill on MBR HDS
Hi all.
I have built a player using Strobe Media Playback as a base. We're using it for several applications.
When I try to plaback an OnDemand Dynamic Stream through HTTP, I get the buffer bar full from the beginning, as if there is no way to have an estimate of the buffer loaded.
In a way I understand that this is logical if there are several renditions for the video. But how does YouTube manage to do this for example? Or any other Video OnDemand site. Basically it seems as if the player tries to stick to a specific rendition and loads the buffer of that specific video quality. But somehow this goes against how ABR works, because choosing a non optimal rendition at the beginning can result in a poor playback experience.
In short what I would like to achieve is to keep ABR but to also allow the player to buffer the video so that the user can pause the video and wait untill the buffer is loaded. But this is not working for me.
Hope you can help.
Regards
I came accross this paper that looks very interesting. Does OSMF have this kind of implementation?
http://yuba.stanford.edu/~nickm/papers/sigcomm2014-video.pdf
Any ideas weather this can be implemented?
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
AndyHi 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. -
m that I am having is that to do this I need to fill two different structures, one containing a pointer to a double, which I don't think I can do without perhaps a wrapper function. The biggest problem is that I don't know how to even go about doing this.I have two structures that I need to fill in order to read a block of data from a given DLL which are
typedef struct CHBL_ORDER_T {
INT32 lBlock; // block number, set by user (typical 0)
INT16 sChan; // channel number, set by user
UINT16 usFlags; // only DATA_1OFN at the moment
INT32 lChSR; // channel sampling rate, returned by open
INT32 lFirstMP; // BSR MP not greater than "open sta
rt"
INT32 lBuffLen; // required CHSR based buffer size
INT32 lIncr; // distance between two buffered values
UINT16 usMask; // Mask used before Shift
INT8 chShift; // number of right shifts
} CHBL_ORDER, *PCHBL_ORDER;
typedef struct CHBL_FETCH_T {
double *pdblMin; // min or 1 of n array
double *pdblMax; // max array (either solo or along with MINMAX
INT32 lPos; // (set by user), returned by fetch
INT32 lNum; // (set by user), returned by fetch
} CHBL_FETCH, *PCHBL_FETCH;
I am trying to do the data block access with labview on page 18 of the attached pdf document.
I also have a c code exapmle attached in the zip file, the function in c i am trying to do is in Sample2Dlg.cpp
if anyone can help me out I would greatly appreciate it.
Attachments:
BS_Toolbox_(Ford).PDF 160 KB
sample2.zip 55 KBm that I am having is that to do this I need to fill two different structures, one containing a pointer to a double, which I don't think I can do without perhaps a wrapper function. The biggest problem is that I don't know how to even go about doing this.I believe you are right about needing to create a wrapper DLL. To do this, just create a DLL which includes a function that accepts a double. Then, it uses this to make a pointer to that double and send it to your original DLL. When that function returns, you return this info to LabVIEW in form of a regular double. Basically, there is just one more layer of code which you use for translation between LabVIEW and the DLL you are currently using. You need to create that layer.
J.R. Allen -
How not to realocate memory in a "buffer write" loop
Hello,
i posted this also in the DIO board, but maybe this is specifically a Labview problem:
my application requires sending data to all 4 ports of a DIO 32HS at a 2MHz rate, for an undefined length of time.
preparing a bit less than the maximum buffer size (about 64MB /4 it seems) and setting the Buffer control to "reserve", i then begin to send information in arrays of 4 words to the "buffer Write", while cycling trough the buffer. after some initial buffer loading time ( about a second worth of timed output), i begin the output operation with DIO start.
my data being prepared online, i cant use a double buffer configuration (half buffer size being recreated and reloaded), because my application typically stops creating output words in the middle of such half buffer size, leaving the rest of the array full of null values, affecting my output applications.
However "Buffer write" reallocate memory each time a 4-bytes array is sent to it. therefore sending out 10ms worth of data takes 500ms, sending 100ms takes 5seconds!! this makes it impossible to actually prepare online the data to be sent out. by preparing the full length array in advance, the windows limitation of ~16Mwords then limits my output application to max ~8 seconds only.
Is there any way to avoid memory reallocation on calling the Buffer Write? what are actually the elements the dll requires?
i am using traditional NI-DAQ and Labview 7.1 or 8.2.
Thanks for any help on the subject.
... And here's where I keep assorted lengths of wires...Hello Kevin,
Thanks for your answer.
attached is some test code (not very clean but should be understandable):
two elements are sent with a time lag of 100ms, during which frame 2 creates a null array of 4 words for about 200000 times (filling the time lag)
the four words are : 16 bits value, channel value 8Bit, and a 2 bit strobe (10 or 11) on port 4.
in this test, i let fill the buffer for this time, check how much time it took, and only after that allow execution out.
the idea of the final code will be to send an undefined nb of elements at various time intervals, to fill the buffer online (regeneratively hopefully) as the execution is taking place. it would be possible if "buffer write" would be fast enough, and i would avoid creating big chuncks of memory , as well as saving on the overall run time (calculation + output execution would be almost parallel, with a short time lag).
if it works, i would just need to introduce some wait commands if buffer filling is faster than execution.
i think the main problem right now is that when i call "buffer write" it realocates memory for its array.
Tell me what you think.
... And here's where I keep assorted lengths of wires...
Attachments:
channels definition and pattern execution test x.vi 76 KB -
Serial VISA 'Write' -why is it slow to return even with large buffer?
Hi,
I'm writing a serial data transfer code 'module' that will run 'in the background' on a cRIO-9014. I'm a bit perplexed about how VISA write in particular seems to work.
What I'm seeing is that the VISA Write takes about 177ms to 'return' from a 4096 byte write, even though my write buffer has been set to >> 4096.
My expectation would be that the write completes near instantly as long as the VISA driver available buffer space is greater than the bytes waiting to be written, and that the write function would only 'slow down' up to the defined VISA timeout value if there was no room in the buffer.
As such, I thought it would be possible to 'pre-load' the transmit buffer at a high rate, then, by careful selection of the time-out value relative to the baud rate, it would self-throttle once the buffer fills up?
Based on my testing this is not the case, which leaves me wondering:
a) If you try to set the transmit buffer to an unsupported value, will you get an error?
b) Assuming 'yes' to a, what the heck is the purpose of the serial write buffer? I see no difference running with serial buffer size == data chunk size and serial buffer size >> data chunk size??
QFang
CLD LabVIEW 7.1 to 2013Hi, I can quickly show the low-level part as a png. It's a sub-vi for transferring file segments. Some things like the thin 'in-line' VI with (s) as the icon were added to help me look at were the hold-up is. I cropped the image to make it more readable, the cut-off left and right side is just the input and output clusters.
In a nut-shell, the VISA Write takes as much time to 'return' as it would take to transfer x bytes over y baud rate. In other words, even though there is suppused to be a (software or hardware) write and read buffer on the com port, the VISA write function seems to block until the message has physically left the port (OR it writes TO the buffer at the same speed the buffer writes out of the port). This is very unexpected to me, and what prompted me to ask about what the point is of the write buffer in the first place? -The observations are on a 9014 RT target built in serial port. Not sure if the same is observed on other targets or other OS's. [edit: and the observation holds even if transmitting block-sizes of say 4096 with a buffer size of 4096 or 2*4096 or 10 * 4096 etc. I also tried smaller block sizes and larger block sizes with larger still buffers. I was able to verify that the buffer re-size function does error out if I give it an insane input buffer size request, so I'm taking that to mean that when I assign e.g. a 4MiB buffer space with no error, the write buffer actually IS 4MiB, but I have not found a property to read back what the HW buffer is, so all I have to base that on is the lack of an error during buffer size setting.) [\edit\]
The rest of the code is somewhat irrelelvant to this discussion, however, to better understand it, the idea is that the remote side of the connection will request various things, including a file. The remote side can request a file as a stream of messages each of size 'Block Size (bytes)', or it can request a particular block (for handling e.g. re-transmission if file MD5 checksum does not match). The other main reason for doing block transfers is that VISA Write hogs a substantial ammount of CPU, so if you were to attempt to write e.g. a 4MiB file out the serial port, assuming your VISA time-out is sufficiently long for that size transfer, the write would succeed, but you would see ~50% CPU from this one thread alone and (depending on baud rates) it could remain at that level for a verrry long time. So, by transferring smaller segments at a time, I can arbitrarily insert delays between segments to let the CPU sleep (at the expense of longer transfer times). The first inner case shown that opens the file only runs for new transfers, the open file ref is kept on a shift register in the calling VI. The 'get file offset' function after the read was just something I was looking at during (continued) development, and not required for the functionality that I'm describing.
QFang
CLD LabVIEW 7.1 to 2013 -
Lose history at end of pause buffer???
I am not sure how long the pause buffer is (it isn't important for this posting), so let's assume for the sake of this issue that it is 15 minutes.
If I am watching TV, and then I get a phone call and hit pause .... and then talk on the phone for 14 minutes and 50 seconds ... walk back into my living room, but don't get to the remote before the 15 minute buffer fills up -- without me touching anything my show/game skips forward to show live TV. I've just missed 15 minutes of whatever I was watching.
My TiVo (which was GREAT before it died) *and* my DirecTV DVR (which was overall an unstable piece of garbage) would simply start playing from the beginning of the buffer once it was full (so that you'd be 15 minutes behind live TV). That way if you leave it paused for 19 minutes (exceeding the buffer by 4 minutes), you only miss 4 minutes of TV. In the case of my FIOS DVR, if I leave it paused for 19 minutes, I miss 19 minutes.
I'm hoping this is simply a configuration option that I can't find ... I am a very happy FIOS customer, and other than a rare audio drop-out in recorded HD programs (one out of every 10 shows will have 5 seconds of audio missing in the middle), this is the only issue I have.Yes it has pissed me off more then once. I too have had Direct TV DVR and Dishnetwork DVR and never had this problem. It worked as you stated. But I think it bufferd 1/2hr. Also I have had a program buffered and watching the rest and it just skipped to the live program at the end of the period in which the currenly buffered program was recording. Like it is 6:48 and I walk back to the TV at 6:55 and start watching, WOW what a **bleep**, at 7:00 it jumped to the new live program. Yea I have not been happy, more then once. I have decided that if I am not going to pause it for more the a few minutes, hit record and then play it back from my dvr. Pause will just make you angry.
-
we use the 6534 for contiuous double buffered output of a changing 32 bit digital sequence. The large on board scarab buffer memory causes a delay when the sequence is changed. We can use set_daq_device_info to set ND_FIFO_TRANSFER_COUNT to ND_None, but what we need is a small buffer, bigger than ND_none but smaller than 32 MBytes. Is there a way of finding the acutal on board scarab buffer fill level. We could use that to avoid filling the scarab memory so that we can limit the delay, and still use the buffer.
thanks, AlexAlex,
I would say there is an important thing to watch for here. The board/driver behaves differently depending on whether you have enabled regeneration or not.
For Regenerative output operations the driver will fill up the entire on-board memory (Scarab) with the pattern in the host buffer.
Non-Regenerative operations are limited to using only as much on-board memory as the host buffer size. A 50k Sample buffer in the host memory would mean that the board will only use 50KSamples worth of its on-board memory.
As you can see you can limit the amount of on-board memory used by disabling the regeneration of data. This of course makes your application vulnerable to speed issues but guarantees that you'll be able to update your output with much less delay.
KB Online - 2QGEIN85 talks about this.
(search for: +6534 +generated +data)
You will also find KB Online - 2MOESVN5 very useful. It mentions a function call you can use to keep track of how much data has actually been generated by the board, which is related to the on-board memory status (empty/full) for non-regenerative operations.
I hope this helps,
Alejandro Asenjo
National Instruments
Applications Engineer -
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 -
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, AHyup...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 -
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 -
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 -
BKI0008E: The environment variable BI_CALLER is not set correctely. The cur
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 <par_file> [-u <user_id>] [-f <function>]
[-t <type>] [-i <in_file>] [-o <out_file>] [-c]
where:
<user_id> backint utility user
<function> backup | restore | inquire | password | delete
<type> file | file_online
<par_file> parameter file for backup utility
<in_file> name of a text file that defines the objects
default: STDIN
<out_file> 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?
-
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 -
Hi Gurus,
We are having problem with analysis authorizations for a particular query. The report is for the vendor balance, it has balance, cumulative balance as key figures and vendor as characteristics. We wanted to restrict the report by account group level. we have 4 account groups. The account group is a navigational attribute of creditor account group. account group [char] is auth relevant but the creditor account group [char] is not. so we gave respective auth group for accnt grp [char] but the query fails. The analysis log is follows, any help will be appreciated
Authorization Check
Detail Check for InfoProvider ZFIAP_S01
Preprocessing:
Selection Checked for Consistency, Preprocessed and Supplemented As Needed
Subselection (Technical SUBNR) 1
Check Node Definitions and Value Authorizations...
Node- and Value Authorizations Are OK
End of Preprocessing
Filling the Buffer...
...Buffer Filled
Main Check:
Subselection (Technical SUBNR) 1
Supplementation of Selection for Aggregated Characteristics
No Check for Aggregation Authorization Required
Following Set Is Checked Comparison with Following Authorized Set Result Remaining Set
Characteristic Content in SQL Format
0ACCNT_GRPV
0TCAACTVT
0TCAACTVT = '03'
AND 0ACCNT_GRPV LIKE *
Characteristic Content in SQL Format
0ACCNT_GRPV I EQ :
I EQ ZCON
I EQ ZCOR
I EQ ZFRN
I EQ ZGAR
0TCAACTVT I CP *
Partially or Fully Authorized (Intersection) Characteristic Content in SQL Format
0ACCNT_GRPV
0TCAACTVT
NOT 0ACCNT_GRPV IN ('ZCON','ZCOR','ZFRN','ZGAR')
AND 0TCAACTVT = '03'
Value selection partially authorized. Check of remainder at end
Following Set Is Checked Comparison with Following Authorized Set Result Remaining Set
Characteristic Content in SQL Format
0ACCNT_GRPV
0TCAACTVT
NOT 0ACCNT_GRPV IN ('ZCON','ZCOR','ZFRN','ZGAR')
AND 0TCAACTVT = '03'
Characteristic Content in SQL Format
0ACCNT_GRPV I EQ :
I EQ ZCON
I EQ ZCOR
I EQ ZFRN
I EQ ZGAR
0TCAACTVT I CP *
Not Authorized
All Authorizations Tested
Message EYE007: You do not have sufficient authorization
No Sufficient Authorization for This Subselection (SUBNR)
Following CHANMIDs Are Affected:
2596 ( ZFIAP_S01___F2 )
Authorization Check CompleteHi,
As per SAP Note 642072 (Authorization check on : for char./navigation attribute):
In new BI 7.x releases, the authorization logic has been enhanced and navigation attributes have the same status as 'normal' characteristics. An overlay of characteristic A and navigation attribute B__A no longer occurs. They are now treated as completely seperate objects.
As you said, account group (0ACCNT_GRPV) is a navigational attribute of creditor account group (say 0CREDITOR), so the characteristics here becomes 0CREDITOR__0ACCNT_GRPV. So you have to mark 0CREDITOR__0ACCNT_GRPV as auth relevant by tcode RSD1> go to 0CREDITOR> in attribute tab check 0ACCNT_GRPV as auth relevant and activate it.
As per the trace you posted, it seems currently its just checking for 0ACCNT_GRPV and not 0CREDITOR__0ACCNT_GRPV which is treated as separate entity in BI7.x versions.
Also, for restriction on navigational attributes, you need to create an authorization variable on your navigational attribute (i.e 0CREDITOR__0ACCNT_GRPV ) and make it input ready in your query. This will pull the user's authorized values and input them into the query. Also, maintain the desired authorized values for your navigation attribute (0CREDITOR__0ACCNT_GRPV) in the Analysis authorization assigned to the user. Leaving it blank or no values entered will make the query check for "*".
P.S (edited): Most importantly, the query should have a check on auth relevant characteristics (in your case 0CREDITOR__0ACCNT_GRPV) otherwise it is not possible to restrict the characteristics to specific values and BI will by default check for "*" and atleast ":" has to be added to the analysis authorization for successful execution of query but that does not serve the purpose as ":" shows aggregated data for all account groups. Please see note # 1140831
Hope this helps!
Sandipan
Edited by: Sandipan Choudhury on Mar 11, 2011 12:36 PM
Maybe you are looking for
-
How to find the number of links in a website
hi every body can any one clear my doubt my doubt is that in a website how to find the number of links the hole website contains is there any navigation tool to find that plz help me yar i am waiting for the reply
-
Extra emails using SO_NEW_DOCUMENT_ATT_SEND_API1.
Hello, I have a requirement to send Purchase order email to a group of people besides the vendor. I set the configuration to send the first email to the vendor and it is working fine. I would like to use SO_NEW_DOCUMENT_ATT_SEND_API1 to send the SAME
-
So here's a new one. I was working around with some newer projects and to maintain my own sanity I opened multiple projects to keep things separate and organized. I really like the "tab" feature of CS4 so you can easily switch between projects. So he
-
Hi, can some one try this with their touch and tell me what happens? Start a song, while song is playing, go to cover flow mode and just start flicking to next album arts. After about 20 seconds of flicking, song will just stop. I tried this over and
-
How to convert varchar to date?
Hello everyone, I'm new to OBIEE and I'm running into a roadblock... I have a date that is stored in a varchar2 column in the physical table, like so: 20071225 Silly I know, but that's what I'm dealing with. Anyway, I want to create a logical column