debuging
- Thread starter ashkan209
- Start date
You can only debug programs that are initiated from within the debugger of the Test Window. If a program is called from within a .NET program, you can mimic that call in the Test Window.
It seems to me that the .Net program is making use of a few Oracle10g stored procedures (be it packages, procedures, functions, ..).
If you want to test the specific functionality of these stored procedures the manual of PL/SQL Developer explains in detail how you can do so. In brief you select for example a function you want to test, right-click it and click on 'Test'. I find the rest self-explanatory but if needed the manual will help you further.
Hope this helps.
If you want to test the specific functionality of these stored procedures the manual of PL/SQL Developer explains in detail how you can do so. In brief you select for example a function you want to test, right-click it and click on 'Test'. I find the rest self-explanatory but if needed the manual will help you further.
Hope this helps.
I explain my problem:
I have a software that builds with .net programming
and this software is connected to oracle database with many packages,procedure,...
Now:
when i run a part of software , i see an error that show "i have a problem in my data (and my procedure is working properly)"
for example i have a button in my software and when i clicked, it call a procedure
and this procedure has an Insert command at loop structure
i meet an error in software environment (not in pl/sql) that say ("can not insert null in to table ...")
HOW CAN I FIND A DATA THAT HAS null VALUE?
---
thanks
I have a software that builds with .net programming
and this software is connected to oracle database with many packages,procedure,...
Now:
when i run a part of software , i see an error that show "i have a problem in my data (and my procedure is working properly)"
for example i have a button in my software and when i clicked, it call a procedure
and this procedure has an Insert command at loop structure
i meet an error in software environment (not in pl/sql) that say ("can not insert null in to table ...")
HOW CAN I FIND A DATA THAT HAS null VALUE?
---
thanks
My guess might be totally wrong but it seems to me like the data you're inserting comes from your .Net program and is being passed to the procedure as an argument of some sorts.
Either you let your .Net programming environment (IDE) help you debug what data is being passed to the stored procedure, or you tweak the stored procedure to log somehow what it's doing.
The error you're running into resembles ORA-01400 (http://ora-01400.ora-code.com/). Somehow you're passing a null value to a 'not null column'. You could make use of this and 'catch' the exception.
Either you let your .Net programming environment (IDE) help you debug what data is being passed to the stored procedure, or you tweak the stored procedure to log somehow what it's doing.
The error you're running into resembles ORA-01400 (http://ora-01400.ora-code.com/). Somehow you're passing a null value to a 'not null column'. You could make use of this and 'catch' the exception.
You're like a mistery novel: always reveal bits and pieces of the puzzle one at a time 
I'm not entirely sure I grasp the situation though. You don't have the code or IDE to test/debug the .Net software, so you purchased it. Is there no support from the supplier of the software?
And if the supplier also delivered the database the software seems to use, my guess is you don't have access to the stored procedures unless maybe execution rights. If that is the case I doubt you'll ever be able to debug this problem yourself unless you're in the lucky situation where there's ample logging of what's happening on the Oracle level of the application.
If you do have access to the PL/SQL code I doubt any of us can do more than point you to the brief howto I wrote earlier in this thread or mention the manual that comes with PL/SQL Developer.
I'm not entirely sure I grasp the situation though. You don't have the code or IDE to test/debug the .Net software, so you purchased it. Is there no support from the supplier of the software?
And if the supplier also delivered the database the software seems to use, my guess is you don't have access to the stored procedures unless maybe execution rights. If that is the case I doubt you'll ever be able to debug this problem yourself unless you're in the lucky situation where there's ample logging of what's happening on the Oracle level of the application.
If you do have access to the PL/SQL code I doubt any of us can do more than point you to the brief howto I wrote earlier in this thread or mention the manual that comes with PL/SQL Developer.
