|
Home > Archive > SQL Anywhere database > December 2005 > Manually updating a table in a SQLRemote scenario
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Manually updating a table in a SQLRemote scenario
|
|
| Oliver Schulze L. 2005-12-19, 8:24 pm |
| Hi,
I started to have some strange errors like:
"SQL statement failed: (-274) Procedure or trigger calls have nested too
deeply"
It seems that there is a problem in a trigger, but never happend
before.
I have a SQL Remote setup using ASA 6.0.4, and I need to insert
the rows that dbremote failed to insert from a Remote DB to the
Consolidated DB.
Is there a way that I can insert those rows manually without breaking
the SQL Remote installation?
I want to insert the missing rows and later install new trigers
with debug code.
Many thanks
Oliver
| |
| Nick Elson 2005-12-21, 11:23 am |
| I would resolve the trigger recursion issue or,
at least, understand why it is happening. It
is entirely likely that is the same reason
SQL Remote is failing to replicate those
rows ... so ... don't break SQL Remote just
yet.
As to posting questions that pertains to SQL
Remote, those should be posed to the the
sybase.public.sqlanywhere.replication
newsgroup instead.
"Oliver Schulze L." <news.oliver@samera.com.py> wrote in message
news:43a73b38@forums
-2-dub...
> Hi,
> I started to have some strange errors like:
> "SQL statement failed: (-274) Procedure or trigger calls have nested too
> deeply"
> It seems that there is a problem in a trigger, but never happend
> before.
>
> I have a SQL Remote setup using ASA 6.0.4, and I need to insert
> the rows that dbremote failed to insert from a Remote DB to the
> Consolidated DB.
>
> Is there a way that I can insert those rows manually without breaking
> the SQL Remote installation?
>
> I want to insert the missing rows and later install new trigers
> with debug code.
>
> Many thanks
> Oliver
| |
| Oliver Schulze L. 2005-12-21, 8:24 pm |
| Hi Nick,
Nick Elson wrote:
> I would resolve the trigger recursion issue or,
> at least, understand why it is happening. It
> is entirely likely that is the same reason
> SQL Remote is failing to replicate those
> rows ... so ... don't break SQL Remote just
> yet.
I also got a corruption in my .log file and dbremote
can not understand it. I resolved the issue and
posted the result in another thread.
I could not find any error in my trigger, still
investigating it.
> As to posting questions that pertains to SQL
> Remote, those should be posed to the the
>
> sybase.public.sqlanywhere.replication
Ooops, sorry about that. Will do, just reinstalled
Thunderbird and forgot that group.
>
> newsgroup instead.
Regards,
Oliver
|
|
|
|
|