Project and Portfolio Management Practitioners Forum
cancel

server.conf parm format

Highlighted
GeeHam_1
New Member.

server.conf parm format

First:
I am reviewing the server.conf file and came across this format for the JDCB URL parm:
com.kintana.core.server.JDBC_URL
jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=aclurib00001022)(PORT=1521))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=svc_o303ppr_pacs)))
instead of the normal format.
The PPM application is up and running. Is anyone else using this format?

Second,
When the database is in a clustered setting how do you show it in the JDCB URL parm? Here is the TNSNames entry:
O303PQA =(DESCRIPTION =(ADDRESS = (PROTOCOL = TCP)(HOST = aclumab00001q01)(PORT = 1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = aclumab00001q02)(PORT = 1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = aoramab00001q06_vip)(PORT = 1521))
(LOAD_BALANCE = yes)
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = o303pqa)
)
)
1 REPLY
Jim Esler
Acclaimed Contributor.

Re: server.conf parm format

The value for this directive is described in the System Administration Guide and Reference. The form you are used to is probably what they describe as the URL short format while you have the full TNSnames entry specified. The manual describes the format of the value when using a RAC cluster. The key things to remember are:

- all information is on one line.
- do not have any blanks in the value.

As I recall, PPM will start an run with blanks in the value but the upgrade process does not parse the value properly when it encounters blanks.