Job Error (RUN-050406)

Hi,
we have installed Data Services Release XI 3.2 SP3 on Linux machine SUSE Linux Enterprise 10 version 64 bit, with
Tomcat 5.5 and Java JRE 5.0.
When we try to execute a simple job that should create a single flat file we receive this error from Job Error Log:
(12.2) 03-07-11 10:36:54 (E) (16840:1206227584) *RUN-050406*: |Session Job_Srv_test|Data flow DF_Load_File
                                                            Data flow <DF_Load_File> received a bad system message. Message text from the child process is
                                                            <huFFA1, ==========================================================
                                                            Please collect the following and send to Customer Support:
                                                            1. Log files(error_*, monitor_*, trace_*) associated with this failed job.
                                                            2. Exported Atl file of this failed job.
                                                            3. DDL statements of tables referenced in this failed job.
                                                            4. Data to populate the tables referenced in the failed job. If not possible, get the last few rows (or sample of them) when
                                                            the job failed.
                                                            5. Core dump, if any, generated from this failed job.
                                                            ==========================================================
                                                            >. The process executing data flow <DF_Load_File> has died abnormally. For NT, check errorlog.txt. For HPUX, check
                                                            stack_trace.txt. Also, notify Technical Support.
(12.2) 03-07-11 10:36:54 (E) (16840:1206227584) *RUN-050409*: |Session Job_Srv_test
                                                            The job process could not communicate with the data flow <DF_Load_File> process. For details, see previously logged error
                                                            <50406>.
(12.2) 03-07-11 10:36:54 (E) (16840:1206227584) *RUN-050406*: |Session Job_Srv_test|Data flow DF_Load_File
                                                            Data flow <DF_Load_File> received a bad system message. Message text from the child process is
                                                            <huFFA1, ==========================================================
                                                            Please collect the following and send to Customer Support:
                                                            1. Log files(error_*, monitor_*, trace_*) associated with this failed job.
                                                            2. Exported Atl file of this failed job.
                                                            3. DDL statements of tables referenced in this failed job.
                                                            4. Data to populate the tables referenced in the failed job. If not possible, get the last few rows (or sample of them) when
                                                            the job failed.
                                                            5. Core dump, if any, generated from this failed job.
                                                            ==========================================================
                                                            >. The process executing data flow <DF_Load_File> has died abnormally. For NT, check errorlog.txt. For HPUX, check
                                                            stack_trace.txt. Also, notify Technical Support.
We try to restart Job Server, again and again, but nothing change.
The validate of the data flow and of all the objects in the project return with no error.
From Designer we can see Job Server running successfully but we can't login in Profiler Server although is running, we have configured a Profiler Repo and an User Admin Repo in the Management Console, can't understand why the login is not successful, but i think that is not important to our problem.
We try to create another simple Job but the result it's the same..
Anyone have any ideas of the type of problem?
Thanks.

Hi:
Please check if the SAP note below helps you in solving this issue.
1299106 - "Error: Data flow received a bad system message - in job containing Table Comparison object"
Regards,
Francisco Milán.

Similar Messages

An unexpected error occurred while the job was running. (ID 104 Details: The parameter is incorrect (0x80070057))

We are using DPM Version: 4.1.3465.0 with System Center 2012 Service Pack 1 to back up VMs in our Hyper V Cluster. We have a total of 37 VMs with a combination of 2008r2 servers and 2012 servers. One of our 2012 servers will not backup, and we consistently
get the message "An unexpected error occurred while the job was running. (ID 104 Details: The parameter is incorrect (0x80070057))". I have seen this error message when I Googled it, but cannot get past it. I have deleted the Protection Group and
data and tried to re-create, but get the same errors. I also thought the the server might be mis-reporting the data size, but I expanded that to cover the replication data. I have also tried to perform consistancy checks multiple times with no luck. I have
not seen a difinitive answer from my Google searches, so was hopeful someone has seen this also, and have had success in resolving. Currently this server has no backup recovery points, so I am worried if it does crash. I think I have the rollups installed
as well.

Hi Kelly,
does the issue still persists?

An unexpected error occurred while the job was running. (ID: 104)

I'm getting this error in the event logs when trying to run a consistency check / sync with one of our file servers.
This server was working fine, but w needed to migrate the data to a new partition (GPT) to allow it to expand past the 2TB limit of MBR partitions. I added a new 3TB disk migrated the data and changed the drive letter to what the old partition was
prior. Since then we seem to get this error.
I have installed the update roll up on both the server and the agent side. I have also removed the server from the protection group then re-added it. I've also removed and reinstalled the agent on the file server.
Any help is appreciated! Here's the full error from the DPM server:
The replica of E:\ on server is inconsistent with the protected data source. All protection activities for data source will fail until the replica is synchronized with consistency check. (ID: 3106)
An unexpected error occurred while the job was running. (ID: 104)

Server Version is Windows 2012 R2 STD. DPM is 4.2.1235.0 (DPM 2012 R2). I expanded the production file server. All that server does is host up file shares.
I suspected the fact that I created a new volume and changed drive letter back to the original to be the source cause of the issue. What I ended up doing is blowing away the backups from this server on disk and re-adding it to the protection group.
It now runs much longer, but still times out at random with the error mentioned above.
Vijay: The error was copied from Event Viewer. Not sure what else you require? Event ID is 3106 from DPM-EM.
The DPM logs say:
Affected area: E:\
Occurred since: 2015-01-05 2:04:38 AM
Description: The replica of Volume E:\ on servername is inconsistent with the protected data source. All protection activities for data source will fail until the replica is synchronized with consistency check. You can recover data from existing recovery
points, but new recovery points cannot be created until the replica is consistent.
For SharePoint farm, recovery points will continue getting created with the databases that are consistent. To backup inconsistent databases, run a consistency check on the farm. (ID 3106)
An unexpected error occurred while the job was running. (ID 104 Details: The semaphore timeout period has expired (0x80070079))
Date inactivated: 2015-01-05 7:03:04 AM
Recommended action: No action is required because this alert is inactive.
Affected area: E:\
Occurred since: 2015-01-05 2:04:38 AM
Description: The replica of Volume E:\ on servername is inconsistent with the protected data source. All protection activities for data source will fail until the replica is synchronized with consistency check. You can recover data from existing
recovery points, but new recovery points cannot be created until the replica is consistent.
For SharePoint farm, recovery points will continue getting created with the databases that are consistent. To backup inconsistent databases, run a consistency check on the farm. (ID 3106)
An unexpected error occurred while the job was running. (ID 104 Details: The semaphore timeout period has expired (0x80070079))

