Hi Experts,

Our informix log file (which outputs from onstat -m or  MSGPATH parameter in onconfig) isn't purged since years &7 has grown in size. Please help how to purge this file & does this requires shutdown. Any risk to DB if done in improper way?

Thanks in advance

Syed H

Hi Experts,

Our informix log file (which outputs from onstat -m or  MSGPATH parameter in onconfig) isn't purged since years &7 has grown in size. Please help how to purge this file & does this requires shutdown. Any risk to DB if done in improper way?

Thanks in advance

Syed H

Hi Experts,

Our informix log file (which outputs from onstat -m or  MSGPATH parameter in onconfig) isn't purged since years &7 has grown in size. Please help how to purge this file & does this requires shutdown. Any risk to DB if done in improper way?

Thanks in advance

Syed H

Hi Experts,

Our informix log file (which outputs from onstat -m or  MSGPATH parameter in onconfig) isn't purged since years &7 has grown in size. Please help how to purge this file & does this requires shutdown. Any risk to DB if done in improper way?

Thanks in advance

Syed H

Syed:

You can set up message log rotation, specifying the number of older copies to keep and how frequently to create a new log file in the engine. You can also set up a cron job to do that using OS features. Finally you can just rename the file or delete it and Informix will just create a new one the next time it has to wrote to the message log. 

Art

Hi Experts,

Our informix log file (which outputs from onstat -m or  MSGPATH parameter in onconfig) isn't purged since years &7 has grown in size. Please help how to purge this file & does this requires shutdown. Any risk to DB if done in improper way?

Thanks in advance

Syed H

Thank you all for the wonderful suggestions & will definitely try out those in non-prod environment. Meanwhile, I find the below suggestion from chatgpt on this topic. Please let me know if this also works.

mv $INFORMIXDIR/tmp/online.log $INFORMIXDIR/tmp/online.log.old
touch $INFORMIXDIR/tmp/online.log
chmod 660 $INFORMIXDIR/tmp/online.log

Thanks again.

Syed:

You can set up message log rotation, specifying the number of older copies to keep and how frequently to create a new log file in the engine. You can also set up a cron job to do that using OS features. Finally you can just rename the file or delete it and Informix will just create a new one the next time it has to wrote to the message log. 

Art

Hi Experts,

Our informix log file (which outputs from onstat -m or  MSGPATH parameter in onconfig) isn't purged since years &7 has grown in size. Please help how to purge this file & does this requires shutdown. Any risk to DB if done in improper way?

Thanks in advance

Syed H

Cordialement, Regards,    Khaled Bentebal Directeur Général - ConsultiX Tél: 33 (0) 1 39 12 18 00 Mobile: 33 (0) 6 07 78 41 97 Email: khaled.bentebal@consult-ix.fr Site Web:  www.consult-ix.fr

Thank you all for the wonderful suggestions & will definitely try out those in non-prod environment. Meanwhile, I find the below suggestion from chatgpt on this topic. Please let me know if this also works.

mv $INFORMIXDIR/tmp/online.log $INFORMIXDIR/tmp/online.log.old
touch $INFORMIXDIR/tmp/online.log
chmod 660 $INFORMIXDIR/tmp/online.log

Thanks again.

Syed:

You can set up message log rotation, specifying the number of older copies to keep and how frequently to create a new log file in the engine. You can also set up a cron job to do that using OS features. Finally you can just rename the file or delete it and Informix will just create a new one the next time it has to wrote to the message log. 

Art

Hi Experts,

Our informix log file (which outputs from onstat -m or  MSGPATH parameter in onconfig) isn't purged since years &7 has grown in size. Please help how to purge this file & does this requires shutdown. Any risk to DB if done in improper way?

Thanks in advance

Syed H

Thank you all for the wonderful suggestions & will definitely try out those in non-prod environment. Meanwhile, I find the below suggestion from chatgpt on this topic. Please let me know if this also works.

mv $INFORMIXDIR/tmp/online.log $INFORMIXDIR/tmp/online.log.old
touch $INFORMIXDIR/tmp/online.log
chmod 660 $INFORMIXDIR/tmp/online.log

Thanks again.

Syed:

You can set up message log rotation, specifying the number of older copies to keep and how frequently to create a new log file in the engine. You can also set up a cron job to do that using OS features. Finally you can just rename the file or delete it and Informix will just create a new one the next time it has to wrote to the message log. 

Art

Hi Experts,

Our informix log file (which outputs from onstat -m or  MSGPATH parameter in onconfig) isn't purged since years &7 has grown in size. Please help how to purge this file & does this requires shutdown. Any risk to DB if done in improper way?

Thanks in advance

Syed H

Thank you all for the wonderful suggestions & will definitely try out those in non-prod environment. Meanwhile, I find the below suggestion from chatgpt on this topic. Please let me know if this also works.

mv $INFORMIXDIR/tmp/online.log $INFORMIXDIR/tmp/online.log.old
touch $INFORMIXDIR/tmp/online.log
chmod 660 $INFORMIXDIR/tmp/online.log

Thanks again.

Syed:

You can set up message log rotation, specifying the number of older copies to keep and how frequently to create a new log file in the engine. You can also set up a cron job to do that using OS features. Finally you can just rename the file or delete it and Informix will just create a new one the next time it has to wrote to the message log. 

Art

Hi Experts,

Our informix log file (which outputs from onstat -m or  MSGPATH parameter in onconfig) isn't purged since years &7 has grown in size. Please help how to purge this file & does this requires shutdown. Any risk to DB if done in improper way?

