5 Known Issues

  1. Migration script fails during infrastructure discovery

    When running the migration script, you may encounter the following error:

    bash migration_script.sh
2025-09-24 06:03:46 [info] Installing dependencies...
2025-09-24 06:03:47 [info] Checking prerequisites...
2025-09-24 06:03:57 [info] Discovering WebLogic domain...
2025-09-24 06:04:20 [info] Discovering infrastructure...
2025-09-24 06:04:30 [error] "Discovering infrastructure" failed. Check /home/domain/mig/oci-weblogic-migration/logs/migration_script.log for details. Run migration_script.sh again after resolving the issue.
2025-09-24 06:04:30 [error] Migration failed.
    In the log file (/home/domain/mig/oci-weblogic-migration/logs/migration_script.log), you may see an error similar to:
    <SEVERE> <discover_infra> <WLSDPLY-20035> <verifySSH encountered an unexpected runtime exception.
Please file an issue on GitHub and attach the log file and stdout. Exception: exceptions.IndexError>

    Cause

    This is an intermittent issue triggered during the infrastructure discovery phase by the verifySSH step.

    Workaround

    Re-run the migration script. Previous successful steps will be skipped automatically, and the script should proceed normally:
    bash migration_script.sh
2025-09-24 06:05:49  [info] "Installing dependencies" already completed successfully. Skipping.
2025-09-24 06:05:49  [info] "Checking prerequisites" already completed successfully. Skipping.
2025-09-24 06:05:49  [info] "Discovering WebLogic domain" already completed successfully. Skipping.
2025-09-24 06:05:49  [info] Discovering infrastructure...
...
2025-09-24 06:08:16  [info] Migration script completed successfully!
  2. Migration script fails in Archive Domain Step

    If the script fails during the Archive Domain step due to insufficient disk space on any of the nodes, the log file will display a TODO message. These TODO messages include the exact commands that must be executed manually on the affected host to complete the archive creation process.

    Example: If the migration_script.log shows:

    WARNING Messages:

        1. WLSDPLY-05027: Not enough space on mbnjrf_machine_1 to create the archives. Please run the commands manually mentioned in the TODO to create the archive, scp to the admin host and upload to bucket.
        2. WLSDPLY-05027: Not enough space on mbnjrf_machine_2 to create the archives. Please run the commands manually mentioned in the TODO to create the archive, scp to the admin host and upload to bucket.

