[Prev] [Top] (2 out of 2)

Overview

The troubleshooting section brings information addresses specific topics such as our first topic: ORACLE'S SQL*Net v2. We will be adding User, and Vendor specific information. For up-to-date FAQs and specific topics regarding Sapphire upgrades and support items, use Help->Support

SQL*Net version 2

Using Sapphire's ORB with Oracle SQL*Net v 2

1. 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.

To rebuild the ORB:

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


[Prev] [Top] (2 out of 2)