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 : 23-06-2017

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

  • ora-24363 : measurements in characters illegal here
  • ora-01618 : redo thread string is not enabled - cannot mount
  • ora-06125 : NETTCP: ORASRV exited unexpectedly
  • ora-40301 : invalid cost matrix specification
  • ora-14279 : index mismatch for tables in ALTER TABLE EXCHANGE SUBPARTITION
  • ora-00113 : protocol name string is too long
  • ora-39001 : invalid argument value
  • ora-16637 : an instance failed to access the Data Guard broker configuration
  • ora-15154 : cluster rolling upgrade incomplete
  • ora-14109 : partition-extended object names may only be used with tables
  • ora-09340 : Specified ORACLE_SID is either invalid or too long
  • ora-24023 : Internal error in DBMS_AQ_EXP_INTERNAL.string [string] [string]
  • ora-02717 : osnpfs: incorrect number of bytes written
  • ora-01245 : offline file string will be lost if RESETLOGS is done
  • ora-39046 : Metadata remap string has already been specified.
  • ora-01554 : out of transaction slots in transaction tables
  • ora-16234 : restarting to reset Logical Standby apply
  • ora-25353 : branch marked for deletion
  • ora-28513 : internal error in heterogeneous remote agent
  • ora-15014 : location 'string' is not in the discovery set
  • ora-27064 : cannot perform async I/O to file
  • ora-25153 : Temporary Tablespace is Empty
  • ora-03264 : cannot drop offline datafile of locally managed tablespace
  • ora-38402 : invalid name: empty string or spaces in the name
  • ora-24321 : inconsistent parameters passed
  • ora-19951 : cannot modify control file until DBNEWID is completed
  • ora-09789 : sllfsk: unable to read file.
  • ora-17610 : file 'string' does not exist and no size specified
  • ora-15078 : ASM diskgroup was forcibly dismounted
  • ora-12911 : permanent tablespace cannot be temporary tablespace
  • 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.