Last updated on MARCH 27, 2017
Applies to:Solaris Cluster - Version 3.3 to 4.3 [Release 3.3 to 4.3]
Oracle Solaris on x86-64 (64-bit)
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on SPARC (32-bit)
Upon attempt to create in Solaris Cluster a resource type SUNW.wls, namely an instance the agent used to control Oracle Weblogic. The creation fails because of validation errors and claim that some configuration files are missing.
In reality the files exists but are located at a different location from the one looked up by the agent.
As an example, suppose that the WebLogic instance have server name MYWLS and shall be configure in a WebLogic domain MYDOMAIN and controlled by a resource named "mywls-rs" the creation command would end up similar to this one:
The command might fails with one of these errors:
Cannot access file /apps/weblogic/Oracle/Middleware/user_projects/domains/config.xml or /apps/weblogic/Oracle/Middleware/user_projects/domains/config/config.xml: No such file or directory
Cannot access file /apps/weblogic/Oracle/Middleware/user_projects/domains/servers/MYWLS/security/boot.properties
along with one of these:
clresource: (C189917) VALIDATE on resource mywls-rs, resource group app-rg, exited with non-zero exit status.
clresource: (C720144) Validation of resource mywls-rs in resource group app-rg on node node2 failed.
clresource: (C891200) Failed to create resource "mywls-rs".
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms