ORA-28168: attempted to grant password-protected role

Cause : An ALTER USER ... GRANT CONNECT command was attempted specifying a role that is protected by a password as a role which the proxy may execute on behalf of a client.

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

Either specify a role that does not have a password or alter the role so that a password is not required.

update : 28-05-2017
ORA-28168

ORA-28168 - attempted to grant password-protected role
ORA-28168 - attempted to grant password-protected role

  • ora-16100 : not a valid Logical Standby database
  • ora-30150 : Invalid argument passed to OCIFile function
  • ora-02092 : out of transaction table slots for distributed transaction
  • ora-13835 : invalid attribute name specified
  • ora-01299 : dictionary string corresponds to a different database incarnation
  • ora-24400 : error occured while creating connections in the pool
  • ora-22913 : must specify table name for nested table column or attribute
  • ora-13447 : GeoRaster metadata BRS error
  • ora-31671 : Worker process string had an unhandled exception.
  • ora-30118 : syntax error at 'string' at the end of input
  • ora-24202 : publisher does not exist for the queue
  • ora-13231 : failed to create index table [string] during R-tree creation
  • ora-25112 : maximum number of BITMAP index columns is 30
  • ora-30192 : reserved for future use
  • ora-06757 : TLI Driver: server got bad command
  • ora-06115 : NETTCP: unable to create ORACLE logicals
  • ora-39762 : streams must be loaded in conversion order
  • ora-36686 : (XSDPART24) Value number is not in partition number.
  • ora-27122 : unable to protect memory
  • ora-13916 : Invalid value "string" specified for parameter "string"
  • ora-13360 : invalid subtype in a compound type
  • ora-29272 : initialization failed
  • ora-13514 : Metric Capture too close to last capture, group string
  • ora-10943 : trace name context forever
  • ora-15193 : Internal ASM tracing event number 15193
  • ora-24353 : user buffer too small to accommodate COBOL display type
  • ora-22894 : cannot add constraint on existing unscoped REF columns of non-empty tables
  • ora-37104 : (XSVPART04) A partitioned variable must be dimensioned by a single partition template only.
  • ora-14000 : only one LOCAL clause may be specified
  • ora-25198 : only range, list, and hash partitioning are supported for index-organized table
  • 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.