on 11-17-2009 5:06 PM
Hi
We just upgraded BRTOOLS to 640 (51) in our production system; since then redolog file is not showing "ACTIVE".
See the resutls
SQL> select group#, status from v$log;
GROUP# STATUS
-
-
11 INACTIVE
12 INACTIVE
13 CURRENT
14 INACTIVE
SQL>
In the morning aslo it was as above status; we did altered the switch log and one group was showing correctly as ACTIVE and its next group was showing CURRENT but now again it changed to above status.
Can you please let me know why it is not showing status "ACTIVE"
Thanks
Very good answers with quick response....Great keep it up.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Kasinath,
the official documentation is your friend:
http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/dynviews_1150.htm#I1030127
ACTIVE - Log is active but is not the current log. It is needed for crash recovery. It may be in use for block recovery. It may or may not be archived.
So of course, if you perform a logswitch the data is not completely checkpointed and so it is still needed for crash recovery. After a while all the corresponding data is written down to the data files and so the status changes to INACTIVE.
Regards
Stefan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Kasinath,
> In this case do we need to take any action?
You can't do anything about it .. this is a normal behaviour and works as designed.
In case of an oracle database crash .. oracle knows that the redo log files with status ACTIVE / CURRENT are needed for a crash recovery (=complete recovery) and will apply them.
The only case when you are in real trouble is, if your database crashes and you have lost the online redo log files with status ACTIVE and they are not archived until the crash.
But as already mentioned .. oracle is working as designed.
Regards
Stefan
Hi Stefan
My issue is no group is showing "ACTIVE" in four of the redolog groups; that is my concern.
See the details below
SQL> select group#, status from v$log;
GROUP# STATUS
-
-
11 INACTIVE
12 INACTIVE
13 CURRENT
14 INACTIVE
SQL>
As per as I know one group should show as ACTIVE next one should show as CURRENT; in this case ACTIVE group is not showing in above.
Please let me know why it is not showing ACTIVE
Thanks
Hello Kasinath,
> Why it is not like that in this case?
Because of in your other databases the corresponding buffers are not flushed to the data files until yet (checkpoint not completed).
You can verify this by comparing the SCNs of the data file headers and the SCNs that are covered in the redo log groups.
Regards
Stefan
User | Count |
---|---|
84 | |
25 | |
12 | |
9 | |
6 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.