Middleware | Service Delivery | Group IT
LLOYDS BANKING GROUP
Subject: Re: [ADSM-L] Changed SQL behavior under server 6.2.3.1
From: Prather, Wanda Wanda.Prather AT ICFI DOT COM
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 9 Jan 2015 17:32:19 +
Oooh, that's evil.
Had a consult
David
Thanks for the suggestion. I would have thought both were equivalent, but I
tried each of them anyway and both gave the wrong answer:
tsm: Xselect count(*) from nodes where node_name not in (select node_name
from filespaces)
Unnamed[1]
0
tsm: Xselect
@VM.MARIST.EDU
Subject: Re: [ADSM-L] Changed SQL behavior under server 6.2.3.1
David
Thanks for the suggestion. I would have thought both were equivalent, but I
tried each of them anyway and both gave the wrong answer:
tsm: Xselect count(*) from nodes where node_name not in (select node_name
Zoltan
Thanks for the response. I'm not sure whether this is platform related - all my
tests were conducted on servers running on AIX. While the problem is not
apparent on v5.x instances, it seems to affect v6.x instances at all our levels.
Like Margaret's experience back in 2012, the problem
Hi,
the last query should be select count(*) from nodes where node_name not in
(select node_name from filespaces)
NOT keyword between column name and IN keyword.
David RIGAUDIERE
Prestataire Logic
SI2M - Direction des Systèmes d’Information Groupe Malakoff Médéric
Direction de la Production
What is your platform/OS? I recently upgraded from 6.3.4.300 to 6.3.5.100
and am seeing lots of problems with selects not return consistent/correct
results as their non-select counterparts.
The reason I ask about the OS is IBM has stated there are known problems
with RedHat 6 kernels causing
I've just tried the select statement on v6.3.5.0 that Margaret tried below in
2012 and it still returns no rows. Does anyone have a work-around that can be
used?
Regards
Neil
On 6/21/2012 9:55 AM, Clark, Margaret wrote:
Using TSM server 6.2.3.1, the following SQL command no longer works:
Using TSM server 6.2.3.1, the following SQL command no longer works:
select node_name from nodes where node_name not in (select node_name from
filespaces)
It still works correctly if you take out the not.
Any ideas?
- Margaret
Hi, Margaret. What error are you getting?
Taking a stab in the dark, explicitly using NODES and FILESPACES in your
predicate can cause unexpected results
(http://www-01.ibm.com/support/docview.wss?uid=swg21380830). I would
guess failing with the addition of the word NOT could be construed as
an
behavior under server 6.2.3.1
Hi, Margaret. What error are you getting?
Taking a stab in the dark, explicitly using NODES and FILESPACES in your
predicate can cause unexpected results
(http://www-01.ibm.com/support/docview.wss?uid=swg21380830). I would guess
failing with the addition
10 matches
Mail list logo
