Dia8402c A Disk Error Has Occurred
IN DB2DIAG.LOG AFTER TRYING TO ATTACH TO DB2 INSTANCE. AIX Fixes are available DB2 Version 9.5 Fix Pack 5for Linux, UNIX, and Windows DB2 Version 9.5 Fix Pack 6afor Linux, UNIX, and disk error occurred dos Windows DB2 Version 9.5 Fix Pack 7for Linux, UNIX, and Windows DB2 Version 9.5 oserr eio 5 i o error Fix Pack 8for Linux, UNIX, and Windows DB2 Version 9.5 Fix Pack 9for Linux, UNIX, and Windows DB2 Version 9.5 Fix a disk error has occurred secure download manager Pack 10for Linux, UNIX, and Windows Subscribe You can track all active APARs for this component. APAR status Closed as program error. Error description OS returns EIO error when DB2 tries to attach to the instance, which requires locking of the instance seed file. If the seed file is somehow unavailable, the following db2diag.log message may appear. An example of instance attachment would be ATTACH TO command as well as GET DBM CFG SHOW DETAIL. 2009-02-05-09.06.26.597549-300 E802279E500 LEVEL: Warning (OS) PID : 31700 TID : 183046802080PROC : db2agent (idle) 1 INSTANCE: db2inst1 NODE : 001 APPHDL : 1-1068 APPID: AA123456.1234.0123456789 FUNCTION: DB2 UDB, oper system services, sqloflock, probe:100 MESSAGE : ZRC=0x860F0003=-2045837309=SQLO_DERR "disk error occurred (DOS)" DIA8402C A disk error has occurred. CALLED : OS, -, fcntl OSERR: EIO (5) Please note that this is not a severe error. Databases will function normally, and only the instance attachment may fail. Also, this error message may happen in other normal situations where DB2 was unable to lock a file. The APAR fix will remove the need of seed file locking. Local fix Try to attach to the instance later. Problem summary QLO_DERR "DISK ERROR OCCURRED (DOS)" WARNING MESSAGES IN B2DIAG.LOG AFTER TRYING TO ATTACH TO DB2 INSTANCE. Problem conclusion FIXED IN DB2 V9.5 FP5 Temporary fix Comments APAR Information APAR numberIZ48399 Reported component nameDB2 UDB ESE AIX Reported component ID5765F4100 Reported release950 StatusCLOSED PER PENoPE HIPERNoHIPER Special AttentionNoSpecatt Submitted date2009-04-07 Closed date2009-12-16 Last modified date2009-12-16 APAR is sysrouted FROM one or more of the following: IZ46871 APAR is sysrouted TO one or more of the following: Fix information Fixed component nameDB2 UDB ESE AIX Fixed component ID5765F4100 Applicable component levels R910 PSYUP R950 PSYUP Document information More support for: DB2 for Linux, UNIX and Windows Software version: 950 Reference #: IZ48399 Modified date: 2009-12-16 Site availability Site assistance Contact and feedback Need support? S
be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. Results 1 to 2 of 2 Thread: HELP!!! DIA8402C A disk error has occurred Tweet Thread Tools http://www.ibm.com/support/docview.wss?uid=swg1IZ48399 Show Printable Version Subscribe to this Thread… Search Thread Advanced Search Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode 07-05-04,22:38 #1 huyuhui View Profile View Forum Posts Registered User Join Date Apr 2004 Posts 22 Unanswered: HELP!!! DIA8402C A disk error has occurred What does DIA8402C http://www.dbforums.com/showthread.php?1003559-HELP!!!-DIA8402C-A-disk-error-has-occurred mean? Is it dangerous????? Sometims when i did reorg tables , i found that the tablespace which the reorged table in would become full, when the tablespace was full ,i got the 'DIA8402C A disk error has occurred' . Sometimes I executed a procedure, I could got same error message. Sometimes I do LOAD,I could got same error message. OS: linux as 3 core 2.6 HOSTELL 6650 +SAN CX200 DB: DB2 V8 ,FP6, the tablespace containers is raw device. ************************ "db2diag.log" 2004-06-30-15.18.28.296202 Instance:biw Node:000 PID:19892(db2pfchr) TID:1130027744 Appid:none oper system services sqlobufreset Probe:100 errno: 0xBFFFCC50 : 0x00000005 .... 2004-06-30-15.18.28.332719 Instance:biw Node:000 PID:19892(db2pfchr) TID:1130027744 Appid:none buffer pool services sqlbSMSTruncateObject Probe:820 DIA8402C A disk error has occurred. ZRC=0x860F0003 2004-06-30-15.18.28.344631 Instance:biw Node:000 PID:19892(db2pfchr) TID:1130027744 Appid:none buffer pool services sqlbSMSTruncateObject Probe:820 Obj={pool:1;obj:2;type:128} State=x37 Page=32 Cont=0 PID:19892 TID:1130027744 Node:000 Title: SQLB_OBJECT_DESC 0x7F147FB0 : 0100 0200 0100 0200 8000 0000 1508 2985 ..............). 0x7F147
on DB2 for Linux, UNIX, and WindowsWhere is this place located?All Places SAP on DB2 for Linux, UNIX, and Windows 6 Replies Latest reply: Jan 16, 2013 11:13 AM by Deepak https://scn.sap.com/thread/3293272 Kori Tweet DB2 Offline backup error Sandeep S Jan 16, 2013 8:16 AM Currently Being Moderated Hi,While trying to take offline backup to disk storage in our SAP ERP http://www.cursor-distribution.de/en/ibm-software/db2-software/support-db2/index.php?option=com_ibmbuglist&view=bugdetail&type=DB2&get_bug=IT03990&Itemid=1176 system with SLES and IBM DB2 9.7 database getting the error and backup is terminating. SQL0980C A disk error occurred. Subsequent SQL statements cannot beprocessed. SQLSTATE=58005Command used -> db2 disk error backup db SID to "
news archiveInformixInformix newsInformix appointmentsInformix newsletter (IBM)Informix news searchInformix useful linksInformix news archiveForumDistribution & SalesYour way to IBM with CURSORWe are your partnerASL/OEM Licensing1. ASL for your product2. A profit for everyone3. Cooperation4. Become a partnerServices on our websiteCURSOR Software AGDB2DB2 newsDB2 product editionsDB2 information materialDB2 announcementsDB2 price listsDB2 license calculatorDB2 license textsDB2 inquiries & ordersInformixInformix newsInformix product editionsInformix comparison tableInformix information materialInformix customer referencesInformix announcementsInformix price listsInformix license calculatorInformix license textsInformix inquiries & ordersCognosCognos InsightCognos information materialCognos announcementsCognos price listsCognos license textsGuardiumGuardium product familyPrivacy as a processGuardium information materialGuardium lifecycleService & TechnologyService and support - You can count on us:Service packagesInstallationBackup & recoveryHigh availabilityPerformance tuningMigration & trade-up7x24 preventiveSupport - standardSupport - basicsSupport - requestsDB2Tools for administratorsTechnical informationDB2 documentationDB2 productlinesDB2 newsletterDB2 downloadInformixTools for administratorsTechnical informationInformix documentationInformix productlinesInformix NewsletterInformix downloadCognosCognos useful linksCognos lifecycleCognos release newsletterCognos release archiveCognos fixlistsCognos product downloadSPSS LifecycleSPSS product downloadAdmin-ScoutAdmin-Scout for Informix - special services and support for Informix administrators Home Latest versionsfixlist 10.5.0.7 10.1.0.5 9.8.0.5 9.7.0.11 9.5.0.10 9.1.0.12 Have problems? - contact us. Register for free Contact form Question in the forum Question in the chat DB2 - Problem description Problem IT03990 Status: Closed DB2INSPECT FAILS WITH SQL1143N ERROR BECAUSE A FILE ERROR OCCURED, MISSING FODC DIRECTORY.product: DB2 FOR LUW / DB2FORLUW / 970 - DB2 Problem description: Example: db2 "inspect check database indexdata results keep node44.inspectdb.out ON DBPARTITIONNUM (44)" SQL1143N The operation cannot complete because a file error occurred for the file "node44.inspectdb.out". "FODC is in progress state" is not reset after data collection. Therefore utilities like INSPECT will not write to db2dump directory, but to an old FODC directory. If this FODC directory was previously deleted errors like SQL1143N can occur. This is the same scenario as descri