Hi, "d0_aopen Error during fork" can be caused by a resource limit (semaphore, cache, processes). This will hit you during backup since the backup thread (or clone process on Linux) is started on demand while all other threads for I/O or SQL processing have been startet with kernel start. It was designed that way due to the relativ short lifetime of such a backup thread. The misleading error message 'Interrupted system call' is a known bug, which has been fixed at least in 7.3.0.40. CU jrg
> -----Original Message----- > From: Jerome Seubert [mailto:[EMAIL PROTECTED] > Sent: Donnerstag, 20. November 2003 13:38 > To: [EMAIL PROTECTED] > Subject: -903,Host file I/O error > > > Hello, > > I am using SAP DB 7.3 Build 28 under SuSE Linux Enterprise > Server 8 and > having a problem with the backup. After installing and loading the > database, I first defined the backup media and afterwards performed a > complete backup in mode cold. Then afterwards I activated > automated log > backups. Both worked fine so far. > > Now, I wanted to perform another complete backup, this time > in mode warm, > using the same command as before: > > dbmcli -d I04 -u control,control -uUTL -c backup_start completeF > > but this time it failed with the following error: > > ERR > -24988,ERR_SQL: sql error > -903,Host file I/O error > > Additional information from the knldiag.err is > > 2003-11-20 11:04:25 3766 ERR 11000 d0_aopen Error during fork, > Interrupted system call > 2003-11-20 11:04:26 3770 ERR 52012 SAVE error occured, > basis_err 3700 > > After that, I tried to perform the backup in mode cold but got the > following error: > > ERR > -24988,ERR_SQL: sql error > -903,Message not available > > knldiag.err: > > 2003-11-20 11:20:36 5181 ERR 11000 d0_aopen Error during fork, > Interrupted system call > 2003-11-20 11:20:36 5185 ERR 52012 SAVE error occured, > basis_err 3700 > 2003-11-20 11:20:37 5185 ERR 53017 I/O SYSDEV DEVNO: 1 > 2003-11-20 11:20:37 5185 ERR 53016 I/O /sapdb/I04/dbsys/SYS > > > What is the cause of the problem? Is there a way to fix this? > > Regards > > J. Seubert > -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
