|
Home > Archive > SQL Anywhere database replication > July 2005 > Old logs won't get deleted
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 |
Old logs won't get deleted
|
|
|
| Hi,
Version: ASA 9.0.2.2542
I'm having a problem with mobilink and delete_old_logs. The
logs won't
get deleted. DELETE_OLD_LOGS is set to 'ON'. I have one
mobilink user,
one publication and no sql remote users. I use dbmlsync with
-x option.
When I run dblog I get this:
Adaptive Server Anywhere Transaction Log Utility Version
9.0.2.2542
"gdansk9.db" is using log file "gdansk9.log"
"gdansk9.db" is using no log mirror file
Transaction log starting offset is 01051687660
SQL Remote truncation offset is 0007886412
DBMLSync truncation offset is 01051671857
Transaction log current relative offset is 0000044387
SYSSYNC-table:
sync_id publication_
id progress site_nam
e option server_co
nnect last_download_
time last_upload_tim
e created log_sent
generation_number
4 NULL NULL gdansk
_article sv=article_
sync01; host=mps3 NU
LL 1900-01-01
00:00:00.000 NULL NULL 0
5 4 NULL NULL sv=
article_sync01; NULL
NULL 1900-01-01
00:00:00.000 NULL NULL 0
6 4 1051687606 gdan
sk_article sv=articl
e_sync01; NULL 2005
-06-30
21:01:00.457 2005-06-30
21:01:00. 457 1042740290 1051
687606 1
Does anyone know what's problem?
regards
David
| |
| Rob Waywell 2005-07-01, 1:23 pm |
| Can you run "select * from sys.sysremoteusers"?
This will verify that there are no SQL Remote users defined. The symptom
suggests that a remote user is still defined.
Another thing to check is to "select * from sys.sysoption where "option" =
'delete_old_logs' " and verify that the delete_old_logs option is set for
PUBLIC, or the user that you are running dbmlsync with. This is a little
less likely given the current symptom, but it is fairly easy to rule out.
--
-----------------------------------------------
Robert Waywell
Sybase Adaptive Server Anywhere Developer - Version 8
Sybase Certified Professional
Sybase's iAnywhere Solutions
Please respond ONLY to newsgroup
EBF's and Patches: http://downloads.sybase.com
choose SQL Anywhere Studio >> change 'time frame' to all
To Submit Bug Reports:
http://case-express.sybase.com/cx/c...sc?CASETYPE=Bug
SQL Anywhere Studio Supported Platforms and Support Status
http://my.sybase.com/detail?id=1002288
Whitepapers, TechDocs, and bug fixes are all available through the iAnywhere
Developer Community at www.ianywhere.com/developer
<David> wrote in message news:42c51e87.29e6.1681692777@sybase.com...
> Hi,
>
> Version: ASA 9.0.2.2542
>
> I'm having a problem with mobilink and delete_old_logs. The
> logs won't
> get deleted. DELETE_OLD_LOGS is set to 'ON'. I have one
> mobilink user,
> one publication and no sql remote users. I use dbmlsync with
> -x option.
>
> When I run dblog I get this:
>
> Adaptive Server Anywhere Transaction Log Utility Version
> 9.0.2.2542
> "gdansk9.db" is using log file "gdansk9.log"
> "gdansk9.db" is using no log mirror file
> Transaction log starting offset is 01051687660
> SQL Remote truncation offset is 0007886412
> DBMLSync truncation offset is 01051671857
> Transaction log current relative offset is 0000044387
>
>
> SYSSYNC-table:
>
> sync_id publication_id progress site_name option server_connect
> last_download_time last_upload_time created log_sent generation_number
> 4 NULL NULL gdansk_article sv=article_sync01; host=mps3 NULL 1900-01-01
> 00:00:00.000 NULL NULL 0
> 5 4 NULL NULL sv=article_sync01; NULL NULL 1900-01-01
> 00:00:00.000 NULL NULL 0
> 6 4 1051687606 gdansk_article sv=article_sync01; NULL 2005-06-30
> 21:01:00.457 2005-06-30
> 21:01:00.457 1042740290 1051687606 1
>
> Does anyone know what's problem?
>
> regards
> David
| |
|
| Thank's for your response.
There is nothing in sys.sysremoteuses. We had remote users
in the database before but they were removed a time ago.
sys.sysoptions:
user_id option settings
1 DELETE_OLD_LOGS ON
2 delete_old_logs ON
best regards
David
> Can you run "select * from sys.sysremoteusers"?
> This will verify that there are no SQL Remote users
> defined. The symptom suggests that a remote user is still
> defined.
>
> Another thing to check is to "select * from sys.sysoption
> where "option" = 'delete_old_logs' " and verify that the
> delete_old_logs option is set for PUBLIC, or the user
> that you are running dbmlsync with. This is a little less
> likely given the current symptom, but it is fairly easy to
> rule out.
>
> --
> -----------------------------------------------
> Robert Waywell
> Sybase Adaptive Server Anywhere Developer - Version 8
> Sybase Certified Professional
>
> Sybase's iAnywhere Solutions
>
> Please respond ONLY to newsgroup
>
> EBF's and Patches: http://downloads.sybase.com
> choose SQL Anywhere Studio >> change 'time frame' to all
>
> To Submit Bug Reports:
>
http://case-express.sybase.com/cx/c...sc?CASETYPE=Bug
>
> SQL Anywhere Studio Supported Platforms and Support Status
> http://my.sybase.com/detail?id=1002288
>
> Whitepapers, TechDocs, and bug fixes are all available
> through the iAnywhere Developer Community at
> www.ianywhere.com/developer <David> wrote in message
> gdansk_article sv=article_sync01; host=mps3 NULL
>
>
| |
| Rob Waywell 2005-07-05, 9:23 am |
| If you check sys.sysuserperms, what is the user name for the user ID's 1 and
2? Do these match the user you are running dbmlsync with?
One other question, have you ever run dbremote since you dropped the last of
the remote users? Dbremote is the tool that will move the SQL Remote
truncation point, if you haven't run it since you dropped the last remote
user, then running it will at least move, if not remove, the SQL Remote
truncation point. I haven't had a chance to try this, but it is worth ruling
out.
--
-----------------------------------------------
Robert Waywell
Sybase Adaptive Server Anywhere Developer - Version 8
Sybase Certified Professional
Sybase's iAnywhere Solutions
Please respond ONLY to newsgroup
EBF's and Patches: http://downloads.sybase.com
choose SQL Anywhere Studio >> change 'time frame' to all
To Submit Bug Reports:
http://case-express.sybase.com/cx/c...sc?CASETYPE=Bug
SQL Anywhere Studio Supported Platforms and Support Status
http://my.sybase.com/detail?id=1002288
Whitepapers, TechDocs, and bug fixes are all available through the iAnywhere
Developer Community at www.ianywhere.com/developer
<David> wrote in message news:42c8d216.44a2.1681692777@sybase.com...[color=darkred]
> Thank's for your response.
>
> There is nothing in sys.sysremoteuses. We had remote users
> in the database before but they were removed a time ago.
>
> sys.sysoptions:
> user_id option settings
> 1 DELETE_OLD_LOGS ON
> 2 delete_old_logs ON
>
> best regards
> David
>
> http://case-express.sybase.com/cx/c...sc?CASETYPE=Bug
| |
|
| sys.sysuserperms
0 SYS
1 DBA
2 PUBLIC
3 dbo
....
I'm using DBA to run dbmlsync.
I tried to run dbremote but get error message: No remote
uses defined.
The logs are still not deleted.
regards
David
> If you check sys.sysuserperms, what is the user name for
> the user ID's 1 and 2? Do these match the user you are
> running dbmlsync with?
>
> One other question, have you ever run dbremote since you
> dropped the last of the remote users? Dbremote is the
> tool that will move the SQL Remote truncation point, if
> you haven't run it since you dropped the last remote user
> , then running it will at least move, if not remove, the
> SQL Remote truncation point. I haven't had a chance to
> try this, but it is worth ruling out.
>
> --
> -----------------------------------------------
> Robert Waywell
> Sybase Adaptive Server Anywhere Developer - Version 8
> Sybase Certified Professional
>
> Sybase's iAnywhere Solutions
>
> Please respond ONLY to newsgroup
>
> EBF's and Patches: http://downloads.sybase.com
> choose SQL Anywhere Studio >> change 'time frame' to all
>
> To Submit Bug Reports:
>
http://case-express.sybase.com/cx/c...sc?CASETYPE=Bug
>
> SQL Anywhere Studio Supported Platforms and Support Status
> http://my.sybase.com/detail?id=1002288
>
> Whitepapers, TechDocs, and bug fixes are all available
> through the iAnywhere Developer Community at
> www.ianywhere.com/developer <David> wrote in message
> your response. >
> time ago. >
> still >> defined.
> sys.sysoption >> where "option" = 'delete_old_logs' " and
> verify that the >> delete_old_logs option is set for
> PUBLIC, or the user >> that you are running dbmlsync with.
> This is a little less >> likely given the current symptom
> , but it is fairly easy to >> rule out.
> all >>
>
http://case-express.sybase.com/cx/c...sc?CASETYPE=Bug
> Status >> http://my.sybase.com/detail?id=1002288
> delete_old_logs. >> > The logs won't
> one >> > mobilink user,
> dbmlsync >> > with -x option.
> Version >> > 9.0.2.2542
>
>
| |
|
|
|
| Ok, thank you for your help.
> Hi David,
> I think it's time to open a support case on this
> issue.
>
> --
> -----------------------------------------------
> Robert Waywell
> Sybase Adaptive Server Anywhere Developer - Version 8
> Sybase Certified Professional
>
> Sybase's iAnywhere Solutions
>
> Please respond ONLY to newsgroup
>
> EBF's and Patches: http://downloads.sybase.com
> choose SQL Anywhere Studio >> change 'time frame' to all
>
> To Submit Bug Reports:
>
http://case-express.sybase.com/cx/c...sc?CASETYPE=Bug
>
> SQL Anywhere Studio Supported Platforms and Support Status
> http://my.sybase.com/detail?id=1002288
>
> Whitepapers, TechDocs, and bug fixes are all available
> through the iAnywhere Developer Community at
> www.ianywhere.com/developer <David> wrote in message
> for >> the user ID's 1 and 2? Do these match the user you
> are >> running dbmlsync with?
> you >> dropped the last of the remote users? Dbremote is
> the >> tool that will move the SQL Remote truncation
> point, if >> you haven't run it since you dropped the last
> remote user >> , then running it will at least move, if
> not remove, the >> SQL Remote truncation point. I haven't
> had a chance to >> try this, but it is worth ruling out.
> all >>
>
http://case-express.sybase.com/cx/c...sc?CASETYPE=Bug
> Status >> http://my.sybase.com/detail?id=1002288
> for >> your response. >
> and >> verify that the >> delete_old_logs option is set
> for >> PUBLIC, or the user >> that you are running
> dbmlsync with. >> This is a little less >> likely given
> the current symptom >> , but it is fairly easy to >> rule
> out. >> >>
> 8 >> >> Sybase Certified Professional
> to >> all >>
>
http://case-express.sybase.com/cx/c...sc?CASETYPE=Bug
> available >> >> through the iAnywhere Developer Community
> at >> >> www.ianywhere.com/developer <David> wrote in
> message >> >> >
> news:42c51e87.29e6.1681692777@sybase.com... Hi, >> >> >
> have >> one >> > mobilink user,
> 0000044387 >> >> >
> last_upload_time >> >> > created log_sent
> generation_number 4 NULL NULL >> >> gdansk_article
> sv=article_sync01; host=mps3 NULL >> >> > 1900-01-01
> 00:00:00.000 NULL NULL 0 >> >> > 5 4 NULL NULL
> sv=article_sync01; NULL NULL 1900-01-01 >> >> >
> 00:00:00.000 NULL NULL 0 >> >> > 6 4 1051687606
> gdansk_article sv=article_sync01; NULL >> >> > 2005-06-30
> 21:01:00.457 2005-06-30 >> >> > 21:01:00.457 1042740290
> 1051687606 1 >> >> >
>
>
|
|
|
|
|