Saturday, June 30, 2012

Kernel Parameters for the Oracle 11g R2 Fusion Applications Database


Configuring the Kernel Parameters according to the requirements of the fusion applications 

To know the kernel parameter which is present in the system user sysctl  command

we have the bellow kernel parameters setting as the default

net.ipv4.ip_forward = 0
net.ipv4.conf.default.rp_filter = 1
net.ipv4.conf.default.accept_source_route = 0
kernel.core_uses_pid = 1
net.ipv4.tcp_syncookies = 1
fs.file-max = 6815744
kernel.msgmni = 2878
kernel.msgmax = 8192
kernel.msgmnb = 65536
kernel.sem = 250 32000 100 142
kernel.shmmni = 4096
kernel.shmall = 1073741824
kernel.shmmax = 4398046511104
kernel.sysrq = 1
net.core.rmem_default = 262144
net.core.rmem_max = 4194304
net.core.wmem_default = 262144
net.core.wmem_max = 1048576
fs.aio-max-nr = 3145728
net.ipv4.ip_local_port_range = 9000 65500
vm.min_free_kbytes = 51200

To edit the kernel parameters vi /etc/sysctl.conf

The recommended Kernel parameters for the Oracle Fusion Applications Database
Refer to the Link  http://docs.oracle.com/cd/E15586_01/fusionapps.1111/e16684/set_up_db_tier.htm#BABGGIGA

fs.file-max = 6815744
kernel.shmall = 2097152
kernel.shmmax = 2147483648
kernel.shmmni = 4096
kernel.sem = 250 32000 100 128
net.core.rmem_default = 4194304
net.core.rmem_max = 4194304
net.core.wmem_default = 262144
net.core.wmem_max = 1048576
net.ipv4.ip_forward = 0
net.ipv4.conf.default.rp_filter = 1
tcp.ipv4.tcp_wmem = 262144 262144 262144
tcp.ipv4.tcp_rmem = 4194304 4194304 4194304
fs.aio-max-nr = 1048576
net.ipv4.ip_local_port_range = 9000 65000




Change the parameters according to your environment 




Changing the kernel parameters according to the requirement set the kernel.Shmmax


as to the half of the Physical ram present in your system 






[root@fahtestdb ~]# sysctl -p
net.ipv4.ip_forward = 0
net.ipv4.conf.default.rp_filter = 1
net.ipv4.conf.default.accept_source_route = 0
kernel.core_uses_pid = 1
net.ipv4.tcp_syncookies = 1
fs.file-max = 6815744
kernel.msgmni = 2878
kernel.msgmax = 8192
kernel.msgmnb = 65536
kernel.sem = 250 32000 100 142
kernel.shmmni = 4096
kernel.shmall = 4294967296
kernel.shmmax = 88046829568
kernel.sysrq = 1
net.core.rmem_default = 262144
net.core.rmem_max = 4194304
net.core.wmem_default = 262144
net.core.wmem_max = 1048576
fs.aio-max-nr = 3145728
net.ipv4.ip_local_port_range = 9000 65500
vm.min_free_kbytes = 51200
net.ipv4.tcp_wmem = 262144 262144 262144
net.ipv4.tcp_rmem = 4194304 4194304 4194304



























Posted by





at




No comments:
              
























Labels:
















          

        

          

        

Friday, June 29, 2012


          

        







Requirements for Installing Oracle 11g R2  Fusion Applications Database


















The fusion applications has Four  database [including one optional data ware house database]

In the fusion applications oracle had come up with two database for the OAM[single sign on] and the OID [oracle internet directory]

now the user details are stored in the separate database not in the transnational database which holds the real data

The User's transitional data or stores in the fusion applications database

There is a fourth optional database known as the datawarehoue database for the fusion applications when you are using the fusion applications BI

[1]Fusion applications transaction database



Holds the schema's of the different domains in which all the translation data's are stored



[2]Oracle Identity management 



In the identity management category oracle has two database



[1] OID database which holds the data of the oracle internet directory

[3]OAM database which holds the data of the oracle access mangement





[4]Fusion data warehouse database --- Optional database when you are using Bi with fusion then we need to install this Db



If you are using the BI with the fusion applications then we need to install the fusion data warehouse  database or you can use OTBI which comes along with the fusion applications





