Specifies an additional set of directories or JAR files in which to search for classes.
|PUBLIC role||For current user||For other users|
|Allowed to set permanently?||Yes, with SET ANY SYSTEM OPTION||No||No|
|Allowed to set temporarily?||Yes, with SET ANY SYSTEM OPTION||No||No|
All Java classes and JAR files used with Java in the database should be installed in the database. If the database is moved to a different computer or operating system, the Java classes and JAR files move with it. Another benefit of installing classes and JAR files into the database is that the database server class loader can fetch the classes and resources from the database, allowing each connection that is using Java in the database to have its own instance of these classes and its own copy of static variables within these classes.
However, when a class or JAR file must be loaded by the system class loader, it can be specified with the java_class_path database option or the -cp dbeng17/dbsrv17 server option. Both options add classes and JAR files to the classpath that the database server builds for launching the Java VM. The java_class_path database option is useful when the server is running multiple databases and each database has a different set of JARs and directories that must be loaded by the system class loader. The -cp database server option is useful when all databases on the server require the same classes or JAR files.