Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Sreedhar Kalasapati (SreedharKUHG)
UnitedHealth Group

UnitedHealth Group
IN
SreedharKUHG Member since 2014 2 posts
UnitedHealth Group
Posted: Sep 28, 2015
Last activity: Sep 29, 2015
Posted: 28 Sep 2015 10:28 EDT
Last activity: 29 Sep 2015 1:17 EDT
Closed
Solved

Gettign error while running through command line in BIX 7x

Hi,

I am getting the below exception while running the BIX on Pega 7.1.7 version and BIX also 7 version. BIX is working fine if we import BIX ruleset. Here my scenario is I have taken the Extract rule XML and running the BIX through command line in higher environments where BIX ruleset is not available. Seems like it is checking the DB table for Log-Extract class and throwing error. But the same is working in lower version without checking this class. When I create Log-Extract class rule and running, then it is generating BIX reports fine. In BIX 7x version, is it mandatory to import BIX rules to run the extract through command line? Is there any other option to execute without importing BIX rules. Below is the error message.

2015-09-28 09:08:30,279 [           xxxx] [                    ] [                    ] (   internal.access.ExtractImpl) ERROR   - Error while generating the handle for logging

2015-09-28 09:08:30,279 [           xxxx] [                    ] [                    ] (   internal.access.ExtractImpl) ERROR   - Error while getting the sequenceNumberDatabase-BadClassDef Log-Extract

2015-09-28 09:08:30,283 [           xxxx] [                    ] [                    ] (   internal.access.ExtractImpl) ERROR   - Error while getting the count from manifest table

Show More

Hi,

I am getting the below exception while running the BIX on Pega 7.1.7 version and BIX also 7 version. BIX is working fine if we import BIX ruleset. Here my scenario is I have taken the Extract rule XML and running the BIX through command line in higher environments where BIX ruleset is not available. Seems like it is checking the DB table for Log-Extract class and throwing error. But the same is working in lower version without checking this class. When I create Log-Extract class rule and running, then it is generating BIX reports fine. In BIX 7x version, is it mandatory to import BIX rules to run the extract through command line? Is there any other option to execute without importing BIX rules. Below is the error message.

2015-09-28 09:08:30,279 [           xxxx] [                    ] [                    ] (   internal.access.ExtractImpl) ERROR   - Error while generating the handle for logging

2015-09-28 09:08:30,279 [           xxxx] [                    ] [                    ] (   internal.access.ExtractImpl) ERROR   - Error while getting the sequenceNumberDatabase-BadClassDef Log-Extract

2015-09-28 09:08:30,283 [           xxxx] [                    ] [                    ] (   internal.access.ExtractImpl) ERROR   - Error while getting the count from manifest table

2015-09-28 09:08:30,290 [           xxxx] [  STANDARD] [                    ] [                    ] (l.access.ConnectionManagerImpl) ERROR   - Not returning connection 1 for database "pegadata" to the pool as it previously encountered the following error

User ID: (unknown)

Last SQL: select pyItemId from null where pzInsKey = ?

java.sql.SQLSyntaxErrorException: ORA-00903: invalid table name

  at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:440)

  at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:396)

  at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:837)

  at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:445)

  at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:191)

  at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:523)

  at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:207)

  at oracle.jdbc.driver.T4CPreparedStatement.executeForDescribe(T4CPreparedStatement.java:863)

  at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1153)

  at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1275)

  at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3576)

  at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3620)

  at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeQuery(OraclePreparedStatementWrapper.java:1491)

  at com.pega.pegarules.data.internal.access.DatabasePreparedStatementImpl.executeQuery(DatabasePreparedStatementImpl.java:405)

  at com.pega.pegarules.data.internal.access.ExtractImpl.processSequenceNumber(ExtractImpl.java:6768)

  at com.pega.pegarules.data.internal.access.ExtractImpl.doExtract(ExtractImpl.java:2752)

  at com.pega.pegarules.data.internal.access.ExtractImpl.runExtract(ExtractImpl.java:1621)

  at com.pega.pegarules.data.internal.access.ExtractImpl.run(ExtractImpl.java:1304)

  at com.pega.pegarules.data.internal.access.ExtractImpl.init(ExtractImpl.java:1278)

  at com.pega.pegarules.data.internal.access.ExtractImpl.parseAndRunExtractCommand(ExtractImpl.java:1235)

  at com.pega.pegarules.data.internal.access.ExtractImpl.main(ExtractImpl.java:953)

  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

  at java.lang.reflect.Method.invoke(Method.java:606)

  at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:338)

  at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:379)

  at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethodPropagatingThrowable(AppServerBridgeToPega.java:216)

  at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethod(AppServerBridgeToPega.java:265)

  at com.pega.pegarules.pub.PegaRULES.main(PegaRULES.java:85)

2015-09-28 09:08:30,294 [           xxxx] [                    ] [                    ] (   internal.access.ExtractImpl) WARN    - returning the connection


Show Less
To see attachments, please log in.
Reporting

Accepted Solution

Posted: 9 years ago
Posted: 29 Sep 2015 1:17 EDT
Rajiv Nistala (nistr) Senior Manager - Engineering
Pegasystems
IN

Hi Sreedhar,

It may have been feasible to do so in prior versions but it is not a supported configuration by Pega. The BIX user guide clearly states that you do need to import the ruleset. You do need to have the Pega-BIX ruleset imported into the system for it to work.

-Rajiv

To see attachments, please log in.
Posted: 9 years ago
Posted: 28 Sep 2015 10:41 EDT
Rajiv Nistala (nistr) Senior Manager - Engineering
Pegasystems
IN
In BIX 7x version, is it mandatory to import BIX rules to run the extract through command line? Is there any other option to execute without importing BIX rules. Below is the error message.

Whether with prior versions of BIX or newer versions, BIX is a combination of the engine (Java) code and rules defined in Pega-BIX ruleset. The ruleset should be present for BIX to execute correctly. The command line depends on the rules in the ruleset for its execution. Please do not execute BIX without import the Pega-BIX ruleset into the environment. This is listed in the BIX User guide shipped with the distribution image.

Also note that with Pega 7, we change the BIX version for each ML. Please make sure you are using the right version found in "additional products" of the Pega 7 distribution image for that ML.

To see attachments, please log in.
Posted: 9 years ago
Posted: 28 Sep 2015 10:55 EDT
Sreedhar Kalasapati (SreedharKUHG)
UnitedHealth Group

UnitedHealth Group
IN

Thank you very much Rajiv, for immediate response. At our client, we are able to run the BIX without importing BIX ruleset (Pega 6.2 SP2) in Production environment. Now for new application we are using Pega 7 and we are using the latest BIX version also. So business is expecting the same in latest version. Is there any way to execute without importing Pega-BIX ruleset. We are using right version of BIX which comes along with Pega distribution image.

Thanks in advance.

To see attachments, please log in.

Accepted Solution

Posted: 9 years ago
Posted: 29 Sep 2015 1:17 EDT
Rajiv Nistala (nistr) Senior Manager - Engineering
Pegasystems
IN

Hi Sreedhar,

It may have been feasible to do so in prior versions but it is not a supported configuration by Pega. The BIX user guide clearly states that you do need to import the ruleset. You do need to have the Pega-BIX ruleset imported into the system for it to work.

-Rajiv

To see attachments, please log in.

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

Pega Collaboration Center 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