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 : 20-08-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-14316 : table is not partitioned by List method
  • ora-29540 : class string does not exist
  • ora-01268 : invalid TEMPFILE clause for alter of permanent TABLESPACE
  • ora-28656 : incomplete attribute specification
  • ora-13769 : Snapshots string and string do not exist.
  • ora-25019 : too much concurreny
  • ora-25145 : allocation policy already specified
  • ora-15190 : Internal ASM testing event number 15190
  • ora-31083 : error while creating SQL type "string"."string"
  • ora-25533 : FAST_START_IO_TARGET or LOG_CHECKPOINT_INTERVAL is specified
  • ora-07597 : spguns: $GETJPIW failure
  • ora-09271 : szlon: error verifying user name
  • ora-02786 : Size needed for shared region is greater than segment size
  • ora-36976 : (XSRELGID00) The format of the GROUPINGID command is: GROUPINGID [relation1] INTO {variable | relation2 | surrogate} [USING levelrelation] [INHIERARCHY {inhvariable | valueset}] [LEVELORDER levelordervs] The source relation can be omitted only when using both surrogate gid and level order valueset.
  • ora-32736 : Hang analysis aborted due to wrong message type
  • ora-29307 : datafile string error, string
  • ora-24006 : cannot create QUEUE, string already exists
  • ora-29535 : source requires recompilation
  • ora-26097 : unsupported conversion for column string (from type number to type number)
  • ora-15010 : name is already used by an existing ASM disk
  • ora-22950 : cannot ORDER objects without MAP or ORDER method
  • ora-01109 : database not open
  • ora-29357 : object string already exists
  • ora-02730 : osnrnf: cannot find user logon directory
  • ora-38853 : cannot mark instance string (redo thread string) as disabled
  • ora-07281 : slsget: times error, unable to get cpu time.
  • ora-06576 : not a valid function or procedure name
  • ora-26701 : STREAMS process string does not exist
  • ora-23620 : bind value size too large for PL/SQL CALL operation
  • ora-28264 : Client identifier is too long
  • 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.