Having clause and subquery

Hi,
The below result Is retrieved from Table T1(Select * From T1),
ID CODE
101 A1
102 A1
103 A2
104 A1
105 B1
106 B1
107 B5
I want the result like below,
101 A1
102 A1
104 A1
105 B1
106 B1
Can anyone help me to get the expected result.

Hi Dhiva !
you can get result with order by clause.
do you want this?
WITH
DATA AS
(select 101 as id, 'A1' val from dual union all
select 102 as id, 'A1' val from dual union all
select 103 as id, 'A2' val from dual union all
select 104 as id, 'A1' val from dual union all
select 105 as id, 'B1' val from dual union all
select 106 as id, 'B1' val from dual union all
SELECT 107 AS ID, 'B5' VAL FROM DUAL)
SELECT * FROM DATA
ORDER by val, id

Similar Messages

Where or Having clause and COUNT(1)

I'm having trouble trying to figure out the way to get the conditional difference between two counts in a where clause.
I would like to scan a table and only select records where the record count of one column attribute is different than another.
I have
select name, count(1) from skill <<< TOTAL_COUNT
and
select name, count(1) from skill where score is not NULL <<<< SCORED_COUNT
I want to have a statement that just returns the names for those where TOTAL_COUNT - SCORED_COUNT = 0
... meaning those names where any of the rows have not been scored.
I've tried a "having clause" but it still returns all there names. Even those there TOTAL_COUNT - SCORED_COUNT > 0
Here's the non-working code....
select * from
(select full_name
from emp e
where e.manager = 'Smith, John'
having
((select count(1)
from emp_skill es
where es.emp_fk = e.id
group by null) -
(select count(1)
from emp_skill es1
where es1.emp_fk = e.id and
es1.self_prof is not NULL
group by null)) = 0
)

Don't take 3360 too seriously in this context. COUNT(expression) is a bit of a running joke around these parts.
However, his response does contain the seed of the solution for your problem.
COUNT(<expression>) works because the COUNT function counts all rows with a non-null value for expression. So COUNT('Chocula') counts the non-null occurences of the literal string 'Chocula' in the table. Obviously, this counts every row in the table. COUNT(*) counts all the non-null occurences of a row in the table (even a row with all null values is a row). Clearly these are equivalent.
However, if <expression> evaluates differently for each row, then COUNT(*) and COUNT(<expression>) can differ. So, for your example, assuming that the scored column is truly NULL in some records, what you need is something like:
SQL> SELECT * FROM skill;
NAME            SCORE
BOB                 5
BOB                 6
BOB                 7
BILL                5
BILL                8
BILL
SQL> SELECT name, total, scored
2 FROM (SELECT name, count(*) total, count(score) scored
3        FROM skill
4        GROUP BY name)
5 WHERE total <> scored;
NAME            TOTAL     SCORED
BILL                3          2

Why Scalar Subquery expression cannot be used in HAVING clauses?

Hi All,
I'm new to SQL. I'm confused with Scalar Subquery.
Is there anyone who can answer me why Scalar Subquery expression cannot be used in HAVING clauses.
Can you show me a example?
Thanks very much,
Xianyi.Ye
Edited by: 908428 on 2012-1-16 下午7:24

Hi,
908428 wrote:
Hi Frank,
Thank you for your quick reply. I also agree with your point.
But when I read the book, "OCA Oracle Database SQL Certified Expert Exam Guide",( link to illegal copies of book removed by moderator )
on Page 359, it said that
Scalar subquery expressions cannot be used in the following locations:
1. In CHECK constraints
2. In GROUP BY clauses
3. In HAVING clauses
4. In a function-based index (which is coming up in Chapter 11)
5. As a DEFAULT value for a column
6. In the RETURNING clause of any DML statement
7. In the WHEN conditions of CASE
8. In the START WITH and CONNECT BY clauses, which we discuss in
Chapter 16.7 and 8 are wrong. Scalar sub-queries can be used in WHEN conditions and START WITH and CONNECT BY clauses. (At least in Oracle 10.2. Is the book based on some earlier version?)
Edited by: BluShadow on 17-Jan-2012 09:08

Urgent Group by Having Clause Fails in Oracle and Works in Sybase

