Unable to generate explain plan

Hi,
Oracle Version :10.2.0.3.0
Operating system : Linux
We are unable to generate explain plan and it is throwing error like this
ORA-02403: plan table does not have correct format
How to modify it please help me
Regards
Poorna

SIDDABATHUNI wrote:
Hi,
Oracle Version :10.2.0.3.0
Operating system : Linux
We are unable to generate explain plan and it is throwing error like this
ORA-02403: plan table does not have correct format
How to modify it please help mePoorna,
since you're already on 10g you can drop any PLAN_TABLEs in user schemas. 10g already has a SYS.PLAN_TABLE$ exposed by a public synonym PLAN_TABLE which is a global temporary table that can be used by anyone.
If you really want to keep private copies of the PLAN_TABLE you need to re-create them according to the layout in $ORACLE_HOME/rdbms/admin/utlxplan.sql on the server side.
Regards,
Randolf
Oracle related stuff blog:
http://oracle-randolf.blogspot.com/
SQLTools++ for Oracle (Open source Oracle GUI for Windows):
http://www.sqltools-plusplus.org:7676/
http://sourceforge.net/projects/sqlt-pp/

Similar Messages

Unable to generate explain plan from toad

HI,
Toad Version:8.6
I was unable to generate the explain plan in the toad.Here i create PLAN_TOAD table also but it is still getting the same error
ORA-00942: table or view does not exist

Hello,
You created the Table PLAN_TABLE but you must check the configuration of TOAD.
It seems to me that by default TOAD use the Table TOAD_PLAN_TABLE.
So, you must set the right name of the Table (or rename the Table PLAN_TABLE).
Best regards,
Jean-Valentin Lubiez

Generating EXPLAIN PLAN on a database which is opened in READ-ONLY mode

Hi,
I am using Oracle 10.2.0.3 version.
If my database is opened in READ-ONLY mode, means no insert/update/delete operations are permitted here.
While generating EXPLAIN PLAN for any SQL, it does entries in PLAN_TABLE. But my database is opened in READ-ONLY mode, means no inserts can happen.
So how can I generate EXPLAIN PLAN for my SQL in this condition?
Thanks in advance.
Best Regards,
oratest

oratest wrote:
I am using Oracle 10.2.0.3 version.
If my database is opened in READ-ONLY mode, means no insert/update/delete operations are permitted here.
While generating EXPLAIN PLAN for any SQL, it does entries in PLAN_TABLE. But my database is opened in READ-ONLY mode, means no inserts can happen.
So how can I generate EXPLAIN PLAN for my SQL in this condition?
You can always do: "explain plan into some_table@remote_database" to avoid inserting into the local database. Unfortunately 10g added a sequence fetch to the "explain plan" code, and this is where the call would fail if you tried this remote approach on your version.
Here's an idea I haven't tested. If you set up a database link from your production database to the read-only database, you could then do an "explain plan" in the production database for the SQL statement by changing every object reference in the SQL statement to "object@readonlydatabase". In most cases this will allow the optimizer to recognise the statement as "fully remote" and get the optimizer on the readonly database to create the execution plan - which would then be written to the production database.
Regards
Jonathan Lewis

Unable to Execute Explain Plan for the selected SQL

When working with several SQL statements in one SQL Worksheet you execute the specific statement by selecting it and pressing F9.
The same is not possible for the explain plan though.
If you select the first SQL statement and press F6, the explain plan is executed correctly. If you try the same for any other statement, all you get is 'No SQL statement entered.' on the status bar.
Maciej

It is available.
Type this in.
create table xx (yy number(10));
create table zz (aa number(10));
select * from xx;
select * from zz;Run all these statements by pressing f5.
Place the cursor on 'select * from xx;'.
Press f6 gives you a plan.
Place the cursor on 'select * from zz;'
press f6 gives you a different plan.
The problem seems to be that F6 is still suffering from a statement selection bug which is already fixed for f9. That is selecting a whole statement results in failure to recognise a statement and the 'No statement entered' message.

Explain plan generating it self taking very long time !!! What to do ?

Hi,
I am trying to generate explain plan for a query which is running more than 2 hours. I am trying to generate explain plan for query by "explin plan for select ..." but it self is taking very long time.
Kindly suggest me how to reduce time for explain plan ? Secondly why explain plan itself taking very long time ?
thanks & regards
PKP

