UDF Installation Issues During Pega Package Installation

Pega-as-a-Service
, , , , , , , , , , ,
1

UDF’s are very useful for reporting and Developers no need to optimize the Tables however, Be it any Pega Platform Version Installation, The below Error is common while Installing UDF.

Any solution to the issue will be more helpful.

Load UDF:
[pega:executesqlintransaction] Execute SQL In Transaction:false
[mkdir] Created dir: C:\Users\sakisho\AppData\Local\Temp\PegaInstallTemp-18-May-2023-16.24.03\udf_temp
[copy] Copying 6 files to C:\Users\sakisho\AppData\Local\Temp\PegaInstallTemp-18-May-2023-16.24.03\udf_temp
[echo] arg values : --config=C:\Users\sakisho\AppData\Local\Temp/PegaInstallTemp-18-May-2023-16.24.03/prbootstrap.properties --profile=install.postgres --dataOnly=false --rulesOnly=${db.onlyRules} --run-in-transaction=false --jar-path=C:\Users\sakisho\Downloads\117358_Pega8.6.6\scripts/../scripts/udf/prreadstream.jar C:\Users\sakisho\AppData\Local\Temp/PegaInstallTemp-18-May-2023-16.24.03/udf_temp
[java] Exception in thread “main” org.postgresql.util.PSQLException: ERROR: relation “sqlj.jar_repository” does not exist
[java] Position: 21
[java] at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2552)
[java] at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2284)
[java] at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:322)
[java] at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:481)
[java] at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:401)
[java] at org.postgresql.jdbc.PgPreparedStatement.executeWithFlags(PgPreparedStatement.java:164)
[java] at org.postgresql.jdbc.PgCallableStatement.executeWithFlags(PgCallableStatement.java:83)
[java] at org.postgresql.jdbc.PgPreparedStatement.executeQuery(PgPreparedStatement.java:114)
[java] at com.pega.pegarules.install.udf.loaders.PostgresUDFJarLoader.isJarLoadedPostgres(PostgresUDFJarLoader.java:154)
[java] at com.pega.pegarules.install.udf.loaders.PostgresUDFJarLoader.installJarOnPostgres(PostgresUDFJarLoader.java:115)
[java] at com.pega.pegarules.install.udf.loaders.PostgresUDFJarLoader.load(PostgresUDFJarLoader.java:88)
[java] at com.pega.pegarules.install.UDFManager$AbstractUDFExecutor.loadUDFJar(UDFManager.java:344)
[java] at com.pega.pegarules.install.UDFManager$ExecuteUDFWithOutTransaction.executeInner(UDFManager.java:289)
[java] at com.pega.pegarules.install.UDFManager$AbstractUDFExecutor.execute(UDFManager.java:353)
[java] at com.pega.pegarules.install.UDFManager.process(UDFManager.java:184)
[java] at com.pega.pegarules.install.UDFManager.main(UDFManager.java:136)

2

Hi @KishoreSanagapalli: Fund out some post which speaks about similar issue. Can you please check if this and this helps?

If now, please wait for other community members to update.

Thanks.

3

@KishoreSanagapalli have you checked the “Bypass Automatic DDL generation” option? What OpenJDK version are you using? If it is OpenJDK17 that is not valid.

Try unchecking the option and using OpenJDK8

Can you please check the below content given in the installation guide under Creating secondary schema for Java user-defined functions

https://docs-previous.pega.com/pega-platform-86-installation-guide-apache-tomcat-and-postgresql

Use the PostgreSQL tool pgAdmin to create the new schema called sqlj with PL/Java correctly installed.

  1. Open the install.sql file in the ResourceKit/PLJava/9. x/OS / directory in a text editor. You will copy the contents of this file into the PostgreSQL tool in a later step.

  2. In pgAdmin, select the database in which you plan to install PL/Java.

  3. Click the SQL icon.

  4. In pgAdmin, paste the contents of the install.sql file into the pgAdmin editor.

  5. Click Execute pgScript.

  6. Verify that there are no error messages. If there is an error, check the library directory settings andrestart the PostgreSQL service.

Please cross check the postgre version.

Once please try this again and run the prpc jar.

If you still run into issues I suggest that you log a support incident via the MSP.