Big transaction

[dju...@gmail.com]

Unfortunately we commited very big transaction on consolidated
database (massive update). Dbremote hangs after creating over 70 files
per remote user, we tried to change memory amount, but it doesn't help
(-m switch).

Is there any possibility to generate files for one remote user (we
think that this is memory issue, so reducing amount of generated data
should help)?

Regards,
Dariusz Jurojć

[Reg Domaratzki [Sybase iAnywhere]]

No. SQL Remote will generate messages for all users every time.

What version and build number of SQL Remote are you using?

Does increasing the amount of memory change how far into the sending of
messages SQL Remote gets? If not, I highly doubt it's a memory problem.

Can you post the SQL Remote log?

--
Reg Domaratzki, Sybase iAnywhere Solutions
Please reply only to the newsgroup

Documentation : Exercise your WRITE @DocCommentXchange: DCX.sybase.com
SQL Anywhere Patches and EBFs : http://downloads.sybase.com/swd/base.do
-> Choose SQL Anywhere
-> Optionally set filter to "Display ALL platforms IN ALL MONTHS"

[dju...@gmail.com]

On 13 Paź, 16:04, "Reg Domaratzki [Sybase iAnywhere]"
<firstname.lastn...@ianywhere.com> wrote:

> djur...@gmail.com wrote:
> > Unfortunately we commited very big transaction on consolidated
> > database (massive update). Dbremote hangs after creating over 70 files
> > per remote user, we tried to change memory amount, but it doesn't help
> > (-m switch).
>
> > Is there any possibility to generate files for one remote user (we
> > think that this is memory issue, so reducing amount of generated data
> > should help)?
>
> No.  SQL Remote will generate messages for all users every time.
>
> What version and build number of SQL Remote are you using?
>
> Does increasing the amount of memory change how far into the sending of
> messages SQL Remote gets?  If not, I highly doubt it's a memory problem.
>
> Can you post the SQL Remote log?
>

Increasing memory buffer size resolved issue only to some extent.
Further increasing didn't help - sql remote agent just hangs in the
same place every time.

In SQL Remote log there are just "Sending message to..." messages:

I. 2009-10-12 08:09:32. Sending message to
"F388" (7-0101862117793-0101862117793-0)
I. 2009-10-12 08:09:32. Sending message to
"F389" (6-0101862117793-0101862117793-0)
I. 2009-10-12 08:09:32. Sending message to
"F401" (17-0101862117793-0101862117793-0)
I. 2009-10-12 08:09:32. Sending message to
"F398" (6-0101862117793-0101862117793-0)
I. 2009-10-12 08:09:32. Sending message to
"F402" (3-0101862117793-0101862117793-0)
I. 2009-10-12 08:09:32. Sending message to
"F555" (19-0101862117793-0101862117793-0)
I. 2009-10-12 08:09:32. Sending message to
"F399" (5-0101862117793-0101862117793-0)

....

I. 2009-10-12 08:11:01. Sending message to
"F318" (11-0101862117793-0101862117793-75)
I. 2009-10-12 08:11:01. Sending message to
"F319" (37-0101862117793-0101862117793-75)
I. 2009-10-12 08:11:01. Sending message to
"F323" (24-0101862117793-0101862117793-75)
I. 2009-10-12 08:11:01. Sending message to
"F320" (96-0101862117793-0101862117793-75)
I. 2009-10-12 08:11:01. Sending message to
"F321" (88-0101862117793-0101862117793-75)
I. 2009-10-12 08:11:01. Sending message to
"F324" (3-0101862117793-0101862117793-75)
I. 2009-10-12 08:11:01. Sending message to
"F325" (6-0101862117793-0101862117793-75)

Same message repeated 76 times for every remote user.

--
Dariusz Jurojć

[Reg Domaratzki [Sybase iAnywhere]]

>>> Unfortunately we committed very big transaction on consolidated

>>> database (massive update). Dbremote hangs after creating over 70 files
>>> per remote user, we tried to change memory amount, but it doesn't help
>>> (-m switch).
>>>
>>> Is there any possibility to generate files for one remote user (we
>>> think that this is memory issue, so reducing amount of generated data
>>> should help)?
>> No. SQL Remote will generate messages for all users every time.
>>

>> Does increasing the amount of memory change how far into the sending of
>> messages SQL Remote gets? If not, I highly doubt it's a memory problem.
>

> Increasing memory buffer size resolved issue only to some extent.
> Further increasing didn't help - sql remote agent just hangs in the
> same place every time.
>
>> Can you post the SQL Remote log?
>
> In SQL Remote log there are just "Sending message to..." messages:
>
> I. 2009-10-12 08:09:32. Sending message to
> "F388" (7-0101862117793-0101862117793-0)

> ...

> I. 2009-10-12 08:11:01. Sending message to
> "F325" (6-0101862117793-0101862117793-75)

What version and build number of SQL Remote are you using?
What message transport system are you using? FILE, FTP, SMTP?
How much memory did you allocate on the -m switch?
How many messages get generated with the default memory value of 2M and
how many get generated when you increase the value specified by -m?

What version and build number of SQL Remote are you using?

How many remote users do you have?
Do your remote users subscribe to the publication(s) with a subscribe by
value, or does everyone receive the same information?

What version and build number of SQL Remote are you using?

--

[tps]

FYI

On our system (sqlanywhere VERSION 8.03) using the FTP transport we have
successfully pushed through over 1000 messages to over 1600 remote
users. i.e. > 1.6 million files pushed. It took our server well over 65
hours to complete the message sending.

TPS