Hello EveryBody I need to select curve data of curve whose date is maximum in that curve so say if i ahve
so if records are
curveid curvename curvedate
1001 test1 12/12/1003
1001 test1 12/13/1003
1002 test2 12/12/2002
1002 test2 12/12/2004
I have query which run well in sybase but oracle screw up...My logic say having clause is use to filter the records of group so it should have worked in oracle.....
Here is query
select curveid,curvename from curve group by curveid having curvedate =max(curve_date)
This give "not a Group by " error in oracle....It work well in sybase...
ORA-00979: not a GROUP BY expression
I have query which use subquery to select these records but i don't want that to use that query
Please help

please understand what I need the result
for each curve i need that data of that curve who date is max in that curve group
so say for 1001 there are two date 1/1/2001 and 1/1/2002
I need the data of curve 1001 with date 1/1/2002
Oracle should have some alternative solution for this....
If i have to use subquery I do have subquery
select a.curveid, b.curvename from curve a group by curveid having curvedate = (select max(curvedate) from curve where a.curveid=b.curveid group by curveid );
I don't want to use that ,,,
I want to solve my probelm using having and group/....
Main purpose of having is to filter the records from group result so IT SHOULD DO THAT WHY ORACLE GIVE ORA ERROR FOR
group by curve_id having curve_date=max(curve_date)
Creators of oracle please reply

Subquery in the HAVING Clause

Hello all,
i'm getting error when i try to write sub query in having clause. check out my query
select ROUND( Count( distinct Sales2011_DIVDPTA.DIVDPTA_Item_Dept ),0) AS "F1" , ROUND( Count( Sales2011.Sales2011_DG1.Item_Season ),0) AS "F2"
from Sales2011.Sales2011_JT
INNER JOIN Sales2011.Sales2011_DG1 On Sales2011.Sales2011_DG1.DG1_ID =Sales2011.Sales2011_JT.DG1_ID
LEFT JOIN Sales2011.Sales2011_DIVDPTA On nvl(Sales2011.Sales2011_DIVDPTA.DIVDPTA_ITEM_DIVISION,' ')=nvl(Sales2011.Sales2011_DG1.Item_Division,' ')
AND nvl(Sales2011.Sales2011_DIVDPTA.DIVDPTA_ITEM_DEPT,' ')=nvl(Sales2011.Sales2011_DG1.Item_Dept,' ')
having ( ROUND( Count( Sales2011.Sales2011_DG1.Item_Season ),0)     in ( 0)
But it is not executed if I use the sub query in having clause
select ROUND( Count( distinct Sales2011_DIVDPTA.DIVDPTA_Item_Dept ),0) AS "F1" , ROUND( Count( Sales2011.Sales2011_DG1.Item_Season ),0) AS "F2"
from Sales2011.Sales2011_JT
INNER JOIN Sales2011.Sales2011_DG1 On Sales2011.Sales2011_DG1.DG1_ID =Sales2011.Sales2011_JT.DG1_ID
LEFT JOIN Sales2011.Sales2011_DIVDPTA On nvl(Sales2011.Sales2011_DIVDPTA.DIVDPTA_ITEM_DIVISION,' ')=nvl(Sales2011.Sales2011_DG1.Item_Division,' ')
AND nvl(Sales2011.Sales2011_DIVDPTA.DIVDPTA_ITEM_DEPT,' ')=nvl(Sales2011.Sales2011_DG1.Item_Dept,' ')
having ( ROUND( Count( Sales2011.Sales2011_DG1.Item_Season ),0)
in ( select   ROUND( Count(
Sales2011.Sales2011_DG1.Item_Season ),0) from    Sales2011.Sales2011_DG1 )
Error at Command Line:1 Column:0
Error report:
SQL Error: ORA-00979: not a GROUP BY expression
00979. 00000 - "not a GROUP BY expression"
*Cause:
*Action:any help ???

Sorry unintentionally i have posted my question here.
will you please elaborate this? Becoz i'm not using group by clause in both query. First query run successfully but as i put sub query in having clause it raised an error. will you tell where i'm committing mistake?
Aggregates in the HAVING clause do not need to appear in the SELECT list. If the HAVING clause contains a subquery, the subquery can refer to the outer query block if and only if it refers to a grouping column.Edited by: Oracle Studnet on Aug 14, 2011 11:28 PM

Which two statements are true about WHERE and HAVING clause ?

Which two statements are true about WHERE and HAVING clause ?
1. WHERE clause can be used to restict rows only
2.HAVING clause can be used to restrict groups only
3.HAVING clause can be used to restrict groups and rows
Plz help me in dis ques...which two will be correct...i think its 1 and 2...but not sure.

863180 wrote:
Plz help me in dis ques...which two will be correct...i think its 1 and 2...but not sure.If you are not sure then you do not fully understand HAVING.
SY.

Use of Where and having clause

Hi all,
I always have a doubt about use of HAVING and WHERE clause,
suppose I have table T1 with only one column C1
CREATE TABLE T1
(C1 VARCHAR2(1) );
which having data by following INSERT scripts
INSERT INTO T1 VALUES('A');
INSERT INTO T1 VALUES('B');
INSERT INTO T1 VALUES('C');
INSERT INTO T1 VALUES('A');
INSERT INTO T1 VALUES('B');
INSERT INTO T1 VALUES('A');
Now I want result as follows
C1 ==== COUNT(C1)
==============
B ===== 2
A ===== 3
So out of query 1 and 2 which approach is right ?
1) SELECT C1,COUNT(C1) FROM T1
WHERE C1<>'C'
GROUP BY C1
ORDER BY C1 DESC;
2) SELECT C1,COUNT(C1) FROM T1
GROUP BY C1
HAVING C1<>'C'
ORDER BY C1 DESC;
Edited by: user13306874 on Jun 21, 2010 2:36 AM

