************* Start of AD Administration session *************
AD Administration version: 12.0.0
AD Administration started at: Wed Feb 21 2018 16:51:57
APPL_TOP is set to /TESTAPPS/app/appldev/apps/apps_st/appl
NLS_LANG value from the environment is : American_America.UTF8
NLS_LANG value for this AD utility run is : AMERICAN_AMERICA.UTF8
You can be notified by email if a failure occurs.
Do you wish to activate this feature [No] ? No
Please enter the batchsize [1000] : 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 [DEV] : DEV *
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 [tjpsb008] : tjpsb008 *
You are about to use or modify Oracle Applications product tables
in your ORACLE database 'DEV'
using ORACLE executables in '/TESTAPPS/app/appldev/apps/tech_st/10.1.2'.
Is this the correct database [Yes] ? 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: *****
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] : *****
AD Administration is verifying your username/password.
Connecting to APPLSYS......Connected successfully.
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
Connecting to SYSTEM......Connected successfully.
Connecting to APPLSYS......Connected successfully.
Identifier for the current session is 58870
Reading product information from file...
Reading language and territory information from file...
Reading language information from applUS.txt ...
AD Administration warning:
Product Data File
/TESTAPPS/app/appldev/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
/TESTAPPS/app/appldev/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
/TESTAPPS/app/appldev/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.
Connecting to SYSTEM......Connected successfully.
Connecting to APPLSYS......Connected successfully.
Connecting to SYSTEM......Connected successfully.
Reading database for information about how products depend on each other.
Connecting to APPLSYS......Connected successfully.
Reading topfile.txt ...
Saving product information.
Connecting to SYSTEM......Connected successfully.
Connecting to APPLSYS......Connected successfully.
AD code level : [B.7]
Connecting to SYSTEM......Connected successfully.
Connecting to APPS......Connected successfully.
Connecting to APPLSYS......Connected successfully.
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] : 5
Connecting to APPS......Connected successfully.
Connecting to APPS......Connected successfully.
Change Maintenance Mode
----------------------------------------
Maintenance Mode is currently: [Disabled].
Maintenance mode should normally be enabled when patching
Oracle Applications and disabled when users are logged on
to the system. See the Oracle Applications Maintenance
Utilities manual for more information about maintenance mode.
Please select an option:
1. Enable Maintenance Mode
2. Disable Maintenance Mode
3. Return to Main Menu
Enter your choice [3] : 1
sqlplus -s &un_apps/***** @/TESTAPPS/app/appldev/apps/apps_st/appl/ad/12.0.0/patch/115/sql/adsetmmd.sql ENABLE
Connected.
PL/SQL procedure successfully completed.
Commit complete.
Successfully enabled Maintenance Mode.
Review the messages above, then press [Return] to continue.
Time is: Wed Feb 21 2018 16:52:34
Backing up restart files, if any......Done.
Connecting to APPLSYS......Connected successfully.
Connecting to APPS......Connected successfully.
Connecting to APPS......Connected successfully.
Change Maintenance Mode
----------------------------------------
Maintenance Mode is currently: [Enabled].
Maintenance mode should normally be enabled when patching
Oracle Applications and disabled when users are logged on
to the system. See the Oracle Applications Maintenance
Utilities manual for more information about maintenance mode.
Please select an option:
1. Enable Maintenance Mode
2. Disable Maintenance Mode
3. Return to Main Menu
Enter your choice [3] : 3
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] : 6
Time is: Wed Feb 21 2018 16:52:34
Backing up restart files, if any......Done.
Time is: Wed Feb 21 2018 16:52:34
There is no timing information available for the current session.
AD Administration is complete.
Errors and warnings are listed in the log file
/TESTAPPS/app/appldev/apps/apps_st/appl/admin/DEV/log/adadmin_27347602_21feb18.log
and in other log files in the same directory.
No comments:
Post a Comment