Slowness in the application when we use Camunda 7.11 with Oracle 19c version

Hi Team,

I am seeing slowness between the processes after upgrading the oracle version from 12.2 to 19c and we are still using Camund 7.12.0 (I see this version in build file) and cockpit is showing v7.11.0.

Is there any Performance issue if we use camunda 7.12.0/7.11.0 with Oracle 19c?
Please help me to understand better and way to fix the issue? we are seeing the performance issue in production.

Regards,
Thanuja.

How did you migrate from Oracle 12.2 to 19c? It looks like you upgraded Camunda from 7.11 to 7.12 as you mentioned Camunda 7.12 and Cockpit as 7.11

you might have not applied the patch when did you upgrade? Here is the patch details:

Would recommend to plan the migration and execute the steps. Revise your steps for executed migration planning document.

DBA team has done the Oracle DB migration from 12.2 version to 19c one week back. Camunda upgraded on 15-FEB-20 to 7.12.0 as shown below in ACT_GE_SCHEMA_LOG. we are seeing the slowness from one process to another process in the workflow after Oracle DB migration to 19c.

image

would you recommend migrating camunda to improve the performance? If so, Can you suggest the steps for the migration?

can we apply few patches on DB and update the version to 7.14 in one go? Kindly let me know the best practice for doing this migration.

Thank you so much for sharing the info.

Regards,
Thanuja.

I am seeing below error in ACT_HI_EXT_TASK_LOG Table.
Can you please help me to understand this exception and how to fix it?

exception: ENGINE-0emphasized text3005 Execution of ‘UPDATE PropertyEntity[next.dbid]’ failed. Entity was updated by another transaction concurrently.
logger: com.centurylink.wf.process.camunda.DomainProcessExecutionPoint
message: An error occurred while trying to call domain for context (ProcessExecutionContext [domain=swift, businessKey=SWIFT:554140647|348308607, processInstanceId=3478952620, processName=SeoSfdcInitiatedAsriComponent, executionPointName=SetTransactionComponentMilestoneStatus, variables={DESIGN=null, ACTIVATION=null, rootProductInstanceId=348308605, productInstanceId=348308607, isDesignCompleteAtleastOnce=false, eligibleMilestones=REQUEST|DESIGN|ACTIVATION|BILLING, billingSent=null, productName=Access, milestoneStatusVersion=null, parentProductInstanceId=348308605, orchestrationId=302710751, businessOrderId=2999828, productPackageStatusInSwift=New, routingGroup=Legacy OES, isDesignSentAtleastOnce=false, BILLING=null, transactionSourceSystem=SWIFT, productId=556, initialProductActionCode=ADD, seoBusinessKey=SWIFT:554140647|348308607, productInstanceVersion=0, transactionId=554140647, orderingSystem=SWIFT, rootProductRoutingGroup=Legacy OES, productPackageId=446081424, recordsOnlyToBilling=false, milestone=REQUEST, gpid=348308607, REQUEST=IP, milestoneStatusEmpMessageId=EMP-202402091846291262576, originatingSystem=SALESFORCE, milestoneStatus=AP, productPackageMarkedForCancelInSwift=false, transactionVersion=0, activationDate=null, parentProcessInstanceId=3474198162, allEligibleMilestonesClosed=false, parentBusinessKey=SWIFT:554140647, productPackageGpid=446081424, productActionCode=ADD}]), error message: ENGINE-03005 Execution of ‘UPDATE PropertyEntity[next.dbid]’ failed. Entity was updated by another transaction concurrently.

Can you please help me to resolve the issue?

Regards,
Thanuja.

Can someone please help me to resolve the above error.

Regards,
Thanuja.

Hi @Thanuja_Vadlamudi,

it looks like you are using the database ID generator: Id Generators | docs.camunda.org

For a production setup I recommend using the UUID generator.

Hope this helps, Ingo

Recently DBA has upgraded the oracle version from 12.2 to 19c and we haven’t not done any camunda migration and our version is camunda 7.12.0. Application is in one center and oracle DB is different center. We are seeing performance issues .the tasks are executing very slowly.using uuid generator will improve the performance for this situation?

Can you also help me to know the process for upgrading camunda to latest version? Also just me to which I can upgrade from 7.12.0?

Please help me to sort this issue.

Regards,
Thanuja.

Hi @Ingo_Richtsmeier ,

Is there any way to enable the logs and check which are the ones taking more time.

Regards,
Thanuja.

Before the DB upgrade, were the applications and DB in the same center?
Recommended practice for most systems is to have the DB and the App server in the same center.

Before DB upgrade, application and DB are in same centre. As part of DB upgrade, we upgraded oracle from 12.2 to 19c. Camunda was not migrated since 2020 and version is 7.12.0. we are seeing the slowness after DB upgrade and movement.

Would you recommend to put both of them in same centre. Oracle 19c with camunda 7.12.0 shouldn’t causing this issue right?

That is standard recommendation, not just for Camunda.
Latency between an application server and its DB will cause performance issues. If the DB and App Server (in this specific case, Camunda) are not in the same data centre, each DB query the App Server makes must transit between the centres, which will automatically increase the latency.

Try putting your Camunda 7.12 server and your Oracle 19c server in the same data centre and see if that resolves your performance issues.

Hi @Thanuja_Vadlamudi,

you can find more details about logging database statements here: Logging | docs.camunda.org

Hope this helps, Ingo