cancel
Showing results for 
Search instead for 
Did you mean: 

Too Many Uncompressed Requests in info cube..

former_member267533
Participant
0 Kudos

Hi All,

I was trying to compress the cubes which are having more uncompressed requests. I wondered for month uncompressed requests job is taking around 32000+ secs. when I check the job log it is taking for changing the Request status from 2/2 to 7/7 and for 7/7 to 8/8.

DB: Oracle 11.2.2.
for moving data from F table to E table is not taking time. for 1 yr requests job took around 12 Days to complete.

Can some help on this.

DebjitSingha
Active Contributor
0 Kudos

Just wanted to check if you tried the suggested solutions.

Thanks,
Debjit

DebjitSingha
Active Contributor
0 Kudos

Just wanted to check if you tried the suggested solutions.

Thanks,
Debjit

Accepted Solutions (0)

Answers (3)

Answers (3)

bhavinvyas
Active Contributor

Please refer following wiki and KBA,

https://wiki.scn.sap.com/wiki/display/BI/OT-DBIF-CON-LR

1778638 - Important facts concerning the compression of InfoCubes

Thanks,

Bhavin

VijayetaSharma
Active Contributor
0 Kudos

Try below KBA, it helped us with GL line item cube compression

590370

Thanks,

Vijayeta

DebjitSingha
Active Contributor
0 Kudos

Hello bellala.vijayakumar,

We had this issue couple years back when we started supporting a new client. Here are some steps we have taken to compress cubes and some issues we faced.

RSMDATASTATE - Status of the data in the Infocubes 'compr-dual'-flag gives the compression information.

BW Compression Issue-

http://wiki.scn.sap.com/wiki/display/BI/OT-DBIF-CON-LR

  • 407260 - FAQs: Compression of InfoCubes
  • 590370 - Too many uncompressed request (f table partitions)
  • 1778638 - Important Facts concerning the compression of InfoCubes
  • 1472386 - 'ORA-04031 out of memory error in BW systems'.
  • 430486 - Overview/repair of F fact table of an BW InfoCube

To speed up the compression in partitioned cube, delete E-Fact indexes and then manually create BitMap index on “T” index. Be careful as from SE14 by default we might create B-Tree instead of BitMap index. How to create BitMap index (SE14)

Last but not the least, I suggest createing a weekly PC to take care of below tasks.

Weekly BW Maintenance:

  1. PSA Cleanup
  2. Change log cleanup
  3. Cube Compression
  4. Delete Temp tables : SE38 : SAP_DROP_TMPTABLES
  5. Delete Stats : SE38 : RSDDSTAT_DATA_DELETE
  6. Delete Error Log : SE38 : RSBM_ERRORLOG_DELETE
  7. Delete DTP Temp and Msg: SE38 : RSBATCH_DEL_MSG_PARM_DTPTEMP
  8. Repair Cube Indexes : SE38 : SAP_INFOCUBE_INDEXES_REPAIR
  9. Collect Cube Stats : SE38 : SAP_ANALYZE_ALL_INFOCUBES

Hope this helps.

Viewers/ readers - If you find above information helpful, feel free to up-vote (arrows on left side).

Thanks,

Debjit