Error: 4535

The DB_Connect function can issue this obscure error message when there is trouble connecting to your database. Consistent appearance of this message may indicate that your database cannot be found, or that the interface programs ("listeners") to the database have not been started. If your scripts worked yesterday, but not today, first try closing QA Partner, end your UNIX login, log back in and try again. If you still have problems, work with your database administrator.

If you are attempting to connect for the first time, compare the spelling of your data source name (DSN) in your DB_Connect function call against your ODBC definition. They should have the same DSN.

On Windows platforms you get to the ODBC definitions via the Control Panel. Oracle databases have an ODBC configuration field called "SQL*Net Connect String". This field should have a single word name of the server that has your database. Oracle then looks for this name in the tnsnames.ora file. This file is located in the directory identified in the registry under HKEY_LOCAL_MACHINE, Software, Oracle, TNS_ADMIN. It is likely that only your network or database administrators can change this file. As a temporary work-around you may want to copy this file to a local directory and change the registry entry to point to that directory. This is dangerous since you will no longer be using the version maintained by your administrators. Be sure to restore your registry when your administrator has updated the network copy of tnsnames.ora.

On at least some UNIX platforms there is either a ".odbc.ini" or "odbc.ini" file in your home directory that you may edit directly. Check your environment variables first. You may find an "ODBC_INI" variable that defines a shared ODBC ini file.

If you get this message intermittently, it may be due to Domain Name System (DNS) problems. If your primary server is busy and your backup server is not up-to-date you can get this message intermittently. Call your systems administrator to verify that all DNS servers are synchronized with the latest information and that your configuration identifies the appropriate servers.
4Test Solution - If you want to cope with intermittent problems in establishing a database connection, you can invoke the DB_Connect function from a do...except clause within a loop. Be sure to include a time-out or limit on the number of attempts.
TestMap Extensions Solution - The TmDbConnect recovers from intermittent database connection problems. If the connection cannot be established, an exception is raised. If the connection fails at first but is later established, a warning message is included in the results file. This approach allows your test scripts to function while testing your applications in situations where the database connection may not always work.