| Author |
Message |
 Topic: mqsiimpexpmsgset error 8165W |
joebrew
Replies: 2
Views: 1958
|
 Forum: WebSphere Message Broker (ACE) Support Posted: Mon Dec 16, 2002 5:44 am Subject: mqsiimpexpmsgset error 8165W |
The Message Set was 888kb. My System Administrator made a change that fixed the problem. He changed the appl_ctl_heap_sz from 128 mb to 512 mb.
Thanks for your help! |
| Topic: mqsiimpexpmsgset error 8165W |
joebrew
Replies: 2
Views: 1958
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Dec 09, 2002 8:09 am Subject: mqsiimpexpmsgset error 8165W |
I'm getting the following error when attempting to import a large Message set:
There may insufficient memory to complete the operation.
Increase the amount of virtual memory available on your syst ... |
| Topic: Inconsistent TimeStamp using Trace Node |
joebrew
Replies: 7
Views: 8232
|
Forum: General IBM MQ Support Posted: Thu May 23, 2002 10:59 am Subject: IT WORKED! |
| After applying CSD02, we are no longer experiencing the problem. |
| Topic: Inconsistent TimeStamp using Trace Node |
joebrew
Replies: 7
Views: 8232
|
Forum: General IBM MQ Support Posted: Mon May 20, 2002 11:18 am Subject: IBM Response |
Here is the response from IBM:
After detail search we found a similar problem with one of our other
Customer.
This problem is fixed in csd02 (problem IY19242 ).
So we recommend you to apply cs ... |
| Topic: Inconsistent TimeStamp using Trace Node |
joebrew
Replies: 7
Views: 8232
|
Forum: General IBM MQ Support Posted: Thu May 16, 2002 6:34 am Subject: I'm having a similar problem |
I'm experiencing similar problems with the CURRENT_TIMESTAMP on AIX.
In my first message flow, I insert a record into an Oracle database and set a create_timestamp field = CURRENT_TIMESTAMP.
My ... |
