Oninit
Talk to an expert →

Informix Error -29003: RDB real-RDB-name not found at the application server.

Cause and resolution

RDB real-RDB-name not found at the application server.

Although a communication conversation was allocated, the application server refused to connect because it has a real-RDB-name that is different from that to which the application would like to connect.

Examine the sqlhosts file on the Gateway computer. Identify the entry with the alias-RDB-name to which the application is referring.

If SNA network protocol is used to connect to the application server, ensure that the "hostname" field contains a correct value.

If TCP/IP network protocol is used to connect to the application server, ensure that the "RDB=real-RDB-name" option in the "options" field contains a correct value.

Oninit® Troubleshooting Guidance

Reasons / Common Causes

-29003 fires when the application server refuses a connection because its own real-RDB-name differs from the one the application is trying to reach — per the official guidance, this happens even though a communication conversation was successfully allocated.

  1. A mismatched real-RDB-name at the application server, per the official guidance — the direct, only cause.
Solutions / Resolution
  1. Check the sqlhosts file on the Gateway computer for the alias-RDB-name entry, per the official guidance.
  2. On SNA: confirm the hostname field is correct, per the official guidance.
  3. On TCP/IP: confirm the RDB=real-RDB-name option is correct, per the official guidance.
Examples
N/A

No specific triggering statement is documented beyond a real-RDB-name mismatch at the application server.

Diagnostic Checks
  1. Check the Gateway computer's sqlhosts entry for the alias-RDB-name, on its protocol-appropriate field.
Related Errors / Related Topics
  • -29002 — "Supplied real-RDB-name does not match the real-RDB-name in sqlhosts." A related real-RDB-name error, on a client-side sqlhosts mismatch rather than the application server's own value.

The application server's real-RDB-name didn't match the target — check the Gateway computer's sqlhosts entry.