Sequence of Applying Kernel Patches

Hi All,
We have ECC 5.0 (Central Instance) OS:HP UNIX and four Dialog Instances on Windows Platform.
For Applying the latest kernel patches what should be the sequence, first dialog instances or Central Instance?
For this landscape is it required that while applying kernel patch Database should be in shutdown mode?
Regards,
Prashant.

Dear,
>First we have to apply Support pack in the Dialog instance
Its not first dialog instance.
Please follow below steps.
1. shutdown all dialog instances.
2. take backup of current kernel directory
3. stop central instance
4. switch the kernel files from new kernel
5. start the central instance.If its successfully up with new patch level then
6. One by one start the dialog instance.
Note: If the dialog instances sharing the path of Central instance Kernel directory then no need to do anything on dialog instances. Sapcpe program will copy new kernel to dialog instance local kernel directory automatically while restarting the dialog instances.
If dialog instances not sharing the path of CI then repeat the same procedure as of CI for DI's.
Edited by: Imran Mulani on Sep 11, 2008 9:29 AM

Similar Messages

Applied Kernel Patch to Solaris 10 on v40z, no longer auto boots

I recently updated the patches on a v40z machine including a kernel patch. After rebooting, the machine would no longer automatically boot to Solaris. Instead it would just wait for user input at the Grub bootloader screen. Anyone experienced this or have a solution?
I believe the patch in question is 118855-19
# bootadm list-menu
The location for the active GRUB menu is: /boot/grub/menu.lst
default 0
timeout 10
0 Solaris 10 6/06 s10x_u2wos_09a X86
1 Solaris failsafe

