Wednesday 30 September 2015

Difference in location of Log files in Oracle EBS Release 12.1.3 and Oracle EBS Release 12.2.4

The Log files locations in Oracle EBS Release 12.1.3 and  Oracle EBS R 12.2.4  are given below:

1.Instance startup and configuration Log files are located for INST_TOP in Oracle Release 12.1.3 are below:

$INST_TOP/logs/appl/admin/log
Startup/Shutdown error message related to tech stack (10.1.2, 10.1.3 forms/reports/web)
$INST_TOP/logs/ora/ (10.1.2 & 10.1.3)
$INST_TOP/logs/ora/10.1.3/Apache/error_log[timestamp](Apache log files)
$INST_TOP/logs/ora/10.1.3/opmn/ (OC4J, oa*, opmn.log)
$INST_TOP/logs/ora/10.1.2/network/ (listener log)
$INST_TOP/apps/$CONTEXT_NAME/logs/appl/conc/log (CM log files)

2. Log files related to cloning in R12.1.3 are as below:

 Preclone log files in source instance
Database Tier – $ORACLE_HOME/appsutil/log/$CONTEXT_NAME/(StageDBTier_MMDDHHMM.log)
Application Tier –
$INST_TOP/apps/$CONTEXT_NAME/admin/log/(StageAppsTier_MMDDHHMM.log)

Clone log files in target instance
Database Tier – $ORACLE_HOME/appsutil/log/$CONTEXT_NAME/ApplyDBTier_.log
Apps Tier – $INST_TOP/admin/log/ApplyAppsTier_.log

3. Patching related log files in R12.1.3 are as below:

i) Application Tier adpatch log – $APPL_TOP/admin/$SID/log/
ii) Developer (Developer/Forms & Reports 10.1.2) Patch – $ORACLE_HOME/.patch_storage
iii) Web Server (Apache) patch – $IAS_ORACLE_HOME/.patch_storage
iv) Database Tier opatch log – $ORACLE_HOME/.patch_storage


4. Autoconfig related log files in R12.1.3 are as below:

a) Database Tier Autoconfig log :
$ORACLE_HOME/appsutil/log/$CONTEXT_NAME/MMDDHHMM/adconfig.log
$ORACLE_HOME/appsutil/log/$CONTEXT_NAME/MMDDHHMM/NetServiceHandler.log


b) Application Tier Autoconfig log : 
$INST_TOP/apps/$CONTEXT_NAME/admin/log/$MMDDHHMM/adconfig.log

5.Autoconfig context file location in R12.1.3 :
$INST_TOP/apps/$CONTEXT_NAME/appl/admin/$CONTEXT_NAME.xml


6)R12.1.3 Installation Logs in R12.1.3 are as below:

 Database Tier Installation
RDBMS_ORACLE_HOME/appsutil/log/$CONTEXT_NAME/.log
RDBMS_ORACLE_HOME/appsutil/log/$CONTEXT_NAME/ApplyDBTechStack_.log
RDBMS_ORACLE_HOME/appsutil/log/$CONTEXT_NAME/ohclone.log
RDBMS_ORACLE_HOME/appsutil/log/$CONTEXT_NAME/make_.log
RDBMS_ORACLE_HOME/appsutil/log/$CONTEXT_NAME/installdbf.log
RDBMS_ORACLE_HOME/appsutil/log/$CONTEXT_NAME/adcrdb_.log RDBMS_ORACLE_HOME/appsutil/log/$CONTEXT_NAME/ApplyDatabase_.log
RDBMS_ORACLE_HOME/appsutil/log/$CONTEXT_NAME//adconfig.log
RDBMS_ORACLE_HOME/appsutil/log/$CONTEXT_NAME//NetServiceHandler.log
Application Tier Installation
$INST_TOP/logs/.log
$APPL_TOP/admin/$CONTEXT_NAME/log/ApplyAppsTechStack.log
$INST_TOP/logs/ora/10.1.2/install/make_.log
$INST_TOP/logs/ora/10.1.3/install/make_.log
$INST_TOP/admin/log/ApplyAppsTechStack.log
$INST_TOP/admin/log/ohclone.log
$APPL_TOP/admin/$CONTEXT_NAME/log/installAppl.log
$APPL_TOP/admin/$CONTEXT_NAME/log/ApplyAppltop_.log
$APPL_TOP/admin/$CONTEXT_NAME/log//adconfig.log
$APPL_TOP/admin/$CONTEXT_NAME/log//NetServiceHandler.log
Inventory Registration:
$Global Inventory/logs/cloneActions.log
$Global Inventory/logs/oraInstall.log
$Global Inventory/logs/silentInstall.log

