Troubleshoot and Known Issues in Domain in Image

Free-Tier Autonomous Database

Free-Tier autonomous database is not supported.

RCU Datasources have Targets only to Administration Server

If you are using Domain In Image, for RAC database, then data sources that you create with the Enterprise Edition are targeted to only the administration server. Some of the data sources. like mds-owsm, opss-audit-DBDS, opss-audit-viewDS, opss-data-source need to be targeted to the WLS cluster. You need to update this after provisioning, by using the update-domain pipeline job.

Issue: Some of the data sources are not targeted to the WLS cluster.

Workaround:

Complete the following steps:

Create a model yaml file with the name ee_datasource.yaml and save it to a preferred location.

Open the ee_datasource.yaml file and copy-paste the following resources information:

Note:

Replace the administration server and cluster names in the target place holders <adminserver-name> and <cluster-name> respectively.

resources:
  JDBCSystemResource:
    'db1-mds-owsm':
      Target: '<adminserver-name>, <cluster-name>'
    'db2-mds-owsm':
      Target: '<adminserver-name>, <cluster-name>'
    'db1-opss-audit-DBDS':
      Target: '<adminserver-name>, <cluster-name>'
    'db2-opss-audit-DBDS':
      Target: '<adminserver-name>, <cluster-name>'
    'db1-opss-audit-viewDS':
      Target: '<adminserver-name>, <cluster-name>'
    'db2-opss-audit-viewDS':
      Target: '<adminserver-name>, <cluster-name>'
    'db1-opss-data-source':
      Target: '<adminserver-name>, <cluster-name>'
    'db2-opss-data-source':
      Target: '<adminserver-name>, <cluster-name>'
    'mds-owsm':
      Target: '<adminserver-name>, <cluster-name>'
    'opss-audit-DBDS':
      Target: '<adminserver-name>, <cluster-name>'
    'opss-audit-viewDS':
      Target: '<adminserver-name>, <cluster-name>'
    'opss-data-source':
      Target: '<adminserver-name>, <cluster-name>'

Run the update-domain pipeline job, with the location of the model yaml file.
After the job succeeds, from the administration console verify that the following data sources are targeted to administration server and the WLS cluster.
- mds-owsm
- opss-audit-DBDS
- opss-audit-viewDS
- opss-data-source

Handling NFS Locking Errors

By default, the WebLogic stores are mount to the shared file system, which use Network File System (NFS) version 3 and is disabled. Therefore, the file locks on the different WebLogic stores and may not release if the VM of any node pool in the WebLogic Node pool is abruptly shut down. This is encountered in different scenarios, like, when a VM is stopped, restarted, or terminated, and there are WebLogic pods assigned to the worker node that is being terminated.

Issue: The WebLogic Server Pod (Admin Server or any manged server) fails to start and displays the following error in the WebLogic logs:

[Store:280105]The persistent file store "_WLS_myinstance-admin-server" cannot open file _WLS_<instanceName>-<ServerName>000000.DAT.

Workaround:

To solve this issue, complete the following steps:

Note:

Even if you are using an earlier version of WebLogic Server you need to complete these steps.

Apply patch 32471832 by using the opatch update job, which is available in July 2021 PSUs.

For administration and managed server pods in the cluster, update the domain.yaml file by adding the Dweblogic.store.file.LockEnabled=false parameter.

Following is an example, where the Dweblogic.store.file.LockEnabled=false parameter is added:

serverPod:
  env:
  - name: USER_MEM_ARGS
    #Default to G1GC algo
    value: "-XX:+UseContainerSupport -XX:+UseG1GC -Djava.security.egd=file:/dev/./urandom"
  - name: JAVA_OPTIONS
    value: "-Dweblogic.store.file.LockEnabled=false -Dweblogic.rjvm.allowUnknownHost=true -Dweblogic.security.SSL.ignoreHostnameVerification=true -Dweblogic.security.remoteAnonymousRMIT3Enabled=false -Dweblogic.security.remoteAnonymousRMIIIOPEnabled=false"

Run the following command to apply domain.yaml.
```
kubectl -f <domain.yaml-file-path>
```

Note:

If you have created Oracle WebLogic Server for OKE instances created after July 20, 2021, or the instances on which the July 2021 PSUs are applied, a few Security warnings are displayed. See About the Security Checkup Tool.

Unable to Access the Console or the Application

Troubleshoot problems accessing the console or the application after the Oracle WebLogic Server for OKE domain is successfully created.

Error accessing the console or the application

If you receive 502 bad gateway error when accessing the Jenkins console and WebLogic Server console, or the application using load balancer, use the kubectl command to get the node ports that are used by the system and ensure that these node ports are open for access via the load balancer subnet.

For example:

kubectl describe service --all-namespaces | grep -i nodeport
NodePort: http 32062/TCP
NodePort: https 30305/TCP

To check port access:

Access the Oracle Cloud Infrastructure console.
From the navigation menu, select Networking, and then click Virtual Cloud Networks.
Select the compartment in which you created the domain.
Select the virtual cloud network in which the domain was created.
Select the subnet where the WebLogic Server compute instance is provisioned.
Select the security list assigned to this subnet.
For an Oracle WebLogic Server for OKE cluster using a private and public subnet, make sure the following ingress rules exist:

Source: <LB Subnet CIDR>
IP Protocol: TCP
Source Port Range: All
Destination Port Range: 32062

Source: <LB Subnet CIDR>
IP Protocol: TCP
Source Port Range: All
Destination Port Range: 30305

For a domain on a private and public subnet, set the Source to the CIDR of the load balancer subnet.

Stack Creation Failed

Troubleshoot a failed Oracle WebLogic Server domain that you created using Oracle WebLogic Server for OKE.

Failed to install WebLogic Operator

Stack provisioning might fail when you create a domain with Oracle WebLogic Server for OKE in a new subnet for an existing VCN due to error in installation of WebLogic Server Kubernetes Operator.

Example message:

module.provisioner.null_resource.check_provisioning_status_1  (remote-exec):
<Aug 27, 2020 07:01:31 PM GMT> <INFO>  <install_wls_operator.sh>
<(host:wrjrf8-admin.wrjrf8admin.existingnetwork.oraclevcn.com) -  <WLSOKE-VM-INFO-0020> :
Installing weblogic operator in namespace [wrjrf8-operator-ns]>
module.provisioner.null_resource.check_provisioning_status_1  (remote-exec): <Aug 27, 2020
07:02:12 PM GMT> <ERROR>  <install_wls_operator.sh>
<(host:wrjrf8-admin.wrjrf8admin.existingnetwork.oraclevcn.com) -  <WLSOKE-VM-ERROR-0013> : Error
installing weblogic operator. Exit  code[1]>