Re: 8i (8.1.7.4.2) hangs on SHUTDOWN ABORT (WIN2000,SP3)

On 29 Jul 2003 04:16:03 -0700, fatih.dokmeci_at_arcelik.com (fatih) wrote:

>"Niall Litchfield" <n-litchfield_at_audit-commission.gov.uk> wrote in message news:<3f210f28$0$15041$ed9e5944_at_reading.news.pipex.net>...
>> What does the alert.log say?
>
>just:
>
>Shutting down instance (abort)
>License high water mark = 125
>Wed Jul 23 22:06:01 2003
>DBW0: terminating instance due to error 1092
>Wed Jul 23 22:06:01 2003
>PMON: terminating instance due to error 1092
>Wed Jul 23 22:06:02 2003
>CKPT: terminating instance due to error 1092
>Wed Jul 23 22:06:03 2003
>LGWR: terminating instance due to error 1092
>Wed Jul 23 22:06:03 2003
>ARC1: terminating instance due to error 1092
>Wed Jul 23 22:06:12 2003
>SNP6: terminating instance due to error 1092
>Wed Jul 23 22:06:14 2003
>SNP9: terminating instance due to error 1092
>Wed Jul 23 22:06:15 2003
>SNP7: terminating instance due to error 1092
>Wed Jul 23 22:06:33 2003
>SNP5: terminating instance due to error 1092
>Wed Jul 23 22:06:34 2003
>SNP3: terminating instance due to error 1092
>Wed Jul 23 22:06:34 2003
>SNP0: terminating instance due to error 1092
>Wed Jul 23 22:06:36 2003
>SNP8: terminating instance due to error 1092
>Wed Jul 23 22:06:42 2003
>SNP4: terminating instance due to error 1092
>Wed Jul 23 22:06:42 2003
>SNP1: terminating instance due to error 1092
>Instance terminated by SNP1, pid = 4724
>Wed Jul 23 22:06:44 2003
>Instance terminated by SNP9, pid = 4624
>Wed Jul 23 22:06:44 2003
>SNP2: terminating instance due to error 1092
>Instance terminated by SNP2, pid = 4512
>Wed Jul 23 22:06:45 2003
>Instance terminated by SNP7, pid = 4020
>Wed Jul 23 22:06:55 2003
>ARC0: terminating instance due to error 1092
>Instance terminated by ARC0, pid = 4868
>Wed Jul 23 22:07:01 2003
>Instance terminated by DBW0, pid = 4608
>Wed Jul 23 22:07:01 2003
>Instance terminated by PMON, pid = 4612
>Wed Jul 23 22:07:02 2003
>Instance terminated by CKPT, pid = 4604
>Wed Jul 23 22:07:03 2003
>Instance terminated by LGWR, pid = 4596
>Wed Jul 23 22:07:03 2003
>Instance terminated by ARC1, pid = 4284
>Wed Jul 23 22:07:03 2003
>Instance terminated by SNP5, pid = 4136
>Wed Jul 23 22:07:04 2003
>Instance terminated by SNP3, pid = 4636
>Wed Jul 23 22:07:04 2003
>Instance terminated by SNP0, pid = 4480
>Wed Jul 23 22:07:06 2003
>Instance terminated by SNP8, pid = 4468
>Wed Jul 23 22:07:12 2003
>Instance terminated by SNP6, pid = 4460
>Wed Jul 23 22:07:12 2003
>Instance terminated by SNP4, pid = 4068
>Wed Jul 23 22:09:26 2003
>SMON: terminating instance due to error 1092
>Instance terminated by SMON, pid = 4700
>Dump file D:\DTG\log\dtgALRT.LOG
>Thu Jul 24 00:04:56 2003
>ORACLE V8.1.7.4.1 - Production vsnsta=0
>vsnsql=f vsnxtr=3
>Windows 2000 Version 5.0 Service Pack 3, CPU type 586
>Starting up ORACLE RDBMS Version: 8.1.7.4.1.
>System parameters with non-default values:
> processes = 1000
> timed_statistics = TRUE
> shared_pool_size = 1153433600
> nls_sort = TURKISH
> nls_date_format = DD/MM/YYYY
> control_files = F:\DTG\control1.con, F:\DTG\control2.con,
>G:\DTG\control1A.con, G:\DTG\control2A.con, H:\DTG\control1B.con,
>H:\DTG\control2B.con, I:\DTG\control1C.con, I:\DTG\control2C.con
> db_block_buffers = 50000
> db_block_size = 8192
> compatible = 8.1.7
> log_archive_start = TRUE
> log_archive_dest_1 = location=D:\ARCH
> log_archive_format = arch%s.arc
> db_files = 100
> dml_locks = 500
> rollback_segments = r01, r02, r03, r04, r05, r06, r07, r08,
>r09, r10, r11, r12, r13, r14, r15, r16, r17, r18, r19, r20, r21, r22,
>r23, r24, r25, r26, r27, r28, r29, r30, r31, r32, r33, r34, r35, r36,
>r37, r38, r39, r40, r50, r51, r52, r53, r54, r55, r56, r57, r58, r59,
>r60, r61, r62, r63, r64, r65, r66, r67, r68, r69
> remote_login_passwordfile= EXCLUSIVE
> db_domain = WORLD
> global_names = TRUE
> open_links = 10
> sort_area_size = 2097152
> db_name = DTG
> open_cursors = 2048
> job_queue_processes = 10
> job_queue_interval = 60
> background_dump_dest = D:\DTG\log
> user_dump_dest = D:\DTG\log
> max_dump_file_size = 10240
>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
>SNP0 started with pid=8
>SNP1 started with pid=9
>SNP2 started with pid=10
>SNP3 started with pid=11
>SNP4 started with pid=12
>SNP5 started with pid=13
>SNP6 started with pid=14
>SNP7 started with pid=15
>SNP8 started with pid=16
>SNP9 started with pid=17
>Thu Jul 24 00:05:02 2003
>ARCH: STARTING ARCH PROCESSES
>ARC0 started with pid=18
>Thu Jul 24 00:05:02 2003
>ARC0: Archival started
>Thu Jul 24 00:05:03 2003
>ARCH: STARTING ARCH PROCESSES COMPLETE
>Thu Jul 24 00:05:03 2003
>alter database mount
>Thu Jul 24 00:05:08 2003
>Successful mount of redo thread 1, with mount id 3165929716.
>Thu Jul 24 00:05:08 2003
>Database mounted in Exclusive Mode.
>Completed: alter database mount
>Thu Jul 24 00:05:08 2003
>alter database open
>Beginning crash recovery of 1 threads
>Thu Jul 24 00:05:08 2003
>Thread recovery: start rolling forward thread 1
>Recovery of Online Redo Log: Thread 1 Group 7 Seq 32583 Reading mem 0
> Mem# 0 errs 0: F:\DTG\LOG7A.RDO
>Thu Jul 24 00:05:11 2003
>Thread recovery: finish rolling forward thread 1
>Thread recovery: 1018 data blocks read, 940 data blocks written, 36914
>redo blocks read
>Crash recovery completed successfully
>Thu Jul 24 00:05:12 2003
>Thread 1 advanced to log sequence 32584
>Thread 1 opened at log sequence 32584
> Current log# 8 seq# 32584 mem# 0: F:\DTG\LOG8A.RDO
>Successful open of redo thread 1.
>Thu Jul 24 00:05:12 2003
>SMON: enabling cache recovery
>Thu Jul 24 00:05:12 2003
>ARC0: Beginning to archive log# 7 seq# 32583
>Thu Jul 24 00:05:13 2003
>SMON: enabling tx recovery
>Thu Jul 24 00:05:13 2003
>ARC0: Completed archiving log# 7 seq# 32583
>Thu Jul 24 00:05:19 2003
>Completed: alter database open
>Thu Jul 24 00:06:45 2003
>Restarting dead background process EMN0
>EMN0 started with pid=20
>Thu Jul 24 00:06:45 2003
>
>Thanks for your attention..

Is there any reason why you think Oracle should still function properly in such a mess? 60+ rollback segments, 2048 open cursors per sessions. And you are running such a configuration on Windoze!!!! It is quite clear your memory consumption for Oracle is so high the O/S will choke, ALL THE TIME

Hire a consultant! NOW!
Before your company goes bankrupt due to this incompetent database configuration.

Sybrand Bakker, Senior Oracle DBA

To reply remove -verwijderdit from my e-mail address Received on Tue Jul 29 2003 - 13:11:27 CDT