SOLVED:
Disabled ECC in the bios (though Windows and Gentoo Linux show now trouble whatsoever with my ECC memory, solaris doesn't like it)

Unable to boot the sytem after applying kernel patch 118844-27

We have an hp ProLiant DL380 Storage server connected to HP StorageWorks Moduler Smart Array 30 via SCSI. Solaris 03/05 was installed previously on this system with kernel 118844-20. When I queried and installed all required patches with 'smpatch add -i .. ' command, all patches applied and the system is rebooted. After reboot, the system kept restarting. I followed the instructions on Sun Alert document 102087, and installed grub using 01/06 1st CDROM. It installed successfully, but problem persisted. The systems started booting, but before printing 'Configuring devices' the system rebooted again. Providing -v option to the kernel, it lastly printed a PCI device id (/pci@....) and after 2-3 seconds rebooted again.
Finally I had to reinstall the solaris (this time 01/06). The disk was accessible after booting with CD ROM, and I was able to get cylinder numbers of disk, and I installed the new system to the root partition of the other live upgrade environment. The boot disk was partitioned under linux, it was three partitions, Solaris2 (50GB),Solaris(4GB),Linux(18GB). Installation medium told that the fdisk partition was invalid, and i repartitioned the whole disk again.
System up and running Solaris 10 01/06 now, but the strange thing is that, previously hard disk (both boot disk and disks on array) locations were identified as '/dev/rdsk/c0tx' but now, the system sees that hard disks at '/dev/c1tx' and CDROM at '/dev/c0t0'.
Now I want to ask tow questions:
* Could this disk number change made the system unbootable previously?
* May I safely apply patch 118844-28 to the system
-Thanks

Here's a similar topic https://bbs.archlinux.org/viewtopic.php?pid=536210 also if that doesn't work you should install vesa as it also says it's not found in your log.

SAP Kernel patch/Support pack Sequence

Hi,
I wanted to know if i need to follow up any order in applying latest kernel patch & Support Pack.
I have installed WAS 6.40 SR1 & want to upgrade to SPS 16. Before applying support pack do i need to apply latest
kernel ?
Is there any side effects for applying latest kernel patch ?
Kindly help me
Thanks,
ramki

Ramki, as other posts say the kernel update is part of SPS16 & should always be applied. But as to the order... it will most likely come down to business requirements and preference & may change for you from stack to stack.
Be sure to test first in your DEV environment (or similar) & always check the known issues notes which should tell you any patch to kernel dependancies that may dictate what order you have to install things (782140 is the note for WAS6.20, sorry don't have the WAS640 note number handy).
In terms of side effects? In my experience (4.0b - ecc6) the kernel will either work or not work (ie system will or wont start!) If it dosn't work roll back to the previous version (also keep a copy of the exe directory!) & things should all be OK.
Generally we always apply the kernel after the patches where I work (just fits in better with managing downtime on prod systems). However last time we patched the SPAM queue we defined was very large & not compatible with our R3Trans release when using the downtime minimised option (this was stated in the known issues note I mentioned earlier). So the kernel update was done 2-3 weeks before we rolled the patches in, once again just to manage prod system downtime better.
Hope that helps a little
Danny

Can i get collection of kernel patches in 1 EXE.....

Hi,
We found around 40 kernel patches and 20 oracle patches in service market place. Is there any option where we can get 1exe file for all 40 kernel patches(
34 are independent & 6 are dependent) & 1exe for all 20 oracle patches?
Where can i find patches for BRTOOLS in market place?
We thought of installing Oracle and thn the patches, then apply kernel & its patches and then once SAPINST is complete go for BI cont 3.53 installtion. Is the sequence i mentioned correct ?
Thanks for your valuable time .........
Bob

You don´t need all of them, you just need specific ones.
SAP releases every quarter a patch set with all the actual and tested patches of the different tools, the DB independent and the DB dependent part.
To get the newest kernel patches download
- SAPEXE*.SAR (for your operating system)
- SAPEXEDB.SAR (for your database)
and then subsequently all the patches, that have creation dates AFTER both the others mentioned above.
The BRTOOLS are in the Oracle folder of your operating system named "DBA".
Your sequence for the installation is not correct:
- start sapinst and install central instance
- start sapinst again and install database instance
- sapinst will stop at a certain point and will tell you to install the database (use the RUNINSTALLER provided on the SAP-CD and NOT the standard runInstaller)
- patch your database up to the latest patchset and all interim patches
- go on with sapinst
This is all covered in the official installation guide available at
http://service.sap.com/instguides
Markus

Kernel Patch questions

Sorry but it has been a while. After reading all the kernel threads, I still have a few kernel patch questions.
1) Sequencing - Does it matter what sequence I apply all the patches? Alphabetic order? Date sequence? Always finish with DW?
2) Versioning info - some commands have a -v parameter to tell what version you currently have. Some don't. Is there some way to find out versioning info for all potential patches?
3) Marketplace - I see there is a "complete" kernel on the marketplace now (albeit in two parts). However it's never current. It looks like the hot setup to download that and patch that and then slip that in. Does everyone agree with that assessment?
4) Yes, I know the truly hot setup would be to contract with Volker to get s fully patched CD but since we were stuck on 4.0B for so long, I haven't had a chance to keep my skills up to date. This looks like a good opportunity.
Thanks,
Rick

Hi my friend
I assume you're referring to how to load new 700 kernel since you didn't mention. Here's the steps listed below, for details you could find in Note 912575 - iSeries: Using LODSAPKRN to load a 7.00 kernel
1. Download the latest SAPEXE.SAR, SAPEXEDB.SAR and IGSEXE.SAR from SWDC.
2. Create a directory in IFS and put 3 SAR files there, create a stream file called "parts" with content below:
SAPEXE.SAR,
SAPEXEDB.SAR,
IGSEXE.SAR,
P.S: I opt this way to patch IGS myself because it's more convenient, the formal IGS patching is introduced in
Note 937000 - iSeries: Installing and patching the IGS
3. Log on as QSECOFR or equivalent user (in 912575 it says SIDADM, which could lead to lack of authorization sometimes), and run command:
LODSAPKRN DEV(STMF) MNTPNT('<dir>') KRNLIB(<kernel library>) USERDEF(YES) LIST('<dir>/parts')
4. Stop SAP system and then remove old kernel:
RMVSAP SID(<SID>) DLTKRNLIB(*NO)
5. Change the library list (EDTLIBL) and replace the old kernel library with the new 7.00 kernel library.
6. Activate the new 7.00 kernel:
APYSAP TYPE(*KERNEL) SID(<SID>) DSTLIB(<new kernel library>)
7. Delete all SQL packages: DLTR3PKG SID(<SID>)
then start SAP system
Regards,

