I'm running PL/SQL Developer 6.0.6.946 against a 10.2.0.1.0 database.
Selecting an XMLType column in an SQL Window produces strange error messages and eventually disconnects.
To reproduce the error, run these statements one at a time in an SQL Window:
create global temporary table TEMP_XML
(
LINE NUMBER,
XML_BLOCK XMLTYPE
)
on commit preserve rows;
INSERT INTO temp_xml(line, xml_block)
VALUES (1, '')
INSERT INTO temp_xml(line, xml_block)
VALUES (2, '')
INSERT INTO temp_xml(line, xml_block)
VALUES (3, '')
SELECT * FROM temp_xml
The message I'm getting is
OCI-21500: internal error code, arguments: [58], [], [], [], [], [], [], []
OCI-21500: internal error code, arguments: [kghfrh:ds], [0x23A8724], [], [], [], [], [], []
You don't even need data in the table to produce the error, but it's less likely to disconnect you or have other strange behaviours beyond displaying the error.
Is it possible to fix this in PL/SQL Developer or is this even a PL/SQL Developer bug or limitation? If it is not a PL/SQL Developer bug, any hints on how to reproduce using only SQLPlus so I could open a TAR with Oracle?
Selecting an XMLType column in an SQL Window produces strange error messages and eventually disconnects.
To reproduce the error, run these statements one at a time in an SQL Window:
create global temporary table TEMP_XML
(
LINE NUMBER,
XML_BLOCK XMLTYPE
)
on commit preserve rows;
INSERT INTO temp_xml(line, xml_block)
VALUES (1, '')
INSERT INTO temp_xml(line, xml_block)
VALUES (2, '')
INSERT INTO temp_xml(line, xml_block)
VALUES (3, '')
SELECT * FROM temp_xml
The message I'm getting is
OCI-21500: internal error code, arguments: [58], [], [], [], [], [], [], []
OCI-21500: internal error code, arguments: [kghfrh:ds], [0x23A8724], [], [], [], [], [], []
You don't even need data in the table to produce the error, but it's less likely to disconnect you or have other strange behaviours beyond displaying the error.
Is it possible to fix this in PL/SQL Developer or is this even a PL/SQL Developer bug or limitation? If it is not a PL/SQL Developer bug, any hints on how to reproduce using only SQLPlus so I could open a TAR with Oracle?