7) Log files related with relink,Network,OUT inventory logs for R12.1.3 are as below:
 1) Database Tier
1.1) Relink Log files :
$ORACLE_HOME/appsutil/log/$CONTEXT_NAME /MMDDHHMM/ make_$MMDDHHMM.log
1.2) Alert Log Files :
$ORACLE_HOME/admin/$CONTEXT_NAME/bdump/alert_$SID.log
1.3) Network Logs :
$ORACLE_HOME/network/admin/$SID.log
1.4) OUI Logs :
OUI Inventory Logs :
$ORACLE_HOME/admin/oui/$CONTEXT_NAME/oraInventory/logs
2) Application Tier
$ORACLE_HOME/j2ee/DevSuite/log
$ORACLE_HOME/opmn/logs
$ORACLE_HOME/network/logs
Tech Stack Patch 10.1.3 (Web/HTTP Server)
$IAS_ORACLE_HOME/j2ee/forms/logs
$IAS_ORACLE_HOME/j2ee/oafm/logs
$IAS_ORACLE_HOME/j2ee/oacore/logs
$IAS_ORACLE_HOME/opmn/logs
$IAS_ORACLE_HOME/network/log
$INST_TOP/logs/ora/10.1.2
$INST_TOP/logs/ora/10.1.3
$INST_TOP/logs/appl/conc/log
$INST_TOP/logs/appl/admin/log


In EBS R12.2.4 the log files locations are as below:

1)Log files file Online patching (adop) in EBS R12.2.4 are in below location:

The adop log files are located on the non-editioned file system (fs_ne), under:

$NE_BASE/EBSapps/log/adop/<adop_session_id>/<phase>_<date>_<time>/<context_name>/log

This log directory will contain patch logs,patch worker logs.

adop(phase=fs_clone) Online pathcing filesystem cloning process related log files are found under:

$INST_TOP/admin/log


2)Log files for Autoconfig process in Oracle EBS R12.2.4 are below:

On Applicaion Tier: $INST_TOP/admin/log/<MMDDhhmm>
On Database Tier: $ORACLE_HOME/appsutil/log/<CONTEXT_NAME>/<MMDDhhmm>

3)Log files for start/stop of services from $ADMIN_SCRIPTS_HOME

In below directory we will find log files related to start/stop process of oacore, forms, apache, opmn, 
weblogic admin server/node manager:

$LOG_HOME/appl/admin/log


4)Log/Out files for Concurrent programs/managers in Oracle R12.2.4 are in below location:

Log/Out files for Oracle Release 12.2 are stored in Non-Editioned filesystem(NE).

Log files: $APPLCSF/$APPLLOG (or $NE_BASE/inst/<CONTEXT_NAME>/logs/appl/conc/log)
Out files: $APPLCSF/$APPLOUT (or $NE_BASE/inst/<CONTEXT_NAME>/logs/appl/conc/out)


5)Log files for OPMN and OHS processes in Oracle R12.2.4 are in below location:

Below directory contains log files related OPMN process(opmn.log), 
OPMN Debug logs(debug.log), HTTP Transaction logs (access.log),security settings related logs.

$IAS_ORACLE_HOME/instances/<ohs_instance>/diagnostics/logs


6)Log file for Weblogic Node Manager in Oracle R12.2.4 are in below location:

Log file is generated by Node Manager and contains data for all domains that 
are controlled by Node Manager on a given physical machine.

$FMW_HOME/wlserver_10.3/common/nodemanager/nmHome1/nodemanager.log


7)Log file for Weblogic  in Oracle R12.2.4 for Oracle Management Service are below

Initial settings for AdminServer and Domain level information is written in this log file