Error : While applying the Patch 4440000

Error : While applying the Patch 4440000
FAILED: file igwprop.odf on worker 1 for product igw username IGW.
When i check the worker log file i got this error
The sequence IGW_AWARDS_S in the database is defined as:
MINVALUE = 1 MAXVALUE = 2147483647 INCREMENT BY = 1
CYCLE = NO ORDER = NO CACHE = 1000
which should be defined as:
MINVALUE = 10000 MAXVALUE = 2147483647 INCREMENT BY = 1
CYCLE = NO ORDER = NO CACHE = 1000
(Note: The cache value for sequence IGW_AWARDS_S is 20 in the ODF file. The value 1000 is being used instead because this provides better performance when selecting from the sequence.)
Alter the sequence with :
Start time for statement below is: Sun Oct 06 2013 22:16:28
ALTER SEQUENCE IGW.IGW_AWARDS_S MINVALUE 10000
AD Worker error:
The following ORACLE error:
ORA-04007: MINVALUE cannot be made to exceed the current value
occurred while executing the SQL statement:
ALTER SEQUENCE IGW.IGW_AWARDS_S MINVALUE 10000
AD Worker error:
Unable to compare or correct sequences
because of the error above
Time when worker failed: Sun Oct 06 2013 22:16:28
plz help me in solving this.

Check the current value of IGW_AWARDS_S sequence and make sure the MINVALUE in the patch (i.e. 10000) is not greater than the current one.
OERR: ORA 4007 MINVALUE cannot be made to exceed the current value (Doc ID 19824.1)
You may also log a SR.
Thanks,
Hussein

Applying a patch to OBIEE 11g

Hello Everyone,
I am new to OBI and specially new to 11g, Now most of you guys will know that there was a bug in 11g in which if you want to see the query generated by the report in session log, It shows "no log found". Now there was a patch available which i have downloaded and i am not so sure as to how to apply that patch to OBI, I tried all the steps given in the read me doc provided with the doc. but all in Vain, as it is very confusing and more importantly it doesnt work,
Can any one help me out here by telling me the actual steps involved.
Thanks,

Try the following -
1. cd to oracle home folder\opatch
set oracle_home=your home directory (iethe parent of opatch\ folder)
opatch lsinventory -patch -detail
The last command should run and say "opatch successful".
Now run the command:
2. opatch apply -verbose "your patch folder's complete path"
(verbose tells u the sequence, success or errors if any)
OK - now,
3. The patch on my PC failed saying that I needed to install the latest opatch. I downloaded the latest opatch (11.2 even though the patch (ie the "no log found" patch) requires 11.1.0.8.2 or something) and just extracted it to the oracle home folder - yes, it will overwrite the current opatch folder, so back it up before you copy the latest opatch folder.
4. After this, I ran the command again from step 2 again. It seemed to be running, ie somewhat successful, but it asked for my oracle support login, some proxy server crap so it could connect to the internet, also gives options to specify "NONE" if you didn't need all this - but never came back...at that point, I quit. I tried again and it got stuck at the same point - so, I wasn't sure if it succeeded or not.
5. I assumed the patch ran OK and tried to view the log - but this time it gave a different error "it is not a Win32 application" or something like that. I am sure that I downloaded the win32 patch only. Yet, I am going to check and try it out again tomorrow.
Let me know if it worked for you and the details.
Hope all this helps :-)

Static library not accessed properly after Solaris Kernel patch update !

