Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

ASA 9.0 - abnormal shutdwon

4 posts in General Discussion Last posting was on 2003-12-22 14:38:33.0Z
Thomas George Posted on 2003-12-20 19:18:04.0Z
Sender: 6be1.3fe4a225.1804289383@sybase.com
From: Thomas George
Newsgroups: ianywhere.public.general
Subject: ASA 9.0 - abnormal shutdwon
X-Mailer: WebNews to Mail Gateway v1.1s
Message-ID: <3fe4a23d.6be2.846930886@sybase.com>
X-Original-NNTP-Posting-Host: 10.22.241.42
X-Original-Trace: 20 Dec 2003 11:25:49 -0800, 10.22.241.42
Lines: 32
X-Original-NNTP-Posting-Host: forums-2-dub.sybase.com
X-Original-Trace: 20 Dec 2003 11:05:19 -0800, forums-2-dub.sybase.com
NNTP-Posting-Host: forums-master.sybase.com
X-Original-NNTP-Posting-Host: forums-master.sybase.com
Date: 20 Dec 2003 11:18:04 -0800
X-Trace: forums-1-dub 1071947884 10.22.108.75 (20 Dec 2003 11:18:04 -0800)
X-Original-Trace: 20 Dec 2003 11:18:04 -0800, forums-master.sybase.com
X-Authenticated-User: ngsysop
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:2218
Article PK: 4425

Hello,
I have an application that currently uses SQLA 5.5.05 and
runs very well. I have been testing an evaluation copy of
ASA 9.0 for the purpose of upgrading my database. My 5.5.05
database was automatically converted to ver 9.0 when I tried
to open it using the 9.0 SQLCentral tool. However, when I
ran my application against the converted datbase, the
database engine simply terminated (crashed) whenever certain
queries were executed. I did some analysis and found that
one such instance is when the database engine execute a case
statement. Pls execute the following sequence on 9.0 and it
will most likey crash the engine:


create table employee (emp_id char(10), emp_level smallint);
insert employee values ('abc',1);
insert employee values ('xyz',2);

//The interesting part follows
case (select max(emp_level) from employee)
when 1 then select 'Level 1'
when 2 then select 'Level 2'
when 3 then select 'Level 3'
end case;


Are there any other such SQL constructs that can cause an
abnormal shutdown of the ASA 9.0 engine? Will I have to make
several code changes to migrate to the ASA 9.0? I hope not.
Please advice on how I should proceed.
Thanks
Thomas


Paul Horan[TeamSybase] Posted on 2003-12-21 04:55:52.0Z
From: "Paul Horan[TeamSybase]" <paulhATvcisolutionsDOTcom>
Newsgroups: ianywhere.public.general
References: <3fe4a23d.6be2.846930886@sybase.com>
Subject: Re: ASA 9.0 - abnormal shutdwon
Lines: 47
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Original-NNTP-Posting-Host: 67-23-182-204.bflony.adelphia.net
Message-ID: <3fe529aa$1@forums-2-dub>
X-Original-Trace: 20 Dec 2003 21:03:38 -0800, 67-23-182-204.bflony.adelphia.net
X-Original-NNTP-Posting-Host: forums-2-dub.sybase.com
X-Original-Trace: 20 Dec 2003 20:43:04 -0800, forums-2-dub.sybase.com
NNTP-Posting-Host: forums-master.sybase.com
X-Original-NNTP-Posting-Host: forums-master.sybase.com
Date: 20 Dec 2003 20:55:52 -0800
X-Trace: forums-1-dub 1071982552 10.22.108.75 (20 Dec 2003 20:55:52 -0800)
X-Original-Trace: 20 Dec 2003 20:55:52 -0800, forums-master.sybase.com
X-Authenticated-User: ngsysop
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:2219
Article PK: 4430

Your example most definitely does NOT crash an ASA9 engine.
I got the result set 'Level 2', which is to be expected... I'm running 9.0.0.1227, with a .db file created with that
version.

I'm curious about your description of the migration process. It "automatically" performed this migration just by
starting Sybase Central? That's a new one on me... I would expect you to have used the DBUNLOAD utility to unload the
5.5 file, DBINIT to create a fresh .db file in 9.0 format, and the ISQL utility to reload the data/structure into that
.db file. AFAIK, none of that happens just by starting SC4.2 on the old database.

--
Paul Horan[TeamSybase]

