| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Urgent: NNSY Issue on MQSI 2.1 after Upgradation of Database |
« View previous topic :: View next topic » |
| Author |
Message
|
| Manu30 |
 Posted: Tue Jun 26, 2007 8:25 am Post subject: Urgent: NNSY Issue on MQSI 2.1 after Upgradation of Database |
 |
|
Newbie
Joined: 26 Jun 2007
Posts: 7
|
Hi,
We just did the upgradation of our database from 8i to 9i. We are using MQ 5.3 and MQSI 2.1. Before upgradation it was working fine, but after upgradation all NNSY formats are not working. Whenever we pass any message through the message flow in which NNSY is involved it throws following error:
[color=red]20070620141719590Z|NeonConnectionManager|55,986|2,057|Database Session|NNOT_EC_NATIVE_API_ERROR|Unknown||A database API call failed.
File: NNSqlOra8Obj.cpp
Line: 244
Call: OCIStmtExecute
Code: 933
Text: ORA-00933: SQL command not properly ended
20070620141719652Z|NeonConnectionManager|55,986|2,057|MessageProcessor|1080|Error||Database internal error. Unable to retrieve format SAP.IC.ORDERS05^1
20070620141719943Z|NeonConnectionManager|55,986|2,057|INFR|INFR|Info||Ending process.
20070620141839928Z|NeonConnectionManager|55,986|2,057|INFR|INFR|Info||Library info:.[/color]
ParserException "NN111E: NEONMSG parser failed to process message. Message type : SAP.IC.ORDERS05^1 Error # : 1080 Error message : Database internal error. Unable to retrieve format SAP.IC.ORDERS05^1 When processing the message using format SAP.IC.ORDERS05^1, NNSY reported an error.The NNSY error code was 1080. The NNSY error text was Database internal error. Unable to retrieve format SAP.IC.ORDERS05^1.
I tried following approaches to troubleshoot the same but no success:
1. The same flow was working fine in QA before Upgrade and the same flow is working fine in Dev environment, so i tried pulling the latest NNFie structures from Dev Config box and importing the same in QA Broker. Still am getting the same error.
2. I tried manual parsing in QA box using NNSY VisualTester, it parses the file correctly.
3. I checked the NNSY User Manual for the above error code, it ask to run Consistency Check. We have run the consistency check and it gives no issue.
Please help.
Thanks and regards,
-Manu |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue Jun 26, 2007 8:35 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
It seems a little unreasonable to expect that you can run a database application (NNSY) that is six or seven years old, and completely unsupported, and have it work without any flaws against a version of the database that it was never tested against, and is probably two versions of the database newer than any version that NNSY was tested against.
I.E. It was very optomistic to think you could run NNSY against Oracle 9i, when it was probably only ever tested against Oracle 6 or 7.
You're also out of support with both IBM and NNSY, unless you've been paying a lot of extra money to maintain support.
Give up on NNSY.
Give up on Broker 2.1.
Embrace the new century, and migrate to MRM and Broker v6.
Please.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Manu30 |
| Posted: Tue Jun 26, 2007 8:51 am Post subject: |
|
|
Newbie
Joined: 26 Jun 2007
Posts: 7
|
Thanks Jeff. But currently we cant move to Broker v6.
And we have done the same exercise on 1 more environment and it has worked fine. But only on 2nd environment we facing this issue. Any pointers.
Regards,
-maneesh |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Jun 26, 2007 9:02 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
No, I don't have any pointers.
I've never worked with NNSY, and I haven't worked with 2.1 in at least three years.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Jun 26, 2007 11:57 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Manu30 wrote: |
And we have done the same exercise on 1 more environment and it has worked fine. But only on 2nd environment we facing this issue. Any pointers.
|
You could try duplicating exactly what you did on the working environment. Including the use of any lucky charms used... 
Seriously, you've got so many mismatched and out of date technologies you're going to need a bit of luck to get it going.
I wish you luck. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Tue Jun 26, 2007 10:14 pm Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
I agree with others, you need to upgrade... and
if you have a working DEV environment with Oracle 9i, try and find differences in the environments like paths, evironment settings, config files etc... it may be your only chance to get this working...
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