An unexpected error occurred while the job was running. (ID 104 Details: The parameter is incorrect (0x80070057)) After DPM 2012 SP1 to R2 Upgrade

Hi,
We have upgraded DPM 2012 SP1 to DPM 2012 R2 and OS is Windows 2012 standard.
Now in File Protection Group, we receive error
"An unexpected error occurred while the job was running. (ID 104 Details: The parameter is incorrect (0x80070057))".
This happens to only one Drive(X: Drive) of the PG server, other drive(Z: Drive) backup is working fine.
We tried,
Deleted entire protection group and recreated ,
Ran consistency job 2 to 3 times.
Ran Synchronize with consistency check.
But every time It failed. Before upgrade it was working fine.
Thanks

Hi
I would suggest opening a new case with MS to allow the DPM team to further look into the issue. Also the DPM 2012 R2 RollUp which addresses the (0x80070057)
issue is Rollup 1 and the private will not be needed after applying Rollup 1. The Roll up is found here
http://support.microsoft.com/kb/2904687/en-us
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your
question. This can be beneficial to other community members reading the thread. Regards, Dwayne Jackson II. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights."

BODI - Job Error " blank message,possibly due to insufficient memory

Ending up with below error while executing a DI job. The job uses a file of size 37 MB as source. As the error looks something related to memory. I have tried splitting up the input file into and executed the job. The job completed successfully without any error.
Could someone help me out to find any memory setting which needs to be investigated in the dataflow level to get a permanent solution for it.
Expecting for help !!!
(11.7) 03-04-11 08:18:06 (E) (21097:0001) RUN-050406: |Session SM_DM_ACCESS_LOG_DTL_F_JOB|Workflow SM_DM_ACCESS_LOG_DTL_F_WF|Dataflow SM_DM_ACCESS_LOG_DTL_F_DF
Data flow <SM_DM_ACCESS_LOG_DTL_F_DF> received a bad system message. Message text from the child process is <blank message, possibly due to insufficient memory>. The process executing data flow <SM_DM_ACCESS_LOG_DTL_F_DF> has died abnormally. For NT,
please check errorlog.txt. For HPUX, please check stack_trace.txt. Please notify Customer Support.
(11.7) 03-04-11 08:18:06 (E) (21097:0001) RUN-050409: |Session SM_DM_ACCESS_LOG_DTL_F_JOB|Workflow SM_DM_ACCESS_LOG_DTL_F_WF
The job process could not communicate with the data flow <SM_DM_ACCESS_LOG_DTL_F_DF> process. For details, see previously
logged error <50406>.
(11.7) 03-04-11 08:18:06 (E) (21097:0001) RUN-050409: |Session SM_DM_ACCESS_LOG_DTL_F_JOB|Workflow SM_DM_ACCESS_LOG_DTL_F_WF
The job process could not communicate with the data flow <SM_DM_ACCESS_LOG_DTL_F_DF> process. For details, see previously
logged error <50406>.

Hi,
loading a 37MB file shouldnt be a problem without splitting it. i´ve loaded GB size flatfiles without problems.
Did you checked the error.txt as stated in the message? Whats in there.
If you split the file and you can load it, you have enough space in your DB.
Please check the memory utilization of your server during executing the job with one file. Maybe the Server is too busy...what would be strange with a 37MB file.
Regards
-Seb.

[Solved] Unable to boot (startup job is running)

Hi there!
Today I went home and tried to boot my laptop there, but was unable to boot Arch.
Before I went home I did a system update using ' sudo pacman -Syu ' and shut the laptop off normally. Right now I get the following message whilst booting:
" A startup job is running for dev-disk...25EFDCE0.device"
It fails after 1 min. 30s and shows a time out error for dependency /mnt/6776F38425EFDCE0, and refuses to boot. I waited for 5 min. but the only thing working at that stage is the shut down button (which appears to enter a normal shutdown mode).
Grub 2 is functioning; Windows 8 boots up fine (same HDD); though all options to boot arch fail because of the 'startup job error message'.
Do any of you know how I can fix this, or how to boot/fix arch such that I can attempt to fix it? Based on a search trough this forum it might be an error in FSTAB, although all cases reported on this forum appear to boot normally after the 'a startup job is running 'error message'.
Many thanks.
Last edited by Simthadim (2014-10-11 09:43:36)

Thank you for your response.
Changing the UUID's to /dev/sdaX did not do it's magic, unfortunately. The ' a start job' message is gone, the boot however gets stuck at
/dev/sda2 clean .... (beginning of boot)
Unfortunately I did not properly save the back-up of my fstab file, so the initial set up is lost. Was able to acces arch using alt+f2 and have restored it manually with
lsblk -f
It currently looks like this. I did have a line to automount my data partition (/dev/sda4, label: Data), but didn' t know how to restore that one as that line got deleted too. My gut says this automount was causing the initial error, but it should boot up normally with the current fstab file, right?
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sda2
UUID=47faa9c6-13d9-4d4f-8744-78766ea7c193 / ext4 rw,relatime,data=ordered 0 1
# /dev/sda3
UUID=bd14a274-a365-4511-9a11-151e086a42db none swap defaults 0 0
UUID=509F9EA61178387E /run/media/simon/Data ntfs auto 0 2

Error run time DYNPRO_FIELD_CONVERSION

I have a dump:
Errore run-time        DYNPRO_FIELD_CONVERSION
       Verific. il     28.11.2007 h 02:12:16
