11 Replies Latest reply: Sep 23, 2013 9:27 AM by Christian Neumueller-Oracle RSS

    APEX 4.2.2 upgrade issue

    user647819

      Hi ,

      We have upgraded our apex installation from APEX 4.0.2 to 4.2.2 and APEX listener to 2.0.2

      Below is our configuration

      Host 1 : Oracle database
      Oracle database - 10.2.0.5
      APEX - 1.1.3


      Host 2 : Apex listener on Weblogic server
      Weblogic server - 10.3.5
      APEX listener - 2.0.2


      Post the upgrade , applications that were existing before the upgrade are not working properly.
      Errors faced:
      1.When we edit any page in application - we get no data found error
      2. When we run any application - We get no data found error

      We are able to create new applications without any issues.Luckily , we had the export backup of one application taken before upgrade. We imported that back( only one application ) and that application is working fine. We imported the application in apex.oracle.com as well and get the same error.

      http://apex.oracle.com/pls/apex/f?p=20593::112257356489653

      Error occurs during page 'Edit' as well.

      Please help us identifying and fixing the issue.

       

      Regards

      Sathya


        • 1. Re: APEX 4.2.2 upgrade issue
          Jens Marre

          Sathya,

           

          have you checked the debug log? If you cannot access it in the browser check

           

          select *

          from apex_debug_messages

          order by id desc;

           

          May be increase the log level using

           

          APEX_DEBUG_MESSAGE.ENABLE_DEBUG_MESSAGES;

           

          Also you may check the trace file using p_trace=YES

          10 Debugging an Application

           

          Jens

          • 2. Re: APEX 4.2.2 upgrade issue
            user647819

            Hi ,

            Thanks for your support.

             

            I wasn't successful in getting the debug logs.

             

            1. Tried p_trace with f?p . No trace files generated in database user_dump_dest

            2. Set log level to 7 using APEX_DEBUG_MESSAGE. No debug messages were found in the table.

            Is it possible to set debug for  specific application-page level using pl/sql packages?

             

            1.Meanwhile , we compared the export output of the application taken before and after the upgrade. We see that many details are missing in the export taken after upgrade.

            In the export file  - For every page in application, we see the pl/sql in the below order

            wwv_flow_api.create_page - Present in both

            wwv_flow_api.create_page_plug - Present in both

            wwv_flow_api.create_worksheet - Present

            wwv_flow_api.create_worksheet_column - This is completely missing in the export taken after upgrade for all pages.

            Exports were taken just before and after the upgrade

             

            2. When we Edit any page in the application we get the error -

             

            Error during rendering of region "Page rendering"

            ORA-01403: no data found

             

             

            Regards

            Sathya

            • 3. Re: APEX 4.2.2 upgrade issue
              Jens Marre

              As for the debugging:

               

              I guess you are not running a runtime-only apex installation.

               

              • Have you checked background_dump_dest as well for the trace file?
              • Is debugging enabled in your application properties?
              • Further: Have you enabled debugging in the URL for the debug messages? (10 Debugging an Application)?

               

              I have no idea about the syntax of the export file.

               

              Jens

              • 4. Re: APEX 4.2.2 upgrade issue
                K Cannell

                We have the same issue in our new environment, using the APEX Listener 2.0.2:

                 

                APEX 4.2.3

                Glassfish 4.0

                APEX listener - 2.0.2

                DB 11.2


                The gotcha is, ONE of our apps works, the others give the no data found error on page processing.


                For Debug messages, we get them all for the Login page render (the Show), but we get no Accept debug messages.

                Firebug shows the POST looks OK, as it should, then an immediate GET with the simple error page and a GET of error.gif.  It looks like nothing gets processed at all.


                No trace file gets generated.


                The app that works was built more recently.

                The apps all use the same open door authentication policy.

                All the apps use the same theme.


                I am running out of things ot try ..

                Thought, suggestions anyone?







                • 5. Re: APEX 4.2.2 upgrade issue
                  Christian Neumueller-Oracle

                  Hi,

                   

                  if there is indeed no processing of the accept request, maybe the APEX listener's log output can give you some hints.

                   

                  Since show works, you could also set LEVEL9 debug in the URL before submitting the page, to get APEX engine internal debug output.

                   

                  Regards,
                  Christian

                  • 6. Re: APEX 4.2.2 upgrade issue
                    K Cannell

                    Thanks Christian - again. no debug info is generated at all, no matter what level. The stop is before then.

                    Am reviewing the APEX Listener logs w the sys admin.

                     

                    The same apps work fine in my Windows-based APEX 4.2, Glassfish 3.2, APEX Listener 2.0.2.

                    I'll upgrade tonight so my env is the same versions. If I can force the same issue locally I have free reign over the logs.

                     

                    The killer is that now 2 apps work, the rest give the error.

                    Am still looking for the common denominator that causes the difference.

                    Have examined debug logs in the old env, to see what should be generated. Nothing odd there. It seem in the new env,  it just never gets to the Accept at all.

                     

                    Back to the APEX Listener logs ...

                    Will post when I figure this out.

                    • 7. Re: APEX 4.2.2 upgrade issue
                      K Cannell

                      An update -

                      We are actually on APEX 4.2.3, APEX Listener 2.0.3

                      I have verified that some apps work, and some apps show the

                       

                      Error Error processing request

                              ORA-01403: no data found

                      error.

                       

                      Happens across different workspaces.

                      Happens in a Linux environment and in a Windows environment.

                       

                      Have confirmed that for apps  that have the error,

                         I get the error using the APEX Listener deployment.

                         I do NOT get the error using the HTTP server deployment

                       

                      For one app, I have an earlier version that gives the error, a later version (new app #) that does not give the error.

                      APEX 4.2.3

                      APEX Listener 2.0.3.221.10/3

                      Glassfish 4.0

                       

                      Again even at  Debug Level 9, I get no debug entries for the POST

                       

                      For an app that gives the error, the APEX Listener log entries are (from the POST):

                       

                      ==== Processing Request: ====

                      Attempting to process with PL/SQL Gateway

                      user-agent: Mozilla/5.0 (Windows NT 5.1; rv:23.0) Gecko/20100101 Firefox/23.0

                      host: qdcls1534:8082

                      Applied database connection info

                      POST /apex/apexd2/wwv_flow.accept

                      ==== Headers in Request ====

                      ==== Cookies in Request ====

                      content-length: 412

                      content-type: application/x-www-form-urlencoded;charset=UTF-8

                      request parameter: p_flow_id=440

                      request parameter: p_flow_id=440

                      request parameter: p_flow_step_id=101

                      request parameter: p_instance=1712832201985

                      request parameter: p_instance=1712832201985

                      request parameter: p_page_submission_id=8493461183923

                      request parameter: p_page_submission_id=35145982114211

                      request parameter: p_request=LOGIN

                      request parameter: p_request=

                      request parameter: p_debug=LEVEL9

                      request parameter: p_debug=LEVEL9

                      request parameter: p_arg_names=13616030313099104709

                      request parameter: p_arg_names=13616030522289104711

                      request parameter: p_t01=karen.x.cannell

                      request parameter: p_t02=sssssssss

                      request parameter: p_md5_checksum=

                      request parameter: p_page_checksum=C2302553B43577579FF77585749CA016

                      Using Procedure:wwv_flow.accept

                      request parameter: p_flow_step_id=101

                      Requesting Pool:apexd2

                      pool exists: apexd2

                      isValidRequest(), procedure name: <wwv_flow.accept>

                      Validating: wwv_flow.accept

                      *** Total number of arguments: 510

                      SID: 214

                      *** Total number of arguments: 510

                      "-----

                      begin

                      wwv_flow.accept(p_flow_step_id=>?,

                      p_md5_checksum=>?,

                      p_arg_names=>?,

                      p_page_checksum=>?,

                      p_t02=>?,

                      p_t01=>?,

                      p_debug=>?,

                      p_request=>?,

                      p_page_submission_id=>?,

                      p_flow_id=>?,

                      p_instance=>?);

                      commit;

                        end;"

                      Parse: 0 ms

                      p_flow_step_id= null

                      p_flow_step_id=[101, 101]

                      {p_md5_checksum=, p_page_submission_id=[8493461183923, 35145982114211], p_debug=[LEVEL9, LEVEL9], p_page_checksum=C2302553B43577579FF77585749CA016, p_request=[LOGIN, ], p_t02=sssssssss, p_t01=karen.x.cannell, p_flow_id=[440, 440], p_instance=[1712832201985, 1712832201985], p_flow_step_id=[101, 101], p_arg_names=[13616030313099104709, 13616030522289104711]}

                      p_request=[LOGIN, ]

                      p_md5_checksum=

                      {p_md5_checksum=, p_page_submission_id=[8493461183923, 35145982114211], p_debug=[LEVEL9, LEVEL9], p_page_checksum=C2302553B43577579FF77585749CA016, p_request=[LOGIN, ], p_t02=sssssssss, p_t01=karen.x.cannell, p_flow_id=[440, 440], p_instance=[1712832201985, 1712832201985], p_flow_step_id=[101, 101], p_arg_names=[13616030313099104709, 13616030522289104711]}

                      p_arg_names=[13616030313099104709, 13616030522289104711]

                      p_arg_names: {13616030313099104709, 13616030522289104711}

                      {p_md5_checksum=, p_page_submission_id=[8493461183923, 35145982114211], p_debug=[LEVEL9, LEVEL9], p_page_checksum=C2302553B43577579FF77585749CA016, p_request=[LOGIN, ], p_t02=sssssssss, p_t01=karen.x.cannell, p_flow_id=[440, 440], p_instance=[1712832201985, 1712832201985], p_flow_step_id=[101, 101], p_arg_names=[13616030313099104709, 13616030522289104711]}

                      {p_md5_checksum=, p_page_submission_id=[8493461183923, 35145982114211], p_debug=[LEVEL9, LEVEL9], p_page_checksum=C2302553B43577579FF77585749CA016, p_request=[LOGIN, ], p_t02=sssssssss, p_t01=karen.x.cannell, p_flow_id=[440, 440], p_instance=[1712832201985, 1712832201985], p_flow_step_id=[101, 101], p_arg_names=[13616030313099104709, 13616030522289104711]}

                      p_instance= null

                      p_instance=[1712832201985, 1712832201985]

                      {p_md5_checksum=, p_page_submission_id=[8493461183923, 35145982114211], p_debug=[LEVEL9, LEVEL9], p_page_checksum=C2302553B43577579FF77585749CA016, p_request=[LOGIN, ], p_t02=sssssssss, p_t01=karen.x.cannell, p_flow_id=[440, 440], p_instance=[1712832201985, 1712832201985], p_flow_step_id=[101, 101], p_arg_names=[13616030313099104709, 13616030522289104711]}

                      p_flow_id= null

                      p_flow_id=[440, 440]

                      {p_md5_checksum=, p_page_submission_id=[8493461183923, 35145982114211], p_debug=[LEVEL9, LEVEL9], p_page_checksum=C2302553B43577579FF77585749CA016, p_request=[LOGIN, ], p_t02=sssssssss, p_t01=karen.x.cannell, p_flow_id=[440, 440], p_instance=[1712832201985, 1712832201985], p_flow_step_id=[101, 101], p_arg_names=[13616030313099104709, 13616030522289104711]}

                      p_page_submission_id= null

                      p_page_submission_id=[8493461183923, 35145982114211]

                      {p_md5_checksum=, p_page_submission_id=[8493461183923, 35145982114211], p_debug=[LEVEL9, LEVEL9], p_page_checksum=C2302553B43577579FF77585749CA016, p_request=[LOGIN, ], p_t02=sssssssss, p_t01=karen.x.cannell, p_flow_id=[440, 440], p_instance=[1712832201985, 1712832201985], p_flow_step_id=[101, 101], p_arg_names=[13616030313099104709, 13616030522289104711]}

                      p_request= null

                      p_md5_checksum=

                      {p_md5_checksum=, p_page_submission_id=[8493461183923, 35145982114211], p_debug=[LEVEL9, LEVEL9], p_page_checksum=C2302553B43577579FF77585749CA016, p_request=[LOGIN, ], p_t02=sssssssss, p_t01=karen.x.cannell, p_flow_id=[440, 440], p_instance=[1712832201985, 1712832201985], p_flow_step_id=[101, 101], p_arg_names=[13616030313099104709, 13616030522289104711]}

                      p_debug= null

                      p_debug=[LEVEL9, LEVEL9]

                      {p_md5_checksum=, p_page_submission_id=[8493461183923, 35145982114211], p_debug=[LEVEL9, LEVEL9], p_page_checksum=C2302553B43577579FF77585749CA016, p_request=[LOGIN, ], p_t02=sssssssss, p_t01=karen.x.cannell, p_flow_id=[440, 440], p_instance=[1712832201985, 1712832201985], p_flow_step_id=[101, 101], p_arg_names=[13616030313099104709, 13616030522289104711]}

                      p_t01= karen.x.cannell

                      p_t01=karen.x.cannell

                      {p_md5_checksum=, p_page_submission_id=[8493461183923, 35145982114211], p_debug=[LEVEL9, LEVEL9], p_page_checksum=C2302553B43577579FF77585749CA016, p_request=[LOGIN, ], p_t02=sssssssss, p_t01=karen.x.cannell, p_flow_id=[440, 440], p_instance=[1712832201985, 1712832201985], p_flow_step_id=[101, 101], p_arg_names=[13616030313099104709, 13616030522289104711]}

                      p_t02= sssssssss

                      p_t02=sssssssss

                      {p_md5_checksum=, p_page_submission_id=[8493461183923, 35145982114211], p_debug=[LEVEL9, LEVEL9], p_page_checksum=C2302553B43577579FF77585749CA016, p_request=[LOGIN, ], p_t02=sssssssss, p_t01=karen.x.cannell, p_flow_id=[440, 440], p_instance=[1712832201985, 1712832201985], p_flow_step_id=[101, 101], p_arg_names=[13616030313099104709, 13616030522289104711]}

                      p_page_checksum= C2302553B43577579FF77585749CA016

                      p_page_checksum=C2302553B43577579FF77585749CA016

                      Exec: 37 ms

                      ==== Headers from Results ====

                      Setting Content-Type (Content-type): text/html; charset=UTF-8

                      Got results length: 307

                      Processed PL/SQL Gateway request

                      ==== Request Processed ====

                       

                      It just stops ...

                       

                      Any ideas?

                       

                      I have tried all of the Compatibility settings, no difference.

                       

                      If it is something I can change in the app, that would be great.

                       

                      The app that does not work was imported from an APEX 4.1, HTTP server instance. This export/import was done twice, just to make sure there was no hiccup.

                      The app that does work was imported from an APEX 4.2.3, APEX Listener 2.0.3 instance.

                       

                      Since the failure is on the Login page -  I cannot get past that - I have compared the Login pages and have found no differences.  Same with App Items, App Computations and App Processes.  In this one case, where I was lucky enough to find two version of the same app, one that works, one that doesn't,  the difference in the app is added pages and List menu items;  no changes to existing pages, including the Login page.

                       

                      Am still looking, but seem to have narrowed the key piece to use of the APEX Listener 2.0.3.

                      Will post when I figure this out - in the meantime I am open to suggestions,

                       

                      Oh yes, and I have posted this to the APEX Listener forum.

                       

                      Thank you - Karen

                      .

                      • 8. Re: APEX 4.2.2 upgrade issue
                        K Cannell

                        Sorry for the multiple posts - browser timeout issue, apparently.

                        • 9. Re: APEX 4.2.2 upgrade issue
                          Christian Neumueller-Oracle

                          Hi Karen,

                           

                           

                          thanks for the APEX Listener output. This looks weird, it seems like some parameters were passed multiple times (p_flow_id, p_instance, p_page_submission_id, p_debug). Are you maybe using some JavaScript that duplicates parts of the DOM tree? I would first check whether items on the login page are actually duplicated, e.g. with

                           

                            $("input").each(function() { console.log(this.name); });

                           

                          in Chrome Dev Tools / Firebug, etc.

                           

                          If there are no duplicate items, this could be an issue with Glassfish / APEX Listener. You could try with APEX Listener standalone, to further isolate the problem.

                           

                          Regards,

                          Christian

                          • 10. Re: APEX 4.2.2 upgrade issue
                            K Cannell

                            Got - Christian, thank you!

                             

                            The JS showed the problem - indeed there were multiple sets of some parameters getting passed.

                            ( I thought that odd, due to how the log was output - I'm getting the output via an external table since I do not have access to that server).

                             

                            Once I saw the duplicates,

                            I found the cause quickly - two #FORM_OPEN directives in the page template.

                            That is an old issue for us (from an old template) that I thought had been removed from all our apps - apparently not all.

                            Time for some housekeeping!

                             

                            Thank you - I owe you one,

                            Karen

                            • 11. Re: APEX 4.2.2 upgrade issue
                              Christian Neumueller-Oracle

                              Hi Karen,

                               

                              great that you found the problem (and that it's not a bug in APEX). Btw, can you please close the APEX Listener forum thread?

                               

                              Thanks,

                              Christian