$EBS_DOMAIN_HOME/sysman/log


8)Log files for server processes initiated through Weblogic in Oracle R12.2.4 are in below location:
Stdout and stderr messages generated by the forms, oafm and oacore services are located 
at NOTICE severity level or higher are written by Weblogic Node Manager to below directory.

$EBS_DOMAIN_HOME/servers/<server_name>/logs/<server_name>.out

Monday 6 July 2015

Datapump fails with ORA-27086 on NFS



Export: Release 10.2.0.4.0 - Production on Tuesday, 2 June, 2015 11:27:50
 
Copyright (c) 2003, 2007, Oracle.  All rights reserved.
 
Connected to: Oracle Database 10g Release 10.2.0.4.0 - Production
ORA-39001: invalid argument value
ORA-39000: bad dump file specification
ORA-31641: unable to create dump file "/backup-nfs/testdb/export/exportfull.dmp"
ORA-27086: unable to lock file - already in use
Linux Error: 37: No locks available
Additional information: 10


In this case problem was lying in NFS locking deamons - on most Unix-like systems also known as rpc.lockd and the rpc.statd. For this just restart the service



Checking if 'nfslock' service is running:
1
2
# service nfslock status
rpc.statd is stopped

Start 'nfslock' service:
1
2
# /etc/init.d/nfslock start
Starting NFS statd:                                        [  OK  ]

Status:
1
2
# service nfslock status
rpc.statd (pid  4943) is running...


Starting 'nfslock' service resolved my problem with performing export to NFS.

Friday 27 March 2015

crontab: error on previous line; number out of bounds




Today I need to comment out a line in crontab in order to do a depolyment.
After I changed crontab, I found I could't save the crontab with error message:

30 4 * * 7 /usr/bin/rm /opt/SUNWexplo/output/*gz ; /opt/SUNWexplo/bin/explorer -d /etc/opt/SUNWexplo/default/explorer
crontab: error on previous line; number out of bounds.

crontab: errors detected in input, no crontab file generated.


Something is wrong with 30 4 * * 7,  the last number means weeks, you can choose a number from 0-6 , 7 is out of bounds.
I guess the guy modified crontab file directly instead of crontab -e and made a mistake.

I changed 7 to 0 and issue fixed.

TNS-12542: TNS:address already in use TNS-12560: TNS:protocol adapter error TNS-00512: Address already in use 32/64-bit Windows Error: 48: Unknown error





c:> sqlplus / as sysdba
 as NO TNS or listener FOUND

c:> exit

Lsnrctl start PROD 

TNSLSNR for 32-bit Windows: Version 10.2.0.3.0 - Production
System parameter file is
D:\oracle\PROD\db\tech_st\10.2.0\network\admin\PROD_erpprod\listener.ora
Log messages written to
D:\oracle\PROD\db\tech_st\10.2.0\network\log\listener.log
Error listening on: (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
TNS-12542: TNS:address already in use
 TNS-12560: TNS:protocol adapter error
  TNS-00512: Address already in use
   32-bit Windows Error: 48: Unknown error

Listener failed to start. See the error message(s) above...




For this error we did the followings

HKEY_LOCAL_MACHINE --> SYSTEM --> Services --> TCPIP ---> Parameters -->
Create one Key file name as MaxUserPort and Value as 65534 save it .




And then we  gave ipaddress instead of hostname in listener.ora file .




Now start the Listener  as Lsnrctl   start PROD



Now i try to connect the DB as sqlplus / as sysdba  and it  startup as MOUNT stage so  we try to OPEN now its open with out an issue. 

OPATCH FAILED WITH ERROR CODE 73









SQL> select name,open_mode from v$database;

NAME      OPEN_MODE
--------- --------------------
DOYEYDB  READ WRITE

SQL> shut immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> exit


==>ls -tlr
total 94688
drwxrwxr-x 15 oracle oinstall     4096 Dec 10 01:42 19769496
-rw-rw-r--  1 oracle oinstall    93056 Jan 20 09:52 PatchSearch.xml
-rw-r--r--  1 oracle oinstall 96857392 Feb 24 12:57 p19769496_112030_Linux-x86-64.zip

==>cd 19769496/

dbcpblkdev01*DOYENDB-/home/oracle/Patches/19769496
==>ls -trlr
total 112
drwxrwxr-x 4 oracle oinstall  4096 Dec 10 01:41 18522512
drwxrwxr-x 4 oracle oinstall  4096 Dec 10 01:41 16902043
drwxrwxr-x 4 oracle oinstall  4096 Dec 10 01:41 14275605
drwxrwxr-x 4 oracle oinstall  4096 Dec 10 01:41 16619892
drwxrwxr-x 4 oracle oinstall  4096 Dec 10 01:41 13696216
drwxrwxr-x 5 oracle oinstall  4096 Dec 10 01:41 17540582
drwxrwxr-x 4 oracle oinstall  4096 Dec 10 01:41 13923374
drwxrwxr-x 4 oracle oinstall  4096 Dec 10 01:41 16056266
drwxrwxr-x 4 oracle oinstall  4096 Dec 10 01:41 18031683
drwxrwxr-x 4 oracle oinstall  4096 Dec 10 01:41 19121548
drwxrwxr-x 4 oracle oinstall  4096 Dec 10 01:41 19769496
drwxr-xr-x 4 oracle oinstall  4096 Dec 10 01:41 13343438
drwxrwxr-x 5 oracle oinstall  4096 Dec 10 01:41 14727310
-rw-r--r-- 1 oracle oinstall    21 Dec 10 01:41 README.txt
-rw-r--r-- 1 oracle oinstall  2872 Dec 10 01:42 patchmd.xml
-rw-rw-r-- 1 oracle oinstall 51692 Jan 17 11:30 README.html





PreCheck:

==>opatch prereq CheckConflictAgainstOHWithDetail -ph ./
Oracle Interim Patch Installer version 11.2.0.3.0
Copyright (c) 2012, Oracle Corporation.  All rights reserved.

PREREQ session

Oracle Home       : /u01/oracle/app/oracle/product/DOYENDB/11.2.3
Central Inventory : /u01/oracle/oraInventory
   from           : /u01/oracle/app/oracle/product/DOYENDB/11.2.3/oraInst.loc
OPatch version    : 11.2.0.3.0
OUI version       : 11.2.0.3.0
Log file location : /u01/oracle/app/oracle/product/DOYENDB/11.2.3/cfgtoollogs/opatch/opatch2015-02-24_13-14-48PM_1.log

Invoking prereq "checkconflictagainstohwithdetail"

Prereq "checkConflictAgainstOHWithDetail" passed.

OPatch succeeded.

dbcpblkdev01*DOYENDB-/home/oracle/Patches/19769496/19769496

==>opatch apply
Oracle Interim Patch Installer version 11.2.0.3.0
Copyright (c) 2012, Oracle Corporation.  All rights reserved.


Oracle Home       : /u01/oracle/app/oracle/product/DOYENDB/11.2.3
Central Inventory : /u01/oracle/oraInventory
   from           : /u01/oracle/app/oracle/product/DOYENDB/11.2.3/oraInst.loc
OPatch version    : 11.2.0.3.0
OUI version       : 11.2.0.3.0
Log file location : /u01/oracle/app/oracle/product/DOYENDB/11.2.3/cfgtoollogs/opatch/opatch2015-02-24_13-16-53PM_1.log

Verifying environment and performing prerequisite checks...
UtilSession failed: null
Log file location: /u01/oracle/app/oracle/product/DOYENDB/11.2.3/cfgtoollogs/opatch/opatch2015-02-24_13-16-53PM_1.log


OPatch failed with error code 73

dbcpblkdev01*DOYENDB-/home/oracle/Patches/19769496

Error:

OPatch failed with error code 73


  


Solution:



cd /u01/oracle/app/oracle/product/DOYENDB/11.2.3

mv Opatch Opatch_bak

unzip p6880880_112000_Linux-x86-64.zip


cd Patches/19769496

opatch prereq CheckConflictAgainstOHWithDetail -ph ./
Oracle Interim Patch Installer version 11.2.0.3.6
Copyright (c) 2013, Oracle Corporation.  All rights reserved.

PREREQ session

Oracle Home       : /u01/oracle/app/oracle/product/DOYENDB/11.2.3
Central Inventory : /u01/oracle/oraInventory
   from           : /u01/oracle/app/oracle/product/DOYENDB/11.2.3/oraInst.loc
OPatch version    : 11.2.0.3.6
OUI version       : 11.2.0.3.0
Log file location : /u01/oracle/app/oracle/product/DOYENDB/11.2.3/cfgtoollogs/opatch/opatch2015-02-24_15-51-36PM_1.log

Invoking prereq "checkconflictagainstohwithdetail"

Prereq "checkConflictAgainstOHWithDetail" passed.

OPatch succeeded.

==>opatch apply
Oracle Interim Patch Installer version 11.2.0.3.6
Copyright (c) 2013, Oracle Corporation.  All rights reserved.


Oracle Home       : /u01/oracle/app/oracle/product/DOYENDB/11.2.3
Central Inventory : /u01/oracle/oraInventory
   from           : /u01/oracle/app/oracle/product/DOYENDB/11.2.3/oraInst.loc
OPatch version    : 11.2.0.3.6
OUI version       : 11.2.0.3.0
Log file location : /u01/oracle/app/oracle/product/DOYENDB/11.2.3/cfgtoollogs/opatch/opatch2015-02-24_15-52-26PM_1.log

Verifying environment and performing prerequisite checks...
OPatch continues with these patches:   19121548  19769496

Do you want to proceed? [y|n]
Y
User Responded with: Y
All checks passed.

Please shutdown Oracle instances running out of this ORACLE_HOME on the local system.
(Oracle Home = '/u01/oracle/app/oracle/product/DOYENDB/11.2.3')


Is the local system ready for patching? [y|n]
y
User Responded with: Y
Backing up files...
Applying sub-patch '19121548' to OH '/u01/oracle/app/oracle/product/DOYENDB/11.2.3'

Patching component oracle.sysman.console.db, 11.2.0.3.0...

Patching component oracle.rdbms.rsf, 11.2.0.3.0...

Patching component oracle.rdbms.rman, 11.2.0.3.0...

Patching component oracle.rdbms, 11.2.0.3.0...

Patching component oracle.rdbms.dbscripts, 11.2.0.3.0...

Patching component oracle.ordim.client, 11.2.0.3.0...

Patching component oracle.ordim.jai, 11.2.0.3.0...

Verifying the update...
Applying sub-patch '19769496' to OH '/u01/oracle/app/oracle/product/DOYENDB/11.2.3'

Patching component oracle.sysman.agent, 10.2.0.4.3...

Patching component oracle.ovm, 11.2.0.3.0...

Patching component oracle.xdk, 11.2.0.3.0...

Patching component oracle.rdbms.util, 11.2.0.3.0...

Patching component oracle.rdbms, 11.2.0.3.0...

Patching component oracle.rdbms.dbscripts, 11.2.0.3.0...

Patching component oracle.xdk.parser.java, 11.2.0.3.0...

Patching component oracle.oraolap, 11.2.0.3.0...

Patching component oracle.rdbms.rsf, 11.2.0.3.0...

Patching component oracle.xdk.rsf, 11.2.0.3.0...

Verifying the update...

OPatch found the word "warning" in the stderr of the make command.
Please look at this stderr. You can re-run this make command.
Stderr output:
ins_emagent.mk:113: warning: overriding commands for target `nmosudo'
ins_emagent.mk:52: warning: ignoring old commands for target `nmosudo'
/u01/oracle/app/oracle/product/DOYENDB/11.2.3/sysman/lib/ins_emagent.mk:113: warning: overriding commands for target `nmosudo'
/u01/oracle/app/oracle/product/DOYENDB/11.2.3/sysman/lib/ins_emagent.mk:52: warning: ignoring old commands for target `nmosudo'


Composite patch 19769496 successfully applied.
OPatch Session completed with warnings.
Log file location: /u01/oracle/app/oracle/product/DOYENDB/11.2.3/cfgtoollogs/opatch/opatch2015-02-24_15-52-26PM_1.log

OPatch completed with warnings.

dbcpblkdev01*DOYENDB-/home/oracle/Patches/19769496