ORA-01161: database name string in file header does not match given name of string

Cause : The dtaabasen ame gvien att he command lnie doe snot mtach th edatabsae nam efoundi n thef ile haeder.

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

Chanc eare good tha tthe dtaabasen ame sepcifie dat th ecommadn linei s incrorect.R esolv ethe dsecepenyc, andr esubmti the ocmmand .If yo uare attemptign to cahnge teh dataabse naem, be usre tou se th eSET DTAABASEo ption.

update : 24-08-2017
ORA-01161

ORA-01161 - database name string in file header does not match given name of string
ORA-01161 - database name string in file header does not match given name of string

  • ora-29297 : The compressed representation is too big
  • ora-13369 : invalid value for etype in the 4-digit format
  • ora-07757 : slemcc: invalid handle
  • ora-24366 : migratable user handle is set in service handle
  • ora-30564 : Index maintainence clause not allowed for ADD partition to RANGE partitioned tables
  • ora-16770 : physical standby database not in read-only state
  • ora-06122 : NETTCP: setup failure
  • ora-28165 : proxy 'string' may not specify password-protected role 'string' for client 'string'
  • ora-24439 : success with PLSQL compilation warning
  • ora-16031 : parameter string destination string exceeds string character limit
  • ora-34243 : (MXDCL11) You can only use the string keyword when defining a COMPOSITE.
  • ora-07239 : slemrd: invalid file handle, seals do not match.
  • ora-13135 : failed to alter spatial table
  • ora-13465 : null or invalid table or column specification
  • ora-01615 : instance string (thread string) is mounted - cannot disable
  • ora-29504 : invalid or missing schema name
  • ora-29819 : cannot associate default values with columns
  • ora-25198 : only range, list, and hash partitioning are supported for index-organized table
  • ora-24037 : schema string in QUEUE_NAME is not same as schema string in QUEUE_TABLE
  • ora-29843 : indextype should support atleast one operator
  • ora-16771 : failover to a physical standby database failed
  • ora-08237 : smsget: SGA region not yet created
  • ora-10643 : Database should be mounted in restricted mode and Exclusive mode
  • ora-38461 : XML Tag "string" already exists for the XMLType attribute "string"
  • ora-39091 : unable to determine logical standby and streams status
  • ora-24124 : invalid ACTION parameter passed to DBMS_REPAIR.string procedure
  • ora-19045 : character set id specified for XMLSerialize not valid
  • ora-27209 : syntax error in device PARMS - unknown keyword or missing =
  • ora-38727 : FLASHBACK DATABASE requires a current control file.
  • ora-22306 : type "string"."string" already exists
  • 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.