Trying to execute a STP which has TABLE TYPES.

Hi,
I wrote a program with the below specification inside a pkg :
pl/sql varray declaration inside the pkg,
TYPE varray_tnb IS TABLE OF CHAR(10) INDEX BY BINARY_INTEGER;
TYPE varray_act_cd IS TABLE OF CHAR(15) INDEX BY BINARY_INTEGER;
TYPE varray_sts_cd IS TABLE OF CHAR(10) INDEX BY BINARY_INTEGER;
TYPE varray_sts_txt IS TABLE OF CHAR(250) INDEX BY BINARY_INTEGER;
PROCEDURE re_STP_u(
a_order_num IN re.nbr_order%TYPE,
a_tnb IN varray_tnb,
a_action_code IN varray_act_cd,
a_status_code IN varray_sts_cd,
a_status_txt IN varray_sts_txt);
When I try to run a test script to test if the above STP, I get the below error:
DECLARE
TYPE V_TNB iS TABLE OF CHAR(10) INDEX BY BINARY_INTEGER;
TYPE V_ACT iS TABLE OF CHAR(15) INDEX BY BINARY_INTEGER;
TYPE V_STS iS TABLE OF CHAR(10) INDEX BY BINARY_INTEGER;
TYPE V_TXT iS TABLE OF CHAR(250) INDEX BY BINARY_INTEGER;
a_OrdN rehome_migration_ord.nbr_order%TYPE := '789';
a_tnb V_TNB := V_TNB(7192340129,7192340128);
a_ac V_ACT := V_ACT('ACT CDE','BGE CDE');
a_sc V_STS := V_STS('INITIATED','INITIATED');
a_st V_TXT := V_TXT('TExt for Status','status text');
begin
tds_upd_pkg.re_STP_u(a_OrdN,a_tnb,a_ac,a_sc,a_st);
exception
WHEN OTHERS THEN
RAISE;
end;
ORA-06550: line 7, column 16:
PLS-00222: no function with name 'V_TNB' exists in this scope
ORA-06550: line 7, column 7:
PL/SQL: Item ignored
ORA-06550: line 8, column 15:
PLS-00222: no function with name 'V_ACT' exists in this scope
ORA-06550: line 8, column 6:
PL/SQL: Item ignored
ORA-06550: line 9, column 15:
PLS-00222: no function with name 'V_STS' exists in this scope
ORA-06550: line 9, column 6:
PL/SQL: Item ignored
ORA-06550: line 10, column 15:
PLS-00222: no function with name 'V_TXT' exists in this scope
ORA-06550: line 10, column 6:
PL/SQL: Item ignored
ORA-06550: line 12, column 44:
PLS-00320: the declaration of the type of this expression is incomplete or
malformed
ORA-06550: line 12, column 1:
PL/SQL: Statement ignored
Can somebody look at the script and see where I am wrong.
If I do not assign any value to the varray variables I am able to go past the above error and getting "PLS-00306: wrong number or types of arguments in call to..".

I can't recall the exact wording Oracle uses but you are mixing the two different types of Collections that Oracle allows. One is where Oracle manages the size of the entry for you automatically. The other is where you have to .EXTEND the collection to increase the number of entries. Using "INDEX BY BINARY_INTEGER" tells Oracle to automanage the collection size. "V_TNB(7192340129,7192340128)" can only be used on those collections where you manage the size. See my modified example that doesn't error out until line 10 (a_sc) with the errors you listed. Note what I commented out on line 2, line 9, and added on lines 13 and 14 to replace line 9.
DECLARE
  TYPE V_TNB iS TABLE OF CHAR(10); -- INDEX BY BINARY_INTEGER;
  TYPE V_ACT iS TABLE OF CHAR(15) INDEX BY BINARY_INTEGER;
  TYPE V_STS iS TABLE OF CHAR(10) INDEX BY BINARY_INTEGER;
  TYPE V_TXT iS TABLE OF CHAR(250) INDEX BY BINARY_INTEGER;
  a_OrdN VARCHAR2(3) := '789';
  a_tnb V_TNB := V_TNB(7192340129,7192340128);
  a_ac V_ACT;-- := V_ACT('ACT CDE','BGE CDE');
  a_sc V_STS := V_STS('INITIATED','INITIATED');
  a_st V_TXT := V_TXT('TExt for Status','status text');
begin
  a_ac(1) := 'ACT CDE';
  a_ac(2) := 'BGE CDE';
  NULL;
end;Here is the Oracle documentation I was thinking of. http://download.oracle.com/docs/cd/B19306_01/appdev.102/b14261/collections.htm#sthref1153

Similar Messages

  • MDO Query errors in log -[Cannot fetch column 22, which has JDBC type DOUBLE, into a Java variable of type ]

    Hello,
    We are seeing a lot of log messages like the one below when an MDO select query is run. There is a message for every numeric column. There doesnt seem to be any issue with the queries working properly its just creating a lot of log messages. Has anyone else had this issue?
    Exception of type com.sap.sql.log.OpenSQLException caught:
    Cannot fetch column 22, which has JDBC type DOUBLE, into a Java variable of type
    float..
    [EXCEPTION]
    com.sap.sql.log.OpenSQLException: Cannot fetch
    column 22, which has JDBC type DOUBLE, into a Java variable of type float.
    at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:83) ...

    Hi Christian,
    You are right. As in your case it is a select query it does not reflect the error automatically. In my case, I had an insert query so it failed then and there, which was easier to debug and fix.
    I have one question regarding your case. When you read the MDO using the query, what do you do with the output? Do you assign it to any local/transaction property in the output links of the query block or in a proceeding assignment block?
    Because, the error mentions that the assignment of float to double datatype fails. So, in theory there should be some assignment done with the output.
    Please check if you could figure out this part in your transaction.
    Regards,
    Saumya Govil

  • Error in executing a layout which has a hierarchy in lead column

    Hi Experts,
    I have used a planning level where a characteristic called 'reporting code' is restricted with a hierarchy.
    Now when I am trying to execute a layout under this level I am getting some error. The characteristic is used in the lead column in this layout.Two differene type of error I am getting in following two different cases.
    1. When I am using the hierarchical settings for the lead column then I am getting the error 'Hierarchy INPUT is not suited to the planning mode.
    2. When I am not using the hierarchical settings for the lead column then I am getting the error 'Too many characteristic combinations for manual planning'.
    If I reduce the no of nodes in the hierarchy for testing then none of this error is coming. So I think this is related to the volume of the hierarchy.
    Can anybody put some light on this why this error is coming and how to resolve this error?
    Regards,
    Saikat Datta Gupta.

    In case of text hierarchies, wherein we can plan only on leaves, for the layout to be displayed in a hierarichal manner, we need the following settings.
    In the first screen of the layout builder, next to the layout description, click on the hierarchy icon, choose non-hierarchical data model and in the additional settings, all possible char combinations.
    In the last screen of the layout builder, in lead column settings, check display totals as hierarchy.
    With the above settings, layout shows the result in hierarchy mode.
    In BPS layout, the no of rows will be limited. As you have given all possible combinations, system tries to display the entire hierarchy, i think which is exceeding the max limit. Try reducing the hierarchy size or keep the additional settings as "Transaction data" and check if the problem persists.

  • Short dump while executing few queries , which has got created on Infoset.

    Hi,
    We went to BI7.0 upgrade from BW3.x now.
    We are getting short dump short dump while executing few queries and work book, which has got created on Infoset.
    When i was executing work book where i was geting popup message saying that "Erro ZSD_XST_F00121 is invalid".When i click that message it went to dump.
    I was getting this error while executing query on infoset.
    We are currently SP Stack 13(Patch level 15).
    I found some note 1067918 as per the shortdum,where it is saying that you need to apply SP Stack14(patch level16).
    Please some one who had earlier this kind of issue.
    I appreciate your answer.

    Dear Krish,
    Yes, It is the patch problem.
    We too faced the same issue on Infosets.
    Apply SP 15.
    Regards,
    Ram.

  • Executing a column which has a sql query in a tabular form

    Hi,
    I have a tabular form which contains a column named as SQL which has sql statements in it. Without going to the SQL workshop in Apex i want to execute that query in the tabular form itself. For that i've created a page item which fetches the particular rows sql query and created a button 'EXECUTE'. When i click the execute button it should run the query and should display whether the query is correct or not and should show the error message.
    Can any one provide solution for this or whether there are any other ways to achive this scenario.
    With Regards
    Balaji.P.K

    Balaji P.K wrote:
    Can any one provide solution for this or whether there are any other ways to achive this scenario.Difficult as we have no idea what this "scenario" actually is. Go back several steps and explain in detail the problem this is supposed to solve.
    I have a tabular form which contains a column named as SQLBad idea. <tt>SQL</tt> is a PL/SQL reserved word. Using any token from Oracle namespaces as a database identifier is confusing/problematic.
    which has sql statements in it.Why? Where does this SQL come from? What is the source of the tabular form?
    Without going to the SQL workshop in Apex i want to execute that query in the tabular form itself.Explain the "execute that query in the tabular form itself" concept. Where do the results go?

  • Trying to execute a procedure which is using VARRAY as a parameter

    Hi Gurus,
    I am trying to execute a procedure having an array as input.
    However I am getting an error during execution.
    Can you please help me on how to execute a procedure having an array as input?
    create or replace type type_a as table of number(10,0);
    Script:
    declare
    txn_id type_a
    begin
    txn_id type_a()
    txn_id(1) := 516963065;
    procedure_1(emp_id =>1001, txn_id)
    end;

    Try this:
    SQL> CREATE OR REPLACE TYPE type_a AS TABLE OF NUMBER (10, 0)
      2  /
    Type created.
    SQL> CREATE OR REPLACE PROCEDURE procedure_1 ( emp_id NUMBER, p_txn type_a)
      2  AS
      3    i          PLS_INTEGER;
      4  BEGIN
      5    DBMS_OUTPUT.ENABLE (1000000);
      6    FOR i IN 1 .. p_txn.COUNT
      7    LOOP
      8      DBMS_OUTPUT.put_line (TO_CHAR ( i, '00.B') || emp_id || ' = ' || p_txn (i));
      9    END LOOP;
    10  END;
    11  /
    Procedure created.
    SQL> DECLARE
      2    txn_id   type_a;
      3  BEGIN
      4    txn_id      :=
      5      type_a (
      6              516963065
      7            , 1963065
      8            , 2963065
      9            , 3963065
    10             );
    11    procedure_1 ( 1001, txn_id);
    12  END;
    13  /
    01.1001 = 516963065
    02.1001 = 1963065
    03.1001 = 2963065
    04.1001 = 3963065
    PL/SQL procedure successfully completed.:p

  • In Smartforms can i use table type which has table inside table

    Hi ,
    I would like to know whether in Form Interface can we declare table type which has a table and one of its field is again a table( Nested tables)..
    Can we declare like that ?? Need your suggestions please...
    Rgds.,
    subash

    Yes, we can.
    Check Smartform LB_BIL_INVOICE
    Importing parameter IS_BIL_INVOICE TYPE LBBIL_INVOICE
    Regards,
    Naimesh Patel

  • Datasources with function module which uses table type

    hi..
    I am creating a datasource which extracts data using a function module from xRPM to BW. When creating the function module it gives an error " TABLES parameters are obsolete!" while trying to specify the extract structure. I searched in SDN and learnt that we need to use table types and use that in the changing tab.Not sure how that works and where we need to use the extract structure for this.
    Could someone please explain this to me and let me know how i can create my datasource using this type of function module.

    Hi,
    in your case you need the tables parameter, as the service api expects the result of the fm in a table called e_t_data. Of course table parameters are obsolet but you can just ignore the warning and it will work.
    regards
    Siggi
    PS: Extraction fm must follow a strict interface definition.
    Message was edited by:
            Siegfried Szameitat

  • How to re-execute a job which has failed

    hi everyone,
                        i am executing a job ....it executed for few minutes and hav been able to load few records in the final table(target)....some exception is thrown up and job failed after that....i want to re-execute the job with only the records that are not processed...how to identify which records are processed?
    is there any process to do so in BO DI?

    Hi Suneel
    You can use several methods to ensure that you do not insert duplicate rows:
    u2022 Design the data flow to completely replace the target table during each
    execution
    This technique can be optimal when the changes to the target table are
    numerous compared to the size of the table. You can use tuning
    techniques such as bulk loading options to improve overall performance.
    u2022 Set the auto correct load option for the target table
    The auto correct load option checks the target table for existing rows
    before adding new rows to the table. Using the auto correct load option,
    however, can needlessly slow jobs executed in non-recovery mode.
    Consider this technique when the target table is large and the changes
    to the table are relatively few.
    u2022 Include a SQL command to execute before the table loads
    Preload SQL commands can remove partial database updates that occur
    during incomplete execution of a step in a job. Typically, the preload SQL
    command deletes rows based on a variable that is set before the partial
    insertion step began.

  • Performance issue when trying to execute DBMS_METADATA.GET_DDL of a table

    Hello.
    I have a database with lots of partitioned tables and indexes and when I try to get the DDL of a partitioned table the query runs for hours and does not end.
    I tried do gather data dictionary statistics but it had no impact on performance.
    Can anybody help me find what's causing this performance problem?
    Information about the enviorment:
    Oracle version:
    SQL> select * from v$version;
    BANNER
    Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
    DDL query:
    select dbms_metadata.get_ddl('TABLE', 'TABLE1') from dual;
    On the "Top Activity" of the Database Control console, this is the query that's running:
    SELECT /*+all_rows*/ SYS_XMLGEN(VALUE(KU$), XMLFORMAT.createFormat2('TABLE_T', '7')), KU$.OBJ_NUM
    FROM SYS.KU$_PHTABLE_VIEW KU$
    WHERE NOT (BITAND (KU$.PROPERTY,8192)=8192) AND NOT BITAND(KU$.SCHEMA_OBJ.FLAGS,128)!=0 AND KU$.SCHEMA_OBJ.NAME=:NAME1 AND KU$.SCHEMA_OBJ.OWNER_NAME=:SCHEMA2;
    Edited by: Krulikowski on Jan 11, 2013 10:44 AM

    |*563 | INDEX RANGE SCAN | I_OBJ1 | 1 | | | 3 (0)| 00:00:01 |
    | 564 | TABLE ACCESS CLUSTER | USER$ | 1 | 19 | | 1 (0)| 00:00:01 |
    |*565 | INDEX UNIQUE SCAN | I_USER# | 1 | | | 0 (0)| 00:00:01 |
    | 566 | VIEW | | 1 | 86 | | 4 (25)| 00:00:01 |
    | 567 | SORT ORDER BY | | 1 | 64 | | 4 (25)| 00:00:01 |
    | 568 | NESTED LOOPS | | 1 | 64 | | 3 (0)| 00:00:01 |
    | 569 | ID TABLE ACCESS BY INDEX ROW | SUBPARTCOL$ | 1 | 15 | | 2 (0)| 00:00:01 |
    |*570 | INDEX RANGE SCAN | I_SUBPARTCOL$ | 1 | | | 1 (0)| 00:00:01 |
    |*571 | TABLE ACCESS CLUSTER | COL$ | 1 | 49 | | 1 (0)| 00:00:01 |
    |*572 | INDEX UNIQUE SCAN | I_OBJ# | 1 | | | 0 (0)| 00:00:01 |
    | 573 | TABLE ACCESS CLUSTER | USER$ | 1 | 19 | | 1 (0)| 00:00:01 |
    |*574 | INDEX UNIQUE SCAN | I_USER# | 1 | | | 0 (0)| 00:00:01 |
    | 575 | TABLE ACCESS CLUSTER | SEG$ | 1 | 70 | | 3 (0)| 00:00:01 |
    |*576 | INDEX UNIQUE SCAN | I_FILE#_BLOCK# | 1 | | | 2 (0)| 00:00:01 |
    | 577 | ROWID TABLE ACCESS BY INDEX | DEFERRED_STG$ | 1 | 28 | | 2 (0)| 00:00:01 |
    |*578 | INDEX UNIQUE SCAN | I_DEFERRED_STG1 | 1 | | | 1 (0)| 00:00:01 |
    | 579 | TABLE ACCESS CLUSTER | USER$ | 1 | 19 | | 1 (0)| 00:00:01 |
    |*580 | INDEX UNIQUE SCAN | I_USER# | 1 | | | 0 (0)| 00:00:01 |
    | 581 | NESTED LOOPS | | 1 | 120 | | 5 (0)| 00:00:01 |
    | 582 | X ROWID TABLE ACCESS BY INDE | OBJ$ | 1 | 101 | | 4 (0)| 00:00:01 |
    |*583 | INDEX RANGE SCAN | I_OBJ1 | 1 | | | 3 (0)| 00:00:01 |
    | 584 | TABLE ACCESS CLUSTER | USER$ | 1 | 19 | | 1 (0)| 00:00:01 |
    |*585 | INDEX UNIQUE SCAN | I_USER# | 1 | | | 0 (0)| 00:00:01 |
    | 586 | R TABLE ACCESS CLUSTE | SEG$ | 1 | 70 | | 3 (0)| 00:00:01 |
    |*587 | INDEX UNIQUE SCAN | I_FILE#_BLOCK# | 1 | | | 2 (0)| 00:00:01 |
    | 588 | DEX ROWID TABLE ACCESS BY IN | DEFERRED_STG$ | 1 | 28 | | 2 (0)| 00:00:01 |
    |*589 | INDEX UNIQUE SCAN | I_DEFERRED_STG1 | 1 | | | 1 (0)| 00:00:01 |
    | 590 | TER TABLE ACCESS CLUS | TS$ | 1 | 18 | | 1 (0)| 00:00:01 |
    |*591 | N INDEX UNIQUE SCA | I_TS# | 1 | | | 0 (0)| 00:00:01 |
    | 592 | STER TABLE ACCESS CLU | TS$ | 1 | 8 | | 1 (0)| 00:00:01 |
    |*593 | AN INDEX UNIQUE SC | I_TS# | 1 | | | 0 (0)| 00:00:01 |
    | 594 | USTER TABLE ACCESS CL | USER$ | 1 | 19 | | 1 (0)| 00:00:01 |
    |*595 | CAN INDEX UNIQUE S | I_USER# | 1 | | | 0 (0)| 00:00:01 |
    | 596 | LUSTER TABLE ACCESS C | SEG$ | 1 | 70 | | 3 (0)| 00:00:01 |
    |*597 | SCAN INDEX UNIQUE | I_FILE#_BLOCK# | 1 | | | 2 (0)| 00:00:01 |
    | 598 | BY INDEX ROWID TABLE ACCESS | DEFERRED_STG$ | 1 | 28 | | 2 (0)| 00:00:01 |
    |*599 | SCAN INDEX UNIQUE | I_DEFERRED_STG1 | 1 | | | 1 (0)| 00:00:01 |
    | 600 | NESTED LOOPS | | 1 | 447 | | 900 (1)| 00:00:04 |
    |*601 | HASH JOIN | | 1 | 425 | | 899 (1)| 00:00:04 |
    | 602 | NESTED LOOPS | | 1 | 120 | | 5 (0)| 00:00:01 |
    | 603 | BY INDEX ROWID TABLE ACCESS | OBJ$ | 1 | 101 | | 4 (0)| 00:00:01 |
    |*604 | SCAN INDEX RANGE | I_OBJ1 | 1 | | | 3 (0)| 00:00:01 |
    | 605 | CLUSTER TABLE ACCESS | USER$ | 1 | 19 | | 1 (0)| 00:00:01 |
    |*606 | E SCAN INDEX UNIQU | I_USER# | 1 | | | 0 (0)| 00:00:01 |
    |*607 | VIEW | INDPARTV$ | 33387 | 9944K| | 893 (1)| 00:00:04 |
    | 608 | R WINDOW BUFFE | | 33387 | 4336K| | 893 (1)| 00:00:04 |
    | 609 | S BY INDEX ROWID TABLE ACCES | INDPART$ | 33387 | 4336K| | 893 (1)| 00:00:04 |
    | 610 | SCAN INDEX FULL | I_INDPART_BOPART$ | 33387 | | | 103 (1)| 00:00:01 |
    | 611 | LUSTER TABLE ACCESS C | TS$ | 1 | 22 | | 1 (0)| 00:00:01 |
    |*612 | SCAN INDEX UNIQUE | I_TS# | 1 | | | 0 (0)| 00:00:01 |
    | 613 | VIEW | | 19858 | 40M| | 1471 (1)| 00:00:07 |
    | 614 | SORT ORDER BY | | 19858 | 3956K| 4688K| 1471 (1)| 00:00:07 |
    |*615 | HASH JOIN | | 19858 | 3956K| | 698 (1)| 00:00:03 |
    | 616 | TABLE ACCESS FULL | LOB$ | 1547 | 24752 | | 461 (1)| 00:00:02 |
    |*617 | VIEW | LOBFRAGV$ | 19858 | 3645K| | 236 (1)| 00:00:01 |
    | 618 | WINDOW BUFFER | | 19858 | 1066K| | 236 (1)| 00:00:01 |
    | 619 | INDEX ROWID TABLE ACCESS BY | LOBFRAG$ | 19858 | 1066K| | 236 (1)| 00:00:01 |
    | 620 | INDEX FULL SCAN | I_LOBFRAG_PARENTOBJFRAG$ | 19858 | | | 61 (0)| 00:00:01 |
    | 621 | ER TABLE ACCESS CLUST | USER$ | 1 | 19 | | 1 (0)| 00:00:01 |
    |*622 | INDEX UNIQUE SCAN | I_USER# | 1 | | | 0 (0)| 00:00:01 |
    | 623 | NESTED LOOPS | | 1 | 120 | | 5 (0)| 00:00:01 |
    | 624 | NDEX ROWID TABLE ACCESS BY I | OBJ$ | 1 | 101 | | 4 (0)| 00:00:01 |
    |*625 | INDEX RANGE SCAN | I_OBJ1 | 1 | | | 3 (0)| 00:00:01 |
    | 626 | TER TABLE ACCESS CLUS | USER$ | 1 | 19 | | 1 (0)| 00:00:01 |
    |*627 | N INDEX UNIQUE SCA | I_USER# | 1 | | | 0 (0)| 00:00:01 |
    | 628 | NESTED LOOPS | | 1 | 53 | | 5 (0)| 00:00:01 |
    | 629 | INDEX ROWID TABLE ACCESS BY | OBJ$ | 1 | 34 | | 4 (0)| 00:00:01 |
    |*630 | AN INDEX RANGE SC | I_OBJ1 | 1 | | | 3 (0)| 00:00:01 |
    | 631 | USTER TABLE ACCESS CL | USER$ | 1 | 19 | | 1 (0)| 00:00:01 |
    |*632 | CAN INDEX UNIQUE S | I_USER# | 1 | | | 0 (0)| 00:00:01 |
    |*633 | STER TABLE ACCESS CLU | COL$ | 1 | 49 | | 2 (0)| 00:00:01 |
    |*634 | AN INDEX UNIQUE SC | I_OBJ# | 1 | | | 1 (0)| 00:00:01 |
    | 635 | USTER TABLE ACCESS CL | TAB$ | 1 | 13 | | 2 (0)| 00:00:01 |
    |*636 | CAN INDEX UNIQUE S | I_OBJ# | 1 | | | 1 (0)| 00:00:01 |
    | 637 | Y INDEX ROWID TABLE ACCESS B | COLTYPE$ | 1 | 13 | | 2 (0)| 00:00:01 |
    |*638 | SCAN INDEX UNIQUE | I_COLTYPE2 | 1 | | | 1 (0)| 00:00:01 |
    | 639 | CLUSTER TABLE ACCESS | SEG$ | 1 | 70 | | 3 (0)| 00:00:01 |
    |*640 | SCAN INDEX UNIQUE | I_FILE#_BLOCK# | 1 | | | 2 (0)| 00:00:01 |
    | 641 | BY INDEX ROWID TABLE ACCESS | DEFERRED_STG$ | 1 | 28 | | 2 (0)| 00:00:01 |
    |*642 | E SCAN INDEX UNIQU | I_DEFERRED_STG1 | 1 | | | 1 (0)| 00:00:01 |
    | 643 | S CLUSTER TABLE ACCES | TS$ | 1 | 18 | | 1 (0)| 00:00:01 |
    |*644 | UE SCAN INDEX UNIQ | I_TS# | 1 | | | 0 (0)| 00:00:01 |
    | 645 | SS CLUSTER TABLE ACCE | TS$ | 1 | 8 | | 1 (0)| 00:00:01 |
    |*646 | QUE SCAN INDEX UNI | I_TS# | 1 | | | 0 (0)| 00:00:01 |
    | 647 | NESTED LOOPS | | 1 | 55 | | 3 (0)| 00:00:01 |
    | 648 | BY INDEX ROWID TABLE ACCESS | TABPART$ | 1 | 42 | | 2 (0)| 00:00:01 |
    |*649 | E SCAN INDEX UNIQU | I_TABPART_OBJ$ | 1 | | | 1 (0)| 00:00:01 |
    |*650 | CLUSTER TABLE ACCESS | TAB$ | 1 | 13 | | 1 (0)| 00:00:01 |
    |*651 | E SCAN INDEX UNIQU | I_OBJ# | 1 | | | 0 (0)| 00:00:01 |
    |*652 | FILTER | | | | | | |
    | 653 | MERGE JOIN | | 53239 | 2287K| | 1334 (2)| 00:00:06 |
    |*654 | VIEW | TABPARTV$ | 96857 | 3026K| | 872 (2)| 00:00:04 |
    | 655 | WINDOW SORT | | 96857 | 1513K| 2672K| 872 (2)| 00:00:04 |
    | 656 | ULL TABLE ACCESS F | TABPART$ | 96857 | 1513K| | 414 (2)| 00:00:02 |
    |*657 | SORT JOIN | | 273 | 3276 | | 462 (1)| 00:00:02 |
    | 658 | LL TABLE ACCESS FU | NTAB$ | 273 | 3276 | | 461 (1)| 00:00:02 |
    |*659 | FILTER | | | | | | |
    |*660 | FILTERING (UNIQUE) CONNECT BY WITH | | | | | | |
    | 661 | INDEX ROWID TABLE ACCESS BY | NTAB$ | 2 | 16 | | 2 (0)| 00:00:01 |
    |*662 | AN INDEX RANGE SC | I_NTAB1 | 2 | | | 1 (0)| 00:00:01 |
    | 663 | NESTED LOOPS | | 4 | 84 | | 4 (0)| 00:00:01 |
    | 664 | P CONNECT BY PUM | | | | | | |
    | 665 | LUSTER TABLE ACCESS C | NTAB$ | 2 | 16 | | 1 (0)| 00:00:01 |
    |*666 | SCAN INDEX UNIQUE | I_OBJ# | 1 | | | 0 (0)| 00:00:01 |
    |*667 | HASH JOIN | | 1 | 32 | | 5 (20)| 00:00:01 |
    |*668 | TER TABLE ACCESS CLUS | TAB$ | 1 | 13 | | 2 (0)| 00:00:01 |
    |*669 | N INDEX UNIQUE SCA | I_OBJ# | 1 | | | 1 (0)| 00:00:01 |
    |*670 | VIEW | TABPARTV$ | 214 | 4066 | | 2 (0)| 00:00:01 |
    | 671 | WINDOW BUFFER | | 214 | 2140 | | 2 (0)| 00:00:01 |
    |*672 | N INDEX RANGE SCA | I_TABPART_BOPART$ | 214 | 2140 | | 2 (0)| 00:00:01 |
    | 673 | VIEW | | 214 | 1304K| | 1555 (2)| 00:00:07 |
    | 674 | SORT ORDER BY | | 214 | 72546 | | 1555 (2)| 00:00:07 |
    |*675 | HASH JOIN | | 214 | 72546 | | 1554 (2)| 00:00:07 |
    | 676 | TABLE ACCESS FULL | USER$ | 184 | 3496 | | 4 (0)| 00:00:01 |
    | 677 | NESTED LOOPS | | | | | | |
    | 678 | NESTED LOOPS | | 214 | 68480 | | 1549 (2)| 00:00:07 |
    |*679 | HASH JOIN | | 214 | 46866 | | 907 (2)| 00:00:04 |
    |*680 | HASH JOIN | | 214 | 42800 | | 34 (3)| 00:00:01 |
    | 681 | TABLE ACCESS FULL | TS$ | 138 | 3036 | | 26 (0)| 00:00:01 |
    | 682 | NDEX ROWID TABLE ACCESS BY I | TABPART$ | 214 | 38092 | | 7 (0)| 00:00:01 |
    |*683 | INDEX RANGE SCAN | I_TABPART_BOPART$ | 214 | | | 2 (0)| 00:00:01 |
    | 684 | VIEW | TABPARTV$ | 96857 | 1797K| | 872 (2)| 00:00:04 |
    | 685 | WINDOW SORT | | 96857 | 1513K| 2672K| 872 (2)| 00:00:04 |
    | 686 | L TABLE ACCESS FUL | TABPART$ | 96857 | 1513K| | 414 (2)| 00:00:02 |
    |*687 | INDEX RANGE SCAN | I_OBJ1 | 1 | | | 2 (0)| 00:00:01 |
    | 688 | X ROWID TABLE ACCESS BY INDE | OBJ$ | 1 | 101 | | 3 (0)| 00:00:01 |
    | 689 | TABLE ACCESS CLUSTER | USER$ | 1 | 19 | | 1 (0)| 00:00:01 |
    |*690 | INDEX UNIQUE SCAN | I_USER# | 1 | | | 0 (0)| 00:00:01 |
    | 691 | TABLE ACCESS CLUSTER | USER$ | 1 | 19 | | 1 (0)| 00:00:01 |
    |*692 | INDEX UNIQUE SCAN | I_USER# | 1 | | | 0 (0)| 00:00:01 |
    | 693 | R TABLE ACCESS CLUSTE | SEG$ | 1 | 70 | | 3 (0)| 00:00:01 |
    |*694 | INDEX UNIQUE SCAN | I_FILE#_BLOCK# | 1 | | | 2 (0)| 00:00:01 |
    | 695 | DEX ROWID TABLE ACCESS BY IN | DEFERRED_STG$ | 1 | 28 | | 2 (0)| 00:00:01 |
    |*696 | INDEX UNIQUE SCAN | I_DEFERRED_STG1 | 1 | | | 1 (0)| 00:00:01 |
    | 697 | TER TABLE ACCESS CLUS | USER$ | 1 | 19 | | 1 (0)| 00:00:01 |
    |*698 | N INDEX UNIQUE SCA | I_USER# | 1 | | | 0 (0)| 00:00:01 |
    | 699 | NESTED LOOPS | | 1 | 120 | | 5 (0)| 00:00:01 |
    | 700 | INDEX ROWID TABLE ACCESS BY | OBJ$ | 1 | 101 | | 4 (0)| 00:00:01 |
    |*701 | N INDEX RANGE SCA | I_OBJ1 | 1 | | | 3 (0)| 00:00:01 |
    | 702 | STER TABLE ACCESS CLU | USER$ | 1 | 19 | | 1 (0)| 00:00:01 |
    |*703 | AN INDEX UNIQUE SC | I_USER# | 1 | | | 0 (0)| 00:00:01 |
    | 704 | USTER TABLE ACCESS CL | SEG$ | 1 | 70 | | 3 (0)| 00:00:01 |
    |*705 | CAN INDEX UNIQUE S | I_FILE#_BLOCK# | 1 | | | 2 (0)| 00:00:01 |
    | 706 | Y INDEX ROWID TABLE ACCESS B | DEFERRED_STG$ | 1 | 28 | | 2 (0)| 00:00:01 |
    |*707 | SCAN INDEX UNIQUE | I_DEFERRED_STG1 | 1 | | | 1 (0)| 00:00:01 |
    | 708 | CLUSTER TABLE ACCESS | TS$ | 1 | 18 | | 1 (0)| 00:00:01 |
    |*709 | SCAN INDEX UNIQUE | I_TS# | 1 | | | 0 (0)| 00:00:01 |
    | 710 | CLUSTER TABLE ACCESS | TS$ | 1 | 8 | | 1 (0)| 00:00:01 |
    |*711 | E SCAN INDEX UNIQU | I_TS# | 1 | | | 0 (0)| 00:00:01 |
    | 712 | S CLUSTER TABLE ACCES | USER$ | 1 | 19 | | 1 (0)| 00:00:01 |
    |*713 | UE SCAN INDEX UNIQ | I_USER# | 1 | | | 0 (0)| 00:00:01 |
    | 714 | SS CLUSTER TABLE ACCE | SEG$ | 1 | 70 | | 3 (0)| 00:00:01 |
    |*715 | QUE SCAN INDEX UNI | I_FILE#_BLOCK# | 1 | | | 2 (0)| 00:00:01 |
    | 716 | ESS BY INDEX ROWID TABLE ACC | DEFERRED_STG$ | 1 | 28 | | 2 (0)| 00:00:01 |
    |*717 | IQUE SCAN INDEX UN | I_DEFERRED_STG1 | 1 | | | 1 (0)| 00:00:01 |
    | 718 | S NESTED LOOP | | 1 | 421 | | 2864 (1)| 00:00:13 |
    | 719 | PS NESTED LOO | | 1 | 402 | | 2863 (1)| 00:00:13 |
    | 720 | N MERGE JOI | | 1 | 380 | | 2862 (1)| 00:00:13 |
    |*721 | VIEW | INDSUBPARTV$ | 203K| 54M| | 2857 (1)| 00:00:13 |
    | 722 | BUFFER WINDOW | | 203K| 13M| | 2857 (1)| 00:00:13 |
    | 723 | ACCESS BY INDEX ROWID TABLE | INDSUBPART$ | 203K| 13M| | 2857 (1)| 00:00:13 |
    | 724 | FULL SCAN INDEX | I_INDSUBPART_POBJSUBPART$ | 203K| | | 517 (1)| 00:00:03 |
    |*725 | N SORT JOI | | 1 | 101 | | 5 (20)| 00:00:01 |
    | 726 | CCESS BY INDEX ROWID TABLE A | OBJ$ | 1 | 101 | | 4 (0)| 00:00:01 |
    |*727 | RANGE SCAN INDEX | I_OBJ1 | 1 | | | 3 (0)| 00:00:01 |
    | 728 | ESS CLUSTER TABLE ACC | TS$ | 1 | 22 | | 1 (0)| 00:00:01 |
    |*729 | IQUE SCAN INDEX UN | I_TS# | 1 | | | 0 (0)| 00:00:01 |
    | 730 | SS CLUSTER TABLE ACCE | USER$ | 1 | 19 | | 1 (0)| 00:00:01 |
    |*731 | QUE SCAN INDEX UNI | I_USER# | 1 | | | 0 (0)| 00:00:01 |
    | 732 | VIEW | | 3220 | 6653K| | 252 (2)| 00:00:02 |
    | 733 | SORT ORDER BY | | 3220 | 679K| | 252 (2)| 00:00:02 |
    |*734 | HASH JOIN | | 3220 | 679K| | 251 (1)| 00:00:02 |
    | 735 | NESTED LOOPS | | | | | | |
    | 736 | NESTED LOOPS | | 12 | 336 | | 14 (0)| 00:00:01 |
    | 737 | FULL TABLE ACCESS | LOBCOMPPART$ | 12 | 144 | | 2 (0)| 00:00:01 |
    |*738 | SCAN INDEX UNIQUE | I_LOB2 | 1 | | | 0 (0)| 00:00:01 |
    | 739 | BY INDEX ROWID TABLE ACCESS | LOB$ | 1 | 16 | | 1 (0)| 00:00:01 |
    |*740 | VIEW | LOBFRAGV$ | 19858 | 3645K| | 236 (1)| 00:00:01 |
    | 741 | WINDOW BUFFER | | 19858 | 1066K| | 236 (1)| 00:00:01 |
    | 742 | BY INDEX ROWID TABLE ACCESS | LOBFRAG$ | 19858 | 1066K| | 236 (1)| 00:00:01 |
    | 743 | SCAN INDEX FULL | I_LOBFRAG_PARENTOBJFRAG$ | 19858 | | | 61 (0)| 00:00:01 |
    | 744 | Y INDEX ROWID TABLE ACCESS B | TABSUBPART$ | 1 | 111 | | 3 (0)| 00:00:01 |
    |*745 | SCAN INDEX UNIQUE | I_TABSUBPART$_OBJ$ | 1 | | | 2 (0)| 00:00:01 |
    | 746 | VIEW | | 418K| 2477M| | 38130 (1)| 00:02:41 |
    | 747 | SORT ORDER BY | | 418K| 177M| 192M| 38130 (1)| 00:02:41 |
    |*748 | HASH JOIN | | 418K| 177M| | 3590 (3)| 00:00:16 |
    | 749 | TABLE ACCESS FULL | USER$ | 184 | 3496 | | 4 (0)| 00:00:01 |
    |*750 | HASH JOIN | | 418K| 170M| | 3582 (2)| 00:00:16 |
    | 751 | L TABLE ACCESS FUL | TS$ | 138 | 3036 | | 26 (0)| 00:00:01 |
    |*752 | HASH JOIN | | 418K| 161M| | 3552 (2)| 00:00:15 |
    | 753 | VIEW | TABSUBPARTV$ | 30 | 9120 | | 4 (0)| 00:00:01 |
    | 754 | WINDOW BUFFER | | 30 | 3750 | | 4 (0)| 00:00:01 |
    | 755 | BY INDEX ROWID TABLE ACCESS | TABSUBPART$ | 30 | 3750 | | 4 (0)| 00:00:01 |
    |*756 | SCAN INDEX RANGE | I_TABSUBPART_POBJSUBPART$ | 30 | | | 3 (0)| 00:00:01 |
    | 757 | LL TABLE ACCESS FU | OBJ$ | 825K| 79M| | 3539 (2)| 00:00:15 |
    | 758 | NDEX ROWID TABLE ACCESS BY I | LOB$ | 1 | 10 | | 2 (0)| 00:00:01 |
    |*759 | N INDEX UNIQUE SCA | I_LOB2 | 1 | | | 1 (0)| 00:00:01 |
    | 760 | STER TABLE ACCESS CLU | USER$ | 1 | 19 | | 1 (0)| 00:00:01 |
    |*761 | AN INDEX UNIQUE SC | I_USER# | 1 | | | 0 (0)| 00:00:01 |
    | 762 | NESTED LOOPS | | 1 | 120 | | 5 (0)| 00:00:01 |
    | 763 | INDEX ROWID TABLE ACCESS BY | OBJ$ | 1 | 101 | | 4 (0)| 00:00:01 |
    |*764 | AN INDEX RANGE SC | I_OBJ1 | 1 | | | 3 (0)| 00:00:01 |

  • Replacing "" from scripts which has table DDLs

    HI,
    I use an oracle version of Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production.
    I have few scripts consisting of DDLs for table. But  almost all CREATE TABLE syntax  consist of double quotes "" for the column name and table name like below example:
    After architecture review, we came to know that we need to remove all the double quotes from all scripts for column names and table names making sure other double quote usage are not impacted in any part of those scripts. But doing it manually by going through all scripts/tables seems to be huge effort. So am seeking suggestion if there is any way we can achieve this in a simpler way.
    Thanks

    After architecture review, we came to know that we need to remove all the double quotes from all scripts for column names and table names making sure other double quote usage are not impacted in any part of those scripts. But doing it manually by going through all scripts/tables seems to be huge effort. So am seeking suggestion if there is any way we can achieve this in a simpler way.
    Yes, there are at least two much simpler ways:
    1. Replace the architecture review team with people who use logic and reason as the basis for the standards that they adopt.
    2. Replace the 'remove all the double quotes' requirement from the standards list.
    If you plan to adopt a standard then you should adopt an industry standard. If you use any other standard then there should not only be a rational justification for NOT using the industry standard (in this case Oracle's) but there should also be some rational, and demonstrable, value to the standard that you adopt. I cannot think of any justification for NOT using the Oracle standard not am I aware of any value whatsoever to removing all double quotes from scripts.
    In addition, in almost 30 years of working in the field I am not aware of ANY organization that has adopted such a standard.
    Oracle both provides, and uses, extensive functionality for creating and using DDL. The DBMS_METADATA package is used by Oracle for both export and import and the standard used by that package is to enclose object names in double quotes. The reasons for this standard have already been stated by others. One example is the possible use of mixed-case for object names. But mixed-case is also used for path names in DIRECTORY objects, TABLESPACE objects, database links and for extracted passwords.
    Any extraction of DDL your org does will likely etiher use the DBMS_METADATA package or a tool that follows the Oracle standard.
    So your teams 'standard' not only contravenes the industry standard but imparts a substantial penalty in terms of the resources needed to constantly identify and correct the any DDL extracted from your systems.
    Here is a trivial example of using the Oracle package to extract DDL for the SCOTT.EMP table.
    select dbms_metadata.get_ddl('TABLE', 'EMP', 'SCOTT') from dual
    CREATE TABLE "SCOTT"."EMP"
    ( "EMPNO" NUMBER(4,0),
    "ENAME" VARCHAR2(10),
    "JOB" VARCHAR2(9),
    "MGR" NUMBER(4,0),
    "HIREDATE" DATE,
    "SAL" NUMBER(7,2),
    "COMM" NUMBER(7,2),
    "DEPTNO" NUMBER(2,0),
    CONSTRAINT "PK_EMP" PRIMARY KEY ("EMPNO")
    USING INDEX PCTFREE 10 INITRANS 2 MAXTRANS 255 COMPUTE STATISTICS
    STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
    PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT)
    TABLESPACE "USERS" ENABLE,
    CONSTRAINT "FK_DEPTNO" FOREIGN KEY ("DEPTNO")
    REFERENCES "SCOTT"."DEPT" ("DEPTNO") ENABLE
    ) SEGMENT CREATION IMMEDIATE
    PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 NOCOMPRESS LOGGING
    STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
    PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT)
    TABLESPACE "USERS"
    If this were me I would use ALL of my political capital to fight the battle against this non-sensical 'standard'. There is simply no rhyme or reason for it, it will waste a lot of valuable personal resources and the cost/benefit ratio simply can't justify it.
    Those resources would be MUCH better used on other tasks.

  • I am trying to download a document which has an adobe symbol in the corner and all I get is a blackX

    See the subject line

    That Download button, is this a direct link to the PDF?  If so, right-click on it, then select Save Target as...
    If you want to view the PDF in the browser (which is?), see http://helpx.adobe.com/acrobat/kb/cant-view-pdf-web.html

  • Accessing  table type from JAVA

    Hi Experts,
    We are making a custom copy of the std FM COM_BPUS_ORG_CONTPERS_REGISTER .
    It is observed that Tables are obsolete and we should not use them in custom function modules.
    I can pass a table type in import parameter and export parameter.
    Can we access a table type from java layer.
    Also, note that this STANDARD function module has parameter IT_BUSINESSPARTNERROLE_ORG which has table type BU_ROLE_T.
    Is it possible to access this?
    Note:- This Function module is not getting called in standard web shops.
    Please let me now how i can access this table type for hava while calling FM so as to input or retrieve valus from it.
    Regards
    Antony

    The issue with you is more than accessing a table type.
    You said:
    This Function module is not getting called in standard web shops.
    For function modules that are not called as a part of the standard flow, you have to develop your own simple BOM, BO, BEI, BE classes and methods to call the custom RFC - the whole nine yards. See the extension guide and see the Extension Demos 2 and 3 for reference.
    See the sample JCO calls from Java to understand how to access the table types.

  • To select table which has TAB as data column with in

    Hi All
    I have a table which has column type defined as TAB type. When I try selecting the table in PL/SQL developer, I got below error.
    What should I do? Even SQL* Plus shows the same error!
    SQL> select *
      2  from my_tab_cap
      3  /
    from my_tab_cap
    ERROR at line 2:
    ORA-00904: : invalid identifierThanks in advance.
    Message was edited by:
    guru paran
    Changed the table name.

    You probably want to help us out with all your ddl:
    create table tab2 (my_tab_col my_type ) nested table my_tab_col store as my_tab;
    create type my_type as table of varchar2(100);
    declare
    v_type my_type := my_type();
    begin
    v_type.extend(4);
    v_type(1) := 'I like table types1';
    v_type(2) := 'I like table types2';
    v_type(3) := 'I like table types3';
    v_type(4) := 'I like table types4';
    insert into tab2(my_tab_col) values (v_type);
    end;
    select * from tab2;
    MY_TAB_COL                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      
    VARCHAR(I like table types1,I like table types2,I like table types3,I like table types4)     

  • File Adapter not processing Files which has COMMA in it

    Hi Experts,
    I am working on Project in SOA 11.1.1.6.
    I am trying to process a file which has comma in it. for eg - XXXXXXX-XX_XX_XXX11,99.pdf
    I am picking the file using file adapter from SOURCE directory and using another file adapter to WRITE to destination directory. Polling processing is working fine.
    I am picking the file from SOURCE directory as ATTACHMENT and WRITING to DESTINATION folder through File Adapter
    While doing file WRITE its failing. While reading the file the values of Content Type, Character Set and Encoding are NULL for the ATTACHMENT as they are optional properties.
    The error I am getting while File WRITE is
    <remoteFault>
    <part name="summary">
    <summary>java.lang.RuntimeException: Failed to decode properties string att.encoding=null,att.charset=null,att.contentId=AReadFile/XXXXXXXX_XX_XXX11,99.pdf_1352184009640,att.contentType=null,att.partName=attach</summary>
    </part>
    <part name="detail">
    <detail>1</detail>
    </part>
    </remoteFault>

    Comma is usually treated as a separator/delimiter and hence it is not really common to have comma in filename. I think because of this reason File adapter does not support it (have to cross-verify). If you really have a requirement to read/write files with comma in filename then better log a SR with Oracle support.
    Regards,
    Anuj

