- 最后登录
- 2023-8-16
- 在线时间
- 1686 小时
- 威望
- 2135
- 金钱
- 50532
- 注册时间
- 2011-10-12
- 阅读权限
- 200
- 帖子
- 5207
- 精华
- 39
- 积分
- 2135
- UID
- 2
|
2#
发表于 2013-7-18 21:02:18
10.2.0.4.0 + AIX
ksedmp: internal or fatal error
ORA-07445: exception encountered: core dump [osnsgl+0204] [SIGSEGV] [Invalid permissions for mapped object] [0x000000068] [] []
Current SQL information unavailable - no session.
----- Call Stack Trace -----
calling call entry argument values in hex
location type point (? means dubious value)
-------------------- -------- -------------------- ----------------------------
ksedst+001c bl ksedst1 000000000 ? 104A2CCED ?
ksedmp+0290 bl ksedst 104A2C670 ?
ssexhd+03e0 bl ksedmp 300001D15 ?
000044F0 ? 00000000
osnsgl3+0048 bl osnsgl 000000000 ? 000000001 ?
100000000 ? FFFFFFFFFFFA047 ?
FFFFFFFFFFF9BD8 ?
FFFFFFFFFFF9BE0 ?
FFFFFFFFFFFC790 ? 1100DD778 ?
kpkiafpt+0044 bl osnsgl3 000000003 ? 000004000 ?
FFFFFFFFFFFC730 ? 000000000 ?
FFFFFFFFFFFC6B0 ?
FFFFFFFFFFF9B20 ?
FFFFFFFFFFF9BE8 ?
FFFFFFFFFFFFCCE ?
upiini+0408 bl _ptrgl
upiah0+00ac bl upiini FFFFFFFFFFFC7F0 ? 11000B510 ?
10039A714 ? 000000000 ?
70000010F470290 ?
7000001084352B8 ? 110195CF8 ?
110393490 ?
kpuatch+0808 bl upiah0 1100DD628 ? 000000098 ?
104BB365C ? 000000000 ?
FFFFFFFFFFFC930 ? 11044BF20 ?
1003170F0 ?
OCIServerAttach+011 bl kpuatch 110195CF8 ? FFFFFFFFFFFDB68 ?
4 110195E78 ? FFFFFFFFFFFDA10 ?
FFFFFFFFFFFDA10 ?
9FFFFFFF000A798 ? 1000D22D4 ?
OCIServerAttach=>kpuatch=>upiah0=>upiini=>kpkiafpt=>osnsgl3
You encounter the following error.:
ORA-07445: exception encountered: core dump [osnsgl()+625] [SIGSEGV] [Invalid permissions for mapped object] [0x000000068] [] []
This may occur with or without an error ORA-3115 .
You may find some or all of the following function codes in the Call Stack Trace section of the trace file:
osnsgl osnsgl3 kpkiafpt upiini upiah0 kpuatch OCIServerAttach opiino opiodr
Cause
You have encountered
Bug 6122696 Dump [osnsgl] after ORA-3115 error
Solution
The bug is fixed in 10.2.0.5 and not present in 11.2 versions.
To implement the solution, please execute the following steps:
1. The following patch sets contain the fix:
10.2.0.5 (Server Patch Set)
11.1.0.7 Patch 37 on Windows Platforms
10.2.0.4 Patch 17 on Windows Platforms
10.2.0.3 Patch 21 on Windows Platforms
2. There are one off patches for a number of different platforms and a few different patch levels. The best option is to login to MOS and look for patch 6122696 on your OS. If it is not available for your current patch level, then an option would be to upgrade the database to a version that has an one-off patch available.
Apply one off patch 6122696 according to its readme file, if available on your platform and database version.
3. The issue is not present in 11.2. Upgrade to 11.2.0.1 or higher if possible.
Currently, there is no workaround for this bug.
|
|