The DBA's examined the OPA batch process while it was running. Oracle was sitting idle most the time waiting on the batch processor (according to the DBA staff.) Locks were not an issue and the DB was not under any load.
The performance is absolutely dismal and we are going to open an OPA support ticket, but would like a quick answer if anyone on this forum has a quick answer.
(Also, if you try to kill the batch job with <ctrl-c> because it is taking too long, then it leaves the sessions and cursors open. Is there a way to gracefully shut down the batch processor?)
We have a single simple table where the first 5 columns are conditions and the last column is a conclusion.
I filled the table with 1,000,000 rows of conditional data. I ran with a configuration like below:
<configuration>
<options>
<rulebase>../output/MyRules.zip</rulebase>
<database>
<url>jdbc:oracle:thin:myusername/mypassword@mydatabase:1521:mySID</url>
<driver>oracle.jdbc.OracleDriver</driver>
<driversrc>\myjdbcdriverpath\ojdbc6.jar</driversrc>
</database>
<output type="db" />
<mappings>
<boolean-format true-value="TRUE" false-value="FALSE" />
<mapping entity="global" table="SSPNA_IN" primary-key="ID">
<attribute name="bHasNoCountableIncome" field="BHASNOCOUNTABLEINCOME" />
<attribute name="bIsResidentOfNY" field="BISRESIDENTOFNY" />
<attribute name="cSSIBenefitAmt" field="CSSIBENEFITAMT" />
<attribute name="tFedLivingArrangementCD" field="TFEDLIVINGARRANGEMENTCD" />
<attribute name="tManualHMOInd" field="TMANUALHMOIND" />
<attribute name="tPaymentStatusCD" field="TPAYMENTSTATUSCD" />
<attribute name="tPrincipleProviderCD" field="TPRINCIPLEPROVIDERCD" />
<attribute name="cSSPNAPayment" field="CSSPNAPAYMENT" output="true" />
</mapping>
</mappings>
</options>
</configuration>