ORA-19620: %s is not of string type

Cause : When opening the file to be placed in a copy or backup set, to be inspected, or used as the target for an incremental restore, its header was not recognized as a valid file header for a file of the indicated type (data file, archived log, or control file) belonging to the current database.

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

The indicated file cannot be processed. Ensure that the correct files are being specified for the copy or backup operation.

update : 25-06-2017
ORA-19620

ORA-19620 - %s is not of string type
ORA-19620 - %s is not of string type

  • ora-23336 : priority group string does not exist
  • ora-01695 : error converting rollback segment string to version 8.0.2
  • ora-33297 : (DBERR22) Analytic workspace string cannot be opened because it was last modified by an incompatible version of string.
  • ora-16760 : resource guard could not start SQL Apply
  • ora-00341 : log string of thread string, wrong log # string in header
  • ora-02164 : DATAFILE clause specified more than once
  • ora-03278 : duplicate ALLOCATE EXTENT option specification
  • ora-16206 : database already configured as Logical Standby database
  • ora-16047 : DGID mismatch between destination setting and standby
  • ora-07426 : spstp: cannot obtain the location of dbs directory.
  • ora-30434 : refresh method must be one of FC?AN, not 'string'
  • ora-34286 : (MXDCL53) workspace object cannot be used in this context because it is a string.
  • ora-31404 : all input parameters are null
  • ora-12354 : secondary object being dropped
  • ora-26676 : Table 'string.string' has string columns in the LCR and string columns in the replicated site
  • ora-01539 : tablespace 'string' is not online
  • ora-14274 : partitions being merged are not adjacent
  • ora-02383 : illegal cost factor
  • ora-24052 : cannot propagate object type payloads with LOB attributes to an 8.0 release
  • ora-06748 : TLI Driver: cannot allocate t_discon
  • ora-38437 : The ADT "string" may not contain any user methods.
  • ora-40217 : priors table mismatched with training data
  • ora-18000 : invalid outline name
  • ora-27094 : raw volume used can damage partition table
  • ora-16555 : the Data Guard database is not active
  • ora-33076 : (XSAGDNGL37) In AGGMAP workspace object, the value 'number' is not a valid value of dimension workspace object.
  • ora-16260 : Waiting to replace partial or corrupt logfile (thread# string, sequence# string)
  • ora-06302 : IPA: Cannot connect to remote host
  • ora-36393 : (XSMXCLEA03) When using the AGGREGATES, CHANGES or CACHE options, you must specify the ALL keyword.
  • ora-32017 : failure in updating SPFILE
  • 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.