Solution : https://service.sap.com/sap/support/notes/181945 (SAP Service marketplace login required)
Key words :
homepage business information warehouse->services & implementation->sap bw asap->bw asap, transaction spro --> sap reference img --> business information warehouse --> general bw settings --> aggregates, golden rules------------- adjust shared memory und pdq parameters, temporary dbspaces informix pdq storage parameters additional onconfig parameters 3, informix - onconfig parameters logical und physical logs size, hkey_local_machine->software->informix->online-> <servername> -> env, long transaction high water mark parameters, blocksize > nof rows basiscube / nof fragments, informix pdq storage parameters------------------------------- buffers, extras -> maintain db storage parameters
Related Notes :
| 571744 | SAPBWNews BW 3.1 Content Support Package 10 |
| 571698 | SAPBWNews BW 3.0B Support Package 15 |
| 567745 | Composite note BW 3.x performance: DB-specific setting |
| 548943 | FAQ: Avoiding disk space problems |
| 523278 | SAPBWNews BW 3.0B Support Package 13 |
| 523204 | SAPBWNews BW 2.1C Support Package 24 |
| 523191 | SAPBWNews BW 2.0B Support Package 32 |
| 434194 | SQL error -208 for BW/APO/CRM on Informix |
| 368859 | Open SQL queries with PDQ occupy resources for too long |
| 192658 | Setting parameters for BW systems |
| 184905 | Collective note Performance BW 2.0 |
| 130253 | General tips on uploading transaction data to BW |