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 : 28-06-2017

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

  • ora-00220 : control file not mounted by first instance, check alert log for more info
  • ora-30500 : database open triggers and server error triggers cannot have BEFORE type
  • ora-19580 : %s conversation not active
  • ora-28508 : invalid value string for Heterogeneous Services initialization parameter string
  • ora-36974 : (XSRELTBL14) workspace object is not a BOOLEAN variable dimensioned by all the dimensions of the hierarchy.
  • ora-27374 : insufficient privileges on event source queue
  • ora-14408 : partitioned index contains subpartitions in a different tablespace
  • ora-39777 : data saves are not allowed when loading lob columns
  • ora-31121 : The string operator can not be FALSE
  • ora-22976 : incorrect number of arguments to MAKE_REF
  • ora-19570 : file number string is outside valid range of 1 through string
  • ora-16635 : NetSlave connection was broken in the middle of a transmission session
  • ora-39303 : schema sync or swap operation failed because of confilcts
  • ora-10362 : simulate a write error to take a file offline
  • ora-19577 : file string is MISSING
  • ora-15072 : command requires at least string failure groups, discovered only string
  • ora-19044 : character length specified for XMLSerialize is too small.
  • ora-24012 : cannot drop QUEUE_TABLE, some queues in string have not been dropped
  • ora-16823 : redo transport mode is incompatible for current operation
  • ora-01272 : REUSE only allowed when a file name is provided.
  • ora-01297 : redo version mismatch between dictionary string and logfiles
  • ora-38755 : Flashback is already turned on for this tablespace.
  • ora-32609 : missing REFERENCE keyword in MODEL clause
  • ora-09758 : osnipn: could not check port in name server.
  • ora-07605 : szprv: $ASCTOID failure
  • ora-06906 : CMX: cannot get maximum packet size from CMX
  • ora-10643 : Database should be mounted in restricted mode and Exclusive mode
  • ora-16550 : truncated result
  • ora-00371 : not enough shared pool memory, should be atleast string bytes
  • ora-02854 : Invalid number of request buffers
  • 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.