SolMan not starting up -- Work process restarting

[Former Member]

DEV_DISP

Fri Feb 27 15:55:27 2015

*** ERROR => DpHdlDeadWp: W5 (pid 5408) died (severity=0, status=0) [dpxxwp.c     1531]

*** ERROR => DpHdlDeadWp: W9 (pid 4700) died (severity=0, status=0) [dpxxwp.c     1531]

*** ERROR => DpHdlDeadWp: W10 (pid 4320) died (severity=0, status=0) [dpxxwp.c     1531]

Fri Feb 27 15:55:47 2015

*** ERROR => DpHdlDeadWp: W9 (pid 4876) died (severity=0, status=0) [dpxxwp.c     1531]

*** ERROR => DpHdlDeadWp: W10 (pid 6496) died (severity=0, status=0) [dpxxwp.c     1531]

Fri Feb 27 15:56:13 2015

J2EE server info

  start = TRUE

  state = ACTIVE

  pid = 5444

  load balance = 1

  start_lazy = 0

  start_control = SAP J2EE startup framework

Fri Feb 27 15:59:07 2015

*** ERROR => DpHdlDeadWp: W2 (pid 5388) died (severity=0, status=0) [dpxxwp.c     1531]

Fri Feb 27 15:59:12 2015

*** WARNING => DpRqNoWpHandle: already dispatched rq_id 686 to W2, do not change state

Fri Feb 27 16:00:27 2015

*** ERROR => DpHdlDeadWp: W2 (pid 6696) died (severity=0, status=0) [dpxxwp.c     1531]

Fri Feb 27 16:05:27 2015

*** ERROR => DpHdlDeadWp: W4 (pid 5404) died (severity=0, status=0) [dpxxwp.c     1531]

Fri Feb 27 16:10:27 2015

*** ERROR => DpHdlDeadWp: W2 (pid 1412) died (severity=0, status=0) [dpxxwp.c     1531]

Fri Feb 27 16:13:47 2015

*** ERROR => DpHdlDeadWp: W2 (pid 944) died (severity=0, status=0) [dpxxwp.c     1531]

Fri Feb 27 16:15:27 2015

*** ERROR => DpHdlDeadWp: W2 (pid 6068) died (severity=0, status=0) [dpxxwp.c     1531]

Fri Feb 27 16:20:27 2015

*** ERROR => DpHdlDeadWp: W5 (pid 2312) died (severity=0, status=0) [dpxxwp.c     1531]

Fri Feb 27 16:25:27 2015

*** ERROR => DpHdlDeadWp: W5 (pid 5600) died (severity=0, status=0) [dpxxwp.c     1531]

Fri Feb 27 16:30:27 2015

*** ERROR => DpHdlDeadWp: W2 (pid 3040) died (severity=0, status=0) [dpxxwp.c     1531]

Fri Feb 27 16:35:27 2015

*** ERROR => DpHdlDeadWp: W5 (pid 4976) died (severity=0, status=0) [dpxxwp.c     1531]

Fri Feb 27 16:40:27 2015

*** ERROR => DpHdlDeadWp: W6 (pid 2796) died (severity=0, status=0) [dpxxwp.c     1531]

Fri Feb 27 16:45:27 2015

*** ERROR => DpHdlDeadWp: W4 (pid 5028) died (severity=0, status=0) [dpxxwp.c     1531]

Fri Feb 27 16:50:27 2015

*** ERROR => DpHdlDeadWp: W6 (pid 4168) died (severity=0, status=0) [dpxxwp.c     1531]

Fri Feb 27 16:55:27 2015

*** ERROR => DpHdlDeadWp: W5 (pid 2308) died (severity=0, status=0) [dpxxwp.c     1531]

Fri Feb 27 17:00:27 2015

*** ERROR => DpHdlDeadWp: W4 (pid 4492) died (severity=0, status=0) [dpxxwp.c     1531]

Fri Feb 27 17:05:27 2015

*** ERROR => DpHdlDeadWp: W6 (pid 1364) died (severity=0, status=0) [dpxxwp.c     1531]

Fri Feb 27 17:09:27 2015

*** ERROR => DpHdlDeadWp: W6 (pid 4628) died (severity=0, status=0) [dpxxwp.c     1531]

Fri Feb 27 17:10:27 2015

*** ERROR => DpHdlDeadWp: W2 (pid 5064) died (severity=0, status=0) [dpxxwp.c     1531]

Fri Feb 27 17:15:27 2015

*** ERROR => DpHdlDeadWp: W6 (pid 4988) died (severity=0, status=0) [dpxxwp.c     1531]

Fri Feb 27 17:20:27 2015

*** ERROR => DpHdlDeadWp: W5 (pid 3128) died (severity=0, status=0) [dpxxwp.c     1531]

Fri Feb 27 17:25:27 2015

*** ERROR => DpHdlDeadWp: W2 (pid 3904) died (severity=0, status=0) [dpxxwp.c     1531]

Fri Feb 27 17:30:27 2015

*** ERROR => DpHdlDeadWp: W6 (pid 2348) died (severity=0, status=0) [dpxxwp.c     1531]

Fri Feb 27 17:35:27 2015

*** ERROR => DpHdlDeadWp: W2 (pid 7700) died (severity=0, status=0) [dpxxwp.c     1531]

