Re: SYSDATE time different from server time

From: Sreejith Nair <sreejithsna_at_gmail.com>
Date: Wed, 3 Jun 2015 07:19:02 +0530
Message-ID: <27be1d1b-bf9c-44ab-a052-de3595666e92_at_SSNs-iPhone>

It depends on the way you are planning to migrate. But generally what you can do is create a listener in the new server and start it with different time zone. You should use this listener for your newly migrated database using local_listener parameter.

Regards
Sreejith

Sent from my iPhone

On 3 Jun 2015 3:49 AM +0530, MARK BRINSMEAD<mark.brinsmead_at_gmail.com>, wrote:
> Yes.Certainly, this is possible.Its been discussed here before.
>
> Perhaps the question you should be asking is how can you do it in a way that is safe and reliable.Perhaps the best way to go would be to run the different-timezone-database in a virtual machine that operates in the appropriate timezone.There will be far fewer opportunities for "accidents" this way.
>
> On Tue, Jun 2, 2015 at 4:58 PM, Dennis Williams<oracledba.williams_at_gmail.com(mailto:oracledba.williams_at_gmail.com)>wrote:
> > List,
> >
> > We are trying to migrate a database from a standalone server to a server that hosts many databases. The problem is that the server time is different from the time currently used (different time zone). The application calls SYSDATE. The application can't be modified and there are many years of data with the current time setting.
> >
> > Is there a way to have SYSDATE return a time different from the server? Like a few hours ahead or behind?
> >
> > Oracle version 11.2.0.4
> >
> > Thank you,
> > Dennis Williams
> >
>
>
>

--
http://www.freelists.org/webpage/oracle-l

Received on Wed Jun 03 2015 - 03:49:02 CEST