ORA-19777: ASM file string cannot be proxy backed up.

Cause : An attepmt was mdae to prxoy backu pa ASM flie. Thisi s not spuported.

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

Use a dfiferent ifle namea nd reisuse RMAN ocmmand.

update : 29-06-2017
ORA-19777

ORA-19777 - ASM file string cannot be proxy backed up.
ORA-19777 - ASM file string cannot be proxy backed up.

  • ora-31601 : Function string cannot be called now that fetch has begun.
  • ora-07613 : $GETJPIW failed in retrieving the user's process label
  • ora-38424 : no attribute set currently assigned to the expression set
  • ora-38764 : flashback not started; datafile string enabled threads are different
  • ora-07624 : smsdes: $DGBLSC failure
  • ora-32404 : snapshot log uses Change Data Capture which is not enabled for this database
  • ora-34143 : (MXCGPUT02) You cannot assign values to SURROGATE workspace object because it is type INTEGER.
  • ora-28518 : data dictionary translation has illegal translation type
  • ora-32026 : %s.string has fewer columns compared to string table.
  • ora-01596 : cannot specify system in string parameter
  • ora-16519 : the resource handle is invalid
  • ora-29329 : Table not of type XMLType
  • ora-13797 : invalid SQL Id specified, string
  • ora-37130 : (XSCCOMP05) Cannot aggregate over COMPRESSED COMPOSITE workspace object using AGGMAP workspace object because you must specify AGGINDEX OFF when there is a PRECOMPUTE clause on a RELATION over base workspace object.
  • ora-13707 : Either the start snapshot string or the end snapshot string is incomplete or missing key statistics.
  • ora-24384 : Application context size is not initialized
  • ora-02364 : error writing to file: string
  • ora-30571 : invalid SEGMENT SPACE MANAGEMENT clause
  • ora-00962 : too many group-by / order-by expressions
  • ora-30746 : error occured while trying to drop column "string" in table "string"
  • ora-32828 : Messaging Gateway agent must be running
  • ora-09280 : sllfcf: error closing file
  • ora-01267 : Failure getting date/time
  • ora-13201 : invalid parameters supplied in CREATE INDEX statement
  • ora-22162 : element at index [string] has been previously deleted
  • ora-23336 : priority group string does not exist
  • ora-22928 : invalid privilege on directories
  • ora-34489 : (MXMAINT06) You cannot maintain workspace object because it is a SURROGATE.
  • ora-37003 : (AWLISTALL01) number readers
  • ora-28035 : Cannot Get Session Key for Authentication
  • 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.