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

PRPC Export Utility not working

SA-5414

Summary



You are trying to export Rule Admin Product ("RAP")  using PRPC commandline utility "prpcUtils.sh/bat" but are experiencing the following error:

 "Unexpected state: the signature of the input byte array has an incorrect format:"

PRPC version is PegaRULES 6.1 SP2 coreBuild_060120_0161.
Database is Oracle Database 10g Enterprise Edition Release 10.1.0.4.0 - 64bit .
Operating System is SunOS 5.10 Generic_127111-11 sun4us sparc FJSV,GPUZC-M
And Java version, I used, is 1.5.0_17.

Error Messages



[java] WARNING: Cannot delete directory: extractedFiles
[java] Unexpected state: the signature of the input byte array has an incorrect format:
[java] 0x 0 0x 0 0x 0 0x 0 0x 0 0x 0 0x 0 0x 0 0x 0 0x 0 0x 0 0x 0 0x 0 0x 0 0x 0 0x 0
[java] 0x94 0x94 0x94 0x94 0x94 0x94 0x94 0x94 0x94 0x94 0x94 0x94 0x94 0x94 0x94 0x94
[...]
[java] 0xd8 0xd8 0xd8 0xd8 0xd8 0xd8 0xd8 0xd8 0xd8 0xd8 0xd8 0xd8 0xd8 0xd8 0xd8 0xd8
[java] 0xbb 0xbb 0xbb 0xbb 0xbb 0xbb 0xbb 0xbb 0xbb 0xbb 0xbb 0xbb 0xbb 0xbb 0xbb 0xbb
[java] Dec 5, 2014 11:12:05 AM com.pega.pegarules.internal.bootstrap.phase2.PRBootstrapImpl
[java] SEVERE: Error initializing PRAppLoader
[java] java.lang.IllegalArgumentException: Input byte array is not recognized as a supported version.
[java] at com.pega.pegarules.internal.bootstrap.phase2.jdbc.AbstractJdbcJarReader.inflate(AbstractJdbcJarR
eader.java:106)
[java] at com.pega.pegarules.internal.bootstrap.phase2.jdbc.AbstractJdbcJarReader.readEntry(AbstractJdbcJa
rReader.java:360)
[java] at com.pega.pegarules.internal.bootstrap.phase2.jdbc.PegaJdbcURLConnection.connect(PegaJdbcURLConne
ction.java:239)
[java] at com.pega.pegarules.internal.bootstrap.phase2.jdbc.PegaJdbcURLConnection.getInputStream(PegaJdbcU
RLConnection.java:300)
[java] at java.net.URL.openStream(URL.java:1007)
[java] at com.pega.pegarules.internal.bootstrap.phase2.PRBootstrapImpl._finishInitialization_privact(PRBoo
tstrapImpl.java:614)
[java] at com.pega.pegarules.internal.bootstrap.phase2.PRBootstrapImpl.finishInitialization(PRBootstrapImp
l.java:239)
[java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[java] at java.lang.reflect.Method.invoke(Method.java:585)
[java] at com.pega.pegarules.internal.bootstrap.PRBootstrap.checkForStartup(PRBootstrap.java:604)
[java] at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.j
ava:386)
[java] at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:438)
[java] at com.pega.pegarules.pub.PegaRULES.main(PegaRULES.java:88)
[java] Dec 5, 2014 11:12:05 AM com.pega.pegarules.internal.bootstrap.PRBootstrap


Steps to Reproduce



This happens immediately when running the script (after suitable configuration of 'prpcUtil.properties' etc have been done).


Root Cause



There is a mismatch between the JDBC driver version and the JVM that is used by the calling script 'prpcUtils.bat/sh' uses.

Resolution



The version of 'ojdbc.jar' used to connect to the Oracle database must be appropriate for your JVM.
In this case the JVM was version 1.5; so the file 'ojdbc5.jar' should be used.

(It is recommended that you use the same JVM and JDBC Driver JAR that your working PRPC system is using).

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