cancel
Showing results for 
Search instead for 
Did you mean: 

ASE Error SQL1105 - Can't allocate space for object 'syslogs' in database 'saptools' because 'logsegment' segment is full/has no free extents

Former Member
0 Kudos

Hi All,

We are getting below error in our Production System frequently.

ASE Error SQL1105][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Can't allocate space for object 'syslogs' in database 'saptools' 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.

When ever the above issue is occurring THEN we are adding the space to saptools database and the related file system (/sybase/GTT/sapdiag) & it is running out of space now.

FYI.

We have not enabled the Transaction Log backup as we have space issues. Please advice for the permanent solution.

Regards,

Karthik

Accepted Solutions (0)

Answers (3)

Answers (3)

christoph_heimann
Participant
0 Kudos

Hi Karthik,

Can you please provide the output of the following command:


sp_helpdb saptools

This will show us the assigned database options for database saptools.

Best regards

Christoph

Johan_sapbasis
Active Contributor
0 Kudos

Hi Karthik,

Victoria is correct.

Please check all the following notes:

1585981 - SYB Ensuring Recoverability for SAP ASE

1588316 - SYB Configure automatic database and log backups

1611715 - SYB How to restore an SAP ASE database server (Windows)

1618817  SYB How to restore a Sybase ASE database server (UNIX)

And if you want to configure threshold archiving please check the following, the below ties in with note 1588316

1801984 - SYB: Automated management of long running transactions

Kind Regards,

Johan

victoria_normand
Contributor
0 Kudos

Hi Karthik,
The best and expected to ensure the recoverability of the entire environment would be to have dumps transaction of saptools database. Saptools is used by the DBACockpit to store informations related with every collector and job scheduled by DBACockpit. One thing you can do is the reduce the history size of the collectors (Days Kept in History, data is deleted after the mentioned number of days).

Since when no dump transaction is done ? If that is since long time ago, you might still see the 1105 error returned even after having increased the log segment a little bit.
To be honest I would say that you should ensure to have dump trans of that database (SAP Note 1588316 - "SYB: Configure automatic database and log backups". You can redirect the dump to a tape.
In general terms, as the database option "trunc log on ckpt" is disabled, every transaction is logged on the log segment and you'll need to manage it, that is, to cleanup committed transaction with a dump tran.

Keep in mind SAP Note 1585981 - "SYB: Ensuring Recoverability for SAP ASE".

Best regards,
Victoria.