Problems in Debug mode

Hi,
I like Raptor a lot, but I can't seem to get the debugger working properly.
I created a tiny sample proc which I include below.
I set a breakpoint on the SELECT statement.
I hit the debug button and the Debug PL/SQL window appears, and so I click OK to debug.
The SELECT statement is highlighted so all looks good as I seem to have hit the breakpoint, but...
The mouse is stuck in hourglass mode and I've lost the debug menu as all entries are greyed out. I can't step through or watch items.
Once the debug process is complete the mouse still is in hourglass mode and I can't use it at all. The keyboard is still usable but the menus aren't in the right context either and I'm stuck. Occasionally, after some minutes, I can resume and end the session using the keyboard, but from there I just have to close down Raptor as the mouse is pretty much useless and I can't fully tab around all the sub-panes.
I can't see a similar issue in the forum or elsewhere for that matter. I get the same issue regardless of proc as I've tried others also.
This is what I ran:
CREATE OR REPLACE
PROCEDURE aatest IS
l_date DATE;
BEGIN
SELECT SYSDATE INTO l_date FROM DUAL;
DBMS_OUTPUT.PUT_LINE(TO_DATE(l_date, 'DD-MON-YY HH:MI:SS'));
END aatest;
Thanks in advance,
Garrett

Set your breakpoints, then hit "Compile with Debug" (of the 4 buttons it is the one furthest to the right, with the Black arrow).
The procedure appears to be running / paused, as what you would see when the procedure is finished is the following:
Process exited.
Disconnecting from the database XE as <username>.
Debugger disconnected from database.
Do a test function like:
CREATE OR REPLACE
function f_test_debugger(
i_arg1 varchar2,
i_arg2 varchar2
) return varchar2 is
v_retn varchar2(200);
begin
v_retn := i_arg1 || ' ' || i_arg2;
DBMS_OUTPUT.PUT_LINE('i_arg1 = ' || i_arg1);
DBMS_OUTPUT.PUT_LINE('i_arg2 = ' || i_arg2);
DBMS_OUTPUT.PUT_LINE('v_retn = ' || v_retn);
return v_retn;
end f_test_debugger;
Without breakpoints, here is the series of events:
Compile with debug
Debug (ladybug button)
A box should popup with all of the input variables defined as:
i_arg1 := NULL;
i_arg2 := NULL;
You should replace these values with the text values. I have used:
i_arg1 := 'first';
i_arg2 := 'second';
Then click ok in that box and the process should run through and in the logging window you should see something like this (note that the 3 bolded lines are programmed output from the DBMS_OUTPUT lines in the function; the rest is all system generated):
Connecting to the database <sid> as <username>.
Executing PL/SQL: ALTER SESSION SET PLSQL_DEBUG=TRUE
Executing PL/SQL: CALL DBMS_DEBUG_JDWP.CONNECT_TCP( '<ip address>', '1547' )
Debugger accepted connection from database on port 1547.
Processing 59 classes that have already been prepared...
Finished processing prepared classes.
i_arg1 = first
i_arg2 = second
v_retn = first second
v_Return = first second
Process exited.
Disconnecting from the database <sid> as <username>.
Debugger disconnected from database.

Similar Messages

  • Problem with Debug mode and SLD

    Using the config tool, we have turned the Debuggable flag to 'yes' and set the Debug mode to OFF.   Now from the studio, when I enable debugging for the process, the server0 stops successfully and restarts successfully. However, during the restart, the SLD service errors out and does not get started. It encounters the following exception. I can verify the error in std_server0.out
    With erred SLD service, when I try to deploy and run the webdynpro application from studio, the deploy fails with the same exception.
    We tried all kinds of restart (of the engine\server instance), debuggable and debug mode setting permutations, but not successfull.  (debug port is 50021)
    We are having remote debug server setup (not local).
    Does anybody have any suggestions???
    The exception we get is:
    Finished with warnings: development component 'CreateOrder'/'local'/'LOKAL'/'0.2007.11.26.14.33.54':Caught exception during application startup from SAP J2EE Engine's deploy service:java.rmi.RemoteException: Error occurred while starting application local/CreateOrder and wait. Reason: Clusterwide execption: server ID 3775750:<Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='com.sap.engine.services.deploy.container.DeploymentException: <Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='Implied start failed for dependency :local/CreateOrder -> service:sld', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key Implied start failed for dependency :local/CreateOrder -> service:sld', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key com.sap.engine.services.deploy.container.DeploymentException: <Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='Implied start failed for dependency :local/CreateOrder -> service:sld', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key Implied start failed for dependency :local/CreateOrder -> service:sld (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)

    Hi Michael,
    one way is to enhance the server go.bat with debug parameters. Under c:\usr\sap\<SID>\j2ee\<INSTANCE>\cluster\server\go.bat define the following params
    set DEBUG_PORT=5000
    set DEBUG_PARAMS=-Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=
    and add both params to the java arguments (e.g. behind the -classpath): %DEBUG_PARAMS%%DEBUG_PORT%.
    Regards,
    Stefan

  • Deployment problem in debug mode

    Hi,
    I developed a project in XP and moved to a laptop with vista. I am able to run (except *.exe) all files but I am not able run debug mode. I get the error:
    Deploying application in domain failed; could not rename C:\program files\sun\creator2_1\sunappserver8\domains\creator\generated\xml\j2ee-modules\PAIRS5_
    Log Level:     SEVERE
    Logger:     javax.enterprise.system.tools.deployment
    Name-Value Pairs:     _ThreadID=13;
    Record Number:     2093
    Message ID:     Exception occured in J2EEC Phase com.sun.enterprise.deployment.backend.IASDeploymentException
    Complete Message
    Could not rename C:\Program Files\Sun\Creator2_1\SunAppServer8\domains\creator\generated\jsp\j2ee-modules\PAIRS5 to C:\Program Files\Sun\Creator2_1\SunAppServer8\domains\creator\generated\jsp\j2ee-modules\PAIRS5_old
         at com.sun.enterprise.deployment.backend.ModuleDeployer.setOldDirs(ModuleDeployer.java:764)
         at com.sun.enterprise.deployment.backend.WebModuleDeployer.preRedeploy(WebModuleDeployer.java:241)
         at com.sun.enterprise.deployment.backend.ModuleDeployer.doRequestFinish(ModuleDeployer.java:158)
         at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:148)
         at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:71)
         at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:639)
         at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:188)
         at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:520)
         at com.sun.enterprise.management.deploy.DeployThread.deploy(DeployThread.java:139)
         at com.sun.enterprise.management.deploy.DeployThread.run(DeployThread.java:168)
    Is there any error I can fix??? Please help...
    dr.am.mohan rao

    Were you able to fix this? I am having the same issue.

  • Creator Hangs in debug mode

    I am testing a five page web page that connects to an SQL Server database.
    I am experiencing severe memory problems in debug mode. The application hangs after stepping through a some code.
    The debug screen goes all grey and I cannot get it to return to normal (see the code).
    I am developing on a windows XP platform and I am using Netscape 7.1 as my browser.

    Not sure why you are getting the error . I just checked the link, as well as the download tab, and it works for me. Could you please try the link again.
    Hot Fix 2: You can download it from update center: Launch the IDE and connect to the Update Center .
    See how to connect to update center from this link:
    http://developers.sun.com/jscreator/downloads/updates/index.jsp

  • Problem viewing cursor value in debug mode

    Hi eveybody!
    I'm French and new here.
    I know some topics deal with my subject but I don't really understand.
    Here's my environnement :
    Win2000 / ORA 9iR2 / SQL DEVELOPPER 1.0.0.15.57
    As some people say when i'm in debug mode (after compiling my procedure PL/SQL for debug) I can't see any value of my cursors !
    Ex :
    CURSOR cur IS
    SELECT COL1, COL2
    FROM TABLE1;
    v_cur cur%ROWTYPE;
    For v_cur in cur
    Loop
    If v_cur.COL1 = 'toto' then
    'do something' ;
    End if;
    End Loop;
    When I run this step by step in debug mode I can't see the data of my cursor in the data or smartdata pane.
    The values of my cursor is allways null !
    I guess I'm not the only one to see that bug.
    My question is should I wait a new release of sql developer or is there any solution for this problem?
    Anyway I want to congratulate the developers team who create this tool which is fabulous! It makes me forget TOAD and it's totally free.
    Thanks a lot for this job.
    Greg

    Here is a piece of code I use:
    CREATE OR REPLACE PROCEDURE sm_list AS CURSOR emp_cursor IS
    SELECT d.department_name,
    e.last_name
    FROM departments d,
    employees e
    WHERE d.department_id = e.department_id;
    emp_record emp_cursor % rowtype;
    BEGIN
    FOR emp_record IN emp_cursor
    LOOP
    DBMS_OUTPUT.PUT_LINE(emp_record.last_name);
    END LOOP;
    END;
    With this example, I agree, the smart data is null. Logged a bug. However, note that I do see values in the data tab and can modify and watch these values.
    When using cursors I've been looping and then fetching into cursor records, i.e.:
    FETCH emp_cursor
    INTO emp_record;
    emp_tab(i) := emp_record;
    and then the values display in the Smart data and data tabs.
    Sue

  • Problem get the parameter ID using debug mode

    Hi Expert,
    I got problem for tracking the problem which is using GET PARAMETER ID under debug mode. the scenario is like that, I go and run the BDC transaction and want to use GET PARAMETER ID 'KUN' to populate data customer code to some variable. but when I using the debug mode sometimes my variable is came from GET PARAMETER ID was missing. but if running not using the debug mode all is populated perfectly. is there any SAP notes or code I can use to continue my debuging instead using GET PARAMETER ID ? Thank you
    Regards,
    Koho koho

    Hi BreakPoint,
    Thanks for the replay, I really don't know and how to configure again. this morning I am running upload program using the BDC using the get paramater ID from posting FB03. I loading 10 documents upload. and 2 is failed to take the "get parameter id 'BLN' field var1" and var1 is blank, the other 8 document posted I can get the paramter id as well. any solution for this case. Thanks
    Regards,
    Koho koho

  • Problem connecting to Realtime system to download or run in debug mode

    I have updated my LabWindows\CVI to 2013. I have a PXI system with a PXIe-8101 controller. The PXIe-controller has a real-time OS installed. I have been programming this system for a while now so I am not exactly a novice anymore. The first time I tried to install the program to my real-time target I got a message which said "LabWindows/CVI cannot connect to the real-time target." It also said " .... The version of the LabWindows/CVI Run-Time Engine for RT must be compatible with the version of the LabWindows/CVI development environment."
    So I figured that was the problem. My next step was to go into MAX and sure enough was getting all sorts of flags and errors when I used the real-time software Wizard in MAX by right clicking on the Remote software and clicking on Add/Remove Software. And like I suspected there were several flags indicating a software differences. My next step was to update the software in my real-time target to resolve the problem. After I did that I compiled the code and installed it on my remote system.  Everything seemed OK.
    The following Monday I restarted LabWindows/CVI and made a couple of changes and tried to build and install to my real-time target. I get that same message as in the first paragraph. So I thought I might not have real-time system  booted up correctly or something like that so I checked all of that and it looked OK. Next I opened up MAX and it could see my real-time target just fine.
    When I had my LabWindows/CVI 2012 I did not have this problem. I think maybe there is some incompatibliity issues with my LabWindows 2013; has anyone had a similar problem? I am able to get around the problem by building the release version and copying it to the PXI with CuteFTP V9.0 but I cannot do run my program in debug mode with my LabWindows/CVI and if you may have noticed I have other problems which is in another post I put in next week. I am hoping the problems are connected and I can kill two birds with one stone LOL.
    I appreciate any suggestions.
    Thanks,
    Don Pearce

    Hello,
    I want to make sure I'm understanding what you are doing in the LabVIEW project. According to the Getting Started with the LabWindows /CVI Real-Time Module manual, these are the steps to install software on the RT target:
    1. Launch MAX.
    2. Find and expand your RT target under the Remote Systems item in the MAX configuration tree, right-click Software, and select Add/Remove Software. When you select Add/Remove Software, MAX launches the LabVIEW Real-Time Software Wizard. This displays all the National Instruments software and drivers installed on the host computer that you can install on a selected RT target.
    3. Select the software you want to install on the RT target, click the icon next to the software, and select Install the feature.
    You need to install LabWindows/CVI Run-Time Engine for RT to add support for LabWindows/CVI RT applications on the RT target. This component is required for all LabWindows/CVI RT applications.
    The forum post here solved this same issue by installing missing drivers based on this KnowledgeBase article.
    Also, LabWindows/CVI 2013 SP1 has been released. Service Pack 1 (SP1) has many  useful bug fixes (listed here), so I recommend upgrading to LabWindows/CVI 2013 SP1 if possible.
    Taylor B.
    National Instruments

  • Runing In debug mode problem

    i m using Form9i suite , oracle 9i running under VMware machine where i installed windows XP service pack 3 with internet explorer version 8 IE8.
    i have a problem when i run my Fmb form in debug mode it is not loaded, even though if i run it normally my fmb form loaded well .
    any suggestion
    thank you
    Edited by: user12923153 on Nov 11, 2012 6:37 AM

    Hi
    But the program to print the advice is set in the payment?
    What can you see in Print Out/Data Medium section?
    You need to considere F110 runs the print program in backgroud mode, that means a job is scheduled, so try to checl the job too
    Max

  • Problem when trying to run in "Debug Mode" in JDeveloper9i

    Hello All ,
    i have a problem to debug my application using
    JDeveloper9i .
    i get an error: "fdebug.exe could not be read "
    and Application error box appears .
    i did the following steps in the instalation:
    1) i installed the JDK 1.3
    2) installed the Jdev9i from base installation zip
    3) In <jdeveloper_root>\jdev\bin\ i executed the command
    InstallOJVM.bat c:\jdk1.3
    and get message:
    "InstallOJVM successfully"
    4) i wrote simple program and put a breakpoint ,
    when i'm trying to run the program in "Debug mode" i get an error box message
    "fdebug.exe Application Error"
    The memory instruction could not be read
    please help ,me to fix the problem i need the debuger option .
    thanks in advance.

    Do you have the file c:\jdk1.3\jre\bin\fdebug.exe, if you don't, you
    need it. Look for the file in the base install directory, it should be
    there and then copy it to the location above.
    Michel

  • Debug mode problem.

    Hi Expert,
    There is sap script form attached to the particular payment advice. When i am running trasanction F110, it contains the particular zprogram assigned to that payment method. I actually want to debug this and want to see how program accesses zprogram and zform but despite of breakpoint in the program and script it don't stop to the zprogram or from. Could you please guide me how i can reach to the zprogram and zscript in debug mode ?...Output is getting generated with the help of zprogram and zform.
    Thanks.

    Hi
    But the program to print the advice is set in the payment?
    What can you see in Print Out/Data Medium section?
    You need to considere F110 runs the print program in backgroud mode, that means a job is scheduled, so try to checl the job too
    Max

  • Can't Run program in Debug Mode

    To: [email protected]
    cc:
    Subject: Can't Run program in Debug Mode
    Has anyone else experienced this problem? We have written a non-express
    program that uses the Express generated services project as a supplier
    plan. However, when we try running this program in debug mode about 50%
    (or more) of the time we abend while Forte is trying to partition the
    application. Since we have many database classes in our Business Model we
    are wondering if Forte is timing out during the partition phase or if the
    server partition is running out of memory . The following error messages
    are produced by Forte. Any suggestions???
    =======================
    Error messages on client:
    =======================
    SYSTEM ERROR: Unable to start the partition testacadprogoffer_CL0_Part1 on
    any
    of the nodes to which it has been assigned. See the remainder of the
    error
    stack for more information.
    Class: qqsp_ResourceException
    Error #: [1602, 593]
    Detected at: qqcf_StandardConfig::LoadRemotePartition at 5
    Last TOOL statement: method overview.StartApplication
    Error Time: Tue Dec 02 12:56:01
    Exception occurred (locally) on partition "Express_cl7_Client",
    (partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
    taskId =
    [F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in application
    "FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
    CentralEnv.
    SYSTEM ERROR: Unable to start partition testacadprogoffer_CL0_Part1 on node
    admin2.
    Class: qqsp_ErrorDescriptor
    Error #: [1602, 592]
    Detected at: qqcf_StandardConfig::LoadRemotePartition at 3
    Error Time: Tue Dec 02 12:56:01
    Exception occurred (locally) on partition "Express_cl7_Client",
    (partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
    taskId =
    [F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in application
    "FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
    CentralEnv.
    SYSTEM ERROR: Lost contact with remote server while trying to load
    partition
    testacadprogoffer_CL0_Part1. Check server log file for more information
    about
    the specific problem.
    Class: qqsp_ResourceException
    Error #: [1301, 102]
    Detected at: qqem_IPartitionAgent::Startup at 5
    Error Time: Tue Dec 02 12:56:01
    Exception occurred (locally) on partition "Express_cl7_Client",
    (partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
    taskId =
    [F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in application
    "FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
    CentralEnv.
    INFORMATION: The connection to the partner was terminated by the
    Communication
    Manager for the reasons below.
    Class: qqsp_DistAccessException
    Detected at: qqdo_PartitionMgr::StopLocation at 1
    Error Time: Tue Dec 02 12:56:00
    Distributed method called: qqrt_ForteExecAgentProxy.LoadPartition!6
    (object name Unnamed) from partition "Forte_Executor", (partitionId =
    F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9, taskId =
    [F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9.229]) in application
    "FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment CentralEnv
    Exception occurred (locally) on partition "Express_cl7_Client",
    (partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
    taskId =
    [F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in application
    "FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
    CentralEnv.
    INFORMATION: Network partner closed connection. This usually means the
    process at the other end of the wire failed. Please go look there and
    find
    out why.
    Class: qqsp_DistAccessException
    Detected at: qqcm_HoseFSM::ReceivedClose at 2
    Error Time: Tue Dec 02 12:56:00
    Exception occurred (locally) on partition "Express_cl7_Client",
    (partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
    taskId =
    [F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in application
    "FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
    CentralEnv.
    INFORMATION: Received close: Connection aborted (10053).
    Class: qqsp_DistAccessException
    Detected at: qqcm_HoseFSM::ReceivedClose at 1
    Error Time: Tue Dec 02 12:56:00
    Exception occurred (locally) on partition "Express_cl7_Client",
    (partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
    taskId =
    [F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in application
    "FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
    CentralEnv.
    =======================
    Log messages on server:
    =======================
    Attached to manager for node admin2.
    aud Tue Dec 2 09:34:36 : Loading partition testacadprogoffer_cl0_Part2
    built on <unknown>.
    Attached to manager for node admin2.
    aud Tue Dec 2 09:41:58 : Shutting down partition as requested.
    aud Tue Dec 2 09:41:59 : Unloaded partition testacadprogoffer_cl0_Part2.
    aud Tue Dec 2 09:49:44 : Loading partition testacadprogoffer_cl0_Part2
    built on <unknown>.
    Attached to manager for node admin2.
    aud Tue Dec 2 10:00:11 : Shutting down partition as requested.
    aud Tue Dec 2 10:00:12 : Unloaded partition testacadprogoffer_cl0_Part2.
    aud Tue Dec 2 10:18:34 : Loading partition testacadprogoffer_cl0_Part3
    built on <unknown>.
    Attached to manager for node admin2.
    aud Tue Dec 2 10:27:00 : Shutting down partition as requested.
    aud Tue Dec 2 10:27:00 : Unloaded partition testacadprogoffer_cl0_Part3.
    aud Tue Dec 2 10:47:03 : Loading partition
    EvaluateApplRequirementsBO_CL0_Part1 built on <unknown>.
    Attached to manager for node admin2.
    aud Tue Dec 2 11:09:26 : Shutting down partition due to failure of agent
    owner's partition.
    aud Tue Dec 2 11:09:26 : Shutting down partition as requested.
    aud Tue Dec 2 11:09:26 : Unloaded partition
    EvaluateApplRequirementsBO_CL0_Part1.
    aud Tue Dec 2 12:36:14 : Loading partition testacadprogoffer_CL0_Part1
    built on <unknown>.
    Attached to manager for node admin2.
    aud Tue Dec 2 12:45:17 : Shutting down partition as requested.
    aud Tue Dec 2 12:45:17 : Unloaded partition testacadprogoffer_CL0_Part1.
    FATAL ERROR: Out of Memory (reason = qqOS_MM_EX_OUT_OF_MEMORY)
    FATAL ERROR: Out of Memory (reason = qqOS_MM_EX_OUT_OF_MEMORY)
    Task 11: qqcm_HoseRecvServiceTask::Run: Caught unexpected exception
    FATAL ERROR: ************* Out of Memory, requested (1K) available (0K)
    Class: qqsp_ResourceException with ReasonCode: SP_ER_OUTOFMEMORY
    Detected at: qqos_MemoryManager
    Error Time: Tue Dec 2 12:49:01
    Exception occurred (locally) on partition "Forte_Executor",
    (partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10f3, t
    askId = [F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10f3.11]) in application
    "Forte Runtime", pid 14020 on node admin2 in environ
    ment CentralEnv.
    FATAL ERROR: ************* Out of Memory, requested (1K) available (0K)
    Class: qqsp_ResourceException with ReasonCode: SP_ER_OUTOFMEMORY
    Detected at: qqos_MemoryManager
    Error Time: Tue Dec 2 12:48:57
    FATAL ERROR: Out of Memory (reason = qqOS_MM_EX_OUT_OF_MEMORY)
    FATAL ERROR: Out of Memory (reason = qqOS_MM_EX_OUT_OF_MEMORY)
    ERROR: TMgr.RunThread: task cm.Recv failed terminating.
    Probably caused by a FATAL exception.
    David Wilbur email: [email protected]
    University of Windsor phone: 519-253-3000 ext. 2779
    Windsor, Ontario Canada
    -----------------------------------------------

    Hi,
    We have had the same problem in a non-express application
    with a heavy server partition. In our case, the error was not
    systematic, depending on the server workload at the time we
    tried to partition and run.
    The work-around we're using is to put the -fm flags (increasing the x
    parameter to say 30000) in the 'server arguments' of your server
    partition
    properties in the partition workshop. Note that if your server is a Unix
    platform,
    you need to put double-quotes before and after the parenthesis in the -fm
    syntax.
    Hope this helps,
    Vincent Figari
    BTW, what Forte version are you using ?
    On Tue, 2 Dec 1997 13:44:24 -0500 "David Wilbur"<[email protected]>
    writes:
    >
    >
    >
    >
    >
    To: [email protected]
    cc:
    Subject: Can't Run program in Debug Mode
    Has anyone else experienced this problem? We have written a
    non-express
    program that uses the Express generated services project as a supplier
    plan. However, when we try running this program in debug mode about
    50%
    (or more) of the time we abend while Forte is trying to partition the
    application. Since we have many database classes in our Business
    Model we
    are wondering if Forte is timing out during the partition phase or if
    the
    server partition is running out of memory . The following error
    messages
    are produced by Forte. Any suggestions???
    =======================
    Error messages on client:
    =======================
    SYSTEM ERROR: Unable to start the partition
    testacadprogoffer_CL0_Part1 on
    any
    of the nodes to which it has been assigned. See the remainder of
    the
    error
    stack for more information.
    Class: qqsp_ResourceException
    Error #: [1602, 593]
    Detected at: qqcf_StandardConfig::LoadRemotePartition at 5
    Last TOOL statement: method overview.StartApplication
    Error Time: Tue Dec 02 12:56:01
    Exception occurred (locally) on partition "Express_cl7_Client",
    (partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
    taskId =
    [F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in
    application
    "FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
    CentralEnv.
    SYSTEM ERROR: Unable to start partition testacadprogoffer_CL0_Part1 on
    node
    admin2.
    Class: qqsp_ErrorDescriptor
    Error #: [1602, 592]
    Detected at: qqcf_StandardConfig::LoadRemotePartition at 3
    Error Time: Tue Dec 02 12:56:01
    Exception occurred (locally) on partition "Express_cl7_Client",
    (partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
    taskId =
    [F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in
    application
    "FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
    CentralEnv.
    SYSTEM ERROR: Lost contact with remote server while trying to load
    partition
    testacadprogoffer_CL0_Part1. Check server log file for more
    information
    about
    the specific problem.
    Class: qqsp_ResourceException
    Error #: [1301, 102]
    Detected at: qqem_IPartitionAgent::Startup at 5
    Error Time: Tue Dec 02 12:56:01
    Exception occurred (locally) on partition "Express_cl7_Client",
    (partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
    taskId =
    [F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in
    application
    "FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
    CentralEnv.
    INFORMATION: The connection to the partner was terminated by the
    Communication
    Manager for the reasons below.
    Class: qqsp_DistAccessException
    Detected at: qqdo_PartitionMgr::StopLocation at 1
    Error Time: Tue Dec 02 12:56:00
    Distributed method called:
    qqrt_ForteExecAgentProxy.LoadPartition!6
    (object name Unnamed) from partition "Forte_Executor",
    (partitionId =
    F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9, taskId =
    [F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9.229]) in
    application
    "FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
    CentralEnv
    Exception occurred (locally) on partition "Express_cl7_Client",
    (partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
    taskId =
    [F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in
    application
    "FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
    CentralEnv.
    INFORMATION: Network partner closed connection. This usually means
    the
    process at the other end of the wire failed. Please go look there
    and
    find
    out why.
    Class: qqsp_DistAccessException
    Detected at: qqcm_HoseFSM::ReceivedClose at 2
    Error Time: Tue Dec 02 12:56:00
    Exception occurred (locally) on partition "Express_cl7_Client",
    (partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
    taskId =
    [F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in
    application
    "FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
    CentralEnv.
    INFORMATION: Received close: Connection aborted (10053).
    Class: qqsp_DistAccessException
    Detected at: qqcm_HoseFSM::ReceivedClose at 1
    Error Time: Tue Dec 02 12:56:00
    Exception occurred (locally) on partition "Express_cl7_Client",
    (partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
    taskId =
    [F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in
    application
    "FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
    CentralEnv.
    =======================
    Log messages on server:
    =======================
    Attached to manager for node admin2.
    aud Tue Dec 2 09:34:36 : Loading partition
    testacadprogoffer_cl0_Part2
    built on <unknown>.
    Attached to manager for node admin2.
    aud Tue Dec 2 09:41:58 : Shutting down partition as requested.
    aud Tue Dec 2 09:41:59 : Unloaded partition
    testacadprogoffer_cl0_Part2.
    aud Tue Dec 2 09:49:44 : Loading partition
    testacadprogoffer_cl0_Part2
    built on <unknown>.
    Attached to manager for node admin2.
    aud Tue Dec 2 10:00:11 : Shutting down partition as requested.
    aud Tue Dec 2 10:00:12 : Unloaded partition
    testacadprogoffer_cl0_Part2.
    aud Tue Dec 2 10:18:34 : Loading partition
    testacadprogoffer_cl0_Part3
    built on <unknown>.
    Attached to manager for node admin2.
    aud Tue Dec 2 10:27:00 : Shutting down partition as requested.
    aud Tue Dec 2 10:27:00 : Unloaded partition
    testacadprogoffer_cl0_Part3.
    aud Tue Dec 2 10:47:03 : Loading partition
    EvaluateApplRequirementsBO_CL0_Part1 built on <unknown>.
    Attached to manager for node admin2.
    aud Tue Dec 2 11:09:26 : Shutting down partition due to failure of
    agent
    owner's partition.
    aud Tue Dec 2 11:09:26 : Shutting down partition as requested.
    aud Tue Dec 2 11:09:26 : Unloaded partition
    EvaluateApplRequirementsBO_CL0_Part1.
    aud Tue Dec 2 12:36:14 : Loading partition
    testacadprogoffer_CL0_Part1
    built on <unknown>.
    Attached to manager for node admin2.
    aud Tue Dec 2 12:45:17 : Shutting down partition as requested.
    aud Tue Dec 2 12:45:17 : Unloaded partition
    testacadprogoffer_CL0_Part1.
    FATAL ERROR: Out of Memory (reason = qqOS_MM_EX_OUT_OF_MEMORY)
    FATAL ERROR: Out of Memory (reason = qqOS_MM_EX_OUT_OF_MEMORY)
    Task 11: qqcm_HoseRecvServiceTask::Run: Caught unexpected exception
    FATAL ERROR: ************* Out of Memory, requested (1K) available
    (0K)
    Class: qqsp_ResourceException with ReasonCode: SP_ER_OUTOFMEMORY
    Detected at: qqos_MemoryManager
    Error Time: Tue Dec 2 12:49:01
    Exception occurred (locally) on partition "Forte_Executor",
    (partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10f3, t
    askId = [F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10f3.11]) in
    application
    "Forte Runtime", pid 14020 on node admin2 in environ
    ment CentralEnv.
    FATAL ERROR: ************* Out of Memory, requested (1K) available
    (0K)
    Class: qqsp_ResourceException with ReasonCode:
    SP_ER_OUTOFMEMORY
    Detected at: qqos_MemoryManager
    Error Time: Tue Dec 2 12:48:57
    FATAL ERROR: Out of Memory (reason = qqOS_MM_EX_OUT_OF_MEMORY)
    FATAL ERROR: Out of Memory (reason = qqOS_MM_EX_OUT_OF_MEMORY)
    ERROR: TMgr.RunThread: task cm.Recv failed terminating.
    Probably caused by a FATAL exception.
    David Wilbur email: [email protected]
    University of Windsor phone: 519-253-3000 ext. 2779
    Windsor, Ontario Canada

  • Can not view contents of variable in debug mode (version 1.1.1.5.0)

    Hi
    I am running on WebLogic 11R1 and using OEPE 1.1.1.5.0.
    When Fast swap is enabled and I run WebLogic in debug mode using OEPE I can not view the contents of variables with the Eclipse debugger. I get the message "Expressions must contain either an expression or a block containing a well formed statement"
    However, if I disable Fast swap, i can view the variable within the Eclipse debugger
    Has anyone else had this problem?
    Regards
    Steve H

    Small correction... the soon-to-be-released version of WebLogic Server that Danny was referring to is 11gR1 PatchSet 2 or 10.3.3.

  • How to fill internal table with no data in debugging mode

    Hi all,
             I modified one existing program.Now I want to test it.I am not given test data.So in the middle of my debugging, I found that one internal table with no data.My problem is how to fill that internal table with few records in that debugging mode just as we change contents in debugging mode.If I want to proceed further means that internal table must have some records.
    Please I dont know how to create test data so I am trying to create values temporarily in debugging mode only.
    Thanks,
    Balaji

    Hi,
    In the debugging do the following..
    Click the Table button..
    Double click on the internal table name..
    Then in the bottom of the screen you will get the buttons like CHANGE, INSERT, APPEND, DELETE..
    Use the APPEND button to insert records to the internal table..
    Thanks,
    Naren

  • Facing Problem while Debugging a custom report using LDB

    Hi Gurus,
    I have requirement to modify a custom report program related to FI. This program used Logical database ZDF ( Copied original DDF) for data fetching.
    when i am trying to see the data in debugging mode, its not allowing to check in start-of-selection event. only in the initialization & end-of-selection i could able to debug.
    when i put breakpoint in initialization, it is allowing to see the flow till a Get Event occurs in the code, once a Get event occur the debugger is coming out and displaying the report.
    If anybody faced this kind of problem when debugging a report using LDB, please share how you resolved it. If there are any other ways to debug a program of this kind please help me.
    Thanks,
    Nanda

    Hi Amith,
    I checked that way also, i put break point in database program of the copied LDB, but its not allowing to check the flow in that program also.
    Please suggest any other ways.
    Thanks,
    Nanda

  • Strange Error During Page Load in Debug Mode (only) - Please Help!

    Hi All,
    Data base version: oracle 11g
    Apex version: Apex 4.1.1
    Webserver: Apache
    Need help with how to troubleshoot a Critical problem. The following error only occurs during page load in "Debug" mode. And, only occurs on a specific page within the application. A web page is served-up containing the following message and the application is blocked from running the page. The browser's (IE 8.0) back button must be clicked to proceed outside of "Debug" mode.
    "Error occurred while painting error page: ORA-06502: PL/SQL: numeric or value error: character string buffer too small ORA-06502: PL/SQL: numeric or value error: character string buffer too small"
    Debug log follows:
    "S H O W: application="2006" page="6" workspace="" request="" session="500549669426301"
    Computation point: Before Header
    ...Perform computation of item: APP_SERVER, type=FUNCTION_BODY
    ...Performing function body computation
    ...Execute Statement: declare function x return varchar2 is begin return owa_util.get_cgi_env('SERVER_NAME'); return null; end; begin wwv_flow.g_computation_result_vc := x; end;
    ......Result = 156.9.122.214
    ...Session State: Save "APP_SERVER" - saving same value: "156.9.122.214"
    Processes - point: BEFORE_HEADER
    ...Process "GET_POSITION" - Type: PLSQL
    ...Execute Statement: begin wwv_flow.g_boolean := :F109_POSITION_ID IS NULL and :APP_PAGE_ID != 101; end;
    ......Result = FALSE
    ......Skip because condition or authorization evaluates to FALSE
    ...Process "Get JARS Sifter Log File Record Count" - Type: PLSQL
    ...Execute Statement: begin DECLARE vcnt NUMBER := 0; BEGIN d('Get JARS Sifter Log File Record Count'); Select count(*) into vcnt From JARS.JARS_SIFTER_LOG Where moveid = to_number(:P6_MOVEID) and sifter_status IN ('F','J'); :F1000_P6_SIFTER_LOG_COUNT := to_char(vcnt); END; end;
    Custom: Get JARS Sifter Log File Record Count
    ...Process "Set PTM Planned Trip Status" - Type: PLSQL
    ......Skip because condition or authorization evaluates to FALSE
    ...compatibility mode - do not set mime type
    ...compatibility mode - do not set additional http headers
    ...close http header
    ...metadata, fetch item type settings
    ...metadata, fetch items
    Show page template header
    Rendering form open tag and internal values
    Add error onto error stack
    ...Error data:
    ......message: Error processing request.
    ......additional_info: ORA-06502: PL/SQL: numeric or value error: character string buffer too small
    ......display_location: ON_ERROR_PAGE
    ......is_internal_error: true
    ......apex_error_code: APEX.UNHANDLED_ERROR
    ......ora_sqlcode: -6502
    ......ora_sqlerrm: ORA-06502: PL/SQL: numeric or value error: character string buffer too small
    ......error_backtrace: ORA-06512: at "APEX_040100.WWV_FLOW", line 3027 ORA-06512: at "APEX_040100.WWV_FLOW", line 7867
    ...Show Error on Error Page
    ......Performing rollback
    Rendering form open tag and internal values
    ...Unhandled Error while painting error page: ORA-06502: PL/SQL: numeric or value error: character string buffer too small ORA-06502: PL/SQL: numeric or value error: character string buffer too small
    ...Error Backtrace: ORA-06512: at "APEX_040100.WWV_FLOW", line 2707 ORA-06512: at "APEX_040100.WWV_FLOW_ERROR", line 185
    End Page Rendering"
    Thanks!
    Bernard

    All,
    It appears that the page Javascript maximum limit size was reached. The error stopped appearing after some of the page Javascript code was removed out to Application Static Files. I wonder if there exists any "direct" indicator by the system whenever the size limit has been reached?
    Again, the run error only occurred when the page was loaded in "Debug" mode.
    Bernard

Maybe you are looking for