psm jcs precheck-patch
Use this command before actually patching the Oracle Java Cloud Service instance to identify potential issues that might prevent the specified patch from completing successfully.
-
Disk space shortage.
-
Database connectivity failure.
-
Server access failure.
-
Storage access failure
Syntax
In the following syntax, line breaks have been added for clarity. Do not include them when entering the command.
psm jcs precheck-patch -s|--service-name serviceName
-p|--patch-id patchId
[-of|-–output-format json|html|short]
[-wc|--wait-until-complete true|false]
Parameters
All parameters are required unless otherwise noted.
Parameter | Description |
---|---|
-s|--service-name serviceName |
Name of the Oracle Java Cloud Service instance. |
-p|--patch-id patchId |
Patch Id for the patch that requires to have a precheck done. |
-of|-–output-format json|html|short |
(Optional) Output format of the command’s response:
Accepted values: The default output format is the one you specified when using the |
|
(Optional) A boolean value that, when set to
true , makes the command behave synchronously; that is, it does not return until the submitted job is complete. The following message is displayed until the job is complete: Default: false |
Example
$ psm jcs precheck-patch -s Example1Instance -p Test_Patch_12.2.1.0.160119 -of json
{
"details":{
"jobId":"34177",
"message":"JCS-PATCHING-5227: Pre-Checking service for patch [Test_Patch_12.2.1.0.160119] is submitted as an asynchronous job."
},
"status":"Completed"
}
Job ID : 34177
Note that this command returned a job ID. To see the status of your precheck-patch
operation, use this ID with the psm jcs operation-status command:
$ psm jcs operation-status -j 34177 -of json
When you see the message:
"operationId":364,
"operationType":"PRECHECK",
"serviceId":364,
"serviceName":"Example1Instance",
"serviceType":"jaas",
"startDate":"2016-04-28T17:31:32.494+0000",
"status":"SUCCEED",
"summaryMessage":"PRECHECK"
the patch precheck is complete.