on 11-17-2008 2:53 PM
Hi all,
I performed a kernel upgrade on all systems in my landscape successfully to ver 700.175 Unicode for WIN2k3 & ORC DB 64bit.
I have observed the logs in work directory after upgrade
dev_w0.old was only 19kb.
but with in a day after kernel upgrade dev_w0 log increased to more than 2 MB in day & the following lines getting repeatedly in the log
X Mon Nov 17 20:10:53 2008
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2214]
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2214]
X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2214]
try to analyze what could be the reason.Pls provide me possible clues.
Yes markus u are right thank you & I have updated to 179
Edited by: Rahul on Nov 17, 2008 8:59 PM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Rahul
I am getting the same error. We have windows 64-bit non-unicode system on ORACLE which was recently upgraded to NW 7.00. I have applied kernel patch 175.
I see there is only kernel part II available for patch 179. Kernel Part I is there till patch 175 only.
Is it okay if I apply only part II to avoid that error?
Thanks,
Ravali
Edited by: Ravali Bandi on Dec 30, 2008 11:28 PM
Hi,
Strange I can't manage to find PART1 for Non Unicode Orc, Win 64 as posted.
Please raise a message to SAP XX-SER-SAPSMP-SWC as suggested in the Note 19466 - Downloading SAP kernel patches
But as im working with unicode I have part 1 & 2 from market place & no issue with that,for Orc, 64 bit Win.
Pls do not perform combinations of patch 175 of Kernel Part - I and 179 of Kernel Part II , it may lead seviour damage of your run time performance.
regards,
rahul
Hi All,
I have raised a message and got this response:
Research shows that one recommendation in this case is to ignore the
EmActiveData: Invalid Context Handle -1 errors as long as Symptom A
(The work process terminates with a signal in the routine FiRemove)
isn't an issue since it's not really an error. One developer suggested
112 - Trace and error information in the "dev_" files
if you wanted to limit the size of the trace files. The second that
came up was to update just the disp+work package to at least level 179.
since, disp+work package 190 was available, I applied it and now I see no error messages.
Thanks again for the help.
Wish you a happy new year.
Ravali
> X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2214]
> X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2214]
> X *** ERROR => EmActiveData: Invalid Context Handle -1 [emxx.c 2214]
This is a known error - see
Note 1239685 - Core in extended memory (EM) management
Markus
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
88 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.