Tuesday, May 19, 2009

Warning: View created with compilation errors.

During compilation of view I got the following error:

Warning: View created with compilation errors.

Show err gives No Errors.
SQL> SQL> show err
No errors.

With the following select statement it is possible to find the error:

select text from dba_errors where name = '[OBJECT_NAME]' and owner = '[OBJECT_OWNER]';

Did this post help you in any way can you please leave a comment? This will motivate me writing more posts.

27 comments:

  1. That's because show errors only shows the *last* error.

    Cheers.

    ReplyDelete
  2. You can also use SQL> show error view :view_name to see errors related to a particular view.

    ReplyDelete
  3. yes helped me - thanks

    ReplyDelete
  4. Great stuff, thanks. Saved me from bothering our senior ^^

    ReplyDelete
  5. Just the trick I needed - a hell of a lot easier than tracking down a legacy version of EMC.

    ReplyDelete
  6. mine is more complicated than that. I have two scripts linked by a UNION statement. Previous version worked OK but after making a change in one of the steps I get this %^&* error message. Obviously, some thing is rotten in the linkages but darned if I can find it.

    ReplyDelete
  7. Very helpful! Thanks!

    ReplyDelete
  8. I tried this but it failed since I am not a DBA and have no access to DBA_ERRORS. But when I simplified it to:

    select text from user_errors where name = 'object_name';

    It worked. Thanks for putting me on the right track.

    ReplyDelete
  9. A tip I found on OTN was to NOT use FORCE keyword. I did that and the CREATE statement showed the error that led me to a solution.

    ReplyDelete
    Replies
    1. omiting d use of FORCE keywork @least till d compilation is d better option, given an inside view of ver exactly d developer made d mistake.

      And this really did helped me.

      Delete
  10. Helped me quickly. Thanks 1

    ReplyDelete
  11. Saved me a lot of time, Thanks!!

    ReplyDelete
  12. Thanks a Lot, was very helpfull and saved the valuable time....

    ReplyDelete
  13. Thank you!! All I was getting was compliation errors and show error said no errors but the query showed me the problem. This was a great tip!! Nick

    ReplyDelete
  14. I have DBA privileges
    Query did not show me any errors
    SHOW ERROR also did not show me any errors
    Removing FORCE key work actually showed me error

    ReplyDelete

  15. SQL> SHOW ERROR TRIGGER trigger_name

    ReplyDelete
  16. Good tip, worked for me.

    ReplyDelete
  17. select * from user_errors;

    It also helps a lot.

    ReplyDelete
  18. Thanks for the info Arjan :)

    ReplyDelete
  19. Excellent. Thanks. All earlier options didn't show the error. Only after removing 'FORCE' error got displayed.

    ReplyDelete
  20. Thanks man! this info helped me to resolve the issue.. :)

    ReplyDelete
  21. Thank you..it helped me... :)

    ReplyDelete

comment