XL reporter disk usage
We are currently experiencing hangups while generating reports via XL reporter,
noticed that DISK WRiTE and READ is way up during this process, Ruled out CPU, memory and network issues.
currently running on RAID 10 configuration. we are planning to migrate SAPB1 and XLR databases to a storage to utilize multiple spindles.
has any body had the same experience? any suggestion?or will the migration work.
I would appreciate any input