here are my notes on how to recompile if that helps

Compiling invalid objects  1. Log on to sqlplus and run : SELECT COUNT  FROM obj$ WHERE status IN (4, 5, 6);
This will show how many objects in database are in invalid state.
2. Run SELECT COUNT  FROM UTL_RECOMP_COMPILED; to find objects in valid state.
3. Run $ORACLE_HOME/rdbms/admin/utlrp.sql script in sqlplus to compile all objects in one go.
This script identifies the object dependency and opens up multiple session depending upon number of CPUs.

4. In large systems, compilation takes lot of time. To monitor the progress run the sqls in item 1 & 2 from a different SqlPlus session.

5. After the utlrp.sql script finishes execution, run again the first Sql to see if there are any invalid objects.

6. If any, run select OWNER,OBJECT_NAME,OBJECT_TYPE from dba_objects where STATUS='INVALID'; and send it to ASGs to determine what those objects are and what they intend to do. As far as DBA's role is concerned, we can do nothing in getting it compiled other than running select * from UTL_RECOMP_ERRORS; and letting ASG know the output.

.

which is what i ran for you

How to check if certificate is going to be expired or not

In Internet Explorer

1. Go to Tools > Internet Options.
2. Click the Content tab, then click the Certificates button (middle of the window).
3. In the Certificates window, click the Personal tab.
   Result: Your personal certificates should be listed. The expiration date is given in the column headed "Expiration Date".
4. Close the Certificates window, then click OK in the Internet Options window.

GAP between standby and primary.

GAP between standby and primary.

http://arup.blogspot.in/2009/12/resolving-gaps-in-data-guard-apply.html

Resolving Gaps in Data Guard Apply Using Incremental RMAN BAckup

Recently, we had a glitch on a Data Guard (physical standby database) on infrastructure. I will describe the issue and how it was resolved. In summary, there are two parts of the problem:

(1) What happened
(2) How to fix it

What Happened

Let’s look at the first question – what caused the standby to lag behind. First, I looked for the current SCN numbers of the primary and standby databases. On the primary:

SQL> select current_scn from v$database;

CURRENT_SCN
-----------
1447102
On the standby:

SQL> select current_scn from v$database;

CURRENT_SCN
-----------
1301571

(Clearly there is a difference. But this by itself does not indicate a problem; since the standby is expected to lag behind the primary (this is an asynchronous non-real time apply setup). The real question is how much it is lagging in the terms of wall clock. To know that I used the scn_to_timestamp function to translate the SCN to a timestamp:)

SQL> select scn_to_timestamp(1447102) from dual;

SCN_TO_TIMESTAMP(1447102)
-------------------------------
18-DEC-09 08.54.28.000000000 AM
I ran the same query to know the timestamp associated with the SCN of the standby database as well (note, I ran it on the primary database, though; since it will fail in the standby in a mounted mode):

SQL> select scn_to_timestamp(1301571) from dual;

SCN_TO_TIMESTAMP(1301571)
-------------------------------
15-DEC-09 07.19.27.000000000 PM
This shows that the standby is two and half days lagging! The data at this point is not just stale; it must be rotten.

The next question is why it would be lagging so far back in the past. This is a 10.2 database where FAL server should automatically resolved any gaps in archived logs. Something must have happened that caused the FAL (fetch archived log) process to fail. To get that answer, first, I checked the alert log of the standby instance. I found these lines that showed the issue clearly:

…
Fri Dec 18 06:12:26 2009
Waiting for all non-current ORLs to be archived...
Media Recovery Waiting for thread 1 sequence 700
Fetching gap sequence in thread 1, gap sequence 700-700
… …
Fri Dec 18 06:13:27 2009
FAL[client]: Failed to request gap sequence
GAP - thread 1 sequence 700-700
DBID 846390698 branch 697108460
FAL[client]: All defined FAL servers have been attempted.
…
Going back in the alert log, I found these lines:

Tue Dec 15 17:16:15 2009
Fetching gap sequence in thread 1, gap sequence 700-700
Error 12514 received logging on to the standby
FAL[client, MRP0]: Error 12514 connecting to DEL1 for fetching gap sequence
Tue Dec 15 17:16:15 2009
Errors in file /opt/oracle/admin/DEL2/bdump/del2_mrp0_18308.trc:
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
Tue Dec 15 17:16:45 2009
Error 12514 received logging on to the standby
FAL[client, MRP0]: Error 12514 connecting to DEL1 for fetching gap sequence
Tue Dec 15 17:16:45 2009
Errors in file /opt/oracle/admin/DEL2/bdump/del2_mrp0_18308.trc:
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
This clearly showed the issue. On December 15th at 17:16:15, the Managed Recovery Process encountered an error while receiving the log information from the primary. The error was ORA-12514 “TNS:listener does not currently know of service requested in connect descriptor”. This is usually the case when the TNS connect string is incorrectly specified. The primary is called DEL1 and there is a connect string called DEL1 in the standby server.

The connect string works well. Actually, right now there is no issue with the standby getting the archived logs; so there connect string is fine - now. The standby is receiving log information from the primary. There must have been some temporary hiccups causing that specific archived log not to travel to the standby. If that log was somehow skipped (could be an intermittent problem), then it should have been picked by the FAL process later on; but that never happened. Since the sequence# 700 was not applied, none of the logs received later – 701, 702 and so on – were applied either. This has caused the standby to lag behind since that time.

So, the fundamental question was why FAL did not fetch the archived log sequence# 700 from the primary. To get to that, I looked into the alert log of the primary instance. The following lines were of interest:

…
Tue Dec 15 19:19:58 2009
Thread 1 advanced to log sequence 701 (LGWR switch)
Current log# 2 seq# 701 mem# 0: /u01/oradata/DEL1/onlinelog/o1_mf_2_5bhbkg92_.log
Tue Dec 15 19:20:29 2009Errors in file /opt/oracle/product/10gR2/db1/admin/DEL1/bdump/del1_arc1_14469.trc:
ORA-00308: cannot open archived log '/u01/oraback/1_700_697108460.dbf'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
Tue Dec 15 19:20:29 2009
FAL[server, ARC1]: FAL archive failed, see trace file.
Tue Dec 15 19:20:29 2009
Errors in file /opt/oracle/product/10gR2/db1/admin/DEL1/bdump/del1_arc1_14469.trc:
ORA-16055: FAL request rejected
ARCH: FAL archive failed.
Archiver continuing
Tue Dec 15 19:20:29 2009
ORACLE Instance DEL1 - Archival Error. Archiver continuing.
…
These lines showed everything clearly. The issue was:

ORA-00308: cannot open archived log '/u01/oraback/1_700_697108460.dbf'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory

The archived log simply was not available. The process could not see the file and couldn’t get it across to the standby site.

Upon further investigation I found that the DBA actually removed the archived logs to make some room in the filesystem without realizing that his action has removed the most current one which was yet to be transmitted to the remote site. The mystery surrounding why the FAL did not get that log was finally cleared.

Solution

Now that I know the cause, the focus was now on the resolution. If the archived log sequence# 700 was available on the primary, I could have easily copied it over to the standby, registered the log file and let the managed recovery process pick it up. But unfortunately, the file was gone and I couldn’t just recreate the file. Until that logfile was applied, the recovery will not move forward. So, what are my options?

One option is of course to recreate the standby - possible one but not technically feasible considering the time required. The other option is to apply the incremental backup of primary from that SCN number. That’s the key – the backup must be from a specific SCN number. I have described the process since it is not very obvious. The following shows the step by step approach for resolving this problem. I have shown where the actions must be performed – [Standby] or [Primary].

1. [Standby] Stop the managed standby apply process:

SQL> alter database recover managed standby database cancel;

Database altered.
2. [Standby] Shutdown the standby database

3. [Primary] On the primary, take an incremental backup from the SCN number where the standby has been stuck:

RMAN> run {
2> allocate channel c1 type disk format '/u01/oraback/%U.rmb';
3> backup incremental from scn 1301571 database;
4> }

using target database control file instead of recovery catalog
allocated channel: c1
channel c1: sid=139 devtype=DISK

