Query expansion and FIRST_ROWS problem

Hello!
I have the following construction:
SELECT p.* FROM ( SELECT q.*, rownum rn FROM (
SELECT /*+ FIRST_ROWS(10) */ SCORE(1) AS score, idf FROM table WHERE CONTAINS(column, **query**, 1) > 0 ORDER BY SCORE(1) DESC, ROWID
) q WHERE rownum <= 10) p WHERE rn > 0;
When I use query:
<query><textquery lang="ENGLISH" grammar="CONTEXT"><progression>
<seq>string within section</seq>
</progression></textquery><score datatype="FLOAT" algorithm="DEFAULT"></query>
I get the results (>10) in some normal time. But with the following query:
<query><textquery lang="ENGLISH" grammar="CONTEXT"><progression>
<seq>string within section</seq>
<seq>fuzzy(string) within section</seq>
<seq>%string% within section</seq>
</progression></textquery><score datatype="FLOAT" algorithm="DEFAULT"></query>
the search is soooo slow. I don't understand it: I set the limit to 10 first rows, which is already satisfied by the first sequence in the query expansion. But Oracle (obviously) seems to execute all the other ones as well!
And another observation: the presence of /*+ FIRST_ROWS(10) */ doesn't really matter from the time viewpoint...
So what I am doing wrong? Thank you SOO much for answers!
Martin

Similar Messages

DRG-51030: wildcard query expansion after using @

The following query returns one row:
select * from userinterface where contains (searchtx, 'Mustermann within name and %gmx.de within email')>0;
returns one row.
If I add @ (=> %@gmx.de within email) the following error occurs:
select * from userinterface where contains (searchtx, 'Mustermann within name and %@gmx.de within email')>0;
returns
ERROR at line 1:
ORA-29902: error in executing ODCIIndexStart() routine
ORA-20000: Oracle Text error:
DRG-51030: wildcard query expansion resulted in too many terms
Is the character @ a special character causing the wildcard query expansion? "@gmx.de" is more restictive compared to "gmx.de" (Oracle 10.2.0.4)
select * from userinterface where contains (searchtx, 'Mustermann within name and %de within email')>0;
is also working and returns three rows.

