Re: SQL error - damaged index maybe??

Hi Dave,

Tried RCLSTG, IPL. RCLSPLSTG, EDTRBDAP etc....still no luck,

Clare

----- Original Message ----- From: "Turnidge, Dave" <DTurnidge@xxxxxxxxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Thursday, April 12, 2007 2:55 PM
Subject: RE: SQL error - damaged index maybe??

Damaged objects are fixed by doing RCLSTG...

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Clare Holtham
Sent: Thursday, April 12, 2007 8:54 AM
To: Midrange Systems Technical Discussion
Subject: Re: SQL error - damaged index maybe??

Thanks Colin,
It didn't show us anything more I'm afraid!
I think IBM have ways of finding these damaged objects and fixing them
don't they? Sadly the client doesn't have maintenance....

cheers,

Clare

----- Original Message -----
From: "Colin Williams" <colinwilliams007@xxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Thursday, April 12, 2007 11:39 AM
Subject: Re: SQL error - damaged index maybe??

try doing a STRDBG on the affected job first, see if that gives more
information...

On 12/04/07, Clare Holtham <Clare.Holtham@xxxxxxxxxxxxxx> wrote:

Hi all,

I have been asked to look at this problem - customer filled up their

disk

and system crashed. Afterwards, consultant deleted a whole lot of

libs,

some
were in the BPCS library list!
He has restored the libs that were in the libl...but doesn't fix the
error:
Since then, pick confirm and BIL501 both issue error msgs MCH3402 and
CPF4204, 'tried to refer to all or part of an object no longer there'

and

'internal failure in query processor'. Msgs are coming from QQQIMPLE

and

QQQQUERY (STARFC), also SQL0901 from QSQROUTE (CK_DEBUG) but no clue

as

to
which object is affected.
Tried RCLSTG and IPL, could try copyfile - but which file??
Anyone have any other ideas? Get it to recreate access paths maybe?

thanks,

Clare

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)

mailing

list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.