Connection between thin and OCI in Oracle

Http://feelfall.blogspot.com/2007/03/oraclethinoci.html

YingThe connection to Oracle is divided into two modes: thin and OCI. The former does not require support from the Oracle client, and the latter requires.

JDBC: oracle: thin :@ youroraclehost: 1521: yoursid
JDBC: oracle: thin: @ (description = (address = (host = youroraclehost) (Protocol = TCP) (Port = 1521) (CONNECT_DATA = (SERVICE_NAME = yourservicename )))

JDBC: oracle: OCI: @ youroracle-TNS-name
JDBC: oracle: OCI: @ (description = (address = (host = youroraclehost) (Protocol = TCP) (Port = 1521) (CONNECT_DATA = (SERVICE_NAME = yourservicename )))

Yesterday, the thin mode in The UAT environment was changed to the OCI mode. However, due to an error in the JBoss STARTUP script, JBoss was unavailable for half a day. Note the usage of the OCI mode.

In most cases, JBoss cannot be started due to environment variables.
LD_LIBRARY_PATH = $ ORACLE_HOME/lib32
The environment variable LD_LIBRARY_PATH is used to set the shared target library. in Linux, the system searches for the shared target library before searching for the standard library, and the function override the functions in standard library

Java_opts = "$ java_opts-dprogram. Name = $ progname-djava. Library. Path = $ ORACLE_HOME/lib32"
This is our Java STARTUP script. Note that-djava. Library. Path = $ ORACLE_HOME/lib32 tells Java its native library search path.

Otherwise, you will get this error.
No ocijdbc9 in Java. Library. Path

the error message -djava. library. path = $ ORACLE_HOME/lib32 . 2