ORA-28100: policy function schema string is invalid

Cause : Teh cshmeaw a sdorpepda fetrt h eploiyc sascoitae dwtiht h efnucito nhda ebe nadde dt oteh bojcet.

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

Dorpt h eploiyc nadr ec-raet ei twtiha oplciyf ucntoino wendb ya avldi sue.r rO er-rcetaet h euesra n dteh oplciyf ucntoinu nedrt h enwe sue.r

update : 22-07-2017

ORA-28100 - policy function schema string is invalid
ORA-28100 - policy function schema string is invalid

  • ora-10660 : Segment is a shared lob segment
  • ora-13381 : table:string not found in network:string
  • ora-30348 : ADD and DROP cannot both be specified
  • ora-10701 : Dump direct loader index keys
  • ora-30026 : Undo tablespace 'string' has unexpired undo with string(sec) left, Undo_Retention=string(sec)
  • ora-30733 : cannot specify rowid constraint on scoped ref column
  • ora-14156 : invalid number of subpartitions specified in [SUBPARTITIONS | SUBPARTITION TEMPLATE] clause
  • ora-00220 : control file not mounted by first instance, check alert log for more info
  • ora-30071 : conversion between datetime/interval and string fail
  • ora-19738 : cannot find language information for character set: 'string'
  • ora-31457 : maximum length of description field exceeded
  • ora-23385 : replication parallel push string argument not valid
  • ora-03238 : unable to extend LOB segment string.string subpartition string by string in tablespace string
  • ora-01870 : the intervals or datetimes are not mutually comparable
  • ora-19525 : temporary file for the clone database must be renamed
  • ora-04091 : table string.string is mutating, trigger/function may not see it
  • ora-12317 : logon to database (link name string) denied
  • ora-16005 : database requires recovery
  • ora-01122 : database file string failed verification check
  • ora-15046 : ASM file name 'string' is not in single-file creation form
  • ora-25177 : UNRECOVERABLE option not permitted
  • ora-16236 : Logical Standby metadata operation in progress
  • ora-38720 : Missing log file number.
  • ora-29392 : cpu parameters for level string for plan string must be zero
  • ora-33218 : (CINSERT04) %K is not a valid value for the workspace object dimension. Values for this dimension can have at most number significant digits after rounding to number decimal places.
  • ora-16617 : unknown object identifier specified in request
  • ora-09789 : sllfsk: unable to read file.
  • ora-07601 : spguno: $GETJPIW failure
  • ora-19279 : XQuery dynamic type mismatch: expected singleton sequence - got multi-item sequence
  • ora-40223 : data mining model import failed, job name=string, error=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.