After upgrade to Oracle 10g, executing any Harvest server side user defined process (UDP) causes Harvest client to hang.

Document ID : KB000054920
Last Modified Date : 14/02/2018
Show Technical Document Details

Description

If following conditions are met, user will experience Harvest client hanging when executing any server side UDP (linked or stand alone).

  1. The Harvest client was used to execute a server side UDP (pre/post linked or standalone).

  2. Harvest server is on a UNIX host.

  3. Harvest is using Oracle 10g for database.

  4. Both Harvest server and Oracle server processes are running on the same UNIX host.

  5. Harvest was not configured to use TNS to connect to Oracle (The service name option of the ODBC DataSource Name (DSN) used to connect to Oracle is blank)

  6. Oracle's Bequeath Detach option is not turned ON.

Solution

There are two options to choose to resolve this particular problem.

Below are the detailed steps including pros/cons for each option:

Option One:

This option affects all the Oracle applications (ex: Harvest) utilizing the database installation's configuration file that's being modified.

  1. Edit the $ORACLE_HOME/network/admin/sqlnet.ora file.

  2. Search for entry BEQUEATH_DETACH.

    1. If it exists, make sure its set to "YES". Example: BEQUEATH_DETACH=YES

    2. If it doesn't exist, create a new line and set it to:

      BEQUEATH_DETACH=YES

    3. Save and close the file.

  3. Stop the Harvest Broker process (which in turn shuts down HServers).

  4. Stop any other applications (ex: Harweb) that are connected to Oracle database above.

  5. Stop and restart Oracle database.

  6. Restart Harvest Broker.

  7. Test the server-side UDP which caused the previous Harvest Client hang situation.

Option Two:

This option only affects Harvest and the way it connects to the Oracle database. This option is going to introduce another layer of communication (TNS protocol layer) between Harvest Server and Oracle database. This may cause some performance impact, though not significant.

  1. Identify the TNS Alias/Service-Name that your Harvest Broker Unix node can use to connect to the Oracle database. Contact your DBA for this if needed.

  2. Stop the Harvest Broker process (which in turn shuts down HServers).

  3. Stop any other applications (ex: Harweb) that are connected to Oracle database above.

  4. Login to the Harvest Broker Unix node as the user who installed Harvest. This user needs to have proper write privileges to the files in the $ODBC_HOME directory. You can obtain the location of $ODBC_HOME by executing below commands at the UNIX prompt:

    1. 'grep odbcenv.sh $HARVESTHOME/bin/hserver' # notice back tick characters here.

    2. echo $ODBC_HOME

  5. On UNIX prompt, change to $HARVESTHOME/bin directory.

  6. Invoke the Harvest database configuration utility by executing ./hdbsetup

  7. Database configuration prompt appears and you'd be prompted to select the DBMS type.

  8. Specify the database type as O for oracle.

  9. Then choose the co option for configure ODBC DSN.

  10. Then provide the name of the existing Harvest DSN name that you'd like to reconfigure (This should be already listed out here. However, if there are multiple DSNs listed here, you can obtain the one that Harvest Server uses by doing: grep datasource $HARVESTHOME/HServer.arg).

  11. Choose to overwrite the existing DSN.

  12. When prompted for service name, provide the Oracle TNS service name (you collected this in Step (1) above).

  13. In the next step confirm the changes.

  14. If you want you can go ahead and select the Test driver connection option and verify connectivity between Oracle and Harvest using this newly configured DSN.

  15. Restart Harvest Broker and other processes (ex: Harweb).

  16. Test the server-side UDP which caused the previous Harvest Client hang situation.