Problems Administering Deployments

The following solutions apply to problems with administering database deployments on Oracle Database Cloud Service.

I am required to change the password for the oracle user when I try to connect to a compute node

You cannot change the password as required because the oracle user does not have a password. Instead, change the properties of the oracle user so that its password does not expire:

  1. Connect to the compute node as the opc user.

    For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH).

  2. Start a root-user command shell:

    $ sudo -s
    #
  3. Change the expiration properties of the oracle user by using the chage command:

    # /usr/bin/chage -I -1 -m 0 -M 99999 -E -1 oracle
  4. Confirm that the expiration properties have been changed by using the chage command again:

    # /usr/bin/chage -l oracle
    Last password change                              : date
    Password expires                                  : never
    Password inactive                                 : never
    Account expires                                   : never
    Minimum number of days between password change    : 0
    Maximum number of days between password change    : 99999
    Number of days of warning before password expires : 7
  5. Close your connection to the compute node.

I get a Linux error 30, Read-only file system, when trying to connect to or work in my environment

In certain rare cases, Oracle Compute Cloud Service sets the access of storage volumes attached to a Database Cloud Service deployment to read-only. When this situation arises, you can restore read-write access by restarting the compute node, as described in Rebooting a Compute Node.

I can’t use dbaascli to update my cloud tooling

Normally, you use the dbaascli utility to update the cloud tooling on Database Cloud Service database deployments hosting a single-instance database or Oracle Data Guard configuration, as described in Updating the Cloud Tooling by Using the dbaascli Utility. However, older deployments don’t support the two dbaascli subcommands you use:

dbaascli patch tools list
dbaascli patch tools apply

Nor do older deployments support the following two deprecated dbaascli subcommands:

dbaascli dbpatchm --run -list_tools
dbaascli dbpatchm --run -toolsinst 

If you get an error when you run the first of either of these pairs of commands, you must use the following method to update the cloud tooling. After using this method one time, you will be able to use the dbaascli utility the next time you want to update the cloud tooling.

  1. Connect as the opc user to the compute node.

    See Connecting to a Compute Node Through Secure Shell (SSH).

  2. Start a root-user command shell:

    $ sudo -s
    #
  3. Navigate to the /tmp directory:

    # cd /tmp
  4. Download the RPM file containing the latest version of the cloud tooling:

    # wget https://storage.us2.oraclecloud.com/v1/dbcsswlibp-usoracle29538/dbaas_patch/dbaastools.rpm
  5. Get information about the cloud tooling in the downloaded RPM file:

    # rpm -qpi ./dbaastools.rpm
    Name        : dbaastools                   Relocations: (not relocatable)
    Version     : version_number                    Vendor: Oracle
    Release     : release_number                Build Date: ...
    ...
  6. Get information about the installed cloud tooling:

    # rpm -qa|grep -i dbaastools
    dbaastools-version_number-release_number
  7. Compare the version and release values of the downloaded cloud tooling and the installed cloud tooling. If the downloaded tooling is newer than the installed tooling, remove the installed tooling and then install the downloaded tooling:

    1. Remove the installed cloud tooling:

      # rpm -ev installed-info

      where installed-info is the information you noted down about the installed cloud tooling; that is, the output from the rpm -qa|grep -i dbaastools command you entered earlier.

    2. Install the cloud tooling in the downloaded RPM file:

      # rpm -ivh ./dbaastools.rpm
  8. Reset the backup configuration:

    # /var/opt/oracle/ocde/assistants/bkup/bkup
  9. Exit the root-user command shell and disconnect from the compute node:

    # exit
    $ exit