Issue - After the EBS/source DB clone, the user getting java.lang.NullPointerException in request logs
Steps verified - DB , Apps and Vertex post clone steps
DB links and XXVERTEX.VERTEX_SERVICE_ENDPOINT properly set
ERROR Messages -
<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Header></soapenv:Header>
<soapenv:Body>
<soapenv:Fault>
<faultcode>soapenv:Server</faultcode>
<faultstring xml:lang="en">java.lang.NullPointerException</faultstring>
<detail>
<ns2:VertexException
xmlns:ns2="urn:vertexinc:oseries:exception:1:0">
<exceptionType>NullPointerException</exceptionType>
<rootCause>java.lang.NullPointerException</rootCause>
</ns2:VertexException>
</detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
Error 2 -
SmartStatement.executeBatch:
ORA-00001: unique constraint (VERTEX_TJ.XPKJOURNALLINEITEM) violated
$$ START $$
Time stamp: 20/11/09 08:30:32.438
Log level: ERROR
Thread name: http-nio-8095-exec-145 priority: 5
Class: com.vertexinc.util.db.action.ActionSequence
Exception classification: APPLICATION
Database operation failed. Retry will be attempted. A single isolated failure is not reason for concern; however, if retries are frequent (even if there is eventually success) there is likely a serious problem which should be evaluated by the Database Administrator. (current retry=3, maximum retries=5, failed sequence=com.vertexinc.util.db.action.ActionSequence@9370516)
Maximum number of retries exceeded for update. Failure likely indicates that either a database problem exists or that the request is invalid. (max retries=1, update string=INSERT INTO LineItem (sourceId,lineItemId,parentLineItemId,lineItemNumber,transactionId,userTransIdCode,transactionTypeId,transOrigTypeId,transSubTypeId,transPrspctvTypeId,transStatusTypeId,transSyncInd,transSyncSeqNum,transSyncIdCode,lineItemSyncIdCode,taxDate,postingDate,transProcDate,itemTypeDtlId,itemTypeCode,itemClassDtlId,itemClassCode,usageTypeDtlId,usageTypeCode,usageClassDtlId,usageClassCode,unitOfMeasISOCode,userLocationCode,unitPrice,extendedPrice,inputExtendedPrice,undiscountedPrice,inputUndiscPrice,itemQuantity,componentInd,inputTotalTaxAmt,freightChargeAmt,chargedTaxAmt,ovrdLocRoleTypeId,taxUnderThrshldInd,simpTypeId,customsStatusId,movementMethodId,basisTypeId,landedCost,shippingTermsId,chainTransId,titleTransferId,lastUpdateDate,busTransTypeId,ovrdTaxbltyTypeId,ovrdTaxbltyReasId,currencyUnitId,origCurrencyUnitId,costCenterDtlId,costCenterCode,departmentDtlId,departmentCode,genLdgrAcctDtlId,genLdgrAcctCode,materialDtlId,materialCode,projectDtlId,projectCode,vendorSKUDtlId,vendorSKUCode,commodityCodeDtlId, commodityCode, commodityCodeType, intrastatCmdtyCode,countryOfOrigin,modeOfTransport,natureOfTrans,netMassKilograms,weight,volume,updateId,strgFlxFld1DtlId,strgFlxFld1TDId,strgFlxFld1Value,strgFlxFld2DtlId,strgFlxFld2TDId,strgFlxFld2Value,strgFlxFld3DtlId,strgFlxFld3TDId,strgFlxFld3Value,strgFlxFld4DtlId,strgFlxFld4TDId,strgFlxFld4Value,strgFlxFld5DtlId,strgFlxFld5TDId,strgFlxFld5Value,strgFlxFld6DtlId,strgFlxFld6TDId,strgFlxFld6Value,strgFlxFld7DtlId,strgFlxFld7TDId,strgFlxFld7Value,strgFlxFld8DtlId,strgFlxFld8TDId,strgFlxFld8Value,strgFlxFld9DtlId,strgFlxFld9TDId,strgFlxFld9Value,strgFlxFld10DtlId,strgFlxFld10TDId,strgFlxFld10Value,strgFlxFld11DtlId,strgFlxFld11TDId,strgFlxFld11Value,strgFlxFld12DtlId,strgFlxFld12TDId,strgFlxFld12Value,strgFlxFld13DtlId,strgFlxFld13TDId,strgFlxFld13Value,strgFlxFld14DtlId,strgFlxFld14TDId,strgFlxFld14Value,strgFlxFld15DtlId,strgFlxFld15TDId,strgFlxFld15Value,strgFlxFld16DtlId,strgFlxFld16TDId,strgFlxFld16Value,strgFlxFld17DtlId,strgFlxFld17TDId,strgFlxFld17Value,strgFlxFld18DtlId,strgFlxFld18TDId,strgFlxFld18Value,strgFlxFld19DtlId,strgFlxFld19TDId,strgFlxFld19Value,strgFlxFld20DtlId,strgFlxFld20TDId,strgFlxFld20Value,strgFlxFld21DtlId,strgFlxFld21TDId,strgFlxFld21Value,strgFlxFld22DtlId,strgFlxFld22TDId,strgFlxFld22Value,strgFlxFld23DtlId,strgFlxFld23TDId,strgFlxFld23Value,strgFlxFld24DtlId,strgFlxFld24TDId,strgFlxFld24Value,strgFlxFld25DtlId,strgFlxFld25TDId,strgFlxFld25Value,dateFlxFld1DtlId,dateFlxFld1Value,dateFlxFld2DtlId,dateFlxFld2Value,dateFlxFld3DtlId,dateFlxFld3Value,dateFlxFld4DtlId,dateFlxFld4Value,dateFlxFld5DtlId,dateFlxFld5Value,numFlxFld1DtlId,numFlxFld1Value,numFlxFld2DtlId,numFlxFld2Value,numFlxFld3DtlId,numFlxFld3Value,numFlxFld4DtlId,numFlxFld4Value,numFlxFld5DtlId,numFlxFld5Value,numFlxFld6DtlId,numFlxFld6Value,numFlxFld7DtlId,numFlxFld7Value,numFlxFld8DtlId,numFlxFld8Value,numFlxFld9DtlId,numFlxFld9Value,numFlxFld10DtlId,numFlxFld10Value,discountCatId,discountTypeId,discountCode,discountAmt,discountPct,grossAmt,inputCostAmt,assistedStateId,recovAmountDate,inpTaxCntryISOCode,inpTaxRecOvrdPct,inpTaxImportInd,inpTaxAmt,buyerPartyDtlId,buyerExemptInd,buyerPartyTypeId,buyrExmptReasCatId,buyrExmptCertCode,buyrPrimPartyCode,buyrScndPartyCode,buyrTrtryPartyCode,buyrPartyClassCode,buyrPrtyClassDtlId,buyerBusinessInd,sellerPartyDtlId,sellerExemptInd,sellerPartyTypeId,selrExmptReasCatId,selrExmptCertCode,selrPrimPartyCode,selrScndPartyCode,selrTrtryPartyCode,selrPartyClassCode,selrPrtyClassDtlId,sellerBusinessInd,ownerPartyDtlId,ownerExemptInd,ownerPartyTypeId,ownrExmptReasCatId,ownrExmptCertCode,ownrPrimPartyCode,ownrScndPartyCode,ownrTrtryPartyCode,ownrPartyClassCode,ownrPrtyClassDtlId,ownerBusinessInd,recpPartyDtlId,recpExemptInd,recpPartyTypeId,recpExmptReasCatId,recpExmptCertCode,recpPrimPartyCode,recpScndPartyCode,recpTrtryPartyCode,recpPartyClassCode,recpPrtyClassDtlId,recpBusinessInd,dispPartyDtlId,dispExemptInd,dispPartyTypeId,dispExmptReasCatId,dispExmptCertCode,dispPrimPartyCode,dispScndPartyCode,dispTrtryPartyCode,dispPartyClassCode,dispPrtyClassDtlId,dispBusinessInd,reversalInd,weightUnitCode,volumeUnitCode,billedToDateAmt,calculateBothPerspectivesInd,exportProcedure,supplementaryUnit,supplementaryUnitType,documentType,billingType,orderType,statisticalValue,statisticalValueCurrencyUnitId,documentSequenceIdCode,paymentDate,transProcTime,taxPointDate,companyCodeCurrencyTaxableAmt,companyCodeCurrencyTaxAmt,companyCodeCurrencyUnitId,materialOriginDtlId,materialOriginCode,invoiceTotalCatId1,invoiceTotalCatSourceId1,invoiceTotalJurisdictionId1,invoiceTotalImpsnSrcId1,invoiceTotalImpsnDtlId1,invoiceTotalAmt1,invoiceTotalCurrencyUnitId1,invoiceTotalCatId2,invoiceTotalCatSourceId2,invoiceTotalJurisdictionId2,invoiceTotalImpsnSrcId2,invoiceTotalImpsnDtlId2,invoiceTotalAmt2,invoiceTotalCurrencyUnitId2,invoiceTotalCatId3,invoiceTotalCatSourceId3,invoiceTotalJurisdictionId3,invoiceTotalImpsnSrcId3,invoiceTotalImpsnDtlId3,invoiceTotalAmt3,invoiceTotalCurrencyUnitId3,invoiceTotalCatId4,invoiceTotalCatSourceId4,invoiceTotalJurisdictionId4,invoiceTotalImpsnSrcId4,invoiceTotalImpsnDtlId4,invoiceTotalAmt4,invoiceTotalCurrencyUnitId4,transForcedInd,specialTaxBasis,wageBasis) VALUES (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?))
null
java.lang.NullPointerException
Solution -
The following unique constraint error occurs during tax calculation:
ORA-00001: unique constraint (VTXUSR_TPS.XPKJOURNALLINEITEM) violated
The Response XML related to the error provides the following information:
</faultstring><detail><ns:VertexException xmlns:ns="urn:vertexinc:oseries:exception:1:0">
<ns:exceptionType>BatchUpdateException</ns:exceptionType><ns:rootCause>java.sql.BatchUpdateException:
ORA-00001: unique constraint (VTXUSR_TPS.XPKJOURNALLINEITEM) violated
</ns:rootCause></ns:VertexException></detail></nsf:Fault></S:Body></S:Envelope>
The error may be caused by the following scenario:
You point to a new database instance without first stopping and restarting the vertex-ws web service on that new instance. As a result, you receive invalid IDs. The IDs are invalid because the ID sequences that are held in the calculation cache are not the same as the ID sequences in the cloned, source database.
To correct the error, stop and restart the vertex-ws web service. This action enables the Calculation Engine to regenerate the proper ID sequences by using the sequences from the cloned, source database.
No comments:
Post a Comment