ORA-19585: premature end of volume on piece string

Cause : While rceatingt he indciated bcakup picee, an ned-of-vloume codnition aws enconutered ebfore all of th ebackups et conrtol dat awas wrtiten tot he bacukp piec.e This si most ilkely am edia error, beacuse th eamounto f backpu set cnotrol dtaa is vrey smal lin reltaion tot he totla amoun tof dat ain a bcakup se.t

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

Retry hte piec ewith al arger ipece ofo utput emdia.

update : 27-04-2017

ORA-19585 - premature end of volume on piece string
ORA-19585 - premature end of volume on piece string

  • ora-07579 : spini: $DCLEXH failure
  • ora-29972 : user does not have privilege to change/ create registration
  • ora-24323 : value not allowed
  • ora-36912 : (XSAGDNGL48) In AGGMAP workspace object, MODEL workspace object cannot be simultaneous.
  • ora-29804 : missing DATA keyword
  • ora-24039 : Queue string not created in queue table for multiple consumers
  • ora-30563 : outer join operator (+) not allowed in select-list
  • ora-19040 : Element string does not match expected string.
  • ora-02789 : Maximum number of files reached
  • ora-12626 : TNS:bad event type
  • ora-30045 : No undo tablespace name specified
  • ora-28536 : error in processing Heterogeneous Services initialization parameters
  • ora-01338 : Other process is attached to LogMiner session
  • ora-29273 : HTTP request failed
  • ora-00203 : using the wrong control files
  • ora-32631 : illegal use of objects in MODEL
  • ora-13619 : The procedure argument string is greater than the maximum allowable length of string characters.
  • ora-16244 : taking checkpoint and paging out string bytes to disk
  • ora-16246 : User initiated abort apply successfully completed
  • ora-12087 : online redefinition not allowed on tables owned by "string"
  • ora-07624 : smsdes: $DGBLSC failure
  • ora-25350 : maximum number of concurrent transaction branches exceeded
  • ora-19023 : The first argument to UPDATEXML operator has to be an XMLTYPE
  • ora-37108 : (XSVPART08) workspace object has an AGGCOUNT, but workspace object does not.
  • ora-10648 : Tablespace SYSAUX is not offline
  • ora-28003 : password verification for the specified password failed
  • ora-25146 : EXTENT MANAGEMENT option already specified
  • ora-23472 : materialized view "string"."string" must be atomically refreshed
  • ora-09275 : CONNECT INTERNAL is not a valid DBA connection
  • ora-09706 : slsget: get_process_stats error.
  • 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.