on 12-31-2010 7:58 AM
Hello SAP Experts,
Generally while we performing kernel update, shutting down the SAP system including the database and replacing the kernel files.
My question is, while performing the kernel update. Database shutdown is required? What SAP recommends?
Thanks
Kiran
Generally, Kernel Upgrade means upgrade of DB Dependent files and DB InDependent files in your kernel directory.
The DB Dependent files consist of DLLs in Windows and similar other library files for other OS as well. So, logic, common sense and SAP recommends that Database should be down when you are doing a manual* Kernal Upgrade.
Lets say, you have not shut the DB and some file from kernel directory is in use. You will just get an error - "File is in use".
Again, the recommendations here is stop the DB, so that the file is no longer in user, instead of figuring out which PID is using that file and then just killing that process.
So, bottom line - get downtime approval for SAP and DB for Kernel Upgrade.
- If you have Java, Using JSPM for Kernel Upgrade is Generally a good option.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
I just want to add one small point.
Shutting down of SAPOSCOL and listnr is also important as SAPOSCOL service should be stopped because it also will get overwritten by the new file.
stop saposcol (saposcol –k)
stop lisner (orasid user – lsnrctl stop)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
kernel upgrade is done using database dependant (sapexedb***) and independant files (sapexe***). Still, stopping of database is not required. Just stop Instance & services.
If there is no database activity like online backup going on, you can as well stop database since there is no user activity.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Following steps need to be carried out for kernel patching.
1. Stop SAP system thru SAP MMC.
2. Stop SAPOSCOL in services.msc
3. Take a backup of sys\exe folder.
4. Replace the sys\exe ... kernel folder with the newly extracted files.
5. Bring up SAP system and SAPOSCOL.
Rgds,
Soujanya
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
83 | |
10 | |
10 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.