My Oracle Support Banner

FS_CLONE Fails With ERROR: S_PATCH_SERVICE_NAME is not set correctly (Doc ID 2923074.1)

Last updated on JANUARY 23, 2023

Applies to:

Oracle Applications DBA - Version 12.2.4 and later
Information in this document applies to any platform.

Symptoms

adop phase=fs_clone
ERROR
-----------------------
Validating configuration on admin node: [hostname].
Output: remote_execution_result_level1.xml
[ERROR] txkADOPValidation failed on Node: "<hostname>"
[ERROR] txkADOPValidation failed or is incomplete on Admin node: <hostname>
[ERROR] Unable to continue processing on other available nodes: vonsaurma
[UNEXPECTED]Error running "txkADOPValidation" on node(s): <hostname>.


ADOPValidations_detailed.log shows:
==================================
Inside checkServiceNameExists()...
==================================
search_service_name: <instance_name>_ebs_patch.WORLD

Service name found.
valid_service_name: <instance_name>_ebs_patch.WORLD
ctx_patch_service_name: <instance_name>_ebs_patch

ERROR: S_PATCH_SERVICE_NAME context variable is not set correctly in the context file.

Corrective Action: Make sure that AutoConfig is executed on all Application Tier nodes.

Changes

 Recently Applied AD/TXK 14

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
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.