Fs_Clone Fails With "ERRORMSG: File instantiation failed"

 Fs_Clone Fails With "ERRORMSG: File instantiation failed"

FS CLONE FAILES WITH THE FOLLOWING ERROR

Fs_clone fails with the following error:

Completed FSCloneStage...
Wed Jan 3 14:51:37 2018
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
Error occurred during initialization of VM
java.lang.Error: Properties init: Could not determine current working directory.
  at java.lang.System.initProperties(Native Method)
  at java.lang.System.initializeSystemClass(System.java:1119)

*******FATAL ERROR*******
PROGRAM : (<DIR>/oracle/fs1/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSynchronize.pl)
TIME : Wed Jan 3 14:57:29 2018
FUNCTION: main::instantiateFile [ Level 1 ]
ERRORMSG: File instantiation failed

--

 found that fs_clone fails when verifying ports:

Filename: adop.log
 [ERROR]     adop phase=fs_clone failed or is incomplete on Admin node: <HOST1>
 [ERROR]     Unable to continue processing on other available nodes: <HOST2>,<HOST3>
 [UNEXPECTED]Error running "adop phase=fs_clone" on node(s): house201.

Filename: txkCloneAcquirePort.log
 Attempting to close socket on port 6101
 Attempting to close socket on port 6201
 Attempting to close socket on port 10000

To solve the issue please do the following:

1. Make sure no services or processes are running from the PATCH file system

2. Ensure the Weblogic Admin Server and Node Manager are running on the Run File system. You can run the following commands to check the status:

    $ adadminsrvctl.sh status
    $ adnodemgrctl.sh status

3. Run these in order:

    $ adop phase=cleanup cleanup_mode=full
      $ adop phase=fs_clone force=yes

fs_clone completed without any issues.

ebs r12 19c Upgrade Process

 EBS R12 19C UPGRADE PROCESS

For Oracle E-Business Suite database upgrades to Oracle Database 19c:

• Oracle Database Release Update 19.3 as well as Release Update 19.5 and later are certified.
• Oracle recommends that you upgrade to the latest Oracle Database Release Update that is certified with Oracle E-Business Suite. Applying the latest Release Update will ensure that you have the security-related fixes and high-priority non-security fixes. See Release Update Introduction and FAQ, Document 2285040.1, for more details.
• You can upgrade directly from an earlier Oracle Database version to Oracle Database Release Update 19.3 or Release Update 19.6 or later.
• You cannot upgrade directly to Oracle Database Release Update 19.5. You must first upgrade from your earlier Oracle Database version to Oracle Database 19.3, and then apply Oracle Database Release Update 19.5.

 

Make sure you confirm that your platform and environment requirements are certified with your Oracle E-Business Suite Release and Oracle Database 19c.

Document to follow

-----------------------

• Document 2552181.1, Interoperability Notes: Oracle E-Business Suite Release 12.2 with Oracle Database 19c
• Document 2530665.1, Using Oracle 19c RAC Multitenant (Single PDB) with Oracle E-Business Suite Release 12.2

Information Center: Oracle Database 19c with Oracle E-Business Suite 12.2 and 12.1 (Doc ID 2655839.2)

 Information Center: Oracle Database 19c with Oracle E-Business Suite 12.2 and 12.1 (Doc ID 2655839.2)

Oracle Database 19c Oracle Database 19c, is the latest Long Term Release, offering Premier Support through April 2024, and Extended Support through April 2027. It is available on Linux, Windows, Solaris, HP/UX and AIX platforms as well as the Oracle Cloud. Oracle Database 19c offers customers the best performance, scalability, reliability and security for all their operational and analytical workloads. Oracle Database 19c - What's New Oracle Database Upgrade Guide 19c Oracle Database Installation Guide 19c Database Performance Tuning Guide Oracle Grid Infrastructure Grid Infrastructure Installation and Upgrade Guide, 19c for Linux     NOTE:2662860.1 - 19c Database with Oracle E-Business Suite R12 Known Issues & Solutions

Database Initialization Parameter Sizing for Oracle E-Business Suite Release 12

 Database Initialization Parameter Sizing 

section provides sizing recommendations based on the active Oracle E-Business Suite user counts. The following table should be used to size the relevant parameters:

