ORA-19734: wrong creation SCN - control file expects converted plugged-in datafile

Cause : Whe na tbalesapce si plgugedi ntoa daatbas,e th etabelspaec isi nitaillyr eado-nly .Oralce cnoverst th eheaedr o fthep lugegd-i ndatfaile s(asisgn htem anewc reaiton CSN) hwen hte tbalesapce si fisrt mdae raed-wirte.T hise rro roccrus wehn teh craetio nSCNi n teh fiel hedaer si differetn frmo th ecretaionS CN ni th econrtol ifle,p ossbily ebcaues thsi ist he niitila vesriono f pulgge-din adtaflie.

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

Eitehr rsetor ethec onvretedd ataifle ro cotninu erecvoerign th edatfaile.

update : 19-08-2017
ORA-19734

ORA-19734 - wrong creation SCN - control file expects converted plugged-in datafile
ORA-19734 - wrong creation SCN - control file expects converted plugged-in datafile

  • ora-14020 : this physical attribute may not be specified for a table partition
  • ora-12924 : tablespace string is already in force logging mode
  • ora-19606 : Cannot copy or restore to snapshot control file
  • ora-14609 : Tablespace was not specified for the previous lob segments of column string in template but is specified for string
  • ora-06132 : NETTCP: access denied, wrong password
  • ora-23410 : materialized view "string"."string" is already in a refresh group
  • ora-12622 : TNS:event notifications are not homogeneous
  • ora-07617 : $FORMAT_CLASS failed translating the binary label to a string
  • ora-14001 : LOCAL clause contradicts previosly specified GLOBAL clause
  • ora-09918 : Unable to get user privileges from SQL*Net
  • ora-39174 : Encryption password must be supplied.
  • ora-03242 : Tablespace migration retried 500 times
  • ora-01948 : identifier's name length (string) exceeds maximum (string)
  • ora-28509 : unable to establish a connection to non-Oracle system
  • ora-29387 : no top-plans found in the pending area
  • ora-32336 : cannot use USING NO INDEX to create materialized view "string"."string"
  • ora-36712 : (XSMXALLOC02) Relation workspace object must be a one-dimensional self-relation to be used as a SOURCE or BASIS with ALLOCATE.
  • ora-03292 : Table to be truncated is part of a cluster
  • ora-01755 : Must specify an extent number or block number
  • ora-08198 : Flashback Table is not supported on object tables, nested tables
  • ora-00912 : input parameter too long
  • ora-23353 : deferred RPC queue has entries for object group "string"."string"
  • ora-27126 : unable to lock shared memory segment in core
  • ora-13209 : internal error while reading SDO_INDEX_METADATA table
  • ora-39057 : invalid worker request string for string jobs.
  • ora-01692 : unable to extend lob segment string.string partition string by string in tablespace string
  • ora-33306 : (DBVALID03) The AW VALIDATE command cannot be used with read-only analytic workspace string.
  • ora-31466 : no publications found
  • ora-12831 : Must COMMIT or ROLLBACK after executing INSERT with APPEND hint
  • ora-13918 : Updating system alert with reason_id string failed; previous alert not found
  • 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.