IAS6sp2 / ias6sp4 on solaris 2.6 : classloader bug ?

Hi,
we here are using iAS for several projects. And, unfortunately, one day or the other, we will be running into the following problem :
Consider an application foo.ear that contains only a foo.war web application.
foo.war contains several jar in its WEB-INF/lib directory : one for the application servlets and classes, and 3rd party jars.
The application deploys well, all classes are unjared into APPS/foo/foo/WEB-INF/lib
And everything works well.
But one day i will deploy it on another iAS.
Suddenly, some of the classes, although they are present, won't be found by the classloader. Example :
********************** kjs log starts here ***********************
[23/Jan/2002 18:03:20:9] error: Exception: SERVLET-execution_failed: Error in executing servlet WebCalendarServlet: java.lang.NoClassDefFoundError: com/siris/selfcare/ihm/control/CIHMSso
Exception Stack Trace:
java.lang.NoClassDefFoundError: com/siris/selfcare/ihm/control/CIHMSso
at com.siris.selfcare.ihm.servlet.WebCalendarServlet.doGet(Unknown Source)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(Compiled Code)
at com.netscape.server.servlet.servletrunner.ServletInfo.service(Compiled Code)
at com.netscape.server.servlet.servletrunner.ServletRunner.execute(Compiled Code)
at com.kivasoft.applogic.AppLogic.execute(Compiled Code)
at com.kivasoft.applogic.AppLogic.execute(Compiled Code)
at com.kivasoft.thread.ThreadBasic.run(Native Method)
at com.kivasoft.thread.ThreadBasic.run(Native Method)
at com.kivasoft.thread.ThreadBasic.run(Native Method)
at com.kivasoft.thread.ThreadBasic.run(Native Method)
at com.kivasoft.thread.ThreadBasic.run(Compiled Code)
at java.lang.Thread.run(Compiled Code)
[23/Jan/2002 18:03:20:9] error: APPLOGIC-caught_exception: Caught Exception:
java.lang.ClassCastException: java.lang.NoClassDefFoundError
at com.netscape.server.servlet.servletrunner.ServletRunner.reportError(Compiled Code)
at com.netscape.server.servlet.servletrunner.ServletRunner.execute(Compiled Code)
at com.kivasoft.applogic.AppLogic.execute(Compiled Code)
at com.kivasoft.applogic.AppLogic.execute(Compiled Code)
at com.kivasoft.thread.ThreadBasic.run(Native Method)
at com.kivasoft.thread.ThreadBasic.run(Native Method)
at com.kivasoft.thread.ThreadBasic.run(Native Method)
at com.kivasoft.thread.ThreadBasic.run(Native Method)
at com.kivasoft.thread.ThreadBasic.run(Compiled Code)
at java.lang.Thread.run(Compiled Code)
********************** kjs log ends here ******************************
But the com/siris/selfcare/ihm/control/CIHMSso.class class is definately here. So, looks like the war classloader just can't find this very class...
Indeed, adding $GX_ROOTDIR/APPS/foo/foo/WEB-INF/lib to the global kjs CLASSPATH will have everything work fine. But if i have to do so, i guess it's not worth using a j2ee app server...
We had this problem with several j2ee applications, running on different solaris 2.6 sparc machines both with iAS6sp2 and iAS6sp4
Any clue would be highly appreciated :-)
thanx
regards
Laurent

Similar Messages

Solaris 10 /dev/poll bug

Solaris 10, at least on my T2000, seems to give me an EINVAL from the DP_POLL ioctl in a case where it shouldn't. The below example code should clarify:
#include <stdio.h>
#include <stdlib.h>
#include <sys/types.h>
#include <fcntl.h>
#include <errno.h>
#include <limits.h>
#include <sys/resource.h>
#include <sys/devpoll.h>
This program demonstrates what seems to be a bug in the /dev/poll interface
on Solaris 10 on our T2000. The man page says:
EINVAL The request or arg parameter is not valid
for this device, or field of the dvpoll
struct pointed by arg is not valid (for
example, dp_nfds is greater than
{OPEN_MAX}).
But in this case, we get EINVAL even though dp_nfds is not greater than
OPEN_MAX.
void fatal(const char *f)
fprintf(stderr, "Unable to show problem: %s\n", f);
exit(1);
int main(void)
struct rlimit r;
struct pollfd pfd[256];
struct dvpoll dp;
int i;
if(getrlimit(RLIMIT_NOFILE, &r)!=0) fatal("unable to get file limit");
if(r.rlim_cur!=256) fatal("set fd limit to 256");
if(OPEN_MAX!=256) fatal("OPEN_MAX must be 256");
i=open("/dev/poll", O_RDWR);
if(i<0) fatal("unable to open /dev/poll");
dp.dp_timeout=0;
dp.dp_nfds=256; /* Changing this to 255 fixes the problem */
dp.dp_fds=pfd;
if(ioctl(i, DP_POLL, &dp)==0) fatal("it does not appear on this system");
printf("errno=%d - Why?\n", errno);
Any ideas?

I ran into the same problem. /dev/poll is too smart for its own good here. You can't monitor your /dev/poll file descriptor using /dev/poll, so the actual maximum number of file descriptors you can monitor is OPEN_MAX - 1. Solaris enforces that limit.
This breaks other code out there too, e.g. the libevent library. Annoying even though it's arguably technically correct.

Solaris 11.1 ehci bug: usb-printer not anymore recognized

