Sybase Log issue

[Former Member]

Hi,

We are facing issue where every time log is getting full and sybase db is not allowing to launch BODS.

If Admin is dumping the log it started working but whenever some error is coming while loading 3-4 millions records again it used to crash with below error:

Can't allocate space for object 'syslogs' in database 'authcenter' because the 'logsegment' segment is full. If you ran out of space in syslogs, dump the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to increase the size of the segment.

What is the standard size admin should use,does it related to Bulk load option?.

Thanks

[jayrijnbergen · Accepted solution]

There's no standard size for log space, it all depends on your applications

If you have to load a lot of data, database option "select into/bulkocopy" can be very useful.

With this option enabled, it's possible to load data much faster. Reason for that is less logging.

Often this database option is combined with "trunc log on chkpt", which automatically frees logspace after the transaction has committed.

Note when using these options it's not possible to make transaction log backups. In case you need to restore, only a full database backup can be restored.

Also try looking at your batch processes. Maybe it's possible to process data in smaller batches (not 4 million records in 1 transaction, but for example using a batch size of 25000 records). This makes it easier to truncate the log, and is also faster for recovery in case something happens.

If you can't change any of these things, you can also extend the log of the database.

[former_member187605]

You might get "better" feedback when posting in or in

[Former Member]

Thanks Dirk