DNF: Enable Cancel Query

Hi all

Hello..

Is it necessary to settle DNF: select Cancel request no.... Have a set this parameter in their env?

Thank you
Baskar.l

Belot,

Please see these documents.

Note: 744143.1 - performance Tuning on e-Business suite
Note: 401737.1 - activate the query Option Cancel interference and results in disconnections
Note: 138159.1 - long cancellation requests Oracle Applications 11i

Kind regards
Hussein

Tags: Oracle Applications

Similar Questions

  • Why should he use CANCEL query data?

    First, JOHN the user launches an application.

    Second, DANIELLE user updates a row that will be included in the query.

    Thirdly, the request of JOHN full.

    Fourth, MALIK commits the change.

    Fifth, JOHN runs its query again.


    Will be First request of JOHN will use the undo data? This book says Yes (without any explanation), but I say no

    Because Danielle has not committed his change, so the line interviewing JOHN has the value it had when the request has been started (see the table). Therefore, there is no need to read UNDO data (which will degrade the performance anyway).

    Where I'm wrong?

    Even if Eric did not commit its changes might still be written to the data file, even though it marked as "not committed". So in this case, John would require access to undo to give his point of view consistent in reading.

  • FRM-40353 - query cancelled on Execute_Query

    Hello

    I have a simple code - followed go_block ('blk') execute_query;

    After running "Execute_query", I get an error message "frm-40353 - cancelled query". "." Why is it so? When I run the select query on the DB table on which rests the block, I can see the documents.

    Thank you

    This is the description of forms for the Mode of Interaction property using:

    Specifies the mode of interaction for the module of the form. Interaction mode dictates how a user can interact with a form during a query.

    If the Interaction is set on blocking, then users cannot resize or otherwise interacting with the form until that records for a query are retrieved from the database.

    If the value of Non-blocking, then end users can interact with the form while the records are be recovered.

    Non-blocking interaction mode is useful if you plan that the query will take a lot of time and you want that the user can interrupt or cancel the request.

    In this mode, the runtime of forms will display a dialog box that allows the user to cancel the query.

    You cannot set the mode programmatic interaction, however, you can get the interaction by programming mode using the built-in function GET_FORM_PROPERTY.

    If you want to leave the Mode of Interaction = Non-blocking (by default),

    then comes to Maximum length of query = 0 (default, medium unlimited time) in order to avoid "frm-40353 - cancelled request".

    Concerning

  • Problem with the input query mode. FRM 41009, 40301

    Hi all

    I have a problem with the mode of input query. What can I say, I'm in the mode of input query, and I click on a button. I get the error THAT FRM-41009 displayed.

    Now, I've wanted handled. So I created a trigger of error in order to handle the error.

    IF ERR_CODE = 41009 THEN
    NULL;
    END IF;

    A problem is that when you use the null value, it will not terminate the mode of input query, and then I get frm-40301 error.

    Second, it's that I can't use exit_form in a trigger of the error.

    I am aware that I can press F4 to exit this mode, but I don't want to do whenever I'm sure I'll get the user complaints.

    Another solution would be to put the following code in the trigger when key pressed for each button in the form:

    If: system.mode = "ENTER-QUERY" then
    exit_form;
    end if;

    But I don't want to reproduce this code in my form.

    Please can you give me an idea how to handle this correctly?

    Thank you
    Michael

    PS: Version of the form = > ORACLE FORMS 10g (Forms [32 bit] Version 10.1.2.3.0)

    I have a problem with the mode of input query. What can I say, I'm in the mode of input query, and I click on a button. I get the error THAT FRM-41009 displayed.

    What is the code in the trigger of your button When-Button-Pressed (WBP)? Maybe you should check to see if the form is in the Mode query in your WBP rather than try and remove the error? In other words, eliminate error - do not delete it. :)

    If you want instead to remove the error, there is a technique to built-ins call restricted to a trigger that does not allow them. Do this by the use of a millisecond zero Timer. For example:

    /* Sample On-Error Trigger */
    DECLARE
      n_err_cd   NUMBER := ERROR_CODE;
      t_on_error TIMER;
      ZERO  NUMBER := 0;
    BEGIN
      IF ( n_err_cd = 41009 ) THEN
        /* Create Timer to execute Exit_Form() */
        /* to Cancel Query-Mode. */
        t_timer := Create_Timer('ON_ERROR', ZERO, NO_REPEAT);
      ELSE
        /* Handle all other errors here... */
      END IF;
    END;
    
    /* Sample When-Timer-Expired Trigger */
    DECLARE
      v_Timer  VARCHAR2(30);
    BEGIN
      v_timer := Get_Application_Property(TIMER_NAME);
    
      IF ( v_timer = 'ON_ERROR' ) THEN
        /* Notice, the timer name is case sensative! */
        Exit_Form;
      END IF;
    END; 
    

    I am aware that I can press F4 to exit this mode, but I don't want to do whenever I'm sure I'll get the user complaints.

    Well, it's just standard features of Oracle Forms. If you switch the Mode request form - you must run a query or cancel the query Mode! This is how it works. Your users need to understand that and accept it - just as they accept the functional also for other programs. ;) Another option would be to add a "Cancel request" button to your form and make it so it is enabled only when the form is placed in Query Mode. Just a thought...

    I personally prefer to prevent the occurrence of an error rather than remove the error. :)
    I hope this helps.
    Craig...

  • Why can't I run this query in parallel?

    DB version: 11.2.0.4

    Platform: Oracle Linux 6.5

    In my DB, a job with parallelism 5 as stats collection below works well. OEM, I confirm that the bottom congregate, stats job runs with 5 slave process.

    exec dbms_stats.gather_table_stats (-)

    ownname = > 'MEA ', -.

    tabname = > "ORDER_DETAIL", -.

    estimate_percent = > DBMS_STATS. AUTO_SAMPLE_SIZE, -.

    Cascade = > TRUE;

    method_opt = > 'for all THE COLUMNS of SIZE AUTO ', -.

    degree = > 5);

    Order_Detail is a table with 400 million records. I wanted to get a number of rows in this table. So, I tried to use parallelism as shown below.

    But the process of slaves were not created. The SELECT query worked only with parallelism 1. I have this cofirmed of data in real-time to OEM and gv$ view px_session.

    SQL > show parameter parallel_max_servers

    VALUE OF TYPE NAME

    ------------------------------------ ----------- ------------------------------

    PARALLEL_MAX_SERVERS around 3200

    SQL > ALTER SESSION FORCE PARALLEL QUERY 5 PARALLELS;

    Modified session.

    SQL > ALTER SESSION enable parallel query.

    Modified session.

    SQL > select / * + PARALLEL (5) * / count (*) from ptms.order_detail;

    -Also tried

    Select / * + PARALLEL(ptms.order_detail,5) * / count (*) from ptms.order_detail;

    -Also tried

    ALTER SESSION ENABLE PARALLEL DML.

    -Setting below must not be the cause. Right? ALTER SESSION command must take precedence over this setting. Right?

    SQL > select table_name, DEGREE from dba_tables where owner = 'MEA' and table_name = "ORDER_DETAIL";

    DEGREE OF TABLE_NAME

    ------------------------------  ----------------------------------------

    ORDER_DETAIL 1

    Have you tried the trick

    SELECT / * + PARALLEL * / COUNT (*)...

  • Should I wait until the end of the execution time of the query for the execution plan?

    Hello Experts,

    I want to see the execution plan of the query below. However, it takes more than 3 hours. Should I wait all the time to see the execution plan?

    Note: EXPLAIN PLAN for does not work. (I mean that I do not see the actual line number, etc. with EXPLAIN the PLAN of market)

    You can see the output of the execution plan when I canceled the execution after 1 minute.

    My first question is: what should I do to see the execution plan for queries running out of time time?

    2nd question: when I cancel the query during execution in order to see the execution plan, will I see the specific plan of execution or erroneous values? Because the first execution plan seems inaccurate, what do you think?

    question 3: why EXPLAIN the PLAN for the clause does not work? Also, should I use EXPLAIN the PLAN of the clause to this scenerio? Can I see the result of running for long time without her queries?

    Thnaks for your help.

    Oracle Database 11 g Enterprise Edition Release 11.2.0.2.0 - 64 bit Production

    PL/SQL Release 11.2.0.2.0 - Production

    CORE Production 11.2.0.2.0

    AMT for Linux: Version 11.2.0.2.0 - Production

    NLSRTL Version 11.2.0.2.0 - Production

    Select / * + GATHER_PLAN_STATISTICS NO_PARALLEL * / J.INVOICEACCOUNT, J.INVOICEID, J.INVOICEDATE, (T.LINEAMOUNT + T.LINEAMOUNTTAX) price

    of custinvoicejour j join custinvoicetrans t on

    substr (nls_lower (j.DataAreaId), 1, 7) = substr (nls_lower (t.dataareaid), 1, 7) and

    substr (nls_lower (J.INVOICEID), 1: 25) = substr (nls_lower (t.INVOICEID), 1: 25)

    where

    substr (nls_lower (T.DATAAREAID), 1, 7) = '201' and T.AVBROCHURELINENUM = 29457

    and substr (nls_lower (j.dataareaid), 1, 7) = '201' and

    J.INVOICEACCOUNT in

    (select IT. Drmpos.avtr_seg_cust_campend ACCOUNTNUM this where THIS. CAMPAIGN = '201406' and THIS. SEGMENT_LEVEL in (', 'E'))

    and J.AVAWARDSALES > 190

    and substr (nls_lower (J.AVBILLINGCAMPAIGN), 1, 13) = '201406'

    "and J.INVOICEDATE between ' 04.06.2014' and ' 13.06.2014 ';

    SQL_ID, dznya6x7st0t8, number of children 0

    -------------------------------------

    Select / * + GATHER_PLAN_STATISTICS NO_PARALLEL * / J.INVOICEACCOUNT,.

    J.INVOICEID, J.INVOICEDATE, (T.LINEAMOUNT + T.LINEAMOUNTTAX) price of

    CustInvoiceJour j join custinvoicetrans t on

    substr (nls_lower (j.DataAreaId), 1, 7) =

    substr (nls_lower (t.DataAreaId), 1, 7) and

    = substr (nls_lower (J.INVOICEID), 1: 25)

    substr (nls_lower (t.INVOICEID), 1: 25) where

    substr (nls_lower (T.DATAAREAID), 1, 7) = '201' and T.AVBROCHURELINENUM =

    29457 and substr (nls_lower, (j.dataareaid), 1, 7) = '201' and

    J.INVOICEACCOUNT in (select CE. ACCOUNTNUM of

    drmpos.avtr_seg_cust_campend this where THIS. CAMPAIGN = '201406' and

    IT. SEGMENT_LEVEL in (', 'E')) and J.AVAWARDSALES > 190 and

    substr (nls_lower (J.AVBILLINGCAMPAIGN), 1, 13) = '201406' and

    "J.INVOICEDATE between ' 04.06.2014' and ' 13.06.2014 '.

    Hash value of plan: 2002317666

    --------------------------------------------------------------------------------------------------------------------------------------------------------------

    | ID | Operation | Name                           | Begins | E - lines. A - lines.   A - time | Pads | Bed |  OMem |  1Mem | Used Mem.

    --------------------------------------------------------------------------------------------------------------------------------------------------------------

    |   0 | SELECT STATEMENT |                                |      1.        |      0 | 00:00:00.01 |       0 |      0 |       |       |          |

    |*  1 |  HASH JOIN |                                |      1.   3956.      0 | 00:00:00.01 |       0 |      0 |  2254K |  1061K | 2190K (0) |

    |*  2 |   HASH JOIN |                                |      1.     87.  16676. 00:00:01.64 |     227K |   3552.  3109K |  1106K | 4111K (0) |

    |*  3 |    TABLE ACCESS BY INDEX ROWID | CUSTINVOICEJOUR |      1.   1155 |  31889 | 00:00:01.16 |     223KO |     15.       |       |          |

    |*  4 |     INDEX RANGE SCAN | I_062INVOICEDATEORDERTYPEIDX |      1.   4943 |    134K | 00:00:00.83 |   45440 |      0 |       |       |          |

    |   5.    SIMPLE LIST OF PARTITION.                                |      1.  82360 |    173K | 00:00:00.08 |    3809 |   3537 |       |       |          |

    |*  6 |     TABLE ACCESS FULL | AVTR_SEG_CUST_CAMPEND |      1.  82360 |    173K | 00:00:00.06 |    3809 |   3537 |       |       |          |

    |   7.   TABLE ACCESS BY INDEX ROWID | CUSTINVOICETRANS |      1.   4560 |      0 | 00:00:00.01 |       0 |      0 |       |       |          |

    |*  8 |    INDEX RANGE SCAN | I_064INVLINENUMCAMPAIGNOFPRICE |      1.   4560 |      0 | 00:00:00.01 |       0 |      0 |       |       |          |

    --------------------------------------------------------------------------------------------------------------------------------------------------------------

    Information of predicates (identified by the operation identity card):

    ---------------------------------------------------

    1 - access("J".") "SYS_NC00299$"="T". "' SYS_NC00165$ ' AND SUBSTR (NLS_LOWER ('J'. "" "" REFFACTURE")(, 1, 25) = SUBSTR (NLS_LOWER ("T"." "" "REFFACTURE")(, 1, 25)).

    2 - access("J".") INVOICEACCOUNT '= SYS_OP_C2C ("EC". ". ACCOUNTNUM'))

    3 - filter("J".") AVAWARDSALES"> 190)

    4 - access("J".") SYS_NC00299$ "= U ' 201"AND "J". INVOICEDATE"> = TO_DATE(' 2014-06-04 00:00:00', 'syyyy-mm-dd hh24:mi:ss') AND

    "J"." SYS_NC00307$ "= U ' 201406"AND "J". INVOICEDATE"< = TO_DATE (' 2014-06-13 00:00:00 ',' syyyy-mm-dd hh24:mi:ss')))

    filter ((' J'. "INVOICEDATE' > = 'J' AND TO_DATE(' 2014-06-04 00:00:00', 'syyyy-mm-dd hh24:mi:ss') '." " SYS_NC00307$ "= U '201406' AND"

    "J"." INVOICEDATE"< = TO_DATE (' 2014-06-13 00:00:00 ',' syyyy-mm-dd hh24:mi:ss'))))

    6 filter (("CE". "SEGMENT_LEVEL" = A "OR"THIS"." SEGMENT_LEVEL "=" E"))

    8 - access("T".") SYS_NC00165$ "= U ' 201"AND "T". AVBROCHURELINENUM "= 29457)

    filter ("T". ("AVBROCHURELINENUM" = 29457)

    EXPLAIN PLAN FOR

    Select / * + GATHER_PLAN_STATISTICS NO_PARALLEL * / J.INVOICEACCOUNT, J.INVOICEID, J.INVOICEDATE, (T.LINEAMOUNT + T.LINEAMOUNTTAX) price

    of custinvoicejour j join custinvoicetrans t on

    substr (nls_lower (j.DataAreaId), 1, 7) = substr (nls_lower (t.dataareaid), 1, 7) and

    substr (nls_lower (J.INVOICEID), 1: 25) = substr (nls_lower (t.INVOICEID), 1: 25)

    where

    substr (nls_lower (T.DATAAREAID), 1, 7) = '201' and T.AVBROCHURELINENUM = 29457

    and substr (nls_lower (j.dataareaid), 1, 7) = '201' and

    J.INVOICEACCOUNT in

    (select IT. Drmpos.avtr_seg_cust_campend ACCOUNTNUM this where THIS. CAMPAIGN = '201406' and THIS. SEGMENT_LEVEL in (', 'E'))

    and J.AVAWARDSALES > 190

    and substr (nls_lower (J.AVBILLINGCAMPAIGN), 1, 13) = '201406'

    "and J.INVOICEDATE between ' 04.06.2014' and ' 13.06.2014 ';

    SELECT * FROM table (DBMS_XPLAN. DISPLAY_CURSOR);

    SELECT * FROM table (DBMS_XPLAN. DISPLAY_CURSOR ('7h1nbzqjgwsp7', 2));

    SQL_ID, 7h1nbzqjgwsp7, number of children 2

    EXPLAIN PLAN for select / * + GATHER_PLAN_STATISTICS NO_PARALLEL * /.

    J.INVOICEACCOUNT, J.INVOICEID, J.INVOICEDATE,

    (T.LINEAMOUNT + T.LINEAMOUNTTAX) join price j custinvoicejour

    CustInvoiceTrans t on substr (nls_lower (j.dataareaid), 1, 7) =

    substr (nls_lower (t.DataAreaId), 1, 7) and

    = substr (nls_lower (J.INVOICEID), 1: 25)

    substr (nls_lower (t.INVOICEID), 1: 25) where

    substr (nls_lower (T.DATAAREAID), 1, 7) = '201' and T.AVBROCHURELINENUM =

    29457 and substr (nls_lower, (j.dataareaid), 1, 7) = '201' and

    J.INVOICEACCOUNT in (select CE. ACCOUNTNUM of

    drmpos.avtr_seg_cust_campend this where THIS. CAMPAIGN = '201406' and

    IT. SEGMENT_LEVEL in (', 'E')) and J.AVAWARDSALES > 190 and

    substr (nls_lower (J.AVBILLINGCAMPAIGN), 1, 13) = '201406' and

    "J.INVOICEDATE between ' 04.06.2014' and ' 13.06.2014 '.

    NOTE: cannot fetch SQL_ID plan: 7h1nbzqjgwsp7, CHILD_NUMBER: 2

    Check the value of SQL_ID and CHILD_NUMBER;

    It could also be that the plan is no longer in the cursor cache (check v$ sql_plan)

    NightWing wrote:

    Randolf,

    I don't understand. What you hear from the above statement that you mean A-lines and E will be incorrect, but the ratio between them remain the same. Therefore, you can deduct the bad things by comparing the differences.

    Thus, A-lines always give a wrong result for cancellation of queries, isn't it?

    Charlie,

    I think that Martin gave a good explanation. Here's another example that hopefully makes more obvious things:

    17:56:55 SQL >-things go very wrong here with a small buffer cache

    17:56:55 SQL >-T2 lines are badly scattered when you access through T1. FK

    17:56:55 SQL >--

    17:56:55 SQL >-"Small job" approach would have been a good idea

    17:56:55 SQL >-if the estimate of 100 iterations of the loop was correct!

    17:56:55 SQL > select

    17:56:55 (t2.attr2) count 2

    17:56:55 3 of

    17:56:55 4 t1

    17:56:55 5, t2

    17:56:55 6 where

    17:56:55   7  /*------------------*/

    17:56:55 8 trunc (t1.attr1) = 1

    17:56:55 9 and trunc (t1.attr2) = 1

    17:56:55 10 / *-* /.

    17:56:55 11 and t1.fk = t2.id

    17:56:55 12.

    T1

    *

    ERROR on line 4:

    ORA-01013: user has requested the cancellation of the current operation

    Elapsed time: 00:04:58.30

    18:01:53 SQL >

    18:01:53 SQL > @xplan_extended_display_cursor ' ' ' ' 'ALLSTATS LAST + COST.

    18:01:53 SQL > set echo off verify off termout off

    SQL_ID, 353msax56jvvp, number of children 0

    -------------------------------------

    SELECT count (t2.attr2) from t1, t2 where

    / / *-* trunc (t1.attr1) = 1 and

    trunc (T1.attr2) = 1 / *-* / and t1.fk = t2.id

    Hash value of plan: 2900488714

    ------------------------------------------------------------------------------------------------------------------------------------

    | ID | The NEST | DSB | Operation | Name | Begins | E - lines. Cost (% CPU). A - lines.   A - time | Pads | Bed |

    ------------------------------------------------------------------------------------------------------------------------------------

    |   0 |     |   7. SELECT STATEMENT |        |      1.        |  4999 (100) |      0 | 00:00:00.01 |       0 |      0 |

    |   1.   0 |   8 2 GLOBAL TRI |        |      1.      1.            |      0 | 00:00:00.01 |       0 |      0 |

    |   2.   1.   5.   NESTED LOOPS |        |      1.        |            |  57516 | 00:04:58.26 |     173K |  30770 |

    |   3.   2.   3.    NESTED LOOPS |        |      1.    100.  4999 (1) |  57516 | 00:00:21.06 |     116K |   3632.

    |*  4 |   3.   1.     TABLE ACCESS FULL | T1 |      1.    100.  4799 (1) |  57516 | 00:00:00.19 |    1008 |   1087 |

    |*  5 |   3.   2.     INDEX UNIQUE SCAN | T2_IDX |  57516 |      1.     1 (0) |  57516 | 00:00:20.82 |     115K |   2545 |

    |   8 2 2 |   4.    TABLE ACCESS BY INDEX ROWID | T2 |  57516 |      1.     2 (0) |  57516 | 00:04:37.14 |   57516 |  27138 |

    ------------------------------------------------------------------------------------------------------------------------------------

    Information of predicates (identified by the operation identity card):

    ---------------------------------------------------

    4 filter ((TRUNC ('T1'. "ATTR1") = 1 AND TRUNC ('T1'. " ATTR2') = 1))

    5 - access("T1".") FK '= 'T2'.' (ID')

    You say here that I canceled a query after about 5 minutes, and looking at the statistics of content (RowSource) I can already say the following:

    1. the estimation of cardinality of T1 is far - the optimizer estimated 100 lines, but it actually generated more than 57000 lines when the query was cancelled. If this definitely seems like a candidate at the origin of the problems

    2. the query has spent most of the time in search of random table T2

    So while it is true that I don't know final A-lines of this cancelled query information, I can still say a lot of this and begin to deal with the problems identified so far.

    Randolf

  • APEX listener returns the empty login page

    APEX 4.2.2

    APEX 2.0.2 listener

    GlassFish 3.1.2.2

    The platform is 32-bit, Linux, Amazon EC2

    I am reasonably sure I have properly deployed the apex.war and i.war to Glassfish and set a virtual path and database connection correctly.

    When you run Firefox on the EC2 machine, access to the

    http://localhost: 8080/apex/dad1.

    does not return a login page, no problem. But navigation externally visible publicly address (I have to hide the real address, I'll use a.b.c.d) of the hosting machine or across the net returns a blank page:

    http://a.b.c.d:8080/apex/dad1.

    The success of this operation:

    http://a.b.c.d:8080

    I get the standard Glassfish page so I know Glassfish is listening on that address.

    I also tried from the stand-alone earphone, and I get the same effect: it refers to a login screen when browsing the localhost, but go to the external address, I get a blank page.

    The pages are really blank, there is no indication in the source of the page and it's all Firebug returns:

    <html>

    <> Chief

    "" <link title= "wrap long lines" " href="resource://gre-resources/plaintext.css" type="text/css"" rel= "alternative style"> "

    < /head>

    <> body

    <>of thepre< /pre>

    < /body>

    < /html>


    I tried to enable the query server side, but I have yet to find the way to produce the equivalent of an access.log. Searching the forum produced a few references to "routing rules" but I couldn't find what and where he could be.

    As the listener works perfectly when you go to localhost, I can't believe that rthis is the common problem of not finding the vivid, or url mapping problem. But I am of course open to suggestions!

    Any idea will be welcome.

    Thank you for your time.

    Fixed. Finally tracked it, a redirection problem fixed with the patch 16760897.

    Thank you to everyone who watched this, I'm sorry to have lost your time, hope to post the solution will help someone else.

  • Studio MaxL helps

    Hi Experts,

    Currently I'm loading the ASO cube to essbase maxl script studio.

    Could help me please what script I have to join to this * "to enable the query and use already saved aggregation list."

    * "deploy the cube schema"\XXX""XXXX"model data connect 'XXX' identified by 'XXX' on the 'XXX' host for the database 'XXX' application 'XXX' crushes using values build streaming using the 'XXXX' connection keep 200 errors on error ignore loading default writing *;

    Please kindly help me realize this question.

    After your deploy command Add
    ALTER database enable query_tracking xxxxx.yyyyy;
    run the overall construction on xxxx.yyyy of database using view_file xxxxxx;

  • Deleting huge records with parallel option in a non-partitioned table

    Hi all

    Is it possible to run delete statement with sub query that removes millions of records in a table that is not partitioned with parallel option?

    SQL > Alter session enable parallel query.

    SQL > Alter session enable parallel dml.

    SQL > alter table table_A parallel 5;

    SQL > delete the table_A where colA = "zzzz";

    SQL > commit;

    SQL > alter table table_A noparallel;

    Please advice,

    Thanks in advance.

    user7280060 wrote:
    Hi all

    Is it possible to run delete statement with sub query that removes millions of records in a table that is not partitioned with parallel option?

    SQL > Alter session enable parallel query.

    SQL > Alter session enable parallel dml.

    SQL > alter table table_A parallel 5;

    SQL > delete the table_A where colA = "zzzz";

    SQL > commit;

    SQL > alter table table_A noparallel;

    Please advice,

    Thanks in advance.

    Yes

  • Need space between buttons displayed on the same line

    Hello - I have 3 buttons html:

    Cancel
    query
    create

    They must be displayed on the same line, in the regions of button. (They're in)
    the lower-left corner of the page; right now I'm on the région #CREATE #.)

    The position of cancel and the query is fine... but I need space (approximately that of a button
    Worth) between query and create. Can not know how to do this.

    Ideas?

    Thank you
    Carol

    Hi Carol,.

    It might be interesting to look at model in your region under the shared components > models > region change the model.
    You should see the place holders of section definition for your buttons etc. #CREATE # CANCEL #. I suggest that you make a copy of the model and then play with it maybe just add another tag td which is empty.

    IF you need help with it just post your definition here and I'll try and help you.

  • How to design this form code

    Hello
    Could someone shed some light on what is the best way to design this form. The muti-record block that has:
    columns family name, given name start_date and end_date (in the second block) that rely on the view.
    Now on the form in the first block, there are 2 query fields end_date1 and end_date2 are just filter to select records in the block 2 (multi record) which have end_date in this range. So that the user can enter two date to the 1st blockthen then run the query and in the 2nd block, records which have end_date range return.

    Since these 2 filters are not DB point so I used 2 control point for them, but I have problem to make them behave like normal DB points, such as the color and cancel the query key works as if the 2 fields were Articles of DB.

    Could you tell me what is the best way to design this situation for end_date1 and end_date2. Also is there a trigger for the function of query cancel key (as we trigger to the entered query function key)?


    Thanks for your help
    Michael

    Your description is fairly short and somewhat difficult to understand.

    It seems that you have two blocks, one being a block of control with two dates, and the other being the block of data based on a view.

    I do not understand why you want two dates in the block of the base table, or 'as normal elements DB '. It is easy to color, then why is it important to make them "Elements DB?

    I don't know why you are concerned about a button "Cancel request" or function. Why not get your form by working first? I have never found the need for such a feature. There is no trigger or function for "cancel query. There is point Abort_Query, which could be published as is the filling of lines in a block, and there is the menu, query, cancel, who just left the enter query mode. I have never used these features because they are of little use.

    The best way to do what you seem to try is to have a control block with your date of two fields which produces a range of dates.

    The user grasps the two dates, then based on a query or search button. In the trigger when button pressed, it emits a Go_block to the block of the table; basic, then Execute_Query

    And in the block of the base table, you define the place WHERE the property Clause: end_date between: CB.date_from and: CB.date_to

    In the above statement, CB is the name of the control bock.

  • DROP AND RE-CREATE ALL INDEXES

    Hi all

    I have a database with all the struture of tables and their indexes, but no data on the tables.

    I have scripts to import that will insert millions of rows in tables.

    What I want to do is:

    (1) built a sript which creates all indexes
    (2) remove all indexes
    (3) load all the data in the tables
    (4) create all indexes the sript running 1)

    My problem is on point 1). I don't know how to build this script.

    Thanks in advance for any help,

    RS

    Yes, I see that I go wrong here... once again ;-)

    I have also addressed this issue in the past and now, remember that there are also some Metalink Notes on this topic, where people complain about the same problem.
    Especially Note 394143.1 manages your problem
    I'm sorry for the mistake. Maybe this note helps.

    I went to the #3 option.

    Edit:
    In fact, it is the script to generate the DDL and put them in a CLOB table. In this case for Materialized views:

    Set serveroutput on;
    declare
    CLOB ddl_out;
    objname varchar2 (30): = ";
    tablechk varchar2 (100): = ";
    number of sqlorder: = 1;
    cursor c1 is select a.mview_name, a.owner from dba_mviews; -where owner = 'EHDA ";

    Start
    -Due to formatting problems dbms_metadata, the output is saved in a table that contains a clob column
    run immediately "drop table ddl_output;
    immediate ' create table ddl_output (objname varchar2 (30), ddl_query clob, number sqlorder);

    for r1 in c1
    loop
    dbms_output. Enable (10000);
    If objname = r1.mview_name
    then
    dbms_output.put_line (' treatment: ' |) R1.mview_name);
    on the other
    objname: = r1.mview_name;
    sqlorder: = 1;
    end if;
    insert into ddl_output values (r1.mview_name, 'drop the materialized view' |) R1.mview_name | ';', sqlorder);
    sqlorder: = sqlorder + 1;
    Select dbms_metadata.get_ddl ('MATERIALIZED_VIEW', "|) R1.mview_name: ",". R1.owner | ") in the double ddl_out;
    insert into ddl_output values (r1.mview_name, ddl_out |) ';', sqlorder);
    sqlorder: = sqlorder + 1; Select dbms_metadata.get_dependent_ddl ('INDEX', "|) R1.mview_name: ",". R1.owner | ") in the double ddl_out;
    insert into ddl_output values (r1.mview_name, ddl_out |) ';', sqlorder);
    sqlorder: = sqlorder + 1;
    commit;
    end loop;
    end;
    /

    After that which has finished, use the script below to recreate the object with the table DDL

    declare
    query varchar2 (2000);
    cursor c1 is select ddl_query from ddl_output by objname, sqlorder;

    BEGIN
    for r1 in c1
    loop
    dbms_output. Enable (999999);
    query: = r1.ddl_query;
    dbms_output.new_line ();
    dbms_output.put_line (Query);
    If length (query) > 5
    then
    immediate execution of the query;
    end if;

    end loop;
    end;
    /

    Published by: fjfranken on March 24, 2009 05:14

  • Implicit is column - I think about it the right way?

    My exploration of the implicit column is below. I would like to know if you think it's intended use.

    When the BI server sees a query where one Dimension is being constrained by another, you must choose a fact table containing references to these two dimensions. The "implicit fact column", which lies in the presentation layer of the RPD is used to guide the BI server to one or more fact tables that can be used to meet the demand. In the absence of the implicit column, I noticed that the BI server has been choosing random fact tables so I went to explore how this feature works. I set the implicit column in my presentation layer and then went looking for see how queries are generated.

    For my example, my two dimensions are program and channel. I want to see the list of channels available to a program. Without the of fact implicit column, queries are of the form:

    Select distinct T289. CHANNEL_NAME C1,
    T36001. Program name C2
    Of
    DIM_PROGRAMS T36001,
    DIM_CHANNELS T289,
    SomeRandomFactTable T41210
    where (T289. DIM_CHANNEL_KEY = T41210. DIM_CHANNEL_KEY and T36001. DIM_PROGRAM_KEY = T41210. DIM_PROGRAM_KEY)
    order by c1, c2

    The spotlight on this issue is that there is only one set of program / channel combinations returned. The downside is that the fact table that is chosen to solve the combinations can be any table actually within the jurisdiction of the BI server. It doesn't even have to be in the same domain where the program and the channel were chosen. When I put the column implied in fact, queries are of the form:

    Select distinct T289. CHANNEL_NAME C1,
    T36001. Program name C2,
    T35832. DIM_SITE_KEY / * this is the implicit column * /.
    Of
    DIM_PROGRAMS T36001,
    DIM_CHANNELS T289,
    AFactTableMappedToFactColumn T35832
    where (T289. DIM_CHANNEL_KEY = T35832. DIM_CHANNEL_KEY and T35832. DIM_PROGRAM_KEY = T36001. DIM_PROGRAM_KEY)
    order by c1, c2

    I was happy that I could predict what fact table has been used, but now the results are bad, I get a double set of records for each DIM_SITE_KEY / channel / program combination. I decided to play a little trick on the algebra. Knowing that the DIM_SITE_KEY has a numerical value, I set the implicit column referred as DIM_SITE_KEY / DIM_SITE_KEY which will always result in a value of 1. Now I get queries that look like:


    Select distinct T289. CHANNEL_NAME C1,
    T36001. Program name C2,
    T35832. DIM_SITE_KEY / nullif (T35832. DIM_SITE_KEY, 0) as c3
    Of
    DIM_PROGRAMS T36001,
    DIM_CHANNELS T289,
    AFactTableMappedToFactColumn T35832
    where (T289. DIM_CHANNEL_KEY = T35832. DIM_CHANNEL_KEY and T35832. DIM_PROGRAM_KEY = T36001. DIM_PROGRAM_KEY)
    order by c1, c2

    Since the DIM_SITE_KEY / DIM_SITE_KEY is always equal to 1, I get only a set of program / channel combinations. I get the added benefit of knowing what set of fact tables will be used to satisfy the query.

    Perfect analysis, but an important point is when you use the default fact table, always choose a measure (which has an aggregation) as a column made implicit. So this will enables the query will remove duplicate lines by a group by operation.

    Another point is to ensure that the performance is good. When we do not have a good model for the fact tables, the tables contains the large data set, make sure that the performance is good by indexes or caching to load guests.

    -Madan

  • online banking can't watch cancelled check opening, it says item query not found. How to fix?

    online banking can't watch cancelled check opening, it says item query not found.  How to fix?

    online banking can't watch cancelled check opening, it says item query not found.  How to fix?

    Contact online banking support team. This has nothing to do with the topic of this forum.

  • LogInsight - need to 'cancel the query' button on the interactive analytical page.

    Case there when we need to find some first occurrences of the event. It could be an extensive research on all the time and we want an opportunity to cancel (stop, pause) the request once it finds few results.

    the function to cancel the running query exists, but you must browse the page admin for it. We need a button on the interactive analytical page.

    Thank you

    ildus

    Hey Ildus,.

    This feature exists on the page of the AI for queries that take a long time to execute (see attachment) - you must hover over an event once the results are returned to see the option (note is put in pause/resume). Looking for something else?

Maybe you are looking for