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 : 24-07-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-14263 : new subpartition name must differ from that of any other subpartition of the object
  • ora-00026 : missing or invalid session ID
  • ora-28041 : Authentication protocol internal error
  • ora-37999 : Serious OLAP error: string. Please contact Oracle Technical Support.
  • ora-28181 : proxy 'string' failed to enable one or more of the specified initial roles for client 'string'
  • ora-33223 : (CMOVE03) You cannot move a session-only dimension value.
  • ora-02172 : The PUBLIC keyword is not appropriate for a disable thread
  • ora-16603 : Data Guard broker detected a mismatch in configuration ID
  • ora-13423 : invalid cell coordinate parameter
  • ora-22878 : duplicate LOB partition or subpartition specified
  • ora-22151 : cannot resize non-zero variable-length array to zero elements
  • ora-09838 : removeCallback: failure removing the callback port.
  • ora-33068 : (XSAGDNGL33) In AGGMAP workspace object, the hierarchy dimension QDR over dimension workspace object must specify a positive dimension offset.
  • ora-38716 : Must supply an integer for the TYPE option.
  • ora-38304 : missing or invalid user name
  • ora-19010 : Cannot insert XML fragments
  • ora-14039 : partitioning columns must form a subset of key columns of a UNIQUE index
  • ora-19765 : mount id string does not match mount id string in control file
  • ora-32109 : invalid column or parameter position
  • ora-15007 : name is already used by an existing template
  • ora-30571 : invalid SEGMENT SPACE MANAGEMENT clause
  • ora-00392 : log string of thread string is being cleared, operation not allowed
  • ora-19718 : length for command id longer than string
  • ora-01270 : %s operation is not allowed if STANDBY_PRESERVES_NAMES is true
  • ora-30752 : column or table string is not substitutable
  • ora-00018 : maximum number of sessions exceeded
  • ora-08008 : another instance is mounted with USE_ROW_ENQUEUES = string
  • ora-09285 : sllfop: unrecognizable processing option, incorrect format
  • ora-09969 : unable to close or remove lock file
  • ora-30134 : reserved for future use
  • 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.