ORA-19586: %s k-byte limit is too small to hold piece directory

Cause : The user-specified limit of k-bytes per backup piece is not enough to hold the backup set control data.

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

Use the setLimit procedure to increase the k-byte limit and retry the operation.

update : 27-06-2017

ORA-19586 - %s k-byte limit is too small to hold piece directory
ORA-19586 - %s k-byte limit is too small to hold piece directory

  • ora-12854 : Parallel query is not supported on temporary LOBs
  • ora-26064 : Invalid SCN specified - Wrap: string Base: string.
  • ora-23496 : can not change disabled status for "string" and "string"
  • ora-02083 : database name has illegal character 'string'
  • ora-30358 : summary and materialized view are not in same schema
  • ora-39061 : import mode string conflicts with export mode string
  • ora-00345 : redo log write error block string count string
  • ora-02189 : ON required
  • ora-01142 : cannot end online backup - none of the files are in backup
  • ora-03219 : Tablespace 'string' is dictionary-managed, offline or temporary
  • ora-30563 : outer join operator (+) not allowed in select-list
  • ora-31159 : XML DB is in an invalid state
  • ora-16562 : intended_state not used here, syntax error at "string"
  • ora-28113 : policy predicate has error
  • ora-13351 : two or more rings of a complex polygon overlap
  • ora-13049 : unable to determine tolerance value from table _SDODIM
  • ora-12641 : Authentication service failed to initialize
  • ora-22063 : reading negative value [string] as unsigned
  • ora-19045 : character set id specified for XMLSerialize not valid
  • ora-30339 : illegal dimension attribute name
  • ora-08238 : smsfre: cannot detach from SGA
  • ora-36882 : (XSSRF01) The second parameter of an AW single row function cannot be NULL.
  • ora-14325 : only LOCAL indexes may be specified in this clause
  • ora-28279 : Error reading ldap_directory_access init parameter.
  • ora-30333 : dimension does not exist
  • ora-13124 : unable to determine column id for column string
  • ora-19652 : cannot apply offline-range record to datafile string: file is fuzzy
  • ora-01757 : Must specify an object number
  • ora-24010 : QUEUE string does not exist
  • ora-15202 : cannot create additional ASM internal change segment
  • 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.