Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Sean Birkhead — — source: Informix-list mailing list archive (1991-1998)
In <5kul2f$92t@news.cis.nctu.edu.tw>, Xiong wrote:
}
} In informix message.log file, I found the following messages :
}
} 20:21:42 lock table overflow - userid ..., sessionid ...
} ... ( Similar lock table overflow messages omitted )
} 20:28:40 lock table overflow - userid ..., sessionid ...
}
} By running 'onstat -g sql', I found 4 sessions with SQL ERR and
} ISAM ERR as follows
}
} SQL ISAM SQL
} ERR ERR stmt
} -240-134 DELETE
} -211-134 ...
} -211-134 CREATE INDEX
} -243-134 UPDATE
}
} -134 ISAM error: no more locks.
} -211 Cannot read system catalog catalog-table.
} -240 Could not delete a row.
} -243 Could not position within a table table-name.
}
}
}
} LOCKS of $INFORMIXDIR/etc/$ONCONFIG is set to 350000
}
} Does the 'lock table overflow' message mean the server need more
}LOCKS?
} Can I solve the problem by increasing LOCKS value ?
} Any response to solve the problem is appreciated !
}
}
}
}--
}Fu-Xiong Lin
This is probably a Unix kernel parameter being exceeded.
Check all parameters in your Unix kernel to do with
files, processes and inodes.
You haven't stated your O/S but for example the parameter to be checked
under SCO Unix would be :
FLCKREC: number of records that can be locked by the system.
other related parameters worth checking are :
NINODE: maximum number of open inodes (systemwide).
NFILE: maximum number of open files (systemwide).
NOFILES: maximum number of open files per process.
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.