[IQUG] IQ table corruption

Amoolya Ajmera Amoolya.Ajmera at rci.rogers.com
Wed Oct 2 19:41:15 MST 2019


@John, can you help us to make it evident from logs about the storage being faulty if IQ msg logs are share.  Can you please share your analysis for the below log line

I. 10/01 12:17:16. 0000169027 {1315} main Bufman: Decompression error during Read; from slib/s_buf.cxx:1820 into buffer 4d718868

@Mark we already have a case opened high priority today afternoon and there is no action on it yet

606489 / 2019 Error while read



From: John Anthony <chirayithaj at gmail.com>
Sent: October 2, 2019 7:10 PM
To: Mark Mumy <markdmumy at gmail.com>
Cc: Amoolya Ajmera <Amoolya.Ajmera at rci.rogers.com>; iqug at iqug.org
Subject: Re: [IQUG] IQ table corruption


CAUTION: This email is from an external sender. Do not click links, open attachments or reply unless you recognize the sender's email address and know the content is safe.
ATTENTION : Ceci vient d’un expéditeur externe. Ne cliquez pas sur les liens, n'ouvrez pas les fichiers et ne répondez pas sauf si vous reconnaissez l'adresse et êtes sûr que le contenu est sécuritaire.


Amoolya - because I know what happened and the process you’ll went through, and having seen this happen at the kind of scale you have , my advise would be to build another IQ instance and copy the data out from the original IQ, while keeping the system running via proxy tables.

It is tough but bad storage , when at scale, messes up IQ!

-JA


On Wed, Oct 2, 2019 at 5:54 PM Mark Mumy <markdmumy at gmail.com<mailto:markdmumy at gmail.com>> wrote:
Open a case so support can get you the right tools.  And most importantly let you know if the issues are already fixed in a newer version.
Mark

========================

Sent from my mobile device


On Oct 2, 2019, at 15:27, Amoolya Ajmera <Amoolya.Ajmera at rci.rogers.com<mailto:Amoolya.Ajmera at rci.rogers.com>> wrote:

We are facing table corruption every now and than on IQ, we are on latest 16.0 Pl23

Anything that can help to track how corruption is going on and what is the possible reason behind it that we can track in details from logs in details





________________________________
This communication is confidential. We only send and receive email on the basis of the terms set out at www.rogers.com/web/content/emailnotice<http://www.rogers.com/web/content/emailnotice>



Ce message est confidentiel. Notre transmission et réception de courriels se fait strictement suivant les modalités énoncées dans l’avis publié à www.rogers.com/aviscourriel <http://www.rogers.com/aviscourriel>
________________________________
_______________________________________________
IQUG mailing list
IQUG at iqug.org<mailto:IQUG at iqug.org>
http://iqug.org/mailman/listinfo/iqug
_______________________________________________
IQUG mailing list
IQUG at iqug.org<mailto:IQUG at iqug.org>
http://iqug.org/mailman/listinfo/iqug
--
Sent from mobile device




________________________________
This communication is confidential. We only send and receive email on the basis of the terms set out at www.rogers.com/web/content/emailnotice<http://www.rogers.com/web/content/emailnotice>



Ce message est confidentiel. Notre transmission et réception de courriels se fait strictement suivant les modalités énoncées dans l’avis publié à www.rogers.com/aviscourriel <http://www.rogers.com/aviscourriel>
________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://iqug.org/pipermail/iqug/attachments/20191003/305faf81/attachment-0001.html>


More information about the IQUG mailing list