We have a user who is performing a query sleection on a virtualized view.
The customer has tried two different approaches to complete the query. One, with DATA MOVEMENT ENABLED. And another with DATA MOVEMENT DISABLED.
with DATA_MOVEMENTPLAN enabled - ERROR - UNSUCCESSFUL EXECUTION DUE TO RESOURCE LIMIT BEING EXCEEDED. this is set on the DATABASE level (DB2PROD). DB2PROD is CANCELLING the query due to using too much CPU. OPTION: Work with DBA to increase CPU allotment (not likely to win that battle)
with DATA_MOVEMENTPLAN disabled- ERROR - No space left on device (this is because data_movement plan is not enabled and the temporary data must be stored on the server / box itself using memory or disk space. This is hitting a maximum. OPTION: Dig into 'no space available' and work to increase that space.
Questions: What space is being eaten up on the server and hitting max? How can the user complete the query?