same hardware, same printer:
after upgrading to 11.1 the usb-printer is not detected
cfgadm does not list it, not detected by HAL.
No usb kern.info for the printer in /var/adm/messages
but unplugging USB cable causes ehci error message in /var/adm/messages.
Rollback to 11.0 BE, and printer is there again:
$> cfgadm
Ap_Id Type Receptacle Occupant Condition
sata6/0::dsk/c5t0d0 disk connected configured ok
sata6/1 sata-port empty unconfigured ok
sata6/2 sata-port empty unconfigured ok
sata6/3::dsk/c5t3d0 cd/dvd connected configured ok
sata6/4 sata-port empty unconfigured ok
sata6/5 sata-port empty unconfigured ok
usb2/1 unknown empty unconfigured ok
usb2/2 unknown empty unconfigured ok
usb2/3 unknown empty unconfigured ok
usb2/4 unknown empty unconfigured ok
usb2/5 unknown empty unconfigured ok
usb2/6 unknown empty unconfigured ok
usb3/1 usb-printer connected configured ok
in /var/adm/messages printer shows up again:
Nov 2 23:16:20 mini11 usba: [ID 349649 kern.info] Samsung Electronics Co., Ltd. CLP-310 Series 1434BABS103573Z
Nov 2 23:16:20 mini11 genunix: [ID 936769 kern.info] usbprn1 is /pci@0,0/pci1025,228@2,1/printer@1
Nov 2 23:16:20 mini11 genunix: [ID 408114 kern.info] /pci@0,0/pci1025,228@2,1/printer@1 (usbprn1) online
example hardware: Acer Aspire X3400
Herstellername:Acer
Manufacture model:Aspire X3400
64 Bit:True
OS version:SunOS mini11 5.11 11.0 i86pc i386 i86pc
CPU Type:AMD Athlon(tm) II X2 220 Processor
CPU Number:1
Number Of Cores Per Processor:2
Number Of Threads Per Processor:2
Bios/Firmware Maker:AMI Version:P01-B1 Release Date:04/02/2010
prtconf -pv:
System Configuration: Oracle Corporation i86pc
Memory size: 4096 Megabytes
System Peripherals (PROM Nodes):
Node 0x000001
bios-boot-device: '80'
stdout: 00000000
name: 'i86pc'
Node 0x000002
existing: 00c21000.00000000.029d1001.00000000
name: 'ramdisk'
Node 0x000003
acpi-namespace: '\_SB_.PCI0'
compatible: 'pciex_root_complex'
device_type: 'pciex'
reg: 00000000.00000000.00000000.00000000.00000000
#size-cells: 00000002
#address-cells: 00000003
name: 'pci'
Node 0x000004
reg: 00000000.00000000.00000000.00000000.00000000
compatible: 'pci10de,754.1025.228.a2' + 'pci10de,754.1025.228' + 'pci1025,228' + 'pci10de,754.a2' + 'pci10de,754' + 'pciclass,050000' + 'pciclass,0500'
model: 'Ram'
power-consumption: 00000001.00000001
66mhz-capable:
fast-back-to-back:
devsel-speed: 00000000
max-latency: 00000000
min-grant: 00000000
subsystem-vendor-id: 00001025
subsystem-id: 00000228
unit-address: '0'
class-code: 00050000
revision-id: 000000a2
vendor-id: 000010de
device-id: 00000754
name: 'pci1025,228'
Node 0x000005
#size-cells: 00000001
#address-cells: 00000002
ranges: 00000001.00000000.81000000.00000000.00000000.0000004e.00000001.00000050.81000000.00000000.00000050.000000b0.00000001.000004d0.81000000.00000000.000004d0.00000002.00000001.00000800.81000000.00000000.00000800.00000010.00000001.00000a00.81000000.00000000.00000a00.00000040.00000001.00000cf8.81000000.00000000.00000cf8.00000008.00000001.00004000.81000000.00000000.00004000.00000100.00000001.00004400.81000000.00000000.00004400.00000100.00000001.00004800.81000000.00000000.00004800.00000100.00000000.00000000.82000000.00000000.00000000.000a0000.00000000.000c0000.82000000.00000000.000c0000.00010000.00000000.000e0000.82000000.00000000.000e0000.c7f20000.00000000.e0000000.82000000.00000000.e0000000.10000000.00000000.fec00000.82000000.00000000.fec00000.01400000.00000000.fec00000.82000000.00000000.fec00000.00001000.00000000.fed00000.82000000.00000000.fed00000.00001000.00000000.fed04000.82000000.00000000.fed04000.00001000.00000000.fee00000.82000000.00000000.fee00000.00100000
acpi-namespace: '\_SB_.PCI0.SBRG'
device_type: 'isa'
assigned-addresses: 81000810.00000000.00004f00.00000000.00000100
reg: 00000800.00000000.00000000.00000000.00000000.01000810.00000000.00000000.00000000.00000100
compatible: 'pci10de,75c.1025.228.a2' + 'pci10de,75c.1025.228' + 'pci1025,228' + 'pci10de,75c.a2' + 'pci10de,75c' + 'pciclass,060100' + 'pciclass,0601'
model: 'ISA bridge'
power-consumption: 00000001.00000001
66mhz-capable:
fast-back-to-back:
devsel-speed: 00000000
max-latency: 00000000
min-grant: 00000000
subsystem-vendor-id: 00001025
subsystem-id: 00000228
unit-address: '1'
class-code: 00060100
revision-id: 000000a2
vendor-id: 000010de
device-id: 0000075c
name: 'isa'
Node 0x000024
unit-address: '1,60'
interrupts: 00000001.0000000c
reg: 00000001.00000060.00000001.00000001.00000064.00000001
name: 'i8042'
Node 0x000025
compatible: 'pnpPNP,303'
device-type: 'keyboard'
interrupts: 00000001.0000000c
reg: 00000000
acpi-namespace: '\_SB_.PCI0.SBRG.PS2K'
model: 'System keyboard'
name: 'keyboard'
Node 0x000026
compatible: 'pnpPNP,f03'
device-type: 'mouse'
reg: 00000001
interrupts: 0000000c
acpi-namespace: '\_SB_.PCI0.SBRG.PS2M'
model: 'Microsoft PS/2-style Mouse'
name: 'mouse'
Node 0x000027
compatible: 'pnpPNP,c01'
reg: 00000000.00000000.000a0000.00000000.000c0000.00010000.00000000.000e0000.00020000.00000000.00100000.c7f00000.00000000.fec00000.01400000
acpi-namespace: '\_SB_.RMEM'
model: 'Motherboard'
name: 'motherboard'
Node 0x000006
acpi-namespace: '\_SB_.PCI0.SMB0'
assigned-addresses: 81000910.00000000.00004900.00000000.00000040.81000920.00000000.00004d00.00000000.00000040.81000924.00000000.00004e00.00000000.00000040
reg: 00000900.00000000.00000000.00000000.00000000.01000910.00000000.00000000.00000000.00000040.01000920.00000000.00000000.00000000.00000040.01000924.00000000.00000000.00000000.00000040
compatible: 'pci10de,752.1025.228.a1' + 'pci10de,752.1025.228' + 'pci1025,228' + 'pci10de,752.a1' + 'pci10de,752' + 'pciclass,0c0500' + 'pciclass,0c05'
model: 'SMBus (System Management Bus)'
power-consumption: 00000001.00000001
66mhz-capable:
fast-back-to-back:
devsel-speed: 00000000
interrupts: 00000001
max-latency: 00000000
min-grant: 00000000
subsystem-vendor-id: 00001025
subsystem-id: 00000228
unit-address: '1,1'
class-code: 000c0500
revision-id: 000000a1
vendor-id: 000010de
device-id: 00000752
name: 'pci1025,228'
Node 0x000007
reg: 00000a00.00000000.00000000.00000000.00000000
compatible: 'pci10de,751.1025.228.a1' + 'pci10de,751.1025.228' + 'pci1025,228' + 'pci10de,751.a1' + 'pci10de,751' + 'pciclass,050000' + 'pciclass,0500'
model: 'Ram'
power-consumption: 00000001.00000001
66mhz-capable:
fast-back-to-back:
devsel-speed: 00000000
max-latency: 00000000
min-grant: 00000000
subsystem-vendor-id: 00001025
subsystem-id: 00000228
unit-address: '1,2'
class-code: 00050000
revision-id: 000000a1
vendor-id: 000010de
device-id: 00000751
name: 'pci1025,228'
Node 0x000008
assigned-addresses: 82000b10.00000000.fce80000.00000000.00080000
reg: 00000b00.00000000.00000000.00000000.00000000.02000b10.00000000.00000000.00000000.00080000
compatible: 'pci10de,753.1025.228.a2' + 'pci10de,753.1025.228' + 'pci1025,228' + 'pci10de,753.a2' + 'pci10de,753' + 'pciclass,0b4000' + 'pciclass,0b40'
model: 'Co-processor'
power-consumption: 00000001.00000001
66mhz-capable:
fast-back-to-back:
devsel-speed: 00000000
interrupts: 00000002
max-latency: 00000001
min-grant: 00000003
subsystem-vendor-id: 00001025
subsystem-id: 00000228
unit-address: '1,3'
class-code: 000b4000
revision-id: 000000a2
vendor-id: 000010de
device-id: 00000753
name: 'pci1025,228'
Node 0x000009
acpi-namespace: '\_SB_.PCI0.IMAP'
reg: 00000c00.00000000.00000000.00000000.00000000
compatible: 'pci10de,568.1025.228.a1' + 'pci10de,568.1025.228' + 'pci1025,228' + 'pci10de,568.a1' + 'pci10de,568' + 'pciclass,050000' + 'pciclass,0500'
model: 'Ram'
power-consumption: 00000001.00000001
66mhz-capable:
fast-back-to-back:
devsel-speed: 00000000
max-latency: 00000000
min-grant: 00000000
subsystem-vendor-id: 00001025
subsystem-id: 00000228
unit-address: '1,4'
class-code: 00050000
revision-id: 000000a1
vendor-id: 000010de
device-id: 00000568
name: 'pci1025,228'
Node 0x00000a
acpi-namespace: '\_SB_.PCI0.USB0'
assigned-addresses: 82001010.00000000.fce7f000.00000000.00001000
reg: 00001000.00000000.00000000.00000000.00000000.02001010.00000000.00000000.00000000.00001000
compatible: 'pci10de,77b.1025.228.a1' + 'pci10de,77b.1025.228' + 'pci1025,228' + 'pci10de,77b.a1' + 'pci10de,77b' + 'pciclass,0c0310' + 'pciclass,0c03'
model: 'Universal Serial Bus OHCI compliant'
power-consumption: 00000001.00000001
66mhz-capable:
fast-back-to-back:
devsel-speed: 00000000
interrupts: 00000001
max-latency: 00000001
min-grant: 00000003
subsystem-vendor-id: 00001025
subsystem-id: 00000228
unit-address: '2'
class-code: 000c0310
revision-id: 000000a1
vendor-id: 000010de
device-id: 0000077b
name: 'pci1025,228'
Node 0x00000b
acpi-namespace: '\_SB_.PCI0.USB2'
assigned-addresses: 82001110.00000000.fce7ec00.00000000.00000100
reg: 00001100.00000000.00000000.00000000.00000000.02001110.00000000.00000000.00000000.00000100
compatible: 'pci10de,77c.1025.228.a1' + 'pci10de,77c.1025.228' + 'pci1025,228' + 'pci10de,77c.a1' + 'pci10de,77c' + 'pciclass,0c0320' + 'pciclass,0c03'
model: 'Universal Serial Bus EHCI compliant'
power-consumption: 00000001.00000001
66mhz-capable:
fast-back-to-back:
devsel-speed: 00000000
interrupts: 00000002
max-latency: 00000001
min-grant: 00000003
subsystem-vendor-id: 00001025
subsystem-id: 00000228
unit-address: '2,1'
class-code: 000c0320
revision-id: 000000a1
vendor-id: 000010de
device-id: 0000077c
name: 'pci1025,228'
Node 0x00000c
acpi-namespace: '\_SB_.PCI0.US15'
assigned-addresses: 82002010.00000000.fce7d000.00000000.00001000
reg: 00002000.00000000.00000000.00000000.00000000.02002010.00000000.00000000.00000000.00001000
compatible: 'pci10de,77d.1025.228.a1' + 'pci10de,77d.1025.228' + 'pci1025,228' + 'pci10de,77d.a1' + 'pci10de,77d' + 'pciclass,0c0310' + 'pciclass,0c03'
model: 'Universal Serial Bus OHCI compliant'
power-consumption: 00000001.00000001
66mhz-capable:
fast-back-to-back:
devsel-speed: 00000000
interrupts: 00000001
max-latency: 00000001
min-grant: 00000003
subsystem-vendor-id: 00001025
subsystem-id: 00000228
unit-address: '4'
class-code: 000c0310
revision-id: 000000a1
vendor-id: 000010de
device-id: 0000077d
name: 'pci1025,228'
Node 0x00000d
acpi-namespace: '\_SB_.PCI0.US12'
assigned-addresses: 82002110.00000000.fce7e800.00000000.00000100
reg: 00002100.00000000.00000000.00000000.00000000.02002110.00000000.00000000.00000000.00000100
compatible: 'pci10de,77e.1025.228.a1' + 'pci10de,77e.1025.228' + 'pci1025,228' + 'pci10de,77e.a1' + 'pci10de,77e' + 'pciclass,0c0320' + 'pciclass,0c03'
model: 'Universal Serial Bus EHCI compliant'
power-consumption: 00000001.00000001
66mhz-capable:
fast-back-to-back:
devsel-speed: 00000000
interrupts: 00000002
max-latency: 00000001
min-grant: 00000003
subsystem-vendor-id: 00001025
subsystem-id: 00000228
unit-address: '4,1'
class-code: 000c0320
revision-id: 000000a1
vendor-id: 000010de
device-id: 0000077e
name: 'pci1025,228'
Node 0x00000e
acpi-namespace: '\_SB_.PCI0.IDE0'
#size-cells: 00000000
#address-cells: 00000001
device_type: 'pci-ide'
assigned-addresses: 81003000.00000000.000001f0.00000000.00000008.81003000.00000000.000003f6.00000000.00000001.81003000.00000000.00000170.00000000.00000008.81003000.00000000.00000376.00000000.00000001.81003020.00000000.0000ffa0.00000000.00000010
reg: 00003000.00000000.00000000.00000000.00000000.81003000.00000000.000001f0.00000000.00000008.81003000.00000000.000003f6.00000000.00000001.81003000.00000000.00000170.00000000.00000008.81003000.00000000.00000376.00000000.00000001.01003020.00000000.00000000.00000000.00000010
compatible: 'pci10de,759.1025.228.a1' + 'pci10de,759.1025.228' + 'pci1025,228' + 'pci10de,759.a1' + 'pci10de,759' + 'pciclass,01018a' + 'pciclass,0101'
model: 'IDE controller'
power-consumption: 00000001.00000001
66mhz-capable:
fast-back-to-back:
devsel-speed: 00000000
max-latency: 00000001
min-grant: 00000003
subsystem-vendor-id: 00001025
subsystem-id: 00000228
unit-address: '6'
class-code: 0001018a
revision-id: 000000a1
vendor-id: 000010de
device-id: 00000759
name: 'pci-ide'
Node 0x00000f
reg: 00000000
name: 'ide'
Node 0x000010
reg: 00000001
name: 'ide'
Node 0x000011
acpi-namespace: '\_SB_.PCI0.HDAC'
assigned-addresses: 82003810.00000000.fce78000.00000000.00004000
reg: 00003800.00000000.00000000.00000000.00000000.02003810.00000000.00000000.00000000.00004000
compatible: 'pci10de,774.1025.228.a1' + 'pci10de,774.1025.228' + 'pci1025,228' + 'pci10de,774.a1' + 'pci10de,774' + 'pciclass,040300' + 'pciclass,0403'
model: 'Mixed Mode device'
power-consumption: 00000001.00000001
66mhz-capable:
fast-back-to-back:
devsel-speed: 00000000
interrupts: 00000001
max-latency: 00000005
min-grant: 00000002
subsystem-vendor-id: 00001025
subsystem-id: 00000228
unit-address: '7'
class-code: 00040300
revision-id: 000000a1
vendor-id: 000010de
device-id: 00000774
name: 'pci1025,228'
Node 0x000012
acpi-namespace: '\_SB_.PCI0.P0P1'
slot-names: 00000600.746f6c53.6c530034.0035746f
reg: 00004000.00000000.00000000.00000000.00000000
compatible: 'pci10de,75a.a1' + 'pci10de,75a' + 'pciclass,060401' + 'pciclass,0604'
model: 'Subtractive Decode PCI-PCI bridge'
bus-range: 00000001.00000001
#size-cells: 00000002
#address-cells: 00000003
device_type: 'pci'
power-consumption: 00000001.00000001
66mhz-capable:
fast-back-to-back:
devsel-speed: 00000000
unit-address: '8'
class-code: 00060401
revision-id: 000000a1
vendor-id: 000010de
device-id: 0000075a
name: 'pci10de,75a'
Node 0x000013
acpi-namespace: '\_SB_.PCI0.ATA0'
assigned-addresses: 81004810.00000000.0000d480.00000000.00000008.81004814.00000000.0000d400.00000000.00000004.81004818.00000000.0000d080.00000000.00000008.8100481c.00000000.0000d000.00000000.00000004.81004820.00000000.0000cc00.00000000.00000010.82004824.00000000.fce76000.00000000.00002000
reg: 00004800.00000000.00000000.00000000.00000000.01004810.00000000.00000000.00000000.00000008.01004814.00000000.00000000.00000000.00000004.01004818.00000000.00000000.00000000.00000008.0100481c.00000000.00000000.00000000.00000004.01004820.00000000.00000000.00000000.00000010.02004824.00000000.00000000.00000000.00002000
compatible: 'pci10de,ad4.1025.228.a2' + 'pci10de,ad4.1025.228' + 'pci1025,228' + 'pci10de,ad4.a2' + 'pci10de,ad4' + 'pciclass,010601' + 'pciclass,0106'
model: 'SATA AHCI 1.0 Interface'
power-consumption: 00000001.00000001
66mhz-capable:
fast-back-to-back:
devsel-speed: 00000000
interrupts: 00000001
max-latency: 00000001
min-grant: 00000003
subsystem-vendor-id: 00001025
subsystem-id: 00000228
unit-address: '9'
class-code: 00010601
revision-id: 000000a2
vendor-id: 000010de
device-id: 00000ad4
name: 'pci1025,228'
Node 0x000014
acpi-namespace: '\_SB_.PCI0.NMAC'
assigned-addresses: 82005010.00000000.fce7c000.00000000.00001000.81005014.00000000.0000c880.00000000.00000008.82005018.00000000.fce7e400.00000000.00000100.8200501c.00000000.fce7e000.00000000.00000010
reg: 00005000.00000000.00000000.00000000.00000000.02005010.00000000.00000000.00000000.00001000.01005014.00000000.00000000.00000000.00000008.02005018.00000000.00000000.00000000.00000100.0200501c.00000000.00000000.00000000.00000010
compatible: 'pci10de,760.1025.8000.a2' + 'pci10de,760.1025.8000' + 'pci1025,8000' + 'pci10de,760.a2' + 'pci10de,760' + 'pciclass,020000' + 'pciclass,0200'
model: 'Ethernet controller'
power-consumption: 00000001.00000001
66mhz-capable:
fast-back-to-back:
devsel-speed: 00000000
interrupts: 00000001
max-latency: 00000014
min-grant: 00000001
subsystem-vendor-id: 00001025
subsystem-id: 00008000
unit-address: 'a'
class-code: 00020000
revision-id: 000000a2
vendor-id: 000010de
device-id: 00000760
name: 'pci1025,8000'
Node 0x000015
acpi-namespace: '\_SB_.PCI0.MXR0'
slot-names: 00000001.746f6c53.00003233
reg: 00008000.00000000.00000000.00000000.00000000
compatible: 'pciex10de,778.a1' + 'pciex10de,778' + 'pciexclass,060400' + 'pciexclass,0604' + 'pci10de,778.a1' + 'pci10de,778' + 'pciclass,060400' + 'pciclass,0604'
model: 'PCI-PCI bridge'
ranges: 81000000.00000000.000003b0.81000000.00000000.000003b0.00000000.0000000c.81000000.00000000.000003c0.81000000.00000000.000003c0.00000000.00000020.81000000.00000000.0000e000.81000000.00000000.0000e000.00000000.00001000.82000000.00000000.000a0000.82000000.00000000.000a0000.00000000.00020000.82000000.00000000.fcf00000.82000000.00000000.fcf00000.00000000.01100000.c2000000.00000000.ce000000.c2000000.00000000.ce000000.00000000.12000000
bus-range: 00000002.00000002
#size-cells: 00000002
#address-cells: 00000003
device_type: 'pciex'
power-consumption: 00000001.00000001
physical-slot#: 00000001
devsel-speed: 00000000
interrupts: 00000001
unit-address: '10'
class-code: 00060400
revision-id: 000000a1
vendor-id: 000010de
device-id: 00000778
name: 'pci10de,778'
Node 0x00001d
assigned-addresses: 82020010.00000000.fd000000.00000000.01000000.c3020014.00000000.d0000000.00000000.10000000.c302001c.00000000.ce000000.00000000.02000000.81020024.00000000.0000ec00.00000000.00000080.a1020000.00000000.000003b0.00000000.0000000c.a1020000.00000000.000003c0.00000000.00000020.a2020000.00000000.000a0000.00000000.00020000
reg: 00020000.00000000.00000000.00000000.00000000.02020010.00000000.00000000.00000000.01000000.43020014.00000000.00000000.00000000.10000000.4302001c.00000000.00000000.00000000.02000000.01020024.00000000.00000000.00000000.00000080.a1020000.00000000.000003b0.00000000.0000000c.a1020000.00000000.000003c0.00000000.00000020.a2020000.00000000.000a0000.00000000.00020000
compatible: 'pciex10de,a22.174b.1141.a2' + 'pciex10de,a22.174b.1141' + 'pciex10de,a22.a2' + 'pciex10de,a22' + 'pciexclass,030000' + 'pciexclass,0300' + 'pci10de,a22.174b.1141.a2' + 'pci10de,a22.174b.1141' + 'pci10de,a22.a2' + 'pci10de,a22' + 'pciclass,030000' + 'pciclass,0300'
model: 'VGA compatible controller'
power-consumption: 00000001.00000001
devsel-speed: 00000000
interrupts: 00000001
subsystem-vendor-id: 0000174b
subsystem-id: 00001141
device_type: 'display'
unit-address: '0'
class-code: 00030000
revision-id: 000000a2
vendor-id: 000010de
device-id: 00000a22
name: 'display'
Node 0x00001e
assigned-addresses: 82020110.00000000.fcf7c000.00000000.00004000
reg: 00020100.00000000.00000000.00000000.00000000.02020110.00000000.00000000.00000000.00004000
compatible: 'pciex10de,be2.174b.1141.a1' + 'pciex10de,be2.174b.1141' + 'pciex10de,be2.a1' + 'pciex10de,be2' + 'pciexclass,040300' + 'pciexclass,0403' + 'pci10de,be2.174b.1141.a1' + 'pci10de,be2.174b.1141' + 'pci174b,1141' + 'pci10de,be2.a1' + 'pci10de,be2' + 'pciclass,040300' + 'pciclass,0403'
model: 'Mixed Mode device'
power-consumption: 00000001.00000001
devsel-speed: 00000000
interrupts: 00000001
subsystem-vendor-id: 0000174b
subsystem-id: 00001141
unit-address: '0,1'
class-code: 00040300
revision-id: 000000a1
vendor-id: 000010de
device-id: 00000be2
name: 'pci174b,1141'
Node 0x000016
acpi-namespace: '\_SB_.PCI0.BR12'
slot-names: 00000001.746f6c53.00003433
reg: 00009000.00000000.00000000.00000000.00000000
compatible: 'pciex10de,75b.a1' + 'pciex10de,75b' + 'pciexclass,060400' + 'pciexclass,0604' + 'pci10de,75b.a1' + 'pci10de,75b' + 'pciclass,060400' + 'pciclass,0604'
model: 'PCI-PCI bridge'
bus-range: 00000003.00000003
#size-cells: 00000002
#address-cells: 00000003
device_type: 'pciex'
power-consumption: 00000001.00000001
physical-slot#: 00000003
devsel-speed: 00000000
interrupts: 00000001
unit-address: '12'
class-code: 00060400
revision-id: 000000a1
vendor-id: 000010de
device-id: 0000075b
name: 'pci10de,75b'
Node 0x000017
acpi-namespace: '\_SB_.PCI0.BR13'
slot-names: 00000001.746f6c53.00003533
reg: 00009800.00000000.00000000.00000000.00000000
compatible: 'pciex10de,77a.a1' + 'pciex10de,77a' + 'pciexclass,060400' + 'pciexclass,0604' + 'pci10de,77a.a1' + 'pci10de,77a' + 'pciclass,060400' + 'pciclass,0604'
model: 'PCI-PCI bridge'
bus-range: 00000004.00000004
#size-cells: 00000002
#address-cells: 00000003
device_type: 'pciex'
power-consumption: 00000001.00000001
physical-slot#: 00000004
devsel-speed: 00000000
interrupts: 00000001
unit-address: '13'
class-code: 00060400
revision-id: 000000a1
vendor-id: 000010de
device-id: 0000077a
name: 'pci10de,77a'
Node 0x000018
acpi-namespace: '\_SB_.PCI0.K800'
reg: 0000c000.00000000.00000000.00000000.00000000
compatible: 'pci1022,1200.0' + 'pci1022,1200' + 'pciclass,060000' + 'pciclass,0600'
model: 'Host bridge'
power-consumption: 00000001.00000001
devsel-speed: 00000000
max-latency: 00000000
min-grant: 00000000
unit-address: '18'
class-code: 00060000
revision-id: 00000000
vendor-id: 00001022
device-id: 00001200
name: 'pci1022,1200'
Node 0x000019
reg: 0000c100.00000000.00000000.00000000.00000000
compatible: 'pci1022,1201.0' + 'pci1022,1201' + 'pciclass,060000' + 'pciclass,0600'
model: 'Host bridge'
power-consumption: 00000001.00000001
devsel-speed: 00000000
max-latency: 00000000
min-grant: 00000000
unit-address: '18,1'
class-code: 00060000
revision-id: 00000000
vendor-id: 00001022
device-id: 00001201
name: 'pci1022,1201'
Node 0x00001a
acpi-namespace: '\_SB_.PCI0.K802'
reg: 0000c200.00000000.00000000.00000000.00000000
compatible: 'pci1022,1202.0' + 'pci1022,1202' + 'pciclass,060000' + 'pciclass,0600'
model: 'Host bridge'
power-consumption: 00000001.00000001
devsel-speed: 00000000
max-latency: 00000000
min-grant: 00000000
unit-address: '18,2'
class-code: 00060000
revision-id: 00000000
vendor-id: 00001022
device-id: 00001202
name: 'pci1022,1202'
Node 0x00001b
acpi-namespace: '\_SB_.PCI0.K803'
reg: 0000c300.00000000.00000000.00000000.00000000
compatible: 'pci1022,1203.0' + 'pci1022,1203' + 'pciclass,060000' + 'pciclass,0600'
model: 'Host bridge'
power-consumption: 00000001.00000001
devsel-speed: 00000000
max-latency: 00000000
min-grant: 00000000
unit-address: '18,3'
class-code: 00060000
revision-id: 00000000
vendor-id: 00001022
device-id: 00001203
name: 'pci1022,1203'
Node 0x00001c
reg: 0000c400.00000000.00000000.00000000.00000000
compatible: 'pci1022,1204.0' + 'pci1022,1204' + 'pciclass,060000' + 'pciclass,0600'
model: 'Host bridge'
power-consumption: 00000001.00000001
devsel-speed: 00000000
max-latency: 00000000
min-grant: 00000000
unit-address: '18,4'
class-code: 00060000
revision-id: 00000000
vendor-id: 00001022
device-id: 00001204
name: 'pci1022,1204'
Node 0x00001f
device_type: 'a

