eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

DBA Data [Home] [Help] [Dependency Information]

TABLE: APPLSYS.AD_PATCH_RUNS

Object Details

Object Name:	AD_PATCH_RUNS
Object Type:	TABLE
Owner:	APPLSYS
FND Design Data:	AD.AD_PATCH_RUNS
Subobject Name:
Status:	VALID

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.

Storage Details

Tablespace:	APPS_TS_TX_DATA
PCT Free:	10
PCT Used:

Indexes

Index	Type	Uniqueness	Tablespace	Column
AD_PATCH_RUNS_U1	NORMAL	UNIQUE	APPS_TS_TX_IDX	PATCH_RUN_ID
AD_PATCH_RUNS_U2	NORMAL	UNIQUE	APPS_TS_TX_IDX	START_DATE APPL_TOP_ID PATCH_DRIVER_ID
AD_PATCH_RUNS_N1	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	END_DATE
AD_PATCH_RUNS_N2	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	PATCH_DRIVER_ID
AD_PATCH_RUNS_N3	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	UPDATED_TO_RELEASE_ID

Columns

Name	Datatype	Length	Mandatory	Comments
PATCH_RUN_ID	NUMBER		Yes	PK
RELEASE_ID	NUMBER		Yes	Identifies the Oracle Applications Release on which this patch was applied
SESSION_ID	NUMBER		Yes	Identifies the Autopatch session. See table description for details
RAPID_INSTALL_FLAG	VARCHAR2	(1)		Y implies that this record was created at Oracle Corporation when building a Rapid Install database
UPDATED_TO_RELEASE_ID	NUMBER			See table description
PATCH_TOP	VARCHAR2	(250)	Yes	Directory where patch was unloaded
START_DATE	DATE		Yes	Date and time when Autopatch started applying the patch
END_DATE	DATE			Date and time when Autopatch completed applying the patch
PATCH_DRIVER_ID	NUMBER		Yes	Identifies the patch driver that was run in this invocation of Autopatch
PATCH_ACTION_OPTIONS	VARCHAR2	(250)		Arguments of the "options" keyword when Autopatch was invoked
APPS_SYSTEM_NAME	VARCHAR2	(8)		Obsoleted
APPL_TOP_ID	NUMBER		Yes	Identifies the APPL_TOP on which the patch was applied
SERVER_TYPE_ADMIN_FLAG	VARCHAR2	(1)		Y => The APPL-TOP implemented the "Admin" server when this patch was applied
SERVER_TYPE_FORMS_FLAG	VARCHAR2	(1)		Y => The APPL-TOP implements the "Forms" server when this patch was applied
SERVER_TYPE_NODE_FLAG	VARCHAR2	(1)		Y => The APPL-TOP implements the "Concurrent Processing" server when this patch was applied
SERVER_TYPE_WEB_FLAG	VARCHAR2	(1)		Y => The APPL-TOP implements the "Web" server when this patch was applied
SOURCE_CODE	VARCHAR2	(3)	Yes	Indicates whether uploaded from applptch.txt (TXT) or whether created as a result of applying a patch driver (DRV)
CREATION_DATE	DATE		Yes	Standard who column - date when this row was created.
SUCCESS_FLAG	VARCHAR2	(1)	Yes	Y => the patch was successful
FAILURE_COMMENTS	VARCHAR2	(255)		User entered comments when flagging a patch as unsuccessful
CREATED_BY	NUMBER		Yes	Standard who column - user who created this row (foreign key to FND_USER.USER_ID).
LAST_UPDATE_DATE	DATE		Yes	Standard Who column - date when a user last updated this row.
LAST_UPDATED_BY	NUMBER		Yes	Standard who column - user who last updated this row (foreign key to FND_USER.USER_ID).
IMPORTED_FLAG	VARCHAR2	(1)		Y=>Imported from another database using patch-history export-import feature
IMPORTED_FROM_DB	VARCHAR2	(30)		ORACLE_SID of the (source) database from which this row is imported
IMPORTED_ID	NUMBER			PATCH_RUN_ID of the source row in the source database
IMPORT_SESSION_ID	NUMBER			Identifies the import session that was responsible for importing this row, if this is an imported row (which is also embedded in the import utility's log file name)
TASK_NUMBER	NUMBER			Task number. See table description for details
PROGRAM_RUN_ID	NUMBER			This column relates the information in this table to that present in AD_PROGRAM_RUN_TASKS, AD_PATCH_RUN_SESS_ATTRIBS & AD_PROGRAM_RUN_TASK_JOBS

Query Text

Cut, paste (and edit) the following text to query this object:


SELECT PATCH_RUN_ID
,      RELEASE_ID
,      SESSION_ID
,      RAPID_INSTALL_FLAG
,      UPDATED_TO_RELEASE_ID
,      PATCH_TOP
,      START_DATE
,      END_DATE
,      PATCH_DRIVER_ID
,      PATCH_ACTION_OPTIONS
,      APPS_SYSTEM_NAME
,      APPL_TOP_ID
,      SERVER_TYPE_ADMIN_FLAG
,      SERVER_TYPE_FORMS_FLAG
,      SERVER_TYPE_NODE_FLAG
,      SERVER_TYPE_WEB_FLAG
,      SOURCE_CODE
,      CREATION_DATE
,      SUCCESS_FLAG
,      FAILURE_COMMENTS
,      CREATED_BY
,      LAST_UPDATE_DATE
,      LAST_UPDATED_BY
,      IMPORTED_FLAG
,      IMPORTED_FROM_DB
,      IMPORTED_ID
,      IMPORT_SESSION_ID
,      TASK_NUMBER
,      PROGRAM_RUN_ID
FROM APPLSYS.AD_PATCH_RUNS;

Dependencies

[top of page]

APPLSYS.AD_PATCH_RUNS does not reference any database object

APPLSYS.AD_PATCH_RUNS is referenced by following:

APPLSYS: AD_PATCH_RUNS#