9i to 10g Migration, RBO to CBO conversion

Hi All,
We used to have 9.2.0.4.0 DB and our applications are tuned to RBO using 'rule' hints.
Recently we migrated to 10gR2 (setting optimizer_hint = 'FIRST_ROWS_1') and we expected that the applications that are using 'rule' hint will be ignored or atleast code will throw errors. But when we looked at the trace file, it looks like it is using RBO.
When Oracle say that RBO is not supported in 10g, does that mean we can still use RBO at our own risk ? Are there any other parameters that need to be set so that CBO is used though RULE hints are used ? (I don't think so..but just to confirm)
Please let me know if someone has any pointers on this,
Thanks,
madhu.

The RBO is no longer supported by Oracle in 10g. The rule hint and optimizer mode are still present in 10g. You are free to use the Rule hint and optimizer mode in 10g, with no support from Oracle.

Similar Messages

  • RBO to CBO conversions

    Hi,
    I need some help.
    My databases are running in RBO environment using oracle 8i, 9i. Now, because RBO being obsolete in oracle 10g and later releases. I want to switch to CBO.
    My databases are in production. I want to look at all the scenarios for conversion to CBO (oracle 10g).
    Could you please suggest, What will be the best approach for that, how should I start.
    I want to know, what conversions are required for changing to CBO. How should i check the performance after conversion e.g. should i check the performance of all operations in both RBO and CBO environment or something else.
    Almost all my queries are using hints, do I have to make some changes on queries also, if yes, then this might be the major task for me. Is there any other way out ?
    If, any other information is required, please let me know.
    Please help in determining the best strategy.
    Regards
    Ashish Goel

    Well, if the RBO is truly desupported in 10G I would expect the RULE hints to just be ignored.
    Keep in mind that you will need to generate stats to assist the CBO so that might be step one (getting a stats gathering job in place).
    As per Strategy, do you know what your most frequent and imporatnt queries are? If so, benchmark them and comapre in 10G with CBO.

  • DISTINCT in the query -- RBO vs CBO

    Hi all,
    We are in a process of migrating our applications from RBO to CBO as we moved to 10g and recently I observed a simple query with DISTINCT clause showing different results in CBO. Here is my order of creating a table in 10g environment,
    create table m_test(col1 varchar2(3));
    insert into m_test values('ZYT');
    insert into m_test values('ABC');
    insert into m_test values('RKT');
    select * from m_test
    col1
    ZYT
    ABC
    RKT
    alter session set optimizer_mode = RULE
    select distinct col1 from m_test;
    col1
    ABC
    RKT
    ZYT
    Note: Explain plan shows that it's doing SORT UNIQUE
    alter session set optimizer_mode = FIRST_ROWS_1
    select distinct col1 from m_test;
    col1
    ZYT
    ABC
    RKT
    Note: Explain plan shows that it's doing HASH UNIQUE
    I would appreciate if someone can let me know why this is happening,
    Thank you,
    Madhu

    It happened to be sorted when you were using the RBO because the query plan the RBO generated happened to involve a sort. The CBO knows that sorting isn't strictly necessary, so it may or may not choose to apply the sort.
    The CBO has a lot of options for generating query plans, depending on table, column, index, and system statistics, histograms, etc. and has a lot more plan options than the old RBO did. The CBO is a lot more likely to change a query plan than the RBO was, which is normally a good thing (a plan that works for a 10 row table might need to be changed if the table grows to 1 million rows). Depending on the Oracle version, initialization parameters, table statistics, system statistics, etc. the CBO may happen to sort rows before returning them.
    If you want Oracle to sort the rows, however, there is only one way to guarantee that-- add an ORDER BY clause.
    Justin

  • 10g Migration issue in forms related to graphics

    Hi..
    I am facing a 10G migration issue realted to graphics in Forms.
    A form got migrated from 6i to 10g and it has Graphics in it but it is not displaying the graphics in Runtime after
    migration.can anyone help me reagrding how to resolve this Graphics issue in 10g.
    Thanks,
    Venkat

    Graphics no longer exists in Developer Suite 10G. You have to replace the functionality , e.g. by using BI Beans. Have a look at the samples page http://www.oracle.com/technology/sample_code/products/forms/index.html

  • Oracle 10g Migration Workbench 10.1.0.4.0

    Hai,
    Could any of you explain me about Oracle 10g Migration Workbench 10.1.0.4.0
    product and also about the features and usage of this project.
    Thanks in advance.
    A.Mohammed Rafi.

    Sandeep,
    Have you used this user which holds the omwb repository before for a migration? When you connected the first itme, did you get a message, that the repository tables did not exist and would you like to create them?
    Are you using the connected or disconnected source model load?
    Donal

  • Query on forms migration 4i to 10g migration approach.

    We are migrating Oracle forms 4.5 to oracle 10g. We have following apporaches.
         1. Oracle 4.5-->6i-->10g, In this what are benefits of migrating into intermediate version.
         2. if we migrating into intermediate version 6i, do we need to fix all the errors before moving to 6i.
         3. if no, do we lose any functionlity while migrating to 10g.
         4. Does Oracle support direct migration to 10g?
         5. if we open oracle 4.5 form in 10g form builder, do we lose any functionality? do we need to lot manual replacement?
    Kindly help me in this regards.

    Balamurugan wrote:
    We are migrating Oracle forms 4.5 to oracle 10g. We have following apporaches.
         1. Oracle 4.5-->6i-->10g, In this what are benefits of migrating into intermediate version.Oracle's migration path is 4.5, 6i, 10g it is more logical to migrate using this path and it is recommended by Oracle, the obsolete built-ins would be pointed out at compilation and fixes would be more automated and simple since Forms 6i was designed to accept migration from 4.5 and the internal design of the forms will be much more adaptable to later releases.
         2. if we migrating into intermediate version 6i, do we need to fix all the errors before moving to 6i.It would be better and easier to fix things in Forms 6i rather than 10g, you can leave them and than you'll have to fix them under 10g.
         3. if no, do we lose any functionlity while migrating to 10g.Functionality built on obsolete built-ins and commands will be lost, you are more likely to face bugs.
         4. Does Oracle support direct migration to 10g?Oracle's official migration path is 4.5 to 6i to 10g
         5. if we open oracle 4.5 form in 10g form builder, do we lose any functionality? do we need to lot manual replacement?It all depends on your application size and features. I suggest you migrate to Forms 6i first and than to 10g although you can do it directly to 10g since Forms 6i is no longer supported.
    I personally rather follow the recommended path and use Oracle support in 10g migration.
    For more Forms migration information check out [Forms Upgrade Center|http://www.oracle.com/technology/products/forms/htdocs/upgrade/index.html] .
    Tony

  • Headstart Designer 10g Migration Guide?

    Is there a Headstart Designer 10g Migration Guide?
    We are migrating our forms application generated from Designer2K 2.1, Forms 5, Headstart 212 with repository in database Oracle 8 to the latest releases Designer 10g (10.1.2.0.2), Forms 10g (10.1.2.0.2) with repository in Database 10g R2 (10.2.0.2).
    If we follow the migration path for designer and the repository database to 6i then to 10g, recompile the object library and form templates, regenrerate our modules, then will it still work? Do we need to do anything to the Headstart Designer Template Package? Hope you can help with a road map.

    Hi Nathan,
    there are several possibilities for a migration path. It depends on the expected life-span of the application(s), wether or not you want to use new Headstart functionality, etc.
    A description of these possibilities can be found in the migration guide which is included in the Headstart 9i/10g documentation. Do you have the latest version of Headstart available?
    Because you currently use an older version of Headstart, a migration will take a bit more work than described in this documentation because Headstart code has changed. So you will have to replace Headstart function calls or create a wrapper library.
    Further, regeneration of (the more complex) Forms is not that simple as you will probably have to modify the lay-out. If you use client-side functionality (open MS Word/Excel, write to the local file system, etc), you will have to use Oracle's Webutil-package.
    So it can be done. But it will take some planning and programming. Succes.
    p.s. if you (temporarily) publish your e-mail address, i can provide you with some additional info.

  • 9i Spatial 10g Migration

    Dear List,
    We are undergoing Oracle 10g migration at the moment. Could someone point to where I can get information with regards to existing 9i spatial tables and metadata in MDSYS schema. In particular,
    1) Once the spatial tables are imported into 10g spatial, is it necessary to run the SDO_MIGRATE_TO_CURRENT procedure?
    2) Can I simply import key metadata tables from 9i's MDSYS into 10g's MDSYS. If not, is there a migration tools I could use without registering the spatial tables?
    Thanks!
    Bo

    Hi,
    There is no migration of spatial data itself you need to worry about when moving from 9i to 10g, so you should not need to execute sdo_migrate.to_current. If your data is of the form supported way back in 8.1.5 (single digit sdo_gtype), then you should run this procedure.
    By following the directions in the database upgrade guide mdsys schema objects will automatically be upgraded - there are no directions specific to spatial. It just works.
    Hope this helps,
    Dan

  • Forms 6i to 10g migration

    Hi,
    please any one can send me the forms 6i to 10g migration document?.
    Edited by: N.K on Jun 21, 2010 11:39 PM

    It really is NOT just a recompile.
    For starters, the entire 3-tier architecture is different, which causes the need for potential changes using WEBUTIL. Compiling it won't add WEBUTIL and change TEXT_IO to CLIENT_TEXT_IO, or the same thing for a number of othere commands. It also doesn't address RUN_PRODUCT, which requires the RP2RRO pll.
    Edited by: ChrisBaker on Jan 4, 2010 6:00 AM

  • 10g migration 후 SYNONYM 이 invalid 되었습니다.

    저희는 서버가 외국에 있는지라 현지에 있는 DBA가 10g migration 을 수행하였습니다. 문제는 수행후 몇몇 오브젝트들의 synonym이 invalid 되었는데 이에대한 규명 아직 되지 않았습니다.
    아래와같은 object 들이 invalid 되었습니다.
    =====
    PUBLIC     F_GET_WN00
    PUBLIC     PPORTPO01
    PUBLIC     DBMS_XDBZ0
    PUBLIC     DBA_HIST_FILESTATXS
    PUBLIC     DBA_HIST_SQLSTAT
    PUBLIC     DBA_HIST_SQLBIND
    PUBLIC     DBA_HIST_SYSTEM_EVENT
    PUBLIC     DBA_HIST_WAITSTAT
    PUBLIC     DBA_HIST_LATCH
    PUBLIC     DBA_HIST_LATCH_MISSES_SUMMARY
    PUBLIC     DBA_HIST_DB_CACHE_ADVICE
    PUBLIC     DBA_HIST_ROWCACHE_SUMMARY
    PUBLIC     DBA_HIST_SGASTAT
    PUBLIC     DBA_HIST_SYSSTAT
    PUBLIC     DBA_HIST_SYS_TIME_MODEL
    PUBLIC     DBA_HIST_OSSTAT
    PUBLIC     DBA_HIST_PARAMETER
    PUBLIC     DBA_HIST_SEG_STAT
    PUBLIC     DBA_HIST_ACTIVE_SESS_HISTORY
    PUBLIC     DBA_HIST_TABLESPACE_STAT
    PUBLIC     DBA_HIST_SERVICE_STAT
    PUBLIC     DBA_HIST_SERVICE_WAIT_CLASS
    ==
    첫번째 두번째 오브젝트는 저희가 creat하여 계속 사용하고 있던 것들로, migration 작업후 alter compile ** 을 시켰더니 synonym 이 죽어버렸더라구요..
    그리고 나머지 오브젝트들은 오라클시스템과 관련된것들 같은데..
    어쨌건...왜 synonym 들이 invalid 되는지 궁금합니다.
    그리고 시스템 구동시 영향을 끼치지 않을가도요..
    고수님들의 답변 부탁드립니다.

    Hussein Sawwan wrote:
    Now I am getting the error:
    ORA:00604 and ORA:06553 whenever I am adding tempfile and running utlrp.sql;
    How to resolve this issue.
    How do you get these errors? Do you get the same error messages when you add tempfile and run utlrp.sql script?Yes.
    ALTER TABLESPACE Temp1
       ADD DATAFILE '/u02/oracle/data/temp01.dbf' SIZE 1M;
    ALTER TABLESPACE Temp2
       ADD DATAFILE '/u02/oracle/data/temp02.dbf' SIZE 1M;>
    Please post the command you run to add tempfiles along with the error message(s). Also, please show the steps you follow to run utlrp.sql script along with the error message(s).This part is described already.
    startup upgrade
    @utlrp.sql (on DBTier RDBMS_ORACLE_HOME/rdbms/admin)>
    OERR: ORA 604 error occurred at recursive SQL level <num> [ID 18489.1]
    OERR: ORA 6553 "PLS-%s: %s" [ID 20074.1]
    Thanks,
    Hussein

  • 10g query running faster with RBO than CBO

    I am running a query in Oracle 10g that is taking 1minute 15 seconds to run using the CBO. All the tables and indexes in the query are fully analyzed. However if i add a /*+ Rule */ hint to the query and force the optimizer to RBO it runs in 5 seconds.
    Anyone any ideas why this would occur? it's contrary to everything Oracle says about CBO and problematic as RBO is no longer supported in 10g
    Any help / advice greatfully appreciated
    Thanks
    Declan

    My "best" CBO explain plan is......
    Explain complete.
    Elapsed: 00:00:01:90
    PLAN_TABLE_OUTPUT                                                                                                                           
    | Id  | Operation                          |  Name                          | Rows  | Bytes |TempSpc| Cost  |                               
    |   0 | SELECT STATEMENT                   |                                |  3364K|  2553M|       |   666K|                               
    |   1 |  SORT ORDER BY                     |                                |  3364K|  2553M|  5840M|   666K|                               
    |   2 |   VIEW                             |                                |  3364K|  2553M|       |   273K|                               
    |   3 |    UNION-ALL                       |                                |       |       |       |       |                               
    |*  4 |     HASH JOIN                      |                                |  2269K|  1415M|       |   255K|                               
    |*  5 |      TABLE ACCESS FULL             | NODE                           |     6 |   198 |       |   183 |                               
    |*  6 |      HASH JOIN OUTER               |                                |  2269K|  1344M|       |   255K|                               
    |*  7 |       HASH JOIN                    |                                |   710 |   266K|       |  2179 |                               
    |*  8 |        HASH JOIN OUTER             |                                |  1219 |   165K|       |   355 |                               
    |*  9 |         HASH JOIN                  |                                |  1219 |   154K|       |   318 |                               
    |* 10 |          HASH JOIN                 |                                |  1219 |   138K|       |   260 |                               
    |* 11 |           HASH JOIN                |                                |  1219 |   127K|       |   224 |                               
    |  12 |            TABLE ACCESS FULL       | TMP_NODE_WALK_ALL_NODES        |  8168 |   311K|       |    17 |                               
    |* 13 |            HASH JOIN               |                                | 10896 |   723K|       |   201 |                               
    |  14 |             INDEX FAST FULL SCAN   | PK_NODE_RULES_NODE_ID_RULE_ID  | 10896 |   106K|       |     6 |                               
    |  15 |             TABLE ACCESS FULL      | NODE                           | 73004 |  4134K|       |   183 |                               
    |  16 |           INDEX FAST FULL SCAN     | IDX_NODE_CIX2                  | 73004 |   641K|       |    33 |                               
    PLAN_TABLE_OUTPUT                                                                                                                           
    |  17 |          INDEX FAST FULL SCAN      | IDX_NODE_CIX1                  | 73004 |   998K|       |    54 |                               
    |  18 |         INDEX FAST FULL SCAN       | IDX_NODE_CIX2                  | 73004 |   641K|       |    33 |                               
    |* 19 |        TABLE ACCESS FULL           | RULES                          |  6344 |  1517K|       |  1820 |                               
    |  20 |       VIEW                         |                                |   405M|    89G|       | 43581 |                               
    |* 21 |        HASH JOIN OUTER             |                                |   405M|    23G|       | 43581 |                               
    |  22 |         TABLE ACCESS FULL          | TMP_NODE_WALK_ALL_NODES        |  8168 |   103K|       |    17 |                               
    |  23 |         TABLE ACCESS FULL          | UNIVERSAL_RULES                |  3377K|   157M|       | 43256 |                               
    |* 24 |     HASH JOIN OUTER                |                                |  1094K|   410M|   148M| 17453 |                               
    |  25 |      MERGE JOIN CARTESIAN          |                                |   390K|   143M|       | 15029 |                               
    |  26 |       NESTED LOOPS                 |                                |    70 | 25060 |       |  2849 |                               
    |  27 |        NESTED LOOPS                |                                |    70 | 21000 |       |  2779 |                               
    |  28 |         TABLE ACCESS BY INDEX ROWID| UNIVERSAL_RULES                |  1392 | 76560 |       |  1387 |                               
    |* 29 |          INDEX RANGE SCAN          | IDX_UNIVERSAL_RULES_ACCOUNT    |  1392 |       |       |     6 |                               
    |* 30 |         TABLE ACCESS BY INDEX ROWID| RULES                          |     1 |   245 |       |     1 |                               
    |* 31 |          INDEX UNIQUE SCAN         | PK_RULES_RULE_ID_VERSION_ID    |    20 |       |       |       |                               
    |* 32 |        TABLE ACCESS BY INDEX ROWID | NODE                           |     1 |    58 |       |     1 |                               
    |* 33 |         INDEX UNIQUE SCAN          | PK_NODE_NODE_ID                |     6 |       |       |       |                               
    |  34 |       BUFFER SORT                  |                                |  5616 |   153K|       | 15028 |                               
    |  35 |        TABLE ACCESS BY INDEX ROWID | NODE                           |  5616 |   153K|       |   174 |                               
    |* 36 |         INDEX RANGE SCAN           | IDX_NODE_NODE_TYPE_ID          |  5616 |       |       |    11 |                               
    |* 37 |      INDEX FAST FULL SCAN          | IDX_RULES_RULE_ID_STATUS       | 42293 |   289K|       |    48 |                               
    PLAN_TABLE_OUTPUT                                                                                                                           
    Predicate Information (identified by operation id):                                                                                         
       4 - access("NODE"."NODE_TYPE_ID"="SN"."HIERARCHY_TYPE_ID")                                                                               
       5 - filter("NODE"."PARENT_NODE_ID" IS NULL)                                                                                              
       6 - access("SYS_ALIAS_1"."RULE_ID"="UR"."RULE_ID"(+) AND "SYS_ALIAS_1"."VERSION_ID"="UR"."VERSION_ID"(+))                                
       7 - access("NR"."RULE_ID"="SYS_ALIAS_1"."COMBINED_RULE_ID")                                                                              
       8 - access("SN"."PARENT_NODE_ID"="SP"."NODE_ID"(+))                                                                                      
       9 - access("AN"."START_NODE_ID"="SN"."NODE_ID")                                                                                          
      10 - access("AN"."EFFECTIVE_NODE_ID"="EN"."NODE_ID")                                                                                      
      11 - access("AN"."SHORTCUT_NODE_ID"="N"."NODE_ID")                                                                                        
      13 - access("N"."NODE_ID"="NR"."NODE_ID")                                                                                                 
      19 - filter(',A,P,' LIKE '%,'||"SYS_ALIAS_1"."STATUS"||',%')                                                                              
      21 - access("UR"."NODE_ID"(+)="AN"."START_NODE_ID")                                                                                       
      24 - access("R"."RULE_ID"="RP"."RULE_ID"(+))                                                                                              
      29 - access("UR"."ACCOUNT_ID"='0069')                                                                                                     
      30 - filter(',A,P,' LIKE '%,'||"R"."STATUS"||',%')                                                                                        
      31 - access("UR"."RULE_ID"="R"."RULE_ID" AND "UR"."VERSION_ID"="R"."VERSION_ID")                                                          
      32 - filter("N"."HIERARCHY_TYPE_ID"=9)                                                                                                    
    PLAN_TABLE_OUTPUT                                                                                                                           
      33 - access("UR"."NODE_ID"="N"."NODE_ID")                                                                                                 
      36 - access("NODE"."NODE_TYPE_ID"=9)                                                                                                      
      37 - filter("RP"."STATUS"(+)='P')                                                                                                         
    Note: cpu costing is off                                                                                                                    
    28 rows selected.
    Elapsed: 00:00:02:45
    68 rows selected.
    Elapsed: 00:00:05:76While my RBO explain plan is
    Explain complete.
    Elapsed: 00:00:01:23
    PLAN_TABLE_OUTPUT                                                                                                                           
    | Id  | Operation                                |  Name                        | Rows  | Bytes | Cost  |                                   
    |   0 | SELECT STATEMENT                         |                              |       |       |       |                                   
    |   1 |  SORT ORDER BY                           |                              |       |       |       |                                   
    |   2 |   VIEW                                   |                              |       |       |       |                                   
    |   3 |    UNION-ALL                             |                              |       |       |       |                                   
    |   4 |     MERGE JOIN OUTER                     |                              |       |       |       |                                   
    |   5 |      SORT JOIN                           |                              |       |       |       |                                   
    |*  6 |       TABLE ACCESS BY INDEX ROWID        | NODE                         |       |       |       |                                   
    |   7 |        NESTED LOOPS                      |                              |       |       |       |                                   
    |   8 |         NESTED LOOPS                     |                              |       |       |       |                                   
    |   9 |          NESTED LOOPS                    |                              |       |       |       |                                   
    |  10 |           NESTED LOOPS                   |                              |       |       |       |                                   
    |  11 |            NESTED LOOPS                  |                              |       |       |       |                                   
    |  12 |             NESTED LOOPS OUTER           |                              |       |       |       |                                   
    |  13 |              NESTED LOOPS                |                              |       |       |       |                                   
    |  14 |               TABLE ACCESS FULL          | TMP_NODE_WALK_ALL_NODES      |       |       |       |                                   
    |  15 |               TABLE ACCESS BY INDEX ROWID| NODE                         |       |       |       |                                   
    |* 16 |                INDEX UNIQUE SCAN         | PK_NODE_NODE_ID              |       |       |       |                                   
    PLAN_TABLE_OUTPUT                                                                                                                           
    |  17 |              TABLE ACCESS BY INDEX ROWID | NODE                         |       |       |       |                                   
    |* 18 |               INDEX UNIQUE SCAN          | PK_NODE_NODE_ID              |       |       |       |                                   
    |  19 |             TABLE ACCESS BY INDEX ROWID  | NODE                         |       |       |       |                                   
    |* 20 |              INDEX UNIQUE SCAN           | PK_NODE_NODE_ID              |       |       |       |                                   
    |  21 |            TABLE ACCESS BY INDEX ROWID   | NODE                         |       |       |       |                                   
    |* 22 |             INDEX UNIQUE SCAN            | PK_NODE_NODE_ID              |       |       |       |                                   
    |  23 |           TABLE ACCESS BY INDEX ROWID    | NODE_RULES                   |       |       |       |                                   
    |* 24 |            INDEX RANGE SCAN              | IDX_NODE_RULES_NODE_ID       |       |       |       |                                   
    |* 25 |          TABLE ACCESS BY INDEX ROWID     | RULES                        |       |       |       |                                   
    |* 26 |           INDEX RANGE SCAN               | IDX_RULES_COMBINED_RULE_ID   |       |       |       |                                   
    |* 27 |         INDEX RANGE SCAN                 | IDX_NODE_NODE_TYPE_ID        |       |       |       |                                   
    |* 28 |      SORT JOIN                           |                              |       |       |       |                                   
    |  29 |       VIEW                               |                              |       |       |       |                                   
    |  30 |        NESTED LOOPS OUTER                |                              |       |       |       |                                   
    |  31 |         TABLE ACCESS FULL                | TMP_NODE_WALK_ALL_NODES      |       |       |       |                                   
    |  32 |         TABLE ACCESS BY INDEX ROWID      | UNIVERSAL_RULES              |       |       |       |                                   
    |* 33 |          INDEX RANGE SCAN                | IDX_UNIVERSAL_RULES_NODE     |       |       |       |                                   
    |  34 |     NESTED LOOPS OUTER                   |                              |       |       |       |                                   
    |  35 |      NESTED LOOPS                        |                              |       |       |       |                                   
    |  36 |       NESTED LOOPS                       |                              |       |       |       |                                   
    |  37 |        NESTED LOOPS                      |                              |       |       |       |                                   
    PLAN_TABLE_OUTPUT                                                                                                                           
    |  38 |         TABLE ACCESS BY INDEX ROWID      | NODE                         |       |       |       |                                   
    |* 39 |          INDEX RANGE SCAN                | IDX_NODE_NODE_TYPE_ID        |       |       |       |                                   
    |  40 |         TABLE ACCESS BY INDEX ROWID      | UNIVERSAL_RULES              |       |       |       |                                   
    |* 41 |          INDEX RANGE SCAN                | IDX_UNIVERSAL_RULES_ACCOUNT  |       |       |       |                                   
    |* 42 |        TABLE ACCESS BY INDEX ROWID       | NODE                         |       |       |       |                                   
    |* 43 |         INDEX UNIQUE SCAN                | PK_NODE_NODE_ID              |       |       |       |                                   
    |* 44 |       TABLE ACCESS BY INDEX ROWID        | RULES                        |       |       |       |                                   
    |* 45 |        INDEX UNIQUE SCAN                 | PK_RULES_RULE_ID_VERSION_ID  |       |       |       |                                   
    |* 46 |      INDEX RANGE SCAN                    | IDX_RULES_RULE_ID_STATUS     |       |       |       |                                   
    Predicate Information (identified by operation id):                                                                                         
       6 - filter("NODE"."PARENT_NODE_ID" IS NULL)                                                                                              
      16 - access("AN"."START_NODE_ID"="SN"."NODE_ID")                                                                                          
      18 - access("SN"."PARENT_NODE_ID"="SP"."NODE_ID"(+))                                                                                      
      20 - access("AN"."EFFECTIVE_NODE_ID"="EN"."NODE_ID")                                                                                      
      22 - access("AN"."SHORTCUT_NODE_ID"="N"."NODE_ID")                                                                                        
      24 - access("N"."NODE_ID"="NR"."NODE_ID")                                                                                                 
      25 - filter(',A,P,' LIKE '%,'||"SYS_ALIAS_1"."STATUS"||',%')                                                                              
    PLAN_TABLE_OUTPUT                                                                                                                           
      26 - access("NR"."RULE_ID"="SYS_ALIAS_1"."COMBINED_RULE_ID")                                                                              
      27 - access("NODE"."NODE_TYPE_ID"="SN"."HIERARCHY_TYPE_ID")                                                                               
      28 - access("SYS_ALIAS_1"."RULE_ID"="UR"."RULE_ID"(+))                                                                                    
           filter("SYS_ALIAS_1"."VERSION_ID"="UR"."VERSION_ID"(+) AND                                                                           
                  "SYS_ALIAS_1"."RULE_ID"="UR"."RULE_ID"(+))                                                                                    
      33 - access("UR"."NODE_ID"(+)="AN"."START_NODE_ID")                                                                                       
      39 - access("NODE"."NODE_TYPE_ID"=9)                                                                                                      
      41 - access("UR"."ACCOUNT_ID"='0069')                                                                                                     
      42 - filter("N"."HIERARCHY_TYPE_ID"=9)                                                                                                    
      43 - access("UR"."NODE_ID"="N"."NODE_ID")                                                                                                 
      44 - filter(',A,P,' LIKE '%,'||"R"."STATUS"||',%')                                                                                        
      45 - access("UR"."RULE_ID"="R"."RULE_ID" AND "UR"."VERSION_ID"="R"."VERSION_ID")                                                          
      46 - access("R"."RULE_ID"="RP"."RULE_ID"(+) AND "RP"."STATUS"(+)='P')                                                                     
    Note: rule based optimization                                                                                                               
    28 rows selected.
    Elapsed: 00:00:04:42
    78 rows selected.
    Elapsed: 00:00:08:86Any additional help appreciated
    I am going to try and run a trace against the sql now and see if i can get any more information
    Thanks in advance
    Declan

  • 10g Migration Problem: error shown when trying to call a report from form

    Dear Friends,
    I am working on migrating developer 2000 forms to 10g forms. I am using migration tool for this. Everything is going fine except calling report from a form.
    Say, in the original form I had the following:
    RUN_PRODUCT(REPORTS,’ C:\test1.rdf’,SYNCHRONOUS,RUNTIME,FILESYSTEM,pi_id,NULL);
    After migration its has become:
    rp2rro.rp2rro_run_product(REPORTS, ’ C:\test1.rdf’,SYNCHRONOUS,RUNTIME,FILESYSTEM,pi_id,NULL);
    Then, I have kept the report ‘test1.rdf’ in the ‘OraHomeAS\reports\samples\demo\’ location and changed the above code into:
    rp2rro.rp2rro_run_product(REPORTS,'test1.rdf',SYNCHRONOUS,RUNTIME,FILESYSTEM,pi_id,NULL);
    Now the form runs fine on application server but it can’t call the report. While attempting to call the report, it shows the following error:
    ORA-06508
    FRM-40735
    Please note that the report ‘test1.rdf’ individually runs fine on the application server and at the time of migration I provided all the information (e.g. report server name) correctly. If I am missing any package, please tell which package I am missing and where should I paste it.
    Please help me because I am very close to the deadline!
    Rgds,
    Luther

    Hi,
    The conversion to use the rp2rrp call needs a library to resolve the call which I think is called rp2rro.pll.
    It seems that this library is not being found at run time, which is what the ora-06508 error often means.
    I guess that you have compiled the form and must therefore have the pll to compile, so it is the forms_path setting in the app server run time that might not be set.
    Look at the environment file (default.env is the original name for this, if you haven't created a custom one) for the entry FORMS_PATH. Is the location of your library specified in the path ?? If not put the directory in, then stop and restart the app server.
    rgds
    Tony

  • RBO vs CBO : Are you going to maintain RBO in DBMS?

    Hello, Oracle?
    I'm facing many critics about the type of SQL optimization from customer.
    I'm still using RBO in application SQL because, sometimes, your automatic optimization (analyze) make the execution plan of performance-oriented SQL worse and that kind of SQL have to be executed very long time.
    So I checked these SQLs and appended the hint ("/*+ RULE */").
    From that time, these SQLs were always executed in the same execution plan
    and other performance issues were disappeared.
    I want to ask you that
    1) Did I do wrong things?
    2) using RBO in the 10g or higher can make other Unexpected, Serious problem?
    3) Do you really want to close supporting the RBO?
    4) Is it wrong using RBO in the 10g or higher ?
    Thanks in Advance, Oracle and Other Experts or People who have the experiece
    about the RBO in Oracle 10g or higer.

    2) using RBO in the 10g or higher can make other Unexpected, Serious problem?If you are really using 10g then you ought to learn how to use all its features properly. This means learning how Cost-Based Optimization works. You should do this as much as a favour to yourself and your career prospects as for any other reason.
    If your database is small enough that the RBO provides sufficiently effective performance then you can get away with it. But in the long run CBO is definitely the way to go.
    Cheers, APC
    blog: http://radiofreetooting.blogspot.com/

  • Sybase to Oracle 10g migration

    Hi, I have a task to perform Sybase to Oracle 10g conversion; can anybody recommend any documents or metalink docs to me?
    Thanks
    Gaurav

    If you have migration workbench related question you can post in Migration Workbench forum,
    Database and Application Migrations

  • Sql server 2005 to Oracle 10g migration

    Hi all,
    Is there any tool to migrate a sql server 2005 database to Oracle 10G ?
    I tried the sql developer migration option but I am unable to load the .ocp file.
    The option to load the .ocp file is not there
    Please advice....

    Great....
    I hope there may be steps in oracle workbench documentation regarding conversion.
    http://www.oracle.com/technology/tech/migration/workbench/htdocs/101040/user_guide/book.pdf
    You have to read in the above link. I am sure, there should be something regarding this too.
    Regards
    Girish Sharma
    Edited by: Girish Sharma on Dec 22, 2009 12:30 PM
    Edited by: Girish Sharma on Dec 22, 2009 12:33 PM

Maybe you are looking for

  • Problem Installing CS5

    Hello there, I'm mac(macbook) OSX snow leopard user trying to complete installing photoshop CS5. Every time I install CS5 by adobe installer it seems to be done, but actually when I go to application folder and see CS5 icon it's broken. And when I cl

  • Can I make iBook available to buyers of print edition for free?

    I am the publisher of an educational guide that gives careers advice to school leavers. Until now this has been produced in print format only and sent out to subscribing school and colleges. I would now like to make the publication available in iBook

  • Serial response groups not working

    Hello,I have the following problem with a serial response group. When I call the response group : 1. it goes to a person in the list but not always the first one in the list 2. if nobody pics up it stays ringing on that person and does not go to the

  • Cinnamon bogging down after a while, windows move in clunky fashion

    After a while, when I drag windows around, they "skip" and don't follow the usual smoth drag a window normally does.  I haven't been able to pin point this, but it happens no matter what application I am using.  If I restart cinnamon, it is back to n

  • Music in the cloud not 256Kbps

    In an attempt to upgrade music quality I've deleted a lot of old songs that are at 128Kbps.  Yet in the cloud, and when I download them, they stay at 128Kbps.  These are well known artists like Aerosmith. Why are they not downloading as 256Kbps?