Troubleshooting
Problem
After a switch back (switchmgr) to 10.2.1.00, 10.2.0.00, or 10.1.0.0x from a Master at 10.2.2.00 or newer, the submission of Broker jobs will fail.
Apply this iFix to an older Master in the event a switchmgr from a newer Master is warranted.
It is recommended to install it if the user plan to switch back (switchmgr) to 10.1 after a switch to 10.2.2 and upper level.
Into WLP logs:
[05/08/2026, 10:00:41:400 BST] 000053e4 com.ibm.scheduling.msg.JobDispatcherMsg E AWKJDE072E The allocation request for job "8e185ad0-5c66-3c36-8fc8-b12f012fe8f4" failed because of the following Resource Advisor error: "AWKRAE024E The resource allocation failed. The following error was returned:"Service not initialized".".
Additional details can be found in trace.log after enabling broker traces.
[31/08/2026, 09:32:17:947 BST] 00000081 id=00000000 com.ibm.scheduling.dao.rdbms.util.DatabaseStatement > executeSelect ENTRY
[31/08/2026, 09:32:17:945 BST] 000000bf id=00000000 ing.resourceadvisor.allocation.manager.AllocationManagerImpl > allocateResource ENTRY
[31/08/2026, 09:32:17:947 BST] 000000bf id=00000000 com.ibm.scheduling.resourceadvisorutil 3 New allocation requested. There are 0 allocations in cache and the max allowed is 5,000.
[31/08/2026, 09:32:17:947 BST] 000000bf id=00000000 com.ibm.scheduling.resourceadvisorutil 1 Throwing ServiceUnavailableException for allocation requested for job null because there are 0 allocations in cache and the max allowed is 5,000 or the AllocationManager is not initialized yet.
[31/08/2026, 09:32:17:949 BST] 000000bf id=00000000 com.ibm.scheduling.msg.JobDispatcherMsg E AWKJDE072E The allocation request for job "3971f6da-c7d4-3b7f-97a3-d897f7a36eb4" failed because of the following Resource Advisor error: "AWKRAE024E The resource allocation failed. The following error was returned:"Service not initialized".".
[31/08/2026, 09:32:17:950 BST] 000000bf id=00000000 eduling.jobdispatcher.impl.plugin.WSAllocationManagementImpl 1 allocateResource The Job Dispatcher request resource alloaction to the Resource Advisor for Job 3971f6da-c7d4-3b7f-97a3-d897f7a36eb4 because of the following Resource Advisor internal error: AWKRAE024E The resource allocation failed. The following error was returned:"Service not initialized"..
[31/08/2026, 09:32:17:950 BST] 000000bf id=00000000 .ibm.scheduling.jobdispatcher.handlers.AllocateResourcesWork 1 run Failed to invoke the Resource Advisor for requesting resource for job 3971f6da-c7d4-3b7f-97a3-d897f7a36eb4. Unrecoverable exception: AWKRAE024E The resource allocation failed. The following error was returned:"Service not initialized".
[31/08/2026, 09:32:17:950 BST] 000000bf id=00000000 com.ibm.scheduling.jobdispatcher.context.JobContext > updateState ENTRY
[31/08/2026, 09:32:17:950 BST] 000000bf id=00000000 com.ibm.scheduling.jobdispatcher.context.JobContext 1 updateState Job with jobid 3971f6da-c7d4-3b7f-97a3-d897f7a36eb4 is going into state 41 with the following status message: null
[31/08/2026, 09:32:17:950 BST] 000000bf id=00000000 com.ibm.scheduling.jobdispatcher.context.JobContext > update ENTRY
[31/08/2026, 09:32:17:950 BST] 000000bf id=00000000 com.ibm.scheduling.dao.rdbms.util.Session 1 isTransactionActive Check if transaction is active null
Problem Summary Text Display
"Service not initialized" error while running the jobs on agents after upgrade
Cause
Resolving The Problem
Install the IJ60834 package available for download from IBM Fix Central.
*Note: This iFix must also be installed on any DDM and Backup DDM at version 10.2.1.00 or earlier. This is because the DDM component accesses its own Broker application and its own database with the same design as a Master instance.
Document Location
Worldwide
Was this topic helpful?
Document Information
Modified date:
03 November 2026
UID
ibm17294897