Troubleshooting

Host Configuration

Reality Networking on UNIX

Check the following:

• /etc/hosts file. This must contain an entry with the network name of the UNIX host similar to:

  192.168.1.20  zeus

  where 192.168.1.20 is the host’s internet (IP) address and zeus is its network name. You can display the network name by entering the uname -n  command.

• /etc/ROUTE-FILE routing entries. These are normally set up automatically and should not need to be changed.

  • Reality entry for the database which is to form the data source.

    For example, for the database SQL_dbase on the host zeus:

    System name        : ZeusSql
    Entry type         : Reality
    Database path      : /user0/realman/SQL_dbase
    REALROOT path      : 
    Executable path    : 
    Comment            : SQL_dbase database

    Note that the characters “[ ] { } ( ) , ; ? * = ! @ \” should not be used in the ROUTE-FILE entry for a Reality SQL/ODBC data source. Use of these characters may result in a RealSQL connection failure.

  • Listening entry for DDA connections.

    The following shows an example of a listening entry:

    System name        : Zeus_TCP
    Entry type         : listening
    Device             : /dev/rcs/tcp0
    Interface type     : TLI
    Provider type      : TCP
    Port Number        : 1203
    Host Name          : zeus
    Network info       : 
    Comment            :

    For more details, refer to The ROUTE-FILE in UNIX-Connect System Administration.

Reality Networking on Windows

Use the netadmin utility to check that the following routing entries have been set up in the Windows Registry:

• Remote Database entry for the database which is to form the data source.
• Listening entry for DDA connections.

For details, see the description of the Network Administration Utility (netadmin) in the User’s Reference: Administration.

Reality User-id

Check the following:

• On a UNIX host, check that the user has a UNIX user-id and password, that their Reality user-id is the same as their UNIX user-id.
• Use SSM option 2 (Define User Profiles) to check that the Reality user-id has been set up to operate in server mode.

SQL/ODBC

• If connecting to a UNIX host, check that the appropriate UNIX user-id and password has been entered in the ODBC data source definition. Check also that there is a Reality user-id with the same name.
• If connecting to a Windows host, check that the appropriate Reality user-id and password has been entered in the ODBC data source definition.

SQL/JDBC

If you cannot connect:

• Check the spelling and case of the connection details.
• If the connection details are correct, check that the CLASSPATH environment variable has been set up correctly. It should contain references to the DDA and RealSQL-JDBC Driver packages (jreal.jar and realsql-jdbc.jar).

The Reality External Components Installation Guide describes how to set the CLASSPATH variable.

If you cannot run the RealJTest program:

• Check that you have installed the Java Runtime Environment (JRE).

• Check that the PATH environment variable contains a reference to the JRE program files. For example, on Windows:

  PATH=C:\WINDOWS;C:\WINDOWS;C:\WINDOWS\COMMAND;C:\PROGRAM FILES\JAVASOFT\JRE\1.2\BIN

  Note: You can check that the JReal and JDBC packages can be accessed by entering

  java com.northgateis.jreal.VersionInfo

  and

  java com.northgateis.reality.realsql.VersionInfo

  at the command prompt. These should both result in a version number (for example, Version V3.0.0.1) being displayed. Note that the case of the above lines is significant they must be typed exactly as shown.

  If either of these this results in:

  'java' is not recognized as an internal or external command, operable program or batch file.

  the PATH variable is not correct.

  If either results in a NoClassDefFoundError exception, CLASSPATH is not set up correctly.