Plan table column Time

Hi,
In the oracle documentation the column time means the elapsed time of operation as estimated by the optimizer. can any body help me to understand why the value of this one is always equal to 00:00:01? even when i perform explain plan for query that takes much more time?
Thanks in advance
Message was edited by:
user470263

Since the cost and time reported by explain plan are just scaled copies of each other, the time prediction is just as valid (or invalid) as the cost prediction.
The optimiser has several flaws in the model including:
* Not allowing for caching effects
* Not dealing properly with correlation between columns
* Not having a good model of data patterns and scatter in all cases
The optimizer is also undermined by the run-time engine which has some mechanical efficiencies built into it that are not "known" to the optimizer.
Consequently, the predicted cost and time for a query should only be used as a detail to help you understand the cases where the optimizer has chosen an unsuitable execution plan.
Regards
Jonathan Lewis
http://jonathanlewis.wordpress.com
http://www.jlcomp.demon.co.uk

Similar Messages

MF50 : Planning table and planning time fence

HI,
I use the transaction MF50 as planning table ( in order to do my MPS planning), I use "set firming date" to fix a firming date.
Now, I want o know if it should possible to reveal a message when we create a planned order within the firming date??
Thanks for your answer.

Hi,
For clarity , I am describing below the functionlity of Set Firming date is explained as below:
By setting Manual Firming date , we extend the planning time fence.
If a planning time fence has been created for a material then the following applies:
If the manual firming date lies before the end of the planning time fence, the planning time fence is still valid.
If the manual firming date lies after the end of the planning time fence, the planning time fence is extended until this date.
All order proposals with availability dates that lie before the end of the planning time fence of the manually extended planning fence are firmed for the planning run, if the materials have an MRP type which contains firming type or firming type 1 or 2
The system does not automatically firm order proposals for materials that have an MRP type with firming type 3 or 4, even if their availability dates lie before the end of the planning time fence or manually extended planning time fence.
Please check if this helps you.
Regards
Datta

Getting table column header names from database

Hi,
We are trying to get table headers from database. So when we query the database it returns multiple rows at the same time. How can we display specific table column headers from the returned result set at respective places.
We tried using record selection expert but that only works for one selection and not for others.
How can we do this?

Thank you Josh and Abhilash for helping us.
We are using PostgreSql.
"command_headers" has query which looks like following-
SELECT id, header FROM labels
WHERE id='header.header_1'
OR id='header.header_2'
OR id='header.header_3'
ORDER BY id;
which will return following result set-
id                              header
header.header_1        Header1
header.header_2        Header2
header.header_3        Header3
Our Table structure is something like this-
Page Header: Header1                        | Header2                       | Header3
Details:           {command_data.value1} | {command_data.value2} | {command_data.value3}
command_data is another command which generates data for the table.
All values in details section coming from command_data is in format string.
We don't need to apply grouping or sub totals. This is a simple table, showing string values for all columns.
Preview:
Header1     |     Header2     |     Header3
car              |     yello           |     abc
bike            |     black          |     xyz
plane          |     white           |     pqr
Currently, all headers are static labels. How do we use "command_headers" to display all table Headers dynamically? Can we achieve this format using cross tab?

Tuning : Inconsistent result between Explain plan VS Execution Time

Dear Experts,
Need your suggestions belongs to contrary result between Explain plan VS Execution Time
Environment :_
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit
PL/SQL Release 10.2.0.4.0 - Production
CORE     10.2.0.4.0     Production
TNS for Linux: Version 10.2.0.4.0 - Production
NLSRTL Version 10.2.0.4.0 - Production
Red Hat Enterprise Linux 5.4
There's same query but : 1st query access Loan_Account, 2nd query access Loan_Account_Han
*1st.*
Query Access Via : Loan_account (Partition Type : Hash (5) with column Contract_Number)
Explain Plan : cost: 4,432, bytes: 716, cardinality: 2
Execution Time : 13 seconds
*2nd.*
Query Access Via : Loan_Account_Han (Partition Type : List(5) with column Loan_Status)
Explain Plan : cost:188,447 bytes: 1,661,088, cardinality: 4,719
Execution Time : 10 seconds
Note :_
all tables and all indexes belong to the table which included in query has been analyzed.
my question :
1. why it could become like this ? I even confusing with Jonathan Lewis Theory : Cost-Based Fundamental Book.
with this result, I even not believed with the result from Explain Plan anymore.
2. If analyze tables and indexes to update statistics which help CBO to choose the best path as part of Daily Performance Tuning,
is there a way that could do in enviroment 24x7 ?
Note : if original query is needed, I'll posting it here.
Any help is very appreciated and thanks very much.
Regards,
Sigcle

The DBMS_XPLAN.DISPLAY_CURSOR output
Query no 1
PLAN_TABLE_OUTPUT
SQL_ID bq7avs72xvmkv, child number 0
SELECT /*+ gather_plan_statistics */ la.office_code, la.currency_code AS currency, mf.NAME multifinance_id,        la.contract_number, mc.customer_name,
dco.os_principal_on_schedule AS os_principal_on_schedule,        f_get_param_value (la.financing_type,                           'FinancingType'
       ) AS financing_type,        CASE la.financing_type           WHEN 11                    -- Asset Purchase              THEN NVL (tp.os_principal_cust,
                  la.os_principal_cust                       )           WHEN 12                                            -- JF Channelling              THEN
