|
midrange.com
When it is a QADB* file problem requesting a RCLSTG you're are in luck.
Normally it's blatently obvious and you'll see messages like Database Cross
reference files are damaged. That part that puts you in luck is that you
can run a RCLSTG *DBXREF. On a system that takes 17 hours to run a full
RCLSTG the RCLSTG *DBXREF takes only 20 minutes. Still requires a
dedicated system.
Rob Berendt
==================
Remember the Cole!
Dimitri Efimov
<defimov@wiese.com. To: MIDRANGE-L@midrange.com
pe> cc:
Sent by: Subject: RE: RV: QDBSRV IN
LCK, please help!
owner-midrange-l@mi
drange.com
02/06/01 05:24 PM
Please respond to
MIDRANGE-L
Last RCLSTG run a lot of time ago (it's a baknig system 24 hours 365 days),
but it looks like there is not any damages of QADB*, but the problem
repeate
each day almoust the same time!
Thanks a lot,
Dmitri
-----Mensaje original-----
De: Pete Massiello [mailto:pmassiello@os-solutions.com]
Enviado el: martes, 06 de febrero de 2001 12:58
Para: MIDRANGE-L@midrange.com
Asunto: Re: RV: QDBSRV IN LCK, please help!
I once saw something similar when their was some damage on one of the QADB*
files. The files needed to be rebuilt, which is one of the things that
RCLSTG
does. The fix was to run a RCLSTG. Not sure if that is what your problem
is,
but when was the last time you ran a RCLSTG?
Have you recently upgraded your machine, or done anything else that may
provide a clue?
Pete Massiello
Dimitri Efimov wrote:
> > Can somebody help me with this, please:
> > 1. Why ALL jobs QDBSRV01-25 (as far as I know, theese jobs rebuid
access
> > paths.) change status to LCKW in our system (740)? They keep this
status
> > for a 30 - 40 min.
> > 2. Can it be a cause of partial system block - looks like other
programs
> > cannot add new records in files ?
> >
> >
> > Any ideas, please!
> >
> > Dmitri Efimov
> >
> > Banco Wiese Sudameris
> >
> >
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
david@midrange.com
> +---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
