High Availability Data Guard, Sharding and Global Data Services (MOSC)

MOSC Banner

After starting the standby database using alter database recover managed standby database using curr

edited Jan 10, 2018 1:21AM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 3 commentsAnswered ✓

After starting the standby database using alter database recover managed standby database using current logfile disconnect; when I check the sequence# and the applied status from v$archived_log, it says that the last log is "In-memory".   Why is that?

If there is a log switch on the primary, the log is sent to the standby.  But again the last log will say that it is in-memory.  I thought that the applied status should say 'YES'

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center