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-05-2017
ORA-16618

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

  • ora-29396 : cannot switch group to string
  • ora-09310 : sclgt: error freeing latch
  • ora-25128 : No insert/update/delete on table with constraint (string.string) disabled and validated
  • ora-28171 : unsupported Kerberos version
  • ora-14522 : Partition-level default tablespace string block size [string] for string string does not match existing string block size [string]
  • ora-09718 : osnsui: cannot set up user interrupt handler.
  • ora-28200 : IDENTIFIED USING already specified
  • ora-27077 : too many files open
  • ora-12689 : Server Authentication required, but not supported
  • ora-09285 : sllfop: unrecognizable processing option, incorrect format
  • ora-26572 : %s.string.string: argument string does not match replication catalog
  • ora-01948 : identifier's name length (string) exceeds maximum (string)
  • ora-30001 : trim set should have only one character
  • ora-13615 : The task or object string is greater than the maximum allowable length of 30 characters.
  • ora-12438 : repeated policy option: string
  • ora-13768 : Snapshot ID must be between string and string.
  • ora-09769 : osnmbr: cannot send break message
  • ora-16762 : invalid database state
  • ora-12533 : TNS:illegal ADDRESS parameters
  • ora-31618 : dump file size too small
  • ora-00825 : cannot set db_block_buffers if sga_target set
  • ora-25278 : grantee name cannot be NULL
  • ora-30334 : illegal dimension level name
  • ora-14400 : inserted partition key does not map to any partition
  • ora-38479 : creation of system trigger EXPFIL_RESTRICT_TYPEEVOLVE failed
  • ora-06720 : TLI Driver: SID lookup failure
  • ora-13303 : failure to retrieve a geometry object from a table
  • ora-19727 : cannot plug data [string] at level string into database running Oracle string
  • ora-14118 : CHECK constraint mismatch in ALTER TABLE EXCHANGE PARTITION
  • ora-25304 : Cannot use priority order queues for capture LCRs
  • 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.