A conversion error occurred.
Causa dell'errore
The current screen processing was terminated, since a situation
occurred from which it could not continue processing.
This is probably due to an error in the current screen of the ABAP
program.
Possibili soluzioni
Make a note of the actions and input which caused the error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
Analisi errori
The program flow was interrupted and could not be resumed.
Program "SAPMM06B" tried to display fields on screen 0106. However, an
error occurred while this data was being converted.
Indic. per la correzione
A conversion error occurred while the program was trying to
display data on the screen.
The ABAP output field and the screen field may not have the
same format.
Some field types require more characters on the screen than
in the ABAP program. For example, a date field on a screen needs
two characters more than it would in the program. When attempting to
display the date on the screen, an error will occur that triggers the
error message.
              Screen name.............. "SAPMM06B"
              Screen number............ 0106
              Screen field............. "EBAN-MENGE"
              Error text............... "FX015: Sign lost."
Further data:
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
   To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
   To obtain this, call the system log with Transaction SM21
   and select the "Print" function to print out the relevant
   part.
3. If the programs are your own programs or modified SAP programs,
   supply the source code.
   To do this, you can either use the "PRINT" command in the editor or
   print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
   or which actions and input led to the error.
It is probably not possible to eliminate the system error
with ABAP alone.
If you have access to SAPnet, you can search for a relevant note
using the following keywords:
"DYNPRO_FIELD_CONVERSION" " "
"SAPMM06B" bzw. "MM06BO0R_RM06B-EPSTP"
"RM06B-EPSTP"
Ambiente sistema
SAP Release.............. "620"
Application server....... "assapoa"
Network address.......... "10.58.19.23"
Operating system......... "AIX"
Release.................. "5.2"
Hardware type............ "00CB585E4C00"
Character length......... 8 Bits
Pointer length........... 64 Bits
Work process number...... 26
Short dump setting....... "full"
Database server.......... "ars005sapdb"
Database type............ "ORACLE"
Database name............ "PRD"
Database owner........... "SAPR3"
Character set............ "it_IT.ISO8859-1"
SAP kernel............... "640"
Created on............... "Jul 16 2006 20:40:53"
Created in............... "AIX 1 5 00538A4A4C00"
Database version......... "OCI_920 "
Patch level.............. "139"
Patch text............... " "
Supported environment....
Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE
10.2.0.."
SAP database version..... "640"
Operating system......... "AIX 1 5, AIX 2 5, AIX 3 5"
Utente, transazione.....
Client.............. 300
User................ "CONSULENTI"
Language key........ "I"
Transaction......... "ME52 "
Program............. "SAPMM06B"
Screen.............. "SAPMM06B 0106"
Screen line......... 26
Informazioni punto di interr.
The termination occurred in the ABAP program "SAPMM06B" in "RM06B-EPSTP".
The main program was "SAPMM06B ".
The termination occurred in line 14 of the source code of the (Include)
program "MM06BO0R_RM06B-EPSTP"
of the source code of program "MM06BO0R_RM06B-EPSTP" (when calling the editor
140).
The program "SAPMM06B" was started as a background job.
Errore verificatosi durante un'elaborazione Batch-Input
Dettaglio cd. sorgente
000010   *eject
000020   *----
000030   * Positionstyp aufbereiten                                             *
000040   *----
000050   MODULE RM06B-EPSTP OUTPUT.
000060
000070   CALL FUNCTION 'ME_ITEM_CATEGORY_OUTPUT'
000080        EXPORTING
000090             PSTYP = EBAN-PSTYP
000100        IMPORTING
000110             EPSTP = RM06B-EPSTP
000120             PTEXT = T163Y-PTEXT.
000130
ENDMODULE.
Contenuto campi sistema
Cmpo SY Contenuto.................... Cmpo SY Contenuto....................
SY-SUBRC 0                             SY-INDEX 0
SY-TABIX 1                             SY-DBCNT 1
SY-FDPOS 1                             SY-LSIND 0
SY-PAGNO 0                             SY-LINNO 1
SY-COLNO 1                             SY-PFKEY VU
SY-UCOMM
SY-TITLE Richiesta d'acquisto mod.: Riepilogo pos.
SY-MSGTY                               SY-MSGID
SY-MSGNO 000                           SY-MSGV1
SY-MSGV2                               SY-MSGV3
SY-MSGV4
Richiami/eventi attivi
N..... Tipo........ Nome..........................
       Programma
       Include                                  Riga
       Classe
     1 MODULE (PBO) RM06B-EPSTP
       SAPMM06B
       MM06BO0R_RM06B-EPSTP                        14
Variabili selezionate
     1 MODULE (PBO) RM06B-EPSTP
       SAPMM06B
       MM06BO0R_RM06B-EPSTP                        14
DIEN                           DIEN
                               4444
                               495E
EBAN-PSTYP                     0
                               3
                               0
LIM                            LIM
                               4442
                               C9D0
RM06B-EPSTP
                               2
                               0
POTE                           TXP
                               5552
                               4800
T163Y-PTEXT                    Standard
                               57666676222222222222
                               341E4124000000000000
Chiamate applicazione
Il dump non riporta informazioni relative
Informazioni applicazione
Il dump non riporta informazioni relative
Note interne
The termination occurred in the function "dynpconv.c" of the SAP
Basis System, specifically in line 701 of the module
"//bas/640_REL/src/krn/dynp/dybas.c#4".
The internal operation just processed is "ENDM".
The internal session was started at 20071128021215.
Application server....... "assapoa"
Network address.......... "10.58.19.23"
Operating system ........ "AIX"
Release.................. "5.2"
Hardware type............ "00CB585E4C00"
Database server.......... "ars005sapdb"
Database type............ "ORACLE"
Database name............ "PRD"
Database user ID......... "SAPR3"
Rich. attivi nel nucleo SAP
=> 64 bit R/3 Kernel
=> 64 bit AIX Kernel
=> Heap limit      = unlimited
=> Stack limit     = unlimited
=> Core limit      = 1073741312
=> File size limit = unlimited
=> Heap address = 0x11dd952a0
=> Stack address = 0xfffffffffffa920
=> Stack low     = 0xfffffffffffa920
=> Stack high    = 0xffffffffffff910
=> Stack Trace:
     AixStack() at 0x1000206bc
     CTrcStack2() at 0x1000207b4
     rabax_CStackSave__Fv() at 0x1001520d4
     ab_rabax() at 0x10014ef04
     dyHandleError() at 0x1005a6850
     dypcnvoXt() at 0x100cbd6cc
     dynplend() at 0x1010cf268
     dynpmcal() at 0x1010c6f60
     dynppbo0() at 0x1010c5134
     dynprctl() at 0x1010ce40c
     dynpen00() at 0x100bd0c30
     Thdynpen00() at 0x1000a1f7c
     TskhLoop() at 0x1000a5298
     tskhstart() at 0x1000bb0d8
     DpMain() at 0x101579ca0
     nlsui_main() at 0x10154d428
     __start() at 0x1000002fc
