weblogic-deploy-tooling: WDT3: Error occurred in "OPSS Processing" phase execution

We are using WDT for domain config of MW components (OAM, OHS, OSB, SOA, …)
Currently, we are working on upgrading WDT from 1.9.20 to 3.2.5 (the latest version)

The flow we follow is simply;

ensure rcu schemas are setup using oracle’s rcu utility, each schema has a unique pwd
domain config (createDomain) using WDT by feeding it with WDT templates

While applying this for OAM domain, I get an error at createDomain phase.
NB! this works fine when using WDT 1.9.20 and this error happens only when using the WDT 3.x.x

...
####<Oct 6, 2023 10:17:09 AM> <FINER> <DomainCreator> <__apply_base_domain_config> <> <RETURN>
####<Oct 6, 2023 10:17:09 AM> <INFO> <DomainCreator> <__extend_domain_with_select_template> <WLSDPLY-12205> <Writing base domain elhoam_domain to directory /u01/elhoam/domain/elhoam_domain>
####<Oct 6, 2023 10:17:09 AM> <FINER> <WlstHelper> <write_domain> <> <ENTRY /u01/elhoam/domain/elhoam_domain>
####<Oct 6, 2023 10:17:18 AM> <FINER> <WlstHelper> <write_domain> <> <THROW
oracle.weblogic.deploy.create.CreateException: WLSDPLY-00044: writeDomain(/u01/elhoam/domain/elhoam_domain) failed : Error writing domain:
64254: Error occurred in "OPSS Processing" phase execution
64254: Encountered error: oracle.security.opss.tools.lifecycle.LifecycleException: JDBC password for opss-audit-DBDS is missing for configuring security store to database.
64254: Check log for more detail.
null
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
        at org.python.core.PyReflectedConstructor.__call__(Unknown Source)
        at org.python.core.PyJavaInstance.__init__(Unknown Source)
        at org.python.core.PyJavaClass.__call__(PyJavaClass.java:891)
        at org.python.core.PyObject.__call__(Unknown Source)
        at wlsdeploy.exception.exception_helper$py.create_create_exception$4(/u01/binaries/elhoam/wdt/3.2.5/weblogic-deploy/lib/python/wlsdeploy/exception/exception_helper.py:102)
        at wlsdeploy.exception.exception_helper$py.call_function(/u01/binaries/elhoam/wdt/3.2.5/weblogic-deploy/lib/python/wlsdeploy/exception/exception_helper.py)
        at org.python.core.PyTableCode.call(Unknown Source)
        at org.python.core.PyTableCode.call(Unknown Source)
        at org.python.core.PyFunction.__call__(PyFunction.java:193)
        at org.python.core.PyObject._callextra(Unknown Source)
        at wlsdeploy.exception.exception_helper$py.create_exception$2(/u01/binaries/elhoam/wdt/3.2.5/weblogic-deploy/lib/python/wlsdeploy/exception/exception_helper.py:74)
        at wlsdeploy.exception.exception_helper$py.call_function(/u01/binaries/elhoam/wdt/3.2.5/weblogic-deploy/lib/python/wlsdeploy/exception/exception_helper.py)
        at org.python.core.PyTableCode.call(Unknown Source)
        at org.python.core.PyTableCode.call(Unknown Source)
        at org.python.core.PyFunction.__call__(PyFunction.java:193)
        at wlsdeploy.tool.util.wlst_helper$py.write_domain$38(/u01/binaries/elhoam/wdt/3.2.5/weblogic-deploy/lib/python/wlsdeploy/tool/util/wlst_helper.py:764)
        at wlsdeploy.tool.util.wlst_helper$py.call_function(/u01/binaries/elhoam/wdt/3.2.5/weblogic-deploy/lib/python/wlsdeploy/tool/util/wlst_helper.py)
        at org.python.core.PyTableCode.call(Unknown Source)
        at org.python.core.PyTableCode.call(Unknown Source)
        at org.python.core.PyTableCode.call(Unknown Source)
        at org.python.core.PyFunction.__call__(PyFunction.java:199)
        at org.python.core.PyMethod.__call__(Unknown Source)
        at org.python.core.PyObject.__call__(Unknown Source)
        at org.python.core.PyObject.invoke(Unknown Source)
 ...  
        at wlsdeploy.tool.create.domain_creator$py._DomainCreator__extend_domain_with_select_template$18(/u01/binaries/elhoam/wdt/3.2.5/weblogic-deploy/lib/python/wlsdeploy/tool/create/domain_creator.py:661)
        at wlsdeploy.tool.create.domain_creator$py.call_function(/u01/binaries/elhoam/wdt/3.2.5/weblogic-deploy/lib/python/wlsdeploy/tool/create/domain_creator.py)
        at org.python.core.PyTableCode.call(Unknown Source)
        at org.python.core.PyTableCode.call(Unknown Source)
        at org.python.core.PyTableCode.call(Unknown Source)
