RE: SQL System Error

[rob@xxxxxxxxx]

True, 

A listing of what hardware may not work on V5R1, V5R2, and -above-, is 
available at:
http://www.ibm.com/servers/eserver/iseries/support/planning/nav.html

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





pnelson@xxxxxxxxxx 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
02/17/2004 10:49 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
cc

Fax to

Subject
RE: SQL System Error






Rob, 

You're making the assumption that Glen's machine can accommodate 5.2. I've 

got some customers who can't make the jump because of hardware and budget 
constraints. Glen needs to get in touch with a good BP (like Jim 
Oberholtzer), as well as IBM's partners in education folks, and get that 
box up to snuff.



Paul Nelson
Arbor Solutions, Inc.
708-670-6978  Cell
pnelson@xxxxxxxxxx





rob@xxxxxxxxx
Sent by: midrange-l-bounces@xxxxxxxxxxxx
02/17/2004 09:33 AM
Please respond to Midrange Systems Technical Discussion

 
        To:     Midrange Systems Technical Discussion 
<midrange-l@xxxxxxxxxxxx>
        cc: 
        Subject:        RE: SQL System Error


Dude, you haven't put a cume on there since 2001?  TL01163 is in Julian.

In a perfect world, I'd suggest the following:
RCLSTG
GO SAVE - 21
Upgrade the OS to V5R2
Put on the latest cume for V5R2
Put on the latest ptf groups; especially hipers and database groups

Option 2)
RCLSTG
GO SAVE - 21
Put on the latest cume for V5R1
Put on the latest ptf groups; especially hipers and database groups

Option 3)
RCLSTG

Option 4)
RCLSTG SELECT(*DBXREF)
(May have to fall back to option 3 if SQL still fails)

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





"Orsburn, Glen O" <orsburn@xxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
02/17/2004 10:05 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
"Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
cc

Fax to

Subject
RE: SQL System Error






OS Release is: V5R1M0 L00

First PTF is: TL01163  Permanently applied

The command WRKPTFGRP doesn't work.

Glen


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Tuesday, February 17, 2004 8:58 AM
To: Midrange Systems Technical Discussion
Subject: Re: SQL System Error


The disconcerting message is MCH1668.

Going to http://www-912.ibm.com/n_dir/nas4apar.nsf/$$Search?openform
and searching for MSGMCH1668 gets a lot of hits.  Searching for
MSGSQL0901 
also gets a lot of hits.  But nothing in combo.

DSPPTF
At the top, what is your OS release?
What is the first ptf, example TL03364?

WRKPTFGRP
What do you have there?

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





"Orsburn, Glen O" <orsburn@xxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
02/17/2004 09:35 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
"Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> cc

Fax to

Subject
SQL System Error






Any suggests or help on this one would be appreciated:

When we run subquery interactively in SQL this is the error: (if I
should run each Select statement by it self no error occurs)

 <<Picture (Metafile)>> SELECT customer_num, customer_name 
  FROM premiere/customer 
WHERE customer_num in (select customer_num from premiere/orders where
                                 order_date = '10/20/2003')

I'm getting the following error when we run a interactive SQL statement
above:

Message ID . . . . . . :   SQL0901       Severity . . . . . . . :   50
Message type . . . . . :   Diagnostic

Message . . . . :   SQL system error.
Cause . . . . . :   An SQL system error has occurred.  The current SQL
  statement cannot be completed successfully.  The error will not
prevent
  other SQL statements from being processed. Previous messages may
indicate
  that there is a problem with the SQL statement and SQL did not
correctly
  diagnose the error. The previous message identifier was CPF4204.
Internal
  error type 3109 has occurred. If precompiling, processing will not
continue
  beyond this statement.

When I dig in a little deeper it has the following message:

System object ORDERS    ORDERS partially damaged. Internal dump ID .
Error
  class 0, device number X'0000'.
Internal failure occurred in query processor.
File QAP0ZDMP created in library QTEMP.
Member QP0Z110085 added to file QAP0ZDMP in QTEMP.
User Trace data for job 110085/GOSQL225/QPADEV000D dumped to member
  QP0Z110085 in file QAP0ZDMP in library QTEMP.
27 records copied from member QP0Z110085.
1 User Trace buffer(s) deleted.
SQL system error.


Glen 
FVTC Instructor


"Give a man a fish and he'll eat for a day. Teach a man to fish and
he'll eat for a lifetime.".


_______________________________________________
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.



_______________________________________________
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.