• State Not Answered
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 134 views
  • Users 0 members are here
Options
Related

Observation when updating to version 9.2.2

sven schmidt

Hello,

We are in the process of upgrading our environments from Version 9.0 LTS to version 9.2.2.

We would also like to use new servers for this - from WinServer 2019 & MSSQL 2019 to new WinServer 2022 & MSSQL 2022. 
We are currently in the development environment and are making the following observation - the operation “QBM-K-BaseMigrationReady” has been in processing for almost 24 hours.

No blockage or similar problems can be detected on the SQL server.
When looking at the dialog journal, messages like this appear:

50000 0 #LDS#No job started for more then {0} s (detected in {1} loop).|      2401|inner|  50000 0 detected in  (SRV=<db-server>, DB=<DB-Name>) procedure QBM_PWorkDBQueueMain Line 050000 0 logged in DBQueue Processor


Are there others who have made similar observations?
Or in other words - which places should we check?
Many thanks for any information.

Kind regards

Parents
  • 0

    Hello Sven,

    We faced a similar issue. I don’t have the exact answer for that, but during our upgrade from version 9.1.1 to 9.2.2, we encountered an error related to "QBM-K-CheckSameCase". We were unable to resolve it initially, so we opened a case with the vendor.

    The vendor suggested deleting the related job "QBM-K-CheckSameCase" from JobQueue before running it again. After deleting the job from the JobQueue, we were able to complete the upgrade successfully. I suppose this behavior isn’t ideal, but we were able to handle it this way.

    BR

Reply
  • 0

    Hello Sven,

    We faced a similar issue. I don’t have the exact answer for that, but during our upgrade from version 9.1.1 to 9.2.2, we encountered an error related to "QBM-K-CheckSameCase". We were unable to resolve it initially, so we opened a case with the vendor.

    The vendor suggested deleting the related job "QBM-K-CheckSameCase" from JobQueue before running it again. After deleting the job from the JobQueue, we were able to complete the upgrade successfully. I suppose this behavior isn’t ideal, but we were able to handle it this way.

    BR

Children
  • 0 in reply to Volkan Ceylan

    Hello Volkan,

    Thanks for your reply. We have now been able to update our development environment to version 9.2.2.

    It is possible that an authorization was missing in the new SQL server or a setting was incorrect. In any case, the update procedure went smoothly after this adjustment. 
    With these findings, we are now planning to upgrade the other environments to the new version.

    Kind regards,

    Sven