Hi Dilip
Ok, if that KBA is not that issue, then the most likely cause is simply that the dump process got interrupted. I don't think it is a write permission issue. This is indeed a large size database to dump to a single stripe. The longer it runs, the bigger the chance that something will happen, but this would be an external factor of some sort. Judging by the message, it is network related (Broken pipe) :
Emulator interprocess communication failed with error state = 16, error code=32, system message=Broken pipe.
The output also points to this command to get error details :
Run "omnidb -session 2016/02/25 0118 -report"
Does that provide any more clues to a cause ?
As this looks like a one-off , I do not believe there is an ASE / BS issue here.
Kind regards
Bart