Fri Feb 27 17:40:27 2015

*** ERROR => DpHdlDeadWp: W2 (pid 6108) died (severity=0, status=0) [dpxxwp.c     1531]

Fri Feb 27 17:45:27 2015

*** ERROR => DpHdlDeadWp: W6 (pid 2456) died (severity=0, status=0) [dpxxwp.c     1531]

Fri Feb 27 17:50:27 2015

*** ERROR => DpHdlDeadWp: W6 (pid 3904) died (severity=0, status=0) [dpxxwp.c     1531]

Fri Feb 27 17:55:27 2015

*** ERROR => DpHdlDeadWp: W2 (pid 5420) died (severity=0, status=0) [dpxxwp.c     1531]

Fri Feb 27 18:00:27 2015

*** ERROR => DpHdlDeadWp: W2 (pid 7000) died (severity=0, status=0) [dpxxwp.c     1531]

Fri Feb 27 18:02:47 2015

*** ERROR => DpHdlDeadWp: W6 (pid 7456) died (severity=0, status=0) [dpxxwp.c     1531]

Fri Feb 27 18:02:52 2015

*** WARNING => DpRqNoWpHandle: already dispatched rq_id 2852 to W6, do not change state

Fri Feb 27 18:05:27 2015

*** ERROR => DpHdlDeadWp: W6 (pid 7284) died (severity=0, status=0) [dpxxwp.c     1531]

Fri Feb 27 18:06:47 2015

*** ERROR => DpHdlDeadWp: W2 (pid 8160) died (severity=0, status=0) [dpxxwp.c     1531]

*** ERROR => DpHdlDeadWp: W6 (pid 4164) died (severity=0, status=0) [dpxxwp.c     1531]

Fri Feb 27 18:06:52 2015

*** WARNING => DpRqNoWpHandle: already dispatched rq_id 2928 to W2, do not change state

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

DEV_RD

Fri Feb 27 15:55:06 2015

GwDpInit: attached to gw_adm at 00000000124202C0

Fri Feb 27 15:55:17 2015

***LOG Q0I=> NiIRead: P=127.0.0.1:51522; L=127.0.0.1:3350: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 5087]

*** ERROR => NiIRead: SiRecv failed for hdl 73/sock 716

    (SI_ECONN_BROKEN/10054; I4; ST; P=127.0.0.1:51522; L=127.0.0.1:3350) [nixxi.cpp    5087]

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

DEV_W2

M 

M Fri Feb 27 15:57:27 2015

M  Deactivate ASTAT hyper index locking

C 

C Fri Feb 27 15:58:07 2015

C  ERROR: -1 in function ExeNormalModify (execute) [line 18799]

C  (1105) [ZZZZZ] [Sybase][ODBC Driver][Adaptive Server Enterprise]Can't allocate space for object

C   'TBTCO' in database 'SOL' because 'default' segment is full/has no free extents

C  . If you ran out of space in syslogs, dump the transaction log. Otherwise, use A

C  LTER DATABASE to increase the size of the segment.

[former_member182657 · Accepted solution]

Addition to it follow SAP Note   1931223 - SYB: SQL Error 1105 - ASE database data and/ or log segment is full

&  1990174 - SAP ASE allocation space error

Hope this will help you.

Regards,

Gaurav

[Former Member]

Thanks Everyone issue is solved with the note 1931223 - SYB: SQL Error 1105 - ASE database data and/ or log segment is full

First increased the device size and then assigned the space by alter database to data file and log file.

Special thanks to Gaurav Rana

[former_member182657]

Hi Viraj,

Nice to hear issue has been resolved & thanks for mentioning,it's really nice to work with you .

Good luck !!

[manumohandas82]

Hi Viraj ,

1 ) Check whether you have enough space in your filesystem  . Especially the tablespace containing table TBTCO ie BTABD ( If your DB is set for Automatic Database Space Expansion

2 ) Follow SAP Note

1931223 - SYB: SQL Error 1105 - ASE database data and/ or log segment is full

alter database  SOL  on <device_name> = '<size in MB>M'

Thanks ,

Manu

[Former Member]

Dear All

Thanks for the reply.

I will check all the possible solutions from your side and update.

Thanks again.

Regards

Viraj

[Former Member]

Hi,

The issue is because your syslogs system table is full which records changes to the databases.

Please refer SAP Note 1990174 for the same

I prefer to extend space rather than dropping values. Also TBTCO table is related to jobs, hence make sure the standard jobs

are running in SAP system as per sap best practises.

16083 - Standard jobs, reorganization jobs

Regards,

Nikhil

[Former Member]

Hi Viraj,

From the error we can see that the tablespace are full can be seen as below in error:-

C  ERROR: -1 in function ExeNormalModify (execute) [line 18799]
C  (1105) [ZZZZZ] [Sybase][ODBC Driver][Adaptive Server Enterprise]Can't allocate space for object
C   'TBTCO' in database 'SOL' because 'default' segment is full/has no free extents
C  . If you ran out of space in syslogs, dump the transaction log. Otherwise, use A
C  LTER DATABASE to increase the size of the segment.

So request you to extend the tablespace in your database.

Regards,

Ram

[former_member182657]

Hi Viraj,

Could you check for space available on the system as well as extend the table space if required for the system & try again.

Regards,