Solaris 8 Patch Cluster 200801 installation / disk utilization spikes

Hello All,
Since we installed the latest Patch Cluster patch our disk utilization has shot up substantially. Is there anyone having same experience? If you do, could you please help us to identify some areas to take a look?
Thanks very much.
Yi

hi again. i just fixed my problem. apparently when i unzipped the file and then burned it onto cd...the data got corrupted. i fixed it by copying the zip file onto cd and then extracting the patches onto the solaris machine.

Similar Messages

Solaris Cluster and VMware Disk and SCSI Sharing Questions

Hello folks,
Does Solaris Clustering support the following?
Oracle Solaris 11 Cluster support shared disk using VMware 5.1 RDM?
Oracle Solaris 11 Cluster using VMware SCSI Bus Sharing? (although VMware doesn’t support this)
Best,
Dave

Hello folks,
Does Solaris Clustering support the following?
Oracle Solaris 11 Cluster support shared disk using VMware 5.1 RDM?
Oracle Solaris 11 Cluster using VMware SCSI Bus Sharing? (although VMware doesn’t support this)
Best,
Dave

Solaris 8 x86 patch cluster installation

hi. i recently installed solaris 8 x86 on my intel p4 machine. i got through the installation fine but i am now running into problems with installing the 8x86 recommended patch cluster.
whenever i run the install_cluster script, it says every patch failed to install due to return code 1. i even tried manually installing the patches manually via patchadd...but i end up getting a message saying the patch directory is not valid.
i basically downloaded the 8x86 recommended patch cluster zip file on a windows 2k machine. i unzip the file and then burn the patches onto a cd. i then copy the patches from the cd onto my solaris machine and try to install the patches that way. so far...this doesn't work..and i dont know what im doing wrong.
does anyone know how to fix this problem? thx.

hi again. i just fixed my problem. apparently when i unzipped the file and then burned it onto cd...the data got corrupted. i fixed it by copying the zip file onto cd and then extracting the patches onto the solaris machine.

Solaris 2.6 Patch cluster

Is there anyone out there knows where I can get the last Solaris 2.6 patch cluster? I know it's de-supported now but sadly some legacy applications are still out there and need to run on old software/hardware.
Many thanks in advance,
Jonathan

if you run a pstack against the core, I might
recognize the failure. Usually, logging is of no
use, as we don't log a crash. . .Thanks. I'll do that. It just generated a new core file.
>
I don't know of any problems with installing 4.15p7,
nor of installing later hotfixes on top of it, and
I've been supporting Messaging Server since 4.0 came
out. . . .
If you've had file permission issues since 4.05,
that's truly news to me, unless it was that pesky
problem with Admin Server, where it would change the
permissions of the logs when it went to roll them
over. I don't remember when we fixed that one, but
we did..We've had file permission issues with the patches since 4.0. When we'd upgrade some of the files would be owned by root and not exec'able by nobody. Some of the patches would fail when the patch process would try to bind to the directory (I don't know why). We've used NMS since the 3.x version. It has also been a long time since we tried to patch to app because our experience was bad. It was stable for a long time (once we disabled shared folders and resolved the nscd issue).

Solaris 8 patches added to Solaris 9 patch cluster and vice versa

Has anyone noticed this? On the Solaris 8 and 9 patch cluster readmes, it shows sol 9 patches have been added to the sol 8 cluster and sol 8 patches have been added to the sol 9 cluster. what's the deal? I haven't found any information about whether or not this is a mistake.

Desiree,
Solaris 9's kernel patch 112233-12 was the last revision for that particular patch number. The individual zipfile became so large that it was subsequently supplanted by 117191-xx and that has also been supplanted when its zipfile became very large, by 118558-xx.
Consequently you will never see any newer version than 112233-12 on that particular patch.
What does <b>uname -a</b> show you for that system?
Solaris 8 SPARC was similarly effected, for 108528, 117000 and 117350 kernel patches.
If you have login privileges to Sunsolve, find <font color="teal">Infodoc 76028</font>.

Solaris boot problem after Patch cluster install

