Simple query-strange output

Hi all,
I have a table x having some data.
if I do,
select * from x where dt='31-OCT-08';
It retrieves the data.
But if do
select * from x where dt=last_day(sysdate);
it retrieves nothing.
Why is that so?
Last_day(sysdate)='31-OCT-08'

MYH wrote:
Why is that so?
Last_day(sysdate)='31-OCT-08'Wrong!
Last_day(sysdate) >'31-OCT-08'
Boneist already gave the correct answer. Sysdate has a time component. THis time component is still there after you used the last_day function.
You can check it for yourself by simply testing this condition.
Proof
SQL*Plus: Release 9.2.0.2.0 - Production on Wed Oct 22 12:59:22 2008
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> select * from dual
2 where Last_day(sysdate)='31-OCT-08';
no rows selected
SQL>
SQL> select * from dual
2 where Last_day(sysdate)>'31-OCT-08';
D
X
SQL> While the point with the datatypes is important it is not the real reason for this behaviour.
Edited by: Sven W. on Oct 22, 2008 1:02 PM

Similar Messages

How to write a simple query.

I have a table where I have data shown below. Now, I want to write a simple query which lists me the project and the count of the distinct effective dates for which data is existant there.
Sample data:
Project Task Effective Date (xx_proj_task_data)
101 T1 01-Jan-2008
101 T1 01-Feb-2008
101 T1 01-Mar-2008
101 T2 01-Jan-2008
101 T2 01-Apr-2008
101 T3 01-Apr-2008
102 T1 01-Jan-2008
102 T1 01-Feb-2008
102 T2 01-Apr-2008
103 T1 01-Jan-2008
103 T1 01-Feb-2008
103 T1 01-Mar-2008
103 T1 01-Apr-2008
103 T2 01-May-2008
103 T3 01-Jun-2008
103 T1 01-Jan-2008
103 T1 01-Aug-2008
103 T2 01-Apr-2008
Output Reqd:
Project Count(Distinct Effective Dates)
101 4
102 3
103 7
I can write a query that says:
select project_id, count(1)
from (select distinct project_id, effective_date
from xx_proj_task_data) x
group by project_id;
But, is there a way I can achieve the same by avoiding the inner Query (x) and just by a simple query ?
Thanks!

Try below query:
select project_id
, count(distinct effective_date)
from xx_proj_task_data
group by project_id;
--venkata

Simple Query in Oracle Linked Table in MS Access causes full table scan.

I am running a very simple query in MS ACCESS to a linked Oracle table as follows:
Select *
From EXPRESS_SERVICE_EVENTS --(the linked table name refers to EXPRESS.SERVICE_EVENTS)
Where performed > MyDate()
or
Select *
From EXPRESS_SERVICE_EVENTS --(the linked table name refers to EXPRESS.SERVICE_EVENTS)
Where performed > [Forms]![MyForm]![Date1]
We have over 50 machines and this query runs fine on over half of these, using an Oracle Index on the "performed" field. Running exactly the same thing on the other machines causes a full table scan, therefore ignoring the Index (all machines access the same Access DB).
Strangely, if we write the query as follows:
Select *
From EXPRESS_SERVICE_EVENTS
Where performed > #09/04/2009 08:00#
it works fast everywhere!
Any help on this 'phenominon' would be appreciated.
Things we've done:
Checked regional settings, ODBC driver settings, MS Access settings (as in Tools->Options), we have the latest XP and Office service packs, and re-linked all Access Tables on both the slow and fast machines independantly).

Primarily, thanks gdarling for your reply. This solved our problem.
Just a small note to those who may be using this thread.
Although this might not be the reason, my PC had Oracle 9iR2 installed with Administratiev Tools, where user machines had the same thing installed but using Runtime Installation. For some reason, my PC did not have 'bind date' etc. as an option in the workarounds, but user machines did have this workaround option. Strangely, although I did not have the option, my (ODBC) query was running as expected, but user queries were not.
When we set the workaround checkbox accordingly, the queries then run as expected (fast).
Once again,
Thanks

Trying to optimize this simple query

Hi,
I am trying to optimize this simple query but the two methods I am trying actually make things worse.
The original query is:
SELECT customer_number, customer_name
FROM bsc_pdt_account_mv
where rownum <= 100
AND Upper(customer_name) like '%SP%'
AND customer_id IN
SELECT cust_id FROM bsc_pdt_assoc_sales_force_mv
WHERE area_identifier IN (
SELECT area_identifier FROM bsc_pdt_assoc_sales_force_mv
WHERE ad_identifier = '90004918' or rm_identifier = '90004918' or tm_identifier = '90004918'
The result set of this query returns me the first 100 rows in 88 seconds and they are all distinct by default (don't know why they are distinct).
My first attempt was to try to use table joins instead of the IN conditions:
SELECT
distinct -- A: I need to use distinct now
customer_number, customer_name
FROM bsc_pdt_account_mv pdt,
bsc_pdt_assoc_sales_force_mv asf,
SELECT distinct area_identifier FROM bsc_pdt_assoc_sales_force_mv
WHERE ad_identifier = '90004918' or rm_identifier = '90004918' or tm_identifier = '90004918'
) area
where
area.area_identifier = asf.area_identifier
AND asf.cust_id = pdt.customer_id
AND Upper(customer_name) like '%SP%'
AND rownum <= 100 -- B: strange when I comment this out
order by 1
I dont understand two things with this query. First issue, I now need to put in the distinct because the result set is not distinct by default. Second issue (very strange), when I put the rownum condition (<100) I get two rows in 1.5 seconds. If I remove the condition, I get 354 rows (whole result set) in 326 seconds.
My second attempt was to use EXISTS instead of IN:
SELECT
customer_number, customer_name
FROM bsc_pdt_account_mv pdt
where Upper(customer_name) like '%SP%'
AND rownum <= 100
AND EXISTS
select 1 from
bsc_pdt_assoc_sales_force_mv asf,
SELECT distinct area_identifier FROM bsc_pdt_assoc_sales_force_mv
WHERE ad_identifier = '90004918' or rm_identifier = '90004918' or tm_identifier = '90004918'
) area
where
area.area_identifier = asf.area_identifier
AND asf.cust_id = pdt.customer_id
This query returns a similar distinct result set as teh original one but takes pretty much the same time (87 seconds).

The query below hangs when run in TOAD or PL/SQL Dev. I noticed there is no rows returned from the inner table for this condition.
SELECT customer_number, customer_name
FROM
bsc_pdt_account_mv pdt_account
where rownum <= 100
AND exists (
SELECT pdt_sales_force.cust_id
FROM bsc_pdt_assoc_sales_force_mv pdt_sales_force
WHERE pdt_account.customer_id = pdt_sales_force.cust_id
AND (pdt_sales_force.rm_identifier = '90007761' or pdt_sales_force.tm_identifier = '90007761') )
ORDER BY customer_name
-- No rows returned by this query
SELECT pdt_sales_force.cust_id
FROM bsc_pdt_assoc_sales_force_mv pdt_sales_force
WHERE pdt_sales_force.rm_identifier = '90007761' or pdt_sales_force.tm_identifier = '90007761'

Help! no response when doing SIMPLE query!

I meet a strange problem when I do a SIMPLE query on a table in Oracle 8.1.7, just like:
SELECT id FROM person WHERE id='12345';
Most of id values are ok to the query, except some values.
Whether I use these values in sqlplus or JDBC, mostly, no response is returned!! And I find the session in Oracle always keeps the status 'Active'. But in few scenario I can get the result quickly.
I don't know the reason. Help me please!
Thanks a lot!
Meyor

I'm not sure if the 'id' column contains something else.
When I shutdown and restart the database, the problem seems to be "solved". If the problem reoccurs again, I will try to use xTRIM functions.
Thanks!
Meyor

Simple Query : Unable to execute

Hi ALL,
I need wnat to extract records from a table where its ID records doesnt match with other Tbale ID values..
TABLEA
ID,NAME
1,A
2,B
TABLEB
ID,AGE
1,60
Now in SQL I can write query as
select TABLEA.ID from TABLEA,TABLEB where TABLEA.ID<>TABLEB.ID
and I can get out as
ID
2
How can I get this in DS??? I am struggleing.. may be its simple ....can any one throw some light?
Thanks
Rajeev

Sorry, I misread your issue and thought you wanted the records where the IDs DID match.
Ok, I know of two options, both quite simple, and both require two steps (two queries):
Option 1) Outer join Tables A and B in a query, with Table A as outer table and B as inner, with join condition A.ID=B.ID. Then map across the fields you want for your target plus the ID from table B, but rename it on the output schema as 'ID_B'. Now because this is an outer join the result will be all records from table A with the ID_B value being populated if there was a matching ID in Table B, and if not then it will be NULL. So then link this query output to a second query and just use the filter WHERE ID_B IS NULL (and you don't need to map the ID_B column to the output as you don't need it anymore). So the second query's output is all the records from Table A that did not have a matching ID in Table B.
If your volume of data is high then I only recommend this option if both tables are in the same datastore (i.e. if the outer join can be pushed down to the database).
Option 2) In the first query link only Table A as the source, then map across all the columns from table A and then create a new function output column called 'ID_B' with a lookup or lookup_ext function which simply performs a lookup of the Table A ID in table B, returning the ID from table B if the lookup finds a match, otherwise NULL. Then similarly in a second query you filter the records where ID_B value IS NULL (i.e. the lookup DID NOT find a match).
This option is probably going to perform better for high data volumes because Table B can be cached if it can fit into available memory, as you probably know you can choose from different caching options in the lookup function. The default option should be fine unless Table B is huge and your memory is low - check the reference guide.

Spool file problem,Can't see the query in output file.

Hello ,
I am facing a very old school kind of problem .....about spool file ....
The scenario -
I have made a script by name DB_Status_checkup.sql which i want to fire on the database to check the database status. In this script their are many queries regarding the data dictionary views to know about the database. It consist of nearly 25-30 different select queries..
The problem is i want to make a spool file of the output of that query....i want to see the SQL query & the output below in the spool file, so it will be easy for me to judge the result. But i can't see the SQL query , i can only see the output , & in so many queries it all gets jumbled up....even i can't understand where the next output starts ...
Sample of my SQL Script ....
clear buffer
spool D:\DB_status.txt
/*To check the database startup time*/
Select to_char(startup_time, 'HH24:MI DD-MON-YY') "Startup time"
from v$instance
.........next query n so on....
spool off;
In the output pf the spool file at D:\db_status.txt..
Startup time
08:25 16-JUL-10It shows only the output of the query in the spool file not the query,
What should i do to get the SQL query as well as the output of that query just below it in the spool file ???
Please suggest if you have anymore ideas , regarding this .....
ORACLE 10g R2
Windows Server 2008
Thanks in advance ...

Why don't you just use database control, instead of re-inventing the wheel?
Apart from that, SQL*Plus has it's own reference manual, which you apparently refuse to read.
The answer to your quiz/doc question is
set echo on
Sybrand Bakker
Senior Oracle DBA

Error in the simple Query

Dear Experts,
Not able to Execute this simple query :
Select T1.JobID , T1.BudgetValue,T1.ActualValue FROM [dbo].[Enprise_JobCost_ActualBudgetView] T1 WHERE T1.TransType = '[%0]'
Regards

Hello,
View - A View in simple terms is a subset of a 'virtual table. It can be used to retrieve data from the tables, Insert, Update or Delete from the tables. The Results of using View are not permanently stored in the database.
Stored Procedure - A stored procedure is a group of SQL statements which can be stored into the database and can be shared over the netwrok with different users.
http://www.geekinterview.com/question_details/65914
Better make a UDT for your requirement.
Thanks
Manvendra Singh Niranjan

Simple Query working on 10G and not working on 11gR2 after upgrade

Hi Folks,
This is the first time i am posting the query in this Blog.
I have a small issue which preventing the UAT Sigoff.
Simple query working fine on 10.2.0.1 and after upgrade to 11.2.0.1 its error out
10.2.0.4:
=====
SQL> SELECT COUNT(*) FROM APPS.HZ_PARTIES HP WHERE ATTRIBUTE_CATEGORY= 'PROPERTY' AND ATTRIBUTE1=1;
COUNT(*)
1
SQL> SELECT COUNT(*) FROM APPS.HZ_PARTIES HP WHERE ATTRIBUTE_CATEGORY= 'PROPERTY' AND ATTRIBUTE1=00001;
COUNT(*)
1
SQL> select ATTRIBUTE1 FROM APPS.HZ_PARTIES HP WHERE ATTRIBUTE_CATEGORY= 'PROPERTY' AND ATTRIBUTE1=1;
ATTRIBUTE1
00001
11.2.0.1:
=====
SQL> SELECT COUNT(*) FROM APPS.HZ_PARTIES HP WHERE ATTRIBUTE_CATEGORY= 'PROPERTY' AND ATTRIBUTE1=1
ERROR at line 1:
ORA-01722: invalid number
SQL> SELECT COUNT(*) FROM APPS.HZ_PARTIES HP WHERE ATTRIBUTE_CATEGORY= 'PROPERTY' AND ATTRIBUTE1=00001
ERROR at line 1:
ORA-01722: invalid number
SQL> select ATTRIBUTE1 FROM APPS.HZ_PARTIES HP WHERE ATTRIBUTE_CATEGORY= 'PROPERTY' AND ATTRIBUTE1='1';
no rows selected
SQL> SELECT COUNT(*) FROM APPS.HZ_PARTIES HP WHERE ATTRIBUTE_CATEGORY= 'PROPERTY' AND ATTRIBUTE1='00001';
COUNT(*)
1
SQL> select ATTRIBUTE1 FROM APPS.HZ_PARTIES HP WHERE ATTRIBUTE_CATEGORY= 'PROPERTY' AND ATTRIBUTE1='00001';
ATTRIBUTE1
00001
++++++++++++++++++++++++++++++++++++++++++++++
SQL > desc APPS.HZ_PARTIES
Name Type
======== ======
ATTRIBUTE1 VARCHAR2(150)
++++++++++++++++++++++++++++++++++++++++++++++
Changes:
Recently i upgraded the DB from 10.2.0.4 to 11.2.0.1
Query:
1.If the type of that row is VARCHAR,why it is working in 10.2.0.4 and why not working in 11.2.0.1
2.after upgrade i analyzed the table with "analyze table " query for all AP,AR,GL,HR,BEN,APPS Schemas--Is it got impact if we run analyze table.
Please provide me the answer for above two questions or refer the document is also well enough to understand.Based on the Answer client will sigoff to-day.
Thanks,
P Kumar

WhiteHat wrote:
the issue has already been identified: in oracle versions prior to 11, there was an implicit conversion of numbers to characters. your database has a character field which you are attempting to compare to a number.
i.e. the string '000001' is not in any way equivalent to the number 1. but Oracle 10 converts '000001' to a number because you are asking it to compare to the number you have provided.
version 11 doesn't do this anymore (and rightly so).
the issue is with the bad code design. you can either: use characters in the predicate (where field = 'parameter') or you can do a conversion of the field prior to comparing (where to_num(field) = parameter).
I would suggest that you should fix your code and don't assume that '000001' = 1I don't think that the above is completely correct, and a simple demonstration will show why. First, a simple table on Oracle Database 10.2.0.4:
CREATE TABLE T1(C1 VARCHAR2(20));
INSERT INTO T1 VALUES ('1');
INSERT INTO T1 VALUES ('0001');
COMMIT;A select from the above table, relying on implicit data type conversion:
SELECT
FROM
T1
WHERE
C1=1;
C1
1
0001Technically, the second row should not have been returned as an exact match. Why was it returned, let's take a look at the actual execution plan:
SELECT
FROM
TABLE(DBMS_XPLAN.DISPLAY_CURSOR(NULL,NULL,NULL));
SQL_ID g6gvbpsgj1dvf, child number 0
SELECT   * FROM   T1 WHERE   C1=1
Plan hash value: 3617692013
| Id | Operation         | Name | Rows | Bytes | Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT |      |       |       |     2 (100)|          |
|* 1 | TABLE ACCESS FULL| T1   |     2 |    24 |     2   (0)| 00:00:01 |
Predicate Information (identified by operation id):
   1 - filter(TO_NUMBER("C1")=1)
Note
   - dynamic sampling used for this statementNotice that the VARCHAR2 column was converted to a NUMBER, so if there was any data in that column that could not be converted to a number (or NULL), we should receive an error (unless the bad rows are already removed due to another predicate in the WHERE clause). For example:
INSERT INTO T1 VALUES ('.0001.');
SELECT
FROM
T1
WHERE
C1=1;
SQL> SELECT
2    *
3 FROM
4    T1
5 WHERE
6    C1=1;
ERROR:
ORA-01722: invalid numberNow the same test on Oracle Database 11.1.0.7:
CREATE TABLE T1(C1 VARCHAR2(20));
INSERT INTO T1 VALUES ('1');
INSERT INTO T1 VALUES ('0001');
COMMIT;
SELECT
FROM
T1
WHERE
C1=1;
C1
1
0001
SELECT
FROM
TABLE(DBMS_XPLAN.DISPLAY_CURSOR(NULL,NULL,NULL));
SQL_ID g6gvbpsgj1dvf, child number 0
SELECT   * FROM   T1 WHERE   C1=1
Plan hash value: 3617692013
| Id | Operation         | Name | Rows | Bytes | Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT |      |       |       |     2 (100)|          |
|* 1 | TABLE ACCESS FULL| T1   |     2 |    24 |     2   (0)| 00:00:01 |
Predicate Information (identified by operation id):
   1 - filter(TO_NUMBER("C1")=1)
