AMX DAS-AMP4 Guia de Configuração descarregar pdf (Página 238)

14-8 Oracle Application Management Pack for Oracle E-Business Suite Guide

within the file driver file for selected file types like forms, reports, and so on. If not, then

the following error is thrown during patching: "File in patch is not a known Oracle

Applications file".

Customization Manager takes care of this file driver file requirement automatically.

Customization Manager implicitly generates a file driver file for the relevant files in a

package. During deployment with Patch Manager, these entries are automatically

added to the custom product master file driver file. In case a user applies a patch

manually with adpatch, he or she can run updateFileDriver.pl within the

<package>/meta-inf folder before invoking adpatch.

Note that if you get the error "File in patch is not a known Oracle Applications file"

while applying a custom patch built with Customization Manager, then it could be due

to a missing entry in file driver file for the custom product for one or more custom files.

The file driver file for a custom product is located under:

$<custom_product_top>/admin/driver/<custom_product_short_name>file.drv

For example, if XXCO is the custom product, then you can find the file driver file under

$XXCO_TOP/admin/driver/xxcofile.drv

All custom files would require an entry in the respective file driver file depending on

the custom product they belong, EXCEPT files which have destination path beginning

with any of the following:

• admin

• sql

• mds

• lib

• patch

• help

• def

as well as any java file under destination path beginning with "java".

The usual format for an entry into the file driver file is:

Sample entries are as below:

xxco admin/sql XXCONLADD.sql

xxco forms/<LANG> XXCOFORM.fmb

1 2 ... 233 234 235 236 237 238 239 240 241 242 243 ... 337 338

Sem comentários

AMX DAS-AMP4 Guia de Configuração Página 238