ORA-00600 in AQ background job
Hi all,
I am getting an ORA-00600 in AQ background job responsible for dequeuing messages.
The trace output is as follows:
ksedmp: internal or fatal error
ORA-00600: internal error code, arguments: [kwqidjqp0], [], [], [], [], [], [], []
Current SQL statement for this session:
DECLARE job BINARY_INTEGER := :job; next_date DATE := :mydate; broken BOOLEAN := FALSE; BEGIN sys.dbms_aqadm_sys.register_driver(); :mydate := next_date; IF broken THEN :b := 1; ELSE :b := 0; END IF; END;
----- PL/SQL Call Stack -----
object line object
handle number name
6713D69C 7249 package body SYS.DBMS_AQADM_SYS
6713D69C 7280 package body SYS.DBMS_AQADM_SYS
66EB50B4 1 anonymous block
----- Call Stack Trace -----
calling call entry argument values in hex
location type point (? means dubious value)
I have job_queue_processes set to 4 and aq_tm_processes set to 2.
Has anyone seen this? Please help.
Thanks,
Atul
May be a bit late to help the original posters, but just for reference, this looks very similar to the following described in Metalink:
Bug 3033868 OERI[kwqidjqp0] from DBMS_AQADM_SYS.REGISTER_DRIVER
This note gives a brief overview of bug 3033868.
The content was last updated on: 20-JAN-2004
Affects:
Range of versions believed to be affected Versions < 10.1.0.2
Versions confirmed as being affected
* 9.0.1.4
* 9.2.0.4
Platforms affected Generic (all / most platforms affected)
Fixed:
This issue is fixed in
* 9.2.0.5 (Server Patch Set)
* 10.1.0.2 (Base Release)
Edited by: Anthony Maslowski on Feb 5, 2010 1:26 PM
Similar Messages
-
ORA-20000 error when executing background jobs in BI System
Hello Experts,
We newly installed NW2004s System. Few BI related background jobs are showing Error no: 4 or Error no: 3 in SM50. Also few BI related background jobs are giving error "ORA-20000 occurred when executing SQL statement (parse error offset=0)". Please let me know what does Error 4 or 3 mean in SM50 and how to resolve Ora-20000 error?
ThanksThis may be to do with insufficient authorization for the user (for creating statistics for example). Check OSS note 963760.
-
Hello,
ORACLE 10GR2
WINDOWS XP
SIR,
I on my test db I hav got this error :
ORA-00600: internal error code, arguments: [Carr_Oscan], [], [], [], [], [], [], []
Is there any solution to get my db back. I hav not backup or archivelog as it was just a test db with default oracle installation.
folloing some starting and bottom lines from my alert log :
Dump file e:\oracle\product\10.2.0/admin/orcl/bdump\alert_orcl.log
Tue Sep 29 12:26:34 2009
ORACLE V10.2.0.1.0 - Production vsnsta=0
vsnsql=14 vsnxtr=3
Windows XP Version V5.1 Service Pack 3
CPU : 2 - type 586, 1 Physical Cores
Process Affinity : 0x00000000
Memory (Avail/Total): Ph:1182M/2038M, Ph+PgF:1523M/2252M, VA:1940M/2047M
Tue Sep 29 12:26:34 2009
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Shared memory segment for instance monitoring created
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 =18
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:
processes = 150
sga_target = 612368384
control_files = E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\CONTROL01.CTL, E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\CONTROL02.CTL, E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\CONTROL03.CTL
db_block_size = 8192
compatible = 10.2.0.1.0
db_file_multiblock_read_count= 16
db_recovery_file_dest = E:\oracle\product\10.2.0/flash_recovery_area
db_recovery_file_dest_size= 2147483648
undo_management = AUTO
undo_tablespace = UNDOTBS1
remote_login_passwordfile= EXCLUSIVE
db_domain =
dispatchers = (PROTOCOL=TCP) (SERVICE=orclXDB)
job_queue_processes = 10
audit_file_dest = E:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\ADUMP
background_dump_dest = E:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\BDUMP
user_dump_dest = E:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\UDUMP
core_dump_dest = E:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\CDUMP
db_name = orcl
open_cursors = 300
pga_aggregate_target = 202375168
PMON started with pid=2, OS id=2468
PSP0 started with pid=3, OS id=132
MMAN started with pid=4, OS id=2972
DBW0 started with pid=5, OS id=1832
LGWR started with pid=6, OS id=3128
CKPT started with pid=7, OS id=2240
SMON started with pid=8, OS id=2052
RECO started with pid=9, OS id=3304
CJQ0 started with pid=10, OS id=1804
MMON started with pid=11, OS id=3292
Tue Sep 29 12:26:35 2009
Beginning crash recovery of 1 threads
parallel recovery started with 2 processes
Sat Nov 21 17:49:04 2009
Started redo scan
Sat Nov 21 17:49:05 2009
Errors in file e:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_3784.trc:
ORA-00600: internal error code, arguments: [kcrfrgv_scn1], [], [], [], [], [], [], []
Sat Nov 21 17:49:17 2009
Aborting crash recovery due to error 600
Sat Nov 21 17:49:17 2009
Errors in file e:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_3784.trc:
ORA-00600: internal error code, arguments: [kcrfrgv_scn1], [], [], [], [], [], [], []
ORA-600 signalled during: alter database open...
Mon Nov 23 10:51:41 2009
db_recovery_file_dest_size of 2048 MB is 0.00% 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.
Thu Nov 26 15:10:27 2009
Starting ORACLE instance (normal)
Thu Nov 26 15:14:26 2009
Starting ORACLE instance (normal)
Thu Nov 26 15:16:23 2009
Starting ORACLE instance (normal)
Thu Nov 26 15:19:18 2009
Shutting down instance: further logons disabled
Thu Nov 26 15:19:18 2009
Stopping background process CJQ0
Thu Nov 26 15:19:18 2009
Stopping background process MMNL
Thu Nov 26 15:19:19 2009
Stopping background process MMON
Thu Nov 26 15:19:20 2009
Shutting down instance (immediate)
License high water mark = 3
Thu Nov 26 15:19:20 2009
Stopping Job queue slave processes
Thu Nov 26 15:19:20 2009
Job queue slave processes stopped
Waiting for dispatcher 'D000' to shutdown
All dispatchers and shared servers shutdown
Thu Nov 26 15:19:22 2009
ALTER DATABASE CLOSE NORMAL
ORA-1109 signalled during: ALTER DATABASE CLOSE NORMAL...
Thu Nov 26 15:19:22 2009
ALTER DATABASE DISMOUNT
Completed: ALTER DATABASE DISMOUNT
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Thu Nov 26 15:19:27 2009
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 =18
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:
processes = 150
__shared_pool_size = 192937984
__large_pool_size = 4194304
__java_pool_size = 4194304
__streams_pool_size = 0
spfile = E:\ORACLE\PRODUCT\10.2.0\DB_1\DBS\SPFILEORCL.ORA
sga_target = 612368384
control_files = E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\CONTROL01.CTL, E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\CONTROL02.CTL, E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\CONTROL03.CTL
db_block_size = 8192
__db_cache_size = 402653184
compatible = 10.2.0.1.0
db_file_multiblock_read_count= 16
db_recovery_file_dest = E:\oracle\product\10.2.0/flash_recovery_area
db_recovery_file_dest_size= 2147483648
undo_management = AUTO
undo_tablespace = UNDOTBS1
remote_login_passwordfile= EXCLUSIVE
db_domain =
dispatchers = (PROTOCOL=TCP) (SERVICE=orclXDB)
job_queue_processes = 10
audit_file_dest = E:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\ADUMP
background_dump_dest = E:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\BDUMP
user_dump_dest = E:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\UDUMP
core_dump_dest = E:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\CDUMP
db_name = orcl
open_cursors = 300
pga_aggregate_target = 202375168
PMON started with pid=2, OS id=5416
PSP0 started with pid=3, OS id=6132
MMAN started with pid=4, OS id=3640
DBW0 started with pid=5, OS id=3048
LGWR started with pid=6, OS id=2220
CKPT started with pid=7, OS id=756
SMON started with pid=8, OS id=2328
RECO started with pid=9, OS id=2460
CJQ0 started with pid=10, OS id=2380
MMON started with pid=11, OS id=2356
Thu Nov 26 15:19:29 2009
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
Thu Nov 26 15:19:29 2009
starting up 1 shared server(s) ...
Thu Nov 26 15:19:30 2009
ALTER DATABASE MOUNT
MMNL started with pid=12, OS id=3664
Thu Nov 26 15:19:34 2009
Setting recovery target incarnation to 2
Thu Nov 26 15:19:34 2009
Successful mount of redo thread 1, with mount id 1231755394
Thu Nov 26 15:19:34 2009
Database mounted in Exclusive Mode
Completed: ALTER DATABASE MOUNT
Thu Nov 26 15:19:34 2009
ALTER DATABASE OPEN
Thu Nov 26 15:19:35 2009
Beginning crash recovery of 1 threads
parallel recovery started with 2 processes
Thu Nov 26 15:19:35 2009
Started redo scan
Thu Nov 26 15:19:35 2009
Errors in file e:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_5304.trc:
ORA-00600: internal error code, arguments: [kcrfrgv_scn1], [], [], [], [], [], [], []
Thu Nov 26 15:19:39 2009
Aborting crash recovery due to error 600
Thu Nov 26 15:19:39 2009
Errors in file e:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_5304.trc:
ORA-00600: internal error code, arguments: [kcrfrgv_scn1], [], [], [], [], [], [], []
ORA-600 signalled during: ALTER DATABASE OPEN...
Thu Nov 26 15:34:32 2009
db_recovery_file_dest_size of 2048 MB is 0.00% 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.
Kindly tell me for knowldege whether is db can be recovered or not. I have no metalink support.
Regards
Edited by: ora-boy on Nov 26, 2009 11:37 PMAn internal error happened.
The parameters that come with this error give more information about the location where this exception occured.
You should contact Oracle support or browse metalink for more information regarding your specific error condition.
Also check the alert.log file and other trace files in the background_dump_dest or user_dump_dest for additional information.
Should you want to find a solution yourself and have access to Oracle Metalink, Oracle support provides the ORA-600 Lookup Tool with which you can troubleshoot the ORA-600.
Regards
Asif Kabir -
Hello!
After googling a lot, I really don't know what may have caused this problem when I'm shutting the DB, as It's a generic one.. Any suggestions?
I'm running oracle on version 10.2.0.3.0 on Win Server 2003 Enterprise SP2.
Part of the alert.log:
Mon Sep 26 07:00:49 2011
Starting background process EMN0
EMN0 started with pid=27, OS id=5192
Mon Sep 26 07:00:49 2011
Shutting down instance: further logons disabled
Mon Sep 26 07:00:50 2011
Stopping background process QMNC
Mon Sep 26 07:00:51 2011
Stopping background process CJQ0
Mon Sep 26 07:00:51 2011
Stopping background process MMNL
Mon Sep 26 07:00:52 2011
Stopping background process MMON
Mon Sep 26 07:00:53 2011
Shutting down instance (immediate)
License high water mark = 26
Mon Sep 26 07:00:53 2011
Stopping Job queue slave processes
Mon Sep 26 07:00:53 2011
Job queue slave processes stopped
Waiting for shared server 'S000' to die
Waiting for shared server 'S001' to die
Waiting for shared server 'S002' to die
Waiting for shared server 'S003' to die
Mon Sep 26 07:01:04 2011
Waiting for shared server 'S004' to die
Mon Sep 26 07:01:23 2011
All dispatchers and shared servers shutdown
Mon Sep 26 07:01:23 2011
alter database close normal
Mon Sep 26 07:01:24 2011
SMON: disabling tx recovery
SMON: disabling cache recovery
Mon Sep 26 07:01:24 2011
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Thread 1 closed at log sequence 4300
Successful close of redo thread 1
Mon Sep 26 07:01:25 2011
Completed: alter database close normal
Mon Sep 26 07:01:25 2011
alter database dismount
Completed: alter database dismount
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
System State dumped to trace file c:\oracle\product\admin\teste\udump\teste_ora_5000.trc
Mon Sep 26 07:01:35 2011
Errors in file c:\oracle\product\admin\teste\udump\teste_ora_5000.trc:
*ORA-00600: internal error code, arguments: [LibraryCacheNotEmptyOnClose], [], [], [], [], [], [], []*Dump file c:\oracle\product\admin\teste\bdump\alert_teste.log
Mon Sep 26 07:09:49 2011
ORACLE V10.2.0.3.0 - Production vsnsta=0
vsnsql=14 vsnxtr=3
Windows Server 2003 Version V5.2 Service Pack 2
CPU : 2 - type 586, 2 Physical Cores
Process Affinity : 0x00000000
Memory (Avail/Total): Ph:1617M/2047M, Ph+PgF:3114M/3437M, VA:1938M/2047M
Mon Sep 26 07:09:49 2011
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
Part of the file teste_ora_5000.trc:
FREELIST CHUNK COUNT:3192 OBJECT SIZE:36
LATCH:1 TOTAL SPACE: 114912
FREELIST CHUNK COUNT:3190 OBJECT SIZE:36
LATCH:2 TOTAL SPACE: 119016
FREELIST CHUNK COUNT:3306 OBJECT SIZE:36
BUCKET 10240:
LIBRARY OBJECT HANDLE: handle=341a4de8 mtx=341A4E9C(0) cdp=0
name=XDB.mime-mapping-type32_T
hash=bfce5ac8b2228d568d457016dd2a2800 timestamp=11-19-2006 11:07:38
namespace=TABL flags=KGHP/TIM/SML/[02000000]
kkkk-dddd-llll=0000-0000-0000 lock=0 pin=0 latch#=2 hpc=0132 hlc=0132
lwt=341A4E44[341A4E44,341A4E44] ltm=341A4E4C[341A4E4C,341A4E4C]
pwt=341A4E28[341A4E28,341A4E28] ptm=341A4E30[341A4E30,341A4E30]
ref=341A4E64[341A4E64,341A4E64] lnd=341A4E70[341A4D18,32B481F8]
LIBRARY OBJECT last freed from HPD addn data CBK
BUCKET 10240 total object count=1
BUCKET 40441:
LIBRARY OBJECT HANDLE: handle=341a4c90 mtx=341A4D44(0) cdp=0
name=XDB.mime-mapping34_COLL
hash=4fd0f011144ed13e64cf519ed06c9df9 timestamp=11-19-2006 11:07:38
namespace=TABL flags=KGHP/TIM/SML/[02000000]
kkkk-dddd-llll=0000-0000-0000 lock=0 pin=0 latch#=2 hpc=0004 hlc=0004
lwt=341A4CEC[341A4CEC,341A4CEC] ltm=341A4CF4[341A4CF4,341A4CF4]
pwt=341A4CD0[341A4CD0,341A4CD0] ptm=341A4CD8[341A4CD8,341A4CD8]
ref=341A4D0C[341A4D0C,341A4D0C] lnd=341A4D18[32B481F8,341A4E70]
LIBRARY OBJECT last freed from HPD addn data CBK
BUCKET 40441 total object count=1
ANONYMOUS LIST:
LIST OF HANDLES WITH DEPENDENTS:
LATCH=0 unpin_call_count=3072 hd_count=0 hd_unpinned_count=3284
LATCH=1 unpin_call_count=3069 hd_count=2 hd_unpinned_count=3263
341a4de8 -> 341a4c90
LATCH=2 unpin_call_count=3085 hd_count=0 hd_unpinned_count=3503
*** 2011-09-26 07:01:35.445
ksedmp: internal or fatal error
*ORA-00600: internal error code, arguments: [LibraryCacheNotEmptyOnClose], [], [], [], [], [], [], []*Current SQL information unavailable - no session.
----- Call Stack Trace -----
calling call entry argument values in hex
location type point (? means dubious value)
ksedst+38 CALLrel ksedst1+0 0 1
ksedmp+898 CALLrel ksedst+0 0
ksfdmp+14 CALLrel ksedmp+0 3
_kgerinv+140 CALLreg 00000000 B158D30 3
kgeasnmierr+19 CALLrel kgerinv+0 B158D30 9CB1F64 607AAD14 0
A19CDA4
__VInfreq__kglshu+4 CALLrel _kgeasnmierr+0 B158D30 9CB1F64 607AAD14 0
6 B158D30 4
kqlnfy+641 CALLrel kglshu+0 B158D30 0
_kscnfy+1334 CALLreg 00000000 18 0
ksmshu+273 CALLrel kscnfy+0
opistpreal+1038 CALLrel _ksmshu+0 0
opistp+267 CALLrel opistp_real+0 31 2 A19F68C
_opiodr+1099 CALLreg 00000000 31 2 A19F68C
_ttcpip+996 CALLreg 00000000 31 2 A19F68C 0
_opitsk+1080 CALL??? 00000000
opiino+1087 CALLrel opitsk+0 0 0
_opiodr+1099 CALLreg 00000000 3C 4 A19FC28
opidrv+819 CALLrel opiodr+0 3C 4 A19FC28 0
sou2o+45 CALLrel opidrv+0 3C 4 A19FC28
opimaireal+112 CALLrel _sou2o+0 A19FC1C 3C 4 A19FC28
opimai+92 CALLrel opimai_real+0 2 A19FC54
OracleThreadStart@ CALLrel opimai+0
4+726
77E6482C CALLreg 00000000
--------------------- Binary Stack Dump ---------------------
========== FRAME [1] (_ksedst+38 -> _ksedst1+0) ==========
Dump of memory from 0x0A19CC78 to 0x0A19CC88
A19CC70 0A19CC88 0040490B [.....I@.]
A19CC80 00000000 00000001 [........]
========== FRAME [2] (_ksedmp+898 -> _ksedst+0) ==========
Dump of memory from 0x0A19CC88 to 0x0A19CD48
A19CC80 0A19CD48 00403303 [H....3@.]
A19CC90 00000000 00000258 0A19CCA0 004238A0 [....X........8B.]
A19CCA0 0A19CCA8 0043CB08 0B1591B8 60731B40 [[email protected]`]
A19CCB0 0B1591BD 607AAD14 0000001B 00000000 [......z`........]
Thanks in advance!!Hi;
ORA-00600: internal error code, You are getting oracle internal error(ORA 600) which mean you could need to work wiht oracle support team. Please see below note, if its not help than i suggest log a sr:
Troubleshoot an ORA-600 or ORA-7445 Error Using the Error Lookup Tool [ID 153788.1]
Regard
Helios -
Ora-00600 while Refreshing data from Source DB
Hi Folks,
Actually i have an ODS system on Target database which has Mappings to source DB. Both DBs are 10.1.0.4.
Most of the refreshes are susccuful excpet for one large mapping.
I got this in the Source DB alert.log :
## Mon Jun 16 12:21:38 2008
## Errors in file /oracle/admin/PPRD/bdump/pprd_mmon_1911.trc:
## ORA-00600: internal error code, arguments: [ktte_verify_tsth], [], [], [], [], [], [], ## []
## Mon Jun 16 12:21:42 2008
## Restarting dead background process MMON
## MMON started with pid=45, OS id=17487
## Mon Jun 16 12:21:45 2008
## Errors in file /oracle/admin/PPRD/bdump/pprd_mmon_17487.trc:
## ORA-00600: internal error code, arguments: [ktte_verify_tsth], [], [], [], [], [], [], ## []
When i logged an SR with Oracle, they didn't help me because the DB is no longer supported ( 10.1.0.4 ) !
The metalink has some bugs that hit this issue but the problem that this used to work fine.
My servers are on Solaris Sparc 64-bit
Please advise Gurus,
Cheers,
FerasHi,
We have a BANNER system which uses a cross product called ODS ( Operational Data Storage ) . ODS is a datawarehouse DB and we run ETL Jobs to refresh data from source DB to ODS database. Jobs which contains PL/SQL insert/update/delete code. When we run one of the heavy refresh processes, we face the issue above.
Please Advise,
Cheers,
Feras -
SAP_COLLECTOR_FOR_PERFMONITOR background job cancelled in SM37
Dear all ,
One of the scheduled background job has been cancelled .
Kindly check the below loga and Background job details .
Job name SAP_COLLECTOR_FOR_PERFMONITOR
Job class C
Status Canceled
(ABAP Program
Name RSCOLL00
Variant
Language EN)
Job Log :
30.05.2010 06:20:32 Job started
30.05.2010 06:20:32 Step 001 started (program RSCOLL00, variant , user ID DDIC)
30.05.2010 06:20:37 Clean_Plan:Cleanup of DB13 Plannings
30.05.2010 06:20:37 Clean_Plan:started by RSDBPREV on server PRDCIXI
30.05.2010 06:20:38 Clean_Plan:Cleaning up jobs of system IRP
30.05.2010 06:20:39 Clean_Plan:finished
30.05.2010 06:20:43 ABAP/4 processor: DBIF_RTAB_SQL_ERROR
30.05.2010 06:20:43 Job cancelled
Kindly suggestDear all ,
Kindly check the ST22 error logs .
Short text SQL error occurred in the database when accessing a table. What happened? The database system detected a deadlock and avoided it by rolling back your transaction. What can you do? If possible (and necessary), repeat the last database transaction in the hope that locking the object will not result in another deadlock. Note which actions and input led to the error. For further help in handling the problem, contact your SAP administrator . You can use the ABAP dump analysis transaction ST22 to view and manage termination messages, in particular for long term reference. Error analysis The database system recognized that your last operation on the database would have led to a deadlock. Therefore, your transaction was rolled back to avoid this. ORACLE always terminates any transaction that would result in deadlock. The other transactions involved in this potential deadlock are not affected by the termination. Last error logged in SAP kernel Component............ "SAP-Gateway" Place................ "SAP-Gateway on host PRDCIXI / sapgw01" Version.............. 2 Error code........... 679 Error text........... "program prodoradb.sapccmsr.99 not registered" Description.......... "TP prodoradb.sapccmsr.99 not registered" How to correct the error Database error text........: "ORA-00060: deadlock detected while waiting for resource" Internal call code.........: "[RTAB/UPD /MONI ]" Please check the entries in the system log (Transaction SM21). If the error occures in a non-modified SAP program, you may be able to find an interim solution in an SAP Note. If you have access to SAP Notes, carry out a search with the following keywords: "DBIF_RTAB_SQL_ERROR" " " "RSHOST3M" or "RSHOST3M" "PUT_LOGBOOK" If you cannot solve the problem yourself and want to send an error notification to SAP, include the following information: 1. The description of the current problem (short dump) To save the description, choose "System->List->Save->Local File (Unconverted)". 2. Corresponding system log Display the system log by calling transaction SM21. Restrict the time interval to 10 minutes before and five minutes after the short dump. Then choose "System->List->Save->Local File (Unconverted)". 3. If the problem occurs in a problem of your own or a modified SAP System call.......... " " Module............... "gwr3cpic.c" Line................. 1835 The error reported by the operating system is: Error number..... " " Error text....... " "
for detail log.
System environment
SAP-Release 700
Application server... "PRDCIXI"
Network address...... "10.54.145.32"
Operating system..... "AIX"
Release.............. "5.3"
Hardware type........ "000184CAD400"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 8
Shortdump setting.... "full"
Database server... "PRODORADB"
Database type..... "ORACLE"
Database name..... "IRP"
Database user ID.. "SAPSR3"
Terminal................. " "
Char.set.... "C"
SAP kernel....... 700
created (date)... "Mar 7 2010 21:00:49"
create on........ "AIX 2 5 005DD9CD4C00"
Database version. "OCI_102 (10.2.0.2.0) "
Patch level. 246
Patch text.. " "
Database............. "ORACLE 10.1.0.., ORACLE 10.2.0.., ORACLE 11.2...*"
SAP database version. 700
Operating system..... "AIX 1 5, AIX 2 5, AIX 3 5, AIX 1 6"
Memory consumption
Roll.... 1217248
EM...... 0
Heap.... 0
Page.... 32768
MM Used. 1050520
MM Free. 146024
and Transaction
Client.............. 000
User................ "DDIC"
Language key........ "E"
Transaction......... " "
Transactions ID..... "4BFF227871E00187E10080000A369120"
In the source code you have the termination point in line 521
of the (Include) program "RSHOST3M".
The program "RSHOST3M" was started as a background job.
Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR"
Job Initiator.. "DDIC"
Job Number..... 02033500
In the source code you have the termination point in line 521
of the (Include) program "RSHOST3M".
The program "RSHOST3M" was started as a background job.
Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR"
Job Initiator.. "DDIC"
Job Number..... 02033500
Program............. "RSHOST3M"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
rmation on where terminated
Termination occurred in the ABAP program "RSHOST3M" - in "PUT_LOGBOOK".
The main program was "RSHOST3M ". -
Background job BI_ODSA_ASD is getting cancelled, set privilege at db level
Hi,
Background job BI_ODSA_ASD is getting cancelled,
i have increased the tablespace, still no luck,
last time i faced the same problem at that time , i gave some permission at oracle level which worked fine, i dont not remember now,
it was something like GRANT PRIVILEGE SAPSYS SAPCON...... (not sure)
if anyone knows please let me know.
Regards,
SMRuntime Errors UNCAUGHT_EXCEPTION
Exception CX_SDB_ORA_PROGRAM_ERROR
Date and Time 20.09.2007 15:46:44
Short text
An exception occurred that was not caught.
What happened?
The exception 'CX_SDB_ORA_PROGRAM_ERROR' was raised, but it was not caught
anywhere along
the call hierarchy.
Since exceptions represent error situations and this error was not
adequately responded to, the running ABAP program
'CL_SDB_ORA_UPDATE_STATS=======CP' has to be
terminated.
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
An exception occurred which is explained in detail below.
The exception, which is assigned to class 'CX_SDB_ORA_PROGRAM_ERROR', was not
caught and
therefore caused a runtime error.
The reason for the exception is:
ـbernehmen
The occurrence of the exception is closely related to the occurrence of
a previous exception "CX_SQL_EXCEPTION", which was raised in the program
"CL_SQL_STATEMENT==============CP",
specifically in line 31 of the (include) program
"CL_SQL_STATEMENT==============CM002".
The cause of the exception was:
ORA-20000: Insufficient privileges
ORA-06512: at "SYS.DBMS_STATS", line
2150
ORA-06512: at "SYS.DBMS_STATS", line 14112
ORA-06512: at line 1
How to correct the error
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"UNCAUGHT_EXCEPTION" "CX_SDB_ORA_PROGRAM_ERROR"
"CL_SDB_ORA_UPDATE_STATS=======CP" or "CL_SDB_ORA_UPDATE_STATS=======CM00I"
"UPDATE_STATS"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error. -
Background job failing - ECC 6.0, Solution Manager 7.0
Dear All,
Four days back, I have installed the Solution Manager 7.0 and ECC 6.0 on
HPUX IA64 hardware with database as Oracle 10.2.0.2.0 (Unicode).
In both server, latest kernel patch has been applied.
The Support package versions are (both server):
KERNEL (Release 700) 146
SAP_BASIS 0014
SAP_ABA 0014
PI_BASIS(2005_1_700) 0014
ST-PI 0005
SAP_BW 0016
While checking the the jobs from SM37, in both the server,
I am observing that following jobs are always failing with
same reason:
SAP_COLLECTOR_FOR_PERFMONITOR
=============================
Date Time Message text Message class Message no. Message type
========== ======== ====================================================================== ============= =========== ============
15.05.2008 06:25:12 Job started 00 516 S
15.05.2008 06:25:12 Step 001 started (program RSCOLL00, variant , user ID BGDUSER) 00 550 S
15.05.2008 06:25:18 Clean_Plan:Cleanup of DB13 Plannings DB6PM 000 S
15.05.2008 06:25:18 Clean_Plan:started by RSDBPREV on server gcbeccd DB6PM 000 S
15.05.2008 06:25:18 Clean_Plan:Cleaning up jobs of system RD3 DB6PM 000 S
15.05.2008 06:25:18 Clean_Plan:finished DB6PM 000 S
15.05.2008 06:25:18 Database system not supported S1 101 S
15.05.2008 06:25:36 ABAP/4 processor: DBIF_DSQL2_SQL_ERROR 00 671 A
15.05.2008 06:25:36 Job cancelled 00 518 A
SAP_REORG_UPDATERECORDS
=======================
Date Time Message text Message class Message no. Message type
========== ======== ===================================================================== ============= =========== ============
14.05.2008 00:31:01 Job started 00 516 S
14.05.2008 00:31:01 Step 001 started (program RSM13002, variant SAP&001, user ID BGDUSER) 00 550 S
14.05.2008 00:31:01 Reorganization of update date not allowed in batch 15 100 A
14.05.2008 00:31:02 Job cancelled 00 518 A
SAP_WP_CACHE_RELOAD_FULL
========================
Date Time Message text Message class Message no. Message type
========== ======== ============================================================================================ ============= =========== ============
15.05.2008 00:30:11 Job started 00 516 S
15.05.2008 00:30:11 Step 001 started (program RWP_RUNTIME_CACHE_RELOAD, variant SAP&RELOAD_ALL, user ID BGDUSER) 00 550 S
15.05.2008 00:30:11 No component system chosen URL_GEN_MSGS 031 E
15.05.2008 00:30:11 Job cancelled after system exception ERROR_MESSAGE 00 564 A
Please help to resolve this issue.
Thanks in advance.
Regards
Sudip GhoshHi Markus,
Thanks for the reply.
Below is the dump:
======
======
Runtime Errors DBIF_DSQL2_SQL_ERROR
Date and Time 15.05.2008 06:25:36
Short text
An SQL error occurred when executing Native SQL.
What happened?
The error 3113 occurred in the current database connection "DEFAULT".
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
How to correct the error
Database error text........: "ORA-03113: end-of-file on communication channel"
Database error code........: 3113
Triggering SQL statement...: "FETCH NEXT "
Internal call code.........: "[DBDS/NEW DSQL]"
Please check the entries in the system log (Transaction SM21).
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"DBIF_DSQL2_SQL_ERROR" " "
"RSORAVSH" or "RSORAVSH"
"FILL_DBVSE"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
System environment
SAP-Release 700
Application server... "gcbeccd"
Network address...... "10.10.4.158"
Operating system..... "HP-UX"
Release.............. "B.11.23"
Hardware type........ "ia64"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 15
Shortdump setting.... "full"
Database server... "gcbeccd"
Database type..... "ORACLE"
Database name..... "RD3"
Database user ID.. "SAPSR3"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Apr 5 2008 00:55:24"
create on........ "HP-UX B.11.23 U ia64"
Database version. "OCI_102 (10.2.0.1.0) "
Patch level. 146
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "HP-UX B.11"
Memory consumption
Roll.... 1117216
EM...... 0
Heap.... 0
Page.... 32768
MM Used. 695792
MM Free. 400816
User and Transaction
Client.............. 000
User................ "BGDUSER"
Language key........ "E"
Transaction......... " "
Transactions ID..... "482B8A4C89F0442BE10000000A0A049E"
Program............. "RSORAVSH"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
Termination occurred in the ABAP program "RSORAVSH" - in "FILL_DBVSE".
The main program was "RSORAVSH ".
In the source code you have the termination point in line 48
of the (Include) program "RSORAVSH".
The program "RSORAVSH" was started as a background job.
Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR"
Job Initiator.. "BGDUSER"
Job Number..... 05251100
Source Code Extract
Line
SourceCde
18
INCLUDE STRUCTURE v_system_event_struc.
19
DATA: END OF v_system_event_tab .
20
21
check sy-dbsys(3) = 'ORA' .
22
23
Get the new snapshots
24
25
PERFORM fill_dbvse TABLES v_system_event_tab.
26
27
28
Get the old snapshots from database table MONI
29
30
startday = sy-datum - days_to_keep .
31
32
33
Save new data now (otherwise these data will be selected twice)
34
35
CONCATENATE 'SYSEVENT' sy-datum sy-uzeit INTO monikey .
36
37
EXPORT sy-datum
38
sy-uzeit
39
v_system_event_tab
40
TO DATABASE moni(db) ID monikey .
41
42
*& Form FILL_DBVSE
43
44
FORM fill_dbvse TABLES v_system_event_tab.
45
date = sy-datum .
46
time = sy-uzeit .
47
EXEC sql performing append_v_system_event .
>>>>>
select event,
49
total_waits,
50
total_timeouts,
51
time_waited * 10,
52
average_wait * 10
53
into :v_system_event_struc
54
from v$system_event
55
ENDEXEC .
56
ENDFORM. " FILL_DBVSE
57
58
59
*& Form APPEND_V_SYSTEM_EVENT
60
61
FORM append_v_system_event.
62
v_system_event_tab-date = date .
63
v_system_event_tab-time = time .
64
65
MOVE-CORRESPONDING v_system_event_struc TO v_system_event_tab.
66
APPEND v_system_event_tab .
67
ENDFORM. " APPEND_V_SYSTEM_EVENT
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
0
SY-TABIX
16
SY-DBCNT
0
SY-FDPOS
0
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
SY-UCOMM
SY-TITLE
Report for Collecting Data from V$SYSTEM_EVENT Hourly
SY-MSGTY
SY-MSGID
SY-MSGNO
000
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO
0
SY-DATUM
20080515
SY-UZEIT
062520
SY-XPROG
RSDBRUNT
SY-XFORM
%_INIT_PBO_FIRST
Active Calls/Events
No. Ty. Program Include Line
Name
2 FORM RSORAVSH RSORAVSH 48
FILL_DBVSE
1 EVENT RSORAVSH RSORAVSH 25
START-OF-SELECTION
Chosen variables
Name
Val.
No. 2 Ty. FORM
Name FILL_DBVSE
SY-REPID
RSORAVSH
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5545455422222222222222222222222222222222
23F2163800000000000000000000000000000000
V_SYSTEM_EVENT_STRUC
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
22222222222222222222222222222222222222222222222222222222222222220000000000000000
0000000000000000000000000000000000000000000000000000000000000000000C000C000C000C
%_SPACE
0
0
2
0
SY
###############################################################################T######## ####
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000004000000
000000000000000000000000000000000000000100000000000000000000000000000000000000000000000D000400
000001000000000000000000000000000000000F000000000000000000000000000000000000010500000005220000
000000000000000000000000010001000000000E00000000000000000000000000000000000006040000000800000C
No. 1 Ty. EVENT
Name START-OF-SELECTION
SY-LDBPG
SAPDB__S
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5454455522222222222222222222222222222222
31042FF300000000000000000000000000000000
%_DUMMY$$
0000
0000
2222
0000
SY-DBSYS+0(6)
ORA
000
000
454
F21
SYST
###############################################################################T######## ####
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000004000000
000000000000000000000000000000000000000100000000000000000000000000000000000000000000000D000400
000001000000000000000000000000000000000F000000000000000000000000000000000000010500000005220000
000000000000000000000000010001000000000E00000000000000000000000000000000000006040000000800000C
V_SYSTEM_EVENT_TAB[]
Table[initial]
V_SYSTEM_EVENT_TAB
00000000000000 ################
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
3333333333333322222222222222222222222222222222222222222222222222222222222222220000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000000000000C000C000C000C
SY-DATUM
20080515
00000000
00000000
33333333
20080515
DAYS_TO_KEEP
30
0001
000E
STARTDAY
00000000
00000000
00000000
33333333
00000000
MONIKEY
0000000000000000000000
0000000000000000000000
2222222222222222222222
0000000000000000000000
SY-UZEIT
062520
000000
000000
333333
062520
SYST-REPID
RSORAVSH
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5545455422222222222222222222222222222222
23F2163800000000000000000000000000000000
MONI-CLUSTR
0
00
00
MONI
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222222222222220022000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Internal notes
The termination was triggered in function "ExecuteCall"
of the SAP kernel, in line 1190 of the module
"//bas/700_REL/src/krn/runt/abexsql.c#2".
The internal operation just processed is "DSQL".
Internal mode was started at 20080515062520.
Internal call code.........: "[DBDS/NEW DSQL]"
Active Calls in SAP Kernel
Lines of C Stack in Kernel (Structure Differs on Each Platform)
(0) 0x4000000003b2b450 CTrcStack + 0x1b0 at dptstack.c:227 [dw.sapRD3_DVEBMGS00]
(1) 0x4000000004d2c470 Z16rabaxCStackSavev + 0x1d0 [dw.sapRD3_DVEBMGS00]
(2) 0x4000000004d32160 ab_rabax + 0x3570 [dw.sapRD3_DVEBMGS00]
(3) 0x40000000047b51e0 Z10abdbdserriPKtiS0_P9DS_HEADERS0_iPv + 0x470 [dw.sapRD3_DVEBMGS00]
(4) 0x4000000003d777f0 Z11ExecuteCallv + 0x11f0 [dw.sapRD3DVEBMGS00]
(5) 0x4000000003d7e7b0 Z8abjdsqlv + 0x1b0 [dw.sapRD3_DVEBMGS00]
(6) 0x400000000402f190 Z8abextriv + 0x440 [dw.sapRD3_DVEBMGS00]
(7) 0x4000000003f53bc0 Z9abxeventPKt + 0x3c0 at abrunt1.c:339 [dw.sapRD3_DVEBMGS00]
(8) 0x4000000003d9f210 Z8abtriggv + 0x110 at abrunt1.c:58 [dw.sapRD3_DVEBMGS00]
(9) 0x4000000003d9ebe0 ab_run + 0xc0 [dw.sapRD3_DVEBMGS00]
(10) 0x4000000001caa820 N_ab_run + 0x20 at dymainstp.c:4739 [dw.sapRD3_DVEBMGS00]
(11) 0x4000000001cb40f0 dynpmcal + 0x3f0 at dymainstp.c:2281 [dw.sapRD3_DVEBMGS00]
(12) 0x4000000001caf260 dynppai0 + 0xcb0 at dymainstp.c:1107 [dw.sapRD3_DVEBMGS00]
(13) 0x4000000001cb1ec0 dynprctl + 0x340 at dymainstp.c:358 [dw.sapRD3_DVEBMGS00]
(14) 0x4000000001c9dff0 dynpen00 + 0xac0 at dymain.c:1628 [dw.sapRD3_DVEBMGS00]
(15) 0x4000000001fea460 Thdynpen00 + 0x510 at thxxhead.c:4830 [dw.sapRD3_DVEBMGS00]
(16) 0x4000000001fb54e0 TskhLoop + 0x5520 at thxxhead.c:3945 [dw.sapRD3_DVEBMGS00]
(17) 0x4000000001faae40 ThStart + 0x460 at thxxhead.c:1164 [dw.sapRD3_DVEBMGS00]
(18) 0x4000000001569ec0 DpMain + 0x5f0 at dpxxdisp.c:1088 [dw.sapRD3_DVEBMGS00]
(19) 0x4000000002c10630 nlsui_main + 0x30 [dw.sapRD3_DVEBMGS00]
(20) 0x4000000002c105c0 main + 0x60 [dw.sapRD3_DVEBMGS00]
(21) 0xc00000000002be30 main_opd_entry + 0x50 [/usr/lib/hpux64/dld.so]
List of ABAP programs affected
Index
Typ
Program
Group
Date
Time
Size
Lang.
0
Prg
RSORAVSH
0
30.03.2005
10:21:59
19456
E
1
Prg
SAPMSSY0
1
17.12.2007
15:41:05
92160
E
2
Prg
SAPMSSYD
1
12.09.2006
11:33:31
21504
E
3
Prg
SAPFSYSCALLS
1
09.09.2004
14:18:32
8192
E
4
Prg
RSDBRUNT
0
17.12.2007
16:04:40
254976
E
5
Typ
RSSCR
0
30.03.2005
10:21:45
5120
6
Prg
RSDBSPBL
0
30.03.2005
10:21:58
72704
E
7
Prg
SAPDB__S
0
30.03.2005
10:22:01
19456
E
8
Prg
RSDBSPMC
0
12.09.2006
11:25:01
79872
E
9
Typ
DDSHDESCR
0
03.09.1997
03:05:16
4096
10
Typ
SPPARAMS
0
07.05.1997
13:10:38
2048
11
Prg
SAPLSABE
11
09.09.2004
14:18:36
13312
E
12
Prg
SAPLSECU
12
17.12.2007
15:31:45
87040
E
13
Typ
RSSUBINFO
0
14.10.1999
22:01:03
3072
14
Prg
SAPLSTUP
14
17.12.2007
15:29:58
74752
E
15
Prg
SAPLCNDP
15
11.09.2007
15:24:45
195584
E
16
Prg
SAPLSCNT
16
18.02.2005
14:16:06
30720
E
17
Prg
SAPSHDTV
16
05.01.2005
16:26:16
33792
E
18
Prg
SAPFGUICNTL
1
18.02.2005
14:15:08
24576
E
19
Prg
SAPLOLEA
19
11.09.2007
11:17:30
96256
E
20
Prg
SAPLSGUI
20
17.12.2007
15:41:05
84992
E
21
Prg
SAPLSTTM
21
05.07.2005
13:10:18
69632
E
22
Prg
SAPLSBDC
22
17.12.2007
15:30:54
44032
E
23
Prg
SAPLSFES
23
17.12.2007
16:04:40
260096
E
24
Prg
SAPLTHFB
24
17.12.2007
15:41:05
394240
E
25
Typ
WPINFO
0
26.02.1999
14:49:01
6144
26
Prg
SAPLURFC
26
17.12.2007
15:37:35
22528
E
27
Prg
SAPLSPLUGIN
27
09.09.2004
14:18:36
8192
E
28
Typ
SWCBCONT
0
15.11.2000
17:55:11
3072
29
Typ
OLE_VERBS
0
04.04.1995
16:02:20
2048
30
Typ
OLE_PA
0
04.04.1995
16:02:19
2048
31
Typ
SYST
0
09.09.2004
14:18:12
31744
32
Typ
MONI
0
31.03.2004
16:41:21
5120
Directory of Application Tables
Name Date Time Lngth
Val.
Program RSORAVSH
SYST 09.09.2004 14:18:12 00004612
\0\0\0\0\0\x0010\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0
MONI . . : : 00002944
\0\0 \0\0\0\0\0\0\0\0\0\0\0\0\0\0
ABAP Control Blocks (CONT)
Index
Name
Fl
PAR0
PAR1
PAR2
PAR3
PAR4
PAR5
PAR6
Source Code
Line
71
PAR2
03
0000
0014
002B
RSORAVSH
37
73
PAR2
03
0000
0015
002D
RSORAVSH
37
75
PAR2
03
0000
0016
0026
RSORAVSH
37
77
00
0000
RSORAVSH
37
78
PERP
00
0002
RSORAVSH
44
79
PERP
1C
0000
RSORAVSH
44
80
PERP
04
0000
RSORAVSH
44
81
mvqk
10
0005
0044
04EC
RSORAVSH
45
83
mvqk
0C
0005
0054
052E
RSORAVSH
46
85
DSQL
00
0017
RSORAVSH
48
86
DSQL
01
0018
RSORAVSH
48
87
DSQL
04
0025
RSORAVSH
48
>>>>>
DSQL
16
0025
RSORAVSH
48
89
BRAN
05
0004
RSORAVSH
48
90
perf
00
000A
RSORAVSH
48
91
PERP
80
0000
RSORAVSH
48
92
BRAX
00
FFFC
RSORAVSH
48
93
DSQL
23
0000
RSORAVSH
48
94
ENDF
00
0000
RSORAVSH
56
95
00
0000
RSORAVSH
56
===========
===========
Please check and advise.
Also, I am trying to search for the note 6083 in market place, but not getting the same.
Please advise.
Thanks & Regards
Sudip -
ORA-00600: internal error code, arguments: [17119]
Hi Techies,
I've got a lot of ORA-00600: internal error code, arguments: [17119] showing in my alertlogs and trace files. Users were unable log on, sunsequently the database crashed.
has anyone come accross such events and how was it solved? There are no activities that I can pin point to the time of occurance.
Extract of the trace file is as follows:
*** SERVICE NAME:(SYS$BACKGROUND) 2009-09-10 15:14:56.386
*** SESSION ID:(293.34537) 2009-09-10 15:14:56.386
********** Internal heap ERROR 17119 addr=(nil) *********
HEAP DUMP heap name="" desc=0x2112183f0
extent sz=0x11218990 alt=19392 het=0 rec=0 flg=0 opc=0
parent=0x25eac5898 owner=0x2112182f8 nex=(nil) xsz=0x0
Hla: 1
*** 2009-09-10 15:14:56.386
ksedmp: internal or fatal error
ORA-00600: internal error code, arguments: [17119], [0x000000000], [], [], [], [], [], []
No current SQL statement being executed.
----- Call Stack Trace -----
calling call entry argument values in hex
location type point (? means dubious value)
ksedst()+31 call ksedst1() 000000000 ? 000000001 ?
7FBFFF8430 ? 7FBFFF8490 ?
7FBFFF83D0 ? 000000000 ?
ksedmp()+610 call ksedst() 000000000 ? 000000001 ?
7FBFFF8430 ? 7FBFFF8490 ?
7FBFFF83D0 ? 000000000 ?
ksfdmp()+21 call ksedmp() 000000003 ? 000000001 ?
7FBFFF8430 ? 7FBFFF8490 ?
7FBFFF83D0 ? 000000000 ?
kgeriv()+176 call ksfdmp() 000000003 ? 000000001 ?
7FBFFF8430 ? 7FBFFF8490 ?
7FBFFF83D0 ? 000000000 ?
kgesiv()+119 call kgeriv() 006618F40 ? 006680C70 ?
000000000 ? 000000000 ?
7FBFFF83D0 ? 000000000 ?
kgesic1()+155 call kgesiv() 006618F40 ? 006680C70 ?
0000042DF ? 000000001 ?
7FBFFF91B0 ? 000000000 ?
kgherror()+986 call kgesic1() 006618F40 ? 006680C70 ?
0000042DF ? 000000002 ?
000000000 ? 000000001 ?
kghpih()+106 call kgherror() 006618F40 ? 2112183F0 ?
0000042DF ? 000000000 ?
000000000 ? 000000000 ?
kghfex()+49 call kghpih() 006618F40 ? 2112183F0 ?
000000001 ? 000000000 ?
000000000 ? 000000000 ?
kghfrx()+42 call kghfex() 006618F40 ? 2112183F0 ?
000000001 ? 000000000 ?
000000000 ? 000000000 ?
kghfrunp()+2456 call kghfrx() 006618F40 ? 2112183F0 ?
000000001 ? 000000000 ?
000000000 ? 000000000 ?
kghfnd()+1042 call kghfrunp() 006618F40 ? 06003C460 ?
000001000 ? 06003DB50 ?
06003DCB8 ? 000000000 ?
kghalo()+587 call kghfnd() 006618F40 ? 000000018 ?
06003C460 ? 0600222E0 ?
000001000 ? 000000000 ?
kghgex()+598 call kghalo() 000000000 ? 06003C460 ?
000000FE8 ? 000000FE8 ?
000001000 ? 000001000 ?
kghfnd()+667 call kghgex() 006618F40 ? 000000000 ?
25DAA9998 ? 000002000 ?
25DAA99E4 ? 000000000 ?
kghalo()+587 call kghfnd() 006618F40 ? 000000000 ?
25DAA9998 ? 000000FD8 ?
2A00000FD8 ? 000000000 ?
kghgex()+598 call kghalo() 000000000 ? 25DAA9998 ?
000000FA8 ? 000000FA8 ?
000000FD8 ? 000000FD8 ?
kghalf()+521 call kghgex() 006618F40 ? 000000000 ?
17A7A79B0 ? 000003000 ?
17A7A79FC ? 000000000 ?
kghalp()+3013 call kghalf() 006618F40 ? 17A7A79B0 ?
000000038 ? 000000001 ?
000000000 ? 0059A9404 ?
qcsAddSqlPath()+107 call kghalp() 006618F40 ? 17A7A79B0 ?
Any helps would be grately appreciative.
Kind Regards
Newbie..Go to metalink and use the ORA-600 lookup table, if nothing help, then open a SR to get help from Oracle support.
Nicolas. -
ORA-00600: Internal error code, arguments [17034],
Anybody know what is this error:
ORA-00600: Internal error code, arguments [17034],
[812574084], [0], [], [], [], [], []
Thanks.1) My RDBMS version is 8.0.4
My OS version is AIX 4.3.2
My forms developer version is 5.0.6.8.0
2) The error has been ocurred about 5 times every day.
3) The session wasn4t kill.
4) Yes, there are many statements, and they are diferent.
5) Yes, the statements are the same in each trace file.
ERROR BACKGROUND
1) The application was develop with forms developer 5.0.6.8.0 and the RDBMS version was 8.0.5 on OS Win NT 4.0.
2) After that, i made an full export of data base.
3) Next, on AIX, i made an import of all data of 2.).
Now, i see that the application don44t work very well.
I send some part os trace file.
I will appreciate your help.
Thanks thomas. -
Compiling error ORA-00600 with Forms 6 and Database 10g
Hi,
I am using "Oracle Database 10g Enterprise Edition Release 10.1.0.4.0" and "Forms [32 Bit] Version 6.0.8.26.0 " with patch 17, when i compile a form that works with some tables in another database under dblink the error ORA-00600:internal error code, arguments:[16203],[],[],[],[],[],[],[] is displayed.
If i word with reports or sqlplus no error is displayed.
Before we installed 10g everything worked ok
What is wrong with forms or do i need to configure something else?
Regards
Yuri V. López ManriqueI searched for this error on Google and found the following blog:
Is there a tool to troubleshoot ORA-00600 and ORA-07445 errors?
February 27th, 2006 By Fahd Mirza
ORA-00600 and ORA-07445 errors are the most esoteric errors in Oracle.
There is a tool called ORA-600/ORA-7445 Troubleshooter available at Metalink. It asks for the first argument of ORA-600 error with an optional database version number.
For example, to see the description of the error:
ORA-00600: internal error code, arguments: [723], [25908], [25908], [memory leak]
You enter 723 in the ORA-600 First Argument field. The first argument is a pointer to where in the code the error was caught and thus is the key information in identifying the problem.
You can also embed (copy/paste) the Call Stack Trace there, and, when you click on the Search Call Stack button an advanced MetaLink search is performed to find documents containing relevant sections from the call stack.
Call Stack extracts from the following files are supported:
* Generic foreground and background server trace files located in background_dump_dest and user_dump_dest
* OpenVMS NETV2 and BEQ log files located in ORA_ROOT:[NETWORK.LOG]
* WINDOWS CORE.LOG files
* GDB (debugger) backtrace call stacks (best endeavors)
Of course you will need a login to Oracle's Metalink site.
Hope that helps,
c -
How to run a background job with the cloud_scheduler package
Hi,
Is the cloud_scheduler package able to run background jobs as documented? When you try to run a job in another session using:
cloud_scheduler.run_job(job_name=>'MYJOB', use_current_session=>false);
The call fails with:
ORA-20002: Cannot run job MYJOB. Adhoc background execution is disallowed. Please enable the job instead.
If you try to use cloud_scheduler.enable to run the job then the job does not run when scheduled.
Rod WestHi Rod,
Yes, I believe so. Here's a test case that I just ran successfully from SQL Workshop in my database trial service:
create table myjob_test (aa timestamp with time zone);
begin
cloud_scheduler.create_job (
job_name => 'MYJOB',
job_type => 'PLSQL_BLOCK',
job_action => 'begin insert into myjob_test values (systimestamp); commit; end;',
repeat_interval => 'freq=minutely; interval=3' );
end;
begin
cloud_scheduler.enable ( name => 'MYJOB' );
end;
select job_name, state, run_count, failure_count, last_start_date, next_run_date, systimestamp from sys.user_scheduler_jobs;
select * from myjob_test order by aa;Is the next_run_date in the past for your job? If it is, try disabling/enabling the job to "reinitialize" the job's schedule.
-- Vlad -
ORA-00600: internal error code
In my alert log file I receive this error:
Errors in file E:\oracle\admin\mofrees1\bdump\mofrees1_m000_336.trc:
ORA-00600: internal error code, arguments: [6002], [6], [0], [4], [0], [], [], []
Some content of trace file is:
*** ACTION NAME:(Auto-Flush Slave Action) 2009-05-28 11:00:53.120
*** MODULE NAME:(MMON_SLAVE) 2009-05-28 11:00:53.120
*** SERVICE NAME:(SYS$BACKGROUND) 2009-05-28 11:00:53.120
*** SESSION ID:(155.1490) 2009-05-28 11:00:53.120
*** 2009-05-28 11:00:53.120
ksedmp: internal or fatal error
ORA-00600: internal error code, arguments: [6002], [6], [0], [4], [0], [], [], []
Current SQL statement for this session:
insert into wrh$_latch (snap_id, dbid, instance_number, latch_hash, level#, gets, misses, sleeps, immediate_gets, immediate_misses, spin_gets, sleep1, sleep2, sleep3, sleep4, wait_time) select :snap_id, :dbid, :instance_number, hash, level#, gets, misses, sleeps, immediate_gets, immediate_misses, spin_gets, sleep1, sleep2, sleep3, sleep4, wait_time from v$latch order by hash
----- Call Stack Trace -----
calling call entry argument values in hex
location type point (? means dubious value)
.ksedst+112 UNK .ksedst1+416
.ksedmp+1728 UNK .ksedst+112
.ksfdmp+48 UNK .ksedmp+1728
.kgeriv+448 UNK .ksfdmp+48
.kgeasi+688 UNK .kgeriv+448
.kdiins0??cold+7987 UNK .kgeasi+688
2
.kauxsin??hot+7312 UNK .kdiins0??cold+7987
2
.insidx+16304 UNK .kauxsin??hot+7312
.insflush+5824 UNK .insidx+16304
.insrow+5632 UNK .insflush+5824
.insdrv+15376 UNK .insrow+5632
.inscovexe+5024 UNK .insdrv+15376
.insExecStmtExecIni UNK .inscovexe+5024
Engine+848
.insexe+5936 UNK .insExecStmtExecIni
Engine+848
.opiexe??hot+21312 UNK .insexe+5936
.kpoal8??hot+5568 UNK .opiexe??hot+21312
.opiodr??hot+3104 UNK .kpoal8??hot+5568
.kpoodrc+64 UNK .opiodr??hot+3104
.rpiswu2??hot+2256 UNK .kpoodrc+64
.kpoodr??hot+1744 UNK .rpiswu2??hot+2256
.xupirtrc??hot+2560 UNK .kpoodr??hot+1744
.upirtrc??hot+208 UNK .xupirtrc??hot+2560
.kpurcsc??hot+256 UNK .upirtrc??hot+208
.kpuexecv8??hot+283 UNK .kpurcsc??hot+256
2
.kpuexec??hot+3072 UNK .kpuexecv8??hot+283
2
.OCIStmtExecute+96 UNK .kpuexec??hot+3072
.kewrose_oci_stmt_e UNK .OCIStmtExecute+96
xec+112
.kewrgwxf1_gwrsql_e UNK .kewrose_oci_stmt_e
xft_1??hot+592 xec+112
.kewrgwxf_gwrsql_ex UNK .kewrgwxf1_gwrsql_e
ft+1472 xft_1??hot+592
.kewrews_execute_wr UNK .kewrgwxf_gwrsql_ex
_sql+112 ft+1472
.kewrftbs_flush_tab UNK .kewrews_execute_wr
le_by_sql??hot+352 _sql+112
.kewrft_flush_table UNK .kewrftbs_flush_tab
+464 le_by_sql??hot+352
.kewrftec_flush_tab UNK .kewrft_flush_table
le_ehdlcx+2064 +464
.kewrfat_flush_all_ UNK .kewrftec_flush_tab
tables+2480 le_ehdlcx+2064
.kewrfos_flush_ones UNK .kewrfat_flush_all_
nap+496 tables+2480
.kewrfsc_flush_snap UNK .kewrfos_flush_ones
shot_c+704 nap+496
.kewrafs_auto_flush UNK .kewrfsc_flush_snap
slave+1888 shotc+704
.kebm_slave_main??h UNK .kewrafs_auto_flush
ot+400 _slave+1888
.ksvrdp??hot+2720 UNK .kebm_slave_main??h
ot+400
.opirip??hot+2192 UNK .ksvrdp??hot+2720
.opidrv??hot+1696 UNK .opirip??hot+2192
.sou2o+96 UNK .opidrv??hot+1696
.opimai_real??hot+6 UNK .sou2o+96
56
.opimai??hot+224 UNK .opimai_real??hot+6
56
.BackgroundThreadSt UNK .opimai??hot+224
art+3168
0000000076EA7600 UNK .BackgroundThreadSt
art+3168
My DB work in archive log mode.
How can I fix this error?suadhm wrote:
My DB is : ORACLE V10.2.0.1.0 - 64bit
OS is: Windows 2003 Server.
But I think that is no matter. My DB was working almost 3 year now.This information does matter as Oracle internal error codes have different meanings in different versions.
I started to receive this error in alert log file at May 28.
Refer metalink note 47449.1 for this problem. -
hi,
i have Oracle 11G on linux enterprise rhel 5
i was runing a delete statement on a table and stopped it because it was taking too much time. after that i saw that the oracle instance was down.
i starteed it up and after some minutes it is going down again.
i even restarted the server and after reboot again down.
in the logs files it is show the following msg:
<attr name='IMPACT' value='POSSIBLE ROLLBACK SEGMENT CORRUPTION'/>
Errors in file /oracle/app/oracle/diag/rdbms/xxx/xxx/trace/xxx_smon_14333.trc (incident=74606):
ORA-00600: internal error code, arguments: [4142], [1835348594], [], [], [], [], [], [], [], [], [], []
and in the trace file
Trace file /oracle/app/oracle/diag/rdbms/xxx/xxx/trace/xxx_smon_14333.trc
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
ORACLE_HOME = /oracle/app/oracle/product/11.1.0/db_1
System name: Linux
Node name: xxx
Release: 2.6.18-128.el5
Version: #1 SMP Wed Jan 21 08:45:05 EST 2009
Machine: x86_64
Instance name: xxx
Redo thread mounted by this instance: 1
Oracle process number: 13
Unix process pid: 14333, image: oracle@xxx (SMON)
*** 2010-11-29 18:35:05.955
*** SESSION ID:(323.1) 2010-11-29 18:35:05.955
*** CLIENT ID:() 2010-11-29 18:35:05.955
*** SERVICE NAME:(SYS$BACKGROUND) 2010-11-29 18:35:05.955
*** MODULE NAME:() 2010-11-29 18:35:05.955
*** ACTION NAME:() 2010-11-29 18:35:05.955
Incident 74601 created, dump file: /oracle/app/oracle/diag/rdbms/xxx/xxx/incident/incdir_74601/xxx_smon_14333_i74601.trc
ORA-00600: internal error code, arguments: [25027], [2], [458753], [], [], [], [], [], [], [], [], []
Parallel Transaction recovery caught exception 12801
Parallel Transaction recovery caught error 600
SMON: Parallel transaction recovery slave got internal error
SMON: Downgrading transaction recovery to serial
KTUNDO: cannot find ts$ entry
SGAFRCWT: 4194304ORA-00600: internal error code, arguments: [4142], [1835348594], [], [], [], [], [], [], [], [], [], []ORA-00600/ORA-07445/ORA-03113 = Oracle bug => search on Metalink and/or call Oracle support
-
ORA-00600: Internal Error when running XSQl Script
Hi,
when running a xsql script with JDeveloper 3.1
the following message appears:
<?xml version="1.0" ?>
- <!-- IRON.xsql Return the results of a table
-->
- <xsql-error action="xsql:query">
<statement>select ename,job,sal from emp where
ename='ALLEN'</statement>
<message>ORA-00600: Interner Fehlercode, Argumente: [ttcgcshnd-
1], [0], [], [], [], [], [], []</message>
</xsql-error>
Does anybody knows, what's wrong ?
Regards
Andylooks like bug #1725012, fixed in either 9.0.1 or 8.1.7.2
(these are RDBMS versions).
Maybe you are looking for
-
Missing Email Accounts in ~/Library/Mail
I just got my iPhone an tried to sync with my Mail accounts but only a very old POP mail account (no longer in use) showed up on my iPhone. I checked on my computer and none of my current POP email accounts from Mail show up in ~/Library/Mail folder.
-
Query in AP Invoice and AP Downpayment Invoice
Hi Expert, I'm using the following query to generate report from AP Invoice by due date: SELECT T0.[CardCode] as 'Payee Code', T0.[TransId] as 'JE Number', T0.[CardName] as 'Payee Name', T0.[DocDueDate], T0.[DocTotal] as 'Amount Due', T1.[U_DisBank]
-
Switching presentations mid presentation
Hello all -- i'm trying to run 4 slides in a 10 minute loop before the main presentation and am wondering if there is anyway to do this within keynote. I'm trying to avoid the desktop picture when swapping from the initial presentation to the actual
-
I HAVE PURCHASED DDL PACK BUT CANNOT DOWLOAD IT???? URGENT AND VERY AN
Are you guys trying to cheat my money? I have painstakingly decided to?Purchase YOUR Dolby Digital Li've pack for my X-Fi card. After making a COMPLETE Transatction and receiving the activation key, I click download but NO I END UP WITH A DEAD LINK.
-
In GL Master- Diff between Open Item & Balance Summary
Hi Experts In GL Master- Diff between Open Item & Balance Summary ? Regards Ramakanth