-
Lru error
Hello Guru's!
Few days ago we got this error in trace files (10.2.0.4): LRU ERROR: LINK=(some big number). What is the meaning of this? Many user sessions could not work - until stop and restart database. Anyone see this error before? Is this some caching issue or what?
TIA,
jc
-
very less information to talk about. May be something related to memory???
have you find any other messages in alert log? and what did you find in your initial investigation?
Thanks,
Vijay Tummala
Try hard to get what you like OR you will be forced to like what you get.
-
Alert log has ORA-600 [17126] with ORA-7445 [Address not mapped to object].
In metalink there is note to change parameters _kgl_latch_count and _kghdsidx_count but what this has to do with the "LRU ERROR"?
-
Please open SR to Oracle.
Thanks,
Vijay Tummala
Try hard to get what you like OR you will be forced to like what you get.
-
I did open SR in Metalink. Analyst referred me to the note about changing _kghdsidx_count to one or _kgl_latch_count to less than or = 31 but no explanation why, how, going to fix the problem. Looking for some explanation, any shared experience. Thx,
-
support simply can't suggest to change the hidden parameter with out proper explanation. As hidden parameters are undocumented, we may not get proper information outside world unless until some one experienced it.
Let's wait for input from the members.
Thanks,
Vijay Tummala
Try hard to get what you like OR you will be forced to like what you get.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|