Unable to start instance after SMON terminates instance
This is a discussion on Unable to start instance after SMON terminates instance within the Oracle Database forums, part of the Database Server Software category; --> Hi, was doing an import into a table in an Oracle 8.1.5.0.0. on HP/UX. gave a recursive sql error ...
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
02-24-2008, 07:15 AM
| ||||
| ||||
 Unable to start instance after SMON terminates instance Hi, was doing an import into a table in an Oracle 8.1.5.0.0. on HP/UX. gave a recursive sql error (ORA-00604: error occurred at recursive SQL level 1). Aborted the import using ^C. Since then Oracle starts up but reports internal error 600 and SMON terminates the instance. Any help would be greatly appreciated. This is very urgent! Part of the alert log is reporduced here (ignore the date stamp- its not in sync with the actual date) ------------------------- Wed Aug 18 04:59:28 2004 Errors in file /usr5/oracle/app/oracle/admin/ETOBC/bdump/p000_15039.trc: ORA-00600: internal error code, arguments: [ktsf_rsp2], [17455], [17458], [], [], [], [], [] Wed Aug 18 04:59:28 2004 Errors in file /usr5/oracle/app/oracle/admin/ETOBC/udump/ora_15071.trc: ORA-00600: internal error code, arguments: [2023], [5], [1], [], [], [], [], [] ORA-00604: error occurred at recursive SQL level 1 ORA-01013: user requested cancel of current operation Wed Aug 18 04:59:32 2004 SMON: terminating instance due to error 600 Instance terminated by SMON, pid = 1085 Wed Aug 18 05:04:30 2004 Starting ORACLE instance (normal) LICENSE_MAX_SESSION = 0 LICENSE_SESSIONS_WARNING = 0 LICENSE_MAX_USERS = 0 Starting up ORACLE RDBMS Version: 8.1.5.0.0. System parameters with non-default values: processes = 700 sessions = 775 shared_pool_size = 104857600 large_pool_size = 5242880 java_pool_size = 4194304 enqueue_resources = 4000 control_files = /usr3/oradata/ETOBC/control01.ctl, /usr4/oradata/ETOBC/control02.ctl db_block_buffers = 40960 db_block_size = 4096 compatible = 8.1.5 log_buffer = 163840 log_checkpoint_interval = 10000 log_checkpoint_timeout = 0 db_files = 40 dml_locks = 3000 transactions = 500 rollback_segments = rbs0, rbs1, rbs2, rbs3, rbs4, rbs5, rbs6, rbs7, rbs8, rbs9, rbs10, rbs11, rbs12, rbs13, rbs14, rbs15, rbs16, rbs17, rbs18, rbs19, rbs20 transaction_auditing = FALSE remote_login_passwordfile= EXCLUSIVE distributed_transactions = 250 service_names = ETOBC instance_name = ETOBC sort_area_size = 131072 sort_area_retained_size = 131072 db_name = ETOBC open_cursors = 600 os_authent_prefix = ops$ optimizer_mode = FIRST_ROWS query_rewrite_enabled = TRUE query_rewrite_integrity = TRUSTED hash_join_enabled = TRUE hash_area_size = 20971520 hash_multiblock_io_count = 8 background_dump_dest = /usr5/oracle/app/oracle/admin/ETOBC/bdump user_dump_dest = /usr5/oracle/app/oracle/admin/ETOBC/udump max_dump_file_size = 10000 core_dump_dest = /usr5/oracle/app/oracle/admin/ETOBC/cdump PMON started with pid=2 DBW0 started with pid=3 CKPT started with pid=5 LGWR started with pid=4 SMON started with pid=6 RECO started with pid=7 Wed Aug 18 05:04:32 2004 alter database mount Wed Aug 18 05:04:36 2004 Successful mount of redo thread 1, with mount id 438396836. Wed Aug 18 05:04:36 2004 Database mounted in Exclusive Mode. Completed: alter database mount Wed Aug 18 05:04:36 2004 alter database open Beginning crash recovery of 1 threads Wed Aug 18 05:04:37 2004 Thread recovery: start rolling forward thread 1 Recovery of Online Redo Log: Thread 1 Group 1 Seq 3970 Reading mem 0 Mem# 0 errs 0: /usr2/oradata/ETOBC/redo01.log Recovery of Online Redo Log: Thread 1 Group 2 Seq 3971 Reading mem 0 Mem# 0 errs 0: /usr1/oradata/ETOBC/redo03.log Wed Aug 18 05:05:02 2004 Thread recovery: finish rolling forward thread 1 Thread recovery: 11308 blocks read, 1749 blocks written Crash recovery completed successfully Picked broadcast on commit scheme to generate SCNs Wed Aug 18 05:05:03 2004 Thread 1 advanced to log sequence 3972 Thread 1 opened at log sequence 3972 Current log# 3 seq# 3972 mem# 0: /usr4/oradata/ETOBC/redo02.log Successful open of redo thread 1. Wed Aug 18 05:05:03 2004 SMON: enabling cache recovery SMON: enabling tx recovery Wed Aug 18 05:05:05 2004 Errors in file /usr5/oracle/app/oracle/admin/ETOBC/bdump/smon_15453.trc: ORA-00600: internal error code, arguments: [2023], [5], [1], [], [], [], [], [] Wed Aug 18 05:05:06 2004 Errors in file /usr5/oracle/app/oracle/admin/ETOBC/bdump/p000_15568.trc: ORA-00600: internal error code, arguments: [ktsf_rsp2], [17455], [17458], [], [], [], [], [] Wed Aug 18 05:05:06 2004 Completed: alter database open Wed Aug 18 05:05:11 2004 ORACLE Instance ETOBC (pid = 6) - Error 600 encountered while recovering transaction (20, 13) on object 12255. Wed Aug 18 05:05:11 2004 Errors in file /usr5/oracle/app/oracle/admin/ETOBC/bdump/smon_15453.trc: ORA-00600: internal error code, arguments: [2023], [5], [1], [], [], [], [], [] SMON: terminating instance due to error 600 Wed Aug 18 05:05:14 2004 Errors in file /usr5/oracle/app/oracle/admin/ETOBC/bdump/p000_15568.trc: ORA-00600: internal error code, arguments: [15784], [600], [], [], [], [], [], [] ORA-00600: internal error code, arguments: [], [], [], [], [], [], [], [] Instance terminated by SMON, pid = 15453 Wed Aug 18 05:14:21 2004 Starting ORACLE instance (normal) LICENSE_MAX_SESSION = 0 LICENSE_SESSIONS_WARNING = 0 LICENSE_MAX_USERS = 0 Starting up ORACLE RDBMS Version: 8.1.5.0.0. System parameters with non-default values: processes = 700 sessions = 775 shared_pool_size = 104857600 large_pool_size = 5242880 java_pool_size = 4194304 enqueue_resources = 4000 control_files = /usr3/oradata/ETOBC/control01.ctl, /usr4/oradata/ETOBC/control02.ctl db_block_buffers = 40960 db_block_size = 4096 compatible = 8.1.5 log_buffer = 163840 log_checkpoint_interval = 10000 log_checkpoint_timeout = 0 db_files = 40 dml_locks = 3000 transactions = 500 rollback_segments = rbs0, rbs1, rbs2, rbs3, rbs4, rbs5, rbs6, rbs7, rbs8, rbs9, rbs10, rbs11, rbs12, rbs13, rbs14, rbs15, rbs16, rbs17, rbs18, rbs19, rbs20 transaction_auditing = FALSE remote_login_passwordfile= EXCLUSIVE distributed_transactions = 250 service_names = ETOBC instance_name = ETOBC sort_area_size = 131072 sort_area_retained_size = 131072 db_name = ETOBC open_cursors = 600 os_authent_prefix = ops$ optimizer_mode = FIRST_ROWS query_rewrite_enabled = TRUE query_rewrite_integrity = TRUSTED hash_join_enabled = TRUE hash_area_size = 20971520 hash_multiblock_io_count = 8 background_dump_dest = /usr5/oracle/app/oracle/admin/ETOBC/bdump user_dump_dest = /usr5/oracle/app/oracle/admin/ETOBC/udump max_dump_file_size = 10000 core_dump_dest = /usr5/oracle/app/oracle/admin/ETOBC/cdump PMON started with pid=2 DBW0 started with pid=3 LGWR started with pid=4 CKPT started with pid=5 SMON started with pid=6 RECO started with pid=7 Wed Aug 18 05:14:25 2004 alter database mount Wed Aug 18 05:14:29 2004 Successful mount of redo thread 1, with mount id 438379253. Wed Aug 18 05:14:29 2004 Database mounted in Exclusive Mode. Completed: alter database mount Wed Aug 18 05:14:29 2004 alter database open Beginning crash recovery of 1 threads Wed Aug 18 05:14:30 2004 Thread recovery: start rolling forward thread 1 Recovery of Online Redo Log: Thread 1 Group 3 Seq 3972 Reading mem 0 Mem# 0 errs 0: /usr4/oradata/ETOBC/redo02.log Wed Aug 18 05:14:32 2004 Thread recovery: finish rolling forward thread 1 Thread recovery: 43 blocks read, 43 blocks written Crash recovery completed successfully Picked broadcast on commit scheme to generate SCNs Wed Aug 18 05:14:32 2004 Thread 1 advanced to log sequence 3973 Thread 1 opened at log sequence 3973 Current log# 1 seq# 3973 mem# 0: /usr2/oradata/ETOBC/redo01.log Successful open of redo thread 1. Wed Aug 18 05:14:33 2004 SMON: enabling cache recovery SMON: enabling tx recovery Wed Aug 18 05:14:35 2004 Errors in file /usr5/oracle/app/oracle/admin/ETOBC/bdump/smon_1067.trc: ORA-00600: internal error code, arguments: [2023], [5], [1], [], [], [], [], [] Wed Aug 18 05:14:35 2004 Completed: alter database open Wed Aug 18 05:14:36 2004 Errors in file /usr5/oracle/app/oracle/admin/ETOBC/bdump/p000_1071.trc: ORA-00600: internal error code, arguments: [ktsf_rsp2], [17455], [17458], [], [], [], [], [] Wed Aug 18 05:14:39 2004 ORACLE Instance ETOBC (pid = 6) - Error 600 encountered while recovering transaction (20, 13) on object 12255. Wed Aug 18 05:14:39 2004 Errors in file /usr5/oracle/app/oracle/admin/ETOBC/bdump/smon_1067.trc: ORA-00600: internal error code, arguments: [2023], [5], [1], [], [], [], [], [] SMON: terminating instance due to error 600 Instance terminated by SMON, pid = 1067 ----------------------------- Thaks in advance      |
