DB error SQL error 1105 occurred

[Former Member]

Dears,

I have working on SAP ERP 6 EHP5 NW 7.02 on Sybase, and get the following error" DB error: SQL error 1105 occurred "also when try to open TCode: dbacockpit to extend the table space, the SAP GUI terminated and show the following error also <SID>: SAP System Message: Work process restated; session terminated.

so please advice how I can solve this issue, thanks in advance.

[Former Member · Accepted solution]

The issue have been solved, Thanks God,

   the solution is: adding new device through

"

use master

go

disk init name ='(Device Name)' ,

physname='/sybase/(SID)/sybsystem/(device name).dat', size='60G'

than alter db to add more space through this device

alter database (database name)

on (device name) = "10240M"

all related information about 1105 error you can find it on the following link

http://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc00729.1500/html/errMessageAdvRes/X10...

[Former Member]

Make sure that the database has been setup for unrestricted file growth. Sometimes when you restrict the file growth and the file size reached its limit, you may get this error message when trying insert / updates on database.

Check out the following article it might be helpful for you to fix SQL Server Error 1105: http://www.sqlserverlogexplorer.com/fix-error-1105-severity-17-state-2/

[Former Member]

I am having the same issue.  I am using repserver and the primary database is fine but the replicate database logs are filling - I have thresholds and dump transactions running.  Both are not clearing the secondary transaction marker - any ideas -

[Former Member]

Hi,

In order to avoid these kind of scenarios, we have implemented seperate tempdb for sapsa user which will allow us login using isql when we face this kind of full situations.

, what is the output of the this statement.

sp_helpsegment logsegment

[Former Member]

thanks for your information

the output of sp_helpsegment logssegment is as the following

segment	name
status

---------------------------- --------------------------------------

     ------------------------

	2	logsegment
	0
device	size

------------------------ ----------------------------

master

248.0MB

free_pages 

-----------

13883

Objects on segment 'logsegment':

table_name
index_name	indid
partition_name

----------------------------------------

     ---------------------------------------- ------------------

     --------------------------------------------------------

syslogs
syslogs	0
syslogs_8

Objects currently bound to segment 'logsegment':

table_name
index_name	indid

----------------------------------------

     ---------------------------------------- ------------------

syslogs
syslogs	0

total_size

total_pages

free_pages

used_pages

     reserved_pages 

----------------- --------------- --------------- ---------------

     ---------------

248.0MB	15872	13883	68
0

(return status = 0)

so what you see?

[Former Member]

1105 -  ASE has run out of space (data or log).

It's possible that dbacockpit is failing because it's running some SQL (to complete the extend) that uses space in tempdb - and it's tempdb that full.

Look at the ASE log to see where thr 1105 occured.

If tempdb is fulll :-

- Use an account that has a seperate tempdb (if set up)

- extend tempdb

- cleanout tempdb manually

- reboot

Cheers,

Chris