John Weatherman[SMTP:[EMAIL PROTECTED]] wrote:
> >In general, I agree with the majority opinion that seems to be saying
> that
> >Oracle chugs along
> >perfectly happy when the date changes. Time based recovery might have
> some
> >issues, so I'd
> >run a hot after the change so I could use it as
In general, I agree with the majority opinion that seems to be saying that
Oracle chugs along
perfectly happy when the date changes. Time based recovery might have some
issues, so I'd
run a hot after the change so I could use it as my basis in a restore.
The real question in my mind is ... What
I imagine it would depend on the application.
Some people are stuck working on 24x7 databases, others are lucky enough to
have a life.
:>)
--Walt Weaver
Bozeman, Montana
-Original Message-
Sent: Wednesday, July 24, 2002 10:44 AM
To: Multiple recipients of list ORACLE-L
Shut the dat
Shut the database DOWN for 1.25 hours?
Who in the heck can afford THAT!
You are *way* off base my friend. If I suggested to my client that they
need to shut the database down because of a time change, they would send me
out on a rail - and I would deserve it.
Bad idea.
Tom Mercadante
Oracle C
I think that you will understand it better if you consider 2 scenario's:
1) RMAN backup from time 13:00 is newer then the backup taken at 13:45.
2) You get Enron accounting when the feds discover that invoice number 123
was issued after invoice 124.
There are a lot of things, application and /
yes , but time based incomplete recovery could create problems if he doesnt
take a full
backup after the os-time-change .
-Original Message-
Sent: Wednesday, July 24, 2002 6:39 PM
To: Multiple recipients of list ORACLE-L
Oracle has no concept wrt. the date & time of Operating System for
Oracle has no concept wrt. the date & time of Operating System for running
individually as a product. It just takes the timestamp in certain DML's
while updating and inserting the rows having DATE as datatype. Nothing more
than this.
Oracle works on the mechanism of SCN ie. System Change Numb
