10g redolog Files have all only one change date

Hi,:confused:

i am a newbee ( not only in this forum, as a dba too ).
So i have this question:
We have som ORACLE 8i DB-Servers and one 10g DB-Server.
The DB/Instances wil be shutdowned immediate via scripts
After the offline Backup they will be startet ( under 10g
via ORADIM -STARTTYPE inst )
On the 8i Servers the REDOLOG Files (3 Groups/ 2 Members) have a
at every LOG-Switch a change-Date/Time ( seen under Windows/
View/details).This is correct an can be viewed in the ALERT-log
At our 10g Server with a very small DB ( 800 MB Size Usertablespace)
there can`t see a change DATE/Time but in the ALERT-log seems
all to be correct.
The REDOLOG-Files have the Date after the start of the DB/Instance.
The DB is in archivelog-mode.
The REDOLOG-Files have 10 MB size.

Are there any problems ( time i.e. ) or misconfigurations visible and
what´s the reason ?
Can you help / explain this behavior of 10g ?
Here a part of the ALERT-LOG:

SYS auditing is disabled
Starting up ORACLE RDBMS Version: 10.1.0.2.0.
System parameters with non-default values:
processes = 150
sga_max_size = 188743680
__shared_pool_size = 83886080
__large_pool_size = 4194304
__java_pool_size = 4194304
sga_target = 188743680
control_files = D:\ORADATA\test1\CONTROL01.CTL, D:\ORADATA\test1\CONTROL02.CTL, D:\ORADATA\test1\CONTROL03.CTL
db_block_size = 8192
__db_cache_size = 92274688
compatible = 10.1.0.2.0
log_archive_start = TRUE
log_archive_dest = D:\oradata\test1\archive
log_archive_format = ARC%S_%R.%T
log_checkpoint_interval = 100000
log_checkpoint_timeout = 1800
db_file_multiblock_read_count= 16
log_checkpoints_to_alert = TRUE
undo_management = AUTO
undo_tablespace = UNDOTBS1
remote_login_passwordfile= EXCLUSIVE
db_domain =
dispatchers = (PROTOCOL=TCP) (SERVICE=test1XDB)
job_queue_processes = 10
background_dump_dest = D:\ORADATA\ADMIN\test1\BDUMP
user_dump_dest = D:\ORADATA\ADMIN\test1\UDUMP
core_dump_dest = D:\ORADATA\ADMIN\test1\CDUMP
sort_area_size = 65536
db_name = test1
open_cursors = 300
sql_trace = FALSE
pga_aggregate_target = 52428800
Deprecated system parameters with specified values:
log_archive_start
End of deprecated system parameter listing
PMON started with pid=2, OS id=5764
MMAN started with pid=3, OS id=5816
DBW0 started with pid=4, OS id=5616
LGWR started with pid=5, OS id=3332
CKPT started with pid=6, OS id=4436
SMON started with pid=7, OS id=1716
RECO started with pid=8, OS id=2880
CJQ0 started with pid=9, OS id=4316
Sat Mar 17 02:44:41 2007
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
starting up 1 shared server(s) ...
Oracle Data Guard is not available in this edition of Oracle.
Sat Mar 17 02:44:41 2007
alter database mount exclusive
Sat Mar 17 02:44:41 2007
Controlfile identified with block size 16384
Sat Mar 17 02:44:45 2007
Setting recovery target incarnation to 2
Sat Mar 17 02:44:45 2007
Successful mount of redo thread 1, with mount id 4203449049
Sat Mar 17 02:44:45 2007
Database mounted in Exclusive Mode.
Completed: alter database mount exclusive
Sat Mar 17 02:44:45 2007
alter database open
Sat Mar 17 02:44:45 2007
LGWR: STARTING ARCH PROCESSES
ARC0 started with pid=13, OS id=464
ARC0: Archival started
ARC1 started with pid=14, OS id=2976
Sat Mar 17 02:44:45 2007
LGWR: STARTING ARCH PROCESSES COMPLETE
Sat Mar 17 02:44:45 2007
LGWR: Primary database is in CLUSTER CONSISTENT mode
Sat Mar 17 02:44:45 2007
Maximum redo generation record size = 120832 bytes
Maximum redo generation change vector size = 116476 bytes
Private_strands 3 at log switch
Sat Mar 17 02:44:46 2007
ARC0: Becoming the 'no FAL' ARCH
Sat Mar 17 02:44:46 2007
ARC0: Becoming the 'no SRL' ARCH
Sat Mar 17 02:44:46 2007
Thread 1 opened at log sequence 19170
Current log# 1 seq# 19170 mem# 0: D:\ORADATA\test1\REDO01_1.LOG
Current log# 1 seq# 19170 mem# 1: D:\ORADATA\test1\REDO01_2.LOG
Successful open of redo thread 1
Sat Mar 17 02:44:46 2007
SMON: enabling cache recovery
Sat Mar 17 02:44:47 2007
Incremental checkpoint up to RBA [0x4ae2.2737.0], current log tail at RBA [0x4ae2.2737.0]
Sat Mar 17 02:44:47 2007
Successfully onlined Undo Tablespace 1.
Sat Mar 17 02:44:47 2007
SMON: enabling tx recovery
Sat Mar 17 02:44:47 2007
Database Characterset is WE8MSWIN1252
Sat Mar 17 02:44:47 2007
Published database character set on system events channel
Sat Mar 17 02:44:47 2007
ARC1: Archival started
Sat Mar 17 02:44:47 2007
All processes have switched to database character set
ARC1: Becoming the heartbeat ARCH
Sat Mar 17 02:44:48 2007
Starting background process QMNC
QMNC started with pid=15, OS id=680
Sat Mar 17 02:44:49 2007
replication_dependency_tracking turned off (no async multimaster replication found)
Sat Mar 17 02:44:50 2007
Starting background process MMON
MMON started with pid=16, OS id=4428
Sat Mar 17 02:44:50 2007
Starting background process MMNL
MMNL started with pid=17, OS id=304
Sat Mar 17 02:44:51 2007
Completed: alter database open
Sat Mar 17 03:00:14 2007
Private_strands 7 at log switch
Beginning log switch checkpoint up to RBA [0x4ae3.2.10], SCN: 0x0000.04bde83d
Thread 1 advanced to log sequence 19171
Current log# 2 seq# 19171 mem# 0: D:\ORADATA\test1\REDO02_1.LOG
Current log# 2 seq# 19171 mem# 1: D:\ORADATA\test1\REDO02_2.LOG
Sat Mar 17 03:00:14 2007
ARC1: Evaluating archive log 1 thread 1 sequence 19170
Committing creation of archivelog 'D:\ORADATA\test1\ARCHIVE\ARC19170_0559826659.001'
Sat Mar 17 03:15:34 2007
Incremental checkpoint up to RBA [0x4ae2.2cff.0], current log tail at RBA [0x4ae3.267d.0]
Sat Mar 17 03:30:05 2007
Completed checkpoint up to RBA [0x4ae3.2.10], SCN: 79554621
Sat Mar 17 03:46:24 2007
Incremental checkpoint up to RBA [0x4ae3.2707.0], current log tail at RBA [0x4ae3.40ed.0]
Sat Mar 17 04:00:42 2007
Private_strands 7 at log switch
Beginning log switch checkpoint up to RBA [0x4ae4.2.10], SCN: 0x0000.04bdf715
Thread 1 advanced to log sequence 19172
Current log# 3 seq# 19172 mem# 0: D:\ORADATA\test1\REDO03_1.LOG
Current log# 3 seq# 19172 mem# 1: D:\ORADATA\test1\REDO03_2.LOG
Sat Mar 17 04:00:42 2007
ARC1: Evaluating archive log 2 thread 1 sequence 19171
Committing creation of archivelog 'D:\ORADATA\test1\ARCHIVE\ARC19171_0559826659.001'
Sat Mar 17 04:17:14 2007
Incremental checkpoint up to RBA [0x4ae3.4232.0], current log tail at RBA [0x4ae4.1fd6.0]
Sat Mar 17 04:30:43 2007
Completed checkpoint up to RBA [0x4ae4.2.10], SCN: 79558421
Sat Mar 17 04:48:02 2007
Incremental checkpoint up to RBA [0x4ae4.1fd7.0], current log tail at RBA [0x4ae4.39d3.0]
Sat Mar 17 05:00:09 2007
Private_strands 7 at log switch
Beginning log switch checkpoint up to RBA [0x4ae5.2.10], SCN: 0x0000.04be044a
Thread 1 advanced to log sequence 19173
Current log# 4 seq# 19173 mem# 0: D:\ORADATA\test1\REDO04_1.LOG
Current log# 4 seq# 19173 mem# 1: D:\ORADATA\test1\REDO04_2.LOG
Sat Mar 17 05:00:09 2007
ARC1: Evaluating archive log 3 thread 1 sequence 19172
Committing creation of archivelog 'D:\ORADATA\test1\ARCHIVE\ARC19172_0559826659.001'
Sat Mar 17 05:18:52 2007
Incremental checkpoint up to RBA [0x4ae4.39d5.0], current log tail at RBA [0x4ae5.1dd0.0]
Sat Mar 17 05:31:00 2007
Completed checkpoint up to RBA [0x4ae5.2.10], SCN: 79561802
Sat Mar 17 05:49:46 2007
Incremental checkpoint up to RBA [0x4ae5.1ddc.0], current log tail at RBA [0x4ae5.359e.0]
Sat Mar 17 06:00:58 2007
Private_strands 7 at log switch
Beginning log switch checkpoint up to RBA [0x4ae6.2.10], SCN: 0x0000.04be11c7
Thread 1 advanced to log sequence 19174
Current log# 1 seq# 19174 mem# 0: D:\ORADATA\test1\REDO01_1.LOG
Current log# 1 seq# 19174 mem# 1: D:\ORADATA\test1\REDO01_2.LOG
Sat Mar 17 06:00:58 2007
ARC1: Evaluating archive log 4 thread 1 sequence 19173
Committing creation of archivelog 'D:\ORADATA\test1\ARCHIVE\ARC19173_0559826659.001'
Sat Mar 17 06:20:33 2007
Incremental checkpoint up to RBA [0x4ae5.35a4.0], current log tail at RBA [0x4ae6.1a8c.0]
Sat Mar 17 06:31:50 2007
Completed checkpoint up to RBA [0x4ae6.2.10], SCN: 79565255
Sat Mar 17 06:51:20 2007
Incremental checkpoint up to RBA [0x4ae6.1a91.0], current log tail at RBA [0x4ae6.3409.0]
Sat Mar 17 07:00:05 2007
Private_strands 7 at log switch
Beginning log switch checkpoint up to RBA [0x4ae7.2.10], SCN: 0x0000.04be203c
Thread 1 advanced to log sequence 19175
Current log# 2 seq# 19175 mem# 0: D:\ORADATA\test1\REDO02_1.LOG
Current log# 2 seq# 19175 mem# 1: D:\ORADATA\test1\REDO02_2.LOG
Sat Mar 17 07:00:05 2007
ARC1: Evaluating archive log 1 thread 1 sequence 19174
Committing creation of archivelog 'D:\ORADATA\test1\ARCHIVE\ARC19174_0559826659.001'
Sat Mar 17 07:00:21 2007
Private_strands 7 at log switch

Quote:

---

Originally Posted by hbuche

The DB/Instances wil be shutdowned immediate via scripts
After the offline Backup they will be startet ( under 10g via ORADIM -STARTTYPE inst )

---

Just a question. If your backup strategy calls for offline -Cold Backup, why do you bother in having instances in archivelog-mode?

so you can recover of course!

As a rule of thumbs...

Cold Backup Strategy => NoArchiveLog mode
Hot Backup Strategy => ArchiveLog mode

Just my two cents

thats just rubbish, sorry pure rubbish

I agree it is rubbish!

Hello back, thanks for all answers.
But my question is not answered.
We dont need a 7/24 online DB.
Teh redolog and Archive-Files are on one Server ( no ressources
for save at another location )
So that is the reason, why we save via Backup once daily on tapes.
Please , if it is ppossible, give me a explanation
for the not changed DATE/Time stamps of the REDOLOG-Files in the 10g RDBMS.
Tahnks al lot

so you are saying the timestamp on the actual file never gets changed? is that right? its not totally clear

How about shows us a ls -l of your logfiles?

Following would help as well

Code:

---


alter session set nls_date_format = 'yyyymmdd hh24miss';

select * from v$log;

alter system switch logfile;

select * from v$log;

and ls -l of redo logs

---

bit trickier on window - but im still failing to see the problem

Does anyone have an explanation for the date/time stamps?
I am experiencing the same thing.

Regards,

Alex