How to Regenerate forms file in Apps R12 using adadmin

1. Start the adadmin Utility 

From a command line session, as the applmgr user, start the adadmin utility. Please note that if your system is configured using more than one tier and more than one APPL_TOP (in contrast to the shared APPL_TOP), you should run this utility from each forms tier.

 $AD_TOP/bin/adadmin

2. Step Through the Initial adadmin Questions

Reply to the questions as required, such as in the following example:

Your default directory is '/u01/oracle/aol11iappl'.
Is this the correct APPL_TOP [Yes] ?

If the above is true, then hit the [Enter] key.

AD Administration records your AD Administration session in a text file
you specify. Enter your AD Administration log file name or press [Return]
to accept the default file name shown in brackets.

Filename [adadmin.log] :

Here you can record your adadmin session in a specific log file.
This log file will be saved in 
$APPL_TOP/admin/<INSTANCE_NAME>/log directory.

You can be notified by email if a failure occurs.
Do you wish to activate this feature [No] ?

This option only works in UNIX and the purpose of this question is to notify the AD administrator by mail if any failure occurred while adadmin was running in unattended mode.

Please enter the batchsize [1000] :

This option asks for a specific batch size, to reserve memory when adadmin validates package and procedure information. This option only is meaningful when running database administrative related tasks. For the purpose of generating a form, you can leave the default value.

After this last step, the utility will read the ad configuration file and display related information.

The next step which requires user interaction is:

You are about to use or modify Oracle Applications product tables 
in your ORACLE database 'aol11i' 
using ORACLE executables in '/u01/oracle/aol11iora/8.0.6'.

Is this the correct database [Yes] ?

If correct, hit the [Enter] key. Otherwise, exit this utility by typing "abort" plus the [b] key and verify if your environment has been sourced correctly.

AD Administration needs the password for your 'SYSTEM' ORACLE schema
in order to determine your installation configuration.

Enter the password for your 'SYSTEM' ORACLE schema:

Here you must enter your SYSTEM database user password. There is no default, since adadmin has no way to determine SYSTEM's password.

Connecting to SYSTEM......Connected successfully.

The ORACLE username specified below for Application Object Library
uniquely identifies your existing product group: APPLSYS
Enter the ORACLE password of Application Object Library [APPS] :

At this point, provide the APPS database user password. By default, the password is APPS.

After finally reaching this point, the utility will try to connect to your database and get information regarding your system.

The next step which requires user interaction is the main menu:

            AD Administration Main Menu

   --------------------------------------------------

   1.    Maintain Applications Files menu

   2.    Exit AD Administration

   Enter your choice : 1

Note: In this example, we are showing the main menu for a forms tier adadmin.

In single node installations, the menu is:

            AD Administration Main Menu

   --------------------------------------------------

   1.    Maintain Applications Database Objects menu

   2.    Maintain Applications Files menu

   3.    Exit AD Administration

   Enter your choice : 2

3. Navigate Through the adadmin Menus.

Select the option "Maintain Applications Files menu" by entering the number located at the left of this option.

(This is the number '2' in the above example.)

This will lead to the next menu:

         Maintain Applications Files

   ----------------------------------------

   1.    Create Applications environment file

   2.    Relink Applications programs

   3.    Copy files to destinations

   4.    Convert Character Set

   5.    Verify files necessary for runtime

   6.    Generate message files

   7.    Generate form files

   8.    Generate graphics files

   9.    Generate product jar files

  10.    Return to Main Menu

Enter your choice :  7

In order to generate a specific form, select the option "Generate form files". Do so by entering the number located at the left of the mentioned option (in this case, 7).  Now, you will be asked for the number of parallel workers that will start generating forms:

Enter the number of workers [3] :

In order to determine the optimal number of workers for your system, you should consider the following general rule:

Total of available workers for your system = (Number of processors) x 3 

In our case, we will generate only ONE form, so there is no need to invoke three workers. In our example, we will generate one single form, but for two languages: US (American English) and ESA (Latin American Spanish). Therefore, the maximum number of workers needed will be two.

The next question is:

Do you want to generate Oracle Forms objects
using this character set [Yes] ?

If this is your correct character set, hit [Enter].  Otherwise, please verify your environment.

