SQL Anywhere 5 DB to migrate to newer version.

[Former Member]

I have some version 5 DB that I'm trying to upgrade to a newer version...but seems like the documents suggest that you need to use SQL Anywhere 9 in order to do so. However that version is no longer available from what I see. The DB use "integrated login" if that makes any difference.

--Michael

[MarkCulp]

Note that since version 10 there is a (restricted) version 9 database engine embedded in the installation that is used to migrate the data from the old database to the new version.

Essentially you need to rebuild your database so that the data is in database that uses the "new" database format (as of version 10).

Please take a look at the Upgrading SQL Anywhere in the documentation for detailed information on how to upgrade from versions prior to v10.

[Former Member]

Thank you for the comments. Now that I look at it more it could be my problem has less to do with migrating the data and more to do with not being about to login to the old DB via "integrated login".

C:UsersMichael Peterson>dbunload -v -c "INTEGRATED=yes;DBF=C:UsersMichael Pe tersonDesktop*.db" -r "C:UsersMICHAE~1AppDataLocalTempreload. sql" -ii "C:UsersMICHAE~1AppDataLocalTempunload Adaptive Server Anywhere Unload Utility Version 9.0.2.2451 *** SQL error: Integrated logins are not permitted

I've tried something similar with an old copy of Sybase V9...but it's giving me:

"Could no connect to database.

Integrated logins are not permitted

The data source you specified is configured to use your Windows userid to connect to the database. This is not supported. Select a data source that does not use integrated logins and try again."

Seems like it's telling me contradictory information. Sorry if the initial question was misleading but as I work with this I'm learning more about it.

--Michael

[VolkerBarth]

Well, I don't see a contradiction: You try to connect with an integrated login, and the database tells you that this is not supported. So you will need to specify explicit database credentials, i.e. a username and password. - You might change the according part of your command line to something like:

... -c "DBF=C:\\Users\\Michael PetersonDesktop.db;UID=dba;PWD=sql" ...

[Former Member]

One of the error messages I was getting above was:

"The data source you specified is configured to use your Windows userid to connect to the database."

[VolkerBarth]

Hm, that would mean a DSN connection parameter - and I don't see one in your command line - or is the SQLCONNECT environment variable used (whose contents will be added to the command line)?

Cf. "SET SQLCONNECT" in a CMD window...

[Former Member]

Maybe I'm confuse...well...that's a given at this point.

DSN connection parameter...from what I've seen it's used when connecting via ODBC driver. Does dbunload require/want/desire that?

BTW...this is a DB file I was given to try and extract the contents of. The only SQL Anywhere environments I have available to me are ones I've installed since getting this file. I have a SA9 ans SA12 both around to try and upgrade this to something newer.

[VolkerBarth]

Well, let's assume the message is right, and the database is not configured to allow integrated login (which can be configured inside the database from a DBA). Then surely you will need database credentials, i.e. a valid user name and password. These may be stored inside an ODBC DSN, an ODBC File DSN, or must be specified manually. - If you have those, add them as suggested in one of my comments above.

---

What you have tried so far, is attempting to connect with integrated login, and that just does not fit to this particular database...