SqlDbx
You are not logged in.
Pages: 1
If will be helpful if for Oracle connection, Objects that are invalid (triggers, views, etc.) becomes marked somehow so it could be possible to quickly see whole objects statuses picture.
I know it is possible to quickly retrieve such objects by Admin/Validate Schema objects, but often it is more convenient to have visual mark in the objects list.
I'd second this feature request with the same use case. It'll be good to have an option to turn-off execution without selection. With some specific flow it is an often situation when you need to keep a lot of requests in the window for a long time. Accident F5 execution could cause a lot of harm. Even it's clearly a user fault an ability to prevent it by configurable option will be much appreciated.
Thanks a lot, that would really help.
Yes, this one returns almost the same errors details, I've checked with different errors. The only difference I've noticed, that error output missed column line. For the same test case I've got:
====
LINE TEXT
6 PLS-00103: Encountered the symbol "1234" when expecting one of the following:
begin case declare exit for goto if loop mod null pragma
raise return select update while with <an identifier>
<a double-quoted delimited-identifier> <a bind variable> <<
close current delete fetch lock insert open rollback
savepoint set sql execute commit forall merge pipe
The symbol "1234" was ignored.
====
Notice that SQLPlus returns 6/9 for Line/Col and not just a line. Everything other is the same for different test cases.
Here is a very simple test case:
I've change "BEGIN" to "BEGIN 1234".
After compile
SELECT LINE, TEXT FROM USER_ERRORS WHERE NAME = 'procedure_name'
Returns nothing
But SQLPlus "show errors" returns:
Warning: Procedure altered with compilation errors.
SQL> show error
Errors for PROCEDURE <name>:
LINE/COL ERROR
-------- -----------------------------------------------------------------
6/9 PLS-00103: Encountered the symbol "1234" when expecting one of
the following:
begin case declare exit for goto if loop mod null pragma
raise return select update while with <an identifier>
<a double-quoted delimited-identifier> <a bind variable> <<
close current delete fetch lock insert open rollback
savepoint set sql execute commit forall merge pipe
The symbol "1234" was ignored.
I've tried to recompile invalid procedure and the output I got is the same:
ALTER PROCEDURE <procedure_name> COMPILE;
ORA-24344: success with compilation error
And that's it.
Oracle version:
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Prod
SQLDbx - 3.48
Just to explain why I need it. Example:
We have and invalid trigger and trying to recompile it. Trigger could not be recompiled due to errors in it and recompilation attempt issuing ORA-24344 - success with compilation error. And that is what I see in SQLDbx. Now, I need to know error details, like LINE/COL ERROR and that is what SQLPlus provides by "show errors" command. Unfortunately as it is impossible in SQLDbx I need to go to SQLPlus and repeat the same recompiling and then retrieve errors. So that is where a nature of my question comes from - just trying to avoid switching between SQLDbx and SQLPlus.
Is there any way in SQLDbx to execute "show errors" command after unsuccessful compilation?
Since 3.42 Package properties returns empty Header and Body. 3.41 producing correct result in this dialog.
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Prod
I think that is a nice feature request. Indeed status bar shows query status like "Query complete:<query>. However if you're running several queries as batch and they are insert/update/delete, it is impossible to see how many rows are affected by each and which of query is completed. It will be good to have as it is valuable information.
Running the following query:
SELECT xx_data FROM yy_table
where xx_data is LONG RAW with BLOB inside causing error:
ORA-03106: fatal two-task communication protocol error
Version in use:
SqlDbx 3.26.1
Oracle: 9.2
In version 3.26.1 maximizing windows causing overlapping of task bar. This is inconvenient SqlDBx overlaps Start button as well as task bar. Could it be corrected so that maximize window will act as suspected by windows GUI?
Thank you.
Pages: 1