6 Replies Latest reply: Aug 26, 2013 6:51 AM by NoGot RSS

    Possible bug in export of static files in v4.1.1.00.23?

    20020
      Hello all,

      We recently updated to version 4.1.1.00.23, and need to do an export of our static files to migrate from our development to test (ApEx run-time) platform. When our DBA attempted to run the export script (we had renamed it from static_file.sql to browser_detect.sql), he received this error:

      SQL> @browser_detect.sql
      Set Credentials...
      Check Compatibility...
      Set Application ID...
      ...static file repository
      p_notes=> '');
      *
      ERROR at line 14:
      ORA-06550: line 14, column 5:
      PLS-00103: Encountered the symbol "P_NOTES" when expecting one of the following:

      . ( ) , * % & = - + < / > at in is mod remainder not rem
      <an exponent (**)> <> or != or ~= >= <= <> and or like LIKE2_
      LIKE4_ LIKEC_ between || multiset member SUBMULTISET_
      The symbol "(" was substituted for "P_NOTES" to continue.
      ORA-06550: line 14, column 18:
      PLS-00103: Encountered the symbol ";" when expecting one of the following:
      . ( ) , * % & = - + < / > at in is mod remainder not rem
      <an exponent (**)> <> or != or ~= >= <= <> and or like LIKE2_
      LIKE4_ LIKEC_ between || multiset

      We took a look at static_file.sql, and noticed this:
      declare
        l_name    varchar2(255);
        l_html_id number := null;
      begin
        l_name := 'browser_detect.js';
        wwv_flow_html_api.remove_html(
          p_html_name => l_name,
          p_flow_id   => nvl(wwv_flow.g_flow_id, 0) );
        l_html_id := wwv_flow_html_api.new_html_repository_record(
          p_name=> l_name,
          p_varchar2_table=> wwv_flow_image_api.g_varchar2_table,
          p_mimetype=> 'application/x-javascript',
          p_flow_id=> nvl(wwv_flow.g_flow_id, 0)
          p_notes=> 'Browser detection routines');
       
      end;
      /
      The comma is missing after the p_flow_id parameter. This appears to be a bug in the export. It appears to be happening pretty consistently (other static files for this application, other static files for other existing applications).

      I did a search of the forum to see if anyone else has reported this and checked the known issues listing on OTN and I don't see any reference to this particular issue. Has anyone else run into this? We're hesitant to just add the comma right now since we don't know whether there may be any other issues in the file it's generating.

      We'll be logging a bug report but as a workaround, does anyone know if the problem is just this missing comma?

      Thanks much!!
      John