Just guessing here, but I've experienced this behaviour when I did two explain's within a second. This is because a plan is identified by a statement_id or, if you don't provide a statement_id, by the timestamp (of DATE datatype). So if you execute two explain plans within the second (using a script), it has two sets of data with the same primary key. The hierarchical query that needs to be executed to provide you the nicely indented text, will exponentially expand in this case.
Maybe time to clean up your plan_table ?
Hope this helps.
Regards,
Rob.

Explain plan for Procedures

Hi,
I know we can generate explain plan for queries using "Explain plan" statement or "Autotrace option". I would like to know how can we generate explain plan for oracle procedures.
Thanks in Advance..

Check this link very helpful info from Rob
When your query takes too long ...
There are no explain plan for procedures.
MAy be you want to do DBMS_PROFILER for procedures execution

Efficient way to read through big explain plan and genterate html explain plan for sql id's executed in past

Hi,
I have a sql which is recently having a performance problems in Production. I have generated a explain plan for it trying to find out what it is doing but plan itself is close to 1000 lines. I want to check if there is any efficient way to go through big plan like this one and quickly find the damaging areas..
2) I also wanted to know if there is way to generate explain plans in HTML format which executed in past and have entry in dba_hist_sqltext.
3) I also have two sql_monitor reports which I want to compare. is there any efficient way to do it as well?
Please share your thoughts!
Thanks in advance!
Regards,
Suman-

Hi,
I suggest you can try running sql advisor on the query maybe something fruitful comes up
http://www.oracle-base.com/articles/11g/sql-access-advisor-11gr1.php
I am not sure about the explain plan being printed in html format but
You may also want to try the sqlhistory.sql query from below page
http://evdbt.com/scripts/
I have used it many times to check on executions and explain plans which may have changed over the period
I have faced it many times , the query picks up a bad explain plan and performs poorly

Explain plan for running query

Hi everyone,
I come to know how to generate explain plan for a given query by giving
Explain plan for select * fro emp;
Consider a query running for 5 hrs in a session and i want to genrate explain plan for that current query in its 4th hour i dont know the sql as well
all the steps by step would be much apppreciated
like finding Current SQL then so on
Thanks
Shareef

912856 wrote:
Hi everyone,
I come to know how to generate explain plan for a given query by giving
Explain plan for select * fro emp;
Consider a query running for 5 hrs in a session and i want to genrate explain plan for that current query in its 4th hour i dont know the sql as well
all the steps by step would be much apppreciated
like finding Current SQL then so on
Thanks
ShareefYOu can also use dbms_xplain to generate plan used in v$sql. like for example
SQL>SELECT SQL_ID, CHILD_NUMBER FROM V$SQL WHERE SQL_TEXT LIKE 'select * from em%';
SQL_ID CHILD_NUMBER
6kd5fkqdjb8fu 0
SQL>SELECT * FROM TABLE(DBMS_XPLAN.DISPLAY_CURSOR('6kd5fkqdjb8fu',0,'ALLSTATS'));If you need the actual tuntime statistics used by sql statement then you need to put hint /*+ gather_plan_statistics */ in sql ststement, something like
select /*+ gather_plan_statistics */ * from emp;
and then generate the explain plan for this
Have a look
http://hoopercharles.wordpress.com/2010/03/01/dbms_xplan-format-parameters/
select * from table(dbms_xplan.display_cursor(null,null,'ALLSTATS LAST'));

Differenet Explain Plan for Same Query

DB Version : 11.2.0.3
OS Version : AIX 6
I have two Queries ( The Difference between Them Only 940 and 584 ) When I Generate Explain Plan Different Output Why ? Why CPU time is Different Each Time
First Query Statement :
INSERT INTO TempSearchResult (t_aid,
                              t_umidl,
                              t_umidh,
                              X_CREA_DATE_TIME_MESG)
   SELECT z.aid,
          z.mesg_s_umidl,
          z.mesg_s_umidh,
          z.mesg_crea_date_time
     FROM ( SELECT m.aid,
                    m.mesg_s_umidl,
                    m.mesg_s_umidh,
                    m.mesg_crea_date_time
               FROM RSMESG_ESIDE m
              WHERE 1 = 1
                    AND m.mesg_crea_date_time BETWEEN TO_DATE (
                                                         '20120131 10:00:00',
                                                         'YYYYMMDD HH24:MI:SS')
                                                  AND TO_DATE (
                                                         '20120131 13:00:00',
                                                         'YYYYMMDD HH24:MI:SS')
                    AND m.mesg_frmt_name = 'Swift'
                    AND m.mesg_sender_x1 = 'SOGEFRPPXXX'
                    AND m.mesg_nature = 'FINANCIAL_MSG'
                    AND m.mesg_type LIKE '950'
           ORDER BY mesg_crea_date_time) z
    WHERE ROWNUM <= 5000