TODO Messages:

        1. WLSDPLY-06042: Please create the FILE_STORE in the archive file at /usr/bin/tar czf /tmp/mbnjrf_machine_1-mbnjrf_domain-java_home.tar.gz --exclude='.pid' --exclude='.state' --exclude='.core' --exclude='diag/ofm/*/*/lck/*.lck' --exclude='servers/*/logs/*.*' --exclude='*.log*[0-9]' --exclude='*.log' --exclude='*.out' --exclude='*.out*[0-9]' --exclude='servers/*/data/store/diagnostics/*' --exclude='oracle-dfw-*/sampling/jvm_threads*' /u01/app/oracle/jdk .
        2. WLSDPLY-06042: Please create the FILE_STORE in the archive file at /usr/bin/tar czf /tmp/mbnjrf_machine_1-mbnjrf_domain-domain_home.tar.gz --exclude='.pid' --exclude='.state' --exclude='.core' --exclude='diag/ofm/*/*/lck/*.lck' --exclude='servers/*/logs/*.*' --exclude='*.log*[0-9]' --exclude='*.log' --exclude='*.out' --exclude='*.out*[0-9]' --exclude='servers/*/data/store/diagnostics/*' --exclude='oracle-dfw-*/sampling/jvm_threads*' /u01/data/domains/mbnjrf_domain .
        3. WLSDPLY-06042: Please create the FILE_STORE in the archive file at /usr/bin/tar czf /tmp/mbnjrf_machine_1-mbnjrf_domain-weblogic_home.tar.gz --exclude='.pid' --exclude='.state' --exclude='.core' --exclude='diag/ofm/*/*/lck/*.lck' --exclude='servers/*/logs/*.*' --exclude='*.log*[0-9]' --exclude='*.log' --exclude='*.out' --exclude='*.out*[0-9]' --exclude='servers/*/data/store/diagnostics/*' --exclude='oracle-dfw-*/sampling/jvm_threads*' /u01/app/oracle/middleware .
        4. WLSDPLY-06042: Please create the FILE_STORE in the archive file at /usr/bin/tar czf /tmp/mbnjrf_machine_1-mbnjrf_domain-custom_dirs.tar.gz --exclude='.pid' --exclude='.state' --exclude='.core' --exclude='diag/ofm/*/*/lck/*.lck' --exclude='servers/*/logs/*.*' --exclude='*.log*[0-9]' --exclude='*.log' --exclude='*.out' --exclude='*.out*[0-9]' --exclude='servers/*/data/store/diagnostics/*' --exclude='oracle-dfw-*/sampling/jvm_threads*' /u01/data/domains/mbnjrf_domain/wlsdeploy/applications .
        5. WLSDPLY-06042: Please create the FILE_STORE in the archive file at /usr/bin/tar czf /tmp/mbnjrf_machine_2-mbnjrf_domain-java_home.tar.gz --exclude='.pid' --exclude='.state' --exclude='.core' --exclude='diag/ofm/*/*/lck/*.lck' --exclude='servers/*/logs/*.*' --exclude='*.log*[0-9]' --exclude='*.log' --exclude='*.out' --exclude='*.out*[0-9]' --exclude='servers/*/data/store/diagnostics/*' --exclude='oracle-dfw-*/sampling/jvm_threads*' /u01/app/oracle/jdk .
        6. WLSDPLY-06042: Please create the FILE_STORE in the archive file at /usr/bin/tar czf /tmp/mbnjrf_machine_2-mbnjrf_domain-domain_home.tar.gz --exclude='.pid' --exclude='.state' --exclude='.core' --exclude='diag/ofm/*/*/lck/*.lck' --exclude='servers/*/logs/*.*' --exclude='*.log*[0-9]' --exclude='*.log' --exclude='*.out' --exclude='*.out*[0-9]' --exclude='servers/*/data/store/diagnostics/*' --exclude='oracle-dfw-*/sampling/jvm_threads*' /u01/data/domains/mbnjrf_domain .
        7. WLSDPLY-06042: Please create the FILE_STORE in the archive file at /usr/bin/tar czf /tmp/mbnjrf_machine_2-mbnjrf_domain-weblogic_home.tar.gz --exclude='.pid' --exclude='.state' --exclude='.core' --exclude='diag/ofm/*/*/lck/*.lck' --exclude='servers/*/logs/*.*' --exclude='*.log*[0-9]' --exclude='*.log' --exclude='*.out' --exclude='*.out*[0-9]' --exclude='servers/*/data/store/diagnostics/*' --exclude='oracle-dfw-*/sampling/jvm_threads*' /u01/app/oracle/middleware .

    Workaround

    Then, log in to that specific host and run the indicated command manually. After the archive is successfully created:
    1. Upload the generated archive file to the designated Object Storage bucket manually or
    2. Use the OCI CLI to upload the file if the OCI CLI is installed on the instance.
    Example (OCI CLI upload): 
    
oci os object put --bucket-name <bucket_name> --file <archive_file_path> --force

    Ensure that all required domain archives are uploaded before proceeding with stack creation.

  3. Error when starting Managed Servers (Hostname Verification Failure)

    You may encounter an error when attempting to start managed servers:

    <Warning> <Security> <BEA-090504> <Certificate chain received from xxxx.example.com - 10.0.2.229 failed hostname verification check. Certificate contained CN=xxxx but check expected xxxx.example.com>

    Cause

    This occurs because the SSL certificate presented by the server does not match the expected hostname.

    For example, the certificate contains the common name CN=xxxx, while WebLogic expects xxxx.example.com. This mismatch causes hostname verification to fail.

    Workaround

    If the source domain is configured with the following in config.xml:
    weblogic.security.SSL.ignoreHostnameVerification=true
    Then you must apply the same setting manually for each managed server:
    1. Start the Admin Server.
    2. Log in to the WebLogic Administration Console.
    3. Navigate to: Environment → Servers → [Managed Server Name] → Server Start tab.
    4. For each Managed Server, add the following JVM option in the Arguments field: 
      -Dweblogic.security.SSL.ignoreHostnameVerification=true
    5. Use the startManagedServer.sh script to start the Managed Servers.
  4. Error when starting Managed Server in WebLogic 12.2.1.4 (secure mode)

    When starting a Managed Server with WebLogic 12.2.1.4 in secure mode, you may see errors such as:

    <BEA-003111> <No channel exists for replication calls for cluster domainCcluster>
<BEA-000386> <Server subsystem failed. Reason: No replication server channel for managedserver1>
Server state changed to FAILED

    Cause

    In secure mode, WebLogic expects replication channels for cluster communication. If no replication channel is configured, the Managed Server startup fails.

    Workaround

    Disable secure replication in the domain configuration (config.xml) before starting the servers.

    <secure-replication-enabled>false</secure-replication-enabled>

    Note:

    This issue has been addressed in the latest code base, and the configuration is automatically handled by the migration tool. No manual action is required.

    However, if the /var/log/owm/wls-restore.log file indicates that this configuration step has failed, perform the above workaround manually before starting the servers, following the instructions provided in this section.