<Thomas George> wrote in message news:3fe4a23d.6be2.846930886@sybase.com...
> Hello,
> I have an application that currently uses SQLA 5.5.05 and
> runs very well. I have been testing an evaluation copy of
> ASA 9.0 for the purpose of upgrading my database. My 5.5.05
> database was automatically converted to ver 9.0 when I tried
> to open it using the 9.0 SQLCentral tool. However, when I
> ran my application against the converted datbase, the
> database engine simply terminated (crashed) whenever certain
> queries were executed. I did some analysis and found that
> one such instance is when the database engine execute a case
> statement. Pls execute the following sequence on 9.0 and it
> will most likey crash the engine:
>
>
> create table employee (emp_id char(10), emp_level smallint);
> insert employee values ('abc',1);
> insert employee values ('xyz',2);
>
> //The interesting part follows
> case (select max(emp_level) from employee)
> when 1 then select 'Level 1'
> when 2 then select 'Level 2'
> when 3 then select 'Level 3'
> end case;
>
>
> Are there any other such SQL constructs that can cause an
> abnormal shutdown of the ASA 9.0 engine? Will I have to make
> several code changes to migrate to the ASA 9.0? I hope not.
> Please advice on how I should proceed.
> Thanks
> Thomas


Thomas George Posted on 2003-12-21 21:17:16.0Z
Sender: 6691.3fe601cc.1804289383@sybase.com
From: Thomas George
Newsgroups: ianywhere.public.general
Subject: Re: ASA 9.0 - abnormal shutdwon
X-Mailer: WebNews to Mail Gateway v1.1s
Message-ID: <3fe60ddc.66a1.846930886@sybase.com>
References: <3fe4a23d.6be2.846930886@sybase.com><3fe529aa$1@forums-2-dub>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 21 Dec 2003 13:17:16 -0800
X-Trace: forums-1-dub 1072041436 10.22.241.41 (21 Dec 2003 13:17:16 -0800)
X-Original-Trace: 21 Dec 2003 13:17:16 -0800, 10.22.241.41
Lines: 82
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:2220
Article PK: 4426

thank you for your quick response.
Here is what I have:
ASA 9.0 9.0.0.1108 (evalulation copy) installed on Windows
2000 server 5.00.2195 service pack 3. The version of Sybase
Central is 4.2.0.2018.

I created a blank new database using Sybase Central and
executed the script I had posted in my earlier message. I
executed the script using ISQL...as before, the engine
disappeared and ISQL came back saying that the connection to
the database was closed.
I got the same result with the network server too.

As regards the migration, this is what happened. I tried to
open the 5.5.05 database with the new Sybase Central and
Sybase Central detected that it is a version 5 db and asked
me if i wanted to converted it to the new 9.0 version. It
asked me for where the new database should be created and
then it started unloading the old and loading the new
database. At the end of the process, I had a version 9.0
database with the data loaded and all procedures, functions
and views created - the 5.5.05 database was not altered,
instead a new equivlaent 9.0 database was created.

> Your example most definitely does NOT crash an ASA9
> engine. I got the result set 'Level 2', which is to be
> expected... I'm running 9.0.0.1227, with a .db file
> created with that version.
>
> I'm curious about your description of the migration
> process. It "automatically" performed this migration just
> by starting Sybase Central? That's a new one on me... I
> would expect you to have used the DBUNLOAD utility to
> unload the 5.5 file, DBINIT to create a fresh .db file in
> 9.0 format, and the ISQL utility to reload the
> data/structure into that ..db file. AFAIK, none of that
> happens just by starting SC4.2 on the old database.
>
> --
> Paul Horan[TeamSybase]
>
> <Thomas George> wrote in message
> > news:3fe4a23d.6be2.846930886@sybase.com... Hello,
> > I have an application that currently uses SQLA 5.5.05
> > and runs very well. I have been testing an evaluation
> > copy of ASA 9.0 for the purpose of upgrading my
> > database. My 5.5.05 database was automatically converted
> > to ver 9.0 when I tried to open it using the 9.0
> > SQLCentral tool. However, when I ran my application
> > against the converted datbase, the database engine
> > simply terminated (crashed) whenever certain queries
> > were executed. I did some analysis and found that one
> > such instance is when the database engine execute a case
> statement. Pls execute the following sequence on 9.0 and
> > it will most likey crash the engine:
> >
> >
> > create table employee (emp_id char(10), emp_level
> > smallint); insert employee values ('abc',1);
> > insert employee values ('xyz',2);
> >
> > //The interesting part follows
> > case (select max(emp_level) from employee)
> > when 1 then select 'Level 1'
> > when 2 then select 'Level 2'
> > when 3 then select 'Level 3'
> > end case;
> >
> >
> > Are there any other such SQL constructs that can cause
> > an abnormal shutdown of the ASA 9.0 engine? Will I have
> > to make several code changes to migrate to the ASA 9.0?
> > I hope not. Please advice on how I should proceed.
> > Thanks
> > Thomas
>
>


