SM:EXEC SERVICES JOB CANCELLED with MESSAGE_TYPE_X dump

In SAP solution manager server SM:EXEC SERVICES job is Cancelling
Hence we are unbale to get the EWA reports...
Error:
Job started
Step 001 started (program RDSMOPBACK_AUTOSESSIONS, variant
&0000000001009, user ID RAOP)
Solution OC Application Monitoring is being edited (Operations)
Trying to perform session 5000000003618
ABAP/4 processor: MESSAGE_TYPE_X
Job cancelled
Applied note 727998 but no use... please help me .
Regards
Prabhakar
Version details:
ST-SER 620-2006_2
PI_ BASIS 2005_1_620

Hi Prabhakar,
Which SP of Solman are you using? If you are using Solman SP12 then the ST-SER has to be upgraded to higher version. Also update the PI_BASIS component.
ST-SER 700_2007_1
PI_BASIS 2006_1_700.
Regards,
Raghavendra.

Similar Messages

Job SM:EXEC SERVICES gets cancelled with SYNTAX_ERROR

Hi,
The job which refreshes Service sessions (for Early Watch Alerts) in SolMan 4. gets cancelled with the message:
Syntax error in program "RDSVASAEA_ROOT_____________050 ".
I performed a syntax check on the program in the ABAP Editor and it gives the following result :
Field "BDLDLTRHOSTS001030" is unknown. It is neither in one of the
specified tables nor defined by a "DATA" statement. "DATA" statement.
Can you let me know, how to solve this problem.
My system is SolMan 4.0 SP 15 on Win 2003 with Oracle 10.2.
ST-SER and ST-ICO are with the latest support pkg level,
Regards,
Anil.

