Standby dtabase archivelog status

Question

I have noticed that archived log status (applied or not) and PROTECTION_MODE,PROTECTION_LEVEL (both form V$ views) are different on standby database and on primary database what is the reason and what is the impact to the system of tease differences ???
Is it possible to correct this
I have physical standby database on RHEL4 with 10gR2

Answer 1

Hear will bee results from selects where you can see differences:
select SEQUENCE#,STANDBY_DEST,APPLIED,ARCHIVED,DELETED,CREATOR,REGISTRAR,STATUS from v$archived_log;
standby db returns
53 NO YES YES NO ARCH RFS A
54 NO YES YES YES FGRD FGRD D
54 NO YES YES NO ARCH RFS A
55 NO YES YES NO ARCH RFS A
56 NO YES YES NO ARCH RFS A
57 NO YES YES NO ARCH RFS A
but primary
53 NO NO YES NO FGRD FGRD A
53 YES YES YES NO ARCH ARCH A
54 NO NO YES NO ARCH ARCH A
55 NO NO YES NO ARCH ARCH A
56 NO NO YES NO ARCH ARCH A
54 YES NO YES NO ARCH ARCH A
55 YES NO YES NO ARCH ARCH A
56 YES YES YES NO ARCH ARCH A
57 NO NO YES NO ARCH ARCH A
57 YES YES YES NO ARCH ARCH A
what can bee the reason of such differences in applied or not if
redo shipping is done automatically by ARCH, mode ASYNC
protection mode: maximum performance
there where no problems with network,both instances are running on the same machine
when the archlog's was created a script was running who inserted data into some table
to make natural redo grow and redo switch.
PS. I have red the b14239.pdf carefully and understood it well.