Function issue: inconsistent datatypes?

Question

Hi all.
I'm having an issue with a function that converts coordinates to a spatial data type.
My database version is:
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - Production
PL/SQL Release 11.2.0.2.0 - Production
CORE     11.2.0.2.0     Production
TNS for Linux: Version 11.2.0.2.0 - Production
NLSRTL Version 11.2.0.2.0 - Production
Here's my package that I'm using
create or replace package make_geometry
as
            function get_geometry_from_coords (p_coords in clob  )
          return sdo_geometry;
end;
create or replace package body make_geometry
as
          function get_geometry_from_coords (p_coords in clob)
          return sdo_geometry
          is
             v_geometry sdo_geometry;
          begin
             --with t as (select p_coords coords from dual)
          select MDSYS.SDO_GEOMETRY(2003,8307,NULL,MDSYS.SDO_ELEM_INFO_ARRAY(1,1003,1)
                              ,cast(multiset(
                                  select ordset
                                 from (
                                        select regexp_substr( regexp_replace(
                                                                            replace(p_coords,chr(10))
                                                                             ,' {1,}',',')
                                                              ,'[^,]+',1,level)  ordset
                                              ,rownum rn
                                          from dual
                                                           connect by level <= length(regexp_replace(regexp_replace(
                                                                                               replace(p_coords,chr(10))
                                                                                               ,' {1,}',','),'[^,]+')) + 1
                                        where mod(rn,3) <> 0
                    ) as sdo_ordinate_array))
              into v_geometry
              from dual;
              return v_geometry;
          end;
end;
/basically, it takes a list of coordinates, in the following format:
with t as (select '130.88214073599997,-12.377589935499998,0 130.88189276799997,-12.378437734999997,0 130.88164895999998,-12.379271400499997,0 ' coords from dual)replaces the spaces with commas and splits the resultant string by comma, then removes the third coordinate in each set (sets delimited by spaces in above example) and converts the result to sdo_geometry type.
This logic is not where my problem is occurring
If I run the query found in the package separately, it works fine:
SQL> with t as (select '130.88214073599997,-12.377589935499998,0 130.88189276799997,-12.378437734999997,0 130.88164895999998,
-12.379271400499997,0 ' coords from dual)
  2            select MDSYS.SDO_GEOMETRY(2003,8307,NULL,MDSYS.SDO_ELEM_INFO_ARRAY(1,1003,1)
  3                                ,cast(multiset(
  4                                    select ordset
  5                                   from (
  6                                          select regexp_substr( regexp_replace(
  7                                                                              replace(coords,chr(10))
  8                                                                               ,' {1,}',',')
  9                                                                ,'[^,]+',1,level)  ordset
10                                                ,rownum rn
11                                            from t
12                                                             connect by level <= length(regexp_replace(regexp_replace(
13                                                                                                 replace(coords,chr(10))
14                                                                                                 ,' {1,}',','),'[^,]+')) +
1
15                                                               )
16                                          where mod(rn,3) <> 0
17                      ) as sdo_ordinate_array))
18                from dual;
MDSYS.SDO_GEOMETRY(2003,8307,NULL,MDSYS.SDO_ELEM_INFO_ARRAY(1,1003,1),CAST(MULTISET(SELECTORDSETFROM(SELECTREGEXP_SUBSTR(REGE
XP_REPL
SDO_GEOMETRY(2003, 8307, NULL, SDO_ELEM_INFO_ARRAY(1, 1003, 1), SDO_ORDINATE_ARRAY(130.882141, -12.37759, 130.881893, -12.378
438, 13
0.881649, -12.379271, NULL))but if I call the function:
SQL> with t as (select '130.88214073599997,-12.377589935499998,0 130.88189276799997,-12.378
-12.379271400499997,0 ' coords from dual)
  2  select make_geometry.get_geometry_from_coords(coords)
  3    from t;
select make_geometry.get_geometry_from_coords(coords)
ERROR at line 2:
ORA-00932: inconsistent datatypes: expected NUMBER got CLOB
ORA-06512: at "HR.MAKE_GEOMETRY", line 13If I change the package to expect varchar2 the above example coordinate list works fine, but obviously that doesn't work when the coordinate list exceeds 4000 characters.
any thoughts?

Answer 1

not sure that is the problem:
SQL> create table foo (mr_clob clob);
Table created.
SQL>
SQL> insert into foo values ('testing'||chr(10)||'testing');
1 row created.
SQL>
SQL> select replace(mr_clob,chr(10),'blah') from foo;
REPLACE(MR_CLOB,CHR(10),'BLAH')
testingblahtesting
1 row selected.