on 05-05-2015 3:22 PM
ASE 15.7 SP133 was released last week, but included the wrong version (OCS SP132) of the OCS (Open Client) component subdirectory.
SP133 has been removed from the download site and will be re-released as SP134 with the correct OCS component later this week (I'm told the target is "before May 11th"). Email has been sent to all identifiable contacts who downloaded the release (if you downloaded it but did not receive some notification, you might verify that your registered contact information contains a valid email address).
If you are using ASE for custom applications (i.e. not for SAP Business Suite, etc.) and have already installed SP133, you can correct the environment by downloading and installing the 15.7 SP133 SDK for ASE patch.
From https://support.sap.com/software/patches/a-z-index.html
Go to "S" -> "SDK for SAP ASE" -> 15.7 -> your platform
If you have not already downloaded SP133, please wait for the SP134 release.
For SAP Application environments, if you have already applied SP133 engineering is writing up more detailed instructions.
If you have downloaded SP133 but not yet applied it please wait for SP134.
If you need a more formal announcement (for your manager, etc.) this information has also been published as KBA 2164138
Would you Please send me Readme file & CR List for SP134
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the information.
We've been running SP132 for 5 days and we're getting timeslice errors.
00:0002:00000:01812:2015/05/02 21:03:57.09 kernel timeslice -1501, current process infected at 0x17c051d (VTABRemoteAccess::getNext()+0xd3)
00:0002:00000:01812:2015/05/02 21:03:59.12 kernel **** Saved signal context (0x0x00002aab08d494c0): ****
00:0002:00000:01812:2015/05/02 21:03:59.12 kernel uc_flags: 0x0,uc_link: 0x(nil)
00:0002:00000:01812:2015/05/02 21:03:59.12 kernel uc_sigmask: 0x416000 0xa 0xfffffffa 0x22b9
00:0002:00000:01812:2015/05/02 21:03:59.12 kernel uc_stack: ss_sp: 0x (nil), ss_size: 0x0, ss_flags: 0x2
From what you've said - none of these errors are due to the packaging of SP133 ?
Can you confirm this is the case ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, the packaging issue with SP133 would not have an effect on SP132.
The timeslice error on VTABRemoteAccess:getNext looks like it mayh match CR 777205 which was fixed in the ill-fated SP133. The fix for that CR will now be available in SP134, due out very soon.
-bret
The dataserver is linked dynamically. When started it loads modules from the OCS directory :
ldd ./dataserver
...
libsybcsi_core29.so => /local/sybase/ase157/OCS-15_0/lib3p64/libsybcsi_core29.so
libsybcsi_profiler29.so => /local/sybase/ase157/OCS-15_0/lib3p64/libsybcsi_profiler29.so
libsybcsi_propertiesconfig29.so => /local/sybase/ase157/OCS-15_0/lib3p64/libsybcsi_propertiesconfig29.so
libsybcsi_openssl29.so => /local/sybase/ase157/OCS-15_0/lib3p64/libsybcsi_openssl29.so
....
Best Regards,
Luc.
User | Count |
---|---|
94 | |
11 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.