http://www.bluestone.com/support/ExplorerWeb.html

To contact Bluestone Technical Support directly, see page xiv of this manual.

This chapter contains information on the following topics:

• Apparent Loss of Project Options

• Core Dump on Re-Opening a Project

• Error Messages

• HP Compiler

• SaCancel Dialog

• SQL*Net version 2

• Terminal Emulation

Resolution: The options have been saved to disk but the list in memory has not been updated. You need to exit the tool after saving your options and restart.

Error Messages

Message: "500 Server Error, execve function failed" or

"500 Server Error, httpd: malformed header from script"

• the executable has execution permission for everybody.

• the executable was compiled and run on the same type of platform.

For example: If the executable is compiled on the HP UX where Sapphire is installed, but the executable is installed on an IBM AIX, the location of the Web server, then "500 Server Error, execve function failed" or "500 Server Error, httpd: malformed header from script" might occur when running the cgi.

• Check the error code for execve for other possible causes.

Resolution: The CGI cannot find the Sapphire/Web Gateway (ORB). Check the settings for the ORB_HOST and ORB_SEED in the Options Editor (Test category); this is where the CGI gets the values for these environment variables.

Message: "error 06114"

Resolution: If you get this message when connecting to an Oracle database, check that the following attributes are set correctly:

1. The environment variable ORACLE_SID should NOT be set.

2. The file $SAPPHIRE/app-defaults/DbuimxOrb should contain a line like: OracleDatabase : MyDatabase for each Oracle database you are trying to reach.

3. The environment variable XAPPLRESDIR is set to the directory in which the resource file lives. (Should be $SAPPHIRE/app-defaults).

Resolution: To set up a Sybase Gateway to access a remote Sybase Server:

1. In addition to the environment variables, INFORMIXDIR and XAPPLRESDIR you have already set, you also need to set the SYBASE environment variable to the directory where you have the Sybase interfaces file. Example:

	%setenv SYBASE /this/dir

The interfaces file, /this/dir/interfaces may look like this:

   SYBLUE
           query tcp sun-ether hemingway 23000
           master tcp sun-ether hemingway 23000
           console tcp sun-ether hemingway 23001
   CEZANNE
           query tcp ether cezanne 60001
           master tcp ether cezanne 60001
           console tcp ether cezanne 60002

2. Restart the ORB. This time you should see both dborbd.syb and dborbd.inf running.

3. Restart Sapphire.

4. Remove all the database specific settings from the project option.

5. You should be able to see both Informix and Sybase servers in the Database Browser as well as using the data objects from either database for object binding.

HP Compiler

1) -g not recognized (WARNING)

2) -D_INCLUDE_POSIX_SOURCE redefinition (WARNING)

3) -lPW not found (ERROR)

Resolution: Remove all of these from the makefile and rebuild all objects before testing the project.

SaCancel Dialog

Resolution: The SaCancel dialog pops-up when there is a transaction in the process stairwell that takes a long time. You have a choice at this point to wait or cancel the transaction. There could be several reasons for this: for example, when a database alias contains an invalid specification of the SID. Check the alias definition in the tnsnames.ora file as shown below. Make sure ORCL is correct. You will have to restart the gateway after changing this reference:

  sapphire =
     (DESCRIPTION =
       (ADDRESS_LIST =
           (ADDRESS =
             (COMMUNITY = TCPCOM)
             (PROTOCOL = TCP)
             (HOST = prodnt4)
             (PORT = 1521)
           )
       )
       (CONNECT_DATA =
         (SID = ORCL)
       )
     )

1. The environment variable ORACLE_SID should not be set.

2. For Oracle version 7.2.3 only:

In this version, Oracle SQL*Net no longer uses the connection string to connect to the database; it uses alias. The alias is usually defined in the TNSNAME.ORA, file, found in the ORACLE_HOME/network/admin directory

You will need the TNSNAME.ORA and the SQLNET.ORA files on the Oracle server. If Oracle and the ORB are not on the same server, then both of these files must exist on both the Oracle Server and the Client Server. The files must be copied to the ORACLE_HOME/network/admin directory.

3. The Sapphire/Gateway resource file should have the following ORACLE resources instead:

	OracleDatabase 	: database_1
	OracleDatabase 	: database_2
						.
						.
						.
	OracleDatabase : database_N 

The database_N cannot be preceded by an '@' symbol even though that would normally be the correct method in Oracle. The ORB adds an @ to the connection string (necessary in SQL*Net V1) and that makes two occurrences of the '@' character.

For example:

OracleDatabase: @database_1 would result in scott/tiger@@database_1 (WRONG!!!!)

OracleDatabase: database_1 would result in scott/tiger@database_1 (RIGHT!!!)

4. Set the ORACLE_HOME environment and start the ORB. Example:

 	$SAPPHIREDIR/bin/dborbd -r100

Note: dborbd is a shell script, and since you have set only the ORACLE_HOME environment variable, it will attempt to start Oracle.

For other database vendors you will get the following warnings:

Not starting SYBASE orb because SYBASE environment 
variable not set.
Not starting INFORMIX orb because INFORMIXDIR environment 
variable not set.

If you still cannot establish a connection, then please rebuild the ORB using your installed Oracle libraries. Sapphire provides a few methods for rebuilding Oracle ORBS with different Oracle configurations, which can be found in the $SAPPHIRE/bin/Makefile.orb file.

Unfortunately, there are so many variations that Bluestone is unable to supply them all. Therefore, you may need to determine the appropriate link line for the configuration, and then modify the Makefile manually.

1. Make a backup copy of original ORB and original Makefile.orb.

2. Modify Makefile.orb for the your specific Oracle configuration. If the ORB does not link properly, look for sample Oracle application Makefiles that illustrate the correct link line for your specific Oracle installation. Model the link line in Makefile.orb after your Oracle sample application Makefile's link line.

To rebuild the ORB type:

 make -f Makefile.orb ORACLE

Resolution: This is a terminal emulation problem. Check your terminal emulation setup and configuration.