Nothing Special   »   [go: up one dir, main page]
Scribd Logo
Upload

Welcome to Scribd!

  • 3 views

    Patchdbsystem

    Uploaded by

    Lokesh kumar
    Db system patching

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd

    Patchdbsystem

    Uploaded by

    Lokesh kumar
    3 views10 pages
    Db system patching

    Original Title

    patchdbsystem

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Db system patching

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    3 views10 pages

    Patchdbsystem

    Uploaded by

    Lokesh kumar
    Db system patching

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    of 10

    Applying Patch in a DB System – Oracle Cloud

    On this post, I will show you how to apply the Patch in a Database System. When you create a DB System inside Oracle Cloud you have already
    the CRS, ASM and Database installed. It’s different of the just a database creation on Cloud as I posted before.
    Also on this post we will have a look in how to use the DBCLI command line tool. For the ones that are used with Oracle Database Appliance
    (ODA) is the same concept used for OAKCLI.

    The current DB Systems:

    On this post I will upgrade the DB System “DBSYS02”.

    The documents followed:


    https://docs.cloud.oracle.com/iaas/Content/Database/Tasks/patchingDB.htm#dbcli
    https://docs.cloud.oracle.com/iaas/Content/Database/References/dbacli.htm#updatedbhome

    1.) Click on the DB System:

    As you can see, my DBSystem has 1 Node, 1 Database and we have 1 patch available to apply. Let’s check it…

    2.) Click on the Patches Option:


    So, on this case we have the PSU April/2018 to Apply.
    3.) Let’s run the Pre-Check:

    After the Pre-Check the status to apply the patch is OK:

    Now let’s play with DBCLI…

    a.) Connect on the DBSystem server, using your RSA Key

    [candrade.DSEU033444] ➤ ssh opc@130.61.78.42


    Last login: Fri Jun 29 07:35:37 2018 from 88.207.202.98
    [opc@dbsys02 ~]$ sudo su -
    [root@dbsys02 ~]#

    b.) Describe your DBSystem

    [root@dbsys02 ~]# dbcli describe-dbsystem -d

    DbSystem Information
    ----------------------------------------------------------------
    ID: 38ea875c-4bb6-46ba-9bad-f3dd68c8f239
    Platform: Vmdb
    Data Disk Count: 8
    CPU Core Count: 1
    Created: June 28, 2018 3:29:40 PM UTC

    System Information
    ----------------------------------------------------------------
    Name: ky5lm4jq
    Domain Name: sub06111427330.vcn0611142733.oraclevcn.com
    Time Zone: UTC
    DB Edition: EE
    DNS Servers:
    NTP Servers: 169.254.169.254

    Disk Group Information


    ----------------------------------------------------------------
    DG Name Redundancy Percentage
    ------------------------- ------------------------- ------------
    Data External 100
    Reco External 100

    DcsCli Details
    ----------------------------------------------------------------
    Version: 2.4.8-SNAPSHOT
    BuildNumber: jenkins-dcs-cli-release-24
    GitNumber: b3485a81a633205403aef1966f8d967cbd506f40
    BuildTime: null

    DcsAgent Details
    ----------------------------------------------------------------
    Version: 2.4.8.4-SNAPSHOT
    BuildNumber: jenkins-dcs-agent-18.1.1.4.0-4
    GitNumber: 1cd6d1d1999a6e60ba96fb35371a78697020c421
    BuildTime: 2018-04-18_1702 UTC

    DcsAdmin Details
    ----------------------------------------------------------------
    Version: 2.4.8-SNAPSHOT
    BuildNumber: jenkins-dcs-admin-release-10
    GitNumber: 312f7e98d2c2347841e7e5a133f22efbde920020
    BuildTime: null

    c.) Check the environment


    As you can see we have some useful information. Also we can see when the components are described that there is a new version of Patch to
    Apply. 18.2.0.0.180417

    Upgrading…

    1.) Upgrade the CLI


    [root@dbsys02 ~]# cliadm update-dbcli

    Job details
    ----------------------------------------------------------------
    ID: 0424a409-6fec-41e1-8bb4-71ed0d5d5df1
    Description: DcsCli patching
    Status: Created
    Created: June 29, 2018 8:28:13 AM UTC
    Message: Dcs cli will be updated

    Task Name Start Time End Time


    Status
    ---------------------------------------- ----------------------------------- --------------------------------
    --- ----------

    2.) Checking Patches

    3.) Update Server Components, Grid Infrastructure


    Follow the process with:
    dbcli describe-job -i 14ad7f2a-b202-42f3-99ca-30ea49de762e

    The Patch for GI is finished , now let’s check some points…

    [grid@dbsys02 ~]$ crsctl query crs releasepatch


    Oracle Clusterware release patch level is [3502001245] and the complete list of patches [26990202 27676517
    27678271 27678276 ]
    have been applied on the local node. The release patch string is [18.2.0.0.0].
    4.) Upgrade the Database

    To follow the process …

    Verify that the database home components were updated successfully by using the dbcli describe-component
    command. The Available Version column should indicate update-to-date.
    Let’s check some points…

    [grid@dbsys02 ~]$ srvctl config database -d dbsys02_fra14n


    Database unique name: dbsys02_fra14n
    Database name: dbsys02
    Oracle home: /u01/app/oracle/product/18.1/dbhome_1
    Oracle user: oracle
    Spfile: +DATA/DBSYS02_FRA14N/PARAMETERFILE/spfile.269.980006837
    Password file:
    Domain: sub06111427330.vcn0611142733.oraclevcn.com
    Start options: open
    Stop options: immediate
    Database role: PRIMARY
    Management policy: AUTOMATIC
    Server pools:
    Disk Groups: RECO,DATA
    Mount point paths:
    Services:
    Type: SINGLE
    OSDBA group: dba
    OSOPER group: dbaoper
    Database instance: dbsys02
    Configured nodes: dbsys02
    CSS critical: no
    CPU count: 0
    Memory target: 0
    Maximum memory: 0
    Default network number for database services:
    Database is administrator managed
     Some curiosities:
    After the patch applied the console is not showing the updated version 18.2.0, after further investigation I found the information below:

    https://docs.cloud.oracle.com/iaas/Content/Database/Tasks/patchingDB.htm

    I opened a service request to confirm the issue, and after apply the patch using CLI, the console is not up
    to date, this is a known issue.
    So to update you try again apply the patch using the Console in order to update.
    Below the Service Request:

    Below I will update the console:

    Click in Patches and execute the Pre-Check:

    Apply the Patch:


    Version updated now…

    You might also like