psm dbcs scale-up

Syntax

In the following syntax, line breaks have been added for clarity. Do not include them when entering the command.

psm dbcs scale-up -s|--service-name instance-name
  {
    -p|--shape shape-name |
    -a|--additional-storage size-in-gb [-u|--usage data|fra]
  }
  [-of|--output-format json|html|short]

Description

When you use this command, you can specify only one scaling operation:

Use the -p or --shape parameter to scale up the shape (OCPUs and memory) of the service instance.
Use the -a or --additional-storage parameter to scale up the storage of the service instance.

When you scale up storage, you can optionally specify the -u or --usage parameter to have the storage added to the database’s data storage or to the database’s fra (fast recovery area) storage. If you do not use these parameters, a new storage volume is created and added to the service instance.

Parameters

Parameter	Description
`-s\|--service-name instance-name`	Specifies the name of the Database Classic Cloud Service instance you want to scale up.
`-p\|--shape shape-name`	Specifies scaling up the shape of the service instance. Valid values for `shape-name` are as follows: `oc4` — 2 OCPUs with 15 GB RAM `oc5` — 4 OCPUs with 30 GB RAM `oc6` — 8 OCPUs with 60 GB RAM `oc7` — 16 OCPUs with 120 GB RAM `oc1m` — 1 OCPU with 15 GB RAM `oc2m` — 2 OCPUs with 30 GB RAM `oc3m` — 4 OCPUs with 60 GB RAM `oc4m` — 8 OCPUs with 120 GB RAM `oc5m` — 16 OCPUs with 240 GB RAM
`-a\|--additional-storage size-in-gb`	Specifies scaling up the storage of the service instance. `size-in-gb` is a number from 1 to 2000 specifying the amount of storage you want add in gigabytes.
`-u\|--usage data\|fra`	(Optional; permitted only when scaling up storage) Specifies how the additional storage is to be used: `data` specifies that the additional storage is to be allocated to the database’s data storage. `fra` specifies that the additional storage is to be allocated to the database’s fra (fast recovery area) storage.
`-of\|--output-format json\|html\|short`	(Optional) Specifies the output format of the command’s response: `json`—output is formatted as a JSON array. `html`—output is formatted as HTML `short`—output is formatted as a brief summary. The default output format is the one you specified when using the `psm setup` command to configure the `psm` CLI.

Examples

The following example scales up the db12c-eeep Database Classic Cloud Service instance to the oc4 shape.

$ psm dbcs scale-up --service-name db12c-eeep --shape oc4
"Accepted"
Job ID : 553960

Here is the information about job 553960 upon successful completion of the operation:

$ psm dbcs operation-status --job-id 553960
{
    "activityLogId":241348,
    "authDomain":"usexample",
    "authUser":"dbaasadmin",
    "endDate":"2016-05-03T03:51:20.650+0000",
    "identityDomain":"usexample",
    "initiatedBy":"USER",
    "jobId":553960,
    "messages":[
        {
            "activityDate":"2016-05-03T03:44:34.137+0000",
            "message":"Activity Submitted"
        },
        {
            "activityDate":"2016-05-03T03:44:36.353+0000",
            "message":"Activity Started"
        },
        {
            "activityDate":"2016-05-03T03:46:54.102+0000",
            "message":"Update of Database Service VM successful..."
        },
        {
            "activityDate":"2016-05-03T03:51:07.900+0000",
            "message":"Started Virtual Machine vm-1..."
        },
        {
            "activityDate":"2016-05-03T03:51:08.348+0000",
            "message":"SSH access to VM [DB_1/vm-1] succeeded..."
        },
        {
            "activityDate":"2016-05-03T03:51:20.650+0000",
            "message":"Activity Ended"
        }
    ],
    "operationId":22847,
    "operationType":"SCALE_UP",
    "serviceId":22847,
    "serviceName":"db12c-eeep",
    "serviceType":"dbaas",
    "startDate":"2016-05-03T03:44:34.137+0000",
    "status":"SUCCEED",
    "summaryMessage":"SCALE_UP"
}