!!! Invalid stack address encountered: 0x0
!!! Stack corrupted.
Lista dei programmi ABAP in oggetto
Tipo
Programma
DataGen   Ora
Dim.car.
Prg
SAPMM06B
25.09.2007 16:07:55
514048
Prg
SAPMSSYD
05.06.2002 17:09:33
16384
Prg
SAPFSYSCALLS
14.02.2002 14:22:47
6144
Typ
T160
12.05.1997 15:22:15
2048
Prg
SAPFMMEX
18.11.2007 09:34:59
177152
Typ
TSTCT
14.02.1998 14:31:34
2048
Typ
TMED
27.08.1994 21:59:16
2048
Typ
TPRG
14.02.1998 14:06:12
2048
Typ
T160D
11.02.2000 14:20:36
5120
Typ
T160V
14.05.1998 22:44:11
6144
Typ
T168T
28.08.1997 09:05:04
2048
Prg
SAPLMEXF
18.11.2007 09:35:00
166912
Typ
T162
02.10.2001 13:56:13
2048
Prg
SAPLSTUP
17.06.2004 12:05:43
65536
Prg
SAPLCNDP
17.06.2004 15:06:47
163840
Prg
SAPFGUICNTL
09.01.2003 17:18:52
20480
Prg
SAPLOLEA
17.06.2004 15:12:42
78848
Prg
SAPLSGUI
09.01.2003 17:15:12
31744
Prg
SAPLSTTM
17.06.2004 15:08:30
75776
Prg
SAPLSBDC
07.01.2003 18:31:25
38912
Prg
SAPLSFES
17.06.2004 15:15:58
174080
Prg
SAPLURFC
17.06.2004 14:25:28
16384
Prg
SAPLSPLUGIN
14.02.2002 14:22:48
6144
Typ
SWCBCONT
15.11.2000 17:55:11
3072
Typ
OLE_VERBS
04.04.1995 16:02:20
2048
Typ
OLE_PA
04.04.1995 16:02:19
2048
Prg
SAPLSCNT
14.02.2002 14:22:47
24576
Prg
SAPSHDTV
17.06.2004 11:46:16
28672
Typ
EBANW
17.06.2004 15:55:16
21504
Prg
CL_CONTEXTFIELD_MM============CP
25.09.2007 16:07:49
9216
Prg
/1BCDWBEN/SAPLMEN0000
18.11.2007 09:35:16
237568
Prg
SAPLSENA
17.06.2004 14:19:40
28672
Typ
EBAN
13.11.2006 11:19:59
20480
Prg
CL_PROCESS_STATE_MM===========CP
25.09.2007 16:07:50
16384
Prg
SAPLSWUG
17.06.2004 14:22:25
53248
Typ
SWCONT
04.04.1995 16:18:01
2048
Typ
OBJ_RECORD
14.02.1998 08:30:43
2048
Typ
SWOTOBJID
04.05.1995 15:20:52
2048
Typ
SWHACTOR
04.04.1995 16:18:07
2048
Prg
CL_GOS_MANAGER================CP
11.04.2001 13:02:00
17408
Prg
CL_GOS_VIEW_MANAGER===========CP
24.01.2002 20:31:22
22528
Typ
SIBFLPOR
15.11.2000 17:53:54
2048
Typ
SGOS_MVOBJ
24.07.2001 09:18:06
3072
Typ
BORIDENT
28.08.1997 08:38:50
2048
Prg
SAPLSUU1
17.06.2004 15:13:06
165888
Typ
USR02
17.06.2004 15:05:37
7168
Typ
USREFUS
07.01.2003 18:24:17
2048
Typ
SIBFLPORB
15.11.2000 17:53:55
2048
Prg
CL_GOS_TOOLBOX_MODEL==========CP
17.06.2004 15:04:37
38912
Typ
SGOS_MODL
24.07.2001 09:18:05
4096
Typ
OBJ_RECORD
14.02.1998 08:30:43
2048
Prg
SAPLSWOR
17.06.2004 15:08:55
270336
Typ
SWOTRI
03.01.1996 15:29:13
2048
Typ
SWOTRETURN
20.08.1998 10:59:29
3072
Prg
SAPLSWOH
14.02.2002 14:22:48
7168
Typ
SWOTENV
11.02.2000 14:20:34
4096
Typ
TOJTD
15.11.1995 03:08:46
2048
Prg
SAPLRHS0
14.02.2002 14:22:47
11264
Prg
SAPLSDIFRUNTIME
17.06.2004 14:20:44
82944
Typ
DFIES
09.11.2000 14:07:05
8192
Typ
X031L
15.11.2000 18:03:28
5120
Prg
SAPLSDNT
17.06.2004 12:06:43
199680
Prg
SAPLSUGS
21.11.2002 10:20:02
29696
Typ
TOJTD
15.11.1995 03:08:46
2048
Typ
TOJTB
14.02.1998 14:02:55
8192
Typ
SWOTLI
04.04.1995 17:30:59
2048
Typ
T100
28.08.1997 09:04:45
2048
Prg
CL_EXITHANDLER================CP
17.06.2004 15:04:37
26624
Prg
CL_ABAP_TYPEDESCR=============CP
17.06.2004 14:19:33
21504
Prg
CL_ABAP_ELEMDESCR=============CP
17.06.2004 14:19:13
18432
Prg
CL_ABAP_DATADESCR=============CP
17.06.2004 14:19:13
14336
Prg
CL_ABAP_REFDESCR==============CP
17.06.2004 14:19:33
16384
Prg
CL_ABAP_STRUCTDESCR===========CP
17.06.2004 14:19:33
19456
Prg
CL_ABAP_COMPLEXDESCR==========CP
17.06.2004 14:19:13
13312
Prg
CL_ABAP_TABLEDESCR============CP
17.06.2004 14:19:33
17408
Prg
CL_ABAP_CLASSDESCR============CP
17.06.2004 14:19:33
23552
Prg
CL_ABAP_OBJECTDESCR===========CP
17.06.2004 14:19:33
25600
Prg
CL_ABAP_INTFDESCR=============CP
17.06.2004 14:19:13
19456
Prg
CL_ABAP_SOFT_REFERENCE========CP
29.03.2001 16:42:12
7168
Prg
CL_ABAP_REFERENCE=============CP
14.02.2002 14:22:46
6144
Prg
IF_EX_GOS_SRV_SELECT==========IP
04.12.2000 16:22:18
4096
Prg
%_CABAP
07.01.2003 18:31:23
23552
Typ
SXS_INTER
30.11.1998 15:55:16
2048
Prg
SAPLSEXV
17.06.2004 15:04:40
106496
Prg
CL_BADI_FLT_DATA_TRANS_AND_DB=CP
17.06.2004 15:04:37
33792
Typ
SXS_ATTR
20.08.2001 12:23:27
4096
Typ
V_EXT_ACT
09.11.2000 14:27:05
2048
Typ
SXC_EXIT
09.11.2000 14:23:43
2048
Prg
CL_EX_GOS_SRV_SELECT==========CP
17.06.2004 15:04:37
13312
Prg
%_CSXRT
17.06.2004 15:04:37
11264
Prg
CL_EXIT_MASTER================CP
17.06.2004 15:04:37
13312
Typ
V_EXT_IMP
09.11.2000 14:27:05
2048
Typ
V_EXT_IMP
09.11.2000 14:27:05
2048
Prg
SAPLBDLS
17.06.2004 11:45:48
176128
Typ
T000
11.09.1997 10:17:18
4096
Typ
SWOTRTIME
14.02.1998 10:19:46
3072
Prg
%_CSWOB
14.02.2002 14:22:46
13312
Typ
SWOTINVOKE
14.02.1998 10:18:40
6144
Typ
SWOTLV
04.12.2000 14:59:45
10240
Prg
SAPLSWCD
17.06.2004 15:06:55
78848
Prg
RBUS2105
13.11.2006 11:20:02
57344
Prg
CL_GOS_PUBLICATION============CP
13.11.2000 16:31:37
15360
Prg
SAPLSGOSHIST
17.06.2004 14:23:50
46080
Typ
EBKN
16.06.2004 13:09:57
9216
Typ
T161
16.06.2004 13:14:35
5120
Typ
T161T
14.02.1998 10:55:58
2048
Typ
CMMDA
18.09.2001 10:02:31
4096
Prg
SAPLMMDA
04.09.2006 11:00:54
65536
Typ
TWLAD
13.08.1997 14:04:45
2048
Typ
TTXID
27.08.1999 17:40:33
3072
Prg
SAPLSTXD
17.06.2004 15:06:22
347136
Typ
STEXTNAME
18.09.2001 10:03:52
1024
Typ
STXDRID
26.02.1999 14:48:42
2048
Typ
STXDRLANG
26.02.1999 14:48:42
2048
Typ
STXDRNAME
26.02.1999 14:48:42
2048
Typ
STXDROBJ
26.02.1999 14:48:42
2048
Typ
THEAD
09.11.2000 14:15:08
6144
Prg
CL_ABAP_CHAR_UTILITIES========CP
07.01.2003 18:31:23
11264
Typ
STXH
17.06.2004 14:15:46
6144
Typ
TCATALOG
25.05.1998 12:19:20
3072
Typ
T168F
27.05.1992 20:16:27
3072
Typ
T168
27.05.1992 17:53:38
3072
Prg
SAPLMECCP
25.09.2007 16:07:53
39936
Prg
CL_BADI_MM====================CP
08.01.2003 16:43:11
9216
Prg
%_CCXTAB
14.02.2002 14:22:46
6144
Prg
SAPLEINH
25.09.2007 16:07:53
56320
Typ
T001W
16.06.2004 13:14:17
9216
Prg
SAPLVDAT
19.02.2002 12:59:51
25600
Typ
T163Y
28.08.1997 09:05:01
2048
Prg
SAPCNVE
14.02.2002 14:22:47
6144
Prg
SAPLOMCV
17.06.2004 10:54:26
16384
Prg
CL_EX_BADI_MATN1==============CP
17.06.2004 10:27:52
22528
Prg
IF_EX_BADI_MATN1==============IP
17.06.2004 10:53:59
4096
Typ
TMCNV
24.02.1999 03:33:25
3072
Typ
RM06B
17.06.1998 03:23:02
10240
Lista tabelle interne
Il dump non riporta informazioni relative
Indice delle tabelle applicative
Programma
Nome................ Contenuto..1.......2........3........4........5....+....
SAPMM06B
SYST                 |00000000000x010000000000000000
EBAN                 |300001100895000010NB B NB           1 Elena Varett20071
*EBAN                |             00000                                   00000
EBKN                 |             0000000 00000000            000000x0C
AEBAN                |3000011008950NB     BBEUR |
EBANW                |300001100895000010NB B NB           1 Elena Varett20071
RM06B                |                           00000000000000000010       00
*RM06B               |                           00000000000000000000       00
RM06E                |          000000000000000    00000000          00000
TPRG                 |300IW2Formato settimana   Sett. |
T001W                |3006   PIATTAFORMA DI LEINI'         6   CEDI6     0000000
T023                 |
T024                 |
T160                 |300ME52                VB        B |
T160V                |300C1XX A              XX X                   X   |
T161                 |300BNB   000100102NBB                 NB         00000
T161T                |300INB BRichiesta d'acquisto|
T168                 |300B AB ***   1 106       0x0C0x0C0x0C0x0C|
T168F                |300B AB XXX                                |
T168T                |300IB0106002 |
TTXID                |EBAN      B04        X
T163K                |                       |
T163Y                |     Standard             |
T001L                |
T160D                |     XXXXXXXXXXXXXXXXXXXXXX
T161E                |                         |
SAPFMMEX
TMED                 |300BB     |
SAPLMEXF
T161                 |300BNB   000100102NBB                 NB         00000
T162                 |300PT0B                ...................................
SAPLSUU1
USR02                |300CONSULENTI ÷x9Fw'x97[æÆ0000000000000000A
USREFUS              |300CONSULENTI
SAPLSWOR
TOJTB                |BUS2105   XI          RBUS2105
SWOTLV               |BUS2105   EXISTENCECHECK                  M
TOJTD                |                                 |
SAPLBDLS
T000                 |300Mandante produzione      Arenzano                 EUR
SAPMM06B
*RM06E               |          000000000000000    00000000          00000
MARA                 |                      00000000            00000000
T006                 |        00          00000000000000x0C 0
SAPLVDAT
TPRG                 |300IW2Formato settimana   Sett. |
SAPLOMCV
TMCNV                |300MATCONV 0x120000000x12
Directory delle tabelle applicative (inf. di gestione)
Programma
Nome.......................... tempo..........lungh....
SAPLOMCV
SYST                           20010612125650 00002404
EBAN                           20061113111959 00000892
*EBAN                          20061113111959 00000892
EBKN                                          00000421
AEBAN                          20000323224119 00000027
EBANW                                         00000896
RM06B                          20000323224119 00000529
*RM06B                         20000323224119 00000529
RM06E                          20020124202505 00001154
TPRG                           20000323231030 00000032
T001W                          20040617141548 00000338
T023                           20040616131428 00000102
T024                           20040616131429 00000352
T160                                          00000035
T160V                                         00000050
T161                           20040616131435 00000095
T161T                                         00000029
T168                                          00000035
T168F                                         00000044
T168T                                         00000013
TTXID                                         00000058
T163K                          20000323230840 00000023
T163Y                                         00000026
T001L                          20000323230832 00000069
T160D                                         00000069
T161E                          20000323230840 00000025
SAPFMMEX
TMED                                          00000010
SAPLMEXF
T161                                          00000095
T162                                          00000234
SAPLSUU1
USR02                                         00000226
USREFUS                                       00000067
SAPLSWOR
TOJTB                                         00000453
SWOTLV                                        00000701
TOJTD                                         00000033
SAPLBDLS
T000                                          00000107
SAPMM06B
*RM06E                         20020124202505 00001154
MARA                           20071118093457 00001118
T006                           20001109142345 00000080
SAPLVDAT
TPRG                                          00000032
SAPLOMCV
TMCNV                                         00000062
Blocchi di contr. CONT ABAP
Include                                 Riga Codice sorg.
Ind. Nome FI Co Par01 Par2. Par3. Par4. Tab.
MM06BO0R_RM06B-EEIND                       25 EXIT.
2502 BRAX 00
MM06BO0R_RM06B-EEIND                       27 ENDSELECT.
2503 BRAX 00
2504 SQLS 08
MM06BO0R_RM06B-EEIND                       31 ENDMODULE.
2505 ENDM 00
2506 -
MM06BO0R_RM06B-EPSTP                        7 CALL FUNCTION 'ME_ITEM_CATEGOR
2507 FUNC 00
2508 FUNC 00
2509 PAR2 02     0336
2511 FUNC 10
2512 PAR2 01     03B9
2514 PAR2 01     03BA
2516 FUNC FF
MM06BO0R_RM06B-EPSTP                       14 ENDMODULE.
>>>>> ENDM 00
2518 -
MM06BO0V_VRTKZ                              6 CASE EBAN-VRTKZ.
2519 BREL 04
MM06BO0V_VRTKZ                              7 WHEN '1'.
2520 when 00 02 0090
2522 BRAN 02
2523 BRAX 00
MM06BO0V_VRTKZ                              8 RM06B-MKNTW = '3 '. "3 Nachkom
2524 MOVL 00 02 0136
MM06BO0V_VRTKZ                              9 WHEN '2'.
2526 BRAX 00
Fine dell'analisi err. run-time
Help me.
Thank you

