Hi community,

I would like to have you feedback about the usage of sybase threads engines vs solaris chip/cpu/threads, if there are any settings that must be prevented.

as far as I understand, the sybase engines are now threaded (if configuration parameter 'kernel mode' is set to 'threaded' which is my case) meaning that at the system level we see only one process

my_host simon /tmp/

bash$ ps -ef | grep dataserver

s157  9192  9190   9   Apr 11 ?        1033:21 /my_host/sybase/ase157/MYHOST/ASE-15_0/bin/dataserver -d/my_host/sybase/ase157

bash$ prstat -L -p 9192                                                 

   PID USERNAME  SIZE   RSS STATE  PRI NICE      TIME  CPU PROCESS/LWPID

  9192 s157       95G   95G sleep    1    0   2:54:48 0.0% dataserver/22

  9192 s157       95G   95G sleep   12    0   2:24:04 0.0% dataserver/20

  9192 s157       95G   95G sleep    1    0   2:18:13 0.0% dataserver/19

...

  9192 s157       95G   95G sleep   13    0   0:00:07 0.0% dataserver/1 

Total: 1 processes, 276 lwps, load averages: 0.19, 0.43, 0.38 

note: By the way is there a way to do the correlation between 'prstat -L' output and the 'number of max online engines'?

So we have threads at Sybase level

On the other hand, most servers I'm working on are Solaris10 zone and with those T6 processors, I have chip containing cores that could be multi-thread.

This means the output of mpstat shows the thread dedicated to my zone, I could potentially have to threads on the same chip etc...

are there any recommendations on how core/threads at system level should be configured for optimal performances? for example if my dataserver is configured for 4 threads, should I ask my UNIX admin to have a zone with 4 'virtual' cpu that are actually four threads on the same core?

Thanks for your input,

Simon

Hello, I am having a bit of a mystery. I have a database which is almost identical on 2 different, identical servers with the same version (Adaptive Server Enterprise/16.0 SP02 PL01/EBF 25183 SMP/P/X64/Windows Server/ase160sp02p100/0/64-bit/FBO/). I am running the same query on both databases. The tables have identical structure and identical indexes. The query plans for the query is different. The top query plan is nearly instant, the bottom query plan takes about 6 minutes to run. I don't understand why it's using different plans. Help please!

Select RSISSet.*, RSC.Sequence as Sequence

from Table1 RSC

inner join Table2 RSISSet

    on RSISSet.Field3= RSC.ContentId

where RSC.IndexRef2 = 1942454143 and ( RSISSet.Kind= -115 or RSISSet.Kind=-128 )

go

QUERY PLAN FOR STATEMENT 1 (at line 3).

Optimized using Serial Mode

    STEP 1

        The type of query is SELECT.

        4 operator(s) under root

       |ROOT:EMIT Operator (VA = 4)

       |

       |   |NESTED LOOP JOIN Operator (VA = 3) (Join Type: Inner Join)

       |   |

       |   |   |SCAN Operator (VA = 0)

       |   |   |  FROM TABLE

       |   |   |  Table1

       |   |   |  RSC

       |   |   |  Index : Table2Ref2Key

       |   |   |  Forward Scan.

       |   |   |  Positioning by key.

       |   |   |  Keys are:

       |   |   |    IndexRef2 ASC

       |   |   |  Using I/O Size 32 Kbytes for index leaf pages.

       |   |   |  With LRU Buffer Replacement Strategy for index leaf pages.

       |   |   |  Using I/O Size 32 Kbytes for data pages.

       |   |   |  With LRU Buffer Replacement Strategy for data pages.

       |   |

       |   |   |RESTRICT Operator (VA = 2)(0)(0)(0)(7)(0)

       |   |   |

       |   |   |   |SCAN Operator (VA = 1)

       |   |   |   |  FROM TABLE

       |   |   |   |  Table2

       |   |   |   |  RSISSet

       |   |   |   |  Index : RSField3Key

       |   |   |   |  Forward Scan.

       |   |   |   |  Positioning by key.

       |   |   |   |  Keys are:

       |   |   |   |    Field3 ASC

       |   |   |   |  Using I/O Size 32 Kbytes for index leaf pages.

       |   |   |   |  With LRU Buffer Replacement Strategy for index leaf pages.

       |   |   |   |  Using I/O Size 32 Kbytes for data pages.

       |   |   |   |  With LRU Buffer Replacement Strategy for data pages.

Total estimated I/O cost for statement 1 (at line 3): 2276580.

QUERY PLAN FOR STATEMENT 1 (at line 2).

Optimized using Serial Mode

    STEP 1

        The type of query is SELECT.

        9 operator(s) under root

       |ROOT:EMIT Operator (VA = 9)

       |

       |   |SEQUENCER Operator (VA = 8) has 2 children.

       |   |

       |   |   |STORE Operator (VA = 2)

       |   |   |  Worktable1 created, in allpages locking mode, for REFORMATTING.

       |   |   |  Creating clustered index.

       |   |   |

       |   |   |   |INSERT Operator (VA = 1)

       |   |   |   |  The update mode is direct.

       |   |   |   |

       |   |   |   |   |SCAN Operator (VA = 0)

       |   |   |   |   |  FROM TABLE

       |   |   |   |   |  Table1

       |   |   |   |   |  RSC

       |   |   |   |   |  Index : Table2Ref2Key

       |   |   |   |   |  Forward Scan.

       |   |   |   |   |  Positioning by key.

       |   |   |   |   |  Keys are:

       |   |   |   |   |    IndexRef2 ASC

       |   |   |   |   |  Using I/O Size 4 Kbytes for index leaf pages.

       |   |   |   |   |  With LRU Buffer Replacement Strategy for index leaf pages.

       |   |   |   |   |  Using I/O Size 4 Kbytes for data pages.

       |   |   |   |   |  With LRU Buffer Replacement Strategy for data pages.

       |   |   |   |

       |   |   |   |  TO TABLE

       |   |   |   |  Worktable1.

       |   |

       |   |   |NESTED LOOP JOIN Operator (VA = 7) (Join Type: Inner Join)

       |   |   |

       |   |   |   |NESTED LOOP JOIN Operator (VA = 5) (Join Type: Inner Join)

       |   |   |   |

       |   |   |   |   |SCAN Operator (VA = 3)

       |   |   |   |   |  FROM OR List

       |   |   |   |   |  OR List has up to 2 rows of OR/IN values.

       |   |   |   |

       |   |   |   |   |SCAN Operator (VA = 4)

       |   |   |   |   |  FROM TABLE

       |   |   |   |   |  Table2

       |   |   |   |   |  RSISSet

       |   |   |   |   |  Index : RSKind_I

       |   |   |   |   |  Forward Scan.

       |   |   |   |   |  Positioning by key.

       |   |   |   |   |  Keys are:

       |   |   |   |   |    Kind ASC

       |   |   |   |   |  Using I/O Size 32 Kbytes for index leaf pages.

       |   |   |   |   |  With LRU Buffer Replacement Strategy for index leaf pages.

       |   |   |   |   |  Using I/O Size 32 Kbytes for data pages.

       |   |   |   |   |  With LRU Buffer Replacement Strategy for data pages.

       |   |   |

       |   |   |   |SCAN Operator (VA = 6)

       |   |   |   |  FROM TABLE

       |   |   |   |  Worktable1.

       |   |   |   |  Using Clustered Index.

       |   |   |   |  Forward Scan.

       |   |   |   |  Positioning by key.

       |   |   |   |  Using I/O Size 4 Kbytes for data pages.

       |   |   |   |  With LRU Buffer Replacement Strategy for data pages.

Total estimated I/O cost for statement 1 (at line 2): 3550013.

Hi All,