just wondering if anyone can assist. i have just installed solaris 10 x86 recommended patches on a 16 disks server. where first 2 disks are mirrored called rpool, and remaining 14 disks are raid z called spool. upon installing the patches successfully and rebooting server, i am coming up with the following error:
NOTICE: Can not read the pool label from '/pci@0,0/pci8086,25f8@4/pci111d,801c@0/pci111d,801c@4/pci108e,286@0/disk@0,0:a /pci@0,0/pci8086,25f8@4/pci111d,801c@0/pci111d,801c@4/pci108e,286@0/disk@1,0:a'
NOTICE: spa_import_rootpool: error 5, Inc. All rights reserved.
Cannot mount root on /pci@0,0/pci8086,25f8@4/pci111d,801c@0/pci111d,801c@4/pci108e,286@0/disk@0,0:a /pci@0,0/pci8086,25f8@4/pci111d,801c@0/pci111d,801c@4/pci108e,286@0/disk@1,0:a fstype zfs
panic[cpu0]/thread=fffffffffbc28820: vfs_mountroot: cannot mount root
fffffffffbc4b190 genunix:vfs_mountroot+323 ()
fffffffffbc4b1d0 genunix:main+a9 ()
fffffffffbc4b1e0 unix:_start+95 ()
skipping system dump - no dump device configured
rebooting...
It looks like the solaris 10 os cannot find zfs filesystem and keeps on rebooting in normal solaris os mode, but when I go to safe mode and type: zfs list, I can see zfs rpool (mirrored) file system and cannot see the zfs spool (raid z) file system, any ideas on how i can fix the boot problem and get zfs spool back in the safest way possible?...

Same problem here with actual recomended patch set.
NOTICE: Can not read the pool label from '/pci@0,0/pci10de,375@f/pci1000,3150@0/sd@0,0:a /pci@0,0/pci10de,375@f/pci1000,3150@0/sd@1,0:a'
NOTICE: spa_import_rootpool: error 5
Cannot mount root on /pci@0,0/pci10de,375@f/pci1000,3150@0/sd@0,0:a /pci@0,0/pci10de,375@f/pci1000,3150@0/sd@1,0:a fstype zfs
panic[cpu0]/thread=fffffffffbc28820: vfs_mountroot: cannot mount root
fffffffffbc4b190 genunix:vfs_mountroot+323 ()
fffffffffbc4b1d0 genunix:main+a9 ()
fffffffffbc4b1e0 unix:_start+95 ()
What the hell happened to the bootsektor or the pool or what ever?

Patch cluster 3/26/10 will hose X4500 disk management task in multiuser

I just want to warn user about the potential problem that you will encounter if you have a SUN X4500 system.
After applying patch cluster 3/26/10 on a SUN X4500 (thumper), now I can not do many disk management tasks in multiuser mode, such as
format
zpool create
and possibly many more commands (involving disk devices) would just hang.
Drop it to single user mode, however, you CAN still do these management task. I had to create zpool in single user mode
zfs create pool/zfsset still works in multiuser mode.
Thank you for your attention.

I'm having exactly the same problem on an x4500 server running OpenSolaris snv_127. We suffered a disk failure (c7t0d0), so I resilvered one of the pools onto a spare drive, which succeeded:
# zpool history data
<snip>
2010-04-20.14:45:08 zpool offline data c7t0d0
2010-04-20.14:58:19 zpool replace -f data c7t0d0 c7t1d0
# zpool status data
pool: data
state: ONLINE
scrub: resilver completed after 43h58m with 0 errors on Thu Apr 22 10:56:50 2010
config:
NAME STATE READ WRITE CKSUM
data ONLINE 0 0 0
raidz2-0 ONLINE 0 0 0
c11t1d0 ONLINE 0 0 0
c10t1d0 ONLINE 0 0 0
c13t1d0 ONLINE 0 0 0
c12t0d0 ONLINE 0 0 0
c8t1d0 ONLINE 0 0 0
c12t1d0 ONLINE 0 0 0
c10t0d0 ONLINE 0 0 0
c10t7d0 ONLINE 0 0 0
c12t2d0 ONLINE 0 0 0
c8t0d0 ONLINE 0 0 0
c7t1d0 ONLINE 0 0 0 381G resilvered
As you can see, the drive c7t0d0 has been successfully replaced and no longer appears in any zpool:
# zpool status | grep c7t0d0
# iostat -En | grep c7t0d0
c7t0d0 Soft Errors: 2 Hard Errors: 4 Transport Errors: 0
# cfgadm -l | grep c7t0d0
sata1/0::dsk/c7t0d0 disk connected configured ok
However when I attempt to unconfigure the sata port in preperation for replacing the drive, it doesn't work:
# cfgadm -c unconfigure sata1/0
Unconfigure the device at: /devices/pci@0,0/pci1022,7458@1/pci11ab,11ab@1:0
This operation will suspend activity on the SATA device
Continue (yes/no)? yes
cfgadm: Hardware specific failure: Failed to unconfig device at ap_id: /devices/pci@0,0/pci1022,7458@1/pci11ab,11ab@1:0
Also just pulling out the drive doesn't work, you end up with an unusable unconfigured port:
# cfgadm -l | grep unusable
sata6/0 disk connected unconfigured unusable
It's highly frustrating, because it means to replace disks we'll have to shut this server down. Not ideal!
I'm fairly certain this used to work fine.
If anyone has a solution, I'm all ears. I'm going to update this box to snv_130 soon (mainly to get the new zfs resilvering code) but I'm not hopeful about this bug/issue.
Regards,
Alasdair

