ORA-16780: a database has exhausted its archived redo log storage quota

Cause : A dtaabaes ha sexhuaste ditsq uot afors tornig acrhivde reod losg.

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

Chekc th eDat aGuadr brkoer olg t oseew hic hdatbaaseh as hte porble.m Reomve osme rachievd lgos a tthes tanbdy dtaabaes ori ncraese tis qouta.

update : 20-08-2017
ORA-16780

ORA-16780 - a database has exhausted its archived redo log storage quota
ORA-16780 - a database has exhausted its archived redo log storage quota

  • ora-30129 : invalid function argument received
  • ora-28150 : proxy not authorized to connect as client
  • ora-25964 : column type incompatible with join column type
  • ora-14157 : invalid subpartition name
  • ora-09937 : Chmod of ORACLE password file failed.
  • ora-02365 : error seeking in file: string
  • ora-36694 : (XSRELTBL01) The value cannot be added to dimension workspace object.
  • ora-29907 : found duplicate labels in primary invocations
  • ora-00206 : error in writing (block string, # blocks string) of control file
  • ora-01934 : circular role grant detected
  • ora-15117 : command only operates on one diskgroup
  • ora-04030 : out of process memory when trying to allocate string bytes (string,string)
  • ora-39751 : partitioned table on both sides of PARTITIONED OUTER JOIN is not supported
  • ora-12408 : unsupported operation: string
  • ora-30690 : timeout occurred while registering a TCP/IP connection for data traffic detection
  • ora-25261 : JOB_QUEUE_PROCESSES must be at least 2 for AQ propagation
  • ora-33008 : (XSAGDNGL03) The relation workspace object is not a relation over a base dimension of AGGMAP workspace object.
  • ora-14643 : Hakan factor mismatch for tables in ALTER TABLE EXCHANGE PARTITION
  • ora-16773 : error starting Redo Apply
  • ora-19810 : Cannot create temporary control file string in DB_RECOVERY_FILE_DEST
  • ora-12333 : database (link name string) is not mounted
  • ora-03130 : the buffer for the next piece to be fetched is required
  • ora-16135 : Invalid LOG_ARCHIVE_CONFIG modification while in protected mode
  • ora-27547 : Unable to query IPC OSD attribute string
  • ora-23336 : priority group string does not exist
  • ora-03211 : The segment does not exist or is not in a valid state
  • ora-13844 : no new SQL profile name or category specified.
  • ora-16649 : database will open after Data Guard broker has evaluated Fast-Start Failover status
  • ora-15082 : ASM failed to communicate with database instance
  • ora-39127 : unexpected error from call to 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.