It is recommended to go with the three server architecture with out datawarehouse database





Server 1 







Which holds the fusion application database 







Server 2







Which hold's the oracle Identity management database's [OID and OAM] with the IDM web logic middle ware







Server 3







Which holds the fusion applications 







It can be done with the two server arrchicture as we can install the IDM database and the Fusion application database and the IDM web logic in the single server  and fusion applications in the another server







Check the prerequisits for creating the fusion app database and the idm database












1] Create the fully qualified Host name 



login to the root and check the /etc/hosts file for the fully qualified hostname with the IP







[root@fah]# vi /etc/hosts

# Do not remove the following line, or various programs

# that require network functionality will fail.

127.0.0.1            localhost.localdomain localhost

::1                      localhost6.localdomain6 localhost6

<ip number>     fahtestdb.<domain_name>.com fahtestdb







and save the hosts file 







2]Before installing The database conform the O/S archicture 







To know the archicture type uname -a







[root@fah ~]# uname -a

Linux fahtestdb.oasiserp.com 2.6.18-194.el5 #1 SMP Mon Mar 29 22:10:29 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux



here we are using the x86_64 bit archicture system for installing and database 











To know the releease of the linux type  $ lsb_release -id







[root@fah ~]# lsb_release -id

Distributor ID: EnterpriseEnterpriseServer

Description:    Enterprise Linux Enterprise Linux Server release 5.5 (Carthage)







To know the kernal which is installed







[root@fah ~]# uname -r

2.6.18-194.el5







3] Rpm's required for the oracle database in the linux x86-64







These are the rpm's which is mandatory to install the oracle database in the Linux environment  the Rpm version numbers may slightly change according to the Linux version you are using











1] binutils-2.17.50*

2] compat-libstdc++-33-3.2.3-61*

3] elfutils-libelf-*

4]  glibc-2.5-81.el5_8.2.

5] glibc-common-2.5-81.el5_8.2.

6] ksh-20100621-5.el5_8.1

7] libaio-0.3.106-5.x86_64

8] libgcc-4.1.2-52.el5_8.1

9] libstdc++-4.1.2-52.el5_8.1

10]libstdc++44-devel.x86_64



11]glibc-headers-2.5-81.el5_8.2.x86_64



12] sysstat-7.0.2-11.el5.x86_64



13] unixODBC-devel-2.2.11-10.el5



14]unixODBC-2.2.11-10.el5



15]unixODBC-libs-2.2.11-10.el5



16]gcc-c++-4.1.2-52.el5_8.1.x86_64



17]kernel-headers.x86_64



18] glibc-devel-2.5-81.el5_8.2.



19] libgomp-4.4.6-3.el5.1



20] make-3.81-3.el5.x86_64 



21]openmotif22-2.2.3-20

22]openmotif-2.3.1-6.1.el5_8

23]xorg-x11-utils





Query to conform all the rpms are installed 







rpm -qa --queryformat "%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n" | grep <rpm name>







1]   rpm -qa --queryformat "%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n" |grep binuti

binutils-2.17.50.0.6-20.el5_8.3 (x86_64)

binutils-devel-2.17.50.0.6-20.el5_8.3 (i386)

binutils-devel-2.17.50.0.6-20.el5_8.3 (x86_64)

binutils220-2.20.51.0.2-5.29.el5 (x86_64)



2]   rpm -qa --queryformat "%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n" |grep compat-libstdc++

compat-libstdc++-33-3.2.3-61 (x86_64)

compat-libstdc++-33-3.2.3-61 (i386)

compat-libstdc++-296-2.96-138 (i386)



3]   rpm -qa --queryformat "%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n" |grep elfutils-libelf-

elfutils-libelf-devel-0.137-3.el5 (x86_64)

elfutils-libelf-0.137-3.el5 (x86_64)

elfutils-libelf-devel-static-0.137-3.el5 (i386)

elfutils-libelf-0.137-3.el5 (i386)

elfutils-libelf-devel-0.137-3.el5 (i386)

elfutils-libelf-devel-static-0.137-3.el5 (x86_64)



4]   rpm -qa --queryformat "%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n" |grep glibc-2.5-81.el5_8.2

glibc-2.5-81.el5_8.2 (x86_64)

glibc-2.5-81.el5_8.2 (i686)







5]   rpm -qa --queryformat "%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n" |grep glibc-common



