Found dead server (ORA-07445)

hello guys.
i have this odd situation in one of my database. Sometimes i have this in my alert log "found dead shared server 'S000', pid = (19,191)" with an ORA-07445 afterwards and which sometimes cause the application to return an error "Io exception: End of TNS data channel". I wonder why this appears in my db. by the way, the machine is our Materialized view db which is part of the master-mv replication setup. Im confused why in my master db, that error doesnt appear, so i guess this is not an application or configuration issue. I wonder if this has something to do with the current setup!!??? to understand further on my problem, here is my setup
MASTER DB (no problem on this machine)
- multi-threaded dual processor
- 4GB memory
- RAID 5 on SATA disk
- Net8 is in Dedicated server connection
- this machine is dedicated only for the database. no other applications running
- OS is redhat 9
- located in our main server farm in US
MATERIALIZED VIEW DB (this is where the errors appears)
- 1 processor
- 1GB memory
- IDE disk
- Net8 is in shared server connection
- this machine is not only a db server but also the web application and the middle tier so jboss resides on this machine.
- OS is in fedora core 3
- located in one of our office somewhere in ASIA
now you know my setup. so, any comments on this!?? if you'll ask me, my best findings why this error occurs is that maybe this has something to do with the resource!?? as you can see, jboss and oracle resides in one machine (currently, this is our setup due to budget constraints) so maybe this is the reason why i had a dead shared connection and the db has memory dumps?? and also, is there a way to test if the problem is due to lack of resources on the machine!?? i need to know so that i can justify to the management that we need to add machine dedicated for jboss and not with this kind of setup. its like our whole architecture was put into 1 machine (i know, this is a bad architecture). currently, we dont see any problem with the application as far as we know (since theres no complaints from the customers), though there is a proof the the application returns end of TNS channel error. I need some inputs from you guys so that i will have an idea on how to justify this to the management... i hope i can get reply from you..
Thanks
Erwin

please check metalink..
ORA-07445 [ACCESS_VIOLATION] [unable_to_trans_pc] on Windows Platforms [ID 456801.1]
ORA-07445 [ACCESS_VIOLATION] [_kkslmtl+524] [PC:0xF41EC0] [ADDR:0x0] [UNABLE_TO_READ] [] [ID 755278.1]
Regards
Rajesh

Similar Messages

Found dead shared server - ORA-07445:

Hi,
Apologies if this has been posted before but can someone help with getting a resolution to the above error that I noticed in my Alert log. Here's an except from the log. i can post the error file but it is 3.4mb in size.
Thanks in Advance,
Alan
Current log# 3 seq# 20641 mem# 0: D:\ORADATA\LIVE\REDO003.ORA
Sun May 02 20:47:05 2010
Thread 1 advanced to log sequence 20642 (LGWR switch)
Current log# 4 seq# 20642 mem# 0: D:\ORADATA\LIVE\REDO004.ORA
Sun May 02 20:49:47 2010
Errors in file d:\oracle\product\10.2.0\admin\live\bdump\live_s005_4612.trc:
ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [kghfrf+157] [PC:0x51F4AE9] [ADDR:0x21B1D6CC] [UNABLE_TO_READ] []
Sun May 02 20:50:16 2010
found dead shared server 'S005', pid = (16, 229)
Sun May 02 20:59:27 2010
ALTER SYSTEM ARCHIVE LOG
Sun May 02 20:59:27 2010
Thread 1 cannot allocate new log, sequence 20643
Private strand flush not complete
Current log# 4 seq# 20642 mem# 0: D:\ORADATA\LIVE\REDO004.ORA
Sun May 02 20:59:30 2010

please check metalink..
ORA-07445 [ACCESS_VIOLATION] [unable_to_trans_pc] on Windows Platforms [ID 456801.1]
ORA-07445 [ACCESS_VIOLATION] [_kkslmtl+524] [PC:0xF41EC0] [ADDR:0x0] [UNABLE_TO_READ] [] [ID 755278.1]
Regards
Rajesh

APEX error: Found dead shared server

