Page updated: 06/09/2004
About the website

                        Valid XHTML 1.0!

 
gLite 3.0

glite-SE_dpm_oracle - Update to version 3.0.14-0

Date 20.08.07
Priority Normal

Description


This update fixes various bugs. For the full list of bugs, please see list below.
YAIM

This release contains a new version of YAIM. YAIM 3.1.1 will configure gLite 3.0 and gLite 3.1 services and clients. The main feature of the new YAIM is its modularity. There will be a yaim core module, a yaim client module and different yaim modules for each gLite service. In the first release not all the services have been splitted in a new module and therefore they are part of yaim core. The idea for upcoming releases is to have a full modular version.

If you have not already performed a manual action in order to fix bug #27539, then you to do need a reconfiguration and restart of the node.

The first YAIM 3.1.1 release is a merge of yaim 3.0.1-22 and yaim 3.1.0 (for UI and WN). The new yaim will allow to configure all gLite 3.0 and gLite 3.1 services and clients.
Information system (MON-Box)

Update to prevent unnecessary load on the schema (co-hosted with the registry) when the R-GMA command line tool starts up.

Please also have a look at the list of known issues.

Fixed bugs

Number Description
 #27504 CLI submits a call to getAllTables when initialised
 #27841 strange node type problem with at least WN_torque

Updated rpms

Name Version Full RPM name Description
glite-rgma-command-line 5.0.5-1 glite-rgma-command-line-5.0.5-1.noarch.rpm R-GMA command line
glite-SE_dpm_oracle 3.0.14-0 glite-SE_dpm_oracle-3.0.14-0.noarch.rpm gLite SE DPM Oracle node
glite-yaim-core 3.1.1-8 glite-yaim-core-3.1.1-8.noarch.rpm org.glite.yaim.core
glite-yaim-dpm 3.1.1-4 glite-yaim-dpm-3.1.1-4.noarch.rpm org.glite.yaim.dpm

The RPMs can be updated using apt via

Service reconfiguration after update

If you have not already performed a manual action in order to fix bug #27539, then you to do need a re-configuration of the nodes.

Service restart after update

If you have not already performed a manual action in order to fix bug #27539, then you to do need a restart of the node.

How to apply the fix

  1. Update the RPMs (see above)
  2. Update configuration (see above)
  3. Restart the service if necessary (see above)