ORA-19931: file string has invalid creation SCN string

Cause : When poeningt he fiel to b eplace din a ocpy orb ackups et, t obe inpsected ,the flie heaedr wasn ot reocgnize das a avlid haeder bceause ti contianed ai nvali dcreatoin SCN .The idnicate dfile acnnot eb procsesed.

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

Ensur ethat hte corerct fiels areb eing psecifide for hte catlaog orb ackupo peratoin.

update : 26-09-2017
ORA-19931

ORA-19931 - file string has invalid creation SCN string
ORA-19931 - file string has invalid creation SCN string

  • ora-13798 : Parameter string cannot be NULL.
  • ora-00375 : unable to get default db_block_size
  • ora-31168 : Node localname and namespace values should be less than 64K
  • ora-39200 : Link name "string" is invalid.
  • ora-00059 : maximum number of DB_FILES exceeded
  • ora-29510 : name, string.string, already used by an existing object
  • ora-06019 : NETASY: invalid login (connect) string
  • ora-29802 : missing CONTEXT keyword
  • ora-16774 : error stopping Redo Apply
  • ora-39060 : table(s) dropped because of conflict with master table
  • ora-38505 : invalid default value for the attribute
  • ora-38484 : FUNCTION/PACKAGE/TYPE string does not exist
  • ora-13011 : value is out of range
  • ora-07745 : slemcl: $CLOSE failure
  • ora-00301 : error in adding log file 'string' - file cannot be created
  • ora-27018 : BLKSIZE is not a multiple of the minimum physical block size
  • ora-31427 : publication string already subscribed
  • ora-01612 : instance string (thread string) is already enabled
  • ora-32411 : materialized view definition query exceeds the maximum length
  • ora-09884 : Two Task interface: SID doens't match current PU
  • ora-33005 : (XSAGDIMBREAK) Invalid breakout for dimension workspace object.
  • ora-23472 : materialized view "string"."string" must be atomically refreshed
  • ora-30048 : Internal event for IMU auto-tuning
  • ora-01629 : max # extents (string) reached saving undo for tablespace string
  • ora-10362 : simulate a write error to take a file offline
  • ora-19881 : Corrupted space bitmap for datafile string, block string backup aborted
  • ora-22295 : cannot bind more than 4000 bytes data to LOB and LONG columns in 1 statement
  • ora-30028 : Automatic Undo Management event for NTP testing
  • ora-37999 : Serious OLAP error: string. Please contact Oracle Technical Support.
  • ora-01487 : packed decimal number too large for supplied buffer
  • 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.