BARMAN archiver errors: FAILED (duplicates: xxx)

 One of our PostgreSQL cluster BARMAN backup was constantly getting "archiver errors: FAILED (duplicates: xxx)" warning via "barman check serverx" command. Also we saw following warnings in barman logfile;

2021-05-18 09:57:02,365 [13875] barman.wal_archiver INFO:       Error: 00000001000000630000005B is already present in server serverx. File moved to errors directory.

 We realized that our server admin was rebooted serverx without notifying us a week ago. So we did'nt properly shut down postgresql cluster.

While investigating the problem we noticed that; everytime serverx postgresql cluster switches a wal file, it tries to send every wal file under pg_wal directory. So duplicate wal files send to barman and they move to "errors" directory. This happens also manually executing switch wal command: "SELECT pg_switch_wal();"

[EN] RMAN connection error: ORA-28041: Authentication protocol internal error

$ rman target rman/xxx@db1;

Recovery Manager: Release 10.2.0.5.0 - Production on Tue May 27 18:44:36 2014

Copyright (c) 1982, 2007, Oracle.  All rights reserved.

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-00554: initialization of internal recovery manager package failed

RMAN-04005: error from target database: 

ORA-28041: Authentication protocol internal error

We got this error after applying PSU12 to one of our 10.2.0.5 production database. It was on a HP-UX Itanium 64 bit server. We applied the PSU successfully, but later we noticed that it gave some WARNINGs.

Here are the warnings;

[EN] EMD upload error: uploadXMLFiles skipped :: OMS version not checked yet.

Problem:


[XXXPRO1]/oracle/product/11.1.0/agent11g/bin $ ./emctl upload agent
Oracle Enterprise Manager 11g Release 1 Grid Control 11.1.0.1.0
Copyright (c) 1996, 2010 Oracle Corporation.  All rights reserved.
---------------------------------------------------------------
EMD upload error: uploadXMLFiles skipped :: OMS version not checked yet. If this issue persists check trace files for ping to OMS related errors.

Solution:

When you get this warning you should also check "emctl status agent" output. 


[XXXPRO1]/oracle/product/11.1.0/agent11g/bin $ ./emctl status agent
Oracle Enterprise Manager 11g Release 1 Grid Control 11.1.0.1.0 
Copyright (c) 1996, 2010 Oracle Corporation.  All rights reserved.
---------------------------------------------------------------
Agent Version     : 11.1.0.1.0
OMS Version       : 11.1.0.1.0
Protocol Version  : 11.1.0.0.0
Agent Home        : /oracle/product/11.1.0/agent11g/hostxxx01
Agent binaries    : /oracle/product/11.1.0/agent11g
Agent Process ID  : 8091
Parent Process ID : 8080
Agent URL         : https://hostxxx01:1830/emd/main
Repository URL    : https://hostemgrid01:1159/em/upload
Started at        : 2012-06-21 11:13:55
Started by user   : oracle
Last Reload       : 2012-06-21 11:13:55
Last successful upload                       : (none)
Last attempted upload                        : (none)
Total Megabytes of XML files uploaded so far :     0.00
Number of XML files pending upload           :      273
Size of XML files pending upload(MB)         :    52.42
Available disk space on upload filesystem    :    47.97%
Collection Status                            : Disabled by Upload Manager
Last attempted heartbeat to OMS              : 2012-06-21 11:26:12
Last successful heartbeat to OMS             : unknown
---------------------------------------------------------------
Agent is Running and Ready