BW batch job in r/3 taking long time.

[Former Member]

Hi SAP experts,

Please help me resolving this issue.

Issue :

BW batch job in r/3 taking long time and failed with error. This is delta load usually finished in 15- 20 mins, but from last 2 days, this BW batch job is taking every long time and failing with error.

details of job runs:

on 31.01.2012, BW batch job took around 7 hours and extracted 208 records.

on 01.02.2012 BW batch job took around 10 hour and extracted 802 records

Today batch job took around 11 hours and failed with following error message.

Job started

Step 001 started (program SBIE0001, variant &0000000106933, user name BWALEREMOTE)

DATASOURCE = ZEXTRACT_ACTUALS

• Current values of selected profile parameter *

• abap/heap_area_nondia......... 2000683008 *

• abap/heap_area_total.......... 2000683008 *

• abap/heaplimit................ 40894464 *

• zcsa/installed_languages...... E2 *

• zcsa/system_language.......... E *

• ztta/max_memreq_MB............ 64 *

• ztta/roll_area................ 6500000 *

• ztta/roll_extension........... 2000683008 *

0 LUWs confirmed and 0 LUWs to be deleted with FB RSC2_QOUT_CONFIRM_DATA

ABAP/4 processor: DBIF_RSQL_SQL_ERROR

Job cancelled

Details of the data source:

It is "Z" data source, created on view (View joining 6 table(all stand tables))

I have checked with basis for available resources, increased priority of the job.

Please help

Thanks and Regards

Chakri

[Former Member · Accepted solution]

Hi,

Please refer below thread

Thanks,

[Former Member · Accepted solution]

Hi Gaurav,

Thank you for quick reply, i have checked the ST22 for ABAP DUMP, and the error message as follows.

Database error text........: "ORA-01555: snapshot too old: rollback segment

number 20 with name "_SYSSMU20$" too small#"

Internal call code.........: "[RSQL/FTCH/ZBW_ACT ]"

Please check the entries in the system log (Transaction SM21).

I have also checked SM21 following is the error.

BY4 Database error 1555 at FET access to table ZBW_ACT

BY0 > ORA-01555: snapshot too old: rollback segment number 20 with

BY0 > name "_SYSSMU20$" too small#

AB0 Run-time error "DBIF_RSQL_SQL_ERROR" occurred

AB1 > Short dump "120201 140214 sapapp2 BWALEREMOTE " generated

D01 Transaction termination 00 671 ( DBIF_RSQL_SQL_ERROR 20120201140214sapapp2 BWALEREMOTE 8001 )

I have also checked for indexing on the View(ZBW_ACT) and also on the tables.

Thanks and Regards

Chakri

[Former Member · Accepted solution]

Hi,

Check the OSS;

Note 600141 - Oracle9i: Automatic UNDO Management

Note 3807 - Error messages regarding rollback and undo segments

You may need to work with the DBA team in order to solve this issue. Show them the error message and OSS notes.

Hope this will help you to analyse the issue further.

Regards,

Sunil

[Former Member · Accepted solution]

Hi Chakri,

Check with your oracle DBA once.

If you have indexes on standard table, please re-create the indexes once again. It should work.

Regards,

Venkatesh

[Former Member · Accepted solution]

Hi All ,

Thank you for your replies.

I have checked SAP Notes 066141 and 3807, i have checked with basis team regarding error message "ORA-01555: Snap shoot too old", they has informed that table space has increased to 20 GB.

The data source effected is customized data source build on view, i have checked for indexes on the table. Data source is delta extraction and Time Stamp field as delta relevant field.

After talking to basis team, i assume the issue is as follows(Please correct me if assumption is wrong ).

1. Once BW job executed in BW systems, a batch job is created in R/3, first step has been executed successfully and while fetching data from database according to selection condition defined in View data is been extracted to BW. i assume that issue is been occurring at this stage.

2. The same Job used to completed in in 10 - 15 min before, but from last 3 days job is taking very long time around 10 hours nothing has changed in BW and R/3 System. i am unable to understand how to approach to this issue.

Please help step to know the core reason for this issue.

Thanks and Regards

Chakri

[Former Member · Accepted solution]

Hi Chakri,

Yes, you have identified the issue. if you have indexes on your base tables , try to create them once again, it will work.

Regards,

Venkatesh

[sven_mader2]

Hi,

check the ABAP code

check the SQL statement -> do you use a db index?

Sven