Oracle DB 19c installed inside my Azure VM and it is not connected to the Azure Webapp.

20591256 1 Reputation point
2021-12-14T07:22:51.913+00:00

I had installed Oracle Database 19c locally on my Azure Virtual Machine. I had export some data dump in that DB using the SID name "BTM". And I deployed Webapp service in the same Resource Group and Same Region. The VNet also integrated. But it shows the error while run the webapp, the JDBC not connected to the webapp, it shows connection timed out. The public IP is not pinging.

Azure Virtual Machines
Azure Virtual Machines
An Azure service that is used to provision Windows and Linux virtual machines.
7,157 questions
Azure App Service
Azure App Service
Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
6,907 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. ajkuma 22,416 Reputation points Microsoft Employee
    2022-01-03T14:07:34.093+00:00

    20591256, Firstly, apologies for the long delay on this. To better assist you on this, I would like to know the following details (will follow-up with you offline for a focused assistance):

    What is the complete error message you receive? How exactly are you testing the connectivity?

    --You need to ensure that you have both your Oracle VM and Linux App Service to that VNET utilizing service endpoints.
    You may append the configuration in app settings, or set the environment variables in the Configuration > Application Settings page in the Azure portal - as outlined on this document.

    --On App Service - There are two consoles that you can use for testing. One is the Kudu console, and the other is the console in the Azure portal.
    To reach the Kudu console from your app, go to Tools > Kudu. You can also reach the Kudo console at [sitename].scm.azurewebsites.net.

    --In native Windows Azure WebApp Apps, the tools ping, nslookup, and tracert won't work through the console because of security constraints. To test DNS functionality, you may use nameresolver.exe

    --A number of things can prevent your app from reaching a specific host and port. Most of the time it's one of these things:

    • A firewall is in the way. If you have a firewall in the way, you hit the TCP timeout. The TCP timeout is 21 seconds in this case. Use the tcpping tool to test connectivity. TCP timeouts can be caused by many things beyond firewalls, but start there.
    • DNS isn't accessible. The DNS timeout is 3 seconds per DNS server. If you have two DNS servers, the timeout is 6 seconds. Use nameresolver to see if DNS is working. You can't use nslookup, because that doesn't use the DNS your virtual network is

    Integrate your app with an Azure virtual network

    Troubleshoot virtual network peering issues

    --Additionally,
    Check the blog Using Azure App Services with Hybrid Connections – demonstrates on connecting Azure App Services with an on-premises Oracle Server and on-premises SQL Server using Azure App Service hybrid connections.

    If the issue persists, kindly let us know I’ll follow-up with you privately and help provide an immediate and focused assistance.

    0 comments