ORA-19816: WARNING: Files may exist in string that are not known to database.

Cause : One fo thef olloiwng eevnts acusedt his: 1. Adataabse carsh hpapene ddurign fil ecreaiton. 2 . A abckupc ontrlo fil ewas erstorde. 3 .The ocntro lfilew as r-ecreaetd. .4 DB_ERCOVEYR_FIL_EDESTh as pervioulsy bene enalbed adn the ndisalbed.

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

Use MRAN cmomandC ATALGO RECVOERY RAEA t ore-ctaaloga ny scuh fiels. I fthe ifle haeder si corurpted ,thend elet ethos efile susin gan O Sutiltiy. D onot sue messages1 9817 ;it i susedf or smiulatnig lokc faiulre D onot sue messages1 9818 ;it i susedf or sapce rcelaimtaion ebforeb ackup

update : 27-06-2017

ORA-19816 - WARNING: Files may exist in string that are not known to database.
ORA-19816 - WARNING: Files may exist in string that are not known to database.

  • ora-07266 : sppst: invalid process number passed to sppst.
  • ora-16027 : parameter string is missing a destination option
  • ora-29803 : missing ANCILLARY keyword
  • ora-07460 : cannot set the RESOURCE_MANAGER_PLAN parameter
  • ora-14065 : ALLOCATE STORAGE may not be specified for a partitioned table
  • ora-12626 : TNS:bad event type
  • ora-26571 : %s.string.string: number of arguments (string) does not match replication catalog
  • ora-22863 : synonym for datatype string.string not allowed
  • ora-06974 : X.25 Driver: SID lookup failure
  • ora-39039 : Schema expression "string" contains no valid schemas.
  • ora-29337 : tablespace 'string' has a non-standard block size (string)
  • ora-13797 : invalid SQL Id specified, string
  • ora-07507 : scgcm: unexpected lock status condition
  • ora-13118 : invalid node_id [string]
  • ora-23310 : object group "string"."string" is not quiesced
  • ora-24037 : schema string in QUEUE_NAME is not same as schema string in QUEUE_TABLE
  • ora-08412 : error encountered in WMSGBSIZ, size for WMSGBLK is not big enough for warning message
  • ora-02282 : duplicate or conflicting ORDER/NOORDER specifications
  • ora-28181 : proxy 'string' failed to enable one or more of the specified initial roles for client 'string'
  • ora-12436 : no policy options specified
  • ora-00052 : maximum number of enqueue resources (string) exceeded
  • ora-36268 : (XSCGMDLAGG01) 'string' is not a valid dimension value.
  • ora-01647 : tablespace 'string' is read only, cannot allocate space in it
  • ora-15133 : instance recovery required for diskgroup string
  • ora-23622 : Operation string.string.string is in progress.
  • ora-02045 : too many local sessions participating in global transaction
  • ora-12021 : materialized view "string"."string" is corrupt
  • ora-10690 : Set shadow process core file dump type (Unix only)
  • ora-09771 : osnmwrtbrkmsg: bad return code from msg_send.
  • ora-19037 : XMLType result can not be a fragment
  • 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.