Error with PL/SQL developer when editing table with SDO_GEOM data type

[Aggieangler]

We have recently noticed an issue with PL/SQL developer when connected to Oracle 9.2.0.4. When we edit a table that has a column in it of type MDSYS.SDO_GEOMETRY, we get an error. The error is "ORA-03113 End of file on communication channel". Then we get an error indicating that the connection has been lost, "ORA-03114 not connected to Oracle."

Anyone else ever hit this one?

Thanks,

Aggieangler

BTW...this is the best tool in the world. The PL/SQL debugger alone is worth every bit of the cost.

 

[Aggieangler]

One thing I omitted. This occurrs when the database is trying to select * from the table. I have seen similiar behavior in other apps when trying to connect to tables with MDSYS.SDO_GEOM objects. It could be the same issue. Tables in the same DB that don't have a geometry data type column in them can be edited just fine.

 

[Marco Kalter]

Maybe this is an environment problem. Can you go to Help > About, press the 'Info' button, press the 'Copy all pages' button on this info screen, and paste this text into an e-mail reply?

 

[Aggieangler]

Hi Marco,

I am sending an email reply with this now. I am also able to reproduce the issue at our client site, with their configuration being roughly the same. I can try it in our office as well later in the week.

Thanks,

Aggieangler

 

[Marco Kalter]

Your system information does not reveal any obvious problems or alternatives. Can you send me the table definition so that we can try to reproduce this?

 

[Aggieangler]

For some reason, this issue went away when we reformatted the server and reloaded oracle and patched it to 9.2.0.4. We also recreated another user in the db that builds objects based on MDSYS, so that could have been part of the problem as well.

A simple test table would be:

CREATE TABLE TESTTABLE(
ID NUMBER,
NAME VARCHAR2(50),
GEOMETRY MDSYS.SDO_GEOMETRY
);

Then put some bogus data in the table.

Then try to open it with PL/SQL developer and edit the varchar data.

I think this was the way we reproduced it on-site.