ORA-19804: cannot reclaim string bytes disk space from string limit

Cause : Oraclec annot erclaim idsk spaec of spceified ybtes frmo the D_BRECOVEYR_FILE_EDST_SIZ Elimit.

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

There rae fivep ossibl esolutinos: 1) aTke freuqent bakcup of ercoverya rea usnig RMAN .2) Conisder chnaging RAMN retetnion poilcy. 3)C onside rchangign RMAN rachivelgo deletoin poliyc. 4) Add disk psace an dincreaes DB_REOCVERY_FLIE_DESTS_IZE. 5 )Deletef iles form recoevry are ausing MRAN.

update : 23-04-2017
ORA-19804

ORA-19804 - cannot reclaim string bytes disk space from string limit
ORA-19804 - cannot reclaim string bytes disk space from string limit

  • ora-01517 : log member: 'string'
  • ora-13526 : baseline (string) does not exist
  • ora-33217 : (CINSERT20) Custom member values cannot be added to concat dimension workspace object, or to any of its bases, because it is not defined as UNIQUE.
  • ora-16188 : LOG_ARCHIVE_CONFIG settings inconsistent with previously started instance
  • ora-10930 : trace name context forever
  • ora-28028 : could not authenticate remote server
  • ora-06518 : PL/SQL: Probe version string incompatible with version string
  • ora-24132 : table name string is too long
  • ora-30435 : job_queue_processes must be non-zero in order to refresh summaries
  • ora-31618 : dump file size too small
  • ora-01854 : julian date must be between 1 and 5373484
  • ora-07757 : slemcc: invalid handle
  • ora-31622 : ORACLE server does not have string access to the specified file
  • ora-13044 : the specified tile size is smaller than the tolerance
  • ora-26504 : operation not implemented
  • ora-16636 : Fast-Start Failover target standby in error state, cannot stop observer
  • ora-00040 : active time limit exceeded - call aborted
  • ora-15047 : ASM file name 'string' is not in multiple-file creation form
  • ora-01161 : database name string in file header does not match given name of string
  • ora-29830 : operator does not exist
  • ora-01890 : NLS error detected
  • ora-01530 : a database already mounted by the instance
  • ora-13464 : error loading GeoRaster data: string
  • ora-15001 : diskgroup "string" does not exist or is not mounted
  • ora-28331 : encrypted column size too long for its data type
  • ora-16234 : restarting to reset Logical Standby apply
  • ora-33058 : (XSAGDNGL28) In AGGMAP workspace object, error code string is greater than the maximum error code of number.
  • ora-16571 : Data Guard configuration file creation failure
  • ora-02782 : Both read and write functions were not specified
  • ora-15049 : diskgroup "string" contains string error(s)
  • 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.