ORA-19695: fixed table x$krbmsft has not been populated

Cause : This is an internal error. The fixed table x$krbmaft was not populated using the function dbms_backup_restore.searchFiles.

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

Internal error - contact Oracle Customer Support.

update : 27-04-2017

ORA-19695 - fixed table x$krbmsft has not been populated
ORA-19695 - fixed table x$krbmsft has not been populated

  • ora-06906 : CMX: cannot get maximum packet size from CMX
  • ora-15179 : missing or invalid alias name
  • ora-10918 : TABLESPACE GROUP name cannot be the same as tablespace name
  • ora-16573 : attempt to change configuration file for an enabled broker configuration
  • ora-30450 : refresh_after_errors was TRUE; The following MVs could not be refreshed: string
  • ora-14277 : tables in EXCHANGE SUBPARTITION must have the same number of columns
  • ora-30189 : reserved for future use
  • ora-29318 : datafile string is online
  • ora-02752 : osnfsmmap: illegal shared memory address
  • ora-38433 : index "string" could not be maintained due to "string"
  • ora-25242 : cannot change subscriber name from string to string without FIRST_MESSAGE option
  • ora-00362 : member is required to form a valid logfile in group string
  • ora-14609 : Tablespace was not specified for the previous lob segments of column string in template but is specified for string
  • ora-09262 : spdde: error terminating detached (background) process
  • ora-13150 : failed to insert exception record
  • ora-01169 : DATAFILE number 1 not found. Must be present
  • ora-30945 : Could not create mapping table 'string'
  • ora-25501 : ALTER SYSTEM QUIESCE RESTRICTED command failed
  • ora-07345 : The datafile name must not contain the string '..'.
  • ora-16193 : Primary and standby network encryption mismatch
  • ora-25454 : error during evaluation of rule set: string.string for iterator: string
  • ora-00088 : command cannot be executed by shared server
  • ora-36712 : (XSMXALLOC02) Relation workspace object must be a one-dimensional self-relation to be used as a SOURCE or BASIS with ALLOCATE.
  • ora-02162 : invalid value for MAXDATAFILES
  • ora-37100 : (XSUNCOMMITTED) You have one or more updated but uncommitted analytic workspaces.
  • ora-07576 : sspexst: $GETJPIW failure on process ID string
  • ora-13383 : inconsistent network metadata: string
  • ora-03276 : duplicate ALLOCATE EXTENT option specification
  • ora-13143 : invalid POLYGON window definition
  • ora-07493 : scgrcl: lock manager error.
  • 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.