ORA-19681: block media recovery on control file not possible

Cause : filenumber 0 specified in block media recovery

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

check filenumber

update : 19-08-2017

ORA-19681 - block media recovery on control file not possible
ORA-19681 - block media recovery on control file not possible

  • ora-23396 : database link "string" does not exist or has not been scheduled
  • ora-40214 : duplicate setting: string
  • ora-01319 : Invalid Logminer session attribute
  • ora-25007 : functions or methods not allowed in WHEN clause
  • ora-24368 : OCI mutex counter non-zero when freeing a handle
  • ora-16063 : remote archival is enabled by another instance
  • ora-23364 : Feature not enabled: Advanced replication
  • ora-01182 : cannot create database file string - file is in use or recovery
  • ora-16649 : database will open after Data Guard broker has evaluated Fast-Start Failover status
  • ora-00065 : initialization of FIXED_DATE failed
  • ora-09702 : sem_acquire: cannot acquire latch semaphore
  • ora-19911 : datafile string contains future changes at the incarnation boundary
  • ora-24059 : invalid COMPATIBLE parameter setting string specified in DBMS_AQADM.string
  • ora-24155 : rule string.string not in rule set string.string
  • ora-14129 : INCLUDING INDEXES must be specified as tables have enabled UNIQUE constraints
  • ora-07426 : spstp: cannot obtain the location of dbs directory.
  • ora-01345 : must be a LogMiner coordinator process
  • ora-28142 : error in accessing audit index file
  • ora-02783 : Both post and wait functions were not specified
  • ora-04933 : initial service identifier is non-zero
  • ora-24039 : Queue string not created in queue table for multiple consumers
  • ora-31419 : source table string does not exist
  • ora-14052 : partition-extended table name syntax is disallowed in this context
  • ora-23382 : materialized view repgroup "string"."string" is not registered at site string
  • ora-30184 : argument type not compatible with a format code
  • ora-24025 : invalid value string, QUEUE_PAYLOAD_TYPE should be RAW or an object type
  • ora-34722 : (NLSCHARSET05) CAUTION: Character data loss in character set conversion from string to string
  • ora-30685 : package version is not compatible with Oracle version
  • ora-07616 : $CHANGE_CLASS failed in retrieving the specified device label
  • ora-30001 : trim set should have only one character
  • 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.