glibc-common-2.5-81.el5_8.2 (x86_64)







6]  rpm -qa --queryformat "%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n" |grep ksh

ksh-20100621-5.el5_8.1 (x86_64)



7] rpm -qa --queryformat "%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n" |grep libaio-

libaio-0.3.106-5 (x86_64)

libaio-devel-0.3.106-5 (i386)

libaio-devel-0.3.106-5 (x86_64)

libaio-0.3.106-5 (i386)







8] rpm -qa --queryformat "%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n" |grep libgcc



libgcc-4.1.2-52.el5_8.1 (x86_64)



libgcc-4.1.2-52.el5_8.1 (i386)



compat-libgcc-296-2.96-138 (i386)







9] and [10] rpm -qa --queryformat "%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n" |grep libstdc++



libstdc++-4.1.2-52.el5_8.1 (i386)



libstdc++-devel-4.1.2-52.el5_8.1 (i386)



compat-libstdc++-33-3.2.3-61 (x86_64)



compat-libstdc++-33-3.2.3-61 (i386)



compat-libstdc++-296-2.96-138 (i386)



libstdc++-devel-4.1.2-52.el5_8.1 (x86_64)



libstdc++44-devel-4.4.6-3.el5.1 (x86_64)



libstdc++-4.1.2-52.el5_8.1 (x86_64)



libstdc++44-devel-4.4.6-3.el5.1 (i386)







11] rpm -qa --queryformat "%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n" |grep glibc-headers



glibc-headers-2.5-81.el5_8.2 (x86_64)







12] rpm -qa --queryformat "%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n" |grep sysstat-



sysstat-7.0.2-11.el5 (x86_64)







13] [14] [15]rpm -qa --queryformat "%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n" |grep unixODBC



unixODBC-devel-2.2.11-10.el5 (x86_64)



unixODBC-2.2.11-10.el5 (x86_64)



unixODBC-libs-2.2.11-10.el5 (x86_64)



unixODBC-2.2.11-10.el5 (i386)



unixODBC-libs-2.2.11-10.el5 (i386)



unixODBC-devel-2.2.11-10.el5 (i386)







16] rpm -qa --queryformat "%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n" |grep gcc-c++



gcc-c++-4.1.2-52.el5_8.1 (x86_64)







17] rpm -qa --queryformat "%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n" |grep kernel-headers



kernel-headers-2.6.18-308.8.2.0.1.el5 (x86_64)







18]rpm -qa --queryformat "%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n" |grep glibc-devel



glibc-devel-2.5-81.el5_8.2 (i386)



glibc-devel-2.5-81.el5_8.2 (x86_64)







19] rpm -qa --queryformat "%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n" |grep libgomp



libgomp-4.4.6-3.el5.1 (i386)



libgomp-4.4.6-3.el5.1 (x86_64)







20] rpm -qa --queryformat "%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n" |grep make



make-3.81-3.el5 (x86_64)



21] [22]  rpm -qa --queryformat "%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n" |grep openmotif

openmotif22-2.2.3-20 (x86_64)

openmotif-devel-2.3.1-6.1.el5_8 (x86_64)

openmotif22-2.2.3-20 (i386)

openmotif-devel-2.3.1-6.1.el5_8 (i386)

openmotif-2.3.1-6.1.el5_8 (i386)

openmotif-2.3.1-6.1.el5_8 (x86_64)



23]  rpm -qa --queryformat "%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n" |grep xorg-x11-utils

xorg-x11-utils-7.1-2.fc6 (x86_64)











If any of the rpm's are not installed then use the yum install to install the particular rpm and check again 



for an  example here we have installed the libstdc++* .. like wise you need to install all the rpm's which are not installed  in your environment  for installing the Public yum please check the previous post   http://orafapp.blogspot.com/2012/06/creating-public-yum-repositiry-for.html







For more information Regarding the different versions of operating system requirements refer to the below link

http://docs.oracle.com/html/E18558_01/fusion_requirements.htm#CHDGICGE


Requirements for Installing Oracle 11gR2 RDBMS on RHEL (and OEL) 5 on AMD64/EM64T [ID 880989.1]









4] creating the O/S user and groups for the necessary installation









Here we explained the structure for the two node and the three node arrchicture for the fusion applications 



