error log from BABLD 11 - log parser anyone?

[FNG3]

My organization is running BABLD 11 and there area few clients in the backup group that seem to attempt a connection but never actually do it – I have turned on rxtrace.ini logging file but the log file is not exactly helpful -


25/10/04 09:13:35:636 2724 2728 Scheduler-WM_TIMER: Set LocalTime and perform schedule
25/10/04 09:13:35:646 2724 2728 Scheduler-ScheduleRead: Read Database: D:\CA_BABLDdata\Client\data\xxx@xxxxxxx.lan\schedule.cdb
25/10/04 09:13:35:646 2724 2728 rwCore32:rwDBFileOpen: opening D:\CA_BABLDdata\Client\data\xxx@xxxxxxx.lan\schedule.cdb, mode=0
25/10/04 09:13:35:656 2724 2728 rwCore32:rwDBFileclose: 0
25/10/04 09:14:35:792 2724 2728 Scheduler-WM_TIMER: Set LocalTime and perform schedule
25/10/04 09:14:35:802 2724 2728 Scheduler-ScheduleRead: Read Database: D:\CA_BABLDdata\Client\data\xxx@xxxxxxx.lan\schedule.cdb
25/10/04 09:14:35:802 2724 2728 rwCore32:rwDBFileOpen: opening D:\CA_BABLDdata\Client\data\xxx@xxxxxxx.lan\schedule.cdb, mode=0
25/10/04 09:14:35:812 2724 2728 rwCore32:rwDBFileclose: 0
25/10/04 09:15:35:948 2724 2728 Scheduler-WM_TIMER: Set LocalTime and perform schedule
25/10/04 09:15:35:958 2724 2728 Scheduler-ScheduleRead: Read Database: D:\CA_BABLDdata\Client\data\xxx@xxxxxxx.lan\schedule.cdb
25/10/04 09:15:35:958 2724 2728 rwCore32:rwDBFileOpen: opening D:\CA_BABLDdata\Client\data\xxx@xxxxxxx.lan\schedule.cdb, mode=0
25/10/04 09:15:35:968 2724 2728 rwCore32:rwDBFileclose: 0
25/10/04 09:16:36:104 2724 2728 Scheduler-WM_TIMER: Set LocalTime and perform schedule
25/10/04 09:16:36:114 2724 2728 Scheduler-ScheduleRead: Read Database: D:\CA_BABLDdata\Client\data\xxx@xxxxxxx.lan\schedule.cdb
25/10/04 09:16:36:114 2724 2728 rwCore32:rwDBFileOpen: opening D:\CA_BABLDdata\Client\data\xxx@xxxxxxx.lan\schedule.cdb, mode=0
25/10/04 09:16:36:124 2724 2728 rwCore32:rwDBFileclose: 0
25/10/04 09:17:36:260 2724 2728 Scheduler-WM_TIMER: Set LocalTime and perform schedule
25/10/04 09:17:36:270 2724 2728 Scheduler-ScheduleRead: Read Database: D:\CA_BABLDdata\Client\data\xxx@xxxxxxx.lan\schedule.cdb
25/10/04 09:17:36:270 2724 2728 rwCore32:rwDBFileOpen: opening D:\CA_BABLDdata\Client\data\xxx@xxxxxxx.lan\schedule.cdb, mode=0
25/10/04 09:17:36:280 2724 2728 rwCore32:rwDBFileclose: 0
25/10/04 09:18:36:416 2724 2728 Scheduler-WM_TIMER: Set LocalTime and perform schedule
25/10/04 09:18:36:426 2724 2728 Scheduler-ScheduleRead: Read Database: D:\CA_BABLDdata\Client\data\xxx@xxxxxxx.lan\schedule.cdb
25/10/04 09:18:36:426 2724 2728 rwCore32:rwDBFileOpen: opening D:\CA_BABLDdata\Client\data\xxx@xxxxxxx.lan\schedule.cdb, mode=0
25/10/04 09:18:36:436 2724 2728 rwCore32:rwDBFileclose: 0
25/10/04 09:19:36:572 2724 2728 Scheduler-WM_TIMER: Set LocalTime and perform schedule
25/10/04 09:19:36:582 2724 2728 Scheduler-ScheduleRead: Read Database: D:\CA_BABLDdata\Client\data\xxx@xxxxxxx.lan\schedule.cdb
25/10/04 09:19:36:582 2724 2728 rwCore32:rwDBFileOpen: opening D:\CA_BABLDdata\Client\data\xxx@xxxxxxx.lan\schedule.cdb, mode=0
25/10/04 09:19:36:592 2724 2728 rwCore32:rwDBFileclose: 0
25/10/04 09:20:36:728 2724 2728 Scheduler-WM_TIMER: Set LocalTime and perform schedule
25/10/04 09:20:36:738 2724 2728 Scheduler-ScheduleRead: Read Database: D:\CA_BABLDdata\Client\data\xxx@xxxxxxx.lan\schedule.cdb
25/10/04 09:20:36:738 2724 2728 rwCore32:rwDBFileOpen: opening D:\CA_BABLDdata\Client\data\xxx@xxxxxxx.lan\schedule.cdb, mode=0
25/10/04 09:20:36:748 2724 2728 rwCore32:rwDBFileclose: 0
25/10/04 09:21:36:884 2724 2728 Scheduler-WM_TIMER: Set LocalTime and perform schedule
25/10/04 09:21:36:894 2724 2728 Scheduler-ScheduleRead: Read Database: D:\CA_BABLDdata\Client\data\xxx@xxxxxxx.lan\schedule.cdb
25/10/04 09:21:36:894 2724 2728 rwCore32:rwDBFileOpen: opening D:\CA_BABLDdata\Client\data\xxx@xxxxxxx.lan\schedule.cdb, mode=0
25/10/04 09:21:36:904 2724 2728 rwCore32:rwDBFileclose: 0
25/10/04 09:22:37:40 2724 2728 Scheduler-WM_TIMER: Set LocalTime and perform schedule
25/10/04 09:22:37:50 2724 2728 Scheduler-ScheduleRead: Read Database: D:\CA_BABLDdata\Client\data\xxx@xxxxxxx.lan\schedule.cdb
25/10/04 09:22:37:50 2724 2728 rwCore32:rwDBFileOpen: opening D:\CA_BABLDdata\Client\data\xxx@xxxxxxx.lan\schedule.cdb, mode=0
25/10/04 09:22:37:61 2724 2728 rwCore32:rwDBFileclose: 0
25/10/04 09:23:37:197 2724 2728 Scheduler-WM_TIMER: Set LocalTime and perform schedule
25/10/04 09:23:37:207 2724 2728 Scheduler-ScheduleRead: Read Database: D:\CA_BABLDdata\Client\data\xxx@xxxxxxx.lan\schedule.cdb
25/10/04 09:23:37:207 2724 2728 rwCore32:rwDBFileOpen: opening D:\CA_BABLDdata\Client\data\xxx@xxxxxxx.lan\schedule.cdb, mode=0
25/10/04 09:23:37:217 2724 2728 rwCore32:rwDBFileclose: 0
25/10/04 09:24:37:353 2724 2728 Scheduler-WM_TIMER: Set LocalTime and perform schedule
25/10/04 09:24:37:363 2724 2728 Scheduler-ScheduleRead: Read Database: D:\CA_BABLDdata\Client\data\xxx@xxxxxxx.lan\schedule.cdb
25/10/04 09:24:37:363 2724 2728 rwCore32:rwDBFileOpen: opening D:\CA_BABLDdata\Client\data\xxx@xxxxxxx.lan\schedule.cdb, mode=0
25/10/04 09:24:37:373 2724 2728 rwCore32:rwDBFileclose: 0
25/10/04 09:25:37:509 2724 2728 Scheduler-WM_TIMER: Set LocalTime and perform schedule
25/10/04 09:25:37:519 2724 2728 Scheduler-ScheduleRead: Read Database: D:\CA_BABLDdata\Client\data\xxx@xxxxxxx.lan\schedule.cdb
25/10/04 09:25:37:519 2724 2728 rwCore32:rwDBFileOpen: opening D:\CA_BABLDdata\Client\data\xxx@xxxxxxx.lan\schedule.cdb, mode=0
25/10/04 09:25:37:529 2724 2728 rwCore32:rwDBFileclose: 0

what I am actually looking for is a log parser that could make heads or tails of this file.

Anybody have any thoughts?

thanks

 

[wayneta]

FNG3:

What does your Job Log indicate? That's wherte you should find an error. I'm not aware of any 3rd-party utilities that will parse out this rxtrace.ini file, but there is one which will parse out your job logs and activity log. You can find more info about it at

http://www.arclog.com.

Perhaps that would help identify your problem.