SQL/MX Guide to Stored Procedures in Java (G06.24+, H06.03+)

Managing SPJs in NonStop SQL/MX
HP NonStop SQL/MX Guide to Stored Procedures in Java—523727-004
6-18
Backing Up SPJs
Backing Up SPJs
Backing up SPJs should be part of a backup and recovery strategy for the entire
database. This strategy should involve periodically storing copies of these files in a
safe location, such as another disk, magnetic tape, or another system:
•
CREATE PROCEDURE statements (or the equivalent SQL/MX metadata)
•
Java class or JAR files that contain the Java classes of the SPJs
For comprehensive strategies of backing up and recovering database files, see the
SQL/MX Installation and Management Guide.
Using SPJs in a Distributed Database
Environment
For an SPJ to operate in a distributed database environment, the catalog in which the
SPJ is created must be visible on every remote node that requires access to that
catalog. In other words, the catalog of the SPJ must be visible on each node where
you want users to be able to call the SPJ.
To make a catalog visible on a remote node, you must register the catalog on the
remote node by issuing a REGISTER CATALOG statement on a node where the
catalog is visible, such as on the local node. For the syntax of the REGISTER
CATALOG statement, see the SQL/MX Reference Manual. For information about how
to manage a distributed database environment, see the SQL/MX Installation and
Management Guide.
In a distributed database environment, NonStop SQL/MX does not replicate or
distribute the Java class that underlies an SPJ. If you create an SPJ on a local node
and want to call that SPJ on a remote node, use one of these approaches:
•
Copying Java Classes to the Remote Node on page 6-19
•
Specifying the Node in the External Path on page 6-21
Make sure that the application classes on which the SPJ depends are also available in
the distributed database environment. For more information, see Distributing
Application Classes on page 6-22.