Home » RDBMS Server » Server Administration » PMON Fail after ORA:00600 in Oracle 9.2.0.1
PMON Fail after ORA:00600 in Oracle 9.2.0.1 [message #192418] Tue, 12 September 2006 04:59
hvvaghani
Messages: 7
Registered: August 2006
Location: Surat,(guj),India
Junior Member

I am Facing a Problem from last two months in oracle database.

Due to that problem i have to restart oracle service/database.

On Sep-09-2006 I have to Face problems that never before due to that i have to restart oracle database to make it normal.
I Have Searched the Reasons. As I Found Responsible Things For Bottlenack is Memory Linkage and PMON Fail.
Database Alert is also indicating Deadlock in transaction statement but there is nothing that makes dead lock.
So i can't decide that what is exact problem.

---------------
Configuration of server
----------------
We have oracle database for manufacturing domain.
Operating System : Microsoft 2003 server
Hardware : IBM Xenon Dual server
Physical Memory : 2 GB
SGA : Allocation Of Memory is Attached in file.(1024 MB)
Daily increase size of Backup DUMP : 3 To 4 MB
Number of client machine : 200.
Concurrent session : 550-600.
We have also Second server with same configuration and Load, both server are connected with db link.
----------------

ORCL_ALERT
-----------------
Sat Sep 09 15:12:18 2006
DISTRIB TRAN ORCL.SERV_1.7132f004.74.15.51068
is local tran 74.15.51068 (hex=4a.0f.c77c))
delete pending collecting tran, scn=717354179 (hex=0.2ac1f4c3)
Sat Sep 09 15:12:22 2006
Error 28 trapped in 2PC on transaction 23.5.53181. Cleaning up.
Sat Sep 09 15:12:22 2006
Error stack returned to user:
Sat Sep 09 15:12:22 2006
DISTRIB TRAN ORCL.SERV_1.7132f004.23.5.53181
is local tran 23.5.53181 (hex=17.05.cfbd)
insert pending collecting tran, scn=717354216 (hex=0.2ac1f4e8)
Sat Sep 09 15:12:22 2006
DISTRIB TRAN ORCL.SERV_1.7132f004.23.5.53181
is local tran 23.5.53181 (hex=17.05.cfbd))
delete pending collecting tran, scn=717354216 (hex=0.2ac1f4e8)
ORA-02050: transaction 23.5.53181 rolled back, some remote DBs may be in-doubt
ORA-00028: your session has been killed
ORA-02063: preceding line from ORCL.SERV_2
Sat Sep 09 15:12:46 2006
Errors in file f:\ora9i\admin\orcl\bdump\orcl_ora_4144.trc:
ORA-00600: internal error code, arguments: [723], [27324], [27324], [memory leak], [], [], [], []

Sat Sep 09 15:13:04 2006
Errors in file f:\ora9i\admin\orcl\bdump\orcl_ora_4288.trc:
ORA-00600: internal error code, arguments: [723], [27324], [27324], [memory leak], [], [], [], []

Sat Sep 09 15:13:10 2006
Errors in file f:\ora9i\admin\orcl\bdump\orcl_ora_5360.trc:
ORA-00600: internal error code, arguments: [723], [72864], [72864], [memory leak], [], [], [], []

Sat Sep 09 15:13:16 2006
Errors in file f:\ora9i\admin\orcl\bdump\orcl_ora_4496.trc:
ORA-00600: internal error code, arguments: [723], [36432], [36432], [memory leak], [], [], [], []

Sat Sep 09 15:13:18 2006
Errors in file f:\ora9i\admin\orcl\bdump\orcl_ora_2576.trc:
ORA-00600: internal error code, arguments: [723], [27324], [27324], [memory leak], [], [], [], []

Sat Sep 09 15:13:39 2006
Errors in file f:\ora9i\admin\orcl\bdump\orcl_ora_3704.trc:
ORA-00600: internal error code, arguments: [723], [36432], [36432], [memory leak], [], [], [], []

Sat Sep 09 15:14:02 2006
Errors in file f:\ora9i\admin\orcl\bdump\orcl_ora_5592.trc:
ORA-00600: internal error code, arguments: [723], [27324], [27324], [memory leak], [], [], [], []

Sat Sep 09 15:15:35 2006
Errors in file f:\ora9i\admin\orcl\bdump\orcl_ora_3624.trc:
ORA-00600: internal error code, arguments: [723], [72864], [72864], [memory leak], [], [], [], []

Sat Sep 09 15:15:42 2006
Errors in file f:\ora9i\admin\orcl\bdump\orcl_ora_924.trc:
ORA-00600: internal error code, arguments: [723], [36432], [36432], [memory leak], [], [], [], []

Sat Sep 09 15:16:55 2006
Errors in file f:\ora9i\admin\orcl\bdump\orcl_ora_1120.trc:
ORA-00600: internal error code, arguments: [723], [36432], [36432], [memory leak], [], [], [], []

Sat Sep 09 15:17:26 2006
Errors in file f:\ora9i\admin\orcl\bdump\orcl_ora_3948.trc:
ORA-00600: internal error code, arguments: [723], [27324], [27324], [memory leak], [], [], [], []

Sat Sep 09 15:18:19 2006
Errors in file f:\ora9i\admin\orcl\bdump\orcl_ora_1816.trc:
ORA-00600: internal error code, arguments: [723], [27324], [27324], [memory leak], [], [], [], []

Sat Sep 09 15:19:23 2006
Errors in file f:\ora9i\admin\orcl\bdump\orcl_ora_1792.trc:
ORA-00600: internal error code, arguments: [723], [45540], [45540], [memory leak], [], [], [], []

Sat Sep 09 15:24:08 2006
----------------------------- THIS IS THE TIME FROM WHERE Bottlenack CREATED AND WE HAVE TO RESTART SERVER----------------
PMON failed to acquire latch, see PMON dump
PMON failed to acquire latch, see PMON dump
PMON failed to acquire latch, see PMON dump
PMON failed to acquire latch, see PMON dump
PMON failed to acquire latch, see PMON dump
PMON failed to acquire latch, see PMON dump
PMON failed to acquire latch, see PMON dump
PMON failed to acquire latch, see PMON dump
PMON failed to acquire latch, see PMON dump
PMON failed to acquire latch, see PMON dump
PMON failed to acquire latch, see PMON dump
PMON failed to acquire latch, see PMON dump
PMON failed to acquire latch, see PMON dump
PMON failed to acquire latch, see PMON dump
.....
We have restarted server after bottelnack


SGA MEMORY DISTRIBUTION IS ATTACHED IN FILE
reply me as fast as possible
am in big truble
thanks in adwance

Previous Topic: outline not working with order by clause
Next Topic: Oracle 7.3 on linux(urgent)
Goto Forum:
  


Current Time: Wed Dec 07 06:37:45 CST 2016

Total time taken to generate the page: 0.10529 seconds