Hi,
I frequently encounter an error when working with APEX. If I submit any change to APEX, fi a change on some page item, APEX asks me to whether I'd like to save the wwv_flow_accept URL. I then get a file save dialog. This doesn't happen all the time, but something like 2 out of 10 times I submit something.
Looking at the database logs, I see an entry in alert.log with this information:
<pre>
Fri May 22 17:56:36 2009
Errors in file c:\oraclexe\app\oracle\admin\xe\bdump\xe_s004_1948.trc:
ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [_npierr+487] [PC:0x5F22C3] [ADDR:0x4] [UNABLE_TO_READ] []
Fri May 22 17:56:40 2009
found dead shared server 'S004', pid = (18, 1)
</pre>
Looking into the respective trace file gives me this information:
<pre>
Dump file c:\oraclexe\app\oracle\admin\xe\bdump\xe_s004_1948.trc
Fri May 22 17:56:36 2009
ORACLE V10.2.0.1.0 - Production vsnsta=0
vsnsql=14 vsnxtr=3
Oracle Database 10g Express Edition Release 10.2.0.1.0 - Production
Windows XP Version V5.1 Service Pack 3
CPU : 1 - type 586, 1 Physical Cores
Process Affinity : 0x00000000
Memory (Avail/Total): Ph:727M/1511M, Ph+PgF:1181M/2133M, VA:1428M/2047M
Instance name: xe
Redo thread mounted by this instance: 1
Oracle process number: 18
Windows thread id: 1948, image: ORACLE.EXE (S004)
*** ACTION NAME:(PAGE 4311) 2009-05-22 17:56:36.625
*** MODULE NAME:(APEX:APPLICATION 4000) 2009-05-22 17:56:36.625
*** CLIENT ID:(CKH_DEV:2151496271973569) 2009-05-22 17:56:36.625
*** SESSION ID:(29.4) 2009-05-22 17:56:36.625
*** 2009-05-22 17:56:36.625
ksedmp: internal or fatal error
ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [_npierr+487] [PC:0x5F22C3] [ADDR:0x4] [UNABLE_TO_READ] []
Current SQL statement for this session:
COMMIT
----- PL/SQL Call Stack -----
object line object
handle number name
267D174C 1275 package body APEX_030200.WWV_FLOW
267D174C 5421 package body APEX_030200.WWV_FLOW
267D174C 13366 package body APEX_030200.WWV_FLOW
26521088 30 anonymous block
----- Call Stack Trace -----
memory dump follows
</pre>
Has anybody an idea what is going wrong on my machine here?
Best regards,
Jürgen

Hi,
I took a bit of time to dig deeper into this issue. I came to the conclusion that there is a bug in Oracle XE:
If you connect to Oracle XE database using the EPG path and if you create a report that gets its data over a database link, the shared server processes used to connect to the database break.
What I did to produce this error:
I installed Oracle XE Universal Edition on a Windows XP system
I then updated APEX to the latest version 3.2
At the database I simply created a database link pointing to the same schema the APEX-application is running at. I tested the database link.
I then produced a simple test application with just one Report (I also tried a PPR-report with the same result) that displays orders with a query in line with this:
<pre>
select o.order_id, i.order_item_id, i.quantity, p.product_name, i.unit_price, i.unit_price * i.quantity amount
from demo_orders@ckh o, demo_order_items@ckh i, demo_product_info@ckh p
where o.order_id = i.order_id
and i.product_id = p.product_id
order by o.order_id, i.order_item_id
</pre>
When I ran this application, I was sometimes able to see the report without an error, sometimes a shared server process broke. You can watch the processes breaking by opening the admin/bdump directory and see how the database writes trace files for the shared server processes.
Interesting to see is that the error happens not only when you try to see the report. If you hit the edit page link while running the page or if you submit the page definition with the link query in it, the same is likely to happen. You can see this error happening when APEX offers you to download the call to wwv_flow or the f-procedure. The contents of this download then is:
<pre>IBMPC/WIN_NT-8.1.0</pre>
with some binary information in front of the message.
Another bug I'd like to add came up when I was lucky to see the report with the PPR-template. I tried pagination but this wouldn't work. Looking into this, I found the following link:
<pre>
javascript:html_PPR_Report_Page(this,'R2060428410112776','javascript:$a_report('2060428410112776','16','15','15');')
</pre>
To my understanding this can't work at all if you look a the apostrophes. So how to proceed with this???
This to me is a severe problem, as I wanted to utilize APEX as a frontend for a production database to report the contents. I was informed by Varad that a way around this is to use an Apache access to Oracle XE but as far as I'm informed, this forces me into a licenced version in order to be able to run mod_plsql.
I read about the mod_owa-approach, but the programmers state that this is not compatible with APEX. So my question is: Do you have any suggestion on how to proceed with this?
Thanks,
Jürgen
Edited by: j.sieben on May 27, 2009 5:41 PM

