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 : 25-04-2017

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

  • ora-29888 : cannot create domain index on a table with row movement enabled
  • ora-08008 : another instance is mounted with USE_ROW_ENQUEUES = string
  • ora-13791 : cannot resume a tuning task created to tune a single statement
  • ora-26024 : SKIP_UNUSABLE_INDEXES requested and index segment was initially unusable
  • ora-01211 : Oracle7 data file is not from migration to Oracle8
  • ora-28533 : Heterogeneous Services coercion handling error
  • ora-26710 : incompatible version marker encountered during Capture
  • ora-19777 : ASM file string cannot be proxy backed up.
  • ora-27068 : I/O buffer is not aligned properly
  • ora-27001 : unsupported device type
  • ora-06022 : NETASY: channel open failure
  • ora-29357 : object string already exists
  • ora-30489 : Cannot have more than one rollup/cube expression list
  • ora-23315 : repcatlog version or request string is not supported by version string
  • ora-01631 : max # extents (string) reached in table string.string
  • ora-01704 : string literal too long
  • ora-13753 : "SQL Tuning Set" "string" already exists for user "string".
  • ora-16523 : operation requires the client to connect to instance "string"
  • ora-33625 : (FRASSIGN02) You cannot use the APPEND keyword with concat dimension workspace object.
  • ora-24067 : exceeded maximum number of subscribers for queue string
  • ora-35066 : (QFGET03) Extension number number is missing for EIF file string.
  • ora-08198 : Flashback Table is not supported on object tables, nested tables
  • ora-31669 : Worker process string violated startup protocol.
  • ora-28654 : table and partition not overflow compatible
  • ora-07204 : sltln: name translation failed due to lack of output buffer space.
  • ora-00983 : cannot audit or noaudit SYS user actions
  • ora-14159 : duplicate subpartition name
  • ora-06702 : TLI Driver: cannot allocate context area
  • ora-14626 : values being added already exist in DEFAULT subpartition
  • ora-32129 : cannot get information about this 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.