Weblogic Servers getting failed on restarting after upgrade failed.

Issue: Servers getting failed on restarting after upgrade failed.

Description: For upgradation purpose all the servers are stopped and tried for reconfig.sh but unable to open GUI due to VDI related issues at the time we planned to revert and tried to start the servers and servers are getting failed_not_restartable state and the cause is below.

The domain version 12.2.1.4.0 is greater than the release version 12.2.1.2.0 of this server when starting an Oracle® WebLogic managed server.

<Aug 6, 2021 4:12:12 AM IST> <Error> <Configuration Management> <BEA-150001> <An error occurred while connecting to the Administration Server to bootstrap through the URL: http://localhost-7001/bea_wls-management_internal1/Bootstrab , user: suAdmin.

weblogic.management.configuration.ConfigurationException: [Management:141252]The domain version 12.2.1.4.0 is greater than the release version 12.2.1.2 of this server

The cause

“The domain version 12.2.1.4.0 is greater than the release version 12.2.1.2 of this server.” because the AdminServer console footer said it was version 12.2.1.2.0.

I discovered there were 12.2.1.4.0 binaries installed in a new $ORACLE_HOME, but as mentioned, these binaries were not referenced by the scripts in $DOMAIN_HOME/bin.

The fact that 12.2.1.4.0 binaries were available on the file system suggested someone had either planned to create a new 12.2.1.2.0 domain, or planned to upgrade the existing 12.2.1.4.0 domain.

After discussing this with a colleague it became clear that he had installed the new binaries, and that all he wanted to do with them was to create response files for running the upgrade of a domain on a different server. He only intended to run the information collection part, but it had obviously also touched the $DOMAIN_HOME/config/config.xml file in the 12.2.1.4.0 domain, and changed the version parameter to 12.2.1.2.0 as shown below:

$ grep version $DOMAIN_HOME/config/config.xml
<?xml version=’1.0′ encoding=’UTF-8′?>
<domain-version>12.2.1.2.0</domain-version>
<configuration-version>12.2.1.2.0</configuration-version>

The solution

Shutdown the entire domain. In my case that meant the AdminServer and the NodeManager.
Took a file system backup of $DOMAIN_HOME
Edited $DOMAIN_HOME/config/config.xml and replaced the two occurences of 12.2.1.4.0 with 12.1.2.0.0
Started the NodeManager, the AdminServer and the managed servers up without any errors.

Post-change verification:

$ grep version config.xml

<?xml version=’1.0′ encoding=’UTF-8′?>

<domain-version>12.2.1.4.0</domain-version>

<configuration-version>12.2.1.4.0</configuration-version>

Conclusion: If you see any issues like above shutdown entire domain,nodemanager and take backup of Domain_home and replaced the version on config.xml as per above and clear cache and tmp and tried to restart will get success.

Sammeta Sudheer