"found dead shared server" in alert.log

Hi.
I am getting the following message in the alert log of 10.2.0.2 database.
Fri Feb 2 11:13:54 2007
found dead shared server 'S005', pid = (32, 3)
Fri Feb 2 11:14:24 2007
found dead shared server 'S005', pid = (32, 4)
Fri Feb 2 11:59:48 2007
found dead shared server 'S001', pid = (11, 1)
found dead shared server 'S005', pid = (32, 5)
Fri Feb 2 12:00:04 2007
found dead shared server 'S001', pid = (80, 165)
found dead shared server 'S001', pid = (80, 166)
What does it mean actaully...
will it affect(what impact) my database.
Thanks
JD

Hi,
Are you using MTS feature? If yes,
Then as given in the site:
http://searchoracle.techtarget.com/tip/0,289483,sid41_gci1018471,00.html
major issue I have seen with MTS is the dispatcher process getting abruptly killed. For some unknown reason the dispatcher process all of a sudden dies, killing the connected sessions. The following is an extract from the alert.log file for one such error:
Wed Sep 8 09:07:35 2004
Errors in file /u01/bdump/abc_d050_521.trc:
ORA-07445: exception encountered: core dump [00000001026BA2D4] [SIGSEGV] [Address
not mapped to object] [0x000000018] [] []
Wed Sep 8 09:07:45 2004
found dead dispatcher 'D050', pid = (667, 207)
The dead dispatcher process is restarted once pmon cleans the in-doubt sessions. The workaround for this issue is to turn off the DCD (dead connection detection) feature. Set SQLNET.EXPIRE_TIME = 0 in sqlnet.ora file. This issue occurred in v9.2.0.4 and v9.2.0.5 and Oracle is currently working to resolve the same.
I think you are not using MTS feature, otherwise you would have received errors
like above & trace file would have been generated & error.ORA-07445
If you are not using MTS feature,
set the initialization parameter shared_servers = 0. also make sure that the parameter dispatcher is not set (it has no default) to anything.
Message was edited by:
Seema

Found dead shared server errors keep appearing

I'm on Windows Server 2003 64-bit SP2
Running Oracle 11.1.0.6.0 64-big Enterprise
Configured as shared server running ASM
In my alert log I keep getting:
Thu May 01 18:36:05 2008
Exception [type: ACCESS_VIOLATION, UNABLE_TO_READ] [ADDR:0x3951B64C] [PC:0x72A7ABB, kghfrf()+161]
Errors in file g:\oracle\diag\rdbms\cma\cma\trace\cma_s004_3648.trc (incident=30201):
ORA-07445: exception encountered: core dump [kghfrf()+161] [ACCESS_VIOLATION] [ADDR:0x3951B64C] [PC:0x72A7ABB] [UNABLE_TO_READ] []
Thu May 01 18:36:05 2008
Errors in file g:\oracle\diag\rdbms\cma\cma\cdump\cmacore.log
ORA-07445: caught exception [ACCESS_VIOLATION] at [kghfrf()+161] [0x00000000072A7ABB]
Thu May 01 18:36:06 2008
Sweep Incident[30201]: completed
Thu May 01 18:36:07 2008
found dead shared server 'S004', pid = (24, 10)
Any idea what is causing this? I can find no references on metalink about this.
Thanks!

