/usr/lib/gcc/x86_64-redhat-linux/4.4.7/32/libgcc_s.so: undefined reference to `__stack_chk_fail

Error :-
==================

/usr/lib/gcc/x86_64-redhat-linux/4.4.7/32/libgcc_s.so: undefined reference to
`__stack_chk_fail@GLIBC_2.4'
collect2: ld returned 1 exit status
make: *** [/APP/apps/apps_st/appl/fnd/12.0.0/bin/FNDLIBR] Error 1
Done with link of fnd executable 'FNDLIBR' on Sat Sep 12 16:31:30 EEST 2015

Relink of module "FNDLIBR" failed.
See error messages above (also recorded in log file) for possible
reasons for the failure. Also, please check that the Unix userid
running adrelink has read, write, and execute permissions
on the directory /APP/apps/apps_st/appl/fnd/12.0.0/bin,
and that there is sufficient space remaining on the disk partition
containing your Oracle Applications installation.

Done with link of product 'fnd' on Sat Sep 12 16:31:30 EEST 2015


adrelink is exiting with status 1


Solution :-
================================

After installation, users must update the stub libraries in the 10.1.2 and 10.1.3 Oracle Homes using Patch 12415211.  In following the instructions below, please note that Opatch should not be used to install this patch.

Users must specifically copy the files in the patch to the specified directories as follows for the 10.1.2 Oracle Home:

$ cd <12.1_INSTALL_DIR>/apps/tech_st/10.1.2/lib
$ cp -p -R stubs stubsORIG
$ cd stubs
$ cp <PATCH_INSTALL_DIR>/12415211/files/lib/stubs/libgcc_s-2.3.2-stub.so .
$ ln -s libgcc_s-2.3.2-stub.so libgcc_s.so.1
$ ln -s libgcc_s.so.1 libgcc_s.so
After this is done and sourcing the APPS<CONTEXT_NAME>.env file, users should relink all 10.1.2 executables by running the $ORACLE_HOME/appsutil/clone/adlnktools.sh script and ensuring that there are now no errors in the make log file output from the script.

The instructions for the 10.1.3 Oracle Home are:

$ cd <12.1_INSTALL_DIR>/apps/tech_st/10.1.3/lib
$ cp -p -R stubs stubsORIG
$ cd stubs
$ cp <PATCH_INSTALL_DIR>/12415211/files/lib/stubs/libgcc_s-2.3.2-stub.so .
$ ln -s libgcc_s-2.3.2-stub.so libgcc_s.so.1
$ ln -s libgcc_s.so.1 libgcc_s.so

RA-00600: internal error code, arguments: [kcratr_nab_less_than_odr]

Solution:-
========================================================

Do cancel based reocvery, and apply 'current online redolog' manually
------------

SQL>Startup mount ;

SQL>Show parameter control_files

Query 1
------------

SQL> select a.member, a.group#, b.status from v$logfile a ,v$log b where a.group#=b.group# and b.status='CURRENT' ;

Note down the name of the redo log

SQL> Shutdown abort ;

Take a OS Level backup of the controlfile (This is to ensure we have a backup of current state of controlfile)

SQL> Startup mount ;
SQL> recover database using backup controlfile until cancel ;

Enter location of redo log shown as current in Query 1 when prompted for recovery

Hit Enter

SQL> Alter database open resetlogs ;

Relink of module "adwrknew" failed. while applying patch 9239089

Error:-
=====================
Relinking executables...

An error occurred while relinking application programs.

Continue as if it were successful [No] : No
 Freeing includes hash table
Freeing fixes hash table
 Freeing basedons hash table
Freeing entities hash table

You should check the file
/u02/apps/apps/apps_st/appl/admin/PROD/log/u9239089.log

for errors.

LOG:-
=======================================================
Relink of module "adwrknew" failed.
See error messages above (also recorded in log file) for possible
reasons for the failure.  Also, please check that the Unix userid
running adrelink has read, write, and execute permissions
on the directory /u02/apps/apps/apps_st/appl/ad/12.0.0/bin,
and that there is sufficient space remaining on the disk partition
containing your Oracle Applications installation.

Done with link of product 'ad' on Mon Jul 24 08:06:18 IST 2017


adrelink is exiting with status 1

End of adrelink session
Date/time is  Mon Jul 24 08:06:18 IST 2017
**********************************************************
**********************************************************

SOLUTION:-
------------------------------------------------------------

Download the patch  12415211 and do the below following :-
========================================================================

[applmgr@apps120 stubs]$ cd /u02/apps/apps/tech_st/10.1.2
[applmgr@apps120 lib]$ cp -p -R stubs stubsORIG
[applmgr@apps120 lib]$ cd stubs
[applmgr@apps120 stubs]$ pwd
/u02/apps/apps/tech_st/10.1.2/lib/stubs

[applmgr@apps120 stubs]$ cp -rvf /u02/Apps_patches/12415211/files/lib/stubs/libgcc_s-2.3.2-stub.so .
`/u02/Apps_patches/12415211/files/lib/stubs/libgcc_s-2.3.2-stub.so' -> `./libgcc_s-2.3.2-stub.so'
[applmgr@apps120 stubs]$  ln -s libgcc_s-2.3.2-stub.so libgcc_s.so.1
[applmgr@apps120 stubs]$ ln -s libgcc_s.so.1 libgcc_s.so
[applmgr@apps120 stubs]$ pwd
/u02/apps/apps/tech_st/10.1.2/lib/stubs

