Skip to Main Content

Java Development Tools

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

JDeveloper Connection closed.

Usman KpJun 20 2022

Hi, I am using Oracle JDeveloper 12.2.1.3.0 with database 19C . I am facing one big issue which is making our development of ADF forms very slow. When Ever we made connection with 19C db within ADF application , connection builds successfully . Issue happens when I try to create Entity Object ( via wizard or from Making Components from Tables ) , modify entity object definition like adding or removing one db column or updating View Object Mappings . JDeveloper stucks and I have to either stop wizards or restart Jdeveloper . Whenever I try to do above all operations with same application using 12C database ( on another server). JDeveloper runs smoothly. I tried connecting with APPS, and other schemas even with sysdba roles but issue is still persistent . Whenever JDeveloper is stuck it only gives messages in Logs like this .

Jun 20, 2022 2:06:23 PM oracle.javatools.db.execute.StatementWrapper cancel
WARNING: Error cancelling statement:IO Error
Jun 20, 2022 2:06:23 PM oracle.javatools.db.AbstractBuildableObject$BuildablePropertySupport logBuildCancelled
WARNING: Building of columns on TABLE PWC_MFG_PRECOSTING_L was cancelled.
Jun 20, 2022 2:06:23 PM oracle.javatools.db.execute.ConnectionWrapper call
INFO: ProgressBarThread: The connection to database Conn1 is closed.
Jun 20, 2022 2:06:23 PM oracle.javatools.db.AbstractDatabase getConnection
INFO: ProgressBarThreadConnection was closed, Conn1 has been reconnected.
Jun 20, 2022 2:06:37 PM oracle.javatools.db.execute.StatementWrapper cancel

Issue is that 19C DB is up and running all the time and TOAD is being connected while JDeveloper hangs out ( so it kills possibility that DB might be down) . Also there isn't much users so there isn't much load on DB also .

What is the cause of this issue and what can be its solution . I have around 20 applications of ADF and I face issue in all . I have to first make connection with 12C database , build my application and then migrate all DB objects in 19C database.

One more thing is that if I runs module tester and save some transactions , it not only runs smoothly but also stores data in database. JDeveloper only stucks when I am making new Entity Object or modifying existing EO or VO definitions .

This post has been answered by Timo Hahn on Jun 22 2022
Jump to Answer

Comments

Mike Kutz

Custom Aggregate functions are implemented via Oracle Data Cartridge Interface (ODCI).
They're UDTs that have a specific set of functions. (ODCIAggregate)
User-Defined Aggregate Functions Interface (0 Bytes)

Solomon Yakobson

Not exactly sure what you need:

with vertices as (
                  select '001' line_id,1 part_num,1 vertex_num,0 x,5 y,0 m from dual union all
                  select '001',1,2,10,10,11.18 from dual union all
                  select '001',1,3,30,0,33.54 from dual union all
                  select '001',2,1,50,10,33.54 from dual union all
                  select '001',2,2,60,10,43.54 from dual
                 ),
           t1 as (
                  select  line_id,
                          part_num,
                          vertex_num,
                          x x_from,
                          y y_from,
                          count(*) over(partition by line_id,part_num) cnt,
                          lead(x) over(partition by line_id,part_num order by vertex_num) x_to,
                          lead(y) over(partition by line_id,part_num order by vertex_num) y_to
                    from  vertices
                 ),
           t2 as (
                  select  line_id,
                          part_num,
                          vertex_num,
                          sdo_geometry(
                                       2002,
                                       null,
                                       null,
                                       sdo_elem_info_array(1,2,1),
                                       sdo_ordinate_array(x_from,y_from,x_to,y_to)
                                      ) section
                    from  t1
                    where vertex_num < cnt
                 )
select  line_id,
        part_num,
        sdo_aggr_concat_lines(section) line
  from  t2
  group by line_id,
           part_num
  order by line_id,
           part_num
/

LINE_ID   PART_NUM LINE(SDO_GTYPE, SDO_SRID, SDO_POINT(X, Y, Z), SDO_ELEM_INFO, SDO_ORDINATES)
------- ---------- -----------------------------------------------------------------------------------------------------
001              1 SDO_GEOMETRY(2002, NULL, NULL, SDO_ELEM_INFO_ARRAY(1, 2, 1), SDO_ORDINATE_ARRAY(0, 5, 10, 10, 30, 0))
001              2 SDO_GEOMETRY(2002, NULL, NULL, SDO_ELEM_INFO_ARRAY(1, 2, 1), SDO_ORDINATE_ARRAY(50, 10, 60, 10))

SQL>

SY.

_jum

Another approach:

WITH vertices (line_id,part_num,vertex_num,x,y,m) AS 
 (SELECT '001',1,1, 0, 5,   0 FROM dual UNION ALL
  SELECT '001',1,2,10,10,11.18 FROM dual UNION ALL
  SELECT '001',1,3,30, 0,33.54 FROM dual UNION ALL
  SELECT '001',2,1,50,10,33.54 FROM dual UNION ALL
  SELECT '001',2,2,60,10,43.54 FROM dual),
 t1 AS                     
 (SELECT x coord, line_id, part_num, vertex_num FROM vertices
    UNION ALL          
  SELECT y     , line_id, part_num, vertex_num FROM vertices)
 SELECT line_id, part_num
      , sdo_geometry(2002, NULL, NULL
        , sdo_elem_info_array(1,2,1)
        , CAST(collect (coord ORDER BY line_id, part_num, vertex_num) AS sdo_ordinate_array)) line
  FROM t1            
 GROUP BY line_id, part_num;


