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 : 28-04-2017
ORA-19586

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-15077 : could not locate ASM instance serving a required diskgroup
  • ora-01207 : file is more recent than control file - old control file
  • ora-12824 : INSTANCES DEFAULT may not be specified here
  • ora-12683 : encryption/crypto-checksumming: no Diffie-Hellman seed
  • ora-12418 : user string not found
  • ora-14628 : specification of bounds is inconsistent with LIST method
  • ora-34243 : (MXDCL11) You can only use the string keyword when defining a COMPOSITE.
  • ora-02191 : correct syntax is: SET TRANSACTION USE ROLLBACK SEGMENT
  • ora-01108 : file string is in backup or media recovery
  • ora-33048 : (XSAGDNGL23) In AGGMAP workspace object, the relation workspace object and the relation workspace object are both over the same base dimension.
  • ora-28200 : IDENTIFIED USING already specified
  • ora-09961 : Unable to restore termination signal handler
  • ora-19661 : datafile string could not be verified
  • ora-01147 : SYSTEM tablespace file string is offline
  • ora-10647 : Tablespace other than SYSTEM, string, string not found in read only mode
  • ora-06264 : NETNTT: data protocol error
  • ora-39956 : duplicate setting for PL/SQL compiler parameter string
  • ora-13278 : failure to convert SRID to native format
  • ora-13902 : The specified file string is not a data file.
  • ora-16822 : new primary database not yet ready for standby database reinstatement
  • ora-01704 : string literal too long
  • ora-19701 : device name exceeds maximum length of string
  • ora-19954 : control file is not current
  • ora-01952 : system privileges not granted to 'string'
  • ora-07846 : sllfop: string byte record too big for string byte user buffer
  • ora-13423 : invalid cell coordinate parameter
  • ora-23536 : the object "string"."string" is not cached at the middle tier as expected.
  • ora-13414 : invalid pyramid parameter
  • ora-09940 : ORACLE password file header is corrupt
  • ora-16171 : RECOVER...FINISH not allowed due to gap for thr string, seq string-string
  • 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.