- SAP Community
- Products and Technology
- Technology
- Technology Q&A
- How to decode or interpret error message ?
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
How to decode or interpret error message ?
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 04-07-2009 8:45 PM
Currently I am troubleshooting some issues with Veritas NetBackup and MaxDB.
I have successfully set this up several times in the past with MaxDB 7.5 and NetBackup 5.1
Now however I must use NetBackup 6.0 and am running into problems.
One thing that might be helpful is to understand this error message from dbm.ebp
========
Have encountered error -24920:
The backup tool failed with -1073741819 as sum of exit codes. The database request was canceled and ended with error -903.
========
The -24920 and -903 errors seem to be fairly generic.
How do I interpret what -1073741819 means?
I have spent a fair bit of time searching for some way to interpret this code, but haven't found anything too useful.
I have been working with NetBackup support on this as well, but haven't really made any progress.
- SAP Managed Tags:
- SAP MaxDB
Accepted Solutions (0)
Answers (3)
Answers (3)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
The problem has been fixed.
The 5.1 version of Veritas NetBackup could not backup directly to pipes.
It required using 2 versions of backint to use a pipe based backup.
The 6.0 version can now directly use pipes.
Though the process is explained in the 6.0 docs, the difference from previous versions is not explained.
After an engineer at Veritas explained the new use of Pipes, I re-read the 6.0 docs (again) and realized my mistake.
The bsi.env file (backint.conf in our case), had to be changed from this:
BACKINT D:\sapdb\aps\db\bin\backint.exe
INPUT D:\sapdb\APS\db\backups\io\backint.input
OUTPUT D:\sapdb\APS\db\backups\io\backint.output
ERROROUTPUT D:\sapdb\APS\db\backups\logs\backint.err
PARAMETERFILE D:\sapdb\APS\db\backups\backint.parm
To This:
BACKINT C:\VERITAS\NetBackup\bin\backint.exe
INPUT D:\sapdb\APS\db\backups\io\backint.input
OUTPUT D:\sapdb\APS\db\backups\io\backint.output
ERROROUTPUT D:\sapdb\APS\db\backups\logs\backint.err
PARAMETERFILE D:\sapdb\APS\db\backups\SAP_backint_maxdb.utl
Notice that in the old bsi.env file that the BACKINT parameter points to the MaxDB version of backint, and the PARAMETERFILE parameter points to the parameter file used to setup the NBU version of backint
(actually the backint for oracle)
For 6.0 the BACKINT parameter of the bsi.env file needs to point to the NBU version of backint.
The PARAMETER file now points directly to the file that used to be specified by the PARAMETERFILE OF BACKINT: parameter that was in the file previously pointed to by PARAMETERFILE in 5.1
If that seems confusing, well, it is.
The 6.0 method is simpler, and faster.
But, I still don't know how to decode the error message I originally asked about.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hello,
1. "VERITAS NetBackup 6.0 for SAP" document available at
ftp://exftpp.symantec.com/pub/support/products/NetBackup_Enterprise_Server/279282.pdf
< Please contact http://support.veritas.com >
2. Please see "Connecting to VERITAS NetBackup" section at Documentation of SAP MaxDB Database
http://maxdb.sap.com/doc/7_7/default.htm
Using the Backint for Oracle Interface, SAP MaxDB can connect to VERITAS NetBackup (from VERITAS) in order to back up, restore, import, and export data.
After the database upgrade to the version higher as 7.5.00.47 you should be able to use your old configuration files.
3. "The backup tool failed with -1073741819 as sum of exit codes."
If an external backup tool called by the DBM Server is returning NOT integer OS RC, for example, on Windows server it could be like 0xC0000005 as return code, this is currently converted by the DBM Server into a signed integer (e.g. -1073741819).
It's planning to take in acount in the new database versions.
Thank you and best regards, Natalia Khlopina
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hello Jared,
-> What is the database version? Please also post the build number.
< 'xinstinfo <SID>' >
Could be the already know issue -> PTS 1150786 < www.sapdb.org/webpts >.
Additional information needed to get clear on this issue.
-> Are you SAP customer?
-> Please check dbmsrv_<server>.err file located in <IndepDataPath>/wrk.
Did you see that DBMServer crashed during the execution of the archive_stage command or when saving using the NetWorker?
-> Please post mere details from dbm.ebp file.
-> Are you running the database on a 64bit Windows platform with x86 architecture (W64/AMD64)?
Thank you & best regards, Natalia Khlopina
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Sorry for the poor formatting - I don't know how to fix it on this forum.
-> What is the database version? Please also post the build number.
version 7.5.0.035
Build # 035-123-123-944
> Could be the already know issue -> PTS 1150786 < www.sapdb.org/webpts >.
I will look for that
-> Are you SAP customer?
Yes
-> Please check dbmsrv_.err file located in /wrk.
Did you see that DBMServer crashed during the execution of the archive_stage command or when saving using the NetWorker?
It doesn't appear that the backint for SAP even gets executed
-> Please post mere details from dbm.ebp file.
dbm.ebp appears below
-> Are you running the database on a 64bit Windows platform with x86 architecture (W64/AMD64)?
64bit x64
========== dbm.ebp ================
2009-04-07 12:25:29
Using environment variable 'TEMP' with value 'C:\WINDOWS\TEMP' as directory for temporary files and pipes.
Using connection to Backint for MaxDB Interface.
2009-04-07 12:25:29
Checking existence and configuration of Backint for MaxDB.
Using environment variable 'BSI_ENV' with value 'D:\sapdb\APS\db\backups\backint.conf' as path of the configuration file of Backint for MaxDB.
Reading the Backint for MaxDB configuration file 'D:\sapdb\APS\db\backups\backint.conf'.
Found keyword 'BACKINT' with value 'D:\sapdb\aps\db\bin\backint.exe'.
Found keyword 'INPUT' with value 'D:\sapdb\APS\db\backups\io\backint.input'.
Found keyword 'OUTPUT' with value 'D:\sapdb\APS\db\backups\io\backint.output'.
Found keyword 'ERROROUTPUT' with value 'D:\sapdb\APS\db\backups\logs\backint.err'.
Found keyword 'PARAMETERFILE' with value 'D:\sapdb\APS\db\backups\backint.parm'.
Finished reading of the Backint for MaxDB configuration file.
Using 'D:\sapdb\aps\db\bin\backint.exe' as Backint for MaxDB program.
Using 'D:\sapdb\APS\db\backups\io\backint.input' as input file for Backint for MaxDB.
Using 'D:\sapdb\APS\db\backups\io\backint.output' as output file for Backint for MaxDB.
Using 'D:\sapdb\APS\db\backups\logs\backint.err' as error output file for Backint for MaxDB.
Using 'D:\sapdb\APS\db\backups\backint.parm' 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 'd:\sapdb\data\wrk\APS\dbm.knl' as backup history of a database to migrate.
Using 'd:\sapdb\data\wrk\APS\dbm.ebf' as external backup history of a database to migrate.
Checking availability of backups using backint's inquire function.
Check passed successful.
2009-04-07 12:25:29
Checking medium.
Check passed successfully.
2009-04-07 12:25:29
Preparing backup.
Setting environment variable 'BI_CALLER' to value 'DBMSRV'.
Setting environment variable 'BI_REQUEST' to value 'NEW'.
Setting environment variable 'BI_BACKUP' to value 'FULL'.
Constructed Backint for MaxDB call 'D:\sapdb\aps\db\bin\backint.exe -u APS -f backup -t file -p D:\sapdb\APS\db\backups\backint.parm -i D:\sapdb\APS\db\backups\io\backint.input -c'.
Created temporary file 'D:\sapdb\APS\db\backups\io\backint.output' as output for Backint for MaxDB.
Created temporary file 'D:\sapdb\APS\db\backups\logs\backint.err' as error output for Backint for MaxDB.
Writing '
.\pipe\APS #PIPE' to the input file.
Prepare passed successfully.
2009-04-07 12:25:29
Starting database action for the backup.
Requesting 'SAVE DATA QUICK TO '
.\pipe\APS' PIPE NO CHECKPOINT MEDIANAME 'BACKAPSFULL'' from db-kernel.
The database is working on the request.
2009-04-07 12:25:29
Waiting until database has prepared the backup.
Asking for state of database.
2009-04-07 12:25:29 Database is still preparing the backup.
Waiting 1 second ... Done.
Asking for state of database.
2009-04-07 12:25:30 Database has finished preparation of the backup.
The database has prepared the backup successfully.
2009-04-07 12:25:30
Starting Backint for MaxDB.
Starting Backint for MaxDB process 'D:\sapdb\aps\db\bin\backint.exe -u APS -f backup -t file -p D:\sapdb\APS\db\backups\backint.parm -i D:\sapdb\APS\db\backups\io\backint.input -c >>D:\sapdb\APS\db\backups\io\backint.output 2>>D:\sapdb\APS\db\backups\logs\backint.err'.
Process was started successfully.
Backint for MaxDB has been started successfully.
2009-04-07 12:25:30
Waiting for end of the backup operation.
2009-04-07 12:25:30 The backup tool is running.
2009-04-07 12:25:30 The database is working on the request.
2009-04-07 12:25:32 The backup tool process has finished work with return code -1073741819.
2009-04-07 12:25:35 The database is working on the request.
2009-04-07 12:25:45 The database is working on the request.
2009-04-07 12:26:00 The database is working on the request.
2009-04-07 12:26:20 The database is working on the request.
2009-04-07 12:26:33 Canceling Utility-task after a timeout of 60 seconds elapsed ... OK.
2009-04-07 12:26:34 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-04-07 12:26:34
Filling reply buffer.
Have encountered error -24920:
The backup tool failed with -1073741819 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 -1073741819 as sum of exit codes. The database request was canceled and ended with error -903.
Reply buffer filled.
2009-04-07 12:26:34
Cleaning up.
Copying output of Backint for MaxDB to this file.
-
Begin of output of Backint for MaxDB (D:\sapdb\APS\db\backups\io\backint.output)----
Reading parameter file D:\sapdb\APS\db\backups\backint.parm.
Using C:\VERITAS\NetBackup\bin\backint.exe as Backint for Oracle.
Using D:\sapdb\APS\db\backups\SAP_backint_maxdb.utl as parameterfile of Backint for Oracle.
Using D:\sapdb\APS\db\backups\logs\SAP_backinthistorymaxdb.log as history file.
Using D:\sapdb\APS\db\backups\io\SAP_backintmaxdb.input as input of Backint for Oracle.
Using D:\sapdb\APS\db\backups\io\SAP_backintmaxdb.output as output of Backint for Oracle.
Using D:\sapdb\APS\db\backups\logs\SAP_backintmaxdb.err as error output of Backint for Oracle.
-
End of output of Backint for MaxDB (D:\sapdb\APS\db\backups\io\backint.output)----
Removed Backint for MaxDB's temporary output file 'D:\sapdb\APS\db\backups\io\backint.output'.
Copying error output of Backint for MaxDB to this file.
-
Begin of error output of Backint for MaxDB (D:\sapdb\APS\db\backups\logs\backint.err)----
-
End of error output of Backint for MaxDB (D:\sapdb\APS\db\backups\logs\backint.err)----
Removed Backint for MaxDB's temporary error output file 'D:\sapdb\APS\db\backups\logs\backint.err'.
Removed the Backint for MaxDB input file 'D:\sapdb\APS\db\backups\io\backint.input'.
Have finished clean up successfully.
Edited by: Jared Still on Apr 8, 2009 5:31 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
-> What is the database version? Please also post the build number.
version 7.5.0.035
Build # 035-123-123-944
> Could be the already know issue -> PTS 1150786 < www.sapdb.org/webpts >.
I will look for that
-> Are you SAP customer?
Yes
-> Please check dbmsrv_.err file located in /wrk.
Did you see that DBMServer crashed during the execution of the archive_stage command or when saving using the NetWorker?
It doesn't appear that the backint for SAP even gets executed
-> Please post mere details from dbm.ebp file.
I tried using the code tags for formatting - didn't help.
See this url for dbm.ebp output [http://jaredstill.com/dbm_ebp.html]
-> Are you running the database on a 64bit Windows platform with x86 architecture (W64/AMD64)?
64bit x64
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
There is a .prt file, but not a .err file.
Here are the latest entries in it, from last week.
I had the wrong password at the time.
0x000009ec ERR -24965 DBM 1,Logon failure: unknown user name or bad password.
2009-03-30 11:50:08 0x00000c3c 0 DBM command user_system
2009-03-30 11:50:08 0x00000c3c ERR -24965 DBM ERR_SYSLOGON: logon to system failed
0x00000c3c ERR -24965 DBM 1,Logon failure: unknown user name or bad password.
2009-03-30 11:50:35 0x00000ab0 0 DBM command user_system
2009-03-30 11:50:35 0x00000ab0 ERR -24965 DBM ERR_SYSLOGON: logon to system failed
0x00000ab0 ERR -24965 DBM 1,Logon failure: unknown user name or bad password.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
backint.parm:
BACKINT D:\sapdb\aps\db\bin\backint.exe
PARAMETERFILE OF BACKINT: D:\sapdb\APS\db\backups\SAP_backint_maxdb.utl
HISTORY FILE: D:\sapdb\APS\db\backups\logs\SAP_backinthistorymaxdb.log
INPUTFILE FOR BACKINT: D:\sapdb\APS\db\backups\io\SAP_backintmaxdb.input
OUTPUTFILE FOR BACKINT: D:\sapdb\APS\db\backups\io\SAP_backintmaxdb.output
ERRORFILE FOR BACKINT: D:\sapdb\APS\db\backups\logs\SAP_backintmaxdb.err
STAGING AREA: D:\sapdb\APS\db\backups\stage\stage1 4 GB
I've been over this a few times, and am sure it is setup correctly.
This isn't the first instance of setting this up here.
We have 3 other LiveCache servers where this all works.
I carefully documented the setup procedures, and tested them.
The difference is that this new server (and one other ) is x64.
The old servers are itanium, using the NetBackup 5.1 MP5 client.
The x64 servers required using NetBackup 6.0 MP7 clients rather than NBU 5.1 MP5.
I would use the 5.1 client, but it is not available on x64 Windows.
When initially setting this up on the first servers, I documented patch levels of the 5.1 client that didn't work.
I don't know if I am running into a similar problem here or not.
Hence that is the reason I am trying to decode the error message being returned.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hello,
From dbm.ebp:
"
2009-04-07 12:25:29
Starting database action for the backup.
Requesting 'SAVE DATA QUICK TO '
.\pipe\APS' PIPE NO CHECKPOINT MEDIANAME 'BACKAPSFULL'' from db-kernel.
The database is working on the request.
"
"
2009-04-07 12:25:30
Starting Backint for MaxDB.
Starting Backint for MaxDB process 'D:\sapdb\aps\db\bin\backint.exe -u APS -f backup -t file -p D:\sapdb\APS\db\backups\backint.parm -i D:\sapdb\APS\db\backups\io\backint.input -c >>D:\sapdb\APS\db\backups\io\backint.output 2>>D:\sapdb\APS\db\backups\logs\backint.err'.
Process was started successfully.
Backint for MaxDB has been started successfully.
u2026.
2009-04-07 12:25:30
Waiting for end of the backup operation.
2009-04-07 12:25:30 The backup tool is running.
2009-04-07 12:25:30 The database is working on the request.
2009-04-07 12:25:32 The backup tool process has finished work with return code -1073741819.
u2026
"
As "MaxDB's own Backint for MaxDB is used and more than 2147483647 bytes were backed up through one pipe. " + the database is running on 64bit Windows and a x86 architecture =>
Could be the already know issue -> PTS 1150786 < www.sapdb.org/webpts >.
***
As you are SAP customer, please let me know if you created OSS ticket where this issue was reported.
Thank you and best regards, Natalia Khlopina
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
>
> "
> As "MaxDB's own Backint for MaxDB is used and more than 2147483647 bytes were backed up through one pipe. " + the database is running on 64bit Windows and a x86 architecture =>
> Could be the already know issue -> PTS 1150786 < www.sapdb.org/webpts >.
>
> ***
>
> As you are SAP customer, please let me know if you created OSS ticket where this issue was reported.
>
> Thank you and best regards, Natalia Khlopina
I did try looking up PTS 11500786 on the website you show, but did not get any results.
Currently I have requested escalation with Veritas on this ticket.
If I don't get anywhere, I will open an OSS ticket, though I think the problem is with NetBackup.
Thanks,
Jared Still
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
-> Advanced Search ->
Number 1150786
-> Search
-> Result
(Displaying 1 of 1 Message)
Please let me know if you still have problems to display PTS.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
>
> -> Advanced Search ->
> Number 1150786
> -> Search
> -> Result
> (Displaying 1 of 1 Message)
>
> Please let me know if you still have problems to display PTS.
Interesting.
Before today I had tried the Advanced Search, and it didn't work.
That is, the advanced search page did not appear.
Today, it is working and I can read the document.
Thanks for your help.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
> The -24920 and -903 errors seem to be fairly generic.
I'd check in knldiag and/or knldiag.err
Markus
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- How to host static webpages through SAP CPI-Iflow in Technology Blogs by Members
- Integration Suite Groovy Script. Getting Destination Service Token in Technology Q&A
- Object Store on SAP BTP | Setting up instance sharing on Object Store in Technology Blogs by SAP
- PGP Encryption/Decryption using Java code inside payload in Technology Blogs by Members
- Fiori launchpad integrated GPT assistant: Middleware in Technology Blogs by Members
| User | Count |
|---|---|
| 86 | |
| 10 | |
| 10 | |
| 9 | |
| 7 | |
| 7 | |
| 6 | |
| 5 | |
| 4 | |
| 4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.