---------------------------------------------------------------------------
LABEL: CORE_DUMP_FAILED
IDENTIFIER: FAA1D46F
Date/Time: Mon Jul 31 15:51:32 DFT 2006
Sequence Number: 4979
Machine Id: 00CB764F4C00
Node Id: lpar2
Class: S
Type: PERM
Resource Name: SYSPROC
Description
SOFTWARE PROGRAM ABNORMALLY TERMINATED
Probable Causes
INTERNAL SOFTWARE ERROR
SYSTEM RUNNING OUT OF PAGING SPACE
User Causes
USER GENERATED SIGNAL
Failure Causes
CORE DUMP FAILED - SEE A REASON CODE BELOW
Recommended Actions
DEFINE ADDITIONAL PAGING SPACE
RERUN THE APPLICATION PROGRAM
IF PROBLEM PERSISTS THEN DO THE FOLLOWING
CONTACT APPROPRIATE SERVICE REPRESENTATIVE
Detail Data
SIGNAL NUMBER
4
USER'S PROCESS ID:
446716
REASON CODE
1
USER ID
204
PROCESSOR ID
0
CORE FILE NAME
/dsqs/datastage/Ascential/DataStage/Projects/CBDK_TEST/core
PROGRAM NAME
dsapi_slave
Something you've tried to do from a DataStage client (through a dsapi_slave process on the server) has hit this limit. Keep the core file in case you need to report the problem to support.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Where can I find some logs of ds server running? I would like to get info such: new client connection, is that connection was succesful/not, how many clients are connected?
Is that possible?
And how to connect to ds server on unix to run DS.TOOLS app?
Where can I find some logs of ds server running? I would like to get info such: new client connection, is that connection was succesful/not, how many clients are connected?
Is that possible?
And how to connect to ds server on unix to run DS.TOOLS app?
How this is related to your topic posted
Success consists of getting up just one more time than you fall.
There is no log. You need to take snapshots using netstat or, perhaps, list_readu | grep :
I'm guessing you want to spot the culprit. The list_readu report will show the identity of the client machine as well as the pid of the dsapi_slave process.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
How much real memory do you have and how much paging space? Reason I ask is because IBM still recommends that you have more paging space then real memory. If not, you can run into many problems. Including, not being able to generate dumps, running out of paging space, cannot fork processes, etc...
Check real memory.
$ lscfg | grep mem
+ mem0 Memory
Determine size of mem0
$ lsattr -El mem0 | grep goodsize
goodsize 16384 Amount of usable physical memory in Mbytes False
I have 16384 MB of real memory.
Check paging space size.
$ lsps -s
Total Paging Space Percent Used
17408MB 2%