Explain Plan for First Query :
PLAN_TABLE_OUTPUT
Plan hash value: 3901722890
| Id | Operation                                 | Name              | Rows | Bytes | Cost (%CPU)| Time     | Pstart| Pstop |
|   0 | INSERT STATEMENT                          |                   | 2866 |   134K|   197   (3)| 00:00:03 |       |       |
|   1 | LOAD TABLE CONVENTIONAL                  | TEMPSEARCHRESULT |       |       |            |          |       |       |
|* 2 |   COUNT STOPKEY                           |                   |       |       |            |          |       |       |
|   3 |    VIEW                                   |                   | 2866 |   134K|   197   (3)| 00:00:03 |       |       |
|* 4 |     SORT ORDER BY STOPKEY                 |                   | 2866 |   333K|   197   (3)| 00:00:03 |       |       |
|   5 |      NESTED LOOPS                         |                   | 2866 |   333K|   196   (2)| 00:00:03 |       |       |
PLAN_TABLE_OUTPUT
|   6 |       NESTED LOOPS                        |                   | 1419 |   148K|   196   (2)| 00:00:03 |       |       |
|* 7 |        HASH JOIN                          |                   | 1419 |   141K|   196   (2)| 00:00:03 |       |       |
|   8 |         NESTED LOOPS                      |                   |    91 | 1911 |     2   (0)| 00:00:01 |       |       |
|   9 |          TABLE ACCESS BY INDEX ROWID      | SUSER             |     1 |    10 |     1   (0)| 00:00:01 |       |       |
|* 10 |           INDEX UNIQUE SCAN               | IX_SUSER          |     1 |       |     0   (0)| 00:00:01 |       |       |
|* 11 |          INDEX FULL SCAN                  | PK_SUNITUSERGROUP |    91 | 1001 |     1   (0)| 00:00:01 |       |       |
| 12 |         PARTITION RANGE SINGLE            |                   | 1450 |   114K|   193   (2)| 00:00:03 |     2 |     2 |
|* 13 |          TABLE ACCESS BY LOCAL INDEX ROWID| RMESG             | 1450 |   114K|   193   (2)| 00:00:03 |     2 |     2 |
|* 14 |           INDEX SKIP SCAN                 | IX_RMESG          |   415 |       |    14 (15)| 00:00:01 |     2 |     2 |
|* 15 |        INDEX UNIQUE SCAN                  | PK_SMSGUSERGROUP |     1 |     5 |     0   (0)| 00:00:01 |       |       |
|* 16 |       INDEX UNIQUE SCAN                   | PK_SBICUSERGROUP |     2 |    24 |     0   (0)| 00:00:01 |       |       |
PLAN_TABLE_OUTPUT
PLAN_TABLE_OUTPUT
Predicate Information (identified by operation id):
   2 - filter(ROWNUM<=5000)
   4 - filter(ROWNUM<=5000)
   7 - access("X_INST0_UNIT_NAME"="UNIT")
10 - access("SUSER"."USERNAME"="SIDE"."GETMYUSER"())
11 - access("SUSER"."GROUPID"="SUNITUSERGROUP"."GROUPID")
       filter("SUSER"."GROUPID"="SUNITUSERGROUP"."GROUPID")
PLAN_TABLE_OUTPUT
13 - filter("RMESG"."MESG_SENDER_X1"='SOGEFRPPXXX' AND "RMESG"."MESG_NATURE"='FINANCIAL_MSG' AND
              "RMESG"."MESG_FRMT_NAME"='Swift')
14 - access("RMESG"."MESG_CREA_DATE_TIME">=TO_DATE(' 2012-01-31 10:00:00', 'syyyy-mm-dd hh24:mi:ss') AND
              "RMESG"."MESG_TYPE"='950' AND "RMESG"."MESG_CREA_DATE_TIME"<=TO_DATE(' 2012-01-31 13:00:00', 'syyyy-mm-dd hh24:mi:ss'))
       filter("RMESG"."MESG_TYPE"='950')
15 - access("X_CATEGORY"="CATEGORY" AND "SUSER"."GROUPID"="SMSGUSERGROUP"."GROUPID")
16 - access("X_OWN_LT"="BICCODE" AND "SUSER"."GROUPID"="SBICUSERGROUP"."GROUPID")
40 rows selected.
Second query
INSERT INTO TempSearchResult (t_aid,
                              t_umidl,
                              t_umidh,
                              X_CREA_DATE_TIME_MESG)
   SELECT z.aid,
          z.mesg_s_umidl,
          z.mesg_s_umidh,
          z.mesg_crea_date_time
     FROM ( SELECT m.aid,
                    m.mesg_s_umidl,
                    m.mesg_s_umidh,
                    m.mesg_crea_date_time
               FROM RSMESG_ESIDE m
              WHERE 1 = 1
                    AND m.mesg_crea_date_time BETWEEN TO_DATE (
                                                         '20120117 10:00:00',
                                                         'YYYYMMDD HH24:MI:SS')
                                                  AND TO_DATE (
                                                         '20120117 13:00:00',
                                                         'YYYYMMDD HH24:MI:SS')
                    AND m.mesg_frmt_name = 'Swift'
                    AND m.mesg_sender_x1 = 'SOGEFRPPGSS'
                    AND m.mesg_nature = 'FINANCIAL_MSG'
                    AND m.mesg_type LIKE '548'
           ORDER BY mesg_crea_date_time) z
    WHERE ROWNUM <= 5000
Explain Plan For Second Query :
PLAN_TABLE_OUTPUT
Plan hash value: 4106071428
| Id | Operation                                  | Name              | Rows | Bytes |TempSpc| Cost (%CPU)| Time     | Pstart| Pstop |
|   0 | INSERT STATEMENT                           |                   | 1073 | 51504 |       | 2622   (1)| 00:00:32 |       |       |
|   1 | LOAD TABLE CONVENTIONAL                   | TEMPSEARCHRESULT |       |       |       |            |          |       |       |
|* 2 |   COUNT STOPKEY                            |                   |       |       |       |            |          |       |       |
|   3 |    VIEW                                    |                   | 1073 | 51504 |       | 2622   (1)| 00:00:32 |       |       |
|* 4 |     SORT ORDER BY STOPKEY                  |                   | 1073 |   124K|       | 2622   (1)| 00:00:32 |       |       |
|   5 |      NESTED LOOPS                          |                   | 1073 |   124K|       | 2621   (1)| 00:00:32 |       |       |
PLAN_TABLE_OUTPUT
|   6 |       NESTED LOOPS                         |                   |   531 | 56817 |       | 2621   (1)| 00:00:32 |       |       |
|   7 |        NESTED LOOPS                        |                   |   531 | 54162 |       | 2621   (1)| 00:00:32 |       |       |
|   8 |         NESTED LOOPS                       |                   |   543 | 49413 |       | 2621   (1)| 00:00:32 |       |       |
|   9 |          TABLE ACCESS BY INDEX ROWID       | SUSER             |     1 |    10 |       |     1   (0)| 00:00:01 |       |       |
|* 10 |           INDEX UNIQUE SCAN                | IX_SUSER          |     1 |       |       |     0   (0)| 00:00:01 |       |       |
| 11 |          PARTITION RANGE SINGLE            |                   |   543 | 43983 |       | 2621   (1)| 00:00:32 |     2 |     2 |
|* 12 |           TABLE ACCESS BY LOCAL INDEX ROWID| RMESG             |   543 | 43983 |       | 2621   (1)| 00:00:32 |     2 |     2 |
| 13 |            BITMAP CONVERSION TO ROWIDS     |                   |       |       |       |            |          |       |       |
| 14 |             BITMAP AND                     |                   |       |       |       |            |          |       |       |
| 15 |              BITMAP CONVERSION FROM ROWIDS |                   |       |       |       |            |          |       |       |
|* 16 |               INDEX RANGE SCAN             | IX_SENDER         | 25070 |       |       |   894   (1)| 00:00:11 |     2 |     2 |
PLAN_TABLE_OUTPUT
| 17 |              BITMAP CONVERSION FROM ROWIDS |                   |       |       |       |            |          |       |       |
| 18 |               SORT ORDER BY                |                   |       |       |   408K|            |          |       |       |
|* 19 |                INDEX RANGE SCAN            | IX_RMESG          | 25070 |       |       | 1405   (1)| 00:00:17 |     2 |     2 |
|* 20 |         INDEX UNIQUE SCAN                  | PK_SUNITUSERGROUP |     1 |    11 |       |     0   (0)| 00:00:01 |       |       |
|* 21 |        INDEX UNIQUE SCAN                   | PK_SMSGUSERGROUP |     1 |     5 |       |     0   (0)| 00:00:01 |       |       |
|* 22 |       INDEX UNIQUE SCAN                    | PK_SBICUSERGROUP |     2 |    24 |       |     0   (0)| 00:00:01 |       |       |
Predicate Information (identified by operation id):
PLAN_TABLE_OUTPUT
   2 - filter(ROWNUM<=5000)
   4 - filter(ROWNUM<=5000)
10 - access("SUSER"."USERNAME"="SIDE"."GETMYUSER"())
12 - filter("RMESG"."MESG_NATURE"='FINANCIAL_MSG' AND "RMESG"."MESG_FRMT_NAME"='Swift')
16 - access("RMESG"."MESG_SENDER_X1"='SOGEFRPPGSS')
19 - access("RMESG"."MESG_CREA_DATE_TIME">=TO_DATE(' 2012-01-17 10:00:00', 'syyyy-mm-dd hh24:mi:ss') AND
              "RMESG"."MESG_TYPE"='548' AND "RMESG"."MESG_CREA_DATE_TIME"<=TO_DATE(' 2012-01-17 13:00:00', 'syyyy-mm-dd hh24:mi:ss'))
       filter("RMESG"."MESG_TYPE"='548' AND "RMESG"."MESG_CREA_DATE_TIME"<=TO_DATE(' 2012-01-17 13:00:00', 'syyyy-mm-dd
              hh24:mi:ss') AND "RMESG"."MESG_CREA_DATE_TIME">=TO_DATE(' 2012-01-17 10:00:00', 'syyyy-mm-dd hh24:mi:ss'))
20 - access("X_INST0_UNIT_NAME"="UNIT" AND "SUSER"."GROUPID"="SUNITUSERGROUP"."GROUPID")
21 - access("X_CATEGORY"="CATEGORY" AND "SUSER"."GROUPID"="SMSGUSERGROUP"."GROUPID")
PLAN_TABLE_OUTPUT
22 - access("X_OWN_LT"="BICCODE" AND "SUSER"."GROUPID"="SBICUSERGROUP"."GROUPID")
45 rows selected.
Table Structure TEMPSEARCHRESULT
CREATE GLOBAL TEMPORARY TABLE TEMPSEARCHRESULT
T_AID                  NUMBER(3),
T_UMIDL                NUMBER(10),
T_UMIDH                NUMBER(10),
X_CREA_DATE_TIME_MESG DATE
ON COMMIT PRESERVE ROWS
NOCACHE;
CREATE INDEX SIDE.TEMP_SEARCH_INDEX ON SIDE.TEMPSEARCHRESULT
(T_AID, T_UMIDL, T_UMIDH, X_CREA_DATE_TIME_MESG);

Again Thank you For your amazing Answer.
For indexes it's a balance. Check this query which is Simple
Select * from RMESGI generated Explain Plan for it to see effect of indexes .
PLAN_TABLE_OUTPUT
Plan hash value: 1686435785
| Id | Operation           | Name | Rows | Bytes | Cost (%CPU)| Time     | Pstart| Pstop |
|   0 | SELECT STATEMENT    |       |    11M| 8920M|   376K (1)| 01:15:20 |      |        |
|   1 | PARTITION RANGE ALL|       |    11M| 8920M|   376K (1)| 01:15:20 |    1 |     12 |
|   2 |   TABLE ACCESS FULL | RMESG |    11M| 8920M|   376K (1)| 01:15:20 |    1 |     12 |
---------------------------------------------------------------------------------------------1:15:20 For table access and Full Scan Also , I generate new Indexes on the table like the following
CREATE TABLE RMESG(
        aid NUMBER(3) NOT NULL,
        mesg_s_umidl NUMBER(10) NOT NULL,
        mesg_s_umidh NUMBER(10) NOT NULL,
        mesg_validation_requested CHAR(18) NOT NULL,
        mesg_validation_passed CHAR(18) NOT NULL,
        mesg_class CHAR(16) NOT NULL,
        mesg_is_text_readonly NUMBER(1) NOT NULL,
        mesg_is_delete_inhibited NUMBER(1) NOT NULL,
        mesg_is_text_modified NUMBER(1) NOT NULL,
        mesg_is_partial NUMBER(1) NOT NULL,
        mesg_crea_mpfn_name CHAR(24) NOT NULL,
        mesg_crea_rp_name CHAR(24) NOT NULL,
        mesg_crea_oper_nickname CHAR(151) NOT NULL,
        mesg_crea_date_time DATE NOT NULL,
        mesg_mod_oper_nickname CHAR(151) NOT NULL,
        mesg_mod_date_time DATE NOT NULL,
        mesg_frmt_name VARCHAR2(17) NOT NULL,
        mesg_nature CHAR(14) NOT NULL,
        mesg_sender_x1 CHAR(11) NOT NULL,
        mesg_sender_corr_type VARCHAR2(24) NOT NULL,
        mesg_uumid VARCHAR2(50) NOT NULL,
        mesg_uumid_suffix NUMBER(10) NOT NULL,
        x_own_lt CHAR(8) NOT NULL,
        x_inst0_unit_name VARCHAR2(32) default 'NONE' NOT NULL,
        x_category CHAR(1) NOT NULL,
        archived NUMBER(1) NOT NULL,
        restored NUMBER(1) NOT NULL,
        mesg_related_s_umid CHAR(16) NULL,
        mesg_status CHAR(12) NULL,
        mesg_crea_appl_serv_name CHAR(24) NULL,
        mesg_verf_oper_nickname CHAR(151) NULL,
        mesg_data_last NUMBER(10) NULL,
        mesg_token NUMBER(10) NULL,
        mesg_batch_reference VARCHAR2(46) NULL,
        mesg_cas_sender_reference VARCHAR2(40) NULL,
        mesg_cas_target_rp_name VARCHAR2(20) NULL,
        mesg_ccy_amount VARCHAR2(501) NULL,
        mesg_copy_service_id VARCHAR2(4) NULL,
        mesg_data_keyword1 VARCHAR2(80) NULL,
        mesg_data_keyword2 VARCHAR2(80) NULL,
        mesg_data_keyword3 VARCHAR2(80) NULL,
        mesg_delv_overdue_warn_req NUMBER(1) NULL,
        mesg_fin_ccy_amount VARCHAR2(24) NULL,
        mesg_fin_value_date CHAR(6) NULL,
        mesg_is_live NUMBER(1) NULL,
        mesg_is_retrieved NUMBER(1) NULL,
        mesg_mesg_user_group VARCHAR2(24) NULL,
        mesg_network_appl_ind CHAR(3) NULL,
        mesg_network_delv_notif_req NUMBER(1) NULL,
        mesg_network_obso_period NUMBER(10) NULL,
        mesg_network_priority CHAR(12) NULL,
        mesg_possible_dup_creation VARCHAR2(8) NULL,
        mesg_receiver_alia_name VARCHAR2(32) NULL,
        mesg_receiver_swift_address CHAR(12) NULL,
        mesg_recovery_accept_info VARCHAR2(80) NULL,
        mesg_rel_trn_ref VARCHAR2(80) NULL,
        mesg_release_info VARCHAR2(32) NULL,
        mesg_security_iapp_name VARCHAR2(80) NULL,
        mesg_security_required NUMBER(1) NULL,
        mesg_sender_x2 VARCHAR2(21) NULL,
        mesg_sender_x3 VARCHAR2(21) NULL,
        mesg_sender_x4 VARCHAR2(21) NULL,
        mesg_sender_branch_info VARCHAR2(71) NULL,
        mesg_sender_city_name VARCHAR2(36) NULL,
        mesg_sender_ctry_code VARCHAR2(3) NULL,
        mesg_sender_ctry_name VARCHAR2(71) NULL,
        mesg_sender_institution_name VARCHAR2(106) NULL,
        mesg_sender_location VARCHAR2(106) NULL,
        mesg_sender_swift_address CHAR(12) NULL,
        mesg_sub_format VARCHAR2(6) NULL,
        mesg_syntax_table_ver VARCHAR2(8) NULL,
        mesg_template_name VARCHAR2(32) NULL,
        mesg_trn_ref VARCHAR2(16) NULL,
        mesg_type CHAR(3) NULL,
        mesg_user_issued_as_pde NUMBER(1) NULL,
        mesg_user_priority_code CHAR(4) NULL,
        mesg_user_reference_text VARCHAR2(30) NULL,
        mesg_zz41_is_possible_dup NUMBER(1) NULL,
        x_fin_ccy CHAR(3) NULL,
        x_fin_amount NUMBER(21,4) NULL,
        x_fin_value_date DATE NULL,
        x_fin_ocmt_ccy CHAR(3) NULL,
        x_fin_ocmt_amount NUMBER(21,4) NULL,
        x_receiver_x1 CHAR(11) NULL,
        x_receiver_x2 VARCHAR2(21) NULL,
        x_receiver_x3 VARCHAR2(21) NULL,
        x_receiver_x4 VARCHAR2(21) NULL,
        last_update DATE NULL,
        set_id NUMBER(10) NULL,
        mesg_requestor_dn VARCHAR2(101) NULL,
        mesg_service VARCHAR2(31) NULL,
        mesg_request_type VARCHAR2(31) NULL,
        mesg_identifier VARCHAR2(31) NULL,
        mesg_xml_query_ref1 VARCHAR2(101) NULL,
        mesg_xml_query_ref2 VARCHAR2(101) NULL,
        mesg_xml_query_ref3 VARCHAR2(101) NULL,
        mesg_appl_sender_reference VARCHAR2(51) NULL,
        mesg_payload_type VARCHAR2(31) NULL,
        mesg_sign_digest_reference VARCHAR2(41) NULL,
        mesg_sign_digest_value VARCHAR2(51) NULL,
        mesg_use_pki_signature NUMBER(1) NULL
PARTITION BY RANGE(MESG_CREA_DATE_TIME) (
    PARTITION SIDE_MIN VALUES LESS THAN (TO_DATE(20000101, 'YYYYMMDD')) TABLESPACE TBS_SIDEDB_DA_01);
CREATE UNIQUE INDEX SIDE.IX_PK_RMESG on SIDE.RMESG (AID, MESG_S_UMIDH, MESG_S_UMIDL, MESG_CREA_DATE_TIME) LOCAL;
ALTER TABLE SIDE.RMESG ADD CONSTRAINT IX_PK_RMESG PRIMARY KEY (AID, MESG_S_UMIDH, MESG_S_UMIDL, MESG_CREA_DATE_TIME) USING INDEX SIDE.IX_PK_RMESG;
CREATE INDEX SIDE.ix_rmesg_cassender ON SIDE.rmesg (MESG_CAS_SENDER_REFERENCE) LOCAL;
CREATE INDEX SIDE.ix_rmesg_creationdate ON SIDE.rmesg (MESG_CREA_DATE_TIME) LOCAL;
CREATE INDEX SIDE.ix_rmesg_trnref ON SIDE.rmesg (MESG_TRN_REF) LOCAL;
CREATE INDEX SIDE.ix_rmesg_uumid ON SIDE.rmesg (MESG_UUMID, MESG_UUMID_SUFFIX) LOCAL;
CREATE INDEX SIDE.IX_UNIT_NAME_RMESG on RMESG(mesg_crea_date_time,X_INST0_UNIT_NAME) LOCAL;
CREATE INDEX SIDE.IX_RMESG on RMESG(mesg_crea_date_time ,mesg_type,x_fin_ccy) LOCAL;
CREATE INDEX SIDE.IX_NAME_FORMAT_TYPE_RMESG on RMESG(mesg_frmt_name,mesg_sub_format,mesg_type,mesg_crea_date_time ) LOCAL;same Explain Plan Same Result .
I always remember TOM Quote "full scans are not evil, indexes are not good"
Which Mean Something Wrong Goes with Indexes , the partition depend on MESG_CREA_DATE_TIME Column I create Index for this column but same explain plan Appear every time. With Same Time.
Thank you
Osama

Printing of Explain Plan Results

Is there any way to print an explain plan in SQL Devveloper when the length of the plan result requires scrolling to view the entire plan. I've tried expanding the plan result window as much as possible. The print result contains only what can be viewed.

I haven't tried DBMS_XPLAN but I'll look it up.
I can generate explain plans in a manner that's acceptable to read by simply using SQL*Plus.
This thread was about evaluating the features and problems with SQL*Developer. What I'm saying with this posting is that there is a problem with printing the explain plans that are generated in SQL*Developer when the plan result extend past the viewed window.
Is there a way to send this problem with the Oracle devlopers the way we do with SRs in Metalink? I didn't know if it was appropriate to send this through Metalink. I thought Oracle was monitoring this Forum for issues that were discovered with SQL*Developer.

What is the base of Explain Plan?

On what basis oracle generates explain plan? I mean, is it based on table structure which we are using in SQL query OR it is based on rows exists in table, Or something else.

user2081225 wrote:
On what basis oracle generates explain plan? I mean, is it based on table structure which we are using in SQL query OR it is based on rows exists in table, Or something else.SQL data is stored in specific data structures. Some SQL data will be indexed. These indexes are also stored in specific data structures.
To retrieve data from these structures, you need a program (a series of executable commands that can find and retrieve the required data).
A SQL query is human readable source code that means nothing to Oracle ito how to find the required rows. It needs to take that source code and compile it into binary machine-like code. In other words, it needs to create an executable program (called a cursor) that can be run to find the required rows.
The execution plan is a human readable format of this program - it shows how the cursor will be executed.
How does it construct the program?
It has a set of modules that can do different things (ito data access). E.g. scan an entire table using a full table scan. Scan a unique index to find the address (rowid) of a row. Scan a non-unique indexes using a range scan and return a range of row addresses. Etc.
It also has algorithms on how to combine these data retrieval methods. For example, hash joining the output of such operations. Merge joining the output of index scans. Using a nested loop, where the inner loop is executed for the data found by the outer loop. Etc.
So the CBO dynamically builds a program (cursor) that consists of methods to get to the data required, and processing algorithms to glue these methods together into a logical process flow.
It does this based on data (stats) it has about the tables and indexes (data volumes, distribution, etc), about the type of data structures used for the relevant tables and indexes (hash tables, iot's, b-trees, bitmaps, partitions, clusters..), and so on.
The CBO is a pretty clever piece of software that dynamically writes data retrieval programs called cursors. And unfortunately this complexity is often underestimated and misunderstood.

How to proceed further once the explain plan and trace files are generated?

Hi Friends,
I need to improve the performance of on of the views that i am working on.
As suggested in the thread - http://forums.oracle.com/forums/thread.jspa?threadID=863295&tstart=0 , i gave generated the explain plan and the trace file.
From the explain plan, we can see the expensive operations for the query.
Can any one please tell, how to proceed further from here on i.e. how to make this expensive operations less expensive?
For ex: FULL TABLE SCAN might be an expensive operation when the table has indexes.In such cases, how can we avoid such operations to make query faster?
Regards,
Sreekanth Munagala.

Hi Veena,
An earlier post by you regarding P45 is as below
Starter report P45(3) / P46 efiling for UK
from my understanding though i have not worked on GB Payroll you have said that you deleted IT 65 details of leaver,however there must be clusters generated in system from where the earlier data needs to be deleted and may be that is why you are facing the issue.
In Indian payroll when we execute text file for efiling of tax after challan mapping all the data compiles and sits in PCL cluster and therefore we are unable to generate form 16 with proper output,here we delete the clusters and rerun again the mappings and then check form 16.
Hope this might help you,Experts have suggested you earlier also,they may correct me for this.
Salil

SQLDeveloper can't generate an explain-plan when using "cube"

If I want to create an explain-plan from the following statement, I get no explain-plan:
SELECT 1
FROM dual
GROUP BY CUBE( 2, 2, 2, 2, 2, 2, 2, 2, 2 )If I now want to create an explain-plan again, I get the following message (and still no explain-plan):
http://i.imgur.com/mGO6Z.jpg
I tried this a few times and of course with a fresh db-session where i didn't run any statements before.
I get this with:
SQLDeveloper Version 3.0.04 Build MAIN-04.34 (i.e. production)
DB 9.2.0.1.0
Oracle Instant Client 11.1.0.6.0
In Toad this works btw.
(Of course it makes no sense to run it on this statement, we encountered this problem with a really big SQL-statement where "cube" was used in an inline-view. SQLDeveloper then wasn't able to generate an explain-plan for the whole-statement)
Regards
Markus

that is correct. I wanted to keep the login page redirect inside my class method so that I could do the check every time someone came to pages that require authentication. I wanted it in the LoadState method so I can do a check there, redirect
them to login page or just get a cookie and then pass that cookie to page to build the UI for the page
I can do what you are suggesting and have actually tried it but then I have to track which page to take the user to after they log in...
I have multiple clicks in the appbar and pages from where the user can come to these authentication-bound pages..
Suggestions?
Also, what am I doing wrong in my class method that it doesn't navigate to the login page in the LoadState method?
Thanks
mujno

Unable to generate PO Requisition in Reorder point planning

Hi All,
I am running the REORDER POINT PLANNING REPORT, but after the completion of the report i am getting the error message Unable to generate PO requisition -- Check purchasing, order, and transaction flags on the item.
So kindly help me to get this issue resolved.
Thanks,
Simbu

Have you checked the org item setup for the particular item? Is Purchased and Purchasable checked on the Purchasing tab? Is there a list price? On the inventory tab is the item stockable /transactable?

Min Max Planning Error-Unable to generate requisition

when we run min max planning in test instance for certain items we get the the below error:
“Unable to generate requisition”
Checked the source type for the items which had this error.There is no Source type set for those items even then we get this error.Any help.
Thanks

Check
Min/Max Planning Message: "Unable to Generate Requisition" [ID 113224.1]
Getting Message "Unable to generate requisition" in the Output of the Min-Max Planning Report (INVISMMX) [ID 1265297.1]
Hope this helps,
Sandeep Gandhi

Unable to generate explain plan

Similar Messages

Maybe you are looking for