📋

Description

The ORA-29269 error indicates that the Oracle database received an error response from an HTTP server. This typically occurs when the database attempts to make an HTTP request using packages like `UTL_HTTP` or `UTL_URL` and the remote server encounters a problem.

💬

Error Message

HTTP server error string

🔍

Known Causes

4 known causes

⚠️

Server Unavailable

The remote HTTP server is down or unreachable due to network issues or server maintenance.

⚠️

Invalid URL

The URL specified in the HTTP request is incorrect or does not exist on the remote server.

⚠️

Server-Side Error

The remote HTTP server encountered an internal error (e.g., 500 Internal Server Error) while processing the request.

⚠️

Authentication Failure

The HTTP request requires authentication, but the provided credentials are invalid or missing.

🛠️

Solutions

4 solutions available

1. Verify Oracle HTTP Server (OHS) Configuration medium

Ensures the OHS configuration correctly points to the Oracle Database listener and is running.

1

Locate the OHS configuration file. This is typically named `httpd.conf` and is found in the `$ORACLE_INSTANCE/config/OHS/component_name/` directory.

2

Examine the `Listen` directive to ensure it's configured for the correct port and IP address that your Oracle Database listener is using. Also, check `VirtualHost` configurations if applicable.

Listen 127.0.0.1:80

3

Verify the `mod_plsql` configuration, if you are using it for PL/SQL calls. Ensure the `PlsqlDocumentPath` and `PlsqlConnect` parameters are correctly set to point to your database.

PlsqlDocumentPath /pls/
PlsqlConnect scott/tiger@orcl

4

Restart the Oracle HTTP Server to apply any changes.

cd $ORACLE_INSTANCE/bin
./opmnctl restartproc process-type=HTTPD

2. Check Oracle Database Listener Status and Configuration easy

Confirms the Oracle Database listener is running and configured to accept connections from OHS.

1

Log in to the Oracle Database server where the listener is running.

2

Check the status of the Oracle Net Listener.

lsnrctl status

3

If the listener is not running, start it.

lsnrctl start

4

Verify the `listener.ora` file (usually located in `$ORACLE_HOME/network/admin/`) contains an entry for the service name that OHS is trying to connect to, and that the host and port are correct.

LISTENER =
  (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = your_db_host)(PORT = 1521))
  )

SID_LIST_LISTENER =
  (SID_LIST =
    (SID_DESC =
      (SID_NAME = your_db_sid)
      (ORACLE_HOME = /path/to/oracle/home)
    )
  )

5

If `listener.ora` was modified, reload the listener configuration.

lsnrctl reload

3. Review OHS and Database Logs for Detailed Errors medium

Inspect relevant log files for more specific error messages that can pinpoint the root cause.

1

Locate the Oracle HTTP Server logs. These are typically found in `$ORACLE_INSTANCE/diagnostics/logs/OHS/component_name/`. Key files include `access_log`, `error_log`, and `application.log`.

2

Examine the Oracle Database alert log. This is usually located in `$ORACLE_BASE/diag/rdbms/db_name/instance_name/trace/alert_<instance_name>.log`.

3

Search for entries around the time of the ORA-29269 error in both OHS and database logs. Look for related error codes, stack traces, or descriptive messages.

tail -f $ORACLE_INSTANCE/diagnostics/logs/OHS/component_name/error_log

4

If the error involves `mod_plsql` or specific PL/SQL packages, review the `mod_plsql` specific logs if available, or enable tracing for the relevant PL/SQL procedures.

4. Validate Network Connectivity Between OHS and Database Server easy

Ensures that the OHS server can reach the database listener over the network.

1

From the Oracle HTTP Server machine, attempt to connect to the Oracle Database listener's host and port using `tnsping`.

tnsping your_db_service_name

2

If `tnsping` fails, verify that there are no firewall rules blocking traffic between the OHS server and the database server on the listener port (default 1521).

3

Use `telnet` or `nc` (netcat) to test basic TCP connectivity to the listener port.

telnet your_db_host 1521

4

Confirm that the `tnsnames.ora` file on the OHS server is correctly configured with the database service name and connection details.

Oracle HTTP Server Error