How To Install Telnet On Exadata?

Telnet is not pre-configured on DB server or Cell server in Exadata Machine. If we required than we can install it separately using Linux rpm.

Telnet is used to check whether particular port is open or not. You can follow below steps to install telnet utility on Database machine.


Step 1: Download required telnet rpm from Linux rpm repository 

RPM : telnet-0.17-39.el5.x86_64.rpm  
RPM Repository URL :  http://public-yum.oracle.com/repo

Note: RPM version can be different as per OS

Step 2: Move rpm to database server

Step 3: Install rpm

[root@db01 ~]# rpm -ivh telnet-0.17-39.el5.x86_64.rpm
Preparing...  ################################### [100%]
   1:telnet    ################################### [100%]

Step 4: Test the telnet utility 

[root@db01 ~]# telnet db02 1521
Trying 192.168.10.12...
Connected to db01.
Escape character is '^]'.

Golden Gate Checkpoint Table Error: Could not Delete DB Checkpoint for REPLICAT

Recently while we were working on goldengate configuration on Exadata we faced below error while deleting the replicate process. Hope it will help you.

ERROR


GGSCI (dm01) 4> delete replicat EXREP1

ERROR: Could not delete DB checkpoint for REPLICAT EXREP1 (OCI Error ORA-00942: table or view does not exist (status = 942). Deleting from checkpoint table ogg.checkpointtable, group 'EXREP1', key 3261899073 (0xc26ca141), SQL <DELETE FROM ogg.checkpointtable  WHERE group_name = 'EXREP1' AND     group_key  = 3261899073>).

After getting above error we have checked whether EXREP1 has been deleted or not, but because of above error it has not been deleted.


GGSCI (dm01) 6> info all


Program     Status      Group       Lag at Chkpt  Time Since Chkpt

MANAGER     RUNNING
REPLICAT     STOPPED     EXREP1     00:00:00      00:00:01


Solution

While deleting specify ! argument as well to remove replicat process.


GGSCI (dm01) 5>  delete replicat EXREP1 !

WARNING: Could not delete DB checkpoint for REPLICAT EXREP1 (OCI Error ORA-00942: table or view does not exist (status = 942). Deleting from checkpoint table ogg.checkpointtable, group 'EXREP1', key 3261899073 (0xc26ca141),SQL <DELETE FROM ogg.checkpointtable  WHERE group_name = 'EXREP1' AND        group_key  = 3261899073>).

Now you can seen in info all, EXREP1 process has been deleted successfully.

GGSCI (dm01) 6> info all


Program     Status      Group       Lag at Chkpt  Time Since Chkpt

MANAGER     RUNNING


What is DBMCLI in Exadata?



Definition:

Starting Exadata Storage Server Release 12.1.2.1.0 a new command-line interface called DBMCLI is introduced for database server.



DBMCLI is the database machine command line interface to administrate exadata database server.

It runs on each database machine. By default it is pre-installed on each database server and on virtualized machine while it shipped.

DBMCLI utility is included in latest release 12.1.2.1.0 of Exadata image


Using DBMCLI:

  • Configure ASR, capacity-on-demand, infrastructure as a service
  • Configure database server e-mail alerts
  • Configure, manage and monitor database servers
  • Start stop server
  • Manage server configuration information
  • Enable or disable the server
  • It can be start through SSH by executing DBMCLI command
  • Used to monitor database server metrcis
  • It uses DB server OS authentication, it doesn't required login parameter, moreover like CELLCLI

Syntax:

  
$dbmcli [port_number] [-n] [-m] [-xml] [-v | -vv | -vvv] [-x] [-e command]

Here 

Port_number  - Specifies HTTP port number of database server. If not specified it will use the port from cellinit.ora file.If it is not in cellinit.ora than port number 8888 will be used.

n                 - Execute DBMCLI command in non-interactive mode
m                - Run DBMLI in run monitor mode (Read Only)
xml              - Display output in xml format, can be used for OEM
v, vv, vvv      - Set log level, Fine, Finer and Finest level of log
x                 - Suppress the banner
e                 - To execute specific DBMCLI command 

Users:

DBMCLI has two users

dbmadmin   - Used for administration purpose
dbmmonitor - Used for monitoring purpose

You can follow our Exadata Certification Question Bank to achieve maximum success in your Exadata certification.

Exadata Patching - Cell Server

Cell storage patching can be done by patchmgr utility which is used to do a patching in rolling as well in non-rolling fashion.


Syntax: ./patchmgr -cells cell_group -patch [-rolling] [-ignore_alerts] [- smtp_from "addr" -smtp_to "addr1 addr2 addr3 ..."]


Here addr is the sending mail id which is used to send status of patching and addr1,addr2,addr3 are receiving mail id to receive the status of patching.

Step-1  First note down the current image version of cell by executing 

#imageinfo

Step-2  Go to cell patch directory where patch has been copied

/19625719/Infrastructure/11.2.3.3.1/ExadataStorageServer_InfiniBandSwitch/patch_11.2.3.3.1.140708

Step-3  Reset the server to a known state using the following command

./patchmgr -cells cell_group -reset_force


Step-4  Clean up any previous patchmgr utility runs using the following command

./patchmgr -cells cell_group -cleanup


Step-5 Verify that the cells meet prerequisite checks using the following command