ORA-19630: end of volume encountered while copying backup piece

Cause : While copying a backup piece from the OS native filesystem to an output device, the output device encountered end-of-volume.

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

The copy fails. This could happen if a tape was used which is not large enough to hold the entire backup piece.

update : 27-04-2017
ORA-19630

ORA-19630 - end of volume encountered while copying backup piece
ORA-19630 - end of volume encountered while copying backup piece

  • ora-16110 : user procedure processing of logical standby apply DDL
  • ora-01176 : data dictionary has more than the string files allowed by the controlfie
  • ora-16030 : session specific change requires a LOG_ARCHIVE_DEST_n destination
  • ora-36998 : (XSRELGID15) LEVEL ORDER VALUESET workspace object and LEVEL RELATION workspace object have the different level dimensions.
  • ora-12445 : cannot change HIDDEN property of column
  • ora-00064 : object is too large to allocate on this O/S (string,string)
  • ora-02026 : missing LINK keyword
  • ora-08430 : raw data missing leading sign
  • ora-29254 : Invalid lower_bound argument passed to procedure dbms_sql.define_array
  • ora-25443 : duplicate column value for table alias: string, column number: string
  • ora-22928 : invalid privilege on directories
  • ora-25219 : enqueue failed, sequence deviation not allowed for queue string.string
  • ora-27487 : invalid object privilege for a string
  • ora-01492 : LIST option not valid
  • ora-02021 : DDL operations are not allowed on a remote database
  • ora-24433 : This statement has already been prepared using OCIStmtPrepare2.
  • ora-39055 : The string feature is not supported in version string.
  • ora-15002 : parameter LOCK_NAME_SPACE exceeds limit of string characters
  • ora-33265 : (DBERRBSZ) Analytic workspace string cannot be opened. Tablespace blocksize number does not match database cache size number.
  • ora-15115 : missing or invalid ASM disk size specifier
  • ora-29298 : Character set mismatch
  • ora-31044 : Top-level prefix length string exceeds maximum string
  • ora-12047 : PCT FAST REFRESH cannot be used for materialized view "string"."string"
  • ora-02471 : SYSDATE, UID, USER, ROWNUM, or LEVEL incorrectly used in hash expression.
  • ora-27460 : cannot execute disabled job "string.string"
  • ora-12702 : invalid NLS parameter string used in SQL function
  • ora-19002 : Missing XMLSchema URL
  • ora-04077 : WHEN clause cannot be used with table level triggers
  • ora-35280 : (SNSYN165) The format of the AGGREGATE command is: AGGREGATE varname1 [varname2 varname3 ...] USING aggmap-name [COUNTVAR intvar-name1 [intvar-name2 intvar-name3 ...]] [FUNCDATA] [THREADS #]
  • ora-39752 : redundant column in partitioning and join columns is not allowed
  • 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.