Maybe you are looking for

  • Safari cannot open pages, but firefox can.

    My daughters Mac Mini has started strange behaviour. Safari will not open most websites (says it can't connect), but Firefox can. This includes sites such as Google and Yahoo, that open on Safari on the other Macs in our home. Network diagnostics say

  • Toast Servo Failure

    Ok. So I have a unibody macbook pro and Toast 10 and suddenly a few months ago it will not burn a dual layer dvd. I've spent a lot of time with the Genius teams in my area and we cannot figure out why I constantly get a "Spindle Servo Error". First,

  • Line break problem

    Hi all, line breaks that i'm giving in text area's text are not been showed by JSP's simple function recordset.getObject(). for instance, if u know PHP...i want a function that perform task similar to nl2br(); desperately waiting for replies. Regards

  • What are the different ways in accessing the SQL server from NWDS ?

    Hi Experts, Can anyone suggest the different ways for accessing the SQL server from NWDS.I also want to know whether any tool is available for accessing SQL server from Webdynpro java application in Netweaver development studio. I am currently using

  • Photoshop Elements Editor (8.0)

    I purchased a Wacom Bamboo about 2 years, which came with a CD of Photoshop 8.0. I now installed it in my laptop and wanted to start editing. The problem is, whenever I try to click the edit button, it shows up: "Could not open a scratch file because