Hangup transport archive log in primary and archive log apply

Question

Hi
I am building Dataguard from 3-node primary cluster to 3-node standby cluster
Oracle Version:10.2.0.4
Operating system : LInux 64 bit
After I restored standby database, I configured dataguard broker with wrong unique_name parameter in standby cluster using grid control
after I corrected mistake, disabled dataguard broker parameters, delete dataguard broker files and reboot standby cluster but don't reboot primary cluster because is production enviroment.
I have problem with following symptoms:
-Hangup transport archive log while recovery database in standby then gap archivelog is produced.
-Copy and register all archivelog gap in standby but don't apply archive log.
- Don't register like applied in v$archived_log in primary the archives applied in standby manually.
-RMAN command: "backup as COMPRESSED BACKUPSET tag 'Backup Full Disk' archivelog all not backed up delete all input;"
don't delete in primary archive log applied because message " archive log is necessary"
I think that is necessary reboot primary cluster.
Please helpme

Answer 1

Post the results of queries. It is difficult to understand.
post from primary
SQL> select thread#,max(sequence#) from v$archived_log group by thread#;select     ds.dest_id id
,     ad.status
,     ds.database_mode db_mode
,     ad.archiver type
,     ds.recovery_mode
,     ds.protection_mode
,     ds.standby_logfile_count "SRLs"
,     ds.standby_logfile_active active
,     ds.archived_seq#
from     v$archive_dest_status     ds
,     v$archive_dest          ad
where     ds.dest_id = ad.dest_id
and     ad.status != 'INACTIVE'
order by
     ds.dest_id
Post from standby.
SQL> select thread#,max(sequence#) from v$archived_log where applied='YES' group by thread#;
select * from v$managed_standby;