NVL (tp.os_principal_mf, la.os_principal)        END AS os_principal_actual,        CASE           WHEN dco.bi_collectibility_with_gp >= 3              THEN 0
      ELSE CASE           WHEN la.financing_type = '12'              THEN   NVL (ia.accrue_interest_pl, 0)                   + NVL (ia.accrue_interest_npl, 0)
      ELSE   NVL (ia.accrue_
Plan hash value: 4011856754
| Id | Operation                                  | Name                           | Starts | E-Rows | A-Rows |   A-Time   | Buffers | Reads | OMem | 1Mem | Used-Mem |
|   1 | TABLE ACCESS BY INDEX ROWID               | COLLECTIBILITY_CODE            |      3 |      1 |      3 |00:00:00.01 |       9 |      2 |       |       |          |
|* 2 |   INDEX SKIP SCAN                          | UNQ_COLLECTIBILITY_CODE        |      3 |      1 |      3 |00:00:00.01 |       6 |      1 |       |       |          |
|   3 | TABLE ACCESS BY GLOBAL INDEX ROWID        | MF_SCH_INSTALLMENT             |    501 |      1 |    501 |00:00:00.03 |    2004 |    796 |       |       |          |
|* 4 |   INDEX UNIQUE SCAN                        | UNQ_MF_SCH_INSTALLMENT1        |    501 |      1 |    501 |00:00:00.02 |    1503 |    377 |       |       |          |
|   5 | TABLE ACCESS BY GLOBAL INDEX ROWID        | MF_SCH_INSTALLMENT             |    333 |      1 |    333 |00:00:00.10 |    3220 |   1074 |       |       |          |
|* 6 |   INDEX UNIQUE SCAN                        | UNQ_MF_SCH_INSTALLMENT1        |    333 |      1 |    333 |00:00:00.09 |    2887 |   1074 |       |       |          |
|   7 |   TABLE ACCESS BY GLOBAL INDEX ROWID       | CUST_SCH_INSTALLMENT           |    168 |      1 |    167 |00:00:00.05 |    1464 |    495 |       |       |          |
|* 8 |    INDEX UNIQUE SCAN                       | UNQ_CUST_SCH_INSTALLMENT1      |    168 |      1 |    167 |00:00:00.05 |    1297 |    495 |       |       |          |
|   9 | TABLE ACCESS BY GLOBAL INDEX ROWID        | MF_SCH_INSTALLMENT             |    333 |      1 |    333 |00:00:00.06 |    3167 |      0 |       |       |          |
|* 10 |   INDEX UNIQUE SCAN                        | UNQ_MF_SCH_INSTALLMENT1        |    333 |      1 |    333 |00:00:00.06 |    2834 |      0 |       |       |          |
| 11 |   TABLE ACCESS BY GLOBAL INDEX ROWID       | CUST_SCH_INSTALLMENT           |    168 |      1 |    167 |00:00:00.03 |    1447 |      0 |       |       |          |
|* 12 |    INDEX UNIQUE SCAN                       | UNQ_CUST_SCH_INSTALLMENT1      |    168 |      1 |    167 |00:00:00.03 |    1280 |      0 |       |       |          |
| 13 | TABLE ACCESS BY GLOBAL INDEX ROWID        | MF_SCH_INSTALLMENT             |    333 |      1 |    333 |00:00:00.06 |    3167 |      0 |       |       |          |
|* 14 |   INDEX UNIQUE SCAN                        | UNQ_MF_SCH_INSTALLMENT1        |    333 |      1 |    333 |00:00:00.06 |    2834 |      0 |       |       |          |
| 15 |   TABLE ACCESS BY GLOBAL INDEX ROWID       | CUST_SCH_INSTALLMENT           |    168 |      1 |    167 |00:00:00.03 |    1447 |      0 |       |       |          |
|* 16 |    INDEX UNIQUE SCAN                       | UNQ_CUST_SCH_INSTALLMENT1      |    168 |      1 |    167 |00:00:00.03 |    1280 |      0 |       |       |          |
| 17 | TABLE ACCESS BY GLOBAL INDEX ROWID        | MF_SCH_INSTALLMENT             |    333 |      1 |    333 |00:00:00.06 |    3167 |      0 |       |       |          |
|* 18 |   INDEX UNIQUE SCAN                        | UNQ_MF_SCH_INSTALLMENT1        |    333 |      1 |    333 |00:00:00.06 |    2834 |      0 |       |       |          |
| 19 |   TABLE ACCESS BY GLOBAL INDEX ROWID       | CUST_SCH_INSTALLMENT           |    168 |      1 |    167 |00:00:00.03 |    1447 |      0 |       |       |          |
|* 20 |    INDEX UNIQUE SCAN                       | UNQ_CUST_SCH_INSTALLMENT1      |    168 |      1 |    167 |00:00:00.03 |    1280 |      0 |       |       |          |
|* 21 | TABLE ACCESS FULL                         | COLLECTIBILITY_CODE            |      3 |      1 |      3 |00:00:00.01 |      12 |      1 |       |       |          |
| 22 | NESTED LOOPS OUTER                        |                                |      1 |      2 |    501 |00:00:01.02 |   96112 | 20091 |       |       |          |
| 23 |   NESTED LOOPS                             |                                |      1 |      2 |    501 |00:00:00.28 |   13445 |   5358 |       |       |          |
| 24 |    NESTED LOOPS                            |                                |      1 |      2 |    501 |00:00:00.26 |   11441 |   5071 |       |       |          |
| 25 |     NESTED LOOPS OUTER                     |                                |      1 |      2 |    501 |00:00:00.24 |    9433 |   5014 |       |       |          |
|* 26 |      HASH JOIN                             |                                |      1 |      2 |    501 |00:00:00.03 |     329 |    325 | 1206K| 1206K| 341K (0)|
|* 27 |       TABLE ACCESS FULL                    | CURRENCY                       |      1 |      1 |      1 |00:00:00.01 |       3 |      2 |       |       |          |
|* 28 |       HASH JOIN                            |                                |      1 |     61 |    501 |00:00:00.02 |     326 |    323 |   868K|   868K| 947K (0)|
|* 29 |        HASH JOIN                           |                                |      1 |     10 |     13 |00:00:00.01 |       7 |      6 |   947K|   947K| 1030K (0)|
| 30 |         TABLE ACCESS BY INDEX ROWID        | MULTIFINANCE                   |      1 |      5 |      9 |00:00:00.01 |       2 |      2 |       |       |          |
|* 31 |          INDEX RANGE SCAN                  | IDX_STATUS_MF                  |      1 |      5 |      9 |00:00:00.01 |       1 |      1 |       |       |          |
|* 32 |         TABLE ACCESS FULL                  | AGREEMENT                      |      1 |     18 |     13 |00:00:00.01 |       5 |      4 |       |       |          |
| 33 |        VIEW                                |                                |      1 |    110 |    501 |00:00:00.02 |     319 |    317 |       |       |          |
|* 34 |         HASH JOIN RIGHT OUTER              |                                |      1 |    110 |    501 |00:00:00.02 |     319 |    317 | 1011K| 1011K| 317K (0)|
| 35 |          TABLE ACCESS BY INDEX ROWID       | TENANT_PARAMETER               |      1 |      1 |      1 |00:00:00.01 |       2 |      2 |       |       |          |
|* 36 |           INDEX UNIQUE SCAN                | PK_TENANT_PARAMETER            |      1 |      1 |      1 |00:00:00.01 |       1 |      1 |       |       |          |
|* 37 |          TABLE ACCESS BY GLOBAL INDEX ROWID| LOAN_ACCOUNT                   |      1 |    110 |    501 |00:00:00.02 |     317 |    315 |       |       |          |
|* 38 |           INDEX RANGE SCAN                 | IDX_STATUS_LA1                 |      1 |   4394 |   3025 |00:00:00.01 |      15 |     14 |       |       |          |
|* 39 |      TABLE ACCESS BY INDEX ROWID           | TX_PAYMENT                     |    501 |      1 |      0 |00:00:00.16 |    9104 |   4689 |       |       |          |
|* 40 |       INDEX RANGE SCAN                     | FK_TX_PAY_LOAN_ACCT            |    501 |     12 |   8799 |00:00:00.02 |    1038 |    207 |       |       |          |
| 41 |     TABLE ACCESS BY INDEX ROWID            | DL_CL_OUTSTANDING              |    501 |      1 |    501 |00:00:00.02 |    2008 |     57 |       |       |          |
|* 42 |      INDEX RANGE SCAN                      | IDXLO_CNUM                     |    501 |      1 |    501 |00:00:00.01 |    1507 |     37 |       |       |          |
|* 43 |    TABLE ACCESS BY INDEX ROWID             | MF_CUSTOMER                    |    501 |      1 |    501 |00:00:00.02 |    2004 |    287 |       |       |          |
|* 44 |     INDEX UNIQUE SCAN                      | MF_CUSTOMER_PK                 |    501 |      1 |    501 |00:00:00.01 |    1503 |     24 |       |       |          |
|* 45 |   TABLE ACCESS BY INDEX ROWID              | TX_INTEREST_ACCRUE             |    501 |      1 |      0 |00:00:00.73 |   82667 | 14733 |       |       |          |
|* 46 |    INDEX RANGE SCAN                        | FK_TX_INTEREST_ACCRUE_LOAN_ACC |    501 |     67 | 40581 |00:00:00.14 |   42084 |    451 |       |       |          |
Predicate Information (identified by operation id):
   2 - access("XX"."COLLECTIBILITY_CODE"=:B1)
       filter("XX"."COLLECTIBILITY_CODE"=:B1)
   4 - access("LOAN_ACCOUNT_ID"=:B1 AND "INSTALLMENT_NUMBER"=1)
   6 - access("MFSCH"."LOAN_ACCOUNT_ID"=:B1 AND "MFSCH"."INSTALLMENT_NUMBER"="F_NEXT_INSTALLMENT_NUMBER"(:B2,TO_DATE(' 2013-02-18 00:00:00', 'syyyy-mm-dd
              hh24:mi:ss'),:B3))
   8 - access("CUSTSCH"."LOAN_ACCOUNT_ID"=:B1 AND "CUSTSCH"."INSTALLMENT_NUMBER"="F_NEXT_INSTALLMENT_NUMBER"(:B2,TO_DATE(' 2013-02-18 00:00:00', 'syyyy-mm-dd
              hh24:mi:ss'),:B3))
10 - access("MFSCH"."LOAN_ACCOUNT_ID"=:B1 AND "MFSCH"."INSTALLMENT_NUMBER"="F_NEXT_INSTALLMENT_NUMBER"(:B2,TO_DATE(' 2013-02-18 00:00:00', 'syyyy-mm-dd
              hh24:mi:ss'),:B3))
12 - access("CUSTSCH"."LOAN_ACCOUNT_ID"=:B1 AND "CUSTSCH"."INSTALLMENT_NUMBER"="F_NEXT_INSTALLMENT_NUMBER"(:B2,TO_DATE(' 2013-02-18 00:00:00', 'syyyy-mm-dd
              hh24:mi:ss'),:B3))
14 - access("MFSCH"."LOAN_ACCOUNT_ID"=:B1 AND "MFSCH"."INSTALLMENT_NUMBER"="F_NEXT_INSTALLMENT_NUMBER"(:B2,TO_DATE(' 2013-02-18 00:00:00', 'syyyy-mm-dd
              hh24:mi:ss'),:B3))
16 - access("CUSTSCH"."LOAN_ACCOUNT_ID"=:B1 AND "CUSTSCH"."INSTALLMENT_NUMBER"="F_NEXT_INSTALLMENT_NUMBER"(:B2,TO_DATE(' 2013-02-18 00:00:00', 'syyyy-mm-dd
              hh24:mi:ss'),:B3))
18 - access("MFSCH"."LOAN_ACCOUNT_ID"=:B1 AND "MFSCH"."INSTALLMENT_NUMBER"="F_NEXT_INSTALLMENT_NUMBER"(:B2,TO_DATE(' 2013-02-18 00:00:00', 'syyyy-mm-dd
              hh24:mi:ss'),:B3))
20 - access("CUSTSCH"."LOAN_ACCOUNT_ID"=:B1 AND "CUSTSCH"."INSTALLMENT_NUMBER"="F_NEXT_INSTALLMENT_NUMBER"(:B2,TO_DATE(' 2013-02-18 00:00:00', 'syyyy-mm-dd
              hh24:mi:ss'),:B3))
21 - filter(TO_NUMBER("COL"."COLLECTIBILITY_CODE")=:B1)
26 - access("from$_subquery$_016"."CURRENCY_CODE"="CURR"."CURRENCY_CODE")
27 - filter(UPPER("CURR"."STATUS")='A')
28 - access("from$_subquery$_016"."AGREEMENT_ID"="A"."AGREEMENT_ID")
29 - access("A"."MULTIFINANCE_ID"="MF"."MULTIFINANCE_ID")
31 - access("MF"."SYS_NC00052$"='A')
32 - filter(UPPER("A"."STATUS")='A')
34 - access("LA"."TENANT_ID"="TENANT_ID")
36 - access("TENANT_PARAMETER_ID"=23)
37 - filter((UPPER("LA"."LOAN_STATUS")='AC' OR ("LA"."CLOSED_DATE"=TO_DATE(' 2013-02-18 00:00:00', 'syyyy-mm-dd hh24:mi:ss') AND
              UPPER("LA"."LOAN_STATUS")='CN')))
38 - access("LA"."SYS_NC00118$"='A')
39 - filter(("TP"."APPROVAL_DATE"=TO_DATE(' 2013-02-18 00:00:00', 'syyyy-mm-dd hh24:mi:ss') AND "TP"."DATA_SOURCE"=152 AND UPPER("TP"."APPROVAL_STATUS")='A'))
40 - access("TP"."LOAN_ACCOUNT_ID"="from$_subquery$_016"."LOAN_ACCOUNT_ID")
42 - access("DCO"."LOAN_CONTRACT_NUMBER"="from$_subquery$_016"."CONTRACT_NUMBER")
43 - filter(UPPER("MC"."STATUS")='A')
44 - access("from$_subquery$_016"."MF_CUSTOMER_ID"="MC"."MF_CUSTOMER_ID")
45 - filter("IA"."ACCRUE_DATE"="XX"."PREV_DATE")
46 - access("LA"."LOAN_ACCOUNT_ID"="IA"."LOAN_ACCOUNT_ID")
The DBMS_XPLAN.DISPLAY_CURSOR output after : alter system flush buffer_cache; alter system flush shared_pool;
Query no 2
PLAN_TABLE_OUTPUT
SQL_ID cxmg4jfvr9pz0, child number 0
SELECT /*+ gather_plan_statistics */ la.office_code, la.currency_code AS currency, mf.NAME multifinance_id,        la.contract_number, mc.customer_name,
dco.os_principal_on_schedule AS os_principal_on_schedule,        f_get_param_value (la.financing_type,                           'FinancingType'
       ) AS financing_type,        CASE la.financing_type           WHEN 11                    -- Asset Purchase              THEN NVL (tp.os_principal_cust,
                  la.os_principal_cust                       )           WHEN 12                                            -- JF Channelling              THEN
NVL (tp.os_principal_mf, la.os_principal)        END AS os_principal_actual,        CASE           WHEN dco.bi_collectibility_with_gp >= 3              THEN 0
      ELSE CASE           WHEN la.financing_type = '12'              THEN   NVL (ia.accrue_interest_pl, 0)                   + NVL (ia.accrue_interest_npl, 0)
      ELSE   NVL (ia.accrue_
Plan hash value: 2072372033
| Id | Operation                            | Name                           | Rows | Bytes | Cost (%CPU)| Time     | Pstart| Pstop |
|   0 | SELECT STATEMENT                     |                                | 4719 | 1622K|   188K (32)| 00:37:42 |       |       |
|   1 | TABLE ACCESS BY INDEX ROWID         | COLLECTIBILITY_CODE            |     1 |    12 |     3   (0)| 00:00:01 |       |       |
|* 2 |   INDEX SKIP SCAN                    | UNQ_COLLECTIBILITY_CODE        |     1 |       |     2   (0)| 00:00:01 |       |       |
|   3 | TABLE ACCESS BY GLOBAL INDEX ROWID | MF_SCH_INSTALLMENT             |     1 |    17 |     3   (0)| 00:00:01 | ROWID | ROWID |
|* 4 |   INDEX UNIQUE SCAN                  | UNQ_MF_SCH_INSTALLMENT1        |     1 |       |     2   (0)| 00:00:01 |       |       |
|   5 | TABLE ACCESS BY GLOBAL INDEX ROWID | MF_SCH_INSTALLMENT             |     1 |    15 |     3   (0)| 00:00:01 | ROWID | ROWID |
|* 6 |   INDEX UNIQUE SCAN                  | UNQ_MF_SCH_INSTALLMENT1        |     1 |       |     2   (0)| 00:00:01 |       |       |
|   7 |   TABLE ACCESS BY GLOBAL INDEX ROWID | CUST_SCH_INSTALLMENT           |     1 |    15 |     3   (0)| 00:00:01 | ROWID | ROWID |
|* 8 |    INDEX UNIQUE SCAN                 | UNQ_CUST_SCH_INSTALLMENT1      |     1 |       |     2   (0)| 00:00:01 |       |       |
|   9 | TABLE ACCESS BY GLOBAL INDEX ROWID | MF_SCH_INSTALLMENT             |     1 |    15 |     3   (0)| 00:00:01 | ROWID | ROWID |
|* 10 |   INDEX UNIQUE SCAN                  | UNQ_MF_SCH_INSTALLMENT1        |     1 |       |     2   (0)| 00:00:01 |       |       |
| 11 |   TABLE ACCESS BY GLOBAL INDEX ROWID | CUST_SCH_INSTALLMENT           |     1 |    15 |     3   (0)| 00:00:01 | ROWID | ROWID |
|* 12 |    INDEX UNIQUE SCAN                 | UNQ_CUST_SCH_INSTALLMENT1      |     1 |       |     2   (0)| 00:00:01 |       |       |
| 13 | TABLE ACCESS BY GLOBAL INDEX ROWID | MF_SCH_INSTALLMENT             |     1 |    17 |     3   (0)| 00:00:01 | ROWID | ROWID |
|* 14 |   INDEX UNIQUE SCAN                  | UNQ_MF_SCH_INSTALLMENT1        |     1 |       |     2   (0)| 00:00:01 |       |       |
| 15 |   TABLE ACCESS BY GLOBAL INDEX ROWID | CUST_SCH_INSTALLMENT           |     1 |    17 |     3   (0)| 00:00:01 | ROWID | ROWID |
|* 16 |    INDEX UNIQUE SCAN                 | UNQ_CUST_SCH_INSTALLMENT1      |     1 |       |     2   (0)| 00:00:01 |       |       |
| 17 | TABLE ACCESS BY GLOBAL INDEX ROWID | MF_SCH_INSTALLMENT             |     1 |    17 |     3   (0)| 00:00:01 | ROWID | ROWID |
|* 18 |   INDEX UNIQUE SCAN                  | UNQ_MF_SCH_INSTALLMENT1        |     1 |       |     2   (0)| 00:00:01 |       |       |
| 19 |   TABLE ACCESS BY GLOBAL INDEX ROWID | CUST_SCH_INSTALLMENT           |     1 |    17 |     3   (0)| 00:00:01 | ROWID | ROWID |
|* 20 |    INDEX UNIQUE SCAN                 | UNQ_CUST_SCH_INSTALLMENT1      |     1 |       |     2   (0)| 00:00:01 |       |       |
|* 21 | TABLE ACCESS FULL                   | COLLECTIBILITY_CODE            |     1 |    12 |     3   (0)| 00:00:01 |       |       |
| 22 | NESTED LOOPS                        |                                | 4719 | 1622K|   188K (32)| 00:37:42 |       |       |
| 23 |   NESTED LOOPS                       |                                | 4719 | 1460K|   183K (33)| 00:36:45 |       |       |
| 24 |    NESTED LOOPS OUTER                |                                | 4719 | 1354K|   180K (33)| 00:36:07 |       |       |
| 25 |     NESTED LOOPS OUTER               |                                | 4719 | 1225K|   130K (46)| 00:26:01 |       |       |
|* 26 |      HASH JOIN                       |                                | 4719 | 1106K| 23591   (2)| 00:04:44 |       |       |
| 27 |       TABLE ACCESS BY INDEX ROWID    | MULTIFINANCE                   |     5 |   130 |     2   (0)| 00:00:01 |       |       |
|* 28 |        INDEX RANGE SCAN              | IDX_STATUS_MF                  |     5 |       |     1   (0)| 00:00:01 |       |       |
|* 29 |       HASH JOIN                      |                                | 8494 | 1775K| 23589   (2)| 00:04:44 |       |       |
|* 30 |        TABLE ACCESS FULL             | AGREEMENT                      |    18 |   360 |     3   (0)| 00:00:01 |       |       |
|* 31 |        HASH JOIN                     |                                | 8494 | 1609K| 23585   (2)| 00:04:44 |       |       |
|* 32 |         TABLE ACCESS FULL            | CURRENCY                       |     1 |     4 |     3   (0)| 00:00:01 |       |       |
| 33 |         VIEW                         |                                |   212K|    38M| 23579   (2)| 00:04:43 |       |       |
|* 34 |          HASH JOIN RIGHT OUTER       |                                |   212K|    32M| 23579   (2)| 00:04:43 |       |       |
| 35 |           TABLE ACCESS BY INDEX ROWID| TENANT_PARAMETER               |     1 |    74 |     1   (0)| 00:00:01 |       |       |
|* 36 |            INDEX UNIQUE SCAN         | PK_TENANT_PARAMETER            |     1 |       |     0   (0)| 00:00:01 |       |       |
| 37 |           PARTITION LIST ALL         |                                |   212K|    17M| 23575   (2)| 00:04:43 |     1 |     5 |
|* 38 |            TABLE ACCESS FULL         | LOAN_ACCOUNT_HAN               |   212K|    17M| 23575   (2)| 00:04:43 |     1 |     5 |
| 39 |      TABLE ACCESS BY INDEX ROWID     | TX_INTEREST_ACCRUE             |     1 |    26 |   130K (46)| 00:26:01 |       |       |
| 40 |       BITMAP CONVERSION TO ROWIDS    |                                |       |       |            |          |       |       |
| 41 |        BITMAP AND                    |                                |       |       |            |          |       |       |
| 42 |         BITMAP CONVERSION FROM ROWIDS|                                |       |       |            |          |       |       |
|* 43 |          INDEX RANGE SCAN            | FK_TX_INTEREST_ACCRUE_LOAN_ACC |    67 |       |     0   (0)| 00:00:01 |       |       |
| 44 |         BITMAP CONVERSION FROM ROWIDS|                                |       |       |            |          |       |       |
|* 45 |          INDEX RANGE SCAN            | IDX_TX_INTEREST_ACCRUE         |    67 |       |    12 (100)| 00:00:01 |       |       |
|* 46 |     TABLE ACCESS BY INDEX ROWID      | TX_PAYMENT                     |     1 |    28 |    11   (0)| 00:00:01 |       |       |
|* 47 |      INDEX RANGE SCAN                | FK_TX_PAY_LOAN_ACCT            |    12 |       |     0   (0)| 00:00:01 |       |       |
| 48 |    TABLE ACCESS BY INDEX ROWID       | DL_CL_OUTSTANDING              |     1 |    23 |     1   (0)| 00:00:01 |       |       |
|* 49 |     INDEX RANGE SCAN                 | IDXLO_CNUM                     |     1 |       |     0   (0)| 00:00:01 |       |       |
|* 50 |   TABLE ACCESS BY INDEX ROWID        | MF_CUSTOMER                    |     1 |    35 |     1   (0)| 00:00:01 |       |       |
|* 51 |    INDEX UNIQUE SCAN                 | MF_CUSTOMER_PK                 |     1 |       |     0   (0)| 00:00:01 |       |       |
Predicate Information (identified by operation id):
   2 - access("XX"."COLLECTIBILITY_CODE"=:B1)
       filter("XX"."COLLECTIBILITY_CODE"=:B1)
   4 - access("LOAN_ACCOUNT_ID"=:B1 AND "INSTALLMENT_NUMBER"=1)
   6 - access("MFSCH"."LOAN_ACCOUNT_ID"=:B1 AND "MFSCH"."INSTALLMENT_NUMBER"="F_NEXT_INSTALLMENT_NUMBER"(:B2,TO_DATE('
              2013-02-18 00:00:00', 'syyyy-mm-dd hh24:mi:ss'),:B3))
   8 - access("CUSTSCH"."LOAN_ACCOUNT_ID"=:B1 AND "CUSTSCH"."INSTALLMENT_NUMBER"="F_NEXT_INSTALLMENT_NUMBER"(:B2,TO_DATE('
              2013-02-18 00:00:00', 'syyyy-mm-dd hh24:mi:ss'),:B3))
10 - access("MFSCH"."LOAN_ACCOUNT_ID"=:B1 AND "MFSCH"."INSTALLMENT_NUMBER"="F_NEXT_INSTALLMENT_NUMBER"(:B2,TO_DATE('
              2013-02-18 00:00:00', 'syyyy-mm-dd hh24:mi:ss'),:B3))
12 - access("CUSTSCH"."LOAN_ACCOUNT_ID"=:B1 AND "CUSTSCH"."INSTALLMENT_NUMBER"="F_NEXT_INSTALLMENT_NUMBER"(:B2,TO_DATE('
              2013-02-18 00:00:00', 'syyyy-mm-dd hh24:mi:ss'),:B3))
14 - access("MFSCH"."LOAN_ACCOUNT_ID"=:B1 AND "MFSCH"."INSTALLMENT_NUMBER"="F_NEXT_INSTALLMENT_NUMBER"(:B2,TO_DATE('
              2013-02-18 00:00:00', 'syyyy-mm-dd hh24:mi:ss'),:B3))
16 - access("CUSTSCH"."LOAN_ACCOUNT_ID"=:B1 AND "CUSTSCH"."INSTALLMENT_NUMBER"="F_NEXT_INSTALLMENT_NUMBER"(:B2,TO_DATE('
              2013-02-18 00:00:00', 'syyyy-mm-dd hh24:mi:ss'),:B3))
18 - access("MFSCH"."LOAN_ACCOUNT_ID"=:B1 AND "MFSCH"."INSTALLMENT_NUMBER"="F_NEXT_INSTALLMENT_NUMBER"(:B2,TO_DATE('
              2013-02-18 00:00:00', 'syyyy-mm-dd hh24:mi:ss'),:B3))
20 - access("CUSTSCH"."LOAN_ACCOUNT_ID"=:B1 AND "CUSTSCH"."INSTALLMENT_NUMBER"="F_NEXT_INSTALLMENT_NUMBER"(:B2,TO_DATE('
              2013-02-18 00:00:00', 'syyyy-mm-dd hh24:mi:ss'),:B3))
21 - filter(TO_NUMBER("COL"."COLLECTIBILITY_CODE")=:B1)
26 - access("A"."MULTIFINANCE_ID"="MF"."MULTIFINANCE_ID")
28 - access(UPPER("STATUS")='A')
29 - access("from$_subquery$_016"."AGREEMENT_ID"="A"."AGREEMENT_ID")
30 - filter(UPPER("A"."STATUS")='A')
31 - access("from$_subquery$_016"."CURRENCY_CODE"="CURR"."CURRENCY_CODE")
32 - filter(UPPER("CURR"."STATUS")='A')
34 - access("LA"."TENANT_ID"="TENANT_ID"(+))
36 - access("TENANT_PARAMETER_ID"(+)=23)
38 - filter((UPPER("LA"."LOAN_STATUS")='AC' OR "LA"."CLOSED_DATE"=TO_DATE(' 2013-02-18 00:00:00', 'syyyy-mm-dd hh24:mi:ss')
              AND UPPER("LA"."LOAN_STATUS")='CN') AND UPPER("LA"."STATUS")='A')
43 - access("LA"."LOAN_ACCOUNT_ID"="IA"."LOAN_ACCOUNT_ID"(+))
45 - access("IA"."ACCRUE_DATE"(+)="XX"."PREV_DATE")
46 - filter("TP"."APPROVAL_DATE"(+)=TO_DATE(' 2013-02-18 00:00:00', 'syyyy-mm-dd hh24:mi:ss') AND "TP"."DATA_SOURCE"(+)=152
              AND UPPER("TP"."APPROVAL_STATUS"(+))='A')
47 - access("TP"."LOAN_ACCOUNT_ID"(+)="from$_subquery$_016"."LOAN_ACCOUNT_ID")
49 - access("DCO"."LOAN_CONTRACT_NUMBER"="from$_subquery$_016"."CONTRACT_NUMBER")
50 - filter(UPPER("MC"."STATUS")='A')
51 - access("from$_subquery$_016"."MF_CUSTOMER_ID"="MC"."MF_CUSTOMER_ID")Typically both query running on 10-12 seconds (or same execution time).
And I can't provide autotrace and tkprof output cause I cannot access via sqlplus.
Thanks very much for the link HOW TO: Post a SQL statement tuning request - template posting
Regards,
Sigcle
Edited by: SigCle on Feb 25, 2013 4:22 AM

BUG: Export DDL and Data fails for mixed case table/column names

Hi there,
I have found a bug in SQL Developer. See details below.
Description:
When "Export DDL and Data) function is used on a table/columns not named in UPPERCASE, sql generated by SQL Developer is invalid.
Steps to reproduce:
- open SQL Developer, connect to DB
- make a table named "lowerCase" (in double quotes, so it won't be automatically changed to capital letters)
- you may also add some columns, for example "lowerCol1", "UpCol2", ALLUPCOL3
- add some data rows to the table
- choose Tools -> Export DDL and Data
- check exporting of tables and data, on "filter" tabs choose your "lowerCase" table
- press "Apply"
Error:
Generated SQL contains invalid INSERTs: mixed-case table and columns are referenced without obligatory double quotes, which yields an error when generated script is executed (see below, relevant line is underlined)
-- DDL for Table lowerCase
CREATE TABLE "DBO_HT"."lowerCase"
(     "lowerCol1" VARCHAR2(100),
     "UpCol2" VARCHAR2(100),
     "ALLUPCOL3" VARCHAR2(100)
-- DATA FOR TABLE lowerCase
-- FILTER = none used
-- INSERTING into lowerCase
Insert into lowerCase (lowerCol1,UpCol2,ALLUPCOL3) values ('lc','uc','auc');
-- END DATA FOR TABLE lowerCase
Remarks
SQL Developer: version 1.2.1, build MAIN-32.13
Oracle DBs: 9.2 & Express
OS: Windows 2000 Professional
If you need any more details/testing, let me know. I'd really appreciate a quick patch for this issue...
Alternatively, do you know of any other simple way of copying a single database (it's called a schema in Oracle, right?) from one computer to another? Possibly something so simple like detaching->copying->reattaching mdf (data) files in SQL Server... I thought that this "Export DDL&Data" function will do, but as you can see I couldn't use it.
I just need a simple solution that works - one operation on source to stuff, get the resulting files to other computer and one operation to have it running there... I think that such scenario is very basic, yet I just can't achieve it and I am simply not allowed to spend more time on it (read: our test project fails, my company rejects my "lobbying" and stays with MSSQL :/ )
Thanks a lot & bye

Thanks for your reply.
ad. 1)
You're right. I just wanted to give some very short feedback on my experiences with SQL Developer, so I didn't think starting new threads would be necessary, but as I was writing it became much bigger than I initially planned - sorry about that. I will make proper threads as soon as possible. Having "Edit post" button on this forum would also be useful.
ad. 2)
Generally, you're right - in most cases it's true that "switching DBMS is a major commitment" and "you will produce terrible code" if you don't learn the new one.
However, I think that you miss one part of market here - the market that I think Express is also targeted on. I'd call it a "fire&forget databases" market; MySQL comes to mind as possibly most common solution here. It's the rather small systems, possibly web-accessed, whose data-throughput requirements are rather modest; the point is to store data at all, and not necesarily in fastest way, because given the amount of data that is used, even on low-end hardware it will work well enough. What's important here is its general ease of use - how easy is to set up such system, connect and access data, develop a software using it, how much maintenance is needed, how easy this maintenance is, how easy are the most common development tasks as creating a DB, moving a DB from test to production server etc. There, "how easy" directly translates to "how much time we need to set it up", which translates to "how much will the development will cost".
Considering the current technology, switching the DBMS in such systems is not necesarily a major commitment and believe me that you will not produce terrible code. In many cases it's as simple as changing a switch in your ORM toolkit: hibernate.dialect = Hibernate.Dialect.OracleDialect vs MySQLDialect vs MsSql2005Dialect
Therefore, in some part of market it's easy to switch DBMS, even on project-by-project basis. The reason to switch will appear when other DBMS makes life easier => development faster. From that point of view, I can understand my colleagues giving me an embarassing look and saying "come on, I won't read all these docs just to have db copied to test server". And it doesn't mean "they are not willing to learn anything new", it's just that they feel such basic task should have self-explaining solution that doesn't require mastering any special knowledge. And if they get such simple solutions somewhere else, it costs them nothing to change the hibernate dialect.
I think Oracle did the great job with introducing the Express to this "fire&forget" market. The installation is a snap, it just works out of the box, nothing serious to configure, opposite to what I remember from installing and working on Oracle 9 a few years ago. In some places it's still "you need to start SQL*Plus and enter this script", but it's definitely less than before. I also find the SQL Developer a great tool, it can do most of what we need to do with the DB, it's also much better and pleasant to use over Oracle 9 tools. Still, a few basic things still require too much hassle, and I'd say taking your schema to another machine is one of them. So I think that, if you do it well, the "schema copy wizard" you mentioned might be very helpful. If I was to give any general advice for Express line of DB/tools, I'd say "make things simple" - make it "a DB you can't see".
That's, IMHO, the way to attract more Express users.

Open a Dynamic URL from a Table column link

Hi,
Jdev Version (11.1.1.6.0)
I have requirement to open a dynamic URL from table column. Any time I click on link, it should generate dynamic URL based on column attribute and open in popup or browser. Can someone pls suggest how to achieve this.
Thanks
Ank

1)If you have any parameters that needs to be passed to build that dynamicURL, just set a propertyListener on the column attribute and get the value.
2)Then on the af:commandLink action, build your dynamicURL with the required parameters.
3) If you URL is all together a different application which doesn't share your transaction, you can open it as below
In the below code, urlWithParams will be your dynamicURL.
ExtendedRenderKitService erks =
Service.getRenderKitService(facesContext, ExtendedRenderKitService.class);
StringBuilder sbURL = new StringBuilder();
sbURL.append("window.open(\"" + urlWithParams + "\");");
erks.addScript(facesContext, sbURL.toString());
You can also try the above response by user 948181.
Hope it helps.

Can we have more than 1 UI element in a single table column?

Hi All,
For example, I want to have IMAGE, ProgressIndicator and LinkToAction together as a template in a table column.
I already tried without success. I could only add single UI elements. After that, tools won't let me do it.
Any help or suggestion will be appreciated.
Sub

Hi
You can have at one time only one UI element in the table.
if you want to have more than one type of editors in the table then you can use table cell editors as suggested above.
but i guess you are referring here to grouping more than one UI element in one editor or one column.
i think that is not possible as such.
How ever what you can do is, make use of the TABLECOLUMNGROUP.
instead of adding column directly to the table use TABLECOLUMNGROUP and add columns to this.
create three table column for three UI elements you are reffering here and put them in this one TABLECOLUMNGROUP.
and add rest of the column straight to the table.
thanks
sarbjeet

Unable to drop or truncate a plan table

Hi guys,
I was trying to execute 'Explain Plan' on one of my query. However, when I tried to drop the plan table, i was prompted that the table or view does not exists:
QL> EXPLAIN PLAN FOR
2 SELECT * FROM ORDERS WHERE TO_CHAR(O_SHIP_DATE, 'YYYY')='2005' AND O_STATUS='PROCESSING';
Explained.
SQL> SELECT * FROM TABLE(DBMS_XPLAN.DISPLAY);
PLAN_TABLE_OUTPUT
Plan hash value: 1275100350
| Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time |
| 0 | SELECT STATEMENT | | 648 | 46008 | 725 (5)| 00:00:09 |
|* 1 | TABLE ACCESS FULL| ORDERS | 648 | 46008 | 725 (5)| 00:00:09 |
Predicate Information (identified by operation id):
PLAN_TABLE_OUTPUT
1 - filter("O_STATUS"='PROCESSING' AND
TO_CHAR(INTERNAL_FUNCTION("O_SHIP_DATE"),'YYYY')='2005')
14 rows selected.
SQL> TRUNCATE TABLE PLAN_TABLE;
TRUNCATE TABLE PLAN_TABLE
ERROR at line 1:
ORA-00942: table or view does not exist
SQL> select count(*) from plan_table;
COUNT(*)
6
Any idea what went wrong? Thanks in advance.

Ok, I managed to find the scripts to recreate the plan table. Now it works again. Cheers.

Frame 9 solution for table column + side head does not work in Frame 10 and 11

In Frame 9 structured (DITA) we could force Frame to record the actual widths of table columns in the DITA XML. Frame 9 would respect the widths when opening the file. This was particularly useful for forcing tables to be wide -- to go across the column and the side head -- and for the columns to never resize.
In Frame 9 this was done by commenting out the line
"writer use proportional widths;"
like this
"/* writer use proportional widths; */"
in the topic.rules.text" file located in
"...\FrameMaker9\Structure\xml\DITA\app\DITA-Topic-FM"
This no longer works in Frame10 and Frame 11. Even though the same line is commented out in all the "NAME.rules.txt" files in all the subdirectories of
    "...\AdobeFrameMaker11\Structure\xml\DITA_1.2\app"
and
    "...\AdobeFrameMaker11\Structure\xml\DITA\app"
and
    "...\AdobeFrameMaker10\Structure\xml\DITA_1.2\app"
and
    "...\AdobeFrameMaker10\Structure\xml\DITA\app" .
Commenting out the line does force Frame 10 and 11 to record the absolute column width (2.357" etc.) in the DITA XML.
However, on Open, Frame 10 and 11 force the table to fit in the column, not the column and sidehead. That is they behave as though they were still using proportional column widths. It seems the original values (as inserted by Frame 10 and 11 before closing!) are recalculated on Open, thereby mimicking the default proportional width behavior.
For example, this on Save then Close from Frame 10 or 11
<table frame = "topbot" colsep = "0" rowsep = "1">
<tgroup cols = "4" colsep = "0" rowsep = "1" outputclass = "FormatB">
<colspec colnum = "1" colname = "1" colwidth = "1.796in" colsep = "0"/>
<colspec colnum = "2" colname = "2" colwidth = "1.852in" colsep = "0"/>
<colspec colnum = "3" colname = "3" colwidth = "1.179in" colsep = "0"/>
<colspec colnum = "4" colname = "4" colwidth = "2.152in" colsep = "0"/>
goes to this on Open then Save:
<table frame = "topbot" colsep = "0" rowsep = "1">
<tgroup cols = "4" colsep = "0" rowsep = "1" outputclass = "FormatB">
<colspec colnum = "1" colname = "1" colwidth = "1.351in" colsep = "0"/>
<colspec colnum = "2" colname = "2" colwidth = "1.393in" colsep = "0"/>
<colspec colnum = "3" colname = "3" colwidth = "0.887in" colsep = "0"/>
<colspec colnum = "4" colname = "4" colwidth = "1.618in" colsep = "0"/>
Any help at all would be appreciated!
We have 8,000 to 10,000 pages to PDF in the next few days and about 33% of those pages are messed up tables!
Message was edited by: borealforest

Hi...
Unfortunately, I don't have any insight into the default DITA table handling in FM10 or FM11 .. so can't give you the answer you're looking for. Since both FM10 and FM11 offer ExtendScript, you could write a script (or have one written) that processes all of your files to reset the table widths. Or, perhaps the best short term solution may be to reinstall FM9 to get the job done, then spend more time later to figure out a better solution.
One alternative would be for you to use DITA-FMx, which supports the table/@pgwide attribute for controlling which tables span the page and which don't. Since your tables probably don't make use of this attribute, it won't help in the near term, but might make sense going forward.
Cheers,
Scott Prentice
Leximation, Inc.
www.leximation.com

Require sum value of one table to be inserted into another table column

Hi
I have a table which contains a list of parts and their prices required for an assembly.
I am trying to calculate the total from this part lists and put into the total price column for the assembly (another table column).
My method was to calculate the total in a page process ( eg, once all parts in the assembly have been entered the page process calculates the total price (the sum of the part prices at that time) and puts the result (total) in the assembly total column)
In the process I capture the total using either
SELECT SUM(TOTAL_COST) Total INTO B from CC_REQ_BOM WHERE RID = :P5_RID;
or
SELECT SUM(TOTAL_COST) INTO B from CC_REQ_BOM WHERE RID = :P5_RID;
Both the above sql statements are allowed ( one with alias and one without alais) by the page process but they dont seem to be working as no total is returned to the table when the page process is run.
to insert the calculation(variable B) into the required table I have used
INSERT INTO CC_REQ(TOTAL_COST)
VALUES(B);
I have used this method a few times with no problems for standard sql statements but this is the first time I have used it with the sum SQL function. For some reason it doesn't seem to like the SUM function even though the code below works in SQL Command window.
SELECT SUM(TOTAL_COST) from CC_REQ_BOM WHERE RID = :P5_RID;
Any help welcome.
PGJ

Hi
In that case, I would do something like this then...
CREATE TABLE crt_crates
(ccr_id   INTEGER        CONSTRAINT ccr_pk PRIMARY KEY,
ccr_name VARCHAR2(4000) CONSTRAINT ccr_nam_nn NOT NULL);
CREATE TABLE crt_requests
(cre_id        INTEGER        CONSTRAINT cre_pk PRIMARY KEY,
cre_reference VARCHAR2(4000) CONSTRAINT cre_ref_nn NOT NULL,
--I've skipped the requester as this would probably refernce a different table
--I've skipped request details as it's not necessary for this example
cre_ccr_id    INTEGER        CONSTRAINT cre_ccr_fk REFERENCES crt_crates);
CREATE TABLE crt_materials
(cma_id   INTEGER        CONSTRAINT cma_pk PRIMARY KEY,
cma_name VARCHAR2(4000) CONSTRAINT cma_nam_nn NOT NULL,
cma_cost NUMBER(12,2)   CONSTRAINT cma_cos_nn NOT NULL);
CREATE TABLE crt_crate_bom
(ccb_id       INTEGER CONSTRAINT ccb_pk PRIMARY KEY,
ccb_ccr_id   INTEGER CONSTRAINT ccb_ccr_fk REFERENCES crt_crates,
ccb_cma_id   INTEGER CONSTRAINT ccb_cma_fk REFERENCES crt_materials,
ccb_quantity INTEGER DEFAULT 1 CONSTRAINT ccb_qua_nn NOT NULL);
INSERT INTO crt_crates
VALUES(1, 'Crate 1');
INSERT INTO crt_requests
VALUES(1,'Request 1',1);
INSERT INTO crt_materials
VALUES(1,'Material 1', 1000);
INSERT INTO crt_materials
VALUES(2,'Material 2', 500);
INSERT INTO crt_crate_bom
VALUES(1,1,1,5);
INSERT INTO crt_crate_bom
VALUES(2,1,2,3);
COMMIT;
--So crate cost totals would be...
SELECT cre_reference              request,
       ccr_name                   crate,
       SUM(cma_cost*ccb_quantity) crate_cost
FROM   crt_requests,
       crt_crates,
       crt_materials,
       crt_crate_bom
WHERE cre_ccr_id = ccr_id
AND    ccb_ccr_id = ccr_id
AND    ccb_cma_id = cma_id
GROUP BY cre_reference,
         ccr_name;
--And request cost totals would be...
SELECT cre_reference              request,
       SUM(cma_cost*ccb_quantity) crate_cost
FROM   crt_requests,
       crt_crates,
       crt_materials,
       crt_crate_bom
WHERE cre_ccr_id = ccr_id
AND    ccb_ccr_id = ccr_id
AND    ccb_cma_id = cma_id
GROUP BY cre_reference; Do you see what I mean - you don't store the derived values as they could get out of sync with the component parts that make then up. You derive them from the underlying data instead.
Hope this makes sense.
Cheers
Ben

The order of the table columns to Srini Chavali

OK I made a mistake Srini Chavali.
So why dont you try to help me now beyond just warn me about burocratic issues, what you really should had done instead just to block the answers of my former question ?
The question is:
How to influence the order of the table columns in time of transformation logic to relational ?
Nelson Alberti da Rosa

because exist an order among primary key columns that was definied in the logical model and it he can't see that.fixed :
function addPKcolumns(list,table){
     pk = table.getPK();
     if(pk!=null){
          pcols = pk.getColumns();
          for(var i = 0;i<pcols.length;i++){
               col = pcols;
               //in fact don't need this check, because PK columns are processed first
               if(!list.contains(col)){
                    list.add(col);
function addFKcolumns(list,fkeys){
     for(var k=0;k<fkeys.length;k++){
          fcols = fkeys[k].getColumns();
          for(var i = 0;i<fcols.length;i++){
          col = fcols[i];
          if(!list.contains(col)){
               list.add(col);
//adds mandatory or oprional columns to list depending on mand parameter
function addMandatoryOptColumns(list,cols, mand){
     for(var i = 0;i<cols.length;i++){
          col = cols[i];
          if(col.isMandatory() == mand && !list.contains(col)){
               list.add(col);
tables = model.getTableSet().toArray();
list = new java.util.ArrayList();
for (var t = 0; t<tables.length;t++){
     list.clear();
     table = tables[t];
     cols = table.getElements();
     // add PK columns to list
     addPKcolumns(list,table);
     // add FK columns to list
     addFKcolumns(list,table.getFKAssociations());
     //add mandatory columns
     addMandatoryOptColumns(list,cols,true);
     //add optional columns
     addMandatoryOptColumns(list,cols,false);
     //use list to reorder columns
     ord_cols = list.toArray();
     for(var n = 0;n<ord_cols.length;n++){
          table.moveToIndex(ord_cols[n],n);
     //prevent reordering from enginnering, can be changed with UI
     table.setAllowColumnReorder(false);
     table.setDirty(true);

To change the width of a Table Column

Hai Developers..................
I have problem with the Table Column Width.
When am on search state.
The search results are showing in a table.
At that time i want to change the width of the each column with respect to the column content.
Like the jsp table.......
Pls replay with example......
Thanks.

And that is why Swing related questions should be posted in the Swing forum so we don't spend time guessing what you are talking about.
Darn, the [Table Column Adjuster|http://www.camick.com/java/blog.html?name=table-column-adjuster] didn't show up in that Google search.

[JS CS3] Merging table columns

Hi all,
What's the fastest way to merge columns in a table?
I'm using the following loop to merge the 4th and 5th columns in my table:
for( var f = myTable.rows.length-1; f >= 0; f-- ){
myTable.columns[3].cells[f].merge (myTable.columns[4].cells[f])
It works, but I'm working on a large table (120 pages worth) and have many instance where I need to merge columns. Using the loop above, the script takes hours to run. Is there a faster way to merge columns while keeping the rows intact?
Thanks,
Michael

I've just done some time testing with CS4 and found the following:
table = app.documents[0].stories[0].tables[0];
start = new Date();
for (var n = 0; 100 > n; n++) {
cells = table.cells;
for (var j = 0; cells.length > j; j++) {
    cells[j].contents = "James";
end = new Date();
alert(end - start);
takes just about the same time to run as:
table = app.documents[0].stories[0].tables[0];
start = new Date();
rowCount = table.rows.length;
columnCount = table.columns.length;
for (var n = 0; 100 > n; n++) {
for (var c = 0; columnCount > c; c++) {
    for (var r = 0; rowCount > r; r++) {
      table.cells.item(c + ":" + r).contents = "Harry";
end = new Date();
alert(end - start);
While this version takes about half as long again:
table = app.documents[0].stories[0].tables[0];
start = new Date();
rowCount = table.rows.length;
columnCount = table.columns.length;
for (var n = 0; 100 > n; n++) {
for (var c = 0; columnCount > c; c++) {
    for (var r = 0; rowCount > r; r++) {
      table.rows[r].cells[c].contents = "Harry";
end = new Date();
alert(end - start);
None of which is particularly surprising. But when I compared the following two scripts, I was astonished by the result:
table = app.documents[0].stories[0].tables[0];
start = new Date();
rowCount = table.rows.length;
columnCount = table.columns.length;
for (var n = 0; 100 > n; n++) {
table.cells.everyItem().contents = "Harry";
end = new Date();
alert(end - start);
table = app.documents[0].stories[0].tables[0];
start = new Date();
rowCount = table.rows.length;
columnCount = table.columns.length;
for (var n = 0; 100 > n; n++) {
table.cells.itemByRange(0, -1).contents = "George";
end = new Date();
alert(end - start);
The latter, using itemByRange was about a third faster than using everyItem(). 1800 milliseconds to 2700 on a 4 x 10 table.
Dave

Webdynpro for ABAP treeBynesting table column Usage

Hi Experts,
I am trying to use treeByNesting table column in webdynpro for ABAP.
Can anyone please share me the code.
I am not getting how to use the recursive node.
I need to develop a tree structure whose leaf if determined at run time, so thought to use this UI element. But right now I am getting an error like : ASSERTION FAILED.
Please suggest how to use recursive node and how to load the child.
Regards,
Kalyani.

Hello friend,
I think these links will help you much in solving your error.
Please visit these links,
http://wiki.sdn.sap.com/wiki/display/WDABAP/WebDynProABAPApplicationusingTreeand+Frame
http://www.****************/Tutorials/WebDynproABAP/Tree/Page1.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/21/ad884118aa1709e10000000a155106/content.htm
Thanks,
Sri Hari

How to display the sorting arrows in the table column header

Hi
I am doing a sorting for some columns from the click of the table column headers, In Developer studio, we are able to view the up and down arrows, I need that also to be made visible at run time, so that the user knows that there exists sorting based on that particular column. Is there any other way of doing it ? I cant place more than one control on the header or wrap the text to two lines..also. please clarify. thanks

I assume you are using NW 04.
The table column header contains a IWDCaption element which may display an icon and a text. See property IWDCaption.imageSource.
The table tutorial might also be helpful.
Armin

Plan table column Time

Similar Messages

Maybe you are looking for