Starting backup at 18-DEC-09
channel c1: starting full datafile backupset
channel c1: specifying datafile(s) in backupset
input datafile fno=00001 name=/u01/oradata/DEL1/datafile/o1_mf_system_5bhbh59c_.dbf
… …
piece handle=/u01/oraback/06l16u1q_1_1.rmb tag=TAG20091218T083619 comment=NONE
channel c1: backup set complete, elapsed time: 00:00:06
Finished backup at 18-DEC-09
released channel: c1
4. [Primary] On the primary, create a new standby controlfile:

SQL> alter database create standby controlfile as '/u01/oraback/DEL1_standby.ctl';

Database altered.
5. [Primary] Copy these files to standby host:

oracle@oradba1 /u01/oraback# scp *.rmb *.ctl oracle@oradba2:/u01/oraback
oracle@oradba2's password:
06l16u1q_1_1.rmb 100% 43MB 10.7MB/s 00:04
DEL1_standby.ctl 100% 43MB 10.7MB/s 00:04 
6. [Standby] Bring up the instance in nomount mode:

SQL> startup nomount

7. [Standby] Check the location of the controlfile:

SQL> show parameter control_files

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
control_files string /u01/oradata/standby_cntfile.ctl
8. [Standby] Replace the controlfile with the one you just created in primary.

9. $ cp /u01/oraback/DEL1_standby.ctl /u01/oradata/standby_cntfile.ctl
10.[Standby] Mount the standby database:

SQL> alter database mount standby database;
11.[Standby] RMAN does not know about these files yet; so you must let it know – by a process called cataloging. Catalog these files:

$ rman target=/

Recovery Manager: Release 10.2.0.4.0 - Production on Fri Dec 18 06:44:25 2009

Copyright (c) 1982, 2007, Oracle. All rights reserved.

connected to target database: DEL1 (DBID=846390698, not open)
RMAN> catalog start with '/u01/oraback';

using target database control file instead of recovery catalog
searching for all files that match the pattern /u01/oraback

List of Files Unknown to the Database
=====================================
File Name: /u01/oraback/DEL1_standby.ctl
File Name: /u01/oraback/06l16u1q_1_1.rmb

Do you really want to catalog the above files (enter YES or NO)? yes
cataloging files...
cataloging done

List of Cataloged Files
=======================
File Name: /u01/oraback/DEL1_standby.ctl
File Name: /u01/oraback/06l16u1q_1_1.rmb
12.Recover these files:

RMAN> recover database;

Starting recover at 18-DEC-09
using channel ORA_DISK_1
channel ORA_DISK_1: starting incremental datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
destination for restore of datafile 00001: /u01/oradata/DEL2/datafile/o1_mf_system_5lptww3f_.dbf
...…
channel ORA_DISK_1: reading from backup piece /u01/oraback/05l16u03_1_1.rmb
channel ORA_DISK_1: restored backup piece 1
piece handle=/u01/oraback/05l16u03_1_1.rmb tag=TAG20091218T083619
channel ORA_DISK_1: restore complete, elapsed time: 00:00:07

starting media recovery

archive log thread 1 sequence 8012 is already on disk as file /u01/oradata/1_8012_697108460.dbf
archive log thread 1 sequence 8013 is already on disk as file /u01/oradata/1_8013_697108460.dbf
… …
13. After some time, the recovery fails with the message:

archive log filename=/u01/oradata/1_8008_697108460.dbf thread=1 sequence=8009
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 12/18/2009 06:53:02
RMAN-11003: failure during parse/execution of SQL statement: alter database recover logfile '/u01/oradata/1_8008_697108460.dbf'
ORA-00310: archived log contains sequence 8008; sequence 8009 required
ORA-00334: archived log: '/u01/oradata/1_8008_697108460.dbf'
This happens because we have come to the last of the archived logs. The expected archived log with sequence# 8008 has not been generated yet.

14.At this point exit RMAN and start managed recovery process:

SQL> alter database recover managed standby database disconnect from session;

Database altered.
15.Check the SCN’s in primary and standby:

[Standby] SQL> select current_scn from v$database;

CURRENT_SCN
-----------
1447474
[Primary] SQL> select current_scn from v$database;

CURRENT_SCN
-----------
1447478Now they are very close to each other. The standby has now caught up.

=================================================================

GAP between standby and primary.

SQL> select current_scn from v$database;

CURRENT_SCN
-----------
1447102
On the standby:

SQL> select current_scn from v$database;

CURRENT_SCN
-----------
1301571


SQL> select scn_to_timestamp(1447102) from dual;

SCN_TO_TIMESTAMP(1447102)
-------------------------------
18-DEC-09 08.54.28.000000000 AM

SQL> select scn_to_timestamp(1301571) from dual;

SCN_TO_TIMESTAMP(1301571)
-------------------------------
15-DEC-09 07.19.27.000000000 PM

1. [Standby] Stop the managed standby apply process:

SQL> alter database recover managed standby database cancel;

Database altered.
2. [Standby] Shutdown the standby database

3. [Primary] On the primary, take an incremental backup from the SCN number where the standby has been stuck:

RMAN> run {
2> allocate channel c1 type disk format '/u01/oraback/%U.rmb';
3> backup incremental from scn 1301571 database;
4> }

or
RMAN> BACKUP INCREMENTAL FROM SCN 20606344 DATABASE FORMAT '/tmp/Standby_Inc_%U' tag 'STANDBY_INC';



using target database control file instead of recovery catalog
allocated channel: c1
channel c1: sid=139 devtype=DISK

Starting backup at 18-DEC-09
channel c1: starting full datafile backupset
channel c1: specifying datafile(s) in backupset
input datafile fno=00001 name=/u01/oradata/DEL1/datafile/o1_mf_system_5bhbh59c_.dbf
… …
piece handle=/u01/oraback/06l16u1q_1_1.rmb tag=TAG20091218T083619 comment=NONE
channel c1: backup set complete, elapsed time: 00:00:06
Finished backup at 18-DEC-09
released channel: c1
4. [Primary] On the primary, create a new standby controlfile:

SQL> alter database create standby controlfile as '/u01/oraback/DEL1_standby.ctl';

Database altered.

or 

RMAN> BACKUP CURRENT CONTROLFILE FOR STANDBY FORMAT '/tmp/Standby_CTRL.bck';


5. [Primary] Copy these files to standby host:

oracle@oradba1 /u01/oraback# scp *.rmb *.ctl oracle@oradba2:/u01/oraback
oracle@oradba2's password:
06l16u1q_1_1.rmb 100% 43MB 10.7MB/s 00:04
DEL1_standby.ctl 100% 43MB 10.7MB/s 00:04 
6. [Standby] Bring up the instance in nomount mode:

SQL> startup nomount

7. [Standby] Check the location of the controlfile:

SQL> show parameter control_files

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
control_files string /u01/oradata/standby_cntfile.ctl
8. [Standby] Replace the controlfile with the one you just created in primary.

9. $ cp /u01/oraback/DEL1_standby.ctl /u01/oradata/standby_cntfile.ctl
10.[Standby] Mount the standby database:

SQL> alter database mount standby database;
11.[Standby] RMAN does not know about these files yet; so you must let it know – by a process called cataloging. Catalog these files:

$ rman target=/

Recovery Manager: Release 10.2.0.4.0 - Production on Fri Dec 18 06:44:25 2009

Copyright (c) 1982, 2007, Oracle. All rights reserved.

connected to target database: DEL1 (DBID=846390698, not open)
RMAN> catalog start with '/u01/oraback';

using target database control file instead of recovery catalog
searching for all files that match the pattern /u01/oraback

List of Files Unknown to the Database
=====================================
File Name: /u01/oraback/DEL1_standby.ctl
File Name: /u01/oraback/06l16u1q_1_1.rmb

Do you really want to catalog the above files (enter YES or NO)? yes
cataloging files...
cataloging done

List of Cataloged Files
=======================
File Name: /u01/oraback/DEL1_standby.ctl
File Name: /u01/oraback/06l16u1q_1_1.rmb
12.Recover these files:

RMAN> recover database;

Starting recover at 18-DEC-09
using channel ORA_DISK_1
channel ORA_DISK_1: starting incremental datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
destination for restore of datafile 00001: /u01/oradata/DEL2/datafile/o1_mf_system_5lptww3f_.dbf
...…
channel ORA_DISK_1: reading from backup piece /u01/oraback/05l16u03_1_1.rmb
channel ORA_DISK_1: restored backup piece 1
piece handle=/u01/oraback/05l16u03_1_1.rmb tag=TAG20091218T083619
channel ORA_DISK_1: restore complete, elapsed time: 00:00:07