So Solaris 11.1 is supposed to support USB 3.0 and I think that may have something to do with it. I have two Gigaware 16GB USB thumb drives that work fine with 11.0 FCS but one of them fails under 11.1. Also not recognized but on occasion I can get /var/adm/messages to log something although most times it has nothing.
So I used a Windows utility to look at both of them and one of them has an older firmware version than the other. The older one doesn't work with 11.1 but the one with the newer firmware runs just fine. Made a nice excuse to upgrade one of them to 32 GB's.
alan

Solaris 10 update 6 keeps generating core file (/core)

I wonder if somebody has encountered the following issue.
I did a fresh install of Solaris 10 update 6 on two servers (T5140 and T524) from DVD.
I noticed that a core file was in the root filesystem (/core).
So, I deleted it.
As soon as I delete the core file, another one is generated.
This is happening on both servers where I installed Solaris 10 update 6 from the DVD.
This is not a live update install. Solaris was installed from scratch. When prompted to preserve previous data, I replied with 'do not preserve data'
Does anybody know where the core file is coming from and how to stop it being generated?
Found out that is coming from vold
SunOS b1osdtsun02 5.10 Generic_137137-09 sun4v sparc SUNW,T5240
# more /etc/release
                      Solaris 10 10/08 s10s_u6wos_07b SPARC
           Copyright 2008 Sun Microsystems, Inc. All Rights Reserved.
                        Use is subject to license terms.
                            Assembled 27 October 2008
