title: What happens to schema objects when you DROP USER but don't specify CASCADE?
body: <p>The <a href="http://docs.oracle.com/cd/B19306_01/server.102/b14200/statements_9008.htm" rel="nofollow">Oracle documentation</a> for <code>DROP USER</code> states: 
  "Oracle Database does not drop users whose schemas contain objects unless you specify <code>CASCADE</code>". </p>
  
  <p>My understanding is that all schemas must have an associated user account (though that account can be restricted from use by restricting <code>CREATE SESSION</code> command, etc...). But what actually happens to previously owned objects when you use the <code>DROP USER</code> command? If the user no longer exists... then what account owns those objects?</p>
  
  <p><strong>For Context</strong>, I'm a developer not a DBA and don't have DCL rights on my databases so I can't test this out myself. I am working a migration project where this command may be necessary but I'd like to better understand the implications before passing a request along to my Enterprise DBA team. </p>