starting media recovery

archive log thread 1 sequence 8012 is already on disk as file /u01/oradata/1_8012_697108460.dbf
archive log thread 1 sequence 8013 is already on disk as file /u01/oradata/1_8013_697108460.dbf
… …
13. After some time, the recovery fails with the message:

archive log filename=/u01/oradata/1_8008_697108460.dbf thread=1 sequence=8009
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 12/18/2009 06:53:02
RMAN-11003: failure during parse/execution of SQL statement: alter database recover logfile '/u01/oradata/1_8008_697108460.dbf'
ORA-00310: archived log contains sequence 8008; sequence 8009 required
ORA-00334: archived log: '/u01/oradata/1_8008_697108460.dbf'
This happens because we have come to the last of the archived logs. The expected archived log with sequence# 8008 has not been generated yet.

14.At this point exit RMAN and start managed recovery process:

SQL> alter database recover managed standby database disconnect from session;

Database altered.
15.Check the SCN’s in primary and standby:

[Standby] SQL> select current_scn from v$database;

CURRENT_SCN
-----------
1447474
[Primary] SQL> select current_scn from v$database;

CURRENT_SCN
-----------
1447478Now they are very close to each other. The standby has now caught up.

gerunds passive voice.mov --- Still more exist.

https://m.youtube.com/watch?v=ixvdY887Nvc

He doesn't like being told. What to do.

I don't like being told.

She enjoyed being read to.

They don't like being watched.

Do you remember being paid.

Some time "being" is replaced by "getting"

Do you remember getting paid.  Or do you remember being paid.

My dog doesn't like being washed or my dog doesn't like getting washed.

https://m.youtube.com/watch?v=0nDFTCJ7jXA

English Grammar: How to use "to" before an "-ing" verb

There is get used to sentence is there find it

1. I look forward to _________ from you.

• hear
• hearing
• heard
• hearding

2. I confess to ____________ from the store.

• steal
• stoling
• stealing
• stole

3. I am committed to ______ hard.

• work
• worked
• workking
• working

4. I am opposed to _______ factory-farmed chickens.

• eating
• ate
• eaten
• eat

5. I’m accustomed to ______ on a tropical island.

• live
• lived
• been living
• living

6. You will get used ________ in these shoes.

• to running
• to ranning
• to ran
• to run

7. Prepositions ("about", "on", "in", "with", etc.) are followed by verbs that end in "ing".

• true
• talse

8. I hope to ________ again.

• see you
• seeing you
• seen you
• seening you

"Hope" is not a phrasal verb. We don't use -ing with it. "Hope" is followed by a verb in the infinitive (to see).

9. We are committed ________ hunger.

• to end
• ending
• to ending
• end

"Committed to" is a phrasal verb. As a result, the verb that follows must end in "ing".

10. I am addicted _________.

• to shop
• to shopping
• shopping
• shop

"Addicted to" is a phrasal verb, so it must be followed by an "ing" verb (shopping).

