Hi experts,
We have a BI 7.0 system and ECC6 system.
I would like to consult the issue that I encountered in extraction of 0FI_GL_10. There are no changes in the system and the extraction is running already for 3 months but last Tuesday we encountered a long running time of job in ECC6.
1st loading scenario:
This is the sm37 of ECC6.
Date Time Message text
09.07.2013 01:05:28 Job started
09.07.2013 01:05:28 Step 001 started (program SBIE0001, variant &0000000012629, user ID RFCUSER)
09.07.2013 01:05:28 Asynchronous transmission of info IDoc 2 in task 0001 (0 parallel tasks)
09.07.2013 01:05:28 DATASOURCE = 0FI_GL_10
09.07.2013 01:05:28 RLOGSYS = XXXXXXXXXX (I manually hide this line)
09.07.2013 01:05:28 REQUNR = REQU_DFLNNZ419SPK0K6VBPWB7ZJEX
09.07.2013 01:05:28 UPDMODE = D
09.07.2013 01:05:28 LANGUAGES = *
09.07.2013 01:05:28 *************************************************************************
09.07.2013 01:05:28 * Current Values for Selected Profile Parameters *
09.07.2013 01:05:28 *************************************************************************
09.07.2013 01:05:28 * abap/heap_area_nondia......... 0 *
09.07.2013 01:05:28 * abap/heap_area_total.......... 8388608000 *
09.07.2013 01:05:28 * abap/heaplimit................ 40000000 *
09.07.2013 01:05:28 * zcsa/installed_languages...... EJ2 *
09.07.2013 01:05:28 * zcsa/system_language.......... E *
09.07.2013 01:05:28 * ztta/max_memreq_MB............ 2047 *
09.07.2013 01:05:28 * ztta/roll_area................ 6500000 *
09.07.2013 01:05:28 * ztta/roll_extension........... 2000000000 *
09.07.2013 01:05:28 *************************************************************************
09.07.2013 01:05:31 281 LUWs confirmed and 281 LUWs to be deleted with function module RSC2_QOUT_CONFIRM_DATA
09.07.2013 07:17:37 Job cancelled due to system shutdown
The job was cancelled because we have a system restart during 7:17:37. As indicated above we have a long running of job.
In BW 0 data was extracted and prompted an error in source system.
I put the RSMO status to red and delete the request in PSA.
2nd loading scenario:
I reloaded the delta again and prompted repeat last of delta.
The extraction was successful but I got 0 data the QM status is green. This is impossible since we have new data in FAGLFLEXT.
3rd loading scenario:
I triggered another delta and I see it was a long running job so I terminated it.
I checked the SM37 of ECC6 while the job is running this is the job log.
In sm51 I confirmed that the job is running but only direct read and sequential read is updating, insert record is still 0 for 4hrs
09.07.2013 11:59:28 Job started
09.07.2013 11:59:28 Step 001 started (program SBIE0001, variant &0000000012629, user ID RFCUSER)
09.07.2013 11:59:28 Asynchronous transmission of info IDoc 2 in task 0001 (0 parallel tasks)
the job is stuck for 4hrs in that process so I terminated it.
I put the QM status of 2nd loading scenario to red.
4th loading.
I requested another delta but did not prompt repeat last delta since I already changed the QM status to red.
the job was also stuck like what happened in 3rd loading scenario.
I already checked SM58 if there are stuck RFC, bwom2_timest, bwom2_timest, bwom_settings and everything is correct. I already checked if I have enough background process, RFC connection issues, BD84, check connection of source system in BW side and no issues was detected.
We don't have any changes in BW or ECC6 when this error occured.
I also checked the table FAGLFLEXT and I confirmed that there are new data based on the timestamp pointer in RSA7.
My last resolution is delete the 0FIGL_010 queue in RSA7. delete the initialization in BW Infopackage and proceed with initialize with data transfer. But as much as possible I want to fix the issue with other solution and know possible root cause of it.
My question can you provide some solution to fix this issue aside from my solution?
I hope you can share your idea on this.
Thank you very much.