Having installed the update to SQL Anywhere 184.108.40.2069, I notice a difference in unloading a database. Up to version 220.127.116.116, I was able to execute the dbunload statement in the Summary page of the Unload Database Wizard directly by pressing the Finish Button. After the update, I get the attached error.
The dbunload statement looks like: dbunload -v -c "UID= testdatabase;PWD=***;Server=skyserver;DBN= Testdatabase;ASTART=No;host=10.0.1.2:2638" -an "/Users/admin/Desktop/Testdatabase.db" -ap 4096 -ea None -kdi 0 -ii -up
If I execute the very same statement in the terminal AND put at PWD= the password in clear instead of the ***, it works. As I think we have not changed the server environment (may be except an update of Java), I am wondering if there is a change in SQL Central?
Best regards, Robert
The generation of the unprocessed.sql file hasn't changed AFAIK. unprocessed.sql will go into the 'current directory'. Perhaps the current directory for your invocation of SQL Central is a location where you do not have write permission?
answered 21 Oct '16, 10:12