Thanks, I think we did have a very large backup (> 30 million files running around the time of the crash). Will check on that. Thanks for the hint.
W -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf Of Billaudeau, Pierre Sent: Wednesday, December 15, 2010 8:17 PM To: [email protected] Subject: Re: [ADSM-L] Anybody seen this? 6.1.3.3 ADM14001C An unexpected and critical error has occurred: ""DBMarkedBad"". Hi Wanda, TSM 6.1.2.0 crashed twice in our environment (AIX 6.1) but each time it was due to a process (expiration once and delete filespace the other time) that was working on a very large node (in term of number of files > 6 millions). TSM DB ran out of space and TSM crashed on a "DB2 space exhausted" error message. Restart went just fine and a lot of space was released. Your message is very different but I thought this could bring somtehing to the discussion. Pierre Billaudeau Analyste en stockage Livraison des Infrastructures Serveurs Société des Alcools du Québec 514-254-6000 x 6559 -----Message d'origine----- De : ADSM: Dist Stor Manager [mailto:[email protected]] De la part de Prather, Wanda Envoyé : 15 décembre 2010 18:56 À : [email protected] Objet : [ADSM-L] Anybody seen this? 6.1.3.3 ADM14001C An unexpected and critical error has occurred: ""DBMarkedBad"". Win2k3 TSM server 6.1.3. Found my TSM server comatose. Had stopped writing to actlog 12 hours ago. Q session showed many sessions just sitting in RUN state, no processes, no tape mounts. DB2 seems to have died out from underneath. Nothing in the activity log, nothing in db2diag.log. But found the messages messages below in the Windows event log. Found one hit on "DBMarkedBad" : http://www-01.ibm.com/support/docview.wss?rs=0&q1=1426627&uid=swg21426627&loc=en_US&cs=utf-8&cc=us&lang=en But that refers to an SQL error initializing the TSM DB after this failure, and my TSM restarted just fine. Also can run a DB backup without errors. So I don't know if anything is actually "bad", or not, or I have corruption in the DB. Event log errors: +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ADM7518C ""TSMDB1 "" marked bad. " 12/14/2010 11:28:15 PM SERVER1 Error None 4 N/A VDCTSM1 " 2010-12-14-23.28.15.921000 Instance:SERVER1 Node:000 PID:2604(db2syscs.exe) TID:6856 Appid:*LOCAL.SERVER1.101215034202 base sys utilities sqeLocalDatabase::MarkDBBad Probe:10 Database:TSMDB1 ADM14001C An unexpected and critical error has occurred: ""DBMarkedBad"". The instance may have been shutdown as a result. ""Automatic"" FODC (First Occurrence Data Capture) has been invoked and diagnostic information has been recorded in directory ""C:\DOCUME~1\ALLUSE~1\APPLIC~1\IBM\DB2\DB2TSM1\SERVER1\FODC_DBMarkedBad_2010-12 -14-23.28.15.890001\"". Please look in this directory for detailed evidence about what happened and contact IBM support if necessary to diagnose the problem. " 12/14/2010 11:28:15 PM SERVER1 Error None 4 N/A VDCTSM1 " 2010-12-14-23.28.15.421000 Instance:SERVER1 Node:000 PID:2604(db2syscs.exe) TID:6856 Appid:*LOCAL.SERVER1.101215034202 relation data serv sqlrr_dump_ffdc Probe:200 Database:TSMDB1 ADM0001C A severe error has occurred. Examine the administration notification log and contact IBM Support if necessary. Wanda Prather | Senior Technical Specialist | [email protected]<mailto:[email protected]> | www.jasi.com<www.jasi.com%20> ICF Jacob & Sundstrom | 401 E. Pratt St, Suite 2214, Baltimore, MD 21202 | 410.539.1135 ___________________________ Information confidentielle: Le présent message, ainsi que tout fichier qui y est joint, est envoyé à l'intention exclusive de son ou de ses destinataires; il est de nature confidentielle et peut constituer une information privilégiée. Nous avertissons toute personne autre que le destinataire prévu que tout examen, réacheminement, impression, copie, distribution ou autre utilisation de ce message et de tout fichier qui y est joint est strictement interdit. Si vous n'êtes pas le destinataire prévu, veuillez en aviser immédiatement l'expéditeur par retour de courriel et supprimer ce message et tout document joint de votre système. Merci.