Note
   - dynamic sampling used for this statement
INSERT INTO T1 VALUES ('.0001.');
SELECT
FROM
T1
WHERE
C1=1;
SQL> SELECT
2    *
3 FROM
4    T1
5 WHERE
6    C1=1;
ERROR:
ORA-01722: invalid numberAs you can see, exactly the same actual execution plan, and the same end result.
The OP needs to determine if non-numeric data now exists in the column. Was the database characterset possibly changed during/after the upgrade?
Charles Hooper
Co-author of "Expert Oracle Practices: Oracle Database Administration from the Oak Table"
http://hoopercharles.wordpress.com/
IT Manager/Oracle DBA
K&M Machine-Fabricating, Inc.

Query in output of sh interface

Hi all,
I have a query in output of sh interface on ASA.
On ASA's when we do 'show interface' for a gig interface, we can get any among two,
input queue (blocks free curr/low): hardware (255/230)
output queue (blocks free curr/low): hardware (255/0)
OR
input queue (curr/max packets): hardware (0/7)
output queue (curr/max packets): hardware (0/13)
cur/low I suppose when we have underruns and overruns going on.
What i want to know is the meaning of the output. In case of curr/max its very clear.
input queue (curr/max packets): hardware (0/7)
output queue (curr/max packets): hardware (0/13)
Above means (correct me if I am incorrect), there are Zero packets currently in input queue, and 7 were the max packets seen at one time. For output queue, zero are the current packets in ouput queue and 13 were max that were seen in output queue. This is documented.
But I could not find an explaination for,
input queue (blocks free curr/low): hardware (255/230)
output queue (blocks free curr/low): hardware (255/0)
How should I interpret it? I need supporting documentaion please.
I have gone through this link :
http://www.cisco.com/en/US/docs/security/asa/asa84/command/reference/s3.html#wp1497263
But i couldn't find an explanation for blocks free current/low
Please explain me the following output:
2506116 packets input, 2624544574 bytes, 0 no buffer
       Received 0 broadcasts, 0 runts, 0 giants
       8036 input errors, 0 CRC, 0 frame, 8036 overrun, 0 ignored, 0 abort
       0 L2 decode drops
       5065834 packets output, 6024814558 bytes, 0 underruns
       0 pause output, 0 resume output
       0 output errors, 0 collisions, 0 interface resets
       0 late collisions, 0 deferred
       0 input reset drops, 0 output reset drops, 0 tx hangs
       input queue (blocks free curr/low): hardware (255/230)
       output queue (blocks free curr/low): hardware (254/0)

i am mainly concerned about
input queue (blocks free curr/low): hardware (255/230)
       output queue (blocks free curr/low): hardware (254/0)

A simple query to show sales versus last year on daily basis/

Hi guys,
I want to build a simple query with day (1,2,3,4,5,6) on the rows and "sales current year" and "sales last year"
on the columns.
I have only 0CALDAY in my cube.
How can I have on the rows the day in stead of the full date?
I would like to see in the sames row sales current year and sales last year.
Thanks
Shlomi

HI Shlomi
Create a virtual characteristic in your infoprovider that can calculate the day from calendar Day. In ZXRSRZZZ while adding code for this virtual characteristic use the function module DATE_COMPUTE_DAY to compute the day for every calendar day.
For calculating Sales Current year, create a restricted ky figure with Sales as the key figure. Add 0CalDay to this RKF and create a variable for this infoobject(Eg: ZCURYEAR) that will receive input from the user for the range of dates eg: 08/16/2009 - 08/22/2009.
For Sales Prior year, create another restricted key figure with Sales. Add 0CalDay to this RKF and add a customer exit variable. In the Customer exit code use the ZCURYEAR variable and offset it to prior year in both the upper and lower limits. This should work.
I hope this helps.
Thanks.

A simple query

a simple query
on plsql block
if i don't define the size of a variable of number type what will be the default size ?
declare
a number ;
begin
null
end;
and in a procedure if i don't mention in or out in the parameters what will oracle take it by default ?
create or replace procedure(a number,b number)
is
begin
null
end;
PLs note that both the pl/sql blocks are just for giving an idea .
regards
SHUBH

You can get such information from the documents.
[imp]The absence of precision and scale designators specifies the maximum range and precision for an Oracle number.[imp]
Cheers
Sarma.

Improving a simple Query

Following is a simple query, what i want to know, i have added upper select to get d.name which is the description of region_code. Can i get whole result with single select
SELECT t.region_code,d.name, t.emp_contr
FROM
(SELECT c.br_region_fo_code as Region_Code,
SUM(c.employer_contribution) AS emp_contr
FROM core_business.cb_contr_emp_pmt_slip c
GROUP BY c.br_region_fo_code ) t,
general_information.cb_region_fo d
WHERE t.br_region_fo_code = d.region_fo_code;

Boneist wrote:
malhi wrote:
Following is a simple query, what i want to know, i have added upper select to get d.name which is the description of region_code. Can i get whole result with single select
SELECT t.region_code,d.name, t.emp_contr
FROM
(SELECT c.br_region_fo_code as Region_Code,
SUM(c.employer_contribution) AS emp_contr
FROM core_business.cb_contr_emp_pmt_slip c
GROUP BY c.br_region_fo_code ) t,
general_information.cb_region_fo d
WHERE t.br_region_fo_code = d.region_fo_code;To be honest, I wouldn't bother rewriting the above query - it looks like it's filtering early (although Oracle could choose to rewrite it so that it does the join first, I guess), so that you're reducing the number of rows that the outer query has to join to. That means less work. If it is rewriting, I'd stick a no_merge hint on the subquery, to tell Oracle to do the grouping first before joining.
You could rewrite the above query as:
SELECT c.br_region_fo_code AS region_code,
d.name,
SUM(c.employer_contribution) AS emp_contr
FROM core_business.cb_contr_emp_pmt_slip c,
general_information.cb_region_fo d
WHERE t.br_region_fo_code = d.region_fo_code
GROUP BY c.br_region_fo_code, d.name;but whether Oracle will filter early or not is another matter. You would have to test both runs.I believe that Jonathan Lewis had a demonstration of execution plans that showed Oracle transforming queries to "push" GROUP BY clause prior to a join when sufficient contraints were in place to allow that and there was a performance benefit in doing so. I'd certainly be interested in seeing whether this was being done. The optimisation was really aimed at reducing the size of the group by key columns.

Simple query takes 18 minutes to retrieve data....

Hi,
I am facing this problem at the customer site where a simple query on a table takes 18 minutes or more. Please find below the details.
Table Structure
CREATE TABLE dsp_data
quantum_id NUMBER(11) NOT NULL,
src      NUMBER(11) NOT NULL,
call_status NUMBER(11) NOT NULL,
dst NUMBER(11) NOT NULL,
measurement_id NUMBER(11) NOT NULL,
is_originating NUMBER(1)     NOT NULL,
measurement_value NUMBER(15,4) NOT NULL,
data_type_id NUMBER(3) NOT NULL,
data VARCHAR2(200) NOT NULL
TABLESPACE dsp_data_tspace
STORAGE (PCTINCREASE 0 INITIAL 100K NEXT 1024K)
PARTITION BY RANGE (quantum_id)
(PARTITION dsp_data_default VALUES LESS THAN (100));
CREATE INDEX dsp_data_idx ON dsp_data
quantum_id,
src,
     call_status,
dst,
     measurement_id,
     is_originating,
measurement_value,
data_type_id
TABLESPACE dsp_data_idx_tspace
LOCAL;
CREATE INDEX dsp_data_src_idx ON dsp_data
src
TABLESPACE dsp_data_idx_tspace
LOCAL;
CREATE INDEX dsp_data_dst_idx ON dsp_data
dst
TABLESPACE dsp_data_idx_tspace
LOCAL;
ALTER TABLE dsp_data
ADD CONSTRAINT fk_dsp_data_1
FOREIGN KEY
quantum_id
REFERENCES mds_measurement_intervals
quantum_id
ALTER TABLE dsp_data
ADD CONSTRAINT fk_dsp_data_2
FOREIGN KEY
data_type_id
REFERENCES mds_drilldown_types
type_id
ALTER TABLE dsp_data
ADD CONSTRAINT pk_dsp_data
PRIMARY KEY
quantum_id,
src,
call_status,
dst,
          measurement_id,
          is_originating,