Do you want to regenerate Oracle Forms PL/SQL library files [Yes] ? 

In this case, we will not generate any PL/SQL library files, so you might reply 'n' to the above question.

Do you want to regenerate Oracle Forms menu files [Yes] ?

Same as above; reply 'n' to this question.

Do you want to regenerate Oracle Forms executable files [Yes] ?

Here, hit [Enter] to accept the default 'Yes'.

Enter list of products ('all' for all products) [all] :

Now, we need to specify the Application short name. (gl, for General Ledger, ap for Payables, and so on).  In our example we will be using module fnd (Application Object Library).  In 11i, the entry must be typed using lowercase characters.

Generate specific forms objects for each selected product [No] ?

Answer 'y' to this question, since it will regenerate all forms for the module selected previously if 'No' is answered here.

The current set of installed languages is: US ESA

Please select languages for generating Oracle Forms files.
You may select all of the above languages, or just a subset.

Enter list of languages ('all' for all of the above) [all] :

In this case, reply 'all', since this will regenerate the form for all existing languages.

You selected the following languages: US ESA

Is this the correct set of languages [Yes] ? 

In this case, answer 'y' since this is the correct language.

At this point, you will receive, based on how you answered the questions a list of all possible forms that you are able to regenerate:

Selecting product forms to generate...

Selecting forms for Application Object Library...

List of forms in Application Object Library :

    APPTREE.fmx   FNDADDSQ.fmx   FNDADDTC.fmx   FNDADDVW.fmx    FNDAPLT.fmx
   FNDATCAT.fmx   FNDATDAG.fmx   FNDATDAI.fmx   FNDATDAT.fmx   FNDATDOC.fmx
   FNDATENT.fmx   FNDATFUN.fmx   FNDATTCH.fmx   FNDCPDCL.fmx   FNDCPDCQ.fmx
   FNDCPDCS.fmx   FNDCPDIA.fmx   FNDCPDPD.fmx   FNDCPDSR.fmx   FNDCPMCP.fmx
   FNDCPMMD.fmx   FNDCPMMT.fmx   FNDCPMPE.fmx   FNDCPRNO.fmx   FNDCPVCM.fmx
   FNDCPVWR.fmx   FNDFBMAS.fmx   FNDFBMPA.fmx   FNDFBRFP.fmx   FNDFBTST.fmx
   FNDFFIDF.fmx   FNDFFIIF.fmx   FNDFFMCV.fmx   FNDFFMDC.fmx   FNDFFMHL.fmx
   FNDFFMIS.fmx   FNDFFMSA.fmx   FNDFFMSV.fmx   FNDFFMVS.fmx   FNDFFMWP.fmx
   FNDFFSRA.fmx   FNDFFSRN.fmx   FNDFFTST.fmx   FNDFLADM.fmx   FNDFMFBF.fmx
   FNDFMFUN.fmx   FNDLVMLU.fmx   FNDMDMSG.fmx   FNDMNMNU.fmx   FNDNLDCX.fmx
   FNDNLDLG.fmx   FNDNLDTI.fmx   FNDPMNET.fmx   FNDPOMPO.fmx   FNDPOMPV.fmx
   FNDPOMSV.fmx   FNDPRMPD.fmx   FNDPRMPR.fmx   FNDPRRPS.fmx   FNDPRTYP.fmx
   FNDRSGRP.fmx   FNDRSRUN.fmx   FNDRSSET.fmx   FNDSCAPP.fmx   FNDSCAUS.fmx
   FNDSCDDG.fmx   FNDSCGRP.fmx   FNDSCMON.fmx   FNDSCMOU.fmx   FNDSCPLS.fmx
   FNDSCRSP.fmx   FNDSCSGN.fmx   FNDSNASQ.fmx   FNDSNDCT.fmx   FNDSNDSQ.fmx
   TEMPLATE.fmx

Enter forms to generate, or enter 'all' [all] :

In this example we will try to regenerate FNDCPMCP.fmx.

Enter 'FNDCPMCP.fmx' at the prompt. Once you do so, adadmin will invoke the appropriate forms compiler and will regenerate the forms.

If any error is found, review the adadmin log file and the adworker log file(s).  The adworker log files are also located under $APPL_TOP/admin/<INSTANCE_NAME>/log directory.  The file name is adworkxx.log where xx is the number of the worker that had failed.

If submitting the problem to Oracle Support as a service request, please upload the adadmin log and the relevant adworker log.

How to Regenerate Message files in Apps R12 using adadmin

[apdba@oracledb1 ~]$

[apdba@oracledb1 ~]$ cd $GL_TOP

[apdba@oracledb1 12.0.0]$ ls

admin  forms  html  lib  mds    mesg  patch    sql

bin    help   java  log  media  out   reports

[apdba@oracledb1 12.0.0]$ cd me

-bash: cd: me: No such file or directory

[apdba@oracledb1 12.0.0]$ cd me

media/ mesg/

[apdba@oracledb1 12.0.0]$ cd mesg/

[apdba@oracledb1 mesg]$ ls

US.msb

[apdba@oracledb1 mesg]$

[apdba@oracledb1 mesg]$

[apdba@oracledb1 mesg]$

[apdba@oracledb1 mesg]$ mv US.msb US.msb.bkp1

[apdba@oracledb1 mesg]$

[apdba@oracledb1 mesg]$

[apdba@oracledb1 mesg]$ ls

US.msb.bkp1

[apdba@oracledb1 mesg]$

[apdba@oracledb1 mesg]$ adadmin

                     Copyright (c) 2002 Oracle Corporation

                        Redwood Shores, California, USA

                     Oracle Applications AD Administration

                                 Version 12.0.0

NOTE: You may not use this utility for custom development

      unless you have written permission from Oracle Corporation.

Your default directory is '/u01/apdba/apps/apps_st/appl'.

Is this the correct APPL_TOP [Yes] ?

AD Administration records your AD Administration session in a text file

you specify.  Enter your AD Administration log file name or press [Return]

to accept the default file name shown in brackets.

Filename [adadmin.log] :

************* Start of AD Administration session *************

AD Administration version: 12.0.0

AD Administration started at: Mon Apr 08 2013 08:26:57

APPL_TOP is set to /u01/apdba/apps/apps_st/appl

You can be notified by email if a failure occurs.

Do you wish to activate this feature [No] ?

Please enter the batchsize [1000] :

Please enter the name of the Oracle Applications System that this

APPL_TOP belongs to.

The Applications System name must be unique across all Oracle

Applications Systems at your site, must be from 1 to 30 characters

long, may only contain alphanumeric and underscore characters,

and must start with a letter.

Sample Applications System names are: "prod", "test", "demo" and

"Development_2".

Applications System Name [PROD] : PROD *

NOTE: If you do not currently have certain types of files installed

in this APPL_TOP, you may not be able to perform certain tasks.

Example 1: If you don't have files used for installing or upgrading

the database installed in this area, you cannot install or upgrade

the database from this APPL_TOP.

Example 2: If you don't have forms files installed in this area, you cannot

generate them or run them from this APPL_TOP.

Example 3: If you don't have concurrent program files installed in this area,

you cannot relink concurrent programs or generate reports from this APPL_TOP.

Do you currently have files used for installing or upgrading the database

installed in this APPL_TOP [YES] ? YES *

Do you currently have Java and HTML files for HTML-based functionality

installed in this APPL_TOP [YES] ? YES *

Do you currently have Oracle Applications forms files installed

in this APPL_TOP [YES] ? YES *

Do you currently have concurrent program files installed

in this APPL_TOP [YES] ? YES *

Please enter the name Oracle Applications will use to identify this APPL_TOP.

The APPL_TOP name you select must be unique within an Oracle Applications

System, must be from 1 to 30 characters long, may only contain

alphanumeric and underscore characters, and must start with a letter.

Sample APPL_TOP Names are: "prod_all", "demo3_forms2", and "forms1".

APPL_TOP Name [oracledb1] : oracledb1 *

You are about to use or modify Oracle Applications product tables

in your ORACLE database 'PROD'

using ORACLE executables in '/u01/apdba/apps/tech_st/10.1.2'.

Is this the correct database [Yes] ?

AD Administration needs the password for your 'SYSTEM' ORACLE schema

in order to determine your installation configuration.

Enter the password for your 'SYSTEM' ORACLE schema:

The ORACLE username specified below for Application Object Library

uniquely identifies your existing product group: APPLSYS

Enter the ORACLE password of Application Object Library [APPS] :

AD Administration is verifying your username/password.

The status of various features in this run of AD Administration is:

                                           <-Feature version in->

Feature                          Active?   APPLTOP    Data model    Flags

------------------------------   -------   --------   -----------   -----------

CHECKFILE                        Yes       1          1             Y N N Y N Y

PREREQ                           Yes       6          6             Y N N Y N Y

CONCURRENT_SESSIONS              No        2          2             Y Y N Y Y N

PATCH_TIMING                     Yes       2          2             Y N N Y N Y

PATCH_HIST_IN_DB                 Yes       6          6             Y N N Y N Y

SCHEMA_SWAP                      Yes       1          1             Y N N Y Y Y

JAVA_WORKER                      Yes       1          1             Y N N Y N Y

CODELEVEL                        Yes       1          1             Y N N Y N Y

Identifier for the current session is 19770

Reading product information from file...

Reading language and territory information from file...

Reading language information from applUS.txt ...

AD Administration warning:

 Product Data File

 /u01/apdba/apps/apps_st/appl/admin/zfaprod.txt

 does not exist for product "zfa".

This product is registered in the database but the

above file does not exist in APPL_TOP.  The product

will be ignored without error.

AD Administration warning:

 Product Data File

 /u01/apdba/apps/apps_st/appl/admin/zsaprod.txt

 does not exist for product "zsa".

This product is registered in the database but the

above file does not exist in APPL_TOP.  The product

will be ignored without error.

AD Administration warning:

 Product Data File

 /u01/apdba/apps/apps_st/appl/admin/jtsprod.txt

 does not exist for product "jts".

This product is registered in the database but the

above file does not exist in APPL_TOP.  The product

will be ignored without error.

Reading database to see what industry is currently installed.

Reading FND_LANGUAGES to see what is currently installed.

Currently, the following language is installed:

Code   Language                                Status

----   --------------------------------------- ---------

US     American English                        Base

Your base language will be AMERICAN.

Setting up module information.

Reading database for information about the modules.

Saving module information.

Reading database for information about the products.

Reading database for information about how products depend on each other.

Reading topfile.txt ...

Saving product information.

AD code level : [B.1]

            AD Administration Main Menu

   --------------------------------------------------

   1.    Generate Applications Files menu

   2.    Maintain Applications Files menu

   3.    Compile/Reload Applications Database Entities menu

   4.    Maintain Applications Database Entities menu

   5.    Change Maintenance Mode

   6.    Exit AD Administration

Enter your choice [6] : 1

         Generate Applications Files

   ----------------------------------------

   1.    Generate message files

   2.    Generate form files

   3.    Generate report files

   4.    Generate product JAR files

   5.    Return to Main Menu

Enter your choice [5] : 1

AD utilities can support a maximum of 999 workers. Your

current database configuration supports a maximum of 73 workers.

Oracle recommends that you use between 4 and 8 workers.

Enter the number of workers [4] :

Your current character set is "UTF8".

Do you want to generate Oracle Message files

using this character set [Yes] ?

Enter list of products ('all' for all products) [all] : GL

The current set of installed languages is: US

Please select languages for generating Oracle Message files.

You may select all of the above languages, or just a subset.

Enter list of languages ('all' for all of the above) [all] : US

You selected the following languages: US

Is this the correct set of languages [Yes] ?

Setting up environment...

Generating message files...

Creating the AD_UTIL_PARAMS table...

Table AD_UTIL_PARAMS already exists, so dropping the table and recreating it.

Creating FND_INSTALL_PROCESSES table...

Writing dependencies of jobs to run to appldep.txt file...

There are now 1 jobs remaining (current phase=admin):

    0 running, 1 ready to run and 0 waiting.

Reading completed jobs from restart file (if any).

There are now 1 jobs remaining (current phase=admin):

    0 running, 1 ready to run and 0 waiting.

Determining which java executables are supported by adJavaWorker...

Starting worker processes.

Worker process 1 started.

Worker process 2 started.

Worker process 3 started.

Worker process 4 started.

