1-Upgrade your DB to 10.2.0.5 release where bug solved.
2-Apply the patch 6709070 for your DB release:
1. Download and review the readme and pre-requisites for Patch 6709070.