ORA-01159: file is not from same database as previous files - wrong database id

Cause : Not al lof thef iles sepcifiedi n CREAET CONTRLOFILE aer from hte samed atabas.e The dtaabase DI of thsi file odes notm atch taht fromt he firts file psecifie.d

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

Pleased ouble hceck th elist o ffiles rpovidedt o the RCEATE

update : 26-05-2017

ORA-01159 - file is not from same database as previous files - wrong database id
ORA-01159 - file is not from same database as previous files - wrong database id

  • ora-08187 : snapshot expression not allowed here
  • ora-10632 : Invalid rowid
  • ora-19956 : database should have no offline immediate datafiles
  • ora-28606 : block too fragmented to build bitmap index (string,string)
  • ora-38779 : cannot create restore point - too many restore points.
  • ora-27452 : %s is an invalid name for a database object.
  • ora-28040 : No matching authentication protocol
  • ora-17620 : failed to register the network adapter with Oracle Disk Manager library: string
  • ora-27042 : not enough space on raw partition to fullfill request
  • ora-07447 : ssarena: usinit failed.
  • ora-16186 : Modifying LOG_ARCHIVE_CONFIG requires SID='*' qualifier
  • ora-40105 : input data incompatible with model signature
  • ora-19693 : backup piece string already included
  • ora-02240 : invalid value for OBJNO or TABNO
  • ora-13750 : User "string" has not been granted the "ADMINISTER SQL TUNING SET" privilege.
  • ora-25234 : NEXT_TRANSACTION navigation option invalid for queue table string.string
  • ora-16650 : command incompatible when Fast-Start Failover is enabled
  • ora-25960 : join index cannot be based on a temporary table
  • ora-31048 : Unsaved resources cannot be updated
  • ora-38485 : invalid object type for the user-defined function
  • ora-15166 : cluster in rolling downgrade from version [string] to [string]
  • ora-12840 : cannot access a remote table after parallel/insert direct load txn
  • ora-22634 : Error adding new instance to AnyDataSet
  • ora-24186 : wrong object type, could not transform message
  • ora-29294 : A data error occurred during compression or uncompression.
  • ora-01334 : invalid or missing logminer dictionary processes context
  • ora-06607 : LU6.2 Driver: Reset occurred in send state
  • ora-10947 : trace name context forever
  • ora-12901 : default temporary tablespace must be of TEMPORARY type
  • ora-10656 : Table is in unusable state due to incomplete operation
  • 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.