We have an entry in QEZJOBLOG that displays this message
Opt File File Nbr Job User Number Date Time
QPJOBLOG 1 PROFOUNDUI QTMHHTTP 142647 08/22/18 20:22:34
RNX0105 Escape 99 08/22/18 13:32:04.067121 QRNXIE ….
From user . . . . . . . . . : DAV_PHEL
From module . . . . . . . . : QRNXMSG
From procedure . . . . . . : SignalException
Statement . . . . . . . . . : 20
To module . . . . . . . . . : PUISQLPRC
To procedure . . . . . . . : SQLP_PROCESS
Statement . . . . . . . . . : 1102
Message . . . . : A character representation of a numeric value is in error.
Cause . . . . . : A conversion from character to numeric found data that was
not valid. Recovery . . . : Correct the numeric data.
Is this anything to be concerned with?
msg RNX0105
-
- Experienced User
- Posts: 139
- Joined: Mon Aug 16, 2010 12:04 pm
- First Name: Wayne
- Last Name: Colasinski
- Company Name: Sofworx / Tantara Transport
- Contact:
-
- Experienced User
- Posts: 2711
- Joined: Wed Aug 01, 2012 8:58 am
- First Name: Scott
- Last Name: Klement
- Company Name: Profound Logic
- City: Milwaukee
- State / Province: Wisconsin
Re: msg RNX0105
No, I wouldn't be concerned unless your database-driven widget is malfunctioning because of it.
We do have a place in the code where we're expecting this error and monitoring/catching it and handling it, but leaving it in the job log... so if this is what you're seeing, it's a non-issue. (But, we should really remove the message so people aren't concerned.)
We do have a place in the code where we're expecting this error and monitoring/catching it and handling it, but leaving it in the job log... so if this is what you're seeing, it's a non-issue. (But, we should really remove the message so people aren't concerned.)
-
- Experienced User
- Posts: 139
- Joined: Mon Aug 16, 2010 12:04 pm
- First Name: Wayne
- Last Name: Colasinski
- Company Name: Sofworx / Tantara Transport
- Contact:
Re: msg RNX0105
Thanx Scott. I think this incident was the perfect storm. Our power went off and came back on pretty quickly. I think the outage might've knocked something for a loop. Neither my boss nor I were there when this happened but a few users were logged on. My boss came in and checked the system and noticed the system was really dragging and the above job was running at 63 (CPU%). He immediately killed (or tried to kill) the job. It took about an hour to end and everything was fine. He discovered the error message scanning thru the job log.
Anyways, everything seems to be fine and this was just a flukey thing. Thanks for your response.
Anyways, everything seems to be fine and this was just a flukey thing. Thanks for your response.
Who is online
Users browsing this forum: No registered users and 1 guest