MB.ACT light OFF --- after Solaris 9 recommended patch cluster applied

After applying the recommended patch cluster to several SunFire V210s/V240s the "system ready" or "activity" light on the front panel no longer illuminates. The systems come up fine and are fully functional, just no light.
While this has absolutely no impact on usability it is a bit disconcerting for the folks in the server room when glancing at the rack and not seeing the typical green light.
I first noticed the problem in mid 2007 and have tried patch clusters as recent as last month, but the light remains out.
One interesting discovery is that if I reset (hard) the ALOM module the light comes back on. However, if the system is subsequently rebooted for any reason the light does not come back on...
If anyone can shed some light on the issue I would greatly appreciate it!
-Sap

continued.
I removed patch 138217-01 (svccfg & svcprop patch) and re-applied it.
Then, after booting into S-mode, I tried to continue with the broken patch 139555-08 (kernel).
It ends with
! root@jumpstart:/var/spool/patch # patchadd 139555-08
Validating patches...
Loading patches installed on the system...
Done!
Loading patches requested to install.
Preparing checklist for non-global zone check...
Checking non-global zones...
This patch passes the non-global zone check.
139555-08
Summary for zones:
Zone oem
Rejected patches:
None.
Patches that passed the dependency check:
139555-08
Patching global zone
Adding patches...
Checking installed patches...
Executing prepatch script...
Installing patch packages...
Pkgadd failed. See /var/tmp/139555-08.log.21103 for details
Patchadd is terminating.
! root@jumpstart:/var/spool/patch #the logfile shows
! root@jumpstart:/var/spool/patch # vi /var/tmp/139555-08.log.21103
Dryrun complete.
No changes were made to the system.
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
pkgadd: ERROR: couldn't lock in /var/run/.patchSafeMode/root/var/sadm/install (s
erver running?): Resource temporarily unavailable
Installation of <SUNWarc> failed (internal error).
No changes were made to the system.Help!
-- Nick

Solaris reboot loop after recommended patch cluster

Hi,
I have a problem with my solaris 10 x86 install on my intel notebook. after installing the latest recommended patch cluster and the necessary reboot my latop stays in a loop.
one of the last lines I was able to see:
panic[cpu0]/thread=fec1d660: boot_mapin():No pp for pfnum=20fff
fec33b4c genunix:main+1b ()
skipping system dump - ....
rebooting...
any ideas ?
cu+thx