# mdb /core
Loading modules: [ libsysevent.so.1 libnvpair.so.1 libc.so.1 ld.so.1 ]
::statusdebugging core file of vold (32-bit) from b1osdtsun02
file: /usr/sbin/vold
initial argv: /usr/sbin/vold -f /etc/vold.conf
threading model: multi-threaded
status: process terminated by SIGSEGV (Segmentation Fault)
::stacklibc.so.1`strlen+0x18(408450a5, 0, 0, 88b70, 600, 180)
read_slices+0x114(874a0, b, 889a0, feeafd34, 1, 5)
read_hsfs_partition+0x88(b, 46c00, 6d0000, 2c, 34400, 1010101)
read_partition+0x30(874a0, 341a4, 3, 34000, 34400, 9)
create_top_partition+0x140(7cbe0, 7cc24, 7cbe0, 874a0, ffffffff, b)
0x265e0(800012, feeaff9c, c, 598e0, 7cbe0, ffffffff)
create_medium+0x74(800012, feeaff9c, 20, 12, 47800, c)
0x2232c(5d278, 0, 0, 800012, 20, 33000)
libc.so.1`_lwp_start(0, 0, 0, 0, 0, 0)
>
#It seems that vold is failing to mount the DVD on both servers after Solaris was installed.
Is this a Solaris 10 update 6 bug?
Edited by: shen on Jan 29, 2009 8:45 PM

