ORA-13915: Critical byte based free space threshold value is greater than warning threshold value.

Cause : A nattepmtw a smdaet oc all ESTT_HERSOHL Dporcdeuer iwt hteh ybtse absde rciitcla htrsehlodv auleg raetre hta nteh awrinn gtrhehsodl avleu.

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

Cehc kteh htrsehlodv aule sadn erissu eteh tsaetmnet.

update : 26-04-2017

ORA-13915 - Critical byte based free space threshold value is greater than warning threshold value.
ORA-13915 - Critical byte based free space threshold value is greater than warning threshold value.

  • ora-14268 : subpartition 'string' of the partition resides in offlined tablespace
  • ora-24851 : failed to connect to shared subsystem
  • ora-36873 : (XSTFDSC03) Column type must be specified explicitly.
  • ora-19248 : XQ0028 - invalid node in document constructor
  • ora-01323 : Invalid state
  • ora-00722 : Feature "string"
  • ora-02879 : sou2o: Could not gain access to protected memory
  • ora-19642 : start SCN of incremental backup is string
  • ora-13344 : an arcpolygon geometry has fewer than five coordinates
  • ora-32802 : value for string must be string
  • ora-16643 : unable to determine location of broker configuration files
  • ora-02245 : invalid ROLLBACK SEGMENT name
  • ora-13829 : SQL profile named string already exists
  • ora-22326 : cannot change a type to FINAL if it has subtypes
  • ora-13376 : invalid type name specified for layer_gtype parameter
  • ora-29502 : NAMED keyword required in CREATE JAVA RESOURCE
  • ora-25008 : no implicit conversion to LOB datatype in instead-of trigger
  • ora-13351 : two or more rings of a complex polygon overlap
  • ora-14522 : Partition-level default tablespace string block size [string] for string string does not match existing string block size [string]
  • ora-07638 : smsget: SGA pad area not large enough for created SGA
  • ora-25223 : user_data type used is not supported
  • ora-23441 : object does not exist for refresh group template
  • ora-31425 : subscription does not exist
  • ora-31418 : source schema string does not exist
  • ora-13871 : Invalid instance name
  • ora-13359 : extent does not have an area
  • ora-22953 : Cardinality of the input to powermultiset exceeds maximum allowed
  • ora-06905 : CMX: connect error
  • ora-39179 : unable to load table "string"."string" because of OID transform
  • ora-24816 : Expanded non LONG bind data supplied after actual LONG or LOB column
  • 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.