cancel
Showing results for 
Search instead for 
Did you mean: 

Please help ... DBUNLOAD not working

Former Member
0 Kudos

We just have a heck of a time with WIN2003 and a certain error.

This message appearing during DBUNLOAD from the DOS prompt or run from our application:

The database server was unable to start the database since the database version is newer than the server version. The server must be upgraded to at least the version of the database to be able to start the database.

We have checked everything!

1. We are sure no other version or objects of SQL Anywhere exists on the computer

2. We have run this directly from the SQL Anywhere\bin32 directory

If we run DBunload, it says it can't do this because of a newer version.  The system has only been installed on this WIN2003 Server for a week!   Nothing else is on it, there is no SQL Anywhere version other than 3867,   It is also coming from a 3867 Deployment Wizard.

If I use DBENG12 or DBSRV12 ---- the database starts up without an issue!   If I start it under SCJVIEW, the database starts without an issue!   But, if I start it using DBUNLOAD, I get this message.  

It only happens on WIN2003 and we've seen this on multiple WIN2003 boxes.

I know dbeng, dbsrv, scjview and dbunload are all part of 3867,   The database is a V12 database. 

We've uninstalled, reinstalled and rebooted the server.,  Same error.   I know no other objects are in the path incorrectly because I am running it directly from the bin32 directory DOS prompt.

This works just fine on any other box but WIN2003.

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hello,

Could you please tell me as we use both Sybase SQL Anywhere versions 9 and Sybase SQL Anywhere 12.

Is the SERVER= compatible/able to be used on DBUNLOAD.EXE for Sybase SQL Anywhere 9?

jeff_albion
Employee
Employee
0 Kudos

Is the SERVER= compatible/able to be used on DBUNLOAD.EXE for Sybase SQL Anywhere 9?

No, ENG= or "EngineName=" is used instead, which is deprecated in SQL Anywhere 12.

Jeff Albion

SAP Active Global Support

jeff_albion
Employee
Employee
0 Kudos

Hi Robert,

Do you have a SQL Anywhere database server already locally running when you're trying the dbunload command? What is the exact dbunload command that you are trying - are you trying to auto-start the database (dbunload -c "DBF=") at the same time? If that's true, it's likely that you're implicitly trying to start the version 12 database on the existing database server already running, thus getting the error message.

If you're trying to auto-start the database (DBF) from dbunload, be sure to always add a "SERVER" and "DBN" argument to the connection string to ensure you're starting a unique version 12 database server:

dbunload -c "uid=dba;pwd=sql;server=unloadserver;dbn=unloaddatabase;dbf=database.db"

You can also add a START parameter to point to dbsrv12/dbeng12 explicitly:

dbunload -c "uid=dba;pwd=sql;server=unloadserver;dbn=unloaddatabase;dbf=database.db;start=dbsrv12"

Regards,

Jeff Albion

SAP Active Global Support

jose_at_sap
Advisor
Advisor
0 Kudos

Hello Robert - do you have another version of SQL Anywhere installed on that same machine?  It looks like dbunload may be from an earlier version - can you please verify the executable version of dbunload.exe?

Former Member
0 Kudos

No - I am sure of it.

The reason being that I open up a DOS window and I physically go to the SQL Anywhere 12\bin32 directory and run it there.  So, every object that it finds would definitely be coming from THIS directory and not any other directory.   So, that would be impossible.

I have looked at the properties of dbsrv12 and dbeng12 and dbunload --- and all of them says 12.0.1.3867

They are ALL the same version.

I did this from root directory of C: 😧 E: and F: and it only appears ONCE!  My application.  Dated 3/5/13 @ 10:48PM.

dir dbeng*.* /s 

There is no other database running on this network - and as stated, these databases start up without issue using DBENG12, DBSRV12 as well as SCJVIEW.

The only time it does not run is when using DBUNLOAD.

I am not using the restart parameter either.  So, no, I am not starting up the database afterwards.   The error is actually happen immediately when the dbunload is run.

This is happening on multiple WIN2003 boxes - not just this one!

Former Member
0 Kudos

UPDATE!


SUCCESS!

All I did was add "server=dbunloadserver"

and now it works!!!!!!!