[applmgr@apps120 stubs]$ cd /u02/apps/apps/tech_st/10.1.3
[applmgr@apps120 10.1.3]$ cd lib/stubs

[applmgr@apps120 lib]$ cp -p -R stubs stubsORIG
[applmgr@apps120 lib]$ cd stubs
[applmgr@apps120 stubs]$ cp -rvf /u02/Apps_patches/12415211/files/lib/stubs/libgcc_s-2.3.2-stub.so .
`/u02/Apps_patches/12415211/files/lib/stubs/libgcc_s-2.3.2-stub.so' -> `./libgcc_s-2.3.2-stub.so'
[applmgr@apps120 stubs]$ ln -s libgcc_s-2.3.2-stub.so libgcc_s.so.1
[applmgr@apps120 stubs]$ ln -s libgcc_s.so.1 libgcc_s.so
[applmgr@apps120 stubs]$ pwd
/u02/apps/apps/tech_st/10.1.3/lib/stubs

Then apply the Patch 9239089

Expect command steps in bash

EXPECT COMMAND:-
======================================================================================================

[root@tlntatl14 Naveen]# cat patch.sh
Userid=naveen.janjanam@*****.com
Password=**********                      # give the password
echo "Enter the patch number:"
read Pno
expect -c "
spawn sh /u51/ar121/patch/get_MOS_patches.sh patch=$Pno
expect \"Userid:\"
send \"$Userid\r\"
expect \"Password:\"
send \"$Password\r\"
interact
"
ls -ltr *$Pno*

out:-
=============================
[root@tlntatl14 Naveen]# sh patch.sh
Enter the patch number:
24828024
spawn sh /u51/ar121/patch/get_MOS_patches.sh patch=24828024
Oracle Support Userid: naveen.janjanam@tieto.com
Oracle Support Password:

Getting patch 24828024 for "Linux x86-64"
1 - p24828024_R12.AP.C_R12_GENERIC.zip
2 - p24828024_R12.AP.B_R12_GENERIC.zip
Comma-delimited list of files to download: 2
Downloading file p24828024_R12.AP.B_R12_GENERIC.zip ...
p24828024_R12.AP.B_R12_GENERIC.zip completed with status: 0

Getting patch 24828024 for "Norwegian (N)"
no patch available
-rw-r--r-- 1 root root 63375 Oct 14  2016 p24828024_R12.AP.B_R12_GENERIC.zip_old
-rw-r--r-- 1 root root 63375 Oct 14  2016 p24828024_R12.AP.B_R12_GENERIC.zip

fnd_conc_clone.setup_clean vs cmclean.sql

fnd_conc_clone.setup_clean
====================
fnd_conc_clone  ===> is package
setup_clean ====> it is procedure name
When we run fnd_conc_clone.setup_clean it deletes the information from the below tables.
Delete from fnd_concurrent_queue_size
Delete from fnd_concurrent_queues_tl
Delete from fnd_concurrent_queuesDelete from fnd_nodes;

We use fnd_conc_clone.setup_clean to cleanup fnd_nodes table in the target to clear source node information as part of cloning.

below syntax to execute:
SQL> sho user
USER is "APPS"
SQL> exec fnd_conc_clone.setup_clean;
PL/SQL procedure successfully completed.
SQL> commit;
Commit complete.
First run the autoconfig on DB tier and middle tier this will regiser the nodes in fnd_nodes tables.

cmclean.sql
=========
If we stop conc manager using abort options then concurrent requests will be in running state ,Next when we start concurrent manager the processes will not start properly.
To cleanup running and pending requests we use cmclean.sql this script will update the below tables.
UPDATE fnd_concurrent_processes
UPDATE fnd_concurrent_queues
UPDATE fnd_concurrent_requests
UPDATE fnd_conflicts_domain
UPDATE fnd_concurrent_conflict_sets
Download cmclean.sql: 
=================
Concurrent Processing - cmclean.sql - Non Destructive Script to Clean Concurrent Manager Tables [ID 134007.1]
Note: cmclean.sql and fnd_conc_clone.setup_clean touch different set of concurrent request tables.
Its better idea to run both during the clone. 

NOFILENAMECHECK Parameter Causes ?

When NOFILENAMECHECK is used with the DUPLICATE command, RMAN does not validate the filenames during restoration.

If the primary database and the standby database are on the same host, The DUPLICATE NOFILENAMECHECK option should not be used.

What really happens when you enable maintenance mode before applying patches

Maintenance mode provides a clear separation between normal runtime operation of Oracle Applications and system downtime for maintenance. Enabling the maintenance mode feature shuts down the Workflow Business Events System and sets up function security so that no Oracle Applications functions are available to users. Used only during AutoPatch sessions, maintenance mode ensures optimal performance and reduces downtime when applying a patch. For more information, refer to Preparing your System for Patching in Oracle Applications Maintenance Utilities.

You may also refer to Article ID 291901.1, which has more information about Maintenance Mode.