for three node arch                                                                   For two node arch



server1    [node1]                                                                                Server1 [node1]



fusion database                                                          Fusion database,IDM database's IDMDomain



server2    [node2]                                                                                Server2 [node2]



IDM database's and IDM domain                             Fusion Applications 



server3    [node3]



Fusion applications 









Creating o/s username and group's for the fusion applications database



1] oracle fusion applications database

2]Oracle OID database

3]Oracle Access manager database

  

Creating the Group names

groupadd  oinstall

groupadd  dba
 

we have create two groups know as the oinstall and the dba the oinstall will be the primary group and the dba will be the secondary group for the database's



If you are suing the ASM  create the asm groups



groupadd   asmadmin

groupadd   asmoper

groupadd   asmoper

if you are using the file system ignore this groups



To Create Users for the database



useradd grid         -g   oinstall -G  dba, asmoper, asmadmin ,asmdba  -- [if you are using the asm]

useradd oraidm    -g   oinstall -G  dba       --[IDM database o/s user]

useradd oraoam   -g    oinstall -G  dba       --[OAM database o/s user]

useradd oracle      -g   oinstall -G  dba       --[fusiondb database o/s user]

useradd  fmwidm  -g oinstall -G dba     --[oraweblogic IDM Domain o/s user]

useradd orafapp        -g oinstall -G dba    --[fusion applications username]



The small g is used to specify the primary group of the user and the G is used to specify the Other groups which the user is assigned to 





[root@fa ~]# id oraidm

uid=54322(oraidm) gid=54321(oinstall) groups=54321(oinstall),54322(dba)

[root@fa ~]# id oraoam

uid=54323(oraoam) gid=54321(oinstall) groups=54321(oinstall),54322(dba)





[root@fa ~]# id oracle



uid=54321(oracle) gid=54321(oinstall) groups=54321(oinstall),54322(dba)





[root@fa~]# id grid

uid=54324(grid) gid=54321(oinstall)groups=54321(oinstall),54322(dba),54333(asmadmin),54334(asmdba),54335(asmoper)





If You have the wrong group combinations then use the  usermod command to modify the  user group to match all the remaining users



 usermod -g oinstall -G dba oraoam







5]Creating the Directory and mount to the label and change the owner to the oracle Users 



For creating the directory and mount to the appropriated label please refer to the previous post 



http://orafapp.blogspot.com/2012/06/mounting-partitions-in-oracle-linux.html


http://orafapp.blogspot.com/2012/06/installing-oracle-11gr2-database-in.html






mkdir  /u01/app/oracle -p



mkdir  /u02/app/oracle -p



mkdir  /u03/app/oracle -p



mkdir  /u04/app/oracle -p



There are three directories which is to be owned by the oracle database users here we are going to install three database in the same machine..

and the fourth directory is used to install the IDM Domain



if you are installing with the three servers then you can create only  one directory

/u01/app/oracle in the fusiondb linux box and remaining  three in the IDMbox





chown command is used to change the owner of the particular directory or file



Server 1

[root@fah ~]# chown oracle:oinstall   /u01/app/oracle       --[Installing Location of the Fusionapp db]

[root@fah ~]# chown oraidm:oinstall /u02/app/oracle       --[Installing Location of OID   db]

[root@fah ~]# chown oraoam:oinstall /u03/app/oracle      --[Installing Location of OAM db]



[root@fah ~]# chown orafmw:oinstall /u04/app/oracle      --[Installing Location Of IDM Domain]

Server 2 [for fusion applications installation]

[root@fah ~]#chown orafapp:oinstall  /u05/app/oracle      -- [Installation location of the fusion applications ]







chmod command is used to change the file permissions to the file system 







we have to assign  the write permission to the group for all the user's 









[root@fah]# cd /u01/app



[root@fah]# chmod 765 oracle



[root@fah]# cd /u02/app



[root@fah]# chmod 765 oracle



[root@fah]# cd /u03/app



[root@fah]# chmod 765 oracle



[root@fah]# ll /u0*/app





  



now the owner has the full access read write and execute to the file system and the group had the read and write and other's has read and execute 







6] Open file Limits for the users



To set the open file limits go the /etc/security/limites.conf



Set the open below parameters in the limites .conf we can use the wild card to match multiple users when we are installing the fusion applications 



*     soft     nproc         131072