This horrible patch caught me out too. I found this and it fixed my problem.
http://weblog.erenkrantz.com/weblog/software/solaris
<snip>
[...at the Solaris boot prompt; enable kmdb, debugging, and single-user
so that you can remove the patch and reboot...]
boot -kds
[...wait for it to boot...]
physmax:w
:c
[...you'll see 'stop on write of'...]
physmax/X
[...you'll see something like the following line:
physmax: bff7f
this is a hex number; add one; so if you see bff7f,
your next line will need to be bff80...]
physxmax/W bff80
:c
[...system will boot and go into single user mode...
now, go toss those patches...]
patchrm 118844-19 120662-03 118345-12 118376-04 \
118565-03 118886-01 119076-10 118813-01 \
118881-02 120082-07 119851-02
shutdown -i6 -y -g0 "sun should test their patches"
</snip>

Need patchset/patch cluster for solaris 10 5/09 update 7 to update8

Please let me know where i can download the patch cluster or patchset to upgrade solaris 10 5/09 from update 7 to update8
Solaris 10 5/09 s10s_u7wos_08 SPARC to Solaris 10 5/09 s10s_u8wos_08 SPARC
Its a 64 bit SPARC
Thanks in advance.
With Regards
Suresh Rao Jc
Edited by: user13549783 on 14-Apr-2012 05:55

Moderator Advice:
Welcome to the OTN forums.
This is your very first post to the forums, so before you go any further, a piece of advice:
When you give your post a title of "Hi All" it does not tell anyone anything about what your inquiry might be.
The topic title that you place onto each one of your posts is just as important as what you place into your post. It tells everyone whether they need to spend any time with it. It tells everyone whether you are worth spending time with, whether you will be able to understand what they type in a reply, how technical they can be in a response.
These are technical forums. They are not chat rooms for casual feel-good gatherings. They are not `blogs`. The site is also NOT a way to make contact to Oracle's technical support staff. The OTN community is from the entire globe and is from end-users that happen to have an interest in the topics you read here.
Spend some time reading the forum FAQ,
https://wikis.oracle.com/display/Forums/Forums+FAQ
which is linked at the top corner of every page.
Also, spend some time with the forums Terms Of Use
http://www.oracle.com/us/legal/terms/index.html
which is linked at the bottom of every page.
In particular, spend some time reviewing section #6 in that T.O.U.
When you make your posts more informative and easier to read then responses will be more helpful.
... now go back and edit your post. Change the title to something that better describes your actual question.

Solaris 10 SPARC Recommended Patch Cluster for 2008 quarter 3 version

Dear All,
Could any one please guide me, where I can download "Solaris 10 SPARC Recommended Patch Cluster" for 2008 quarter 3 version.
I have checked in sunsolve.sun.com, I'm able to find only the latest release.
please guide me.
Thanks and regards,
veera

Ok,
Here's a cute little formula to try using your systems parameters to gain some "head's-up" on an expected or estimated time to complete the patch run.
You will need a few things to prepare.
Number of "real" CPU's (not hyperthreads)
Speed of each CPU as a whole number i.e 2.87Ghz = 2,867
the total number of patches from the cluster i.e. Sept 15th = 381 (Solaris 10)
Network factor if using NFS = 2.5
local cluster file factor = 1.5
Patch cluster on CDROM factor = 3.25
Now, combine all of those elements in this equation:
{ ( #1 * #2 ) / #3 * factor(#4 or #5 or #6) }
This will yield a number in minutes of patch run time. Then all you will need to add is the standard boot up time to get the total of all patching and reboot.
Of course you could write a script to extract all of this information and feed it to "bc -l" to get a quick figure.
Example, on one of my Solaris 10 boxes with the information filled in to the equation:
#> echo "((4*2660)/381)*1.5"|bc -l
#> 41.88976377952755905511
It actually took 44.2 minutes to complete the patching of this box plus another 12 minutes to reboot. But all in all a pretty fair estimate I think.

How to backout a Recommended Patch cluster deployment in Solstice disksuite

Hello Admin's,
I am planning to use the following Plan of action for deploying the latest Solaris 8 Recommended Patch cluster on the production server's i support.My
concern is if the patching activity fails or the application and Oracle databases dont come up after deploying the patch cluster.How do i revert back to system to its original state using the submirror's which i have detached prior to patching the system :
1) Will shutdown the applications and the databases on the server:
2) Will capture the output of the following commands :
df -k
ifconfig -a
contents of the files /etc/passwd /etc/shadow /etc/vfstab /etc/system
metastat -p
netstat -rn
prtvtoc /dev/rdsk/c1t0d0s0
prtvtoc /dev/rdsk/c1t1d0s0
3) We bring the system to the ok prompt
4) We will try to boot the system from both the disk's which are part of the d10 metadevice for root filesystem
=======================================================================================
user1@myserver>pwd ; df -k / ; ls -lt | egrep '(c1t0d0s0|c1t1d0s0)' ; prtconf -vp | grep bootpath ; metastat d10
/dev/dsk
Filesystem kbytes used avail capacity Mounted on
/dev/md/dsk/d10 8258597 3435895 4740117 43% /
lrwxrwxrwx 1 root root 43 Jul 28 2003 c1t0d0s0 -> ../../devices/pci@1c,600000/scsi@2/sd@0,0:a
lrwxrwxrwx 1 root root 43 Jul 28 2003 c1t1d0s0 -> ../../devices/pci@1c,600000/scsi@2/sd@1,0:a
bootpath: '/pci@1c,600000/scsi@2/disk@0,0:a'
d10: Mirror
Submirror 0: d11
State: Okay
Submirror 1: d12
State: Okay
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 16779312 blocks
d11: Submirror of d10
State: Okay
Size: 16779312 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t0d0s0 0 No Okay
d12: Submirror of d10
State: Okay
Size: 16779312 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t1d0s0 0 No Okay
user1@myserver>
===================================================================================
ok nvalias backup_root <disk path>
Redefine the boot-device variable to reference both the primary and secondary submirrors, in the order in which you want to access them. For example:
ok printenv boot-device
boot-device= disk net
ok setenv boot-device disk backup_root net
boot-device= disk backup_root net
In the event of primary root disk failure, the system automatically boots from the secondary submirror. To test the secondary submirror, boot the system manually, as follows:
ok boot backup_root
user1@myserver>metadb -i
flags first blk block count
a m p luo 16 1034 /dev/dsk/c1t0d0s7
a p luo 1050 1034 /dev/dsk/c1t0d0s7
a p luo 2084 1034 /dev/dsk/c1t0d0s7
a p luo 16 1034 /dev/dsk/c1t1d0s7
a p luo 1050 1034 /dev/dsk/c1t1d0s7
a p luo 2084 1034 /dev/dsk/c1t1d0s7
o - replica active prior to last mddb configuration change
u - replica is up to date
l - locator for this replica was read successfully
c - replica's location was in /etc/lvm/mddb.cf
p - replica's location was patched in kernel
m - replica is master, this is replica selected as input
W - replica has device write errors
a - replica is active, commits are occurring to this replica
M - replica had problem with master blocks
D - replica had problem with data blocks
F - replica had format problems
S - replica is too small to hold current data base
R - replica had device read errors
user1@myserver>df -k
Filesystem kbytes used avail capacity Mounted on
/dev/md/dsk/d10 8258597 3435896 4740116 43% /
/dev/md/dsk/d40 2053605 929873 1062124 47% /usr
/proc 0 0 0 0% /proc
fd 0 0 0 0% /dev/fd
mnttab 0 0 0 0% /etc/mnttab
/dev/md/dsk/d30 2053605 937231 1054766 48% /var
swap 2606008 24 2605984 1% /var/run
swap 6102504 3496520 2605984 58% /tmp
/dev/md/dsk/d60 13318206 8936244 4248780 68% /u01
/dev/md/dsk/d50 5161437 2916925 2192898 58% /opt
user1@myserver>metastat d40
d40: Mirror
Submirror 0: d41
State: Okay
Submirror 1: d42
State: Okay
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 4194828 blocks
d41: Submirror of d40
State: Okay
Size: 4194828 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t0d0s4 0 No Okay
d42: Submirror of d40
State: Okay
Size: 4194828 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t1d0s4 0 No Okay
user1@myserver>metastat d30
d30: Mirror
Submirror 0: d31
State: Okay
Submirror 1: d32
State: Okay
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 4194828 blocks
d31: Submirror of d30
State: Okay
Size: 4194828 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t0d0s3 0 No Okay
d32: Submirror of d30
State: Okay
Size: 4194828 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t1d0s3 0 No Okay
user1@myserver>metastat d50
d50: Mirror
Submirror 0: d51
State: Okay
Submirror 1: d52
State: Okay
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 10487070 blocks
d51: Submirror of d50
State: Okay
Size: 10487070 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t0d0s5 0 No Okay
d52: Submirror of d50
State: Okay
Size: 10487070 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t1d0s5 0 No Okay
user1@myserver>metastat -p
d10 -m d11 d12 1
d11 1 1 c1t0d0s0
d12 1 1 c1t1d0s0
d20 -m d21 d22 1
d21 1 1 c1t0d0s1
d22 1 1 c1t1d0s1
d30 -m d31 d32 1
d31 1 1 c1t0d0s3
d32 1 1 c1t1d0s3
d40 -m d41 d42 1
d41 1 1 c1t0d0s4
d42 1 1 c1t1d0s4
d50 -m d51 d52 1
d51 1 1 c1t0d0s5
d52 1 1 c1t1d0s5
d60 -m d61 d62 1
d61 1 1 c1t0d0s6
d62 1 1 c1t1d0s6
user1@myserver>pkginfo -l SUNWmdg
PKGINST: SUNWmdg
NAME: Solstice DiskSuite Tool
CATEGORY: system
ARCH: sparc
VERSION: 4.2.1,REV=1999.11.04.18.29
BASEDIR: /
VENDOR: Sun Microsystems, Inc.
DESC: Solstice DiskSuite Tool
PSTAMP: 11/04/99-18:32:06
INSTDATE: Apr 16 2004 11:10
VSTOCK: 258-6252-11
HOTLINE: Please contact your local service provider
STATUS: completely installed
FILES: 150 installed pathnames
6 shared pathnames
19 directories
1 executables
7327 blocks used (approx)
user1@myserver>
=======================================================================================
5) After successfully testing the above we will bring the system to the single user mode
# reboot -- -s
6) Detach the following sub-mirrors :
# metadetach -f d10 d12
#metadetach -f d30 d32
#metadetach -f d40 d42
#metadetach -f d50 d52
# metastat =====> (to check if the submirror�s are successfully detached)
7) Applying patch on the server
After patch installation is complete will be rebooting the server to single user mode
# reboot -- -s
confirming if patch installation was successful (uname �a) .
8) Will be booting the server to the multiuser mode (init 3) and confirming with the database and the application teams if the
Applications/databases are working fine .Once confirmed successful will be reattaching the d12 submirror.
# metattach d12 d10
# metattach d30 d32
#metattach d40 d42
# metattach d50 d52
# metastat d10 =====> (to check the submirror is successfully reattached)
user1@myserver>uname -a ; cat /etc/release ; date
SunOS myserver 5.8 Generic_117350-04 sun4u sparc SUNW,Sun-Fire-V210
Solaris 8 HW 12/02 s28s_hw1wos_06a SPARC
Copyright 2002 Sun Microsystems, Inc. All Rights Reserved.
Assembled 12 December 2002
Mon Apr 14 17:10:09 BST 2008
-----------------------------------------------------------------------------------------------------------------------------

