Re: [U2] UV Memory issues

I too would suspect disk issues. We had exactly the same symptoms on our HP UX Universe installation, and tracked it down (eventually) to disk issues caused by problems with a Veritas replication link which copied data from the live server to an offsite DR server... Symeon Breen

Re: [U2] UV Memory issues

Hi. We had the opposite problem with the same sympthons: the same bad performance but free memory. Same as you, I would like to know how to rule the amount of memory each uv-process takes. We did ps -el | grep uv in order to see the memory usage. (The SZ column gives you the number of 4 kb

[U2] problem - Attempted WRITE with record ID larger than file/table maximum

We encountered a problem during our nightly batch processing last night and it pertains to a specific record/key. The error that we received in our log is as follows: -- Program LFBDOPOS: Line 337, Attempted WRITE with record ID larger than file/table maximum record ID size of 255 characters.

Re: [U2] problem - Attempted WRITE with record ID larger than file/table maximum

Make sure there is not an index on that file being updated with a key 255 characters. Perry -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Chris Austin Sent: Wednesday, June 09, 2010 8:19 AM To:

Re: [U2] problem - Attempted WRITE with record ID larger than file/table maximum

I believe that is the problem, the key for record '15500*60431*EJK' must have more than 255 characters. Is there a way to check the # of characters on a key from a telnet prompt? I'm confused why the key would be so big? There must be 'historical encoding of record locks' or something behind

Re: [U2] problem - Attempted WRITE with record ID larger than file/table maximum

On 6/9/2010 10:46 AM, Chris Austin wrote: I believe that is the problem, the key for record '15500*60431*EJK' must have more than 255 characters. Is there a way to check the # of characters on a key from a telnet prompt? I'm confused why the key would be so big? There must be 'historical

Re: [U2] problem - Attempted WRITE with record ID larger than file/table maximum

Yeah that could be it but I just did a restore of last nights pre-cycle data. An interesting thing I noticed in regards to the table GENACCTRN (the one we're having issues with) and noticed the following errors with the index: Restoring c:\LIVE/I_GENACCTRN/INDEX.005 (19:34:23) Restoring

Re: [U2] problem - Attempted WRITE with record ID larger than file/table maximum

Perhaps the index is defined as single-valued when it should be defined as multi-valued. Best regards, Henry Unger Hitech Systems, Inc. http://www.hitech.com -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Chris