I'm trying to unload a very old Sybase database in order to use it
with the new version 11 but I'm running into a quagmire of SQL errors:

Using unload.exe (version 11.0.1) I receive the following error:
Not the most helpful message... It won't even let me unload the
database schema alone. I naturally tried to use some older versions
of dbunload on the file and received the following results:

Using unload.exe (version 9.0.2) I receive:
Using unload.exe (version 7.0.1) I receive:
***** SQL error: User ID 'dbo' does not exist

I'm out of ideas on how to proceed. Does anyone have any
suggestions? Is anyone familiar with this problem? Any suggestions
would be greatly appreciated.

Thanks,

Mike

Can you be specific about the age of this database? Do you know the version and build?

--
Joshua Savill
Sybase Inc. - Product Manager


Jonesy wrote:

Josh,

Thanks for the reply.

This is a legacy system so I don't have knowledge of which build was
used to create the DB. I know it was <= 5.0 because Sybase Central
spits out an error to that extent when attempting to open the DB. The
'database_version' field of the 'SYSINFO' table is set to '10', I
dunno if that helps. Is there another way to extract the version?

Thanks in advance,

Mike

On Aug 11, 1:05*pm, "Josh Savill [Sybase]"
<no_spam_jsavill_no_s... (AT) sybase (DOT) com> wrote:

Normally, the current version of dbunload should be used to unload a database; however, in this case
I would recommend using an older version.

I'm a bit surprised version 9.0.2 did not work. Make sure you are using a current 9.0.2 build,
and do the rebuild as separate steps. If necessary, you could try connecting to the database using a 9.0.2 server
and execute:
set option PUBLIC.Non_keywords=''
then try the unload again.

SQL Anywhere Developer Community:
http://www.sybase.com/developer/libr...ere-techcorner


SQL Anywhere Blog Center: http://www.sybase.com/sqlanyblogs




Jonesy wrote:

I concur with Bruce about it being strange that V9 did not
handle this but since your database is an early V4.0 data store,
maybe you should use the V9 DBUPGRAD.exe utility to
see if that cleans up any ancient history.

I found and older V4 database (only slightly newer than
yours) and once I ran dbupgrade I got past the two errors
you were seeing.

In short do these 3 steps in this order:
1 - V9.0.2 dbupgrad -c "UID=....;DBF=<olddb.db>"
2 - V9.0.2 dbunload -ar -c "UID=....;DBF=<olddb.db>"
3 - V11.0.x dbunload -ar -c ....

and you should be good for the meta-structure problems
you are hitting. You may not even need to do step #2
(untested) going straight to step #3.

CAVEAT: databases that old may have some undetected
corruption in them which can cause steps #2 and #3 to
fail. If you hit a problem of that kind then, doing step #2
as a manual rebuild will be required.

Best of luck



[incidentally the dbo account did not exist until 5.0 and the
non_keywords option was around that same time frame]
"Bruce Hay" <h_a_y_@_i_a_n_y_w_h_e_r_e_d_o_t_c_o_m> wrote

Bruce,

After executing your suggested 'SET' statement, the unload on version
9 worked.

Thanks a million,

Mike

On Aug 11, 4:02*pm, Bruce Hay <h_a_y_@_i_a_n_y_w_h_e_r_e_d_o_t_c_o_m>
wrote: