ORA-16618: response document of size "string" bytes is too large

Cause : The document response cannot be returned because the size of the document is too large. This can occur when displaying the Data Guard broker log.

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

View the broker log for the given database directly.

update : 17-08-2017

ORA-16618 - response document of size "string" bytes is too large
ORA-16618 - response document of size "string" bytes is too large

  • ora-02736 : osnfpm: illegal default shared memory address
  • ora-29926 : association already defined for the object
  • ora-22903 : MULTISET expression not allowed
  • ora-06002 : NETASY: port read failure
  • ora-13205 : internal error while parsing spatial parameters
  • ora-01336 : specified dictionary file cannot be opened
  • ora-13509 : error encountered during updates to a AWR table
  • ora-24392 : no connection pool to associate server handle
  • ora-13836 : invalid attribute value specified
  • ora-22807 : cannot resolve to a scalar type or a collection type
  • ora-19664 : file type: string, file name: string
  • ora-37141 : (XSSQLMDQ01) Invalid host variable syntax for MDQUERY procedure.
  • ora-13500 : SYSAUX DATAFILE clause specified more than once
  • ora-22323 : error table "string"."string" does not exist
  • ora-36993 : (XSRELGID10) OBJECT workspace object must be a VARIABLE, RELATION, or a numeric SURROGATE DIMENSION based on the level dimension workspace object.
  • ora-07802 : slbtpd: overflow while converting to packed decimal
  • ora-00825 : cannot set db_block_buffers if sga_target set
  • ora-12840 : cannot access a remote table after parallel/insert direct load txn
  • ora-25101 : duplicate REBUILD option specification
  • ora-26765 : invalid parameter "string" for downstream capture "string"
  • ora-16083 : LogMiner session has not been created
  • ora-10653 : Table is in a cluster
  • ora-39055 : The string feature is not supported in version string.
  • ora-14641 : STORE-IN clause can be specified only for a Hash, Composite Range Hash table/partition
  • ora-10562 : Error occurred while applying redo to data block (file# string, block# string)
  • ora-32508 : no such watchpoint id
  • ora-09276 : All bequeath database links must be loopback database links
  • ora-31097 : Hierarchical Index not empty
  • ora-14625 : subpartition contains rows corresponding to values being dropped
  • ora-07223 : slspool: fork error, unable to spawn spool process.
  • 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.