Hi,
We are facing a sever issue in our application after our customer updated the Solaris 10 kernel patch u9 to u10.
We have two static libraries libdlib.a and libDLIB.a, with exactly same code base, but these two libraries are scattered across the code base and linked by many shared objects in our application.
However, one of the shared objects that links to "libdlib.a" library tries to access a function from "libDLIB.a". This behavior is causing a crash at a later point, since that shared object is supposed to access the function from "libdlib.a". Moreover, we found this is happening through the use of dbx.
I'm unable to understand why this problem surfaced after kernel patch update, though still the shared object works fine on Solaris 10 u9 patch.
Flow is something like this :
1. syslogrecorder.so gets loaded by one of the processes.
2. syslogrecorder.so is linked to "libdlib.a" at compile time, so it uses "libdlib.a" function DLIB_LoadLibrary and gets a handle to all the function pointers of the loaded library ( The purpose of DLIB_LoadLibrary is to load a shared library dynamically using dlopen )
3. syslogrecorder.so tries to do a "dlsym" and to do that it needs access to the library handle which we got in previous call DLIB_LoadLibrary. So syslogrecorder.so calls another function from DLIB_ProcAddress, which actually gives back the access to the loaded shared library.
Here is a catch in step 3, it is supposed to call DLIB_ProcAddress from the libdlib.a but as we observed from dbx output it does so by calling DLIB_ProcAddress from libDLIB.a and hence fails to give back the access to loaded shared library, causing crash at a later point in code.
Can someone put some light here that why this could happen ??
Thanks
Kuldeep

To clarify: You did not modify or rebuild any of your binaries, but after installing a kernel patch, the application stopped working. Most likely, something about your application depended on a accidental behavior of the runtime loader. That accidental behavior changed due to the patch, and your application failed.
For example, if there is a circular dependency among shared libraries, the loader will break the cycle at an arbitrary point to establish an initialization order. By accident, that order might work, in the sense of not causing a problem. A change to the loader could cause the cycle to be broken at a different point, and the resulting initialization order could cause a now-uninitialized object to be accessed. I'm not saying this is what is wrong, but this is an example of a dependency on accidental loader behavior.
Finding your actual problem will require tracing the sequence of operations leading up to the failure. You are more likely to find help in a Solaris linker forum. AFAIK, there are currently no Oracle forums for Solaris, and the old OpenSolaris forums have been converted to mailing lists. You can try the "tools-linking" list found on this page:
http://mail.opensolaris.org/mailman/listinfo
I also suggest you review the paper on best practices for using shared libraries written by Darryl Gove and myself:
http://www.oracle.com/technetwork/articles/servers-storage-admin/linkinglibraries-396782.html
If you have a service contract with Oracle, you can use your support channel to get more help.
Edited by: Steve_Clamage on May 18, 2012 3:21 PM

Kernel patch 127128-11 renders my x86 system unbootable - what to do?

