cancel
Showing results for 
Search instead for 
Did you mean: 

"sql error -903 Host file I/O error" during MaxDB Backup

Former Member
0 Kudos
1,693

we are using MaxDB 7.5 with R/3 46C on Win 2003 64bit . We try to execute

a full backup of the maxdb .

We schedule the backup via at command using this command:

dbmcli -d ABC -u control,control -uUTL -c backup_start full_backup

THe backup starts but after some hours, after about 40GB have been

saved we receive this error:

"sql error -903,Host file I/O error"

We did more attempts but the backup is always interrupted after about 40 GB of data saved. The abend occurs always after about 3h from the start.

We didn't find any Oss Note for this error.

Regards

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi Roberto,

You need to define a medium for the backup to take place. If it did not find any medium how can it will backup. so define a medium through DBM GUI or dbmcli and then fire the backup.

Medium: ANYNAME

location: D:\ANYFOLDER

Regards

Prashant

Former Member
0 Kudos

Hi Roberto,

may be Data Cache parameter problem .Please check once .

Thanks & Regards,

Ramarao.A

Former Member
0 Kudos

Addendum.

Into the knldiag.err file there are these informations.

0x1C0 ERR 18206 IO Could not write to 'f:\backup\sapbck', rc = 33

0xCEC ERR 52012 SAVE error occured, basis_err 3700

0xCEC ERR 52012 SAVE error occured, basis_err 5750

0xCEC ERR 52012 SAVE error occured, basis_err 5750

0x434 ERR 18206 IO Could not write to 'f:\backup\sapbck', rc = 1450

0xCEC ERR 52012 SAVE error occured, basis_err 3700

0xC90 ERR 18206 IO Could not write to 'f:\backup\sapbck', rc = 1450

0xCEC ERR 52012 SAVE error occured, basis_err 3700

0x1890 ERR 18206 IO Could not write to 'f:\backup\sapbck', rc = 1450

0xCEC ERR 52012 SAVE error occured, basis_err 3700

0x17A4 ERR 18206 IO Could not write to 'f:\backup\sapbck', rc = 33

What these rc means ?

regards

0 Kudos

Hello Roberto,

the operatings system error codes 33 and 1450 have this meaning

Errortext for errorcode 33:

'The process cannot access the file because another process has locked a portion of the file.'

Errortext for errorcode 1450:

'Insufficient system resources exist to complete the requested service.'

Maybe there are also some entries in the windows event log.

Best regards

Bernd

Melanie
Advisor
Advisor
0 Kudos

Hi Roberto,

these are Windows return codes.

They mean:

Errortext for errorcode 33:

'The process cannot access the file because another process has locked a portion

of the file.'

Errortext for errorcode 1450:

'Insufficient system resources exist to complete the requested service.'

(Please also have a look at: https://wiki.sdn.sap.com/wiki/x/LDU).

I don't know how rc 33 is involved in this, but you should check note 855562 concerning rc 1450.

Regards,

Melanie

Former Member
0 Kudos

Hi

please how I can check eventually the "Data Cache parameter problem " ??

regards

Former Member
0 Kudos

Hi Melany

sorry so if I understand well the solution is to change the regedit key of the Windows server as indicated into the windows bulletin http://support.microsoft.com/kb/304101 ?

regards

Melanie
Advisor
Advisor
0 Kudos

Hi Roberto,

I have never tried these registry changes.

I'd go for the solution mentioned in the note:

Generally, the error occurs only if the 3 GB option is active in the

boot.ini file.

The workaround implemented as of Version 7.5.00 Build 29 cannot always

ensure that the error will no longer occur. <b>To make more internal

administration memory available on the operating system, you should use

the additional option /USERVA to limit the 3 GB option.</b> For more

information, see Note 990538.

Regards,

Melanie

Former Member
0 Kudos

Hi Melany,

we added the /USERVA=2600 parameter to the boot.ini, restarted the server but the backup continue to fails with the same error.

Please , any other idea ?

Melanie
Advisor
Advisor
0 Kudos

Hello Roberto,

this is a limit of the 32bit OS. We can only work around this limit.

Try to set the parameter to a lower value or deactivate the 3 GB option. Of course you have to adapt the database parameters then accordingly that the database does not use more than 2 GB of memory...

You could also ask Microsoft about the options you have.

Another option would be to switch to 64bit...

Regards,

Melanie

Former Member
0 Kudos

THanks for the feedback.

The problem is that the server is already a 64 bit platform. It uses the Win 2003 64 bit x64 operating systems.

Please could you be more precise when you says to limiti deactivate the 3GB option or to adapt the DB parameters ?

Which parameters sould be better to change and how ?

regards

Melanie
Advisor
Advisor
0 Kudos

Hello Roberto,

as you are already using a 64bit platform, I'd like to ask you to open a OSS message for the problem. Then SAP support can analyse this in detail. Most probably we need to logon to your system and check the configuration and all log files.

Thanks,

Melanie