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 : 20-08-2017
ORA-19816

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-12406 : unauthorized SQL statement for policy string
  • ora-19640 : datafile checkpoint is SCN string time string
  • ora-28338 : cannot encrypt indexed column(s) with salt
  • ora-24010 : QUEUE string does not exist
  • ora-27019 : tape filename length exceeds limit (SBTOPMXF)
  • ora-13143 : invalid POLYGON window definition
  • ora-07717 : sksaalo: error allocating memory
  • ora-31013 : Invalid XPATH expression
  • ora-00094 : %s requires an integer value
  • ora-00085 : current call does not exist
  • ora-32007 : internal
  • ora-07251 : spcre: semget error, could not allocate any semaphores.
  • ora-37012 : (XSACQUIRE_TIMEOUT) Object workspace object is locked by another user and the WAIT timed out.
  • ora-06920 : CMX: getbrkmsg illegal datatype
  • ora-01083 : value of parameter "string" is inconsistent with that of other instances
  • ora-32833 : failure string trying to release administration lock
  • ora-16236 : Logical Standby metadata operation in progress
  • ora-09853 : snyRemovePort: bad return code from request.
  • ora-30461 : 'string.string' cannot be refreshed because it is marked DISABLED
  • ora-16154 : suspect attribute: string
  • ora-33332 : (DSSEXIST01) Use the AW command to establish a current analytic workspace. Then start your current activity again.
  • ora-12535 : TNS:operation timed out
  • ora-13838 : invalid ADDRESS value
  • ora-12661 : Protocol authentication to be used
  • ora-16169 : LGWR network server invalid parameters
  • ora-16187 : LOG_ARCHIVE_CONFIG contains duplicate, conflicting or invalid attributes
  • ora-27100 : shared memory realm already exists
  • ora-12989 : invalid value for checkpoint interval
  • ora-01546 : tablespace contains active rollback segment 'string'
  • ora-08340 : This command not allowed on nCUBE, only one thread is ever used.
  • 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.