Checking if all jobs have their actual and symbolic arguments in sync....

Done.

Writing jobs to run to restart file.

Reading jobs from FND_INSTALL_PROCESSES table ...

Done reading jobs from FND_INSTALL_PROCESSES table ...

Telling workers to read 'todo' restart file.

************* Start of AD Worker session *************

AD Worker version: 12.0.0

AD Worker started at: Mon Apr 08 2013 08:28:29

APPL_TOP is set to /u01/apdba/apps/apps_st/appl

************* Start of AD Worker session *************

AD Worker version: 12.0.0

AD Worker started at: Mon Apr 08 2013 08:28:29

APPL_TOP is set to /u01/apdba/apps/apps_st/appl

************* Start of AD Worker session *************

AD Worker version: 12.0.0

AD Worker started at: Mon Apr 08 2013 08:28:29

APPL_TOP is set to /u01/apdba/apps/apps_st/appl

************* Start of AD Worker session *************

AD Worker version: 12.0.0

AD Worker started at: Mon Apr 08 2013 08:28:29

APPL_TOP is set to /u01/apdba/apps/apps_st/appl

Done.

Starting phase 1000 (admin): Administration

There are now 1 jobs remaining (current phase=admin):

    0 running, 1 ready to run and 0 waiting.

 Assigned: file US.msb       on worker  1 for product gl  username GL.

Completed: file US.msb       on worker  1 for product gl  username GL.

Telling workers to quit...

All workers have quit.

Dropping FND_INSTALL_PROCESSES table...

FND_INSTALL_PROCESSES table dropped.

Dropping AD_DEFERRED_JOBS table...

AD_DEFERRED_JOBS table dropped.

Review the messages above, then press [Return] to continue.

Backing up restart files, if any......Done.

         Generate Applications Files

   ----------------------------------------

   1.    Generate message files

   2.    Generate form files

   3.    Generate report files

   4.    Generate product JAR files

   5.    Return to Main Menu

Enter your choice [5] :

            AD Administration Main Menu

   --------------------------------------------------

   1.    Generate Applications Files menu

   2.    Maintain Applications Files menu

   3.    Compile/Reload Applications Database Entities menu

   4.    Maintain Applications Database Entities menu

   5.    Change Maintenance Mode

   6.    Exit AD Administration

Enter your choice [6] :

Backing up restart files, if any......Done.

