DIA-48313 and DIA-48322 Errors while purging files using adrci

Few months back I have upgraded Oracle Clusterware 11.1.0.6 to Oracle Grid Infrastructure 11.2.0.3 on Solaris Sparc machines. I invoked adrci of the new Oracle Gridinfrastructure home and tried to purge the logs and trace files in the listener's diagnostics destination directory but encountered the following error.

On first machine:
$adrci

ADRCI: Release 11.2.0.3.0 - Production on Tue Oct 23 10:24:54 2012

Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.

ADR base = "/misc/oracle"
adrci> show home
ADR Homes:
diag/tnslsnr/xxx/listener_xxx
adrci> purge
DIA-48313: Updates not allowed on ADR relation [INCIDENT] of Version=3

adrci> migrate schema
Schema migrated.
adrci> purge
adrci> quit

On second machine:

$adrci

ADRCI: Release 11.2.0.3.0 - Production on Tue Oct 23 10:26:03 2012

Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.

ADR base = "/misc/oracle"
adrci> purge
DIA-48322: Relation [INCIDENT] of ADR V[2] incompatible with V[2] tool
DIA-48210: Relation Not Found
DIA-48166: error with opening ADR block file because file does not exist [/misc/oracle/diag/tnslsnr/yyy/listener/metadata/INCIDENT.ams] [0]

adrci> show home
ADR Homes:
diag/tnslsnr/yyy/listener
adrci> migrate schema
Schema migrated.
adrci> purge
adrci> quit


The error is due to the mismatch in the metadata and one can use "migrate schema" command(as shown above) to upgrade the metadata of the corresponding diagnostics destination to the level mandated by the invoked adrci utility.

Similarly for errors like "DIA-48318: ADR Relation [INCIDENT] of version=4 cannot be supported", one has to downgrade the schema using the higher level adrci(adrci>migrate schema -downgrade) and then use low level adrci to get away with the error.