Sponsored Content
Full Discussion: Patching failed on Sun T2000
Operating Systems Solaris Patching failed on Sun T2000 Post 302696077 by hicksd8 on Tuesday 4th of September 2012 08:45:10 AM
Old 09-04-2012
It is difficult to say whether a M3000 would also fail to install a standard patchset.

I have patched a number of different hardware models with the latest patchsets without any problems except for the T2000. I also know of others, like yourself, who have hit the same problem.

Although I have not read every last detail about the latest patchset, Oracle do not seem to issue any specific warning about the T2000 falling over. However, without the latest OBP, it seems that is does.

Sadly, I have no experience with the M3000 model.

I would guess (and it is a guess) that you would not have any similar issue with a M3000, but absolutely no guarantees given. It depends on how much inconvenience it will cause you to recover a similar failure to patch as to whether you bring the OBP, etc up to date first.

Hope that helps.

Last edited by hicksd8; 09-05-2012 at 07:50 AM..
 

10 More Discussions You Might Find Interesting

1. SuSE

FAILED during patching kernel sources

Hi all. I have an issue with kernel patching. My system: OpenSuse 10.2, kernel version: 2.6.18.2. I've downloaded the patch from kernel.org - 2.6.26. I've invoked the following command: "patch -p1 -f < patch-2.6.26" (-f - because some files are not exist. to automatically skip this issues).... (2 Replies)
Discussion started by: Vourhey
2 Replies

2. Solaris

Sun Sparc T2000 + StorageTek 2540 - Help, I'm lost

I have a Sun Sparc T2000 (Solaris 10 05-08) and have installed a PCI-X 4GB Single Port HBA card in it. I have one StorageTek 2540 array that I would like to connect to the T2000. For the moment it would be a single path connection, but I've ordered a 2nd HBA, so eventually it would be... (4 Replies)
Discussion started by: soliberus
4 Replies

3. Solaris

Error while trying to boot from cdrom on Sun Fire T2000

Hi Guyz, I recently downloaded sol-10-u6-ga1-sparc-dvd.iso from Sun. I burned the disk as cd .iso. When trying to boot at the ok> boot cdrom i get the following error: ----------------------------------------------------------------------- Boot device:... (2 Replies)
Discussion started by: Mwamba
2 Replies

4. Solaris

Sun Server T2000 occasionally reboot

Hi, i am really 'fresh' to Solaris or any UNIX OS. My role as web developer but i need slightly involve to Solaris support. It is harder for me to understand it and i recently encounter a problems. /var file system (/dev/md/rdsk/d425) is being checked. run fsck -F ufs /dev/md/rdsk/d425 ... (8 Replies)
Discussion started by: webster5u
8 Replies

5. Solaris

Auto boot problem on Sun T2000

Hi All I have a problem on T2000 server. bash-3.00# uname -a SunOS 5.10 aaa Generic_120011-14 sun4v sparc SUNW,Netra-T2000After the initial solaris installation server failed to boot: Rebooting with command: boot Boot device: disk:b File and args: The file just loaded does not appear... (1 Reply)
Discussion started by: ouzist
1 Replies

6. Solaris

locator led SUN T2000

Hi Guys, I am unable to turn on the locator led light on a SUN T2000 machine # uname -a SunOS node1 5.10 Generic_137137-09 sun4v sparc SUNW,Sun-Fire-T200 when i try to turn it on I have following error. # locator -n 'system' locator not found Although the hardware specfication... (5 Replies)
Discussion started by: Asteroid
5 Replies

7. Solaris

Sun T2000 question

This may be a stupid question, but I don't want to take any chances. I have a Sun T2000 in production. I want to run the "resetsc" command on the ALOM controller to active an IP address change. Will resetting ALOM affect the running OS? Thanks (2 Replies)
Discussion started by: soliberus
2 Replies

8. Hardware

Hardware RAID on Sun T2000 Server

Hi All I have a Sun T2000 server. Couple of years ago I had configured and mirrored the boot drive with an other drive using hardware RAID 1 using raidctl command. Following is the hardware RAID output. root@oracledatabaseserver / $ raidctl RAID Volume RAID RAID Disk... (0 Replies)
Discussion started by: Tirmazi
0 Replies

