Abstract: An electromechanical linear drive having a housing and a piston rod that passes through a housing end cover, and is carried by a spindle nut arranged longitudinally displaceably in a housing interior space. The spindle nut engages the motor-driven threaded spindle such that it is displaceable back and forth in the housing interior space by rotary motion of the spindle. A lubrication nipple is accessible on an outer side of the housing, and at least one lubrication passage extends from the nipple and opens to a stop surface located in the housing interior space, which stop surface forms an end stop for motion of the spindle nut. At least one lubrication conduit leads to lubrication sites of the spindle nut and is arranged in the spindle nut so that when the spindle nut is in abutment against the stop surface, the lubrication conduit is joined to the housing-side lubrication passage.

Abstract: An electromechanical linear drive having a housing and having at least one piston rod that passes through an end-located housing cover, projects at one end out of the housing, and is carried by a spindle nut arranged longitudinally displaceably in a housing interior space, the spindle nut sitting on a threaded spindle that extends through the housing interior space and can have a rotary motion imparted to it by means of an electric motor, and is displaceable back and forth in the housing interior space as a result of the rotary motion of the threaded spindle, is characterized in that a lubrication nipple (22) accessible on the outer side of the housing (11), and at least one lubrication passage (23, 24) joined to said nipple (22) and opening into a stop surface (21), located in the housing interior space (31), for the spindle nut (18), are arranged in a housing region (14) constituting an end stop for the motion of the spindle nut (18); and at least one lubrication conduit (25) leading to the lubrication site

Abstract: A system and method for constraint management in a database middleware system that responds to queries for data from requesting user applications by accessing diverse data sources. A constraint manager receives notifications of updates from sources that support notification, and the constraint manager monitors other sources that support monitoring, to undertake constraint management. Repairs of inconsistencies are made when possible, and when repairs are not possible, the inconsistencies are nulled out if the inconsistencies are totally useless to the requesting user application. In contrast, if the requesting application has some use for otherwise inconsistent, unrepairable data, the data is sent to the application along with an alert of the inconsistencies. Also, for those sources that do not support either notification or monitoring, the constraint manager executes just-in-time checking, i.e.