• Restarting Ingres

    From Steve@21:1/5 to All on Sun Jun 13 08:14:42 2021
    Hi folks

    Where I work I restart the prod and DR Ingres installations on a weekly basis. I do this out of tradition, rather than because there is some noticeable improvement in restarting Ingres.

    At times during COVID I have restarted DR less and there has been no issue.

    Interested to know how often others restart their prod and/or DR installations. Are there any recommendations regarding this?

    Thanks
    Steve

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Martin Bowes@21:1/5 to Steve on Sun Jun 13 16:47:40 2021
    To: info-ingres@lists.planetingres.org (info-ingres@lists.planetingres.org)

    Hi Steve,

    We tend to restart only when the situation demands. This means we would normally achieve uptime measured in months. I've not seen a compelling argument to stop and restart more often than that.

    Marty

    -----Original Message-----
    From: Steve <s.anderson.au@gmail.com>
    Sent: 13 June 2021 16:15
    To: info-ingres@lists.planetingres.org
    Subject: [Info-ingres] Restarting Ingres

    Hi folks

    Where I work I restart the prod and DR Ingres installations on a weekly basis. I do this out of tradition, rather than because there is some noticeable improvement in restarting Ingres.

    At times during COVID I have restarted DR less and there has been no issue.

    Interested to know how often others restart their prod and/or DR installations. Are there any recommendations regarding this?

    Thanks
    Steve
    _______________________________________________
    Info-ingres mailing list
    Info-ingres@lists.planetingres.org https://lists.planetingres.org/mailman/listinfo/info-ingres

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Steve@21:1/5 to Martin Bowes on Sun Jun 13 20:28:17 2021
    On Monday, June 14, 2021 at 2:48:09 AM UTC+10, Martin Bowes wrote:

    We tend to restart only when the situation demands. This means we would normally achieve uptime measured in months. I've not seen a compelling argument to stop and restart more often than that.

    Thanks Marty.

    Can I ask what situations, apart from patching or upgrading, might cause you to restart Ingres?

    Steve

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul White@21:1/5 to Steve on Mon Jun 14 14:11:29 2021
    Hi Steve,

    Our client's MS Windows installations are restarted every 1 to 3 months
    due to OS patches and hosting provider requirements. I think the longest continues runtime on one server was about 2 years.

    The Linux/Unix servers get a restart about once a year since Ingres
    supports 24x7 operations. Generally I don't patch the OS on these
    servers. They run for 4 to 5 years trouble free then are migrated to new Infrastructure/OS together with a major Ingres upgrade.   The longest
    runtime I recall was about 2 years on a Solaris V880.

    The DR / replication servers are restarted more often for testing purposes.

    Exceptional outages occur when a power pole is knocked down, UPS fails
    or the computer room air conditioner fails.

    Paul


    On 14/06/2021 1:28 pm, Steve wrote:
    On Monday, June 14, 2021 at 2:48:09 AM UTC+10, Martin Bowes wrote:

    We tend to restart only when the situation demands. This means we would normally achieve uptime measured in months. I've not seen a compelling argument to stop and restart more often than that.
    Thanks Marty.

    Can I ask what situations, apart from patching or upgrading, might cause you to restart Ingres?

    Steve
    _______________________________________________
    Info-ingres mailing list
    Info-ingres@lists.planetingres.org https://lists.planetingres.org/mailman/listinfo/info-ingres

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Martin Bowes@21:1/5 to Steve on Mon Jun 14 06:29:15 2021
    To: info-ingres@lists.planetingres.org (info-ingres@lists.planetingres.org)

    We very occasionally get a situation which we call a stuck lock list where a session has exited but the lock list remains. The only way out is to restart the installation. It is rare, and I would guess of the 50+ installations that we field, that such an
    event would happened just a few times annually.

    Marty

    -----Original Message-----
    From: Steve <s.anderson.au@gmail.com>
    Sent: 14 June 2021 04:28
    To: info-ingres@lists.planetingres.org
    Subject: Re: [Info-ingres] Restarting Ingres

    On Monday, June 14, 2021 at 2:48:09 AM UTC+10, Martin Bowes wrote:

    We tend to restart only when the situation demands. This means we would normally achieve uptime measured in months. I've not seen a compelling argument to stop and restart more often than that.

    Thanks Marty.

    Can I ask what situations, apart from patching or upgrading, might cause you to restart Ingres?

    Steve
    _______________________________________________
    Info-ingres mailing list
    Info-ingres@lists.planetingres.org https://lists.planetingres.org/mailman/listinfo/info-ingres

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Adrian Williamson@21:1/5 to Martin Bowes on Mon Jun 14 09:12:28 2021
    To: s.anderson.au@gmail.com (Steve)
    To: info-ingres@lists.planetingres.org

    Hi,

    I have one customer where we reboot the Windows server each week (it is
    one box solution : OpenROAD & Ingres running on Terminal Services ) .

    I do that as it means that any minor leaks from any software do not
    snowball.

    Not that I've witnessed memory leaks, but it gives me the warm feeling that
    it reboots itself rather than me getting a call out cause the server has stopped.

    Gives me the illusion of being in control.

    Twelve years now and no outages.*

    Cheers

    Adrian

    *Well apart from when the 'employees' of the Multinational services company which runs the infrastructure decide to just pull the power on the VM
    causing ''The last shutdown was unexpected' message to appear in the event
    log. We have educated them to the benefits of an orderly shutdown on
    windows.

    -----Original Message-----
    From: info-ingres-bounces@lists.planetingres.org <info-ingres-bounces@lists.planetingres.org> On Behalf Of Martin Bowes
    Sent: 14 June 2021 07:29
    To: Steve <s.anderson.au@gmail.com>; info-ingres@lists.planetingres.org Subject: Re: [Info-ingres] Restarting Ingres

    We very occasionally get a situation which we call a stuck lock list where a session has exited but the lock list remains. The only way out is to restart the installation. It is rare, and I would guess of the 50+ installations
    that we field, that such an event would happened just a few times annually.

    Marty

    -----Original Message-----
    From: Steve <s.anderson.au@gmail.com>
    Sent: 14 June 2021 04:28
    To: info-ingres@lists.planetingres.org
    Subject: Re: [Info-ingres] Restarting Ingres

    On Monday, June 14, 2021 at 2:48:09 AM UTC+10, Martin Bowes wrote:

    We tend to restart only when the situation demands. This means we would
    normally achieve uptime measured in months. I've not seen a compelling
    argument to stop and restart more often than that.

    Thanks Marty.

    Can I ask what situations, apart from patching or upgrading, might cause you
    to restart Ingres?

    Steve
    _______________________________________________
    Info-ingres mailing list
    Info-ingres@lists.planetingres.org https://lists.planetingres.org/mailman/listinfo/info-ingres _______________________________________________
    Info-ingres mailing list
    Info-ingres@lists.planetingres.org https://lists.planetingres.org/mailman/listinfo/info-ingres

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)