We are using the Database Auto Expansion policy for our product, the current architecture is as following : A Device contains multiple segments, with monthly partitions (12 months per segment). We have successfully enabled the Auto Expansion policy for device, and the corresponding segment by issuing following commands

1. For device growthby and max size : sp_dbextend 'set', 'device', my_device, '500m', '50000m'

2. For segment growthby : sp_dbextend 'set', 'database', mydatabase, 'my_segment', '500m'

3. For segment threshold: sp_extend 'set', 'threshold', mydatabase, 'my_segment', '100m'

(Note: Because of the segments is created on same device, so we only need to set the threshold for a device, the others will be applied the same)

Everything works properly when the growthby value of segment is smaller than the current device size. But when I set the growthby value of segment equal or greater than current device size, and the Auto Expansion policy seem not work any more until we modify the device size to the value that is greater than growthby value of segment.

For example: I create a device (my_device) with 500 MB of size, and then I set the growthby value of segment (my_segment  -- created on my_device ) is 512 MB. In theory, the device will grown automatically when beginning to insert the data but it did not. I also added the data to reach the threshold of segment, but again nothing happened. Would you please let me know your idea about this case ?

Thanks

Khoa Tran

Hi.

This question is in regard to using datalength() on a text or image column that allows nulls.

For decades now, going back probably to Sybase SQL Server version 4, I have used datalength() to tell if a text/image column is null. If that returns 0, it's null. This is true up through ASE 15.0. But now I observe in ASE 16.0 that datalength() returns NULL when given a null text/image column. I'm guessing that datalength() will no longer return 0 under any circumstances. This causes some of my existing T-SQL code to break.

I've checked the manual, and it says "datalength of any NULL data returns NULL". That's fine, but it also says that in the ASE15.0 manual, and indeed all the way back to the 11.5 manual (which is the oldest one I have easy access to). So apparently for a long, long time the manual did not correspond to the behavior. And instead of fixing the ASE16 manual to match the behavior, Sybase apparently fixed the behavior to match the manual. This is annoying. In my long experience with Sybase it's extremely rare for a new ASE version to break my existing T-SQL code.

I googled this topic and didn't find anything, which surprises me because wouldn't most people dealing with text or image columns experience this same problem when moving up to ASE16?

My first question is, is there an option to revert the behavior in ASE16 to match the old behavior? If not, then my second question is what should I do about this?

I'm thinking that in a pure ASE16 environment, I can just test for the function returning null, or even better I can now test the text/image value directly, like one of the following:

     where datalength(text) is null

or...

     where text is null

But for a while I will be in a mixed ASE15/16 environment, where I have a common base of source code that's intended to work in both versions. So I think I could do this:

     where isnull(datalength(text),0)=0

And that should work reliably in any version of ASE (even if Sybase ever decides to change the behavior BACK to what it was).

Any other advice for me?

Thanks.

- John.

load 800G archive db received Msg 711

My env:

ASE: ASE15.7 sp132 ia64

DB: 600GB

20 stripe dump file: 200GB

dump db cmd:

dump database DB to "/DB_DUMP/db0104070120.dmp"

stripe on "/DB_DUMP/0204070120.dmp"

...

stripe on "/DB_DUMP/0204070120.dmp"

with compression=6

Archive DB schema:

disk init name="scratchdb_dev", physname="/…/…/…", size="30000M", skip_alloc=true, dsync=false, directio=false

disk init name="archivedb_dev", physname="/…/…/…", size="2000M", skip_alloc=true, dsync=false, directio=false

create database scratchdb on scratchdb_dev=30000

sp_dboption "scratchdb", "scratch database", "true"

create archive database DBarchive on archivedb_dev = 2000 with scratch_database = scratchdb

load db cmd:

load database DBarchive from "/DB_DUMP/db0104070120.dmp"

stripe on "/DB_DUMP/0204070120.dmp"

...

stripe on "/DB_DUMP/0204070120.dmp"

Received the following message:

Msg 711, Level 17, State 9:

Server 'ASE1570', Line 1:

There is presently insufficient system memory to allocate 2048 bytes for new structures. Please try again when there is less

activity on the system.

Msg 965, Level 21, State 2:

Server 'ASE1570', Line 1:

Unable to create the database disk map for the archive database '9'.

Execution Time (ms.): 11246916          Clock Time (ms.): 11246916

I had do the following configured:

max memory from 2000M to 8000M

default data cache from 1000M to 2000M

compress memory from 100M to 1000M

Still received the same Msg 711, and the execution time no change

Any idea what is the "system memory" mean?

or any parameter I can tune?

Hi All,

I am trying to get hold of the ASE 15.7 client and I am unable to find a download (and I find the store search the pits, really).  Any ideas where I could get that from?

Regards,

Martin

Hello guys.

I already read some other forums and articles in the Internet, but nothing that I found helped me.

Could you please try to help me?

- There is an application job executing the bcp utility (with -e option) and inserting data into a table

- The permission of the file is being wrongly generated. It should be 644, but the file is created as 400

- The application team cannot read the file as they are using different Ids from the one used by the batch job

- We already tried to use the filemode option, change the umask to 022, change the OS Id to different groups, etc. None of them worked.

- The ASE version is 15.7 SP136

- The application team says the issue started happening after the upgrade from ASE 15.0.2 to 15.7

- Although this is just an ordinary error file, Customer want us to fix the issue as we're responsible for their environment. We could simply add a chmod command after the bcp and change the permission.

- I already connect to the Unix server using the Id used by the batch job and executed the bcp out command and the file was correctly generated (for both ASE V15 versions)

- The Unix team opened a PRM and already performed all the activities suggested by the 2nd level support

Do you guys have another suggestion?

Thanks.

Sergi

-- 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

-- end ---

Good afternoon,

I'm looking at the top 10 WaitEvent system-wide in table monSysWaits and I noticed the WaitEvent 'checkpoint worker waiting for wakeup from parent'

I couldn't find any description in Sybase infocenter.

Does anyone have some information about it and whether I should worry if the value is high?

Thanks

Simon

Hi.

In many previous ASE versions (up through 15.0), my standard practice when replacing a trigger in a live system was to simply use CREATE TRIGGER, without using DROP TRIGGER first. ASE allowed that, and I assume that it implicitly performed a DROP in an atomic operation with the CREATE.

The reason why the atomicity is important is because, without it, a user could perform a DML operation during the tiny window of time between the DROP and the CREATE, meaning some data could get into the database that was not subject to all the normal logic that the trigger would perform. I always have assumed (with no real proof) that my old way of doing it (i.e. CREATE with no DROP) prevented that possibility.

Now in ASE 16.0, my old method doesn't seem to work. ASE now disallows creating a trigger when a trigger with that name already exists. So I thought to use the CREATE OR REPLACE TRIGGER command. But that also didn't work for me, because ASE forbids it if I wasn't the user who created the trigger. Note that I am aliased to dbo in the database, and so is the user who created the trigger, but that apparently matters not to ASE.

Strangely, even though ASE16 forbids CREATE OR REPLACE TRIGGER, it still lets me DROP TRIGGER. So I am now explicitly dropping the trigger prior to creating it. That gets the job done, but now I assume it opens me up to the logic glitch I mentioned above, where a live user might insert a row during the window between my DROP and my CREATE.

Am I doing something wrong? Is there a permission setting that will allow CREATE OR REPLACE TRIGGER to work the way I want? Is there a way to force atomicity of the DROP and CREATE commands? Would the "ddl in tran" option be usable here? (I have no experience using that option). Must I limit all my trigger replacements to off-hours when no live users are in the system?

Thanks.

- John.

To be honest, this is the first time when I've been frustrated much much more than excited looking through the session catalogue of the forthcoming great SAP technology event  (you may see it here if you want to be frustrated too:  https://sessioncatalog.sapevents.com/go/agendabuilder.sessions/?l=130&locale=en_US).