*     hard     nproc         131072

*     soft     nofile        327679

*     hard     nofile        327679

*     soft     stack         131072







7] Init Parameters for the fusion applications database



[1]  audit_trail                                  string      NONE



Desc :audit trail is set to be none for disable the database auditing



[2]  plsql_code_type                       string      NATIVE



Desc: we need to set the value to the NATIVE PL/SQL library units (with the possible exception of top-level anonymous PL/SQL blocks) will be compiled to native (machine) code. Such modules will be executed natively without incurring any interpreter overhead.



[3]  nls_sort                                    string          BINARY



Desc :Setting NLS_SORT to anything other than BINARY causes a sort to use a full table scan, regardless of the path chosen by the optimizer. BINARY is the exception because indexes are built according to a binary order of keys. Thus the optimizer can use an index to satisfy the ORDER BY clause when NLS_SORT is set to BINARY. If NLS_SORT is set to any linguistic sort, the optimizer must include a full table scan and a full sort in the execution plan Nls_sort is set to Binary for the improved performance of the ORDER BY quires



[4]open_cursors                              integer     1000



Desc: OPEN_CURSORS specifies the maximum number of open cursors (handles to private SQL areas) a session can have at once. You can use this parameter to prevent a session from opening an excessive number of cursors ..no of Cursors open is set to be 500 to 1000 according to you environment



[5]session_cached_cursors               integer     1000





DESC :  Recommended value for the parameter is 500 to 1000 according to the env 

Specifies the number of session cursors to cache. Repeated parse calls of the same SQL statement cause the session cursor for that statement to be moved into the session cursor cache. Subsequent parse calls find the cursor in the cache and do not reopen the cursor. Oracle uses a least recently used algorithm to remove entries in the session cursor cache to make room for new entries when needed.This parameter also constrains the size of the PL/SQL cursor cache that PL/SQL uses to avoid having to re-parse as statements are re-executed by a user





[6] processes                            integer     5000



Desc : The recommended vale for the process is 5000 for fusion database and 2500 for idm database's

Sets the maximum number of operating system processes that can be connected to Oracle concurrently. The value of this parameter must account for Oracle background processes. SESSIONS parameter is deduced from this value

[7]star_transformation_enabled          string      FALSE




Desc recommended value is False Determines whether a cost-based query transformation will be applied to star queries







[8] query_rewrite_integrity              string      enforced





Desc QUERY_REWRITE_INTEGRITY determines the degree to which Oracle must enforce query rewriting. At the safest level, Oracle does not use query rewrite transformations that rely on unenforced relationships.

Determines whether a cost-based query transformation will be applied to star queries

we need to set the value as Enforced  as it  guarantees consistency and integrity





[9]parallel_max_servers                 integer     640



Desc :PARALLEL_MAX_SERVERS specifies the maximum number of parallel execution processes and parallel recovery processes for an instance. As demand increases, Oracle increases the number of processes from the number created at instance start up up to this value. we need to specify the value as 640 in the fusion applications  



[10] job_queue_processes                  integer     100



Desc Specifies the maximum number of job slaves per instance that can be created for the execution of DBMS_JOB jobs and Oracle Scheduler (DBMS_SCHEDULER) jobs the recommended value is 10 to 100









[11]_b_tree_bitmap_plans                 boolean     FALSE







Desc we need to set the value as false we are setting to false for the improved performance with the sql quries







[12]_fix_control                         string      5483301:OFF, 6708183:ON







Desc we need to specify the two values one is OFF and another is ON







[13] sga_target                           big integer 18







Desc The suggested value for an Oracle Fusion Applications Starter database is 9 GB







[14]pga_aggregate_target                 big integer 8G







Desc The suggested value for an Oracle Fusion Applications Starter database is 4 GB


































Posted by





at




9 comments:
              
























Labels:






















Creating the Public Yum repositiry for Oracle Linux 5















   







To Create the Public yum please we need to use the wget option to get the .repo file from internet .. so please check the net connection before running the command





[root@fahtestdb ~]# cd /etc/yum.repos.d

[root@fahtestdb yum.repos.d]# ls

[root@fahtestdb yum.repos.d]# wget http://public-yum.oracle.com/public-yum-el5.repo

--2012-06-30 01:01:03--  http://public-yum.oracle.com/public-yum-el5.repo