Thank you for your reply.
Unfortunately I'm on 11.1.0.6.0.
Note 310177.1 lists 4 bugs that have been fixed prior to 11.1.0.6.0
Note 4739114.8 list is a bug fixed in 11.1.0.6.0
And the ORA-600/ORA-7445 Troubleshooter on Metalink unfortunately does not bring up anything other than the bug docs fixed prior to 11.1.0.6.0 (nor has 11g support yet).
Has anyone else experienced this?

Page not found, ORA-07445: exception encountered: core dump

any one can help me to check this log? I get "page not found" occasionally.thanks .
Dump file f:\oraclexe\app\oracle\admin\xe\bdump\alert_xe.log
Tue Jan 08 18:14:24 2008
ORACLE V10.2.0.1.0 - Production vsnsta=0
vsnsql=14 vsnxtr=3
Windows XP Version V5.1 Service Pack 1
CPU : 2 - type 586
Process Affinity : 0x00000000
Memory (Avail/Total): Ph:2991M/3583M, Ph+PgF:4952M/5471M, VA:1945M/2047M
Tue Jan 08 18:14:24 2008
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 2
Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT =10
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.1.0.
System parameters with non-default values:
sessions = 49
__shared_pool_size = 222298112
__large_pool_size = 16777216
__java_pool_size = 4194304
__streams_pool_size = 0
spfile = F:\ORACLEXE\APP\ORACLE\PRODUCT\10.2.0\SERVER\DBS\SPFILEXE.ORA
sga_target = 805306368
control_files = F:\ORACLEXE\ORADATA\XE\CONTROL.DBF
__db_cache_size = 557842432
compatible = 10.2.0.1.0
db_recovery_file_dest = F:\oraclexe\app\oracle\flash_recovery_area
db_recovery_file_dest_size= 10737418240
undo_management = AUTO
undo_tablespace = UNDO
remote_login_passwordfile= EXCLUSIVE
dispatchers = (PROTOCOL=TCP) (SERVICE=XEXDB)
shared_servers = 5
job_queue_processes = 4
audit_file_dest = F:\ORACLEXE\APP\ORACLE\ADMIN\XE\ADUMP
background_dump_dest = F:\ORACLEXE\APP\ORACLE\ADMIN\XE\BDUMP
user_dump_dest = F:\ORACLEXE\APP\ORACLE\ADMIN\XE\UDUMP
core_dump_dest = F:\ORACLEXE\APP\ORACLE\ADMIN\XE\CDUMP
db_name = XE
open_cursors = 300
os_authent_prefix =
pga_aggregate_target = 268435456
PMON started with pid=2, OS id=1132
PSP0 started with pid=3, OS id=3612
MMAN started with pid=4, OS id=2392
DBW0 started with pid=5, OS id=3624
LGWR started with pid=6, OS id=1356
CKPT started with pid=7, OS id=1164
SMON started with pid=8, OS id=3832
RECO started with pid=9, OS id=2904
CJQ0 started with pid=10, OS id=2844
MMON started with pid=11, OS id=2176
Tue Jan 08 18:14:24 2008
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
MMNL started with pid=12, OS id=1292
Tue Jan 08 18:14:24 2008
starting up 5 shared server(s) ...
Oracle Data Guard is not available in this edition of Oracle.
Tue Jan 08 18:14:24 2008
alter database mount exclusive
Tue Jan 08 18:14:28 2008
Setting recovery target incarnation to 2
Tue Jan 08 18:14:28 2008
Successful mount of redo thread 1, with mount id 2524594368
Tue Jan 08 18:14:28 2008
Database mounted in Exclusive Mode
Completed: alter database mount exclusive
Tue Jan 08 18:14:28 2008
alter database open
Tue Jan 08 18:14:28 2008
Beginning crash recovery of 1 threads
Tue Jan 08 18:14:28 2008
Started redo scan
Tue Jan 08 18:14:28 2008
Completed redo scan
1305 redo blocks read, 132 data blocks need recovery
Tue Jan 08 18:14:28 2008
Started redo application at
Thread 1: logseq 62, block 3
Tue Jan 08 18:14:29 2008
Recovery of Online Redo Log: Thread 1 Group 1 Seq 62 Reading mem 0
Mem# 0 errs 0: F:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\ONLINELOG\O1_MF_1_3NX4T37T_.LOG
Tue Jan 08 18:14:29 2008
Completed redo application
Tue Jan 08 18:14:29 2008
Completed crash recovery at
Thread 1: logseq 62, block 1308, scn 126409946604
132 data blocks read, 132 data blocks written, 1305 redo blocks read
Tue Jan 08 18:14:30 2008
Thread 1 advanced to log sequence 63
Thread 1 opened at log sequence 63
Current log# 2 seq# 63 mem# 0: F:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\ONLINELOG\O1_MF_2_3NX4T4J3_.LOG
Successful open of redo thread 1
Tue Jan 08 18:14:30 2008
SMON: enabling cache recovery
Tue Jan 08 18:14:30 2008
Successfully onlined Undo Tablespace 1.
Tue Jan 08 18:14:30 2008
SMON: enabling tx recovery
Tue Jan 08 18:14:30 2008
Database Characterset is AL32UTF8
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
QMNC started with pid=20, OS id=524
Tue Jan 08 18:14:32 2008
Completed: alter database open
Tue Jan 08 18:14:33 2008
db_recovery_file_dest_size of 10240 MB is 0.98% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Tue Jan 08 18:14:53 2008
Memory Notification: Library Cache Object loaded into SGA
Heap size 2208K exceeds notification threshold (2048K)
KGL object name :XDB.XDbD/PLZ01TcHgNAgAIIegtw==
Tue Jan 08 18:56:55 2008
Errors in file f:\oraclexe\app\oracle\admin\xe\bdump\xe_s000_3780.trc:
ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [_npierr+487] [PC:0x5F22C3] [ADDR:0x4] [UNABLE_TO_READ] []
Tue Jan 08 18:56:55 2008
Errors in file f:\oraclexe\app\oracle\admin\xe\bdump\xe_s000_3780.trc:
ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [_npierr+487] [PC:0x5F22C3] [ADDR:0x4] [UNABLE_TO_READ] []
Tue Jan 08 18:56:56 2008
Errors in file f:\oraclexe\app\oracle\admin\xe\bdump\xe_s000_3780.trc:
ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [_npierr+487] [PC:0x5F22C3] [ADDR:0x4] [UNABLE_TO_READ] []
Tue Jan 08 18:57:00 2008
Errors in file f:\oraclexe\app\oracle\admin\xe\bdump\xe_s001_3252.trc:
ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [_npierr+487] [PC:0x5F22C3] [ADDR:0x4] [UNABLE_TO_READ] []
Tue Jan 08 18:57:00 2008
found dead shared server 'S000', pid = (14, 1)
Tue Jan 08 18:57:00 2008
Errors in file f:\oraclexe\app\oracle\admin\xe\bdump\xe_s001_3252.trc:
ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [_npierr+487] [PC:0x5F22C3] [ADDR:0x4] [UNABLE_TO_READ] []
Tue Jan 08 18:57:01 2008
Errors in file f:\oraclexe\app\oracle\admin\xe\bdump\xe_s001_3252.trc:
ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [_npierr+487] [PC:0x5F22C3] [ADDR:0x4] [UNABLE_TO_READ] []
Tue Jan 08 18:58:00 2008
found dead shared server 'S001', pid = (15, 1)
Tue Jan 08 19:03:56 2008
Errors in file f:\oraclexe\app\oracle\admin\xe\bdump\xe_s000_1816.trc:
ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [_npierr+487] [PC:0x5F22C3] [ADDR:0x4] [UNABLE_TO_READ] []
Tue Jan 08 19:03:57 2008
Errors in file f:\oraclexe\app\oracle\admin\xe\bdump\xe_s000_1816.trc:
ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [_npierr+487] [PC:0x5F22C3] [ADDR:0x4] [UNABLE_TO_READ] []
Tue Jan 08 19:03:57 2008
Errors in file f:\oraclexe\app\oracle\admin\xe\bdump\xe_s000_1816.trc:
ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [_npierr+487] [PC:0x5F22C3] [ADDR:0x4] [UNABLE_TO_READ] []
Tue Jan 08 19:03:58 2008
Errors in file f:\oraclexe\app\oracle\admin\xe\bdump\xe_s001_3056.trc:
ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [_npierr+487] [PC:0x5F22C3] [ADDR:0x4] [UNABLE_TO_READ] []
Tue Jan 08 19:04:03 2008
found dead shared server 'S000', pid = (14, 2)
Tue Jan 08 19:04:03 2008
Errors in file f:\oraclexe\app\oracle\admin\xe\bdump\xe_s002_312.trc:
ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [_npierr+487] [PC:0x5F22C3] [ADDR:0x4] [UNABLE_TO_READ] []
Tue Jan 08 19:05:03 2008
found dead shared server 'S001', pid = (15, 2)
found dead shared server 'S002', pid = (16, 1)
Tue Jan 08 19:05:30 2008
Errors in file f:\oraclexe\app\oracle\admin\xe\bdump\xe_s002_2864.trc:
ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] npierr+487] [PC:0x5F22C3] [ADDR:0x4] [UNABLE_TO_READ] []
Tue Jan 08 19:06:03 2008
found dead shared server 'S002', pid = (16, 2)