Please tell me that I'm wrong - tried to find sessions on ASE - found none (search engine error I hope).  Made me upset - but not really surprised as I've got used to this rather methodical neglect.

What made be really upset is when I came across this session:

Are you serious?  Oracle has at last released a flavour of in-memory database that approaches ASE IMDB (with a delay of ... a decade?).

SAP gives Oracle the platform to talk about this ground-breaking step forward and keeps philosophically quiet about "things important in life".  What about ASE IMDB "proof points?"  Are there any?  How many of SAP users know  that the platform exists in ASE long before it has been introduced into Oracle?  Will it continue to be buried behind the gloss of the real SAP favourite - HANA - to the extend that ASUG technology summit will advertise Oracle products and meticulously avoid talking about similar (better? more mature?) products from its ex-Sybase factory - because it threatens to obscure the gloss of its favourite bright kid (737 sessions out of 1560 somehow related to HANA and 0 to ASE)?

I've come across this rather distressing negligence about a year ago when attending Melbourne SAUG conference.  Oracle was there - talking gleefully how Oracle has much better chances than any of its competitors (SAP inclusive) to offer real in-memory DBMS platform.  To me this looks like a cancerous development in the soft tissue of SAP marketing brain.  The problem is - no one seems to care.

Not sure what to say.

I feel sad.

Andrew

Hello,

The question is described in the title. The question derives from the limitations of Edge edition on the number of cores. For ASE Small Business Edition on virtual machines we had to run a utility on the vm host and declare a variable in the vm. I don't find any similar procedure for Azure, so I assume that if the machine is inside the limits of Edge edition the license will be checked out. I am trying to confirm this assumption.

Thank you in advance

Kimon Moschandreou

Hi gues!

Maybe someone saw such error.

Msg 12313, Level 21, State 1:

Server 'test1', Line 1:

Internal error: Insert into page id 278443007 of index id 4 of table 'sysobjects' (id = 1) in database 'test1' tried to replace undeleted RID (385699354,12) at slot 10 and ridposn 4. Try dropping and recreating the index.

Msg 12313, Level 21, State 1:

Server 'test8', Line 1:

Internal error: Insert into page id 278443007 of index id 4 of table 'sysobjects' (id = 1) in database 'test1' tried to replace undeleted RID (385699354,12) at slot 10 and ridposn 4. Try dropping and recreating the index.

When I load a dumping from the working server on test (I checked on 2 different test servers) I receive the following error.

In backup server log:

......(normal load database)

Backup Server: 4.188.1.1: Database test1: 3375882328 kilobytes (97%) LOADED.

Backup Server: 4.188.1.1: Database test1: 3410754414 kilobytes (98%) LOADED.

Backup Server: 4.188.1.1: Database test1: 3445497480 kilobytes (99%) LOADED.

Backup Server: 4.188.1.1: Database test1: 3480366076 kilobytes (100%) LOADED.

Backup Server: 4.188.1.1: Database test1: 3487125576 kilobytes (100%) LOADED.

Backup Server: 3.42.1.1: LOAD is complete (database test1).

Started estimating recovery log boundaries for database 'test1'.

Database 'test1', checkpoint=(34548290, 14), first=(34548164, 36), last=(39489424, 42).

Completed estimating recovery log boundaries for database 'test1'.

Started ANALYSIS pass for database 'test1'.

Completed ANALYSIS pass for database 'test1'.

Started REDO pass for database 'test1'. The total number of log records to process is 52036795.

Recovery prefetch size is 2400 log records.

Recovery prefetch size is 2880 log records.

Redo pass for database 'test1': 2601839 records done (4%); 49434956 records left.

Recovery prefetch size is 3456 log records.

Recovery prefetch size is 4147 log records.

Redo pass for database 'test1': 5203678 records done (9%); 46833117 records left.

Recovery prefetch size is 4976 log records.

Recovery prefetch size is 5971 log records.

Redo pass for database 'test1': 7805517 records done (14%); 44231278 records left.

Recovery prefetch size is 7165 log records.

Recovery prefetch size is 8598 log records.

Redo pass for database 'test1': 10407356 records done (19%); 41629439 records left.

Recovery prefetch size is 10317 log records.

Recovery prefetch size is 12380 log records.

Redo pass for database 'test1': 13009195 records done (24%); 39027600 records left.

Recovery prefetch size is 14856 log records.

Recovery prefetch size is 17827 log records.

Redo pass for database 'test1': 15611034 records done (29%); 36425761 records left.

Recovery prefetch size is 20000 log records.

Redo pass for database 'test1': 18212873 records done (34%); 33823922 records left.

Redo pass for database 'test1': 20814712 records done (39%); 31222083 records left.

Redo pass for database 'test1': 23416551 records done (44%); 28620244 records left.

Redo pass for database 'test1': 26018390 records done (49%); 26018405 records left.

Redo pass for database 'test1': 28620229 records done (54%); 23416566 records left.

Redo pass for database 'test1': 31222068 records done (59%); 20814727 records left.

Redo pass for database 'test1': 33823907 records done (64%); 18212888 records left.

Msg 12313, Level 21, State 1:

Server 'test1', Line 1:

Internal error: Insert into page id 278443007 of index id 4 of table 'sysobjects' (id = 1) in database 'test1' tried to replace undeleted RID (385699354,12) at slot 10 and ridposn 4. Try dropping and recreat.

During of a backup work in databases is continued.(not dbo use only)

And as the error seems to me occurs at the time of load of a log of databases

Some time ago we already received similar errors,with other number of the page, but with the same object'sysobjects' (id = 1).

Internal error: Insert into page id 274230927 of index id 3 of table 'sysobjects' (id = 1) in database 'diasdb1' tried to replace

undeleted RID (383680310,5) at slot 130 and ridposn 0. Try dropping and recreating the index.

But next day in case of dump and a load database of errors wasn't.

And it is strange that the error arises on index id 4 'sysobjects' (id = 1) because on this objects only 2 indexes:(only 2 and 3)

select * from sysindexes

where id=1

dbcc checktable (sysobjects) in test database not have errors(the basis is load after the previous error).

What it is possible to make mistakes for the decision?

Hello ,

Running SAP ASE 16 SP02- Linux, I'm getting this error in errorlog :

00:0012:00000:00040:2016/04/17 08:00:41.99 server  SET SWITCH SERVERWIDE OFF 3605, SPID 40.

00:0012:00000:00040:2016/04/17 08:00:41.99 server  Error: 12328, Severity: 21, State: 1

00:0012:00000:00040:2016/04/17 08:00:41.99 server  The calculated row offset '0' of an index key on page '30374162' for object '1365576872' in database '6' is out of bounds (table offset on page = '-8', page status = '257', local offset table address = 0x0x198464fb0).

..<stack trace>

I've checked some KBA's and one points to the following action :

Turning off some optimizer strategies such as "group_inserting" and "distinct_hashing" may avoid this issue.

Q: Is "distinct_hashing" still available on ASE 16 in order to be changed with "set" command?

Thank you

Regards

Jose

Hi,

I am running version 15.5 of ASE and I wonder if it is possible to run python under this version ?

Regards,

Klas

Hi Experts,

Recently we got an error 5859,5899 with severity 16 during non business hours and the customer today in the morning addressed that he is noticing heap database errors which are specified below.

Errors from DS error log file(our end):

00:0002:00000:00002:2016/04/20 00:45:52.07 kernel  Virtual device 12 started using asynchronous (with DIRECTIO) i/o.

00:0002:00000:00002:2016/04/20 00:45:52.11 server  Error: 5859, Severity: 16, State: 1

00:0002:00000:00002:2016/04/20 00:45:52.11 server  The configuration number '652' is invalid.

00:0003:00000:00000:2016/04/20 00:45:57.60 kernel  Thread 3 (LWP 11889) of Threadpool syb_default_pool online as engine 1

00:0002:00000:00002:2016/04/20 00:45:58.00 server  Error: 5899, Severity: 16, State: 1

00:0002:00000:00002:2016/04/20 00:45:58.00 server  The value of the 'max memory' parameter (5242880) defined in the configuration file is not high enough to set the other parameter values specified in the configuration file.

Can anyone from you let me know the way to fix these errors and also is there any relation between these errors that are generated at our end with the errors that are being noticed at customer's end?

Customer noticed error details below:

Noticed there are heaps database error, insufficient privilege errors in the message log on vlhecspaci.

Apr 20 14:08:53 vlhecspaci SAPSPA_00[20461]: R47 Basis System: Deletes session T137_U20917_M0 after error Execution was canceled (Softcancel) [Warning/Session]

Apr 20 14:09:12 vlhecspaci SAPSPA_00[40938]: R47 Basis System: Deletes session T125_U20921_M0 after error Execution was canceled (Softcancel) [Warning/Session]

Apr 20 14:09:49 vlhecspaci SAPSPA_00[8112]: BY2 Database: Database error 258 at EXE

Apr 20 14:10:55 vlhecspaci SAPSPA_00[18967]: BY2 Database: Database error 258 at EXE

Apr 20 14:10:56 vlhecspaci SAPSPA_00[46425]: BY2 Database: Database error 258 at EXE

Apr 20 14:10:59 vlhecspaci SAPSPA_00[11757]: BY2 Database: Database error 258 at EXE

Apr 20 14:11:55 vlhecspaci SAPSPA_00[60609]: BY2 Database: Database error 258 at EXE

Apr 20 14:11:58 vlhecspaci SAPSPA_00[26909]: BY2 Database: Database error 258 at EXE

Apr 20 14:12:49 vlhecspaci SAPSPA_00[60609]: BY2 Database: Database error 258 at EXE

Apr 20 14:12:53 vlhecspaci SAPSPA_00[21628]: BY2 Database: Database error 258 at EXE

Apr 20 14:12:58 vlhecspaci SAPSPA_00[34944]: BY2 Database: Database error -10709 at CON

Apr 20 14:14:49 vlhecspaci SAPSPA_00[36747]: R47 Basis System: Deletes session T76_U22309_M0 after error Execution was canceled (Softcancel) [Warning/Session]

Apr 20 14:14:50 vlhecspaci SAPSPA_00[37207]: BY2 Database: Database error 258 at EXE

Apr 20 14:15:08 vlhecspaci SAPSPA_00[43014]: R47 Basis System: Deletes session T122_U22311_M0 after error Execution was canceled (Softcancel) [Warning/Session]

Apr 20 14:15:50 vlhecspaci SAPSPA_00[21661]: BY2 Database: Database error 258 at EXE

Apr 20 14:15:50 vlhecspaci SAPSPA_00[21649]: BY2 Database: Database error 258 at EXE

Apr 20 14:15:54 vlhecspaci SAPSPA_00[27710]: BY2 Database: Database error -10709 at CON

Apr 20 14:15:54 vlhecspaci SAPSPA_00[21624]: BY2 Database: Database error 258 at EXE

Apr 20 14:16:55 vlhecspaci SAPSPA_00[21637]: BY2 Database: Database error 11216 at OPC

Apr 20 14:16:55 vlhecspaci SAPSPA_00[21637]: BY0 Database: > [ASE Error SQL11216][SAP][ASE ODBC Driver][Adaptive Server

Apr 20 14:16:55 vlhecspaci SAPSPA_00[21637]: BY0 Database: > Enterprise]Internal Ct-Lib/Cs-Lib error 33816856:

Apr 20 14:16:55 vlhecspaci SAPSPA_00[21637]: BY0 Database: > 'cs_convert: cslib user api layer: common library error: The

Apr 20 14:16:55 vlhecspaci SAPSPA_00[21637]: BY0 Database: > conversion/operation was stopped due to a syntax error in th

Apr 20 14:16:57 vlhecspaci SAPSPA_00[21625]: BY2 Database: Database error 258 at EXE

Apr 20 14:17:00 vlhecspaci SAPSPA_00[21609]: BY2 Database: Database error 258 at EXE

Apr 20 14:17:51 vlhecspaci SAPSPA_00[21625]: BY2 Database: Database error 258 at EXE

Apr 20 14:17:52 vlhecspaci SAPSPA_00[55777]: BY2 Database: Database error 258 at EXE

Apr 20 14:17:52 vlhecspaci SAPSPA_00[53946]: BY2 Database: Database error 258 at EXE

Apr 20 14:17:53 vlhecspaci SAPSPA_00[26210]: BY2 Database: Database error 258 at EXE

Apr 20 14:18:50 vlhecspaci SAPSPA_00[21670]: BY2 Database: Database error 258 at EXE

Apr 20 14:19:03 vlhecspaci SAPSPA_00[27710]: BY2 Database: Database error -10709 at CON

Regards,

Dilip Voora

Hi All,

We are using the Database Auto Expansion policy for our product, the current architecture is as following : A Device contains multiple segments, with monthly partitions (12 months per segment). We have successfully enabled the Auto Expansion policy for device, and the corresponding segment by issuing following commands

1. For device growthby and max size : sp_dbextend 'set', 'device', my_device, '500m', '50000m'

2. For segment growthby : sp_dbextend 'set', 'database', mydatabase, 'my_segment', '500m'

3. For segment threshold: sp_extend 'set', 'threshold', mydatabase, 'my_segment', '100m'

(Note: Because of the segments is created on same device, so we only need to set the threshold for a device, the others will be applied the same)

Everything works properly when the growthby value of segment is smaller than the current device size. But when I set the growthby value of segment equal or greater than current device size, and the Auto Expansion policy seem not work any more until we modify the device size to the value that is greater than growthby value of segment.

For example: I create a device (my_device) with 500 MB of size, and then I set the growthby value of segment (my_segment  -- created on my_device ) is 512 MB. In theory, the device will grown automatically when beginning to insert the data but it did not. I also added the data to reach the threshold of segment, but again nothing happened. Would you please let me know your idea about this case ?

Thanks

Khoa Tran

-- 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

-- end ---

Good afternoon,

I'm looking at the top 10 WaitEvent system-wide in table monSysWaits and I noticed the WaitEvent 'checkpoint worker waiting for wakeup from parent'

I couldn't find any description in Sybase infocenter.

Does anyone have some information about it and whether I should worry if the value is high?

Thanks

Simon

We've tried an upgrade to Sybase 16 ( AdSP02 PL02/EBF 25320 SMP)                               

and we've hit a possible bug with isolation level and insert into temp tables.

This proc

create or replace proc showbug

as

        select 1461081 pf_Id into #unwrap

runs ok normally, but when run like this

set transaction isolation level 0

go

showbug

go

We get this

     ASE is terminating this process.

and a stack trace.

Hello,

in our new installed NW 7.4 environment with ASE 16.0.02.02 we’ve to decide to use database encryption or not.

Are there any experience about performance, problems?

Many thanks.

Best regards

Winfried Bayer

When using table variables like this

declare @tab table

(

    PK char(8),

    Currency char(3)

)

update @tab

set Currency = s.Currency

from @tab p , s

where p.PK = s.PK

I get the message

      Ambiguous column name Currency

I've tried

     set p.Currency = s.Currency

Also,

     select p.Currency c1, s.Currency c2

     from @tab, s

gives 2 error messages

     Ambiguous column name Currency

What is going on ?

Is there a workaround.