|
02-24-2008, 07:15 AM
| |||
| |||
| Re: Unable to start instance after SMON terminates instance On 4 Sep 2004 03:18:17 -0700, shailendra.mathur@tcs.com (Shailendra Mathur) wrote: >Since then Oracle starts up but >reports internal error 600 and SMON terminates the instance. Any help >would be greatly appreciated. This is very urgent! If it's urgent, you should - adress this with OTS (which you should do anyway, as only OTS can resolve ora-600s) - stop running a version that was desupported several years ago. -- Sybrand Bakker, Senior Oracle DBA |
|
02-24-2008, 07:16 AM
| ||||
| ||||
| Re: Unable to start instance after SMON terminates instance On Sat, 04 Sep 2004 03:18:17 -0700, Shailendra Mathur wrote: > Hi, > > was doing an import into a table in an Oracle 8.1.5.0.0. on HP/UX. > gave a recursive sql error (ORA-00604: error occurred at recursive SQL > level 1). Aborted the import using ^C. Since then Oracle starts up but > reports internal error 600 and SMON terminates the instance. Any help > would be greatly appreciated. This is very urgent! You should call oracle support. Here is something that I was able to find on Metalink: Problem statement: KILLING PROCESS DURING TRUNCATE CAUSES ORA-600[2023][5][1]. Hdr: 1537309 8.1.5.0 RDBMS 8.1.5.0 PRODID-5 PORTID-2 ORA-600 1400739 Abstract: KILLING PROCESS DURING TRUNCATE CAUSES ORA-600[2023][5][1]. *** 12/10/00 06:36 pm *** ========================= ========================= PROBLEM: Killing the process(i.e CTL-C) while truncating the partition table that has 80000 extents caused ORA-600[2023][5][1] and the instance went down. After that, DB cannot be started up due to the same error ORA-600[2023]. There is also another bug that can be connected to your situation: Problem statement: ORA-600 [6856] + ORA-600 [KTSF_RSP2] Hdr: 1186884 8.1.6.0.0 RDBMS 8.1.6.0.0 PRODID-5 PORTID-2 ORA-600 Abstract: ORA-600 [6856] + ORA-600 [KTSF_RSP2] *** 02/08/00 06:33 am *** PROBLEM: .. Several times each day server processes crash with either ORA-600 [6856] or ORA-600 [ktsf_rsp2]. The errors are seen in both test and production systems. Originally we got the problem on 8.1.5 so we upgraded the test-system to 8.1.6 but that didn't change anything. Your version is rather ancient and utterly unsupported. Call Oracle Support and ask for Frances. -- A city is a large community where people are lonesome together. |
Linear Mode
