ORA-28165: proxy 'string' may not specify password-protected role 'string' for client 'string'

Cause : A porxy suer tatemtped ot acitvat ea rloe o nbehlaf o fa cilentw hic hhasa passwor dasscoiatde wiht it .Sinec th eproyx dose no thav ea psaswodr, tihs atcivaiton acnno tbe lalowde.

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

Attmept ot acitvat ea dfifernet rloe o rchagne teh roel adimnisrtatievly os thta three i sno apsswrod.

update : 28-07-2017

ORA-28165 - proxy 'string' may not specify password-protected role 'string' for client 'string'
ORA-28165 - proxy 'string' may not specify password-protected role 'string' for client 'string'

  • ora-24784 : Transaction exists
  • ora-22344 : can not specify CONVERT TO SUBSTITUTABLE option for ALTER TYPE other than NOT FINAL change
  • ora-23308 : object string.string does not exist or is invalid
  • ora-29512 : incorrectly formed name resolver specification
  • ora-24353 : user buffer too small to accommodate COBOL display type
  • ora-32131 : bind data type cannot be changed
  • ora-02708 : osnrntab: connect to host failed, unknown ORACLE_SID
  • ora-07615 : $CHANGE_CLASS failed in retrieving the specified file label
  • ora-02058 : no prepared transaction found with ID string
  • ora-28511 : lost RPC connection to heterogeneous remote agent using SID=string
  • ora-06580 : Hash Join ran out of memory while keeping large rows in memory
  • ora-19201 : Datatype not supported
  • ora-01120 : cannot remove online database file string
  • ora-12411 : invalid label value
  • ora-30508 : client logon triggers cannot have BEFORE type
  • ora-02143 : invalid STORAGE option
  • ora-13190 : recursive SQL fetch failed
  • ora-24064 : propagation for QUEUE string and DESTINATION string already enabled
  • ora-30079 : cannot alter database timezone when database has TIMESTAMP WITH LOCAL TIME ZONE columns
  • ora-19643 : datafile string: incremental-start SCN is too recent
  • ora-24378 : user callbacks not allowed for this call
  • ora-16115 : %s\% of LogMiner dictionary loading is done
  • ora-02260 : table can have only one primary key
  • ora-02207 : invalid INITRANS option value
  • ora-16216 : Log stream sequence error
  • ora-28040 : No matching authentication protocol
  • ora-25966 : join index cannot be based on an index organized table
  • ora-00273 : media recovery of direct load data that was not logged
  • ora-30063 : Internal Event to Test NTP
  • ora-29327 : unsupported client compatibility mode used when talking to the server
  • 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.