7.5.0-B019: more ressources needed? [was: RE: -903,Host file I/O error]

> 2004-11-14 04:36:07  1131 ERR 11000 d0_aopen Error during 
> thread creation, resource limit.
> 2004-11-14 04:36:07  1225 ERR 52012 SAVE     error occured, 
> basis_err 3700

We have exactly the same error since the update to 7.5.0-B019, Build 18
worked fine with our current configuration.

Additionally the DB didn't even come up after upgrading to build 19:

2004-11-19 18:07:17    61 ERR 11000 d0_vatta Error during fork, resource
limit.
2004-11-19 18:07:17   165 ERR 11000 vattach  dev0_vattach returned FALSE
2004-11-19 18:07:17   165 ERR    14 IOMan    Attach error on Data volume 1:
Could not create volume
2004-11-19 18:07:17   165 ERR    15 Admin    RestartFilesystem failed with
'I/O error'
2004-11-19 18:07:17   165 ERR     8 Admin    ERROR 'disk_not_accessibl'
CAUSED EMERGENCY SHUTDOWN


I had to reduce CACHE_SIZE and MAXUSERTRASKS in order to get the DB up and
running again. We decreased the CACHE_SIZE from 170000 to 150000 and the
MAXUSERTASKS from 180 to 160. Then the db came up but our backup is still
not running so we have to go even lower with the CACHE_SIZE.

There was something fundamentally changed between Build 18 and 19 so that
the higher memory requirement will reach the system imposed 32bit limit.

The currently used resident memory is (according to top): 1471.376 we had ~
1.8 GB before.

Maybe someone of the dev team can explain what's happening here...


Greetz,

SIEGENIA-AUBI KG
Informationswesen
 
i.A.
 
Markus Döhr
SAP-CC/BC, SAPDB-DBA

Tel.:    +49 6503 917-152
Fax:     +49 6503 917-7152
E-Mail: markus.doehr@xxxxxxxxxxxxxxxxx
Internet: http://www.siegenia-aubi.com 
  

--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe:    http://lists.mysql.com/maxdb?unsub=gcdm-maxdb@xxxxxxxxxxx