Anyone can help on it?
The content in trc :
Dump file f:\oraclexe\app\oracle\admin\xe\bdump\xe_s000_4016.trc
Thu Jan 10 11:22:05 2008
ORACLE V10.2.0.1.0 - Production vsnsta=0
vsnsql=14 vsnxtr=3
Oracle Database 10g Express Edition Release 10.2.0.1.0 - Production
Windows XP Version V5.1 Service Pack 1
CPU : 2 - type 586
Process Affinity : 0x00000000
Memory (Avail/Total): Ph:2860M/3583M, Ph+PgF:4122M/5471M, VA:1095M/2047M
Instance name: xe
Redo thread mounted by this instance: 1
Oracle process number: 14
Windows thread id: 4016, image: ORACLE.EXE (S000)
*** ACTION NAME:(PAGE 4150) 2008-01-10 11:22:05.390
*** MODULE NAME:(APEX:APPLICATION 4000) 2008-01-10 11:22:05.390
*** SERVICE NAME:(SYS$USERS) 2008-01-10 11:22:05.390
*** CLIENT ID:(DENNIS:4389204267300536) 2008-01-10 11:22:05.390
*** SESSION ID:(27.149) 2008-01-10 11:22:05.390
*** 2008-01-10 11:22:05.390
ksedmp: internal or fatal error
ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [_npierr+487] [PC:0x5F22C3] [ADDR:0x4] [UNABLE_TO_READ] []
Current SQL statement for this session:
COMMIT
----- PL/SQL Call Stack -----
object line object
handle number name
3BFE8478 6676 package body FLOWS_030000.WWV_FLOW
3BFE8478 9782 package body FLOWS_030000.WWV_FLOW
3BFF9504 255 procedure FLOWS_030000.F
3BFFC6EC 30 anonymous block
----- Call Stack Trace -----
calling call entry argument values in hex
location type point (? means dubious value)
_npierr+487 00000000 B70F61FA 660D72C2 F7AFA83
1DE5487 20E88300 8D0004C2
8589F841 FFFFFED8 F183B66
3B686 E9098B00 3A1 10845F6
29EE850F A2E90000 8B0002A5
8AFE909 6A0000 82474FF 707E8
~~~~~~~~~~~~~~~~
4C200 33104D8B C1D18BC0
ABF302E9 E183CA8B E9AAF303
3FA 2468B66 FC83B66 E5982
C33B6600 9451850F 5B80002
*** 2008-01-10 11:22:06.406
ksedmp: internal or fatal error
ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [_npierr+487] [PC:0x5F22C3] [ADDR:0x4] [UNABLE_TO_READ] []
Current SQL statement for this session:
COMMIT
----- PL/SQL Call Stack -----
object line object
handle number name
3BFE8478 6676 package body FLOWS_030000.WWV_FLOW
3BFE8478 9782 package body FLOWS_030000.WWV_FLOW
3BFF9504 255 procedure FLOWS_030000.F
3BFFC6EC 30 anonymous block
ksedmp: Obtaining call stack failed twice. not retrying

Found dead shared server

every day i found this message in the db log :
"Tue Mar 29 22:21:08 2005
found dead shared server 'S000', pid = (10, 5)
Wed Mar 30 13:51:58 2005
found dead shared server 'S000', pid = (10, 6)"
what do it means ??
it is danger for the databse ???

mrashid07 wrote:
In /bdump oracle only provide this information---
found dead shared server 'S000', pid = (17, 49)
How can I find out these processes (17, 49) which made the dead lock event??? There's no evidence from this message that the process was terminated due to a dead lock event.
Oracle also does not terminate a dead lock process - it raises a deadlock exception, allowing the process to catch this exception and re-act on it.
When Oracle does terminate a process, it will be due to some kind of fatal error. In which case there will be an ORA-0600 or similar error message in the alert log, together with a trace file reference (or cdmp ref) that contains the technical details as to what happened.
Dead shared servers are usually caused by an external process (or user) explicitly issuing a command to terminate the shared server process. E.g. killing the shared process at o/s level (using the o/s CLI), or via Oracle using the "+alter system kill session+" command.
You have not shown any evidence yet to the contrary - so the only conclusion that can be made thus far is that Oracle is not an issue here, but application code and/or users are.

Found dead shared server in aler file

hi
some times i got these entries in my alert log file.
found dead shared server 'S001', pid = (12, 2)
Tue Apr 01 15:47:28 2008
found dead shared server 'S001', pid = (12, 3)
Tue Apr 01 15:51:31 2008
found dead shared server 'S001', pid = (12, 4)
Tue Apr 01 15:55:37 2008
found dead shared server 'S001', pid = (12, 5)
Tue Apr 01 15:57:34 2008
found dead shared server 'S001', pid = (12, 6)
Tue Apr 01 16:49:41 2008
found dead shared server 'S000', pid = (11, 3)
Tue Apr 01 18:00:21 2008
Private_strands 7 at log switchi want to know is it harmful for oracle because its on my oracle live server.
so can any body tell me what are the negative effects of this error means is it cause
some serious effects.
thanks