Hello Maurizio,
Thre screen field EBAN-MENGE is unable to handle a sign along with the value.
Regards,
Ammey Kesarkar

Sending job error message to admin by email

Hi everyone...
Anyone knows how to send job error message to admin by email? For example, if crawler failed, an email is sent to admin with the error message. I'm thinking of building windows service which run at the background and knows when a job fail and send the error message through email to admin.
Is there a better way?
Cheers,
Jefi Santoso

hi,
>>>Can this be achieved through BPM?
yes you can put your transformation step
and send step in a block and specify an exception
branch and catch all exceptions that will
occur during transformations and the send step
then you can send info from the exception branch to
any other system
you won't be able to catch the error's name
but you will be able to notify any thinrd party
about the error
more on error catching:
http://help.sap.com/saphelp_nw04/helpdata/en/33/4a773f12f14a18e10000000a114084/content.htm
Regards,
michal

Cron job not running - script uses rsync, ssh (with id_rsa)

Does anyone know how to get cron to run a rsync/ssh script which uses id_rsa for passwordless logins?
I have a backup script I have slaved for months over that works wonderfully when running it from the command line.
It uses rsync and connects with SSH (passwordless using ssh keys). I have setup id_rsa and id_rsa.pub for passwordless logins (this is my user account, and connects using root@ to the server)
As stated all works find when run from the command line. But when I setup a cron job to run this file (exact same line I run from the command line) it does not execute. Actually, it does run, as I have an email notifiction which sends to me. It is just the rsync/ssh part that does not run.
I have spent days and days trying to figure it out. No error messages occur, nothing. Took me a while to find out cron is emailing the user account on Lion the messages (not to a proper email address).
The error shows a permission denied, which I believe to be the cron user cannot use the id_rsa/ssh connection.
Cron is running the script as my user, the same I use on the command line. I even tried copying the id_rsa to the root user .ssh folder in case cron is running as root but that does not work either.
So does anyone know how to get cron to run this rsync/ssh script which used id_rsa for passwordless logins?
Thanks a lot

