Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Issue with connection string in prpcUtils property

SA-2544

Summary



Trying to execute Import and Export from the command line using prpcUtils. The Oracle database being used is on the PEGA server where the prpcUtils script is executed. The connection string is used as ''pega.jdbc.url=jdbc:oracle:thin:@//localhost:1521/org.server.local" in the prpcUtils property file. Error is received if the server name or IP address is used instead of the localhost in the connection string.

For example:
pega.jdbc.url=jdbc:oracle:thin:@//WINDOWS-HOSTNAME:1521/org.server.local
pega.jdbc.url=jdbc:oracle:thin:@//192.0.0.168:1521/org.server.local


Error Messages



The error is "Failed to connect using provided properties. IO Error: The Network adapter could not establish the connection."


Steps to Reproduce



1. Open command prompt as administrator.
2. Set location using cd d:\pega\scripts\utils
3. Execute command - prpcUtlls exportRAP
4. With 'localhost' value in the JDBC URL the command executes successfully. However, if the server name or IP address instead of the localhost is used, an error is received.


Root Cause



The root cause of this problem is a defect/misconfiguration in the PRPC operating environment.



Resolution



The explanation for this behavior is as follows: 

The connection URL syntax is the thin driver net service name syntax. This can be contrasted with the Oracle SID (service identifier) syntax. For the net service name syntax, a service name registered and available on the server with the name "org.server.local" is needed. You can check your tnsnames configuration to determine if this is the case. Also verify that the tnsnames.ora and listener.ora configuration files are setup to listen for the hostname, NOT just "localhost".

If the service name looks to be properly configured in the tnsnames.ora file, and the listener.ora is setup to listen on your hostname (WINDOWS-HOSTNAME), then verify that Windows firewall isn't blocking incoming connections to port 1521

Published January 31, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us