Recommended patch sets are and to the best of my knowledge have always been regenerated twice a month.
I think your thinking of maintenance releases. When they generate a new CD image which can be used to do an upgrade install.
They try to generate those every 6 months, but the schedule often slips.
The two most recent were sol10 11/06 and sol10 8/07.

Grid Control showing excessive amount of disk utilization.

Hi Folks,
I understand that Oracle doesn't support their products 100% on non Oracle VMs, but I thought I might take a stab at it.
I decided to stick with a simple installation of Oracle Grid Control running on a Windows 2003 R2 32 bit os, here are the steps I took.
1. Run Guest OS Windows 2003 R2 32 bit on a Windows 2008 x64 running Hyper-V (Yes I know why not EL5 running XEN, long story)
2. Install Grid Control with Database and Agent versions 10.2.0.2.1
3. Patch agent and oms to 10.2.0.5.0
4. Some minor issues, but managed to get by those.
- First off EM Website shows down, got to take a look at that, probably need to fix the beacon, not sure!
Problem:
- Grid shows that the host running em is over 100% disk utilization.
- According to Metalink this is a known bug in Windows 2000 Performance Counters (not 2003?)
- More specially Microsoft KB article Q310067.
- Metalink Doc Id: 303788.1
- Note, I'm running 2003 on a Hyper-V Guest, so anything can go wrong!
The specific error is:
Metric               Disk Device Busy (%)
Disk Device               0 C:
Severity               Critical
Alert Triggered          Jun 3, 2009 7:57:54 PM
Last Updated          Jun 4, 2009 3:48:48 PM
Acknowledged          No
Acknowledged By     n/a
Message               Disk Utilization for 0 C: is 587.86%, crossed warning (80) or critical (95) threshold.
More info:
- Guest is running on a Dual Quad Core Xeon System with 16 GB of RAM
- Guest has dedicated 4096MB of ram
- Guest has dedicated 2 CPUS
- Guest is configured with a Virtual Disk (specifically partition c:\) to be on local Hyper-V disk array
- Windows 2008 Hyper-V host disk array is in a RAID 5 configuration running 10k SAS drives
- Windows 2008 Hyper-V host utilization is literary at most 5% (current is 1%)
- Windows 2008 Hyper-V disk utilization according to graphs is showing 100KB/s usage (less than 1%)
Temporary solution is to turn off the metric, but not sure if that's such a good idea.
- Note that 11g EM and 10g EM running on Hyper-V server had the same issue.
- Note that 11g EM and 10g EM running without visualization had no issues.
Any thoughts?

It may be related to Bug 8677212: BACKUP INFORMATION FOR SOME DATABASES SHOWS INCORRECTLY
Although bug info says it for HP-UX, I've also seen the same problem on Grid Control 10.2.0.5 running on Solaris.
You may want to apply 10.2.0.5.4 Grid Control Patch Set Update (PSU) [ID 1139563.1] to fix it.
Best Regards,
Gokhan Atil
If this question is answered, please mark appropriate posts as correct/helpful and the thread as closed. Thanks

Management console problem after installing recommended patch cluster

Hello everyone.
I just got a new SUN 440 server, it didn't come with the solaris os installed and so I installed solaris 9 12/03 to it. The installation went fine and I could start the management console with no problems at all. Then I went to sunsolve.sun.com to download the latest recommended patch clusters for solaris 9 (this was yesterday Sept.-06-2006), I downloaded the file, checked it with md5sum, unzipped it, went to single user mode and ran the install_patch script. After the patch cluster finished installing I rebooted the server for the patches to take effect, I logged in, tried to run console management 2.1 and it starts OK but I cannot use any services it offers because it says (in the console events):
"Server Not Running: no solaris management console server was available on the specified server. Please ensure there is a Solaris Management Console server available on the specified host and that it is running"
When I click on "See Exception" I get (for a particular service that is... in this case com.sun.admin.fsmgr.client.VFsMgr - for managing file systems):
java.rmi.RemoteException: Server RMI is null:
at sun.com.management.viperimpl.client.ViperClient.lookupServer(ViperClient.java:376)and so on...
I already checked that the service is running on port 898 and it seems that there is no other app. using that same port. I also restarted the service using /etc/init.d.init stop/status/start but I get the same results.
I don't know solaris very much and don't know what else to do, please help.
Thanks in advance.

