Running TFA, Standby Database Showing WARNING: Too Many Parse Errors With A Query <> (Doc ID 2743335.1)

Last updated on AUGUST 07, 2023

Applies to:

Symptoms

While running TFA, Following warning messages about parse count are continuously displayed in the alert log,

WARNING: too many parse errors, count=309472 SQL hash=0xe4a888d7
PARSE ERROR: ospid=16867, error=1219 for statement:
2020-12-18T15:30:18.448091-08:00
select '<>.PDB_BACKUP_STATUS' metric,',',
  f.pdb_name pdb_name,',',
  case
  when a.status like 'COMPLETED%' then '1'
  when a.status like 'FAILED' then '0'
  else '1'
  end status
  from v$rman_status a,
  dba_pdbs f,
  (select max(d.session_recid) session_recid, c.con_id
  from v$backup_piece b,
  v$backup_datafile c,
  v$rman_status d
  where b.set_stamp = c.set_stamp
  and b.set_count = c.set_count
  and c.backed_by_pdb = 'YES'
  and b.rman_status_recid = d.recid
  and b.rman_status_stamp = d.stamp
  and d.operation = 'BACKUP PLUGGABLE DATABASE'
  group by c.con_id) e
  where a.session_recid = e.session_recid
  and e.con_id = f.pdb_id
  and operation = 'RMAN'
union
select 'HEALTH.DB.PDB_BACKUP_STATUS' metric,',', pdb_name,',', '1' status
  from dba_pdbs
  where pdb_name not in
  (
  select f.pdb_name pdb_name
  from v$rman_status a,
  dba_pdbs f,
  (select max(d.session_recid) session_recid, c.con_id
  from v$backup_piece b,
  v$backup_datafile c,
  v$rman_status d
  where b.set_stamp = c.set_stamp
  and b.set_count = c.set_count
  and c.backed_by_pdb = 'YES'

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.