Support Article

Extract rule is failing with NullPointerException error

SA-29333

Summary



Extract rule is failing with NullPointerException error.

Error Messages




2016-09-21 23:45:48,303 [ rh0006v.theaa.local] [                    ] [                    ] (   internal.access.ExtractImpl) ERROR   - Error while getting the sequenceNumberORA-00942: table or view does not exist
2016-09-21 23:45:48,310 [ rh0006v.theaa.local] [                    ] [                    ] (   internal.access.ExtractImpl) ERROR   - Error while getting the count from manifest table
2016-09-21 23:45:48,358 [ rh0006v.theaa.local] [                    ] [                    ] (   internal.access.ExtractImpl) ERROR   - Unable to process Rule-InsProd-Product: null
java.lang.NullPointerException
               at com.pega.pegarules.data.internal.access.ExtractImpl.processSequenceNumber(ExtractImpl.java:7386)
               at com.pega.pegarules.data.internal.access.ExtractImpl.doExtract(ExtractImpl.java:3014)
               at com.pega.pegarules.data.internal.access.ExtractImpl.runExtract(ExtractImpl.java:1762)
               at com.pega.pegarules.data.internal.access.ExtractImpl.init(ExtractImpl.java:1409)
               at com.pega.pegarules.data.internal.access.ExtractImpl.parseAndRunExtractCommand(ExtractImpl.java:1354)
               at com.pega.pegarules.data.internal.access.ExtractImpl.parseAndRunExtractCommand(ExtractImpl.java:1071)
               at com.pega.pegarules.data.internal.access.ExtractImpl.main(ExtractImpl.java:1051)
               at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
               at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
               at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
               at java.lang.reflect.Method.invoke(Method.java:497)
               at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:370)


Steps to Reproduce



1. Run the Extract using shell scripts.
2. Check the log files for errors.


Root Cause



Database user does not have privileges to access Pega data schema tables causing this issue.

Resolution



User provided SELECT privileges to database user to access Pega data schema tables resolve the issue.

Published October 19, 2016 - Updated November 28, 2016

Have a question? Get answers now.

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