sqlplus -s APPS/***** @/u01/apdba/apps/apps_st/appl/ad/12.0.0/sql/adtimrpt.sql 19770 adt19770

A job timing report has been generated for the current session.

You should check the file

    /u01/apdba/apps/apps_st/appl/admin/PROD/out/adt19770.lst

for details.

Purging timing information for prior sessions.

sqlplus -s APPS/***** @/u01/apdba/apps/apps_st/appl/ad/12.0.0/sql/adtpurge.sql 10 1000

Done purging timing information for prior sessions.

AD Administration is complete.

Errors and warnings are listed in the log file

/u01/apdba/apps/apps_st/appl/admin/PROD/log/adadmin.log

and in other log files in the same directory.

[apdba@oracledb1 mesg]$ ls

US.msb  US.msb.bkp1

[apdba@oracledb1 mesg]$

To compile JSP manually in 11i/R12

How to compile all JSP pages  manually in R12:
---->login as appliation user and source environment file

---->go to the below location and run commands
cd $FND_TOP/patch/115/bin
perl ojspCompile.pl --compile --flush -p 2

---> Restart the Apache services or Middleware services.



How to compile individual JSP manually in R12:

---> go to below mentioned location and delete any file. for every jsp page in $OA_HTML location there will be class file in $COMMON_TOP/_pages

   cd $COMMON_TOP/_pages

--->Delete the class files (abcdef.class) for the JSP that you want to compile manually.

    Eg. JSP File abcdef_12.jsp
    Class File: abcdef_12.class ------------- Delete this file.

---->Navigate to the OA_HTML (Location for all the Jsp pages). if the JSP pages do not exist, copy the       JSP to the location & run the below command.

      $FND_TOP/patch/115/bin/ojspCompile.pl --compile -s 'abcdef_12.jsp' --flush

---->Restart the Apache services or Middle-ware services.

---->Check whether the respective class files have been created under

     cd $COMMON_TOP/_pages

Location of JSP Compilation logs:

---->In 11i, all jsp compilation errors are logged in $IAS_ORACLE_HOME/ Apache/ Jserv/ logs/ mod_jserv.log

---->In R12, all jsp compilation errors are logged in $LOG_HOME/ ora/ 10.1.3/ j2ee/ oacore/ oacore_default_group_1/ application.log

How to run autoconfig R12 - Steps

 A) Running Autoconfig on R12 environment Application Tier

1. Login as user owning application tier for R12 (usually applmgr)

2. Set environment variable by executing env file $INSTALL_BASE/ apps/ apps_st/ appl/ APPL[$SID]_[$hostname].env

3. cd $ADMIN_SCRIPTS_HOME  (or $INSTALL_BASE/apps/$CONTEXT_NAME/ admin/ scripts)

4. run adautocfg.sh (Autoconfig script)
./adautocfg.sh

5. Supply apps password when prompted.
 

 B) Running Autoconfig on R12 environment Database Tier

1.Login as user owning database tier for R12 (usually oracle)

2. Set environment variable by executing env file $INSTALL_BASE/ db/ tech_st/ [11.1.0 or 10.2.0]/ [$SID]_[$hostname].env

3. cd $ORACLE_HOME/ appsutil/ scripts/ $CONTEXT_NAME

4. run adautocfg.sh (Autoconfig script)
./adautocfg.sh

5. Supply apps password when prompted

.

.

Things good to know about Autoconfig in R12

1. Autoconfig logs for R12 application tier are at

$INSTALL_BASE/inst/apps/$CONTEXT_NAME/admin/log/$MMDDHHMM/adconfig.log ($INST_TOP/admin/log/[$MMDDhhmm])

2. Autoconfig logs for R12 Database tier are at

[$RDBMS_ORACLE_HOME]/appsutil/log/[$CONTEXT_NAME]/[$MMDDhhmm]/adconfig.log

3. R12 system is autoconfig enabled and uses context file stored in [INST_TOP]/appl/admin/[CONTEXT_NAME].xml (Application Tier)
and
[$DATABASE_ORACLE_HOME]/appsutil/[$CONTEXT_NAME].xml (Database Tier)

.

Related

387859.1  Using AutoConfig to Manage System Configurations in Oracle E-Business Suite Release 12

oracle apps disable maintenance mode

Warning

The system has not been taken off maintenance mode completely. Please contact your System Administrator.

This problem usually arises when you start the application tier services before bringing the system out of the "Maintenance Mode".

Please follow these steps:

1) Shutdown all the application tier services and ensure that the Concurrent Manager (FNDLIBR) and JAVA processes are stopped completely.
The java processes may still be running kill the parent process using
kill -9 PID command.

2) Through adadmin "DISABLE" maintenance mode.

3) Run autoconfig once

4) Start the application tier services

root#su - ap user

ap user$adadmin

[appltest@au10dmzh49 scripts]$ adadmin

Copyright (c) 2002 Oracle Corporation

Redwood Shores, California, USA

Oracle Applications AD Administration

Version 12.0.0

NOTE: You may not use this utility for custom development

unless you have written permission from Oracle Corporation.

Your default directory is '/d01/oracle/PROD/apps/apps_st/appl'.

Is this the correct APPL_TOP [Yes] ?

AD Administration records your AD Administration session in a text file

you specify. Enter your AD Administration log file name or press [Return]

to accept the default file name shown in brackets.

Filename [adadmin.log] :

************* Start of AD Administration session *************

AD Administration version: 12.0.0

AD Administration started at: Tue Jun 21 2011 14:54:06

APPL_TOP is set to /d01/oracle/PROD/apps/apps_st/appl

You can be notified by email if a failure occurs.

Do you wish to activate this feature [No] ?

Please enter the batchsize [1000] :

Please enter the name of the Oracle Applications System that this

APPL_TOP belongs to.

The Applications System name must be unique across all Oracle

Applications Systems at your site, must be from 1 to 30 characters

long, may only contain alphanumeric and underscore characters,

and must start with a letter.

Sample Applications System names are: "prod", "test", "demo" and

"Development_2".

Applications System Name [PROD] : PROD *

NOTE: If you do not currently have certain types of files installed

in this APPL_TOP, you may not be able to perform certain tasks.

Example 1: If you don't have files used for installing or upgrading

the database installed in this area, you cannot install or upgrade

the database from this APPL_TOP.

Example 2: If you don't have forms files installed in this area, you cannot

generate them or run them from this APPL_TOP.

Example 3: If you don't have concurrent program files installed in this area,

you cannot relink concurrent programs or generate reports from this APPL_TOP.

Do you currently have files used for installing or upgrading the database

installed in this APPL_TOP [YES] ? YES *

Do you currently have Java and HTML files for HTML-based functionality

installed in this APPL_TOP [YES] ? YES *

Do you currently have Oracle Applications forms files installed

in this APPL_TOP [YES] ? YES *

Do you currently have concurrent program files installed

in this APPL_TOP [YES] ? YES *

Please enter the name Oracle Applications will use to identify this APPL_TOP.

The APPL_TOP name you select must be unique within an Oracle Applications

System, must be from 1 to 30 characters long, may only contain

alphanumeric and underscore characters, and must start with a letter.

Sample APPL_TOP Names are: "prod_all", "demo3_forms2", and "forms1".

APPL_TOP Name [au10dmzh49] : au10dmzh49 *

You are about to use or modify Oracle Applications product tables

in your ORACLE database 'PROD'

using ORACLE executables in '/d01/oracle/PROD/apps/tech_st/10.1.2'.

Is this the correct database [Yes] ?

AD Administration needs the password for your 'SYSTEM' ORACLE schema

in order to determine your installation configuration.

Enter the password for your 'SYSTEM' ORACLE schema:manager

The ORACLE username specified below for Application Object Library

uniquely identifies your existing product group: APPLSYS

Enter the ORACLE password of Application Object Library [APPS] :apps

AD Administration is verifying your username/password.

The status of various features in this run of AD Administration is:

<-Feature version in->

Feature Active? APPLTOP Data model Flags

------------------------------ ------- -------- ----------- -----------

CHECKFILE Yes 1 1 Y N N Y N Y

PREREQ Yes 6 6 Y N N Y N Y

CONCURRENT_SESSIONS No 2 2 Y Y N Y Y N

PATCH_TIMING Yes 2 2 Y N N Y N Y

PATCH_HIST_IN_DB Yes 6 6 Y N N Y N Y

SCHEMA_SWAP Yes 1 1 Y N N Y Y Y

JAVA_WORKER Yes 1 1 Y N N Y N Y

CODELEVEL Yes 1 1 Y N N Y N Y

Identifier for the current session is 16760

Reading product information from file...

Reading language and territory information from file...

Reading language information from applUS.txt ...

AD Administration warning:

Product Data File

/d01/oracle/PROD/apps/apps_st/appl/admin/zfaprod.txt

does not exist for product "zfa".

This product is registered in the database but the

above file does not exist in APPL_TOP. The product

will be ignored without error.

AD Administration warning:

Product Data File

/d01/oracle/PROD/apps/apps_st/appl/admin/zsaprod.txt

does not exist for product "zsa".

This product is registered in the database but the

above file does not exist in APPL_TOP. The product

will be ignored without error.

AD Administration warning:

Product Data File

/d01/oracle/PROD/apps/apps_st/appl/admin/jtsprod.txt

does not exist for product "jts".

This product is registered in the database but the

above file does not exist in APPL_TOP. The product

will be ignored without error.

Reading database to see what industry is currently installed.

Reading FND_LANGUAGES to see what is currently installed.

Currently, the following language is installed:

Code Language Status

---- --------------------------------------- ---------

US American English Base

Your base language will be AMERICAN.

Setting up module information.

Reading database for information about the modules.

Saving module information.

Reading database for information about the products.

Reading database for information about how products depend on each other.

Reading topfile.txt ...

Saving product information.

AD code level : [B.1]

AD Administration Main Menu

--------------------------------------------------

1. Generate Applications Files menu

2. Maintain Applications Files menu

3. Compile/Reload Applications Database Entities menu

4. Maintain Applications Database Entities menu

5. Change Maintenance Mode

6. Exit AD Administration

select 5