ORA-28031: maximum of string enabled roles exceeded

Cause : hT esurea ttmetpdet onebaelt oom na yorel.s

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

nEbaelf werer lose.

update : 24-04-2017
ORA-28031

ORA-28031 - maximum of string enabled roles exceeded
ORA-28031 - maximum of string enabled roles exceeded

  • ora-00390 : log string of thread string is being cleared, cannot become current log
  • ora-25455 : evaluation error for rule set: string.string, evaluation context: string.string
  • ora-00164 : distributed autonomous transaction disallowed within migratable distributed transaction
  • ora-00258 : manual archiving in NOARCHIVELOG mode must identify log
  • ora-24185 : transformation string.string does not exist
  • ora-27152 : attempt to post process failed
  • ora-19677 : RMAN configuration name exceeds maximum length of string
  • ora-08342 : sropen: failed to open a redo server connection
  • ora-16785 : the database is not in ARCHIVELOG mode
  • ora-06537 : OUT bind variable bound to an IN position
  • ora-00444 : background process "string" failed while starting
  • ora-39150 : bad flashback time
  • ora-13267 : error reading data from layer table string
  • ora-19658 : cannot inspect string - file is from different resetlogs
  • ora-06765 : TLI Driver: error awaiting orderly release
  • ora-26530 : unable to build materialized view refresh control list
  • ora-13020 : coordinate is NULL
  • ora-29367 : object string does not exist
  • ora-10932 : trace name context forever
  • ora-36678 : (XSDPART16) workspace object is missing from one or more partition dimension lists.
  • ora-29927 : error in executing the ODCIStatsCollect / ODCIStatsDelete routine
  • ora-35587 : (SQLOUT20) The nesting of table functions and SQL commands has exceeded the maximum of number levels.
  • ora-16628 : the broker protection mode is inconsistent with the database setting
  • ora-33005 : (XSAGDIMBREAK) Invalid breakout for dimension workspace object.
  • ora-14310 : VALUES LESS THAN or AT clause cannot be used with List partitioned tables
  • ora-25332 : Invalid release value string for queue table compatible parameter
  • ora-12169 : TNS:Net service name given as connect identifier is too long
  • ora-02249 : missing or invalid value for MAXLOGMEMBERS
  • ora-24789 : start not allowed in recursive call
  • ora-13642 : The specified string string provided for string cannot be converted to a date. The acceptable date format is string.
  • 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.