ORA-19589: %s is not a snapshot or backup control file

Cause : The control file that is the source for a backup or copy operation is not a snapshot or backup control file.

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

Specify the name of a snapshot or backup control file.

update : 21-08-2017
ORA-19589

ORA-19589 - %s is not a snapshot or backup control file
ORA-19589 - %s is not a snapshot or backup control file

  • ora-12805 : parallel query server died unexpectedly
  • ora-32344 : cannot create a secondary materialized view with synonym as base table
  • ora-01506 : missing or illegal database name
  • ora-10941 : trace name context forever
  • ora-37602 : (XSPGERRTEMPUSER) Ran out of temporary storage while writing to analytic workspace string. Free some temporary storage immediately. You can do so, for example, by DETACHING an analytic workspace.
  • ora-09812 : Unable to get user clearance from connection
  • ora-25219 : enqueue failed, sequence deviation not allowed for queue string.string
  • ora-12465 : Not authorized for read or write on specified groups or compartments
  • ora-31055 : A null XMLType element cannot be inserted into RESOURCE_VIEW
  • ora-02720 : osnfop: shmat failed
  • ora-26001 : Index string specified in SORTED INDEXES does not exist on table string
  • ora-39006 : internal error
  • ora-39012 : Client detached before the job started.
  • ora-15031 : disk specification 'string' matches no disks
  • ora-19932 : control file is not clone or standby
  • ora-12716 : Cannot ALTER DATABASE CHARACTER SET when CLOB data exists
  • ora-24501 : invalid UTF16 string passed in
  • ora-31534 : Change Data Capture string publisher string is missing DBA role
  • ora-12401 : invalid label string: string
  • ora-08237 : smsget: SGA region not yet created
  • ora-36176 : (XSMXAGGR25) Relation workspace object must be a one-dimensional self-relation to be used as a weight for AGGREGATE.
  • ora-08450 : invalid specification of CR in picture mask
  • ora-39014 : One or more workers have prematurely exited.
  • ora-33060 : (XSAGDNGL29) In AGGMAP workspace object, the value for the ERRORLOG MAX option must be greater than 0.
  • ora-01350 : must specify a tablespace name
  • ora-14128 : FOREIGN KEY constraint mismatch in ALTER TABLE EXCHANGE PARTITION
  • ora-01681 : max # extents (string) reached in LOB segment in tablespace string
  • ora-36875 : (XSTFDSC05) LIMITMAP is missing or is not a string literal.
  • ora-24354 : number fetched too large to fit in COBOL display type buffer.
  • ora-00293 : control file out of sync with redo log
  • 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.