Never mind.
It is a known bug documented on manual " [Solaris 10 10/08 Release Notes, Chapter 2 Solaris Runtime Issues|http://docs.sun.com/app/docs/doc/820-5245/chapter2-1000?a=view] " as shown below.
The solution is to apply vold patch [138130-01|http://sunsolve.sun.com/search/document.do?assetkey=1-21-138130-01-1].
Solaris 10 10/08 DVD Media Might Not be Automatically Mounted by vold (6712352)
The Solaris 10 10/08 DVD does not mount by default during runtime. No error message is displayed.
Workaround: Perform the following steps:
   1. Become superuser.
   2. Disable vold:
      * On Solaris 10 Systems:
            # svcadm disable -t volfs
      * On Solaris 8 and Solaris 9 systems:
            /etc/init.d/volmgt stop
   3. Mount the media manually by using the # mount -F hsfs path to block device path to mount point command. For example:
      # mount -F hsfs /dev/rdsk/c0t2d0s2 /mnt

Solaris Update Release Query

As a requirement for Oracle 11g I need Solaris 10 to be on at least update 6.
I am currently on update 4.
Applying the patch bundle isn't an option as the 11g upgrade pre-req checks needs to see that /etc/release specificies u6 or greater.
What I'd like to know is, will installing the Oracle Solaris OS Recommended Patchset achieve this or do I need to go for an Update Release?
As far as I can see on this is that only the latest update release version is available through OTN which I can't use as our EMC software is not compatible with it and there is no fix yet. OTN points to MOS for older updates but I can only see Patch Bundles and Patch Sets.
Many thanks in advance
Paul

I have not used these myself but did you try the instructions near the bottom:
"Older Versions of Solaris
Older versions of Solaris can also be requested by logging a Physical Media Request through My Oracle Support. Follow the instructions above. If a download is sufficient, please state this in the request."
I have no idea how long it would take to get Physical Media but that maybe your best option.
I do not have the details but I think some of the vendors have patches for the latest Solaris 10 update - maybe bugging them would be fruitful.
GlenG

TestClassLoader Bug

I'm reinstalling WAS SR1 JAVA on Windows 2003 Server/SQL Server after uninstalling EP6/WAS/DB etc; and am encountering a problem with the TestClassLoader check within the install.
Does anyone know what this check is looking for specifically? I'm using JAVA SDK 1.4.2_06 and have tried reinstalling that as well, and cannot work out where the problem is. I have a couple of other applications loaded which could be causing the problem but want to know what to look for before removing these.
Note - I've read the correpsonding note which doesn't apply to Windows, plus the comment already about running as local admin.
Thanks in advance,
Matt

Sorry, wasn't very clear. I get the response "BUG" in the output from the calling of the JAVA app testclassload. portion of log below:
Execution of the command "C:\j2sdk1.4.2_06/bin/java.exe '-version'" finished with return code 0. Output:
java version "1.4.2_06"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_06-b03)
Java HotSpot(TM) Client VM (build 1.4.2_06-b03, mixed mode)
TRACE      [iaxxejsexp.cpp:208]
           EJS_Installer::writeTraceToLogBook()
Java.compareSubVersions(1, 1) = 0
TRACE      [iaxxejsexp.cpp:208]
           EJS_Installer::writeTraceToLogBook()
Java.compareSubVersions(4, 4) = 0
TRACE      [iaxxejsexp.cpp:208]
           EJS_Installer::writeTraceToLogBook()
Java.compareSubVersions(2, 2) = 0
TRACE      [iaxxejsexp.cpp:208]
           EJS_Installer::writeTraceToLogBook()
Java.compareSubVersions(05, 06) = -1
TRACE      [iaxxejsexp.cpp:208]
           EJS_Installer::writeTraceToLogBook()
Java.compareSubVersions(1, 1) = 0
TRACE      [iaxxejsexp.cpp:208]
           EJS_Installer::writeTraceToLogBook()
Java.compareSubVersions(4, 5) = -1
TRACE      [iaxxejsexp.cpp:208]
           EJS_Installer::writeTraceToLogBook()
Don't need to determine JDK datamodel on I386
INFO       2005-05-31 17:10:31
           CJSlibModule::writeInfo_impl()
Execution of the command "C:\j2sdk1.4.2_06/bin/java.exe '-classpath' 'C:/DOCUME1/DACADM1.AAD/LOCALS1/Temp/sapinst_exe.3568.1117523329/JAR/ins-j2ee.jar;C:/DOCUME1/DACADM1.AAD/LOCALS1/Temp/sapinst_exe.3568.1117523329/JAR/sapxmltoolkit.jar' 'com.sap.ins.j2ee.TestClassLoader'" finished with return code 0. Output:
BUG
INFO       2005-05-31 17:10:31
           CJSlibModule::writeInfo_impl()
The JDK installed in directory C:\j2sdk1.4.2_06 contains a classloader bug. See SAP Note 701838.

Compiling "unzip" triggers bug

When compiling "unzip" from NetBSD's pkgsrc under Solaris 10, the following bug is triggered:
gcc -c -I/usr/local/pkgsrc/pkgsrc-2008Q3/include -O -I. -DUNIX -Dunix -DUSE_UNSHRINK -I/usr/local/pkgsrc/pkgsrc-2008Q3/include -DSFX inflate_.c
Assertion failed: use != NULL, file ../src/var_df.c, line 2959
gcc: Internal error: Abort (program iropt)
This bug is not triggered when compiling with -O2 (or -O3, which is used, when compiling "unzip" outside of pkgsrc).

Thank you for reporting. We will try to reproduce it in house and resolve the issue.
Prashanth

Ho w to file bug in this forum

Hi,
Please provide me the link, where I could file bug on Solaris-11-express OS.

bugs.opensolaris.org taps into the internal Sun bug tracking system so bugs opened there are indeed monitored (as I routinely discover through new bug reports and monitoring of old requests). If you try to submit a bug/RFE today, it lets you select up to snv_174 (Solaris 11 Express is currently snv_151a).
The support channels only work for people with a support contract. For the others covered by the OTN license, which allows testing, prototyping and development, I guess bugs.opensolaris.org will have to do it. On the other hand, most people doing these activities usually have a support contract anyway.
It's not clear to me what's the path that a bug submited through MOS follows for Solaris 11 Express. I know for a fact that any bugs opened at bug.opensolaris.org get quickly triaged and handled by an Oracle engineer.

Shutdown normal|immediate slow on new install of 11R2.0.3.{2|3|4} on Solaris

Just installed a new pair of SPARC T4-4 (each w/2x CPUs, 128GB mem) with Solaris 11.1 sru 3.4.1 to run a Data Guard solution for 3x instances using 3x diff. Oracle 11R2 versions (11.2.0.3.2-4)
But all three instances on both pro & sec server randomly indicates Time Drift warnings in their alert logs and vktm traces, but both solaris boxes are running ntp sync fine.
Also various operations like instance startup/shutdown takes a long time, as well as a simple launch of sqlplus can take minutes. Also spawning a simple CLI like 'ps -ef' can sometimes take up to 20-30 sec. Neither swap nor cpu is loaded.
Could it be a known bug seen before or a faulty init ora parameter and/or combination?
Also posted this under Solaris 11 Forum:
simple processes are very slow at intervals
TIA for any hints!
snip of a VKTM trace:
Trace file /global/oraadmin/diag/rdbms/<redacted>/trace/<redacted>_vktm_27415.trc Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Product ion ORACLE_HOME = /global/orabase/product/11.2.0.3.4/db_1 System name:    SunOS Node name:      <redacted> Release:        5.11 Version:        11.1 Machine:        sun4v Instance name: <redacted> Redo thread mounted by this instance: 0 <none> Oracle process number: 3 Unix process pid: 27415, image: oracle@<redacted> (VKTM) *** 2013-06-03 12:51:02.036 *** SESSION ID:(1609.1) 2013-06-03 12:51:02.036 *** CLIENT ID:() 2013-06-03 12:51:02.036 *** SERVICE NAME:() 2013-06-03 12:51:02.036 *** MODULE NAME:() 2013-06-03 12:51:02.036 *** ACTION NAME:() 2013-06-03 12:51:02.036 kstmmainvktm: succeeded in setting elevated priority highres_enabled *** 2013-06-03 12:51:02.036 VKTM running at (1)millisec precision with DBRM quantum (100)ms [Start] HighResTick = 4585953873256 kstmrmtickcnt = 0 : ksudbrmseccnt[0] = 1370256662 *** 2013-06-03 12:55:54.137 kstmchkdrift (kstmhighrestimecntkeeper:highres): Time jumped forward by (2984405)usec at (4586245994477) whereas (1000000) is allowed *** 2013-06-03 12:56:13.269 kstmchkdrift (kstmhighrestimecntkeeper:highres): Time jumped forward by (19133925)usec at (4586265128403) whereas (1000000) is allowed kstmchkdrift (kstmhighrestimecntkeeper:lowres): Time stalled at 1370256973 kstmchkdrift (kstmhighrestimecntkeeper:lowres): Stall, backward drift ended at 1370256974 drift: 1 kstmchkdrift (kstmhighrestimecntkeeper:highres): Time jumped forward by (7023737)usec at (4586963505968) whereas (1000000) is allowed
Mod. action: please, to keep tab formatting on forum side, use the tag
before and after your code output, thanks. lease, Edited by: N Gasparotto on Jun 3, 2013 4:16 PM

Thanks for your suggestion but as I have read the doc then the patch for Bug 9843304 is included in the 11.2.0.2 patchset and then also for PSUs 11.2.0.3.*
I think that the reason we see VKTM trace/drift is not high load as this is not the case, but more lock contention emulating high load. Question is just what lock and why and how to work around it...
Hoped that other SPARC T4 + 11R2 users might have seen similar issue and know what to tweak of either init ora/solaris setting or if bug is known.
Just to show a snap in time. miles varies off course and issue (as mentioned in Solaris 11 forum) is not seen constantly and not during below sampling...
#root:~# top -n 2
last pid: 6594; load avg: 8.07, 6.17, 7.32; up 6+21:28:53        18:04:14
249 processes: 239 sleeping, 5 zombie, 5 on cpu
CPU states: 95.5% idle, 1.0% user, 3.5% kernel, 0.0% iowait, 0.0% swap
Kernel: 67325 ctxsw, 624 trap, 53970 intr, 55554 syscall, 15 flt
Memory: 128G phys mem, 14G free mem, 64G total swap, 64G free swap
   PID USERNAME NLWP PRI NICE SIZE   RES STATE    TIME    CPU COMMAND
20916 oracle     18 20    0   50G   50G cpu/86 146:50 0.77% oracle
6202 oracle      7 51    0   25G   25G cpu/90   0:25 0.18% oracle
prstat -m -U oracle -n 10
   PID USERNAME USR SYS TRP TFL DFL LCK SLP LAT VCX ICX SCL SIG PROCESS/NLWP
21426 oracle    28 0.0 0.0 0.0 0.0 0.0 72 0.0   2 11 39   0 oracle/1
20916 oracle   5.5 0.0 0.0 0.0 0.0 89 5.6 0.0   3 24 8K   0 oracle/18
6180 oracle   2.2 2.3 0.0 0.0 0.0 62 33 0.2 8K 287 20K   0 oracle/7
6212 oracle   1.9 1.9 0.0 0.0 0.0 67 29 0.2 8K 269 19K   0 oracle/8
6196 oracle   1.9 1.8 0.0 0.0 0.0 67 29 0.2 8K 279 20K   0 oracle/8
6209 oracle   1.8 1.8 0.0 0.0 0.0 67 30 0.2 8K 311 19K   0 oracle/8
6178 oracle   1.5 1.0 0.0 0.0 0.0 65 32 0.2 1K 18 1K   0 oracle/7
6202 oracle   1.4 1.0 0.0 0.0 0.0 67 30 0.1 974 18 1K   0 oracle/8
6156 oracle   1.9 0.4 0.0 0.0 0.0 87 11 0.1 7K 193 16K   0 oracle/17
6158 oracle   1.9 0.4 0.0 0.0 0.0 83 15 0.1 5K 217 11K   0 oracle/13
Total: 171 processes, 3808 lwps, load averages: 9.36, 7.14, 7.48
#root:~# plockstat -CH -n 10 -e 5 -p 20916
        0
Mutex hold
Count     nsec Lock                         Caller
    2    22935 libc.so.1`_time_lock         oracle`slgtd+0x70
    1    27510 libc.so.1`_time_lock         oracle`slgtd+0x70
    2    13120 libc.so.1`libc_malloc_lock   oracle`lwemfaa+0x60
    2     8720 libc.so.1`libc_malloc_lock   oracle`sltstidinit+0x4
    2     7975 libc.so.1`__aio_mutex        libc.so.1`_aio_close+0x44
    2     5150 libc.so.1`libc_malloc_lock   oracle`sltsmxd+0x30
    2     4935 libc.so.1`libc_malloc_lock   oracle`sltsmxi+0x4
    2     3990 libc.so.1`libc_malloc_lock   oracle`sltstiddestroy+0x4
    2     3945 libc.so.1`libc_malloc_lock   oracle`slwmmputmem+0x10
    1     5910 libc.so.1`_time_lock         oracle`sLdiGetDate+0x6c

Bug id 4924525 on olaris 10?

Hi,
Hope this is the correct forum fo rthis qs - if not, please help redirect.
Does the problem pertaining to bug id 4924525 exist on Solaris 10?
If yes, then is it fixed - patch id info would help.
On Solaris 2.8, this bug is fixed in 110955-05..is there an equivalent patch on Solaris 10?
Thanks,
Madhvi

This is not the correct forum since this is only for questions about Patch Tools, as opposed to patches themselves.
For what it's worth my understanding is that bug 4924525 does not exist in Solaris 10 and so there is no need for any Solaris 10 patch for the issue.
However please post your query on one of the Solaris 10 OS forums as hopefully you will get a more definite answer there.
http://forum.sun.com/jive/forum.jspa?forumID=298

Ultra 10 + Sil0680 + 400GB drive still seen as 128GB

I am trying to get a 400GB drive to work on an Ultra 10 with Solaris 10u4 (8/07) and the newest OBP (3.31).
I understand that the on-board controller has a 128GB limit.
However, I've done a fair amount of digging and from what I've read, a PCI card with the Sil 0680 chip should work fine with the larger drives on SPARC hardware.
http://www.opensolaris.org/jive/message.jspa?messageID=43267#43267
Unfortunately, this does not appear to be the case.
I installed a Rosewill RC-208, which is a (non-RAID) dual UATA controller using the Sil 0680 chip.
After running devfsadm -v, the drive is seen and accessible.
However, it is being shown with the same limitations as the on-board controller.
prtdiag shows:
0 PCI-2 33 1 pci1095,680-pci1095,680.1095.680+
Format shows:
3. c1t0d0 <DEFAULT cyl 65533 alt 2 hd 16 sec 255>
/pci@1f,0/pci@1/pci1095,680@1/dad@0,0
...and for partitions:
Current partition table (original):
Total disk cylinders available: 65533 + 2 (reserved cylinders)
Part Tag Flag Cylinders Size Blocks
2 backup wu 0 - 65532 127.49GB (65533/0/0) 267374640
This drive is brand-new and unlabeled.
/kernel/drv/uata.conf does not have any useful configuration options.
Does anyone know how to get this system to see the full 400GB?
I did further digging, and it looks like the person who posted that it works was wrong, and that it is a Solaris-SPARC driver bug (as it is not a hardware limitation of this device).
I'm just hoping someone might have some further info... if a bug report has been filed with Sun, or maybe I can switch to Nevada (Solaris Express/11 beta), etc.
Much appreciated,
Kevin

Yes, as I stated above, it appears to be a bug in the Solaris uata driver.
To clarify my statement, this is a bug since this hardware does support drives larger than 128GB.
The part I find amazing is that Solaris/SPARC has this bug, but Solaris/x86 does not. I was under the mistaken impression that the driver (uata kernel module) code was the same between the two.
Since it's a driver bug, changing to yet another PCI IDE card won't help, as the uata driver handles all of the various ATA chips.
# grep ata /etc/driver_aliases
uata "pci1095,646"
uata "pci10b9,5229"
uata "pci10b9,5288"
uata "pci1095,649"
uata "pci1095,680"
pcata "pccard,disk"
It sounds as if there is no way to get a PATA drive bigger than 128GB to work on any Solaris/SPARC system.
(SATA systems obviously don't have this problem, but that doesn't help here.)
I'm mainly trying to find out if anyone knows if there is an intended fix for this, if t works in Nevada, or even in OpenSolaris (I will likely try OpenSolaris or Nevada on my personal Ultra 10 at home tonight to test it).
Regards,
Kevin

Query slowness after upgrading to 10.2.0.4

Is anyone else having spatial query problems after applying the 10.2.0.4 patch? We applied it to our DEV and QA environments last weekend and we are now seeing a degragation of spatial queries.
On the database we upgaded a query that has been running fine for years now takes 5.5 hours to complete. The same query on a database that has not been upgraded takes 5 minutes.
Both databases are on servers with the same hardware and operating system (Solaris 10 64bit), the only difference is the database version.
We have an SR open, but we aren't feeling the love yet.

Hi Robenour,
7003151 is not just for Linux, it's for all platforms, and will definitely help 10.2.0.4 and 11.1.0.6 spatial performance.
Below is the current list of Oracle Locator/Spatial/MapViewer patches I recommend.
The only one specific to Solaris is 5888136 for 10.2.0.3.
I recommend all the other patches for all hardware platforms.
Most of the following patches are available on Metalink.
If the patch is not there for your hardware platform/database release, please log a SR with Oracle support and request a backport.
Hope this helps. Thanks.
Dan
For Oracle 10.2.0.3, patches:
· 6980648 - Bug fixes and improved performance
· 6329260 - Bug fixes and improved performance
· 5888136 - Only if you are running Solaris - improved performance
· 6956194 - Bug fix if working with geodetic data
For Oracle 10.2.0.4, patches:
· 7003151 - Bug fixes and improved performance
· 6989483 - Improved performance
· 7046751 - Apply this patch if you applied patch 6989483 (necessary for some GIS software to work)
· 7237687 - Bug fix if working with geodetic data
· 6956194 - Bug fix if working with geodetic data
· 7276032 - Bug fix if working with geodetic data
For Oracle 11.1.0.6, patches:
· 7003151 - Bug fixes and improved performance
· 6989483 - Improved performance
· 7046751 - Apply this patch if you applied patch 6989483 (necessary for some GIS software to work)
· 6956194 - If working with geodetic data
For MapViewer 10.1.3.1
· 7195504 - Bug fixes and improved performance

Luxadm probe / Could not find the loop address for the device at physical path

Using EMC FibreChannel Disks on a Solaris 10
# luxadm probe
No Network Array enclosures found in /dev/es
Error: Could not find the loop address for the device at physical path.
# echo $?
255
Any ideas how to fix?
Thank,
Marcel

Hi Marcel,
Which Solaris 10 release is this?
I found a very old bug that says this problem is already fixed in Solaris 10 although the bug description says
its mostly seen on Solaris 8 and 9.
https://bug.oraclecorp.com/pls/bug/webbug_print.showbug?c_rptno=15123550
The bug says that these errors are displayed when StorADE 2.1 is running its rasagent cron job, which executes a luxadm display.
This process runs in the background so the user is not aware that another luxadm display process is running.
Work-around: Do not run Storade rasagent cron job at same time as another luxadm display process.
I hope this might help to debug this problem but I puzzled why this might be happening if its already fixed.
Let me know if the workaround helps or so I can follow-up with the right support team.
Thanks, Cindy

DskPercent not returned for ZFS filesystems?