Parameter Name	Development or Test Instance	11-100 Users	101-500 Users	501-1000 Users	1001-2000 Users
processes	200	200	800	1200	2500
sessions	400	400	1600	2400	5000
sga_target Footnote 1	2G	2G	2G	3G	14G
shared_pool_size	400M	600M	800M	1000M	2000M
shared_pool_reserved_size	40M	60M	80M	100M	100M
pga_aggregate_target	1G	2G	4G	10G	20G
Total Memory Required Footnote 2	~ 3 GB	~ 4 GB	~ 6 GB	~ 13 GB	~ 34 GB

General Notes on Sizing Table

• "Development or Test instance" refers to a small instance used only for development or testing, with no more than 10 users.
  
  
• The range of user counts provided above refers to active Oracle E-Business Suite users, not total or named users. For example, if you plan to support a maximum of 500 active Oracle E-Business Suite users, then you should use the sizing as per the range 101-500 users.
  
  
• The parameter values provided in this document reflect a small instance configuration, and you should adjust the relevant parameters based on the Oracle E-Business Suite user counts as listed in the table above.

Footnote 1

• The parameter sga_target should be used for Oracle 11g or 12c or 19c based environments. Also, it is not necessary to set the parameter undo_retention for 11g or 12c or 19c-based systems,  since undo retention is set automatically as part of automatic undo tuning

• Enabling the 11g or 12c Automatic Memory Management (AMM) feature is supported in Oracle E-Business Suite, and has been found to be useful in scenarios where memory is limited, as it will dynamically adjust the SGA and PGA pool sizes. 
• AMM is enabled by using the memory_target and memory_max_target initialization parameters. MEMORY_TARGET specifies the system-wide sharable memory for Oracle to use when dynamically controlling the SGA and PGA as workloads change. The memory_max_target parameter specifies the maximum size that memory_target may take. AMM has proven useful for small to mid-range systems as it simplifies both the configuration and management. However, many customers with large production systems have experienced better performance with manually sized pools (or large minimum values for the pools). 
• On Linux, Hugepages has resulted in improved performance; however, this configuration is not compatible with AMM. 
• For large mission-critical applications systems, it is advisable to set sga_target with a minimum fixed value for shared_pool_size and pga_aggregate_target.

Footnote 2

• The total memory required refers to the amount of memory required for the database instance and associated memory, including the SGA and the PGA. You should ensure that your system has sufficient available memory in order to support the values provided above. The values provided above should be adjusted based on available memory so as to prevent paging and swapping.

Database Initialization Parameters for Oracle E-Business Suite Release 12

Database Initialization Parameters for Oracle E-Business Suite Release 12 (Doc ID 396009.1)

Mostly talking about 19c (multitenant) 

For Oracle Database 19c with a single tenant (1 CDB:1 PDB) configuration:

Update Database Initialization Parameter at PDB level

• By default, initialization parameters at the PDB level inherit the value from the initialization parameters at the CDB level.
• There are parameters that can be changed at the PDB level and override what is being inherited from the CDB.
• To identify which parameters can be modified for a PDB, the ISPDB_MODIFIABLE column in the V$SYSTEM_PARAMETER view must be TRUE.
•   If the ISPDB_MODIFIABLE is TRUE then the parameter inherits the value from the CDB until it is changed with an ALTER SYSTEM SET command at the PDB.
• The initialization parameter set at the PDB level aren't stored in the spfile. They are stored in a data dictionary table in the root of the CDB (SYS.PDB_SPFILE$).
• When a PDB is moved around (through an unplug/plug), the initialization parameters set at the PDB level are part of the metadata stored in the XML file used for the unplug/plug.
• To reset a database parameter at PDB level

source <EBS CDB>_<hostname>.env

export ORACLE_PDB_SID=<EBS PDB SID>

sqlplus "/as sysdba"

Example: alter system set "_disable_actualization_for_grant"=TRUE;

To check what all DB parameters can be set at PDB level, following query can be used:

SELECT NAME,ISPDB_MODIFIABLE FROM V$SYSTEM_PARAMETER WHERE UPPER(NAME) IN ('PROCESSES','SESSIONS','OPEN_CURSORS','_DISABLE_ACTUALIZATION_FOR_GRANT') ORDER BY 2,1;

 Check value of DB parameters at CDB and PDB level:

 

SELECT CON_ID,NAME,DISPLAY_VALUE FROM V$SYSTEM_PARAMETER WHERE UPPER(NAME) IN ('<db parameter name>') ORDER BY 1,2,3;

Required Parameters - validate and set below init parameters ( if any parameter is set then validate and check if missing from list)

compatible = 19.0.0 #MP
optimizer_adaptive_plans = TRUE #MP
optimizer_adaptive_statistics = FALSE #MP
pga_aggregate_limit = 0 #MP <<<<<<<<<<<<<<<<<< change/update
temp_undo_enabled = FALSE <<<<<<<<<<<<<<<<<< change/update
_pdb_name_case_sensitive = TRUE #MP
event='10946 trace name context forever, level 8454144' #MP

Change/update parameter result_cache_max_size to 600M

4.2 Parameter Removal List for Oracle Database 19c
validate and remove from database
olap_page_pool_size

#MP - Must parameters

Release-Specific Database Initialization Parameters for Oracle 19c

4.1 Required Parameters

The following list describes database initialization parameters required for this specific release of the Oracle Database. These parameters should be added to the common database initialization parameters provided in Section 1, so that the final database initialization parameters file includes the common section plus the contents of this release-specific section.

####################################################################
#
# Oracle E-Business Suite Release 12
# Release-Specific Database Initialization Parameters for 19c
#
####################################################################

#########
#
# Compatibility parameter.
#
# Compatibility should be set to the current release.
#
#########

compatible = 19.0.0 #MP

#########
#
# Optimizer parameters.
#
# In Oracle Database 12.2 or higher, the Parameter optimizer_adaptive_features has been obsoleted,
# replaced and controlled by two new parameters, optimizer_adaptive_plans, which defaults to TRUE and
# optimizer_adaptive_statistics, which defaults to FALSE. For more details Refer MOS DOC ID 2031605.1.
#
##########

optimizer_adaptive_plans = TRUE #MP
optimizer_adaptive_statistics = FALSE #MP

#########
#
# PGA Aggregate Limit parameter.
#
# PGA_AGGREGATE_LIMIT feature in 19c limits PGA memory usage
#
# The default value of PGA_AGGREGATE_LIMIT is set to the greater of 2 GB,
# 200% of PGA_AGGREGATE_TARGET, and 3 MB times the PROCESSES parameter.
# It will not exceed 120% of the physical memory size minus the total SGA size.
#
# PGA_AGGREGATE_LIMIT cannot be set below its default value. If a value of 0 is specified,
# it means there is no limit to the aggregate PGA memory consumed by the instance.
# If total PGA memory usage is over PGA_AGGREGATE_LIMIT value. The sessions or processes
# that are consuming the most untunable PGA memory will be terminated.
#
# Recommended value for PGA_AGGREGATE_LIMIT is 0.
#
##########

pga_aggregate_limit = 0 #MP

#########
#
# Temp Undo Enabled parameter.
#
# TEMP_UNDO_ENABLED helps to reduce the amount of redo caused by DML on global temporary tables.
# Setting to TRUE may cause serious issues, such as ORA-55526, for distributed transactions (Ref. Bug 20712819).
# The recommended value for systems using distributed transactions is currently FALSE (Pending ER 24286334).
# If not using distributed transactions, TRUE will improve performance by eliminating REDO on permanent UNDO.
#
##########

temp_undo_enabled = FALSE

#########
#
# Multitenant Architecture parameter.
#
# This parameter is required if the non-cdb name in lower case or mixed case, then
# plugin database will be created with the same case. Otherwise default is Upper case.
# This parameter needs to be set at the CDB level before plugging in the PDB
#
##########

_pdb_name_case_sensitive = TRUE #MP

#########
#
# Event parameter.
#
# Ensure the following event is set for Oracle E-Business Suite to work with Database Release 19c.
# This parameter needs to be set at the CDB level. When this event is set,
# it will allow utl_file functions to accept a directory path as input and
# enable backward compatibility of user/all/dba_arguments behavior on 19c.
#
##########

event='10946 trace name context forever, level 8454144' #MP


###############################################################################
#
# End of Release-Specific Database Initialization Parameters Section for 19c
#
###############################################################################

4.2 Parameter Removal List for Oracle Database 19c

If they exist, you should remove the following parameters from your database initialization parameters file for Oracle Database 19c.

Note: Parameters may appear on a "removal list" because they are obsolete; because the default value is required and no other value may be set; or to cater for certain special cases where a non-default value has to be set to meet specific needs (currently, there is only one such case, which is described in Section 6).

_kks_use_mutex_pin
_shared_pool_reserved_min_alloc
_sqlexec_progression_cost
exafusion_enabled
exclude_seed_cdb_view
global_context_pool_size
max_enabled_roles
o7_dictionary_accessibility
olap_page_pool_size
optimizer_adaptive_features
parallel_automatic_tuning
parallel_degree_level
parallel_io_cap_enabled
parallel_server
parallel_server_instances
plsql_compiler_flags
plsql_native_library_dir
plsql_native_library_subdir_count
plsql_optimize_level
standby_archive_dest
timed_statistics
use_indirect_data_buffers
utl_file_d

Section 5: Additional Database Initialization Parameters For Oracle E-Business Suite Release 12.2

The parameters in this section only apply to Oracle E-Business Suite Release 12.2 on Oracle Database 11g Release 2 (11.2.0.4 and higher), and should be used in addition to the parameters in the other relevant sections of this document.

#########
#
# Recyclebin parameter.
#
# The database recyclebin must be turned off to allow the cleanup phase of the
# online patching cycle to be performed without having to connect as SYS.
#
# This feature may still be used at other times.
#
#########

recyclebin = off #MP

#########
# 
# Service Names and Local Listener parameters.
#
# To support online patching, Oracle E-Business Suite Release 12.2 introduces a
# new database service.
#
# The service_names parameter specifies one or more names by which clients can
# connect to an instance. The instance registers its service names with the
# listener. When a client requests a service, the listener determines which
# instances offer the requested service and then routes the client to the most
# appropriate instance.
#
# On codelevels lower than AD-TXK Delta 9, the service name is always 'ebs_patch'.
# From the AD-TXK Delta 9 codelevel, the service name is defined by the the value
# of the context variable 's_patch_service_name'.
# 
# The local_listener setting is part of the AutoConfig templates, and required
# for listener registration of any non-default (1521) ports.
# 
#########
# 
# For Oracle Database 19c with a single tenant (1 CDB:1 PDB) configuration:
#
# service_names: The value for this parameter is auto-populated when CDB is created.
# This parameter should not be modified manually.
#
# local_listener: Need to set this parameter value as per the instructions given in the
# Interoperability Notes: Oracle E-Business Suite Release 12.2 with Oracle Database 19c
# (Ref. MOS Doc ID 2552181.1).
#
#########

service_names=%s_dbSid%, <s_patch_service_name or ebs_patch>  # Based on AD/TXK Code level

local_listener=%s_dbSid%_LOCAL

#########
#
# Result Cache parameter.
#
# For Oracle E-Business Suite 12.2.x, you should set the result_cache_max_size parameter to make optimal use of result cache memory.
# The value of result_cache_max_size is the maximum amount of memory taken from the shared pool, so it should be set in consideration
# with the setting of the shared_pool_size parameter.
#
# For higher concurrency environments that have more than 2000 active Oracle E-Business Suite user accounts, a setting of 600M is
# recommended.
#
#########

result_cache_max_size = 600Mir

Section 5: Additional Database Initialization Parameters For Oracle E-Business Suite Release 12.2

The parameters in this section only apply to Oracle E-Business Suite Release 12.2 on Oracle Database 11g Release 2 (11.2.0.4 and higher), and should be used in addition to the parameters in the other relevant sections of this document.

#########
#
# Recyclebin parameter.
#
# The database recyclebin must be turned off to allow the cleanup phase of the
# online patching cycle to be performed without having to connect as SYS.
#
# This feature may still be used at other times.
#
#########

recyclebin = off #MP

#########
# 
# Service Names and Local Listener parameters.
#
# To support online patching, Oracle E-Business Suite Release 12.2 introduces a
# new database service.
#
# The service_names parameter specifies one or more names by which clients can
# connect to an instance. The instance registers its service names with the
# listener. When a client requests a service, the listener determines which
# instances offer the requested service and then routes the client to the most
# appropriate instance.
#
# On codelevels lower than AD-TXK Delta 9, the service name is always 'ebs_patch'.
# From the AD-TXK Delta 9 codelevel, the service name is defined by the the value
# of the context variable 's_patch_service_name'.
# 
# The local_listener setting is part of the AutoConfig templates, and required
# for listener registration of any non-default (1521) ports.
# 
#########
# 
# For Oracle Database 19c with a single tenant (1 CDB:1 PDB) configuration:
#
# service_names: The value for this parameter is auto-populated when CDB is created.
# This parameter should not be modified manually.
#
# local_listener: Need to set this parameter value as per the instructions given in the
# Interoperability Notes: Oracle E-Business Suite Release 12.2 with Oracle Database 19c
# (Ref. MOS Doc ID 2552181.1).
#
#########

service_names=%s_dbSid%, <s_patch_service_name or ebs_patch>  # Based on AD/TXK Code level

local_listener=%s_dbSid%_LOCAL

#########
#
# Result Cache parameter.
#
# For Oracle E-Business Suite 12.2.x, you should set the result_cache_max_size parameter to make optimal use of result cache memory.
# The value of result_cache_max_size is the maximum amount of memory taken from the shared pool, so it should be set in consideration
# with the setting of the shared_pool_size parameter.
#
# For higher concurrency environments that have more than 2000 active Oracle E-Business Suite user accounts, a setting of 600M is
# recommended.
#
#########

result_cache_max_size = 600M

Autoconfig Fails With "Timed out( 300000 ): Interrupted Exception" Error

Autoconfig Fails With "Timed out( 300000 ): Interrupted Exception" Error  

While running Autoconfig we faced the error in ebsr12 

 Its not completing and later its giving error 

[ Config tool : /u01/applmgr/abcdef/fs2/EBSapps/appl/fnd/12.0.0/patch/115/bin/txkManageDBConnectionPool.pl ]
Command : /u01/applmgr/abcdef/fs2/FMW_Home/webtier/perl/bin/perl -I /u01/applmgr/abcdef/fs2/FMW_Home/webtier/perl/lib/5.10.0 -I /u01/applmgr/abcdef/fs2/FMW_Home/webtier/perl/lib/site_perl/5.10.0 -I /u01/applmgrabcdef/fs2/EBSapps/appl/au/12.0.0/perl -I /u01/applmgr/abcdef/fs2/FMW_Home/webtier/ohs/mod_perl/lib/site_perl/5.10.0/x86_64-linux-thread-multi /u01/applmgr/abcdef/fs2/EBSapps/appl/fnd/12.0.0/patch/115/bin/txkManageDBConnectionPool.pl PASSWORD contextfile=/u01/applmgr/abcdef/fs2/inst/apps/WYOFNSIT_sit-appofin02/appl/admin/WYOFNSIT_sit-appofin02.xml -options=updateDSOffline

Action : execute

SCRIPT RETURNED:
Timed out( 300000 ): Interrupted Exception

Created SR and oracle provided the solution .

Autoconfig Fails With "Timed out( 300000 ): Interrupted Exception" Error (Doc ID 2177265.1)

[ Config tool : $FND_TOP/patch/115/bin/txkSetConfig.pl ]

Command : ...

Action : execute

SCRIPT RETURNED:

Timed out( 300000 ): Interrupted Exception

:

:

[ Config tool : $FND_TOP/patch/115/bin/txkManageDBConnectionPool.pl ]

Command : ...

Action : execute

SCRIPT RETURNED:

Timed out( 300000 ): Interrupted Exception

:

:

WARNING: [CVM Error Report]

The following report lists errors encountered during CVM Phase

<filename> <return code where appropriate>

$FND_TOP/patch/115/bin/txkSetConfig.pl -1

 $FND_TOP/patch/115/bin/txkManageDBConnectionPool.pl -1

No. of scripts failed in CVM phase: 2

AutoConfig is exiting with status 2

AutoConfig execution completed

CAUSE

The scripts can not finish due to timeout.

Generally, timeout issues are seen when the server is running too slowly to complete the process in the allotted time.
The cause could be because:
1. There are not enough CPU or memory resources to complete the task, or
2. The timeout setting limits were reached.

SOLUTION

1. Perform one of these 2 options:

  a. Free up resources on the server by stopping other processes and/or increasing the CPU and memory.
-or-
  b. Change the timeout value:
Open a new Shell and source the Environment
export TIMEDPROCESS_TIMEOUT=-1 (infinite)
export TIMEDPROCESS_DEBUG=YES

2. Run AutoConfig again.