Here are some of the important tables used by and updated by ADPATCH utility.
AD_APPLIED_PATCHES
AD_APPLIED_PATCHES holds information about the “distinct” Oracle Applications patches that have been applied. If 2 patches happen to have the same name but are different in content (eg. “merged” patches), then they are considered distinct and this table will therefore hold 2 records.
AD_BUGS
AD_BUGS holds information about the various Oracle Applications bugs whose fixes have been applied (ie. patched) in the Oracle Applications installation.
AD_PATCH_DRIVERS
This table holds information about the patch drivers that comprise a patch.
AD_FILE_VERSIONS
This table holds the various versions of Oracle Applications files (real files, not “pseudo-files”), that have ever been patched or executed in the Oracle Applications installation.
AD_FILES
AD_FILES is the “files repository”. It contains information about the various files that have been patched in the Oracle Applications installation.
Some entries are “pseudo-files” and not real files, (eg. directories) in which case some of the columns are not applicable and would then hold the value “DUMMY”
AD_PATCH_DRIVER_LANGS
NLS patches (or more specifically, NLS patch drivers) pertain to a language or multiple languages. This table holds that language (or multiple languages).
AD_PATCH_DRIVER_MINIPKS
This table holds information about the various Mini Packs contained in a patch (driver)
AD_PATCH_RUN_BUG_ACTIONS holds the various actions present in “applied” bug (fix). If Autopatch determined not to apply a bug (fix), then this table will not hold any records for that “unapplied” bug fix.
AD_PATCH_RUN_BUG_ACTIONS
Even though a patch may have been applied on an Oracle Applications installation, some actions in some of its included bugs (fixes) may not have got executed if the “Autopatch” utility determined that it was not necessary to execute those actions. In such cases, EXECUTED_FLAG is set to N.
AD_PATCH_RUN_BUGS
This table holds information about the bugs fixed in a specific run of Autopatch.
AD_PATCH_RUN_BUGS holds information about the various bugs fixed in a specific run of Autopatch.
Even though a patch may have been applied on an Oracle Applications installation, some bugs (fixes) contained in it may not get applied due to some reason. In such cases, the REASON_NOT_APPLIED column holds the reason.
AD_PATCH_RUNS
AD_PATCH_RUNS holds information about the various invocations of Autopatch for applying Oracle Applications patches to a specific release of an Oracle Applications installation.
If multiple drivers are run in one invocation of Autopatch, they result in multiple records in this table. These multiple records will all have the same SESSION_ID (because they arose from one Autopatch invocation), but different TASK_NUMBER’s. The TASK_NUMBER’s in this case will be numbered sequentially as 1, 2, 3, etc.
Note that when the database driver of a Maintenance Pack is applied, it bumps up the release version by creating a new record in AD_RELEASES, which is then pointed to by the UPDATED_TO_RELEASE_ID column of the old record.
AD_RELEASES
AD_RELEASES holds the various Oracle Applications releases that an installation of Oracle Applications has gone through in its entire life cycle.
It should be noted that START_DATE_ACTIVE, END_DATE_ACTIVE and BASE_RELEASE_FLAG are loosely-maintained informational columns and are not accurately maintained, and therefore should not be relied upon heavily.
AD_PATCH_COMMON_ACTIONS
This table holds distinct information about the various actions that are (often repeatedly) performed by Autopatch as part of applying patches.
Hope this helps !!
References:
Metalink ETRM DIRECT ACCESS DOCUMENT 150230.1
SELECT USER_NAME, CREATION_DATE, START_DATE,END_DATE FROM FND_USER;
USER_NAME CREATION_DATE START_DATE END_DATE
JAGADISH 25-OCT-02 18-JUL-02 18-JUL-10
DUMMY 18-NOV-09 18-NOV-09 22-DEC-09
2. FND_TABLES;
SELECT TABLE_NAME FROM FND_TABLES;
TABLE_NAME______________
..
3. FND_RESPONSIBILITY
SELECT RESPONSIBILITY_ID, START_DATE, END_DATE, VERSION FROM FND_RESPONSIBILITY;
RESPONSIBILITY_ID START_DATE END_DATE VERSION
26546 24-MAY-04 26-JAN-05 4
24763 25-NOV-03 17-MAR-05 W
4. FND_RESPONSIBILITY_TL
SELECT RESPONSIBILITY_ID, LANGUAGE, RESPONSIBILITY_NAME, DESCRIPTION FROM FND_RESPONSIBILITY_TL
RESPONSIBILITY_ID LANGUAGE RESPONSIBILITY_NAME DESCRIPTION
24127 US Daily Procurement Intelligence Daily Purchasing Intelligence
5. FND_ORACLE_USERID
SELECT ORACLE_ID, ORACLE_USERNAME FROM ORACLE_USERID;
ORACLE_ID ORACLE_USERNAME
20006 PORTAL30
278 IZU
6. FND_APPL_TOPS
SELECT NAME, NODE_ID, SHARED, PATH FROM FND_APPL_TOPS;
NAME NODE_ID SHARED PATH
LINUX 2110 Y /U01/APPS/ONEAPPL
7. FND_PRODUCT_GROUPS
Syn: Select release_name from fnd_product_groups;
Release_name_____________
11.5.10.2
8. AD_APPLIED_PATCHES
SELECT APPLIED_PATCH_ID, PATCH_NAME, PATCH_TYPE FROM AD_APPLIED_PATCHES;
APPLIED_PATCH_ID PATCH_NAME PATCH_TYPE
404 2647958 ONE-OFF
401 5161676 PATCH-SET
402 5161676 PATCH-SET
9. FND_CONCURRENT_PROGRAMS
SELECT CONCURRENT_PROGRAM_NAME FROM FND_CONCURRENT_PROGRAMS;
CONCURRENT_PROGRAM_NAME
FNDCPCRQ
FNDCPCRS
FNDCPGLC
10. FND_CONCURRENT_PROCESSES
SELECT CONCURRENT_PROCESS_ID, CONCURRENT_QUEUE_ID, SESSION_ID, DB_NAME, LOGFILE_NAME FROM FND_CONCURRENT_PROCESSES;
CONCURRENT_PROCESS_ID CONCURRENT_QUEUE_ID SESSION_ID DB_NAME LOGFILE_NAME
2075 6290 629890 PROD /u01/apps/prodcomn/admin/log/PROD_linux/FNDSM2075.mgr
11. FND_CONCURRENT_REQUESTS
SELECT REQUEST_ID, RESPONSIBILITY_ID, REQUEST_TYPE FROM FND_CONCURRENT_REQUESTS;
REQUEST_ID RESPONSIBILITY_ID REQUEST_TYPE
237594 20420 S
237595 20420 P
12. FND_CONCURRENT_QUEUES
Select concurrent_queue_id, concurrent_queue_name from fnd_concurrent_queues;
CONCURRENT_QUEUE_ID CONCURRENT_QUEUE_NAME
4 FNDCRM
8300 JAGANMGR
13. FND_DUAL
SELECT * FROM FND_DUAL;
DUMMY
1
14. FND_DATA_GROUPS
SELECT DATA_GROUP_NAME, DESCRIPTION FROM FND_DATA_GROUPS;
DATA_GROUP_NAME DESCRIPTION
Multiple Reporting Currencies Multiple Reporting Currencies Data Group
Standard Standard Data Group
15. FND_LANGUAGES
SELECT LANGUAGE_CODE, LANGUAGE_ID, NLS_LANGUAGE, NLS_CODESET FROM FND_LANGUAGES;
LANGUAGE_CODE LANGUAGE_ID NLS_LANGUAGE NLS_CODESET
US 0 AMERICAN US7ASCII
JA 15 JAPANESE JA16EUC
RU 112 RUSSIAN CL8ISO8859P5
16. FND_MENUS
SELECT MENU_ID, MENU_NAME, TYPE FROM FND_MENUS;
MENU_ID MENU_NAME TYPE
69216 AR_CUSTOMERS_VIEW STANDARD
75492 IRC_EMP_CANDIDATE_GLOBAL GLOBAL
75745 HZ_DSS_MAIN_G SECURITY
17. FND_NODES
SELECT NODE_ID, NODE_NAME, SERVER_ADDRESS, HOST, DOMAIN FROM FND_NODES;
NODE_ID NODE_NAME SERVER_ADDRESS HOST DOMAIN
2110 LINUX 192.168.215.25 LINUX MADYS.COM
AUTHENTICATION
18. FND_PRODUCT_INSTALLATIONS
SELECT ORACLE_ID, PRODUCT_VERSION, STATUS, TABLESPACE, TEMPORARY_TABLESPACE, PATCH_LEVEL FROM FND_PRODUCT_INSTALLATIONS;
ORACLE_ID PRODUCT_VERSION STATUS TABLESPACE TEMP_ PATCH_LEVEL
808 11.5.0 N APPS_TS_TX_DATA TEMP 11I.ADI.7
19. FND_PRINTER
SELECT PRINTER_NAME, PRINTER_TYPE FROM FND_PRINTER;
PRINTER_NAME PRINTER_TYPE
NOPRINT HPLJ4SI
20. FND_SESSIONS
SELECT * FROM FND_SESSIONS;
SESSION_ID EFFECTIVE
183607 01-JAN-01
221751 01-JAN-01
21. FND_SIDS
SELECT SID FROM FND_SIDS;
SID________
PRDTST
PRD926
ONE
22. FND_TABLESPACES
SELECT TABLESPACE_TYPE, TABLESPACE FROM FND_TABLESPACES;
TABLESPACE_TYPE TABLESPACE
TRANSACTION_INDEXES APPS_TS_TX_IDX
TRANSACTION_TABLES APPS_TS_TX_DATA
23. FND_VIEWS
SELECT VIEW_ID, VIEW_NAME, DESCRIPTION FROM FND_VIEWS;
VIEW_ID VIEW_NAME DESCRIPTION
23846 PQH_RULES_V RULES VIEW
10016 PER_ABSENCE_ATTENDANCES_V EMPLOYEE PERIODS OF ABSEN
24. FND_EXECUTABLES
Syn: Select executable_name from fnd_executables;
Executable_name_______________
ABORT
ACTIVATE
DEACTIVATE
25. PRODUCT_COMPONENT_VERSION;
SELECT * FROM PRODUCT_COMPONENT_VERSION;
PRODUCT VERSION STATUS
NLSRTL 9.2.0.6.0 PRODUCTION
PL/SQL 9.2.0.6.0 PRODUCTION
26. DBA_REGISTRY
SELECT COMP_NAME, VERSION, STATUS FROM DBA_REGISTRY;
COMP_NAME VERSION STATUS
OLAP Catalog 9.2.0.6.0 VALID
Spatial 9.2.0.6.0 VALID
Oracle Data Mining 9.2.0.6.0 VALID
AD_APPL_TOPS
This table holds the various APPL-TOP’s in the Oracle Applications installation that have ever been patched.AD_APPLIED_PATCHES
AD_APPLIED_PATCHES holds information about the “distinct” Oracle Applications patches that have been applied. If 2 patches happen to have the same name but are different in content (eg. “merged” patches), then they are considered distinct and this table will therefore hold 2 records.
AD_BUGS
AD_BUGS holds information about the various Oracle Applications bugs whose fixes have been applied (ie. patched) in the Oracle Applications installation.
AD_PATCH_DRIVERS
This table holds information about the patch drivers that comprise a patch.
AD_FILE_VERSIONS
This table holds the various versions of Oracle Applications files (real files, not “pseudo-files”), that have ever been patched or executed in the Oracle Applications installation.
AD_FILES
AD_FILES is the “files repository”. It contains information about the various files that have been patched in the Oracle Applications installation.
Some entries are “pseudo-files” and not real files, (eg. directories) in which case some of the columns are not applicable and would then hold the value “DUMMY”
AD_PATCH_DRIVER_LANGS
NLS patches (or more specifically, NLS patch drivers) pertain to a language or multiple languages. This table holds that language (or multiple languages).
AD_PATCH_DRIVER_MINIPKS
This table holds information about the various Mini Packs contained in a patch (driver)
AD_PATCH_RUN_BUG_ACTIONS holds the various actions present in “applied” bug (fix). If Autopatch determined not to apply a bug (fix), then this table will not hold any records for that “unapplied” bug fix.
AD_PATCH_RUN_BUG_ACTIONS
Even though a patch may have been applied on an Oracle Applications installation, some actions in some of its included bugs (fixes) may not have got executed if the “Autopatch” utility determined that it was not necessary to execute those actions. In such cases, EXECUTED_FLAG is set to N.
AD_PATCH_RUN_BUGS
This table holds information about the bugs fixed in a specific run of Autopatch.
AD_PATCH_RUN_BUGS holds information about the various bugs fixed in a specific run of Autopatch.
Even though a patch may have been applied on an Oracle Applications installation, some bugs (fixes) contained in it may not get applied due to some reason. In such cases, the REASON_NOT_APPLIED column holds the reason.
AD_PATCH_RUNS
AD_PATCH_RUNS holds information about the various invocations of Autopatch for applying Oracle Applications patches to a specific release of an Oracle Applications installation.
If multiple drivers are run in one invocation of Autopatch, they result in multiple records in this table. These multiple records will all have the same SESSION_ID (because they arose from one Autopatch invocation), but different TASK_NUMBER’s. The TASK_NUMBER’s in this case will be numbered sequentially as 1, 2, 3, etc.
Note that when the database driver of a Maintenance Pack is applied, it bumps up the release version by creating a new record in AD_RELEASES, which is then pointed to by the UPDATED_TO_RELEASE_ID column of the old record.
AD_RELEASES
AD_RELEASES holds the various Oracle Applications releases that an installation of Oracle Applications has gone through in its entire life cycle.
It should be noted that START_DATE_ACTIVE, END_DATE_ACTIVE and BASE_RELEASE_FLAG are loosely-maintained informational columns and are not accurately maintained, and therefore should not be relied upon heavily.
AD_PATCH_COMMON_ACTIONS
This table holds distinct information about the various actions that are (often repeatedly) performed by Autopatch as part of applying patches.
Hope this helps !!
References:
Metalink ETRM DIRECT ACCESS DOCUMENT 150230.1
Important Tables in Apps
1. FND_USERSELECT USER_NAME, CREATION_DATE, START_DATE,END_DATE FROM FND_USER;
USER_NAME CREATION_DATE START_DATE END_DATE
JAGADISH 25-OCT-02 18-JUL-02 18-JUL-10
DUMMY 18-NOV-09 18-NOV-09 22-DEC-09
2. FND_TABLES;
SELECT TABLE_NAME FROM FND_TABLES;
TABLE_NAME______________
..
3. FND_RESPONSIBILITY
SELECT RESPONSIBILITY_ID, START_DATE, END_DATE, VERSION FROM FND_RESPONSIBILITY;
RESPONSIBILITY_ID START_DATE END_DATE VERSION
26546 24-MAY-04 26-JAN-05 4
24763 25-NOV-03 17-MAR-05 W
4. FND_RESPONSIBILITY_TL
SELECT RESPONSIBILITY_ID, LANGUAGE, RESPONSIBILITY_NAME, DESCRIPTION FROM FND_RESPONSIBILITY_TL
RESPONSIBILITY_ID LANGUAGE RESPONSIBILITY_NAME DESCRIPTION
24127 US Daily Procurement Intelligence Daily Purchasing Intelligence
5. FND_ORACLE_USERID
SELECT ORACLE_ID, ORACLE_USERNAME FROM ORACLE_USERID;
ORACLE_ID ORACLE_USERNAME
20006 PORTAL30
278 IZU
6. FND_APPL_TOPS
SELECT NAME, NODE_ID, SHARED, PATH FROM FND_APPL_TOPS;
NAME NODE_ID SHARED PATH
LINUX 2110 Y /U01/APPS/ONEAPPL
7. FND_PRODUCT_GROUPS
Syn: Select release_name from fnd_product_groups;
Release_name_____________
11.5.10.2
8. AD_APPLIED_PATCHES
SELECT APPLIED_PATCH_ID, PATCH_NAME, PATCH_TYPE FROM AD_APPLIED_PATCHES;
APPLIED_PATCH_ID PATCH_NAME PATCH_TYPE
404 2647958 ONE-OFF
401 5161676 PATCH-SET
402 5161676 PATCH-SET
9. FND_CONCURRENT_PROGRAMS
SELECT CONCURRENT_PROGRAM_NAME FROM FND_CONCURRENT_PROGRAMS;
CONCURRENT_PROGRAM_NAME
FNDCPCRQ
FNDCPCRS
FNDCPGLC
10. FND_CONCURRENT_PROCESSES
SELECT CONCURRENT_PROCESS_ID, CONCURRENT_QUEUE_ID, SESSION_ID, DB_NAME, LOGFILE_NAME FROM FND_CONCURRENT_PROCESSES;
CONCURRENT_PROCESS_ID CONCURRENT_QUEUE_ID SESSION_ID DB_NAME LOGFILE_NAME
2075 6290 629890 PROD /u01/apps/prodcomn/admin/log/PROD_linux/FNDSM2075.mgr
11. FND_CONCURRENT_REQUESTS
SELECT REQUEST_ID, RESPONSIBILITY_ID, REQUEST_TYPE FROM FND_CONCURRENT_REQUESTS;
REQUEST_ID RESPONSIBILITY_ID REQUEST_TYPE
237594 20420 S
237595 20420 P
12. FND_CONCURRENT_QUEUES
Select concurrent_queue_id, concurrent_queue_name from fnd_concurrent_queues;
CONCURRENT_QUEUE_ID CONCURRENT_QUEUE_NAME
4 FNDCRM
8300 JAGANMGR
13. FND_DUAL
SELECT * FROM FND_DUAL;
DUMMY
1
14. FND_DATA_GROUPS
SELECT DATA_GROUP_NAME, DESCRIPTION FROM FND_DATA_GROUPS;
DATA_GROUP_NAME DESCRIPTION
Multiple Reporting Currencies Multiple Reporting Currencies Data Group
Standard Standard Data Group
15. FND_LANGUAGES
SELECT LANGUAGE_CODE, LANGUAGE_ID, NLS_LANGUAGE, NLS_CODESET FROM FND_LANGUAGES;
LANGUAGE_CODE LANGUAGE_ID NLS_LANGUAGE NLS_CODESET
US 0 AMERICAN US7ASCII
JA 15 JAPANESE JA16EUC
RU 112 RUSSIAN CL8ISO8859P5
16. FND_MENUS
SELECT MENU_ID, MENU_NAME, TYPE FROM FND_MENUS;
MENU_ID MENU_NAME TYPE
69216 AR_CUSTOMERS_VIEW STANDARD
75492 IRC_EMP_CANDIDATE_GLOBAL GLOBAL
75745 HZ_DSS_MAIN_G SECURITY
17. FND_NODES
SELECT NODE_ID, NODE_NAME, SERVER_ADDRESS, HOST, DOMAIN FROM FND_NODES;
NODE_ID NODE_NAME SERVER_ADDRESS HOST DOMAIN
2110 LINUX 192.168.215.25 LINUX MADYS.COM
AUTHENTICATION
18. FND_PRODUCT_INSTALLATIONS
SELECT ORACLE_ID, PRODUCT_VERSION, STATUS, TABLESPACE, TEMPORARY_TABLESPACE, PATCH_LEVEL FROM FND_PRODUCT_INSTALLATIONS;
ORACLE_ID PRODUCT_VERSION STATUS TABLESPACE TEMP_ PATCH_LEVEL
808 11.5.0 N APPS_TS_TX_DATA TEMP 11I.ADI.7
19. FND_PRINTER
SELECT PRINTER_NAME, PRINTER_TYPE FROM FND_PRINTER;
PRINTER_NAME PRINTER_TYPE
NOPRINT HPLJ4SI
20. FND_SESSIONS
SELECT * FROM FND_SESSIONS;
SESSION_ID EFFECTIVE
183607 01-JAN-01
221751 01-JAN-01
21. FND_SIDS
SELECT SID FROM FND_SIDS;
SID________
PRDTST
PRD926
ONE
22. FND_TABLESPACES
SELECT TABLESPACE_TYPE, TABLESPACE FROM FND_TABLESPACES;
TABLESPACE_TYPE TABLESPACE
TRANSACTION_INDEXES APPS_TS_TX_IDX
TRANSACTION_TABLES APPS_TS_TX_DATA
23. FND_VIEWS
SELECT VIEW_ID, VIEW_NAME, DESCRIPTION FROM FND_VIEWS;
VIEW_ID VIEW_NAME DESCRIPTION
23846 PQH_RULES_V RULES VIEW
10016 PER_ABSENCE_ATTENDANCES_V EMPLOYEE PERIODS OF ABSEN
24. FND_EXECUTABLES
Syn: Select executable_name from fnd_executables;
Executable_name_______________
ABORT
ACTIVATE
DEACTIVATE
25. PRODUCT_COMPONENT_VERSION;
SELECT * FROM PRODUCT_COMPONENT_VERSION;
PRODUCT VERSION STATUS
NLSRTL 9.2.0.6.0 PRODUCTION
PL/SQL 9.2.0.6.0 PRODUCTION
26. DBA_REGISTRY
SELECT COMP_NAME, VERSION, STATUS FROM DBA_REGISTRY;
COMP_NAME VERSION STATUS
OLAP Catalog 9.2.0.6.0 VALID
Spatial 9.2.0.6.0 VALID
Oracle Data Mining 9.2.0.6.0 VALID
No comments:
Post a Comment