S
Stefan Marquardt
Guest
"So *every* time you use increaseto and set -B to 200000 the DB goes down at any time this is performed." Yes, i can reproduce it. [2014/10/17@15:26:09.802+0200] P-43912 T-94968 I Usr 11: (13980) Increase Params increasing buffer pools size (-B) from 50000 to 200000. [2014/10/17@15:26:10.584+0200] P-43912 T-94968 I Usr 11: (453) Logout by Increase Params on CON:. [2014/10/17@15:26:50.347+0200] P-17928 T-72648 I PROMON 11: (-----) Login by smq_adm. [2014/10/17@15:35:12.167+0200] P-87512 T-55664 I ABL 10: (14676) bkioRead:Unknown O/S error during Read, errno 2, fd 788, len 8192, offset 225599, file C:\ProgramData\Progress\eNora\winsurede\sure_db\winsure_13.d1 database ..\sure_db\winsure. (9451) [2014/10/17@15:35:12.176+0200] P-87512 T-55664 I ABL 10: (9450) bkioRead:Insufficient disk space during Read, fd 788, len 8192, offset 225599, file C:\ProgramData\Progress\eNora\winsurede\sure_db\winsure_13.d1. I know that there are 32bit limits but I can understand why 1.) increaseto work return without error 2.) the error happend later (depends on data-io!!), one time it was the next day when worktime began 3.) the error message is not "memory problems", it says: unkonw error accessng a special file Every poor admin would think that he has a terrible OS filesystem error. BTW: promon showed 1701 MB shared memory
Continue reading...
Continue reading...