Debugging Procedure in BW

What is the debugging Procedure in BW

HI
In 3.5 you can debug routines in the below way.
1. Load data to the target
2. Then open the update rules -> Extras -> Display Activated Program
3. select the lines where you want to debug. and set a break point.
4. go to manage -> monitor of your request -> details -> processing 
5. select the data package and right click -> simulate update.
6. it will ask you select the records for which you want to debug.. or you can debug for all the records also.
In Bi 7.0
There are two ways.
1. Open the transformation and go to the generated program.
2. Set the break points.
3. Open your DTP and in the execution tab set the processing to "Serially in dialog box (Debugging)"
4. Execute the DTP. It will take you to the debugger .
This way you can debug in the same session only. If you want to debug in new session then you have to set the break points again.
The other way is as follows.
1. Go to your code.
2. Hard code "break-points" in the code.
3. Run your DTP.
4. In the monitor tab click on Debugging and Pass the selections for which you want to debug the routine.
The benefit of this approach is you can debug routine any time and you can give the selections.But dont forget to remove the break points (Hard coded) before transport.
Hope this will help .
- Jaimin

Similar Messages

  • How to see variable Data at the time debugging procedure in oracle toad 9.1

    Hi all,
    I am not able to see variable Data at the time of debugging procedure in oracle toad 9.1 .
    Any help would be appreciated .
    Regards,
    P Prakash
    Edited by: prakash on May 30, 2011 1:37 AM
    Edited by: prakash on May 30, 2011 1:37 AM
    Edited by: prakash on May 30, 2011 1:37 AM

    You might be aware Toad is not an Oracle product, so you need to post this at the forums of Quest, http://www.questsoftware.com
    Sybrand Bakker
    Senior Oracle DBA

  • Unable to debug procedure with parameters

    I have created following dummy procedure to reproduce my problem
    create or replace
    procedure dummy_proc (p_no number, p_name varchar2)
    is
    v_date date;
    begin
    select sysdate into v_date from dual;
    end;
    I am following these steps for debugging
    1. Open procedure in edit mode
    2. Compile it for debug with an icon “compile for debug”
    3. Add breakpoint on select.
    4. Click on lady bug icon to start debugging.
    5. Parameter window pop-up with following pop-up error message i.e.
    An error was encountered performing the requested operation:
    Fail to convert to internal representation
    Vendor code *17059*
    What I understand about problem is:
    It is related to data type conversion of parameters. When Oracle SQL Developer tries to create anonymous PL/SQL block for debugging any procedure with parameters it does not able to translate parameters data types properly. I have checked Tool--> Preferences -- > Debugger but did not find any help. Any one who could able to solve this issue?

    Dear K,
    What I understand from your reply is. This is not Oracle SQL Developer issue is this issue with Oracle configuration?
    Tell me would you able to debug procedures with parameters? Parameter window would successfully generate anonymous pl/sql block with correct data type translation?
    I have noticed one more thing kindly see this might give you any clue to solve my issue.
    DECLARE
    v_Return UNKOWN TYPE;
    BEGIN
    v_Return := db_dummy_pkg.set_dummy_date();
    -- Modify the code to output the variable
    -- DBMS_OUTPUT.PUT_LINE('v_Return = ' || v_Return);
    END;
    This PL/SQL block is generated by OSD for a procedure, not function, without parameters. I have to edit it like following to move on with debugging.
    BEGIN
    db_dummy_pkg.set_dummy_date();
    END;
    It means Oracle SQL Developer might not configure to understand data types like number, varchar2 in debugging mode only. Kindly see above bold text
    kind regards,
    Vitality

  • Not able to debug procedure using oracle 11g & toad 9.0.1.8

    hi..
    i m using oracle 11g & toad 9.0.1.8 ..i want to debug procedure , i set parameter, but not able to debug procedure , there is 'debug' option, but that option is disable..
    can u plz help me regarding this..
    can u suggest me another tool where i can debug my procedure..
    thanx..
    Edited by: user10502250 on Jun 22, 2009 4:15 AM

    "Help, About" should list the installed options, and "Debugger" should be in the list otherwise you'll need an expensive upgrade or a change of IDE.
    In TOAD you have to open the source code editor, at which point the debugging options should be accessible. You can either set a breakpoint and hit the 'Execute' lightening symbol, or place the cursor at a suitable point in the code and press F12.
    I'm not completely sure how you are supposed to pass runtime parameters but it may be to do with right-click, Action Console, Execute, which brings up a 'Set Parameters' dialog. However this won't run in debug mode, it just runs and remembers the arguments. I don't really get it. As you can probably tell I'm not a great fan of the product. Have you looked at PL/SQL Developer?

  • Cannot debug procedure in 11g database using SQL Developer

    Hi,
    We have recently migrated our database from 10.2.0.4 to 11.2.0.2. We were able to debug procedures using PL/SQL Developer earlier but after 11g migration we are not able to debug the same procedure in 11g database.
    Is it that we require 11g PL/SQL developer with 11g client installed to debug?

    11g has a new privilege required to debug stored procedures, DEBUG CONNECT SESSION.
    Does your user have this priv?
    No client required to debug, but if you ARE using a client via OCI THICK preference, be sure that the client version matches the server version.

  • Please help with Debug procedure

    Could someone please guide me ..... I am a first timer.  I have an app that runs in Xcode and before I send it off to Apple I would like to (in an ideal world) debug it on both my 5s and my iPad.  I am sure that there is probably an easy procedure that I have to go through in order to put it on both devices but never having done it before I am a bit in the dark.  Would someone who has done this before please give me a hand.  Latest OS is on the phone and iPad and iTunes connect is on the MBP, not sure if that is key.  Many thanks

    There's not too much to say. Just change your target to your devices and build. Hopefully you won't have to do too much debugging. Have you reviewed all of the hoops necessary to submit an app? You will need video previews and screenshots. I find that once I get an app stable enough to complete this process, it is pretty much ready to go.

  • Can't debug procedures (and other minor quirks)

    I'm using 1.2.1.3213 that bundles JDK1.5.0_06, and running it under RHELWSr3 from /home/jdl/tmp/sqldeveloper/ .
    While editing a procedure, when I hit the debug icon & then hit OK in the Debug PL/SQL window, I don't get the "resume|step into|etc." toolbar in the Debugging-Log tab, nor the SmartData|Data|Watches set of tabs. It seems to do nothing, though this gets displayed back in
    the shell where I started it:
    Exception in thread "AWT-EventQueue-0" java.lang.NoClassDefFoundError
    at oracle.jdevimpl.runner.debug.DebuggingListener.startListening(DebuggingListener.java:68)
    at oracle.jdevimpl.runner.debug.RaptorDebuggingHelper.startDatabaseListener(RaptorDebuggingHelper.java:327)
    at oracle.jdevimpl.runner.debug.RaptorDebuggingHelper.getDatabaseCommands(RaptorDebuggingHelper.java:139)
    at oracle.dbtools.raptor.runner.DBStarterFactory$PlSqlStarter.start(DBStarterFactory.java:267)
    at oracle.ide.runner.RunProcess.startTarget(RunProcess.java:823)
    at oracle.jdeveloper.runner.JRunProcess.startTarget(JRunProcess.java:470)
    at oracle.jdevimpl.runner.debug.DebuggingProcess.startTarget(DebuggingProcess.java:630)
    at oracle.ide.runner.RunProcess.start(RunProcess.java:771)
    at oracle.jdeveloper.runner.JRunProcess.super_start(JRunProcess.java:358)
    at oracle.jdeveloper.runner.JRunProcess.mav$super_start(JRunProcess.java:43)
    at oracle.jdeveloper.runner.JRunProcess$1$1.run(JRunProcess.java:383)
    at java.awt.event.InvocationEvent.dispatch(Unknown Source)
    at java.awt.EventQueue.dispatchEvent(Unknown Source)
    at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source) at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
    at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
    at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
    at java.awt.EventDispatchThread.run(Unknown Source)
    Other minor quirks:
    New connection: the button that should have a label of "Connect"
    instead has "..."; only when I manually widen the window do I see
    what the button label actually is.
    This one is quite difficult to reproduce, but it's happened at least
    4 times to me, so I thought I'd bring it up. I'm not in the habit
    of saving passwords, so when I try to open a connection and I get
    prompted for the Connection Information, occasionally the window
    will not accept any input other than a mouse-click on the buttons:
    it will not accept keyboard focus, so I can't enter a password.
    Hitting the Cancel and selecting the connection again seems to work.
    Maybe this is my old window mgr.
    There's lots of disconcerting noise on startup, which may reveal the source of the debugger problem listed above:
    Oracle SQL Developer
    Copyright (c) 2006, 2007, Oracle. All rights reserved.
    Using oracle.home=/home/jdl/tmp/sqldeveloper
    Using ide.user.dir=/home/jdl/.sqldeveloper
    oracle.classloader.util.AnnotatedNoClassDefFoundError:
    Missing class: com.sun.jdi.Bootstrap
    Dependent class: oracle.jdevimpl.debugger.jdi.DebugJDIConnector
    Loader: main:11.0
    Code-Source: /home/jdl/tmp/sqldeveloper/jdev/extensions/oracle.javacore.jar
    Configuration: system property /home/jdl/tmp/sqldeveloper/jdev/extensions/oracle.javacore.jar
    The missing class is not available from any code-source or loader in the system.
    at oracle.classloader.PolicyClassLoader.handleClassNotFound (PolicyClassLoader.java:2100) [home/jdl/tmp/sqldeveloper/j2ee/home/lib/pcl.jar (from system property java.class.path), by sun.misc.Launcher$AppClassLoader@20120943]
    at oracle.classloader.PolicyClassLoader.internalLoadClass (PolicyClassLoader.java:1698) [home/jdl/tmp/sqldeveloper/j2ee/home/lib/pcl.jar (from system property java.class.path), by sun.misc.Launcher$AppClassLoader@20120943]
    at oracle.classloader.PolicyClassLoader.access$000 (PolicyClassLoader.java:141) [home/jdl/tmp/sqldeveloper/j2ee/home/lib/pcl.jar (from system property java.class.path), by sun.misc.Launcher$AppClassLoader@20120943]
    at oracle.classloader.PolicyClassLoader$LoadClassAction.run (PolicyClassLoader.java:297) [home/jdl/tmp/sqldeveloper/j2ee/home/lib/pcl.jar (from system property java.class.path), by sun.misc.Launcher$AppClassLoader@20120943]
    at java.security.AccessController.doPrivileged (Native method) [unknown, by unknown]
    at oracle.classloader.PolicyClassLoader.loadClass (PolicyClassLoader.java:1657) [home/jdl/tmp/sqldeveloper/j2ee/home/lib/pcl.jar (from system property java.class.path), by sun.misc.Launcher$AppClassLoader@20120943]
    at oracle.classloader.PolicyClassLoader.loadClass (PolicyClassLoader.java:1639) [home/jdl/tmp/sqldeveloper/j2ee/home/lib/pcl.jar (from system property java.class.path), by sun.misc.Launcher$AppClassLoader@20120943]
    at java.lang.ClassLoader.loadClassInternal (Unknown source file) [jre bootstrap, by jre.bootstrap:1.5.0_11]
    at oracle.jdevimpl.debugger.jdi.DebugJDIConnector.getVersion (DebugJDIConnector.java:30) [home/jdl/tmp/sqldeveloper/jdev/extensions/oracle.javacore.jar (from system property /home/jdl/tmp/sqldeveloper/jdev/extensions/oracle.javacore.jar), by main:11.0]
    at oracle.jdevimpl.debugger.support.DebugFactory.<clinit> (DebugFactory.java:83) [home/jdl/tmp/sqldeveloper/jdev/extensions/oracle.javacore.jar (from system property /home/jdl/tmp/sqldeveloper/jdev/extensions/oracle.javacore.jar), by main:11.0]
    at oracle.jdevimpl.cm.dt.DatabaseAddin._initialisePLSQLDebugger (DatabaseAddin.java:232) [home/jdl/tmp/sqldeveloper/jdev/extensions/oracle.onlinedb.jar (from system property /home/jdl/tmp/sqldeveloper/jdev/extensions/oracle.onlinedb.jar), by main:11.0]
    at oracle.jdevimpl.cm.dt.DatabaseAddin.initialize (DatabaseAddin.java:218) [home/jdl/tmp/sqldeveloper/jdev/extensions/oracle.onlinedb.jar (from system property /home/jdl/tmp/sqldeveloper/jdev/extensions/oracle.onlinedb.jar), by main:11.0]
    at oracle.ideimpl.extension.AddinManagerImpl.initializeAddin (AddinManagerImpl.java:433) [home/jdl/tmp/sqldeveloper/ide/lib/ideimpl.jar (from manifest of /home/jdl/tmp/sqldeveloper/ide/lib/ide.jar), by main:11.0]
    at oracle.ideimpl.extension.AddinManagerImpl.initializeAddins (AddinManagerImpl.java:244) [home/jdl/tmp/sqldeveloper/ide/lib/ideimpl.jar (from manifest of /home/jdl/tmp/sqldeveloper/ide/lib/ide.jar), by main:11.0]
    at oracle.ideimpl.extension.AddinManagerImpl.initProductAndUserAddins (AddinManagerImpl.java:157) [home/jdl/tmp/sqldeveloper/ide/lib/ideimpl.jar (from manifest of /home/jdl/tmp/sqldeveloper/ide/lib/ide.jar), by main:11.0]
    at oracle.ide.IdeCore.initProductAndUserAddins (IdeCore.java:1517) [home/jdl/tmp/sqldeveloper/ide/extensions/oracle.ide.jar (from manifest of /home/jdl/tmp/sqldeveloper/ide/lib/ide.jar), by main:11.0]
    at oracle.ide.IdeCore.startupImpl (IdeCore.java:1280) [home/jdl/tmp/sqldeveloper/ide/extensions/oracle.ide.jar (from manifest of /home/jdl/tmp/sqldeveloper/ide/lib/ide.jar), by main:11.0]
    at oracle.ide.Ide.startup (Ide.java:642) [home/jdl/tmp/sqldeveloper/ide/extensions/oracle.ide.jar (from manifest of /home/jdl/tmp/sqldeveloper/ide/lib/ide.jar), by main:11.0]
    at oracle.ideimpl.DefaultIdeStarter.startIde (DefaultIdeStarter.java:35) [home/jdl/tmp/sqldeveloper/ide/lib/ideimpl.jar (from manifest of /home/jdl/tmp/sqldeveloper/ide/lib/ide.jar), by main:11.0]
    at oracle.ideimpl.Main.start (Main.java:90) [home/jdl/tmp/sqldeveloper/ide/lib/ideimpl.jar (from manifest of /home/jdl/tmp/sqldeveloper/ide/lib/ide.jar), by main:11.0]
    at oracle.ideimpl.Main.main (Main.java:51) [home/jdl/tmp/sqldeveloper/ide/lib/ideimpl.jar (from manifest of /home/jdl/tmp/sqldeveloper/ide/lib/ide.jar), by main:11.0]
    at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native method) [unknown, by unknown]
    at sun.reflect.NativeMethodAccessorImpl.invoke (Unknown source file) [unknown, by unknown]
    at sun.reflect.DelegatingMethodAccessorImpl.invoke (Unknown source file) [unknown, by unknown]
    at java.lang.reflect.Method.invoke (Unknown source file) [unknown, by unknown]
    at oracle.ide.boot.PCLMain.callMain (PCLMain.java:45) [home/jdl/tmp/sqldeveloper/ide/lib/ide-boot.jar (from manifest of /home/jdl/tmp/sqldeveloper/ide/lib/ide.jar), by sun.misc.Launcher$AppClassLoader@20120943]
    at oracle.ide.boot.PCLMain.main (PCLMain.java:37) [home/jdl/tmp/sqldeveloper/ide/lib/ide-boot.jar (from manifest of /home/jdl/tmp/sqldeveloper/ide/lib/ide.jar), by sun.misc.Launcher$AppClassLoader@20120943]
    at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native method) [unknown, by unknown]
    at sun.reflect.NativeMethodAccessorImpl.invoke (Unknown source file) [unknown, by unknown]
    at sun.reflect.DelegatingMethodAccessorImpl.invoke (Unknown source file) [unknown, by unknown]
    at java.lang.reflect.Method.invoke (Unknown source file) [unknown, by unknown]
    at oracle.classloader.util.MainClass.invoke (MainClass.java:89) [home/jdl/tmp/sqldeveloper/j2ee/home/lib/pcl.jar (from system property java.class.path), by sun.misc.Launcher$AppClassLoader@20120943]
    at oracle.ide.boot.IdeLauncher.bootClassLoadersAndMain (IdeLauncher.java:218) [home/jdl/tmp/sqldeveloper/ide/lib/ide-boot.jar (from manifest of /home/jdl/tmp/sqldeveloper/ide/lib/ide.jar), by sun.misc.Launcher$AppClassLoader@20120943]
    at oracle.ide.boot.IdeLauncher.launchImpl (IdeLauncher.java:90) [home/jdl/tmp/sqldeveloper/ide/lib/ide-boot.jar (from manifest of /home/jdl/tmp/sqldeveloper/ide/lib/ide.jar), by sun.misc.Launcher$AppClassLoader@20120943]
    at oracle.ide.boot.IdeLauncher.launch (IdeLauncher.java:66) [home/jdl/tmp/sqldeveloper/ide/lib/ide-boot.jar (from manifest of /home/jdl/tmp/sqldeveloper/ide/lib/ide.jar), by sun.misc.Launcher$AppClassLoader@20120943]
    at oracle.ide.boot.IdeLauncher.main (IdeLauncher.java:55) [home/jdl/tmp/sqldeveloper/ide/lib/ide-boot.jar (from manifest of /home/jdl/tmp/sqldeveloper/ide/lib/ide.jar), by sun.misc.Launcher$AppClassLoader@20120943]
    at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native method) [unknown, by unknown]
    at sun.reflect.NativeMethodAccessorImpl.invoke (Unknown source file) [unknown, by unknown]
    at sun.reflect.DelegatingMethodAccessorImpl.invoke (Unknown source file) [unknown, by unknown]
    at java.lang.reflect.Method.invoke (Unknown source file) [unknown, by unknown]
    at oracle.ide.boot.Launcher.invokeMain (Launcher.java:508) [home/jdl/tmp/sqldeveloper/ide/lib/ide-boot.jar (from manifest of /home/jdl/tmp/sqldeveloper/ide/lib/ide.jar), by sun.misc.Launcher$AppClassLoader@20120943]
    at oracle.ide.boot.Launcher.launchImpl (Launcher.java:106) [home/jdl/tmp/sqldeveloper/ide/lib/ide-boot.jar (from manifest of /home/jdl/tmp/sqldeveloper/ide/lib/ide.jar), by sun.misc.Launcher$AppClassLoader@20120943]
    at oracle.ide.boot.Launcher.launch (Launcher.java:60) [home/jdl/tmp/sqldeveloper/ide/lib/ide-boot.jar (from manifest of /home/jdl/tmp/sqldeveloper/ide/lib/ide.jar), by sun.misc.Launcher$AppClassLoader@20120943]
    at oracle.ide.boot.Launcher.main (Launcher.java:49) [home/jdl/tmp/sqldeveloper/ide/lib/ide-boot.jar (from manifest of /home/jdl/tmp/sqldeveloper/ide/lib/ide.jar), by sun.misc.Launcher$AppClassLoader@20120943]
    Addin: Translator PlSql is trying to register a input type (.plsql) which conflicts with translator PlSql who already using this input type

    figured out the main problem (and resolved the startup noise) - I had the windoze distribution that contains "java.exe", so that java wasn't found, and the java that was being found was a jre & not a jdk.

  • Debuging procedures?

    How do you debug a creation/modification of a proc?
    Everytime when I encounter an error creating or modifying a proc I get the same old error:
    Warning: Procedure created with compilation errors.
    is there a log file, table or any place that I can look and it tells me or give any hints of where in the proc caused the compilation error?
    Thanks

    This Select shows the lines in the source-code which have errors in it:
    SELECT e.name, e.text, e.line, s.text FROM user_errors e, all_source s
    where e.name=s.name AND e.type=s.type AND s.owner=user
    AND e.line=s.line AND rownum < 4 ORDER BY e.line;
    null

  • Debug Procedure using JDev10g

    I was using Oracle JDeveloper 10g to debug a pl/sql procedure. I used to do it on different Oracle server and debug works fine. This time, after I let DBA granted the DEBUG connect session and DEBUG any procedure priviledges, I got new problem.
    I did not turn on remote debugger in project setting. The IP address is tied to Nortel IPSECSHM adaptor.
    Connecting to the database CMENTDEV.
    Executing PL/SQL: ALTER SESSION SET PLSQL_DEBUG=TRUE
    Executing PL/SQL: ALTER SESSION SET PLSQL_COMPILER_FLAGS=INTERPRETED
    Executing PL/SQL: CALL DBMS_DEBUG_JDWP.CONNECT_TCP( '169.254.241.150', '3548' )
    ORA-30683: failure establishing connection to debugger
    ORA-12535: TNS:operation timed out
    ORA-06512: at "SYS.DBMS_DEBUG_JDWP", line 68
    ORA-06512: at line 1
    Process exited.
    Disconnecting from the database CMENTDEV.
    Any help will be appreciated. Thank you very much.

    Shay,
    I have downloaded the jdev zip file from oracle.com and then unzipped it on my machine. I try to start jdev using jdev/bin/jdevw.exe and then create a db connection and then a simple procedure.
    When I run the procedure, it works fine. But when I debug it, I get the error "ORA-30683: failure establishing connection to debugger".
    Connecting to the database TST.
    Executing PL/SQL: ALTER SESSION SET PLSQL_DEBUG=TRUE
    Executing PL/SQL: ALTER SESSION SET PLSQL_COMPILER_FLAGS=INTERPRETED
    Executing PL/SQL: CALL DBMS_DEBUG_JDWP.CONNECT_TCP( '192.168.10.55', '3208' )
    ORA-30683: failure establishing connection to debugger
    ORA-12541: TNS:no listener
    ORA-06512: at "SYS.DBMS_DEBUG_JDWP", line 68
    ORA-06512: at line 1
    Process exited.
    Disconnecting from the database TST.
    This database is hosted on a unix machine on our network.
    I installed 9i database on my machine (same as jdev machine) and debug works for that database. Can you please advise what could be the issue?
    Also, the project properties page looks different in my jdev. There is no option for remote debugging. I am using 10.1.2.1.0 (build 1913) of jdev.
    Thanks,
    Gaurav.

  • Debugging Procedures using dbVarName

    It seems as though debug information is not returning the
    names of parameters called in a stored procedure. When using the
    "dockable" debug panel, the information under stored procedures
    shows data in the "type", "CFSQLType", "value" and "variable"
    columns, but nothing under the "dbVarName" column.
    Furthermore, if I run the following code snippet:
    <cfobject action="create" type="java"
    class="coldfusion.server.ServiceFactory" name="factory">
    <cfset cfdebugger = factory.getDebuggingService()>
    <cfset qEvents = cfdebugger.getDebugger().getData()>
    <cfset qEvents = duplicate(qEvents)>
    <cfdump var="#qEvents#">
    ... the name of each parameter called is nowhere to be seen
    in the resulting dump.
    I'm running:
    Update Level /C:/CFusionMX7/lib/updates/hf702-52712.jar
    Is there any way to resolve this issue?

    The other pieces we need to know are what DBMS and which
    drivers. Not all DBMSs and JDBC drivers support dbvarname. Also,
    you need the latest MM JDBC drivers - 3.5 or Microsoft's own latest
    jdbc driver for MSSQL. Oracle thin does not support it.

  • Debugging procedure or packages using sql*plus reg

    Dear all,
    I am new to oracle, can any body provide me some information related to this below issues.
    a) suppose i have created a procedure using sql*plus tool then next day i wanted to debug or modify my stored procedure.
    Then what could approach using sql*plus
    b) same case if we consider for packages then for any specific stored procedure or functions what would be the approach to debug or modify using sql*plus
    yours cordination will be highly appreciate
    Thanks n regards
    Laxman

    Using SQL*Plus you can debug your stored pl/sql code only adding some "prints" in your code:
    SQL> create or replace procedure test is
      2  begin
      3  dbms_output.put_line('starting...');
      4  --do something here
      5  dbms_output.put_line('done step 1');
      6  --do something else here
      7  dbms_output.put_line('end procedure...');
      8  end;
      9  /
    Procedura creata.
    SQL> set serverout on
    SQL> exec test
    starting...
    done step 1
    end procedure...
    Procedura PL/SQL completata correttamente.Or writing logs in a log table:
    SQL> create table logtab(ts timestamp(9),mess varchar2(4000));
    Tabella creata.
    SQL> create or replace procedure test is
      2  begin
      3  insert into logtab values(systimestamp,'starting...');
      4  --do something here
      5  insert into logtab values(systimestamp,'done step 1');
      6  --do something else here
      7  insert into logtab values(systimestamp,'end procedure...');
      8  end;
      9  /
    Procedura creata.
    SQL> exec test
    Procedura PL/SQL completata correttamente.
    SQL> col ts for a40
    SQL> col mess for a40
    SQL> select * from logtab;
    TS                                       MESS
    25-DIC-09 15:33:13,656000000             starting...
    25-DIC-09 15:33:13,656000000             done step 1
    25-DIC-09 15:33:13,656000000             end procedure...Max
    [My Italian Oracle blog|http://oracleitalia.wordpress.com]

  • Debug procedure

    Dear all,
    We have the below script to run a concurrent request in E-Business suite :
    CREATE OR REPLACE Procedure APPS.MED_MGR (
          p_err_code                 IN       VARCHAR2
         ,p_err_msg                  IN       VARCHAR2
         ,p_org_id                   IN       NUMBER
       IS
          l_phase                       VARCHAR2 (2000);
          l_status                      VARCHAR2 (2000);
          l_dev_phase                   VARCHAR2 (2000);
          l_dev_status                  VARCHAR2 (2000);
          l_message                     VARCHAR2 (2000);
          l_conc_status                 BOOLEAN;
          l_req_id                      NUMBER;
          l_print_style                 fnd_concurrent_requests.print_style%Type;
          l_printer                     fnd_concurrent_requests.printer%Type;
          l_number_of_copies            fnd_concurrent_requests.number_of_copies%Type;
          l_save_output_flag            fnd_concurrent_requests.save_output_flag%Type;
          l_get_print_option            BOOLEAN;
          l_set_print_option            BOOLEAN;
          l_add_printer                 BOOLEAN;
          l_req                         NUMBER;
       BEGIN
          FOR rec_org IN
             (SELECT   ood.organization_id
                      ,ood.ORGANIZATION_CODE, ood.ORGANIZATION_NAME
                  FROM MTL_PARAMETERS Mp, org_organization_definitions ood
                 WHERE ood.OPERATING_UNIT = p_org_id
                   AND ood.organization_id = mp.organization_id
                      AND mp.PM_COST_COLLECTION_ENABLED = 1
                      AND ood.DISABLE_DATE IS NULL
                    AND ood.OPERATING_UNIT <> ood.organization_id
          LOOP
                l_req_id                   :=
                   Fnd_Request.submit_request (application      => 'BOM'
                                              ,program          => 'CMCCCM'
                                              ,description      => NULL
                                              ,start_time       => SYSDATE
                                              ,sub_request      => FALSE
                                              ,argument1        => rec_org.organization_id
                                              ,argument2        => 0
             COMMIT;
             Fnd_File.put (Fnd_File.output, rec_org.organization_code||'     '||rec_org.organization_name);
             l_conc_status              :=
                Fnd_Concurrent.wait_for_request (request_id      => l_req_id
                                                ,INTERVAL        => 0
                                                ,max_wait        => 0
                                                ,phase           => l_phase
                                                ,status          => l_status
                                                ,dev_phase       => l_dev_phase
                                                ,dev_status      => l_dev_status
                                                ,MESSAGE         => l_message
          END LOOP;
       END MED_MGR;
    /The problem is when running , we are getting the below error :
    ORA-20100: File o0185007.tmp creation failed as this is writing to UTL_FILE_DIR (/usr/tmp - location in the server). so, I thought of placing
    tracking messages in the above to show exactly what you are passing to FND_FILE in the message log before calling it.
    Any idea ?
    Kai

    Thanks Keith.
    What version of the database are you using?
    10.2.0.5
    Why are you using utl_file_dir and not an oracle directory?
    Its comes default with EBS installation and requires it that way.
    Assuming this is an old unsupported database, and you are using utl_file_dir, then did the os directory on the database server that you are using exist before oracle was last started up?
    This version is still supported.
    Assuming it is a newer configuration,
    Does the file system directory exist on the database server?
    Yes. All other concurrent programs are working fine and wirting to this directory.
    Does oracle have privileges to write to that directory?
    Yes.
    Does oracle have privileges on the directories above that directory.
    Yes.
    Please advise
    Kai
    Pl/sql debugging won't help here. It's an oracle environment issue , or a directory not existing on database server issue.

  • How to debugging a procedure

    Hi,
    I have some 1000 lines of code in a procedure
    now i want to debug this procedure to find out where the error getting
    could any one help me how to debug the huge lines of procedure

    Hi,
    I usually opt for PL/SQL developer tool for debugging millions of line of code. Try to grant the privilege to user 'debug connect session'.
    Try to execute the procedure in step by step execution. Pass the run time variable input value to procedure and go on with debug procedure then you can watch how code is carrying out the changes.
    HTH
    - Pavan Kumar N

  • How to debug a report

    how to debug a report
    i am new to ABAP

    Hi
    <b>ABAP Debugger</b>
    The ABAP Debugger is an integrated test tool within the ABAP Workbench. You use it to check the program logic and to find errors in the source code of an ABAP program. In the Debugger, you can step through the source code of a program. The running program is interrupted after each step, allowing you to check its processing logic and the results of individual statements.
    As of Release 6.10, you can also run Business Server Pages (BSP) in the debugging mode. You can also display and set breakpoints here. Business Server Pages can be displayed in the Object Navigator when you select an appropriate application under BSP Application.
    <b>Features</b>
    The Debugger provides an efficient means of identifying errors in ABAP programs. It contains the following functions:
    •    Ways of starting the Debugger
    •     Choosing different views
    •     Choosing different execution options in the Debugger
    •     Displaying source code in the Debugger
    •               Setting and deleting breakpoints
    •               Setting and deleting watchpoints
    •               Stopping a program at a particular statement or event
    •     Displaying and changing field contents at runtime
    •     Displaying ABAP Objects and references
    •     Displaying and positioning strings
    •     Setting and deleting database locks
    •     Opening the ABAP Editor, or Object Navigator
    •     System settings and runtime warnings
    <b>Starting the Debugger</b>
    There are two possible strategies for starting the Debugger in the ABAP Workbench:
    •     By setting breakpoints then running the program
    •     By running the program in debugging mode.
    <b>Setting Breakpoints</b>
    A breakpoint is a signal in a line of code that tells the ABAP runtime processor to interrupt the program at that line and start the ABAP Debugger. A distinction is made between static and dynamic breakpoints. For further information about the different types of breakpoints and how to use them, refer to Breakpoints.
    Running a Program in Debugging Mode
    You can start the Debugger without previously having set breakpoints. This is the best procedure to use when you want to test a program right from the beginning. It is also useful if you do not know the program very well and therefore are not sure where best to set breakpoints. You can start the Debugger as follows:
    From the Object Navigator     Select a report or transaction and program and choose Program &#61614;&#61472;Test &#61614;&#61472;Debugging.
    From the ABAP Editor     Choose Program &#61614; Execute &#61614; Debugging (or the Debugging pushbutton).
    From any screen     Choose System &#61614; Utilities &#61614; Debug ABAP.
    From any screen     Enter " /h " in the command field.
    <b>Checking System Programs for Errors</b>
    To check a program or program component that is part of the ABAP Workbench (for example, the Screen Painter), you must use the system Debugger. To start the system Debugger, choose System &#61614; Utilities &#61614; Debug system from any screen. To stop the system Debugger, choose Debugger &#61614; Debugging off.
    <b>
    Displaying Program Attributes</b>
    You can display the attributes Fixed point arithmetic, System program and Unicode checks active of the program that has just been executed by choosing Goto &#61614; Further Information &#61614; Program Attributes.
    <b>
    Display Modes in the Debugger</b>
    When you are debugging a program, there are various display modes that you can use. All of the display modes have the same structure. The top part of the screen displays an extract of the program source code. The bottom part displays the information specifically available in that display mode. There are also pushbuttons on the screen allowing you to switch to the most frequently-used display modes. 
    go to se38->give ur program name-.execute->give /h at command prompt->execute->now debugging will start->
    f5-used for line by line debugging
    f6-used for directly executing function modules or performs i.e. control won't go into that block.
    f7-run to cursor
    f8-direct executing.
    fileds: here we can check fild values.
    click fileds option and double click on the filed or type the filen name beside filed
    tables : here we can check the data in the internal table.
    click tables option and double click on the internal table.
    Break points:
    if you want to debug a particulr part you can use this.
    place the cursor at any perform click breakpoint or double click on that line.it will be set.
    if /h from report statement it will debug,so for debugging from particular point we will use break points.use f7 to traverse between multiple break points.
    Watch-points: In some cases we need to check the data populated in the internal table for eample if we want to check the data of internal table record belongs to 100th vendor we will create watch point for this goto->breakpoints->create watch points->give filed itab-lifnr->=->100.
    debugging procedure:
    Use '/H' in the command line and execute the report/program, so that it goes to debugging mode
    2. keep a hard coded break point in the code like BREAK-POINT and it stops there.
    3.From the program Menu, Keep the Soft Break-points and do the debugging.
    see the links
    Refer to this thread
    http://help.sap.com/saphelp_47x200/helpdata/en/c6/617ca9e68c11d2b2ab080009b43351/content.htm
    http://www.sappro.com/downloads/Settings&SystemAreas.pdf
    http://help.sap.com/saphelp_47x200/helpdata/en/c6/617ca9e68c11d2b2ab080009b43351/frameset.htm
    https://forums.sdn.sap.com/click.jspa?searchID=2673672&messageID=3187106
    https://forums.sdn.sap.com/click.jspa?searchID=2673672&messageID=850453
    https://forums.sdn.sap.com/click.jspa?searchID=2673672&messageID=1546485
    https://forums.sdn.sap.com/click.jspa?searchID=2673628&messageID=2048883
    http://www.saplinks.net/index.php?option=com_content&task=view&id=24&Itemid=34
    http://www.sap-img.com/abap/testing-and-debugging-abap-codes-functions.htm
    Reward points if useful

  • How to debug PL/SQL functions? Passing parameter and debugger error

    Hi,
    How to debug a PL/SQL function in JDeveloper? There are two problems with it:
    1) Don't see how it's possible to pass parameters required by function call (in the dialog opening after Debug -> Debug FUNCTION_NAME)
    2) In a function returning table_name%ROWTYPE (and having a record declaration for table_name%ROWTYPE), debug gives error:
    PLS-00103: Encountered symbol "/" when expecting one of ... in line
    v_Return PL/SQL RECORD;
    Debugging procedures works as expected.
    Found a similar question without answer here:
    Debugging PL/SQL with parameters

    Check
    http://www.oracle.com/technology/obe/obe9051jdev/plsqlobe/obeplsql.htm#t2
    Frank

Maybe you are looking for

  • How to Embed a custom view

    Hi Experts, 1) I have a requirement to Embed a custom view in the component CRMCMP_BPIDENT. In the place of IBASE component, my custom view needs to be loaded. 2) Also the result view will be a custom view. which should display list of customers. 3)

  • SAP R/3 different versions,  release years

    HI SAP Gurus, Can any body please can give me the details of SAP R/3 releases and its release years . Example : in 2004 or 205 ECC5 is released and in 2006 ECC6 is released, This also i am not sure i am just giving as an example. I just want to know

  • How to save QT files?

    I can move iTunes files to QT where they sound much better. How can I save these files in the QT format instead of having to open iTunes and drag and drop every time I want to listen to them? Is there some app that I could use to store them and have

  • I have lost more than 500 bookmarks.. i have X marks and synchronizing feature

    I have rescued 500 + bookmarks another 500 have gone awol and i know this cause i saw a brief message saying i had lost them. Unfortunately i lost that remark but obviously firefox has admitted that there are more. How do i find them all now? Thank y

  • Adobe Captivate 5.5 file could not open project

    After copying/pasting a few Captivate slides from one project to another, we received the following message and can not open the file any more. Any advice would be appreciated.  Should we insert slides from one Captivate to another someway differentl