psm analytics precheck-patch

Use this command before patching a service created with Oracle Analytics Cloud - Classic so you can identify potential issues that might prevent the specified patch from completing successfully.

Patching precheck reports on the following conditions:

Disk space shortage.
Database connectivity failure.
Server access failure.
Storage access failure.

Prechecks don’t check whether another administration task (backup, restoration, or scaling) is in progress, although these also prevent patching.

Syntax

In the following syntax, line breaks have been added for clarity. Don’t include them when entering the command.

psm analytics precheck-patch -s|--service-name serviceName 
  -p|--patch-id patchId 
    [-of|--output-format json|html|short]

Parameters

All parameters are required unless otherwise noted.

Parameter	Description
`-s\|--service-name`	Specifies the name of the service.
`-p\|--patch-id`	Patch ID for the patch that requires to have a precheck done.
`-of\|-–output-format`	(Optional) Desired output format. Accepted values: `json, html, short`

Example

$ psm analytics precheck-patch -s Example1Service -p Test_Patch_12.2.1.0.160119 
{
    "details":{
        "jobId":"34177",
        "message":"Analytics-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 analytics operation-status command:

$ psm analytics operation-status -j 34177

When you see the message:

  "operationId":364,
  "operationType":"PRECHECK",
  "serviceId":364,
  "serviceName":"Example1Service",
  "serviceType":"analytics",
  "startDate":"2016-04-28T17:31:32.494+0000",
  "status":"SUCCEED",
  "summaryMessage":"PRECHECK"

the patch precheck is complete.