Just installed some patches with smpatch as usual, kernel patch 127128-11 among them. I then dropped to single user mode to finish the installation, rebooted and... nothing. I get the SunOS copyright notice, and then nothing but a flashing cursor... I waited for half an hour, but nothing happened, no disk activity, keyboard not responding, nothing.
I had to reset the stupid machine...
This happened on old(ish) HP Vectra SFF.
What I can do now? What are my options? (And please DON'T say: "reinstall everything"!!!)
I have used Linux for 7-8 years, but Solaris is pretty new for me, this installation is some 2 months old (Sun Solaris 10 - 8/07 - x86)

I remember I ever tried a tool that you need to run in order to put your computer on the list.
Well it suddenly crashed and I didn't try it again.The certification tool: http://www.sun.com/bigadmin/hcl/hcts/
At Sun they know very well which systems I'm running Solaris on.
This data is sent when you register to apply for updates.They don't use your registration info to list a system as certified to run Solaris10. See link above.
I have to admit I never added any patches by going into single user mode.I install in single user per instructions in patch README. I have rarely had issues installing patches this way.
Reading back this thread I see that this patch was part of the Solaris 10 5/08 version
and since I recently upgraded to this version and everything is working fine,
I don't think there is an issue. Neither do I think that there is an issue with 127128-11 patch, which is why I mentioned that OPs machine was not on HCL. It's an issue with OPs hardware, not the new kernel. So, what is that 'fix' disabling so that Solaris will run on unsupported hardware?
I haven't tried OpenSolaris yet. What do you think of it so far?

Solaris 10 U4 and kernel patches

When I install a fresh U4 machine, I then (as I always do) apply the recommended patch cluster. U4 has kernel patched to 120011-14. In the patch cluster, there are kernel patches 118833-36 and also 120011-14. When I run the patch cluster, it installs 118833-36! Isn't this older than the kernel on there? Shouldn't both 118833-36 and 120011-14 BOTH not install as the kernel is already at level 120011-14. The cluster gets to 118833-36 installs that and then of course every patch after that one fails as the machine is waiting for a reboot.

KJP 137138-09 should be ok with cpquary3 driver 1.9.1. KJP 137138 introduced new feature which does not allow misaligned pointer mutexes to work and panics the system. with revision 07 SUN introduced a new environment variable as a for applications which cannot be ported easily "6729759 need to accommodate non-8-byte-aligned mutexes".
This is documented in alert 244606 "The resolution for OpenSolaris releases sets _THREAD_LOCKS_MISALIGNED to 0. This is to ensure that any faulty applications fail and are identified. To allow such applications to continue to work on OpenSolaris releases based upon snv_96 or later, the environment variable _THREAD_LOCKS_MISALIGNED must be set to 1." For this to work you need to have revision 09 of this KJP applied.
Can you post the stack trace so i can have a look at it. I guess you have another application which uses unaligned mutexes.
A pkginfo of the cpquary3 package would also be useful.
-Marco

Solaris 10 kernel Patch 127127-11

we need to apply solaris 10 kernel Patch 127127-11 in our prod server as a prerequisite for oracle10g patch set 10.2.0.4 installation
but i found a Doc 242366 (May Cause a system Panic from ip_wput_ioctl()).It is mentioned in doc that Binary relief is available through normal
support channels.Is that Binary complete fix of this problem?If yes, then i need that binary please give me the link where i can download the binary,
If not, then what is the solution of this problem.?
Thanks

These kinds of binary hotfixes/IDR's are only available through sun support to contract customers.
If your concerned, I suggest you raise a support case.
That being said, 127127-11 is kinda old. So I would be surprised if the bug hadnt been fixed by now.
Its been replaced by either 137111 or 137137.
Ive upgraded at least a dozen systems past that level and never seen a problem.
So it can't be too common..

Steps for Kernel Patch Updation on Solaris 10 X4100 with 2disks mirrored

Hi all,
I have Solaris 10 10/06 (118855-19) installed on one of the X4100 server. This is the time for me to update the latest kernel patch (118855-36). We have two disks mirrored. My questions are,
1) Do i need to detach any of the disk from the mirror before doing any patching.
2) Is it possible to install the patches without detaching any disks from the mirror. (i.e. installeing patch on mirrored root filesystem)
3) how to boot from the second disk in case the patch installation creates problem while booting up.
Any suggestions or steps which you have already implemented for the above scenario.

This isn't really a question for this forum, you may be better to look at some of the sys-admin forums for a complete answer.
You should not need to break the mirror in order to apply the kernel patch, however doing so would allow for quicker recovery of the system should something go wrong during patching.
I would strongly advise that you read the special install instructions for the kernel patch prior to installing it.
http://sunsolve.sun.com/search/document.do?assetkey=1-21-118855-36-1
You may also wish to use a patch cluster rather than smpatch/updatemanager, these can be downloaded from SunSolve:
http://sunsolve.sun.com/private-cgi/show.pl?target=patchpage

Kernel Patching with zones

I have a T2000 installed with the Solaris 10 1/06 release with several zones created on it. 4 zones are "sparse" root, and one (zone-5) is a "whole root" zone.
In order to apply and certify (internally) the latest sendmail patch, Solaris 10 needs a later kernel patch than I had installed (this is a subject for another discussion...). So I downloaded the latest patch cluster (4/6 Recommended cluster) to apply it.
I shut down the non-global zones, and took the machine to single user mode, and installed the cluster. It seemed to go in fine, except for the following error:
Zone zone-5
Rejected patches:
122856-01
Patches that passed the dependency check:
None.
Fatal failure occurred - impossible to install any patches.
zone-5: For patch 122856-01, required patch 118822-30 does not exist.
Fatal failure occurred - impossible to install any patches.Now, 118822-30 is a kernel patch series that is prerequisite for the latest kernel patch (118833-03). Zone-5 is my only whole-root zone. I then looked at the patch cluster log, and discovered that a handful of patches (including 118822-30) had also failed:
titan15n> grep failed /var/sadm/install_data/Solaris_10_Recommended_Patch_Cluster_log
Pkgadd failed. See /var/tmp/119254-19.log.6615 for details
Pkgadd failed. See /var/tmp/118712-09.log.9307 for details
Pkgadd failed. See /var/tmp/119578-18.log.15160 for details
Pkgadd failed. See /var/tmp/121308-03.log.18339 for details
Pkgadd failed. See /var/tmp/119689-07.log.22068 for details
Pkgadd failed. See /var/tmp/118822-30.log.9404 for details
Pkgadd failed. See /var/tmp/119059-11.log.29911 for details
Pkgadd failed. See /var/tmp/119596-03.log.4724 for details
Pkgadd failed. See /var/tmp/119985-02.log.8349 for details
Pkgadd failed. See /var/tmp/122032-02.log.13334 for details
Pkgadd failed. See /var/tmp/118918-14.log.27743 for detailsLooking at any of these logs (in the non-global zone-5's /var/tmp directory shows failures like the following snippet:
pkgadd: ERROR: unable to create unique temporary file </usr/platform/sun4us/include/sys/cheetahregs.h6HaG8w>: (30) Read-only file sy
stem
pkgadd: ERROR: unable to create unique temporary file </usr/platform/sun4us/include/sys/clock.h7HaG8w>: (30) Read-only file system
pkgadd: ERROR: unable to create unique temporary file </usr/platform/sun4us/include/sys/dvma.h8HaG8w>: (30) Read-only file systemQuestion(s):
Why would there be read-only file systems where tmp files are getting written? Possibly a timing issue?
Is there a "best practice" on applying patch clusters, and specifically, the kernel patch? Did I make a mistake in taking the zones down first? It seems like the zones were being booted up as the patches were getting applied, but I may be misinterpreting the output.
Even though the patches failed to apply to zone-5, the uname -a output in the zone show the latest kernel patch, but does NOT show 118822-30 (118822-25 is what showrev -p in the non-global zone-5 shows -- which is the level I was at before attempting to patch).
Any solutions?
Thanks.

The kernel config and patch are irrelevant - I have tried to compile the stock arch kernel just to make sure that it WASN'T the patch - I simple copied the folder from ABS, did makepkg and installed - no lucky. The problem seems to be that all of the kernels I compile end up with the folder in /lib/modules having -dirty on the end of them. How do I stop this '-dirty'?
I notice in the build I get this message -
==> Building the kernel
fatal: cannot describe '604d205b49b9a478cbda542c65bacb9e1fa4c840'
CHK include/linux/version.h

SP 's and Kernel patches

Hi all,
I have a few questions and want clear my basics.
Is Kernel upgrade the same as applying a kernel patch? For any SAP system release, there's
just one kernel version right? We just keep applying new patch versions to update it. Is this
correct? Please throw some light.
secondly, in SPAM, what is the difference between new and imported packages? When trying
to apply latest support packages, what steps should you follow? And what are support package
stacks? I know they are a collection od packages but how to find out which one I will need
depending on the current package status of my system?
Thanks in advance
Cyrus

hi Cyrus,
> secondly, in SPAM, what is the difference between new
> and imported packages? When trying
> to apply latest support packages, what steps should
> you follow?
SPAM - Support Package Manager is used to put ABAP patches in your system. Imported packages mean the packages that are already imported in your system. say your WAS is on SP9 - this means you will find SP1..SP9 in imported packages. this will be useful if you are patching it up in stages. you will find which are already imported and hence put the rest. Sometimes higher patches needs to have some prerequisites. you may find if these prerequisites are satisfied.
New packages are already loaded but yet to be imported. You will find the traffic light - Yellow. for imported packs you will find it green.
if you want to apply latest support packs, first load them into your ABAP system after downloading them from service market place. you may do it using the SUPPORT PACKAGE --> Load FROM FORNT END. then upload the car files and Display/Define Queue. then Import Queue. after queue is imported, Confirm
Presto! you have finished upgrading.
>And what are support package
> stacks? I know they are a collection od packages but
> how to find out which one I will need
> depending on the current package status of my
> system?
first Find which stack your system is running. this is source stack. then find give the target (say SP14) in service market place. this will give all necessary stacks from your source to target. download them.
hope i managed to throw some light!
Regards
ak
Message was edited by: Arun Kumar Ravi

Sequence of Applying Kernel Patches

Similar Messages

Maybe you are looking for