Highlighted
Absent Member.
Absent Member.
5589 views

Novell DataSynchronizer Mobility Pack 1.2 Patch File 1

Hello All,

Novell Data Synchronizer Mobility Pack 1.2 Patch File 1 has been published
on patch finder. This is Not an update and will not modify the Build
Numbers. It will only replace few files on the Mobility Server running Build
579 to fix some issues mentioned in the Readme

http://download.novell.com/Download?buildid=J-KjQHJBrpw~

Regards
MJ
Labels (1)
0 Likes
35 Replies
Highlighted
Absent Member.
Absent Member.

Nice script.

Thanks,

Al

On 10/19/2011 at 12:51 PM, mj@novell.com<mj@novell.com> wrote:

Hello All,

Novell Data Synchronizer Mobility Pack 1.2 Patch File 1 has been published
on patch finder. This is Not an update and will not modify the Build
Numbers. It will only replace few files on the Mobility Server running Build
579 to fix some issues mentioned in the Readme

http://download.novell.com/Download?buildid=J-KjQHJBrpw~

Regards
MJ

0 Likes
Highlighted
Absent Member.
Absent Member.

Hmmm...applied this and it restarted the services ok.

Issued rcdatasync status and we have everything running but no emails
were going through to the devices.

Went in to the administration console and mobility connector wasn't
running. Manually tried starting it and it came up with the "Please
verify that the Connector Manager is running and that the
connectors.xml is correctly configured" error.

Oddly when looking a the mobility connection under type it said
"Mobility (v)", when I backrevved the type is "Mobility V1.1.0.2339"
but I was able to start everything back up again.

Thoughts?

Cheers,
Scott
0 Likes
Highlighted
Cadet 2nd Class Cadet 2nd Class
Cadet 2nd Class

mj@novell.com;2147317 wrote:
This is Not an update and will not modify the Build
Numbers.

Why release a patch that does not change version or build number? How does user know if patch has been applied or not, if version/build number won't show it?
0 Likes
Highlighted
Absent Member.
Absent Member.

Do i have to stop the datasync server completely before the update? or only some connectors. Or nothing at all?
It looks like the script is stopping nothing, only a restart at the end of the script.
How long does the update takes time?
0 Likes
Highlighted
Absent Member.
Absent Member.

kautium wrote:

> Why release a patch that does not change version or build number?


When a new version of Mobility is released which bumps the build number
there are a lot of changes. In fact, quite often, there's even a
script to modify the Postgres database. In between releases there are
a number of issues that come up (many of which are documented in this
forum) and customers only have two choices:

1) Open an SR to obtain a one-off fix for a particular issue.
2) Wait for the next version of Mobility, which may be 2-3 months.

The idea behind this patch is to get a collection of fixes to customers
so that those two options can be avoid. It's similar to, say, a
GroupWise FTF. Novell hasn't released FTFs in a long time, but when
they did it wasn't a new "service pack" or "hot fix." It was just a
fix for a particular issue.

> How
> does user know if patch has been applied or not, if version/build
> number won't show it?


Now that's an excellent question. I'd hope there would be some sort of
file which documents any patch updates which have been applied, similar
to the version file in /opt/novell/datasync. I'll ask.

--
Novell Knowledge Partner
Enhancement Requests: http://www.novell.com/rms

Joe Marton Emeritus Knowledge Partner
0 Likes
Highlighted
Absent Member.
Absent Member.

The script should not take more than 60 seconds and will stop and restart Datasync. If your connector startup is set to manual you will have to login and start the connectors after the script completes. We updated 7 Mobility servers without any issues.

Al

On 10/20/2011 at 3:56 AM, floort<floort@no-mx.forums.novell.com> wrote:


Do i have to stop the datasync server completely before the update? or
only some connectors. Or nothing at all?
It looks like the script is stopping nothing, only a restart at the end
of the script.
How long does the update takes time?


--
floort
------------------------------------------------------------------------
floort's Profile: http://forums.novell.com/member.php?userid=43048
View this thread: http://forums.novell.com/showthread.php?t=447054

0 Likes
Highlighted
Absent Member.
Absent Member.

kautium wrote:

> How
> does user know if patch has been applied or not, if version/build
> number won't show it?


It looks like the backup script creates /tmp/mobility_patch_579.tar.bak
so if that file exists you're probably patches. It's not a perfect
test since the backup happens prior to patching and of course that file
could be deleted. But it's one thing.

I've asked Novell if future patch updates like this could be modified
slightly to leave some sort of file which tells the currently installed
patch. Say for instanced, /opt/novell/datasync/patches.

--
Novell Knowledge Partner
Enhancement Requests: http://www.novell.com/rms

Joe Marton Emeritus Knowledge Partner
Highlighted
Absent Member.
Absent Member.

Done the update.
So far so good!

ahidalgo;2147504 wrote:
The script should not take more than 60 seconds and will stop and restart Datasync. If your connector startup is set to manual you will have to login and start the connectors after the script completes. We updated 7 Mobility servers without any issues.

Al

On 10/20/2011 at 3:56 AM, floort<floort@no-mx.forums.novell.com> wrote:


Do i have to stop the datasync server completely before the update? or
only some connectors. Or nothing at all?
It looks like the script is stopping nothing, only a restart at the end
of the script.
How long does the update takes time?


--
floort
------------------------------------------------------------------------
floort's Profile: View Profile: floort - Novell - NetIQ - SUSE
View this thread: Novell DataSynchronizer Mobility Pack 1.2 Patch File 1
0 Likes
Highlighted
Absent Member.
Absent Member.

Applied patch 1.2 and 1.2 Patch File 1 together and after that got some issues with the "event timing". Emails need some time (~20 minutes) to be shown on the mobile device in comparison to the gw client.
Further I can no longer access the "mobility monitor page" which is now telling my to make sure the "connector is running".

Till now no user complained so it does not bother me...so far... 😉
0 Likes
Highlighted
Absent Member.
Absent Member.

pitnika wrote:

> Applied patch 1.2 and 1.2 Patch File 1 together and after that got
> some issues with the "event timing". Emails need some time (~20
> minutes) to be shown on the mobile device in comparison to the gw
> client. Further I can no longer access the "mobility monitor page"
> which is now telling my to make sure the "connector is running".


After installing 1.2 (build 579) did you make sure to run the update
script?

--
Novell Knowledge Partner
Enhancement Requests: http://www.novell.com/rms

Joe Marton Emeritus Knowledge Partner
0 Likes
Highlighted
Absent Member.
Absent Member.

After I applied the Novell Data Synchronizer Mobility Pack 1.2 Patch File 1 I have 3 HTC Thunderbolts that cannot download attchments. They can see that they have attachments but no download and no error message. Andoid X and iphones are working correctly.

any thoughts
WMS
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.