Database - RAC/Scalability (MOSC)

MOSC Banner

gv$archived_log shows "gaps" in SCN between NEXT_CHANGE# and FIRST_CHANGE# of the next log. Should I

edited Mar 29, 2011 3:51AM in Database - RAC/Scalability (MOSC) 4 commentsAnswered ✓
 Hi,

I've got a 3-node RAC running 10g (10.2.0.4) on AIX. It all runs smoothly but I have noticed some strange behaviour in GV$ARCHIVED_LOG.

Following an 'open database resetlogs', there seems to be "gap" in SCN between the NEXT_CHANGE# value on one archivelog #1 and the FIRST_CHANGE# on the subsequent archivelog #2.

All following archivelogs have an exact match, where the prior archivelog NEXT_CHANGE# = following archivelog FIRST_CHANGE#. This is true for archivelogs #2, #3, #4, #5...etc

All the archivelogs are present and there are no gaps in sequence & thread.

So, the question is "Should I worry"? Will this compromise my ability to recover this database? Also, this database is the source for a datawarehouse stage database. Am I losing transactions?

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