In SQL, it's always best to filter data at the earliest moment possible.
In your example the WHERE clause would be that moment:
SQL> explain plan for
2 select c1,count(c1)
3 from t1
4 where c1 != 'C'
5 group by c1
6* order by c1 desc;
Explained.
SQL> select * from table(dbms_xplan.display);
PLAN_TABLE_OUTPUT
Plan hash value: 3946799371
| Id | Operation          | Name | Rows | Bytes |
|   0 | SELECT STATEMENT   |      |     5 |    10 |
|   1 | SORT GROUP BY     |      |     5 |    10 |
|* 2 |   TABLE ACCESS FULL| T1   |     5 |    10 |
Predicate Information (identified by operation id):
   2 - filter("C1"!='C')
18 rows selected.
SQL>As you can see the filter is applied during the scan of T1.
Whereas in the HAVING case:
SQL> explain plan for
2 select c1,count(c1)
3 from t1
4 group by c1
5 having c1 != 'C'
6* order by c1 desc;
Explained.
SQL> select * from table(dbms_xplan.display);
PLAN_TABLE_OUTPUT
Plan hash value: 3146800528
| Id | Operation           | Name | Rows | Bytes |
|   0 | SELECT STATEMENT    |      |     6 |    12 |
|* 1 | FILTER             |      |       |       |
|   2 |   SORT GROUP BY     |      |     6 |    12 |
|   3 |    TABLE ACCESS FULL| T1   |     6 |    12 |
Predicate Information (identified by operation id):
   1 - filter("C1"!='C')
18 rows selected.
SQL>The scan is done after all groups have been computed: one of which was computed in vain, since it will be filtered away due to the HAVING clause.
In general I would use as a guideline: if you are not using aggregate functions in your HAVING clause predicate, then move that predicate to the WHERE portion of your query.
Edited by: Toon Koppelaars on Jun 21, 2010 11:54 AM

Use of group by and having clause

hi frnds
can anybody explain me the use of group by an having clause in select state ment

