R12 d49656 gc10-apps dba 25

Editor's Notes

• #2: ILT Schedule: Timing Topic 30 minutes Lecture 30 minutes Practice 60 minutes Total
• #3: <Course name> <Lesson number> -
• #4: <Course name> <Lesson number> -
• #5: <Course name> <Lesson number> -
• #6: <Course name> <Lesson number> - Applied Patches Information AutoPatch stores patch information in the database automatically each time it successfully applies a patch. However, if the patch is not applied successfully, or when you run AutoPatch in pre-install mode, patch history is not written directly to the database, but instead is written to these patch information files : For Release 12, there are two patch history files: Javaupdates<timestamp>.txt: contains information on changes to Java files Adpsv<timestamp>.txt: contains information on changes to all other files These files exist only if a patch session did not write applied patch information to the database. Both files are located in the APPL_TOP/admin/<SID> directory.
• #7: <Course name> <Lesson number> -
• #8: <Course name> <Lesson number> -
• #9: <Course name> <Lesson number> -
• #10: <Course name> <Lesson number> -
• #11: <Course name> <Lesson number> -
• #12: <Course name> <Lesson number> - Normal Mode The AutoPatch log file records whether the upload of applied patch information from the patch history files to the applied patch information database was successful.
• #13: <Course name> <Lesson number> -
• #14: <Course name> <Lesson number> -
• #15: <Course name> <Lesson number> - Accessing Applied Patches Information You can access the Applied Patches Information by selecting Applied Patches from the Oracle Applications Manager Dashboard.
• #16: <Course name> <Lesson number> - Applied Patches Search Pages The Aplied Patches Simple Search page allows you to search for applied patch using just a few search criteria. The Advanced Search page provides more search criteria options.
• #17: <Course name> <Lesson number> - Applied Patches Simple Search When you choose Search Patches from the Oracle Applications Manager Site Map, it defaults to the Applied Patches Simple Search page. From this Applied Patches “home page” you can: Search for patches that have been applied by entering search criteria in one or more fields and clicking the Go button. Click the Advanced Search button to access the Applied Patches Advanced Search page. Go to other OAM functionality by selecting it from the Select Feature drop-down menu. There are three fields in the Applied Patches Simple Search page: Patch ID: Enter the patch number in this field. Applied from Date <begin date> To Date <end date>: This field allows you to search for patches that were applied during a specified period of time. Click the calendar icon to select the date or enter the date directly in the field. The format for this field is shown under the field. Some examples for the use of this field are: Enter only the begin date. This search returns all patches applied from the begin date through today's date. Enter only the end date. This search returns all patches applied up to the end date. Enter the begin date and the end date. This search returns all patches applied between the begin date and the end date. Language: This drop down menu allows you to select the language of a patch to be queried. You can select only one language in this field. To select multiple languages, go to the Applied Patches Advanced Search page. You must enter a value in at least one of the three fields, otherwise, an error page appears requesting you to go back and enter a value. To submit the query, click the Go button. Click the Reset button to clear all search fields. The results section at the bottom of the page displays the results of a query submitted through the search section. If the results section contains multiple pages of retrieved information, use the Previous and Next links or the drop down list to navigate from page to page. The retrieved applied patch information is presented in increments of 25 line items per page. Each line item represents an applied patch. The details provided for each patch are: Patch Name: This is the name of the patch. Merged Patches: If this a merge patch, it would be yes with a link and the link will take you to Merge Patches page where all the patches that were merged would be displayed. APPL_TOP Name: This is the name of the APPL_TOP where the patches were applied. Language: Indicates the language of the patch. Completion Date: This is the date and time the patch was applied and completed. Details: Clicking this link accesses the Patch Details report. Clicking on the heading for a column allows you to sort the patch summary information based on the content in that column. The sortable columns have column headings with dark borders and when the mouse cursor is placed over the column heading the pointer will change to a hand. The sort alternates between ascending and descending each time you click the column heading.
• #18: <Course name> <Lesson number> - Applied Patches Advanced Search Clicking the Advanced Search button in the Applied Patches Simple Search page accesses the Applied Patches Advanced Search page. The Advanced Search page provides greater granularity of query criteria than the Simple Search page. There are five additional search criteria to narrow the results of a query. The option buttons at the top of this page are identical to those of the Simple Search page. From this page you can: Search for patches that have been applied by entering search criteria in one or more fields and clicking the Go button. Click the Simple Search button to access the Applied Patches Simple Search page. Access applied patch information migrated from another Oracle Applications system. These are the available search options: Applications System Name (required): Defaults to the name of your Oracle Applications system. If you have migrated applied patch information from another system, and want to search those records, enter the name of that system. APPL_TOP: This is the name of the APPL_TOP where the patches were applied. Server Type: Select the type of server where the patches were applied. The options are All APPL_TOP Server Types or one or more of the following Specific Server Types: Form, Concurrent, Web, and Administration. You can select one server or multiple servers. To select multiple servers, select the appropriate boxes. Product: Enter the product short name of the product that owns the patch in this field. For example, ad or fnd. This field is not case sensitive. Patch ID: Enter the patch number in this field. Applied From Date <begin date> To Date <end date>: This field allows you to search for patches that were applied during a specified period of time. Click the calendar icon to select the date or enter the date directly in the field. The format for this field is mm/dd/yy. Language: This list box allows you to select the language of a patch to be queried. You can select one language or multiple languages by selecting a language in the Available Languages box and clicking the Move button. You must enter a value in at least one of these fields, otherwise, an error page appears requesting you to go back and enter a value. To submit the query, click the Go button. Click the Reset button to clear all search fields. Instructor Note: Some situations that may require the migrating of applied patch information from one system to another are: Cloning Using a Staged APPL_TOP
• #19: <Course name> <Lesson number> - File History Search Pages The File History Simple Search page allows you to search for file history information for files that have been updated by a patch. The File History Advanced Search page provides additional search criteria options.
• #20: <Course name> <Lesson number> - File History Simple Search The Simple Files Search page can be accessed in three ways: Choose File History from the Maintenance tab of the OAM Site Map. Select the File History from the Select Features drop-down menu. Click the Simple Search button from the File History Advanced Search page. From this page you can: Search for files that have been updated by a patch by entering search criteria in one or more fields and clicking the Go button. Click the Advanced Search button to access the File History Advanced Search page. There are three fields in the File History Simple Search page: File name: Enter the name of a file in this field. Do not include a directory path. This field is required and is case-sensitive. You can use the % wildcard symbol in combination with literal characters. Changed From Date <begin date> To Date <end date>: This field allows you to search for files that were updated during a specified period of time. Language: This drop down menu allows you to select the language of a file to be queried. You can select only one language in this field. To select multiple languages, go to the Advanced Search page. You must enter a value in the File Name field, otherwise, a window appears requesting you to go back and enter a value. To submit the query, click the Go button. Click the Reset button to clear all search fields. The results section displays the results of a query submitted through the search section. If the results section contains multiple pages of retrieved information, use the Previous and Next links or the drop down list to navigate from page to page. The retrieved information is presented in increments of 25 line items per page. Each line item represents the changing of a file due to its inclusion in a patch. The details provided for a file are: APPL_TOP Name: This is the name of the APPL_TOP containing the files. Product: This is the product abbreviation for the product that owns the file. Directory: This is the directory path where the file is located. File: This is the name of the file. Version: This is the version number of the file. Changed Date: This is the date this version of the file was updated by a patch. Patch Details: Click on the patch number to see the Patch Details report for the patch the file was included in. Action Summary: Click on the icon to see the Action Summary report for the action that updated the file. If a file has never been patched, "The above criteria resulted in no rows" appears in the APPL_TOP Name column.
• #21: <Course name> <Lesson number> - File History Advanced Search Clicking the Advanced Search button in the File History Simple Search page opens the File History Advanced Search page. There are four search criteria, in addition to the three found on the Simple Search page, to narrow the results of a query. From this page you can: Search for version history of files that have been updated by a patch by entering search criteria in one or more fields and clicking the Go button. Click the Simple Search button to access the File History Simple Search page. Access file history information migrated from another Oracle Applications system. These are the available search options: Applications System Name (required): Defaults to the name of your Oracle Applications system. If you have migrated file history information from another system, and want to search those records, enter the name of that system. APPL_TOP name: This is the name of the APPL_TOP containing the files. File name (required): Enter the name of a file in this field. Do not include a directory path. This field is required and is case-sensitive. Latest Version Only: The options are Yes or No. Yes returns information for only the latest version of the file. No returns information for all versions of the selected file. Changed From Date <begin date> To Date <end date>: This field allows you to search for file history information spanning a specified period of time. Language: This list box allows you to select the language of a patch to be queried. You can select one language or multiple languages by selecting a language in the Available Languages box and clicking the Move button. You must enter a value in the File Name field, otherwise, an error page appears requesting you to go back and enter a value. To submit the query, click the Go button. Click the Reset button to clear all search fields.
• #22: <Course name> <Lesson number> - Applied Patches Reports Most of these reports have a standard layout. The top portion of the report displays the search criteria and the bottom portion displays the results of the search. A navigation path appears at the top of each report and each item in the navigation path is a link. Clicking on the link accesses the respective search page or report. Click the heading of a column to sort the information based on the content in that column. The sortable columns have column headings that appear 3-dimensional. The sort alternates between ascending and descending each time you click the column heading. When the reports contain multiple pages of retrieved information, use the Previous and Next links or the drop down list to navigate from page to page. The report information is presented in increments of 25 line items per page.
• #23: <Course name> <Lesson number> - Patch Details Report Clicking the Details link in a selected row from the results section of one of the Applied Patches search pages opens the Patch Details report. The Patch Details report provides details for a specific patch. The patch summary information is carried over from the Results section of the Applied Patches Search page and appears at the top of the Patch Details report. This report contains the following information for a specific patch: Select: This option button determines which driver file details are presented in the Timing Details report, Files Copied report, the Bug Fixes report, or the Action Summary report. Driver File: This is the name of the driver file. Start Date: This is the date and time the application of the driver file began. End Date: This is the date and time the application of the driver file completed. AutoPatch Options: This column displays any command line options used to run the driver file. Platform: This is the platform of the driver file. Patch Top: This is the location of the driver when it was run. Codelevel Introduced: This link will be enabled if the patch introduces new codelevels and the link will take you to Codelevel Introduced page. To see additional details for a patch click on one of the following buttons: Timing Details: Clicking this button takes you to the AutoPatch Timing Details report for the particular patch session. Files Copied: Clicking this button takes you to the Files Copied report. Bug Fixes: Clicking this button takes you to the Bug Fixes report. Action Summary: Clicking this button takes you to the Action Summary report.
• #24: <Course name> <Lesson number> - Files Copied Report Select a driver file in the Patch Details report and click the Files Copied button to access the Files Copied report. This report lists all files copied to the file system as a result of the actions in the selected driver file. This report provides the following information about the files copied: Product: This is the product short name for the product that owns the file. Directory: This is the directory path where the file was copied. File: This is the name of the file. Version: This is the version number of the copied file. If there are no files copied in the patch, no rows are displayed. If the number of files copied exceeds 200, the report lists only the first 200 files. Use the filter to reduce the number of files in the report.
• #25: <Course name> <Lesson number> - Bug Fixes Report Select a driver file in the Patch Details report and click the Bug Fixes button to access the Bug Fixes report. This report lists all bug fixes included in the selected driver file. Each line item represents a bug fix. This report provides the following information about bug fixes: Bug Fix: This is the bug number of the bug fixed as a result of the selected driver file. The first item in this column is usually a link clicking on it accesses the Action Summary report. Product: This is the product abbreviation for the product whose bug was fixed. Applied: This represents whether the bug fix was applied. Reason Not Applied: If the bug fix was not applied, the reason is stated here. If there are no bug fixes in the patch, no rows are displayed. If the number of files copied exceeds 200, the report lists only the first 200 bug fixes. Use the filter to reduce the number of bug fixes in the report.
• #26: <Course name> <Lesson number> - Action Summary Report The Action Summary report is accessed by one of two methods: By selecting a driver file in the Patch Details report and clicking the Action Summary button. By clicking a bug fix number in the Bug Fix column of the Bug Fixes report. This report provides summary information for the actions of a selected driver file. Each line item represents a performed action. The Action Summary report provides the following summary information: Product: This is the product short name for the product that owns the file referenced by the action. Directory: This is the directory path for the file referenced by the action. File: This is the name of the file referenced by the action. Before Version : This is the version of the file before the update. After Version: This is the version of the file after the update Action: This is the type of action performed on the updated file. Phase: This is the phase in which the action occurred. Run: This signifies whether the action was executed. Bug Fix : This is the bug number of the bug fixed as a result of the selected driver file. Details: This link is active if AutoPatch performed database actions. Click this link to access the Action Details report. You can sort each of these columns by clicking the column title at the top of the report. If the number of actions exceeds 200, the report lists only the first 200. Use the filter to reduce the number of items in the report.
• #27: <Course name> <Lesson number> - Action Details Report The Action Detail report is accessed by clicking the details link in a selected row of the Action Summary report. The Action Summary information is carried over and presented at the top of the report. The action detail provided are: Arguments : This is the specific arguments for SQL and EXEC commands. Command Modifier : This is the SQL or EXEC command modifier in the database driver. Check Object : This is the name of the database object to check for, along with name and password of the schema where AutoPatch looks for the check object. (This is "none none none" for most SQL commands and is not specified for EXEC commands.) Elapsed Time : This is the time required to complete the action. Start Time : This is the date and time the action began. Restart Time : This is the date and time the action was restarted. End Time : This is the date and time the action completed. Restarted?: States whether the action was restarted. N/A in the report represents action details that are not specified. For example, in the Arguments field, N/A means no additional arguments were specified.
• #28: <Course name> <Lesson number> -
• #29: <Course name> <Lesson number> -
• #30: <Course name> <Lesson number> - Refer to Practice - Searching for Applied Patch Information [ LAB421DY ]