Thanks in advance

Syed H

Thank you all for the wonderful suggestions & will definitely try out those in non-prod environment. Meanwhile, I find the below suggestion from chatgpt on this topic. Please let me know if this also works.

mv $INFORMIXDIR/tmp/online.log $INFORMIXDIR/tmp/online.log.old
touch $INFORMIXDIR/tmp/online.log
chmod 660 $INFORMIXDIR/tmp/online.log

Thanks again.

Syed:

You can set up message log rotation, specifying the number of older copies to keep and how frequently to create a new log file in the engine. You can also set up a cron job to do that using OS features. Finally you can just rename the file or delete it and Informix will just create a new one the next time it has to wrote to the message log. 

Art

Hi Experts,

Our informix log file (which outputs from onstat -m or  MSGPATH parameter in onconfig) isn't purged since years &7 has grown in size. Please help how to purge this file & does this requires shutdown. Any risk to DB if done in improper way?

Thanks in advance

Syed H

The rename (mv) alone should do.  The next message created by the server will automatically re-create the file.

Thank you all for the wonderful suggestions & will definitely try out those in non-prod environment. Meanwhile, I find the below suggestion from chatgpt on this topic. Please let me know if this also works.

mv $INFORMIXDIR/tmp/online.log $INFORMIXDIR/tmp/online.log.old
touch $INFORMIXDIR/tmp/online.log
chmod 660 $INFORMIXDIR/tmp/online.log

Thanks again.

Syed:

You can set up message log rotation, specifying the number of older copies to keep and how frequently to create a new log file in the engine. You can also set up a cron job to do that using OS features. Finally you can just rename the file or delete it and Informix will just create a new one the next time it has to wrote to the message log. 

Art

Hi Experts,

Our informix log file (which outputs from onstat -m or  MSGPATH parameter in onconfig) isn't purged since years &7 has grown in size. Please help how to purge this file & does this requires shutdown. Any risk to DB if done in improper way?

Thanks in advance

Syed H

The rename (mv) alone should do.  The next message created by the server will automatically re-create the file.

Thank you all for the wonderful suggestions & will definitely try out those in non-prod environment. Meanwhile, I find the below suggestion from chatgpt on this topic. Please let me know if this also works.

mv $INFORMIXDIR/tmp/online.log $INFORMIXDIR/tmp/online.log.old
touch $INFORMIXDIR/tmp/online.log
chmod 660 $INFORMIXDIR/tmp/online.log

Thanks again.

Syed:

You can set up message log rotation, specifying the number of older copies to keep and how frequently to create a new log file in the engine. You can also set up a cron job to do that using OS features. Finally you can just rename the file or delete it and Informix will just create a new one the next time it has to wrote to the message log. 

Art

Hi Experts,

Our informix log file (which outputs from onstat -m or  MSGPATH parameter in onconfig) isn't purged since years &7 has grown in size. Please help how to purge this file & does this requires shutdown. Any risk to DB if done in improper way?

Thanks in advance

Syed H

Milan:

No, the engine does not keep the message log open, it opens the log, writes a message, then closes the log file.

It is, as Andreas stated, and I had implied in an earlier post, only necessary to rename or delete the current message log file and the engine will just create a new one. Witness:

Art

The rename (mv) alone should do.  The next message created by the server will automatically re-create the file.

Thank you all for the wonderful suggestions & will definitely try out those in non-prod environment. Meanwhile, I find the below suggestion from chatgpt on this topic. Please let me know if this also works.

mv $INFORMIXDIR/tmp/online.log $INFORMIXDIR/tmp/online.log.old
touch $INFORMIXDIR/tmp/online.log
chmod 660 $INFORMIXDIR/tmp/online.log

Thanks again.

Syed:

You can set up message log rotation, specifying the number of older copies to keep and how frequently to create a new log file in the engine. You can also set up a cron job to do that using OS features. Finally you can just rename the file or delete it and Informix will just create a new one the next time it has to wrote to the message log. 

Art

Hi Experts,

Our informix log file (which outputs from onstat -m or  MSGPATH parameter in onconfig) isn't purged since years &7 has grown in size. Please help how to purge this file & does this requires shutdown. Any risk to DB if done in improper way?

Thanks in advance

Syed H

Milan:

No, the engine does not keep the message log open, it opens the log, writes a message, then closes the log file.

It is, as Andreas stated, and I had implied in an earlier post, only necessary to rename or delete the current message log file and the engine will just create a new one. Witness:

Art

The rename (mv) alone should do.  The next message created by the server will automatically re-create the file.

Thank you all for the wonderful suggestions & will definitely try out those in non-prod environment. Meanwhile, I find the below suggestion from chatgpt on this topic. Please let me know if this also works.

mv $INFORMIXDIR/tmp/online.log $INFORMIXDIR/tmp/online.log.old
touch $INFORMIXDIR/tmp/online.log
chmod 660 $INFORMIXDIR/tmp/online.log

Thanks again.

Syed:

You can set up message log rotation, specifying the number of older copies to keep and how frequently to create a new log file in the engine. You can also set up a cron job to do that using OS features. Finally you can just rename the file or delete it and Informix will just create a new one the next time it has to wrote to the message log. 

Art

Hi Experts,

Our informix log file (which outputs from onstat -m or  MSGPATH parameter in onconfig) isn't purged since years &7 has grown in size. Please help how to purge this file & does this requires shutdown. Any risk to DB if done in improper way?

Thanks in advance

Syed H