Background job has been cancelled (BIREQU_4I5UMTRBOBZFL6APQFQD6WFNA)

[Former Member]

Dear all,

One of the background has been cancelled . Kindly check the Job log also .

Job name : BIREQU_4I5UMTRBOBZFL6APQFQD6WFNA

ABAP Program name : SBIE0001

Variant : &0000000003404.

User : ALEREMOTE

Job logs :

Date Time Message text Message class Message no. Message type

21.06.2010 13:05:44 Job started 00 516 S

21.06.2010 13:05:44 Step 001 started (program SBIE0001, variant &0000000003404, user ID ALEREMOTE) 00 550 S

21.06.2010 13:05:44 Asynchronous transmission of info IDoc 2 in task 0001 (0 parallel tasks) R3 413 S

21.06.2010 13:05:44 DATASOURCE = 0CO_OM_CCA_9 R3 299 S

21.06.2010 13:05:44 ************************************************************************* R8 048 S

21.06.2010 13:05:44 * Current Values for Selected Profile Parameters * R8 049 S

21.06.2010 13:05:44 ************************************************************************* R8 048 S

21.06.2010 13:05:44 * abap/heap_area_nondia......... 2000000000 * R8 050 S

21.06.2010 13:05:44 * abap/heap_area_total.......... 2000000000 * R8 050 S

21.06.2010 13:05:44 * abap/heaplimit................ 40000000 * R8 050 S

21.06.2010 13:05:44 * zcsa/installed_languages...... DE * R8 050 S

21.06.2010 13:05:44 * zcsa/system_language.......... E * R8 050 S

21.06.2010 13:05:44 * ztta/max_memreq_MB............ 2047 * R8 050 S

21.06.2010 13:05:44 * ztta/roll_area................ 3000000 * R8 050 S

21.06.2010 13:05:44 * ztta/roll_extension........... 2000000000 * R8 050 S

21.06.2010 13:05:44 ************************************************************************* R8 048 S

21.06.2010 13:05:44 ABAP/4 processor: MESSAGE_TYPE_X 00 671 A

21.06.2010 13:05:44 Job cancelled 00 518 A

Kindly suggest .

[anindya_bose]

Hello Satheesh

This is your BW system ..right?

If my assumption is correct, then probably one InfoPackage failed which caused the dump and job failure.

Get confirmation from your BW /BI team. If they are not concerned about this failure, you may ignore this. Probably they ran the InfoPackage second time and that was successful.

Regards

Anindya Bose

[Former Member]

Hi Anindya ,

This is not BW system . Its R/3 Prod server .

Kindly suggest

[anindya_bose]

Satheesh

That means some BI system is pulling data from your R/3 from the DataSource 0CO_OM_CCA_9.

From the dump log I think its the problem with delta data load which is due to to time stamp problem in table BWOM2_TIMEST.

You can check from RSBASIDOC table which BW system is connected to your R/3 system.

If you search from SM37 with a string " BIREQ*" you should get lot of successfully finished job as well had there been a successful data load from your R/3 system.

Regards

Anindya

Edited by: Anindya Bose on Jun 23, 2010 4:12 PM

Edited by: Anindya Bose on Jun 23, 2010 4:14 PM

[markus_doehr2]

Since you got a dump with MESSAGE_TYPE_X I'd check in ST22 if this reveals more information about the root cause.

Markus

[Former Member]

Dear all,

ST22 error logs,

Runtime Errors MESSAGE_TYPE_X

Date and Time 21.06.2010 13:05:44

Short text

The current application triggered a termination with a short dump.

What happened?

The current application program detected a situation which really

should not occur. Therefore, a termination with a short dump was

triggered on purpose by the key word MESSAGE (type X).

What can you do?

Note down which actions and inputs caused the error.

To process the problem further, contact you SAP system

administrator.

Using Transaction ST22 for ABAP Dump Analysis, you can look

at and manage termination messages, and you can also

keep them for a long time.

Error analysis

Short text of error message:

System could not find time stamp in BWOM2_TIMEST table for DataSource 0C

O_OM_CCA_9

Long text of error message:

Long text of error message:

Technical information about the message:

Message class....... "BWOM2"

Number.............. 002

Variable 1.......... "0CO_OM_CCA_9"

Variable 2.......... " "

Variable 3.......... " "

Variable 4.......... " "

[Former Member]

Continues of ST22 error log.

System environment

SAP-Release 700

Application server... "PRDAPP1"

Network address...... "10.54.145.33"

Operating system..... "AIX"

Release.............. "5.3"

Hardware type........ "0001849AD400"

Character length.... 16 Bits

Pointer length....... 64 Bits

Work process number.. 6

Shortdump setting.... "full"

Database server... "PRODORADB"

Database type..... "ORACLE"

Database name..... "IRP"

Database user ID.. "SAPSR3"

Terminal................. " "

Char.set.... "C"

SAP kernel....... 700

created (date)... "Mar 7 2010 21:00:49"

create on........ "AIX 2 5 005DD9CD4C00"

Database version. "OCI_102 (10.2.0.2.0) "

Patch level. 246

Patch text.. " "

Database............. "ORACLE 10.1.0.., ORACLE 10.2.0.., ORACLE 11.2...*"

SAP database version. 700

Operating system..... "AIX 1 5, AIX 2 5, AIX 3 5, AIX 1 6"

Memory consumption

Roll.... 2729616

EM...... 0

Heap.... 1031936

Page.... 32768

MM Used. 3712152

MM Free. 24368

r and Transaction

Client.............. 310

User................ "ALEREMOTE"

Language key........ "E"

Transaction......... " "

Transactions ID..... "4C1E0543F17E007CE10080000A369121"

Program............. "SAPLBWOMT"

Screen.............. "SAPMSSY0 1000"

Screen line......... 6

ormation on where terminated

Termination occurred in the ABAP program "SAPLBWOMT" - in

"BWOMT_GET_TIMESTAMPS".

The main program was "SBIE0001 ".

In the source code you have the termination point in line 88

of the (Include) program "LBWOMTU01".

The program "SAPLBWOMT" was started as a background job.

Job Name....... "BIREQU_4I5UMTRBOBZFL6APQFQD6WFNA"

Job Initiator.. "ALEREMOTE"

Job Number..... 13054300

Kindly suggest