Forum Discussion

BooHyunJang's avatar
BooHyunJang
Occasional Contributor
3 years ago

Collab "Cpu resources reduce" & "Version Upgrade" Problem

Hello. Collab support Teams~!!

 

There are two issues.

 

First ISSUECpu resource is increasing continuously.

Is there a way to adjust it?

Let me know if there's any way.

===============================================================

 

Second ISSUE → Collab Server Version Upgrade 

the present Server Version : Collaborator Enterprise 11.3.11301

Upgrade Version : ccollab_server_13_6_13600

 

OS : Linux collab 2.6.32-573.el6.x86_64

JAVA : java version "1.8.0_181"

Oracle JDBC *.jar : ojdbc8.jar

 

↓ Error log & DB info & Capture Screen

com.smartbear.ccollab.service.api.v7001.ServiceException:
A critical error occurred while upgrading the database: com.smartbear.ccollab.database.CollaboratorDatabaseException: com.smartbear.ccollab.database.CollaboratorDatabaseException: com.smartbear.ccollab.database.CollaboratorDatabaseException:
Exception occurred executing query. Please contact customer support.

==========================================================================================================

 

Please let me know in detail how to solve the problem with the second upgrade rather than the first issue.

Thank U

Regard

BooHyun.

1 Reply

  • For the first issue, use your system monitoring tools to verify what is using the CPU.  Is it all Collaborator?

     

    For the second issue, "upgrade your database" refers not to which version of the Oracle server or Oracle JDBC driver you're using but rather to the fact that we have to upgrade (modify) the Collaborator database schema to work with Collaborator 13.6.  The upgrade error *might* be a temporary problem in the internal DB upgrade process.  Try restarting Collaborator.  If that doesn't work, then the problem may be that you need the CTX_DDL package installed on the Oracle server.  See this article:

     

    https://support.smartbear.com/collaborator/docs/server/install/db/oracle.html

     

    If that doesn't help, open a support case.