Published on 22 Apr 2016In this lesson, I explain how and when we use "to" before a verb with the "-ing" ending. The use of "to" before an "-ing" verb is not always correct. But it is correct in a particular case to express an emotion or action happening in the present referring to a past or future event. If this sounds complicated, have no fear! It is a simple structure once you understand how it works. And if you do our quiz at http://www.engvid.com/english-grammar... you will get used to using this concept in no time! TRANSCRIPT Hi there. My name is Emma, and in today's video, we are going to talk about something many students wonder about, and that is when we use "to" and "ing" together. Sorry. Okay, so for example... Yeah: "What???" Many students, when they see this, it "poof" their minds; they have no idea: What is this? It goes against all the rules they've learned. So I'm going to explain to you when this happens, and how we can use it. So, let's look at some examples. This is the most common example of this you will see: "I look forward to meeting you." Notice we have our verb: "look forward", and then we have this little guy, here, "to", and then we also have "ing". Okay? So, in this case, it's very strange. We're going to learn about why this is in a moment, but before we do that, I want to tell you some of the basic rules so you can understand, first off: What am I talking about with "ing", and what am I talking about with "to"? So let's look at the basic rules. This is all about when you have two verbs in a sentence. For example: "thank" is the first verb, and "help" is the second verb. Okay? What you will notice in English, the first rule is: Any time you have a preposition between the first verb and the second, you're going to use "ing". A preposition is a word like "for", "to", "about", "toward", "up", "down", "in", "out", all of these words that kind of tell us where something is located, these are called "prepositions". So, whenever you see a preposition after a verb, this next verb is going to end in "ing". So our example here: "I thank you for helping me." Similarly, we have our verb: "interested", "I'm interested", so this is the verb. And we have a second verb: "learn". So, if we have a preposition after the first verb: "I'm interested in", you're going to see that the second verb is going to end in "ing". "I'm interested in learning English." So we don't say: "I'm interested in to learn English." Similarly, we don't say: "I thank you to help me." If you have a preposition like "for", "in", "out", you are going to have the second verb with "ing". Okay, some verbs... These are verbs without prepositions. If we have two verbs and there's no preposition between them, they will be either verb with a second verb ending in "ing", or a verb plus the second verb beginning in "to". So let's look at some examples so you understand what I'm talking about. Okay, I have here the verb "enjoy". Here's my first verb. Think of a second verb we can use. Let's say "eat". With the verb "enjoy", the verb that follows is always going to end in "ing". "I enjoy eating.", "I enjoy reading.", "I enjoy listening to music.", "I enjoy shopping." Okay? So, in this case, all... The second verb will always end in "ing". We have another example, here: "I started". "I started", let's think of a verb, any verb. "Fish". "I started fishing." So, again, this is the first verb, here's the second verb, second verb ends in "ing". I en-... Or: "I started drinking.", "I started eating my dinner." Okay? Then we also have some verbs that you will see... Here's the first verb: "decided". The second verb does not end in "ing". "I decided to", what's a verb we can use here? "Watch". "I decided to watch TV." Okay? "I want to eat ice cream." So, in this case, we have two verbs-so verb one, verb two; verb one, verb two-the second verb begins with the word "to". Now, other teachers on engVid have already covered this information. What you will notice is that some verbs are always like this, some verbs are always like this, and some verbs do both. It's pretty much you have to memorize: When is it "ing"...? Sorry. "ing", and when is it "to"? What we're really interested in today is this, this really confusing thing: Why is it "ing" and "to"? All right? So let's look at some more examples of this, and I will tell you the rule on when we use "ing" and "to" together. Okay, so I've explained to you the three rules we use when we have two verbs together. Okay? Sometimes you have a verb followed by "ing", sometimes you have a verb followed by "to", and in the case of prepositions, you have a verb followed by "ing". So I've taught you these three rules. Now we're going to look at when we have both "ing" and "to" together. Okay? So, "ing" and "to" together. So in this case, we have two verbs. The first verb is: "I look forward to". The second verb is: "meeting". Okay?

# Minute       Hour          Day of Month       Month                         Day of Week        Command  
# (0-59)        (0-23)                 (1-31)           (1-12 or Jan-Dec)       (0-6 or Sun-Sat)              

string         meaning
------         -------
@reboot        Run once, at startup.
@yearly        Run once a year, "0 0 1 1 *".
@annually      (same as @yearly)
@monthly       Run once a month, "0 0 1 * *".
@weekly        Run once a week, "0 0 * * 0".
@daily         Run once a day, "0 0 * * *".
@midnight      (same as @daily)
@hourly        Run once an hour, "0 * * * *".

https://www.pantz.org/software/cron/croninfo.html

in chrome ,

how to navigate foward : CTRL+tab
how to navigate backward : CTRL+SHIFT+TAB


CPU and memory info from the files /proc/cpuinfo and /proc/meminfo, utilisation from commands such as sar, vmstat, etc. Please look at those.


-sh-4.1$ lscpu
Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                8
On-line CPU(s) list:   0-7
Thread(s) per core:    1
Core(s) per socket:    1
Socket(s):             8
NUMA node(s):          1
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 45
Stepping:              7
CPU MHz:               2700.000
BogoMIPS:              5400.00
Hypervisor vendor:     VMware
Virtualization type:   full
L1d cache:             32K
L1i cache:             32K
L2 cache:              256K
L3 cache:              20480K
NUMA node0 CPU(s):     0-7
-sh-4.1$

