Copy Patch /u01/oracle/PROD/apps/fs_ne/EBSapps/patch
chown -Rf oracle:dba /file_path
chmod -Rf 775 /file_path
Stop application from by running the APPS.Env
$ADMIN_SCRIPTS_HOME
./adstpall.sh apps/apps
./adadminsrvctl.sh start apps/apps
Navigate to path /u01/oracle/PROD/apps/fs_ne/EBSapps/patch
adop phase=apply patches=patch_num hotpatch=yes
After applying patch stop
./adadminsrvctl.sh stop
./adnodemgrctl.sh stop
Run ./adautocfg.sh after applying patch
--------------------------------------------------------------------------------------------------------------------------
Error:
Validating credentials...
Initializing...
Run Edition context : /u01/oracle/PROD/apps/fs1/inst/apps/PROD_TEST/appl/admin/PROD_TEST.xml
Patch edition context: /u01/oracle/PROD/apps/fs2/inst/apps/PROD_TEST/appl/admin/PROD_TEST.xml
Reading driver file (up to 50000000 bytes).
*******FATAL ERROR*******
PROGRAM : (/u01/oracle/PROD/apps/fs1/EBSapps/appl/ad/12.0.0/bin/adzdoptl.pl)
TIME : Sun Feb 21 13:04:32 2016
FUNCTION: ADOP::GlobalVars::_validateApplyRestartArgs [ Level 1 ]
ERRORMSG: Since earlier patching session failed and you are invoking apply again, please specify 'abandon' or 'restart' parameter.
[STATEMENT] Please run adopscanlog utility, using the command
"adopscanlog -latest=yes"
to get the list of the log files along with snippet of the error message corresponding to each log file.
adop exiting with status = 255 (Fail)
Solution:
adop phase=apply patches=patch_num hotpatch=yes abandon=yes (to start patch from failing end)
adop phase=apply patches=patch_num hotpatch=yes restart=yes (to start patch from begning)
--------------------------------------------------------------------------------------------------------------------------
Validating system setup...
Node registry is valid.
Application services are down.
[ERROR] ETCC not run in the database node TEST
The EBS Technology Codelevel Checker needs to be run on the database node.
It is available as Patch 17537119.
Encountered the above errors when performing database validations.
Resolve the above errors and restart adop.
[STATEMENT] Please run adopscanlog utility, using the command
"adopscanlog -latest=yes"
to get the list of the log files along with snippet of the error message corresponding to each log file.
adop exiting with status = 1 (Fail)
Solution:
select * from fnd_nodes
select * from applsys.txk_tcc_results
Copy DB_MT.tar in /u01/
Run Database Enviroment
connect sqlplus
SQL> create table shafqat_txk as select * from applsys.txk_tcc_results;
SQL> drop table applsys.txk_tcc_results;
[oracle@TEST u01]$ tar -xzvf DB_MT.tar (to untar)
-----[oracle@TEST u01]$ tar -czvf DB_MT.tar DB_MT (to make tar)
check the rights ls-alrt
chmod -Rf 775 DB_MT
chown -Rf oracle:dba DB_MT
------------------------------------------------------------------------
[oracle@TEST u01]$ cd DB_MT
[oracle@TEST DB_MT]$ ls
backup checkMTpatch.cmd README.txt
checkDBpatch.cmd p17537119_R12_GENERIC.zip
[oracle@TEST DB_MT]$ cd b
-bash: cd: b: No such file or directory
[oracle@TEST DB_MT]$ cd backup/
[oracle@TEST backup]$ ls
checkDBpatch_11738.log checkDBpatch_4455.log checkMTpatch_3195.log
checkDBpatch_12360.log checkDBpatch_5035.log checkMTpatch_4471.log
checkDBpatch_13066.log checkDBpatch_5630.log checkMTpatch_5250.log
checkDBpatch_13548.log checkDBpatch_7114.log checkMTpatch_5970.log
checkDBpatch_13970.log checkDBpatch_963.log checkMTpatch_7294.log
checkDBpatch_14414.log checkDBpatch.cmd checkMTpatch.cmd
checkDBpatch_14526.log checkDBpatch.sh checkMTpatch.sh
checkDBpatch_19122.log checkMTpatch_12641.log p17537119_R12_GENERIC.zip
checkDBpatch_19742.log checkMTpatch_13359.log README.txt
checkDBpatch_20562.log checkMTpatch_1686.log txk_R1220_DB_base_bugs.xml
checkDBpatch_21575.log checkMTpatch_2417.log txk_R1220_MT_base_bugs.xml
checkDBpatch_3582.log checkMTpatch_26608.log
[oracle@TEST backup]$ ./checkDBpatch.sh
+===============================================================+
| Copyright (c) 2005, 2015 Oracle and/or its affiliates. |
| All rights reserved. |
| Database EBS Technology Codelevel Checker (DB-ETCC) |
+===============================================================+
Starting Database EBS Technology Codelevel Checker, Version 120.26
Enter the full path to the DB Context file :/u01/oracle/PROD/db/tech_st/11.2.0/appsutil/PROD_TEST.xml
Using database context file:
/u01/oracle/PROD/db/tech_st/11.2.0/appsutil/PROD_TEST.xml
Bugfix XML file version: 120.0.12020000.24
This file will be used as the reference for identifying missing bugfixes.
[WARNING] DB-ETCC: Bugfix XML file (txk_R1220_DB_base_bugs.xml) in current directory is more than 30 days old.
Check if a newer version is available in patch 17537119.
Identifying database release ...
Setting database release to 11.2.0.4
=======================================================
[WARNING] DB-ETCC: Could not connect to database, so unable to check:
- Whether database is in READ-WRITE mode.
- Existence of table needed to store DB-ETCC results.
Resolve the database connectivity issue, and then rerun DB-ETCC.
=========================================================
Started prerequisite patch testing : Sun Feb 21 14:51:44 PKT 2016
Log file for this session : ./checkDBpatch_12937.log
Obtained list of bugfixes to be applied and the list to be rolled back.
Now checking Database ORACLE_HOME.
The opatch utility is at the required version.
Found patch records in the inventory.
All the required one-off bugfixes are present in Database ORACLE_HOME.
Database not available. DB-ETCC results cannot be stored.
Finished prerequisite patch testing : Sun Feb 21 14:52:11 PKT 2016
=========================================================
[oracle@TEST scripts]$ ./adadminsrvctl.sh stop
[oracle@TEST scripts]$ ./adadminnode.sh stop
You are running adadminsrvctl.sh version 120.10.12020000.9
Enter the WebLogic Admin password:
Enter the APPS Schema password:
Stopping WLS Admin Server...
Refer /u01/oracle/PROD/apps/fs1/inst/apps/PROD_TEST/logs/appl/admin/log/adadminsrvctl.txt for details
adadminsrvctl.sh: exiting with status 0
adadminsrvctl.sh: check the logfile /u01/oracle/PROD/apps/fs1/inst/apps/PROD_TEST/logs/appl/admin/log/adadminsrvctl.txt for more information ...
[oracle@TEST scripts]$
---------------------------------------------------------
Run Database Env
connect to SQLPLUS
SQL> show parameter _system_trig_enabled;
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
_system_trig_enabled boolean TRUE
----------------------------------------------------------------------------------------------
Down the Listener
[oracle@TEST 11.2.0]$ lsnrctl stop PROD
Down Database
SQL> shut immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
[oracle@TEST 11.2.0]$ cd appsutil
[oracle@TEST appsutil]$ ls
bin install jdk jre1.5 media perl scripts temp
html java jre log out PROD_TEST.xml sql template
[oracle@TEST appsutil]$ cd scripts/
[oracle@TEST scripts]$ ls
PROD_TEST
[oracle@TEST scripts]$ cd PROD_TEST/
[oracle@TEST PROD_TEST]$ ls
adautocfg.sh addbctl.sh adexecsql.pl adpreclone.pl adstrtdb.sql
adchknls.pl addlnctl.sh adlsnodes.sh adstopdb.sql
[oracle@TEST PROD_TEST]$ ./adautocfg.sh
------------------------------------------------------------------------------
AutoConfig completed with errors.
------------------------------------------------------------------------------
Check the logfile for errors >>>> Verifying connection to the Database : Could not be stablished
lsnrctl start PROD
connect to sqlplus and start database
sql>startup
Run ./adautocfg.sh again
[oracle@TEST PROD_TEST]$ ./adautocfg.sh
--------------------------------------------------------------------------------
AutoConfig completed successfully.
--------------------------------------------------------------------------------
Run apps Enviroment adn run ./adautocfg.sh
[oracle@TEST appl]$ . ./APPSPROD_TEST.env
[oracle@TEST scripts]$ ./adautocfg.sh
------------------------------------------------------------------------------
AutoConfig completed successfully.
------------------------------------------------------------------------------
No comments:
Post a Comment