SQL Anywhere Mobile - Oracle Sync Error: Unable to fetch the download timestamp

Author

Oracle Sync Error: Unable to fetch the download timestamp

Aaron Reicher

2005-03-30, 9:42 am

We just upgraded to ASA 9.02 with EBF 3044 and are now running into an error
during the download while trying to do an initial synchronization against an
Oracle 8i database (8.1.7).

There is only a warning (no error) in the ML server log:
Warning: [10074] Unable to fetch the download timestamp from the
consolidated database.

However, we are getting an error on the client; in the dbmlsync verbose
client log, we are getting the error:
Download did not contain next last download timestamp.

This was working smoothly with Oracle with ASA 9.01.1922 client and ML
server with the same synchronization scripts. It is still working well
against our ASA 9.02 consolidated database.

One thing that looks like it could be related is a case from the EBF
documentation (Build #3021 - Engineering Case #377900). It appears there
were some changes in the Oracle timestamp-based downlads. We have read this
information and verified that the the user has select privileges on the
v_$transaction view (not granted via a role). The synonym for this
(v$transaction) also appears accessible.

We can't find any documentation in the 9.02 docs about the 10074 warning,
nor do we see anything similar in the newsgroup . Does anyone have any
ideas?

Thanks!
Aaron

Aaron Reicher

2005-03-30, 9:42 am

A little follow-up info. We found this statement in the ML server log file
right before the warning:
SELECT NVL( MIN( TO_TIMESTAMP( START_TIME, 'mm/dd/rr hh24:mi:ss' ) ),
localtimestamp ) FROM v$transaction

Mobilink is using this to get the next last download date that takes open
transactions into account (to avoid missing downloading uncommitted
transactions). However, this syntax fails because we're using Oracle 8i and
this is Oracle 9 syntax. The 8 syntax should be (something like):
SELECT NVL( MIN( TO_DATE( START_TIME, 'mm/dd/rr hh24:mi:ss' ) ), sysdate )
FROM v$transaction

We tried getting Mobilink to use the alternate syntax instead by using the
modify_next_last_dow
nload_timestamp connection event, but this was not
firing before the error occured.

We tried rolling back to the previous EBF (2551) and everything works fine.

It anyone knows a way to make this work correctly, it would be helpful. We
moved to this EBF because of a different issue that was addressed and would
like to continue using it if possible.

Thanks,
Aaron

"Aaron Reicher" < no_reply_by_email@di
ginsp.com> wrote in message
news:422e306f$1@foru
ms-2-dub...
> We just upgraded to ASA 9.02 with EBF 3044 and are now running into an
> error during the download while trying to do an initial synchronization
> against an Oracle 8i database (8.1.7).
>
> There is only a warning (no error) in the ML server log:
> Warning: [10074] Unable to fetch the download timestamp from the
> consolidated database.
>
> However, we are getting an error on the client; in the dbmlsync verbose
> client log, we are getting the error:
> Download did not contain next last download timestamp.
>
> This was working smoothly with Oracle with ASA 9.01.1922 client and ML
> server with the same synchronization scripts. It is still working well
> against our ASA 9.02 consolidated database.
>
> One thing that looks like it could be related is a case from the EBF
> documentation (Build #3021 - Engineering Case #377900). It appears there
> were some changes in the Oracle timestamp-based downlads. We have read
> this information and verified that the the user has select privileges on
> the v_$transaction view (not granted via a role). The synonym for this
> (v$transaction) also appears accessible.
>
> We can't find any documentation in the 9.02 docs about the 10074 warning,
> nor do we see anything similar in the newsgroup . Does anyone have any
> ideas?
>
> Thanks!
> Aaron
>
>

Graham Hurst

2005-03-30, 9:43 am

Thanks for reporting this. You're right, we're issuing the wrong
statement for Oracle 8i. I can't think of a way to suppress that other
than removing permission for v_$transaction.

Cheers,

Graham

Aaron Reicher wrote:
> A little follow-up info. We found this statement in the ML server log file
> right before the warning:
> SELECT NVL( MIN( TO_TIMESTAMP( START_TIME, 'mm/dd/rr hh24:mi:ss' ) ),
> localtimestamp ) FROM v$transaction
>
> Mobilink is using this to get the next last download date that takes open
> transactions into account (to avoid missing downloading uncommitted
> transactions). However, this syntax fails because we're using Oracle 8i and
> this is Oracle 9 syntax. The 8 syntax should be (something like):
> SELECT NVL( MIN( TO_DATE( START_TIME, 'mm/dd/rr hh24:mi:ss' ) ), sysdate )
> FROM v$transaction
>
> We tried getting Mobilink to use the alternate syntax instead by using the
> modify_next_last_dow
nload_timestamp connection event, but this was not
> firing before the error occured.
>
> We tried rolling back to the previous EBF (2551) and everything works fine.
>
> It anyone knows a way to make this work correctly, it would be helpful. We
> moved to this EBF because of a different issue that was addressed and would
> like to continue using it if possible.
>
> Thanks,
> Aaron

Graham Hurst

2005-03-30, 9:43 am

FYI, this has been fixed, as of build 9.0.2.3097.

Cheers,

Graham

Breck Carter [TeamSybase]

2005-03-30, 9:43 am

That took *more than two hours*, what did you do, break for lunch?
<gr&d>

On 10 Mar 2005 13:21:54 -0800, Graham Hurst
< spam_guard_hurst@ian
ywhere.com> wrote:

>FYI, this has been fixed, as of build 9.0.2.3097.
>
>Cheers,
>
>Graham

--
SQL Anywhere Studio 9 Developer's Guide
Buy the book: http://www.amazon.com/exec/obidos/A...7/risingroad-20
bcarter@risingroad.com
RisingRoad SQL Anywhere and MobiLink Professional Services
www.risingroad.com

Sponsored Links