Hi Rohit,
1. GROUP BY f1 ... fn
2. GROUP BY (itab)
1. GROUP BY f1 ... fn
Effect
Groups database table data in a SELECT command on one line in the result set. A group is a set of lines which all have the same values in each column determined by the field descriptors f1 ... fn.
... GROUP BY f1 ... fn always requires a list in the SELECT clause. If you use field descriptors without an aggregate funciton in the SELECT clause, you must list them in the GROUP BY f1 ... fn clause.
Example
Output the number of passengers, the total weight and the average weight of luggage for all Lufthansa flights on 28.02.1995:
TABLES SBOOK.
DATA: COUNT TYPE I, SUM TYPE P DECIMALS 2, AVG TYPE F.
DATA: CONNID LIKE SBOOK-CONNID.
SELECT CONNID COUNT( * ) SUM( LUGGWEIGHT ) AVG( LUGGWEIGHT )
       INTO (CONNID, COUNT, SUM, AVG)
       FROM SBOOK
       WHERE
         CARRID   = 'LH'       AND
         FLDATE   = '19950228'
       GROUP BY CONNID.
WRITE: / CONNID, COUNT, SUM, AVG.
ENDSELECT.
Note
... GROUP BY f1 ... fn is not supported for pooled and cluster tables.
2. GROUP BY (itab)
Effect
Works like GROUP BY f1 ... fn if the internal table itab contains the list f1 ... fn as ABAP source code. The internal table itab can only have one field. This field must be of the type C and should not be more than 72 characters long. itab must be enclosed in parentheses and there should be no blanks between the parentheses and the table name.
Note
The same restrictions apply to this variant as to GROUP BY f1 ... fn.
Example
Output all Lufthansa departure points with the number of destinations:
TABLES: SPFLI.
DATA:   BEGIN OF WA.
          INCLUDE STRUCTURE SPFLI.
DATA:     COUNT TYPE I.
DATA:   END OF WA.
DATA:   WA_TAB(72) TYPE C,
        GTAB LIKE TABLE OF WA_TAB,
        FTAB LIKE TABLE OF WA_TAB,
        COUNT TYPE I.
CLEAR: GTAB, FTAB.
WA_TAB = 'COTYFROM COUNT( * ) AS COUNT'. APPEND FTAB.
APPEND WA_TAB TO FTAB.
WA_TAB = 'CITYFROM'.
APPEND WA_TAB TO GTAB.
SELECT DISTINCT (FTAB)
       INTO CORRESPONDING FIELDS OF WA
       FROM SPFLI
       WHERE
         CARRID   = 'LH'
       GROUP BY (GTAB).
WRITE: / WA-CITYFROM, WA-COUNT.
ENDSELECT.
Regards,
Susmitha

Group by clause and having clause in select

hi frnds
plz give me some information of group by and having clause used in select statement with example
thanks

The Open SQL statement for reading data from database tables is:
SELECT      <result>
INTO      <target>
FROM      <source>
[WHERE    <condition>]
[GROUP BY <fields>]
[HAVING   <cond>]
[ORDER BY <fields>].
The SELECT statement is divided into a series of simple clauses, each of which has a different part to play in selecting, placing, and arranging the data from the database.
You can only use the HAVING clause in conjunction with the GROUP BY clause.
To select line groups, use:
SELECT <lines> <s1> [AS <a1>] <s2> [AS <a2>] ...
               <agg> <sm> [AS <am>] <agg> <sn> [AS <an>] ...
       GROUP BY <s1> <s2> ....
       HAVING <cond>.
The conditions <cond> that you can use in the HAVING clause are the same as those in the SELECT clause, with the restrictions that you can only use columns from the SELECT clause, and not all of the columns from the database tables in the FROM clause. If you use an invalid column, a runtime error results.
On the other hand, you can enter aggregate expressions for all columns read from the database table that do not appear in the GROUP BY clause. This means that you can use aggregate expressions, even if they do not appear in the SELECT clause. You cannot use aggregate expressions in the conditions in the WHERE clause.
As in the WHERE clause, you can specify the conditions in the HAVING clause as the contents of an internal table with line type C and length 72.
Example
DATA WA TYPE SFLIGHT.
SELECT   CONNID
INTO     WA-CONNID
FROM     SFLIGHT
WHERE    CARRID = 'LH'
GROUP BY CONNID
HAVING   SUM( SEATSOCC ) > 300.
WRITE: / WA-CARRID, WA-CONNID.
ENDSELECT.
This example selects groups of lines from database table SFLIGHT with the value LH for CARRID and identical values of CONNID. The groups are then restricted further by the condition that the sum of the contents of the column SEATSOCC for a group must be greater than 300.
The <b>GROUP BY</b> clause summarizes several lines from the database table into a single line of the selection.
The GROUP BY clause allows you to summarize lines that have the same content in particular columns. Aggregate functions are applied to the other columns. You can specify the columns in the GROUP BY clause either statically or dynamically.
Specifying Columns Statically
To specify the columns in the GROUP BY clause statically, use:
SELECT <lines> <s1> [AS <a 1>] <s 2> [AS <a 2>] ...
               <agg> <sm> [AS <a m>] <agg> <s n> [AS <a n>] ...
       GROUP BY <s1> <s 2> ....
