Hello,

We've been a Sybase user since ASA 6.0 and have many clients -- This is the
first time I've been so annoyed and frustrated with Sybase, because I've
spent close to 6 hours on this issue, and I'm getting on a plane to do a
demo tomorrow and work on a project and I've gotten absolutely nowhere -
maybe this is from my own stupidity of loading Windows 7-RC1 instead of just
keeping my laptop on Vista.

We heavily use Sybase SQL Anywhere 9.02 (hundreds of installations) ...
it's worked fine all the time.

I installed Windows 7 RC1 on my laptop and Sybase 9.02 will not run Sybase
Central or start the database. It gives a JAVA Exception error. I've
loaded the latest release of JAVA and this laptop was formatted and just put
JAVA, Firefox and Sybase 9.02 on it.

Anyway ... after 2 hours of messing around with that...I gave up! I then
when to our subscribe net and generated the license for Sybase SQL Anywhere
11, which Sybase has been asking us to use but we've been very comfortable
in 9.02 land until now so we might as well be ready for Windows 7.

So, I completely uninstalled 9.02 from my laptop, deleted every trace of it,
rebooted. I then downloaded and installed ASA 11 and did all the updates
(EBF) to 11.0.1.2052 with our newly generated license.

Now, I can't get my database to run whatsoever under V11! I tried running
it, it won't run. So, you look at the help and it gives specific
instructions on how to convert a 9.x database using UNLOAD which I did to
the letter, and it always comes up with the following: (Using Unload and
Reload into a new database)

**** SQL error: Unable to start specified database: autostarting database
failed
An error occurred while attempting to unload the database c:\roommaster.db

.....

So I went back to my V9.02 server at work, verified the database and
upgraded it making sure it was completely fine. I then took the DB and LOG
files and try an unload again, no dice - same exact error.

I then created a new empty database, and tried using ISQL to bring the data
in from an unloaded "SQL" statement, and it's error after error about
authentication violations on the user levels.

We have well over 150 customers now to convert to V11 from V9.02, and we
can't have this type of hoops and issues. It needs to be smooth....and
unloading and reloading a database is fine for them, but what's the deal?

Can I send this database to Sybase to look at and see why it won't work
under V11? I really need this by 11AM EST on Monday (I know, I'm pretty
much screwed -- my fault, I should have just left Vista on my machine - but
what can I say)

1. We need Sybase to make sure 9.02 works on Windows 7
2. I need this database convertible to V11 along with our 150+ other
customers someday - but this one test one needs to work first.

Please help me out ... I really need some answers fast.

Thank you!!

-Robert

Hello,

What are my options on this? I can't release passwords to this database or
migrate/change passwords, as they are highly sensitive and very sensitive
data. We can't have support editing SQL files.

I surely can't go to V10 and then to V11 ...

It's best if we just stay forever on V9.02 but with WIN7 coming out, we
can't do that ... unless Sybase is aware of the issue of V9.02 running
properly under WIN7.

Please help ASAP.

-Robert

Hello,

I think my issue has to do with trying to run a developer beta test database
using the authentication license copy I downloaded from subscribenet. The
one developer database I trying to start is not an authenticated one ...
could that be the issue?

-Robert

"Robert Paresi" <firstinitiallastname (AT) company (DOT) com> wrote

Robert,

You cannot run a version 9 database under version 11. I have had to use ASA
10 to first convert the database to the new format. I haven't tried but you
might have to do a unload in ASA 9 and reload using ASA 11.

Best Regards

Michael Gould


"Robert Paresi" <firstinitiallastname (AT) company (DOT) com> wrote

Mike,

That is what I did (unload and reload using ASA 11) --- it fails and says it
can't unload it.

-Robert

"Michael Gould" <mgould (AT) firstcoast (DOT) net> wrote

Hello,

In the final hour - before getting on the plane - I got it working somehow.
I uninstalled my license and loaded a trial license. I still was unable to
convert the database using a simply UNLOAD/RELOAD in Version 11.01 like I
should be able to. I had to unload the database in V9.02 into reload
statement, create a new database, create all the user profiles, and then run
the reload.sql statement in ISQL.

This is fine for me, but not fine for our support department to do this to
150 sites. We'll also not have their passwords and we don't want to have
to recreate end-user passwords.

Can someone at Sybase take our 9.02 database and find the reason why a
V11.01 UNLOAD/RELOAD does not work and try and fix the problem in an updated
EBF please? How can I do that? We would need an NDA signed first.

Thank you.

-Robert


"Robert Paresi" <firstinitiallastname (AT) company (DOT) com> wrote

Robert,

When Sybase 10 came out they were very clear that you would have to convert
the db. In version 10 there was a routine in Sybase Central that would do
that. I believe it was removed in Sybase 11. When I converted our ASA 9 to
10 we didn't have to manually do anything. We unloaded using 9 and then
created a 10 db and everything was converted over. If you look at the
reload file that comes out of 9, were the userid's not in that file?

Best Regards

Mike Gould

"Robert Paresi" <firstinitiallastname (AT) company (DOT) com> wrote

Please feel free to open a technical support case and work with support
to identify/resolve the problems you have encountered.

-chris


Robert Paresi wrote:

There was significant effort put in to make the move to SA10 (the
version that introduced the file format change) - and newer versions -
as free of issues as possible.

You should not upgrade the java that ships with SQL Anywhere and used by
the java tools. These tools were only tested with the java version that
shipped. Other installed java versions would not be used by the tools so
upgrading those would not impact SQL Anywhere.

The database must have the database_authentication option set before
running on an OEM (aka Authenticated) engine. This makes the database
authenticated. If you are upgrading or rebuilding the database, the
authenticate.sql file containing that option is used to create an
authenticated database. Details of this is discussed in the SA11
documentation referenced below

SQL Anywhere Server - Database Administration
» Starting and Connecting to Your Database
» Running the database server
» Running authenticated SQL Anywhere applications
» Developing an authenticated application

or in the Read Me First Authenticated Edition file on the SA9 OEM
edition install image.

This could happen if the database needs to go into an automatic recovery
at startup. Can you describe the process used to get the source database
used in this process. For example, a database from a backup may be
marked as needing recovery.


Robert Paresi wrote:

SA11 continues to have the upgrade wizard for versions prior to SA10.


Michael Gould wrote: