ORA-28184: global user cannot have proxy permissions managed in the directory

Cause : The clinet name psecifiedw as a glboal user.

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

Use ALTRE USER t ochange hte type fo user (rfom IDENITFIED GLBOALLY tos omethin gelse, scuh as IDNETIFIED YB passwodr or IDETNIFIED ETXERNALLY.)

update : 20-09-2017
ORA-28184

ORA-28184 - global user cannot have proxy permissions managed in the directory
ORA-28184 - global user cannot have proxy permissions managed in the directory

  • ora-36951 : (XSFCAST28) The ALLOCLAST parameter cannot be set to YES unless PERIODICITY specifies more than one cycle.
  • ora-32013 : failure in verifying parameters from the restored SPFILE
  • ora-13219 : failed to create spatial index table [string]
  • ora-07233 : slemcw: invalid file handle, seals do not match.
  • ora-16641 : failure to acquire broker configuration metadata lock
  • ora-31414 : error(s) occurred during change table advance
  • ora-13515 : Error encountered during Database Usage Statistics capture
  • ora-36904 : (XSAGDNGL44) In AGGMAP workspace object, RELATION workspace object occurs after a dynamic model. The dynamic model must be the last calculation within the AGGMAP.
  • ora-25532 : MTTR specified is too large: string
  • ora-30485 : missing ORDER BY expression in the window specification
  • ora-07496 : sppst: lm_post failed.
  • ora-30502 : system triggers cannot have INSERT, UPDATE, or DELETE as triggering events
  • ora-02815 : Unable to attach shared memory
  • ora-27508 : IPC error sending a message
  • ora-24780 : cannot recover a transaction while in an existing transaction
  • ora-04086 : trigger description too long, move comments into triggering code
  • ora-28003 : password verification for the specified password failed
  • ora-01636 : rollback segment 'string' is already online
  • ora-38708 : not enough space for first flashback database log file
  • ora-13381 : table:string not found in network:string
  • ora-38707 : Media recovery is not enabled.
  • ora-25286 : Invalid number of elements in the message properties array
  • ora-30959 : The indexed column is not stored in CLOB.
  • ora-02479 : error while translating file name for parallel load
  • ora-06743 : TLI Driver: cannot alloc t_bind
  • ora-09844 : soacon: Archmon unable to open named pipe.
  • ora-07715 : sksadtd: could not dismount archival device (SYS$DISMNT failure)
  • ora-19620 : %s is not of string type
  • ora-07616 : $CHANGE_CLASS failed in retrieving the specified device label
  • ora-39961 : message specified was not found
  • Oracle Database Error Messages



    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    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.