• State Verified Answer
  • Replies 6 replies
  • Subscribers 93 subscribers
  • Views 803 views
  • Users 0 members are here
Options
Related

One Identity Manager 9.0 Cumulative Update 1 Error

babak pouladi
over 1 year ago

Hello,

Im currently getting this error when executing the Cumulative Update 1 for OIM 9.0 LTS (support.oneidentity.com/.../one-identity-manager-9-0-cumulative-update-1) :

This is the error message inside the logfile:

2023-02-07 11:08:09.4646 TRACE (SqlLog 3fc9ff0c-3468-4ce3-a11c-da5d175d8b12) : 	ClaimConnectionAsync: Releasing lock on connection 1 
2023-02-07 11:08:09.4646 TRACE (SqlLog 3fc9ff0c-3468-4ce3-a11c-da5d175d8b12) : 	Decremented pin count to 0 
2023-02-07 11:08:09.4646 DEBUG (SqlLog 3fc9ff0c-3468-4ce3-a11c-da5d175d8b12) : 	(3 ms) - Pinned physical connection 
2023-02-07 11:08:09.4646 TRACE (SqlLog ) : -- Connection 1 switched from Working to Available 
2023-02-07 11:08:09.4646 INFO (Transport ) : Wait 10s for database processor. 
2023-02-07 11:08:18.8983 TRACE (SqlLog Database Session GC) : Cleanup physical connection pool 
2023-02-07 11:08:18.8983 TRACE (SqlLog Database Session GC) : 	0 connections disposed. 
2023-02-07 11:08:18.8983 TRACE (SqlLog Database Session GC) : 	Available = 1 
2023-02-07 11:08:18.8983 TRACE (SqlLog Database Session GC) : 	Reusable = 1 
2023-02-07 11:08:19.4825 TRACE (SqlLog ) : -- Connection 1 switched from Available to Working after comparison 
2023-02-07 11:08:19.4825 TRACE (SqlLog ) : --> existing connection 1 
2023-02-07 11:08:19.4825 DEBUG (SqlLog 3fc9ff0c-3468-4ce3-a11c-da5d175d8b12) : 	(< 1 ms) - Pin DbSession to physical connection 
2023-02-07 11:08:19.4825 TRACE (SqlLog 3fc9ff0c-3468-4ce3-a11c-da5d175d8b12) : 	Incremented pin count to 1 
2023-02-07 11:08:19.4825 TRACE (SqlLog 3fc9ff0c-3468-4ce3-a11c-da5d175d8b12) : 	ClaimConnectionAsync - read write, _transaction == 60912231 
2023-02-07 11:08:19.4825 TRACE (SqlLog 3fc9ff0c-3468-4ce3-a11c-da5d175d8b12) : 	ClaimConnectionAsync: Lock aquired on connection 1 
2023-02-07 11:08:19.4825 TRACE (SqlLog 3fc9ff0c-3468-4ce3-a11c-da5d175d8b12) : 	ClaimConnectionAsync: Use the transaction 
2023-02-07 11:08:19.4825 DEBUG (SqlLog 3fc9ff0c-3468-4ce3-a11c-da5d175d8b12) : 	Setting DB context data to: user = One Identity Manager, id = 6c422f3e-7e0b-4ab5-8333-be390e83670d, level = 0 
2023-02-07 11:08:19.4825 TRACE (SqlLog 3fc9ff0c-3468-4ce3-a11c-da5d175d8b12) : 	ClaimConnectionAsync: Releasing lock on connection 1 
2023-02-07 11:08:19.4825 TRACE (SqlLog 3fc9ff0c-3468-4ce3-a11c-da5d175d8b12) : 	ClaimConnectionAsync - read write, _transaction == 60912231 
2023-02-07 11:08:19.4825 TRACE (SqlLog 3fc9ff0c-3468-4ce3-a11c-da5d175d8b12) : 	ClaimConnectionAsync: Lock aquired on connection 1 
2023-02-07 11:08:19.4825 TRACE (SqlLog 3fc9ff0c-3468-4ce3-a11c-da5d175d8b12) : 	ClaimConnectionAsync: Use the transaction 
2023-02-07 11:08:19.4825 DEBUG (SqlLog 3fc9ff0c-3468-4ce3-a11c-da5d175d8b12) : 	(1 ms) - declare @notReady int
exec @notReady = QBM_PMigrationNotReadyForComp
select @notReady

There are also no blocking transactions which could cause this error.

So which reason could this have?

