Skip to main content

Generating public/private rsa key in Solaris

To set the auto authentication in ssh please follow the steps described below:


bash-3.00$ ssh-keygen -t rsa
Generating public/private rsa key pair.

Enter file in which to save the key (/home/oracle/.ssh/id_rsa):  <Press Enter>


Enter passphrase (empty for no passphrase):  <Press Enter>


Enter same passphrase again:  <Press Enter>

Your identification has been saved in /home/oracle/.ssh/id_rsa.
Your public key has been saved in /home/oracle/.ssh/id_rsa.pub.
The key fingerprint is:
22:55:d2:30:cb:5f:7b:eb:1e:ec:8e:72:48:cb:05:b6 oracle@DCDB01

bash-3.00$ pwd
/home/oracle

bash-3.00$ cd .ssh/
bash-3.00$ cat id_rsa.pub | ssh root@172.17.2.100 "cat - >> /.ssh/authorized_keys"

The authenticity of host '172.17.2.100 (172.17.2.100)' can't be established.
RSA key fingerprint is b5:3a:ce:a0:9f:44:18:ee:a0:33:a3:c6:ff:1a:b0:c3.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '172.17.2.100' (RSA) to the list of known hosts.

Password: 
< Provide password of remote host. i.e. 172.17.2.100 >

< Check That the authentication is working >

bash-3.00$ ssh root@172.17.2.100

Last login: Wed May  9 10:12:55 2012 from 172.17.2.101
Sun Microsystems Inc.   SunOS 5.10      Generic January 2005
You have new mail.
Sourcing //.profile-EIS.....


root@DCDB3 # 


< So, the connection was established>

Comments

Popular posts from this blog

ORACLE FLASH RECOVERY AREA USAGE QUERY

FINDING ORACLE FLASH RECOVERY AREA USAGE SELECT NAME,        (SPACE_LIMIT / 1024 / 1024 / 1024) SPACE_LIMIT_GB,          ((SPACE_LIMIT - SPACE_USED + SPACE_RECLAIMABLE) / 1024 / 1024 / 1024) AS SPACE_AVAILABLE_GB,        ROUND((SPACE_USED - SPACE_RECLAIMABLE) / SPACE_LIMIT * 100, 1) AS PERCENT_FULL   FROM V$RECOVERY_FILE_DEST;

Shared Pool Tuning: Cursor Tuning (Tuning Open_Cursors, Session_Cached_Cursors, Cursor_Space_For_Time)

Shared Pool Tuning: Cursor Tuning The three most important parameter for shared pool tuning are OPEN_CURSORS , SESSION_CACHED_CURSORS and CURSOR_SPACE_FOR_TIME. But most of the time we see that these two parameters SESSION_CACHED_CURSORS and CURSOR_SPACE_FOR_TIME are ignored or unused . OPEN CURSORS Open cursors take up space in the shared pool, in the library cache. OPEN_CURSORS sets the maximum number of cursors each session can have open, per session. For example, if OPEN_CURSORS is set to 1000, then each session can have up to 1000 cursors open at one time. V$open_cursor shows cached cursors, not currently open cursors, by session. If you’re wondering how many cursors a session has open, don’t look in v$open_cursor. It shows the cursors in the session cursor cache for each session, not cursors that are actually open.  To monitor open cursors, query v$sesstat where name= ’opened cursors current’ . This will give the number of currently opened cursors, by session:

How to delete/remove Management Agent from Oracle Enterprise Manager 12C

  1. Before you deinstall a Management Agent, do the following:     a. Stop the Agent using command from Management Agent home:                 cd /u01/oemcc_latest/core/12.1.0.2.0/bin/                 $ emctl stop agent     b. Wait for the Management Agent to go to the unreachable state in the Cloud Control console.     c. It is mandatory to delete the Management Agent and their monitored targets using any of the following methods: Remove the Agent target manually from the console: 1. Login to 12C Cloud Control 2. Navigate to Setup => Manage Cloud Control => Agents 3. Go to the Home page of the Agent that you want to remove 4. Expand the drop-down menu near the " Agent " 5. Expand the " Target Setup " option 6. Select " Remove Target "            In Cloud Control Release 12.1.0.2, the following dialog box will be displayed if the Agent is still monitoring targets. Click Continue. You can then remove all targets (usin