Scandisks crashed instance
I wanted to add disks to an existing diskgroup.
After running /etc/init.d/oracleasm createdisk DISK18 /dev/sdr1
on blade 1
I went to blades 2, 3 4 to run
/etc/init.d/oracleasm scandisk
but the instance on blades 2 and 3 crashed.
Can anyone think of why scandisks would do this?
1. the asm alert log showed nothing.
2. I can never read the dmesg log no date/time
3, the /var/log/message on all 3 blades looked something like this:
Apr 1 14:26:36 swymcooracl002 kernel: Device busy for revalidation (usage=2)
Apr 1 14:26:36 swymcooracl002 kernel: I/O error: dev 08:20, sector 11753600
Apr 1 14:26:36 swymcooracl002 kernel: I/O error: dev 08:20, sector 11753568
No hardware errors were detected, the disks all have green lights. And this message occurred only when I did the oracleasm scandisks
Similar Messages
-
what is the difference between crash recovery and instance recovery???
From http://download-uk.oracle.com/docs/cd/B10501_01/server.920/a96519/recov.htm#1004618
Crash recovery is used to recover from a failure either when a single-instance database crashes or all instances of an Oracle Real Application Clusters database crashes. Instance recovery refers to the case where a surviving instance recovers a failed instance in an Oracle Real Application Clusters database. -
Are archived logs useful for crashed instance?
when the machine powers off,and start it again,the database will experience instance recover,will this kind of recover use archived log£¿I see if the database worked under unarchive mod before,then instance recover will not use archived log(no archived log).
surpose that oracle makes a commit,and the commited
data are already written into log file,but are not
written back to datafile,and if the log file is
archived,at this time OS crash.when oracle startup again
it will user the online redo,and some of the latest
archvied log to recover the committed data.and if the
archvied log accidentally lost,how can oracle recovery.
Or oracle will not reuse the online redo log until
its data are written back to the datafile under archived
log mod? -
I have a bpel-process like the following:
1) receive (client)
2) assign
3) assign
4) reply (client)
5) assign
6) assign
7) invoke (client callback)
A instance of this process chrashed during server-restart after 4)
After the server-restart the instance is still in status open.running but not doing anything.
How can i recover such an instance?Harald,
You could try looking in 'Perform Manual Recovery' within the BPEL console. This can be accessed from:
1) Logging into the BPEL console
2) Select BPEL Processes tab
3) Select 'Perform Manual Recovery' Link on the Left hand side palette.
If you look under each of the tabs (invoke, callback) there may be a record for your instance (look at conversation id and bpel process). If there is, you should be able to manually recovery your instance
Hope that Helps
Dave -
ORA-00488: RBAL process terminated with error causing ASM instance to crash
Hi Freinds,
I am manging a three node ASM cluster on 10g(10.2.0.2).Yesterday I observed one of the ASM instance got crashed .On reviewing the Alert log of crashed ASM instance I found
"*ORA-00488: RBAL process terminated with error*"
and subsequently
"*PMON: terminating instance due to error 488*".
I could restart the crashed instance without an issues but I want to know what kind of event could lead to such scenario.
I searched net and metalink but didn't found any helpful information.
Did any of you faced similar issues and do you have understanding why and when it happens.
Thanks in Advance
Arindam.Hi,
There is bug reported on such issue, please check further on metalink if you have support.
Dilip Patel. -
Difference between Instance Crash and Database Crash in Standalone and RAC?
I am new to Oracle Environment. I would appreiciate if i get clarified on the "_+Difference between Instance Crash and Database Crash in Standalone and
RAC_".+
Oracle Version: 11.1.0.7.0
O.S Version: HP-UX B.11.31 USivaprasad S wrote:
I am new to Oracle Environment. I would appreiciate if i get clarified on the "_+Difference between Instance Crash and Database Crash in Standalone and
RAC_".+That depends on your definitions of database crash versus instance crash.
Literally, database crash means that the database itself is damaged in some way. A disk is no more. Data files are corrupted. Etc. The database itself thus causes the crash - and a database crash will also cause all database instances (RAC or single) for that database to crash too.
An instance crash will therefore mean that the crash occurs in the instance due to an Oracle bug or similar. In other words a s/w error and not a database error. The database is still "fine", but the instance not. Instance crashes. However, any other instance on that same (RAC) database will still be fine as the database itself is unaffected by that s/w error in the crashed instance.
If you mean something different, please enlighten us. Not all crashes are equal. {noformat};-){noformat} -
TABLESPACE BACKUP - Database crash
Hello guys,
i got a little question about "Online / Hot Backup" and a crashing instance.
The following worst case happen:
1) Alter Tablespace TABSP_USER01 in backup mode at 03:00 am
2) There is a problem, while copying the datafiles and the backup modus for the tablespace TABSP_USER01 exists all the time
3) Database crashes at 04:30 am and the tablespace TABSP_USER01 is still in backup mode
4) While the whole online/hot backup was run, an archive log backup runs at 04:00 am and the saved archive log files are deleted from disk
I know what happen to the datafiles while the "online backup". The SCN is frozen when the "backup modus" is set... and in the redo log files a complete block-image is written.
All dirty blocks are written to the datafiles, while the "backup modus" is on, but the SCN is not updated.
But my question is now:
1) If i restart my crashed instance at 05:03 am .. are the archive logs needed for checking (which were already back upped and deleted) at a startup?
2) Does Oracle verify the data in the redo/archive logs with the ones in the datafiles?
3) Or does Oracle only set the actual SCNs to the header of the datafiles (the actual scn is get from the controlfile)?
Thanks and Regards
Stefan#1) If i restart my crashed instance at 05:03 am .. are the archive logs needed for checking (which were already back upped and deleted) at a startup? ##
Yes it will ask for the recovery needed in the mount stage.you need to backup again...
# 2) Does Oracle verify the data in the redo/archive logs with the ones in the datafiles? &3) Or does Oracle only set the actual SCNs to the header of the datafiles (the actual scn is get from the controlfile)? ###
The asnwer is yes and no...It checks both header and information..
Since it is asking for the recocvery it is understandable that it checks for header is not in synch and will apply all the changes...to make it synch.(.all the sequenced are captured in redo-log and archived logs.)
kindly go through this document for clarifications..
http://download-west.oracle.com/docs/cd/B19306_01/server.102/b14220/backrec.htm#i1007289
Thanks
-- Raman -
Linux 3.12 and streaming media on a Dell XPS 13: kernel panic
Hi all,
Shortly after upgrading from Linux 3.11.6 to 3.12, I started getting kernel panics while playing streaming media (in particular from Youtube and The Daily Show). Here is a camera shot. The crash would not take place immediatly, but perhaps after 15 minutes of streaming. After downgrading to Linux 3.11.6 everything works fine. Therefore, it is clear to me that the issue is related to the Linux 3.12 kernel, but this is all I know.
The fifth-to-last line from the camera shot reads:
[11438.332699] RIP [<ffffffff8129e160>] __sg_page_iter_start+0x20/0x20
A quick Google search reveals that __sg_page_iter_start is a function inside the scatterlist.h library in the Linux kernel, which apparently deals with memory paging, but my knowledge about this stuff is so poor that the message is almost meaningless. I would greatly appreciate if someone could give me a hint about this.
I did not find anything useful in the journal, but here are the last few journal lines for 2 different crash instances:
Crash #1
Nov 15 00:22:45 xps gnome-session[385]: Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Nov 15 00:24:15 xps gnome-session[385]: Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Nov 15 00:24:22 xps gnome-session[385]: Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Nov 15 00:24:24 xps gnome-session[385]: Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Nov 15 00:24:26 xps gnome-session[385]: Starting FCEUX 2.2.2...
Nov 15 00:24:26 xps gnome-session[385]: Loading /home/vrg/MyFiles/roms/nes/CASTLEVA.NES...
Nov 15 00:24:26 xps gnome-session[385]: PRG ROM: 8 x 16KiB
Nov 15 00:24:26 xps gnome-session[385]: CHR ROM: 0 x 8KiB
Nov 15 00:24:26 xps gnome-session[385]: ROM CRC32: 0xb668c7fc
Nov 15 00:24:26 xps gnome-session[385]: ROM MD5: 0x728e05f245ab8b7fe61083f6919dc485
Nov 15 00:24:26 xps gnome-session[385]: Mapper #: 2
Nov 15 00:24:26 xps gnome-session[385]: Mapper name: UNROM
Nov 15 00:24:26 xps gnome-session[385]: Mirroring: Vertical
Nov 15 00:24:26 xps gnome-session[385]: Battery-backed: No
Nov 15 00:24:26 xps gnome-session[385]: Trained: No
Nov 15 00:24:26 xps gnome-session[385]: Power on
Nov 15 00:24:26 xps gnome-session[385]: Initializing video... Video Mode: 256 x 224 x 32 bpp
Nov 15 00:24:26 xps gnome-session[385]: Initializing video... Video Mode: 1920 x 1080 x 32 bpp full screen
Nov 15 00:24:26 xps gnome-session[385]: Emulation speed 126.0%
Nov 15 00:24:26 xps gnome-session[385]: Emulation speed 158.7%
Nov 15 00:24:26 xps gnome-session[385]: Emulation speed 200.0%
Nov 15 00:24:26 xps gnome-session[385]: Emulation speed 252.0%
Nov 15 00:24:26 xps gnome-session[385]: Emulation speed 200.0%
Nov 15 00:24:26 xps gnome-session[385]: Emulation speed 158.7%
Nov 15 00:24:26 xps gnome-session[385]: Emulation speed 126.0%
Nov 15 00:24:26 xps gnome-session[385]: Emulation speed 100.0%
Nov 15 00:24:26 xps gnome-session[385]: Initializing video... Video Mode: 256 x 224 x 32 bpp
Nov 15 00:24:27 xps gnome-session[385]: Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Nov 15 00:26:02 xps kernel: perf samples too long (2530 > 2500), lowering kernel.perf_event_max_sample_rate to 50100
Nov 15 00:27:43 xps gnome-session[385]: Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Nov 15 00:28:44 xps gnome-session[385]: Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Nov 15 00:30:55 xps gnome-session[385]: Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Nov 15 00:30:55 xps gnome-session[385]: Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Nov 15 00:30:55 xps gnome-session[385]: !!! [YouTubeInfoService: setting loadContext]: TypeError: channel is undefined
Nov 15 00:31:25 xps gnome-session[385]: Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Nov 15 00:31:31 xps gnome-session[385]: Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Nov 15 00:31:32 xps gnome-session[385]: !!! [YouTubeInfoService: setting loadContext]: TypeError: channel is undefined
Crash #2
Nov 17 14:35:41 xps dbus-daemon[279]: dbus[279]: [system] Activating via systemd: service name='org.freedesktop.NetworkManager' unit='dbus-org.freedesktop.NetworkManager.service'
Nov 17 14:35:41 xps dbus[279]: [system] Activating via systemd: service name='org.freedesktop.NetworkManager' unit='dbus-org.freedesktop.NetworkManager.service'
Nov 17 14:35:41 xps dbus[279]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.NetworkManager.service': Unit dbus-org.freedesktop.NetworkManager.service failed to load: No such file or directory.
Nov 17 14:35:41 xps dbus-daemon[279]: dbus[279]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.NetworkManager.service': Unit dbus-org.freedesktop.NetworkManager.service failed to load: No such file or directory.
Nov 17 16:15:31 xps gnome-session[351]: Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Nov 17 16:15:39 xps gnome-session[351]: Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Nov 17 16:15:50 xps gnome-session[351]: Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Nov 17 16:15:50 xps gnome-session[351]: !!! [YouTubeInfoService: setting loadContext]: TypeError: channel is undefined
Nov 17 16:16:03 xps gnome-session[351]: Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Nov 17 16:24:09 xps gnome-session[351]: Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Nov 17 16:29:40 xps gnome-session[351]: Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Nov 17 16:37:00 xps gnome-session[351]: Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Nov 17 16:41:42 xps gnome-session[351]: NOTE: child process received `Goodbye', closing down
In the first journal log, the following line calls my attention:
Nov 15 00:26:02 xps kernel: perf samples too long (2530 > 2500), lowering kernel.perf_event_max_sample_rate to 50100
However, this seems to be a normal occurrence after playing games (https://bbs.archlinux.org/viewtopic.php?id=170471), so I would guess this is not related to the kernel panic.
For reference, here are some hardware specifications of my Dell XPS 13:
# lsmod
Module Size Used by
usb_storage 47847 1
fuse 74829 3
uvcvideo 72804 0
videobuf2_vmalloc 3272 1 uvcvideo
videobuf2_memops 2335 1 videobuf2_vmalloc
videobuf2_core 27797 1 uvcvideo
videodev 110188 2 uvcvideo,videobuf2_core
media 11591 2 uvcvideo,videodev
hid_generic 1153 0
usbhid 41434 0
hid 89751 2 hid_generic,usbhid
joydev 9663 0
dell_wmi 1485 0
sparse_keymap 3114 1 dell_wmi
ax88179_178a 12500 0
usbnet 26083 1 ax88179_178a
mii 4027 2 usbnet,ax88179_178a
x86_pkg_temp_thermal 6959 0
intel_powerclamp 8642 0
coretemp 6326 0
kvm_intel 129457 0
kvm 379351 1 kvm_intel
crc32_pclmul 2987 0
crc32c_intel 14249 0
ghash_clmulni_intel 4469 0
cryptd 8473 1 ghash_clmulni_intel
nls_cp437 5953 2
iTCO_wdt 5407 0
vfat 10055 2
fat 51827 1 vfat
iTCO_vendor_support 1929 1 iTCO_wdt
dell_laptop 8851 0
dcdbas 6455 1 dell_laptop
arc4 2000 2
iwldvm 172354 0
mac80211 454008 1 iwldvm
microcode 15024 0
psmouse 85356 0
snd_hda_codec_hdmi 30233 1
evdev 10693 15
serio_raw 5041 0
pcspkr 2027 0
i2c_i801 11269 0
iwlwifi 137049 1 iwldvm
snd_hda_codec_realtek 37276 1
cfg80211 403337 3 iwlwifi,mac80211,iwldvm
i915 611138 3
wmi 8347 1 dell_wmi
rfkill 15698 3 cfg80211
thermal 8620 0
snd_hda_intel 36520 3
intel_agp 10872 1 i915
snd_hda_codec 148129 3 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_intel
intel_gtt 12664 2 i915,intel_agp
drm_kms_helper 35854 1 i915
snd_hwdep 6332 1 snd_hda_codec
tpm_tis 10921 0
tpm 15091 1 tpm_tis
snd_pcm 77765 3 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel
tpm_bios 9745 1 tpm
drm 236060 4 i915,drm_kms_helper
snd_page_alloc 7202 2 snd_pcm,snd_hda_intel
shpchp 25457 0
snd_timer 18718 1 snd_pcm
i2c_algo_bit 5391 1 i915
snd 59141 13 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_hda_codec,snd_hda_intel
i2c_core 23720 6 drm,i915,i2c_i801,drm_kms_helper,i2c_algo_bit,videodev
soundcore 5450 1 snd
mei_me 9296 0
battery 6925 0
mei 62003 1 mei_me
video 11380 1 i915
mperf 1235 0
lpc_ich 13112 0
ac 3324 0
processor 25077 0
button 4669 1 i915
vboxdrv 263994 0
ext4 470284 3
crc16 1359 1 ext4
mbcache 5866 1 ext4
jbd2 83376 1 ext4
sd_mod 30739 8
ahci 22888 5
libahci 21393 1 ahci
ehci_pci 4120 0
libata 171318 2 ahci,libahci
ehci_hcd 48052 1 ehci_pci
xhci_hcd 91357 0
scsi_mod 128695 3 usb_storage,libata,sd_mod
usbcore 178087 8 uvcvideo,usb_storage,ehci_hcd,ehci_pci,usbhid,usbnet,ax88179_178a,xhci_hcd
usb_common 1648 1 usbcore
# lshw
xps
description: Portable Computer
product: Dell System XPS L322X (System SKUNumber)
vendor: Dell Inc.
version: 0.1
serial: 2H0CVW1
width: 64 bits
capabilities: smbios-2.7 dmi-2.7 vsyscall32
configuration: administrator_password=unknown boot=normal chassis=portable family=ChiefRiver System frontpanel_password=unknown keyboard_password=unknown power-on_password=unknown sku=System SKUNumber uuid=44454C4C-4800-1030-8043-B2C04F565731
*-core
description: Motherboard
product: 0PJHXN
vendor: Dell Inc.
physical id: 0
version: A00
serial: .2H0CVW1.CN4864332G0061.
slot: Part Component
*-cpu
description: CPU
product: Core i7 (To Be Filled By O.E.M.)
vendor: Intel Corp.
physical id: 4
bus info: cpu@0
version: Intel(R) Core(TM) i7-3537U CPU @ 2.00GHz
serial: To Be Filled By O.E.M.
slot: CPU Socket - U3E1
size: 2500MHz
capacity: 3100MHz
width: 64 bits
clock: 100MHz
capabilities: x86-64 fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer xsave avx f16c rdrand lahf_lm ida arat epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms cpufreq
configuration: cores=2 enabledcores=2 threads=4
*-cache:0
description: L1 cache
physical id: 6
slot: L1-Cache
size: 32KiB
capacity: 32KiB
capabilities: internal write-through instruction
*-cache:1
description: L2 cache
physical id: 7
slot: L2-Cache
size: 256KiB
capacity: 256KiB
capabilities: internal write-through unified
*-cache:2
description: L3 cache
physical id: 8
slot: L3-Cache
size: 4MiB
capacity: 4MiB
capabilities: internal write-back unified
*-cache
description: L1 cache
physical id: 5
slot: L1-Cache
size: 32KiB
capacity: 32KiB
capabilities: internal write-through data
*-firmware
description: BIOS
vendor: Dell Inc.
physical id: 0
version: A06
date: 12/03/2012
size: 128KiB
capacity: 6592KiB
capabilities: pci pnp upgrade shadowing escd cdboot bootselect edd int13floppy360 int13floppy1200 int13floppy720 int5printscreen int9keyboard int14serial int17printer int10video acpi usb ls120boot smartbattery biosbootspecification netboot
*-memory
description: System Memory
physical id: 35
slot: System board or motherboard
size: 8GiB
*-bank:0
description: DIMM DDR3 Synchronous 1600 MHz (0.6 ns)
product: HT5SMRAP
vendor: Hynix/Hyundai
physical id: 0
serial: 00000000
slot: ChannelA-DIMM0
size: 4GiB
width: 64 bits
clock: 1600MHz (0.6ns)
*-bank:1
description: DIMM DDR3 Synchronous 1600 MHz (0.6 ns)
product: HT5SMRAP
vendor: Hynix/Hyundai
physical id: 1
serial: 00000000
slot: ChannelB-DIMM0
size: 4GiB
width: 64 bits
clock: 1600MHz (0.6ns)
*-pci
description: Host bridge
product: 3rd Gen Core processor DRAM Controller
vendor: Intel Corporation
physical id: 100
bus info: pci@0000:00:00.0
version: 09
width: 32 bits
clock: 33MHz
*-display
description: VGA compatible controller
product: 3rd Gen Core processor Graphics Controller
vendor: Intel Corporation
physical id: 2
bus info: pci@0000:00:02.0
version: 09
width: 64 bits
clock: 33MHz
capabilities: msi pm vga_controller bus_master cap_list rom
configuration: driver=i915 latency=0
resources: irq:45 memory:d0000000-d03fffff memory:c0000000-cfffffff ioport:2000(size=64)
*-usb:0
description: USB controller
product: 7 Series/C210 Series Chipset Family USB xHCI Host Controller
vendor: Intel Corporation
physical id: 14
bus info: pci@0000:00:14.0
version: 04
width: 64 bits
clock: 33MHz
capabilities: pm msi xhci bus_master cap_list
configuration: driver=xhci_hcd latency=0
resources: irq:40 memory:d0500000-d050ffff
*-usbhost:0
product: xHCI Host Controller
vendor: Linux 3.11.6-1-ARCH xhci_hcd
physical id: 0
bus info: usb@2
logical name: usb2
version: 3.11
capabilities: usb-3.00
configuration: driver=hub slots=4 speed=5000Mbit/s
*-usb
description: Ethernet interface
product: AX88179
vendor: ASIX Elec. Corp.
physical id: 2
bus info: usb@2:2
logical name: enp0s20u2
version: 1.00
serial: 0000249B0982FA
size: 100Mbit/s
capacity: 1Gbit/s
capabilities: usb-3.00 ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=ax88179_178a duplex=full ip=128.103.14.222 link=yes maxpower=496mA multicast=yes port=MII speed=100Mbit/s
*-usbhost:1
product: xHCI Host Controller
vendor: Linux 3.11.6-1-ARCH xhci_hcd
physical id: 1
bus info: usb@1
logical name: usb1
version: 3.11
capabilities: usb-2.00
configuration: driver=hub slots=4 speed=480Mbit/s
*-usb
description: USB hub
product: USB2.0 Hub
vendor: Genesys Logic, Inc.
physical id: 1
bus info: usb@1:1
version: 32.98
capabilities: usb-2.00
configuration: driver=hub maxpower=100mA slots=4 speed=480Mbit/s
*-usb:0
description: Mouse
product: USB OPTICAL MOUSE
vendor: PIXART
physical id: 1
bus info: usb@1:1.1
version: 1.00
capabilities: usb-1.10
configuration: driver=usbhid maxpower=100mA speed=2Mbit/s
*-usb:1
description: Mass storage device
product: Android Phone
vendor: HTC
physical id: 2
bus info: usb@1:1.2
version: 2.26
serial: HT08DHL10581
capabilities: usb-2.00 scsi
configuration: driver=usb-storage maxpower=500mA speed=480Mbit/s
*-communication
description: Communication controller
product: 7 Series/C210 Series Chipset Family MEI Controller #1
vendor: Intel Corporation
physical id: 16
bus info: pci@0000:00:16.0
version: 04
width: 64 bits
clock: 33MHz
capabilities: pm msi bus_master cap_list
configuration: driver=mei_me latency=0
resources: irq:42 memory:d0515000-d051500f
*-usb:1
description: USB controller
product: 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2
vendor: Intel Corporation
physical id: 1a
bus info: pci@0000:00:1a.0
version: 04
width: 32 bits
clock: 33MHz
capabilities: pm debug ehci bus_master cap_list
configuration: driver=ehci-pci latency=0
resources: irq:16 memory:d051a000-d051a3ff
*-usbhost
product: EHCI Host Controller
vendor: Linux 3.11.6-1-ARCH ehci_hcd
physical id: 1
bus info: usb@3
logical name: usb3
version: 3.11
capabilities: usb-2.00
configuration: driver=hub slots=2 speed=480Mbit/s
*-usb
description: USB hub
product: Integrated Rate Matching Hub
vendor: Intel Corp.
physical id: 1
bus info: usb@3:1
version: 0.00
capabilities: usb-2.00
configuration: driver=hub slots=6 speed=480Mbit/s
*-usb
description: Video
product: Laptop_Integrated_Webcam_1.3M
vendor: 00248CE62D1E-CC18-000603
physical id: 5
bus info: usb@3:1.5
version: 27.09
capabilities: usb-2.00
configuration: driver=uvcvideo maxpower=500mA speed=480Mbit/s
*-multimedia
description: Audio device
product: 7 Series/C210 Series Chipset Family High Definition Audio Controller
vendor: Intel Corporation
physical id: 1b
bus info: pci@0000:00:1b.0
version: 04
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list
configuration: driver=snd_hda_intel latency=0
resources: irq:43 memory:d0510000-d0513fff
*-pci
description: PCI bridge
product: 7 Series/C210 Series Chipset Family PCI Express Root Port 1
vendor: Intel Corporation
physical id: 1c
bus info: pci@0000:00:1c.0
version: c4
width: 32 bits
clock: 33MHz
capabilities: pci pciexpress msi pm normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:16 memory:d0400000-d04fffff
*-network DISABLED
description: Wireless interface
product: Centrino Advanced-N 6235
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:01:00.0
logical name: wlp1s0
version: 24
serial: c8:f7:33:83:71:1f
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=iwlwifi driverversion=3.11.6-1-ARCH firmware=18.168.6.1 latency=0 link=no multicast=yes wireless=IEEE 802.11abgn
resources: irq:44 memory:d0400000-d0401fff
*-usb:2
description: USB controller
product: 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1
vendor: Intel Corporation
physical id: 1d
bus info: pci@0000:00:1d.0
version: 04
width: 32 bits
clock: 33MHz
capabilities: pm debug ehci bus_master cap_list
configuration: driver=ehci-pci latency=0
resources: irq:23 memory:d0519000-d05193ff
*-usbhost
product: EHCI Host Controller
vendor: Linux 3.11.6-1-ARCH ehci_hcd
physical id: 1
bus info: usb@4
logical name: usb4
version: 3.11
capabilities: usb-2.00
configuration: driver=hub slots=2 speed=480Mbit/s
*-usb
description: USB hub
product: Integrated Rate Matching Hub
vendor: Intel Corp.
physical id: 1
bus info: usb@4:1
version: 0.00
capabilities: usb-2.00
configuration: driver=hub slots=8 speed=480Mbit/s
*-isa
description: ISA bridge
product: QS77 Express Chipset LPC Controller
vendor: Intel Corporation
physical id: 1f
bus info: pci@0000:00:1f.0
version: 04
width: 32 bits
clock: 33MHz
capabilities: isa bus_master cap_list
configuration: driver=lpc_ich latency=0
resources: irq:0
*-storage
description: SATA controller
product: 7 Series Chipset Family 6-port SATA Controller [AHCI mode]
vendor: Intel Corporation
physical id: 1f.2
bus info: pci@0000:00:1f.2
version: 04
width: 32 bits
clock: 66MHz
capabilities: storage msi pm ahci_1.0 bus_master cap_list
configuration: driver=ahci latency=0
resources: irq:41 ioport:2098(size=8) ioport:20bc(size=4) ioport:2090(size=8) ioport:20b8(size=4) ioport:2060(size=32) memory:d0518000-d05187ff
*-serial UNCLAIMED
description: SMBus
product: 7 Series/C210 Series Chipset Family SMBus Controller
vendor: Intel Corporation
physical id: 1f.3
bus info: pci@0000:00:1f.3
version: 04
width: 64 bits
clock: 33MHz
configuration: latency=0
resources: memory:d0514000-d05140ff ioport:efa0(size=32)
*-battery
product: DELL
vendor: Dynapack
physical id: 1
version: 2008
serial: 1.0
slot: Rear
capacity: 46620mWh
configuration: voltage=7.4V
*-scsi
physical id: 2
bus info: scsi@6
logical name: scsi6
capabilities: scsi-host
configuration: driver=usb-storagePosted to [email protected], I hope I just haven't dawdled for too long and this can make it to 3.13 final.
Hopefully this should be sufficient information, I've linked to this thread too. I've also mentioned I'm willing to beam one at someone from Amazon, with 2-day shipping to the USA the Pluggable branded adapter is just under NZD$40, which I can easily live with.
===========================================================================================================
USB3 gigabit ethernet adapters with the ASIX AX88179 chipset (LevelOne USB0401-V3, Plugable USB3-E1000, SIIG JU-NE0211-S1 and others) are experiencing kernel panics in usb_hcd_map_urb_for_dma since 3.12. The issue does not seem to directly correlate with low or high network activity, occurring seemingly at random. Some panics occurred less than 5 minutes from boot and tens of megabytes of network transfer, while on other occasions it would be stable for multiple days with tens to hundreds of gigabytes of line-rate throughput and several sleep/resume cycles.
Both my Sony Vaio Pro 13 and another user reporting this issue on the Arch forums [1] are Intel-based, my USB controller is an 8086:9c31 (Lynx Point LP), the other is reported as a C210/7 series (unknown PID). A third with a Haswell Dell XPS has attempted my workaround and reports similar success.
I have a mediocre quality photo of my laptop's screen from one of these panics [2], the call trace - which is similar but not identical between my machine and that of the other user reporting the issue - is as follows:
usb_hcd_map_urb_for_dma
usb_hcd_submit_urb
local_bh_enable_ip
selinux_parse_skb
usb_alloc_urb
__kmalloc
usbnet_start_xmit
usbnet_start_xmit
dev_hard_start_xmit
sch_direct_xmit
dev_queue_xmit
ip_finish_output2
ip_finish_output
ip_output
dst_output
ip_local_out
ip_queue_xmit
tcp_transmit_skb
tcp_write_xmit
__tcp_push_pending_frames
tcp_push
tcp_sendmsg
inet_sendmsg
__sock_sendmsg_nosec
sock_sendmsg
set_restore_sigmask
set_restore_sigmask
fget_light
SYSC_sendto
set_restore_sigmask
SyS_sendto
system_call_fastpath
So far as I can tell, the driver is unaffected as late as 3.11.6, but problematic as of 3.12 (and still affected in 3.13-rc5). The history of drivers/net/usb/ax88179_178a.c for this time period yields this patch, which at least in my somewhat limited understanding appeared a likely candidate. I've reverted this on my system - against several linux-next builds from the last 3-4 weeks - and have had no issues with this network controller since.
commit 3804fad45411b48233b48003e33a78f290d227c8
Author: Ming Lei <[email protected]>
Date: Thu Aug 8 21:48:25 2013 +0800
USBNET: ax88179_178a: enable tso if usb host supports sg dma
This patch enables 'can_dma_sg' flag for ax88179_178a device
if the attached host controller supports building packet from
discontinuous buffers(DMA SG is possible), so TSO can be enabled
and skb fragment buffers can be passed to usb stack via urb->sg
directly.
With the patch, system CPU utilization decreased ~50% and throughput
increased by ~10% when doing iperf client test on one ARM A15 dual
core board.
Cc: Ben Hutchings <[email protected]>
Cc: Grant Grundler <[email protected]>
Cc: Oliver Neukum <[email protected]>
Cc: Alan Stern <[email protected]>
Cc: Freddy Xin <[email protected]>
Signed-off-by: Ming Lei <[email protected]>
Acked-by: Eric Dumazet <[email protected]>
Acked-by: David S. Miller <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
Unfortunately I have not retained the built kernel from a broken 3.12 build, so the system information below reflects the patched linux-next kernel I am running currently.
I understand this may be a somewhat obscure piece of hardware, I am willing to assist by drop-shipping one to someone from Amazon (or local country equivalent if the price is not extortionate) should it be required.
System information:
ver_linux:
Linux neko 3.13.0-rc5-next-20131224+ #1 SMP Sat Dec 28 19:09:27 NZDT 2013 x86_64 Intel(R) Core(TM) i7-4500U CPU @ 1.80GHz GenuineIntel GNU/Linux
Gnu C 4.7.3
Gnu make 4.0
binutils 2.24
util-linux scripts/ver_linux: line 23: fdformat: command not found
mount assert
module-init-tools 16
e2fsprogs 1.42.9
jfsutils 1.1.15
reiserfsprogs 3.6.24
reiser4progs 1.0.7
xfsprogs 3.1.11
quota-tools 4.01.
PPP 2.4.5
Linux C Library 2.17
Dynamic linker (ldd) 2.17
Procps 3.3.9
Net-tools 1.60_p20130513023548
Kbd 2.0.1
Sh-utils 8.22
Modules Loaded bonding rndis_host cdc_ether tun snd_usb_audio snd_usbmidi_lib snd_rawmidi cdc_acm ctr ccm hidp nfsd rfcomm bnep iptable_nat nf_nat_ipv4 nf_nat uvcvideo btusb bluetooth hid_multitouch videobuf2_vmalloc videobuf2_memops videobuf2_core uinput ax88179_178a usbnet mii rtsx_pci_sdmmc rtsx_pci mmc_core fuse snd_hda_codec_realtek iwlmvm kvm_intel snd_hda_codec_generic mac80211 kvm pn544_mei mei_phy iwlwifi pn544 snd_hda_intel hci nfc snd_hda_codec snd_hwdep cfg80211 xhci_hcd
/proc/cpuinfo:
processor : 3
vendor_id : GenuineIntel
cpu family : 6
model : 69
model name : Intel(R) Core(TM) i7-4500U CPU @ 1.80GHz
stepping : 1
microcode : 0x10
cpu MHz : 2968.125
cache size : 4096 KB
physical id : 0
siblings : 4
core id : 1
cpu cores : 2
apicid : 3
initial apicid : 3
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 fma cx16 xtpr pdcm pcid sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm ida arat epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid
bogomips : 4788.92
clflush size : 64
cache_alignment : 64
address sizes : 39 bits physical, 48 bits virtual
power management:
PCI:
-[0000:00]-+-00.0 Intel Corporation Haswell-ULT DRAM Controller [8086:0a04]
+-02.0 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16]
+-03.0 Intel Corporation Device [8086:0a0c]
+-14.0 Intel Corporation Lynx Point-LP USB xHCI HC [8086:9c31]
+-16.0 Intel Corporation Lynx Point-LP HECI #0 [8086:9c3a]
+-1b.0 Intel Corporation Lynx Point-LP HD Audio Controller [8086:9c20]
+-1c.0-[01]----00.0 Intel Corporation Wireless 7260 [8086:08b1]
+-1c.3-[02]--
+-1c.4-[03]----00.0 Samsung Electronics Co Ltd Device [144d:a800]
+-1d.0 Intel Corporation Lynx Point-LP USB EHCI #1 [8086:9c26]
+-1f.0 Intel Corporation Lynx Point-LP LPC Controller [8086:9c43]
\-1f.3 Intel Corporation Lynx Point-LP SMBus Controller [8086:9c22]
USB:
Bus 001 Device 002: ID 8087:8000 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 025: ID 0b95:1790 ASIX Electronics Corp.
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 027: ID 8087:07dc Intel Corp.
Bus 002 Device 003: ID 04f2:b3be Chicony Electronics Co., Ltd
Bus 002 Device 002: ID 0eef:a108 D-WAV Scientific Co., Ltd
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
/proc/modules:
bonding 84837 0 - Live 0xffffffffc00d5000
rndis_host 5162 0 - Live 0xffffffffc0096000
cdc_ether 4324 1 rndis_host, Live 0xffffffffc006e000
tun 16811 0 - Live 0xffffffffc009e000
snd_usb_audio 102474 0 - Live 0xffffffffc007b000
snd_usbmidi_lib 16542 1 snd_usb_audio, Live 0xffffffffc0072000
snd_rawmidi 15891 1 snd_usbmidi_lib, Live 0xffffffffc0017000
cdc_acm 16166 0 - Live 0xffffffffc05ec000
ctr 3471 2 - Live 0xffffffffc05e8000
ccm 6977 2 - Live 0xffffffffc05e3000
hidp 12989 0 - Live 0xffffffffc05db000
nfsd 192979 13 - Live 0xffffffffc059b000
rfcomm 27704 12 - Live 0xffffffffc058e000
bnep 9055 2 - Live 0xffffffffc0587000
iptable_nat 2550 0 - Live 0xffffffffc0583000
nf_nat_ipv4 3118 1 iptable_nat, Live 0xffffffffc057f000
nf_nat 9984 2 iptable_nat,nf_nat_ipv4, Live 0xffffffffc0577000
uvcvideo 60542 0 - Live 0xffffffffc0562000
btusb 14182 0 - Live 0xffffffffc0519000
bluetooth 200149 23 hidp,rfcomm,bnep,btusb, Live 0xffffffffc04d8000
hid_multitouch 8791 0 - Live 0xffffffffc04d1000
videobuf2_vmalloc 2528 1 uvcvideo, Live 0xffffffffc04cd000
videobuf2_memops 1559 1 videobuf2_vmalloc, Live 0xffffffffc04c9000
videobuf2_core 22473 1 uvcvideo, Live 0xffffffffc04be000
uinput 6657 0 - Live 0xffffffffc04b9000
ax88179_178a 11352 0 - Live 0xffffffffc04b2000
usbnet 17066 3 rndis_host,cdc_ether,ax88179_178a, Live 0xffffffffc04a7000
mii 3427 2 ax88179_178a,usbnet, Live 0xffffffffc04a3000
rtsx_pci_sdmmc 8434 0 - Live 0xffffffffc049d000
rtsx_pci 24242 1 rtsx_pci_sdmmc, Live 0xffffffffc0490000
mmc_core 73734 1 rtsx_pci_sdmmc, Live 0xffffffffc0471000
fuse 65180 0 - Live 0xffffffffc0458000
snd_hda_codec_realtek 37786 1 - Live 0xffffffffc0448000
iwlmvm 99382 0 - Live 0xffffffffc03d9000
kvm_intel 119916 0 - Live 0xffffffffc033e000
snd_hda_codec_generic 39626 1 snd_hda_codec_realtek, Live 0xffffffffc032d000
mac80211 352537 1 iwlmvm, Live 0xffffffffc0239000
kvm 332678 1 kvm_intel, Live 0xffffffffc014f000
pn544_mei 1507 0 - Live 0xffffffffc014b000
mei_phy 1942 1 pn544_mei, Live 0xffffffffc0147000
iwlwifi 70257 1 iwlmvm, Live 0xffffffffc0129000
pn544 6215 1 pn544_mei, Live 0xffffffffc0124000
snd_hda_intel 29721 2 - Live 0xffffffffc0106000
hci 13343 2 mei_phy,pn544, Live 0xffffffffc00fd000
nfc 46459 2 pn544,hci, Live 0xffffffffc00c8000
snd_hda_codec 72588 3 snd_hda_codec_realtek,snd_hda_codec_generic,snd_hda_intel, Live 0xffffffffc00a7000
snd_hwdep 5373 2 snd_usb_audio,snd_hda_codec, Live 0xffffffffc009b000
cfg80211 320801 3 iwlmvm,mac80211,iwlwifi, Live 0xffffffffc001e000
xhci_hcd 88348 0 - Live 0xffffffffc0000000
/proc/iomem:
00000000-00000fff : reserved
00001000-00057fff : System RAM
00058000-00058fff : reserved
00059000-0009dfff : System RAM
0009e000-0009ffff : reserved
000a0000-000bffff : PCI Bus 0000:00
000c0000-000c3fff : PCI Bus 0000:00
000c4000-000c7fff : PCI Bus 0000:00
000c8000-000cbfff : PCI Bus 0000:00
000cc000-000cffff : PCI Bus 0000:00
000d0000-000d3fff : PCI Bus 0000:00
000d4000-000d7fff : PCI Bus 0000:00
000d8000-000dbfff : PCI Bus 0000:00
000dc000-000dffff : PCI Bus 0000:00
000f0000-000fffff : System ROM
00100000-ca4b7fff : System RAM
06000000-066753ba : Kernel code
066753bb-06cc83ff : Kernel data
06dc9000-06ecffff : Kernel bss
ca4b8000-ca4befff : ACPI Non-volatile Storage
ca4bf000-ca8e7fff : System RAM
ca8e8000-cac39fff : reserved
cac3a000-da89bfff : System RAM
da89c000-dab3ffff : reserved
dab40000-dab55fff : ACPI Tables
dab56000-dbaaafff : ACPI Non-volatile Storage
dbaab000-dbffefff : reserved
dbfff000-dbffffff : System RAM
dd000000-df1fffff : reserved
dd200000-df1fffff : Graphics Stolen Memory
df200000-feafffff : PCI Bus 0000:00
df200000-df3fffff : PCI Bus 0000:01
e0000000-efffffff : 0000:00:02.0
e0000000-e07e8fff : BOOTFB
f0000000-f09fffff : PCI Bus 0000:03
f0a00000-f13fffff : PCI Bus 0000:02
f6400000-f67fffff : 0000:00:02.0
f6800000-f71fffff : PCI Bus 0000:03
f6800000-f680ffff : 0000:03:00.0
f6810000-f6811fff : 0000:03:00.0
f6810000-f6811fff : ahci
f7200000-f7bfffff : PCI Bus 0000:02
f7c00000-f7cfffff : PCI Bus 0000:01
f7c00000-f7c01fff : 0000:01:00.0
f7c00000-f7c01fff : iwlwifi
f7d00000-f7d0ffff : 0000:00:14.0
f7d00000-f7d0ffff : xhci_hcd
f7d10000-f7d13fff : 0000:00:1b.0
f7d10000-f7d13fff : ICH HD audio
f7d14000-f7d17fff : 0000:00:03.0
f7d19000-f7d190ff : 0000:00:1f.3
f7d1a000-f7d1a3ff : 0000:00:1d.0
f7d1a000-f7d1a3ff : ehci_hcd
f7d1c000-f7d1c01f : 0000:00:16.0
f7d1c000-f7d1c01f : mei_me
f7fef000-f7feffff : pnp 00:0a
f7ff0000-f7ffffff : pnp 00:0a
f8000000-fbffffff : PCI MMCONFIG 0000 [bus 00-3f]
f8000000-fbffffff : reserved
f8000000-fbffffff : pnp 00:0a
fec00000-fec00fff : reserved
fec00000-fec003ff : IOAPIC 0
fed00000-fed03fff : reserved
fed00000-fed003ff : HPET 0
fed10000-fed17fff : pnp 00:0a
fed18000-fed18fff : pnp 00:0a
fed19000-fed19fff : pnp 00:0a
fed1c000-fed1ffff : reserved
fed1c000-fed1ffff : pnp 00:0a
fed1f410-fed1f414 : iTCO_wdt
fed1f410-fed1f414 : iTCO_wdt
fed20000-fed3ffff : pnp 00:0a
fed45000-fed8ffff : pnp 00:0a
fed90000-fed93fff : pnp 00:0a
fee00000-fee00fff : Local APIC
fee00000-fee00fff : reserved
ff000000-ffffffff : reserved
ff000000-ffffffff : pnp 00:0a
100000000-21fdfffff : System RAM
21fe00000-21fffffff : RAM buffer
/proc/ioports:
0000-0cf7 : PCI Bus 0000:00
0000-001f : dma1
0020-0021 : pic1
0040-0043 : timer0
0050-0053 : timer1
0060-0060 : keyboard
0062-0062 : EC data
0064-0064 : keyboard
0066-0066 : EC cmd
0070-0077 : rtc0
0080-008f : dma page reg
00a0-00a1 : pic2
00c0-00df : dma2
00f0-00ff : fpu
04d0-04d1 : pnp 00:07
0680-069f : pnp 00:04
0cf8-0cff : PCI conf1
0d00-ffff : PCI Bus 0000:00
164e-164f : pnp 00:04
1800-1803 : ACPI PM1a_EVT_BLK
1804-1805 : ACPI PM1a_CNT_BLK
1808-180b : ACPI PM_TMR
1810-1815 : ACPI CPU throttle
1830-1833 : iTCO_wdt
1830-1833 : iTCO_wdt
1850-1850 : ACPI PM2_CNT_BLK
1854-1857 : pnp 00:06
1860-187f : iTCO_wdt
1860-187f : iTCO_wdt
1880-189f : ACPI GPE0_BLK
1c00-1cfe : pnp 00:04
1d00-1dfe : pnp 00:04
1e00-1efe : pnp 00:04
1f00-1ffe : pnp 00:04
2008-200b : pnp 00:04
3000-3fff : PCI Bus 0000:01
d000-dfff : PCI Bus 0000:03
e000-efff : PCI Bus 0000:02
f000-f03f : 0000:00:02.0
f040-f05f : 0000:00:1f.3
ffff-ffff : pnp 00:04
ffff-ffff : pnp 00:04
Regards,
Thomas -
ORA-03113: end-of-file on communication channel
Hi
While I startup Oracle database, i get the following error. What could be the issue and how to resolve this.
SQL> startup
ORACLE instance started.
Total System Global Area 864333824 bytes
Fixed Size 2231368 bytes
Variable Size 704644024 bytes
Database Buffers 150994944 bytes
Redo Buffers 6463488 bytes
Database mounted.
ORA-03113: end-of-file on communication channel
Process ID: 6507
Session ID: 580 Serial number: 5
Below is the content from alert log and trace log
*#alert_orcl.log#*
Bad header found during crash/instance recovery
Reading datafile '+DATA/orcl/datafile/sysaux.257.762570243' for corruption at rdba: 0x0080f01b (file 2, block 61467)
Data in bad block:
type: 255 format: 2 rdba: 0x0000a2ff
last change scn: 0x0000.0080019f seq: 0x0 flg: 0x00
spare1: 0x0 spare2: 0x0 spare3: 0x4ff
consistency value in tail: 0x643e0346
check value in block header: 0x0
Read datafile mirror 'ASM5' (file 2, block 61467) found same corrupt data (no logical check)
block checksum disabled
Reading datafile '+DATA/orcl/datafile/sysaux.257.762570243' for corruption at rdba: 0x0080019f (file 2, block 415)
Read datafile mirror 'ASM4' (file 2, block 415) found same corrupt data (no logical check)
Read datafile mirror 'ASM1' (file 2, block 61467) found same corrupt data (no logical check)
Hex dump of (file 2, block 34539) in trace file /appl/oracle/diag/rdbms/orcl/orcl/trace/orcl_p000_6831.trc
Corrupt block relative dba: 0x008086eb (file 2, block 34539)
Bad header found during crash/instance recovery
Data in bad block:
type: 1 format: 6 rdba: 0x0000a201
last change scn: 0x0000.008086eb seq: 0x0 flg: 0x00
Read datafile mirror 'ASM3' (file 2, block 415) found same corrupt data (no logical check)
spare1: 0xbb spare2: 0xe1 spare3: 0x4ff
consistency value in tail: 0x02c20304
check value in block header: 0x0
block checksum disabled
Reading datafile '+DATA/orcl/datafile/sysaux.257.762570243' for corruption at rdba: 0x008086eb (file 2, block 34539)
Read datafile mirror 'ASM2' (file 2, block 34539) found same corrupt data (no logical check)
Hex dump of (file 2, block 420) in trace file /appl/oracle/diag/rdbms/orcl/orcl/trace/orcl_p002_6839.trc
Corrupt block relative dba: 0x008001a4 (file 2, block 420)
Bad header found during crash/instance recovery
Data in bad block:
type: 255 format: 2 rdba: 0x0000a206
last change scn: 0xe1f3.008001a4 seq: 0x74 flg: 0x00
spare1: 0x0 spare2: 0x0 spare3: 0x401
consistency value in tail: 0x474f4c20
check value in block header: 0x0
block checksum disabled
Reading datafile '+DATA/orcl/datafile/sysaux.257.762570243' for corruption at rdba: 0x008001a4 (file 2, block 420)
Read datafile mirror 'ASM4' (file 2, block 420) found same corrupt data (no logical check)
Read datafile mirror 'ASM1' (file 2, block 34539) found same corrupt data (no logical check)
Read datafile mirror 'ASM3' (file 2, block 420) found same corrupt data (no logical check)
Hex dump of (file 1, block 3097) in trace file /appl/oracle/diag/rdbms/orcl/orcl/trace/orcl_p002_6839.trc
Corrupt block relative dba: 0x00400c19 (file 1, block 3097)
Bad header found during crash/instance recovery
Data in bad block:
type: 2 format: 6 rdba: 0x0000a202
last change scn: 0x0000.00400c19 seq: 0x0 flg: 0x00
spare1: 0xdf spare2: 0xe2 spare3: 0x4ff
consistency value in tail: 0x09c10280
check value in block header: 0x0
Hex dump of (file 2, block 34765) in trace file /appl/oracle/diag/rdbms/orcl/orcl/trace/orcl_p000_6831.trc block checksum disabled
Corrupt block relative dba: 0x008087cd (file 2, block 34765)
Reading datafile '+DATA/orcl/datafile/system.256.762570243' for corruption at rdba: 0x00400c19 (file 1, block 3097)
Bad header found during crash/instance recovery
Data in bad block:
type: 255 format: 1 rdba: 0x0000a206
last change scn: 0xe27b.008087cd seq: 0x74 flg: 0x00
spare1: 0x0 spare2: 0x0 spare3: 0x401
Read datafile mirror 'ASM5' (file 1, block 3097) found same corrupt data (no logical check)
consistency value in tail: 0x00000000
check value in block header: 0x0
block checksum disabled
Reading datafile '+DATA/orcl/datafile/sysaux.257.762570243' for corruption at rdba: 0x008087cd (file 2, block 34765)
Read datafile mirror 'ASM3' (file 2, block 34765) found same corrupt data (no logical check)
Read datafile mirror 'ASM2' (file 1, block 3097) found same corrupt data (no logical check)
Hex dump of (file 3, block 272) in trace file /appl/oracle/diag/rdbms/orcl/orcl/trace/orcl_p002_6839.trc
Reading datafile '+DATA/orcl/datafile/undotbs1.258.762570243' for corruption at rdba: 0x00c00110 (file 3, block 272)
Read datafile mirror 'ASM1' (file 3, block 272) found same corrupt data (logically corrupt)
Read datafile mirror 'ASM5' (file 2, block 34765) found same corrupt data (no logical check)
Hex dump of (file 2, block 34771) in trace file /appl/oracle/diag/rdbms/orcl/orcl/trace/orcl_p000_6831.trc
Corrupt block relative dba: 0x008087d3 (file 2, block 34771)
Bad header found during crash/instance recovery
Data in bad block:
type: 1 format: 6 rdba: 0x0000a201
last change scn: 0x0000.008087d3 seq: 0x0 flg: 0x00
spare1: 0x3a spare2: 0xe3 spare3: 0x4ff
consistency value in tail: 0x00045055
check value in block header: 0x0
block checksum disabled
Reading datafile '+DATA/orcl/datafile/sysaux.257.762570243' for corruption at rdba: 0x008087d3 (file 2, block 34771)
Read datafile mirror 'ASM3' (file 2, block 34771) found same corrupt data (no logical check)
Read datafile mirror 'ASM2' (file 3, block 272) found same corrupt data (logically corrupt)
RECOVERY OF THREAD 1 STUCK AT BLOCK 272 OF FILE 3
Read datafile mirror 'ASM5' (file 2, block 34771) found same corrupt data (no logical check)
Wed Jun 27 05:49:55 2012
Hex dump of (file 2, block 65353) in trace file /appl/oracle/diag/rdbms/orcl/orcl/trace/orcl_dbw0_6713.trc
Corrupt block relative dba: 0x0080ff49 (file 2, block 65353)
Bad header found during buffer corrupt after write
Data in bad block:
type: 1 format: 6 rdba: 0x0000a206
last change scn: 0xe2bf.0080ff49 seq: 0x74 flg: 0x00
spare1: 0xf5 spare2: 0xe0 spare3: 0x602
consistency value in tail: 0x00000000
check value in block header: 0x0
block checksum disabled
Reread of rdba: 0x0080ff49 (file 2, block 65353) found different data
Hex dump of (file 2, block 65356) in trace file /appl/oracle/diag/rdbms/orcl/orcl/trace/orcl_dbw0_6713.trc
Corrupt block relative dba: 0x0080ff4c (file 2, block 65356)
Bad header found during buffer corrupt after write
Data in bad block:
type: 2 format: 6 rdba: 0x0000a206
last change scn: 0xe2a7.0080ff4c seq: 0x74 flg: 0x00
spare1: 0xbf spare2: 0xe2 spare3: 0x602
consistency value in tail: 0x00000059
check value in block header: 0x0
block checksum disabled
Reread of rdba: 0x0080ff4c (file 2, block 65356) found different data
Hex dump of (file 2, block 66114) in trace file /appl/oracle/diag/rdbms/orcl/orcl/trace/orcl_dbw0_6713.trc
Corrupt block relative dba: 0x00810242 (file 2, block 66114)
Bad header found during preparing block for write
Data in bad block:
type: 255 format: 1 rdba: 0x0000a206
last change scn: 0xe1bb.00810242 seq: 0x74 flg: 0x00
spare1: 0x0 spare2: 0x0 spare3: 0x401
consistency value in tail: 0x800102c1
check value in block header: 0x0
block checksum disabled
Errors in file /appl/oracle/diag/rdbms/orcl/orcl/trace/orcl_dbw0_6713.trc (incident=292893):
ORA-00600: internal error code, arguments: [kcbzpbuf_1], [4], [1], [], [], [], [], [], [], [], [], []
Incident details in: /appl/oracle/diag/rdbms/orcl/orcl/incident/incdir_292893/orcl_dbw0_6713_i292893.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Exception [type: SIGBUS, Non-existent physical address] [ADDR:0x72BFFFF8] [PC:0x3612E7CAE9, _wordcopy_bwd_dest_aligned()+185] [flags: 0x0, count: 1]
Errors in file /appl/oracle/diag/rdbms/orcl/orcl/trace/orcl_p000_6831.trc (incident=293021):
ORA-07445: exception encountered: core dump [_wordcopy_bwd_dest_aligned()+185] [SIGBUS] [ADDR:0x72BFFFF8] [PC:0x3612E7CAE9] [Non-existent physical address] []
Incident details in: /appl/oracle/diag/rdbms/orcl/orcl/incident/incdir_293021/orcl_p000_6831_i293021.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Exception [type: SIGSEGV, SI_KERNEL(general_protection)] [ADDR:0x0] [PC:0x546B040, kcbs_dump_adv_state()+634] [flags: 0x0, count: 2]
Wed Jun 27 05:49:59 2012
Dumping diagnostic data in directory=[cdmp_20120627054959], requested by (instance=1, osid=6831 (P000)), summary=[incident=293021].
Errors in file /appl/oracle/diag/rdbms/orcl/orcl/trace/orcl_p000_6831.trc (incident=293022):
ORA-07445: exception encountered: core dump [kcbs_dump_adv_state()+634] [SIGSEGV] [ADDR:0x0] [PC:0x546B040] [SI_KERNEL(general_protection)] []
ORA-07445: exception encountered: core dump [_wordcopy_bwd_dest_aligned()+185] [SIGBUS] [ADDR:0x72BFFFF8] [PC:0x3612E7CAE9] [Non-existent physical address] []
Incident details in: /appl/oracle/diag/rdbms/orcl/orcl/incident/incdir_293022/orcl_p000_6831_i293022.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Exception [type: SIGSEGV, SI_KERNEL(general_protection)] [ADDR:0x0] [PC:0x546B040, kcbs_dump_adv_state()+634] [flags: 0x0, count: 1]
Errors in file /appl/oracle/diag/rdbms/orcl/orcl/incident/incdir_293021/orcl_p000_6831_i293021.trc:
ORA-00607: Internal error occurred while making a change to a data block
ORA-00602: internal programming exception
ORA-07445: exception encountered: core dump [kcbs_dump_adv_state()+634] [SIGSEGV] [ADDR:0x0] [PC:0x546B040] [SI_KERNEL(general_protection)] []
ORA-07445: exception encountered: core dump [_wordcopy_bwd_dest_aligned()+185] [SIGBUS] [ADDR:0x72BFFFF8] [PC:0x3612E7CAE9] [Non-existent physical address] []
Errors in file /appl/oracle/diag/rdbms/orcl/orcl/trace/orcl_dbw0_6713.trc (incident=292894):
ORA-07445: exception encountered: core dump [kcbs_dump_adv_state()+634] [SIGSEGV] [ADDR:0x0] [PC:0x546B040] [SI_KERNEL(general_protection)] []
ORA-00600: internal error code, arguments: [kcbzpbuf_1], [4], [1], [], [], [], [], [], [], [], [], []
Incident details in: /appl/oracle/diag/rdbms/orcl/orcl/incident/incdir_292894/orcl_dbw0_6713_i292894.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Dumping diagnostic data in directory=[cdmp_20120627055004], requested by (instance=1, osid=6713 (DBW0)), summary=[incident=292893].
Wed Jun 27 05:50:08 2012
PMON (ospid: 6679): terminating the instance due to error 471
Wed Jun 27 05:50:08 2012
ORA-1092 : opitsk aborting process
Wed Jun 27 05:50:08 2012
License high water mark = 4
Instance terminated by PMON, pid = 6679
USER (ospid: 6860): terminating the instance
Instance terminated by USER, pid = 6860
*#trace logs#*
Corrupt block relative dba: 0x00810242 (file 2, block 66114)
Bad header found during preparing block for write
Data in bad block:
type: 255 format: 1 rdba: 0x0000a206
last change scn: 0xe1bb.00810242 seq: 0x74 flg: 0x00
spare1: 0x0 spare2: 0x0 spare3: 0x401
consistency value in tail: 0x800102c1
check value in block header: 0x0
block checksum disabled
kcra_dump_redo_internal: skipped for critical process
kcbz_try_block_recovery <1, 8454722>: tries=0 max=5 cur=1340797795 last=0
BH (0x7bbe0fc8) file#: 2 rdba: 0x00810242 (2/66114) class: 1 ba: 0x7b8f4000
set: 12 pool: 3 bsz: 8192 bsi: 0 sflg: 2 pwc: 0,0
dbwrid: 0 obj: 68150 objn: -1 tsn: 1 afn: 2 hint: f
hash: [0x912f45b0,0x912f45b0] lru-req: [0x7bbdfdb0,0x90deff60]
lru-flags: on_auxiliary_list
obj-flags: object_write_list
ckptq: [0x7bbfc4c8,0x7bbea0a8] fileq: [NULL] objq: [0x8b251480,0x8b251480] objaq: [0x8b251450,0x7bbe0e88]
st: INST_RCV md: NULL rsop: 0x90d110e0
flags: buffer_dirty being_written block_written_once recovery_resilver
recovery_read_complete
cr pin refcnt: 0 sh pin refcnt: 0
kcra_dump_redo_internal: skipped for critical process
Incident 292893 created, dump file: /appl/oracle/diag/rdbms/orcl/orcl/incident/incdir_292893/orcl_dbw0_6713_i292893.trc
ORA-00600: internal error code, arguments: [kcbzpbuf_1], [4], [1], [], [], [], [], [], [], [], [], []
Incident 292894 created, dump file: /appl/oracle/diag/rdbms/orcl/orcl/incident/incdir_292894/orcl_dbw0_6713_i292894.trc
ORA-07445: exception encountered: core dump [kcbs_dump_adv_state()+634] [SIGSEGV] [ADDR:0x0] [PC:0x546B040] [SI_KERNEL(general_protection)] []
ORA-00600: internal error code, arguments: [kcbzpbuf_1], [4], [1], [], [], [], [], [], [], [], [], []Did you actually read the alert-log ??
The problem is clear in there. Your datafiles are corrupted!!!
While the database is trying to correct these, a lot of ORA-00600 and ORA-07445's are generated.
Consult Oracle Support to get this resolved
Thanks
FJFranken -
Oracle service terminated unexpectedly -
Good Morning everyone,
I came in this morning and encountered our production database has crashed. We are running Oracle 10G 10.2.0.1 on Windows 2003 R2 Server.
The OS system log just reports the service terminated unexpectedly. With no other information in the lower data box.
Looking in the alert log points to this trace file 3 times and ends.
Tue Feb 03 07:15:53 2009
Errors in file c:\oracle\admin\ptmn\udump\ptmn_ora_2980.trc:
ORA-00600: internal error code, arguments: [kssadpm: null parent], [], [], [], [], [], [], []
ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [unable_to_trans_pc] [PC:0x7FF773113D4] [ADDR:0x0] [UNABLE_TO_WRITE] []
This is what I have in each trace file.
Dump file c:\oracle\admin\ptmn\udump\ptmn_ora_2980.trc
Tue Feb 03 07:15:52 2009
ORACLE V10.2.0.1.0 - 64bit Production vsnsta=0
vsnsql=14 vsnxtr=3
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
Windows Server 2003 Version V5.2 Service Pack 2
CPU : 8 - type 8664, 2 Physical Cores
Process Affinity : 0x0000000000000000
Memory (Avail/Total): Ph:20525M/32767M, Ph+PgF:20903M/33873M
Instance name: ptmn
Redo thread mounted by this instance: 1
Oracle process number: 230
Windows thread id: 2980, image: ORACLE.EXE (SHAD)
*** SERVICE NAME:(ptmn.world) 2009-02-03 07:15:52.923
*** SESSION ID:(1329.1631) 2009-02-03 07:15:52.923
*** 2009-02-03 07:15:52.923
ksedmp: internal or fatal error
ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [unable_to_trans_pc] [PC:0x7FF773113D4] [ADDR:0x0] [UNABLE_TO_WRITE] []
Current SQL statement for this session:
ALTER SESSION SET CURRENT_SCHEMA = PROD
----- Call Stack Trace -----
After calling around a bit I discovered that a developer in an outter office ran a massive select query against the database.
He said it he ran it once it failed, twice it failed, and a 3rd time it failed. According the the alert log, after this 3rd time the
database crashed.
All I'm wanting to know is why did it crash, did the developer use all the os/oracle resources doing this? Any insight would be much appreciated.
To prevent this from happening again he's been restricted to TEST database resources only :)
Thank you all for your time and service :)
Edited by: Steve Baker on Feb 3, 2009 6:37 AM
Edited by: Steve Baker on Feb 3, 2009 6:38 AMSatish, Thank you for the fast response!
Looking over the solutuions on this document
Ensure that the existing memory is functioning properly. - It's fine, ran a memory sys test on it
If there is no hardware issue, then you have simply run out of available memory and you need to purchase more. This server has 32GB and this oracle DB is allocated 7GB
Check your OS log for hardware errors. none in the event viewer logs
I'm thinking he just ran the instance out of memory some how. I also should mention the is another database instance running on
this server, and it has remained fine during all these issues this morning. So it's gotta be something to do with that instance.
I'll increase the memory for the PTMN (crashed) instance.
Possible look into setting some resource limits for the developers on this database.
Thank you again for the information. I do appreciate it. -
Oracle 9.2.0.4/AMD64 on SLES9/x86-64
Hello!
I just tried to install Oracle 9.2.0.4/AMD64 to SLES9.
It hangs during install:
runInstaller says :
Installing Oracle required support files 32 bit 9.2.0.1.0
link pending
copying naeet.o
And it stays forever.
I see in log:
java.lang.UnsatisfiedLinkError: /tmp/OraInstall2004-08-09_03-16-54PM/libactionUn
no, version GLIBC_2.0 not defined in file libc.so.6 with link time reference
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1560)
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1456)
at java.lang.Runtime.load0(Runtime.java:737)
at java.lang.System.load(System.java:811)
at ssOiGenClassux22.<clinit>(ssOiGenClassux22.java:25)
at sstouchFileux.touchFile(sstouchFileux.java:135)
at sstouchFileux.installAction(sstouchFileux.java:65)
at oracle.sysman.oii.oiis.OiisCompActions.doActionWithException(OiisComp
at oracle.sysman.oii.oiis.OiisCompActions.doActionImpl(OiisCompActions.j
at oracle.sysman.oii.oiis.OiisCompActions.doAction(OiisCompActions.java:
at Components.oracle.rsf.hybrid.v9_2_0_1_0.CompActions.doAction(Unknown
at Components.oracle.rsf.hybrid.v9_2_0_1_0.CompInstallPhase1.doActionP1t
at Components.oracle.rsf.hybrid.v9_2_0_1_0.CompInstallPhase1.stateChange
at Components.oracle.rsf.hybrid.v9_2_0_1_0.CompActions.stateChangeAction
at oracle.sysman.oii.oiic.OiicInstallActionsPhase$OiilActionThr.run(Oiic
at oracle.sysman.oii.oiic.OiicInstallActionsPhase.executeProductPhases(O
at oracle.sysman.oii.oiic.OiicInstallActionsPhase.doInstalls(OiicInstall
at oracle.sysman.oii.oiic.OiicInstallActionsPhase$OiInstRun.run(OiicInst
at java.lang.Thread.run(Thread.java:534)
Any ideas?
Previously I installed Oracle on Mandrake 9.2/AMD64 without problemsI had a successfull installation without relinking problems using the orarun.rpm from SLES8.
My system is a Tyan Dual Opteron S2882 with 4GB memory.
I commented out the gcc_old reference in the PATH variable from /etc/profile.d/oracle.sh and added $ORACLE_HOME/lib32 reference to the LD_LIBRARY_PATH there(maybe not needed, I didn't test it without)
Even "relink all" did work.
I only got an error message at the installation of Oracle Text (some missing quote in a script)
The rest was smooth.
Allocation of more than 2 GB SGA worked fine.
But I didn't get the oemapp GUI application. Is it missing in the 9.2.0.4 AMD64 Kit or is there a java problem in runInstaller ?
Creating a database and import of a database worked.
Changing filesystem_io_options to anything else than "none" results in a crashing instance (ext3 Filesystem). -
dear dba,
i'm using oracle 11gR2 database in ARCHIVELOG mode in windows server 2003R2.
when we take an offlinebackup, i need clear idea about,
1. what happens internally ie,in architecture level
2. whether the archive logs are backed up or not
3. in which senario we have to use offline backups
thanks & regards,
JOhn Marshal.A895689 wrote:
if i manually copy that all archive logs means can we use that file for recoveryWhat do you mean by offline backup , an offline backup could be done by database shutting in immediate,normal,transactional or abort mode,with normal,transactionasl and immediate mode database down , archivelog bakcup is useless,when you do shutdown immediate alls the memory cache (i.e data buffer cache, log buffer cache) writes the data to database files (datafile,controlfiles etc), shutdown immediate terminates all active transactions ,roll back them ,trigger a checkpoint where oracle makes the control files and datafiles consistent to the same checkpoint SCN.I believe you know what is checkpoint? Its useless to take archivelog backup when you have offline backup with database down in consistent mode (shutdown immediate/normal/transactionl) not in inconsistent mode like (shutdown abort).
Archivelog backup is necessary when you have an inconsistent backup , more precisely say redo is necessary when you have an inconsistent backup or there would be required crash/instance/media recovery.Aechivelogs is an archive of redos and redos are the transaction logs of yours database , it is exactly a recorder of yours database activity ,by using redo logs i can take my database to a particular state, for further detail lets take an example which i have given here as before.
Suppose i have three disk (disk1,disk2 and disk3),i have one datafile in my database which is f1.dbf on my disk1,i have 2 redo log file i.e r1.log and r2.log which are on disk2.At disk3 i copy my database file f1.dbf from disk1 daily at 12:00 PM. On Monday i have successfully copied the f1.dbf file from disk1 to disk3 at 12:00 PM , at 1 PM on monday i insert some record in a table "test".
Insert into test values (1)
It means on monday at 1:00 PM within my datafile f1.dbf i have modified a block and this block contain the record of table test (1 values) , at 1:00 PM if you compare datafile f1.dbf at disk1 from disk3 , you will find only that f1.dbf will contain a new record of test table with values 1 but this will not be within backed up datafile f1.dbf at disk3 . At disk2 r1.log contain those record which i inserted on monday at 1:00 PM, it means i have redo (transactions log) of this datafile f1.dbf within r1.log, i can redo (again inserting) that record from redo log r1.log which i have done at 1:00 PM.
Suppose at 2 PM on monday my disk1 smoked out , if disk1 smoked out f1.dbf has been also smoked out , then what will i do , i will put a new hard disk disk4 and will copy the database file f1.dbf from backup disk3 , this f1.dbf would not have record of "Insert into test values (1)" which occured after backup at 1:00 PM.After coping f1.dbf to new hard disk disk4 i will start reading and applying my redo log file r1.log after 12:00 PM which contain the (redo entry i.e redo vectors) "insert into test values (1)" to my new restored file f1.dbf at new disk4 , in short it is going to replay from recorder of my transactions log (r1.log) and after applying the redo from r1.log i will have exact data before crashing the hard disk1 at 2:00 PM.The only purpose of redo log file in this scenario is to recover the database in case of media failure , if i do not have r1.log then i can only recover my database till 12:00 PM which was copied from disk1 to disk3 but this recovered backup file does not have entry of "insert into test values (1)", i can only bring back my database to before failure current backup at 12:00 PM not just exact before the failure.
You may think why the wastage of three disk for one information , one is at disk1 (f1.dbf),another one is at disk2 (r1.log) and last one is at disk3 for coping f1.dbf from disk1.You may think that it is ok with two disk (disk1 and disk3) why do we need another storage area for r1.log , basically r1.log is the transactions log until between yours current backup to the next backup.It does not contain the whole redo (transaction logs) of yours database but have information (transaction log) till yours next backup which is going to be start on next day tuesday at 12:00 PM ,when it gets filled it is switched to another redo log r2.log, when r2.log is filled then it switched back to r1.log , it overwrites whatever written at 12:00 PM "insert into test values (1)" with new database transactions , for the safety of this overcome this redo is archived and keep save till yours next backup.Redo log switching depneds on yours database transaction pace and its size, the more database activity the quickest redo filling and in turn redo log switching.
Thats all why we need redo and archived log files, as far as the data from redo logs can be directly written to Datafiles is wrong , whenever you do any activity i.e DML , this DML modify the two block one is in within DB buffer cache another one in redo buffer cache , at every 3 seconds or 1/3 filing of redo buffer or commit occurs whichever occur first LGWR write transactions log from redo buffer to online redo log file.
DBWR writes data (dirty buffer) from database buffer cache when checkpoint occurs (checkpointing a process which updates alls datafile headers with the SCN) before Oracle 8.0 it was LGWR which does the job of CKPT to update alls datafile header with SCN , but after Oracle 8.0 CKPT is now responsible to do this activity cause LGWR already keep involved in writing redo buffer data to redo log file.
Khurram -
SQL Server 2012 Reorg Index Job Blew up the Log File
We have a maintenance plan that nightly (1) runs dbcc checkdb on all databases, (2) reorgs indexes on all databases, compacting large objects, (3) updates statistics, etc. There are three user databases, one large, one medium, one small. Usually it uses
a little more than 80% of the medium database's log, set to 6,700 MB. Last night the reorg index step caused the log to increase to almost 14,000 MB and then blew up because the maximum file size was set to 14,000 MB, one of the alter index commands failed
because it ran out of log space. (Dbcc checkdb step ran successfully.) Anyone have any idea what might cause this? There is one update process on this database, it runs at 3 AM. The maintenance plan runs at 9 PM and completes by 1 AM. The medium database has
a 21,000 MB data file, reserved space is at about 10 GB. This is a SQL 2012 Standard SP 2 running on Windows 2012 Server Standard.I personally like to shrink the log files once the indexes have been rebuilt and before switching back to full recovery, because as I'm going to take a full backup afterwards, having a small log file reduces the size of the backup.
Do you grow them afterwards, or do you let the application waste time on that during peak hours?
I have not checked, but I see no reason why the backup size would depend on the size of the log file - it's the data in the data file you back up, not the log file.
I would say this is highly dubious.
Erland Sommarskog, SQL Server MVP, [email protected]
Yeah I let the application allegedly "waste" a few milisseconds a day autogrowing the log file. Common, how long do you think it takes for a log file to grow a few GB on most storage systems nowadays? As long as you set an appropriate autogrow
interval so your log file doesn't get too fragmented (full of VLFs), you'll be perfectly fine in most situations.
Lets say you have a logical disk dedicated to log file storage, but it is shared across multiple databases within the instance. Having allocated space for the log files means there will be not much free space left in the disk in case ANY database needs more
space than the others due to a peak in transactional workload, even though other databases have unused space that could have been used.
What if this same disk, for some reason, is also used to store the tempdb log file? Then all applications will become unstable.
These are the main reasons I don't recommend people blindly crucify keeping log files small when possible. I know there are many people who disagree and I'm aware of their reasons. Maybe we just had different experiences about this subject. Maybe people
just haven't been through the nightmare of having a corrupted system database or a crashed instance because of insuficient log space in the middle of the day.
And you are right about the size of the backup, I didn't put it correctly. It isn't the size of the backup that gets smaller (although the backup operation will run faster, having tested this myself), but the benefit from backing up a database with a small
log file is that you won't need the extra space to restore it in a different environment such as a BI or DEV server, where recuperability doesn't matter and the database will be on simple recovery mode.
Restoring the database will also be faster.
Just because there are clouds in the sky it doesn't mean it isn't blue. But someone will come and argue that in addition to clouds, birds, airplanes, pollution, sunsets, daltonism and nuclear bombs, all adding different colours to the sky, this
is an undocumented behavior and should not be relied upon. -
제품 : ORACLE SERVER
작성날짜 : 2004-08-16
ORACLE8 OPS BACKUP & RECOVERY
=============================
SCOPE
Standard Edition 에서는 Real Application Clusters 기능이 10g(10.1.0) 이상 부터 지원이 됩니다.
Explanation
OPS에서의 database backup & recovery 방법은 single instance의 backup 방법과
비슷하다. 즉, Single instance에서의 모든 backup 방법은 ops에서도 지원된다.
1. Backup 방법
다음의 backup 방법 모두 사용이 가능하다. 여기서는 2)의 os 명령을 이용한
backup 방법에 대해 기술합니다.
1) Recovery Manager (RMAN) : <Bulletin 11451> 참고
2) OS 명령을 활용한 백업
Noarchive log mode : full offline backup only
Archive log mode : full or partial, offline or online backup
3) export : <Bulletin 10080> 참고 : ORACLE 7 BACKUP 및 RECOVERY 방법
2. backup 정책 수립 시 고려 사항
1) disk crash나 user error 등으로 말미암은 손실을 허용하지 않는다면 ARCHIVE
LOG MODE를 사용해야 한다.
2) 대부분 모든 instance는 자동 archiving을 사용한다.
3) 모든 data backup 작업이 어떤 instance 건 가능하다.
4) media recovery 시 모든 thread의 archive file이 사용된다.
5) Instance recovery 시 살아있는 instance의 smon에 의해 자동으로 recovery된다.
3. Noarchive log mode : Full offline backup
1) 다음의 view들을 query하여 backup이 필요한 file을 알아낸다.
V$DATAFILE or DBA_DATA_FILES
V$LOGFILE
V$CONTROLFILE
2) 모든 instance를 shutdown한다.
3) 확인된 file을 backup destination으로 copy한다.
4. Archive log mode : Partial or Full Online Backup
1) 백업을 수행하기 전에 ALTER SYSTEM ARCHIVE LOG CURRENT 명령 실행(이 명령을
실행하여 현재 운영되지 않는 데이터베이스를 포함한 모든 노드의 current redo
log에 대한 로그 스위치와 그에 따른 아카이브를 모든 인스턴스에서 실행시킨다.)
2) ALTER TABLESPACE tablespace BEGIN BACKUP 명령 실행
3) ALTER TABLESPACE 명령이 성공적을 실행될 때까지 대기
4) OS에서 적절한 명령어를 활용하여 테이블스페이스에 속하는 데이터파일들을 백업
(tar, cpio, cp 등)
5) OS 명령을 활용한 백업이 다 끝날 때까지 대기
6) ALTER TABLESPACE tablespace END BACKUP 명령 수행
7) ALTER DATABASE BACKUP CONTROLFILE TO filename 이나
ALTER DATABASE BACKUP CONTROLFILE TO TRACE
명령을 수행시켜 컨트롤 파일을 백업.
만약 아카이브 로그 파일을 백업받는다면 END BACKUP 명령을 실행시킨 이후
ALTER SYSTEM ARCHIVE LOG CURRENT 명령을 실행시켜 END BACKUP 시점까지의
모든 리두 로그 파일들을 확보한다.
5. Import Parameter
1) Controlfile 내의 Redo Log History (MAXLOGHISTORY )
CREATE DATABASE 명령이나 CREATE CONTROLFILE 명령에서 MAXLOGHISTORY 값을
지정하여 parallel server에서 다 채워진 리두 로그 파일에 대한 history를
컨트롤 파일이 저장하도록 할 수 있다. 이미 데이터베이스를 생성한 후라면
log history 값을 증가시키거나 감소시키기 위해서는 컨트롤 파일을 재생성
하여야만 한다.
MAXLOGHISTORY는 컨트롤 파일 내의 archive history를 얼마나 저장할 수
있는지를 지정하며, 기본값은 플랫폼 별로 다르다. 이 값이 0이 아닌 다른
값으로 지정된다면 log switch가 발생할 때마다 LGWR 프로세스에서는 컨트롤
파일에 다음 정보를 기록한다.
thread number, log sequence number, low SCN, low SCN timestamp, next SCN
(next log의 가장 낮은 SCN값)
(이 정보는 리두 로그 파일이 archive된 후가 아니라 log switch가 발생할 때
컨트롤 파일에 저장된다.)
MAXLOGHISTORY 값에서 지정한 값을 넘어서 log history가 저장되어야 할 경우
가장 오래된 history를 overwrite하는 방식으로 저장된다. Log history 정보는
OPS에서 자동 media recovery 시 SCN, thread number를 기준으로 적절한
아카이브 로그 파일을 찾아 재구성하는 데 사용된다. 데이터베이스를 exclusive
모드에서 한개의 쓰레드만 사용하는 환경에서는 log history 정보가 필요하지 않다.
Log history 관련 정보는 V$LOG_HISTORY를 이용해 조회해 볼 수 있다.
서버 관리자에서 V$RECOVERY_LOG를 조회하면 media recovery에 필요한 아카이브
로그에 대한 정보를 얻을 수 있다.
Multiplex된 리두 로그 파일에 대해서, log history 내에서 여러개의 entry가
사용되지 않는다. 각각의 entry는 개개의 파일에 대한 정보가 아니라, multiplex
된 log 파일의 그룹에 대한 정보를 가지고 있다.
2) Archive Log Mode 시 Parameter
OPS에서 archive log mode로 변경 시 exclusive mode로 db mount 후에 변경한다.
a. LOG_ARCHIVE_FORMAT
파라미터 설명 예
%T thread number, left-zero-padded arch0000000001
%t thread number, not padded arch1
%S log sequence number, left-zero-padded arch0000000251
%s log sequence number, not padded arch251
이 가운데 %T와 %t는 OPS에서만 유효한 파라미터이다.
모든 instance의 format은 같아야 하며 OPS 환경에서는 반드시 thread 번호를
포함시켜야 한다.
예) log_archive_format = %t_%s.arc
b. LOG_ARCHIVE_START
- 자동 archiving : TRUE로 지정한 후 인스턴스를 구동시키면 background process
인 ARCH에서 자동 archiving을 수행한다. Closed Thread의 경우에는 실행 중인
thread에서 closed thread를 대신해 log switch와 archiving을 수행한다.
이것은 모든 노드에서 비슷한 SCN을 유지하도록 하기 위해 강제적으로 log switch
가 발생할 때 일어난다
- 수동 Archiving : FALSE이면 archive를 시작하도록 지시하는 명령을 명시적으로
내리지 않는 이상 동작을 멈추고 대기한다. OPS에서는 각각의 인스턴스에서 서로
다른 LOG_ARCHIVE_START 값을 사용할 수 있다.
다음과 같은 방법으로 수동 archiving을 수행할 수 있다.
ALTER SYSTEM ARCHIVE LOG SQL 명령을 실행
ALTER SYSTEM ARCHIVE LOG START 명령을 실행하여 자동 archiving을 실행하도록
지정.
수동 archiving은 명령을 실행시킨 노드에서만 실행 되며, 이 때 archiving
작업을 ARCH 프로세스가 처리하지 않는다.
c. LOG_ARCHIVE_DEST
archive log file이 만들어질 directory를 지정한다.
예) log_archive_dest = /arch2/arc
6. OPS Recovery
1) Instance Failure 시
Instance failure는 S/W나 H/W 상의 문제, 정전이나 background process에서
fail이 발생하거나, shutdown abort를 시키거나 OS crash 등 여러가지 이유로
인해 instance가 더 이상 작업을 진행할 수 없을 때 발생할 수 있다.
Single instance 환경에서는 instance failure는 instance를 restart 시키고
database를 open하여 해결된다. Mount 상태에서 open 되는 중간 단계에서 SMON은
online redo log 파일을 읽어 instance recovery 작업을 수행한다.
OPS에서는 instance failure가 발생 했을 경우 다른 방식으로 instance
recovery가 수행된다. OPS에서는 한 노드에서 fail이 발생했다고 하더라도
다른 노드의 인스턴스는 계속 운영될 수 있기 때문에 instance failure는
database가 가용하지 않다는 것을 의미하지는 않는다.
Instance recovery는 dead instance를 처음으로 발견한 SMON 프로세스에서
수행한다. Recovery가 수행되는 동안 다음과 같은 작업이 일어난다.
- Fail이 발생하지 않은 다른 인스턴스에서는 fail이 발생한 인스턴스의
redo log 파일을 읽어 들여 데이터파일에 그 내용을 적용시킨다.
- 이 기간 동안 fail이 발생하지 않은 다른 노드에서도 buffer cache 영역의
내용을 write 하지는 못한다.
- DBWR disk I/O가 일어나지 못한다.
- DML 사용자에 의해 lock request를 할 수 없다.
a. Single-node Failure
한 인스턴스에서 fail이 난 다른 인스턴스에 대한 recovery를 수행하는 동안,
정상적으로 운영 중인 인스턴스는 fail이 난 인스턴스의 redo log entry를
읽어 들어 commit이 된 트랜잭션의 결과치를 데이터베이스에 반영시킨다.
따라서 commit 된 데이터에 대한 손실은 일어나지 않으며, fail이 난
인스턴스에서 commit 시키지 않은 트랜잭션에 대해서는 rollback을 수행하고,
트랜잭션에서 사용 중이던 자원을 release시킨다.
b. Multiple-node Failure
만약 OPS의 모든 인스턴스에서 fail이 발생했을 경우, 인스턴스 recovery는
어느 한 인스턴스라도 open이 될 때 자동으로 수행된다. 이 때 open되는 인스턴스는
fail이 발생한 인스턴스가 아니라도 상관 없으며, OPS에서 shared 모드
혹은 execlusive 모드에서 데이터베이스를 mount 하더라도 상관 없이 수행된다.
오라클이 shared 모드에서 수행되던, execlusive 모드에서 수행되건,
recovery 절차는 하나의 인스턴스에서, fail이 난 모든 인스턴스에 대한
recovery를 수행하는지 여부를 제외하고는 동일하다.
2) Media Failure 시
Oracle에서 사용하는 file을 저장하는 storage media에 문제가 발생했을 경우
발생한다. 이와 같은 상황에서는 일반적으로 data에 대한 read/write가 불가능하다.
Media failure가 발생했을 경우 recovery는 single instance의 경우와
마찬가지로 recovery가 수행되어야 한다. 두 경우 모드 archive log 파일을
이용해서 transaction recovery를 수행하여야 한다.
3) Node Failure 시
OPS 환경에서, 한 노드 전체에 fail이 발생했을 때, 해당 노드에서 동작하던
instance와 IDLM 컴포넌트에서도 fail이 발생한다. 이 경우 instance recovery를
하기 위해서는 IDLM은 lock에 대한 remaster를 시키기 위해 그 자신을
reconfigure시켜야 한다.
한 노드에서 fail이 발생했을 때 Cluster Manager 또는 다른 GMS product에서는
failure를 알리고, reconfiguration을 수행하여야만 한다. 이 작업이 수행되어야만
다른 노드에서 운영 중인 LMD0 프로세스와의 통신이 가능하다.
오라클에서는 fail이 발생한 노드에서 잡고 있는 lock 정보를 access할 경우나,
LMON 프로세스에서 heartbeat을 이용해서 fail이 발생한 노드가 더 이상
가용하지 않다는 것을 감지할 때 failure가 발생한 것을 알게 된다.
IDLM에서 reconfigure가 일어나면 instance recovery가 수행된다.
Instance recovery는 recovery를 수행하는 동안 자원에 대한 contention을
피하기 위해 전체 데이터베이스의 작업을 일시 중지시킬 수 있다.
FREEZE_DB_FOR_FAST_INSTANCE_RECOVERY initialization parameter 값을
TRUE로 지정하며 전체 데이터베이스가 일시적으로 작업을 멈추게 된다.
데이터 화일에서 fine-grain lock을 사용할 경우 기본값은 TRUE이다.
이 값을 FALSE로 지정할 경우 recovery가 필요한 데이터만이 일시적으로 작업이
멈춰진다. 데이터 화일이 hash lock을 사용할 경우 FALSE가 기본 값이다.
4) IDLM failure 시
한 노드에서 다른 연관된 프로세스의 fail이나 memory fault 등의 이유로 인해
IDLM 프로세스만 fail이 발생했다면 다른 노드의 LMON에서는 이 문제를 감지하여
lock reconfiguration process를 시작한다.
이 작업이 진행 중인 동안 lock 관련 작업은 처리가 정지되고 PCM lock 또는
다른 resource를 획득하기 위해 일부 사용자들은 대기 상태로 들어간다.
5) Interconnect Failure ( GMS failure ) 시
노드 간의 interconnect에서 fail이 발생하면 각각의 노드에서는 서로 다른
노드의 IDLM과 GMS에서 fail 이 발생했다고 간주하게 된다. GMS에서는 quorum
disk나 node에 pinging 등을 수행하는 다른 방법을 통해 시스템의 상태를 확인한다.
이 경우 Fail이 발생한 connection에 대해 두 노드 혹은 한쪽 노드에서
shutdown 이 일어난다.
Oracle 8 recovery mechanism에서는 노드 혹은 인스턴스에서 강제로 fail이
발생했을 경우 IDLM이나 instance가 startup 될 수 없게 된다. 경우에 따라서는
노드 간의 IDLM communication이 가용한지 여부를 확인하기 위해 cluster
validation code를 직접 작성하여 사용할 수도 있다. 이 방법을 사용하여
GMS에서 제공하지는 않지만, 문제를 진단한 후 shutdown을 수행하도록 할 수 있다.
이같은 code를 작성하기 위해서는 단일 PCM lock에서 처리되는 단일 data block에
대해 계속해서 update 를 수행해 보는 루틴이 들어가면 된다. 서로 연결된
두 노드에서 이 프로그램을 실행시키게 될 경우 interconnect에서 fail이
난 상황을 진단할 수 있게 된다.
만약 여러개의 노드가 cluster를 구성할 경우에는 매 interconnect 마다
다른 PCM lock에 의해 처리되는 data block을 update 함으로써, 어떤 노드와의
interconnect에 문제가 발생했는지를 알아낼 수 있다.
7. Parallel Recovery
Parallel Recovery의 목표는 compute와 I/O parallelism을 사용해서 crash
recovery, single-instance recovery, media recovery 시 소요되는 시간을 줄이는
데 있다.
Parallel recovery는 여러 디스크에 걸쳐 몇 개의 데이터파일에 대해 동시에
recovery를 수행할 때 가장 효율적이다
다음과 같이 2가지 방식으로 병렬화시킬 수 있다.
- RECOVERY_PARALLELISM 파라미터 지정
- RECOVER 명령의 옵션에 지정
오라클 서버는 하나의 프로세스에서 log file을 순차적으로 읽어들이고, redo
정보를 여러 개의 recovery 프로세스에 전달해, log file에 기록된 변동 사항을
데이터파일에 적용시킬 수 있다.
Recovery Process는 오라클에서 자동적으로 구동되므로, recovery를 수행할 경우
한 개 이상의 session을 사용할 필요가 없다.
RECOVERY_PARALLELISM의 최대값은 PARALLEL_MAX_SERVERS 파라미터에 지정된 값을
초과할 수 없다.
Reference Ducumment
Oracle8 ops manualConfiguration files of the Oracle Application server can be backed up by "Backup and Recovery Tool"
Pls refer to the documentation,
http://download.oracle.com/docs/cd/B32110_01/core.1013/b32196/part5.htm#i436649
Also "backup to tapes feature" is not yet supported by this tool
thanks,
Murugesh
Message was edited by:
Murugesan Appukuttty -
Is anybody familiar with the HA Events and RAC?
I use a RAC with 2 instances. After shutting down the instance to which my client is connected, I would expect that the lost connection pool is recreated automatically on the surviving instance. But it isn't.
Using HA Events in the connection string, I receive a failover event on the connection after the instance shutdown. But only 6 minutes later.
6 minutes seems useless to me, maybe it relates to the connection pool management cycle which is 3 minutes according to the documentation.
After doing the failover, the connection pool is not recreated either.
e.g. if I had 3 connections on the crashed instance, I only see 1 connection after the failure (looking at v$session).
I don't think, that this is a setup or configuration problem.
Has anybody some experience on this and can tell me how the HA Events are supposed to work?
Maybe the Oracle development team can help?
Thank you.Thank you. I would exactly expect what you mentioned.
However, I observe the following behaviour
1) shutting down my instance does not re-establish new connections on the second instance. This makes make believe that my old connection stays severed.
2) re-using my connection after the shutdown still fires a failover-event on the connection. This makes me believe that this connection is still severed. After this first re-use (and after the failover event) the connection is moved to the second instance. But this is also the case if I don't use HA Events in the connection string.
3) The only difference of using HA Events in the connection string is the fact, that I receive after 6 min. a failover-event on the connection. Without HA Events I don't receive this one, but point 1) and 2) are still the same.
This makes me believe that my setup is OK.
Do you have any other hint or tip?
Thanks so much.
Regards,
Urs
Maybe you are looking for
-
Error on starting PE 12: "This is not a valid pdf file"
I get that message on opening PE 12 (for the first time-I"m a new user) and then the program freezes. I haven't done anything yet!
-
DP_How to lock KF in the interactive Planning table
Dear Expert! I want to lock the data in the Interactive Planning table according to each Key figure and a period of time (that mean I can not change the data of KF after locked). How can I do? e.g: I created a Planning book and data view with followi
-
Hello i am just trying out Arch Linux and just did a fresh install. And i trying to enable the repositories and i seem to keep running into an error everytime i type pacman or anything related it get this error error: config file /etc/pacman.conf, li
-
i need Help! My parent directory displays in the web browser. How do i get rid of this. i am pretty new to websites so any suggestions would be greatly appreciated.. THANKS
-
Error in extraction via FTP using mdmgx trx in R3
Hi, I am using SAP MDM 5.5 and use mdmgx trx for extraction in R3. When i try to start extraction via ftp (i.e Upload via FTP) in mdmgx trx, it shows me error: "<i>User <username> has no access authorization for computer <IP address></i>" I can local