SAP Knowledge Base Article
1931223 - Error SQL1105 "Can't allocate space for object..." - SAP ASE for Business Suite
and SAP BW
Component: BC-DB-SYB (Basis Components > Database Interface, Database Platforms > Business Suite on
Adaptive Server Enterprise), Version: 44, Released On: 11.03.2024
Symptom
This KBA describes the various scenarios where you may encounter SQL1105 errors returned from SAP systems running
on SAP ASE database. As well as describes how to avoid and resolve SQL1105 errors on SAP systems. Hence, please read
the KBA carefully to see what will help to clear the SQL1105 in your specific scenario.
SQL1105 errors may arise during runtime (includes installation time) or during database recovery (ASE server
start-up/boot)
For runtime failures, ASE is up and running, you see that work processes disconnect with a short dump with one of
the following error messages which also appear in SM21 system log, in a work process developer trace (in the ASE
errorlog it will be reported as "Msg 1105"):
[ASE Error SQL1105] Can't allocate space for object '<objectname>' in database '<dbname>' because 'default/
system' 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.
[ASE Error SQL1105] Can't allocate space for object 'syslogs' in database '<dbname>' 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.
For recovery failures, you see that one or more of the ASE databases do not come online (and/or subsequently
marked suspect) due to the Error 1105. Please refer to SAP Note 1810223 - "SYB: Recovery of a database fails with
error 3475".
Warning message during Netweaver Patch installation/upgrades:
There is not enough free space in the database. The expected amount of space is #### MB but only #### MB are
available. Note that you may encounter problems if you discontinue this process. We recommend that you extend
the free space to meet the requirement.
Environment
SAP Adaptive Server Enterprise (ASE) 15.7 and 16.0 for Business Suite
SAP NetWeaver (NW) - All versions
Cause
The available space to store data or transaction log has been exhausted.
Resolution
For Error 1105 reported for DBACockpit jobs on the saptools database, please refer to KBA 1836607
For Errors 1105 and 3475 reported during ASE database recovery, please refer to SAP Note 1810223
In other situations:
Carefully check which segment is running out of space. The error message indicates whether space ran out
on the logsegment or on default/system segment, based on that apply steps A) or B):
A. If SQL1105 is reported on the log segment (syslogs):
1. First, try clearing the transaction log manually within SQL command-line in DBACockpit or in isql via the
command: dump transaction <SID> to "<file>"
2. If previous step doesn't release space, extend the logsegment using one of those options:
Using DBACOCKPIT: go to menu Space → Databases → click on your SID → click on bottom "Extend
DB Space" → follow the steps/instructions for the log device
or
Manually via ASE isql utility, issue commands: isql -S<SID> -Usapsa -X -w1000
Check database current log devices:
sp_helpdb <SID>
go
To resize an existing log device:
use master
go
disk resize name = '<existing_log_device_name>', size = '<size in GB>G' -- size is what is being
added, not the total target size of the device
go
alter database <dbname> log on <existing_log_device_name> = '<size in GB>G'
go
OR to create a new log device:
use master
go
disk init name = '<new_log_device_name>' , physname = '<path/filename>' , size = '<size in GB>G'
go
alter database <dbname> log on <new_log_device_name> = '<size in GB>G'
go
3. Also, check if there is an old active transaction which might be preventing the log from being truncated via:
Using DBACOCKPIT -> Performance -> Process Monitor -> Task Status: Holding Oldest Active Log
Manually via ASE isql utility, issue command: select * from master..syslogshold
If this is the case, increase the size of the logsegment as indicated above. Do not kill long-
running jobs/spids without checking the state of the ASE spid (server process ID) and it's corresponding
SAP work process (see KBA 2010795)
B. If SQL1105 error is reported on the default or system segment:
1. First, check that DBACockpit ATM REORG jobs are scheduled and running as planned. If not, then correct the
scheduling of the REORG jobs and see if SQL1105 persists.
2. Expand the database via DBACOCKPIT, or manually via isql like so:
Using DBACOCKPIT: go to menu Space → Databases → click on your SID → click on bottom "Extend
DB Space" → follow the steps/instructions for the data device
or
Manually via ASE isql utility, issue commands: isql -S<SID> -Usapsa -X -w1000
Check database current data devices:
sp_helpdb <SID>
go
To resize an existing data device:
use master
go
disk resize name='<existing_data_device_name>', size = '<size in GB>G' -- size is what is being added,
not the total target size of the device
go
alter database <dbname> on <existing_data_device_name> = '<size in GB>G'
go
OR to create a new data device:
use master
go
disk init name = '<new_data_device_name>' , physname = '<path/filename>' , size = '<size in GB>G'
go
alter database <dbname> on <new_data_device_name>='<size in GB>G'
go
To avoid running into SQL1105 errors:
Ensure regular database backups are set up per SAP Note 1588316
Set up Automatic Database Expansion on SAP ASE as explained in SAP Note 1815695
Set up threshold procedures for automated management of transaction log space on DML- and I/O-intensive
systems as explained in SAP Note 1801984
For sybmgmtdb database, log & data can be separated at installation time, please follow instructions from
KBA 2462650
See Also
SAP Note 1588316 - SYB: Configure automatic database and log backups
SAP Note 1815695 - SYB: Automatic Database Expansion in SAP ASE
SAP Note 1801984 - SYB: Automated management of long running transactions
SAP Note 2462650 - separate log device for sybmgmtdb database
Keywords
DBSQL_SQL_ERROR, "Transaction log full", "dump transaction", disk, SQL1105, 1105, sp_dbextend, logsegment, device, log,
full, "not enough free space", "no enough free space", "extend the free space", freespace, Msg 1105, extend, GA1105, "Guided
Answer"
Attributes
Key Value
Other SAP Business Warehouse > Basis System and Installation > BW Database Platforms > BW on Adaptive Server
Components Enterprise (BW-SYS-DB-SYB)
Products
Products
SAP Adaptive Server Enterprise 15.7
SAP Adaptive Server Enterprise 16.0
SAP NetWeaver all versions
This document refers to
SAP Note/ Component Title
KBA
2462650 BC-DB-SYB separate log device for sybmgmtdb database - SAP ASE for BS
2010795 BC-DB-SYB How to find out the SAP work process number related to an ASE spid - SAP ASE for BS
1945185 BC-SYB-ASE How to expand a database automatically - SAP ASE
1836607 BC-DB-SYB How to solve error 1105 "Can't allocate space for object..." in saptools database - SAP ASE for Business
Suite
1815695 BC-DB-SYB SYB: Automatic Database Expansion in SAP ASE
1810223 BC-DB-SYB SYB: Recovery of a database fails with error 3475
1802842 BC-DB-SYB SYB: Error 1105 and Error 3475 in ASE error log
1801984 BC-DB-SYB SYB: Automated management of long running transactions
1588316 BC-DB-SYB SYB: Configure automatic database and log backups
Reference Manual: Procedures > sp_thresholdaction
Reference Manual: Procedures > sp_dbextend
Reference Manual: Commands > alter database
Troubleshooting: Error Messages > Error 1105
Configuring Automatic Database Space Expansion in SAP Adaptive Server Enterprise
This document is referenced by
SAP Note/ Component Title
KBA
2856536 Navigation Page for: Error: 3475, Severity: 21 - SAP ASE
2450303 BW-SYS-DB- Infocube compression job cancelled after system exception ERROR_MESSAGE - SAP BW on ASE
SYB
2486001 BC-DB-SYB Error "Can't allocate space for object 'syslogs' in database" returned in MAIN_SHDCRE/
SUBMOD_SHDDBCLONE/DBCLONE - SAP ASE for BS
2556783 BC-DB-SYB How to add more space to a database device - SAP ASE for BS and BW
2451430 BC-SYB-ASE Error 1105 Decision Tree - SAP ASE
2462650 BC-DB-SYB separate log device for sybmgmtdb database - SAP ASE for BS
2487759 BC-UPG-TLS- SUM Severe error(s) occurred in phase MAIN_SHDCRE/EU_IMPORT2
TLA
2452627 BW-SYS-DB- InfoCube loading fails with ASE Error SQL9573 and SQL1105 - Solution Manager on SAP ASE
SYB
