1. Forum
  2. USENET
  3. comp.databases.ingres

  • Re: [Info-ingres] Checking logging status of a session

    From Steve@s.anderson.au@gmail.com to comp.databases.ingres on Fri Aug 28 02:54:12 2020
    From Newsgroup: comp.databases.ingres

    On Wednesday, August 5, 2020 at 6:13:10 AM UTC+10, Roy Hann wrote:
    Laframboise wrote:

    Logging to a Canadian, involves cutting down trees ..... :)
    I did say the word is overloaded! :-)

    Roy
    No, I didn't mean the Canadian-logging! :D
    Sorry, transaction logging.
    I was editing a shell script process where someone had commented out ALL the error handling! Some of the commented out error handling code indicated the database would be marked inconsistent if the transaction failed with nologging enabled. Hence I wondered if there was a way to check if logging was enabled/disabled from within a shell script.
    Could one turn off logging using ING_SET?
    Andre, your point about grounds for dismissal are noted. :D
    Steve
    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From Roy Hann@specially@processed.almost.meat to comp.databases.ingres on Fri Aug 28 11:09:14 2020
    From Newsgroup: comp.databases.ingres

    Steve wrote:

    Sorry, transaction logging.

    I was editing a shell script process where someone had commented out ALL
    the error handling! Some of the commented out error handling code
    indicated the database would be marked inconsistent if the transaction
    failed with nologging enabled.

    That is exactly what would happen and it is unrecoverable. So if you are
    going to turn logging off you may as well comment out the error handling because you are screwed. There is no handling to be done. The only
    option is to roll forward from the last good checkpoint up to the moment logging was turned off.

    Hence I wondered if there was a way to
    check if logging was enabled/disabled from within a shell script.

    Could one turn off logging using ING_SET?

    If one were absolutely insane, yes. Set ING_SET and restart Ingres. I
    can think of no defensible reason ever to do that.

    So to answer your question a little differently, you don't need to check
    if logging is turned off because it is such a grossly abnormal situation
    you just shouldn't be routinely running Ingres that way. I'll repeat my
    earlier comment: if you only suspect logging is turned off (i.e. you
    didn't turn it off yourself having first taken the necessary
    precautions so you know *for sure* it is off) shut Ingres down and
    restart it. You should also do an off-line checkpoint to reinitialize journaling before you start using the database(s) again.

    Roy



    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From Roy Hann@specially@processed.almost.meat to comp.databases.ingres on Fri Aug 28 11:38:11 2020
    From Newsgroup: comp.databases.ingres

    Roy Hann wrote:

    If one were absolutely insane, yes. Set ING_SET and restart Ingres.

    That came out wrong. "...restart your Ingres application/job."

    Roy
    --- Synchronet 3.21d-Linux NewsLink 1.2