Hi,

I managed to do a UNLOAD to script. I edited the script and changed all
FORMAT TEXT to FORMAT ASCII. I removed a few lines as well as all the lines
which says SA_UNLOAD_DISPLAY_TABLE_STATUS.

I then ran the scripts over shell V9.02 databases (one internal one
external) ... ran the process (took 2 hours).

Now, started up both databases and all issues have completely disappeared.
Screens are like lightning fast and Processes no longer remain after the
connection disconnects. All our screens are faster than sub-second
response.

Sorry for the frustration yesterday. All is back to normal and we are back
to using 9.02 for both databases. Now we just have to run the process over
one customer in the U.K. who we put on V11 so far, but we'll bring them back
to the 9.02 like all our other customers.

Thanks.

-Robert

Very good, I am very pleased to learn that your back-out to version 9
was successful.

That said I am obviously still keenly interested in determining what
your problems were with v11 so that you can migrate to version 11 (or
later), with confidence, at some point in the future.

Myself and my team will be happy to work with you to determine what
these problems were, and how we can overcome them.

Glenn

Robert Paresi wrote:
--
Glenn Paulley
Director, Engineering (Query Processing)
Sybase iAnywhere

Blog: http://iablog.sybase.com/paulley

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

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
Sybase iAnywhere pages at
http://www.sybase.com/products/datab...chnicalsupport

Hello,

It's frustrating but at the same time, very time consuming and costly for me
to work at fixing these issues. Work on this takes away from other
projects and makes it costly for us - especially since we believe we pay a
premier to use Sybase products over alternatives.

There are at least three issues we are having, and to be honest, I have to
have the confidence that all three issues can be resolved before I spend the
time and resources to resolve each issue one at a time.

I don't plan on working on this until January ... maybe wait for a bunch
more EBF's to come out where you may find some of the issues, and then I
have to setup a box to recreate these issues outside of production
environments because of the impact that this had on us over a very short
time was too much for me.

To be frank, this was not an issue with fragmentation of the database --- I
simply reloaded the data as primary key and the slowness was immediate going
to Version 11. All I did was bring the database back down to V9 with a
hacked Unload/Reload and all things went back to normal immediately. The
staff is happy today. I don't want to put them through this again.

So, in January ... I will get a dedicated box, go through recreating the
entire environment again for both products/databases and then recreating the
issues. At that point, I will work with my Sybase representative (Tom) to
have someone hopefully log in, see the issues and help resolve them with a
dedicated box.

-Robert

"Glenn Paulley [Sybase iAnywhere]" <paulley (AT) ianywhere (DOT) com> wrote