9. Solaris

Sun T2000 error codes

I got a Power supply failure. I replaced the power supply and still got the error. Any ideas on what I should try next? (1 Reply)
Discussion started by: 642fiddi
1 Replies

10. Emergency UNIX and Linux Support

Solaris 10 patching failed

I was installing Solaris-10 Recommended patch Cluster and it came out without installling all patches. I gave a rebooted and tried installing it again, but it seems some lock or something is prevenventing to install further patches. I am not able to figure out and I am struck in between... (4 Replies)
Discussion started by: solaris_1977
4 Replies
inc::latest(3)						User Contributed Perl Documentation					    inc::latest(3)

NAME
inc::latest - use modules bundled in inc/ if they are newer than installed ones SYNOPSIS
# in Build.PL use inc::latest 'Module::Build'; DESCRIPTION
The "inc::latest" module helps bootstrap configure-time dependencies for CPAN distributions. These dependencies get bundled into the "inc" directory within a distribution and are used by Build.PL (or Makefile.PL). Arguments to "inc::latest" are module names that are checked against both the current @INC array and against specially-named directories in "inc". If the bundled version is newer than the installed one (or the module isn't installed, then, the bundled directory is added to the start of <@INC> and the module is loaded from there. There are actually two variations of "inc::latest" -- one for authors and one for the "inc" directory. For distribution authors, the "inc::latest" installed in the system will record modules loaded via "inc::latest" and can be used to create the bundled files in "inc", including writing the second variation as "inc/latest.pm". This second "inc::latest" is the one that is loaded in a distribution being installed (e.g. from Build.PL). This bundled "inc::latest" is the one that determines which module to load. Special notes on bundling The "inc::latest" module creates bundled directories based on the packlist file of an installed distribution. Even though "inc::latest" takes module name arguments, it is better to think of it as bundling and making available entire distributions. When a module is loaded through "inc::latest", it looks in all bundled distributions in "inc/" for a newer module than can be found in the existing @INC array. Thus, the module-name provided should usually be the "top-level" module name of a distribution, though this is not strictly required. For example, Module::Build has a number of heuristics to map module names to packlists, allowing users to do things like this: use inc::latest 'Devel::AssertOS::Unix'; even though Devel::AssertOS::Unix is contained within the Devel-CheckOS distribution. At the current time, packlists are required. Thus, bundling dual-core modules may require a 'forced install' over versions in the latest version of perl in order to create the necessary packlist for bundling. USAGE
When calling "use", the bundled "inc::latest" takes a single module name and optional arguments to pass to that module's own import method. use 'inc::latest' 'Foo::Bar' qw/foo bar baz/; Author-mode You are in author-mode inc::latest if any of the Author-mode methods are available. For example: if ( inc::latest->can('write') ) { inc::latest->write('inc'); } loaded_modules() my @list = inc::latest->loaded_modules; This takes no arguments and always returns a list of module names requested for loading via "use inc::latest 'MODULE'", regardless of whether the load was successful or not. write() inc::latest->write( 'inc' ); This writes the bundled version of inc::latest to the directory name given as an argument. It almost all cases, it should be '"inc"'. bundle_module() for my $mod ( inc::latest->loaded_modules ) { inc::latest->bundle_module($mod, $dir); } If $mod corresponds to a packlist, then this function creates a specially-named directory in $dir and copies all .pm files from the modlist to the new directory (which almost always should just be 'inc'). For example, if Foo::Bar is the name of the module, and $dir is 'inc', then the directory would be 'inc/inc_Foo-Bar' and contain files like this: inc/inc_Foo-Bar/Foo/Bar.pm Currently, $mod must have a packlist. If this is not the case (e.g. for a dual-core module), then the bundling will fail. You may be able to create a packlist by forced installing the module on top of the version that came with core Perl. As bundled in inc/ All methods are private. Only the "import" method is public. AUTHOR
Eric Wilhelm <ewilhelm@cpan.org>, David Golden <dagolden@cpan.org> COPYRIGHT
Copyright (c) 2009 by Eric Wilhelm and David Golden This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself. SEE ALSO
Module::Build perl v5.16.3 2014-06-10 inc::latest(3)
All times are GMT -4. The time now is 03:54 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy