Upgrade to 7.3.5 for a Cluster Environment Fails During ReassociateSecurityStore
(Doc ID 2384348.1)
Last updated on JULY 14, 2020
Applies to:
Oracle Communications Unified Inventory Management - Version 7.3.5.0.0 and laterInformation in this document applies to any platform.
Symptoms
During upgrade from UIM 7.2.5 to UIM 7.3.5 ,when running the reassociate command in WLST observing below error:
reassociateSecurityStore(domain="uim_domain",datasourcename="jdbc/opssDataSource",servertype="DB_ORACLE",jpsroot="cn=jdbcRootNode")
Location changed to domainRuntime tree. This is a read-only tree with DomainMBean as the root.
For more help, use help(domainRuntime)
Starting policy store reassociation.
The store and ServiceConfigurator setup done.
Schema is seeded into the store
Data is migrated to the store. Check logs for any failures or warnings during migration.
Command FAILED, Reason: JPS-09008: Application policy for application oracle.communications.inventory does not exist.
Traceback (innermost last):
File "", line 1, in ?
File "/opt/oracle/Middleware/oracle_common/common/wlst/jpsWlstCmd.py", line 1569, in reassociateSecurityStore
File "/opt/oracle/Middleware/oracle_common/common/wlst/jpsWlstCmd.py", line 1543, in reassociateSecurityStoreImpl
at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:237)
at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:223)
at javax.management.remote.rmi.RMIConnectionImpl_1036_WLStub.invoke(Unknown Source)
at weblogic.management.remote.common.RMIConnectionWrapper$16.run(ClientProviderBase.java:918)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
at weblogic.security.Security.runAs(Security.java:61)
at weblogic.management.remote.common.RMIConnectionWrapper.invoke(ClientProviderBase.java:916)
at javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection.invoke(RMIConnector.java:1020)
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)
Location changed to domainRuntime tree. This is a read-only tree with DomainMBean as the root.
For more help, use help(domainRuntime)
Starting policy store reassociation.
The store and ServiceConfigurator setup done.
Schema is seeded into the store
Data is migrated to the store. Check logs for any failures or warnings during migration.
Command FAILED, Reason: JPS-09008: Application policy for application oracle.communications.inventory does not exist.
Traceback (innermost last):
File "", line 1, in ?
File "/opt/oracle/Middleware/oracle_common/common/wlst/jpsWlstCmd.py", line 1569, in reassociateSecurityStore
File "/opt/oracle/Middleware/oracle_common/common/wlst/jpsWlstCmd.py", line 1543, in reassociateSecurityStoreImpl
at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:237)
at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:223)
at javax.management.remote.rmi.RMIConnectionImpl_1036_WLStub.invoke(Unknown Source)
at weblogic.management.remote.common.RMIConnectionWrapper$16.run(ClientProviderBase.java:918)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
at weblogic.security.Security.runAs(Security.java:61)
at weblogic.management.remote.common.RMIConnectionWrapper.invoke(ClientProviderBase.java:916)
at javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection.invoke(RMIConnector.java:1020)
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)
Changes
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 |