Blog dedicated to Oracle Applications (E-Business Suite) Technology; covers Apps Architecture, Administration and third party bolt-ons to Apps

Wednesday, September 26, 2007

File in patch is not a known Oracle Applications file

While applying 11.5.10.2 maintenance pack 3480000 on an 11.5.9 instance we got the following error:

AutoPatch error:
File in patch is not a known Oracle Applications file:
'bne conf example.txt'

Error occurred in version checking.
See above error messages or AutoPatch log file for details.
Exiting AutoPatch...

BNE.D was already applied on the 11.5.9 instance.

Patch 3480000 ships with bnefile.drv version 115.87.1012.5 which has this content:

# $Header: bnefile.drv 115.87.1012.5 2004/09/10 00:41:31 acleung noship $
# dbdrv: none
#==========================================================================
# (c) Copyright Oracle Corporation 1991
# All Rights Reserved
#
# =========================================================================
# FILENAME
# bnefile.drv
#
# PURPOSE
# Autoinstall file driver for Oracle Web ADI
#
#
# HISTORY
#
# 2001/06/22 DV Initial Creation.
# 2003/08/01 DG Added bne_processCheck.gif
# 3004/06/09 DG BNE.D
# ===========================================================================
#
#

if installation-type admin

bne admin/odf bneprim.odf
bne conf example.txt

Since we already applied BNE.D our bnefile.drv is already at a higher version: ppwms76@tsgsd1004 # adident Header $BNE_TOP/admin/driver/bnefile.drv
$BNE_TOP/admin/driver/bnefile.drv:
$Header bnefile.drv 115.96.1013.8 2007/02/16 03:34:35 dagroves noship $


# $Header: bnefile.drv 115.96.1013.8 2007/02/16 03:34:35 dagroves noship $
# dbdrv: none
#==========================================================================
# (c) Copyright Oracle Corporation 1991
# All Rights Reserved
#
# =========================================================================
# FILENAME
# bnefile.drv
#
# PURPOSE
# Autoinstall file driver for Oracle Web ADI
#
#
# HISTORY
#
# 2001/06/22 DV Initial Creation.
# 2003/08/01 DG Added bne_processCheck.gif
# 3004/06/09 DG BNE.D
# 2007/02/16 DG bug5886305
# ===========================================================================
#
#

if installation-type admin

bne admin/odf bneprim.odf

# SQL scripts for manual post-upgrade or post-install steps.
#

# Script for adding language rows to _TL tables for MLS
# bne admin/sql BNENLADD.sql
# Script for adding language rows to _TL tables for MLS, to be run via adpatch or 11i
bne sql BNENLINS.sql
#
#
# Added .lct files for the loaders
bne admin/import bnecomp.lct
bne admin/import bnecont.lct
bne admin/import bnefile.lct
bne admin/import bneint.lct
bne admin/import bnelay.lct
bne admin/import bnelaylob.lct
bne admin/import bnemap.lct
bne admin/import bneparamlist.lct
bne admin/import bness.lct
bne admin/import bneuserset.lct
bne admin/import bnevw.lct
bne admin/import bnequery.lct
bne admin/import bneperf.lct
bne admin/import bneflexoverride.lct
bne admin/import bnesecurity.lct
# Old Files pre 8.3... for back patching needs
# Added .lct files for the loaders
bne admin/import bnelang.lct
bne admin/import bnelangt.lct


Unfortunately Oracle removed the example file in the latest driver file. That’s why we are getting this issue. There are two workarounds:

Comment the example line in the 3480000/bne/admin/driver/bnefile.drv OR
Add the example line in the $BNE_TOP/admin/driver/bnefile.drv

I logged an SR with Oracle to validate my workaround. As expected, Oracle said: It is not supported to change or amend scripts, therefore please do not change the scripts unless Support advises to do so.

They gave a different workaround which we finally followed:

Please do not edit the bnefile.drv this is not a supported solution.

Instead please do the following:

1. Backup the existing file:
>cd $BNE_TOP/admin/driver
>mv bnefile.drv bnefile_bak.drv

2. Manually copy the bnefile.drv from patch 3480000 to $BNE_TOP/admin/driver

3. Run adpatch again.

4. Once 3480000 is applied successfully replace the backed up file.

Funny thing is that when we upgraded the 11.5.9 ASCP instance which also had BNE.D already applied, this error did not crop up. Still investigating, why it didn't happen in the ASCP instance.

No comments: