ORA-00932: inconsistent datatypes: expected - got -

Question

Hi,
I have writen PL/SQL packages for data loging through pipe lined function for better peformance.The below packages has been compiled sucessfully but during the run time it shows an error
like "ORA-00932: inconsistent datatypes: expected - got -".
CREATE OR REPLACE PACKAGE pkg_mkt_hub_load
AS
     PROCEDURE sp_final_load_mkt_hub;
       FUNCTION fnc_pipe_tot_lvl_idx_mon_hub
    (pi_input_cur IN SYS_REFCURSOR)
   RETURN tot_lvl_idx_mon_tt
   PIPELINED;
END pkg_mkt_hub_load;
CREATE OR REPLACE PACKAGE BODY pkg_mkt_hub_load
AS
  c_default_limit CONSTANT PLS_INTEGER:=5000;
  c_created_dt    CONSTANT DATE:=SYSDATE;
  c_created_user  CONSTANT VARCHAR2(20):='SYSTEM';
  c_updated_dt    CONSTANT DATE:=SYSDATE;
  c_updated_user  CONSTANT VARCHAR2(20):='SYSTEM';
  -- to get the debug desc for updating process log table
  vg_debug_log_desc mkt_process_log.debug_log_desc%TYPE;
  --to get process log key
  vg_process_log_ky mkt_process_log.process_log_ky%TYPE;
   -- reset the all variables.
  PROCEDURE sp_reset_global_variables;
  PROCEDURE sp_final_lvl_idx_mon_hub;
  --PROCEDURE sp_final_lvl_idx_dly_hub;
  FUNCTION fnc_pipe_tot_lvl_idx_mon_hub
    (pi_input_cur IN SYS_REFCURSOR)
   RETURN tot_lvl_idx_mon_tt
   PIPELINED
  AS
   vl_lvl_idx_mon_cur_data tot_lvl_idx_mon_tt;
   BEGIN
     LOOP
      FETCH pi_input_cur BULK COLLECT INTO vl_lvl_idx_mon_cur_data LIMIT c_default_limit;
      EXIT WHEN vl_lvl_idx_mon_cur_data.COUNT = 0;
      FOR i IN 1 .. vl_lvl_idx_mon_cur_data.COUNT
      LOOP
        PIPE ROW (tot_lvl_idx_mon_ot(vl_lvl_idx_mon_cur_data(i).SSIA_INDEX_ID,
        vl_lvl_idx_mon_cur_data(i).start_date,vl_lvl_idx_mon_cur_data(i).currency,
      vl_lvl_idx_mon_cur_data(i).level1,vl_lvl_idx_mon_cur_data(i).type,
      vl_lvl_idx_mon_cur_data(i).RETURN_MONTH,vl_lvl_idx_mon_cur_data(i).RETURN_3MONTHS,
      vl_lvl_idx_mon_cur_data(i).RETURN_6MONTHS,vl_lvl_idx_mon_cur_data(i).RETURN_YTD,
      vl_lvl_idx_mon_cur_data(i).RETURN_1YEAR,vl_lvl_idx_mon_cur_data(i).RETURN_3YEARS,
      vl_lvl_idx_mon_cur_data(i).RETURN_5YEARS,vl_lvl_idx_mon_cur_data(i).RETURN_10YEARS,
      vl_lvl_idx_mon_cur_data(i).MARKET_CAP));
      END LOOP;
      END LOOP;
      CLOSE pi_input_cur;
      RETURN;
   END fnc_pipe_tot_lvl_idx_mon_hub;     
   PROCEDURE sp_final_lvl_idx_mon_hub
   AS
   BEGIN
   MERGE INTO mkt_total_lvl_indx_mon_hub idxhub  
   USING TABLE(pkg_mkt_hub_load.fnc_pipe_tot_lvl_idx_mon_hub(CURSOR(SELECT idxmap.ssia_index_code,idxstg.start_date,idxstg.currency,idxstg.level1,idxstg.type,
       idxstg.return_month,idxstg.return_3months, idxstg.return_6months, idxstg.return_ytd, idxstg.return_1year,
       idxstg.return_3years, idxstg.return_5years,idxstg.return_10years,idxstg.market_cap
     FROM   mkt_total_lvl_indx_mon_stg idxstg,
             md_vendor_index_map idxmap
     WHERE  idxmap.source = idxstg.source
             AND idxmap.base_currency = idxstg.currency
             AND idxmap.return_type = idxstg.TYPE
             AND idxmap.mkt_index_id = idxstg.vendor_code
             AND idxmap.monthly = 'Y'
             AND idxmap.file_type = 'T'))) idxmonstg
     ON (idxhub.ssia_index_id=idxmonstg.ssia_index_id)
     WHEN MATCHED THEN
     UPDATE set effective_date=idxmonstg.start_date,
                  CURRENCY=idxmonstg.currency,
                  INDEX_LEVEL=idxmonstg.LEVEL1,
                  TYPE=idxmonstg.type,
                  return_month=idxmonstg.return_month,
                  return_3months=idxmonstg.return_3months,
                  return_6months=idxmonstg.return_6months,
                  return_ytd=idxmonstg.return_ytd,
                  return_1year=idxmonstg.return_1year,
                  return_3years=idxmonstg.return_3years,
                  return_5years=idxmonstg.return_5years,
                  return_10years=idxmonstg.return_10years,
                  market_cap=idxmonstg.market_cap,
                  updated_dt=SYSDATE,
                  updated_user='MICHAEL'
     WHEN NOT MATCHED THEN
      INSERT (  ssia_index_id,
                effective_date,
                  currency,
                  INDEX_LEVEL,
                  TYPE,
                  return_month,
                  return_3months,
                  return_6months,
                  return_ytd,
                  return_1year,
                  return_3years,
                  return_5years,
                  return_10years,
                  market_cap,
                  created_dt,
                  created_user)
     VALUES(        idxmonstg.ssia_index_id,
                  idxmonstg.start_date,
                  idxmonstg.currency,
                  idxmonstg.LEVEL1,
                  idxmonstg.type,
                  idxmonstg.return_month,
                  idxmonstg.return_3months,
                  idxmonstg.return_6months,
                  idxmonstg.return_ytd,
                  idxmonstg.return_1year,
                  idxmonstg.return_3years,
                  idxmonstg.return_5years,
                  idxmonstg.return_10years,
                  idxmonstg.market_cap,
               SYSDATE,
               'MICHAEL');     
   END sp_final_lvl_idx_mon_hub;
   PROCEDURE sp_final_load_mkt_hub
   as
   BEGIN
    sp_final_lvl_idx_mon_hub;
   END sp_final_load_mkt_hub;
   PROCEDURE Sp_reset_global_variables
   AS
   BEGIN
   vg_debug_log_desc := NULL;
   END sp_reset_global_variables;      
