Automate MOS Patch Downloads using WGET

-


Recently, I was searching for a way to completely automate the process of MOS patch downloads when I stumbled upon this blog post - a very well written blog explaining the intricacies of automating patch download from MOS using CURL.

This set me thinking if it could be done using WGET command instead of CURL and I found out that it can, indeed, be done.

Though the blog post that I have referenced offers a completely automated solution, it uses CURL command beacuse CURL comes installed, by default, with most of the Linux based Docker images, while wget doesn't.

Most of the other blog posts that describe patch download using wget, rely on manual authentication with MOS or manually fetching the download URL from MOS. However, I present to you a completely automated way of My Oracle Support Patch Downloads using wget.

NOTE: I have assumed the OS to be Linux x86-64 bit and accordingly, hard-coded the platform ID as 226P (plat_lang=226P). I plan to publish another blog post detailing the process to fetch all the available platforms and languages shortly.

Briefly, the steps involved in this process are:

1. Login to MOS and save a cookie file
2. Search for the patch number and fetch the patch download URL from the output
3. Download the patch using the patch download URL

Login to MOS and save a cookie file

I have used the below as inputs/references:

a. steps for creating/saving the cookie file, provided in the wget.sh script for downloading any patch in MOS.

b. usage of the WGETRC file with the wget command for storing credentials

There are 3 sub-steps here:

  1. Create the WGETRC file - by prompting the user and accepting user input for username and password to login to MOS
  2. Set the variables (including WGETRC)
  3. Login to MOS and save the cookie file

Fetch the patch download URL from MOS

Below are the sub-steps for doing this:

a. Search for the patch in MOS using the cookie file (saved in the previous step) and save the output in a file

b. Glean the patch download URL from the saved output


Download the patch from MOS and ensure that it is safe

The sub-steps in this phase are:

a. Download the patch using the download URL gleaned from the above step.

b. Also download the patch XML in order to glean the SHA256 checksum of the source patch

c. Find the sha256 checksum of the download patch zip and compare it with the one from the patch XML. Ensure that both match else, delete the patch zip file.


Download the basic script from git.

Bonus: Download the enhanced script that uses:

1. options (-p or --patch) to specify the patch number

2. Functions to perform validations

3.  a different way of checking whether the given argument (i.e., patch number) is indeed a numeral.


Comments

Post a Comment

Popular posts from this blog

Solution to "End Program - WMS Idle"

-
Image
Though this topic is unrelated any Apps DBA topics, I found it necessary to share the solution so that everyone benifits out of it ! Issue: I used to receive the below error message whenever I tried to shutdown windows XP. A rather vexing problem, no doubt. Cause: This message appears because when windows is trying to shutdown and end all the running processes, the WMS idle process keeps working. Thus an end-program message appears. The two most common reasons for this are: Scout service run by Nero 7 Microsoft Office Communicator 2005 Solution: The fix is simple, disable the Nero 7 scout service if it is enabled. For this, go to Start > All Programs > Nero > Tools > Nero Scout . On this screen , Uncheck Enable the Nero scout. This will fix the issue for most of the users, for the rest of you who are not using Nero are most probably getting this error because of Microsoft Office Communicator 2005. For that you need to either manually exit the communicator 2005 from the s
Read more

Modify retention period of workflow queues

-
Yesterday, there was a requirement to increase the retention period of WF_DEFERRED and WF_BPEL_Q so that the developers could troubleshoot issues involving business events. This can be done this way: 1. Check the retention period of existing workqueues. SQL> SELECT owner, name, retention FROM all_queues WHERE name LIKE 'WF%'; OWNER           NAME                                                RETENTION --------------- --------------------------------------------- ------------------------------ APPS                 WF_BPEL_Q                                                0 APPLSYS         WF_INBOUND_QUEUE                             0 APPLSYS         WF_OUTBOUND_QUEUE                          0 APPLSYS         WF_SMTP_O_1_QUEUE                           0 APPLSYS         WF_DEFERRED_QUEUE_M                        0 APPLSYS         WF_DEFERRED                                            0 APPLSYS         WF_ERROR                                           0 AP
Read more

Check if UTL_FILE and FND_FILE are working fine

-
Yesterday, while troubleshooting a vexing ORA-29280 error, I came across 2 useful PL/SQL anonymous blocks that can be used to test FND_FILE and UTL_FILE to find out whether they are indeed working fine. UTL_FILE set serveroutput on DECLARE file_location VARCHAR2(256) := '<first entry on utl_file_dir>'; file_name VARCHAR2(256) := 'utlfile1.lst'; file_text VARCHAR2(256) := 'THIS IS A TEST'; file_id UTL_FILE.file_type; BEGIN file_id := UTL_FILE.fopen(file_Location, file_name, 'W'); UTL_FILE.put_line(file_id, file_text); UTL_FILE.fclose(file_id); EXCEPTION WHEN UTL_FILE.INVALID_PATH THEN dbms_output.put_line('Invalid path ' || SQLERRM); WHEN OTHERS THEN dbms_output.put_line('Others '|| SQLCODE || ' ' || SQLERRM); END; / References: Metalink (MOS) Note ID: 261693.1 FND_FILE set serveroutput on exec FND_FILE.PUT_LINE(FND_FILE.LOG, 'THIS IS A TEST'); HTH.
Read more