...
        at weblogic.management.scripting.WLST.main(WLST.java:186)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at weblogic.WLST.main(WLST.java:47)
Caused by: com.oracle.cie.domain.script.jython.WLSTException: Error writing domain:
64254: Error occurred in "OPSS Processing" phase execution
64254: Encountered error: oracle.security.opss.tools.lifecycle.LifecycleException: JDBC password for opss-audit-DBDS is missing for configuring security store to database.
64254: Check log for more detail.
null
        at com.oracle.cie.domain.script.jython.CommandExceptionHandler.handleException(CommandExceptionHandler.java:69)
        at com.oracle.cie.domain.script.jython.WLScriptContext.handleException(WLScriptContext.java:3085)
        at com.oracle.cie.domain.script.jython.WLScriptContext.runCmd(WLScriptContext.java:738)
        at sun.reflect.GeneratedMethodAccessor800.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)

If needed, I can also send the full createDomain.log

Please kindly advise, your feedback is much appreciated

Regards Yilmaz

About this issue

Original URL
State: closed
Created 9 months ago
Comments: 36 (17 by maintainers)

Most upvoted comments

Oh I see the problem. I do the reset before the topology is created, so set targets failed. Can you try this again. I don’t have an easy way to test OAM.

weblogic-deploy.zip

jshum2479 on Oct 10, 2023

@zeusbaba https://github.com/oracle/weblogic-deploy-tooling/releases/tag/release-3.2.6

robertpatrick on Oct 13, 2023

@zeusbaba I will try to get a new release created tomorrow.

robertpatrick on Oct 12, 2023

My suggestion is we focus on making the JRF domain creation work properly. WDT does not officially support OAM so once the JRF use case is working, you should be able to use a valid typedef file for OAM and have it work properly.

What fields are needed in the typedef file to create a domain with RCU schemas has not changed. I suppose it is possible that WDT 1.9.x might have been more tolerant of typedef file omissions/errors but that doesn’t constitute a regression in my mind.

robertpatrick on Oct 11, 2023

You should also consider changing your custom typedefs to set the serverGroupToTargets and dynamicClusterServerGroupsToTarget, check the JRF.json for syntax. I don’t know the details for OAM but usually you can get that if you are using the graphical config wizard. That way your sparse jdbc part of the model only have to override what you need and no need to provide the whole portion, the template should have all the common attributes set. We use the information in RCUDbinfo for the default connection information where all schemas use, and then the sparse model can be used as an override if needed (e.g. just override the credentials, initial connection pool connections).

jshum2479 on Oct 10, 2023

I make a minor change, can you use this instead.

weblogic-deploy.zip

jshum2479 on Oct 10, 2023

Our logic depends on that, so you should put list out the schemas there.

jshum2479 on Oct 10, 2023

@zeusbaba I have created a fix for the issue, if you don’t mind, can you test this out in your environment?

weblogic-deploy.zip

jshum2479 on Oct 10, 2023

@zeusbaba Thanks, we have managed to identify an issue so Johnny is working to try to understand what needs to be done to correct the problem. Once we identify a fix, it would be good if we could send you an installer to test to make sure that it resolves your issue prior to releasing a new version.

robertpatrick on Oct 10, 2023