My Oracle Support Banner

After applying Microsoft KB, DBCA Fails With [DBT-50000] Unable To Check For Available Memory (Doc ID 2807229.1)

Last updated on SEPTEMBER 23, 2021

Applies to:

Oracle Database Configuration Assistant - Version 19.3.0.0.0 and later
Information in this document applies to any platform.

Symptoms

After applying Microsoft Patch KB5005030 for Windows 2019 DataCenter Edition 64bit Server, attempts to run DBCA generates a "SEVERE: [FATAL] [DBT-50000] Unable to check for available memory."
The DBCA log ($ORACLE_BASE/cfgtoollogs/dbca/<DBNAME>/trace.log) shows:

[pool-1-thread-1] [ 2021-08-31 12:39:24.375 EDT ] [OracleHome.hasEELicense:357]  home=D:\oracle\product\19.3.0 has EE licensing
SEVERE: Aug 31, 2021 12:39:24 PM oracle.install.commons.util.exception.AbstractErrorAdvisor getDetailedMessage
SEVERE: [FATAL] [DBT-50000] Unable to check available system memory.
   CAUSE: An exception occured while checking kernel parameter.
*ADDITIONAL INFORMATION:*
Exception details
 - PRVG-1901 : failed to setup CVU remote execution framework directory "C:\Users\someuser\AppData\Local\Temp\CVU_19.0.0.0.0_someuser\" on nodes "somenode" Please select a different work area for the framework PRVH-0516 : failed to retrieve CVU remote execution framework version from node "somenode" during an attempt to setup remote execution framework directory "C:\Users\someuser\AppData\Local\Temp\CVU_19.0.0.0.0_someuser\" somenode : PRKN-1014 : Failed to execute remote command "C:\Users\someuser\AppData\Local\Temp\CVU_19.0.0.0.0_someuser\\exectask.exe" on node "SOMENODE".Cannot run program "C:\Users\someuser\AppData\Local\Temp\CVU_19.0.0.0.0_someuser\\exectask.exe": CreateProcess error=2, The system cannot find the file specified somenode : Cannot run program "C:\Users\someuser\AppData\Local\Temp\CVU_19.0.0.0.0_someuser\\exectask.exe": CreateProcess error=2, The system cannot find the file specified

oracle.assistants.common.base.exception.CVUException: [DBT-50000] Unable to check available system memory.
    at oracle.assistants.common.lib.CVUHelper.checkAvailableMemory(CVUHelper.java:104)
    at oracle.assistants.dbca.validator.extsupport.MemoryMgmtCheck.validateAvailableMemory(MemoryMgmtCheck.java:210)
    at oracle.assistants.dbca.validator.MemoryMgmtValidator.validate(MemoryMgmtValidator.java:130)
    at oracle.assistants.dbca.validator.TypicalModeDBCreationValidator.validate(TypicalModeDBCreationValidator.java:64)
    at oracle.install.commons.flow.validation.ValidationHelper.validateState(ValidationHelper.java:194)
    at oracle.install.commons.flow.AbstractFlowExecutor.validate(AbstractFlowExecutor.java:527)
    at oracle.install.commons.flow.AbstractFlowExecutor.leaveVertex(AbstractFlowExecutor.java:835)
    at oracle.install.commons.flow.AbstractFlowExecutor.transition(AbstractFlowExecutor.java:434)
    at oracle.install.commons.flow.AbstractFlowExecutor.nextState(AbstractFlowExecutor.java:360)
    at oracle.install.commons.flow.AbstractFlowExecutor.nextViewState(AbstractFlowExecutor.java:315)
    at oracle.install.commons.flow.DefaultFlowNavigator.goForward(DefaultFlowNavigator.java:58)
    at oracle.install.commons.flow.jewt.FlowWizard$1.run(FlowWizard.java:190)
    at oracle.install.commons.flow.jewt.FlowWizard$TransitionManager$1.run(FlowWizard.java:160)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    at java.lang.Thread.run(Thread.java:748)

Changes

OS patch was applied.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.