First find out partition detail,
#fdisk -l
#mkdir /win
#mount -t msdos /dev/sda1 /win .....(If partition is FAT32)
-or-
#mount -t ntfs /dev/sda1 /win .....(If partition is NTFS)
#cd /win
Note: If your are using RHEL 3,4,5 then NTFS mounting will not be Supported. For that you need to complile a new kernel.
Linux administration , Unix administration , Vmware Vsphere administration , Oracle DBA ,apache, backup, dhcp, dns, kvm, xen, kernel, ldap, kvm, monitoring, ticketing, networking, Mail servers, SAN,troubleshooting
Labels
- Amanda (2)
- Ansible (2)
- Answer these Questions (2)
- antivirus (2)
- apache (3)
- Bash (16)
- Chef (3)
- Citrix (2)
- clusters (2)
- Concept (22)
- DatabaseAdminstration (11)
- DevOps (1)
- dhcp (2)
- Downloads (3)
- ELK (1)
- ELK stack (1)
- encryption (1)
- Free trainings (1)
- Frequently Used Commands (46)
- FTP (1)
- git (1)
- gpg (2)
- Hardware (1)
- httpd (2)
- Interview Questions (53)
- iptables (1)
- IT NEWS (3)
- java (1)
- kibana (2)
- knife (1)
- KVM (2)
- linux (17)
- Linux installations (22)
- Linux Jobs (4)
- Linux Links (2)
- logstash (1)
- Mac (1)
- MediaWiki (1)
- MySql (2)
- Nagios (2)
- Networking (3)
- open Nebula (5)
- Open Source tools (12)
- OpenNMS (1)
- openSSL (1)
- Oracle on Linux (5)
- Performance Monitoring (1)
- php (1)
- postfix (1)
- postgres (1)
- postgres-XL (1)
- Product Reviews (1)
- Python (2)
- rssh (1)
- Samba (2)
- Scripting (16)
- security (4)
- selinux (1)
- Server (1)
- SFTP (1)
- Social Awareness (1)
- Solaris (1)
- SSL (1)
- svn (1)
- TCP/IP (1)
- Technology (1)
- Tips and Tricks (32)
- Training and materials (8)
- Troubleshooting (6)
- Ubuntu (18)
- unix (1)
- virtualization (17)
- Vmware (25)
- Vyatta (1)
- windows7 (1)
- xml (1)
What is SGA
The SGA is a chunk of memory that is allocated by an Oracle Instance during the nomount stage and is shared among Oracle processes, hence the name. It contains all sorts of information about the instance and the database that is needed to operate.
The SGA consists of the following four (five if MTS) parts:
* Fixed Portion
* Variable Portion
* Shared pool
* java pool
Fixed portion
The size of the fixed portion is constant for a release and a plattform of Oracle, that is, it cannot be changed through any means such as altering the initialization parameters
Variable portion
The variable portion is called variable because its size (measured in bytes) can be changed.The variable portion consists of:
* large pool which provides working space for rman (although rman will also work without large pool).
* Shared pool used for objects that are shared among all users.
The shared pool can further be subdivied into:
o Control structures
o Character sets
o Dictionary cache
The dictionary cache stores parts fo the data dictionary because Oracle has to query the data dictionary very often as it is fundamental to the functioning of Oracle.
o Library cache
The library cache is further divided into
+ Shared SQL Area,
+ PL/SQL Procedures and
+ Control Structures (Latches and Locks).
The size of the Shared Pool is essentially governed by the initialization parameter shared_pool_ size (although shared_pool_ size is usually smaller than the size of the shared pool, see here) and db_block_buffers (which plays a role for this size because the database buffer cache must be administered. )
The size for the variable portion is roughly equal to the result of the following statement:
select sum(bytes) from
v$sgastat where
pool in ('shared pool', 'java pool', 'large pool');
Redo log buffer
Redo Buffers is roughly equal to the parameter log_buffer
Database buffer cache
It's size is equal to db_block_size * db_block_buffers.
db_block_buffers is deprecated as of 9i, so if the init parameter db_cache_size) is set, the buffer cache's size will be set according to this value.
UGA
If the instance is running in MTS mode, there'se also a UGA: user global area
You can use v$sga to show the amount of these sizes or alternatively use SHOW SGA in sql*plus.
The following initialization parameters affect the size of the SGA:
* db_block_buffers,
* db_block_size,
* db_cache_size,
* db_keep_cache_ size,
* db_recycle_cache_ size,
* java_pool_size.
* large_pool_size,
* log_buffer,
* shared_pool_ size,
* streams_pool_ size,
The amount of SGA that a user can use can be limitted through profiles. Use the private_sga option in the create profile statement.
Dynamic SGA allows to change the size of the buffer cache, the large pool, the shared pool and the process private memory on the fly, that is without shutting down the instance.
The x$ tables are an sql interface to the SGA and allow to peek into the SGA.Notably, x$ksmmem seems to allow to address every byte in the SGA.
The SGA consists of the following four (five if MTS) parts:
* Fixed Portion
* Variable Portion
* Shared pool
* java pool
Fixed portion
The size of the fixed portion is constant for a release and a plattform of Oracle, that is, it cannot be changed through any means such as altering the initialization parameters
Variable portion
The variable portion is called variable because its size (measured in bytes) can be changed.The variable portion consists of:
* large pool which provides working space for rman (although rman will also work without large pool).
* Shared pool used for objects that are shared among all users.
The shared pool can further be subdivied into:
o Control structures
o Character sets
o Dictionary cache
The dictionary cache stores parts fo the data dictionary because Oracle has to query the data dictionary very often as it is fundamental to the functioning of Oracle.
o Library cache
The library cache is further divided into
+ Shared SQL Area,
+ PL/SQL Procedures and
+ Control Structures (Latches and Locks).
The size of the Shared Pool is essentially governed by the initialization parameter shared_pool_ size (although shared_pool_ size is usually smaller than the size of the shared pool, see here) and db_block_buffers (which plays a role for this size because the database buffer cache must be administered. )
The size for the variable portion is roughly equal to the result of the following statement:
select sum(bytes) from
v$sgastat where
pool in ('shared pool', 'java pool', 'large pool');
Redo log buffer
Redo Buffers is roughly equal to the parameter log_buffer
Database buffer cache
It's size is equal to db_block_size * db_block_buffers.
db_block_buffers is deprecated as of 9i, so if the init parameter db_cache_size) is set, the buffer cache's size will be set according to this value.
UGA
If the instance is running in MTS mode, there'se also a UGA: user global area
You can use v$sga to show the amount of these sizes or alternatively use SHOW SGA in sql*plus.
The following initialization parameters affect the size of the SGA:
* db_block_buffers,
* db_block_size,
* db_cache_size,
* db_keep_cache_ size,
* db_recycle_cache_ size,
* java_pool_size.
* large_pool_size,
* log_buffer,
* shared_pool_ size,
* streams_pool_ size,
The amount of SGA that a user can use can be limitted through profiles. Use the private_sga option in the create profile statement.
Dynamic SGA allows to change the size of the buffer cache, the large pool, the shared pool and the process private memory on the fly, that is without shutting down the instance.
The x$ tables are an sql interface to the SGA and allow to peek into the SGA.Notably, x$ksmmem seems to allow to address every byte in the SGA.
various Admin requirements
Linux
/Solaris/AIX/HPUX/Redhat (Expertise in at least two)
Remote support, KVM, DRAC, ALOM, HMC
Perl/shell scripting(MUST)
LVM/Sun Disk Suite
Network services, NFS, NIS, DNS, Samba.
OpenSource software compilation and installation (gcc, cc)
Knowledge of RAID (0,1,1+0,3,5)
OS installation, kernel configuration
Web servers, apache, iPlanet, tomcat
Monitoring tools, Nagios, Netsaint, OVO, BMC patrol, MRTG, Remedy
Troubleshooting and performance tuning.
Veritas products - File System, Clustering, Volume Manager
OpenPKG / RPM, Sun Packages
Storage knowledge, EMC, HP-EVA, IBM-ESS
Virtualization, Vmware, Xen
Role: Configuration Management-unix and linux admin exp
?The individual should have sound Unix Background, with at least 2years of Administration Skills in Solaris 5.8 and above and Redhat Linux 4 and above.
?The individual should have handson admin experience of at least 4 years in ClearCase ver 6 and above, ClearCase MultiSite
?The individual must be skilled in DesignSync and should have at least 1years hands-on experience with DesignSync
?The individual should posses sufficient knowledgeable of Windows environment to be able to different windows related and Application related issues
?The individual should have knowledgeable in Defect and Requirement Management tools like ClearQuest, RequisitePro
?The individual must exhibit very good programming skills with Perl
Good To Have Skills:
?Knowledge / hands-on with BuildForge, Klockwork, Sourceforge, GIT will be an added advantage
/Solaris/AIX/HPUX/Redhat (Expertise in at least two)
Remote support, KVM, DRAC, ALOM, HMC
Perl/shell scripting(MUST)
LVM/Sun Disk Suite
Network services, NFS, NIS, DNS, Samba.
OpenSource software compilation and installation (gcc, cc)
Knowledge of RAID (0,1,1+0,3,5)
OS installation, kernel configuration
Web servers, apache, iPlanet, tomcat
Monitoring tools, Nagios, Netsaint, OVO, BMC patrol, MRTG, Remedy
Troubleshooting and performance tuning.
Veritas products - File System, Clustering, Volume Manager
OpenPKG / RPM, Sun Packages
Storage knowledge, EMC, HP-EVA, IBM-ESS
Virtualization, Vmware, Xen
Role: Configuration Management-unix and linux admin exp
?The individual should have sound Unix Background, with at least 2years of Administration Skills in Solaris 5.8 and above and Redhat Linux 4 and above.
?The individual should have handson admin experience of at least 4 years in ClearCase ver 6 and above, ClearCase MultiSite
?The individual must be skilled in DesignSync and should have at least 1years hands-on experience with DesignSync
?The individual should posses sufficient knowledgeable of Windows environment to be able to different windows related and Application related issues
?The individual should have knowledgeable in Defect and Requirement Management tools like ClearQuest, RequisitePro
?The individual must exhibit very good programming skills with Perl
Good To Have Skills:
?Knowledge / hands-on with BuildForge, Klockwork, Sourceforge, GIT will be an added advantage
Difference between a database and an instance
The terms instance and database are closely related, but not the same thing.
The database is the set of files where application data (the reason for a database) and meta data is stored.
An instance is the software (and memory) that Oracle uses to manipulate the data in the database. In order for the instance to be able to manipulate that data, the instance must open the database. A database can be opened (or mounted) by more than one instance, however, an instance can open at most one database.
The database is the set of files where application data (the reason for a database) and meta data is stored.
An instance is the software (and memory) that Oracle uses to manipulate the data in the database. In order for the instance to be able to manipulate that data, the instance must open the database. A database can be opened (or mounted) by more than one instance, however, an instance can open at most one database.
What is a instance
Database programs, with few exceptions, need to utilize both the computer's memory and permanent storage space such as the hard drive to operate. The drives provide both long-term storage and the necessary room for millions of records and gigabytes worth of information.
However, accessing information from disks is much slower than retrieving the same information from memory. Therefore, database engines use memory to cache information, which speeds its retrieval.
The complexity of how the information is stored and where it is retrieved from is hidden from the casual user who queries the database. But if you plan on administering Oracle, you need to become familiar with how Oracle handles both resources.
An instance is the (executed) Oracle software (Oracle processes) and the memory they use (SGA). It is the instance that manipulates the data stored in the database.
It acts as a bridge between the database and the filesystem
However, accessing information from disks is much slower than retrieving the same information from memory. Therefore, database engines use memory to cache information, which speeds its retrieval.
The complexity of how the information is stored and where it is retrieved from is hidden from the casual user who queries the database. But if you plan on administering Oracle, you need to become familiar with how Oracle handles both resources.
An instance is the (executed) Oracle software (Oracle processes) and the memory they use (SGA). It is the instance that manipulates the data stored in the database.
It acts as a bridge between the database and the filesystem
Oracle Architecture simplified
Oracle = Instance + Database File
1A) Instance [ SGA + Background Services]
2A) database file [ control file, datafile , redolog file]
SGA
1)Share pool [ library cache , data dictonary cache]
2)database buffer cache
3)Redolog buffer
Background servies
1) Pmon
2) Smon
3) DBWR
4) LGWR
5) CKPT
1A) Instance [ SGA + Background Services]
2A) database file [ control file, datafile , redolog file]
SGA
1)Share pool [ library cache , data dictonary cache]
2)database buffer cache
3)Redolog buffer
Background servies
1) Pmon
2) Smon
3) DBWR
4) LGWR
5) CKPT
Subscribe to:
Posts (Atom)