Hello.
I'm trying to monitor the space usage of some ZFS filesystems on a Solaris 10 10/08 (137137-09) Sparc system with SNMP. I'm using the Systems Management Agent (SMA) agent.
To monitor the stuff, I added the following to /etc/sma/snmp/snmpd.conf and restarted svc:/application/management/sma:default:
# Bug in SMA?
# Reporting - NET-SNMP, Solaris 10 - has a bug parsing config file for disk space.
# -> http://forums.sun.com/thread.jspa?threadID=5366466
disk /proc 42% # Dummy Wert; wird fälschlicherweise ignoriert werden...
disk / 5%
disk /tmp 10%
disk /apps 4%
disk /data 3%Now I'm checking what I get via SNMP:
--($ ~)-- snmpwalk -v2c -c public 10.0.1.26 dsk
UCD-SNMP-MIB::dskIndex.1 = INTEGER: 1
UCD-SNMP-MIB::dskIndex.2 = INTEGER: 2
UCD-SNMP-MIB::dskIndex.3 = INTEGER: 3
UCD-SNMP-MIB::dskIndex.4 = INTEGER: 4
UCD-SNMP-MIB::dskPath.1 = STRING: /
UCD-SNMP-MIB::dskPath.2 = STRING: /tmp
UCD-SNMP-MIB::dskPath.3 = STRING: /apps
UCD-SNMP-MIB::dskPath.4 = STRING: /data
UCD-SNMP-MIB::dskDevice.1 = STRING: /dev/md/dsk/d200
UCD-SNMP-MIB::dskDevice.2 = STRING: swap
UCD-SNMP-MIB::dskDevice.3 = STRING: apps
UCD-SNMP-MIB::dskDevice.4 = STRING: data
UCD-SNMP-MIB::dskMinimum.1 = INTEGER: -1
UCD-SNMP-MIB::dskMinimum.2 = INTEGER: -1
UCD-SNMP-MIB::dskMinimum.3 = INTEGER: -1
UCD-SNMP-MIB::dskMinimum.4 = INTEGER: -1
UCD-SNMP-MIB::dskMinPercent.1 = INTEGER: 5
UCD-SNMP-MIB::dskMinPercent.2 = INTEGER: 10
UCD-SNMP-MIB::dskMinPercent.3 = INTEGER: 4
UCD-SNMP-MIB::dskMinPercent.4 = INTEGER: 3
UCD-SNMP-MIB::dskTotal.1 = INTEGER: 25821143
UCD-SNMP-MIB::dskTotal.2 = INTEGER: 7150560
UCD-SNMP-MIB::dskTotal.3 = INTEGER: 0
UCD-SNMP-MIB::dskTotal.4 = INTEGER: 0
UCD-SNMP-MIB::dskAvail.1 = INTEGER: 13584648
UCD-SNMP-MIB::dskAvail.2 = INTEGER: 6471520
UCD-SNMP-MIB::dskAvail.3 = INTEGER: 0
UCD-SNMP-MIB::dskAvail.4 = INTEGER: 0
UCD-SNMP-MIB::dskUsed.1 = INTEGER: 11978284
UCD-SNMP-MIB::dskUsed.2 = INTEGER: 679040
UCD-SNMP-MIB::dskUsed.3 = INTEGER: 0
UCD-SNMP-MIB::dskUsed.4 = INTEGER: 0
UCD-SNMP-MIB::dskPercent.1 = INTEGER: 47
UCD-SNMP-MIB::dskPercent.2 = INTEGER: 9
UCD-SNMP-MIB::dskPercent.3 = INTEGER: 0
UCD-SNMP-MIB::dskPercent.4 = INTEGER: 0
UCD-SNMP-MIB::dskPercentNode.1 = INTEGER: 9
UCD-SNMP-MIB::dskPercentNode.2 = INTEGER: 0
UCD-SNMP-MIB::dskPercentNode.3 = INTEGER: 0
UCD-SNMP-MIB::dskPercentNode.4 = INTEGER: 0
UCD-SNMP-MIB::dskErrorFlag.1 = INTEGER: noError(0)
UCD-SNMP-MIB::dskErrorFlag.2 = INTEGER: noError(0)
UCD-SNMP-MIB::dskErrorFlag.3 = INTEGER: noError(0)
UCD-SNMP-MIB::dskErrorFlag.4 = INTEGER: noError(0)
UCD-SNMP-MIB::dskErrorMsg.1 = STRING:
UCD-SNMP-MIB::dskErrorMsg.2 = STRING:
UCD-SNMP-MIB::dskErrorMsg.3 = STRING:
UCD-SNMP-MIB::dskErrorMsg.4 = STRING: As expected, dskPercent.1 and dskPercent.2 (ie. */* and */tmp*) returned good values. But why did Solaris/SNMP/??? return 0 for dskPercent.3 (*/apps*) and dskPercent.4 (*/data*)? Those directories are on two ZFS which are on seperate zpools:
--($ ~)-- zpool list
NAME   SIZE   USED AVAIL    CAP HEALTH ALTROOT
apps 39.2G 20.4G 18.9G    51% ONLINE -
data   136G   121G 15.2G    88% ONLINE -
--($ ~)-- zfs list apps data
NAME   USED AVAIL REFER MOUNTPOINT
apps 20.4G 18.3G    20K /apps
data   121G 13.1G   101K /dataOr is it supposed to be that way? I'm pretty much confused, because I found some blog posting by a guy called asyd at http://sysadmin.asyd.net/home/en/blog/asyd/zfs+snmp. Copying from there:
snmpwalk -v2c -c xxxx katsuragi.global.asyd.net UCD-SNMP-MIB::dskTable
UCD-SNMP-MIB::dskPath.1 = STRING: /
UCD-SNMP-MIB::dskPath.2 = STRING: /home
UCD-SNMP-MIB::dskPath.3 = STRING: /data/pkgsrc
UCD-SNMP-MIB::dskDevice.1 = STRING: /dev/dsk/c1d0s0
UCD-SNMP-MIB::dskDevice.2 = STRING: data/home
UCD-SNMP-MIB::dskDevice.3 = STRING: data/pkgsrc
UCD-SNMP-MIB::dskTotal.1 = INTEGER: 1017935
UCD-SNMP-MIB::dskTotal.2 = INTEGER: 0
UCD-SNMP-MIB::dskTotal.3 = INTEGER: 0
UCD-SNMP-MIB::dskAvail.1 = INTEGER: 755538
UCD-SNMP-MIB::dskAvail.2 = INTEGER: 0
UCD-SNMP-MIB::dskAvail.3 = INTEGER: 0
UCD-SNMP-MIB::dskPercent.1 = INTEGER: 21
UCD-SNMP-MIB::dskPercent.2 = INTEGER: 18
UCD-SNMP-MIB::dskPercent.3 = INTEGER: 5What I find confusing, are his dskPercent.2 and dskPercent.3 outputs - for him, he got back dskPercent for what seems to be directories on ZFS filesystems.
Because of that I'm wondering about how it is supposed to be - should Solaris return dskPercent values for ZFS?+
Thanks a lot,
Alexander

I don't have the ability to test out my theory, but I suspect that you are using the default mount created for the zpools you've created (apps & data) as opposed to specific ZFS files systems, which is what the asyd blog shows.
Remember, the elements reported on in the asyd blog ARE zfs file systems; they are not just directories. They are indeed mountpoints, and it is reporting the utilization of those zfs file systems in the pool ("data") on which they are constructed. In the case of /home, the administrator has specifically set the mountpoint of the ZFS file system to be /home instead of the default /data/home.
To test my theory, instead of using your zpool default mount point, try creating a zfs file system under each of your pools and using that as the entry point for your application to write data into the zpools. I suspect you will be rewarded with the desired result: reporting of "disk" (really, pool) percent usage.

Cannot get software RAID-1 going on root (/) on Sun V240's

Hi All,
I for the life of me cannot get software RAID-1 going on the root file-system. I've followed the instructions in Solaris Volume Manager Admin. Guide and I think I'm doing it right. This is in a Sun V240 with two 137GB drives.
I basically do the following:
Disk0 - c1t0d0s0
Disk1 - c1t0d1s0
prtvtoc /dev/rdsk/c1t0d0s2 | fmthard -s - /dev/rdsk/c1t1d0s2
prtvtoc /dev/rdsk/c1t1d0s2 (Double check that disk 1 looks like disk 2)
metadb -af -c 2 /dev/rdsk/c1t0d0s3 /dev/rdsk/c1t0d0s4
metadb -af -c 2 /dev/rdsk/c1t1d0s3 /dev/rdsk/c1t1d0s4
metainit -f d10 1 1 /dev/rdsk/c1t0d0s0
metainit -f d20 1 1 /dev/rdsk/c1t1d0s0
metainit d0 -m d10
metaroot d0
lockfs -fa
reboot
Before I reboot, I do a metastat and it shows the following:
# metastat
d0: Mirror
    Submirror 0: d10
      State: Okay
    Pass: 1
    Read option: roundrobin (default)
    Write option: parallel (default)
    Size: 20494464 blocks (9.8 GB)
d10: Submirror of d0
    State: Okay
    Size: 20494464 blocks (9.8 GB)
    Stripe 0:
        Device     Start Block Dbase        State Reloc Hot Spare
        c1t0d0s0          0     No            Okay   Yes
d20: Concat/Stripe
    Size: 20494464 blocks (9.8 GB)
    Stripe 0:
        Device     Start Block Dbase   Reloc
        c1t1d0s0          0     No      YesUpon reboot, I get this:
Rebooting with command: boot
Boot device: /pci@1c,600000/scsi@2/disk@0,0:a File and args:
SunOS Release 5.10 Version Generic 64-bit
Copyright 1983-2005 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
Cannot open mirrored root device, error 19
Cannot remount root on /pseudo/md@0:0,0,blk fstype ufs
panic[cpu1]/thread=180e000: vfs_mountroot: cannot remount root
000000000180b960 genunix:vfs_mountroot+2b8 (18aa800, 0, 185e6f8, 3000153dc40, 1859ce8, 4)
%l0-3: 0000000000000000 0000000000000003 00000000018a40b0 00000000018a40b0
%l4-7: 000000000185b800 00000000011cb000 00000000018aa800 0000000001834340
000000000180ba20 genunix:main+88 (1813c98, 1011c00, 1834340, 18a7c00, 0, 1813800)
%l0-3: 000000000180e000 0000000000000001 000000000180c000 0000000001835200
%l4-7: 0000000070002000 0000000000000001 000000000181ba54 0000000000000000
syncing file systems... done
skipping system dump - no dump device configured
rebooting...HELP! What am I doing wrong? Thanks!

You created to many metadatabases..
I'm not kidding, you did. You created 8 which i suspect trigged a bug which currently exists in Solaris 9 / Solaris 10.
This bug occours on the following disks: MAT3073N, MAT3147N, MAT3300N and ST373207LC, if you have any of those disks in your system (can be determined with iostat -En) you must use less than 8 replicas.
Check out bugreport 6244431, if you got a sunsolve login linked to a contract number.
You could try and boot up the system from a cdrom or similar and add "md_devid_destroy=1;" to the /kernel/drv/md.conf file above the 'Begin MDD database info' line.
hopefully your system will come up after this, if it does the best workaround is to remove a few replicas, the above line from md.conf and reboot.
Best regards,
//Magnus
Best regards,
//Magnus

IAS6sp2 / ias6sp4 on solaris 2.6 : classloader bug ?

Similar Messages

Maybe you are looking for