Backint - MaxDB
Hello all,
we are trying to backup our MaxDB using the backint interface. Unfortunately, the backup process fails with the error messages shown in the appended KNLDIAG log and EXTERNAL BACKUP log
KNLDIAG
0:32:53 31276 11560 COMMUNIC Releasing T132
2008-07-31 20:32:53 31276 12827 COMMUNIC wait for connection T132
2008-07-31 20:32:54 31258 11561 COMMUNIC Connecting T125 local 3626
2008-07-31 20:32:54 31276 12929 TASKING Task T125 started
2008-07-31 20:32:54 31276 11007 COMMUNIC wait for connection T125
2008-07-31 20:32:54 31276 11561 COMMUNIC Connected T125 local 3626
2008-07-31 20:32:54 31276 11560 COMMUNIC Releasing T125
2008-07-31 20:32:54 31276 12827 COMMUNIC wait for connection T125
2008-07-31 20:32:55 3634 ERR 11000 devio write error (fd = 54): Broken pipe
2008-07-31 20:32:55 31272 11000 vasynclo '/tmp/backintdb-pipe' devno 34 T72
2008-07-31 20:32:55 31259 12822 TASKING Thread 3634 joining
2008-07-31 20:32:55 3634 11566 stop DEVi stopped
2008-07-31 20:32:55 31272 52024 SAVE 63992 pages -> "/tmp/backintdb-pipe"
2008-07-31 20:32:55 31276 52012 SAVE new tape required 4300
2008-07-31 20:32:55 31276 1 Backup Backupmedium #1 (/tmp/backintdb-pipe) end of file
2008-07-31 20:32:55 31276 6 KernelCo + Backup error occured, Errorcode 4300 "new_hostfile_required"
2008-07-31 20:32:56 31276 12929 TASKING Task T142 started
2008-07-31 20:32:56 31258 11561 COMMUNIC Connecting T142 local 3626
2008-07-31 20:32:56 31276 11007 COMMUNIC wait for connection T142
2008-07-31 20:32:56 31276 11561 COMMUNIC Connected T142 local 3626
2008-07-31 20:32:56 31276 11560 COMMUNIC Releasing T142
2008-07-31 20:32:56 31276 12827 COMMUNIC wait for connection T142
2008-07-31 20:36:23 31276 11000 vasynclo '/sapdata/SOM/DISKD0001' devno 17 T143
2008-07-31 20:36:23 31259 12822 TASKING Thread 3629 joining
EXTERNAL BACKUP
2008-07-31 20:32:36
Setting environment variable 'TEMP' for the directory for temporary files and pipes to default ''.
Setting environment variable 'TMP' for the directory for temporary files and pipes to default ''.
Using connection to Backint for MaxDB Interface.
2008-07-31 20:32:36
Checking existence and configuration of Backint for MaxDB.
Reading the Backint for MaxDB configuration file '/sapdb/data/wrk/SOM/bsi.env'.
Found keyword 'BACKINT' with value '/sapdb/SOM/db/bin/backint'.
Found keyword 'INPUT' with value '/tmp/tsm-logs/som-backint4maxdb.in'.
Found keyword 'OUTPUT' with value '/tmp/tsm-logs/som-backint4maxdb.out'.
Found keyword 'ERROROUTPUT' with value '/tmp/tsm-logs/som-backint4maxdb.err'.
Found keyword 'PARAMETERFILE' with value '/sapdb/SOM/db/bin/backintmaxdbconfig.par'.
Found keyword 'TIMEOUT_SUCCESS' with value '600'.
Found keyword 'TIMEOUT_FAILURE' with value '300'.
Found keyword 'ORIGINAL_RUNDIRECTORY' with value '/sapdb/data/wrk/SOM'.
Finished reading of the Backint for MaxDB configuration file.
Using '/sapdb/SOM/db/bin/backint' as Backint for MaxDB program.
Using '/tmp/tsm-logs/som-backint4maxdb.in' as input file for Backint for MaxDB.
Using '/tmp/tsm-logs/som-backint4maxdb.out' as output file for Backint for MaxDB.
Using '/tmp/tsm-logs/som-backint4maxdb.err' as error output file for Backint for MaxDB.
Using '/sapdb/SOM/db/bin/backintmaxdbconfig.par' as parameter file for Backint for MaxDB.
Using '600' seconds as timeout for Backint for MaxDB in the case of success.
Using '300' seconds as timeout for Backint for MaxDB in the case of failure.
Using '/sapdb/data/wrk/SOM/dbm.knl' as backup history of a database to migrate.
Using '/sapdb/data/wrk/SOM/dbm.ebf' as external backup history of a database to migrate.
Checking availability of backups using backint's inquire function.
Check passed successful.
2008-07-31 20:32:36
Checking medium.
Check passed successfully.
2008-07-31 20:32:36
Preparing backup.
Setting environment variable 'BI_CALLER' to value 'DBMSRV'.
Setting environment variable 'BI_REQUEST' to value 'NEW'.
Setting environment variable 'BI_BACKUP' to value 'FULL'.
Constructed Backint for MaxDB call '/sapdb/SOM/db/bin/backint -u SOM -f backup -t file -p /sapdb/SOM/db/bin/backintmaxdbconfig.par -i /tmp/tsm-logs/som-backint4maxdb.in -c'.
Created temporary file '/tmp/tsm-logs/som-backint4maxdb.out' as output for Backint for MaxDB.
Created temporary file '/tmp/tsm-logs/som-backint4maxdb.err' as error output for Backint for MaxDB.
Writing '/tmp/backintdb-pipe #PIPE' to the input file.
Prepare passed successfully.
2008-07-31 20:32:36
Creating pipes for data transfer.
Creating pipe '/tmp/backintdb-pipe' ... Done.
All data transfer pipes have been created.
2008-07-31 20:32:36
Starting database action for the backup.
Requesting 'SAVE DATA QUICK TO '/tmp/backintdb-pipe' PIPE BLOCKSIZE 8 NO CHECKPOINT MEDIANAME 'backindb'' from db-kernel.
The database is working on the request.
2008-07-31 20:32:36
Waiting until database has prepared the backup.
Asking for state of database.
2008-07-31 20:32:36 Database is still preparing the backup.
Waiting 1 second ... Done.
Asking for state of database.
2008-07-31 20:32:37 Database is still preparing the backup.
Waiting 2 seconds ... Done.
Asking for state of database.
2008-07-31 20:32:39 Database is still preparing the backup.
Waiting 3 seconds ... Done.
Asking for state of database.
2008-07-31 20:32:42 Database is still preparing the backup.
Waiting 4 seconds ... Done.
Asking for state of database.
2008-07-31 20:32:46 Database is still preparing the backup.
Waiting 5 seconds ... Done.
Asking for state of database.
2008-07-31 20:32:51 Database has finished preparation of the backup.
The database has prepared the backup successfully.
2008-07-31 20:32:51
Starting Backint for MaxDB.
Starting Backint for MaxDB process '/sapdb/SOM/db/bin/backint -u SOM -f backup -t file -p /sapdb/SOM/db/bin/backintmaxdbconfig.par -i /tmp/tsm-logs/som-backint4maxdb.in -c >>/tmp/tsm-logs/som-backint4maxdb.out 2>>/tmp/tsm-logs/som-backint4maxdb.err'.
Process was started successfully.
Backint for MaxDB has been started successfully.
2008-07-31 20:32:51
Waiting for end of the backup operation.
2008-07-31 20:32:51 The backup tool is running.
2008-07-31 20:32:51 The database is working on the request.
2008-07-31 20:32:56 The backup tool process has finished work with return code 2.
2008-07-31 20:32:56 The backup tool is not running.
2008-07-31 20:32:56 The database has finished work on the request.
Receiving a reply from the database kernel.
Got the following reply from db-kernel:
SQL-Code :-8020
Date :20080731
Time :00203248
Database :SOM
Server :bssomp02
KernelVersion :Kernel 7.6.00 Build 035-123-139-084
PagesTransfered :64000
PagesLeft :4907326
MediaName :backindb
Location :/tmp/backintdb-pipe
Errortext :end of file
Label :DAT_000000055
IsConsistent :true
FirstLogPageNo :3321207
DBStamp1Date :20080731
DBStamp1Time :00203244
BDPageCount :4971302
DevicesUsed :1
DatabaseID :bssomp02:SOM_20070910_162640
Max Used Data Page
Converter Page Count :2676
The backup operation has ended.
2008-07-31 20:32:56
Filling reply buffer.
Have encountered error -24920:
The backup tool failed with 2 as sum of exit codes. The database request failed with error -8020.
Constructed the following reply:
ERR
-24920,ERR_BACKUPOP: backup operation was unsuccessful
The backup tool failed with 2 as sum of exit codes. The database request failed with error -8020.
Reply buffer filled.
It seem to me that it is a MUST to use the Tivoli Data Protection for the MaxDB. Is anybody out there to tell me if this is right? Or ist it possible to directly transfer backup data from MaxDB to Tivoli Storage Manager (TSM) via a pipe?
Thanks and kind regards
Anette Feierabend
> 2008-07-31 20:32:55 3634 ERR 11000 devio write error (fd = 54): Broken pipe
> 2008-07-31 20:32:55 31272 11000 vasynclo '/tmp/backintdb-pipe' devno 34 T72
> 2008-07-31 20:32:55 31259 12822 TASKING Thread 3634 joining
> 2008-07-31 20:32:55 3634 11566 stop DEVi stopped
> 2008-07-31 20:32:55 31272 52024 SAVE 63992 pages -> "/tmp/backintdb-pipe"
> 2008-07-31 20:32:55 31276 52012 SAVE new tape required 4300
> 2008-07-31 20:32:55 31276 1 Backup Backupmedium #1 (/tmp/backintdb-pipe) end of file
> 2008-07-31 20:32:55 31276 6 KernelCo + Backup error occured, Errorcode 4300 "new_hostfile_required"
> Receiving a reply from the database kernel.
> Got the following reply from db-kernel:
> SQL-Code :-8020
> KernelVersion :Kernel 7.6.00 Build 035-123-139-084
> PagesTransfered :64000
> PagesLeft :4907326
> MediaName :backindb
> Location :/tmp/backintdb-pipe
> Errortext :end of file
> Label :DAT_000000055
> IsConsistent :true
> FirstLogPageNo :3321207
> DBStamp1Date :20080731
> DBStamp1Time :00203244
> BDPageCount :4971302
> DevicesUsed :1
> DatabaseID :bssomp02:SOM_20070910_162640
> Max Used Data Page
> Converter Page Count :2676
> The backup operation has ended.
>
> 2008-07-31 20:32:56
> Filling reply buffer.
> Have encountered error -24920:
> The backup tool failed with 2 as sum of exit codes. The database request failed with error -8020.
>
> Constructed the following reply:
> ERR
> -24920,ERR_BACKUPOP: backup operation was unsuccessful
> The backup tool failed with 2 as sum of exit codes. The database request failed with error -8020.
> Reply buffer filled.
Hi Anette,
it looks pretty much as if the backup medium definition for the MaxDB contains a maximum size. Thus the database will request a new medium once the setup maximum pages for the medium (64000 in your case) are reached.
Error -8020 says exactly this: "Next medium needed"
Therefore I would propose to check the backup medium.
> It seem to me that it is a MUST to use the Tivoli Data Protection for the MaxDB. Is anybody out there to tell me if this is right? Or ist it possible to directly transfer backup data from MaxDB to Tivoli Storage Manager (TSM) via a pipe?
No, that's wrong - once you setup the backup medium correctly it will work.
Best regards,
Lars
p.s.
If you're an SAP customer -> open a support message.
And - of course - you're using a very old version of MaxDB. Get the current patch here in the SDN download area or via SAP Service Marketplace!
Similar Messages
-
MaxDB backup through Backint on Oracle for TSM
Hello Gurus:
We are using TSM backint interface for Oracle database. We are in the process of implementing SCM. We would like to schedule MaxDB backup through backint interface for Oracle.
I checked some forums and configured but backint is not recognizing MaxDB parameter file. Please see below parameter file and error logs.
*BSI File:*
BACKINT D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe
INPUT D:\sapdb\data\wrk\backint\sapdb.in
OUTPUT D:\sapdb\data\wrk\backint\sapdb.out
ERROROUTPUT D:\sapdb\data\wrk\backint\sapdb.err
PARAMETERFILE D:\sapdb\data\wrk\LCD\maxdb_config.par
ORIGINAL_RUNDIRECTORY L:\sapdb\LCD\sapdata
*Parameter File - MaxDB_config*
STAGING AREA: D:\TEMP\STAGE1 1024000 KB
FILES PER BACKINT CALL: 2
BACKINT: D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe
PARAMETERFILE OF BACKINT: D:\oracle\SCD\102\database\initSCD.utl
HISTORY FILE: D:\sapdb\data\wrk\BackintHistory
INPUTFILE OF BACKINT: D:\sapdb\data\wrk\backint\backint.in
OUTPUTFILE OF BACKINT: D:\sapdb\data\wrk\backint\backint.out
ERRORFILE OF BACKINT: D:\sapdb\data\wrk\backint\backint.err
MAXIMAL DELAY OF BACKINT CALL: 30
Error Logs:
2010-03-30 17:38:35
Using environment variable 'TEMP' with value 'C:\Windows\TEMP' as directory for temporary files and pipes.
Using connection to Backint for MaxDB Interface.
2010-03-30 17:38:35
Checking existence and configuration of Backint for MaxDB.
Using environment variable 'BSI_ENV' with value 'D:\sapdb\data\wrk\LCD\bsi.env' as path of the configuration file of Backint for MaxDB.
Reading the Backint for MaxDB configuration file 'D:\sapdb\data\wrk\LCD\bsi.env'.
Found keyword 'BACKINT' with value 'D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe'.
Found keyword 'INPUT' with value 'D:\sapdb\data\wrk\backint\sapdb.in'.
Found keyword 'OUTPUT' with value 'D:\sapdb\data\wrk\backint\sapdb.out'.
Found keyword 'ERROROUTPUT' with value 'D:\sapdb\data\wrk\backint\sapdb.err'.
Found keyword 'PARAMETERFILE' with value 'D:\sapdb\data\wrk\LCD\maxdb_config.par'.
Found keyword 'ORIGINAL_RUNDIRECTORY' with value 'L:\sapdb\LCD\sapdata'.
Finished reading of the Backint for MaxDB configuration file.
Using 'D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe' as Backint for MaxDB program.
Using 'D:\sapdb\data\wrk\backint\sapdb.in' as input file for Backint for MaxDB.
Using 'D:\sapdb\data\wrk\backint\sapdb.out' as output file for Backint for MaxDB.
Using 'D:\sapdb\data\wrk\backint\sapdb.err' as error output file for Backint for MaxDB.
Using 'D:\sapdb\data\wrk\LCD\maxdb_config.par' as parameter file for Backint for MaxDB.
Using '300' seconds as timeout for Backint for MaxDB in the case of success.
Using '300' seconds as timeout for Backint for MaxDB in the case of failure.
Using 'L:\sapdb\LCD\sapdata\dbm.knl' as backup history of a database to migrate.
Using 'L:\sapdb\LCD\sapdata\dbm.ebf' as external backup history of a database to migrate.
Checking availability of backups using backint's inquire function.
Check passed successful.
2010-03-30 17:38:35
Checking medium.
Check passed successfully.
2010-03-30 17:38:35
Preparing backup.
Setting environment variable 'BI_CALLER' to value 'DBMSRV'.
Setting environment variable 'BI_REQUEST' to value 'NEW'.
Setting environment variable 'BI_BACKUP' to value 'FULL'.
Constructed Backint for MaxDB call 'D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe -u LCD -f backup -t file -p D:\sapdb\data\wrk\LCD\maxdb_config.par -i D:\sapdb\data\wrk\backint\sapdb.in -c'.
Created temporary file 'D:\sapdb\data\wrk\backint\sapdb.out' as output for Backint for MaxDB.
Created temporary file 'D:\sapdb\data\wrk\backint\sapdb.err' as error output for Backint for MaxDB.
Writing '
.\pipe\BACKscd #PIPE' to the input file.
Prepare passed successfully.
2010-03-30 17:38:35
Starting database action for the backup.
Requesting 'SAVE DATA QUICK TO '
.\pipe\BACKscd' PIPE BLOCKSIZE 8 NO CHECKPOINT MEDIANAME 'Back123'' from db-kernel.
The database is working on the request.
2010-03-30 17:38:35
Waiting until database has prepared the backup.
Asking for state of database.
2010-03-30 17:38:35 Database is still preparing the backup.
Waiting 1 second ... Done.
Asking for state of database.
2010-03-30 17:38:36 Database has finished preparation of the backup.
The database has prepared the backup successfully.
2010-03-30 17:38:36
Starting Backint for MaxDB.
Starting Backint for MaxDB process 'D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe -u LCD -f backup -t file -p D:\sapdb\data\wrk\LCD\maxdb_config.par -i D:\sapdb\data\wrk\backint\sapdb.in -c >>D:\sapdb\data\wrk\backint\sapdb.out 2>>D:\sapdb\data\wrk\backint\sapdb.err'.
Process was started successfully.
Backint for MaxDB has been started successfully.
2010-03-30 17:38:36
Waiting for end of the backup operation.
2010-03-30 17:38:36 The backup tool process has finished work with return code 2.
2010-03-30 17:38:36 The backup tool is not running.
2010-03-30 17:38:36 The database is working on the request.
2010-03-30 17:38:36 The database is working on the request.
2010-03-30 17:38:41 The database is working on the request.
2010-03-30 17:38:51 The database is working on the request.
2010-03-30 17:39:06 The database is working on the request.
2010-03-30 17:39:26 The database is working on the request.
2010-03-30 17:39:37 Canceling Utility-task after a timeout of 60 seconds elapsed ... OK.
2010-03-30 17:39:38 The database has finished work on the request.
Receiving a reply from the database kernel.
Got the following reply from db-kernel:
SQL-Code :-903
The backup operation has ended.
2010-03-30 17:39:38
Filling reply buffer.
Have encountered error -24920:
The backup tool failed with 2 as sum of exit codes. The database request was canceled and ended with error -903.
Constructed the following reply:
ERR
-24920,ERR_BACKUPOP: backup operation was unsuccessful
The backup tool failed with 2 as sum of exit codes. The database request was canceled and ended with error -903.
Reply buffer filled.
2010-03-30 17:39:38
Cleaning up.
Copying output of Backint for MaxDB to this file.
**-- Begin of output of Backint for MaxDB (D:\sapdb\data\wrk\backint\sapdb.out)--**
**Data Protection for SAP(R)**
**Interface between BRTools and Tivoli Storage Manager***
**- Version 6, Release 1, Modification 0.0 for Win x64 -**
**Build: 358 compiled on Nov 4 2008**
**(c) Copyright IBM Corporation, 1996, 2008, All Rights Reserved.**
**BKI8310E: The keyword MAXIMAL is not allowed.**
**BKI1001E: syntax error in file 'D:\sapdb\data\wrk\LCD\maxdb_config.par'. Exiting program.**
**BKI0020I: End of program at: 03/30/10 17:38:36 .**
**BKI0021I: Elapsed time: 00 sec .**
**BKI0024I: Return code is: 2.**
End of output of Backint for MaxDB (D:\sapdb\data\wrk\backint\sapdb.out)----
Removed Backint for MaxDB's temporary output file 'D:\sapdb\data\wrk\backint\sapdb.out'.
Copying error output of Backint for MaxDB to this file.
Begin of error output of Backint for MaxDB (D:\sapdb\data\wrk\backint\sapdb.err)----
End of error output of Backint for MaxDB (D:\sapdb\data\wrk\backint\sapdb.err)----
Removed Backint for MaxDB's temporary error output file 'D:\sapdb\data\wrk\backint\sapdb.err'.
Removed the Backint for MaxDB input file 'D:\sapdb\data\wrk\backint\sapdb.in'.
Have finished clean up successfully.
Any help will be appreciated.
Thanks,
Miral.> We are using TSM backint interface for Oracle database. We are in the process of implementing SCM. We would like to schedule MaxDB backup through backint interface for Oracle.
> *BSI File:*
>
> BACKINT D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe
> *Parameter File - MaxDB_config*
> STAGING AREA: D:\TEMP\STAGE1 1024000 KB
> FILES PER BACKINT CALL: 2
> BACKINT: D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe
>
> Using 'D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe' as Backint for MaxDB program.
> 2010-03-30 17:39:38
> Cleaning up.
> Copying output of Backint for MaxDB to this file.
> **Data Protection for SAP(R)**
> **Interface between BRTools and Tivoli Storage Manager***
> **- Version 6, Release 1, Modification 0.0 for Win x64 -**
> **BKI8310E: The keyword MAXIMAL is not allowed.**
> **BKI1001E: syntax error in file 'D:\sapdb\data\wrk\LCD\maxdb_config.par'. Exiting program.**
> **BKI0020I: End of program at: 03/30/10 17:38:36 .**
> **BKI0021I: Elapsed time: 00 sec .**
> **BKI0024I: Return code is: 2.**
>
> -
End of output of Backint for MaxDB (D:\sapdb\data\wrk\backint\sapdb.out)----
> Removed Backint for MaxDB's temporary output file 'D:\sapdb\data\wrk\backint\sapdb.out'.
> Copying error output of Backint for MaxDB to this file.
> -
Begin of error output of Backint for MaxDB (D:\sapdb\data\wrk\backint\sapdb.err)----
@Markus: thanks for the hint with the quote-formatting option!
Concerning the issue:
Sorry, but you misunderstood the way how the general BACKINT for Oracle interface is used with MaxDB.
See, MaxDB comes with a own BACKINT executable.
This is a enhanced BACKINT tools that allows pipes as data input channels - which is not supported by the Backint for Oracle.
The MaxDB Backint serves as a adapter program between the MaxDB Kernel and the backint for Oracle program.
So instead of
BACKINT: D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe
you should point it to the MaxDB provided adapater program.
I propose to revisit the documentation on that topic [Connecting to a Backint for Oracle Interface |http://maxdb.sap.com/doc/7_7/45/746a5712e14022e10000000a1553f6/content.htm].
best regards,
Lars -
Backup 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 -
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. -
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 MaxDB 7.7.06.09 to Veritas Netbackup 6.5 fails
We want to backup MaxDB to Veritas Netbackup server.
According documentation found about this topic the backup is configured
by creating 3 files: bsi.env, initWDO.par (for backint for MaxDB) and
initWDO.utl (for backint for Oracle). The contents of these files are shown below.
When running the backup, it seems that backint for MaxDB ends with return code 2,
the error message received is:
-24920,ERR_BACKUPOP: backup operation was unsuccessful
The backup tool failed with 2 as sum of exit codes.
Unfortunately no further errors/warnings are shown that points in any direction
what's going wrong here.
We start the backup via the following dbmcli-command:
dbmcli -u control,****** -d WDO -uUTL control,****** backup_start BACKData_WDO
(for the time being without xuser entries, first make sure the backup is ok)
The files dbm.ebl, dbm.prt and several others do not show any additional details/hints.
It seems as if the "save data quick" to the named pipe is ok, the sql-code returns "0".
After this the backint for MaxDB should read the named pipe and write it to stage-files,
but backint (for MaxDB) ends with return code 2.
Any idea what might go wrong here?
With kind regards,
R. Hoogeveen
The Netherlands
File bsi.env:
=========
BACKINT /sapdb/WDO/db/bin/backint
INPUT /tmp/backint4maxdb_WDO.in
OUTPUT /tmp/backint4maxdb_WDO.out
ERROROUTPUT /tmp/backint4maxdb_WDO.err
PARAMETERFILE /sapdb/data/wrk/WDO/initWDO.par
TIMEOUT_SUCCESS 600
TIMEOUT_FAILURE 300
ORIGINAL_RUNDIRECTORY /sapdb/data/wrk/WDO
File initWDO.par:
=============
STAGING AREA: /tmp/stageWDO 1 GB
FILES PER BACKINT CALL: 1
BACKINT: /usr/openv/netbackup/bin/backint
PARAMETERFILE OF BACKINT: /sapdb/data/wrk/WDO/initWDO.utl
HISTORY FILE: /sapdb/data/wrk/WDO/backint_history_WDO.log
INPUTFILE FOR BACKINT: /tmp/backint4ora_WDO.in
OUTPUTFILE FOR BACKINT: /tmp/backint4ora_WDO.out
ERRORFILE FOR BACKINT: /tmp/backint4ora_WDO.err
MAXIMAL DELAY OF BACKINT CALL: 30
File initWDO.utl:
=============
switch_list /tmp/.switch_WDO.lis
switch_sem /tmp/.switch_WDO.sem
switch_log /tmp/.switch_WDO.log
drives 1
client wdocsz01
server backfire
policy sap_WDOLars,
The /tmp/backint4maxdb.err file tells me:
Backint for Oracle was unsuccessful.
(Unfortunately that was all information in this file.)
The backint4ora.in file tells me:
/tmp/stageWDO.0
(looks ok to me, also at the time backint4ora was started the stage file was created with non-zero size)
The backint4ora.out file tells me:
ERROR: incorrect format or option in .utl file (-p)
(this seems as if the -p option is not recognized by the backint4ora executable)
When I run this executable manually as user sdb it shows me the commandline that I should use, including the -p option.
One strange thing I notice is that the order of the options is different from the commandline that is executed.
(in the usage it shows -p as almost last parameter, the command executed has -p in the middle; I will see if I can execute the backint4ora command manually, since I have the stage file available, I have copied it during the process)
The backint4ora.err file is empty.
The commandline of the dbmcli command I execute shows me another interesting error message,
this might also be the source of all problems here.
-24920,ERR_BACKUPOP: backup operation was unsuccessful
Could not get external backup ID's from the backup tool.
I tried to retrieve the external backup id's manually for medium BACKDataWDO, it show me OK without any external backup id's.
I am not sure, but I think this is correct since no successfull backup was created yet with external backup tool.
Can it also be that the parameter "history file" from the initWDO.par file is set wrong?
Currently it is set to "/sapdb/data/wrk/WDO/backint_history_WDO.log" (see above also), but I can imagine
that this should be set to the dbm.knl or dbm.ebf file ??
With kind regards,
Roger Hoogeveen -
Is there a way on maxdb to force netbackup to use different initSID.utl fil
(This thread refers to a question that was posted to a blog and where the proper location to handle it is this forum)
Is there a way on maxdb to force netbackup to use different initSID.utl files ? I have try to do it with different bsi.env file . But if i start the backup it keep on asking for the default bsi.env file in /sapdb/data/wrk/SID directory . I have set the variable BSI.ENV to the new file but it looks like it ignore it. Its on a sun solaris operating system
Due to security reasons the DBM server process does no longer inherit environment variables from its caller, e.g. dbmcli.
see PTS 1155045, as especially in the area of external backup tools inheriting environment settings seem to be rather common.
Idea is to add BSI_ENV to the dbm.cfg file with a command like:
dbmcli -d ... -u ... dbm_configset BSI_ENV
For further information please refer to this documentation section
or for Backint also here
Best regards
JörgHi Jörg,
hmmm. I'd guess there are some problem with for which user the environment variables have been defined...
Anyhow, usually it's easier not to use the environment variables but to provide the dbm-server it's own runtime variables via dbm_configset.
Check the old thread archive_stage and archive_stage_repeat to different NSR_POOLs for an example application of this.
regards,
Lars -
MaxDB install failure on Win 2003 Server
Win 2003 Server
MaxDB v 7.6.05.09
HP Proliant G5
Good morning,
We've got a problem with a MaxDB install on a fresh Win 2003 server.
- The first install process and the demo database worked fine
- We tried to create a new database instance and it hung. As nothing was working as expected we decided to uninstall maxdb and all its component and to re-start from a clean process. That's were things are becoming weird :
- The first time the setup assistant hung when installing the kernel
- The secund time the setup assistant hung when installing the demo database
- Every following test hangs when installing the kernel
We tried to do a clean uninstall MaxDB, to watch which registry keys we should restore... but nothings worked as expected.
We found a link at this address describing the same problem but it doesn't provide us anything to solve our problem.
Here is our log file :
INSTALLER_INFO: Version = 7.6.05 Build 009-123-191-997
INSTALLER_INFO: Changelist = 191997
INSTALLER_INFO: MakeId = 323091
INSTALLER_INFO: Type = kit
SYS_INFO: Host name = SRVBATINOR
SYS_INFO: System = Windows
SYS_INFO: Architecture = I386
SYS_INFO: Version = NT 5.2
SYS_INFO: Subversion = Service Pack 2
MSG: collector found 12 archives
MSG: debug package SDBBAS.SDB is valid
MSG: debug package SDBKRN.SDB is valid
MSG: debug package SDBUTL.SDB is valid
MSG: initializing package "Base"
MSG: calling preinstall...
MSG: service "sql6" in "C:/WINDOWS/system32/drivers/etc/services" found
MSG: service "sapdbni72" in "C:/WINDOWS/system32/drivers/etc/services" found
MSG: Template set indep data path to "c:/documents and settings/all users/application data/sdb/data"
MSG: Template set indep programs path to "c:/program files/sdb/programs"
ACTION: make directory "c:/documents and settings/all users/application data/sdb/data/config" mode "775"
ACTION: make directory "c:/documents and settings/all users/application data/sdb/data/config/install" mode "775"
MSG: InstallRegistry: space check ok: 41676028 kb on C: (51203980 kb total) available
MSG: install registry successfully locked
MSG: InstallRegistry::Log: space check ok: 41676028 kb on C: (51203980 kb total) available
MSG: writing 0 packages
MSG: net install registry size = 63 bytes
MSG: wrote install registry (125 bytes)
MSG: InstallRegistry: reserved 1024 kb disk space
getRelease():C:/Program Files/SDB/MAXDB1/pgm/kernel.exe not found
MSG: migrate server installation data for INSTROOT "c:/program files/sdb/maxdb1"
MSG: initializing package "Server Utilities"
MSG: calling preinstall...
MSG: path was set by preinstall script (c:/program files/sdb/programs)
MSG: initializing package "Database Kernel"
MSG: calling preinstall...
MSG: Template or instance update set dependent path to c:/program files/sdb/maxdb1
Msg: checking update of package "Database Kernel" in C:Program Filessdbmaxdb1
MSG: installed package is flaged as invalid => skipping update check
MSG: initializing package "Redist Python"
MSG: calling preinstall...
MSG: path was set by preinstall script (c:/program files/sdb/programs)
MSG: initializing package "Loader"
MSG: calling preinstall...
MSG: path was set by preinstall script (c:/program files/sdb/programs)
MSG: initializing package "ODBC"
MSG: calling preinstall...
MSG: path was set by preinstall script (c:/program files/sdb/programs)
MSG: initializing package "Messages"
MSG: calling preinstall...
MSG: path was set by preinstall script (c:/program files/sdb/programs)
MSG: initializing package "JDBC"
MSG: calling preinstall...
MSG: path was set by preinstall script (c:/program files/sdb/programs)
MSG: initializing package "Synchronization Manager"
MSG: calling preinstall...
MSG: path was set by preinstall script (c:/program files/sdb/programs)
MSG: initializing package "SQLDBC"
MSG: calling preinstall...
MSG: path was set by preinstall script (c:/program files/sdb/programs)
MSG: initializing package "MaxDB PHP Driver"
MSG: calling preinstall...
MSG: path was set by preinstall script (c:/program files/sdb/programs)
MSG: initializing package "DB Analyzer"
MSG: calling preinstall...
MSG: path was set by preinstall script (c:/program files/sdb/programs)
ACTION: make directory "C:/Program Files/sdb" mode "555"
ACTION: make directory "C:/Program Files/sdb/programs" mode "555"
STDOUT: start extraction test run of "C:/DOCUME1/ADMINI1/LOCALS~1/Temp/Max31.tmp/SDBBAS.TGZ"
MSG: running postprepare of package Base
STDOUT: start extraction test run of "C:/DOCUME1/ADMINI1/LOCALS~1/Temp/Max31.tmp/SDBUTL.TGZ"
ACTION: make directory "C:/Program Files/sdb/MAXDB1" mode "555"
STDOUT: start extraction test run of "C:/DOCUME1/ADMINI1/LOCALS~1/Temp/Max31.tmp/SDBKRN.TGZ"
MSG: running postprepare of package Database Kernel
STDOUT: start extraction test run of "C:/DOCUME1/ADMINI1/LOCALS~1/Temp/Max31.tmp/SDBRDPY.TGZ"
MSG: running postprepare of package Redist Python
STDOUT: start extraction test run of "C:/DOCUME1/ADMINI1/LOCALS~1/Temp/Max31.tmp/SDBLD.TGZ"
MSG: running postprepare of package Loader
STDOUT: start extraction test run of "C:/DOCUME1/ADMINI1/LOCALS~1/Temp/Max31.tmp/SDBODBC.TGZ"
MSG: running postprepare of package ODBC
STDOUT: start extraction test run of "C:/DOCUME1/ADMINI1/LOCALS~1/Temp/Max31.tmp/SDBMSG.TGZ"
MSG: running postprepare of package Messages
STDOUT: start extraction test run of "C:/DOCUME1/ADMINI1/LOCALS~1/Temp/Max31.tmp/SDBJDBC.TGZ"
STDOUT: start extraction test run of "C:/DOCUME1/ADMINI1/LOCALS~1/Temp/Max31.tmp/SYNCMAN.TGZ"
MSG: running postprepare of package Synchronization Manager
STDOUT: start extraction test run of "C:/DOCUME1/ADMINI1/LOCALS~1/Temp/Max31.tmp/SDBC.TGZ"
MSG: running postprepare of package Database Connectivity
STDOUT: start extraction test run of "C:/DOCUME1/ADMINI1/LOCALS~1/Temp/Max31.tmp/SDBPHP.TGZ"
STDOUT: start extraction test run of "C:/DOCUME1/ADMINI1/LOCALS~1/Temp/Max31.tmp/SDBANA.TGZ"
MSG: running postprepare of package DB Analyzer
MSG: space check ok: 41672820 kb on (51203980 kb total) available
MSG: packagedata of package Base changed
MSG: writing 2 packages
MSG: net install registry size = 4113 bytes
MSG: wrote install registry (5162 bytes)
STDOUT: start real extraction of "C:/DOCUME1/ADMINI1/LOCALS~1/Temp/Max31.tmp/SDBBAS.TGZ"
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 00:58:53 bin/
STDOUT: extracting: -rwxr-xr-x 802816 2008-08-15 21:53:13 bin/dbmevtdisp.exe
STDOUT: extracting: -rwxr-xr-x 294912 2008-08-15 21:49:43 bin/protconv.exe
STDOUT: extracting: -rwxr-xr-x 151552 2008-08-15 20:11:07 bin/sdbconfig.exe
STDOUT: extracting: -rwxr-xr-x 7168 2008-08-16 00:57:39 bin/SDBINST.EXE
STDOUT: extracting: -rwxr-xr-x 6144 2008-08-16 00:57:40 bin/sdbpack.exe
STDOUT: extracting: -rwxr-xr-x 7680 2008-08-16 00:57:40 bin/sdbreg.exe
STDOUT: extracting: -rwxr-xr-x 7680 2008-08-16 00:57:40 bin/sdbregview.exe
STDOUT: extracting: -rwxr-xr-x 13824 2008-08-16 00:57:39 bin/SDBSETUP.EXE
STDOUT: extracting: -rwxr-xr-x 7680 2008-08-16 00:57:39 bin/sdbuninst.exe
STDOUT: extracting: -rwxr-xr-x 7168 2008-08-16 00:57:40 bin/sdbverify.exe
STDOUT: extracting: -rwxr-xr-x 1257472 2008-08-16 00:35:29 bin/sqlcli.exe
STDOUT: extracting: -rwxr-xr-x 40960 2008-08-16 00:05:33 bin/xsysrc.exe
STDOUT: extracting: -rwxr-xr-x 323584 2008-08-15 20:24:45 bin/xtcpupd.exe
STDOUT: extracting: -rwxr-xr-x 294912 2008-08-15 19:55:07 bin/xuser.exe
STDOUT: extracting: -rwxr-xr-x 40960 2008-08-16 00:05:33 bin/x_ping.exe
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 00:58:53 install/
STDOUT: extracting: -rwxr-xr-x 192512 2008-08-16 00:54:07 install/Grid.dll
STDOUT: extracting: -rwxr-xr-x 757760 2008-08-16 00:41:09 install/perl58.dll
STDOUT: extracting: -rw-rr 117099 2008-08-16 00:57:38 install/RESOURCES.TGZ
STDOUT: extracting: -rw-rr 465022 2008-08-16 00:57:38 install/SDBINST.TGZ
STDOUT: extracting: -rwxr-xr-x 421888 2008-08-16 00:57:27 install/sdbrun.dll
STDOUT: extracting: -rwxr-xr-x 1245184 2008-08-16 00:56:33 install/Wx.dll
STDOUT: extracting: -rwxr-xr-x 2265088 2008-08-16 00:53:37 install/wxmsw24.dll
STDOUT: extracting: -rw-rr 64327 2008-08-16 00:57:42 install/WXPERL.TGZ
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 00:58:54 pgm/
STDOUT: extracting: -rwxr-xr-x 2101248 2008-08-15 21:49:55 pgm/dbmcli.exe
STDOUT: extracting: -rwxr-xr-x 2101248 2008-08-15 21:49:55 pgm/dbmcli_HelpInst.exe
STDOUT: extracting: -rwxr-xr-x 217088 2008-08-15 22:11:27 pgm/regupd.exe
STDOUT: extracting: -rwxr-xr-x 307200 2008-08-15 20:25:09 pgm/sqlping.exe
STDOUT: extracting: -rwxr-xr-x 49152 2008-08-15 19:46:03 pgm/sqltcp.dll
STDOUT: extracting: -rwxr-xr-x 49152 2008-08-15 19:46:03 pgm/sqltcp1.dll
STDOUT: extracting: -rwxr-xr-x 49152 2008-08-15 19:46:05 pgm/sqltcp2.dll
STDOUT: extracting: -rwxr-xr-x 45056 2008-08-15 19:46:07 pgm/sqltcpn.dll
STDOUT: extracting: -rwxr-xr-x 281952 2008-08-16 00:58:28 pgm/sqluser72.dll
STDOUT: extracting: -rwxr-xr-x 372672 2008-08-16 00:58:32 pgm/sqluser73.dll
STDOUT: extracting: -rwxr-xr-x 393216 2008-08-16 00:58:35 pgm/sqluser74.dll
STDOUT: extracting: -rwxr-xr-x 438272 2008-08-16 00:58:38 pgm/sqluser74n.dll
STDOUT: extracting: -rwxr-xr-x 524288 2008-08-16 00:15:41 pgm/sqluser76.dll
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 00:59:01 Support/
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 00:59:02 Support/Mapfiles/
STDOUT: extracting: -rw-rr 3023564 2008-08-15 21:49:54 Support/Mapfiles/dbmcli.map
STDOUT: extracting: -rw-rr 1265024 2008-08-15 21:53:13 Support/Mapfiles/dbmevtdisp.map
STDOUT: extracting: -rw-rr 115063 2008-08-15 20:28:06 Support/Mapfiles/sqltcp.map
STDOUT: extracting: -rw-rr 115066 2008-08-15 20:28:07 Support/Mapfiles/sqltcp1.map
STDOUT: extracting: -rw-rr 115148 2008-08-15 20:28:09 Support/Mapfiles/sqltcp2.map
STDOUT: extracting: -rw-rr 108889 2008-08-15 20:28:13 Support/Mapfiles/sqltcpn.map
STDOUT: extracting: -rw-rr 125887 2008-08-16 00:58:30 Support/Mapfiles/sqluser72.map
STDOUT: extracting: -rw-rr 147341 2008-08-16 00:58:33 Support/Mapfiles/sqluser73.map
STDOUT: extracting: -rw-rr 258131 2008-08-16 00:58:36 Support/Mapfiles/sqluser74.map
STDOUT: extracting: -rw-rr 739428 2008-08-16 00:58:39 Support/Mapfiles/sqluser74n.map
STDOUT: extracting: -rw-rr 916710 2008-08-16 00:15:41 Support/Mapfiles/sqluser76.map
STDOUT: extracting: -rw-rr 593052 2008-08-15 20:24:45 Support/Mapfiles/xtcpupd.map
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 00:59:04 symbols/
STDOUT: extracting: -rw-rr 8252416 2008-08-15 21:49:54 symbols/dbmcli.pdb
STDOUT: extracting: -rw-rr 3836928 2008-08-15 21:53:13 symbols/dbmevtdisp.pdb
STDOUT: extracting: -rw-rr 289792 2008-08-15 20:28:06 symbols/sqltcp.pdb
STDOUT: extracting: -rw-rr 289792 2008-08-15 20:28:07 symbols/sqltcp1.pdb
STDOUT: extracting: -rw-rr 289792 2008-08-15 20:28:09 symbols/sqltcp2.pdb
STDOUT: extracting: -rw-rr 281600 2008-08-15 20:28:13 symbols/sqltcpn.pdb
STDOUT: extracting: -rw-rr 1887232 2008-08-16 00:58:37 symbols/sqluser74.pdb
STDOUT: extracting: -rw-rr 2059264 2008-08-16 00:58:40 symbols/sqluser74n.pdb
STDOUT: extracting: -rw-rr 4705280 2008-08-15 20:24:44 symbols/xtcpupd.pdb
STDOUT: checking unpacked archive... MSG: check file "Support/Mapfiles/sqluser72.map": ok
MSG: check file "symbols/sqltcpn.pdb": ok
MSG: check file "pgm/dbmcli_HelpInst.exe": ok
MSG: check file "bin/x_ping.exe": ok
MSG: check file "Support/Mapfiles/sqluser74.map": ok
MSG: check file "bin/SDBINST.EXE": ok
MSG: check file "install/SDBINST.TGZ": ok
MSG: check file "pgm/sqluser74.dll": ok
MSG: check file "symbols/dbmcli.pdb": ok
MSG: check file "symbols/sqltcp1.pdb": ok
MSG: check file "bin/SDBSETUP.EXE": ok
MSG: check file "pgm/sqluser74n.dll": ok
MSG: check file "Support/Mapfiles/sqltcp.map": ok
MSG: check file "bin/protconv.exe": ok
MSG: check file "symbols/sqltcp.pdb": ok
MSG: check file "Support/Mapfiles/sqltcpn.map": ok
MSG: check file "install/WXPERL.TGZ": ok
MSG: check file "install/wxmsw24.dll": ok
MSG: check file "install/sdbrun.dll": ok
MSG: check file "bin/xuser.exe": ok
MSG: check file "pgm/sqluser73.dll": ok
MSG: check file "pgm/sqluser76.dll": ok
MSG: check file "symbols/xtcpupd.pdb": ok
MSG: check file "pgm/sqltcp1.dll": ok
MSG: check file "Support/Mapfiles/sqluser74n.map": ok
MSG: check file "pgm/dbmcli.exe": ok
MSG: check file "pgm/sqltcp.dll": ok
MSG: check file "install/RESOURCES.TGZ": ok
MSG: check file "Support/Mapfiles/dbmevtdisp.map": ok
MSG: check file "Support/Mapfiles/sqluser73.map": ok
MSG: check file "Support/Mapfiles/xtcpupd.map": ok
MSG: check file "bin/sdbverify.exe": ok
MSG: check file "bin/xsysrc.exe": ok
MSG: check file "Support/Mapfiles/sqltcp1.map": ok
MSG: check file "Support/Mapfiles/sqltcp2.map": ok
MSG: check file "install/perl58.dll": ok
MSG: check file "Support/Mapfiles/sqluser76.map": ok
MSG: check file "bin/sdbuninst.exe": ok
MSG: check file "pgm/regupd.exe": ok
MSG: check file "symbols/dbmevtdisp.pdb": ok
MSG: check file "pgm/sqlping.exe": ok
MSG: check file "bin/sdbpack.exe": ok
MSG: check file "symbols/sqltcp2.pdb": ok
MSG: check file "pgm/sqltcpn.dll": ok
MSG: check file "pgm/sqluser72.dll": ok
MSG: check file "symbols/sqluser74.pdb": ok
MSG: check file "Support/Mapfiles/dbmcli.map": ok
MSG: check file "pgm/sqltcp2.dll": ok
MSG: check file "bin/dbmevtdisp.exe": ok
MSG: check file "bin/sdbregview.exe": ok
MSG: check file "bin/xtcpupd.exe": ok
MSG: check file "install/Grid.dll": ok
MSG: check file "bin/sdbconfig.exe": ok
MSG: check file "symbols/sqluser74n.pdb": ok
MSG: check file "bin/sdbreg.exe": ok
MSG: check file "install/Wx.dll": ok
MSG: check file "bin/sqlcli.exe": ok
STDOUT: ok
STDOUT: checking system libraries...MSG: update test sytem file "C:/WINDOWS/system32/mfc70.dll"
MSG: system file "mfc70.dll" inside archive has version 7.00.9466.0
MSG: installed system file "mfc70.dll" is up to date (version 7.00.9466.0)
MSG: update test sytem file "C:/WINDOWS/system32/mfc70u.dll"
MSG: system file "mfc70u.dll" inside archive has version 7.00.9466.0
MSG: installed system file "mfc70u.dll" is up to date (version 7.00.9466.0)
MSG: update test sytem file "C:/WINDOWS/system32/mfc71.dll"
MSG: system file "mfc71.dll" inside archive has version 7.10.3077.0
MSG: installed system file "mfc71.dll" is up to date (version 7.10.3077.0)
MSG: update test sytem file "C:/WINDOWS/system32/mfc71u.dll"
MSG: system file "mfc71u.dll" inside archive has version 7.10.3077.0
MSG: installed system file "mfc71u.dll" is up to date (version 7.10.3077.0)
MSG: update test sytem file "C:/WINDOWS/system32/msvcr70.dll"
MSG: system file "msvcr70.dll" inside archive has version 7.00.9466.0
MSG: installed system file "msvcr70.dll" is up to date (version 7.00.9466.0)
MSG: update test sytem file "C:/WINDOWS/system32/msvcr71.dll"
MSG: system file "msvcr71.dll" inside archive has version 7.10.3052.4
MSG: installed system file "msvcr71.dll" is up to date (version 7.10.3052.4)
STDOUT: ok
SYS: "C:Program Filessdbprograms insdbconfig.exe" "IndepPrograms=C:Program Filessdbprograms"
SYS: "C:Program Filessdbprograms insdbconfig.exe" "IndepData=C:Documents and SettingsAll UsersApplication Datasdbdata"
STDOUT: system path updated successfully
STDOUT: please reboot your system after installation to take effect changes
MSG: registry subkey "SOFTWAREMicrosoft" exist
MSG: registry subkey "SOFTWAREMicrosoftWindows" exist
MSG: registry subkey "SOFTWAREMicrosoftWindowsCurrentVersion" exist
MSG: registry subkey "SOFTWAREMicrosoftWindowsCurrentVersionUninstall" exist
MSG: created registry subkey "SOFTWAREMicrosoftWindowsCurrentVersionUninstallSAP DB (ALL)" successfully
ACTION: make directory "C:/Documents and Settings/All Users/Menu DÈmarrer/Programmes/MaxDB" mode "775"
ACTION: make directory "C:/Documents and Settings/All Users/Menu DÈmarrer/Programmes/MaxDB/Command Line Tools" mode "775"
MSG: start menu shortcuts created
MSG: packagedata of package Base changed
MSG: writing 2 packages
MSG: net install registry size = 32157 bytes
MSG: wrote install registry (36384 bytes)
MSG: packagedata of package Server Utilities changed
MSG: writing 3 packages
MSG: net install registry size = 32773 bytes
MSG: wrote install registry (37403 bytes)
STDOUT: start real extraction of "C:/DOCUME1/ADMINI1/LOCALS~1/Temp/Max31.tmp/SDBUTL.TGZ"
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 00:59:53 bin/
STDOUT: extracting: -rwxr-xr-x 65536 2008-08-15 21:52:21 bin/sdbinfo.exe
STDOUT: extracting: -rwxr-xr-x 356352 2008-08-16 00:05:31 bin/sqlrun.dll
STDOUT: extracting: -rwxr-xr-x 40960 2008-08-16 00:05:33 bin/sysmon.exe
STDOUT: extracting: -rwxr-xr-x 40960 2008-08-16 00:05:33 bin/xbackup.exe
STDOUT: extracting: -rwxr-xr-x 40960 2008-08-16 00:05:33 bin/xinstinfo.exe
STDOUT: extracting: -rwxr-xr-x 40960 2008-08-16 00:05:33 bin/xpu.exe
STDOUT: extracting: -rwxr-xr-x 40960 2008-08-16 00:05:33 bin/x_analys.exe
STDOUT: extracting: -rwxr-xr-x 40960 2008-08-16 00:05:33 bin/x_cons.exe
STDOUT: extracting: -rwxr-xr-x 40960 2008-08-16 00:05:33 bin/x_server.exe
STDOUT: extracting: -rwxr-xr-x 40960 2008-08-16 00:05:33 bin/x_show.exe
STDOUT: extracting: -rwxr-xr-x 40960 2008-08-16 00:05:33 bin/x_start.exe
STDOUT: extracting: -rwxr-xr-x 40960 2008-08-16 00:05:33 bin/x_stop.exe
STDOUT: extracting: -rwxr-xr-x 40960 2008-08-16 00:05:33 bin/x_wiz.exe
STDOUT: extracting: -rwxr-xr-x 40960 2008-08-16 00:05:33 bin/x_wizard.exe
STDOUT: extracting: -rwxr-xr-x 40960 2008-08-16 00:05:33 bin/x_wizstop.exe
STDOUT: extracting: -rwxr-xr-x 40960 2008-08-16 00:05:33 bin/x_wiztrc.exe
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 00:59:53 env/
STDOUT: extracting: -rw-rr 122 2008-08-15 22:02:13 env/serv.use
STDOUT: extracting: -rw-rr 245 2008-08-15 22:02:13 env/xstart.use
STDOUT: extracting: -rw-rr 542 2008-08-15 22:02:13 env/xstop.use
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 00:59:53 etc/
STDOUT: extracting: -rw-rr 207 2008-08-15 19:42:23 etc/VERSIONS
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 00:59:53 pgm/
STDOUT: extracting: -rwxr-xr-x 483328 2008-08-15 20:11:45 pgm/serv.exe
STDOUT: extracting: -rwxr-xr-x 307200 2008-08-15 20:11:09 pgm/show.exe
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 00:59:54 Support/
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 00:59:54 Support/Mapfiles/
STDOUT: extracting: -rw-rr 839796 2008-08-15 20:11:44 Support/Mapfiles/serv.map
STDOUT: extracting: -rw-rr 540173 2008-08-15 20:11:08 Support/Mapfiles/show.map
STDOUT: extracting: -rw-rr 615852 2008-08-16 00:05:31 Support/Mapfiles/sqlrun.map
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 00:59:55 symbols/
STDOUT: extracting: -rw-rr 2575360 2008-08-15 20:11:44 symbols/serv.pdb
STDOUT: extracting: -rw-rr 2051072 2008-08-15 20:11:08 symbols/show.pdb
STDOUT: extracting: -rw-rr 2075648 2008-08-16 00:05:31 symbols/sqlrun.pdb
STDOUT: checking unpacked archive... MSG: check file "bin/x_wizstop.exe": ok
MSG: check file "bin/x_analys.exe": ok
MSG: check file "bin/x_cons.exe": ok
MSG: check file "bin/xpu.exe": ok
MSG: check file "bin/sysmon.exe": ok
MSG: check file "bin/x_start.exe": ok
MSG: check file "pgm/serv.exe": ok
MSG: check file "env/xstart.use": ok
MSG: check file "bin/x_server.exe": ok
MSG: check file "bin/sqlrun.dll": ok
MSG: check file "etc/VERSIONS": ok
MSG: check file "bin/x_wiz.exe": ok
MSG: check file "bin/xbackup.exe": ok
MSG: check file "Support/Mapfiles/sqlrun.map": ok
MSG: check file "symbols/show.pdb": ok
MSG: check file "bin/x_show.exe": ok
MSG: check file "symbols/sqlrun.pdb": ok
MSG: check file "env/serv.use": ok
MSG: check file "env/xstop.use": ok
MSG: check file "symbols/serv.pdb": ok
MSG: check file "pgm/show.exe": ok
MSG: check file "bin/x_wizard.exe": ok
MSG: check file "bin/sdbinfo.exe": ok
MSG: check file "bin/xinstinfo.exe": ok
MSG: check file "bin/x_wiztrc.exe": ok
MSG: check file "Support/Mapfiles/show.map": ok
MSG: check file "Support/Mapfiles/serv.map": ok
MSG: check file "bin/x_stop.exe": ok
STDOUT: ok
SYS: "c:program filessdbprograms inx_server.exe" install: 19712 INFO: Service 'XServer' is already installed
SYS: "c:program filessdbprograms inx_server.exe" remove: 19710 INFO: Service 'XServer' removed successfully
SYS: "c:program filessdbprograms inx_server.exe" install: 19709 INFO: Service 'XServer' installed successfully
MSG: SYSTEM PATH is up to date
MSG: packagedata of package Server Utilities changed
MSG: writing 3 packages
MSG: net install registry size = 39793 bytes
MSG: wrote install registry (45406 bytes)
MSG: packagedata of package Database Kernel changed
MSG: writing 3 packages
MSG: net install registry size = 39793 bytes
MSG: wrote install registry (45405 bytes)
MSG: no function "register" in package Database Kernel
MSG: set function reference "unregister" in package Database Kernel
MSG: set function reference "preuninstall" in package Database Kernel
MSG: set function reference "postuninstall" in package Database Kernel
MSG: no function "verify" in package Database Kernel
STDOUT: unregister Database Kernel 7.6.5.9
WRN: cannot execute command: xregcomp -u "c:program filessdbmaxdb1pgmdbpinstall": cannot create process, Le fichier spÈcifiÈ est introuvable.
WRN: cannot execute command: xregcomp -u "c:program filessdbprogramsliblivecachedbg": cannot create process, Le fichier spÈcifiÈ est introuvable.
SYS: dbmcli -R "c:program filessdbmaxdb1" inst_unreg : Error! Connection failed to node (local) for database (no dbname):
SYS: dbmcli -R "c:program filessdbmaxdb1" inst_unreg : dbmsrv executable not found
STDOUT: start real extraction of "C:/DOCUME1/ADMINI1/LOCALS~1/Temp/Max31.tmp/SDBKRN.TGZ"
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 01:00:15 bin/
STDOUT: extracting: -rwxr-xr-x 274432 2008-08-15 21:51:01 bin/backint.exe
STDOUT: extracting: -rwxr-xr-x 802816 2008-08-15 21:53:13 bin/dbmevtdisp.exe
STDOUT: extracting: -rwxr-xr-x 552960 2008-08-15 21:53:27 bin/dbmevthndl_display.exe
STDOUT: extracting: -rwxr-xr-x 569344 2008-08-15 21:53:37 bin/dbmevthndl_winlog.exe
STDOUT: extracting: -rwxr-xr-x 290816 2008-08-15 21:48:43 bin/dbmsrvctl.exe
STDOUT: extracting: -rwxr-xr-x 41705 2008-08-15 19:51:15 bin/ireport.py
STDOUT: extracting: -rwxr-xr-x 245760 2008-08-15 21:52:11 bin/pipe2file.exe
STDOUT: extracting: -rwxr-xr-x 1232896 2008-08-15 21:51:09 bin/sdbfill.exe
STDOUT: extracting: -rwxr-xr-x 356352 2008-08-16 00:05:31 bin/sqlrun.dll
STDOUT: extracting: -rwxr-xr-x 53248 2008-08-15 19:55:01 bin/sqlver.exe
STDOUT: extracting: -rwxr-xr-x 53248 2008-08-15 19:55:01 bin/sqlwhat.exe
STDOUT: extracting: -rwxr-xr-x 40960 2008-08-16 00:05:33 bin/xkernprot.exe
STDOUT: extracting: -rwxr-xr-x 40960 2008-08-16 00:05:33 bin/xservice.exe
STDOUT: extracting: -rwxr-xr-x 40960 2008-08-16 00:05:33 bin/xtracesort.exe
STDOUT: extracting: -rwxr-xr-x 40960 2008-08-16 00:05:33 bin/x_diagnose.exe
STDOUT: extracting: -rwxr-xr-x 331776 2008-08-15 21:53:55 bin/x_python.exe
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 01:00:07 cluster/
STDOUT: extracting: -rwxr-xr-x 2121728 2008-08-15 20:24:13 cluster/dbmsrv_clu.exe
STDOUT: extracting: -rwxr-xr-x 81920 2008-08-15 20:12:33 cluster/SAPDBMSCSEx.dll
STDOUT: extracting: -rwxr-xr-x 122880 2008-08-15 20:12:43 cluster/sapdbmscsman.dll
STDOUT: extracting: -rwxr-xr-x 77824 2008-08-15 20:12:07 cluster/SAPDBMSCSMan.exe
STDOUT: extracting: -rwxr-xr-x 57344 2008-08-15 20:12:01 cluster/SAPDBMSCSRes.dll
STDOUT: extracting: -rwxr-xr-x 307200 2008-08-15 20:12:57 cluster/service_clu.exe
STDOUT: extracting: -rwxr-xr-x 499712 2008-08-15 20:12:55 cluster/serv_clu.exe
STDOUT: extracting: -rwxr-xr-x 339968 2008-08-15 20:12:53 cluster/stop_clu.exe
STDOUT: extracting: -rwxr-xr-x 339968 2008-08-15 20:12:51 cluster/strt_clu.exe
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 01:00:07 demo/
STDOUT: extracting: -rw-rr 3110911 2008-08-15 19:51:15 demo/HOTEL.py
STDOUT: extracting: -rwxr-xr-x 367 2008-08-15 19:51:15 demo/ltutorial.py
STDOUT: extracting: -rw-rr 11333 2008-08-15 19:51:15 demo/tutoriallib.py
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 01:00:17 doc/
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 01:00:19 doc/FirstSteps/
STDOUT: extracting: -rw-rr 3455 2008-08-15 19:51:15 doc/FirstSteps/index.html
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 01:00:18 doc/FirstSteps/Java/
STDOUT: extracting: -rw-rr 1019 2008-08-15 19:51:15 doc/FirstSteps/Java/DemodbData.class
STDOUT: extracting: -rw-rr 1536 2008-08-15 19:51:15 doc/FirstSteps/Java/DemodbData.java
STDOUT: extracting: -rw-rr 1599 2008-08-15 19:51:15 doc/FirstSteps/Java/HelloMaxDB.class
STDOUT: extracting: -rw-rr 1459 2008-08-15 19:51:15 doc/FirstSteps/Java/HelloMaxDB.java
STDOUT: extracting: -rw-rr 1959 2008-08-15 19:51:15 doc/FirstSteps/Java/HowToJava.html
STDOUT: extracting: -rw-rr 1305 2008-08-15 19:51:15 doc/FirstSteps/Java/StateMaxDB.class
STDOUT: extracting: -rw-rr 1064 2008-08-15 19:51:15 doc/FirstSteps/Java/StateMaxDB.java
STDOUT: extracting: -rw-rr 227 2008-08-15 19:51:15 doc/FirstSteps/maxdbenv.cmd
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 01:00:18 doc/FirstSteps/ODBC/
STDOUT: extracting: -rw-rr 4510 2008-08-15 19:51:15 doc/FirstSteps/ODBC/HelloMaxDB.c
STDOUT: extracting: -rw-rr 1293 2008-08-15 19:51:15 doc/FirstSteps/ODBC/HowToODBC.html
STDOUT: extracting: -rw-rr 393 2008-08-15 19:51:15 doc/FirstSteps/ODBC/Makefile
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 01:00:18 doc/FirstSteps/Perl/
STDOUT: extracting: -rw-rr 973 2008-08-15 19:51:15 doc/FirstSteps/Perl/demodbData.pm
STDOUT: extracting: -rw-rr 1894 2008-08-15 19:51:15 doc/FirstSteps/Perl/HowToPerl.html
STDOUT: extracting: -rwxr-xr-x 960 2008-08-15 19:51:15 doc/FirstSteps/Perl/StateMaxDB.pl
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 01:00:19 doc/FirstSteps/Python/
STDOUT: extracting: -rw-rr 871 2008-08-15 19:51:15 doc/FirstSteps/Python/demodbData.py
STDOUT: extracting: -rwxr-xr-x 859 2008-08-15 19:51:15 doc/FirstSteps/Python/HelloMaxDB-API.py
STDOUT: extracting: -rwxr-xr-x 859 2008-08-15 19:51:15 doc/FirstSteps/Python/HelloMaxDB.py
STDOUT: extracting: -rw-rr 3043 2008-08-15 19:51:15 doc/FirstSteps/Python/HowToPython.html
STDOUT: extracting: -rwxr-xr-x 865 2008-08-15 19:51:15 doc/FirstSteps/Python/StateMaxDB.py
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 01:00:20 doc/FirstSteps/SQLDBC/
STDOUT: extracting: -rw-rr 3522 2008-08-15 19:51:15 doc/FirstSteps/SQLDBC/HelloMaxDB.cpp
STDOUT: extracting: -rw-rr 1329 2008-08-15 19:51:15 doc/FirstSteps/SQLDBC/HowToSQLDBC.html
STDOUT: extracting: -rw-rr 563 2008-08-15 19:51:15 doc/FirstSteps/SQLDBC/Makefile
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 01:00:10 env/
STDOUT: extracting: -rwxr-xr-x 6260 2008-08-15 21:53:37 env/APPS.py
STDOUT: extracting: -rw-rr 3800 2008-08-15 21:53:37 env/CNR3DATA.py
STDOUT: extracting: -rw-rr 8216 2008-08-15 21:53:37 env/CNR3TAB.py
STDOUT: extracting: -rw-rr 201779 2008-08-15 22:02:13 env/cserv.pcf
STDOUT: extracting: -rw-rr 1861 2008-08-15 21:53:37 env/DBANA.py
STDOUT: extracting: -rw-rr 17874 2008-08-15 21:53:39 env/DBMVIEWS.py
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 01:00:08 env/en/
STDOUT: extracting: -rw-rr 7609 2008-08-15 22:02:13 env/en/DBM.en
STDOUT: extracting: -rw-rr 15713 2008-08-15 21:53:39 env/GARBAGE.py
STDOUT: extracting: -rw-rr 249 2008-08-15 22:02:13 env/general.use
STDOUT: extracting: -rwxr-xr-x 1304 2008-08-15 21:53:45 env/getpackages.py
STDOUT: extracting: -rw-rr 1144 2008-08-15 21:53:39 env/INFO.py
STDOUT: extracting: -rw-rr 14609 2008-08-15 21:53:45 env/installib.py
STDOUT: extracting: -rw-rr 90473 2008-08-15 21:53:39 env/JDBC.py
STDOUT: extracting: -rw-rr 396 2008-08-15 22:02:13 env/kernprot.use
STDOUT: extracting: -rwxr-xr-x 949 2008-08-15 21:53:45 env/lapps.py
STDOUT: extracting: -rw-rr 8269 2008-08-15 19:51:15 env/lsystab.py
STDOUT: extracting: -rw-rr 19514 2008-08-15 21:53:39 env/ODBC.py
STDOUT: extracting: -rw-rr 1241 2008-08-15 21:53:39 env/ORADD.py
STDOUT: extracting: -rw-rr 266421 2008-08-15 21:53:41 env/ORADDCOM.py
STDOUT: extracting: -rw-rr 9586 2008-08-15 21:53:41 env/ORADDSYN.py
STDOUT: extracting: -rw-rr 158400 2008-08-15 21:53:41 env/ORADDV.py
STDOUT: extracting: -rw-rr 1400 2008-08-15 21:53:41 env/PRECOM.py
STDOUT: extracting: -rw-rr 50345 2008-08-15 21:53:45 env/REPOSITORY.py
STDOUT: extracting: -rw-rr 61439 2008-08-15 21:53:39 env/SAPDBLOADER.py
STDOUT: extracting: -rw-rr 4483 2008-08-15 21:53:41 env/SHOWCMD.py
STDOUT: extracting: -rw-rr 49869 2008-08-15 21:53:41 env/SQLDBC.py
STDOUT: extracting: -rw-rr 48352 2008-08-15 21:53:41 env/SYSDBA.py
STDOUT: extracting: -rw-rr 59678 2008-08-15 21:53:43 env/SYSDBACOM.py
STDOUT: extracting: -rw-rr 16770 2008-08-15 21:53:43 env/SYSINFO.py
STDOUT: extracting: -rw-rr 114665 2008-08-15 21:53:43 env/SYSINFOCOM.py
STDOUT: extracting: -rw-rr 17793 2008-08-15 21:53:43 env/TRIGGER.py
STDOUT: extracting: -rw-rr 3203 2008-08-15 21:53:43 env/UDE.py
STDOUT: extracting: -rw-rr 6596 2008-08-15 21:53:45 env/WA.py
STDOUT: extracting: -rw-rr 54914 2008-08-15 21:53:43 env/XDD.py
STDOUT: extracting: -rw-rr 106448 2008-08-15 21:53:43 env/XDDCOM.py
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 01:00:11 lib/
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 01:00:11 lib/python2.3/
STDOUT: extracting: -rw-rr 6867 2008-08-15 19:51:15 lib/python2.3/optlib.py
STDOUT: extracting: -rwxr-xr-x 135234 2008-08-15 19:51:15 lib/python2.3/pyexpat.pyd
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 01:00:11 lib/python2.3/sdb/
STDOUT: extracting: -rw-rr 14852 2008-08-15 19:51:15 lib/python2.3/sdb/dbapi.py
STDOUT: extracting: -rwxr-xr-x 507904 2008-08-15 21:54:03 lib/python2.3/sdb/dbm.pyd
STDOUT: extracting: -rwxr-xr-x 487424 2008-08-15 21:54:07 lib/python2.3/sdb/loader.pyd
STDOUT: extracting: -rwxr-xr-x 475136 2008-08-15 21:54:15 lib/python2.3/sdb/sql.pyd
STDOUT: extracting: -rw-rr 208 2008-08-15 19:51:15 lib/python2.3/sdb/__init__.py
STDOUT: extracting: -rwxr-xr-x 61503 2008-08-15 19:51:15 lib/python2.3/zlib.pyd
STDOUT: extracting: -rwxr-xr-x 49218 2008-08-15 19:51:15 lib/python2.3/_socket.pyd
STDOUT: extracting: -rwxr-xr-x 57407 2008-08-15 19:51:15 lib/python2.3/_sre.pyd
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 01:00:11 misc/
STDOUT: extracting: -rw-rr 2437 2008-08-16 00:38:45 misc/create_demo_db.cmd
STDOUT: extracting: -rw-rr 417 2008-08-16 00:38:45 misc/drop_demo_db.cmd
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 01:00:17 pgm/
STDOUT: extracting: -rwxr-xr-x 200704 2008-08-15 21:52:15 pgm/backup.exe
STDOUT: extracting: -rwxr-xr-x 380928 2008-08-15 20:10:53 pgm/cons.exe
STDOUT: extracting: -rwxr-xr-x 45056 2008-08-15 20:10:33 pgm/cr_param.exe
STDOUT: extracting: -rwxr-xr-x 940032 2008-08-15 19:51:15 pgm/dbghelp.dll
STDOUT: extracting: -rwxr-xr-x 299008 2008-08-15 21:49:01 pgm/dbmreg.exe
STDOUT: extracting: -rwxr-xr-x 454656 2008-08-15 21:49:37 pgm/dbmshm.exe
STDOUT: extracting: -rwxr-xr-x 2105344 2008-08-15 21:48:31 pgm/dbmsrv.exe
STDOUT: extracting: -rwxr-xr-x 1843200 2008-08-15 21:49:17 pgm/dbmsrvscd.exe
STDOUT: extracting: -rwxr-xr-x 299008 2008-08-15 21:48:49 pgm/dbmstart.exe
STDOUT: extracting: -rwxr-xr-x 299008 2008-08-15 21:48:53 pgm/dbmstop.exe
STDOUT: extracting: -rwxr-xr-x 299008 2008-08-15 21:49:05 pgm/dbmunreg.exe
STDOUT: extracting: -rwxr-xr-x 69632 2008-08-16 00:15:35 pgm/dbpinstall.dll
STDOUT: extracting: -rwxr-xr-x 1073152 2008-08-15 20:33:23 pgm/diagnose.exe
STDOUT: extracting: -rwxr-xr-x 7258112 2008-08-15 21:48:17 pgm/kernel.exe
STDOUT: extracting: -rwxr-xr-x 118784 2008-08-15 20:25:15 pgm/libhsscopy.dll
STDOUT: extracting: -rwxr-xr-x 1204224 2008-08-16 00:11:25 pgm/liboms.dll
STDOUT: extracting: -rwxr-xr-x 159744 2008-08-16 00:16:23 pgm/libsqlcls.dll
STDOUT: extracting: -rwxr-xr-x 1191936 2008-08-16 00:17:23 pgm/libSQLDBC.dll
STDOUT: extracting: -rwxr-xr-x 1269760 2008-08-16 00:20:23 pgm/libSQLDBC_C.dll
STDOUT: extracting: -rwxr-xr-x 3022848 2008-08-15 22:01:27 pgm/lserver.exe
STDOUT: extracting: -rwxr-xr-x 20545 2008-08-15 19:51:15 pgm/pysapdb.exe
STDOUT: extracting: -rwxr-xr-x 974915 2008-08-15 19:51:15 pgm/python23.dll
STDOUT: extracting: -rw-rr 2071185 2008-08-15 19:51:15 pgm/python23.zip
STDOUT: extracting: -rwxr-xr-x 45056 2008-08-15 20:10:31 pgm/renparam.exe
STDOUT: extracting: -rwxr-xr-x 294912 2008-08-15 20:11:51 pgm/service.exe
STDOUT: extracting: -rwxr-xr-x 417792 2008-08-15 20:11:55 pgm/sqlinst.dll
STDOUT: extracting: -rwxr-xr-x 1359872 2008-08-15 20:11:59 pgm/sqlmsg.dll
STDOUT: extracting: -rwxr-xr-x 319488 2008-08-15 20:11:01 pgm/stop.exe
STDOUT: extracting: -rwxr-xr-x 319488 2008-08-15 20:10:57 pgm/strt.exe
STDOUT: extracting: -rwxr-xr-x 98304 2008-08-15 22:11:33 pgm/StudioUtil.dll
STDOUT: extracting: -rwxr-xr-x 49152 2008-08-15 20:25:11 pgm/sysrc.exe
STDOUT: extracting: -rwxr-xr-x 73728 2008-08-15 20:11:57 pgm/systemrc.exe
STDOUT: extracting: -rwxr-xr-x 229376 2008-08-15 22:11:43 pgm/TableDefC.dll
STDOUT: extracting: -rwxr-xr-x 45056 2008-08-15 21:53:29 pgm/Tools_WinEvtLog.dll
STDOUT: extracting: -rwxr-xr-x 73728 2008-08-15 22:01:47 pgm/tracesort.exe
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 01:00:17 sap/
STDOUT: extracting: -rw-rr 147 2008-08-15 19:51:15 sap/dbpinstall.lst
STDOUT: extracting: -rw-rr 761 2008-08-15 21:50:29 sap/grantxdb.dbm
STDOUT: extracting: -rwxr-xr-x 18192 2008-08-15 19:51:15 sap/lcinit.bat
STDOUT: extracting: -rwxr-xr-x 126976 2008-08-16 00:15:27 sap/lvcbench.dll
STDOUT: extracting: -rw-rr 89 2008-08-15 19:51:15 sap/saprfc.ini
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 01:00:44 pgm/
STDOUT: extracting: -rwxr-xr-x 14577664 2008-08-15 23:36:03 pgm/slowknl.exe
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 01:00:45 Support/
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 01:00:57 Support/Mapfiles/
STDOUT: extracting: -rw-rr 505962 2008-08-15 21:51:00 Support/Mapfiles/backint.map
STDOUT: extracting: -rw-rr 661472 2008-08-15 20:10:53 Support/Mapfiles/cons.map
STDOUT: extracting: -rw-rr 121797 2008-08-15 20:10:32 Support/Mapfiles/cr_param.map
STDOUT: extracting: -rw-rr 1265024 2008-08-15 21:53:13 Support/Mapfiles/dbmevtdisp.map
STDOUT: extracting: -rw-rr 913124 2008-08-15 21:53:26 Support/Mapfiles/dbmevthndl_display.map
STDOUT: extracting: -rw-rr 918119 2008-08-15 21:53:36 Support/Mapfiles/dbmevthndl_winlog.map
STDOUT: extracting: -rw-rr 802618 2008-08-15 21:49:36 Support/Mapfiles/dbmshm.map
STDOUT: extracting: -rw-rr 3115022 2008-08-15 20:24:12 Support/Mapfiles/dbmsrv-clu.map
STDOUT: extracting: -rw-rr 3049582 2008-08-15 21:48:31 Support/Mapfiles/dbmsrv.map
STDOUT: extracting: -rw-rr 2607026 2008-08-15 21:49:16 Support/Mapfiles/dbmsrvscd.map
STDOUT: extracting: -rw-rr 78229 2008-08-16 00:15:35 Support/Mapfiles/dbpinstall.map
STDOUT: extracting: -rw-rr 1937316 2008-08-15 20:33:22 Support/Mapfiles/diagnose.map
STDOUT: extracting: -rw-rr 155915 2008-08-15 20:10:31 Support/Mapfiles/get_page.map
STDOUT: extracting: -rw-rr 11970292 2008-08-15 21:48:16 Support/Mapfiles/kernel.map
STDOUT: extracting: -rw-rr 191857 2008-08-15 20:25:15 Support/Mapfiles/libhsscopy.map
STDOUT: extracting: -rw-rr 2152785 2008-08-16 00:11:24 Support/Mapfiles/liboms.map
STDOUT: extracting: -rw-rr 259698 2008-08-16 00:16:22 Support/Mapfiles/libsqlcls.map
STDOUT: extracting: -rw-rr 1983758 2008-08-16 00:17:23 Support/Mapfiles/libSQLDBC.map
STDOUT: extracting: -rw-rr 2270630 2008-08-16 00:20:22 Support/Mapfiles/libSQLDBC_C.map
STDOUT: extracting: -rw-rr 3030264 2008-08-15 22:01:26 Support/Mapfiles/lserver.map
STDOUT: extracting: -rw-rr 241759 2008-08-16 00:15:26 Support/Mapfiles/lvcbench.map
STDOUT: extracting: -rw-rr 22799 2008-08-15 19:51:40 Support/Mapfiles/odbcreg.map
STDOUT: extracting: -rw-rr 437361 2008-08-15 21:52:10 Support/Mapfiles/pipe2file.map
STDOUT: extracting: -rw-rr 170094 2008-08-15 20:12:32 Support/Mapfiles/sapdbmscsex.map
STDOUT: extracting: -rw-rr 260595 2008-08-15 20:12:42 Support/Mapfiles/sapdbmscsman.map
STDOUT: extracting: -rw-rr 130593 2008-08-15 20:12:01 Support/Mapfiles/sapdbmscsres.map
STDOUT: extracting: -rw-rr 864387 2008-08-15 20:12:55 Support/Mapfiles/serv-clu.map
STDOUT: extracting: -rw-rr 573796 2008-08-15 20:12:57 Support/Mapfiles/service-clu.map
STDOUT: extracting: -rw-rr 545676 2008-08-15 20:11:50 Support/Mapfiles/service.map
STDOUT: extracting: -rw-rr 15115432 2008-08-15 23:36:03 Support/Mapfiles/slowknl.map
STDOUT: extracting: -rw-rr 674679 2008-08-15 20:11:54 Support/Mapfiles/sqlinst.map
STDOUT: extracting: -rw-rr 138012 2008-08-15 19:55:01 Support/Mapfiles/sqlver.map
STDOUT: extracting: -rw-rr 137724 2008-08-15 19:55:00 Support/Mapfiles/sqlwhat.map
STDOUT: extracting: -rw-rr 100215 2008-08-16 00:05:33 Support/Mapfiles/sql_run.map
STDOUT: extracting: -rw-rr 126593 2008-08-15 20:25:11 Support/Mapfiles/sysrc.map
STDOUT: extracting: -rw-rr 205806 2008-08-15 20:11:57 Support/Mapfiles/systemrc.map
STDOUT: extracting: -rw-rr 329621 2008-08-15 22:11:43 Support/Mapfiles/TableDefC.map
STDOUT: extracting: -rw-rr 180003 2008-08-15 22:01:47 Support/Mapfiles/tracesort.map
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 01:01:45 symbols/
STDOUT: extracting: -rw-rr 1199104 2008-08-15 21:51:00 symbols/backint.pdb
STDOUT: extracting: -rw-rr 2092032 2008-08-15 20:10:53 symbols/cons.pdb
STDOUT: extracting: -rw-rr 281600 2008-08-15 20:10:32 symbols/cr_param.pdb
STDOUT: extracting: -rw-rr 3836928 2008-08-15 21:53:13 symbols/dbmevtdisp.pdb
STDOUT: extracting: -rw-rr 3058688 2008-08-15 21:53:26 symbols/dbmevthndl_display.pdb
STDOUT: extracting: -rw-rr 3083264 2008-08-15 21:53:36 symbols/dbmevthndl_winlog.pdb
STDOUT: extracting: -rw-rr 2485248 2008-08-15 21:49:36 symbols/dbmshm.pdb
STDOUT: extracting: -rw-rr 8563712 2008-08-15 20:24:12 symbols/dbmsrv-clu.pdb
STDOUT: extracting: -rw-rr 8391680 2008-08-15 21:48:30 symbols/dbmsrv.pdb
STDOUT: extracting: -rw-rr 7703552 2008-08-15 21:49:15 symbols/dbmsrvscd.pdb
STDOUT: extracting: -rw-rr 420864 2008-08-16 00:15:35 symbols/dbpinstall.pdb
STDOUT: extracting: -rw-rr 4803584 2008-08-15 20:33:21 symbols/diagnose.pdb
STDOUT: extracting: -rw-rr 338944 2008-08-15 20:10:31 symbols/get_page.pdb
STDOUT: extracting: -rw-rr 36047872 2008-08-15 21:48:12 symbols/kernel.pdb
STDOUT: extracting: -rw-rr 470016 2008-08-15 20:25:15 symbols/libhsscopy.pdb
STDOUT: extracting: -rw-rr 5868544 2008-08-16 00:11:24 symbols/liboms.pdb
STDOUT: extracting: -rw-rr 1264640 2008-08-16 00:16:21 symbols/libsqlcls.pdb
STDOUT: extracting: -rw-rr 4713472 2008-08-16 00:17:22 symbols/libSQLDBC.pdb
STDOUT: extracting: -rw-rr 5180416 2008-08-16 00:20:21 symbols/libSQLDBC_C.pdb
STDOUT: extracting: -rw-rr 7171072 2008-08-15 22:01:25 symbols/lserver.pdb
STDOUT: extracting: -rw-rr 642048 2008-08-16 00:15:26 symbols/lvcbench.pdb
STDOUT: extracting: -rw-rr 1207296 2008-08-15 21:52:10 symbols/pipe2file.pdb
STDOUT: extracting: -rw-rr 3058688 2008-08-15 20:12:32 symbols/sapdbmscsex.pdb
STDOUT: extracting: -rw-rr 1002496 2008-08-15 20:12:42 symbols/sapdbmscsman.pdb
STDOUT: extracting: -rw-rr 330752 2008-08-15 20:12:01 symbols/sapdbmscsres.pdb
STDOUT: extracting: -rw-rr 2739200 2008-08-15 20:12:55 symbols/serv-clu.pdb
STDOUT: extracting: -rw-rr 2141184 2008-08-15 20:12:56 symbols/service-clu.pdb
STDOUT: extracting: -rw-rr 1944576 2008-08-15 20:11:50 symbols/service.pdb
STDOUT: extracting: -rw-rr 40643584 2008-08-15 23:35:57 symbols/slowknl.pdb
STDOUT: extracting: -rw-rr 2321408 2008-08-15 20:11:54 symbols/sqlinst.pdb
STDOUT: extracting: -rw-rr 2075648 2008-08-16 00:05:31 symbols/sqlrun.pdb
STDOUT: extracting: -rw-rr 306176 2008-08-15 19:55:01 symbols/sqlver.pdb
STDOUT: extracting: -rw-rr 306176 2008-08-15 19:55:00 symbols/sqlwhat.pdb
STDOUT: extracting: -rw-rr 248832 2008-08-16 00:05:33 symbols/sql_run.pdb
STDOUT: extracting: -rw-rr 2214912 2008-08-15 20:12:51 symbols/start-clu.pdb
STDOUT: extracting: -rw-rr 2206720 2008-08-15 20:12:52 symbols/stop-clu.pdb
STDOUT: extracting: -rw-rr 306176 2008-08-15 20:25:10 symbols/sysrc.pdb
STDOUT: extracting: -rw-rr 388096 2008-08-15 20:11:57 symbols/systemrc.pdb
STDOUT: extracting: -rw-rr 846848 2008-08-15 22:11:43 symbols/TableDefC.pdb
STDOUT: extracting: -rw-rr 887808 2008-08-15 22:01:47 symbols/tracesort.pdb
STDOUT: checking unpacked archive... MSG: check file "Support/Mapfiles/diagnose.map": ok
MSG: check file "doc/FirstSteps/ODBC/HowToODBC.html": ok
MSG: check file "lib/python2.3/_socket.pyd": ok
MSG: check file "Support/Mapfiles/get_page.map": ok
MSG: check file "pgm/dbmsrv.exe": ok
MSG: check file "env/INFO.py": ok
MSG: check file "symbols/dbmsrv-clu.pdb": ok
MSG: check file "pgm/diagnose.exe": ok
MSG: check file "symbols/cons.pdb": ok
MSG: check file "misc/create_demo_db.cmd": ok
MSG: check file "symbols/sapdbmscsres.pdb": ok
MSG: check file "symbols/cr_param.pdb": ok
MSG: check file "Support/Mapfiles/dbpinstall.map": ok
MSG: check file "lib/python2.3/sdb/__init__.py": ok
MSG: check file "symbols/dbmevthndl_winlog.pdb": ok
MSG: check file "symbols/libSQLDBC_C.pdb": ok
MSG: check file "bin/xtracesort.exe": ok
MSG: check file "bin/x_diagnose.exe": ok
MSG: check file "symbols/pipe2file.pdb": ok
MSG: check file "pgm/Tools_WinEvtLog.dll": ok
MSG: check file "symbols/dbmshm.pdb": ok
MSG: check file "pgm/cons.exe": ok
MSG: check file "sap/grantxdb.dbm": ok
MSG: check file "demo/tutoriallib.py": ok
MSG: check file "demo/HOTEL.py": ok
MSG: check file "symbols/liboms.pdb": ok
MSG: check file "env/cserv.pcf": ok
MSG: check file "Support/Mapfiles/TableDefC.map": ok
MSG: check file "lib/python2.3/_sre.pyd": ok
MSG: check file "pgm/service.exe": ok
MSG: check file "doc/FirstSteps/Python/HowToPython.html": ok
MSG: check file "doc/FirstSteps/ODBC/HelloMaxDB.c": ok
MSG: check file "Support/Mapfiles/libSQLDBC.map": ok
MSG: check file "doc/FirstSteps/Java/DemodbData.java": ok
MSG: check file "sap/saprfc.ini": ok
MSG: check file "pgm/dbghelp.dll": ok
MSG: check file "cluster/strt_clu.exe": ok
MSG: check file "symbols/libhsscopy.pdb": ok
MSG: check file "symbols/dbmsrv.pdb": ok
MSG: check file "symbols/sapdbmscsman.pdb": ok
MSG: check file "cluster/SAPDBMSCSMan.exe": ok
MSG: check file "pgm/tracesort.exe": ok
MSG: check file "Support/Mapfiles/sqlinst.map": ok
MSG: check file "bin/sqlwhat.exe": ok
MSG: check file "lib/python2.3/pyexpat.pyd": ok
MSG: check file "pgm/libSQLDBC_C.dll": ok
MSG: check file "Support/Mapfiles/sapdbmscsman.map": ok
MSG: check file "Support/Mapfiles/sapdbmscsres.map": ok
MSG: check file "Support/Mapfiles/dbmevthndl_winlog.map": ok
MSG: check file "bin/x_python.exe": ok
MSG: check file "symbols/sql_run.pdb": ok
MSG: check file "pgm/python23.dll": ok
MSG: check file "env/SQLDBC.py": ok
MSG: check file "symbols/tracesort.pdb": ok
MSG: check file "cluster/SAPDBMSCSRes.dll": ok
MSG: check file "cluster/stop_clu.exe": ok
MSG: check file "pgm/sqlinst.dll": ok
MSG: check file "pgm/StudioUtil.dll": ok
MSG: check file "Support/Mapfiles/slowknl.map": ok
MSG: check file "doc/FirstSteps/Python/HelloMaxDB.py": ok
MSG: check file "symbols/lserver.pdb": ok
MSG: check file "Support/Mapfiles/serv-clu.map": ok
MSG: check file "pgm/cr_param.exe": ok
MSG: check file "bin/backint.exe": ok
MSG: check file "bin/sqlrun.dll": ok
MSG: check file "pgm/libSQLDBC.dll": ok
MSG: check file "Support/Mapfiles/kernel.map": ok
MSG: check file "symbols/kernel.pdb": ok
MSG: check file "bin/dbmsrvctl.exe": ok
MSG: check file "env/UDE.py": ok
MSG: check file "symbols/dbmsrvscd.pdb": ok
MSG: check file "symbols/sqlinst.pdb": ok
MSG: check file "doc/FirstSteps/Java/DemodbData.class": ok
MSG: check file "env/lsystab.py": ok
MSG: check file "sap/lcinit.bat": ok
MSG: check file "lib/python2.3/zlib.pyd": ok
MSG: check file "doc/FirstSteps/Perl/StateMaxDB.pl": ok
MSG: check file "pgm/python23.zip": ok
MSG: check file "doc/FirstSteps/Java/HelloMaxDB.class": ok
MSG: check file "symbols/dbmevtdisp.pdb": ok
MSG: check file "env/installib.py": ok
MSG: check file "pgm/renparam.exe": ok
MSG: check file "doc/FirstSteps/Python/StateMaxDB.py": ok
MSG: check file "env/TRIGGER.py": ok
MSG: check file "pgm/libhsscopy.dll": ok
MSG: check file "symbols/serv-clu.pdb": ok
MSG: check file "pgm/systemrc.exe": ok
MSG: check file "pgm/dbmunreg.exe": ok
MSG: check file "Support/Mapfiles/sysrc.map": ok
MSG: check file "Support/Mapfiles/libhsscopy.map": ok
MSG: check file "bin/dbmevtdisp.exe": ok
MSG: check file "doc/FirstSteps/ODBC/Makefile": ok
MSG: check file "Support/Mapfiles/dbmsrv-clu.map": ok
MSG: check file "pgm/stop.exe": ok
MSG: check file "Support/Mapfiles/service-clu.map": ok
MSG: check file "Support/Mapfiles/lserver.map": ok
MSG: check file "Support/Mapfiles/libsqlcls.map": ok
MSG: check file "symbols/backint.pdb": ok
MSG: check file "Support/Mapfiles/systemrc.map": ok
MSG: check file "symbols/get_page.pdb": ok
MSG: check file "lib/python2.3/sdb/sql.pyd": ok
MSG: check file "Support/Mapfiles/dbmsrv.map": ok
MSG: check file "env/APPS.py": ok
MSG: check file "env/kernprot.use": ok
MSG: check file "Support/Mapfiles/lvcbench.map": ok
MSG: check file "symbols/systemrc.pdb": ok
MSG: check file "symbols/sqlver.pdb": ok
MSG: check file "pgm/liboms.dll": ok
MSG: check file "cluster/service_clu.exe": ok
MSG: check file "env/ORADDSYN.py": ok
MSG: check file "Support/Mapfiles/backint.map": ok
MSG: check file "env/SYSINFOCOM.py": ok
MSG: check file "Support/Mapfiles/dbmevthndl_display.map": ok
MSG: check file "cluster/SAPDBMSCSEx.dll": ok
MSG: check file "pgm/slowknl.exe": ok
MSG: check file "symbols/slowknl.pdb": ok
MSG: check file "symbols/sqlwhat.pdb": ok
MSG: check file "symbols/TableDefC.pdb": ok
MSG: check file "doc/FirstSteps/SQLDBC/HelloMaxDB.cpp": ok
MSG: check file "env/CNR3DATA.py": ok
MSG: check file "doc/FirstSteps/index.html": ok
MSG: check file "doc/FirstSteps/Java/HowToJava.html": ok
MSG: check file "bin/pipe2file.exe": ok
MSG: check file "doc/FirstSteps/Perl/demodbData.pm": ok
MSG: check file "bin/dbmevthndl_winlog.exe": ok
MSG: check file "Support/Mapfiles/tracesort.map": ok
MSG: check file "symbols/lvcbench.pdb": ok
MSG: check file "demo/ltutorial.py": ok
MSG: check file "symbols/sapdbmscsex.pdb": ok
MSG: check file "bin/xservice.exe": ok
MSG: check file "doc/FirstSteps/Python/HelloMaxDB-API.py": ok
MSG: check file "symbols/libSQLDBC.pdb": ok
MSG: check file "env/REPOSITORY.py": ok
MSG: check file "Support/Mapfiles/cr_param.map": ok
MSG: check file "lib/python2.3/optlib.py": ok
MSG: check file "cluster/serv_clu.exe": ok
MSG: check file "symbols/sysrc.pdb": ok
MSG: check file "env/ORADDCOM.py": ok
MSG: check file "doc/FirstSteps/SQLDBC/Makefile": ok
MSG: check file "pgm/dbmsrvscd.exe": ok
MSG: check file "symbols/diagnose.pdb": ok
MSG: check file "pgm/TableDefC.dll": ok
MSG: check file "doc/FirstSteps/Perl/HowToPerl.html": ok
MSG: check file "Support/Mapfiles/sqlwhat.map": ok
MSG: check file "symbols/stop-clu.pdb": ok
MSG: check file "cluster/dbmsrv_clu.exe": ok
MSG: check file "pgm/sysrc.exe": ok
MSG: check file "pgm/kernel.exe": ok
MSG: check file "Support/Mapfiles/sql_run.map": ok
MSG: check file "doc/FirstSteps/Java/StateMaxDB.class": ok
MSG: check file "Support/Mapfiles/dbmsrvscd.map": ok
MSG: check file "symbols/service-clu.pdb": ok
MSG: check file "symbols/dbmevthndl_display.pdb": ok
MSG: check file "Support/Mapfiles/odbcreg.map": ok
MSG: check file "env/SAPDBLOADER.py": ok
MSG: check file "bin/sqlver.exe": ok
MSG: check file "env/general.use": ok
MSG: check file "sap/dbpinstall.lst": ok
MSG: check file "pgm/dbpinstall.dll": ok
MSG: check file "doc/FirstSteps/Java/StateMaxDB.java": ok
MSG: check file "env/en/DBM.en": ok
MSG: check file "sap/lvcbench.dll": ok
MSG: check file "pgm/lserver.exe": ok
MSG: check file "env/getpackages.py": ok
MSG: check file "env/lapps.py": ok
MSG: check file "Support/Mapfiles/dbmshm.map": ok
MSG: check file "Support/Mapfiles/service.map": ok
MSG: check file "misc/drop_demo_db.cmd": ok
MSG: check file "lib/python2.3/sdb/dbm.pyd": ok
MSG: check file "env/WA.py": ok
MSG: check file "symbols/dbpinstall.pdb": ok
MSG: check file "bin/ireport.py": ok
MSG: check file "Support/Mapfiles/sapdbmscsex.map": ok
MSG: check file "Support/Mapfiles/libSQLDBC_C.map": ok
MSG: check file "Support/Mapfiles/liboms.map": ok
MSG: check file "lib/python2.3/sdb/dbapi.py": ok
MSG: check file "doc/FirstSteps/Java/HelloMaxDB.java": ok
MSG: check file "env/ORADDV.py": ok
MSG: check file "doc/FirstSteps/maxdbenv.cmd": ok
MSG: check file "pgm/pysapdb.exe": ok
MSG: check file "pgm/libsqlcls.dll": ok
MSG: check file "env/GARBAGE.py": ok
MSG: check file "symbols/libsqlcls.pdb": ok
MSG: check file "bin/xkernprot.exe": ok
MSG: check file "Support/Mapfiles/dbmevtdisp.map": ok
MSG: check file "env/SYSINFO.py": ok
MSG: check file "symbols/sqlrun.pdb": ok
MSG: check file "env/XDDCOM.py": ok
MSG: check file "bin/sdbfill.exe": ok
MSG: check file "lib/python2.3/sdb/loader.pyd": ok
MSG: check file "env/XDD.py": ok
MSG: check file "doc/FirstSteps/SQLDBC/HowToSQLDBC.html": ok
MSG: check file "pgm/backup.exe": ok
MSG: check file "env/ODBC.py": ok
MSG: check file "Support/Mapfiles/pipe2file.map": ok
MSG: check file "Support/Mapfiles/cons.map": ok
MSG: check file "pgm/dbmshm.exe": ok
MSG: check file "env/SYSDBA.py": ok
MSG: check file "env/CNR3TAB.py": ok
MSG: check file "env/ORADD.py": ok
MSG: check file "env/PRECOM.py": ok
MSG: check file "pgm/strt.exe": ok
MSG: check file "cluster/sapdbmscsman.dll": ok
MSG: check file "Support/Mapfiles/sqlver.map": ok
MSG: check file "env/DBANA.py": ok
MSG: check file "env/SHOWCMD.py": ok
MSG: check file "pgm/dbmstop.exe": ok
MSG: check file "env/SYSDBACOM.py": ok
MSG: check file "symbols/start-clu.pdb": ok
MSG: check file "bin/dbmevthndl_display.exe": ok
MSG: check file "doc/FirstSteps/Python/demodbData.py": ok
MSG: check file "pgm/dbmstart.exe": ok
MSG: check file "env/DBMVIEWS.py": ok
MSG: check file "env/JDBC.py": ok
MSG: check file "pgm/sqlmsg.dll": ok
MSG: check file "pgm/dbmreg.exe": ok
MSG: check file "symbols/service.pdb": ok
STDOUT: ok
MSG: file "c:/program files/sdb/maxdb1/doc/FirstSteps/index.html" modified by installer
MSG: file "c:/program files/sdb/maxdb1/doc/FirstSteps/Perl/HowToPerl.html" modified by installer
MSG: file "c:/program files/sdb/maxdb1/doc/FirstSteps/Python/HowToPython.html" modified by installer
MSG: file "c:/program files/sdb/maxdb1/doc/FirstSteps/ODBC/HowToODBC.html" modified by installer
MSG: file "c:/program files/sdb/maxdb1/doc/FirstSteps/Java/HowToJava.html" modified by installer
MSG: file "c:/program files/sdb/maxdb1/misc/create_demo_db.cmd" modified by installer
MSG: file "c:/program files/sdb/maxdb1/misc/drop_demo_db.cmd" modified by installer
MSG: file "c:/program files/sdb/maxdb1/doc/FirstSteps/maxdbenv.cmd" modified by installer
SYS: "C:Program FilessdbMAXDB1 indbmsrvctl.exe" start
SYS: "C:Program Filessdbprogramspgmdbmcli.exe" -R "C:Program FilessdbMAXDB1" inst_reg -k "C:Program FilessdbMAXDB1": ERR
SYS: "C:Program Filessdbprogramspgmdbmcli.exe" -R "C:Program FilessdbMAXDB1" inst_reg -k "C:Program FilessdbMAXDB1": -24913,ERR_SERVICEDB: Cannot register service database instance for C:Program FilesSDBMAXDB1
STDERR: error occured while executing "C:Program Filessdbprogramspgmdbmcli.exe" -R "C:Program FilessdbMAXDB1" inst_reg -k "C:Program FilessdbMAXDB1"
STDERR: "C:Program Filessdbprogramspgmdbmcli.exe" -R "C:Program FilessdbMAXDB1" inst_reg -k "C:Program FilessdbMAXDB1": ERR
"C:Program Filessdbprogramspgmdbmcli.exe" -R "C:Program FilessdbMAXDB1" inst_reg -k "C:Program FilessdbMAXDB1": -24913,ERR_SERVICEDB: Cannot register service database instance for C:Program FilesSDBMAXDB1
STDERR: installation exited abnormally at Fr, Jan 09, 2009 at 18:17:25
MSG: packagedata of package Redist Python changed
MSG: writing 4 packages
MSG: net install registry size = 40263 bytes
MSG: wrote install registry (46259 bytes)
STDOUT: start real extraction of "C:/DOCUME1/ADMINI1/LOCALS~1/Temp/Max31.tmp/SDBRDPY.TGZ"
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 01:04:43 bin/
STDOUT: extracting: -rwxr-xr-x 331776 2008-08-15 21:53:55 bin/x_python.exe
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 01:04:43 lib/
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 01:04:44 lib/python2.3/
STDOUT: extracting: -rw-rr 6867 2008-08-15 19:51:15 lib/python2.3/optlib.py
STDOUT: extracting: -rwxr-xr-x 135234 2008-08-15 19:51:15 lib/python2.3/pyexpat.pyd
STDOUT: extracting: drwxr-xr-x 0 2008-08-16 01:04:43 lib/python2.3/sdb/
STDOUT: extracting: -rwxr-xr-x 507904 2008-08-15 21:54:03 lib/python2.3/sdb/dbm.pyd
STDOUT: extractiHI there,
it really does look like as the "uninstallation" was done by merely deleting files from the filesystem.
This will always lead to problems when you try to re-install a MaxDB afterwards.
Uninstallations should be done via SDBUNIST to avoid such issues.
Based on the error messages like:
getRelease():C:/Program Files/SDB/MAXDB1/pgm/kernel.exe not found
MSG: migrate server installation data for INSTROOT "c:/program files/sdb/maxdb1"
MSG: installed package is flaged as invalid => skipping update check
WRN: cannot execute command: xregcomp -u "c:program filessdbmaxdb1pgmdbpinstall": cannot create process, Le fichier spÈcifiÈ est introuvable.
>WRN: cannot execute command: xregcomp -u "c:program filessdbprogramsliblivecachedbg": cannot create process, Le fichier spÈcifiÈ est introuvable.
we can tell: the MaxDB installation registration had not been deleted correctly.
If I'd to guess, I'd say you just deleted whatever was in the folder "c:program filessdb" and crossed fingers that this would do.
Anyhow, on this system, due to the usage of non-SAP-standard folder layout check this one, the installation registration can by found in the all users data folder:
>MSG: Template set indep data path to "c:/documents and settings/all users/application data/sdb/data"
This would have to be removed as well.
Anyhow, maybe you want to read the documentation before messing up your system by try and error:
Installation Manual
regards,
Lars -
Getting backup using "backint for Oracle" to work
Hi
We are trying to get the backups to work on MaxDB 7.6 using the backint for Oracle interface.
I have created an environment/config file and set the variable NSR_ENV. The contents of this file is as follows:
NSR_HOST cmsapapp01.csenergy.com.au
NSR_HOME "C:\Program Files (x86)\Legato\nsr\bin"
NSR_POOL SAPData
NSR_EXPIRE year
NSR_EBIDTYPE NSAVETIME
NSR_USEOUTPUT SAVE
I have created a backup media with the following options:
Backup Type: Full Backup
Device Type: PIPE
Backup Tool: NSR
Device File: c:\temp\file.pipe0
When I run this, I get the following error:
Begin of error output of NetWorker (C:\WINDOWS\TEMP\temp1204089773-1)----
save: VSS Enabler is requested from NetWorker License Manager.
save: c:\temp\file.pipe0: No such file or directory
Am I doing something wrong...
OS is Windows 2003.
Thanks
DougHello Doug,
on Windows the pipe syntax is as follows:
.\pipe\<pipename>
HTH,
Melanie -
Another attempt to install MaxDB failed
Since I saw there is new version of MaxDB available I have decided to give it another since last time I wasn't able to get it installed. I have downloaded the latest version (seems to be 7.6.03.02) and started the installation. I chode the client+server and chose to do not create database instance. During installation I got error it cannot register database kernel but the rest completed successfully (I will paste log below).
Then I install the Database Manager and tried to create instance. I chose the Desktop/Laptop, left all the settings at the default values and tried to progress through the wizard. I got error message:
Creating database instance <Local>:MAXTEST
-24724 Resource ParamAccess not locked [param_startsession];
-24726 ERR_SHMLINESEXEEDED: Too many lines of type 1
I cancel the installation and it asked me if I want to delete the created instance. I said Yes and got some more errors. Then I discovered in the Database Manager there is an instance MAXTEST to which I cannot connect, because I do not know the password (the one I entered for DBADMIN doesn't work).
Now I cannot drop this instance. What is even worse I cannot uninstall MaxDB because it asks me to drop the database to which I cannot connect since I do not now the credentials.
Is there anybody who can help me to install this DBMS? I haven't got any solutions the last time. Anybody can help now?
Also how I can drop the database which failed during creation?
Thank you so much,
Miro HalasHere is the log during installation
INSTALLER_INFO: Version = 7.6.03 Build 007-123-157-515
INSTALLER_INFO: Changelist = 157515
INSTALLER_INFO: MakeId = 256246
INSTALLER_INFO: Type = kit
SYS_INFO: Host name = CLXITISE3OJD
SYS_INFO: System = Windows
SYS_INFO: Architecture = I386
SYS_INFO: Version = NT 5.1
SYS_INFO: Subversion = Service Pack 2
Can't open registry key "HKEY_LOCAL_MACHINE\SOFTWARE\SAP\SAP DBTech":
MSG: collector found 11 archives
debug package SDBBAS.SDB not found
debug package SDBKRN.SDB not found
debug package SDBUTL.SDB not found
Can't open registry key "HKEY_LOCAL_MACHINE\SOFTWARE\SAP\SAP DBTech":
MSG: initializing package "Base"
MSG: calling preinstall...
MSG: service "sql6" in "C:/WINNT/system32/drivers/etc/services" found
MSG: service "sapdbni72" in "C:/WINNT/system32/drivers/etc/services" found
Can't open registry key "HKEY_LOCAL_MACHINE\SOFTWARE\SAP\SAP DBTech":
MSG: selected new installation in ""
MSG: selected new installation in "c:/program files/sdb/programs"
ACTION: make directory "c:/data/maxdb/config" mode "775"
ACTION: make directory "c:/data/maxdb/config/install" mode "775"
MSG: InstallRegistry: space check ok: 10852228 kb on C: (30716244 kb total) available
MSG: install registry successfully locked
MSG: InstallRegistry::Log: space check ok: 10852228 kb on C: (30716244 kb total) available
MSG: writing 0 packages
MSG: net install registry size = 63 bytes
MSG: wrote install registry (125 bytes)
MSG: InstallRegistry: reserved 1024 kb disk space
Can't open registry key "HKEY_LOCAL_MACHINE\SOFTWARE\SAP\SAP DBTech":
Can't open registry key "HKEY_LOCAL_MACHINE\SOFTWARE\SAP\SAP DBTech\Installations": No such file or directory
Can't open registry key "HKEY_LOCAL_MACHINE\SOFTWARE\SAP\SAP DBTech\Installations\": No such file or directory
STDERR: getInstalledReleasesWin(): wrong version format
getRelease():/pgm/kernel.exe not found
WRN: old DBROOT installation found
0.0.0.0 in "" ignored
MSG: no installation data to migrate
MSG: initializing package "Server Utilities"
MSG: calling preinstall...
MSG: path was set by preinstall script (c:/program files/sdb/programs)
MSG: initializing package "Database Kernel"
MSG: calling preinstall...
MSG: selected new installation in "c:/program files/sdb/7603"
MSG: initializing package "Redist Python"
MSG: calling preinstall...
MSG: path was set by preinstall script (c:/program files/sdb/programs)
MSG: initializing package "Loader"
MSG: calling preinstall...
MSG: path was set by preinstall script (c:/program files/sdb/programs)
MSG: initializing package "ODBC"
MSG: calling preinstall...
MSG: path was set by preinstall script (c:/program files/sdb/programs)
MSG: initializing package "Messages"
MSG: calling preinstall...
MSG: path was set by preinstall script (c:/program files/sdb/programs)
MSG: initializing package "JDBC"
MSG: calling preinstall...
MSG: path was set by preinstall script (c:/program files/sdb/programs)
MSG: initializing package "Synchronization Manager"
MSG: calling preinstall...
MSG: path was set by preinstall script (c:/program files/sdb/programs)
MSG: initializing package "SQLDBC"
MSG: calling preinstall...
MSG: path was set by preinstall script (c:/program files/sdb/programs)
MSG: initializing package "DB Analyzer"
MSG: calling preinstall...
MSG: path was set by preinstall script (c:/program files/sdb/programs)
ACTION: make directory "C:/Program Files/sdb" mode "555"
ACTION: make directory "C:/Program Files/sdb/programs" mode "555"
STDOUT: start extraction test run of "C:/Temp/MaxC.tmp/SDBBAS.TGZ"
MSG: running postprepare of package Base
ACTION: make directory "c:/data/maxdb/wrk" mode "770"
STDOUT: start extraction test run of "C:/Temp/MaxC.tmp/SDBUTL.TGZ"
ACTION: make directory "C:/Program Files/sdb/7603" mode "555"
STDOUT: start extraction test run of "C:/Temp/MaxC.tmp/SDBKRN.TGZ"
MSG: running postprepare of package Database Kernel
STDOUT: start extraction test run of "C:/Temp/MaxC.tmp/SDBRDPY.TGZ"
MSG: running postprepare of package Redist Python
STDOUT: start extraction test run of "C:/Temp/MaxC.tmp/SDBLD.TGZ"
MSG: running postprepare of package Loader
STDOUT: start extraction test run of "C:/Temp/MaxC.tmp/SDBODBC.TGZ"
MSG: running postprepare of package ODBC
STDOUT: start extraction test run of "C:/Temp/MaxC.tmp/SDBMSG.TGZ"
MSG: running postprepare of package Messages
STDOUT: start extraction test run of "C:/Temp/MaxC.tmp/SDBJDBC.TGZ"
STDOUT: start extraction test run of "C:/Temp/MaxC.tmp/SYNCMAN.TGZ"
MSG: running postprepare of package Synchronization Manager
STDOUT: start extraction test run of "C:/Temp/MaxC.tmp/SDBC.TGZ"
MSG: running postprepare of package Database Connectivity
STDOUT: start extraction test run of "C:/Temp/MaxC.tmp/SDBANA.TGZ"
MSG: running postprepare of package DB Analyzer
MSG: space check ok: 10848996 kb on (30716244 kb total) available
MSG: packagedata of package Base changed
MSG: writing 1 packages
MSG: net install registry size = 1020 bytes
MSG: wrote install registry (1617 bytes)
STDOUT: start real extraction of "C:/Temp/MaxC.tmp/SDBBAS.TGZ"
STDOUT: extracting: drwxr-xr-x 0 2007-08-22 16:20:22 bin/
STDOUT: extracting: -rwxr-xr-x 794624 2007-08-22 13:01:49 bin/dbmevtdisp.exe
STDOUT: extracting: -rwxr-xr-x 294912 2007-08-22 12:58:21 bin/protconv.exe
STDOUT: extracting: -rwxr-xr-x 151552 2007-08-22 11:21:59 bin/sdbconfig.exe
STDOUT: extracting: -rwxr-xr-x 7168 2007-08-22 16:18:50 bin/SDBINST.EXE
STDOUT: extracting: -rwxr-xr-x 6144 2007-08-22 16:18:52 bin/sdbpack.exe
STDOUT: extracting: -rwxr-xr-x 7680 2007-08-22 16:18:52 bin/sdbreg.exe
STDOUT: extracting: -rwxr-xr-x 7680 2007-08-22 16:18:51 bin/sdbregview.exe
STDOUT: extracting: -rwxr-xr-x 13824 2007-08-22 16:18:50 bin/SDBSETUP.EXE
STDOUT: extracting: -rwxr-xr-x 7680 2007-08-22 16:18:51 bin/sdbuninst.exe
STDOUT: extracting: -rwxr-xr-x 7168 2007-08-22 16:18:52 bin/sdbverify.exe
STDOUT: extracting: -rwxr-xr-x 1228800 2007-08-22 15:36:09 bin/sqlcli.exe
STDOUT: extracting: -rwxr-xr-x 40960 2007-08-22 14:54:37 bin/xsysrc.exe
STDOUT: extracting: -rwxr-xr-x 323584 2007-08-22 11:38:01 bin/xtcpupd.exe
STDOUT: extracting: -rwxr-xr-x 294912 2007-08-22 11:02:37 bin/xuser.exe
STDOUT: extracting: -rwxr-xr-x 40960 2007-08-22 14:54:37 bin/x_ping.exe
STDOUT: extracting: drwxr-xr-x 0 2007-08-22 16:20:23 install/
STDOUT: extracting: -rwxr-xr-x 192512 2007-08-22 16:10:57 install/Grid.dll
STDOUT: extracting: -rwxr-xr-x 757760 2007-08-22 15:45:12 install/perl58.dll
STDOUT: extracting: -rw-rr 67080 2007-08-22 16:18:49 install/RESOURCES.TGZ
STDOUT: extracting: -rw-rr 459564 2007-08-22 16:18:49 install/SDBINST.TGZ
STDOUT: extracting: -rwxr-xr-x 421888 2007-08-22 16:18:27 install/sdbrun.dll
STDOUT: extracting: -rwxr-xr-x 1245184 2007-08-22 16:16:39 install/Wx.dll
STDOUT: extracting: -rwxr-xr-x 2265088 2007-08-22 16:09:47 install/wxmsw24.dll
STDOUT: extracting: -rw-rr 64319 2007-08-22 16:18:55 install/WXPERL.TGZ
STDOUT: extracting: drwxr-xr-x 0 2007-08-22 16:20:25 pgm/
STDOUT: extracting: -rwxr-xr-x 2043904 2007-08-22 12:58:33 pgm/dbmcli.exe
STDOUT: extracting: -rwxr-xr-x 2043904 2007-08-22 12:58:33 pgm/dbmcli_HelpInst.exe
STDOUT: extracting: -rwxr-xr-x 217088 2007-08-22 13:18:45 pgm/regupd.exe
STDOUT: extracting: -rwxr-xr-x 307200 2007-08-22 11:38:29 pgm/sqlping.exe
STDOUT: extracting: -rwxr-xr-x 49152 2007-08-22 10:51:25 pgm/sqltcp.dll
STDOUT: extracting: -rwxr-xr-x 49152 2007-08-22 10:51:27 pgm/sqltcp1.dll
STDOUT: extracting: -rwxr-xr-x 49152 2007-08-22 10:51:29 pgm/sqltcp2.dll
STDOUT: extracting: -rwxr-xr-x 45056 2007-08-22 10:51:31 pgm/sqltcpn.dll
STDOUT: extracting: -rwxr-xr-x 281952 2007-08-22 16:19:53 pgm/sqluser72.dll
STDOUT: extracting: -rwxr-xr-x 372672 2007-08-22 16:19:56 pgm/sqluser73.dll
STDOUT: extracting: -rwxr-xr-x 393216 2007-08-22 16:19:59 pgm/sqluser74.dll
STDOUT: extracting: -rwxr-xr-x 438272 2007-08-22 16:20:02 pgm/sqluser74n.dll
STDOUT: extracting: -rwxr-xr-x 520192 2007-08-22 15:07:21 pgm/sqluser76.dll
STDOUT: checking unpacked archive... MSG: check file "bin/x_ping.exe": ok
MSG: check file "pgm/dbmcli_HelpInst.exe": ok
MSG: check file "bin/SDBINST.EXE": ok
MSG: check file "pgm/sqluser74.dll": ok
MSG: check file "install/SDBINST.TGZ": ok
MSG: check file "pgm/sqluser74n.dll": ok
MSG: check file "bin/SDBSETUP.EXE": ok
MSG: check file "bin/protconv.exe": ok
MSG: check file "install/wxmsw24.dll": ok
MSG: check file "install/WXPERL.TGZ": ok
MSG: check file "install/sdbrun.dll": ok
MSG: check file "pgm/sqluser73.dll": ok
MSG: check file "bin/xuser.exe": ok
MSG: check file "pgm/sqluser76.dll": ok
MSG: check file "pgm/sqltcp1.dll": ok
MSG: check file "install/RESOURCES.TGZ": ok
MSG: check file "pgm/sqltcp.dll": ok
MSG: check file "pgm/dbmcli.exe": ok
MSG: check file "bin/sdbverify.exe": ok
MSG: check file "bin/xsysrc.exe": ok
MSG: check file "install/perl58.dll": ok
MSG: check file "bin/sdbuninst.exe": ok
MSG: check file "pgm/regupd.exe": ok
MSG: check file "pgm/sqlping.exe": ok
MSG: check file "bin/sdbpack.exe": ok
MSG: check file "pgm/sqltcpn.dll": ok
MSG: check file "pgm/sqluser72.dll": ok
MSG: check file "pgm/sqltcp2.dll": ok
MSG: check file "bin/sdbregview.exe": ok
MSG: check file "bin/dbmevtdisp.exe": ok
MSG: check file "install/Grid.dll": ok
MSG: check file "bin/xtcpupd.exe": ok
MSG: check file "bin/sdbconfig.exe": ok
MSG: check file "install/Wx.dll": ok
MSG: check file "bin/sdbreg.exe": ok
MSG: check file "bin/sqlcli.exe": ok
STDOUT: ok
STDOUT: checking system libraries...MSG: update test sytem file "C:/WINNT/system32/mfc70.dll"
MSG: system file "mfc70.dll" inside archive has version 7.00.9466.0
MSG: installed system file "mfc70.dll" is up to date (version 7.00.9466.0)
MSG: update test sytem file "C:/WINNT/system32/mfc70u.dll"
MSG: system file "mfc70u.dll" inside archive has version 7.00.9466.0
MSG: installed system file "mfc70u.dll" is up to date (version 7.00.9466.0)
MSG: update test sytem file "C:/WINNT/system32/mfc71.dll"
MSG: system file "mfc71.dll" inside archive has version 7.10.3077.0
MSG: installed system file "mfc71.dll" is up to date (version 7.10.3077.0)
MSG: update test sytem file "C:/WINNT/system32/mfc71u.dll"
MSG: system file "mfc71u.dll" inside archive has version 7.10.3077.0
MSG: installed system file "mfc71u.dll" is up to date (version 7.10.3077.0)
MSG: update test sytem file "C:/WINNT/system32/msvcr70.dll"
MSG: system file "msvcr70.dll" inside archive has version 7.00.9466.0
MSG: installed system file "msvcr70.dll" is up to date (version 7.00.9466.0)
MSG: update test sytem file "C:/WINNT/system32/msvcr71.dll"
MSG: system file "msvcr71.dll" inside archive has version 7.10.3052.4
MSG: installed system file "msvcr71.dll" is up to date (version 7.10.3052.4)
STDOUT: ok
SYS: "C:\Program Files\sdb\programs\bin\sdbconfig.exe" "IndepPrograms=C:\Program Files\sdb\programs"
SYS: "C:\Program Files\sdb\programs\bin\sdbconfig.exe" "IndepData=C:\Data\MaxDB"
STDOUT: system path updated successfully
STDOUT: please reboot your system after installation to take effect changes
MSG: registry subkey "SOFTWARE\Microsoft" exist
MSG: registry subkey "SOFTWARE\Microsoft\Windows" exist
MSG: registry subkey "SOFTWARE\Microsoft\Windows\CurrentVersion" exist
MSG: registry subkey "SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall" exist
MSG: created registry subkey "SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\SAP DB (ALL)" successfully
ACTION: make directory "C:/Documents and Settings/All Users/Start Menu/Programs/MaxDB/Command Line Tools" mode "775"
MSG: start menu shortcuts created
MSG: packagedata of package Base changed
MSG: writing 1 packages
MSG: net install registry size = 27334 bytes
MSG: wrote install registry (30674 bytes)
MSG: packagedata of package Server Utilities changed
MSG: writing 2 packages
MSG: net install registry size = 27950 bytes
MSG: wrote install registry (31693 bytes)
STDOUT: start real extraction of "C:/Temp/MaxC.tmp/SDBUTL.TGZ"
STDOUT: extracting: drwxr-xr-x 0 2007-08-22 16:21:45 bin/
STDOUT: extracting: -rwxr-xr-x 65536 2007-08-22 13:00:51 bin/sdbinfo.exe
STDOUT: extracting: -rwxr-xr-x 352256 2007-08-22 14:54:35 bin/sqlrun.dll
STDOUT: extracting: -rwxr-xr-x 40960 2007-08-22 14:54:37 bin/sysmon.exe
STDOUT: extracting: -rwxr-xr-x 40960 2007-08-22 14:54:37 bin/xbackup.exe
STDOUT: extracting: -rwxr-xr-x 40960 2007-08-22 14:54:37 bin/xinstinfo.exe
STDOUT: extracting: -rwxr-xr-x 40960 2007-08-22 14:54:37 bin/xpu.exe
STDOUT: extracting: -rwxr-xr-x 40960 2007-08-22 14:54:37 bin/x_analys.exe
STDOUT: extracting: -rwxr-xr-x 40960 2007-08-22 14:54:37 bin/x_cons.exe
STDOUT: extracting: -rwxr-xr-x 40960 2007-08-22 14:54:37 bin/x_server.exe
STDOUT: extracting: -rwxr-xr-x 40960 2007-08-22 14:54:37 bin/x_show.exe
STDOUT: extracting: -rwxr-xr-x 40960 2007-08-22 14:54:37 bin/x_start.exe
STDOUT: extracting: -rwxr-xr-x 40960 2007-08-22 14:54:37 bin/x_stop.exe
STDOUT: extracting: -rwxr-xr-x 40960 2007-08-22 14:54:37 bin/x_wiz.exe
STDOUT: extracting: -rwxr-xr-x 40960 2007-08-22 14:54:37 bin/x_wizard.exe
STDOUT: extracting: -rwxr-xr-x 40960 2007-08-22 14:54:37 bin/x_wizstop.exe
STDOUT: extracting: -rwxr-xr-x 40960 2007-08-22 14:54:37 bin/x_wiztrc.exe
STDOUT: extracting: drwxr-xr-x 0 2007-08-22 16:21:45 env/
STDOUT: extracting: -rw-rr 122 2007-08-22 13:11:04 env/serv.use
STDOUT: extracting: -rw-rr 245 2007-08-22 13:11:04 env/xstart.use
STDOUT: extracting: -rw-rr 542 2007-08-22 13:11:04 env/xstop.use
STDOUT: extracting: drwxr-xr-x 0 2007-08-22 16:21:45 etc/
STDOUT: extracting: -rw-rr 207 2007-08-22 10:47:53 etc/VERSIONS
STDOUT: extracting: drwxr-xr-x 0 2007-08-22 16:21:46 pgm/
STDOUT: extracting: -rwxr-xr-x 483328 2007-08-22 11:22:45 pgm/serv.exe
STDOUT: extracting: -rwxr-xr-x 311296 2007-08-22 11:22:01 pgm/show.exe
STDOUT: checking unpacked archive... MSG: check file "bin/x_wizstop.exe": ok
MSG: check file "bin/x_analys.exe": ok
MSG: check file "bin/x_cons.exe": ok
MSG: check file "bin/xpu.exe": ok
MSG: check file "bin/sysmon.exe": ok
MSG: check file "bin/x_start.exe": ok
MSG: check file "env/xstart.use": ok
MSG: check file "pgm/serv.exe": ok
MSG: check file "bin/x_server.exe": ok
MSG: check file "bin/sqlrun.dll": ok
MSG: check file "etc/VERSIONS": ok
MSG: check file "bin/xbackup.exe": ok
MSG: check file "bin/x_wiz.exe": ok
MSG: check file "bin/x_show.exe": ok
MSG: check file "env/serv.use": ok
MSG: check file "env/xstop.use": ok
MSG: check file "pgm/show.exe": ok
MSG: check file "bin/x_wizard.exe": ok
MSG: check file "bin/sdbinfo.exe": ok
MSG: check file "bin/xinstinfo.exe": ok
MSG: check file "bin/x_wiztrc.exe": ok
MSG: check file "bin/x_stop.exe": ok
STDOUT: ok
SYS: "c:\program files\sdb\programs\bin\x_server.exe" install: 19709 INFO: Service 'XServer' installed successfully
MSG: SYSTEM PATH is up to date
MSG: packagedata of package Server Utilities changed
MSG: writing 2 packages
MSG: net install registry size = 34516 bytes
MSG: wrote install registry (39107 bytes)
MSG: packagedata of package Database Kernel changed
MSG: writing 3 packages
MSG: net install registry size = 35011 bytes
MSG: wrote install registry (39960 bytes)
STDOUT: start real extraction of "C:/Temp/MaxC.tmp/SDBKRN.TGZ"
STDOUT: extracting: drwxr-xr-x 0 2007-08-22 16:22:29 bin/
STDOUT: extracting: -rwxr-xr-x 274432 2007-08-22 12:59:27 bin/backint.exe
STDOUT: extracting: -rwxr-xr-x 794624 2007-08-22 13:01:49 bin/dbmevtdisp.exe
STDOUT: extracting: -rwxr-xr-x 548864 2007-08-22 13:02:01 bin/dbmevthndl_display.exe
STDOUT: extracting: -rwxr-xr-x 561152 2007-08-22 13:02:13 bin/dbmevthndl_winlog.exe
STDOUT: extracting: -rwxr-xr-x 290816 2007-08-22 12:57:17 bin/dbmsrvctl.exe
STDOUT: extracting: -rwxr-xr-x 41705 2007-08-22 10:57:11 bin/ireport.py
STDOUT: extracting: -rwxr-xr-x 245760 2007-08-22 13:00:41 bin/pipe2file.exe
STDOUT: extracting: -rwxr-xr-x 1204224 2007-08-22 12:59:35 bin/sdbfill.exe
STDOUT: extracting: -rwxr-xr-x 352256 2007-08-22 14:54:35 bin/sqlrun.dll
STDOUT: extracting: -rwxr-xr-x 53248 2007-08-22 11:02:31 bin/sqlver.exe
STDOUT: extracting: -rwxr-xr-x 53248 2007-08-22 11:02:31 bin/sqlwhat.exe
STDOUT: extracting: -rwxr-xr-x 40960 2007-08-22 14:54:37 bin/xci.exe
STDOUT: extracting: -rwxr-xr-x 40960 2007-08-22 14:54:37 bin/xkernprot.exe
STDOUT: extracting: -rwxr-xr-x 40960 2007-08-22 14:54:37 bin/xoldci.exe
STDOUT: extracting: -rwxr-xr-x 40960 2007-08-22 14:54:37 bin/xservice.exe
STDOUT: extracting: -rwxr-xr-x 40960 2007-08-22 14:54:37 bin/xtracesort.exe
STDOUT: extracting: -rwxr-xr-x 40960 2007-08-22 14:54:37 bin/x_diagnose.exe
STDOUT: extracting: -rwxr-xr-x 327680 2007-08-22 13:02:31 bin/x_python.exe
STDOUT: extracting: drwxr-xr-x 0 2007-08-22 16:22:14 cluster/
STDOUT: extracting: -rwxr-xr-x 2064384 2007-08-22 11:37:27 cluster/dbmsrv_clu.exe
STDOUT: extracting: -rwxr-xr-x 81920 2007-08-22 11:23:39 cluster/SAPDBMSCSEx.dll
STDOUT: extracting: -rwxr-xr-x 122880 2007-08-22 11:23:51 cluster/sapdbmscsman.dll
STDOUT: extracting: -rwxr-xr-x 77824 2007-08-22 11:23:11 cluster/SAPDBMSCSMan.exe
STDOUT: extracting: -rwxr-xr-x 57344 2007-08-22 11:23:05 cluster/SAPDBMSCSRes.dll
STDOUT: extracting: -rwxr-xr-x 307200 2007-08-22 11:24:07 cluster/service_clu.exe
STDOUT: extracting: -rwxr-xr-x 495616 2007-08-22 11:24:05 cluster/serv_clu.exe
STDOUT: extracting: -rwxr-xr-x 339968 2007-08-22 11:24:01 cluster/stop_clu.exe
STDOUT: extracting: -rwxr-xr-x 339968 2007-08-22 11:23:59 cluster/strt_clu.exe
STDOUT: extracting: drwxr-xr-x 0 2007-08-22 16:22:15 demo/
STDOUT: extracting: -rw-rr 3110911 2007-08-22 10:57:11 demo/HOTEL.py
STDOUT: extracting: -rwxr-xr-x 367 2007-08-22 10:57:11 demo/ltutorial.py
STDOUT: extracting: -rw-rr 11333 2007-08-22 10:57:11 demo/tutoriallib.py
STDOUT: extracting: drwxr-xr-x 0 2007-08-22 16:22:31 doc/
STDOUT: extracting: drwxr-xr-x 0 2007-08-22 16:22:33 doc/FirstSteps/
STDOUT: extracting: -rw-rr 3455 2007-08-22 10:57:11 doc/FirstSteps/index.html
STDOUT: extracting: drwxr-xr-x 0 2007-08-22 16:22:32 doc/FirstSteps/Java/
STDOUT: extracting: -rw-rr 1019 2007-08-22 10:57:11 doc/FirstSteps/Java/DemodbData.class
STDOUT: extracting: -rw-rr 1536 2007-08-22 10:57:11 doc/FirstSteps/Java/DemodbData.java
STDOUT: extracting: -rw-rr 1599 2007-08-22 10:57:11 doc/FirstSteps/Java/HelloMaxDB.class
STDOUT: extracting: -rw-rr 1459 2007-08-22 10:57:11 doc/FirstSteps/Java/HelloMaxDB.java
STDOUT: extracting: -rw-rr 1959 2007-08-22 10:57:11 doc/FirstSteps/Java/HowToJava.html
STDOUT: extracting: -rw-rr 1305 2007-08-22 10:57:11 doc/FirstSteps/Java/StateMaxDB.class
STDOUT: extracting: -rw-rr 1064 2007-08-22 10:57:11 doc/FirstSteps/Java/StateMaxDB.java
STDOUT: extracting: -rw-rr 227 2007-08-22 10:57:11 doc/FirstSteps/maxdbenv.cmd
STDOUT: extracting: drwxr-xr-x 0 2007-08-22 16:22:33 doc/FirstSteps/ODBC/
STDOUT: extracting: -rw-rr 4510 2007-08-22 10:57:11 doc/FirstSteps/ODBC/HelloMaxDB.c
STDOUT: extracting: -rw-rr 1293 2007-08-22 10:57:11 doc/FirstSteps/ODBC/HowToODBC.html
STDOUT: extracting: -rw-rr 393 2007-08-22 10:57:11 doc/FirstSteps/ODBC/Makefile
STDOUT: extracting: drwxr-xr-x 0 2007-08-22 16:22:33 doc/FirstSteps/Perl/
STDOUT: extracting: -rw-rr 973 2007-08-22 10:57:11 doc/FirstSteps/Perl/demodbData.pm
STDOUT: extracting: -rw-rr 1894 2007-08-22 10:57:11 doc/FirstSteps/Perl/HowToPerl.html
STDOUT: extracting: -rwxr-xr-x 960 2007-08-22 10:57:11 doc/FirstSteps/Perl/StateMaxDB.pl
STDOUT: extracting: drwxr-xr-x 0 2007-08-22 16:22:33 doc/FirstSteps/Python/
STDOUT: extracting: -rw-rr 871 2007-08-22 10:57:11 doc/FirstSteps/Python/demodbData.py
STDOUT: extracting: -rwxr-xr-x 859 2007-08-22 10:57:11 doc/FirstSteps/Python/HelloMaxDB-API.py
STDOUT: extracting: -rwxr-xr-x 859 2007-08-22 10:57:11 doc/FirstSteps/Python/HelloMaxDB.py
STDOUT: extracting: -rw-rr 3043 2007-08-22 10:57:11 doc/FirstSteps/Python/HowToPython.html
STDOUT: extracting: -rwxr-xr-x 865 2007-08-22 10:57:11 doc/FirstSteps/Python/StateMaxDB.py
STDOUT: extracting: drwxr-xr-x 0 2007-08-22 16:22:34 doc/FirstSteps/SQLDBC/
STDOUT: extracting: -rw-rr 3522 2007-08-22 10:57:11 doc/FirstSteps/SQLDBC/HelloMaxDB.cpp
STDOUT: extracting: -rw-rr 1329 2007-08-22 10:57:11 doc/FirstSteps/SQLDBC/HowToSQLDBC.html
STDOUT: extracting: -rw-rr 563 2007-08-22 10:57:11 doc/FirstSteps/SQLDBC/Makefile
STDOUT: extracting: drwxr-xr-x 0 2007-08-22 16:22:21 env/
STDOUT: extracting: -rwxr-xr-x 6150 2007-08-22 13:02:13 env/APPS.py
STDOUT: extracting: -rw-rr 3800 2007-08-22 13:02:13 env/CNR3DATA.py
STDOUT: extracting: -rw-rr 8216 2007-08-22 13:02:13 env/CNR3TAB.py
STDOUT: extracting: -rw-rr 196453 2007-08-22 13:11:05 env/cserv.pcf
STDOUT: extracting: -rw-rr 1861 2007-08-22 13:02:15 env/DBANA.py
STDOUT: extracting: -rw-rr 17874 2007-08-22 13:02:15 env/DBMVIEWS.py
STDOUT: extracting: drwxr-xr-x 0 2007-08-22 16:22:16 env/en/
STDOUT: extracting: -rw-rr 7609 2007-08-22 13:11:04 env/en/DBM.en
STDOUT: extracting: -rw-rr 15713 2007-08-22 13:02:15 env/GARBAGE.py
STDOUT: extracting: -rw-rr 249 2007-08-22 13:11:04 env/general.use
STDOUT: extracting: -rwxr-xr-x 1304 2007-08-22 13:02:21 env/getpackages.py
STDOUT: extracting: -rw-rr 1144 2007-08-22 13:02:15 env/INFO.py
STDOUT: extracting: -rw-rr 14122 2007-08-22 13:02:23 env/installib.py
STDOUT: extracting: -rw-rr 73794 2007-08-22 13:02:17 env/JDBC.py
STDOUT: extracting: -rw-rr 396 2007-08-22 13:11:04 env/kernprot.use
STDOUT: extracting: -rwxr-xr-x 949 2007-08-22 13:02:23 env/lapps.py
STDOUT: extracting: -rw-rr 8269 2007-08-22 10:57:11 env/lsystab.py
STDOUT: extracting: -rw-rr 19374 2007-08-22 13:02:15 env/ODBC.py
STDOUT: extracting: -rw-rr 1241 2007-08-22 13:02:17 env/ORADD.py
STDOUT: extracting: -rw-rr 266421 2007-08-22 13:02:17 env/ORADDCOM.py
STDOUT: extracting: -rw-rr 9586 2007-08-22 13:02:17 env/ORADDSYN.py
STDOUT: extracting: -rw-rr 158400 2007-08-22 13:02:17 env/ORADDV.py
STDOUT: extracting: -rw-rr 1400 2007-08-22 13:02:19 env/PRECOM.py
STDOUT: extracting: -rw-rr 50345 2007-08-22 13:02:23 env/REPOSITORY.py
STDOUT: extracting: -rw-rr 61439 2007-08-22 13:02:15 env/SAPDBLOADER.py
STDOUT: extracting: -rw-rr 4483 2007-08-22 13:02:19 env/SHOWCMD.py
STDOUT: extracting: -rw-rr 49869 2007-08-22 13:02:19 env/SQLDBC.py
STDOUT: extracting: -rw-rr 47433 2007-08-22 13:02:19 env/SYSDBA.py
STDOUT: extracting: -rw-rr 57876 2007-08-22 13:02:19 env/SYSDBACOM.py
STDOUT: extracting: -rw-rr 16770 2007-08-22 13:02:19 env/SYSINFO.py
STDOUT: extracting: -rw-rr 114095 2007-08-22 13:02:21 env/SYSINFOCOM.py
STDOUT: extracting: -rw-rr 12526 2007-08-22 13:02:21 env/TRIGGER.py
STDOUT: extracting: -rw-rr 3203 2007-08-22 13:02:21 env/UDE.py
STDOUT: extracting: -rw-rr 6596 2007-08-22 13:02:23 env/WA.py
STDOUT: extracting: -rw-rr 54824 2007-08-22 13:02:21 env/XDD.py
STDOUT: extracting: -rw-rr 106292 2007-08-22 13:02:21 env/XDDCOM.py
STDOUT: extracting: drwxr-xr-x 0 2007-08-22 16:22:21 lib/
STDOUT: extracting: drwxr-xr-x 0 2007-08-22 16:22:22 lib/python2.3/
STDOUT: extracting: -rw-rr 6867 2007-08-22 10:57:11 lib/python2.3/optlib.py
STDOUT: extracting: -rwxr-xr-x 135234 2007-08-22 10:57:11 lib/python2.3/pyexpat.pyd
STDOUT: extracting: drwxr-xr-x 0 2007-08-22 16:22:22 lib/python2.3/sdb/
STDOUT: extracting: -rw-rr 14852 2007-08-22 10:57:11 lib/python2.3/sdb/dbapi.py
STDOUT: extracting: -rwxr-xr-x 507904 2007-08-22 13:02:37 lib/python2.3/sdb/dbm.pyd
STDOUT: extracting: -rwxr-xr-x 487424 2007-08-22 13:02:41 lib/python2.3/sdb/loader.pyd
STDOUT: extracting: -rwxr-xr-x 471040 2007-08-22 13:02:49 lib/python2.3/sdb/sql.pyd
STDOUT: extracting: -rw-rr 208 2007-08-22 10:57:11 lib/python2.3/sdb/__init__.py
STDOUT: extracting: -rwxr-xr-x 61503 2007-08-22 10:57:11 lib/python2.3/zlib.pyd
STDOUT: extracting: -rwxr-xr-x 49218 2007-08-22 10:57:11 lib/python2.3/_socket.pyd
STDOUT: extracting: -rwxr-xr-x 57407 2007-08-22 10:57:11 lib/python2.3/_sre.pyd
STDOUT: extracting: drwxr-xr-x 0 2007-08-22 16:22:22 misc/
STDOUT: extracting: -rw-rr 2437 2007-08-22 15:41:01 misc/create_demo_db.cmd
STDOUT: extracting: -rw-rr 417 2007-08-22 15:41:01 misc/drop_demo_db.cmd
STDOUT: extracting: drwxr-xr-x 0 2007-08-22 16:22:31 pgm/
STDOUT: extracting: -rwxr-xr-x 200704 2007-08-22 13:00:45 pgm/backup.exe
STDOUT: extracting: -rwxr-xr-x 380928 2007-08-22 11:21:45 pgm/cons.exe
STDOUT: extracting: -rwxr-xr-x 45056 2007-08-22 11:21:21 pgm/cr_param.exe
STDOUT: extracting: -rwxr-xr-x 940032 2007-08-22 10:57:11 pgm/dbghelp.dll
STDOUT: extracting: -rwxr-xr-x 294912 2007-08-22 12:57:33 pgm/dbmreg.exe
STDOUT: extracting: -rwxr-xr-x 454656 2007-08-22 12:58:13 pgm/dbmshm.exe
STDOUT: extracting: -rwxr-xr-x 2043904 2007-08-22 12:57:05 pgm/dbmsrv.exe
STDOUT: extracting: -rwxr-xr-x 1814528 2007-08-22 12:57:53 pgm/dbmsrvscd.exe
STDOUT: extracting: -rwxr-xr-x 294912 2007-08-22 12:57:23 pgm/dbmstart.exe
STDOUT: extracting: -rwxr-xr-x 294912 2007-08-22 12:57:29 pgm/dbmstop.exe
STDOUT: extracting: -rwxr-xr-x 294912 2007-08-22 12:57:39 pgm/dbmunreg.exe
STDOUT: extracting: -rwxr-xr-x 69632 2007-08-22 15:07:11 pgm/dbpinstall.dll
STDOUT: extracting: -rwxr-xr-x 1069056 2007-08-22 11:46:57 pgm/diagnose.exe
STDOUT: extracting: -rwxr-xr-x 7131136 2007-08-22 12:56:49 pgm/kernel.exe
STDOUT: extracting: -rwxr-xr-x 118784 2007-08-22 11:38:37 pgm/libhsscopy.dll
STDOUT: extracting: -rwxr-xr-x 1175552 2007-08-22 15:00:39 pgm/liboms.dll
STDOUT: extracting: -rwxr-xr-x 147456 2007-08-22 15:08:37 pgm/libsqlcls.dll
STDOUT: extracting: -rwxr-xr-x 1159168 2007-08-22 15:10:19 pgm/libSQLDBC.dll
STDOUT: extracting: -rwxr-xr-x 1245184 2007-08-22 15:13:55 pgm/libSQLDBC_C.dll
STDOUT: extracting: -rwxr-xr-x 3006464 2007-08-22 13:10:31 pgm/lserver.exe
STDOUT: extracting: -rwxr-xr-x 20545 2007-08-22 10:57:11 pgm/pysapdb.exe
STDOUT: extracting: -rwxr-xr-x 974915 2007-08-22 10:57:11 pgm/python23.dll
STDOUT: extracting: -rw-rr 2071185 2007-08-22 10:57:11 pgm/python23.zip
STDOUT: extracting: -rwxr-xr-x 45056 2007-08-22 11:21:21 pgm/renparam.exe
STDOUT: extracting: -rwxr-xr-x 290816 2007-08-22 11:22:51 pgm/service.exe
STDOUT: extracting: -rwxr-xr-x 1286144 2007-08-22 11:45:21 pgm/slowci.exe
STDOUT: extracting: -rwxr-xr-x 413696 2007-08-22 11:22:55 pgm/sqlinst.dll
STDOUT: extracting: -rwxr-xr-x 1359872 2007-08-22 11:23:01 pgm/sqlmsg.dll
STDOUT: extracting: -rwxr-xr-x 323584 2007-08-22 11:21:53 pgm/stop.exe
STDOUT: extracting: -rwxr-xr-x 323584 2007-08-22 11:21:49 pgm/strt.exe
STDOUT: extracting: -rwxr-xr-x 98304 2007-08-22 13:18:51 pgm/StudioUtil.dll
STDOUT: extracting: -rwxr-xr-x 49152 2007-08-22 11:38:31 pgm/sysrc.exe
STDOUT: extracting: -rwxr-xr-x 73728 2007-08-22 11:22:59 pgm/systemrc.exe
STDOUT: extracting: -rwxr-xr-x 225280 2007-08-22 13:19:01 pgm/TableDefC.dll
STDOUT: extracting: -rwxr-xr-x 45056 2007-08-22 13:02:03 pgm/Tools_WinEvtLog.dll
STDOUT: extracting: -rwxr-xr-x 73728 2007-08-22 13:10:47 pgm/tracesort.exe
STDOUT: extracting: drwxr-xr-x 0 2007-08-22 16:22:31 sap/
STDOUT: extracting: -rw-rr 147 2007-08-22 10:57:11 sap/dbpinstall.lst
STDOUT: extracting: -rw-rr 761 2007-08-22 12:59:05 sap/grantxdb.dbm
STDOUT: extracting: -rwxr-xr-x 18192 2007-08-22 10:57:11 sap/lcinit.bat
STDOUT: extracting: -rwxr-xr-x 126976 2007-08-22 15:06:45 sap/lvcbench.dll
STDOUT: extracting: -rw-rr 89 2007-08-22 10:57:11 sap/saprfc.ini
STDOUT: extracting: -rwxr-xr-x 86016 2007-08-22 13:21:11 sap/sphsapdb.dll
STDOUT: extracting: -rw-rr 12 2007-08-22 10:57:11 sap/sphsapdb.lst
STDOUT: checking unpacked archive... MSG: check file "doc/FirstSteps/ODBC/HowToODBC.html": ok
MSG: check file "lib/python2.3/_socket.pyd": ok
MSG: check file "pgm/dbmsrv.exe": ok
MSG: check file "env/INFO.py": ok
MSG: check file "pgm/diagnose.exe": ok
MSG: check file "misc/create_demo_db.cmd": ok
MSG: check file "lib/python2.3/sdb/__init__.py": ok
MSG: check file "bin/xci.exe": ok
MSG: check file "bin/xtracesort.exe": ok
MSG: check file "bin/x_diagnose.exe": ok
MSG: check file "pgm/Tools_WinEvtLog.dll": ok
MSG: check file "pgm/cons.exe": ok
MSG: check file "sap/grantxdb.dbm": ok
MSG: check file "demo/tutoriallib.py": ok
MSG: check file "sap/sphsapdb.dll": ok
MSG: check file "demo/HOTEL.py": ok
MSG: check file "env/cserv.pcf": ok
MSG: check file "lib/python2.3/_sre.pyd": ok
MSG: check file "pgm/service.exe": ok
MSG: check file "doc/FirstSteps/Python/HowToPython.html": ok
MSG: check file "doc/FirstSteps/ODBC/HelloMaxDB.c": ok
MSG: check file "doc/FirstSteps/Java/DemodbData.java": ok
MSG: check file "sap/saprfc.ini": ok
MSG: check file "pgm/dbghelp.dll": ok
MSG: check file "cluster/strt_clu.exe": ok
MSG: check file "cluster/SAPDBMSCSMan.exe": ok
MSG: check file "pgm/tracesort.exe": ok
MSG: check file "bin/sqlwhat.exe": ok
MSG: check file "lib/python2.3/pyexpat.pyd": ok
MSG: check file "pgm/libSQLDBC_C.dll": ok
MSG: check file "bin/x_python.exe": ok
MSG: check file "pgm/python23.dll": ok
MSG: check file "env/SQLDBC.py": ok
MSG: check file "cluster/SAPDBMSCSRes.dll": ok
MSG: check file "cluster/stop_clu.exe": ok
MSG: check file "pgm/sqlinst.dll": ok
MSG: check file "pgm/StudioUtil.dll": ok
MSG: check file "doc/FirstSteps/Python/HelloMaxDB.py": ok
MSG: check file "sap/sphsapdb.lst": ok
MSG: check file "pgm/cr_param.exe": ok
MSG: check file "bin/sqlrun.dll": ok
MSG: check file "bin/backint.exe": ok
MSG: check file "pgm/libSQLDBC.dll": ok
MSG: check file "bin/dbmsrvctl.exe": ok
MSG: check file "env/UDE.py": ok
MSG: check file "doc/FirstSteps/Java/DemodbData.class": ok
MSG: check file "sap/lcinit.bat": ok
MSG: check file "env/lsystab.py": ok
MSG: check file "doc/FirstSteps/Perl/StateMaxDB.pl": ok
MSG: check file "lib/python2.3/zlib.pyd": ok
MSG: check file "pgm/python23.zip": ok
MSG: check file "doc/FirstSteps/Java/HelloMaxDB.class": ok
MSG: check file "env/installib.py": ok
MSG: check file "pgm/renparam.exe": ok
MSG: check file "doc/FirstSteps/Python/StateMaxDB.py": ok
MSG: check file "env/TRIGGER.py": ok
MSG: check file "pgm/libhsscopy.dll": ok
MSG: check file "pgm/systemrc.exe": ok
MSG: check file "pgm/dbmunreg.exe": ok
MSG: check file "bin/dbmevtdisp.exe": ok
MSG: check file "doc/FirstSteps/ODBC/Makefile": ok
MSG: check file "pgm/stop.exe": ok
MSG: check file "lib/python2.3/sdb/sql.pyd": ok
MSG: check file "env/APPS.py": ok
MSG: check file "env/kernprot.use": ok
MSG: check file "pgm/liboms.dll": ok
MSG: check file "cluster/service_clu.exe": ok
MSG: check file "env/ORADDSYN.py": ok
MSG: check file "env/SYSINFOCOM.py": ok
MSG: check file "cluster/SAPDBMSCSEx.dll": ok
MSG: check file "doc/FirstSteps/SQLDBC/HelloMaxDB.cpp": ok
MSG: check file "env/CNR3DATA.py": ok
MSG: check file "doc/FirstSteps/index.html": ok
MSG: check file "doc/FirstSteps/Java/HowToJava.html": ok
MSG: check file "doc/FirstSteps/Perl/demodbData.pm": ok
MSG: check file "bin/pipe2file.exe": ok
MSG: check file "bin/dbmevthndl_winlog.exe": ok
MSG: check file "demo/ltutorial.py": ok
MSG: check file "doc/FirstSteps/Python/HelloMaxDB-API.py": ok
MSG: check file "bin/xservice.exe": ok
MSG: check file "env/REPOSITORY.py": ok
MSG: check file "cluster/serv_clu.exe": ok
MSG: check file "lib/python2.3/optlib.py": ok
MSG: check file "env/ORADDCOM.py": ok
MSG: check file "doc/FirstSteps/SQLDBC/Makefile": ok
MSG: check file "pgm/dbmsrvscd.exe": ok
MSG: check file "doc/FirstSteps/Perl/HowToPerl.html": ok
MSG: check file "pgm/TableDefC.dll": ok
MSG: check file "cluster/dbmsrv_clu.exe": ok
MSG: check file "pgm/sysrc.exe": ok
MSG: check file "bin/xoldci.exe": ok
MSG: check file "pgm/kernel.exe": ok
MSG: check file "doc/FirstSteps/Java/StateMaxDB.class": ok
MSG: check file "pgm/slowci.exe": ok
MSG: check file "env/SAPDBLOADER.py": ok
MSG: check file "bin/sqlver.exe": ok
MSG: check file "env/general.use": ok
MSG: check file "sap/dbpinstall.lst": ok
MSG: check file "pgm/dbpinstall.dll": ok
MSG: check file "doc/FirstSteps/Java/StateMaxDB.java": ok
MSG: check file "env/en/DBM.en": ok
MSG: check file "sap/lvcbench.dll": ok
MSG: check file "env/lapps.py": ok
MSG: check file "env/getpackages.py": ok
MSG: check file "pgm/lserver.exe": ok
MSG: check file "env/WA.py": ok
MSG: check file "lib/python2.3/sdb/dbm.pyd": ok
MSG: check file "misc/drop_demo_db.cmd": ok
MSG: check file "bin/ireport.py": ok
MSG: check file "lib/python2.3/sdb/dbapi.py": ok
MSG: check file "doc/FirstSteps/Java/HelloMaxDB.java": ok
MSG: check file "env/ORADDV.py": ok
MSG: check file "pgm/pysapdb.exe": ok
MSG: check file "doc/FirstSteps/maxdbenv.cmd": ok
MSG: check file "env/GARBAGE.py": ok
MSG: check file "pgm/libsqlcls.dll": ok
MSG: check file "bin/xkernprot.exe": ok
MSG: check file "env/SYSINFO.py": ok
MSG: check file "env/XDDCOM.py": ok
MSG: check file "bin/sdbfill.exe": ok
MSG: check file "doc/FirstSteps/SQLDBC/HowToSQLDBC.html": ok
MSG: check file "env/XDD.py": ok
MSG: check file "lib/python2.3/sdb/loader.pyd": ok
MSG: check file "env/ODBC.py": ok
MSG: check file "pgm/backup.exe": ok
MSG: check file "env/SYSDBA.py": ok
MSG: check file "pgm/dbmshm.exe": ok
MSG: check file "env/CNR3TAB.py": ok
MSG: check file "env/ORADD.py": ok
MSG: check file "env/PRECOM.py": ok
MSG: check file "pgm/strt.exe": ok
MSG: check file "cluster/sapdbmscsman.dll": ok
MSG: check file "env/DBANA.py": ok
MSG: check file "env/SHOWCMD.py": ok
MSG: check file "pgm/dbmstop.exe": ok
MSG: check file "env/SYSDBACOM.py": ok
MSG: check file "bin/dbmevthndl_display.exe": ok
MSG: check file "doc/FirstSteps/Python/demodbData.py": ok
MSG: check file "pgm/dbmstart.exe": ok
MSG: check file "env/DBMVIEWS.py": ok
MSG: check file "env/JDBC.py": ok
MSG: check file "pgm/sqlmsg.dll": ok
MSG: check file "pgm/dbmreg.exe": ok
STDOUT: ok
MSG: file "c:/program files/sdb/7603/doc/FirstSteps/index.html" modified by installer
MSG: file "c:/program files/sdb/7603/doc/FirstSteps/Perl/HowToPerl.html" modified by installer
MSG: file "c:/program files/sdb/7603/doc/FirstSteps/Python/HowToPython.html" modified by installer
MSG: file "c:/program files/sdb/7603/doc/FirstSteps/ODBC/HowToODBC.html" modified by installer
MSG: file "c:/program files/sdb/7603/doc/FirstSteps/Java/HowToJava.html" modified by installer
MSG: file "c:/program files/sdb/7603/misc/create_demo_db.cmd" modified by installer
MSG: file "c:/program files/sdb/7603/misc/drop_demo_db.cmd" modified by installer
MSG: file "c:/program files/sdb/7603/doc/FirstSteps/maxdbenv.cmd" modified by installer
SYS: "C:\Program Files\sdb\7603\bin\dbmsrvctl.exe" start
SYS: "C:\Program Files\sdb\programs\pgm\dbmcli.exe" -R "C:\Program Files\sdb\7603" inst_reg -k \"C:\Program Files\sdb\7603\": ERR
SYS: "C:\Program Files\sdb\programs\pgm\dbmcli.exe" -R "C:\Program Files\sdb\7603" inst_reg -k \"C:\Program Files\sdb\7603\": -24913,ERR_SERVICEDB: Cannot register service database instance for C:\Program Files\sdb\7603
STDERR: error occured while executing "C:\Program Files\sdb\programs\pgm\dbmcli.exe" -R "C:\Program Files\sdb\7603" inst_reg -k \"C:\Program Files\sdb\7603\"
STDERR: "C:\Program Files\sdb\programs\pgm\dbmcli.exe" -R "C:\Program Files\sdb\7603" inst_reg -k \"C:\Program Files\sdb\7603\": ERR
"C:\Program Files\sdb\programs\pgm\dbmcli.exe" -R "C:\Program Files\sdb\7603" inst_reg -k \"C:\Program Files\sdb\7603\": -24913,ERR_SERVICEDB: Cannot register service database instance for C:\Program Files\sdb\7603
STDERR: installation exited abnormally at We, Sep 12, 2007 at 16:42:41
MSG: packagedata of package Redist Python changed
MSG: writing 4 packages
MSG: net install registry size = 35481 bytes
MSG: wrote install registry (40814 bytes)
STDOUT: start real extraction of "C:/Temp/MaxC.tmp/SDBRDPY.TGZ"
STDOUT: extracting: drwxr-xr-x 0 2007-08-22 16:26:58 bin/
STDOUT: extracting: -rwxr-xr-x 327680 2007-08-22 13:02:31 bin/x_python.exe
STDOUT: extracting: drwxr-xr-x 0 2007-08-22 16:26:58 lib/
STDOUT: extracting: drwxr-xr-x 0 2007-08-22 16:26:59 lib/python2.3/
STDOUT: extracting: -rw-rr 6867 2007-08-22 10:57:11 lib/python2.3/optlib.py
STDOUT: extracting: -rwxr-xr-x 135234 2007-08-22 10:57:11 lib/python2.3/pyexpat.pyd
STDOUT: extracting: drwxr-xr-x 0 2007-08-22 16:26:58 lib/python2.3/sdb/
STDOUT: extracting: -rwxr-xr-x 507904 2007-08-22 13:02:37 lib/python2.3/sdb/dbm.pyd
STDOUT: extracting: -rwxr-xr-x 487424 2007-08-22 13:02:41 lib/python2.3/sdb/loader.pyd
STDOUT: extracting: -rwxr-xr-x 471040 2007-08-22 13:02:49 lib/python2.3/sdb/sql.pyd
STDOUT: extracting: -rw-rr 208 2007-08-22 10:57:11 lib/python2.3/sdb/__init__.py
STDOUT: extracting: -rwxr-xr-x 61503 2007-08-22 10:57:11 lib/python2.3/zlib.pyd
STDOUT: extracting: -rwxr-xr-x 18432 2007-08-22 10:57:11 lib/python2.3/_csv.pyd
STDOUT: extracting: -rwxr-xr-x 49218 2007-08-22 10:57:11 lib/python2.3/_socket.pyd
STDOUT: extracting: -rwxr-xr-x 57407 2007-08-22 10:57:11 lib/python2.3/_sre.pyd
STDOUT: extracting: -rwxr-xr-x 36864 2007-08-22 10:57:11 lib/python2.3/_winreg.pyd
STDOUT: extracting: drwxr-xr-x 0 2007-08-22 16:26:59 pgm/
STDOUT: extracting: -rwxr-xr-x 20545 2007-08-22 10:57:11 pgm/pysapdb.exe
STDOUT: extracting: -rwxr-xr-x 974915 2007-08-22 10:57:11 pgm/python23.dll
STDOUT: extracting: -rw-rr 2071185 2007-08-22 10:57:11 pgm/python23.zip
STDOUT: checking unpacked archive... MSG: check file "lib/python2.3/_socket.pyd": ok
MSG: check file "lib/python2.3/sdb/__init__.py": ok
MSG: check file "lib/python2.3/_sre.pyd": ok
MSG: check file "lib/python2.3/pyexpat.pyd": ok
MSG: check file "lib/python2.3/_winreg.pyd": ok
MSG: check file "bin/x_python.exe": ok
MSG: check file "pgm/python23.dll": ok
MSG: check file "lib/python2.3/zlib.pyd": ok
MSG: check file "pgm/python23.zip": ok
MSG: check file "lib/python2.3/_csv.pyd": ok
MSG: check file "lib/python2.3/sdb/sql.pyd": ok
MSG: check file "lib/python2.3/optlib.py": ok
MSG: check file "lib/python2.3/sdb/dbm.pyd": ok
MSG: check file "pgm/pysapdb.exe": ok
MSG: check file "lib/python2.3/sdb/loader.pyd": ok
STDOUT: ok
MSG: packagedata of package Redist Python changed
MSG: writing 4 packages
MSG: net install registry size = 38247 bytes
MSG: wrote install registry (43998 bytes)
MSG: packagedata of package Loader changed
MSG: writing 5 packages
MSG: net install registry size = 38756 bytes
MSG: wrote install registry (44891 bytes)
STDOUT: start real extraction of "C:/Temp/MaxC.tmp/SDBLD.TGZ"
STDOUT: extracting: drwxr-xr-x 0 2007-08-22 16:27:11 bin/
STDOUT: extracting: -rwxr-xr-x 3063808 2007-08-22 13:10:41 bin/loadercli.exe
STDOUT: extracting: drwxr-xr-x 0 2007-08-22 16:27:11 config/
STDOUT: extracting: -rw-rr 2323 2007-08-22 10:57:11 config/loader.cfg
STDOUT: extracting: drwxr-xr-x 0 2007-08-22 16:27:12 env/
STDOUT: extracting: -rw-rr 10895 2007-08-22 10:57:11 env/ISO_8859_1.TXT
STDOUT: extracting: -rw-rr 11119 2007-08-22 10:57:11 env/ISO_8859_2.TXT
STDOUT: extracting: -rw-rr 10794 2007-08-22 10:57:11 env/ISO_8859_3.TXT
STDOUT: extracting: -rw-rr 11095 2007-08-22 10:57:11 env/ISO_8859_4.TXT
STDOUT: extracting: -rw-rr 10730 2007-08-22 10:57:11 env/ISO_8859_5.TXT
STDOUT: extracting: -rw-rr 8568 2007-08-22 10:57:11 env/ISO_8859_6.TXT
STDOUT: extracting: -rw-rr 10890 2007-08-22 10:57:11 env/ISO_8859_7.TXT
STDOUT: extracting: drwxr-xr-x 0 2007-08-22 16:27:11 lib/
STDOUT: extracting: drwxr-xr-x 0 2007-08-22 16:27:11 lib/python2.3/
STDOUT: extracting: drwxr-xr-x 0 2007-08-22 16:27:11 lib/python2.3/sdb/
STDOUT: extracting: drwxr-xr-x 0 2007-08-22 16:27:11 lib/python2.3/sdb/loader/
STDOUT: extracting: -rw-rr 471627 2007-08-22 10:57:11 lib/python2.3/sdb/loader/transport.py
STDOUT: extracting: drwxr-xr-x 0 2007-08-22 16:27:11 pgm/
STDOUT: extracting: -rwxr-xr-x 3006464 2007-08-22 13:10:31 pgm/lserver.exe
STDOUT: checking unpacked archive... MSG: check file "env/ISO_8859_5.TXT": ok
MSG: check file "env/ISO_8859_3.TXT": ok
MSG: check file "bin/loadercli.exe": ok
MSG: check file "env/ISO_8859_7.TXT": ok
MSG: check file "config/loader.cfg": ok
MSG: check file "env/ISO_8859_4.TXT": ok
MSG: check file "env/ISO_8859_6.TXT": ok
MSG: check file "lib/python2.3/sdb/loader/transport.py": ok
MSG: check file "pgm/lserver.exe": ok
MSG: check file "env/ISO_8859_2.TXT": ok
MSG: check file "env/ISO_8859_1.TXT": ok
STDOUT: ok
MSG: packagedata of package Loader changed
MSG: writing 5 packages
MSG: net install registry size = 41068 bytes
MSG: wrote install registry (47551 bytes)
MSG: packagedata of package ODBC changed
MSG: writing 6 packages
MSG: net install registry size = 41566 bytes
MSG: wrote install registry (48457 bytes)
STDOUT: start real extraction of "C:/Temp/MaxC.tmp/SDBODBC.TGZ"
STDOUT: extracting: drwxr-xr-x 0 2007-08-22 16:26:36 incl/
STDOUT: extracting: -rw-rr 10677 2007-08-22 10:57:11 incl/SDBBOS.h
STDOUT: extracting: -rw-rr 30864 2007-08-22 11:02:14 incl/sql.h
STDOUT: extracting: -rw-rr 80764 2007-08-22 11:02:15 incl/sqlext.h
STDOUT: extracting: -rw-rr 8831 2007-08-22 11:02:15 incl/sqltypes.h
STDOUT: extracting: -rw-rr 23610 2007-08-22 11:02:15 incl/sqlucode.h
STDOUT: extracting: drwxr-xr-x 0 2007-08-22 16:26:36 lib/
STDOUT: extracting: -rw-rr 17738 2007-08-22 11:01:47 lib/sqlod32.lib
STDOUT: extracting: -rw-rr 25646 2007-08-22 11:02:15 lib/sqlod32w.lib
STDOUT: extracting: drwxr-xr-x 0 2007-08-22 16:26:37 pgm/
STDOUT: extracting: -rwxr-xr-x 491520 2007-08-22 13:22:33 pgm/libSDBBOS.dll
STDOUT: extracting: -rwxr-xr-x 13312 2007-08-22 10:58:17 pgm/odbcreg.exe
STDOUT: extracting: -rwxr-xr-x 1081344 2007-08-22 11:01:47 pgm/sqlod32.dll
STDOUT: extracting: -rwxr-xr-x 1142784 2007-08-22 11:02:15 pgm/sqlod32w.dll
STDOUT: extracting: -rwxr-xr-x 45056 2007-08-22 11:02:29 pgm/sqlodext.dll
STDOUT: extracting: -rwxr-xr-x 73728 2007-08-22 11:02:25 pgm/sqlsp32.dll
STDOUT: checking unpacked archive... MSG: check file "pgm/sqlsp32.dll": ok
MSG: check file "incl/SDBBOS.h": ok
MSG: check file "pgm/sqlodext.dll": ok
MSG: check file "incl/sqlucode.h": ok
MSG: check file "pgm/libSDBBOS.dll": ok
MSG: check file "pgm/odbcreg.exe": ok
MSG: check file "lib/sqlod32w.lib": ok
MSG: check file "pgm/sqlod32w.dll": ok
MSG: check file "pgm/sqlod32.dll": ok
MSG: check file "lib/sqlod32.lib": ok
MSG: check file "incl/sql.h": ok
MSG: check file "incl/sqlext.h": ok
MSG: check file "incl/sqltypes.h": ok
STDOUT: ok
SYS: "c:\program files\sdb\programs\pgm\odbcreg.exe" "SAP DB" -i -p "c:\program files\sdb\programs\pgm": ODBC Driver for 'SAP DB' has been successfully registered.
SYS: "c:\program files\sdb\programs\pgm\odbcreg.exe" "SAP DB" -i -p "c:\program files\sdb\programs\pgm":
SYS: "c:\program files\sdb\programs\pgm\odbcreg.exe" "SAP DB (Unicode)" -i -p "c:\program files\sdb\programs\pgm" -d sqlod32w.dll: ODBC Driver for 'SAP DB (Unicode)' has been successfully registered.
SYS: "c:\program files\sdb\programs\pgm\odbcreg.exe" "SAP DB (Unicode)" -i -p "c:\program files\sdb\programs\pgm" -d sqlod32w.dll:
SYS: "c:\program files\sdb\programs\pgm\odbcreg.exe" "SAP DB 7.4" -i -p "c:\program files\sdb\programs\pgm": ODBC Driver for 'SAP DB 7.4' has been successfully registered.
SYS: "c:\program files\sdb\programs\pgm\odbcreg.exe" "SAP DB 7.4" -i -p "c:\program files\sdb\programs\pgm":
SYS: "c:\program files\sdb\programs\pgm\odbcreg.exe" "MaxDB" -i -p "c:\program files\sdb\programs\pgm": ODBC Driver for 'MaxDB' has been successfully registered.
SYS: "c:\program files\sdb\programs\pgm\odbcreg.exe" "MaxDB" -i -p "c:\program files\sdb\programs\pgm":
SYS: "c:\program files\sdb\programs\pgm\odbcreg.exe" "MaxDB (Unicode)" -i -p "c:\program files\sdb\programs\pgm" -d sqlod32w.dll: ODBC Driver for 'MaxDB (Unicode)' has been successfully registered.
SYS: "c:\program files\sdb\programs\pgm\odbcreg.exe" "MaxDB (Unicode)" -i -p "c:\program files\sdb\programs\pgm" -d sqlod32w.dll:
MSG: packagedata of package ODBC changed
MSG: writing 6 packages
MSG: net install registry size = 45735 bytes
MSG: wrote install registry (53227 bytes)
MSG: packagedata of package Messages changed
MSG: writing 7 packages
MSG: net install registry size = 46260 bytes
MSG: wrote install registry (54118 bytes)
STDOUT: start real extraction of "C:/Temp/MaxC.tmp/SDBMSG.TGZ"
STDOUT: extracting: drwxr-xr-x 0 2007-08-22 16:27:34 msg/
STDOUT: extracting: -rw-rr 172 2007-08-22 10:57:11 msg/SDBMsg_AccessPathOptimize.xml
STDOUT: extracting: -rw-rr 846 2007-08-22 10:57:11 msg/SDBMsg_Admin.xml
STDOUT: extracting: -rw-rr 787 2007-08-22 10:57:11 msg/SDBMsg_APO.xml
STDOUT: extracting: -rw-rr 1107 2007-08-22 10:57:11 msg/SDBMsg_Backup.xml
STDOUT: extracting: -rw-rr 2879 2007-08-22 10:57:11 msg/SDBMsg_BTree.xml
STDOUT: extracting: -rw-rr 3255 2007-08-22 10:57:11 msg/SDBMsg_Catalog.xml
STDOUT: extracting: -rw-rr 8583 2007-08-22 10:57:11 msg/SDBMsg_Converter.xml
STDOUT: extracting: -rw-rr 29010 2007-08-22 10:57:11 msg/SDBMsg_Data.xml
STDOUT: extracting: -rw-rr 1692 2007-08-22 10:57:11 msg/SDBMsg_DataCache.xml
STDOUT: extracting: -rw-rr 333 2007-08-22 10:57:11 msg/SDBMsg_DBMCLI.xml
STDOUT: extracting: -rw-rr 6813 2007-08-22 10:57:11 msg/SDBMsg_DBMEd.xml
STDOUT: extracting: -rw-rr 340 2007-08-22 10:57:11 msg/SDBMsg_DBMLog.xml
STDOUT: extracting: -rw-rr 3395 2007-08-22 10:57:11 msg/SDBMsg_DBMScd.xml
STDOUT: extracting: -rw-rr 103652 2007-08-22 10:57:11 msg/SDBMsg_DBMSrv.xml
STDOUT: extracting: -rw-rr 2164 2007-08-22 10:57:11 msg/SDBMsg_DBMSrvBackTemplate.xml
STDOUT: extracting: -rw-rr 354 2007-08-22 10:57:11 msg/SDBMsg_DBMSrvOI.xml
STDOUT: extracting: -rw-rr 1174 2007-08-22 10:57:11 msg/SDBMsg_DBMSrvTest.xml
STDOUT: extracting: -rw-rr 1321 2007-08-22 10:57:11 msg/SDBMsg_DBProc.xml
STDOUT: extracting: -rw-rr 13403 2007-08-22 10:57:11 msg/SDBMsg_DBProvider.xml
STDOUT: extracting: -rw-rr 553 2007-08-22 10:57:11 msg/SDBMsg_DIAGNOSE.xml
STDOUT: extracting: -rw-rr 9669 2007-08-22 10:57:11 msg/SDBMsg_FileDir.xml
STDOUT: extracting: -rw-rr 1478 2007-08-22 10:57:11 msg/SDBMsg_Index.xml
STDOUT: extracting: -rw-rr 7628 2007-08-22 10:57:11 msg/SDBMsg_IOMan.xml
STDOUT: extracting: -rw-rr 2420 2007-08-22 10:57:11 msg/SDBMsg_Join.xml
STDOUT: extracting: -rw-rr 1790 2007-08-22 10:57:11 msg/SDBMsg_JoinPathOptimizer.xml
STDOUT: extracting: -rw-rr 2668 2007-08-22 10:57:11 msg/SDBMsg_KernelCommon.xml
STDOUT: extracting: -rw-rr 1035 2007-08-22 10:57:11 msg/SDBMsg_KSQL.xml
STDOUT: extracting: -rw-rr 1510 2007-08-22 10:57:11 msg/SDBMsg_LiveCache.xml
STDOUT: extracting: -rw-rr 172 2007-08-22 10:57:11 msg/SDBMsg_Loader.xml
STDOUT: extracting: -rw-rr 813 2007-08-22 10:57:11 msg/SDBMsg_LockManager.xml
STDOUT: extracting: -rw-rr 392 2007-08-22 10:57:11 msg/SDBMsg_LOCKS.xml
STDOUT: extracting: -rw-rr 10275 2007-08-22 10:57:11 msg/SDBMsg_Log.xml
STDOUT: extracting: -rw-rr 4145 2007-08-22 10:57:11 msg/SDBMsg_Messages.xml
STDOUT: extracting: -rw-rr 465 2007-08-22 10:57:11 msg/SDBMsg_MultiVersionRead.xml
STDOUT: extracting: -rw-rr 562 2007-08-22 10:57:11 msg/SDBMsg_ObjectContainer.xml
STDOUT: extracting: -rw-rr 3793 2007-08-22 10:57:11 msg/SDBMsg_OMS.xml
STDOUT: extracting: -rw-rr 172 2007-08-22 10:57:11 msg/SDBMsg_OPMSG.xml
STDOUT: extracting: -rw-rr 172 2007-08-22 10:57:11 msg/SDBMsg_Optimizer.xml
STDOUT: extracting: -rw-rr 435 2007-08-22 10:57:11 msg/SDBMsg_Query.xml
STDOUT: extracting: -rw-rr 442 2007-08-22 10:57:11 msg/SDBMsg_QueryRewrite.xml
STDOUT: extracting: -rw-rr 3843 2007-08-22 10:57:11 msg/SDBMsg_Recovery.xml
STDOUT: extracting: -rw-rr 5744 2007-08-22 10:57:11 msg/SDBMsg_Rst.xml
STDOUT: extracting: -rw-rr 826 2007-08-22 10:57:11 msg/SDBMsg_RTECKC.xml
STDOUT: extracting: -rw-rr 2472 2007-08-22 10:57:11 msg/SDBMsg_RTEComm.xml
STDOUT: extracting: -rw-rr 2100 2007-08-22 10:57:11 msg/SDBMsg_RTEConf.xml
STDOUT: extracting: -rw-rr 889 2007-08-22 10:57:11 msg/SDBMsg_RTEDBState.xml
STDOUT: extracting: -rw-rr 5001 2007-08-22 10:57:11 msg/SDBMsg_RTEDiag.xml
STDOUT: extracting: -rw-rr 73375 2007-08-22 10:57:11 msg/SDBMsg_RTEIO.xml
STDOUT: extracting: -rw-rr 15680 2007-08-22 10:57:11 msg/SDBMsg_RTEKernel.xml
STDOUT: extracting: -rw-rr 9023 2007-08-22 10:57:11 msg/SDBMsg_RTEMem.xml
STDOUT: extracting: -rw-rr 11450 2007-08-22 10:57:11 msg/SDBMsg_RTESec.xml
STDOUT: extracting: -rw-rr 3696 2007-08-22 10:57:11 msg/SDBMsg_RTESync.xml
STDOUT: extracting: -rw-rr 2287 2007-08-22 10:57:11 msg/SDBMsg_RTESys.xml
STDOUT: extracting: -rw-rr 5248 2007-08-22 10:57:11 msg/SDBMsg_RTETask.xml
STDOUT: extracting: -rw-rr 1124 2007-08-22 10:57:11 msg/SDBMsg_RTEThread.xml
STDOUT: extracting: -rw-rr 16515 2007-08-22 10:57:11 msg/SDBMsg_RunTime.xml
STDOUT: extracting: -rw-rr 1653 2007-08-22 10:57:11 msg/SDBMsg_SAPDBAlgo.xml
STDOUT: extracting: -rw-rr 744 2007-08-22 10:57:11 msg/SDBMsg_SAPDBMem.xml
STDOUT: extracting: -rw-rr 1809 2007-08-22 10:57:11 msg/SDBMsg_Savepoint.xml
STDOUT: extracting: -rw-rr 5909 2007-08-22 10:57:11 msg/SDBMsg_SharedSQL.xml
STDOUT: extracting: -rw-rr 331 2007-08-22 10:57:11 msg/SDBMsg_SQLExecution.xml
STDOUT: extracting: -rw-rr 27488 2007-08-22 10:57:11 msg/SDBMsg_SQLMan.xml
STDOUT: extracting: -rw-rr 10192 2007-08-22 10:57:11 msg/SDBMsg_SrvTasks.xml
STDOUT: extracting: -rw-rr 3874 2007-08-22 10:57:11 msg/SDBMsg_Table.xml
STDOUT: extracting: -rw-rr 1523 2007-08-22 10:57:11 msg/SDBMsg_ToolsCommon.xml
STDOUT: extracting: -rw-rr 1620 2007-08-22 10:57:11 msg/SDBMsg_ToolsCommonDC.xml
STDOUT: extracting: -rw-rr 4031 2007-08-22 10:57:11 msg/SDBMsg_ToolsCommonXML.xml
STDOUT: extracting: -rw-rr 1548 2007-08-22 10:57:11 msg/SDBMsg_Transaction.xml
STDOUT: extracting: -rw-rr 7958 2007-08-22 10:57:11 msg/SDBMsg_ZZZTest.xml
STDOUT: checking unpacked archive... MSG: check file "msg/SDBMsg_RTEKernel.xml": ok
MSG: check file "msg/SDBMsg_Recovery.xml": ok
MSG: check file "msg/SDBMsg_FileDir.xml": ok
MSG: check file "msg/SDBMsg_Rst.xml": ok
MSG: check file "msg/SDBMsg_BTree.xml": ok
MSG: check file "msg/SDBMsg_Converter.xml": ok
MSG: check file "msg/SDBMsg_OMS.xml": ok
MSG: check file "msg/SDBMsg_DBMSrvOI.xml": ok
MSG: check file "msg/SDBMsg_RTESync.xml": ok
MSG: check file "msg/SDBMsg_APO.xml": ok
MSG: check file "msg/SDBMsg_Loader.xml": ok
MSG: check file "msg/SDBMsg_RTEThread.xml": ok
MSG: check file "msg/SDBMsg_ZZZTest.xml": ok
MSG: check file "msg/SDBMsg_DBProc.xml": ok
MSG: check file "msg/SDBMsg_DBProvider.xml": ok
MSG: check file "msg/SDBMsg_ToolsCommonDC.xml": ok
MSG: check file "msg/SDBMsg_ToolsCommonXML.xml": ok
MSG: check file "msg/SDBMsg_Table.xml": ok
MSG: check file "msg/SDBMsg_SAPDBMem.xml": ok
MSG: check file "msg/SDBMsg_RTECKC.xml": ok
MSG: check file "msg/SDBMsg_RTETask.xml": ok
MSG: check file "msg/SDBMsg_DBMSrvBackTemplate.xml": ok
MSG: check file "msg/SDBMsg_RTESys.xml": ok
MSG: check file "msg/SDBMsg_LockManager.xml": ok
MSG: check file "msg/SDBMsg_RunTime.xml": ok
MSG: check file "msg/SDBMsg_KernelCommon.xml": ok
MSG: check file "msg/SDBMsg_RTEIO.xml": ok
MSG: check file "msg/SDBMsg_Transaction.xml": ok
MSG: check file "msg/SDBMsg_RTEMem.xml": ok
MSG: check file "msg/SDBMsg_DBMCLI.xml": ok
MSG: check file "msg/SDBMsg_DBMSrv.xml": ok
MSG: check file "msg/SDBMsg_DBMScd.xml": ok
MSG: check file "msg/SDBMsg_OPMSG.xml": ok
MSG: check file "msg/SDBMsg_RTESec.xml": ok
MSG: check file "msg/SDBMsg_SrvTasks.xml": ok
MSG: check file "msg/SDBMsg_Data.xml": ok
MSG: check file "msg/SDBMsg_QueryRewrite.xml": ok
MSG: check file "msg/SDBMsg_Log.xml": ok
MSG: check file "msg/SDBMsg_AccessPathOptimize.xml": ok
MSG: check file "msg/SDBMsg_DIAGNOSE.xml": ok
MSG: check file "msg/SDBMsg_Index.xml": ok
MSG: check file "msg/SDBMsg_RTEConf.xml": ok
MSG: check file "msg/SDBMsg_DBMLog.xml": ok
MSG: check file "msg/SDBMsg_Admin.xml": ok
MSG: check file "msg/SDBMsg_IOMan.xml": ok
MSG: check file "msg/SDBMsg_Messages.xml": ok
MSG: check file "msg/SDBMsg_DataCache.xml": ok
MSG: check file "msg/SDBMsg_Catalog.xml": ok
MSG: check file "msg/SDBMsg_Query.xml": ok
MSG: check file "msg/SDBMsg_Optimizer.xml": ok
MSG: check file "msg/SDBMsg_RTEComm.xml": ok
MSG: check file "msg/SDBMsg_DBMSrvTest.xml": ok
MSG: check file "msg/SDBMsg_KSQL.xml": ok
MSG: check file "msg/SDBMsg_JoinPathOptimizer.xml": ok
MSG: check file "msg/SDBMsg_SQLExecution.xml": ok
MSG: check file "msg/SDBMsg_LOCKS.xml": ok
MSG: check file "msg/SDBMsg_SAPDBAlgo.xml": ok
MSG: check file "msg/SDBMsg_RTEDiag.xml": ok
MSG: check file "msg/SDBMsg_Backup.xml": ok
MSG: check file "msg/SDBMsg_Savepoint.xml": ok
MSG: check file "msg/SDBMsg_ToolsCommon.xml": ok
MSG: check file "msg/SDBMsg_LiveCache.xml": ok
MSG: check file "msg/SDBMsg_DBMEd.xml": ok
MSG: check file "msg/SDBMsg_MultiVersionRead.xml": ok
MSG: check file "msg/SDBMsg_ObjectContainer.xml": ok
MSG: check file "msg/SDBMsg_SharedSQL.xml": ok
MSG: check file "msg/SDBMsg_RTEDBState.xml": ok
MSG: check file "msg/SDBMsg_SQLMan.xml": ok
MSG: check file "msg/SDBMsg_Join.xml": ok
STDOUT: ok
MSG: packagedata of package Messages changed
MSG: writing 7 packages
MSG: net install registry size = 51568 bytes
MSG: wrote install registry (60562 bytes)
MSG: packagedata of package JDBC changed
MSG: writing 8 packages
MSG: net install registry size = 52039 bytes
MSG: wrote install -
Configure MaxDB with Veritas Netbackup
Hi team,
When i configure Veritas Netbackup with MaxDB I have the following queries:
1. should i create a staging file (will it get created automatically) ?
2. Will all the log, error & History files get created automatically?
3. Should i use PIPES only to take backup? can't i use FILE backup?
please help
Thanks in advance
Regards,
Pradeep Chandru.Hi,
I have made the log files to be generated. Now i am getting the following error:
dbm.prt
2006-09-04 16:07:15 0x00002624 INF 283 DBMSrv command backup_save "test01" DATA RECOVERY
2006-09-04 16:08:22 0x00002624 ERR -24920 DBMSrv ERR_BACKUPOP: backup operation was unsuccessful
0x00002624 ERR -24778 DBMSrv The backup tool failed with 2 as sum of exit codes. The database request was canceled and ended with error -903.
2006-09-04 16:32:50 0x00002624 INF 226 DBMSrv DBM Server client disconnect: PID 7012 on computer xxxxxxxx.local
dbm.ebl
2006-09-04 16:07:49 The database is working on the request.
2006-09-04 16:08:09 The database is working on the request.
2006-09-04 16:08:20 Canceling Utility-task after a timeout of 60 seconds elapsed ... OK.
2006-09-04 16:08: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 :-903
The backup operation has ended.
2006-09-04 16:08:21
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.
2006-09-04 16:08:22
Cleaning up.
Copying output of Backint for MaxDB to this file.
dbm.prt
(established at 2006-09-04 15:31:14): PID 11028 on computer xxxxxxxx.local
2006-09-04 15:31:14 0x000026f8 INF 283 DBMSrv command backup_start BACKt09 DATA
2006-09-04 15:32:20 0x000026f8 ERR -24920 DBMSrv ERR_BACKUPOP: backup operation was unsuccessful
0x000026f8 ERR -24778 DBMSrv The backup tool failed with 2 as sum of exit codes. The database request was canceled and ended with error -903.
2006-09-04 15:32:20 0x000026f8 INF 226 DBMSrv DBM Server client disconnect: PID 11028 on computer xxxxxx.local
2006-09-04 15:32:53 0x00001900 INF 216 DBMSrv DBM Server client connection (established at 2006-09-04 15:32:53): PID 7308 on computer xxxxx.local
2006-09-04 15:32:53 0x00001900 INF 283 DBMSrv command backup_start BACKt09 DATA
2006-09-04 15:33:58 0x00001900 ERR -24920 DBMSrv ERR_BACKUPOP: backup operation was unsuccessful
0x00001900 ERR -24778 DBMSrv The backup tool failed with 2 as sum of exit codes. The database request was canceled and ended with error -903.
2006-09-04 15:33:58 0x00001900 INF 226 DBMSrv DBM Server client disconnect: PID 7308 on computer xxxxxx.local
Incase any logs are required then please let me know. -
RHEL4 Maxdb Online Backup Agent
Hi can anyone recomend a cost effective online backup agent for a RHEL4-Maxdb installation.
What experiences have you had with said scenario wrt HA&DR - How was it configured, what software was used and are there any gotchas...We have been running Netvault's product
called backint for backing up or MAX
DB 7.5.0.29 system within a RedHat 2.1
Enterprise system. We have used this for
the last 3 years and it has been working
very well.
At the time we were setting this up, there
were no other vendors who could directly
backup SAP DB databases along with all of
our other WIN2K and RedHat boxes. If we had to
do it again, we would probably backup the
MAX DB databases to a separate drive array
and then back up that rather than trying to
go directly from the DB to the backup software.
Not sure if this will help because it is so
late but thought I would throw in my 2 cents.
Thanks,
Joe Haynes
Heritage Propane
Helena, Montana -
Error message when starting MaxDB instance
I am getting the following Error message when starting the MaxDB instance after a series of failed attempts at starting the DB Manager Backup for our PI 7.1 server.
"-24994,ERR_RTE: Runtime environment error
1,Cannot create ipc db directories for SID (OS error code 11000)"
Max DB version : 7.7.02
Does anyone have any specific pointers on where the issue could be.
Any help is greatly appreciated.
Regards,
Murali NarayananHi gurus,
I'm a complete newbye searching the forums in order to decrypt what is inconsistent to me (I'm acting as a substitute for a real dba): a sapdb refusing any more connection due to an 'user space exhausted' issue.
I do not even know if/where some admin tool is/isn't installed - eventually, what to look for - onto the running demianapachetomcat framework. Actually, all I have been provided was: 1. call 'Henplus' (done); 2. connect this way (jdbc:sapdb://localhost/database&options) and 3. select, upgrade, delete what needed. Problem arises on point (2): connection resufed 'user space exhausted'.
My question is: this issue seems so similar to mine, how can one eventually check/modify this '/sapdb directory space'?
Thanks in advance for any (much appreciated) hint, and be patient about my English and newbyeness (?).
MaxM -
Steps to empty SAPDB (MaxDB) log file
Hello All,
i am on Redhat Unix Os with NW 7.1 CE and SAPDB as Back end. I am trying to login but my log file is full. Ii want to empty log file but i havn't done any data backup yet. Can anybody guide me how toproceed to handle this problem.
I do have some idea what to do like the steps below
1. take databackup (but i want to skip this step if possible) since this is a QA system and we are not a production company.
2. Take log backup using same methos as data backup but with Log type (am i right or there is somethign else)
3. It will automatically overwrite log after log backups.
or should i use this as an alternative, i found this in note Note 869267 - FAQ: SAP MaxDB LOG area
Can the log area be overwritten cyclically without having to make a log backup?
Yes, the log area can be automatically overwritten without log backups. Use the DBM command
util_execute SET LOG AUTO OVERWRITE ON
to set this status. The behavior of the database corresponds to the DEMO log mode in older versions. With version 7.4.03 and above, this behavior can be set online.
Log backups are not possible after switching on automatic overwrite. Backup history is broken down and flagged by the abbreviation HISTLOST in the backup history (dbm.knl file). The backup history is restarted when you switch off automatic overwrite without log backups using the command
util_execute SET LOG AUTO OVERWRITE OFF
and by creating a complete data backup in the ADMIN or ONLINE status.
Automatic overwrite of the log area without log backups is NOT suitable for production operation. Since no backup history exists for the following changes in the database, you cannot track transactions in the case of recovery.
any reply will be highly appreciated.
Thanks
ManiHello Mani,
1. Please review the document u201CUsing SAP MaxDB X Server Behind a Firewallu201D at MAXDB library
http://maxdb.sap.com/doc/7_7/44/bbddac91407006e10000000a155369/content.htm
u201CTo enable access to X Server (and thus the database) behind a firewall using a client program such as Database Studio, open the necessary ports in your firewall and restrict access to these ports to only those computers that need to access the database.u201D
Is the database server behind a Firewall? If yes, then the Xserver port need to be open. You could restrict access to this port to the computers of your database administrators, for example.
Is "nq2host" the name of the database server? Could you ping to the server "nq2host" from your machine?
2. And if the database server and your PC in the local area NetWork you could start the x_server on the database server & connect to the database using the DB studio on your PC, as you already told by Lars.
See the document u201CNetwork Communicationu201D at
http://maxdb.sap.com/doc/7_7/44/d7c3e72e6338d3e10000000a1553f7/content.htm
Thank you and best regards, Natalia Khlopina -
R3load EXPORT tips for 1,5 TB MAXDB Database are welcome!
Hello to ALL;
this post is addressed to ALL MAXDB-GURU's !!
I'v few questions to MAXDB Performance-Guy's for R3load Export on MAXDB!
(remark to my person:
I'm certified OS/DB migration consultant and have already done over 500 OS/DB migrations since 1995 successfully)
BUT now I'm face with following setup for Export:
HP- IA64 BL870c, 4 CPUu2019s Dual-Core + Hyperthreading activ (mean's 16 "CPU'S" shown via top or glance)
64 GB RAM, HPUX V11.31;
MAXDB 7.7.07
ECC 5.0; Basis/Aba 640.22
SAP-Kernel 640-Unicode Patch 381
8 sapdatas are configured on unique 200GB LUN's and VG's in HP-UX; on storage-side the 8 220GB LUN's are located on (only) 9 300GB-Disks with Raid-5 Level and within HP-UX each VG/LVOL is mirrored via LVM to a second desasterdatacenter (200m distance)
LOGFILES:
2 x 4 GB LUN Raid-1 on Storage and via LVM also mirrored to failover-center
MAXDB-Datasize: 1600 GB Overall and within this 1350 GB used, TEMPUsage about 25 GB !
MAXDB-Parameter-Settings
MAXCPUu2019s 10 (4 x IA64 QuadCore+Hyperthreading shows 16 Cores within top and galcne
Cache_SIZE= I/O Buffer Cache = 16 GB (2.000.000 Pages)
Data-Cache-HitRatio: 99.61%
Undo-Cache = 99,98%
the following sapnote for MAXDB Peformance and Migrations are well known and already processes
928037, 1077887, 1385089, 1327874, 954268, 1464560, 869267,
My major problem is the export-runtime with over 4 days on the first dry-run (6 R3load's running on Linux-APPL-Server), and 46h on second runtime, 6 R3loads running on DB-Server IA64)
the third trail-run was aborted by me after 48hours and 50% export-dump-space was written. In all 3 dry-runs, no more than approx 3.5GB DUMP-Space were written per hour!
My first question to all MAXDB-Guru'S: How can I influence/optimize the TEMP - Area in MAXDB?? I didn't find any hint's in SDN or SAPNOTES or MaxDB Wiki or google....As fare as I know, this TEMP area "resides" within MAXDB-datafiles, thus it's seperated on my 48 datafiles, spreaded over 8 LUN/VG/disks. But I see LESS throughput on disk's and MAXDB-Kernel uses only ONE of ten's cpu-cores (approx 80% - 120% of 1000%).
The throughput or cpu-usage doesn't change when I use 2 or 4 or 10 or 16 R3load' processes in parallel. The "result" is always the same: approx. 3,5 GB Export-Dump and 1 CPU MAX-DB Kernelprocess is used !
so the BIG Question for me: WHERE is the bottleneck ?? (RAID-5 Disk-LUNS mirrored with LVM ???)
on HP-UX scsi_queue_depth_length I'v increased default value from 8 to 32 to 64 to 128 --> no impact
2nd question:
I'v read OS-Note 1327874 - FAQ: SAP MaxDB Read Ahead/Prefetch, and we are running MAXDB 7.7.07.19! (MaxDB 7.8 is not suppored via PAM for IA64 640-UC-Kernel) and as far as I understood, this parameter will no HELP me on EXPORT with primary-key-sequence ! is this correct? THUS: which parameter HELPS for speeding up Export-Runtime?
MAXCPU is set to 10, but ONLY 1 of them is used??
so this post is for ALL MAXDB GURU'S!
who will be intrested to contriubte on this "high-sophisticated" migration-project with 1.5TB MAXDB-Database-size and ONLY 24h Downtime !!
all tips and hints are welcome and I will give us coninued updates to this running project until WE did a successfull migration job.
PS: Import is not yet started, but should be done within vSphere 5 and SLES 11 SP1 on MAXDB 7.8 ....and of yours in parallel to export with migration monitor, BUT again a challenge: 200km distance from source to traget system !!!
NICE PROJECT;
best regards AlfredHi Alfred,
nice project ... just some simple questions:
Did you open a message at SAP? Maybe you could buy some upgrade support, this could be usefull to get direct access to the SAP support...
Which byte order do you use? I know Itanium could use both. But it should be different, otherwise you would use a backup for the migration.
And the worst question, I do not even want to ask: What about your MAXCPUS parameter? Is it set to more than 1? This could be the problem why only one CPU is used.
Best regards
Christian
Maybe you are looking for
-
Lumia 720 amber update not available
I am using Lumia 720.In Nokia support site it's showing update is available but when I try to update it's showing phone is up-to-date.I bought my phone from UAE and am now in India.plz help. Solved! Go to Solution.
-
How do I add numbers to contact groups I've created
Ive created a list of sub-groups for my fairly extensive contact list, but I can't figure out how to add contacts to these subgroups without having to re-enter the contact info as a "new contact". Is it possible to select from my "All Contacts" lis
-
I am working on forms 6i ,I have one application that containts a menu module, once the user click on menu item it will direct him to a specific screen. all screen are working accept two menu items ,once I click on one of them i am getting the follow
-
Doubleclick on file doesn't open related application
This has happend with a few applications...for example, Photoshop. Double clicking on a file that would normally open in photoshop results in nothing happening. I've also tried click and dragging to the application in the dock..nothing happens. Only
-
Where download Oracle Business Inteligence Suite Enterprise Edition plus?
Where I can found link for download Oracle Business Inteligence Suite Enterprise Edition plus? Gordan