These steps can be done easier as of Support Package Stack 15:
>
Amit Devale wrote:
> Step 1:
> Run report BDL_DELETE_ALL_TABLES via SE38 to delete all entries
> in the service definition tables
>
> Step 2:
> Execute a 'Refresh service definitions' task session in transaction
> SDCCN ->Task ->Create ->'Refresh service definitions'
>
> Step 3:
> Execute in transaction SE37 the function module "BDL_GENERATE_LOGFUNC
> _INCLUDES" and enter the value "ALL" in the 'OPTION' field.
Hi Amit,
Support Package Stack 15 of SAP Solution Manager does contain an update of SDCCN (shipped within ST-PI 2005_1_700 SP06.
[SAP Note 727998|www.service.sap.com/sap/support/notes/727998]
This offers an easy way to update the service definitions and to generate the logfunc Includes.
Step 0: Ensure that optimizer statistics exist for table D010INC.
Step 1-3 :You can use functionality in SDCCN to execute these steps.
Perform:
- Path: SDCCN -> Utilities -> Maintain Service Definitions
- Select 'Delete and Replace Service Definitions -> Confirm this selection
- Confirm that you want to delete the definitions
- Confirm that a new task 'Service Definition Refresh' was created
(Take a note of the task id -> Review the log for this task id when it is completed)
You should not not see any errors for either the update of a Service Definitions table or the generation of any re-import include.
Best regards,
Ruediger
P.S.: Great, that you start to share your rich experience here in SDN.

SM: EXEC SERVICES Job is Cancelling

Hello everyone-
I have seen a few posts about this job cancelling however I haven't been able to gather a solution from what I have read. After appling SP15 in our Solution Manager system, the SM: EXEC SERVICES job is failing.
We sent a note off to SAP and they responded back with the instruction to implement notes 611536 and 727998. We have held off on implementing them because they seem awfully involved in order to correct a cancelled batch job. Has anyone implemented these notes? If so, did it solve this problem?
Here are the details from ST22:
The current ABAP program "SAPLDSVAS_PROC" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "RDSVASAEW_DBUDB____________057
" in include "RDSVASAEW_DBUDB____________057 " in
line 61:
"INCLUDE report "/1CAGTF/IF_LOGFUNC_000300" not found"
The include has been created and last changed by:
Created by: "SAP "
Last changed by: "SAP "
Error in the ABAP Application Program
The current ABAP program "SAPLDSVAS_PROC" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
Any ideas?

>
Nathaniel Williams wrote:
> Hello everyone-
> We sent a note off to SAP and they responded back with the instruction to implement notes 611536 and 727998. We have held off on implementing them because they seem awfully involved in order to correct a cancelled batch job.
>Has anyone implemented these notes? If so, did it solve this >problem?
Hi Nathaniel,
just follow the instructions of SAP Note 727998. It's the standard answer and is always recommended.
It will solve the mentioned SYNTAX_ERROR.
Just search for this note in the forum.
Best regards,
Ruediger (also from SAP)

Problem in SM:EXEC SERVICES job.

Hi Experts,1. SM:EXEC SERVICES job is getting cancelled in our solution manager system,
After checking the job log I found out that Job is getting cancelled with ABAP dump SYNTAX_ERROR
2. I checked for the ABAP dump and found that job is getting dump when trigerring Standard SAP program
RDSVASCEW_DBORA____________060. I checked for any OSS notes in service market place but could not fix...
3. I tried manually doing syntactical check for the program but it is getting syntax error in
INCLUDE report "/1CAGTF/IF_LOGFUNC_000498" not found.
If some body could advice on the issue, it would be great help !! Thanks
Let me know if I need to provide more details on the problem.
Regards, Amber S

>
Ruediger Stoecker wrote:
> This is not required for the mentioned dump. The dump pattern is well known
>
> Just follow the instructions of SAP Note 727998 (which has been already recommended above). It's the standard answer and it's always recommended. It will solve the SYNTAX_ERROR.
If the dump pattern is well known, the reason behind the dump or to replace service definitions should have been explained.
Some of the programs (e.g.'RDSVASAEW_ROOT_____________027', 'RDSVASAEW_DBORA____________032') used in the SAP Solution Manager cannot be generated anymore. During the attempt to generate them, the system generates the following error: 'GEN_TOO_MANY_CBS, generation error: Too many DATA control blocks generated', 'Field "OMS_VERSIONS000910" unknown'.
Check this note.
525097
-=-Ragu

SM:EXEC SERVICES job getting failed in Solution manager

HI All,
SM:EXEC SERVICES job getting failed in solution mnager and job log will be fowlloing:
01-31-2012 19:09:21 Job started
01-31-2012 19:09:21 Step 001 started (program RDSMOPBACK_AUTOSESSIONS_ALL, variant , user ID BASISUSER)
01-31-2012 19:09:21 MemSize Begin = 796480 Bytes
01-31-2012 19:09:21 *******************************
01-31-2012 19:09:21 MemSize Begin = 1919120 Bytes
01-31-2012 19:09:23 Solution <000000106120000> "SID..." is being edited (Operations)
01-31-2012 19:09:23 <000000106120000> "SID..."(Operations)
01-31-2012 19:09:23 "Create_Periodic_Services" uses = 0 bytes
01-31-2012 19:09:23 "Create_Periodic_Services" uses = 690 us time
01-31-2012 19:09:23 Trying to perform session EC2000000001313
01-31-2012 19:09:24 MODEL_KEY: SID Installation Number: 6 MODEL_MODE: E MODEL_VERSNR 00001 MODEL_CLASS: EWA Data Model
01-31-2012 19:09:30 Definition nicht vorhanden
01-31-2012 19:09:33 Definition nicht vorhanden
01-31-2012 19:09:45 Internal session terminated with a runtime error (see ST22)
01-31-2012 19:09:45 Job cancelled
St22 Dump:
The exception 'CX_DSVAS_API_CONTEXT_INSTANCE' was raised, but it was not caught
anywhere along
the call hierarchy.
Since exceptions represent error situations and this error was not
adequately responded to, the running ABAP program 'SAPLDSVAS_PROC' has to be
terminated.
Please suggest how to proceed further and provide your valuble inputs
Thanks
Nekkalapu

HI Siva,
I have done the changes according the note but still same problem.
Please suggest any other ways to resolve this issue .
Advance thanks
Regards
Nekkalapu

All my B/G job canceling due to dump: TSV_TNEW_PAGE_ALLOC_FAILED

Hi SAP Gurus,
Production system SAP R/3 Enterprice. 4.7
OS:AIX 5.3
DB:DB2
memory Parameters are already set properly, there was no issues from past 3 years, We din't change any parameter recently.
All my Pay run B/G job canceling due to dump: TSV_TNEW_PAGE_ALLOC_FAILED
B/G job log
================
11/26/2007     03:01:22     Job started
11/26/2007     03:01:22     Step 001 started (program RBDSER01, variant YBD40_01, user ID BC-BATCH)
11/26/2007     03:01:22     0 master IDocs set up for message type CHRMAS
11/26/2007     03:01:22     0 communication IDoc(s) generated for message type CHRMAS
11/26/2007     03:01:23     0 master IDocs set up for message type CLSMAS
11/26/2007     03:01:23     0 communication IDoc(s) generated for message type CLSMAS
11/26/2007     03:01:23     0 master IDocs set up for message type CLFMAS
11/26/2007     03:01:23     0 communication IDoc(s) generated for message type CLFMAS
11/26/2007     03:05:53     ABAP/4 processor: TSV_TNEW_PAGE_ALLOC_FAILED
11/26/2007     03:05:54     Job cancelled
Please let me know ASAP,
Thanks & Regards,
Kishore.
null

Hi,
If you did'nt change anything in the system, you'd better open a SAP support call urgently as it is a production problem...
>>>Production system SAP R/3 Enter<b>price</b>. 4.7
Nice and well choosen typo !
Regards,
Olivier

EWA state="data is available" but there is no "SM:EXEC SERVICES" job

Hi everybody,
i have a Problem with EWAs. It seems to work all fine, it does, until the EWA is in the state "data is available".I can generate a EWA without a problem, when i use the button "start service processing", but i want it to be generated automatically. I searched with TA SM37 for the job SM:EXEC SERVICES in SolMan and in the monitored system, but i didn´t find the job?
Any ideas, what the problem can be?
Best regards,
Stefan

Hi,
@Rohit
Thank you for your reply, but this was not what i looked for. Thank you anyway!
@David
Thanks, i will check my system and look at the table, i think this is a good beginning. Unfortuneately the note is at the moment not available....
I am going to give feedback, if i found the finally solution!
Bg,
Stefan

Job Cancelled with an error "Data does not match the job def: Job terminat"

Dear Friends,
The following job is with respect to an inbound interface that transfers data into SAP.
The file mist.txt is picked from the /FI/in directory of the application server and is moved to the /FI/work directory of application server for processing. Once the program ends up without any error, the file is moved to /FI/archive directory.
The below are the steps listed in job log, no spool is generated for this job and it ended up with an error "Data does not match the job definition; job terminated".Please see below for more info.
1.Job   Started
2.Step 001 started (program Y_SAP_FI_POST, variant MIST, user ID K364646)
3.File mist.txt copied from /data/sap/ARD/interface/FI/in/ to /data/sap/ARD/interface/FI/work/.
4.File mist.txt deleted from /data/sap/ARD/interface/FI/in/.
5.File mist.txt read from /data/sap/ARD/interface/FI/work/.
6.PD-DKLY-Y_SAP_FI_POST: This job was started periodically or directly from SM36/SM37 (Message Class: BD, Message Number : 076)
7.Job PD-DKLY-Y_SAP_FI_POST: Data does not match the job definition; job terminated (Message Class : BD, Message No. 078)
8.Job cancelled after system exception
ERROR_MESSAGE
Could you please analyse and come up about under what circumstance the above error is reported.
As well I heard that because of the customization issues in T.Code BMV0, the above error has raised.
Also please note that we can define as well schedule jobs from the above transaction and the corresponding data is stored in the table TBICU
My Trials
1. Tested uplaoding an empty file
2. Tested uploading with wrong data
3. Tested uploading with improper data that has false file structue
But failed to simulate the above scenario.
Clarification Required
Assume that I have defined a job using BMV0. Is that mandatory to use the same job in SM37/SM36 for scheduling?
Is the above question valid?
Edited by: dharmendra gali on Jan 28, 2008 6:06 AM

Dear Friends,
_Urgent : Please work on this ASAP _
The following job is with respect to an inbound interface that transfers data into SAP.
The file mist.txt is picked from the /FI/in directory of the application server and is moved to the /FI/work directory of application server for processing. Once the program ends up without any error, the file is moved to /FI/archive directory.
The below are the steps listed in job log, no spool is generated for this job and it ended up with an error "Data does not match the job definition; job terminated".Please see below for more info.
1.Job Started
2.Step 001 started (program Y_SAP_FI_POST, variant MIST, user ID K364646)
3.File mist.txt copied from /data/sap/ARD/interface/FI/in/ to /data/sap/ARD/interface/FI/work/.
4.File mist.txt deleted from /data/sap/ARD/interface/FI/in/.
5.File mist.txt read from /data/sap/ARD/interface/FI/work/.
6.PD-DKLY-Y_SAP_FI_POST: This job was started periodically or directly from SM36/SM37 (Message Class: BD, Message Number : 076)
7.Job PD-DKLY-Y_SAP_FI_POST: Data does not match the job definition; job terminated (Message Class : BD, Message No. 078)
8.Job cancelled after system exception
ERROR_MESSAGE
Could you please analyse and come up about under what circumstance the above error is reported.
As well I heard that because of the customization issues in T.Code BMV0, the above error has raised.
Also please note that we can define as well schedule jobs from the above transaction and the corresponding data is stored in the table TBICU
My Trials
1. Tested uplaoding an empty file
2. Tested uploading with wrong data
3. Tested uploading with improper data that has false file structue
But failed to simulate the above scenario.
Clarification Required
Assume that I have defined a job using BMV0. Is that mandatory to use the same job in SM37/SM36 for scheduling?
Is the above question valid?

Background Job cancelling with error Data does not match the job definition

Dear Team,
Background Job is getting cancelled when I run a Job on periodically but the same Job is executing perfectly when I run it manually(repeat scheduling) .
Let me describe the problem clearly.
We have a program which picks up files from an FTP server and posts the documents into SAP. We are scheduling this program as a background Job daily. This Job is running perfectly if the files contain no data. But if the file contains data the JOb is getting cancelled with the following messages.
And also the same Job is getting executed perfectly when repeat scheduling is done ( even for files with data).
Time     Message text                                                                       Message class Message no. Message type
03:46:08 Job PREPAID_OCT_APPS2_11: Data does not match the job definition; job terminated        BD           078          E
03:46:08 Job cancelled after system exception ERROR_MESSAGE                                      00           564          A
Please help me in resolving this issue.
Thanks in advance,
Sai.

hi,
If you have any GUI function modules used in the program of job
you cannot run it in background mode.

Web Service Job Parameters with Job Actions

I have a set of web service jobs for which I am supplying input parameters. This works fine when defined against a single particular job but i have a need to insert this job based upon a job event and pull some information off of the job the had the event condition occur (i.e. Completed Abnormally). When defining the Job Action to launch the job, the default and override parameter fields are not editable. Has anyone had any luck with this? I didn't notice anything in the documentation but I could have just overlooked this. Any help would be appreciated.
Thanks,
kyle

Me to, and i use Axis for web services (and WebSphere
WebServices).
And, if you use bind from text input you get [object Object]
in general case
<mx:request>
<value>{entry1.text}</value>
</mx:request>
<mx:TextInput x="23" y="101" text="" id="entry1"/>
if you enter any text at textinput and delete it you DONT get
"[object Object]" at web service....
if you dont enter text you get "[object Object]" at web
service...
if you use variable or other elements its the same.
Any help?
TIA

Backgroung job cancelled with the error-Homogenous Lock

Hi All,
We have a custom report ( customer update )which is scheduled to run in the background. In the production system, the job gets cancelled and when we check the log We have the following messages:
20.10.2010 07:14:17 Job started
20.10.2010 07:14:17 Customer 10372118 has been updated                                                               /DS1/A         411          S
20.10.2010 07:14:17 Object requested is currently locked by user XXXX                                                MC           601          E
20.10.2010 07:14:17 Job cancelled after system exception ERROR_MESSAGE
Because of the message"Object requested is currently locked by user xxxx( Homogenous lock ), the job gets cancelled.
Enqeue and deqeue have been taken care correctly.
This problem is reported recently...before that it was working fine.
Have checked SM12, there is no lock. While debugging this error is not reported.
Now please let me know how to know the cause of the error.
Edited by: swarupa.mayflower on Oct 20, 2010 10:45 AM

Hi Immanuel,
I tried opening the customer which I am trying to update in the change mode and then tried debugging the job then it gives me an error message at the bottom of the screen, in this case when I go check there is a lock in SM12.
But my problem is I get this message in the job log and not at the bottom of the screen because of this message(error) the job gets cancelled. Also there is no lock in SM12 in this case and while debugging also I am not getting this message anywhere....
This type of lock is called homogenous lock....but I donno how to trace this error .....

Job getting cancelled with Tbale_illegal_statement dump

hello,
Hi Experts,
i have a background job scheduled for a standard transaction SARA .it is getting cancelled and giving the following error:
"TABLE_ILLEGAL_STATEMENT"
Information on where terminated
The termination occurred in the ABAP program "SAPLCKMLLAARCH" in
"CKMLLA_INIT_READ".
The main program was "RKSARCDL ".
The termination occurred in line 253 of the source code of the (Include)
program "LCKMLLAARCHF01"
of the source code of program "LCKMLLAARCHF01" (when calling the editor 2530).
The program "SAPLCKMLLAARCH" was started as a background job.
The line it is giving Dump Is > INSERT handle_tab.
I have tried to debug the transaction but the execution is not ata all going to the program
SAPLCKMLLAARCH where it is giving dump.Propably because that program is running in Background.
So please let me know how I can fix this issue..Please

Hi Prashanth,
Were you able to resolve the issue ? Because, i am also facing the same problem, when I am triggering the Delete step for CO_CCMAST archiving object.
Regards,
Shail.

Problem with EXEC services Job

Hi,
We are facing problem in Solution Manager 3.0 with EWA report generation. For the scheduled date of EWA , the job RDSMOPBACK_AUTOSESSIONS failed with an error CONNE_ILLEGAL_TRANSPORT_HEADER.
Can anybody , faced or have an solution for the same.
Regards,
Narender

Hi Narender,
usually, this kind of dump is related to a corrupted data collection for the EWA session.
I recommend to delete the download (run DSA, enter the 13 digits session number, choose display and click on the truck symbol, there should be possibility to delete the data). The processing job will run again. You may collect the data in SDCCN again or just create a new EWA session in Solution Manager.
Best regards
Ruediger Stoecker

Some SAP Jobs cancel with error TSV_TNEW_PAGE_ALLOC_FAILS

Some of background jobs started cancelling since 10 days ago.
Here are info from ABAP Dump:
The amount of storage space (in bytes) filled at termination time was:
Roll area...................... 6221248
Extended memory (EM)........... 50278176
Assigned memory (HEAP)......... 799483568
Short area..................... " "
Paging area.................... 24576
Maximum address space.......... 18446744063552822256
Below are my current setting:
Roll, extended and heap memory EXTM
ztta/roll_area        6500000    Byte
ztta/roll_first       1000000    Byte
ztta/short_area       3200000    Byte
rdisp/ROLL_SHM        16384      8 kB
rdisp/PG_SHM          8192       8 kB
rdisp/PG_LOCAL        150        8 kB
em/initial_size_MB    2048       MB
em/blocksize_KB       4096       kB
em/address_space_MB   4092       MB
ztta/roll_extension   50000000   Byte
abap/heap_area_dia    1800000000 Byte
abap/heap_area_nondia 800000000 Byte
abap/heap_area_total 1000000000 Byte
abap/heaplimit        20000000   Byte
abap/use_paging       0
Here are more info
ECC6 SPS13
Oracle 10.2.0.2
Solaris 5.9
Can some please let me know what will be correct parameter setting?
I have played with them a little bit, but still I am getting the error.
Regards,
Ray

Hi,
Please check the link this may resolve your issue.
Re: dump TSV_TNEW_PAGE_ALLOC_FAILED
Regards
K.R

Inetd service/program crashes with core dump in Solaris 8 zone/container

I have developed a service in C that is launched from inetd when something comes on a specific port.
When a connection is opened to the port a core dump is created in the same directory where the executable file is located.
If you run the same service program from the command line everything is working perfect.
This is running in a Solaris 8 zone/container on a Solaris 10 machine.
Everything is set correctly in /etc/inetd.conf and in /etc/services.
I have even stripped down the program to a hello world program that is just printing a string to the screen and it is still crashing with a core dump.
# ldd test_srv
/usr/lib/secure/s8_preload.so.1
libc.so.1 => /usr/lib/libc.so.1
libdl.so.1 => /usr/lib/libdl.so.1
/usr/platform/SUNW,Sun-Fire-480R/lib/libc_psr.so.1
The same service is running on a Linux machine and on a Solaris 10 machine without zones/containers without any problems.
Can you please help me figure out what am I missing. Is there something specific with zones/containers that should be set / configured?
Do I have to set some specific env. variables to work in a Solaris 8 zone/container environment or is it something very simple that I'm missing?

Could you please examine the truss log and advice what the problem is and how to fix it?
(some lines deleted)
bash-2.03# truss -f -p 18361 #### /usr/sbin/inetd -s -t &
18361: poll(0xFFBFF528, 53, -1)        (sleeping...)
18361: poll(0xFFBFF528, 53, -1)                        = 1
18361: accept(63, 0xFFBFF870, 0xFFBFF914, 1)           = 3
18361: sigprocmask(SIG_BLOCK, 0xFFBFF5F0, 0xFFBFF600) = 0
18361: lwp_sigtimedwait(0xFFBFF600, 0xFFBFF578, 0x00000010) = 0
18361: lwp_sigtimedwait(0xFFBFF568, 0xFFBFF728, 0x00000010) = 0
18361: fork()                                          = 1921
1921:   fork()          (returning as child ...)        = 18361
1921:   sigprocmask(0, 0x00000000, 0xFFBFF600)          = 0
18361: sigprocmask(0, 0x00000000, 0xFFBFF600)          = 0
1921:   lwp_sigtimedwait(0xFFBFF600, 0xFFBFF578, 0x00000010) = 0
18361: sigprocmask(SIG_SETMASK, 0xFFBFF5F0, 0xFFBFF600) = 0
18361: close(3)                                        = 0
18361: sigprocmask(0, 0x00000000, 0xFFBFF600)          = 0
1921:   lwp_sigtimedwait(0xFFBFF668, 0xFFBFF528, 0x00000020) = 0
1921:   sigaction(SIGHUP, 0xFFBFF528, 0xFFBFF500)       = 0
18361: lwp_sigtimedwait(0xFFBFF568, 0xFFBFF5F0, 0x00000010) = 0
1921:   lwp_sigtimedwait(0xFFBFF508, 0xFFBFF458, 0x00000010) = 0
18361: sigprocmask(SIG_SETMASK, 0xFFBFF5F0, 0xFFBFF600) = 0
1921:   sigprocmask(SIG_SETMASK, 0xFFBFF5F0, 0xFFBFF600) = 0
1921:   lwp_sigtimedwait(0xFFBFF600, 0xFFBFF578, 0x00000010) = 0
1921:   lwp_sigtimedwait(0xFFBFF568, 0xFFBFF728, 0x00000010) = 0
1921:   fcntl(3, F_DUP2FD, 0x00000000)                  = 0
1921:   close(3)                                        = 0
1921:   fcntl(0, F_DUP2FD, 0x00000001)                  = 1
1921:   fcntl(0, F_DUP2FD, 0x00000002)                  = 2
1921:   open64("/etc/.name_service_door", O_RDONLY)     = 3
1921:   fcntl(3, F_SETFD, 0x00000001)                   = 0
1921:   door_info(3, 0xFF0C2748)                        = 0
1921:   door_call(3, 0xFFBFF278)                        = 0
1921:   close(67)                                       Err#9 EBADF
1921:   close(66)                                       Err#9 EBADF
1921:   close(65)                                       Err#9 EBADF
1921:   close(64)                                       Err#9 EBADF
1921:   close(63)                                       = 0
1921:   close(62)                                       = 0
1921:   close(12)                                       = 0
1921:   close(11)                                       = 0
1921:   close(10)                                       Err#9 EBADF
1921:   close(9)                                        Err#9 EBADF
1921:   close(8)                                        Err#9 EBADF
1921:   close(7)                                        Err#9 EBADF
1921:   close(6)                                        Err#9 EBADF
1921:   close(5)                                        Err#9 EBADF
1921:   close(4)                                        Err#9 EBADF
1921:   setrlimit(RLIMIT_NOFILE, 0xFFBFFD20)            = 0
1921:   xenix(398872, 0xFFBFF5E4, 0x00000040)           = 38
1921:   execve("/tmp/srv/t_srv", 0x0008B5FC, 0xFFBFFDA0) argc = 0
1921:   getuid()                                        = 0 [0]
1921:   resolvepath("/usr/lib/ld.so.1", "/usr/lib/ld.so.1", 1023) = 16
1921:   open("/var/ld/ld.config", O_RDONLY)             = 3
1921:   fstat(3, 0xFFBFF5E8)                            = 0
1921:   mmap(0x00000000, 148, PROT_READ, MAP_SHARED, 3, 0) = 0xFF3E0000
1921:   close(3)                                        = 0
1921:   stat("/usr/lib/libc.so.1", 0xFFBFF648)          = 0
1921:   resolvepath("/usr/lib/libc.so.1", "/usr/lib/libc.so.1", 1023) = 18
1921:   open("/usr/lib/libc.so.1", O_RDONLY)            = 3
1921:   mmap(0x00000000, 8192, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0xFF340000
1921:   mmap(0x00000000, 802816, PROT_NONE, MAP_PRIVATE|MAP_NORESERVE|MAP_ANON, -1, 0) = 0xFF200000
1921:   mmap(0xFF200000, 703520, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED, 3, 0) = 0xFF200000
1921:   mmap(0xFF2BC000, 24772, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_FIXED, 3, 704512) = 0xFF2BC000
1921:   munmap(0xFF2AC000, 65536)                       = 0
1921:   memcntl(0xFF200000, 113528, MC_ADVISE, MADV_WILLNEED, 0, 0) = 0
1921:   close(3)                                        = 0
1921:   stat("/usr/lib/libdl.so.1", 0xFFBFF648)         = 0
1921:   resolvepath("/usr/lib/libdl.so.1", "/usr/lib/libdl.so.1", 1023) = 19
1921:   open("/usr/lib/libdl.so.1", O_RDONLY)           = 3
1921:   mmap(0xFF340000, 8192, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED, 3, 0) = 0xFF340000
1921:   mmap(0x00000000, 8192, PROT_NONE, MAP_PRIVATE|MAP_NORESERVE|MAP_ANON, -1, 0) = 0xFF330000
1921:   mmap(0xFF330000, 2638, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_FIXED, 3, 0) = 0xFF330000
1921:   close(3)                                        = 0
1921:   stat("/usr/platform/SUNW,Sun-Fire-480R/lib/libc_psr.so.1", 0xFFBFF368) = 0
1921:   resolvepath("/usr/platform/SUNW,Sun-Fire-480R/lib/libc_psr.so.1", "/usr/platform/sun4u-us3/lib/libc_psr.so.1", 1023) = 41
1921:   open("/usr/platform/SUNW,Sun-Fire-480R/lib/libc_psr.so.1", O_RDONLY) = 3
1921:   mmap(0xFF340000, 8192, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED, 3, 0) = 0xFF340000
1921:   close(3)                                        = 0
1921:   mmap(0x00000000, 8192, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_ANON, -1, 0) = 0xFF320000
1921:   dup(0)                                          = 3
1921:   llseek(0, 0, SEEK_CUR)                          Err#29 ESPIPE
1921:   close(0)                                        = 0
1921:   fcntl(3, F_DUP2FD, 0x00000000)                  = 0
1921:   close(3)                                        = 0
1921:   dup(1)                                          = 3
1921:   close(1)                                        = 0
1921:   fcntl(3, F_DUP2FD, 0x00000001)                  = 1
1921:   close(3)                                        = 0
1921:   dup(2)                                          = 3
1921:   close(2)                                        = 0
1921:   fcntl(3, F_DUP2FD, 0x00000002)                  = 2
1921:   close(3)                                        = 0
1921:   sys#177(0x00000080, 0xFFBFFB7C, 0xFF3F0518, 0x00000000, 0xFF3C2EF8, 0xFF2C0284) = 0x00000000 [0xFFBFFB7C]
1921:   sys#227(0x00000006, 0x00000000, 0x0001ADF0, 0xFF3F0518, 0xFF3C3C18, 0xFF3C2670) = 0x0000000C [0x00000000]
1921:   sys#227(0x00000002, 0x0000000C, 0x0000000E, 0xFFBFFCAE, 0x00000002, 0xFF3C2670) = 0x00000002 [0x00000000]
1921:       Incurred fault #6, FLTBOUNDS %pc = 0xFF232E2C
1921:         siginfo: SIGSEGV SEGV_MAPERR addr=0x00000000
1921:       Received signal #11, SIGSEGV [default]
1921:         siginfo: SIGSEGV SEGV_MAPERR addr=0x00000000
1921:           *** process killed ***
18361:      Received signal #18, SIGCLD, in poll() [caught]
18361:        siginfo: SIGCLD CLD_DUMPED pid=1921 status=0x000B
18361: poll(0xFFBFF528, 53, -1)                        Err#4 EINTR
18361: lwp_sigtimedwait(0xFFBFF218, 0xFFBFF140, 0x00000010) = 0
18361: lwp_sigtimedwait(0xFFBFF130, 0xFFBFF218, 0x00000010) = 0
18361: sigprocmask(0, 0x00000000, 0xFFBFEF28)          = 0
18361: poll(0xFFBFF528, 53, -1)        (sleeping...)Thank you in advance

SM:EXEC SERVICES JOB CANCELLED with MESSAGE_TYPE_X dump

Similar Messages

Maybe you are looking for