同步到生产 Oracle DB 选项时出现 Mobilink 错误

发布于 2024-08-13 10:39:21 字数 1856 浏览 5 评论 0原文

好的,这是场景。我们有两个开发人员使用 Mobilink 开发人员版本可同步到整合的 Oracle 数据库使用SqlAnywhere。 mobilink 版本是版本 11.0.1.2331

在两个开发环境中一切正常。
一种开发环境是 Windows 7 x64 和 Oracle 11g r1。另一个是xp x86 和 Oracle 10gr2。两者都工作正常并且正在与副本同步 生产数据库(从生产服务器获取转储文件)。 我们现在处于测试状态,正在尝试设置 同步并且一直失败。 beta环境正在使用 “SQL Anywhere MobiLink 服务器版本 11.0.1.2044”并且正在运行 Windows 2003 x64。查看 PDA 和服务器上的错误日志 确认用户已通过身份验证并且 同步正在开始,但每次都会在同一点中断 时间。以下是日志中的一些其他详细信息。

一、2009-12-04 13:30:38。 <1> end_download_rows G_INV_LOCATION_DESC(无 脚本)

一、2009-12-04 13:30:38。 <1> begin_download_deletes G_COMMENT_INFO(无 脚本)

一、2009-12-04 13:30:38。 <1> download_delete_cursor G_COMMENT_INFO

                    --{ml_ignore} 

一、2009-12-04 13:30:38。 <1>翻译后的 SQL:

E.2009-12-04 13:30:38。 <1> [-10002] Consolidated 数据库服务器或

ODBC 错误:ODBC:[Sybase][iAnywhere Solutions - Oracle][Oracle]

ORA-00900:无效的 SQL 语句

                     (ODBC State = 42000, Native error code = 900) 

I. 2009-12-04 13:30:38。 <1>错误上下文:

I.2009-12-04 13:30:38。 <1>远程 ID:62e3d800-e09d-11de-8000- fb73ff3a8e87

一、2009-12-04 13:30:38。 <1>用户名:bogus_user 一、2009-12-04 13:30:38。 <1>修改后的用户名:bogus_user 一、2009-12-04 13:30:38。 <1>交易:下载 一、2009-12-04 13:30:38。 <1>表名称:G_COMMENT_INFO 一、2009-12-04 13:30:38。 <1>脚本版本:bogus_user_scan

I.2009-12-04 13:30:38。 <1>脚本:

                    --{ml_ignore} 

I.2009-12-04 13:30:38。 <1>错误上下文结束

I. 2009-12-04 13:30:38。 <1>报告错误(无脚本) 一、2009-12-04 13:30:38。 <1> report_odbc_error(无脚本)

我还在此处发布了此问题

Ok so here is the scenario. We have two developers using the
developer edition of Mobilink to sync to a consolidated Oracle
DataBase using SqlAnywhere.
The mobilink Version is Version 11.0.1.2331

Everything works fine in the two development environments.
One dev environment is Windows 7 x64 and Oracle 11g r1. The other is xp x86
and Oracle 10gr2. Both work fine and are syncing with a replica of
the production database(took a dump file from the production server).
We are now in a beta state and are trying to set up the
synchronization and it keeps failing. The beta environment is using
"SQL Anywhere MobiLink Server Version 11.0.1.2044" and is running on
Windows 2003 x64. Looking at the error log on the PDA and the Server
confirms that the user is getting authenticated and that the
synchronization is starting but it breaks at the same point each
time. Below are some additional details from the log.

I. 2009-12-04 13:30:38. <1> end_download_rows G_INV_LOCATION_DESC (no
script)

I. 2009-12-04 13:30:38. <1> begin_download_deletes G_COMMENT_INFO (no
script)

I. 2009-12-04 13:30:38. <1> download_delete_cursor G_COMMENT_INFO

                    --{ml_ignore} 

I. 2009-12-04 13:30:38. <1> Translated SQL:

E. 2009-12-04 13:30:38. <1> [-10002] Consolidated database server or

ODBC error: ODBC: [Sybase][iAnywhere Solutions - Oracle][Oracle]

ORA-00900: invalid SQL statement

                     (ODBC State = 42000, Native error code = 900) 

I. 2009-12-04 13:30:38. <1> Error Context:

I. 2009-12-04 13:30:38. <1> Remote ID: 62e3d800-e09d-11de-8000-
fb73ff3a8e87

I. 2009-12-04 13:30:38. <1> User Name: bogus_user
I. 2009-12-04 13:30:38. <1> Modified User Name: bogus_user
I. 2009-12-04 13:30:38. <1> Transaction: download
I. 2009-12-04 13:30:38. <1> Table Name: G_COMMENT_INFO
I. 2009-12-04 13:30:38. <1> Script Version: bogus_user_scan

I. 2009-12-04 13:30:38. <1> Script:

                    --{ml_ignore} 

I. 2009-12-04 13:30:38. <1> End of Error Context

I. 2009-12-04 13:30:38. <1> report_error (no script)
I. 2009-12-04 13:30:38. <1> report_odbc_error (no script)

I also posted this question here

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

菩提树下叶撕阳。 2024-08-20 10:39:21

我怀疑您遇到了 --{ml_ignore} 脚本的问题,该问题已在 v11.0.1 build 2260 中修复。

================(Build #2260  - Engineering Case #577142)================

The MobiLink server would not have skipped a script that was defined to be
ignored, if the script contained white space (spaces, tabs, and/or line-breaks)
before the special prefix, '--{ml_ignore}'.  This problem is fixed now. 

我强烈怀疑,如果您将 beta 环境升级到与开发环境相同的版本,这个问题将会消失离开。

I suspect you've run into a problem with --{ml_ignore} scripts that was fixed in v11.0.1 build 2260.

================(Build #2260  - Engineering Case #577142)================

The MobiLink server would not have skipped a script that was defined to be
ignored, if the script contained white space (spaces, tabs, and/or line-breaks)
before the special prefix, '--{ml_ignore}'.  This problem is fixed now. 

I strongly suspect that if you upgrade your beta environment to the same build as your development environment, that this problem will go away.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文