Like Roger said, you could include the @ in your printjoins attribute of your basic_lexer and use a substring_index, then that might allow you to search for '%@gmx.de' and find '[email protected]' without encountering the wildcard expansion error. Increasing the wildcard_maxterms would also make the error less likely. However, I believe that is using Oracle Text in a manner other than it is intended and will cause more problems than it will solve, like increasing the size of your domain index tables by storing substrings and making your searches slower.
If you just leave things the way they are, then @ and . are treated as spaces and '[email protected]' is seen as 'somebody gmx de' and indexed as three separate words, so searching for '@gmx.de' will search for 'gmx de' and will find it, so there is no need for a leading wildcard. If you want to avoid problems with errors due to users entering unnecessary leading wildcards with such special characters, then you can replace them in the string before searching. I usually find it convenient to create a cleanup function and include any such problems, then include that in my code that uses a bind variable for the search string. Please see the example below.
SCOTT@orcl_11gR2> -- table:
SCOTT@orcl_11gR2> create table userinterface
2    (id       number,
3      searchtx xmltype)
4 /
Table created.
SCOTT@orcl_11gR2> -- lexer:
SCOTT@orcl_11gR2> begin
2    ctx_ddl.create_preference('german_lexer','basic_lexer');
3    ctx_ddl.set_attribute('german_lexer','composite','german');
4    ctx_ddl.set_attribute('german_lexer','mixed_case','yes');
5    ctx_ddl.set_attribute('german_lexer','alternate_spelling','german');
6 end;
7 /
PL/SQL procedure successfully completed.
SCOTT@orcl_11gR2> -- index:
SCOTT@orcl_11gR2> CREATE INDEX ui_t_ind on userinterface (searchtx)
2      indextype is ctxsys.context
3           PARAMETERS ('
4                SECTION GROUP ctxsys.auto_section_group
5                LEXER        german_lexer
6                MEMORY        100000000
7                SYNC        (MANUAL)'
8           )
9 /
Index created.
SCOTT@orcl_11gR2> -- insert data:
SCOTT@orcl_11gR2> insert /*+ APPEND */ into userinterface (id, searchtx)
2 values (1, xmltype (
3 '<?xml version="1.0"?>
4 <data>
5    <name>Mustermann</name>
6    <email>[email protected]</email>
7 </data>'))
8 /
1 row created.
SCOTT@orcl_11gR2> insert /*+ APPEND */ into userinterface (id, searchtx)
2 values (2, xmltype (
3 '<?xml version="1.0"?>
4 <data>
5    <name>Hans Haeberle</name>
6    <email>[email protected]</email>
7 </data>'))
8 /
1 row created.
SCOTT@orcl_11gR2> -- synchronize, then optimize with rebiuld:
SCOTT@orcl_11gR2> begin
2    ctx_ddl.sync_index ('ui_t_ind');
3    ctx_ddl.optimize_index ('ui_t_ind', 'rebuild');
4 end;
5 /
PL/SQL procedure successfully completed.
SCOTT@orcl_11gR2> -- what is tokenized, indexed, and searchable:
SCOTT@orcl_11gR2> select token_text from dr$ui_t_ind$i
2 /
TOKEN_TEXT
DATA
EMAIL
Haeberle
Hans
Häberle
Mann
Muster
Mustermann
NAME
com
de
gmx
somebody
unknown
whatever
15 rows selected.
SCOTT@orcl_11gR2> -- function to clean up search strings:
SCOTT@orcl_11gR2> create or replace function cleanup
2    (p_string in varchar2)
3    return         varchar2
4 as
5    v_string     varchar2 (100);
6 begin
7    v_string := p_string;
8    v_string := replace (p_string, '%@', ' ');
9    return v_string;
10 end cleanup;
11 /
Function created.
SCOTT@orcl_11gR2> show errors
No errors.
SCOTT@orcl_11gR2> -- example search strings, queries, and results:
SCOTT@orcl_11gR2> column name format a15
SCOTT@orcl_11gR2> column email format a20
SCOTT@orcl_11gR2> variable search_string varchar2 (100)
SCOTT@orcl_11gR2> begin
2    :search_string :=
3       'Mustermann within name and %@gmx.de within email';
4 end;
5 /
PL/SQL procedure successfully completed.
SCOTT@orcl_11gR2> select id,
2          extractvalue (u.searchtx, '//name') name,
3          extractvalue (u.searchtx, '//email') email
4 from   userinterface u
5 where contains (searchtx, cleanup (:search_string)) > 0
6 /
        ID NAME            EMAIL
         1 Mustermann      [email protected]
1 row selected.
SCOTT@orcl_11gR2> begin
2    :search_string :=
3       'Häberle within name and unknown@whatever within email';
4 end;
5 /
PL/SQL procedure successfully completed.
SCOTT@orcl_11gR2> select id,
2          extractvalue (u.searchtx, '//name') name,
3          extractvalue (u.searchtx, '//email') email
4 from   userinterface u
5 where contains (searchtx, cleanup (:search_string)) > 0
6 /
        ID NAME            EMAIL
         2 Hans Haeberle   [email protected]
1 row selected.
SCOTT@orcl_11gR2>

BEx Variable defined in BI 7.0 Query Designer and using in BW 3.5 Analyzer

Hi,
I have defined a variable in BI 7.0 Query designer for a characteristic which is present in characteristic restrictions area to restrict it . Ideally when that query is executed a pop up box should be opened to enter a value of the variable. But when that query is opened in BW 3.5 BEx Analyzer, instead of pop up box the error message " Error specify a value for the Variable ' Variable Name ' " has been displayed. Please help me to resolve this problem
<i><b>Details of Variable:</b></i>
Type: Characteristic Value
Processed by: Manual Entry/Default Value
Variable is : Mandatory
and Ready for input
No default values are defined for this variable.
Thanks
Hari Prasad.

Hi,
Once a query opened and changed in the BI7.0 query designer u can not use the same query in lower version.
Thats the reason the error message coming.
If u need the 3.5 query just keep as it is , and copy the same query in different name and open it in the BI7.0 and do the changes.
Thanks,
Debasish

Af:query how to control the query combobox and change it's label text

My colleague designed a well working af:query search page with several selectable predefined queries. Now it's up to me to control this combobox from outside the component with big colored buttons for user convenience. If the user clicks on one of the big buttons, the assigned item of the combobox is selected and then the query is submitted.
I though about doing this with javascript, but the difficulty is, that I have no idea and didn't find a way to reference the id of the combobox? The combobox is a 'built in' component in he af:query component and there is no way to give it an id in the properties.
The second problem is that I didn't find a way to change the label text of the combobox. It seems to be hard coded?
Thanks in advance for your suggestion!

Hi,
the text should be coming from a message bundle and some other look and feel related elements should be settable through skinning in CSS
http://www.oracle.com/technology/products/adf/adffaces/11/doc/skin-selectors.html
search for af|query
Regarding the JavaScript access, use firebug JS debugger. The af query class is AdfRichQuery.js
http://www.oracle.com/technology/products/adf/adffaces/11/doc/multiproject/adf-richclient-api/js_docs_out/AdfRichQuery.html
Note however that you should be able to do in Java what you are aimning for in JavaScript. However the usecase you want to implement is not fully clear to me - to be honest
Frank

Output mismatch between BEx query output and WebI Report output

Hi All,
I have a BEx query in which there are only characteristics placed in rows.
There are combinations of the values of the characteristics giving different records in the query output.
Date is one of the characterisctics in the query output.
There is an output mismatch between the query output and the WebI report output in the following case:
When there are 'Not Assigned' or '#' or blank values, there are additional entries(rows) in the WebI report, giving repeating or wrong entries in the Date field. This is incorrect data.
Is this because of the 'Not Assigned' or '#' or blank values of the Characteristics or is there any other reason?
How do I fix this?
Please helo me with this.
Thanks and Regards,
Srilakshmi B

Hi Rajesh,
I need to verify the WebI report output for records with # and 'Not assigned' values for the cHracteristics in the report.
So I cannot check the WebI report by hiding the # or Not assigned values.
The problem is that in the Query output the records are like these shown below:
Char1                    CHar2                          CHar3                       Date field
A                             B                                 C                                Date1
#(Not assgined)      #(Not assgined)      #(Not assgined)             No value
Where as the WebI report output is as below:
Char1                    CHar2                          CHar3                       Date field
A                             B                                 C                                Date1
#(Not assgined)      #(Not assgined)      #(Not assgined)            Date1
As shown here, there are wrong/repeating entries for the Date field in the WebI report output.
Please check this and let me know what could be the issue and how do I fix it.
Thanks and Regards,
Srilakshmi B

Flex/cold fusion wizard & Visual Query builder has a problem

has anybody tried the cold fusion / flex application wizard in flex 3?
to get there follow these menu choices:
file new other cold fusion wizards coldfusion / flex application wizard
I previously installed cf8 and the rds query viewer works fine.
i simply choose from the following menus:
window other views... Cold Fusion RDS dataview
i was initially prompted for the rds password which i entered.
in the RDS Dataview, I can see the tables, columns, and data for all my existing datasources.
Unfortunately, when I use the COld Fusion/Flex application wizard,
I get to the page layout and design screen, add a page with the name artists, choose page type master, and click the Edit master page button.
Nothing happens when I click the Edit Master Page button. I followed the cf/flex tutorial exactly but there is no query builder.
I dont know if this is related but in the RDS query viewer, the Visual Query BUilder doesn't work.
I think this may be the problem (the visual query builder has a problem)
Unfortunately, how do I fix this problem

already found the answer
flex has to be run as administrator if using WIndows Vista
simply shut down flex, right click the startup icon, choose run as administrator, and the visual query builder runs fine.
Dont know why this occurs because you are always prompted for the rds password.
anyway, problem solved.
http://forums.adobe.com/message/228385#228385

Query LOV and how to display the LOV back in the Text item.

Hi All,
I have got a big time problem in getting back my LOV value after Querying it.
Am using a Tabular Canvas having 10 rows and two columns, one having "Type"(as LOV) and corresponding "Type identifier".
My LOV is an non data block item, having the correct return type. When ever i search for a value in the LOV, its should give out all the "Type Identifier" list and the "Type".
But what i am facing is, am not able to get back the selected LOV after querying it and am getting the entire "Type Identifier' with out any filter.
In short my requirement is,
- I need to search an LOV,
- Display the LOV value in the "TYPE" field.
- Display the corresponding "Type Identifiers'
Pls note: Since am new to Oracle Forms, if in your replies, if you specify to use any code in trigger, pls specify which trigger to use.
Thanks a lot in Advance... its bit urgent
Arun

Hi Dave
The requirement is suppose i have an Lov called OrgName is atatched to a column in which user will select the Ou Name from the list and internally the respective org_id will store into the database where the OU Name is available in the same data block but it is not database item . (Only org_id is database item)
Now if you query the same block i would expect the Ou Name should display .
Right now in my case it is not displaying anything into that column.
Hope u understood this time..Please let me know is there any trick?

Named query in Entity Bean - Problem with embedded class

Hello Forum,
I'm trying to set up a named query in my Entity Bean and I'm unable to get
it up and running for an embedded class object.
The class hierarchy is as follows:
         @MappedSuperclass
         AbstractSapResultData (contains dayOfAggregation field)
                 ^
                 |
        @MappedSuperclass
        AbstractSapUserData (contains the timeSlice field)
                 ^
                 |
          @Entity
          SapUserDataThe named query is as follows:
@NamedQuery(name = SapUserDataContext.NAMED_QUERY_NAME_COUNT_QUERY,
                            query = "SELECT COUNT(obj) FROM SapUserData AS obj WHERE "
                                     + "obj.sapCustomerId"
                                     + "= :"
                                     + SapResultDataContext.COLUMN_NAME_SAP_CUSTOMER_ID
                                     + " AND "
                                     + "obj.sapSystemId"
                                     + "= :"
                                     + SapResultDataContext.COLUMN_NAME_SAP_SYSTEM_ID
                                     + " AND "
                                     + "obj.sapServerId"
                                     + "= :"
                                     + SapResultDataContext.COLUMN_NAME_SAP_SERVER_ID
                                     + " AND "
                                     + "obj.dayOfAggregation.calendar"
                                     + "= :"
                                     + DayContext.COLUMN_NAME_DAY_OF_AGGREGATION
                                     + " AND "
                                     + "obj.timeSlice.startTime"
                                     + "= :"
                                     + "timeSliceStartTime"
                                     + " AND "
                                     + "obj.timeSlice.endTime"
                                     + "= :"
                                     + "timeSliceEndTime")The query deploys and runs except that part:
                                     + "obj.dayOfAggregation.calendar"
                                     + "= :"
                                     + DayContext.COLUMN_NAME_DAY_OF_AGGREGATIONI don't see any difference to the part of the query accessing the timeSlice
field which is also an embedded class object - I access it in exactly the same way:
                                     + "obj.timeSlice.startTime"
                                     + "= :"
                                     + "timeSliceStartTime"
                                     + " AND "
                                     + "obj.timeSlice.endTime"
                                     + "= :"
                                     + "timeSliceEndTime"The problem is that the complete query runs on JBoss application server
but on the SAP NetWeaver application server it only rund without the
                                     + "obj.dayOfAggregation.calendar"
                                     + "= :"
                                     + DayContext.COLUMN_NAME_DAY_OF_AGGREGATIONpart - If I enable that part on SAP NetWeaver the server complains:
[EXCEPTION]
{0}#1#java.lang.IllegalArgumentException: line 1: Comparison '=' not defined for dependent objects
SELECT COUNT(obj) FROM SapUserData AS obj WHERE obj.sapCustomerId= :sap_customer_id AND obj.sapSystemId= :sap_system_id AND obj.sapServerId= :sap_server_id AND obj.dayOfAggregation.calendar= :day_of_aggregation AND obj.timeSlice.startTime= :timeSliceStartTime AND obj.timeSlice.endTime= :timeSliceEndTime
                                                                                                                                                                                             ^I know that this isn't an application server specific forum but the SAP NetWeaver server is the most strict EJB 3.0 and JPA 1.0 implementation I've seen so far so I think I'm doing something wrong there.
Someone in the SAp forum mentioned:
The problem here is that you compare an input-parameter with an embeddable field of your entity.
Regarding to the JPQL-grammer (spec 4.14) you are not allowed to compare
with the non-terminal embeddable field but with the terminal fields of your
embeddable. Stating that your embedded class might have the fields
startTime and endTime your JPQL query might look like this:
Query q = em.createQuery("SELECT count(obj.databaseId) FROM SapUserData obj WHERE obj.timeSlice.startTime = :startTime AND obj.timeSlice.endTime = :endTime");
q.setParameter("startTime", foo.getStartTime());
q.setParameter("endTime", foo.getEndTime());
q.getResultList();
This limitation in the JPQL grammar is rather uncomfortable.
An automatic mapping of the parameter's fields to the terminal fields of your
embedded field would be more convenient. The same can be said for lists
as parameter-values which is possible in HQL, too. I think we have to wait
patiently for JPA 2.0 and hope for improvements there. :-)
With that help I was able to get it up and running for the timeSlice field but
I don't see the difference to the dayOfAggregation field which is also just
another embedded class using an object of a class annotated with
@Embeddable.
The get method of the dayOfAggregation field is as follows:
     * Get method for the member "<code>dayOfAggregation</code>".
     * @return Returns the dayOfAggregation.
    @Embedded
    @AttributeOverrides({@AttributeOverride(name = "calendar", /* Not possible to use interface constant here - field name must be used for reference */
                                            column = @Column(name = DayContext.COLUMN_NAME_DAY_OF_AGGREGATION,
                                                             nullable = false)),
                         @AttributeOverride(name = "weekday",
                                            column = @Column(name = DayContext.COLUMN_NAME_WEEKDAY,
                                                             nullable = false)),
    public Day getDayOfAggregation() {
        return this.dayOfAggregation;
    }The link to my question in the SAP forum for reference:
https://www.sdn.sap.com/irj/sdn/thread?messageID=3651350
Any help or ideas would be greatly appreciated.
Thanks in advance.
Henning Malzahn

Hello Forum,
got a response in the SAP forum - Issue is a bug in the SAP NetWeaver
app. server.
Henning Malzahn

Error - DRG-51030: wildcard query expansion resulted in too many terms

Hi All,
My searches against a 100 million company names table on org names often result in the following error:
DRG-51030: wildcard query expansion resulted in too many terms
A sample query would be:
select v.* --xref.external_ref_party_id,v.*
from xxx_org_search_x_v vwhere 1 =1
and state_province = 'PA'
and country = 'US'
and city = 'BRYN MAWR'
and catsearch(org_name,'BRYN MAWR AUTO*','CITY=''BRYN MAWR''' ) > 0
I understand that is caused by the presence of the word Auto to which we append a * . (If i remove the auto the search works fine).
My question is - is there a way to limit the query expansion to only , say 100, results that get returned from the index?

Thanks for the reply. This is how the preferences are set:
exec ctx_ddl.create_preference('STEM_FUZZY_PREF', 'BASIC_WORDLIST');
exec ctx_ddl.set_attribute('STEM_FUZZY_PREF','FUZZY_MATCH','AUTO');
exec ctx_ddl.set_attribute('STEM_FUZZY_PREF','FUZZY_SCORE','60');
exec ctx_ddl.set_attribute('STEM_FUZZY_PREF','FUZZY_NUMRESULTS','100');
exec ctx_ddl.set_attribute('STEM_FUZZY_PREF','STEMMER','AUTO');
exec ctx_ddl.set_attribute('STEM_FUZZY_PREF', 'wildcard_maxterms',15000) ;
exec ctx_ddl.create_preference('LEXTER_PREF', 'BASIC_LEXER');
exec ctx_ddl.set_attribute('LEXTER_PREF','index_stems', 'ENGLISH');
exec ctx_ddl.set_attribute('LEXTER_PREF','skipjoins',',''."+-/&');
exec ctx_ddl.create_preference('xxx_EXT_REF_SEARCH_CTX_PREF', 'BASIC_STORAGE');
exec ctx_ddl.set_attribute('xxx_EXT_REF_SEARCH_CTX_PREF', 'I_TABLE_CLAUSE','tablespace ICV_TS_CTX_IDX');
exec ctx_ddl.set_attribute('xxx_EXT_REF_SEARCH_CTX_PREF', 'K_TABLE_CLAUSE','tablespace ICV_TS_CTX_IDX');
exec ctx_ddl.set_attribute('xxx_EXT_REF_SEARCH_CTX_PREF', 'N_TABLE_CLAUSE','tablespace ICV_TS_CTX_IDX');
exec ctx_ddl.set_attribute('xxx_EXT_REF_SEARCH_CTX_PREF', 'I_INDEX_CLAUSE','tablespace ICV_TS_CTX_IDX Compress 2');
exec ctx_ddl.set_attribute('xxx_EXT_REF_SEARCH_CTX_PREF', 'P_TABLE_CLAUSE','tablespace ICV_TS_CTX_IDX ');
exec ctx_ddl.set_attribute('xxx_EXT_REF_SEARCH_CTX_PREF', 'I_ROWID_INDEX_CLAUSE','tablespace ICV_TS_CTX_IDX ');
exec ctx_ddl.set_attribute('xxx_EXT_REF_SEARCH_CTX_PREF', 'R_TABLE_CLAUSE','tablespace ICV_TS_CTX_IDX LOB(DATA) STORE AS (CACHE) ');
exec ctx_ddl.create_index_set('xxx_m_iset');
exec ctx_ddl.add_index('xxx_m_iset','city, country');
exec ctx_ddl.add_index('xxx_m_iset','postal_code, country');
Users will always use city or postal code when searching for a name. When I run this query -
SELECT dr$token
FROM DR$XXX_EXT_REF_SEARCH_CTX_I1$I
where dr$token like 'AUTO%'
ORDER BY dr$token desc
i get more than 1M rows.
is there a way to include and search for the city name along with the org name?
Thanks again..

SuPM - Data from SAP BW Query(Automatic) and Manual not displayed in KPI

Dear Forum,
I am also, currently working on a project implementing BO SuPM Version 1.0. Landscape is ECC -> BI -> SuPM dashboards.
I have created a KPI in SuPM dashboard.
Case 1 : Automatic data collection - This KPI is marked for Automatic data collection. So, maintained Scripts with Connectivity and SAP BW Query name. I save this KPI and include in a new report and Run it. There are no records displayed.
Case 2: Manual data collection - This KPI is marked for manual data collection. So, maintained values in SuPM portal itself. I save this KPI and include in a new report and Run it. There are no records displayed.
Could you please help me how KPI in SuPM be filled manually and automatically ( from BW Query)?
Thanks,
Best Regards
PhaniRaj

Dear Phani,
First of All, you should have a framework created and assign the Core KPI to that framework and specify the frequency of the framework (Say Monthly) and Activate it.
Upon Activation, if it is a Manual Data Collection, then you should perform Role Assignment ie specifyinfwho would be the Business Contributor & Approver for ur Manual KPI.
After this, you have to run this program [/SRCORE/DATAREQUEST] in SE38 in the backend system which wil create a data request,
Later you should login as Business Contributor and go to MY Data Requests and then provide the data for the Month specified. Then login as Approver and under Approvals option, you should Approve the data. Now, you should go to SuPM application and select that Month in the dimension and KPI and then RUN the Report.
For Automated Data Collection, you should have to initially creata a Query (SAP/ BW) and specify the name of the query in SPRO--> Sustainability Performance Management --> Automated Data Collection --> Maintain Queries (SAP/ BW) --> Specify that Query name and the Connector ID (SM59).
Now go for KPI creation and specify the Query name in the KPI and then Assign the KPI to the framework and activate it.
Upon Activation, You should RUN the program /SRCORE/AUTO_DATA_COLLECT. Now, select this KPI in the report and RUN the report.
If you perform these actions, you will get the values in the report.
It can be checked in the backend application, either by checking the Process chain[RSPC] or by checking the Infocube if the data is loaded into the Infocube or not.
Let me know if you face any problems...
Regards,
Raghu

PeopleSoft Query Access Services security problems, in other words does QAS

PeopleSoft Query Access Services security problems, in other words does QAS bypass PeopleSoft?

Rod,
Can you please post the entire contents of the dataserver summary screen...thanks.
Typically the "No suitable driver exists" error is due to trying to connect to an unsupported DB version with the driver. For example using the MSSQL 2000 driver to connect to MSSQL 2005, be sure that you have downloaded both the MSSQL 2000 (una2000.jar) and 2005 jars and have the proper classpaths specified.
Sam

DRG-51030: wildcard query expansion resulted in too many terms

Hello,
I have sql report in my apex application that is based on sql query with oracle text. I am trying to execute query with % parameter: select * from mytable where contains(term, '%')>0
I now that wildcard_maxterms default maximum is 5000 and in sql-developer query works normally without any errors, but in apex I receive DRG-51030: wildcard query expansion resulted in too many terms.
Please help!!!

Hello,
There's a good discussion of that exception here -
How to limit the number of search results returned by oracle text
John
http://jes.blogs.shellprompt.net
http://apex-evangelists.com

Excel 2013 crashes every single time I click on Power Query Tab and try anything

I have Windows 7 Professional 64 bit. I installed Office 2013 Professional Plus 64 bit. I dont have any older versions of office. I downloaded and installed power query 64 bit. I start excel, click on power query tab and select any option, excel crashes
and closes, every single time.
The event viewer says "Excel is running into problems with "microsoft power query for excel" add-in If it keeps happening disable this add in and check for updates.
P1: 700160
P2: 15.0.4420.1017
Event ID: 300
Task Category : None
Level: Information
User: N/A
Keywords: Classic
Excruciatingly frustrating to have such an unintuitive message. What should I do to get power query working in excel 2013 and most importantly for excel to function ?

Hi,
It should be the latest version of Power Query. Make sure there is no old version of power Query installed in your computer.And what happens if you reinstall Power Query add-in or repair your office program?
Also Microsoft Power Query for Excel requires Internet Explorer 9 or greater.
Wind Zhang
TechNet Community Support

Strange query plans, and so different results from a view.

In my database (11g), I have a currency exchange rate table, which contains all currencies and their exchange rate to USD. I need to have a number of different exchange rates - To GBP, EUR, etc...
To accomplish this I have created a view, which has one union statement of all the USD exchange rates, with the same data joined back on itself to give the exchange rates based on their exchange rate to USD - ie: SELECT b1.Date, b1.Currency AS FromCurrency, b2.Currency as ToCurrency, b1.Rate/b2.Rate as Exchange Rate FROM Rates b1, Rates b2 on b1.Date = b2.Date
This view works fine when I query it, and returns the data as I expect.
I have a second view that is joined to this view to give a return of the amount in each currency for reporting. This view seems to work correctly when I narrow down the search requirements and have a small set of data.
The issue I am having is when I query the second view and get it to return all the data. Instead of receiving 4 rows per transaction (I am only interested in 4 exchange rates for display) I typically receive up to 2 rows. The first record is for the conversion to USD, the second record is for the conversion to the supplied currency. The issue is that this exchange rate actually includes the aggregate for all 3 other requested currencies (not the USD).
So instead of getting something like:
Amt RC BC (Amt = Amount, RC = Reporting Currency. BC = Base Currency)
60 GBP GBP
80 EUR GBP
100 USD GBP
1000 ZAR GBP
60 GBP USD
80 EUR USD
100 USD USD
1000 ZAR USD
I get the following set of results:
1140 GBP GBP
100 USD GBP
100 USD USD
Has anyone come accross something similar or have any ideas on how I can resolve this?
Thanks
PS: I can get both sets of results from the same view depending on the filter criteria. Also if I convert the exchange rates into a table, it then returns the correct results as expected.

943081 wrote:
The idea is to seek help in solving the problem. I was hoping that perhaps someone had experienced the same thing - different results for "effectively" the same query:Well, that's the issue... without additional info, it's not clear what issue you were seeing.
SELECT * FROM view WHERE Date = '01 January, 2012'
verse
SELECT * FROM view WHERE Date > '31 December, 2011' ORDER BY DateNow it's a bit clearer. That second query is not "effectively" the same as the first query. If the date column is in DATE format, then you ought to have a to_date() around the date string to explicitly convert it into a date so you can do date-to-date comparisons correctly. Also, DATE datatype stores times as well as dates, so asking for data matching midnight of a specific date is different than asking for data greater than midnight of the previous day.
If the date string is a string, then ... well, the string "31 December 2011" is greater than the string "31 August 2013", despite it being an earlier date. This is why making sure you're using the right datatype for the job is important - a date is different to a string that just happens to contain a date.
DateID
I have no objection to using a Date but always struggle to understand what someone means when they tell me "06/07/2012" - granted if the day is above 12 or the same day and month I don't have a problem - but it still leaves 121 days a year that are confusing. sure, but just because you find outputting the display (or rather, someone else's output) confusing doesn't mean you still shouldn't use the correct datatype. Store things as a date, and you can then output it in whatever format you like. Try doing that with a string or a number.
Don't say it doesn't happen as I got a birthday card from a company in May this year when I have specifically entered my date of birth as being the 5 of a month (name drop down box on their website)!Just because someone else doesn't understand how to work with dates correctly doesn't mean you can't! It's not exactly rocket science, after all!*{;-)

Query slow and contention Oracle RAC

Hi,
I have problems with our BD...
I have a query that takes a long time and freeze...
our BD is Oracle 10.2.0.4 on RAC with 2 nodes over Red Hat Enterprise Linux Server release 5.3, 64G RAM CPU
SGA : sga_max_target=16G sga__target=15G
db_4k_cache_size=4G , keep=800M , default =10G in mode automatic
return results of the ADDM says:
ACTION: Investigate the SQL statement with SQL_ID "bb9bma7du62h3" for possible performance improvements.
RELEVANT OBJECT: SQL statement with SQL_ID bb9bma7du62h3 and PLAN_HASH 2145292722
SELECT X.DOCDOCUMENTOID, X.DOCNUMERODOCSERVICIO,         X.DOCFECHADOCSERVICIO, X.DOCFECHADOCCGR, IDEN.ISEGLOSANOMBRE,          X.SCGDESCRIPCION, MAT.MDODESCRIPCION, TIP.TDODESCRIPCION,          X.DESNUMEROCASOS, X.DESESTADO, X.DESSECCIONID, X.DESUSERID,          X.TIMESTAMP, X.TSTAMP, IDENREP.ISEGLOSANOMBRE AS REPARTICION,         X.NOMOBSERVACION
FROM
( SELECT DOC.DOCDOCUMENTOID,         DOC.DOCNUMERODOCSERVICIO, DOC.DOCFECHADOCSERVICIO,         DOC.DOCFECHADOCCGR, SEC.SCGDESCRIPCION, DES.DESNUMEROCASOS,         DES.DESESTADO, DES.DESSECCIONID, DES.DESUSERID, DOC.TIMESTAMP, DES.TIMESTAMP AS TSTAMP, NOM.NOMOBSERVACION, DOC.DOCREPARTICIONID, DOC.DOCSERVICIOID,DOC.DOCTIPODOCUMENTO, DOC.DOCMATERIAINGRESO
FROM
TBLDOCESTUDIO DES,
TBLDOCUMENTO DOC, TBLSECCIONCGR SEC,TBLNOMINA NOM
WHERE 1 = 1
AND :B7 = DES.DESESTADO
AND :B6 = DES.DESSECCIONID
AND DOC.DOCDOCUMENTOID = DES.DESDOCUMENTOID
      AND DES.DESSECCIONID = SEC.SCGCODIGO
AND NOM.NOMNOMINAID = DES.DESNOMINAACTIVA
AND DES.DESNUMEROCASOS BETWEEN :B5 AND :B4
AND NOM.NOMNRONOMINA BETWEEN :B3 AND :B2
AND DOC.DOCNUMERODOCSERVICIO LIKE :B1 ) X,
TBLTIPODOCUMENTO TIP,
TBLMATERIADOCUMENTO MAT,
TBLIDENTIFICACIONSERVICIO IDEN,
TBLIDENTIFICACIONSERVICIO IDENREP
WHERE 1=1
AND X.DOCMATERIAINGRESO = MAT.MDOCODIGO
AND X.DOCTIPODOCUMENTO = TIP.TDOCODIGO
AND X.DOCSERVICIOID = IDEN.ISESERVICIOID
AND X.DOCREPARTICIONID = IDENREP.ISESERVICIOID
AND ROWNUM < :B8RATIONALE: SQL statement with SQL_ID "bb9bma7du62h3" was executed 155 times and had an average elapsed time of 283 seconds.
RATIONALE: Waiting for event "direct path read temp" in wait class "User I/O" accounted for 19% of the database time spent in processing the SQL statement with SQL_ID "bb9bma7du62h3".
RATIONALE: Waiting for event "enq: TS - contention" in wait class "Other" accounted for 8% of the database time spent in processing the SQL statement with SQL_ID "bb9bma7du62h3".
RATIONALE: Waiting for event "direct path write temp" in wait class "User I/O" accounted for 4% of the database time spent in processing the SQL statement with SQL_ID "bb9bma7du62h3".
RATIONALE: Average CPU used per execution was 78 seconds.
We have table TBLDOCUMENTO with 4K tablespaces.
We have indexes of TBLDOCUMENTO in other tablespaces with 8K
segments TBLLDOCUMENTO have size of 3,5G
Any ideas how to solve "direct path read temp" , "enq: TS - contention" , "direct path write temp"
and how to make the query faster and not hang
sorry for my bad english...
Regards..
Mario
Edited by: user1056867 on 07-09-2011 12:21 PM

DBMS_SQLTUNE.REPORT_TUNING_TASK('SIAPER')
GENERAL INFORMATION SECTION
Tuning Task Name                  : Siaper
Tuning Task Owner                 : SYSTEM
Scope                             : COMPREHENSIVE
Time Limit(seconds)               : 60
Completion Status                 : COMPLETED
Started at                        : 09/08/2011 10:18:04
Completed at                      : 09/08/2011 10:18:55
Number of SQL Profile Findings    : 1
Schema Name: SIAPER3
SQL ID     : bb9bma7du62h3
SQL Text   : SELECT X.DOCDOCUMENTOID, X.DOCNUMERODOCSERVICIO,
             X.DOCFECHADOCSERVICIO, X.DOCFECHADOCCGR, IDEN.ISEGLOSANOMBRE,
             X.SCGDESCRIPCION, MAT.MDODESCRIPCION, TIP.TDODESCRIPCION,
             X.DESNUMEROCASOS, X.DESESTADO, X.DESSECCIONID, X.DESUSERID,
             X.TIMESTAMP, X.TSTAMP, IDENREP.ISEGLOSANOMBRE AS REPARTICION,
             X.NOMOBSERVACION FROM ( SELECT DOC.DOCDOCUMENTOID,
             DOC.DOCNUMERODOCSERVICIO, DOC.DOCFECHADOCSERVICIO,
DBMS_SQLTUNE.REPORT_TUNING_TASK('SIAPER')
             DOC.DOCFECHADOCCGR, SEC.SCGDESCRIPCION, DES.DESNUMEROCASOS,
             DES.DESESTADO, DES.DESSECCIONID, DES.DESUSERID, DOC.TIMESTAMP,
             DES.TIMESTAMP AS TSTAMP, NOM.NOMOBSERVACION,
             DOC.DOCREPARTICIONID, DOC.DOCSERVICIOID , DOC.DOCTIPODOCUMENTO,
             DOC.DOCMATERIAINGRESO FROM TBLDOCESTUDIO DES, TBLDOCUMENTO DOC,
             TBLSECCIONCGR SEC, TBLNOMINA NOM WHERE 1 = 1 AND :B7 =
             DES.DESESTADO AND :B6 = DES.DESSECCIONID AND DOC.DOCDOCUMENTOID
             = DES.DESDOCUMENTOID AND DES.DESSECCIONID = SEC.SCGCODIGO AND
             NOM.NOMNOMINAID = DES.DESNOMINAACTIVA AND DES.DESNUMEROCASOS
             BETWEEN :B5 AND :B4 AND NOM.NOMNRONOMINA BETWEEN :B3 AND :B2 AND
             DOC.DOCNUMERODOCSERVICIO LIKE :B1 ) X, TBLTIPODOCUMENTO TIP,
             TBLMATERIADOCUMENTO MAT, TBLIDENTIFICACIONSERVICIO IDEN,
             TBLIDENTIFICACIONSERVICIO IDENREP WHERE 1=1 AND
             X.DOCMATERIAINGRESO = MAT.MDOCODIGO AND X.DOCTIPODOCUMENTO =
             TIP.TDOCODIGO AND X.DOCSERVICIOID = IDEN.ISESERVICIOID AND
             X.DOCREPARTICIONID = IDENREP.ISESERVICIOID AND ROWNUM < :B8
FINDINGS SECTION (1 finding)
DBMS_SQLTUNE.REPORT_TUNING_TASK('SIAPER')
1- SQL Profile Finding (see explain plans section below)
A potentially better execution plan was found for this statement.
Recommendation (estimated benefit<=10%)
- Consider accepting the recommended SQL profile.
    execute dbms_sqltune.accept_sql_profile(task_name => 'Siaper', replace =>
            TRUE);
EXPLAIN PLANS SECTION
1- Original With Adjusted Cost
Plan hash value: 3376565491
| Id | Operation                            | Name                         | Ro
DBMS_SQLTUNE.REPORT_TUNING_TASK('SIAPER')
ws | Bytes | Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT                     |                              |
1 |   246 |    34   (3)| 00:00:01 |
|* 1 | COUNT STOPKEY                       |                              |
    |       |            |          |
|* 2 |   FILTER                             |                              |
    |       |            |          |
|* 3 |    HASH JOIN                         |                              |
1 |   246 |    34   (3)| 00:00:01 |
|   4 |     TABLE ACCESS FULL                | TBLTIPODOCUMENTO             |
32 |   608 |     2   (0)| 00:00:01 |
|   5 |     NESTED LOOPS                     |                              |
1 |   227 |    32   (4)| 00:00:01 |
|   6 |      NESTED LOOPS                    |                              |
1 |   182 |    31   (4)| 00:00:01 |
|* 7 |       HASH JOIN                      |                              |
1 |   137 |    30   (4)| 00:00:01 |
|   8 |        NESTED LOOPS                  |                              |
1 |   113 |    27   (0)| 00:00:01 |
DBMS_SQLTUNE.REPORT_TUNING_TASK('SIAPER')
|   9 |         NESTED LOOPS                 |                              |
1 |    75 |    26   (0)| 00:00:01 |
| 10 |          NESTED LOOPS                |                              |
16 |   688 |     2   (0)| 00:00:01 |
| 11 |           TABLE ACCESS BY INDEX ROWID| TBLSECCIONCGR                |
1 |    29 |     1   (0)| 00:00:01 |
|* 12 |            INDEX UNIQUE SCAN         | PK_TBLSECCIONCGR             |
1 |       |     1   (0)| 00:00:01 |
| 13 |           TABLE ACCESS BY INDEX ROWID| TBLNOMINA                    |
16 |   224 |     1   (0)| 00:00:01 |
|* 14 |            INDEX RANGE SCAN          | IDX_IDX_NOM_NRONOMINA        |
1 |       |     1   (0)| 00:00:01 |
|* 15 |          TABLE ACCESS BY INDEX ROWID | TBLDOCESTUDIO                |
1 |    32 |     2   (0)| 00:00:01 |
|* 16 |           INDEX RANGE SCAN           | IDX_DESNOMINA                |
1 |       |     1   (0)| 00:00:01 |
|* 17 |         TABLE ACCESS BY INDEX ROWID | TBLDOCUMENTO                 |
1 |    38 |     1   (0)| 00:00:01 |
|* 18 |          INDEX UNIQUE SCAN           | PK_TBLDOCUMENTO              |
1 |       |     1   (0)| 00:00:01 |
| 19 |        TABLE ACCESS FULL             | TBLMATERIADOCUMENTO          |
DBMS_SQLTUNE.REPORT_TUNING_TASK('SIAPER')
47 | 1128 |     2   (0)| 00:00:01 |
| 20 |       TABLE ACCESS BY INDEX ROWID    | TBLIDENTIFICACIONSERVICIO    |
1 |    45 |     1   (0)| 00:00:01 |
|* 21 |        INDEX UNIQUE SCAN             | PK_TBLIDENTIFICACIONSERVICIO |
1 |       |     1   (0)| 00:00:01 |
| 22 |      TABLE ACCESS BY INDEX ROWID     | TBLIDENTIFICACIONSERVICIO    |
1 |    45 |     1   (0)| 00:00:01 |
|* 23 |       INDEX UNIQUE SCAN              | PK_TBLIDENTIFICACIONSERVICIO |
1 |       |     1   (0)| 00:00:01 |
Predicate Information (identified by operation id):
   1 - filter(ROWNUM<TO_NUMBER(:B8))
   2 - filter(:B3<=:B2 AND :B5<=:B4)
   3 - access("DOC"."DOCTIPODOCUMENTO"="TIP"."TDOCODIGO")
   7 - access("DOC"."DOCMATERIAINGRESO"="MAT"."MDOCODIGO")
12 - access("SEC"."SCGCODIGO"=:B6)
14 - access("NOM"."NOMNRONOMINA">=:B3 AND "NOM"."NOMNRONOMINA"<=:B2)
DBMS_SQLTUNE.REPORT_TUNING_TASK('SIAPER')
15 - filter("DES"."DESSECCIONID"=:B6 AND "DES"."DESESTADO"=:B7 AND "DES"."DESN
UMEROCASOS">=:B5 AND
              "DES"."DESNUMEROCASOS"<=:B4)
16 - access("NOM"."NOMNOMINAID"="DES"."DESNOMINAACTIVA")
       filter("DES"."DESNOMINAACTIVA">=0)
17 - filter("DOC"."DOCNUMERODOCSERVICIO" LIKE :B1)
18 - access("DOC"."DOCDOCUMENTOID"="DES"."DESDOCUMENTOID")
21 - access("DOC"."DOCSERVICIOID"="IDEN"."ISESERVICIOID")
23 - access("DOC"."DOCREPARTICIONID"="IDENREP"."ISESERVICIOID")
2- Using SQL Profile
Plan hash value: 2086638886
| Id | Operation                            | Name                         | Ro
ws | Bytes | Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT                     |                              |
DBMS_SQLTUNE.REPORT_TUNING_TASK('SIAPER')
1 |   246 |    31   (0)| 00:00:01 |
|* 1 | COUNT STOPKEY                       |                              |
    |       |            |          |
|* 2 |   FILTER                             |                              |
    |       |            |          |
|   3 |    NESTED LOOPS                      |                              |
1 |   246 |    31   (0)| 00:00:01 |
|   4 |     NESTED LOOPS                     |                              |
1 |   201 |    30   (0)| 00:00:01 |
|   5 |      NESTED LOOPS                    |                              |
1 |   156 |    29   (0)| 00:00:01 |
|   6 |       NESTED LOOPS                   |                              |
1 |   132 |    28   (0)| 00:00:01 |
|   7 |        NESTED LOOPS                  |                              |
1 |   113 |    27   (0)| 00:00:01 |
|   8 |         NESTED LOOPS                 |                              |
1 |    75 |    26   (0)| 00:00:01 |
|   9 |          NESTED LOOPS                |                              |
16 |   688 |     2   (0)| 00:00:01 |
| 10 |           TABLE ACCESS BY INDEX ROWID| TBLSECCIONCGR                |
1 |    29 |     1   (0)| 00:00:01 |
DBMS_SQLTUNE.REPORT_TUNING_TASK('SIAPER')
|* 11 |            INDEX UNIQUE SCAN         | PK_TBLSECCIONCGR             |
1 |       |     1   (0)| 00:00:01 |
| 12 |           TABLE ACCESS BY INDEX ROWID| TBLNOMINA                    |
16 |   224 |     1   (0)| 00:00:01 |
|* 13 |            INDEX RANGE SCAN          | IDX_IDX_NOM_NRONOMINA        |
1 |       |     1   (0)| 00:00:01 |
|* 14 |          TABLE ACCESS BY INDEX ROWID | TBLDOCESTUDIO                |
1 |    32 |     2   (0)| 00:00:01 |
|* 15 |           INDEX RANGE SCAN           | IDX_DESNOMINA                |
1 |       |     1   (0)| 00:00:01 |
|* 16 |         TABLE ACCESS BY INDEX ROWID | TBLDOCUMENTO                 |
1 |    38 |     1   (0)| 00:00:01 |
|* 17 |          INDEX UNIQUE SCAN           | PK_TBLDOCUMENTO              |
1 |       |     1   (0)| 00:00:01 |
| 18 |        TABLE ACCESS BY INDEX ROWID   | TBLTIPODOCUMENTO             |
1 |    19 |     1   (0)| 00:00:01 |
|* 19 |         INDEX UNIQUE SCAN            | PK_TBLTIPODOCUMENTO          |
1 |       |     1   (0)| 00:00:01 |
| 20 |       TABLE ACCESS BY INDEX ROWID    | TBLMATERIADOCUMENTO          |
1 |    24 |     1   (0)| 00:00:01 |
|* 21 |        INDEX UNIQUE SCAN             | PK_TBLMATERIADOCUMENTO       |
DBMS_SQLTUNE.REPORT_TUNING_TASK('SIAPER')
1 |       |     1   (0)| 00:00:01 |
| 22 |      TABLE ACCESS BY INDEX ROWID     | TBLIDENTIFICACIONSERVICIO    |
1 |    45 |     1   (0)| 00:00:01 |
|* 23 |       INDEX UNIQUE SCAN              | PK_TBLIDENTIFICACIONSERVICIO |
1 |       |     1   (0)| 00:00:01 |
| 24 |     TABLE ACCESS BY INDEX ROWID      | TBLIDENTIFICACIONSERVICIO    |
1 |    45 |     1   (0)| 00:00:01 |
|* 25 |      INDEX UNIQUE SCAN               | PK_TBLIDENTIFICACIONSERVICIO |
1 |       |     1   (0)| 00:00:01 |
Predicate Information (identified by operation id):
   1 - filter(ROWNUM<TO_NUMBER(:B8))
   2 - filter(:B3<=:B2 AND :B5<=:B4)
11 - access("SEC"."SCGCODIGO"=:B6)
13 - access("NOM"."NOMNRONOMINA">=:B3 AND "NOM"."NOMNRONOMINA"<=:B2)
14 - filter("DES"."DESSECCIONID"=:B6 AND "DES"."DESESTADO"=:B7 AND "DES"."DESN
UMEROCASOS">=:B5 AND
DBMS_SQLTUNE.REPORT_TUNING_TASK('SIAPER')
              "DES"."DESNUMEROCASOS"<=:B4)
15 - access("NOM"."NOMNOMINAID"="DES"."DESNOMINAACTIVA")
       filter("DES"."DESNOMINAACTIVA">=0)
16 - filter("DOC"."DOCNUMERODOCSERVICIO" LIKE :B1)
17 - access("DOC"."DOCDOCUMENTOID"="DES"."DESDOCUMENTOID")
19 - access("DOC"."DOCTIPODOCUMENTO"="TIP"."TDOCODIGO")
21 - access("DOC"."DOCMATERIAINGRESO"="MAT"."MDOCODIGO")
23 - access("DOC"."DOCREPARTICIONID"="IDENREP"."ISESERVICIOID")
25 - access("DOC"."DOCSERVICIOID"="IDEN"."ISESERVICIOID")
1 row selected.

Query expansion and FIRST_ROWS problem

Similar Messages

Maybe you are looking for