Skip to Content
Jun 10, 2014 at 06:32 PM

System Crash after transactional log filled filesystem


Dear gurus,

We have an issue in our PRD system under FlexFrame platform. We SAP NW 7.4 (SP03) with ASE (SuSe SLES 11 SP1) running as BW system.

While uploading data from ERP system, the transactional log was filled. We can see in <SID>.log:

Can't allocate space for object 'syslogs' in database '<SID>' because 'logsegment' segment is full/has no free extents. If you ran out of space in syslogs, dump the transaction log. Otherwise, use ALTER DATABASE to increase the size of the segment.

After this, we increase the transactional log (disk resize). Then, executed ALTER DATABASE <SID> log on <LOGDEVICE> = '<size>'

While ALTER is running the log filesystem was filled (100%), after this, <SID>.log began to grow tremendously.

We stopped Sybase and now, when we try start it all FF node will be down. The filesystem has free space (around 10 GB)

Could you help us?

Add: We think that a posible solution could be to delete the transactional log due to the fact that we understand that the failure is related to this log (maybe corrupted?)