hi, my NSP
show error like this Maintenance Unable To Clean Alerts And Packet Logs due to com.intruvert.ext.alert.AlertLogException: java.sql.SQLException: Table '.\lf\iv_packetlog' is marked as crashed and should be repaired
what are the meaning like this.
Knowledgebase article KB66222 covers this issue. For information, I have found a main cause of DB corruption is due to AV. Best practise dictates that the NSM install directory and the MySQL directory are configured as AV exceptions.
Hope this helps, let me know how it goes.
can u guide me. im new on it
With regard to the KB article, simply browse to mysupport.mcafee.com, and search the knowledgebase for KB66222. If you are referring to AV, then exceptions are configured differently depending on the AV product used - if you are using VSE, then changes can be made on the server itself or via ePO (if centrally managed).
If you are new to the product I would suggest browsing to mysupport.mcafee.com and following the product documentation link. Select the product 'Network Security Manager Software' then the version.
Let me know if this helps,
Have you checked out the above KB and tried to follow it through? Could you advise on what you have done so far, and what bit you are stuck on?
You need your Mysql root password (set up at installation) and mysql-gui-tools-noinstall-5.0-r12-win32 software.
Conect to your DB and mark the table iv_packetlog as ok (right click over the table).
can anybody help what step to do
Have you been tried to use mysql-gui-tools-noinstall-5.0-r12-win32 software?
Both myself and Pablo have tried to assist with this matter - you have a knowledgebase article that you can refer to above (if you get stuck on this, please advise what steps you have carried out so far, and exactly what step you are struggling on), and you also have the note on the GUI tool available for MySQL. Please work with either of these and let us know what you have done and what step you need help with.
With regard to your suggestion of marking the table as OK, doesnt this simply mask the problem and run the risk of causing further problems down the line? I ask for my own benefit, as I am not overly familiar with the inner workings of MySQL, and from what I can gather the table should be repaired, not just marked as OK (or does marking it as OK also repair the table?).