========================================
-sh-4.1$ cat /proc/cpuinfo
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 45
model name      : Intel(R) Xeon(R) CPU E5-2680 0 @ 2.70GHz
stepping        : 7
cpu MHz         : 2700.000
cache size      : 20480 KB
fpu             : yes
fpu_exception   : yes
cpuid level     : 13
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts mmx fxsr sse sse2 ss syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts nopl xtopology tsc_reliable nonstop_tsc aperfmperf pni pclmulqdq ssse3 cx16 sse4_1 sse4_2 x2apic popcnt aes xsave avx hypervisor lahf_lm ida arat epb xsaveopt pln pts dts
bogomips        : 5400.00
clflush size    : 64
cache_alignment : 64
address sizes   : 40 bits physical, 48 bits virtual
power management:

processor       : 1
vendor_id       : GenuineIntel
cpu family      : 6
model           : 45
model name      : Intel(R) Xeon(R) CPU E5-2680 0 @ 2.70GHz
stepping        : 7
cpu MHz         : 2700.000
cache size      : 20480 KB
fpu             : yes
fpu_exception   : yes
cpuid level     : 13
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts mmx fxsr sse sse2 ss syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts nopl xtopology tsc_reliable nonstop_tsc aperfmperf pni pclmulqdq ssse3 cx16 sse4_1 sse4_2 x2apic popcnt aes xsave avx hypervisor lahf_lm ida arat epb xsaveopt pln pts dts
bogomips        : 5400.00
clflush size    : 64
cache_alignment : 64
address sizes   : 40 bits physical, 48 bits virtual
power management:

processor       : 2
vendor_id       : GenuineIntel
cpu family      : 6
model           : 45
model name      : Intel(R) Xeon(R) CPU E5-2680 0 @ 2.70GHz
stepping        : 7
cpu MHz         : 2700.000
cache size      : 20480 KB
fpu             : yes
fpu_exception   : yes
cpuid level     : 13
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts mmx fxsr sse sse2 ss syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts nopl xtopology tsc_reliable nonstop_tsc aperfmperf pni pclmulqdq ssse3 cx16 sse4_1 sse4_2 x2apic popcnt aes xsave avx hypervisor lahf_lm ida arat epb xsaveopt pln pts dts
bogomips        : 5400.00
clflush size    : 64
cache_alignment : 64
address sizes   : 40 bits physical, 48 bits virtual
power management:
=========================================================

Intel(R) Xeon(R) CPU E5-2680 0 @ 2.70GHz -->  it means you are having Intel cpu having speed of 2 giga hurtz

if you get ouput has

-sh-4.1$ cat /proc/cpuinfo | grep processor
processor       : 0
processor       : 1
processor       : 2
processor       : 3
processor       : 4
processor       : 5
processor       : 6
processor       : 7

and no of core = 2 

then , it means you have 4 physical processor and each having 2 cores. 

No of cores represents multi threading means each processor can accept 2 tasks at a time.

CPU is a processing unit and it has number of processor. or you can say processor and cpu are both same.

if a processor or CPU has 4 core , then it means it quad core processor.


ps aux | awk '{print $2, $4, $11}' | sort -k2rn | head -n 20


This will list the first 20 applications in reverse order, from the one using more RAM to the one using lest RAM

==============================================

-sh-4.1$ lscpu
Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                8
On-line CPU(s) list:   0-7
Thread(s) per core:    1
Core(s) per socket:    1
Socket(s):             8
NUMA node(s):          1
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 45
Stepping:              7
CPU MHz:               2700.000
BogoMIPS:              5400.00
Hypervisor vendor:     VMware
Virtualization type:   full
L1d cache:             32K
L1i cache:             32K
L2 cache:              256K
L3 cache:              20480K
NUMA node0 CPU(s):     0-7
-sh-4.1$

=========================

ctrl+alt+end to chnage the password of remote desktop.

====================

Loopback address is a special IP number (127.0.0.1) that is designated for the software loopback interface of a machine. ... The loopback interface allows IT professionals to test IP software without worrying about broken or corrupted drivers or hardware.