I am running dbunload with the following options:
dbunload - c "uid..." -y -ar c:\unloaddir

After the unload is complete, the log file is out of sync. Should I just
delete the log file at this point? The database is not involved in
replication. SQL Anywhere 9 ebf 1235.

Jim

Do not use the dbunload -ac, -an or -ar options. They cause more
problems than they are worth and IMO should be removed from the
product. Use separate dbunload, dbinit and dbisql reload steps.

Breck

On 15 Dec 2003 10:39:50 -0800, "Jim Cullison"
<c_u_l_l_i_s_o_n_j (AT) p_o_s_i_m_ (DOT) _c_o_m> wrote:

--
bcarter (AT) risingroad (DOT) com
Mobile and Distributed Enterprise Database Applications
www.risingroad.com

Hey, you read my mind! I am now getting dbtool.dll access violations in
testing converting larger databases, and I can see that in ebf 1250 they
fixed quite a few bugs in dbunload.

The actual problem is that there is a duplicate procedure
"dbo.sa_get_server_messages" which of course causes an error. Somehow this
procedure is getting into the reload.sql, but already exists in the newly
created database.

Jim

"Breck Carter [TeamSybase]" <NOSPAM__bcarter (AT) risingroad (DOT) com> wrote in
message news:iu6stvge1or4sommh4ee2vkult1016alel (AT) 4ax (DOT) com...

If you continue to see the access violation issue after going to
ASA9.0.0.1250, could you consider submiting the database so that the problem
could be investigated.

The dbo.sa_get_server_messages duplication is the result of some problem
introduced when the database was created. This problem has not be reproduced
inhouse nor are we able to determine how the problem was introduced. If you
know the specific histroy of the database i.e., version and build that the
database was initialized, if the database was upgraded/rebuild from another
version, etc, it may help us to isolate the problem.

As a workaround, use the EXCLUDEOBJECT table to exclude items in the UNLOAD
process. For example,

insert into EXCLUDEOBJECT values( 'sa_get_server_messages',
'P' )

--

Chris Keating
Sybase Adaptive Server Anywhere Professional Version 8

************************************************** **************************
*
Sign up today for your copy of the SQL Anywhere Studio 9 Developer Edition
and try out the market-leading database for mobile, embedded and small to
medium sized business environments for free!

http://www.ianywhere.com/promos/deved/index.html

************************************************** **************************
*

iAnywhere Solutions http://www.iAnywhere.com

** Please only post to the newsgroup

** Whitepapers can be found at http://www.iAnywhere.com/developer
** EBFs can be found at http://downloads.sybase.com/swx/sdmain.stm
** Use CaseXpress to report bugs http://casexpress.sybase.com

************************************************** **************************
*

"Jim Cullison" <c_u_l_l_i_s_o_n_j (AT) p_o_s_i_m_ (DOT) _c_o_m> wrote

EBF 1250 does not fix this problem.

Should I be running ALTER DATABASE UPGRADE before doing the unload/rebuild
steps? That might be where the duplicate sa_get_server_messages is coming
from.

I am no longer going to try to use the dbunload -ar option on the unload.
Instead, as Breck suggested, I am running dbunload, dbinit, then dbisql.
The benefit of splitting it up is that if it does have an error in ISQL, I
get decent information about the error, and can have a user continue on if
desired. dbunload seems to have a nagging problem of crashing when it gets
sql errors like 'Procedure already exists' (based on browsing the bugs that
have been fixed in it recently).

As far as submitting the database, it is our own database we run in house
and I'll check if I can do it.

Jim

"Chris Keating (iAnywhere Solutions)" <FightSpam_keating (AT) iAnywhere (DOT) com>
wrote in message news:3fdf1c69 (AT) forums-1-dub (DOT) ..

You should be able to just drop the procedure before running dbunload. I
suspect the procedure was added by dbconsole.exe. The procedure did not
exist in ASA 6, but was required by dbconsole; unfortunately, the way it was
added resulted in the dbunload failure (duplicate procedure). The procedure
is now created when you initialize a new database.

Whitepapers, TechDocs, bug fixes are all available through the iAnywhere
Developer Community at http://www.ianywhere.com/developer

"Jim Cullison" <c_u_l_l_i_s_o_n_j (AT) p_o_s_i_m_ (DOT) _n_e_t> wrote