Informix Error -29002: Supplied real-RDB-name does not match the real-RDB-name in sqlhosts.
Cause and resolution
Supplied real-RDB-name does not match the real-RDB-name in sqlhosts.
A mismatch was detected between the user-supplied real-RDB-name and the real-RDB-name that was derived from the user-supplied alias-RDB-name using the sqlhosts file.
Check the spelling of the user-supplied real-RDB-name. Ensure that the user-supplied alias-RDB-name is the correct one.
If SNA network protocol is used to connect to the application server, check the real-RDB-name column (the "hostname" field) in the "sqlhosts" file for the alias-RDB-name entry, and check that it is spelled correctly.
If TCP/IP network protocol is used to connect to the application server, check the "RDB=real-RDB-name" option (in the "options" field) in the "sqlhosts" file for the alias-RDB-name entry, and check that it is spelled correctly.
Oninit® Troubleshooting Guidance
Reasons / Common Causes
-29002 fires when a user-supplied real-RDB-name doesn't match the one sqlhosts derives
from the user-supplied alias-RDB-name — per the official guidance.
- A misspelled
real-RDB-name, per the official guidance — the first named cause. - The wrong
alias-RDB-namesupplied, per the official guidance — the second named cause.
Solutions / Resolution
- Check the spelling of the supplied
real-RDB-name, per the official guidance. - On SNA: check the
hostnamefield for thealias-RDB-nameentry insqlhosts, per the official guidance. - On TCP/IP: check the
RDB=real-RDB-nameoption in theoptionsfield for thealias-RDB-nameentry insqlhosts, per the official guidance.
Examples
N/A
No specific triggering statement is documented beyond a real-RDB-name mismatch.
Diagnostic Checks
- Check the
sqlhostsentry for thealias-RDB-name, on its protocol-appropriate field (hostnamefor SNA,RDB=option for TCP/IP).
Related Errors / Related Topics
- -29003 — "RDB real-RDB-name not found at the application server." A related
real-RDB-name error, on the application server's own mismatch rather than a client-side
sqlhostsdiscrepancy.
The supplied real-RDB-name didn't match the one derived from sqlhosts — check spelling
and the protocol-appropriate sqlhosts field.