Resolving public-yum.oracle.com... 141.146.44.34

Connecting to public-yum.oracle.com|141.146.44.34|:80... connected.

HTTP request sent, awaiting response... 200 OK

Length: 3974 (3.9K) [text/plain]

Saving to: `public-yum-el5.repo'



100%[==============================================================================================================================>] 3,974       --.-K/s   in 0.001s



2012-06-30 01:01:06 (4.58 MB/s) - `public-yum-el5.repo' saved [3974/3974]







By using the Public Yum we can install the necessry packages through the internet from the Oracle repository Servers



[root@fahtestdb yum.repos.d]# yum install vnc*

Loaded plugins: security

el5_latest                                                                                                                                       | 1.1 kB     00:00

el5_latest/primary                                                                                                                               | 9.4 MB     00:37

el5_latest                                                                                                                                                    9130/9130

Setting up Install Process

Resolving Dependencies

--> Running transaction check

---> Package vnc.x86_64 0:4.1.2-14.el5_6.6 set to be updated

---> Package vnc-server.x86_64 0:4.1.2-14.el5_6.6 set to be updated

--> Finished Dependency Resolution



Dependencies Resolved



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

 Package                                Arch                               Version                                         Repository                              Size

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

Updating:

 vnc                                    x86_64                             4.1.2-14.el5_6.6                                el5_latest                             159 k

 vnc-server                             x86_64                             4.1.2-14.el5_6.6                                el5_latest                             2.0 M



Transaction Summary

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

Install       0 Package(s)

Upgrade       2 Package(s)



Total download size: 2.2 M

Is this ok [y/N]: Y

Downloading Packages:

(1/2): vnc-4.1.2-14.el5_6.6.x86_64.rpm                                                                                                           | 159 kB     00:00

(2/2): vnc-server-4.1.2-14.el5_6.6.x86_64.rpm                                                                                                    | 2.0 MB     00:32

------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Total                                                                                                                                    64 kB/s | 2.2 MB     00:34

warning: rpmts_HdrFromFdno: Header V3 DSA signature: NOKEY, key ID 1e5e0159

el5_latest/gpgkey                                                                                                                                | 1.4 kB     00:00

Importing GPG key 0x1E5E0159 "Oracle OSS group (Open Source Software group) <build@oss.oracle.com>" from http://public-yum.oracle.com/RPM-GPG-KEY-oracle-el5

Is this ok [y/N]: Y

Running rpm_check_debug

Running Transaction Test

Finished Transaction Test

Transaction Test Succeeded

Running Transaction

  Updating       : vnc-server                                                                                                                                       1/4

  Updating       : vnc                                                                                                                                              2/4

  Cleanup        : vnc-server                                                                                                                                       3/4

  Cleanup        : vnc                                                                                                                                              4/4



Updated:

  vnc.x86_64 0:4.1.2-14.el5_6.6                                                   vnc-server.x86_64 0:4.1.2-14.el5_6.6



Complete!

[root@fahtestdb yum.repos.d]#











Posted by





at




No comments:
              
























Labels:






















Formating the partition to the Linux file System
















Formating the raw partitions in Oracle linux 5.5







mkfs.ext3 is the command to format the partition in Oracle linux 6 and above you can use the mkfs.ext4 because the version 6 and above use's the ext4 file system



[root@fahtestdb ~]# mkfs.ext3 /dev/sdc1

mke2fs 1.39 (29-May-2006)

Filesystem label=

OS type: Linux

Block size=4096 (log=2)

Fragment size=4096 (log=2)

19906560 inodes, 39792997 blocks

1989649 blocks (5.00%) reserved for the super user

First data block=0

Maximum filesystem blocks=4294967296

1215 block groups

32768 blocks per group, 32768 fragments per group

16384 inodes per group

Superblock backups stored on blocks:

        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,

        4096000, 7962624, 11239424, 20480000, 23887872



Writing inode tables: done

Creating journal (32768 blocks): done

Writing superblocks and filesystem accounting information: done



This filesystem will be automatically checked every 28 mounts or

180 days, whichever comes first.  Use tune2fs -c or -i to override



Partition all the raw file system to the O/S file system to Mount the partition to the Lable













Posted by





at




No comments:
              
























Labels:
















        

      









Subscribe to:
Posts (Atom)