on 2013 Jan 07 8:14 PM
I have a client who has software that uses a Sybase SQL Anywhere 6.0? database. He has sent the .db file to me. I have downloaded and installed the SQL Anywhere 10.0 Developer edition in an attempt to convert this db file to a 10.0 compliant file so that I can load it up into a server so that I can then test my MS Access application to the sybase database.
However, the problem is that when I click on the "Prepare a version 9 or earlier database for SQL Anywhere 10" and go through the wizard, I get an error message that states:
*SQL error: Unable to start database server: Server fatal error. The database....could not be unloaded The database....could not be unloaded
Am I missing something obvious?
Thanks in advance for any help anyone can provide.
There was a problem with trying to unload files from pre-v10 databases that needed recovery before they could be started by the engine used by v10, however this was fixed some time ago (in v10.0.1.3917). Is the v10.0.1 you are using later than that? If not, either apply the latest ebf to your engine or get your client to start and then stop the v6 db and then send you the .db and .log file. That should give you a clean start.
If you are using a later v10 engine, it would be still worth trying to start the db file you have under v6 just to make sure there is no issue with it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the response.
I have updated my Sybase Central to v10.0.1.4310 and I still get the same problem with the "Prepare a version 9 or earlier database for SQL Anywhere 10" command.
Unfortunately, I do not have v6 and from what I can tell, Sybase no longer offers this version for download. Do you know of a location?
Thanks!
I guess I should also confirm that I am headed in the right direction with this. I want to connect MS Access to the Sybase .db file so that I can use the data contained within. To do that I need to use ODBC. To do connect via ODBC the Sybase .db file needs to be running in a server? are these assumptions correct?
...actually, for development purposes I could simply import all the tables from the .db file into the MS Access. I dont need live connection for development purposes.
I don't think I can. A developer edition of v9 would do, but as you say that isn't available either.
Your client must have a v6 db engine if he is able to connect to the database - you can't connect except through a server.
Breck's question about how the copy of the db was made is very relevant. If the db is currently running, then a properly made online backup (or a copy of the db & log file when the dbengine is closed down) should start fine under Breck's process.
Not too obvious if one is used to a server-less DBMS (should I put that in quotes?) like MS Access...:)
Edit the following command file, and try it on your V6 *.db file. If it gives the same error, post the output *.txt files here...
REM If you're a command-line kinda guy, here is my template Windows REM batch file run_dbunload_upgrade_to_10.bat. It does the REM unload-reload-all-in-one-dbunload-step, then starts dbeng10 REM and dbisql so you can make sure the new database is up and running. REM Be sure to stop *all* database engines on the computer you're using, REM before starting the upgrade. REM Watch out for wrapped lines in the newsgroup display... REM dbunload... REM -an ... where to put new database REM -c ... old database startup connection string REM -o ... where to put unload console display text file REM -v verbose mode for console display PAUSE MAKE SURE YOU DO NOT HAVE ANY ENGINES RUNNING. "%SQLANY10%\\win32\\dbunload.exe" -an ddd10.db -c "DBF=ddd6.db;UID=dba;PWD=sql" -o dbunload_log_ddd6.txt -v PAUSE dbunload/reload done... REM dbeng10... REM -c ... initial RAM cache size REM -o ... where to put server console display text file REM -os ... when to rename and restart server console display text file REM -x none speed startup by disabling client protocols except shmem REM ddd10.db new database to start "%SQLANY10%\\win32\\dbspawn.exe" -f "%SQLANY10%\\win32\\dbeng10.exe" -o dbeng10_log_ddd10.txt ddd10.db PAUSE dbeng10 started... REM dbisql... REM -c ... new database connection string "%SQLANY10%\\win32\\dbisql.exe" -c "ENG=ddd10;DBN=ddd10;UID=dba;PWD=sql" PAUSE dbisql running...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Chances are the database file is unusable. You could try using Version 12 instead of 10, and if that has the same problem then you should call Tech Support http://www.sybase.com/contactus/support/
I have tried 10, 11, and 12 with no luck. At least through the sybase central. The client can connect just fine but he has v6 of the driver I believe. I dont think he has the full version as this is just a backend to another application he has. I currently am having him import into a MS Access database so that I can at least see the data structure and data.
Thanks for your help. If nothing else, I will need to contact sybase support. Do they monitor these forums?
How did the client create the copy of the *.db file? Did they stop the SQL Anywhere 6 server and make a file copy, or did they use some other technique? (other techniques sometimes result in bad copies).
I guess I am on my own with this one. Perhaps I will just abandon working with sybase and stick to SQL Server and MS Access. Thanks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
71 | |
11 | |
10 | |
10 | |
10 | |
8 | |
7 | |
7 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.