END pkg_mkt_hub_load;
SHOW ERRORS  Error:
ERROR at line 1:
ORA-00932: inconsistent datatypes: expected - got -
ORA-06512: at "GPAIHMKTDTA.PKG_MKT_HUB_LOAD", line 33
ORA-06512: at "GPAIHMKTDTA.PKG_MKT_HUB_LOAD", line 55
ORA-06512: at "GPAIHMKTDTA.PKG_MKT_HUB_LOAD", line 92
ORA-06512: at line 1
types scripts:
create or replace type tot_lvl_idx_mon_ot as object
(SSIA_INDEX_ID  VARCHAR2(60),
start_date date,
CURRENCY               VARCHAR2(10),
LEVEL1                  NUMBER(31,11),
TYPE                    VARCHAR2(31) ,
RETURN_MONTH            NUMBER(31,11),
RETURN_3MONTHS          NUMBER(31,11),
RETURN_6MONTHS          NUMBER(31,11),
RETURN_YTD              NUMBER(31,11),
RETURN_1YEAR            NUMBER(31,11),
RETURN_3YEARS           NUMBER(31,11),
RETURN_5YEARS           NUMBER(31,11),
RETURN_10YEARS          NUMBER(31,11),
MARKET_CAP              NUMBER(31,11));
create or replace type tot_lvl_idx_mon_tt is table of tot_lvl_idx_mon_ot;how to resolve this issue?

Answer 1

>
could you please pointed out whether ref cursor used method correct or not?
>
The use looks correct but without your tables and DDL we can't even try to reproduce the problem.
Notice how you had to break down the process to find out the query that is causing the problem?
select *
from TABLE(pkg_mkt_hub_load.fnc_pipe_tot_lvl_idx_mon_hub(CURSOR(SELECT . . .Unfortunately, this is where you should have started when you began creating the process.
You are trying to design, implement and debug a process using code that has 3,4, 5 or more layers and objects and tables that have a dozen or more columns.
That is not the way I would recommend especially if you do not have experience with some of the pieces like object types and tables, pipelined functions and ref cursors. You are trying to deal with too many complications at the same time.
Here is how I would approach this if I were you.
1. Get the process to work first and then build on it. Start by copying and hacking up what you already have.
2. Create a very simple version of each of the pieces
3. Create an object type like 'tot_lvl_idx_mon_ot' with only one or two columns.
4. Create an object type like 'tot_lvl_idx_mon_tt' as a table of that simple object type
5. Create a pipelined function that uses the two new simple types, simply hard-codes a value for one or two rows and then pipes out the rows.
6. Use a simple query like the last one you posted to query the simple pipelined function
select *
from TABLE(pkg_mkt_hub_load.simpe_pipeline_function(CURSOR(SELECT . . .Work on that simple set of objects until you have the process defined and working.
Then expand the now working example to use get the data values dynamically and to use more complicated objects.
Start with something simple that works. Then build on it.
It will take a lot less time and will point out other issues with your approach to this. Also, if you try a simple version using the SCOTT emp or dept table and it doesn't work you can post the code and we can try to reproduce it and help find the problem.