What is your database version (complete) and O/S? Have the users been facing -ORA-3113 and ORA-3114 errors?
Oracle Metalink Document: Dead Shared Servers And Connections Fail with ORA-3113 Calling External Procedures: Doc ID: Note:333026.1
https://metalink.oracle.com/metalink/plsql/f?p=130:14:12268887976412175026::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,333026.1,1,1,1,helvetica
Adith

In FORMS 10G found dead shared server 'S000', pid = (10, 9)

during a test phase that we are doing before convert to FORMS 10G sometime the form crash (random) and in the same moment we foun the follow message in the log :
found dead shared server 'S000', pid = (10, 9)
DO YOU SOMEThING ???

what is MTS ??
we have doa standard installation with forms and report as application server and oracle 9i as db.
we leve the standard configuration for the db.
I don't Know what is MTS?

"found dead shared server ... " errors occured in oracle alert log

Dear all,
I have found a error message in my oracle alert log which is "found dead shared server 's000, pid=(10,1)'". What's this mean? and this error will casue a core dump in ../cdump directory.
btw. Thanks the answers of antti.koskinen and yingkuan.

one more thing, my server is not configured as shared server mode, it is dedicated server mode. but I don't know why system inform me "found dead shared server..".

ORA-07445 error in 10.2.0.4 database on Windows Server 2003

