Skip to Content
0
Former Member
Mar 03, 2009 at 05:34 PM

Sybase - Bad system message. Message text from the child process is..

213 Views

Hi,

I am running DS 3.1 level SP1 with an sybase repo on Solaris plattform and do often get an error situation like "...child prosess is.." <blank> or as shown in the log below.

-


26106 10 RUN-050406 03.03.2009 08:01:34 |Session INTRANETT_FEILMELDINGER_JOB|Workflow POST_INTRANETT_WF|Workflow STG_IRMA_SERIAL_ORDER_HIST_TAB_WF|Dataflow STG_IRMA_SERIAL_ORDER_HIST_TAB_DF

26106 10 RUN-050406 03.03.2009 08:01:34 Data flow <STG_IRMA_SERIAL_ORDER_HIST_TAB_DF> received a bad system message. Message text from the child process is

26106 10 RUN-050406 03.03.2009 08:01:34 <2_4cb6_80e6_790004786e7c.txt"-z"/app/bodi/dataservices/log/diserver21_js2/bodirep_bodi_prod_bodi_prod/error_03_03_2009_08_00_01

26106 10 RUN-050406 03.03.2009 08:01:34 145_d153bb7f_4232_4cb6_80e6_790004786e7c.txt"-w"/app/bodi/dataservices/log/diserver21_js2/bodirep_bodi_prod_bodi_prod/monitor_

26106 10 RUN-050406 03.03.2009 08:01:34 03_03_2009_08_00_01_145__d153bb7f_4232_4cb6_80e6_790004786e7c.txt"-r1000-RRepository-Ubodi_prod-h-P;520EECB019C0AEEE71CD997B5EF6

26106 10 RUN-050406 03.03.2009 08:01:34 EC65FA2E83E269876B66A9B7EE4461B4E3E8-SBODIREP-NSybase-Qbodi_prod-Cjdiserver21-Cp3700-Cn-m"STG_IRMA_SERIAL_ORDER_HIST_TAB_DF:STG_

26106 10 RUN-050406 03.03.2009 08:01:34 IRMA_SERIAL_ORDER_HIST_TAB_WF"-B"2009030308000326106001_1"-nParentContext/INTRANETT_FEILMELDINGER_JOB/POST_INTRANETT_WF/STG_IRMA

26106 10 RUN-050406 03.03.2009 08:01:34 SERIALORDER_HIST_TAB_WF/STG_IRMA_SERIAL_ORDER_HIST_TAB_DF@@00000-207155849403031090800142610601000000000000094950007-Ch566-Ser

26106 10 RUN-050406 03.03.2009 08:01:34 verGroup-ClusterLevelJOB-KdcP26106-KdcIDU7==========================================================

26106 10 RUN-050406 03.03.2009 08:01:34 Please collect the following and send to Customer Support:

26106 10 RUN-050406 03.03.2009 08:01:34 1. Log files(error_, monitor_, trace_*) associated with this failed job.

26106 10 RUN-050406 03.03.2009 08:01:34 2. Exported Atl file of this failed job.

26106 10 RUN-050406 03.03.2009 08:01:34 3. DDL statements of tables referenced in this failed job.

26106 10 RUN-050406 03.03.2009 08:01:34 4. Data to populate the tables referenced in the failed job. If not possible, get the last few rows (or sample of them) when

26106 10 RUN-050406 03.03.2009 08:01:34 the job failed.

26106 10 RUN-050406 03.03.2009 08:01:34 5. Core dump, if any, generated from this failed job.

-


I then run it again manually without problems.

Any ideas..?

Regards,

- jem