AIX

I want to update the ntp.conf file on different client AIX servers to so they may have to correct
ntp SERVERname info. In a few words, the clients server should have the correct NTP server name.
How can I update the NTP clients and not have time synchronization problem. How can I update client servers' ntp.conf file and make sure that
clocks are in synchronization with the master clock.
How can I avoid the clock from changing in a negative direction after updating the ntp.conf file?
Should I update an ntp.conf file with the correct info and scp that file to the clients to replace the previous ntp.conf file?
Should I edit the ntp.conf file in each client and then do a refresh -s xntpd?
What do you think is the best way to go about have the same ntp.conf file on clients and master server without changing in a negative direction?

Thanks in advance?

For question #1 I have no clue what are you talking about , I'll check the documentation and I may post here later.
For question #2 I See no harm SCPing ntp.conf to replace the original , But you'd better to backup the original 1st
For question #3 You may issue the command

Code:

refresh -s xntpd

after making changes Please refer to steps below On Client
For question #4 I have no clue what are you talking about , I'll check the documentation and I may post here later.

Please see steps here for more information

On server

Verify that you have a suitable NTP server. Enter:

Code:

# lssrc -ls xntpd

NOTE: Sys peer should show a valid server or 127.127.1.0.

If the server is "insane", you will need to correct it by adding a server line to /etc/ntp.conf and restarting xntpd. This can be done by following these steps:

Code:

# vi /etc/ntp.conf

Add:
server 127.127.1.0
Double check that "broadcast client" is commented out.

Code:

# stopsrc -s xntpd

Code:

# startsrc -s xntpd

NOTE: If the server runs databases, use the -x flag to prevent the clock from changing in a negative direction. Enter the following:

Code:

# startsrc -s xntpd -a "-x"

Repeat Step 1 to verify that the server is synched. This process can take up to 12 minutes.

On client

Verify that you have a server suitable for synchronization. Enter:

Code:

# ntpdate -d ip.address.of.server

The offset must be less than 1000 seconds for xntpd to synch. If the offset is greater than 1000 seconds, change the time manually on the client and run the ntpdate -d again.

If you get the message, "no server suitable for synchronization found", verify xntpd is running on the server (see above) and that no firewalls are blocking port 123.
Specify your xntp server in /etc/ntp.conf, enter:

Code:

# vi /etc/ntp.conf

(Comment out the "broadcastclient" line and add server ip.address.of.server prefer.)

Leave the driftfile and tracefile at their defaults.
Start the xntpd daemon:

Code:

# startsrc -s xntpd

(Use the -x flag if it is appropriate for your environment.)

Uncomment xntpd from /etc/rc.tcpip so it will start on a reboot.

Code:

# vi /etc/rc.tcpip

Uncomment the following line:

start /usr/sbin/xntpd "$src_running"

If using the -x flag, add "-x" to the end of the line. You must include the quotes around the -x.

Verify that the client is synched.

Code:

# lssrc -ls xntpd

NOTE: Sys peer should display the IP address or name of your xntp server. This process may take up to 12 minutes.

Hello thank you for your kind answer. I also have this documentation by IBM that you posted on the forum. What I was really trying to find out is how can I update the ntp.conf file on production server without affecting ORACLE running on production server. I want to avoid the clock from changing in a negative direction after updating the ntp.conf file on the client servers and keep this client servers in sync with the with the master clock on the main NTP server.

Any idea how to proceed wit that?

All I know as follows I do always stop database process before changing time/date as precaution procedure .
I do know that there is sync between database and OS clock , but there is some ways to sync database with OS's time/date after changes e.g ( NTP sync ) .
You'd better to wait for someone to answer your quires