DBAsupport.com Forums - Powered by vBulletin
Results 1 to 6 of 6

Thread: error using drop user cascade?

  1. #1
    Join Date
    Dec 2000
    Posts
    18

    Question

    need your opinion;

    issued a command:

    drop user abc cascade;

    result was
    error occurred at recoursive SQL Level1
    table or view does not exsist

    I connected using system.

    viewed the user_tables, there are tables of the user, what could be the problem.

    thanks

  2. #2
    Join Date
    Jan 2001
    Posts
    3
    [QUOTE][i]Originally posted by gma800 [/i]
    [B]need your opinion;

    issued a command:

    drop user abc cascade;

    result was
    error occurred at recoursive SQL Level1
    table or view does not exsist

    I connected using system.

    viewed the user_tables, there are tables of the user, what could be the problem.

    thanks [/B][/QUOTE]

    REPLAY :

    The reason may be talbes are being used .
    Try to drop tables first .


  3. #3
    Join Date
    Dec 2000
    Posts
    10

    Smile

    hi,

    U first login as system or sys to drop that user. It definately works if u've login as sys or system. Then give drop user (username) cascade.

    Be sure at that time no one is working under that user.


  4. #4
    Join Date
    Jan 2001
    Posts
    36
    I use 'drop user username cascade' on a daily basis.
    I usually login as SYS, but I think SYSTEM is also OK.
    You don't have to drop any of the users tables,before you
    drop the user.
    Cascade does that for you.



  5. #5
    Join Date
    Apr 2000
    Location
    Baltimore, MD
    Posts
    759
    This happened to me once. Turns out that some of the AQ tables were missing.

  6. #6
    Join Date
    Jan 2001
    Posts
    36
    Had an 8i database once where the User simply refused to be dropped !!
    To this day we have no idea what caused the problem. A junior developer wrote some PLSQL code using TOAD, and somehow managed to compile a package/procedures that REFUSED to be dropped, no matter what.
    (the procedures called each other in a strange fashion)

    Cascade did not work.
    Drop package/procedure did not work.

    Eventually exporting valid users, dropping the database and re-creating the database was the only solution.


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  


Click Here to Expand Forum to Full Width