LINE_ID   PART_NUM LINE(SDO_GTYPE, SDO_SRID, SDO_POINT(X, Y, Z), SDO_ELEM_INFO, SDO_ORDINATES)
------- ---------- -----------------------------------------------------------------------------------------------------
001              1 SDO_GEOMETRY(2002, NULL, NULL, SDO_ELEM_INFO_ARRAY(1, 2, 1), SDO_ORDINATE_ARRAY(0, 5, 10, 10, 30, 0))
001              2 SDO_GEOMETRY(2002, NULL, NULL, SDO_ELEM_INFO_ARRAY(1, 2, 1), SDO_ORDINATE_ARRAY(50, 10, 60, 10))
User_1871

@jum3
Thanks! Does that approach assume that we'd need to do an additional step afterwards: merge the two single-part geometries into a multi-part geometry?

_jum

Yes, with an additional merge step, based on an adapted and extended (for M) approach of @SY or mine. The present draft was ready
This collapse is certainly possible in one very smart step...

Solomon Yakobson

@_jum: Another approach:
Careful, you need to weigh X & Y, othersise you get non-deterministic results and Y can end up first:

WITH vertices (line_id,part_num,vertex_num,x,y,m) AS 
 (SELECT '001',1,1, 0, 5,   0 FROM dual UNION ALL
  SELECT '001',1,2,10,10,11.18 FROM dual UNION ALL
  SELECT '001',1,3,30, 0,33.54 FROM dual UNION ALL
  SELECT '001',2,1,50,10,33.54 FROM dual UNION ALL
  SELECT '001',2,2,60,10,43.54 FROM dual),
 t1 AS                     
 (SELECT x coord, line_id, part_num, vertex_num, 1 weight FROM vertices
    UNION ALL          
  SELECT y     , line_id, part_num, vertex_num,2 weight FROM vertices)
 SELECT line_id, part_num
      , sdo_geometry(2002, NULL, NULL
        , sdo_elem_info_array(1,2,1)
        , CAST(collect (coord ORDER BY line_id, part_num, vertex_num,weight) AS sdo_ordinate_array)) line
  FROM t1            
 GROUP BY line_id, part_num;

SY.

_jum

Of course, I need a break - Thanks @Solomon Yakobson!

User_1871

@jum3
This collapse is certainly possible in one very smart step...
What's the smart step for merging?

_jum

I honestly have no idea currently!

_jum

Last step could be:

SELECT sdo_geom.sdo_union(
       SDO_GEOMETRY(3002, NULL, NULL, SDO_ELEM_INFO_ARRAY(1, 2, 1), SDO_ORDINATE_ARRAY(0, 5, 0, 10, 10, 11.18, 30, 0, 33.54))
     , SDO_GEOMETRY(3002, NULL, NULL, SDO_ELEM_INFO_ARRAY(1, 2, 1), SDO_ORDINATE_ARRAY(50, 10, 33.54, 60, 10, 43.54))
     , 0.01) ugeom
 FROM dual; 

UGEOM
---------------------------------
MDSYS.SDO_GEOMETRY(3006, NULL, NULL
      , MDSYS.SDO_ELEM_INFO_ARRAY(1, 2, 1, 10, 2, 1)
      , MDSYS.SDO_ORDINATE_ARRAY(0, 5, 0, 10, 10, 11.18, 30, 0, 33.54, 50, 10, 33.54, 60, 10, 43.54))

odie_63

Isn't it just a matter of CONCAT them together?

WITH vertices (line_id,part_num,vertex_num,x,y,m) AS 
 (SELECT '001',1,1, 0, 5,  0 FROM dual UNION ALL
 SELECT '001',1,2,10,10,11.18 FROM dual UNION ALL
 SELECT '001',1,3,30, 0,33.54 FROM dual UNION ALL
 SELECT '001',2,1,50,10,33.54 FROM dual UNION ALL
 SELECT '001',2,2,60,10,43.54 FROM dual),
 t1 AS           
 (SELECT x coord, line_id, part_num, vertex_num, 1 weight FROM vertices
  UNION ALL      
 SELECT y   , line_id, part_num, vertex_num,2 weight FROM vertices
 UNION ALL      
 SELECT m   , line_id, part_num, vertex_num,3 weight FROM vertices
 )
, t2 as (
 SELECT line_id, part_num
   , sdo_geometry(2002, NULL, NULL
    , sdo_elem_info_array(1,2,1)
    , CAST(collect (coord ORDER BY line_id, part_num, vertex_num,weight) AS sdo_ordinate_array)) line
 FROM t1       
 GROUP BY line_id, part_num
 )
 select line_id
   , sdo_aggr_concat_lines(line) 
 from t2
 group by line_id
 ;
1 - 11

Post Details

Added on Jun 20 2022
11 comments
435 views