Robert Waywell Posted on 2003-12-22 14:38:33.0Z
From: "Robert Waywell" <nospam_rwaywell@ianywhere.com>
Newsgroups: ianywhere.public.general
References: <3fe4a23d.6be2.846930886@sybase.com><3fe529aa$1@forums-2-dub> <3fe60ddc.66a1.846930886@sybase.com>
Subject: Re: ASA 9.0 - abnormal shutdwon
Lines: 112
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2600.0000
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
NNTP-Posting-Host: rwaywell-pc.sybase.com
X-Original-NNTP-Posting-Host: rwaywell-pc.sybase.com
Message-ID: <3fe701e9$1@forums-1-dub>
Date: 22 Dec 2003 06:38:33 -0800
X-Trace: forums-1-dub 1072103913 172.31.142.236 (22 Dec 2003 06:38:33 -0800)
X-Original-Trace: 22 Dec 2003 06:38:33 -0800, rwaywell-pc.sybase.com
X-Authenticated-User: techsupp
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:2221
Article PK: 4427

So, since you can reproduce the problem in build 1108 and Paul can't
reproduce the problem using the more recent build 1227, you have
confirmation that this bug is already fixed in an EBF. As long as you have
registered for the free Developer Edition, then you should be able to
download and apply the EBF to verify the fix for yourself.

--
-----------------------------------------------
Robert Waywell
Sybase Adaptive Server Anywhere Developer - Version 8
Sybase Certified Professional

Sybase's iAnywhere Solutions

Please respond ONLY to newsgroup

EBF's and Patches: http://downloads.sybase.com
choose SQL Anywhere Studio >> change 'time frame' to all

To Submit Bug Reports: http://case-express.sybase.com/cx/cx.stm

SQL Anywhere Studio Supported Platforms and Support Status
http://my.sybase.com/detail?id=1002288

Whitepapers, TechDocs, and bug fixes are all available through the iAnywhere
Developer Community at www.ianywhere.com/developer

<Thomas George> wrote in message news:3fe60ddc.66a1.846930886@sybase.com...
> thank you for your quick response.
> Here is what I have:
> ASA 9.0 9.0.0.1108 (evalulation copy) installed on Windows
> 2000 server 5.00.2195 service pack 3. The version of Sybase
> Central is 4.2.0.2018.
>
> I created a blank new database using Sybase Central and
> executed the script I had posted in my earlier message. I
> executed the script using ISQL...as before, the engine
> disappeared and ISQL came back saying that the connection to
> the database was closed.
> I got the same result with the network server too.
>
> As regards the migration, this is what happened. I tried to
> open the 5.5.05 database with the new Sybase Central and
> Sybase Central detected that it is a version 5 db and asked
> me if i wanted to converted it to the new 9.0 version. It
> asked me for where the new database should be created and
> then it started unloading the old and loading the new
> database. At the end of the process, I had a version 9.0
> database with the data loaded and all procedures, functions
> and views created - the 5.5.05 database was not altered,
> instead a new equivlaent 9.0 database was created.
>
>
>
>
>
>
> > Your example most definitely does NOT crash an ASA9
> > engine. I got the result set 'Level 2', which is to be
> > expected... I'm running 9.0.0.1227, with a .db file
> > created with that version.
> >
> > I'm curious about your description of the migration
> > process. It "automatically" performed this migration just
> > by starting Sybase Central? That's a new one on me... I
> > would expect you to have used the DBUNLOAD utility to
> > unload the 5.5 file, DBINIT to create a fresh .db file in
> > 9.0 format, and the ISQL utility to reload the
> > data/structure into that ..db file. AFAIK, none of that
> > happens just by starting SC4.2 on the old database.
> >
> > --
> > Paul Horan[TeamSybase]
> >
> > <Thomas George> wrote in message
> > > news:3fe4a23d.6be2.846930886@sybase.com... Hello,
> > > I have an application that currently uses SQLA 5.5.05
> > > and runs very well. I have been testing an evaluation
> > > copy of ASA 9.0 for the purpose of upgrading my
> > > database. My 5.5.05 database was automatically converted
> > > to ver 9.0 when I tried to open it using the 9.0
> > > SQLCentral tool. However, when I ran my application
> > > against the converted datbase, the database engine
> > > simply terminated (crashed) whenever certain queries
> > > were executed. I did some analysis and found that one
> > > such instance is when the database engine execute a case
> > statement. Pls execute the following sequence on 9.0 and
> > > it will most likey crash the engine:
> > >
> > >
> > > create table employee (emp_id char(10), emp_level
> > > smallint); insert employee values ('abc',1);
> > > insert employee values ('xyz',2);
> > >
> > > //The interesting part follows
> > > case (select max(emp_level) from employee)
> > > when 1 then select 'Level 1'
> > > when 2 then select 'Level 2'
> > > when 3 then select 'Level 3'
> > > end case;
> > >
> > >
> > > Are there any other such SQL constructs that can cause
> > > an abnormal shutdown of the ASA 9.0 engine? Will I have
> > > to make several code changes to migrate to the ASA 9.0?
> > > I hope not. Please advice on how I should proceed.
> > > Thanks
> > > Thomas
> >
> >