Hello,
We run an Oracle 10.2.0.4 database on a Windows 2003 Server. Yesterday we started encountering an odd, repeating error:
ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [__VInfreq__kqlCompileSynonym+3038] [PC:0x2F93172] [ADDR:0x30] [UNABLE_TO_READ] []
I've tried researching this error on Metalink and Google, however I have not been able to find any information on the specific "VInfreq__kqlCompileSynonym" portion of the issue. I do not see any immediate issues with the existing synonyms in our database, so I am uncertain what else to check.
We've tried a database reboot, a server reboot, and checked the Event Viewer logs.... None of these things proved useful. :) Has anyone else experienced this issue? Any insight in to the specifics of this error?
Thanks!
-Sabrina

I'm assuming you logged a TAR about this on Metalink?
(sorry, an SR on Metalink)
Message was edited by:
SomeoneElse

What found dead shared server error mean?

Please, I found the error found dead shared server in my alert.log file and I need to know what cause this error?
If it is critical?
What I should look up?

There is a known issue with using heterogenous services routine and MTS. Kuljeet is correct. Most probably you are hitting bug 3243584. You may have to check with oracle support on this!
-Ramesh

Found dead shared server 'S002', pid = (12, 37)

Whats up with that ? I got a client running a utility (Tora) against a 9.2.0.1 database, and every 30 seconds he get's disconnected, and this appears in the alert log
"found dead shared server 'S002', pid = (12, 37)"
.. Mind that this exact setup has worked flawlessly for at least 2 weeks, just begun doing it today... Only other thing going on is a massive insert operation, for wich i've had to add tablespaces to make room for... Should i restart the db ? shouldnt be neccesary, right ?

I recommend you to read completely this chapter:
Configuring Shared Servers
Proper configuration of shared servers can result in significant performance improvement.
This chapter contains the following topic:
Introduction to Shared Server Performance
Configuring the Number of Shared Servers
Introduction to Shared Server Performance
Using shared servers enables you to reduce the number of processes and the amount of memory consumed on the server machine. Shared servers are beneficial for systems where there are many OLTP users performing intermittent transactions.
Using shared servers rather than dedicated servers is also generally better for systems that have a high connection rate to the database. With shared servers, when a connect request is received, a dispatcher is already available to handle concurrent connection requests. With dedicated servers, on the other hand, a connection-specific dedicated server is sequentially initialized for each connection request.
Performance of certain database features can improve when a shared server architecture is used, and performance of certain database features can degrade slightly when a shared server architecture is used. For example, a session can be prevented from migrating to another shared server while parallel execution is active.
A session can remain nonmigratable even after a request from the client has been processed, because not all the user information has been stored in the UGA. If a server were to process the request from the client, then the part of the user state that was not stored in the UGA would be inaccessible. To avoid this, individual shared servers often need to remain bound to a user session.
Configuring the Number of Shared Servers
When using some features, you may need to configure more shared servers, because some servers might be bound to sessions for an excessive amount of time.
This section discusses how to reduce contention for processes used by Oracle's architecture:
Identifying Contention Using the Dispatcher-Specific Views
Reducing Contention for Dispatcher Processes
Reducing Contention for Shared Servers
Determining the Optimal Number of Dispatchers and Shared Servers
http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96533/features.htm#22666
Joel Pérez
http://otn.oracle.com/experts

Found dead multi-threaded server

hi all
My database is not running in multithread mode.
mts_dispatchers = "(protocol=TCP)"
I am getting such error
found dead multi-threaded server 'S000', pid = (8, 4)
Pl guide me
suresh

go on metalink http://metalink.oracle.com
Good Luck,
Fred

Found Dead Multi-Threaded Server Error!!!

I am in the process of testing an application based on EJBs deployed on an Oracle 8.1.5 database.
Some times the whole instance chashes without any obvious reason.
The error reported in the Alert file is
"found dead multi-threaded server 'SOOO',pid(8,1). Terminating Instance".
I check my code and i think that there is no problem with cleaning up resources. I increased also the JAVA_POOL_SIZE and LARGE_POOL_SIZE size without any result.
Can anybody give me a hint for the error cause?
Thanks in advance.
null

go on metalink http://metalink.oracle.com
Good Luck,
Fred

Found dead server (ORA-07445)

Similar Messages

Maybe you are looking for