YES! Got it working, finally!
So the issue is indeed cron/launchd not being able to access the ssh-agent which holds the key.
So this is the solution...
Download keychain for Mac:
http://www.funtoo.org/wiki/Keychain
Then once its installed and configured, the script to run needs this added to the top:
eval `keychain --noask --eval id_rsa` || exit 1
Note I am using id_rsa whereas keychains instructions refer to id_dsa so I just changed it and it works OK.
When the script runs the first time it asks for the key password. Then it works from then on.
What I do not know yet is will I need to re-enter the password when I logoff/logon again. That will cause an issue as I auto restart the Mac every day which means if I am off for a few days backup will stop (can you see the madness in this issue!).

HELP scheduling a job to run within a window

Hi,
I am trying to create a job that can only run at certain times of the day. Since I will be creating a lot of these jobs (each of which will run once), I thought I could use a window to define when this job runs. As a test, I tried the following:
begin
   dbms_scheduler.create_window(
      window_name => 'TEST_WINDOW',
      resource_plan => null,
      repeat_interval => 'FREQ=DAILY',
      duration => INTERVAL '24' hour,
      window_priority => 'LOW'
   dbms_scheduler.create_job(
      job_name => 'TEST_WINDOW_JOB',
      job_type => 'PLSQL_BLOCK',
      job_action => 'BEGIN NULL; END;',
      schedule_name => 'SYS.TEST_WINDOW',
      enabled => true );
end;
/But this doesn't work as expected.
1) all_scheduler_windows shows that TEST_WINDOW is not ACTIVE. However, if I try to explicitly open the window with DBMS_SCHEDULER.OPEN_WINDOW, I get an error saying the window is currently open.
2) The job is created, but its STATE is set to SCHEDULED and it doesn't run even though the window is open and the job is enabled. (I also tried creating a job using a window that was ACTIVE in all_scheduler_windows and got the same results).
Can anyone point out what I am doing wrong here?
Thank you,
Eric

