Informix

Informix

Connect with Db2, Informix, Netezza, open source, and other data experts to gain value from your data, share insights, and solve problems.

 View Only

  • 1.  Conversion halted because logs are not backed up

    Posted 6 days ago

    Hi again.

    My heels have not cooled since my last problem and I go another one.  This keeps happening!

    Before trying the upgrade we meticulously run onmode -c and onmode -l and, as I watch the online log, I see a log backup start and finish.  The we shut down the server and try the upgrade (12.10 => 14.10).  In testing we often (it's inconsistent) get the message:

    Conversion halted because logs are not backed up

    ....  As I compose my thoughts to write this, it occurs to me that even after a log switch and backup of the log file whence we just switched away, the new log is not backed up, although there is no activity to log at the time. I am adding to the upgrade document that the BA shall run onbar -c to back up the new (nearly empty) log.

    Does this make sense to y'all who have gone through the pain of a release upgrade?  Perhaps I just needed another set of eyes on our procedures.

    Thanks for reading and commenting.

    -- JS



    ------------------------------
    +-----------------------------------------------------------+
    | I am pleased to report that I had no problems today. |
    | I had only issues, opportunities, challenges and valuable |
    | learning experiences. |
    +------------------------------------------ Jacob S --------+
    ------------------------------


  • 2.  RE: Conversion halted because logs are not backed up

    Posted 6 days ago

    Any open trans ? Expliciity run ontape -a?



    ------------------------------
    Paul Watson
    Oninit LLC
    Cell +1 9133877529
    ------------------------------

    Original Message


  • 3.  RE: Conversion halted because logs are not backed up

    Posted 6 days ago

    The current log (C flag) not being backed up should NOT cause such message and failure, so there must be other used (U) logs missing the backup flag.

    -> check onstat -l in such case (collect it before final shutdown preceding the upgrade attempt).



    ------------------------------
    Andreas Legner
    Informix Dev
    HCL Software
    ------------------------------

    Original Message


  • 4.  RE: Conversion halted because logs are not backed up

    Posted an hour ago

    Hi Jacob,

    Convert the HDR to an RSS then it is not a fatal error!

    Also stop the dbscheduler which can write to the log

    • https://www.ibm.com/docs/en/informix-servers/12.10.0?topic=saaf-scheduler-argument-stop-start-scheduler-sql-administration-api OR
    • touch $INFORMIXDIR/etc/sysadmin/stop  before starting the instance

    Shutdown sequence should be

    Primary   onmode -l && onmode -c && ontape -a && onmode -c

    Answer "y"  to backup the current log.

    The last checkpoint flushes the backed up log status to the seondaries - IMPORTANT AND NOT IN THE MANUAL last time I looked!!!

    onstat -g cluster to ensure all nodfes in sync

    onstat -l  on Primary AND Secondaries to ensure all logs markerd as backed up everywhere

    onmode -ky Secondaries

    onmode -ky Primary

    Regards,
    David.



    ------------------------------
    David Williams
    Senior Database Platform Engineer
    Flutter
    London
    ------------------------------

    Original Message


Related Content