ORA-16719: unable to query V$ARCHIVE_DEST fixed view

Cause : The broker failed to query the V$ARCHIVE_DEST fixed view."

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

Test and clear the problem using SQL*Plus.

update : 30-04-2017

ORA-16719 - unable to query V$ARCHIVE_DEST fixed view
ORA-16719 - unable to query V$ARCHIVE_DEST fixed view

  • ora-32027 : There is no string column with the matching type in string.string.
  • ora-07264 : spwat: semop error, unable to decrement semaphore.
  • ora-38418 : ADT associated with the attribute set string does not exist
  • ora-01560 : LIKE pattern contains partial or illegal character
  • ora-12476 : least upper bound resulted in an invalid OS label
  • ora-16648 : a new observer registered with identifier string
  • ora-01079 : ORACLE database was not properly created, operation aborted
  • ora-13143 : invalid POLYGON window definition
  • ora-07230 : slemcr: fopen error, unable to open error file.
  • ora-32331 : type "string"."string" is incompatible with the master site
  • ora-16206 : database already configured as Logical Standby database
  • ora-30388 : name of the rewrite equivalence is not specified
  • ora-08186 : invalid timestamp specified
  • ora-16769 : the physical standby database is open read-only
  • ora-00402 : database changes by release string cannot be used by release string
  • ora-00255 : error archiving log string of thread string, sequence # string
  • ora-06579 : Bind variable not big enough to hold the output value
  • ora-04003 : sequence parameter string exceeds maximum size allowed (string digits)
  • ora-36261 : (XSAGPARTDEP00) Can not Aggregate PARTITION TEMPLATE %J because the path of aggregation would recursively enter partition %J.
  • ora-37134 : (XSCCOMP09) You cannot add new values to workspace object because it includes positions for precomputed aggregate values.
  • ora-32627 : illegal pattern in MODEL FOR LIKE loop
  • ora-16579 : bad Data Guard NetSlave state detected
  • ora-09827 : SCLGT: atomic latch return unknown error.
  • ora-27472 : invalid metadata attribute string
  • ora-38463 : invalid XML Tag list
  • ora-25333 : Buffered Queue to Queue propagation did not connect to the correct instance
  • ora-01574 : maximum number of concurrent transactions exceeded
  • ora-08175 : discrete transaction restriction violated (string)
  • ora-06558 : buffer in dbms_pipe package is full. No more items allowed
  • ora-34141 : (MXCGPUT00) You cannot use the ASSIGN keyword with DIMENSION workspace object.
  • 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.