Hi Eric,
Two things.
1) You can have a schedule which repeats once an hour (or even once a minute) from 8pm till 7am and then point all your jobs to this schedule. You will need to set max_runs for the jobs to 1 before enabling them. So they will only run on the given schedule and only once. A possible repeat interval for the schedule is :
freq=minutely;bysecond=0;byhour=20,21,22,23,0,1,2,3,4,5,6,7;byday=MON,TUE,WED,THU,FRI
2) By default, the database comes with several pre-created windows and a MAINTENANCE_WINDOW_GROUP . This window group is supposed to be user-modified to periods where it is ok to do maintenance tasks. You may be able to point your jobs to this window group or one of its windows, if you want your jobs to run during this period.
Hope this helps,
Ravi.

Having trouble getting a job to run using job scheduler

I am using Oracle 11g. I run a sql script that schedules a job:
exec sys.dbms_scheduler.create_job( job_name => '"SYSTEM"."UCR"', job_type => 'EXECUTABLE', job_action => 'D:\UserCountReport\bin\ucr.bat', repeat_interval => 'FREQ=HOURLY;BYHOUR=3;BYMINUTE=0;BYSECOND=0',start_date => to_timestamp_tz('2011-07-21 US/Eastern', 'YYYY-MM-DD TZR'), job_class => 'DEFAULT_JOB_CLASS', auto_drop => FALSE,enabled => FALSE);
exec sys.dbms_scheduler.set_attribute( name => '"SYSTEM"."UCR"', attribute => 'job_weight', value => 1);
exec sys.dbms_scheduler.enable( '"SYSTEM"."UCR"' );
commit;
exit;When I am connected to the database, I run these commands:
SQL> SELECT JOB_NAME, STATE, job_action, repeat_interval FROM DBA_SCHEDULER_JOBS
where job_name='UCR';
JOB_NAME
STATE
JOB_ACTION
REPEAT_INTERVAL
UCR
SCHEDULED
C:\UserCountReport\bin\ucr.bat
FREQ=HOURLY;BYHOUR=9;BYMINUTE=0;BYSECOND=0
SQL> SELECT JOB_NAME, status FROM DBA_SCHEDULER_JOB_LOG where job_name = 'UCR';
JOB_NAME
STATUS
UCR
SUCCEEDED
UCR
SUCCEEDED
UCR
SUCCEEDEDHowever, I don't get any signs that the job has run even though Oracle says all the runs have succeeded. The batch file that the job is supposed to execute creates a file and writes stuff to it. However, the file is not written. When I run the batch file from command prompt, it executes correctly.
I have tried following instructions here:
Answers to "Why are my jobs not running?"
However, all three of these commands return errors:
SQL> select value from v$parameter where name='job_queue_processes';
select value from v$parameter where name='job_queue_processes'
ERROR at line 1:
ORA-00942: table or view does not exist
SQL> select count(*) from dba_scheduler_running_jobs;
select count(*) from dba_scheduler_running_jobs
ERROR at line 1:
ORA-00942: table or view does not exist
SQL> select count(*) from dba_jobs_running;
select count(*) from dba_jobs_running
ERROR at line 1:
ORA-00942: table or view does not existI've tried various other commands from that list and I get errors as well.
I'm not quite sure where to go from here to troubleshoot this problem. Any help would be appreciated. Thanks.
Edited by: 874375 on Jul 22, 2011 9:14 AM
Edited by: 874375 on Jul 22, 2011 9:18 AM

