| Oracle server shutdown [message #549553] |
Sun, 01 April 2012 07:20  |
 |
chandrasekhar.datrika
Messages: 1
Registered: February 2012
Location: hyderabad
|
Junior Member |
|
|
Hi Team,
We have changed the SYSDATE to 03-FEB-1994 in our AIX machine where oracle11g database is running.
Once the sysdate is changed db and listner are getting down immediately and its generating the core in $ORACLE_HOME/dbs
This AIX machine is for PT test and as per one requirement we are changing the sysdate.
Moreover, we found that database is getting down if we change the sysdate till 1999. If we change the sysdate to 2000, then we are not seeing any issue.
Below point is for additional info. After changing the sysdate and trying to connect to the db user, we are getting the below issue.
$ sqlplus '/as sysdba'
Segmentation issue (Core dump)
Please suggest is there any setting avoid this issue? Thank you in advance.
- Rama
|
|
|
|
|
|
|
|
| Re: Oracle server shutdown [message #549560 is a reply to message #549556] |
Sun, 01 April 2012 08:42  |
John Watson
Messages: 8964
Registered: January 2010
Location: Global Village
|
Senior Member |
|
|
|
The time can change at any time: NTP will make adjustments as needed, whether a datbase instance is running or not. If I remember correctly, setting the clock backwards is not supported, so you need to configure the NTP daemon to force slewing instead of stepping. But to slew the time back to 1994 would take decades.
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
