Hi all,
I have propably found a critical bug in DOA 4.0.7.1 in conjunction with
the oracle standard client 9.2.0.1
I have an Oracle Database Version 9.2.0.6 with an oracle client V. 9.2.0.1
For test purpose I have build a package-function which will always force
an oracle exception ORA-01422.
When I execute the function within a procedure plsql context the error is
reported:
begin
declare x number;
begin
select errortest.error('123') into x from dual;
end;
end;
ORA-01422: exact fetch returns more than requested number of rows
If executed from within a functional context, no error is reported and
the resultset is empty.
select errortest.error('1234') from dual;
The same effect occurs with the doa-based Software TOAD from Quest-Software,
the Trial-Version of PLSQL-Developer from Allroundautomations is behaving the same.
Executed within SQLPlus the error is reported correctly.
Within Netbeans the same statement is executed with the oracle jdbc driver
the error is also reported correctly.
Further tests have shown that this issue doesn't effect the newest oracle client
9.2.0.8
Is something going wrong with the error trapping of the DOA components?
Is this a configuration issue or a client bug ?
Volker Wilhelm
Compu-Orga GmbH
I have propably found a critical bug in DOA 4.0.7.1 in conjunction with
the oracle standard client 9.2.0.1
I have an Oracle Database Version 9.2.0.6 with an oracle client V. 9.2.0.1
For test purpose I have build a package-function which will always force
an oracle exception ORA-01422.
When I execute the function within a procedure plsql context the error is
reported:
begin
declare x number;
begin
select errortest.error('123') into x from dual;
end;
end;
ORA-01422: exact fetch returns more than requested number of rows
If executed from within a functional context, no error is reported and
the resultset is empty.
select errortest.error('1234') from dual;
The same effect occurs with the doa-based Software TOAD from Quest-Software,
the Trial-Version of PLSQL-Developer from Allroundautomations is behaving the same.
Executed within SQLPlus the error is reported correctly.
Within Netbeans the same statement is executed with the oracle jdbc driver
the error is also reported correctly.
Further tests have shown that this issue doesn't effect the newest oracle client
9.2.0.8
Is something going wrong with the error trapping of the DOA components?
Is this a configuration issue or a client bug ?
Volker Wilhelm
Compu-Orga GmbH