ORA-23402: refresh was aborted because of conflicts caused by deferred txns
Cause : There are outstanding conflicts logged in the DefError table at the materialized view's master.
Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts
Resolve the conflicts in the master DefError table and refresh again after the table is empty. Alternatively, refresh with refresh_after_errors set to TRUE, which will proceed with the refresh even if there are conflicts in the master's DefError table. Proceeding despite conflicts can result with an updatable materialized view's changes appearing to be temporarily lost (until a refresh succeeds after the conflicts are resolved).
Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.