Could someone tell me where the below issues was discussed on SCN so that I can subscribe to the appropriate groups?
https://www.trustwave.com/Resources/Security-Advisories/Advisories/TWSL2015-004/?fid=6200

Revision History:

01/15/2014 - Vulnerability disclosed

04/22/2015 - SAP published security note 2113995

04/23/2015 - Advisory published

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

What causes the error

     Database tempdb_xxxx with dbid xx is already shut down

Our server was bounced at 17 mins after the reboot we got this message but nothing before this to indicate why ?

The only messages I can see before this for

Timestamp for database 'tempdb_xxxx' is (0x0000, 0x0000d8a9).

Forcing server to scan allocation pages to find free log space count for database 'xx'

Forcing server to scan allocation pages to find free data space count for database 'xx'

The transaction log in the database 'tempdb_xxxx' will use I/O size of 32 Kb.

Database 'tempdb_xxxx' is now online.

Is there something we can do to increase the logging to see what caused it.

ASE 15.7 SP 132 has been released without documentation set on either help.sap.com or infocenter. 

Which is the closest documentation applicable to it sp100 or esd2 (Some overlap, some don't)?

Thanks

Hi Community, it's possible configuremultisitereplicationwithreplicationserverincluded inSAP ASE Edge Edition?

We have a proc which is hanging after it terminates a process with

Msg 233, Level 16, State 2

Server 'LN_DELTA_D1_SQL', Procedure 'test', Line 32

The column CallType in table #features does not allow null values.

(return status = -6)

ASE is terminating this process.

We're creating a temp table incorrectly in the proc, by including the line

           CallType               char(1)     default null

We then insert into it and update it.

We get the message - the sessions terminates but the process continues to appear in sp_who.

The only way to clear it is a reboot.

We haven't tried this on SP132 - but will try it on SP134 when we get it.

We also get a stack trace - if it helps. The stack trace points to the update being at fault rather than the insert.

00:0011:00000:00223:2015/05/11 11:01:48.72 kernel  uc_flags: 0x0, uc_link: 0x(nil)

00:0011:00000:00223:2015/05/11 11:01:48.72 kernel  uc_sigmask: 0x416000 0xb 0x1 0xdeadbafe

00:0011:00000:00223:2015/05/11 11:01:48.72 kernel  uc_stack: ss_sp: 0x(nil), ss_size: 0x0, ss_flags: 0x2

00:0011:00000:00223:2015/05/11 11:01:48.72 kernel  General Registers (uc_mcontext.gregs):

00:0011:00000:00223:2015/05/11 11:01:48.72 kernel  PC : 0x0000000000f19a46 (xact_beginupdate+0x316)

00:0011:00000:00223:2015/05/11 11:01:48.72 kernel          RAX : 0x00000000deadbabe  RBX : 0x00002aabfcbf8c90

00:0011:00000:00223:2015/05/11 11:01:48.72 kernel          RCX : 0x00002aab8606e498  RDX : (nil)

00:0011:00000:00223:2015/05/11 11:01:48.72 kernel  RBP : 0x00002aaac2db6ff0  RSP : 0x00002aaac2db6f90

00:0011:00000:00223:2015/05/11 11:01:48.72 kernel  R8  : (nil)  R9  : 0x0000000000000001

00:0011:00000:00223:2015/05/11 11:01:48.72 kernel  R10 : (nil)  R11 : (nil)

00:0011:00000:00223:2015/05/11 11:01:48.72 kernel  R12 : 0x00002aac18fdbd28  R13 : 0x00002aabfcbf80c8

00:0011:00000:00223:2015/05/11 11:01:48.72 kernel  R14 : 0x0000000000000001  R15 : (nil)

00:0011:00000:00223:2015/05/11 11:01:48.72 kernel  RDI : 0x0000000002a581c8  RSI : 0x00000000fffffffb

00:0011:00000:00223:2015/05/11 11:01:48.72 kernel  RIP : 0x0000000000f19a46  CSGSFS : 0x0000000000000033

00:0011:00000:00223:2015/05/11 11:01:48.72 kernel  TRAPNO : 0x000000000000000e  ERR : 0x0000000000000004

00:0011:00000:00223:2015/05/11 11:01:48.72 kernel  EFL : 0x0000000000010206

00:0011:00000:00223:2015/05/11 11:01:48.72 kernel  **** end of signal context ****

00:0011:00000:00223:2015/05/11 11:01:48.72 kernel  ************************************

00:0011:00000:00223:2015/05/11 11:01:48.72 kernel  SQL causing error :

00:0011:00000:00223:2015/05/11 11:01:48.72 kernel  Current Procedure: F

00:0011:00000:00223:2015/05/11 11:01:48.72 kernel  Current statement number: 17 Current line number: 137

00:0011:00000:00223:2015/05/11 11:01:48.72 kernel  ************************************

00:0011:00000:00223:2015/05/11 11:01:48.72 server  SQL Text:

00:0011:00000:00223:2015/05/11 11:01:48.72 server  SQL Text: update  #features

    set     f.Sinking = 1

    from    #features f

    where   exists (select  *

                    from    POC..Schedule bfs

                    where   bfs.IId= f.IId

                    and     f.ValidFrom >= bfs.ValidFrom

                    and     f.ValidFrom <  bfs.ValidTo

                    )

00:0011:00000:00223:2015/05/11 11:01:48.72 kernel  curdb = 83 tempdb = 83 pstat = 0x10000 p2stat = 0x40101000

00:0011:00000:00223:2015/05/11 11:01:48.72 kernel  p3stat = 0x10800 p4stat = 0x0 p5stat = 0x8 p6stat = 0x10008011 p7stat = 0x10008

00:0011:00000:00223:2015/05/11 11:01:48.73 kernel  lasterror = 0 preverror = 0 transtate = 0

00:0011:00000:00223:2015/05/11 11:01:48.73 kernel  curcmd = 195 program = DBArtisan

00:0011:00000:00223:2015/05/11 11:01:48.74 kernel  pc: 0x00000000015e55ab pcstkwalk+0x3a3()

00:0011:00000:00223:2015/05/11 11:01:48.74 kernel  pc: 0x00000000015e5083 ucstkgentrace+0x263()

00:0011:00000:00223:2015/05/11 11:01:48.74 kernel  pc: 0x00000000015e0fee ucbacktrace+0x50()

00:0011:00000:00223:2015/05/11 11:01:48.74 kernel  pc: 0x0000000000784d5c terminate_process+0xa7c()

00:0011:00000:00223:2015/05/11 11:01:48.75 kernel  pc: 0x00000000016336d8 kisignal+0x31f()

00:0011:00000:00223:2015/05/11 11:01:48.75 kernel  pc: 0x0000000000f19a46 xact_beginupdate+0x316()

00:0011:00000:00223:2015/05/11 11:01:48.75 kernel  [Handler pc: 0x0x000000000152c8a6 trunctaberr installed by the following function:-]

00:0011:00000:00223:2015/05/11 11:01:48.75 kernel  pc: 0x000000000152b0d7 trunctab__phys+0x267()

00:0011:00000:00223:2015/05/11 11:01:48.75 kernel  [Handler pc: 0x0x000000000152c8a6 trunctaberr installed by the following function:-]

00:0011:00000:00223:2015/05/11 11:01:48.75 kernel  pc: 0x000000000152a5fe trunctab+0x56e()

00:0011:00000:00223:2015/05/11 11:01:48.75 kernel  [Handler pc: 0x0x00000000013c9ec0 droperr installed by the following function:-]

00:0011:00000:00223:2015/05/11 11:01:48.75 kernel  pc: 0x00000000013c24b0 dropo+0x22c0()

00:0011:00000:00223:2015/05/11 11:01:48.75 kernel  pc: 0x00000000012042f4 drop_with_retry+0xb4()

00:0011:00000:00223:2015/05/11 11:01:48.75 kernel  pc: 0x0000000001203428 tmp_alldrop+0x108()

00:0011:00000:00223:2015/05/11 11:01:48.75 kernel  pc: 0x00000000011d923b s_free+0x71b()

00:0011:00000:00223:2015/05/11 11:01:48.75 kernel  pc: 0x00000000011d85c4 s_pop+0x124()

00:0011:00000:00223:2015/05/11 11:01:48.75 kernel  pc: 0x00000000011d4420 s_cleanframe+0x130()

00:0011:00000:00223:2015/05/11 11:01:48.75 kernel  pc: 0x00000000011d3558 s_handle+0xaf8()

00:0011:00000:00223:2015/05/11 11:01:48.75 kernel  pc: 0x000000000123aad3 exc__raise+0x2f3()

00:0011:00000:00223:2015/05/11 11:01:48.75 kernel  pc: 0x000000000123a76c exc_raise+0x10c()

00:0011:00000:00223:2015/05/11 11:01:48.75 kernel  pc: 0x000000000117f810 s_compile_stmt+0x2750()

00:0011:00000:00223:2015/05/11 11:01:48.75 kernel  pc: 0x000000000117b117 s_compile+0x567()

00:0011:00000:00223:2015/05/11 11:01:48.75 kernel  pc: 0x00000000011da9f8 s_recompile+0x807()

00:0011:00000:00223:2015/05/11 11:01:48.75 kernel  [Handler pc: 0x0x000000000123afb0 hdl_stack installed by the following function:-]

00:0011:00000:00223:2015/05/11 11:01:48.75 kernel  [Handler pc: 0x0x00000000011d2a60 s_handle installed by the following function:-]

00:0011:00000:00223:2015/05/11 11:01:48.75 kernel  pc: 0x00000000011d736a sequencer+0x22ea()

00:0011:00000:00223:2015/05/11 11:01:48.75 kernel  pc: 0x00000000011a14b0 execproc+0x740()

00:0011:00000:00223:2015/05/11 11:01:48.75 kernel  pc: 0x0000000001195054 s_execute+0x3354()

00:0011:00000:00223:2015/05/11 11:01:48.75 kernel  [Handler pc: 0x0x000000000123afb0 hdl_stack installed by the following function:-]

00:0011:00000:00223:2015/05/11 11:01:48.75 kernel  [Handler pc: 0x0x00000000011d2a60 s_handle installed by the following function:-]

00:0011:00000:00223:2015/05/11 11:01:48.75 kernel  pc: 0x00000000011d5b1e sequencer+0xa9e()

00:0011:00000:00223:2015/05/11 11:01:48.75 kernel  pc: 0x00000000011a14b0 execproc+0x740()

00:0011:00000:00223:2015/05/11 11:01:48.75 kernel  pc: 0x0000000001195054 s_execute+0x3354()

00:0011:00000:00223:2015/05/11 11:01:48.75 kernel  [Handler pc: 0x0x000000000123afb0 hdl_stack installed by the following function:-]

00:0011:00000:00223:2015/05/11 11:01:48.75 kernel  [Handler pc: 0x0x00000000011d2a60 s_handle installed by the following function:-]

00:0011:00000:00223:2015/05/11 11:01:48.75 kernel  pc: 0x00000000011d5b1e sequencer+0xa9e()

00:0011:00000:00223:2015/05/11 11:01:48.75 kernel  pc: 0x00000000007c7a99 tdsrecv_language+0x199()

00:0011:00000:00223:2015/05/11 11:01:48.75 kernel  [Handler pc: 0x0x000000000153d570 ut_handle installed by the following function:-]

00:0011:00000:00223:2015/05/11 11:01:48.75 kernel  pc: 0x00000000007e87e0 conn_hdlr+0x1100()

"Some statistics, particularly cluster ratios, may be slightly inaccurate because not all page allocations and deallocations are recorded during changes made by data modification queries. Run update statistics or create index to correct any inconsistencies."

I am curious in what condition table level statistics like DPCR became slightly inaccurate and why the document is mentioning 'not all page allocations and deallocations are recorded during changes made by data modification queries.' so i did some research from Note,google,old document.. and also raised to SAP support but I can only get partial answers without expaination, anyway below is my understanding/summary for Table level statistics inaccuracy based on my shallow knowledge, please correct me/share me some light on it:

For Table level statsitcs(pagecnt/SPUT/DPCR):

1. Flush happens periodically by Housekeeper process.

2. Flush can also be triggered before scavenge process, but it's not guaranteed as deadlock can be happened.

If deadlock happened and after scavenge, and if DES is gone from cache, the new pagecnt can't be flushed into systabstats to reflect new value.

3. If a spin-lock on DES and at same time, first oam page for table is exclusively latched, pagecnt will not be flushed to systabstats this time, but can be flushed next time.

4. For performance reasons, the Tally Manager works in a non-transactional fashion, which can allow for some inaccuracy for some stats like pagecnt/dpcr.

-->I guess some page split happens during inserting but pagecnt should be recorded. But during roll-back, for perfromance purpose, those deleted pages is recorded with estimate values.

5. DES not in cache because of crashes: the new pagecnt can't be flushed to systabstats to reflect new value.

6. DES not in cache because of roll-backs: the new pagecnt can't be flushed to systabstats to reflect new value.

But I can't imagine how DES can be lost during roll-back..

7. SPUT "Space utilization uses the average row size and number of rows to compute the expected minimum number of data pages, and compares it to the current number of pages."

datarowsize is populated with an estimate which may be inaccurate, particularly if have variable width columns (for instance NULLable columns).

8. reorg rebuild will update accurate pagecnt, but does not update datarowsize in systabstats.

9. Updating the table statistics improves the datarowsize accuracy.

10. Spinlock contention on DES can slow down ASE but it's not the cause of inaccuracy.

Dear all,

It has been weeks that my colleagues and I are looking for the version 12.5.4 of Sybase ASE for Solaris 11.2. We eventually found a download but the latter contains only a folder called ebf23292 which contains the setup binary file to launch.

Could you please tell me whether this is actually a complete setup or does it only contain patches for an existing version that should previously be installed?

Thank you for your help.

Regards,

Hi,

I am having problems catching server messages with my python scripts.

Specifically, when I issue the command:

mount database all from 'manifest' with listonly

If I issue this in an isql prompt I get a big list of all the devices in the manifest file, but I am having problems accessing this information with my python script.

If I use the sybpydb module, the information ends up in connection.messages, but from what I have gathered, sybpydb requires SYBASE to be installed, which is not viable as I am writing a client and not every user will have a valid Sybase installation.

I have been trying with a regular ODBC driver, which works fine except that I am unable to access system messages, such as the output from the mount command above.

Anyone have any ideas or tips?

Dear all,

I am attempting to install an ASE server on a Solaris 11.2 machine (sun4v) but I am getting the following error:

-bash-4.1$ ./setup
InstallShield Wizard

Initializing InstallShield Wizard...

Searching for Java(tm) Virtual Machine...
Bad System Call (core dumped)

When I ask for more details from the core file generated after the setup fails, I get:

ffbfee08 access+8(baeb9, 89bb4, ba4b0, ba4b0, 0, 9)

ffbfef00 __1cMPlatformImplWcreateTempSubDirectory6F_nHSString__+0x30(baeb9, 1, 0, b8800, 0, b99a8)

ffbfefb0 __1cIJVMFilesOwriteVerifyJar6M_v_+0xd8(1, b99a8, b99a8, 0, baeb8, 1)

ffbff078 __1cIJVMFilesGsearch6MrnQJVMMatchPtrDeque__v_+0x18(b0790, ffbff270, ffbff594, 1, 0, baeb8)

ffbff198 __1cILauncherHfindJVM6Fbb_v_+0xdc(1, 1, 1, 1, 1, 1)

ffbff2b8 __1cMInstructionsHexecute6kM_i_+0x260(daf80, b8800, 0, 0, 4, b9a78)

ffbff5a8 __1cILauncherDrun6F_i_+0x20(b0760, 1, 7, 4, b9a78, b2e6c)

ffbff650 __1cILauncherOprocessCmdLine6FrknLStringDeque__i_+0xedc(ffbffb90, 0, 0, 1, 13, 0)

ffbffa28 __1cILauncherHprocess6FrnLStringDeque_rknHSString__i_+0x98(ffbffb90, ffbffb80, 400, e, b9871, 0)

ffbffac0 main+0x13c(1, ffbffc0c, ffbffc14, b0000, b9870, 1)

ffbffba8 _start+0xf8(0, 0, 0, 0, 0, 0)

Would you have any idea about the problem I am facing here? Seems like the system call access cannot be found and someone told me I should try on Solaris 10? Do you confirm that? Is ASE 12.5.4 incompatible with Solaris 11?

What do you suggest? I URGENTLY need to install an ASE 12.5.4 on a Solaris system.. Thanks for your help

Regards,

Hi, I've been testing LDAP logins with an ASE16 server, and we've been seeing some strange behaviour: If I set up an ASE login with ASE pwd pass123 and LDAP is enabled, and the user logins with their Windows account with pwd Win123, it seems that the Windows password overwrites the ASE password. i.e. if I turn off LDAP afterwards and the user tries to login with their ASE login, it requires pwd Win123.

Is this expected behaviour?

thanks

We attempted an upgrade from 15.7 SP122 to SP132 but we experienced a problem with trigger permissions.

Case :

     Table A     in DB1 has a trigger which fires a      delete from      Table B in DB2

     All databases, tables and triggers are owned by user 1

After the upgrade to SP132, we updated table A and the trigger fails with

          DELETE permission denied on object B, database DB2, owner dbo

We extracted the trigger definition from the database and reloaded it.

We ran the updated on table A again and the process was successful.

We have a few triggers and this didn't affect all of them so far so seems like a glitch somewhere.

We're due to try the upgrade on another server so we'll be able to test this before and after the upgrade.

A serious bug has been found in 15.7 SP133 and higher (currently SP134 is the only higher release).

The problem is seen when (or after) loading a transaction log dump that contains log records for a reorg rebuild with online command.  The known symptoms are either a 3475 error "During redo the page timestamp value is less than old timestamp from log. ..." during recovery of the load transaction, or error 2503 "Table Corrupt: Page linkage is not consistent" reported running dbcc checktable or dbcc checkdb following load transaction.

Recommendation:

Do not use reorg rebuild with online until an SP containing a fix for this bug has been released and you have upgraded to it.  (Development is currently working on a fix, but it is not yet available).  The regular reorg rebuild can still be run, the problem is limited to the with online option.

It is also possible to avoid the issue by downgrading ASE to a version lower than 15.7 SP133.  However, this option is not particularly recommended as SP133/134 contain security fixes.

KBA 2168634 http://service.sap.com/sap/support/notes/2168634 has been published containing this same information.  You can subscribe to the KBA to be automatically notified when the CR is fixed. I will also update this thread when I become aware the CR is fixed.

-bret

Message was edited by: Bret Halford Corrected KBA number to 2168634.

Dear Experts,

I was trying to install ASE 16 on RHEL 6.5 using VMware 11 interface on a windows 8.1 platform (Laptop)

Software downloaded from SAP service market place

--Received following errors

Product configuration failed

We've upgraded from 15.7 SP122 to 15.7 SP134.

However, 3 days after the upgrade we're seeing a lot of these messages in the log.

00:0023:00000:02175:2015/05/16 12:23:06.53 server Error: 2805, Severity: 18, State: 43 
00:0023:00000:02175:2015/05/16 12:23:06.53 server Bad pointer 0x0xffff0000 encountered while remapping stored procedure ' Invalid pointer param number 3, pointer value 0x(nil) '. Must re-create procedure. 

It says we need to re-create the proc - but there is no inidication of which proc to re-create ?

We have lots of these errors in the log - so it could be one proc or many. How do we find out ?

Luckily we've only upgraded a test server, how do we minimise these problems when rolling it out to live servers ?

Hi community.

I'm interested about the RoadMap for ASE Cluster Edition 16. I know that with ASE CE I can't read and/or write in the same objects of database simultaneously in each node as I understand that Oracle RAC does . What is the position of SAP about this topic?

Thanks for your answers.

Christian!

Sybase version: Adaptive Server Enterprise/15.7.0/EBF 22639 SMP SP52 /P/Sun_svr4/OS 5.10/ase157sp5x/3293/64-bit/FBO/Wed May 21 02:49:14 2014

--

Hi community,

I'm using sqsh to connect to my dataserver

I want to drop a database -- after rebooting my dataserver -- but the command failed because it seems somebody is using it

1> drop database ANDREAS_20150511

2> go

Msg 3702, Level 16, State 14

Server 'NY423ZN', Line 1

Cannot drop the database 'ANDREAS_20150511' because it is currently in use.

But when I do a 'sp_who' I cannot see any connection into it

1> sp_who

2> go | grep ANDREAS_20150511

1>

How can I find out my guilty connection? How can I drop it

Just to add an exotic thing. I'm working on migration project and my task is to fine-tune the system to make them fast.

One option I'm trying is to have my log segment on a ram-disk (I know, very dangerous) just for the time of the conversion. As soon as the conversion is finished, I reload my DB on disk devices.

My database has indeed one of its device on a ram-disk so I understand it's no usable anymore but I just want to get rid-off it.

How can I proceed?

Thanks

Simon

Hi All,

I'm handling about customer's issue that has a problem with disappearing a dataserver.

Once when I restart a server, dataserver is operating properly.
So, at the moment before 20 minutes user can login to server.

But, after about 20 minutes the server has been disappeared automatically.

Accordingly, user can't connect to not only a server directly but also through by SAPGUI.

There was no process which can be started to kill the server.
In addition, there was no history in error log file.

Nobody, execute a kill command.

Have you ever seen that before?

If you have, please let me know about that.

Server Version : 15.7 EBF 24258 SMP SP133 for Linux 2.6.32-220.el6.x86_64

Thanks in advance.

jinkyun.

We're trying to load up numeric values using C# ADO driver into fields of type numeric (38,8)

In C# we're using Decimal which supports precision upto 28. https://msdn.microsoft.com/en-us/library/364x0z75.aspx

However, the C# ADO drivers for Sybase only support up to precision 26 even thought the database does.

As soon as you use precision > 26 you get the error message "Data overflow. Increase specified column size or buffer size"

(looks similar to this issue ADO.NET data provider supports max precision of 26 numbers in decimals #toadworld)

We've checked the drivers and the check exists in all the SDK releases up to SP130 and the value 26 is hard coded in the drivers.

Why the limitation ?

How can data be loaded into numeric(38,8) using C# ?

Is it fixed in later SDKs

I'm not sure where to post this as it applies to all the SAP products.

Hi all,

Every time SAP comes out with a new set of pdf manuals, the meta data has to be corrected.  Often the stored titles, description, etc are wildly wrong.  Very sloppy and unprofessional for a mega corp the size of SAP.

The ePub book format has been out for many years and has many features that make it tablet, phone, PC, whatever friendly.  Reading a SAP manual at night?  No problem, change the font color to white on black so you don't wake your spouse.  The font is too small?  No problem, choose a larger or different font.  You can't do any of that with a PDF.  Try reading the ASE Admin guides on a 4" iPhone.  I dare you.  You might as well pour salt in your eye sockets.

jason

Wanted: SAP manuals in ePub format | Jason L. Froebe &amp;#8211; Tech tips and How Tos for Fellow Techies