cancel
Showing results for 
Search instead for 
Did you mean: 

dbsl patch not upgraded

former_member183044
Active Participant
0 Kudos

Hi,


We have downloaded the dbsl patch version(318) from marketplace. We

have done the uncar, extracted the files and copied the files to the kernel

location. After restarting the server again, while checking the sm51, the dbsl

patch version in our server is still the same(315).


Please help...


Regards


Praveen

Accepted Solutions (1)

Accepted Solutions (1)

hugo_amo
Employee
Employee
0 Kudos

Hi Praveen,

Have you updated the kernel following the steps mentioned in the note 19466? Have you used the same unicode DBSL with your kernel?

The SAP Kernel comprises of two parts:

The database-indepedent part of the kernel (disp+work.<extension>)
The database-dependent part of the kernel (db<dbms_type>slib.<extension>

Have you updated them all?

Regards,

Hugo

former_member183044
Active Participant
0 Kudos

Hi Hugo,

Thanks for the reply. We have downloaded both the files for SAP kernel (database independent & database dependent) and uncared and installed in our server.

Can u please tell that How can we check same unicode DBSL with our kernel??

Regards

praveen

hugo_amo
Employee
Employee
0 Kudos

Hi Praveen,

You need to download the dbsl from the same location where you downloaded the kernel. See the note 19466.

http://service.sap.com/sap/support/notes/19466

Regards,

Hugo

former_member183044
Active Participant
0 Kudos

Hi Hugo,

Thanks for the mail.

Regards

Praveen

former_member183044
Active Participant
0 Kudos

Hi Hugo,

I have already done the kernel upgrade. But the actual problem is dbsl patch upgrade. I have done the kernel upgrade as per the notes. I also downloaded the dbsl patch version and done the whole same process.

But after restarting the server, while i checking the dbsl patch version , it is still showing the dbsl patch level.

Regards

Praveen

hugo_amo
Employee
Employee
0 Kudos

Hi Praveen,

I think you are doing something wrong. Please, follow exactly the steps in Note 19466, if you follow them, I presume you will not get this problem.

Regards,

Hugo

alichtenau
Advisor
Advisor
0 Kudos

Hi Praveen,

which is your basis release and which kernel release is in use?

Best regards,
Andreas

former_member183044
Active Participant
0 Kudos

Hi Andreas,

Our Basis version is 731 and kernel release in use is 721_EXT_REL

Regards

Praveen

alichtenau
Advisor
Advisor
0 Kudos


Hi Praveen,

according to note #1591607 you should use the 720_EXT kernel, but it is also fine with the latest 721_EXT.

Please change the kernel according to notes #19466 and #1713986. Please work through #1713986 step by step.

Best regards,
Andreas

former_member183044
Active Participant
0 Kudos

Hi Andreas,

According to note 1713986, in that note it is written that we must execute ./saproot.sh.

Is it necessary to execute that command?

Also Andreas, my question is on dbsl patch version. We have successfully upgraded the kernel version from 720 to 721 according to the said SAP Note. But when we do dbsl upgrade from 315 to 318 it is not upgrading.

Regards

Praveen

alichtenau
Advisor
Advisor
0 Kudos

Hi Praveen,

you have to execute the "saproot.sh" script to configure the ownership and permissions of some kernel files, including saposcol.

After changing the DBSL at "/usr/sap/<SAPSID>/SYS/exe/run" did you run "sapcpe" for all application server instances?


Did you step by step work through that note? Or did you only switch DBSL at "/usr/sap/<SAPSID>/SYS/exe/run"?

Best regards,
Andreas

former_member183044
Active Participant
0 Kudos

Hi Andreas,

Please note the following.

After changing the DBSL at "/usr/sap/<SAPSID>/SYS/exe/run" did you run "sapcpe" for all application server instances? ----- No

Did you step by step work through that note? Or did you only switch DBSL at "/usr/sap/<SAPSID>/SYS/exe/run"? -------kernel upgrade has been done successfully completed.After that

we have done the uncar of dbsl patch files and copied the two files in kernel folder. After checking the version again, the dbsl patch version is same.

Regards

Praveen

alichtenau
Advisor
Advisor
0 Kudos

Hi Praveen,

would you please run "sapcpe" according to note #1713986?

Cheers,
Andreas

former_member183044
Active Participant
0 Kudos

Hi Andreas,

Sorry for the wrong information. We had already done the sapcpe , but not after dbsl upgrade.

Please take a look at the screenshot.

Am i suppossed to do the sapcpe just after the dbsl patch version upgrade?

Awaiting your earliest reply...

Regards

Praveen

alichtenau
Advisor
Advisor
0 Kudos

Hi Praveen,

yes, please do SAPCPE again to ensure that all executables are in sync.

Cheers,
Andreas

former_member183044
Active Participant
0 Kudos

Hi Andreas,

So u want me to do the dbsl upgrade again and immediately after dbsl upgrade , do the sapcpe command?

Awaiting your reply

Regards

Praveen

alichtenau
Advisor
Advisor
0 Kudos

Exactly Praveen.
This ensures that the new DBSL is not just under "/usr/sap/<SAPSID>/SYS/exe/run", but also in sync with all other executables.

former_member183044
Active Participant
0 Kudos

Hi Andreas,

Thanks for the update. We will do the same process in our environment and will surely update u.

Regards

Praveen

alichtenau
Advisor
Advisor
0 Kudos

Hi Praveen.

okay, thanks for the feedback. Please keep me posted.

Best regards,
Andreas

Former Member
0 Kudos

Hello Andreas Lichtenau and Praveen Ninan Alex,

I´m facing the same problem after I performed a kernel update! The problem is exactly the same, with the DBSL version (318), but the system doesn´t show this version, it show me the "old" version (315)!

I did exactly what is recommended in the sap note 1713986 for the Windows platform. I also ran the following two sapcpe commands but unfortunatelly it gave me the same problem (my system is a SAP Solution Manager - double stack (abap+java):

S:\usr\sap\SM1\DVEBMGS00\work>sapcpe pf=S:\usr\sap\SM1\sys\profile\SM1_DVEBMGS00_SATDCSSM1

S:\usr\sap\SM1\DVEBMGS00\work>sapcpe pf=S:\usr\sap\SM1\SYS\profile\SM1_DVEBMGS00_SATDCSSM1 source:S:\usr\sap\SM1

\SYS\exe\jvm\NTAMD64 list:S:\usr\sap\SM1\SYS\exe\jvm\NTAMD64\sapjvm_

4.1.040\sapjvm_4.lst

I ran the following sapcontrol command and this was the output:

S:\usr\sap\SM1\DVEBMGS00\work>sapcontrol -nr 00 -function GetVersionInfo

27.10.2014 12:44:45

GetVersionInfo

OK

Filename, VersionInfo, Time

S:\usr\sap\SM1\DVEBMGS00\exe\sapstartsrv.exe, 721, patch 330,

changelist 1530112, optU (EXT), NTAMD64, 2014 10 19 22:09:27

S:\usr\sap\SM1\DVEBMGS00\exe\disp+work.exe, 721, patch 330, changelist

1530112, optU (EXT), NTAMD64, 2014 10 19 22:09:21

S:\usr\sap\SM1\DVEBMGS00\exe\gwrd.exe, 721, patch 330, changelist

1530112, optU (EXT), NTAMD64, 2014 10 19 22:09:23

S:\usr\sap\SM1\DVEBMGS00\exe\msg_server.exe, 721, patch 330, changelist

1530112, optU (EXT), NTAMD64, 2014 10 19 22:09:26

S:\usr\sap\SM1\DVEBMGS00\exe\dboraslib.dll, 721, patch 300, changelist

1498740, optU (EXT), NTAMD64, 2014 05 26 02:29:25

S:\usr\sap\SM1\DVEBMGS00\exe\dbmssslib.dll, 721, patch 300, changelist

1498740, optU (EXT), NTAMD64, 2014 05 26 02:29:25

S:\usr\sap\SM1\DVEBMGS00\exe\dbdb2slib.dll, 721, patch 300, changelist

1498740, optU (EXT), NTAMD64, 2014 05 26 02:29:24

S:\usr\sap\SM1\DVEBMGS00\exe\dbdb4slib.dll, 721, patch 300, changelist

1498740, optU (EXT), NTAMD64, 2014 05 26 02:29:24

S:\usr\sap\SM1\DVEBMGS00\exe\dbdb6slib.dll, 721, patch 300, changelist

1498740, optU (EXT), NTAMD64, 2014 05 26 02:29:25

S:\usr\sap\SM1\DVEBMGS00\exe\dbsybslib.dll, 721, patch 318, changelist

1513330, optU (EXT), NTAMD64, 2014 07 29 03:57:06

S:\usr\sap\SM1\DVEBMGS00\exe\enserver.exe, 721, patch 330, changelist

1530112, optU (EXT), NTAMD64, 2014 10 19 19:11:25

S:\usr\sap\SM1\DVEBMGS00\exe\icman.exe, 721, patch 330, changelist

1530112, optU (EXT), NTAMD64, 2014 10 19 22:09:23

S:\usr\sap\SM1\DVEBMGS00\exe\sapwebdisp.exe, 721, patch 330, changelist

1530112, optU (EXT), NTAMD64, 2014 10 19 22:09:28

S:\usr\sap\SM1\DVEBMGS00\exe\jcontrol.exe, 721, patch 330, changelist

1530112, optU (EXT), NTAMD64, 2014 10 19 22:09:25

S:\usr\sap\SM1\DVEBMGS00\exe\jlaunch.exe, 721, patch 330, changelist

1530112, optU (EXT), NTAMD64, 2014 10 19 22:09:25

S:\usr\sap\SM1\DVEBMGS00\exe\jstart.exe, 721, patch 330, changelist

1530112, optU (EXT), NTAMD64, 2014 10 19 22:09:26

I don´t understand what is wrong here... damn

I also created a thread but at this momment I didn´t found any solution for this problem

Can you help me please? Any tips?

Best regards,

samid raif

former_member183044
Active Participant
0 Kudos

Hi Samid,

Did u performed sapcpe steps as per andreas mentioned in above mail??

Regards

Praveen

Former Member
0 Kudos

Hello Praveen,

Yes, I performed that steps. What I did was, I ran the two following sapcpe commands (because this is a ABAP+JAVA system) as it said in sap note 1713986:

S:\usr\sap\SM1\DVEBMGS00\work>sapcpe pf=S:\usr\sap\SM1

\sys\profile\SM1_DVEBMGS00_SATDCSSM1

S:\usr\sap\SM1\DVEBMGS00\work>sapcpe pf=S:\usr\sap\SM1

\SYS\profile\SM1_DVEBMGS00_SATDCSSM1 source:S:\usr\sap\SM1

\SYS\exe\jvm\NTAMD64 list:S:\usr\sap\SM1\SYS\exe\jvm\NTAMD64\sapjvm_

4.1.040\sapjvm_4.lst

I sent to you attached to this message the log files of sapcpe.

Can you help me please? Any tips?

Best regards,

samid raif

former_member183044
Active Participant
0 Kudos

Hi samid,

Can u explain in detail with each of the screenshot? pls send a copy to Andreas Lichtenau also.


Regards


praveen

Former Member
0 Kudos

Hello Praveen,

I don´t understand what you want... but I believe you asked me to put some print screens here in way to explain more better what I done, am I right?

I followed the instructions in the sap note 1713986 - Installation of kernel 721 (EXT) in the section "4.2 On Windows". As you can see in that sap note, for the Dual-Stack systems, which is the case of my SAP system, I must run the following two commands:

< drive>:

cd \usr\sap\<SAPSID>\<INSTANCE>\work

sapcpe pf=<drive>:\usr\sap\<SAPSID>\sys\profile\<instance profile>

If your system is running with the SAPJVM:

sapcpe pf=<drive>:\usr\sap\<SAPSID>\sys\profile\<instance profile> source:<sapjvm directory> list:<sapjvm directory>\sapjvm_<version>.lst



So, I did exactly what is recommended in note! I ran the following sapcpe commands:


For Abap side:

S:

cd \usr\sap\SM1\DVEBMGS00\work

sapcpe pf=S:\usr\sap\SM1\sys\profile\SM1_DVEBMGS00_SATDCSSM1


For Java side:

S:

cd \usr\sap\SM1\DVEBMGS00\work

sapcpe pf=S:\usr\sap\SM1\SYS\profile\SM1_DVEBMGS00_SATDCSSM1 source:S:\usr\sap\SM1\SYS\exe\jvm\NTAMD64 list:S:\usr\sap\SM1\SYS\exe\jvm\NTAMD64\sapjvm_4.1.040\sapjvm_4.lst



After I run that sapcpe commands that I described above, I started the SAP system but again the DBSL has the old version (315) and not the version (318) that I added in the kernel directory!



Can you help me please? Any tips? Any solution for this weird situation?!



Best regards,

samid raif

Answers (0)