Thank you very much!

  • 0 over 1 year ago

    Is a DB Scheduler Agent running (on a Job Service or as a CMD-line version)? It looks like your DB Queue will not be processed.

  • 0 over 1 year ago in reply to Markus Weiss-Ehlers

    The DB Queue is processing as usual, Database Agent is also running.

  • 0 over 1 year ago in reply to babak pouladi

    Okay. And what is the error exactly? I can just see, that the system is waiting for the DB Queue to process. How many entries are in the DB Queue?

  • 0 over 1 year ago in reply to Markus Weiss-Ehlers

    Both DialogDBQueue and QBMDBQueueCurrent are currently empty, the error message at the end is this according to the logfile:

    2023-02-07 11:08:19.4825 TRACE (SqlLog 3fc9ff0c-3468-4ce3-a11c-da5d175d8b12) : 	ClaimConnectionAsync: Releasing lock on connection 1 
2023-02-07 11:08:19.4825 TRACE (SqlLog 3fc9ff0c-3468-4ce3-a11c-da5d175d8b12) : 	Decremented pin count to 0 
2023-02-07 11:08:19.4825 DEBUG (SqlLog 3fc9ff0c-3468-4ce3-a11c-da5d175d8b12) : 	(2 ms) - Pinned physical connection 
2023-02-07 11:08:19.4825 TRACE (SqlLog ) : -- Connection 1 switched from Working to Available 
2023-02-07 11:08:19.4825 ERROR (Transport ) : System.OperationCanceledException: The operation was canceled. System.OperationCanceledException: The operation was canceled.
   at System.Threading.CancellationToken.ThrowOperationCanceledException()
   at VI.Transport.Transport.WaitForDbProcessorCompiler()
   at VI.Transport.Transport.SaveToDatabase()
   at VI.Transport.CumulativeTransport._ImportFiles()    at System.Threading.CancellationToken.ThrowOperationCanceledException()
   at VI.Transport.Transport.WaitForDbProcessorCompiler()
   at VI.Transport.Transport.SaveToDatabase()
   at VI.Transport.CumulativeTransport._ImportFiles()
2023-02-07 11:08:19.4981 ERROR (Transport ) : System.OperationCanceledException: The operation was canceled. System.OperationCanceledException: The operation was canceled.
   at System.Threading.CancellationToken.ThrowOperationCanceledException()
   at VI.Transport.Transport.WaitForDbProcessorCompiler()
   at VI.Transport.Transport.SaveToDatabase()
   at VI.Transport.CumulativeTransport._ImportFiles()    at System.Threading.CancellationToken.ThrowOperationCanceledException()
   at VI.Transport.Transport.WaitForDbProcessorCompiler()
   at VI.Transport.Transport.SaveToDatabase()
   at VI.Transport.CumulativeTransport._ImportFiles()
2023-02-07 11:08:19.4981 ERROR (Transport ) : Transport finished with error (2/7/2023 11:08:19 AM) VI.Transport.TransportErrorException: Import cumulative transport ---> System.Exception: Import cumulative transport ---> System.OperationCanceledException: The operation was canceled.
   at System.Threading.CancellationToken.ThrowOperationCanceledException()
   at VI.Transport.Transport.WaitForDbProcessorCompiler()
   at VI.Transport.Transport.SaveToDatabase()
   at VI.Transport.CumulativeTransport._ImportFiles()
   --- End of inner exception stack trace ---
   --- End of inner exception stack trace ---
   at VI.Transport.Transport.HandleException(ITransportTask sender, Exception ex, IEntity dbEntity)
   at VI.Transport.CumulativeTransport._ImportFiles()
   at VI.Transport.CumulativeTransport.Import(TransportTaskArguments args)
   at VI.Transport.Transport.SaveToDatabase(TransportParts tParts)    at VI.Transport.Transport.HandleException(ITransportTask sender, Exception ex, IEntity dbEntity)
   at VI.Transport.CumulativeTransport._ImportFiles()
   at VI.Transport.CumulativeTransport.Import(TransportTaskArguments args)
   at VI.Transport.Transport.SaveToDatabase(TransportParts tParts)
2023-02-07 11:08:19.5137 DEBUG (ObjectLog 3fc9ff0c-3468-4ce3-a11c-da5d175d8b12) : Session variable: Removing HOTFIXMODE.

    Interestingly the Jobqeue needs to be compiled after the failed update every time (which I do simply through the DBCompiler).

  • 0 over 1 year ago in reply to babak pouladi

    I assume you didn't cancel or end the CU setup. So I suggest contacting support.

  • +1 over 1 year ago

    I found the solution to this issue.

    Before starting the update tool OIM requires you to close all the tools and the service.

    After closing all of them and stopping the service, the update can be started, and within the first seconds after starting the update it seems to be necessary to start the service again, because the tool needs to compile afew times while updating, and this is not possible of course.

    To summarize it if you have the same issue:

    • Start the CU setup
    • Close all the tools and stop the service
    • After starting the update, start the service again, and everything should work fine