Hi everyone,
I need to do unload+reload of my remote DBs due to performance lack.
I read the old posts about this issue, so I had a look at ASA User's Guide
and tried the unload with -ar option as follows:
1- the remote DB is called "mydb.db"
2- I created under the same folder a new empty sub-folder called old_log
3- I opened a command prompt and wrote << dbunload -c
"uid=...;pwd=...;dbf=mydb.db" -ar old_log >>
4- the dbunload utility is then executed and 2 new files are created,
mydb.dbR and mydb.logR
5- execution stops without any error
6- now I find only one file mydb.db, while in the old_log sub-folder i find
mydb.log
7- at this point I manually shutdown the DB engine started by dbunload
8- I execute my application which restarts the DB engine
9- a new mydb.log file is created

When the application calls dbremote to synchronize with consolidated DB, the
following messages appear:
I. 11/04 14:05:05. Processing transaction logs from directory "./db/"
I. 11/04 14:05:05. Scanning logs starting at offset 0004885577
E. 11/04 14:05:05. No off-line transaction log file found and on-line
transaction log starts at offset 0004917134.
I. 11/04 14:05:05. We are looking for a transaction log file starting at
offset 0004885577.
I. 11/04 14:05:06. Execution completed

The guide tells that when using the dbunload -ar option there is no need to
manually adjust log offsets with the dblog utility.
Anyway I also had a second attempt with the same operations described above,
but adding this AFTER shutdown of the new DB and BEFORE executing the
application:
7- ...
7a- from the command prompt I wrote << dblog -x 0 -z N mydb.db >> where N is
the starting offset of the OLD mydb.log of the starting DB
8- ...

This second way had same results of the first one: the synchronization error
shown above.

I am using ASA 6.0.4 build 3594 on the remote db while the consolidated db
is ASE 12.5.

I would really appreciate any kind of help.

Thanks, Michele

[ Post a follow-up to this message ]

If files of type dbR and logR are created, that means that dbunload crashed
during the reload.  Those files are useless.

Can you try manually rebuilding the database and following the instructions
in the docs and see if that works?  I don't have the v604 docs handy, but
you can look in the index for a title similar to "rebuilding a consolidated
database involved in replication".

--
Reg Domaratzki, Sybase iAnywhere Solutions
Sybase Certified Professional - Sybase ASA Developer Version 8
Please reply only to the newsgroup

iAnywhere Developer Community : http://www.ianywhere.com/developer
iAnywhere Documentation : http://www.ianywhere.com/developer/product_manuals
ASA Patches and EBFs : http://downloads.sybase.com/swx/sdmain.stm
-> Choose SQL Anywhere Studio
-> Set "Platform Preview" and "Time Frame" to ALL

"Michele Phoenix" <michele.mazzucco@wuerth-phoenix.com> wrote in message
news:418a3340@forums-1-dub...
> Hi everyone,
> I need to do unload+reload of my remote DBs due to performance lack.
> I read the old posts about this issue, so I had a look at ASA User's Guide
> and tried the unload with -ar option as follows:
> 1- the remote DB is called "mydb.db"
> 2- I created under the same folder a new empty sub-folder called old_log
> 3- I opened a command prompt and wrote << dbunload -c
> "uid=...;pwd=...;dbf=mydb.db" -ar old_log >>
> 4- the dbunload utility is then executed and 2 new files are created,
> mydb.dbR and mydb.logR
> 5- execution stops without any error
> 6- now I find only one file mydb.db, while in the old_log sub-folder i
find
> mydb.log
> 7- at this point I manually shutdown the DB engine started by dbunload
> 8- I execute my application which restarts the DB engine
> 9- a new mydb.log file is created
>
> When the application calls dbremote to synchronize with consolidated DB,
the
> following messages appear:
> I. 11/04 14:05:05. Processing transaction logs from directory "./db/"
> I. 11/04 14:05:05. Scanning logs starting at offset 0004885577
> E. 11/04 14:05:05. No off-line transaction log file found and on-line
> transaction log starts at offset 0004917134.
> I. 11/04 14:05:05. We are looking for a transaction log file starting at
> offset 0004885577.
> I. 11/04 14:05:06. Execution completed
>
> The guide tells that when using the dbunload -ar option there is no need
to
> manually adjust log offsets with the dblog utility.
> Anyway I also had a second attempt with the same operations described
above,
> but adding this AFTER shutdown of the new DB and BEFORE executing the
> application:
> 7- ...
> 7a- from the command prompt I wrote << dblog -x 0 -z N mydb.db >> where N
is
> the starting offset of the OLD mydb.log of the starting DB
> 8- ...
>
> This second way had same results of the first one: the synchronization
error
> shown above.
>
> I am using ASA 6.0.4 build 3594 on the remote db while the consolidated db
> is ASE 12.5.
>
> I would really appreciate any kind of help.
>
> Thanks, Michele
>
>

[ Post a follow-up to this message ]

hi Reg,
yes manual rebuild as described in the ASA User's Guide works fine.
but what my bosses asked was to develop an utility that could automatically
do the unload/reload process so we could give it to our customers for their
slow remote DBs.
the problem is that using manual rebuild I need the dbtran to read the
offset of the LOG file.
I thought i could output dbtran to a txt file and then make my utility to
read inside it and automatically launch rebuild and dblog.
Anyway this doesn't look like a very clean solution.
That's why I was trying to use the -ar option.
But if you could have any hint on how to obtain the LOG offset from code,
then it would be ok for me.

TIA, Michele

"Reg Domaratzki (iAnywhere Solutions)" <Spam_bad_rdomarat@ianywhere.com>
wrote in message news:418a3b33$1@forums-1-dub...
> If files of type dbR and logR are created, that means that dbunload
crashed
> during the reload.  Those files are useless.
>
> Can you try manually rebuilding the database and following the
instructions
> in the docs and see if that works?  I don't have the v604 docs handy, but
> you can look in the index for a title similar to "rebuilding a
consolidated
> database involved in replication".
>
> --
> Reg Domaratzki, Sybase iAnywhere Solutions
> Sybase Certified Professional - Sybase ASA Developer Version 8
> Please reply only to the newsgroup
>
> iAnywhere Developer Community : http://www.ianywhere.com/developer
> iAnywhere Documentation :
http://www.ianywhere.com/developer/product_manuals
> ASA Patches and EBFs : http://downloads.sybase.com/swx/sdmain.stm
>    -> Choose SQL Anywhere Studio
>    -> Set "Platform Preview" and "Time Frame" to ALL

[ Post a follow-up to this message ]