Can't allocate space for object 'syslogs'

[Former Member]

Hi All, We have added the space to log file as below getting warning, is there any issue with the database in the future. 2> go 3> alter database TST log ON TST_log_001='5000m' 4> go Extending database by 320000 pages (5000.0 megabytes) on disk TST_log_001 Processed 125 allocation unit(s) out of 1250 units (allocation page 10837504). 10% completed. ..... 80% completed. Processed 1125 allocation unit(s) out of 1250 units (allocation page 11093504). 90% completed. Processed 1250 allocation unit(s) out of 1250 units (allocation page 11125504). 100% completed. Got the below warning: Warning: Using ALTER DATABASE to extend the log segment will cause user thresholds on the log segment within 128 pages of the last chance threshold to be disabled. I have got actual error in SM21 as follows: > [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 th > transaction log. Otherwise, use ALTER DATABASE to increase > the size of the segment. [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. Please suggest, what to do on this. Regards, Karthik

[former_member187136 · Accepted solution]

Hello Karthik,

You did a wrong thing here 😞

The error says there is problem in the logsegment of saptools instead you increased to your SID.

Increase the space to saptools logsement you will not get the error.

Regards

Kiran K Adharapuram

[former_member187136 · Accepted solution]

Karthik,

Run the below command to find what is the device name of saptools

sp_helpdb saptools

go

Next disk resize it and alter the database

use master

go

disk resize name = "device_name", size = "XXXM"

go

use master

go

alter database saptools log on "device_name" = "XXXM"

go

PS- Follow this sapnote: 1836607

Regards

Kiran K Adharapuram

[former_member187136 · Accepted solution]

Buddy,

Going forward you can always proactively look into the sybase database error log and cockpit database space management which will alert for space crunch.

Let's make habit of looking into error log once in a day may be EOD so that we can react pro actively avoiding disasters not only for space but also any shortage of any parameters.

Regards

Kiran K Adharapuram

[Former Member · Accepted solution]

Hi Kiran, For my error where to add. 1> sp_helpdb saptools 2> go saptools             2252.0 MB         sapsa                  5         Dec 18, 2014         full                 100             2000                                                                                       saptools_data_001                  2048.0 MB data only         Dec 18 2014  2:51PM                1981488 saptools_log_001                    204.0 MB log only         Dec 18 2014  2:51PM      not applicable                                                                                                   device         segment --------------------------------------------------------------------         ---------------------------------------- saptools_data_001         default saptools_data_001         system saptools_log_001         logsegment use master go disk resize name = "device_name", size = "XXXM" go use master go alter database saptools log on "device_name" = "XXXM" In my case, device name: saptools_log_001, do I need to add space to saptools_log_001 or 76% /sybase/GED/sapdata_1--> data file GED_data_002.dat 76% /sybase/GED/sapdata_2--> data file GED_data_002.dat 76% /sybase/GED/sapdata_3--> data file GED_data_003.dat 76% /sybase/GED/sapdata_4--> data file GED_data_004.dat 41% /sybase/GED/saplog_1--> log file GED_log_001.dat 29% /sybase/GED/saplog_2 --> log file GED_log_002.dat Please suggest where to add. Regards, Karthik

[former_member187136 · Accepted solution]

Karthik,

I suggest first fully utilise the saptools_log_001 then use 002 disk

Regards

Kiran K Adharapuram

[Former Member · Accepted solution]

Hi Kiran, Thanks for the information. Shall I proceed as below: use master go disk resize name = "saptools_log_001", size = "XXXM" go alter database saptools log on "saptools_log_001" = "XXXM" go Is this add to log file system -->  /sybase/GED/saplog_1 Regards, Karthik.

[former_member187136 · Accepted solution]

Karthik,

You can go ahead and alter but replace XXX with the numerical value

use master

go

disk resize name = "saptools_log_001", size = "1024M"

go

alter database saptools log on "saptools_log_001" = "1024M"

go

Regards

Kiran K Adharapuram

[Former Member · Accepted solution]

Hi Kiran, Getting below error: 1> alter database saptools log on "saptools_log_001" = "1024M" 2> go Msg 102, Level 15, State 181: Server 'GED', Line 1: Incorrect syntax near 'on'. Then I used below worked: 1> alter database GED on saptools_log_001 = "1024M" 2> go Is this OK? Regards, Karthik

[former_member187136 · Accepted solution]

Karthik,

No

There is a space crunch in log device and you increased the data device and that too you gave the log device to data

This is wrong, kindly increase the log device of the database with the available log device.

Please update your contact number I will call you if you need

Regards

Kiran K Adharapuram

[Former Member · Accepted solution]

Kiran, I am in Dubai, please send your number to ks21836@gmail.com will call you. Regards, Karthik.