RE: DB/cockpit error

Posted in 1997

Sujit Pal — 26 Aug 1997 19:48:20 -0400 — source: Informix-list mailing list archive (1991-1998)

Rich Sorry for posting this reply again, but I was not sure the first one = made it through. Are not "Almost empty big tables" an alarm rather than error in = DB/Cockpit? IMO they indicate highly fragmented tables that could use a = reorg. If you edit the alarm you will notice that the SQL against the = sysmaster database looks for tables which have npused > 0 (non-empty), = np_total > 8 (more than 8 extents, ie big table) and where = npused*100/np_total < 0.1 (less that 0.1% full ie almost empty). HTH Sujit Pal ---------- From: rich[SMTP:richn@northv.com] Sent: Tuesday, August 26, 1997 11:56 AM To: informix-list@rmy.emory.edu Subject: DB/cockpit error Does anyone know what the following error from DB/cockpi means?? "Almost empty big tables" then it lists three tables from one of my = databases. Support never heard of this error!!! Help richn@northv.com PS Im just upgraded from 7.10uc1 to 7.14uc1 on a sun sparc20 Thanks