measurement_value,
data_type_id,
data
USING INDEX
TABLESPACE dsp_data_idx_tspace
LOCAL;
Table Space Creation
All table space creation is done using following command
CREATE TABLESPACE [tablespaceName]
DATAFILE [tablespaceDatafile] SIZE 500M REUSE
AUTOEXTEND ON NEXT 10240K
DEFAULT STORAGE ( INITIAL 1024K
NEXT 1024K
MINEXTENTS 10
MAXEXTENTS UNLIMITED
PCTINCREASE 0
Server Configuration on CUtsomer Site
(1)     2 x Dual PA8900 Proc = 4GHz
(2)     RAM = 16GB
(3)     3 x Internal HDDs
(4)     1 x External MSA-30 storage array (oracle db)
Record Information On Customer Site
select count(*) from dsp_data;
COUNT(*)
181931197
select min (quantum_id) from dsp_data where dst=2;
This takes 18 minutes or more....
SQL> SQL> SQL> explain plan for select min (quantum_id) from dsp_data where dst=2;
Explained.
SQL> @?/rdbms/admin/utlxpls
PLAN_TABLE_OUTPUT
Plan hash value: 999040277
| Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time | Pstart| Pstop |
| 0 | SELECT STATEMENT | | 1 | 14 | 1 (0)| 00:00:01 | | |
| 1 | SORT AGGREGATE | | 1 | 14 | | | | |
| 2 | FIRST ROW | | 92 | 1288 | 1 (0)| 00:00:01 | | |
| 3 | PARTITION RANGE ALL | | 92 | 1288 | 1 (0)| 00:00:01 | 1 | 29 |
|* 4 | INDEX FULL SCAN (MIN/MAX)| DSP_DATA_IDX | 92 | 1288 | 1 (0)| 00:00:01 | 1 | 29 |
As mentioned above the query takes 18 minutes or more. This is a critical issue at customer. Can you please give your suggestions how to improve and reduce the query time. Thanks in advance.

Hi,
I did the following changes in the indexes of table.
drop index DSP_DATA_IDX;
create index DSP_DATA_MEASUREMENT_ID_IDX on DSP_DATA (MEASUREMENT_ID) TABLESPACE dsp_data_idx_tspace LOCAL;
After that I did explain plan,
explain plan for select min(QUANTUM_ID) from mds.DSP_DATA where SRC=11;
PLAN_TABLE_OUTPUT
| Id | Operation | Name | Rows | Bytes | Cost (%CPU
| 0 | SELECT STATEMENT | | 1 | 11 | 3 (0
| 1 | SORT AGGREGATE | | 1 | 11 |
| 2 | FIRST ROW | | 430K| 4626K| 3 (0
| 3 | PARTITION RANGE ALL | | 430K| 4626K| 3 (0
| 4 | INDEX FULL SCAN (MIN/MAX)| PK_DSP_DATA | 430K| 4626K| 3 (0
Note
- 'PLAN_TABLE' is old version
14 rows selected
SELECT table_name, index_name, monitoring, used FROM v$object_usage;
TABLE_NAME INDEX_NAME MONITORING USED
DSP_DATA DSP_DATA_SRC_IDX YES NO
It seems that DSP_DATA_SRC_IDX is not getting used in query. What changes do i need to make so that DSP_DATA_SRC_IDX index gets used.
Also, you have stated that to create global index on src and dst. How do i create them.
Thanks in Advance.
Edited by: 780707 on Jul 8, 2010 11:58 PM

Simple query optimization

Hi,
I'm using Oracle 10g r2.
I have this simple query that seems to take too much time to execute :
DECLARE
     nb_mesures INTEGER;
     min_day DATE;
     max_day DATE;
BEGIN
     SELECT
          COUNT(meas_id),
          MIN(meas_day),
          MAX(meas_day)
     INTO
          nb_mesures,
          min_day,
          max_day
     FROM
          geodetic_measurements gm
          INNER JOIN
          operation_measurements om
          ON gm.meas_id = om.ogm_meas_id
     WHERE ogm_op_id = 0;
     htp.p(nb_mesures||' measurements from '||min_day||' to '||max_day);
END;- Tables (about 11.000 records for the "Operations" table, and 800.000 for the 2 others) :
"Operation_measurements" is the table who makes the link between the 2 others (get the 2 keys).
SQL> DESCRIBE OPERATIONS
Nom                  NULL     Type
OP_ID                NOT NULL NUMBER(7)
OP_PARENT_OP_ID               NUMBER(7)
OP_RESPONSIBLE       NOT NULL VARCHAR2(10)
OP_DESCRIPT                   VARCHAR2(80)
OP_VEDA_NAME         NOT NULL VARCHAR2(10)
OP_BEGIN             NOT NULL DATE
OP_END                        DATE
OP_INSERT_DATE                DATE
OP_LAST_UPDATE                DATE
OP_INSERT_BY                  VARCHAR2(50)
OP_UPDATE_BY                  VARCHAR2(50)
SQL> DESCRIBE OPERATION_MEASUREMENTS
Nom                  NULL     Type
OGM_MEAS_ID          NOT NULL NUMBER(7)
OGM_OP_ID            NOT NULL NUMBER(6)
OGM_INSERT_DATE               DATE
OGM_LAST_UPDATE               DATE
OGM_INSERT_BY                 VARCHAR2(50)
OGM_UPDATE_BY                 VARCHAR2(50)
SQL> DESCRIBE GEODETIC_MEASUREMENTS
Nom                  NULL     Type
MEAS_ID              NOT NULL NUMBER(7)
MEAS_TYPE            NOT NULL VARCHAR2(2)
MEAS_TEAM            NOT NULL VARCHAR2(10)
MEAS_DAY             NOT NULL DATE
MEAS_OBJ_ID          NOT NULL NUMBER(6)
MEAS_STATUS                   VARCHAR2(1)
MEAS_COMMENT                  VARCHAR2(150)
MEAS_DIRECTION                VARCHAR2(1)
MEAS_DIST_MODE                VARCHAR2(2)
MEAS_SPAT_ID         NOT NULL NUMBER(7)
MEAS_INST_ID                  NUMBER(7)
MEAS_DECALAGE                 NUMBER(8,5)
MEAS_INST_HEIGHT              NUMBER(8,5)
MEAS_READING         NOT NULL NUMBER(11,5)
MEAS_CORRECT_READING          NUMBER(11,5)
MEAS_HUMID_TEMP               NUMBER(4,1)
MEAS_DRY_TEMP                 NUMBER(4,1)
MEAS_PRESSURE                 NUMBER(4)
MEAS_HUMIDITY                 NUMBER(2)
MEAS_CONSTANT                 NUMBER(8,5)
MEAS_ROLE                     VARCHAR2(1)
MEAS_INSERT_DATE              DATE
MEAS_LAST_UPDATE              DATE
MEAS_INSERT_BY                VARCHAR2(50)
MEAS_UPDATE_BY                VARCHAR2(50)
MEAS_TILT_MODE                VARCHAR2(4000) - Explain plan (I'm not familiar with explain plans...) :
| Id | Operation                     | Name                   | Rows | Bytes | Cost (%CPU)| Time     |
PLAN_TABLE_OUTPUT
|   0 | SELECT STATEMENT              |                        |     1 |    19 |   256 (10)| 00:00:02 |
|   1 | SORT AGGREGATE               |                        |     1 |    19 |            |          |
|   2 |   NESTED LOOPS                |                        |    75 | 1425 |   256 (10)| 00:00:02 |
|* 3 |    TABLE ACCESS FULL          | OPERATION_MEASUREMENTS |    75 |   600 |    90 (27)| 00:00:01 |
|   4 |    TABLE ACCESS BY INDEX ROWID| GEODETIC_MEASUREMENTS |     1 |    11 |     3   (0)| 00:00:01 |
|* 5 |     INDEX UNIQUE SCAN         | MEAS_PK_2              |     1 |       |     2 (50)| 00:00:01 |
--------------------------------------------------------------------------------------------------------How can I optimize this query ?
Thanks.
Yann.

Looks like you are missing an FK-index on the middle table, for the FK going to OPERATIONS.
Currently this:
WHERE ogm_op_id = 0;Is computed via a full table scan followed by a filter operation. Assuming OP_ID is rather selective, an index on OGM_OP_ID could do the trick here.

Simple query-strange output

Similar Messages

Maybe you are looking for