3 Replies Latest reply on Jun 19, 2013 3:43 PM by sb92075

    ORA-29273: HTTP request failed ORA-12535: TNS:operation timed out

    1001371

      SQL*Plus: Release 11.2.0.3.0

      Solaris 10 SPARC

       

      Hi,

       

      I get the following error when trying to make an HTTP request. Below is the snippet of code I run. I get the error after exactly 60 seconds(default timeout?). I searched through the forums and found many similar errors but nothing that helped me resolve this issue. The problem does not exist in the rest of our environments, only our test environment.

       

      Help is greatly appreciated. Thanks.

       

      DECLARE
         p_mid_tier    VARCHAR2 (500);
         responsestr   VARCHAR2 (500);
      BEGIN
         --
         SELECT *****
           INTO p_mid_tier
           FROM *****
          WHERE profile_type = '*****';
      
         --
         UTL_HTTP.set_wallet ('file://$ORACLE_HOME/network/admin/wallets');
         UTL_HTTP.set_transfer_timeout (6000);
         UTL_HTTP.set_response_error_check (TRUE);
         responsestr :=
            UTL_HTTP.request (
               UTL_URL.ESCAPE (p_mid_tier || '*****'));
         DBMS_OUTPUT.put_line (responsestr);
      END;
      /
      

       

       

      ORA-29273: HTTP request failed

      ORA-06512: at "SYS.UTL_HTTP", line 1722

      ORA-12535: TNS:operation timed out

      ORA-06512: at line 15

        • 1. Re: ORA-29273: HTTP request failed ORA-12535: TNS:operation timed out
          sb92075

          1001371 wrote:

           

          SQL*Plus: Release 11.2.0.3.0

          Solaris 10 SPARC

           

          Hi,

           

          I get the following error when trying to make an HTTP request. Below is the snippet of code I run. I get the error after exactly 60 seconds(default timeout?). I searched through the forums and found many similar errors but nothing that helped me resolve this issue. The problem does not exist in the rest of our environments, only our test environment.

           

          Help is greatly appreciated. Thanks.

           

          1. DECLARE 
          2.    p_mid_tier    VARCHAR2 (500); 
          3.    responsestr   VARCHAR2 (500); 
          4. BEGIN 
          5.    -- 
          6.    SELECT ***** 
          7.      INTO p_mid_tier 
          8.      FROM ***** 
          9.     WHERE profile_type = '*****'
          10.    -- 
          11.    UTL_HTTP.set_wallet ('file://$ORACLE_HOME/network/admin/wallets'); 
          12.    UTL_HTTP.set_transfer_timeout (6000); 
          13.    UTL_HTTP.set_response_error_check (TRUE); 
          14.    responsestr := 
          15.       UTL_HTTP.request ( 
          16.          UTL_URL.ESCAPE (p_mid_tier || '*****')); 
          17.    DBMS_OUTPUT.put_line (responsestr); 
          18. END

           

           

          ORA-29273: HTTP request failed

          ORA-06512: at "SYS.UTL_HTTP", line 1722

          ORA-12535: TNS:operation timed out

          ORA-06512: at line 15

           

          the most frequent cause for TIMEOUT is a FireWall on or between client & server.

           

          when was last time this worked without error?

          what changed since then?

          • 2. Re: ORA-29273: HTTP request failed ORA-12535: TNS:operation timed out
            1001371

            I should have mentioned. The biggest difference between this environment and others is that it is our new Fusion MW testing environment. It has never worked on this environment. Our non-fusion environment had the same issue where it would work sometimes and not other times. The strange thing was that it went away all of the sudden. We don't have the issue anymore in the non-fusion environment. 

            • 3. Re: ORA-29273: HTTP request failed ORA-12535: TNS:operation timed out
              sb92075

              1001371 wrote:

               

              I should have mentioned. The biggest difference between this environment and others is that it is our new Fusion MW testing environment. It has never worked on this environment. Our non-fusion environment had the same issue where it would work sometimes and not other times. The strange thing was that it went away all of the sudden. We don't have the issue anymore in the non-fusion environment.

               

              consider to packet sniff to see where the breakdown occurs.