To use the GROUP BY clause, you must specify all of the relevant columns in the SELECT clause. In the GROUP BY clause, you list the field names of the columns whose contents must be the same. You can only use the field names as they appear in the database table. Alias names from the SELECT clause are not allowed.
All columns of the SELECT clause that are not listed in the GROUP BY clause must be included in aggregate functions. This defines how the contents of these columns is calculated when the lines are summarized.
Specifying Columns Dynamically
To specify the columns in the GROUP BY clause dynamically, use:
... GROUP BY (<itab>) ...
where <itab> is an internal table with line type C and maximum length 72 characters containing the column names <s 1 > <s 2 > .....
Example
DATA: CARRID TYPE SFLIGHT-CARRID,
      MINIMUM TYPE P DECIMALS 2,
      MAXIMUM TYPE P DECIMALS 2.
SELECT   CARRID MIN( PRICE ) MAX( PRICE )
INTO     (CARRID, MINIMUM, MAXIMUM)
FROM     SFLIGHT
GROUP BY CARRID.
WRITE: / CARRID, MINIMUM, MAXIMUM.
ENDSELECT.
regards
vinod

Select stmts with Having Clause

Hi,
Can some body help me to improve the performance of the below query...
select t.seq_no,t.contract_id,t.date_from from test_plan_tab t
group by t.seq_no,t.contract_id,t.date_from
having (select count(*)
from test_plan_tab p
where p.contract_id = t.contract_id
and p.date_from = t.date_from) > 1
The having clause will reduce the performance of the above query I guess...
Thanks And Best Regards,
/Dinesh...

If Seq_no is unique then try this
SELECT MIN(t.seq_no),contract_id,t.date_from,count(*) from test_plan_tab t
group by t.contract_id,t.date_from
HAVING COUNT(*) > 1or
you can try as fsitja said, but you can omit the group by as the partition has already been done on grouping columns
SELECT seq_no, contract_id, date_from
FROM (SELECT t.seq_no, t.contract_id, t.date_from, COUNT(*) over(PARTITION BY contract_id, date_from) tot
FROM test_plan_tab t)
WHERE tot > 1Regards,
Prazy

Where clause and order by to DAO classes

Hi
Is it ok(I mean design wise) to pass the 'where clause' conditions and order by clause as a parameter to the method of DAO class?