So I changed my script to this:
exec sys.dbms_scheduler.create_job( job_name => '"SYSTEM"."UCR"', job_type => 'EXECUTABLE', job_action => '%windir%\system32\cmd.exe /C D:\UserCountReport\bin\ucr.bat', ....I now have this:
SQL> SELECT JOB_NAME, status FROM DBA_SCHEDULER_JOB_LOG where job_name='BOXTONE_
MONTHLY_UCR';
JOB_NAME
STATUS
BOXTONE_MONTHLY_UCR
FAILED
BOXTONE_MONTHLY_UCR
SUCCEEDED
BOXTONE_MONTHLY_UCR
SUCCEEDED
JOB_NAME
STATUS
BOXTONE_MONTHLY_UCR
SUCCEEDEDIs there a place with log files that will tell me why the job failed? If so where are the log files located?

Jobs with running status in OEM while it was already finished

Hi
We have rebooted our server and all the jobs which are suppose to run some scripts in the server are showing running state for more than 16hours now! checking the scripts logs it was successfully executed and finished. When trying to delete the running jobs and schedule a new one it refuses to stop (although its not even running in reality). What can we do to clear this running status and let oem to schedule new ones? or how can we resolve this situation?
We are running Enterprise manager 10g
Swaid

Hi Jozsef,
I've tried to follow the instructions in that Metalink note and the job seems to be deleted from mgmt_job table as well as the executions for that job in mgmt_job_execution; but still everything is hanging and when i checked in the EM page it still shows the job in running state! how can I clean it? and why is it hanging in the first place?
I've looked into the agent trace and its not getting updated since the problem has started and here is a bit of the last messages we have in the trace:
2009-04-17 12:05:09 Thread-2413 ERROR http: secondary header = Host, value = snmsmaster:3938
2009-04-17 12:05:09 Thread-2413 ERROR http: secondary header = Connection, value = Keep-Alive, TE
2009-04-17 12:05:09 Thread-2413 ERROR http: secondary header = TE, value = trailers, deflate, gzip, compress
2009-04-17 12:05:09 Thread-2413 ERROR http: secondary header = User-Agent, value = RPT-HTTPClient/0.3-3
2009-04-17 12:05:09 Thread-2413 ERROR http: secondary header = Accept-Encoding, value = gzip, x-gzip, compress, x-compress
2009-04-17 12:05:09 Thread-2413 ERROR http: secondary header = Content-type, value = application/octet-stream
2009-04-17 12:05:09 Thread-2413 ERROR http: secondary header = Content-length, value = 593
2009-04-17 12:05:09 Thread-2413 ERROR http: --- Error context dump end for incoming request ---
The emoms trace is getting updated with some repeated error messages that looks like below:
2009-04-18 15:56:57,114 [HealthMonitor] ERROR em.jobs pingPastDue.604 - Job step continuing
2009-04-18 15:57:13,362 [HealthMonitor] ERROR emd.main run.291 - HealthMonitor : Found errant task : TaskRegn:ID3440,Callback:class oracle.sysman.emdrep.jobs.JobWorker,Iterative:true,Duration:900,DueTime:1240059433359
2009-04-18 15:57:13,363 [HealthMonitor] ERROR em.jobs pingPastDue.602 - Entry - 15 Minute timeout error for jobstep:Stepname: Command
Commandname: remoteOp
Commandtype: Short-Running
StepId: 97914
jobIdStr: 679733b18b7a5698e04400144fa10220
executionIdStr: 67bd0ff86c9b4268e04400144fa10220
iterateParam: null
iterateParamIndex: -1
Swaid

How to find the particular record in 1000's of workflow jobs are running

Hi,
In a data manager -> in workflow tab>IF a record is in CHECK-OUT MODE there are 1000's of jobs are running in that workflow tab. Can anyone tell me how to find that particular record in that workflow jobs.
Can anyone show me the difference in getting a record in 5.5 and 7.1

Hello COTI
Unfortunatly, SAP MDM doesn't have good ability for WF search.
All WF clarify by it's status (unlaunched, avialable, Received, complited, error etc.)
For each WF SAP MDM assing unique Job ID and this id will be shown in Job ID field in Data Manager WF Tab.
You can change WF list order by all WF fields like as Job ID, Step, User, Start etc. and try to find your's WF.
You can use Java API - this is one of the best solution for WF management and WF mass upload (for example)
Regards
Kanstantsin Chernichenka

Easy way to schedule a job to run for a set period?

Is there an easy way to schedule (dbms_scheduler) a job to run for a set period -say, half an hour- and then to stop.
Currently, I schedule a procedure to do the work (a bunch of inserts or updates, say) and the first line of that procedure assigns sysdate to a variable when it starts. Then as the procedure loops through its work, I compare the current sysdate with that original one, and if the new sysdate>original one by more than 30 minutes, I raise an application error. But it's messy, and I was wondering if there was a nicer way of doing it?

"Admin" -I think you'll find that 'end_time' merely states a time after which the job will not be run. It doesn't do anything to kill off a job which is already running at the time that comes round. Similarly, repeat_interval merely states how often the job should be run, not a time interval within which it must run and outside of which it must stop being run.
Satish: your suggestion looks great. Do you have, or know of, any examples where that is used, though? The doco you pointed to says the parameter raises an event, but that it's up to my event handler to deal with it. I wouldn't have the first idea of how to deal with this in code myself. If I could see a simple example, it would help a lot! Unfortunately, that page doesn't contain such an example!

SQL SERVER AGENT JOB ERROR - SSIS PACKAGE

Hi ,
I have a SQL server agent job which runs SSIS package as the daily job. The SSIS package contains multiple child package. Its a master package which calls other SSIS package. The master package calls 23 SSIS packages, few of the packages runs in parallel.
I am getting the below 2 different errors more frequently. It fails only in the production server, I scheduled the job in UAT server, it did not fail. Also when we run the master package with out sql agent job, it did not fail.
Error 1 :
R6025 - pure virtual function call. The return value was unknown. The process exit code was 255. The step failed.
Error 2 : The step did not generate any output. The return value was unknown. The process exit code was -1073741819. The step failed.
We tried browsing for the answers ,no luck. It failing in live , so we need to run the package manually in live server every time.
Please help me to resolve this issue. Thanks in advance.
Regards,
Dhivya Sivakumar

Hi Vijeth,
Thanks for your reply.
1) Run the Package manually and check whether it runs successfully. -
No Failures. Package completed succesfully
2) If Step 1 is successful,
a) Point the same package to the UAT database and run it and check whether it runs successfully or not. -
We tried to schedule the package almost for 1 month. No failures in UAT.
b) In UAT database, point to the Production database and run the package. - I am not sure, if i can do this.I will try and let you know the result.
These steps will help us identify whether the problems lies within the package or the Environment.
3) Run the Package manually in production Environment using dtexec utilily. -
No Failures. Success.
4) Check the ID used to run the SQL Agent job and modify to an account with elevated permissions or GRANT more permissions to the existing ID. -
The account used currently is having all the privileges. Its the most powerful user in live DB.
Regards,
Dhivya S

Job Error (RUN-050406)

Similar Messages

Maybe you are looking for