Well, I guess what you see isn't what you get.
Guess I'm used to the fact USENET just left things formatted the way they were :-O

PI 7.0 Cluster based Installation

Hi all,
         I did Central System installation but never installed High Availability sytem. We got a requirement for a cluster based installation.
I have gone through some links and got a basic idea, but not perfect in starting installation. Could you pls. help me in understanding for a successfully installation. (Requirement: Install SAP Netweaver PI 7.0 in Production Server).
For a High Availability syetm i have seen the following options to follow as per SAPINST:
1.) Central Services Instance for ABAP (ASCS) --   Consists of Msg. service & Enqueue Service (Shared Disk)
2.) Central Services Instance (SCS)                   --   Consists of Msg. service & Enqueue Service (Should be installed after installation of 1.)                                                                                (Same Shared Disk)
3.) Microsoft Cluster Service (MSCS)                 --   This step creates the SAP cluster group on the first MSCS node and adds the ASCS                                                                                and SCS instance(s) to the SAP cluster group
4.) Database Instance
5.) Microsoft Cluster Service (MSCS)
6.) Enqueue Replication Server
7.) Central Instance                                           -- If you install the central instance on one of the MSCS nodes, make sure that you use a                                                                                local drive, not a shared drive.
8.) Dialog Instance                                            -- You have to install at least one dialog instance. Make sure that you install the dialog                                                                                instance on a host other than the central instance host.
>> I guess that we need to install ASCS(1) and SCS(2) in two seperate systems, but what is that shared disk?(Aslo mentioned that NFS must be installed?) [It means that we require 2 hosts?]
>> Mentioned that one Enqueue Replication Server (ERS) for each Java SCS and one ERS for each ABAP SCS (ASCS) installed in your system. [It means that we require 2 hosts?]
>> Do we need to install all the above mentioned instances only in Windows or will this work on any platform?? [Example: SOLARIS]
>> Database Instance on 1 host, Central instance in 1 host --- That means we require a total of 6 hosts (excluding Dialog Instance??)
Pls. suggest whether my undertanding is correct or not???
Thanks & Regards,
Subbu

Dimitrios,
Check the below links
Installation
High Availability
Cheers
Agasthuri

Solaris 8 Patch Cluster 200801 installation / disk utilization spikes

Similar Messages

Maybe you are looking for