We have load jobs running in the night. DBC diskspace getting filled rapidly. I can see it in the view point, it raises from 11% to 80 %. or some time it reaches 100 % and all the jobs get failed. My question is, IS DBC Diskspace filling is normal ?. is there a way to reduce it to keep the jobs running.
Most likely, this is due to WAL space (DBC.TransientJournal) holding uncommited insert / update / delete information, in case a transaction aborts.
Perhaps you need to commit / checkpoint more frequently, or do more "bulk" operations versus transactions that contain multiple reqeusts.