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-05-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-30454 : summary contains STDDEV without corresponding SUM & COUNT
  • ora-22606 : pickler image handle [string] is not well-formed
  • ora-26576 : cannot acquire SR enqueue
  • ora-12620 : TNS:requested characteristic not available
  • ora-40215 : model string is incompatible with current operation
  • ora-12596 : TNS:internal inconsistency
  • ora-31613 : Master process string failed during startup.
  • ora-31453 : invalid value string for parameter, expecting: Y, N, or NULL
  • ora-30400 : identical JOIN KEY clauses
  • ora-19118 : duplicate default namespace definition - string
  • ora-22899 : cannot specify both scope and rowid constraint on ref column
  • ora-10361 : check buffer change vector count consistency
  • ora-10282 : Inhibit signalling of other backgrounds when one dies
  • ora-10266 : Trace OSD stack usage
  • ora-24183 : invalid transformation
  • ora-38414 : invalid datatype for the attribute string
  • ora-31212 : DBMS_LDAP: PL/SQL - Invalid LDAP mod_array.
  • ora-04028 : cannot generate diana for object stringstringstringstringstring
  • ora-36671 : (XSDPART09) Leaves of workspace object have different datatypes. A partition dimension cannot have more than one datatype when RANGE partitioning is used.
  • ora-30726 : cannot specify referenced column list here
  • ora-39022 : Database version string is not supported.
  • ora-01640 : cannot make tablespace read only with active transactions
  • ora-01073 : fatal connection error: unrecognized call type
  • ora-14512 : cannot perform operation on a clustered object
  • ora-25119 : LOGGING/NOLOGGING option already specified
  • ora-28345 : cannot downgrade because there exists encrypted column
  • ora-22324 : altered type has compilation errors
  • ora-09921 : Unable to get information label from connection
  • ora-00405 : compatibility type "string"
  • ora-31206 : DBMS_LDAP: PL/SQL - Invalid LDAP search scope.
  • 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.