Well, I would suggest you write seperate methods in your dao , one to select data without the where clause and one to select data with the where clause thrown in. If you have different 'where' clauses for selecting different kinds of data, have that many dao methods. The dao methods being specific know exactly what is the data that's coming in.
Lets assume you have a list of purchase orders and each purchase order is indetified by a unique id called PURCHASE_ORDER_ID.
1. The following code would populate a purchase order's details given an id.
private statis final String QUERY_1 = "select * from PURCHASE_ORDERS where PURCHASE_ORDER_ID = ? ";
PurchaseOrderModel getPurchaseOrderData(long poId){
     //get a prepared statement from your connection
     PreparedStatement pst = conn.prepareStatement(QUERY_1);
     //set the poId passed as params to your query
     pst.setLong(1, poId);
     ResultSet rs = pst.executeQuery();
     if(rs.next()){
          //populate data into a model
     finally{
          //clean up resources
     return model;
}2. The following code would return a list of PurchaseOrderModel's whose shipping date falls between a set of dates selected by the user.
private statis final String QUERY_2 = "select * from PURCHASE_ORDERS where SHIPPING_DATE between ? and ? ";
PurchaseOrderModel getPurchaseOrdersBetweenDates(list bindValues){
     //get a prepared statement from your connection
     PreparedStatement pst = conn.prepareStatement(QUERY_1);
     //set the dates passed as params to your query
     //we know that the List ought to contain only 2 dates
     pst.setDate(1, (Date)bindValues.get(0));
     pst.setDate(2, (Date)bindValues.get(1));
     ResultSet rs = pst.executeQuery();
     if(rs.next()){
          //iterate and populate data into a model
          //add model to a list
     finally{
          //clean up resources
     return list;
     3. This is more interesting - the dao method searches a list of Purchase Orders starting with a set of specific words. The words themselves may be one or many. This means that the number of '?' in your prepared statement may be dynamic. Each element of the list is a String that contains the start substring of a purcahse order name. For example - the list may contain elements like ["a", "ab", "c", "gh"] and the dao method returns all purchase order starting with these names.
private statis final String QUERY_3 = "select * from PURCHASE_ORDERS where ";
PurchaseOrderModel getPurchaseOrderNameMatches(list bindValues){
     //construct the query dynamically
     StringBuffer query = new StringBuffer(QUERY_3);
     int count = 0;
     for(Iterator itr = bindValues.iterator(); itr.hasNext();;){
          String value = (String)itr.next();
          query.append ("name like 'value%' ");
          if (count != 0 and (count+1 != bindValues.length)){
               query.append(" or ");
          count ++;
     //get a prepared statement from your connection
     PreparedStatement pst = conn.prepareStatement(query.toString());
     ResultSet rs = pst.executeQuery();
     if(rs.next()){
          //iterate and populate data into a model
          //add model to a list
     finally{
          //clean up resources
     return list;
To sum up,
1. You need as many methods as you have different kinds of searches (one method for each kind of 'where' clause).
2. The ejb/business layer would examine the data and decide on which method to call.
3. Increases coding effort, but makes the code clean and readable. Each layer does it's job. Thus we dont have ejbs forming 'where' clauses and so on.
Having said that, it really is your decision - you should take into consideration the following factors -
1. How big is the project ? If its a huge codebase developed by many people, then segregate the responsibilities clearly in each layer as I have outlined. For a small scale project, you could go with your approach.
2. Whats the take on maintenance and future add-ons ? Do you see the codebase growing with time ?
3. Is your project a commercial one - is it a product that needs to be maintained or is it a one-off development - develop once and you are done with it.
4. What are the design considerations ? Is somebody going to audit code for quality ? Or is it a academic one ?
You should take into account all these before deciding to go one way or the other.
A general thumb rule should be that you should be convinced that your code readable (maintainable), scalable and efficient. Anything that you do towards these ends is good code/design despite what people/books/patterns say, IMO.
cheers,
ram.

Having clause with Analytic function

can you pls let me know if we can use HAVING clause with analytic function
select eid,empno,sum(sal) over(partition by year)
from employee
where dept = 'SALES'
having sum(sal) > 10000I m getting error while using the above,
IS that we can use HAVING clause with partition by
Thanks in advance

Your having clause isn't using an analytical function, is using a regular aggregate function.
You also can't use analytical functions in the where clause or having clause like that as they are windowing functions and belong at the top of the query.
You would have to wrap the query to achieve what you want e.g.
SQL> ed
Wrote file afiedt.buf
1 select deptno, total_sal
2 from (
3        select deptno,sum(sal) over (partition by deptno) as total_sal
4        from   emp
5       )
6 group by deptno, total_sal
7* having total_sal > 10000
SQL> /
    DEPTNO TOTAL_SAL
        20      10875
SQL>

How can user specify HAVING clause in Interactive Report

How can user specify HAVING clause in Interactive Report after making the group by selection? Under Actions/Format, the user sees just the Group By-Sort and Group By options.

Hi ,
Thanks for your information.
I am new to the APEX.*i need to show Progress bar while opening the each page* then user can know some process is happening from the backside and i don't know where i need to add and call the below function.could you please provide the steps for the progress bar.
In my application there are almost 100 pages are there so, i need to show progress bar on each page while opening .could you please provide Global function to call on each page.
function html_url_Progress(pThis){
$x_Show('AjaxLoading');
window.setTimeout('$s("AjaxLoading",$x("AjaxLoading").innerHTML)', 100);
//doSubmit('APPLY_CHANGES');
redirect(pUrl);
Regards
Narender B

HAVING clause, or ORDER BY clause ....ERROR

hi i have following query which throws error plz find the solution for the query to go safe..
Select C.src_cd,
D.src_nm,
count(*) supp_clm_count,
(CASE WHEN A.clm_ttladjamt > 0 then A.clm_ttladjamt else A.clm_ttlreqamt END) as amount
From IWOWNER.WC_clm A,
IWOWNER.WC_clm_srvc B,
SHOWNER.WC_SRC C,
SHOWNER.WC_SRC_lang D
where A.clm_id = B.clm_id
and A.rcv_loc_id = C.src_id
and C.src_id = D.src_id
and TRANSLATE(A.clm_rqst_type_cd) = 'SUPPLIERCLAIM'
and TRANSLATE(A.clm_typ_cd) in ('WARRANTY','PRE-DELIVERY')
and DATE(A.clm_create_dt) between '01/01/2000' and '01/01/2010'
Group by C.src_cd, D.src_nm
ERROR:
SQLSTATE: 42803, SQLERRMC: CLM_TTLADJAMT
Message: An expression starting with "CLM_TTLADJAMT" specified in a SELECT clause, HAVING clause, or ORDER BY clause is not specified in the GROUP BY clause or it is in a SELECT clause, HAVING clause, or ORDER BY clause with a column function and no GROUP BY clause is specified

Hi,
With analytic function
/* Formatted on 2009/07/22 10:47 (Formatter Plus v4.8.8) */
SELECT DISTINCT c.src_cd, d.src_nm,
                COUNT (1) OVER (PARTITION BY c.src_cd, d.src_nm)
                                                               supp_clm_count,
                SUM (CASE
                        WHEN a.clm_ttladjamt > 0
                           THEN a.clm_ttladjamt
                        ELSE a.clm_ttlreqamt
                     END
                    ) OVER (PARTITION BY c.src_cd, d.src_nm) AS amount
           FROM iwowner.wc_clm a,
                iwowner.wc_clm_srvc b,
                showner.wc_src c,
                showner.wc_src_lang d
          WHERE a.clm_id = b.clm_id
            AND a.rcv_loc_id = c.src_id
            AND c.src_id = d.src_id
            AND a.clm_rqst_type_cd = 'SUPPLIERCLAIM'
            AND a.clm_typ_cd IN ('WARRANTY', 'PRE-DELIVERY')
            AND a.clm_create_dt BETWEEN TO_DATE ('01/01/2000', 'dd/mm/yyyy')
                                    AND TO_DATE ('01/01/2010', 'dd/mm/yyyy')

Group By -- Having Clause related doubt.

Hello,
Can we Write/Use rather a 'Having Condition' Before a Group by Clause ..?
If Yes then How does it Work.. I mean a 'Having' is a WHERE clause (filter) on Aggregate results ...
SO how does Having works before grouping the Results..??

Hi,
Aijaz Mallick wrote:
Hello,
Can we Write/Use rather a 'Having Condition' Before a Group by Clause ..?What happens when you try it?
If Yes then How does it Work.. I mean a 'Having' is a WHERE clause (filter) on Aggregate results ... Right; the HAVING clause is like another WHERE clause.
The WHERE clause is applied before the GROUP BY is done, and the aggregate functions are computed.
The HAVING clause is applied after the GROUP BY is done, and the aggregate functions are computed, so you can use aggregate functions in the HAVING clause.
SO how does Having works before grouping the Results..??The order in which clauses appear in your code isn't necessarily the order in which they are performed. For example,
SELECT    job
,         COUNT (*) AS cnt
FROM      scott.emp
GROUP BY job;Does it confuse you that this query can reference COUNT (*) in the SLECT clause, which is before the GROUP BY clause?
The SELECT clause which always comes before the GROUP BY clause in code. That does not mean that the SELECT clause is completed before the GROUP BY clause is begun.
If the documentation says that clauses must be in a certain order, then use that order, even if your current version of Oracle allows them to be in a different order. There's no guarantee that the next version of Oracle will allow something that was always said to be wrong.

Having clause and subquery

Similar Messages

Maybe you are looking for