welcome to Oracle Solaris Solutions

Solaris 10 Account Lockout ("Three Strikes!")

2011-12-25T10:04:00.001-08:00

The next item of my list of lesser known and/or publicized security enhancements to the Solaris 10 OS is account lockout. Account lockout is the ability of a system or service to administratively lock an account after that account has suffered "n" consecutive failed authentication attempts. Very often "n" is three hence the "three strikes" reference.

Account lockout can be enabled in one of two ways. The first way will enable account lockout globally for all users. The second method will all more granular control of which users will or will not be subject to account lockout policy.Note that the account lockout capability will only apply to accounts local to the system. We will look at both in a little more detail below.

Before we look at how to enable or disable the account lockout policy, let's first take a look at how you configure the number of consecutive, failed authentication attempts that will serve as your line in the sand. Any number of consecutive, failed attempts beyond the number selected will result in the account being locked. This number is based on the RETRIES parameter in the /etc/default/login file. By default, this parameter is set to 5. You can certainly customize this parameter based on your local needs and policy. By default, the Solaris Security Toolkit will set theRETRIES parameter to 3.

Now that we know how to define how many consecutive, unsuccessful authentication attempts we will allow, let's take a look at how you can enable the account lockout policy globally. This policy can be altered using theLOCK_AFTER_RETRIES variable in the /etc/security/policy.conf file. Just as it sounds, if you set this parameter toYES, then the account lockout policy is enabled for all users on the system (unless there is a user override which we will talk about in a minute). By default, this parameter is set to NO which means that account lockout is not enabled.

So, let's try a simple example. First, I created a test account called gmb. Next, I set the LOCK_AFTER_RETRIESparameter in /etc/security/policy.conf to YES. To see, how this feature works, I attempted to authenticate to a system (and failed) using three different services:(1) TELNET, (2) FTP and (3) RLOGIN. I failed the login attempt for each of these services (in turn) twice with the exception of RLOGIN since after the fifth failed attempt the account was locked. I ran this test from the system's console so that the log messages could be injected into the output stream to give you a better idea of what was happening. Here is the actual log of the test that was run:

# telnet localhost
Trying 127.0.0.1...
Connected to localhost.
Escape character is '\^]'.
login: gmb
Password:
Login incorrect
login: gmb
Password:
Login incorrect
login: 
Connection to localhost closed by foreign host.
# ftp localhost
Connected to localhost.
220 sampleHost FTP server ready.
Name (localhost:root): gmb
331 Password required for gmb.
Password:
530 Login incorrect.
Login failed.
ftp> user gmb
331 Password required for gmb.
Password:
530 Login incorrect.
Login failed.
ftp> quit 221 Goodbye.
# rlogin -l gmb localhost Password:
Sep 23 23:23:47 sampleHost login: Excessive (5) login failures for gmb: locking account. Login incorrect
login:

As you can see, after the fifth attempt, the gmb account was locked. This can also be verified by looking at the shadow(4) file entry for that account:

# grep "\^gmb:" /etc/shadow
gmb:\*LK\*R12OfCMPngtJQ:12685::::::5

You can see that the account has been locked and that a record of the number of failures is available in the last column. From the shadow(4) manual page, the last field (called "flag") stores the failed login count in the low order four bits while reserving the remainder for future use. This means that you can also look at individual shadow(4) entries and see how many consecutive failed authentication attempts have been made per user. For example, you could do the following to see how many users have had failed authentication attempts since their last successful login:

# awk -F: '$NF >= 1 { print; }' /etc/shadow
gmb:\*LK\*R12OfCMPngtJQ:12685::::::5
foo:02YZb5ZaMrcrk:12685::::::2
bar:XF0Ggjq1c6tYQ:12685::::::1
baz:.VxOG4ytNE8es:12685::::::3

If a user who has had failed authentication attempts is finally able to successfully login to the system, that user will be presented with a message like:

# telnet localhost
Trying 127.0.0.1...
Connected to localhost.
Escape character is '\^]'.
login: baz
Password:
Warning: 3 failed login attempts since last successful login.
Last login: Thu Sep 23 23:36:44 from localhost

This warning message is available for interactive login services (not FTP) and is very helpful in providing warning to users who may not have been responsible for the failed authentication attempts. It is important that you educate your users to not simply ignore these messages as they could be a symptom of an ongoing attack on their account.

Also, note that once a user has successfully authenticated to a system, the failed login count is reset:

# grep "\^baz" /etc/shadow
baz:.VxOG4ytNE8es:12685::::::

Note that the use of alternate authentication mechanisms such as rhosts or Secure Shell public key authentication will not reset the failed login count even on successful login. Should an account be locked however (either administratively or through the account lockout facility), the account would no longer be accessible even when using these alternate authentication methods. For example:

# grep gmb /etc/shadow
gmb:\*LK\*R12OfCMPngtJQ:12685::::::
# rsh -l gmb localhost /bin/finger
account expired

or for Secure Shell...

# ssh -l gmb -i /export/home/gmb/.ssh/id_dsa localhost
Enter passphrase for key '/export/home/gmb/.ssh/id_dsa':
Sep 24 00:34:59 sampleHost sshd[1504]: Failed publickey for gmb from 127.0.0.1 port 32801 ssh2
Password:

The second way in which account lockout can be configured is per-user in the /etc/user_attr file. Each user listed in the /etc/user_attr file can have an attribute defined called lock_after_retries. For a description of the format of this file, see the user_attr(4) manual page. By default, this value is set to no.

To configure account lockout for a specific user, simply add the lock_after_retries attribute with a value of yes. For example, let's assume you have an entry for user gmb:

gmb::::type=normal;profiles=FOO Security Management;roles=secadm

To enable account lockout, you simple change the above line to:

gmb::::type=normal;profiles=FOO Security Management;roles=secadm;lock_after_retries=yes

Let's take another view on this. Let's assume that the account lockout policy has been enabled globally using the method described above. You can then configure some users to be immune to this policy using this user-specific override. For example, if the LOCK_AFTER_RETRIES parameter was set to YES in /etc/security/policy.conf, but you did not want the policy to apply to the gmb account, then you only need to make sure that the /etc/user_attr file contains an entry for the gmb account that sets the lock_after_retries attribute to no as in:

gmb::::lock_after_retries=no

Here is an example of how this works. I will attempt to access the gmb account with an invalid password five times using TELNET. In contrast to the above example, the account should not be locked and no account locked message should be generated. First, let's confirm we have our system configured correctly for this test:

# grep "\^gmb:" /etc/shadow
gmb:h8HsRoqrne1oQ:12685::::::::::
# grep "\^gmb:" /etc/user_attr
gmb::::lock_after_retries=no
# grep "\^LOCK_AFTER_RETRIES=" /etc/security/policy.conf
LOCK_AFTER_RETRIES=YES

Now, let's see if the account actually gets locked after 5 failed authentication attempts.

# telnet localhost
Trying 127.0.0.1...
Connected to localhost.
Escape character is '\^]'.
login: gmb
Password:
Login incorrect
login: gmb
Password:
Login incorrect
login: gmb
Password:
Login incorrect
login: gmb
Password:
Login incorrect
login: gmb
Password:
Login incorrect
Sep 23 23:51:46 sampleHost login: REPEATED LOGIN FAILURES ON /dev/pts/1 FROM localhost, gmb
Connection to localhost closed by foreign host.
# grep "\^gmb:" /etc/shadow
gmb:h8HsRoqrne1oQ:12685::::::

Just as expected, the gmb account is immune from the account lockout policy that applies to other users on the system. This is in fact what is implemented by default for the root account. That is, even if account lockout is enabled globally (which is not the default), the root account is still immune from being locked out. This is done to prevent a malicious user from locking the root account out of the system. If you would like this policy to apply to the rootaccount, then simply change the value of the lock_after_retries parameter to yes in the /etc/user_attr file.

This concludes another installment. As always, I hope you find this information useful in understanding how some of the new Solaris 10 security enhancements work and how they can be applied to solve real-world problems in your environment.

Solaris Network configuration

2011-12-24T11:27:00.001-08:00

Setting up Solaris networking often becomes challenging for the new sysadmins and new owners of Sun systems . This document details the steps involved in setting up of Solaris networking and can be used as a check list if you are already familiar with Solaris network configuration .

Table of contents :
1. Enable the network card
2. Configuring ipaddress and netmask and making the interface status as up .
3. Configuring Virtual interface :
4. Ip-forwarding
5. Router Configuration
6. Network Terms
7. Next Steps

Ifconfig command is used in Solaris to configure the network interfaces . The following lines describes the activities needed to configure a freshly installed network card from the root prompt .

1. Enable the network card
#ifconfig hme0 plumb

ifconfig -a command should show following type of output which means device is enabled and is ready to configure ip address and netmask :

hme0: flags=842 mtu 1500
inet 0.0.0.0 netmask 0
ether 3:22:11:6d:2e:1f

2. Configuring ipaddress and netmask and making the interface status as up .

#ifconfig hme0 192.9.2.106 netmask 255.255.255.0 up

#ifconfig -a will now show the ip address , netmask and up status as follows :

hme0: flags=843 mtu 1500
inet 192.9.2.106 netmask ffffff00 broadcast 192.9.2.255
ether 3:22:11:6d:2e:1f

The file /etc/netmasks is used to define netmasks for ip addresses .

127.0.0.1, is the standard loop back route and 127.0.0.0 is the default loopback ipaddress used by the kernel when no interface is configured this will be the only entry displayed by the system on invoking ifconfig -a command..

3. Configuring Virtual interface
Virtual interface can be configured to enable hme0 reply to more then one ip addresses. This is possible by using hme0 alias which can be configured by ifconfig command only . The new alias device name now becomes hme0:1 hme:2 etc.

#ifconfig hme0:1 172.40.30.4 netmask 255.255.0.0 up

ifconfig -a will show the original hme0 and alias interface :

hme0: flags=843 mtu 1500
inet 192.9.2.106 netmask ffffff00 broadcast 192.9.2.255
ether 3:22:11:6d:2e:1f
hme0:1: flags=842 mtu 1500
inet 172.40.30.4 netmask ffff0000 broadcast 172.40.255.255

4. Ip-forwarding
IP forwarding allows you to forward all requests coming for a certain port or URL to be redirected to a specified IP address.
ip forwarding becomes enabled automatically when system detects more then one interface at the booting time . The file involved is /etc/rc2.d/S69inet .
ipforwarding is on by default but can be turned off by following command :

#ndd -set /dev/ip ip_forwarding 0

5. Router Configuration
After interfaces and ipaddess have been configured the system needs a default router which will allow the machine to talk to world outside of local network .
You can specify a particular route for a particular address as in following example

#route add -net 10.0.0.0 -netmask 255.0.0.0 172.40.30.1 1

if the the destination ipaddess is not defined in this manner system forwards all requests to the default router .
default route is defined manually by editing /etc/defaultrouter file and putting router’s ipaddress entry in it. This file is read by /etc/rc2.d/S69inet file during the booting process and entry added to the routing table .
The route can be defined online also using routeadd command but the changes will be lost on reboot .To make changes permanent make sure to put an entry in /etc/defaultrouter.

#route add default 205.100.155.2 1
#route change default 205.100.155.2 1

The 1 at the end is the number of hops to the next gateway.

If an interface is not responding to the network, check to be sure it has the correct IP address and netmask , network cables are fine .

6. Network Terms
CIDR
CIDR : Classless Inter-Domain Routing – the notation often used instead of writing the subnet mask along with ip-address . It has network prefix at the end of a address as / number of network bits.This means that the IP address 192.200.20.10 with the subnet mask 255.255.255.0 can also be expressed as 192.200.20.10/24. The /24 indicates the network prefix length, which is equal to the number of continuous binary one-bits in the subnet mask (11111111.11111111.11111111.000000). Zeros are for addressing the hosts on this network.

VLSM
network can be variably subnetted into smaller networks, each smaller network having a different subnet mask .This functionality is avaiable in Solaris 2.6 above. the ipaddresses

Solaris: How to Share Folder ?

2011-10-21T04:02:00.000-07:00

Servers: Indapp001 and Usaapp002
To do: To mount “/export/home” of Indapp001 on Usaapp002.
Issue the following commands on Indapp001:
1. Share the required file system “/export/home” of Indapp001.
Start the nfs server on Indapp001.
# svcadm enable network/nfs/server
2. Share the “/export/home” of Indapp001 for everyone on the network.
#share -F nfs -o rw -d “home dirs” /export/home
Issue the following commands on Usaapp002:
3. From Usaapp002 check which files are shared on Indapp001 for NFS mount.
# showmount -e Indapp001
export list for Indapp001:
/export/home (everyone)
4. Create mount point on Usaapp002 “t2”
#mkdir /t2
5. Mount file system of Indapp001 “/export/home” on Usaapp002
# mount Indapp001:/export/home /t2
6. Checked the mounted file system by issuing the “df -h” command:
# df -h /t2
Filesystem size used avail capacity Mounted on
Indapp001:/export/home
29G 3.1G 25G 11% /t2
#

Regards.

What is Sun Ray ?

2011-10-15T11:41:00.000-07:00

This Video Will do it all !!!

In contrast to a thick client, the Sun Ray is a networked display device, with applications running on a server elsewhere, and the state of the user's session being independent of the display. This enables another notable feature of the Sun Ray, portable sessions: a user can go from one Sun Ray to another and continue their work without closing any programs. With a smartcard, all the user has to do is slip in the card, enter their password when prompted, and they will be presented with their session. Without the smartcard, the procedure is almost identical, except the user must specify their username as well as password to get their session. In either case, if a session does not yet exist, a new one will be created the first time they connect.

Sun Ray clients are connected via an Ethernet network to the Sun Ray Server. Sun Ray Server Software (SRSS) is available for the Solaris Operating System and Linux. Sun developed a separate network display protocol, Appliance Link Protocol (ALP), for the Sun Ray system.

Best Regards.

Oracle Cloud Computing (part1)

2011-09-24T20:28:00.001-07:00

Cloud computing is a significant advancement in the delivery of information technology and services.

By providing on demand access to a shared pool of computing resources in a self-service, dynamically

scaled and metered manner, cloud computing offers compelling advantages in speed, agility and

efficiency. Today, cloud computing is

at an early stage in its lifecycle, but it is also the evolution and

convergence of several trends that have been driving enterprise data centers and service providers over

the last several years.

Cloud computing builds off a foundation of technologies such as grid computing, which includes

clustering, server virtualization and dynamic provisioning, as well as SOA shared services and large-

scale management automation. For the better part of a decade, Oracle has been the leader in these

areas with thousands of customer successes and high level of investment. Today, Oracle offers the

industry’s most complete, open and integrated products and services to enable public, private and

hybrid clouds.

Oracle aims to make cloud computing fully enterprise-grade and supports both public and private

cloud computing to give customers choice. Oracle offers technology that enables organizations to

build private clouds, leverage public clouds and provide cloud services to others. Oracle also offers a

broad set of horizontal and industry applications that run in a shared services private cloud model as

well as a public Software-as-a-Service (SaaS) cloud model.

This white paper provides an overview of Oracle’s cloud computing strategy and how Oracle helps

customers and partners plan their evolution and adoption of a cloud computing model.

Installing and Configuring Oracle Database 10g on the Solaris Platform

2010-12-29T12:48:00.000-08:00

Introduction
This paper will walk you through the steps of installing Oracle Database 10g release 1 (Oracle version 10.1.0) in a Sun Solaris SPARC environment. About 90% of the material presented here applies to other platforms as well. Everything you read in this paper is hands on, roll-up-your-sleeves-and-get-busy material for Oracle users who want to get an Oracle database up and running quickly without reading hundreds of pages of documentation and “readme” files.

These steps are meant to get you up and running as fast as possible, while leveraging best practices in order to set up a scalable, robust database environment that offers high performance. In order to keep the steps reasonably simple this paper does not cover Real Application Clusters (RAC), nor does it cover Oracle Internet Directory (OID), Automatic Storage Management (ASM), or Grid Control.

In this paper we will install the 10.1.0.4 release of Oracle Database 10g. This is the base distribution of Oracle Database 10g release 1 (10.1.0.2) with the 10.1.0.4 patch set applied on top. For this paper we ran our Oracle installations on Sun servers with SPARC processors running Solaris 8.

There are four phases to getting Oracle up and running on your server:

Prepare the server
Install the Oracle software and latest patch set
Create a database
Complete the server configuration
We will walk through these phases one at a time, detailing all the steps involved. The end result will be a very usable database that can be scaled up quite large, and an Oracle installation that follows industry-recognized best practices. Of course, every implementation is unique, and you will need to evaluate each step carefully against your particular requirements. However, this paper will get you off to a very solid start.
Prepare the Server

These steps configure your database server so that it will be ready to accept the Oracle software and database. In this section, we will make sure your server meets Oracle’s minimum requirements, create a Unix user and group to “own” the software, and create some directories that will be used by the Oracle software and database. All of the steps in this section are run as the root user.

Make sure that your operating system platform is certified by Oracle Corporation for use with Oracle Database 10g. The 64 bit versions of Solaris 8, 9, and 10 for SPARC are certified for use with Oracle Database 10g, while the 32 bit versions are not. Some special steps and an extra Oracle patch are required to run Oracle Database 10g release 1 with Solaris 10. (These are detailed in

Metalink bulletin 169706.1 and will be listed in the next step.) Solaris x86 is a different platform and is not covered in this paper.

You can verify your operating system version and see whether it is the 32 or 64 bit version with the following commands:

$ uname -a
$ /bin/isainfo -kv
Make sure that your Solaris system has all of the required operating system patches installed. If you are running Solaris 8 or 9, the patch requirements are as follows:
Patches for Solaris 8
108528-23: SunOS 5.8: kernel update patch
108652-66: X11 6.4.1: Xsun patch
108773-18: SunOS 5.8: IIIM and X I/O Method patch
108921-16: CDE 1.4: dtwm patch
108940-53: Motif 1.2.7 and 2.1.1: Runtime lib. patch for Solaris 8
108987-13: SunOS 5.8: Patch for patchadd and patchrm
108989-02: /usr/kernel/sys/acctctl & /.../exacctsys patch
108993-18: SunOS 5.8: LDAP2 client, libc, libthread ... lib. patch
109147-24: SunOS 5.8: linker patch
110386-03: SunOS 5.8: RBAC Feature Patch
111023-02: SunOS 5.8: /kernel/fs/mntfs and ... sparcv9/mntfs
111111-03: SunOS 5.8: /usr/bin/nawk patch
111308-03: SunOS 5.8: /usr/lib/libmtmalloc.so.1 patch
111310-01: SunOS 5.8: /usr/lib/libdhcpagent.so.1 patch
112396-02: SunOS 5.8: /usr/bin/fgrep patch
111721-04: SunOS 5.8: Math Library (libm) patch
112003-03: SunOS 5.8: Unable to load fontset in 64-bit Solaris 8 iso-1 or iso-15
112138-01: SunOS 5.8: usr/bin/domainname patch
Patches for Solaris 9
112233-11: SunOS 5.9: Kernel Patch
111722-04: SunOS 5.9: Math Library (libm) patch
You can see if a specific patch has been installed with the following command:

$ /usr/sbin/patchadd -p | grep
You may download necessary Solaris patches from http://sunsolve.sun.com. The revision numbers on the required patches listed above are minimums—you may install a newer version of a patch than what is listed here. For example, patch 108940-53 is required for Solaris 8, but installing patch 108940-65 instead is allowed.
If you are running Solaris 10, no specific operating system patches are required. However, special extra steps are required during the installation process. See Metalink bulletin 169706.1 for details, but the basic points of interest are as follows:

When running the Oracle Installer, run the runInstaller script with the -ignoreSysPrereqs option.
During installation, the warning message 'SUNWsprox package not installed' can be ignored. Click Continue to resume the installation when this message appears.
The following line must be added to the instance parameter file for the Oracle database:
_enable_NUMA_optimization=FALSE
You will need to download and install Oracle patch 4163208 from http://metalink.oracle.com.
If you have an End User Solaris 10 distribution, install the SUNWuiu8 package prior to installing the Oracle Database 10g client.
Make sure that the following software packages have been installed.
Required Packages
SUNWarc
SUNWbtool
SUNWhea
SUNWlibm
SUNWlibms
SUNWsprot
SUNWtoo
SUNWi1of
SUNWxwfnt
SUNWi1cs
SUNWsprox
SUNWi15cs
You can use the following command to verify that a package has been installed:

$ pkginfo -i
You will need to perform the installation from an X window environment—you cannot use a character mode environment such as a telnet or SSH session. There is a facility for performing non-interactive installations (“silent” installs), but we won’t be covering that technique here. Your X environment can be the console on the database server, but it does not need to be. You can also use a Windows X emulator like Cygwin. If the database server is in a remote location, you can use SSH to securely forward X traffic from the database server back to your desktop. I ran the installation from a Windows desktop using Cygwin and had no problems
The following executables must be present in /usr/ccs/bin: make, ar, ld, nm.
Make sure that your hardware is sufficient. You’ll need at least 512 Mb RAM, a swap space at least twice the size of physical memory (less swap space is okay if you have 2 Gb or more of RAM), and a bare minimum of 2.7 Gb of disk space. This will let you perform a “typical” Enterprise or Standard Edition software installation from CD ROM and create a starter database. If you will be downloading the Oracle software from http://otn.oracle.com, you will need about 1.4 Gb of additional disk space to stage and unpack the Oracle software. A production implementation will almost always require more RAM and more disk space than the minimums listed here. The following commands will allow you to check physical memory and swap space (blocks of swap space are 512 bytes each):
$ /usr/sbin/prtconf | grep size
$ /usr/sbin/swap -l
The Oracle installer will need access to a directory with at least 400 Mb of free space for writing temporary files during installation. Usually /tmp serves this purpose. If /tmp on your database server has less than 400 Mb of free space, then you will need to locate another directory with sufficient free space for use during the installation.
Make sure that the Solaris kernel has parameters set sufficiently high for Oracle. The Oracle architecture makes extensive use of shared memory segments for sharing data among multiple processes and semaphores for handling locking. Many operating systems, including Solaris, do not by default offer sufficient shared memory or semaphores for maintaining an Oracle database. Happily, you can change kernel parameters in Solaris simply by editing the /etc/system file and rebooting the server.
Kernel Parameter Setting To Get
You Started Purpose
SHMMAX 4294967295 Maximum size of a single shared memory segment
SHMMIN [1] 1 Minimum size of a single shared memory segment
SHMMNI 100 Maximum number of shared memory segments in entire system
SHMSEG [1] 10 Maximum number of shared memory segments one process can attach
SEMMNS 1024 Maximum number of semaphores in entire system
SEMMSL 256 Maximum number of semaphores per set
SEMMNI 100 Maximum number of semaphore sets in entire system
SEMVMX 32767 Maximum allowed semaphore value
NOEXEC_USER_STACK [1] 1 Disable certain types of stack buffer overflow exploits
[1] Applies to Solaris 8 only.

The first four kernel parameters configure shared memory segments. The recommended settings shown here should be appropriate for almost any Oracle database implementation. The SHMMAX setting may seem excessive, but there is no penalty for setting SHMMAX larger than you actually need.

The next four kernel parameters configure semaphores. Each Oracle instance requires one semaphore for each process, plus ten extras. Additionally, the largest instance requires a second semaphore for each process. If you will only be setting up one database on your server, the upshot is that you will need two semaphores for each process plus ten extras.

The recommended settings for the first two semaphore kernel parameters, SEMMNS and SEMMSL, should be appropriate for most Oracle implementations. For systems with large numbers of concurrent database connections, you may need to increase these values. The recommended setting shown here for SEMMNI and SEMVMX should be appropriate for just about any Oracle database implementation.

Note that these recommended settings assume you have no other applications running on the database server that use shared memory segments or semaphores. You can view current shared memory and semaphore usage on your system with the following command:

$ ipcs -Ams
In general, if your Solaris kernel already has any of these parameters set larger than recommended here, you should not reduce the settings. If you do change any kernel parameter settings in /etc/system, then reboot the server so that the new settings will take effect.

I added the following lines to the end of my /etc/system file:

set shmsys:shminfo_shmmax=4294967295
set shmsys:shminfo_shmmin=1
set shmsys:shminfo_shmmni=100
set shmsys:shminfo_shmseg=10
set semsys:seminfo_semmns=1024
set semsys:seminfo_semmsl=256
set semsys:seminfo_semmni=100
set semsys:seminfo_semvmx=32767
set noexec_user_stack=1
Create a Unix group that will be used by the Oracle software owner and database administrators. You can call it anything you like, but the standard is “dba”. Anybody who logs onto the database server with a Unix login that belongs to this group will be able to log onto all databases that run from this Oracle software installation with DBA privileges. If you will be installing Oracle on multiple servers on your network, you might want to keep the groupid the same on all servers. You can create your dba group with a command like:
$ groupadd -g 300 dba
If you will be installing multiple copies of the Oracle software on one database server and you will want some Unix logins to be able to log onto some databases with DBA privileges but not others, then you will need to create a different “dba” group for each Oracle software installation. In that case you will also need to create one additional Unix group called “oinstall”. You can create the oinstall group with a command like:
$ groupadd -g 301 oinstall
Remember, you do not need to create an oinstall Unix group if you will only be installing one Oracle software installation on the database server, or if all of the Oracle software installations will share the same dba group.
Create a Unix user that will be the Oracle software owner. You can call it anything you like, but the standard is “oracle”. If you will be installing Oracle on multiple servers on your network, you might want to keep the userid the same on all servers. Note that this user’s home directory will not be the ORACLE_HOME or where the actual Oracle software is installed; this user’s home directory should be in the same place as other users’ home directories.
The group affiliations for this user will depend on whether or not you created an oinstall Unix group in the previous step. If you did not create an oinstall group, then you should make dba the primary group for the oracle user. In this case, you can create your oracle user with commands like:

$ useradd -c 'Oracle software owner' -d /home/oracle \
-g dba -m -u 300 -s /usr/bin/ksh oracle
$ passwd oracle
If you did create an oinstall group in the previous step, then you should make oinstall the primary group for the oracle user and dba a secondary group. In this case, you can create your oracle user with commands like:
$ useradd -c 'Oracle software owner' -d /home/oracle \
-g oinstall -G dba -m -u 300 -s /usr/bin/ksh oracle
$ passwd oracle
The useradd commands shown here give your oracle user the Korn shell. You could just as easily choose Bash or Bourne instead.
Create mount points for the Oracle software and the Oracle database. Each mount point should correspond to a separate physical device or set of devices. You’ll need at least one mount point. Typically you use one mount point for the Oracle software and one or more mount points for each database. One common convention is to call the mount points /u01, /u02, and so on. Because mount points are typically owned by root and the Oracle installer will run as the oracle user and not as root, you should create some subdirectories now to avoid permission problems later. Create an app/oracle subdirectory below the software mount point, and oradata subdirectories below the mount points to be used for database files. (You can put software and a database on the same mount point if you wish.) Make these subdirectories owned by the oracle user and dba group (or oinstall group if you are going that route), and give them 775 permissions. You can use commands like:
$ mkdir /u01/app /u01/app/oracle /u01/oradata
$ chown oracle:dba /u01/app /u01/app/oracle /u01/oradata
$ chmod 775 /u01/app /u01/app/oracle /u01/oradata
If you downloaded the Oracle software off of the Internet, then use gunzip and cpio to unpack the distribution. Use commands like:
$ gunzip ship_rel10_sol64_db.cpio.gz
$ cpio -idm < ship_rel10_sol64_db.cpio
If you have the software on CD ROM, then mount the Oracle Database 10g CD ROM now.
Create the /var/opt/oracle directory and make it owned by the oracle user. After installation, this directory will contain a few small text files that briefly describe the Oracle software installations and databases on the server. These commands will create the directory and give it appropriate permissions:
$ mkdir /var/opt/oracle
$ chown oracle:dba /var/opt/oracle
$ chmod 755 /var/opt/oracle
Install the Oracle Software and Latest Patch Set
These steps install the Oracle software and latest patch set on your server. As of this writing, Oracle release 10.1.0.2 is the only version of Oracle Database 10g release 1 (for Solaris SPARC) available for download from Oracle Technology Network or on CD ROM. However, the current patch set is 10.1.0.4. Therefore, we will install Oracle release 10.1.0.2 and apply patch set 10.1.0.4 on top of the installation. Before proceeding with the steps in this section, you should check Oracle Technology Network (http://otn.oracle.com) and Oracle Metalink (http://metalink.oracle.com) to see if any newer releases and/or patch sets are available.

The Oracle Universal Installer will suggest creating a database at the same time that it installs the Oracle software. It will be better to hold off on database creation until after the latest patch set has been applied—this will allow us to avoid having to patch the newly created database when installing the patch set.

In this section, we will prepare the oracle Unix user’s environment, run the Oracle Universal Installer twice (once to install the base release and once to install the latest patch set), and tidy up a few minor loose ends. All of the steps in this section, except where noted, are run as the oracle user.

Edit the oracle user’s login file on the database server so that the environment will be configured automatically on login. If you are using Bourne or Korn shell, then edit .profile. If you are using Bash shell, then edit .bash_profile. You can also use C shell and edit .cshrc, but the syntax will be different from the examples you see here. For now, we will hardcode certain things. But after we create a database, we will come back and eliminate all hardcodings. Here is what I added to my .profile for the install:
umask 022
#
# Substitute your Oracle software mount point in the line below.
export ORACLE_BASE=/u01/app/oracle
#
# Ensure that ORACLE_HOME and TNS_ADMIN are not set.
unset ORACLE_HOME
unset TNS_ADMIN
#
# If your /tmp directory has less than 400 Mb free, then edit
# and uncomment the following three lines.
# TEMP=/mount_point_with_400_mb_free
# TMPDIR=/same_mount_point
# export TEMP TMPDIR
#
# The documentation does not mention how PATH should be set.
# The following PATH setting worked for me:
export PATH=/usr/bin:/usr/local/bin:/usr/ccs/bin
Log out and log back in as the oracle user from an X window so that the environment is set correctly. If you will be performing the installation from a PC or other workstation instead of using the database server’s console directly, you may wish to forward X window traffic over an SSH connection. This offers increased security (in the case of a public network) and convenience. If you will be performing the installation from a Windows PC, you can use PuTTY to forward your X window traffic by selecting the “Enable X11 forwarding” checkbox in PuTTY’s SSH Tunnels configuration screen.
Make sure your DISPLAY variable is set. If you are forwarding X window traffic over an SSH connection or working from the server’s console directly, the DISPLAY variable will probably already be set for you. If your DISPLAY variable has not been set already, then you will need to set it manually to the IP address of your X server plus the X server and screen numbers. You can set your DISPLAY variable with a command like:
$ export DISPLAY=myworkstation:0.0
If you are not using the console of the database server or forwarding X window traffic over an SSH connection, then ensure that the X server on your workstation will allow your database server to open windows on your display. The easiest way to do this is to issue an xhost command from a session on your workstation. (Don’t get confused and issue the command in a window that is logged onto your database server.) You can issue a command like:
$ xhost +mydatabaseserver
Ensure that the mount point you plan to use for the Oracle software has sufficient free space. For a basic Enterprise Edition and patch set installation, allow 1.8 Gb for the software mount point as a bare minimum. You will need more space if you plan to install non-default options or components from the Oracle Database 10g Companion CD ROM.
Double check that you are logged in as oracle and not root. Then change to your home directory and start the Oracle Universal Installer with these commands:
$ cd
$ /runInstaller
We’ll walk through the installer prompts one at a time:
The Welcome window appears. Click Next.
If the Specify Inventory Directory and Credentials window appears, verify that the inventory directory is set to the oraInventory subdirectory of the directory referenced by the ORACLE_BASE environment variable you set in the login script. In the Operating System Group Name field, select the oinstall group (or the dba group if you did not create the oinstall group). Click OK. You won't see this window if you have previously installed Oracle software on the database server.
If the Unix Group Name window appears, enter the name of your dba group and click Next. You won’t see this window if you have previously installed Oracle software on the database server, or if your dba group is called “dba”. (You won’t see this window the next time you run the installer because Oracle saves this information in the /var/opt/oracle/oraInst.loc file.)
The Specify File Locations window appears. Leave the Source field unchanged. Oracle provides a suggested Name and Path for the Oracle home (software installation) that is about to be created. You can name this Oracle home anything you like. For the path, you will probably want to go with the suggestion provided but you don’t have to. Beginning in Oracle 10g the standard for Oracle home location has changed to //app/oracle/product/10.1.0/db_. The new component at the end, such as db_1 or db_2, allows you to install multiple copies of the same Oracle version on one server in a standardized way. Note that we will refer back to this path frequently, calling it the Oracle home or simply $ORACLE_HOME. When you are satisfied with the name and path for your Oracle home, click Next.
The Select Installation Type window appears. We will perform a “typical” install to get a basic set of Oracle software installed. You can rerun the installer again later and choose Custom to install additional products individually. For now, choose Standard Edition or Enterprise Edition. The Enterprise Edition of Oracle Database 10g has some very sophisticated features missing from Standard Edition, and the opportunity to purchase additional options that might be valuable to a large enterprise. However, the Enterprise Edition is much more expensive than Standard Edition. It is very important that you choose the edition that matches your license, as this will be difficult to fix later. Click Next.
At this point Oracle performs a minimum requirements check. If you performed all of the preparation steps correctly, all checks should be successful and you can simply click the Next button. If there are any problems, you can correct the problem and click Retry.
If you have any existing Oracle databases on your server that are at a version prior to what you are now installing, the installer will ask if you would like to run the Database Upgrade Assistant at the end of the installation to migrate or upgrade these older databases to the current version. Make your decision and click Next. (We won’t be covering the Database Upgrade Assistant here.)
The Select Database Configuration window appears. We could have Oracle create a database at the same time the software is installed, but this would not be a good idea because we would have to immediately patch the database when we apply the patch set. We will choose the “Do not create a starter database” option instead. After we have applied the patch set, we will use the Database Configuration Assistant to create a database. Click Next.
The Summary window appears. Review all of the selections you have made to confirm they are correct. Click Install.
During the installation a Setup Privileges window will appear. The installation will be paused at this point, waiting for you to run a script as root. The script will be called root.sh and can be found in the Oracle home directory (the directory you specified as the Path in the File Locations window). You should open another window, log in to the database server as root, review the root.sh script thoroughly, run the script, and click OK in the Setup Privileges window.
The End of Installation window appears. URLs for various features, such as Ultra Search and iSQL*Plus, will be displayed. Note these URLs for future reference. Click Exit to exit the installer.
You can run the installer again and perform a custom installation to install any individual products that did not get installed as part of the “typical” installation.
It is important to note that the default Enterprise Edition install loads certain extra cost options, such as OLAP and table partitioning, onto your database server. If you are not licensed to use these options, then you should deinstall them. To deinstall products, restart the installer and click the Deinstall Products button on the Welcome window.
The root.sh script that you ran as root during the installation process started a cluster services daemon that runs as the root user. We will need to stop this daemon before we can apply the Oracle patch set. Oracle only needs the cluster services daemon on database servers that use Oracle’s Automatic Storage Management (ASM) or Real Application Clusters (RAC). Since we will not be using either of these facilities, there will be no need to have this daemon run at all. We cannot simply kill the daemon, because the root.sh script added a “respawn” entry to the inittab. (If we kill the daemon, the operating system will restart it.)
To stop the cluster services daemon and prevent it from restarting immediately or when the server is rebooted in the future, we will need to restore the inittab to is previous state. Luckily, the root.sh script preserved a backup copy before editing the inittab. First, doublecheck that the backup copy of inittab is identical to the real inittab except for the one entry added by the root.sh script:

$ diff /etc/inittab.orig /etc/inittab
Next, run the following commands very carefully as root:
$ mv /etc/inittab.orig /etc/inittab
$ /etc/init.d/init.cssd stop
$ mv /etc/rc3.d/S96init.cssd /etc/rc3.d/_S96init.cssd
$ mv /etc/rc3.d/K96init.cssd /etc/rc3.d/_K96init.cssd
At this point we are ready to patch the Oracle software installation. Log onto Oracle Metalink (http://metalink.oracle.com) and download the latest patch set for Sun Solaris SPARC. As of this writing, release 10.1.0.4 (patch number 4163362) is the latest.
Use a command like the following to unpack the patch set:
$ unzip p4163362_10104_SOLARIS64.zip
Double check that you are logged in as oracle and not root, and that your DISPLAY environment variable is still set correctly. Then change to the directory where you unpacked the patch set and start the Oracle Universal Installer with these commands:
$ cd /Disk1
$ ./runInstaller
Once again, we’ll walk through the installer prompts one at a time:
The Welcome window appears. Click Next.
The Specify File Locations window appears. Leave the Source Path field unchanged. For the Destination, use the dropdown list on the Name or Path fields to select the Oracle home where you just installed Oracle software in the previous steps. Do not go with a different Destination Name or Path, even if the installer has defaulted these fields this way. Click Next.
The Summary window appears. Click Install.
During the installation a Setup Privileges window will appear. Once again the installation will be paused at this point, waiting for you to run a root.sh script as root. As before, the script can be found in the Oracle home directory. You should open another window, log in to the database server as root, and review the root.sh script thoroughly before running it. The script will detect that Oracle cluster software has already been installed and cnfigured, but it might complain that the daemon is not running. You can ignore messages along the lines of “Oracle Cluster Registry for cluster has already been initialized” and “Giving up: Oracle CSS stack appears NOT to be running”. Click OK in the Setup Privileges window after running the script.
The End of Installation window appears. Click Exit to exit the installer.
In $ORACLE_HOME/bin (the bin directory under your Oracle home) you will find a shell script called oraenv. This script can be called from .profile or .bash_profile to set up a user’s environment automatically whenever they log onto the database server. We will customize the oraenv script because there are a few variables that the script should set but doesn’t. Make a backup copy of the oraenv script and then edit it, adding the following lines to the very end:
# Begin customizations
ORACLE_BASE=`dirname $ORACLE_HOME`
ORACLE_BASE=`dirname $ORACLE_BASE`
case "$ORACLE_BASE" in
*/product) ORACLE_BASE=`dirname $ORACLE_BASE` ;;
*) ;;
esac
DBA=$ORACLE_BASE/admin
# Substitute the locale and character set you plan to use for your
# database in the line below. Some common choices are:
# NLS_LANG=american_america.WE8ISO8859P1 (Unix default)
# NLS_LANG=american_america.AL32UTF8 (Unicode 3.1)
# NLS_LANG=american_america.UTF8 (Unicode 3.0)
# NLS_LANG=american_america.WE8MSWIN1252 (Windows)
NLS_LANG=american_america.WE8ISO8859P1
export ORACLE_BASE DBA NLS_LANG
# End customizations
In the same directory you’ll also find a shell script called coraenv that can be called from .cshrc. If you use C shell, you will want to back up and edit coraenv with similar changes to the oraenv script.
The root.sh script copied oraenv and coraenv from $ORACLE_HOME/bin to your local bin directory. You just updated these scripts in $ORACLE_HOME/bin. Copy the updated versions to your local bin directory.
Create a Database
These steps create an Oracle database. Everybody will have different needs for their database, but the steps here will yield you a functional database that you can further tailor to your specific needs. In this section we will use the Database Configuration Assistant to create a database, adjust the database in order to better comply with industry-proven best practices, and configure Oracle Net. All of the steps in this section are run as the oracle user.

Set up your environment the same way you did when you ran the Oracle Universal Installer: Log in as the oracle user on the database server from an X window, set your DISPLAY variable appropriately, and make sure that your ORACLE_BASE variable is set correctly based on your login file.
Set the ORACLE_HOME environment variable to point to your Oracle home with a command like:
$ export ORACLE_HOME=/u01/app/oracle/product/10.1.0/db_1
Choose a name for your Oracle instance, up to eight characters long. The instance name is easy to change at any time. However, you will want to keep the instance name the same as the database name in order to avoid confusion. Changing the database name later is possible, but not the easiest thing to do. So pick a name for the instance that you like. Set the ORACLE_SID variable accordingly with a command like:
$ export ORACLE_SID=dev101ee
Launch the Database Configuration Assistant with the following commands:
$ cd $ORACLE_HOME/bin
$ ./dbca
We’ll walk through the prompts one at a time:
The Welcome window appears. Click Next.
The Operations window appears. Choose “Create a Database” and click Next.
The Database Templates window appears. Here you choose a template (a set of default specifications) for the database you wish to create. Oracle provides templates called “Data Warehouse,” “General Purpose,” and “Transaction Processing.” Oracle has prebuilt data files available for these three templates, meaning that database creation will go faster than if Oracle has to build the database from scratch. You can also choose Custom and create your own template. We will choose General Purpose here. Click Next.
The Database Identification window appears. Here you specify the global name and the instance name (SID) for the database. It would be nice if these fields defaulted from the ORACLE_SID environment variable, but this may or may not happen. In the Global Database Name field, enter the database name you selected, followed by a period and your domain name. For example, “dev101ee.dbspecialists.com”. The SID field will fill in automatically from the global name. Click Next.
The Management Options window appears. Here you indicate whether or not you wish to have the Enterprise Manager tool configured. Grid Control is Oracle’s enterprise-wide database management tool. This option will be grayed out if Grid Control infrastructure has not already been established. Database Control is a stand-alone management tool specifically configured to manage one database. If Grid Control is not present, the defaults in this window will specify to configure Database Control for this database. This will enable you to perform many database management functions for this database from a web browser. You may optionally configure Database Control to send you alerts via email and to back up the database daily. It does not hurt to choose Database Control configuration at this time—you can always shut it down later. We will not be covering the database backup feature here. Click Next.
The Database Credentials window appears. Every Oracle 10g database has accounts called SYS, SYSTEM, DBSNMP, and SYSMAN. You must provide passwords for each of these accounts, although you can choose to give all four the same password. It is easy to change passwords later, and members of the dba Unix group can access the database without a password and change passwords for any database account. Enter the initial passwords for these accounts and click Next.
The Storage Options window appears. The files that make up an Oracle database can be stored on a regular file system, raw devices, or disks managed automatically by Oracle’s Automatic Storage Management facility. We will not be covering raw devices or ASM here, so select File System and click Next.
The Database File Locations window appears. Here you specify where on the file system the files that make up the database should initially reside. It will be easy to change file locations later, and database files can be spread over multiple directories. The default option on this window is to use the file location specified in the template. This is not a good idea as the location specified by the templates goes against standard conventions. Instead you should select “Use Common Location for All Database Files” and enter a mount point name followed by the oradata subdirectory, such as “/u01/oradata”. The location you enter here should match one of the directories you created in step 12 of the first section above. Click Next.
The Recovery Configuration window appears. A solid backup and recovery plan is absolutely necessary for any database that will hold data of any importance. However, there are many options available and needs vary greatly from one situation to the next. The flash recovery area is used by the “Flashback database” feature and also by Enterprise Manager if you chose to configure automatic database backups. Archiving, meanwhile, is necessary for databases that will be backed up while they are open. Archiving can be enabled easily at a later time. Since we are not covering backup and recovery strategies here, we will uncheck both options and click Next.
The Database Content window appears. This window contains multiple tabs where you may choose what data will be preloaded in the new database. Your options here will vary depending on which Oracle software options you installed and which database creation template you chose. Typically there will be no need for you to specify any custom scripts, and preloading the sample schemas can be helpful in a development database for seeing examples of various techniques. Make your selections and click Next.
The Initialization Parameters window appears. If your database server has only 512 Mb of physical memory, an error window may appear which you can ignore. The error arises from the fact that default settings for memory-related initialization parameters are derived from the amount of physical memory, and a flaw in the algorithm picks a default value that is too small on machines with only 512 Mb of physical memory. Tabs in this window let you set various initialization parameters, and a button lets you view and edit all parameters in a tabular form. Click on the Character Sets tab and select the character set for the database that matches the character set name you put into the oraenv script in an earlier step. It is hard to change the character set of a database, so make sure you are happy with your selection before proceeding. Initialization parameters, on the other hand, are easily changed later. In this window, therefore, you should make sure the character set is correct but not worry too much about the other settings. (Setting the character sets is very different from setting initialization parameters, so the fact that the Character Sets tab appears on a window entitled Initialization Parameters may be confusing.) Click Next.
The Database Storage window appears. Here you can review and edit the details of how the control files, online redo logs, data files, and tablespaces will be created. If you are using one of the templates that was provided, you will not be able to change very many settings. If you want to change the locations of some of the database files, you can do that here or after the database has been created. The default redo log size (10 Mb) is somewhat small, so yu might want to change it. Again, you can do that here or after the database has been created. When you are satisfied with the settings, click Next.
The Creation Options window appears. You may choose to create the database now and/or save the settings as a template. Saving as a template allows you to create the database at a later time or create many similar databases more easily. Click Finish.
A Confirmation window appears. Review all of your selections and click OK.
A progress window appears and database creation proceeds.
When database creation is complete, a window will appear which indicates the name of the database, the location of the parameter file, and the URL for accessing Enterprise Manager. Note this URL for future reference. Depending n what options you selected, additional accounts may have been created on the database besides the basic SYS, SYSTEM, DBSNMP, and SYSMAN. All additional accounts are now locked. You may click the Password Management button to unlock these accounts and set passwords if you wish, but you should only unlock an account if you have a specific reason for doing so. When you are finished, click the Exit button to exit the Database Creation Assistant.
While logged onto the database server as the oracle user, run the following commands to set environment variables so that you will be able to access the database easily (substitute your Oracle instance name):
$ export ORACLE_SID=dev101ee
$ export ORAENV_ASK=NO
$ . /usr/local/bin/oraenv
If you would like to move any of the data files or online redo logs for this database to another directory, use commands like the following:
$ sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> SHUTDOWN IMMEDIATE
SQL> STARTUP MOUNT
SQL> HOST mv -i /u01/oradata/dev101ee/users01.dbf /u02/oradata/dev101ee/users01.dbf
SQL> ALTER DATABASE RENAME FILE
2 '/u01/oradata/dev101ee/users01.dbf' TO
3 '/u02/oradata/dev101ee/users01.dbf';
SQL> HOST mv -i /u01/oradata/dev101ee/redo01.log /u02/oradata/dev101ee/redo01.log
SQL> ALTER DATABASE RENAME FILE
2 '/u01/oradata/dev101ee/redo01.log' TO
3 '/u02/oradata/dev101ee/redo01.log';
SQL> ALTER DATABASE OPEN;
SQL> EXIT
Note that this procedure does not work for control files. Relocating database control files will be covered in a later step.
In databases created with supplied templates, all data files have the “auto-extend” feature turned on. This means that when a data file becomes full, it will automatically grow larger as needed. The problem with this is that an application can get out of control and fill up an entire disk partition. It also means that you need to manage your free space at the operating system level. Many DBAs prefer to manage free space at the database level by pre-allocating space to data files and not using the auto-extend feature. You may resize data files and disable auto-extend with commands like:
$ sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> ALTER DATABASE DATAFILE '/u01/oradata/dev101ee/system01.dbf' AUTOEXTEND OFF;
SQL> ALTER DATABASE DATAFILE '/u01/oradata/dev101ee/sysaux01.dbf' AUTOEXTEND OFF;
SQL> ALTER DATABASE DATAFILE '/u01/oradata/dev101ee/undotbs01.dbf' AUTOEXTEND OFF;
SQL> ALTER DATABASE DATAFILE '/u01/oradata/dev101ee/example01.dbf' AUTOEXTEND OFF;
SQL> ALTER DATABASE DATAFILE '/u01/oradata/dev101ee/users01.dbf' AUTOEXTEND OFF;
SQL> ALTER DATABASE TEMPFILE '/u01/oradata/dev101ee/temp01.dbf' AUTOEXTEND OFF;
SQL> ALTER DATABASE DATAFILE '/u01/oradata/dev101ee/system01.dbf' RESIZE 500m;
SQL> ALTER DATABASE DATAFILE '/u01/oradata/dev101ee/sysaux01.dbf' RESIZE 300m;
SQL> ALTER DATABASE DATAFILE '/u01/oradata/dev101ee/undotbs01.dbf' RESIZE 50m;
SQL> ALTER DATABASE TEMPFILE '/u01/oradata/dev101ee/temp01.dbf' RESIZE 50m;
Oracle uses a server parameter file or “spfile” to store the initialization parameters—settings that affect the instance. The default parameter settings provided by the Database Configuration Assistant are not bad, but you may want to make some changes. Unfortunately, you cannot edit the spfile. Instead, you must export the contents of the spfile to a plain text file called a “pfile”. You can then edit the pfile and convert it back to an spfile for use on your database. (This might sound confusing, but is actually pretty straightforward.)
Shut down the database and export the contents of the spfile into a pfile that you can edit with commands like:

$ sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> CREATE PFILE='/home/oracle/dev101ee-params.txt'
2 FROM SPFILE;
SQL> SHUTDOWN IMMEDIATE
Make a backup copy of the pfile you created in the previous step and edit the pfile to change parameters as you wish, based on your needs and your server’s capabilities. You can always change parameters again in the future, so you are not locking yourself into anything right now. Here is the pfile that I ended up with:
*.background_dump_dest='/u01/app/oracle/admin/dev101ee/bdump'
*.compatible='10.1.0.4.0'
*.control_files='/u01/oradata/dev101ee/control01.ctl','/u01/oradata/
dev101ee/control02.ctl','/u01/oradata/dev101ee/control03.ctl'
*.core_dump_dest='/u01/app/oracle/admin/dev101ee/cdump'
*.db_block_size=8192
*.db_domain='dbspecialists.com'
*.db_file_multiblock_read_count=16
*.db_name='dev101ee'
*.job_queue_processes=10
*.open_cursors=300
*.os_authent_prefix=''
*.pga_aggregate_target=24m
*.processes=50
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=240m
*.undo_management='AUTO'
*.undo_tablespace='UNDOTBS1'
*.user_dump_dest='/u01/app/oracle/admin/dev101ee/udump'
The database is created with three control files. The control file is a pretty small file that contains crucial configuration and synchronization information that Oracle needs in order to locate all the files that make up the database and keep them consistent. All three copies of the control file are kept identical; whatever Oracle writes to one control file it also writes to the other two. (Think of it like software mirroring.) It is a good idea to move at least one of the control files to another location. With the database shut down, you can go ahead and move the control files around as you wish. Be sure to change the control_files entry in your pfile accordingly.
Remove the existing spfile that the Database Configuration Assistant created, and the bogus pfile that it left behind, with the following commands:
$ rm -i $ORACLE_HOME/dbs/spfile$ORACLE_SID.ora
$ rm -i $ORACLE_BASE/admin/$ORACLE_SID/pfile/init.ora*
Create a symbolic link from the location where Oracle looks for the spfile to the location where you will actually maintain the spfile:
$ ln -s $ORACLE_BASE/admin/$ORACLE_SID/pfile/spfile$ORACLE_SID.ora \
$ORACLE_HOME/dbs/spfile$ORACLE_SID.ora
Now convert the pfile that you edited back into an spfile that Oracle can use with the following commands:
$ sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> CREATE SPFILE='$ORACLE_BASE/admin/$ORACLE_SID/pfile/spfile$ORACLE_SID.ora'
2 FROM PFILE='/home/oracle/dev101ee-params.txt';
You are now ready to restart your database using your newly created spfile. Use the following commands to start the database and view the parameters that are in effect. These settings should match what you put in your pfile a few steps back:
$ sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> STARTUP
SQL> SET PAGESIZE 100
SQL> SELECT name, value, isdefault
2 FROM v$parameter
3 ORDER BY isdefault, name;
You can follow the above few steps at any time to make further changes to the parameters. However, if you only have a few changes to make, there is a much easier way than exporting the spfile into a pfile, editing the pfile, and converting back to an spfile. You can simply:
$ sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> ALTER SYSTEM SET parameter = value
2 SCOPE = SPFILE;
This will update the setting in your spfile, and the change will take effect the next time you restart the database. Many parameters are dynamic, meaning that you can change them on the fly without restarting the database. For dynamic parameters, you can omit the SCOPE = line above and Oracle will change the parameter setting immediately and in the spfile.
Oracle Net is the networking infrastructure that allows applications running on other servers to access the database. The Oracle Net listener is a process that runs on the database server and monitors a TCP port for requests to access the database. The Oracle Net listener is configured by creating a file called listener.ora in the $ORACLE_HOME/network/admin directory. In the $ORACLE_HOME/network/admin/samples directory you will find an example listener.ora file. Unfortunately, many Oracle security exploits involve the Oracle Net listener, and therefore it is important that you configure it properly and securely. A functional listener.ora file that uses operating system authentication for securing the Oracle Net listener is as follows:
#
# Filename: listener.ora
#
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.1.16)(PORT = 1521))
)
)
)
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(GLOBAL_DBNAME = dev101ee.dbspecialists.com)
(ORACLE_HOME = /u01/app/oracle/product/10.1.0/db_1)
(SID_NAME = dev101ee)
)
)
The permissions on the listener.ora file should be 640.
Start the Oracle Net listener with the following command:
$ lsnrctl start
The Oracle client libraries invoked by an application wishing to access the database read configuration files called sqlnet.ora and tnsnames.ora in order to figure out how to find the Oracle Net listener and what connection parameters should be used. In the same directory where the sample listener.ora file is located, you will also find a sample sqlnet.ora and tnsnames.ora. You should create a sqlnet.ora file and a tnsnames.ora file in the same directory where you created your listener.ora file. Set the file permissions to 644. Copy these two files to all application servers or other machines that will access the database. Functional sqlnet.ora and tnsnames.ora files are as follows:
#
# Filename: sqlnet.ora
#
NAMES.DEFAULT_DOMAIN = dbspecialists.com
NAMES.DIRECTORY_PATH= (TNSNAMES)

#
# Filename: tnsnames.ora
#
DEV101EE.DBSPECIALISTS.COM =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.1.16)(PORT = 1521))
)
(CONNECT_DATA =
(SERVICE_NAME = dev101ee.dbspecialists.com)
)
)
You can verify that Oracle Net is configured correctly by attempting to access the database from an application server or other remote server, or by using commands like the following on the database server directly:
$ sqlplus /nolog
SQL> CONNECT system@dev101ee
Enter password:
At this point you are ready to create tablespaces—logical groupings of data files—to hold your application data. You can put all of your data into one tablespace, or you can separate data into multiple tablespaces based on object type, object size, permanence, volatility, I/O volume, or any of a number of other criteria. In the past, choosing storage parameters and allocation schemes for database objects was rather tedious. Now it is quite simple because you can have Oracle do the space allocation and management automatically and it will do a pretty good job. Here is a sample tablespace creation statement for an application called “Flex”:
CREATE TABLESPACE flex_data
DATAFILE '/u02/oradata/dev101ee/flex_data01.dbf' SIZE 500m
SEGMENT SPACE MANAGEMENT AUTO;
Create application roles if desired. Alternatively, you can use the default roles CONNECT, RESOURCE, and DBA.
Create your application accounts that will own the application schemas. Set the default tablespace to one of your application tablespaces designated to hold tables. Assign quotas on all of the application tablespaces where the account will need to be able to create schema objects. (You can use the keyword UNLIMITED.) You should not set any quota on the SYSTEM, SYSAUX, or TEMP tablespaces. Do not plan to create any application objects in the SYS or SYSTEM schemas, or store any application objects in the SYSTEM, SYSAUX, or TEMP tablespaces. Here is a sample application account creation statement:
CREATE USER bob IDENTIFIED BY bob123
DEFAULT TABLESPACE flex_data
QUOTA UNLIMITED ON flex_data;
Grant roles and/or system privileges to the application accounts. Note that if you grant the RESOURCE role to an account, that account will also receive the UNLIMITED TABLESPACE system privilege. This will let the account create objects in any tablespace, regardless of quotas. Think very carefully before granting the DBA role or allowing any accounts th have the UNLIMITED TABLESPACE privilege. Sample statements to grant and revoke privileges are as follows:
GRANT connect, resource TO bob;
REVOKE unlimited tablespace FROM bob;
Review the overall security of your database. Oracle Corporation published a very good ten-page listing of security checks that you should perform against Oracle 9i database. This document does not appear to have been updated for Oracle Database 10g yet, but it still contains a lot of relevant material. Download it from the Oracle Technology Network at http://otn.oracle.com/deploy/security/oracle9i/pdf/9iR2_checklist.pdf. Another checklist, although not all of the recommendations seem appropriate, is available at http://www.sans.org/score/checklists/Oracle_Database_Checklist.pdf.
Complete the Server Configuration
These steps complete the configuration of your server for smooth Oracle operation. In this section we will change the oracle user’s login script to eliminate hardcoding, create individual operating system accounts for each database user, and configure the server to start the database and listeners automatically whenever the server is rebooted.

Edit the login file (.profile or .bash_profile) for the oracle user to eliminate hardcodings and call the oraenv script to set the environment instead. The following will work with Bourne, Korn, or Bash shell:
# Settings for Oracle environment
ORACLE_SID=dev101ee # Put your instance name here
ORAENV_ASK=NO
export ORACLE_SID ORAENV_ASK
. oraenv
Note that this script assumes that the /usr/local/bin directory is on your path. Also, if you use C shell then you should edit .cshrc and have it source coraenv.
Create separate Unix accounts for DBAs and database users who will log onto the database server directly. You should only log in as oracle when installing or patching software. The Unix accounts for DBAs should be members of the dba group, and other users should not be members of the dba group. Give each of these accounts a login file like oracle’s so that their environment initializes correctly when they log in.
Edit the /var/opt/oracle/oratab file to verify that the entry for your database is correct. Lines starting with a pound sign are considered comments and are ignored. Each non-comment line contains the name of one Oracle instance, its Oracle home, and a Y or N. A Y indicates that the database should be started automatically on server reboot, and an N indicates that it should not. The three fields should be separated by colons. A sample /var/opt/oracle/oratab file looks like this:
#
# /var/opt/oracle/oratab
# ======================
#
dev101ee:/u01/app/oracle/product/10.1.0/db_1:Y
To make the database and listeners start up automatically when the server reboots and shut down automatically when the server shuts down, you’ll need to create a dbora file in /etc/init.d and link it to /etc/rc2.d and /etc/rc0.d. You’ll need to do this as the root user. First create a file called dbora in /etc/init.d as follows:
#!/bin/sh
ORA_HOME=/u01/app/oracle/product/10.1.0/db_1
ORA_OWNER=oracle
if [ ! -f $ORA_HOME/bin/dbstart ]
then
echo "Oracle startup: cannot start"
exit
fi
case "$1" in
'start') # Start the Oracle databases and listeners
su - $ORA_OWNER -c "$ORA_HOME/bin/dbstart"
su - $ORA_OWNER -c "$ORA_HOME/bin/lsnrctl start"
su - $ORA_OWNER -c "$ORA_HOME/bin/emctl start dbconsole"
su - $ORA_OWNER -c "$ORA_HOME/bin/isqlplusctl start"
;;
'stop') # Stop the Oracle databases and listeners
su - $ORA_OWNER -c "$ORA_HOME/bin/isqlplusctl stop"
su - $ORA_OWNER -c "$ORA_HOME/bin/emctl stop dbconsole"
su - $ORA_OWNER -c "$ORA_HOME/bin/lsnrctl stop"
su - $ORA_OWNER -c "$ORA_HOME/bin/dbshut"
;;
esac
After creating the dbora file, you need to link it to /etc/rc2.d and /etc/rc0.d:
ln -s /etc/init.d/dbora /etc/rc2.d/S99dbora
ln -s /etc/init.d/dbora /etc/rc0.d/K10dbora
Conclusion
This paper walks you through the intricate details of getting Oracle Database 10g up and running on a database server running SPARC Solaris. It may look complicated, but that’s only because this paper goes down to a nitty-gritty level of detail.

Please keep in mind, though, that the requirements are different for every Oracle implementation. I am extremely confident that if you follow these steps to install Oracle Database 10g release 1 (Oracle version 10.1.0) on a server running SPARC Solaris 8, 9, or 10, the process will go very smoothly for you. However, no single document can address every specific hardware configuration and every set of business needs. Please use this paper as a starting point to get Oracle up and running in your shop. To get the best performance and scalability, each system needs to be considered individually.

About the Author

Roger Schrag has been an Oracle DBA and application architect for over fifteen years. He started out at Oracle Corporation on the Oracle Financials development team and moved into the roles of production DBA and database architect at various companies in the San Francisco Bay Area. Roger is a frequent speaker at Oracle World and the IOUG Live! conferences. He is also vice-president of the Northern California Oracle Users Group. In 1995, Roger founded Database Specialists, Inc.

How to Use the Unix Top Command

2010-12-29T09:24:00.001-08:00

How to Use the Unix Top Command
Top is a small, but powerful program available on both UNIX and Linux systems whose purpose is to allow you to monitor processes on your system.

It has two main sections. The first displays general information such as the load averages, number of running and sleeping tasks, and overall CPU and memory usage. The second main section displays a sorted list of processes (usually by CPU usage) and showing their PIDs (Process ID number), user who owns the process, running time, and CPU and memory used by that process.

As such top is useful even without any further configuration. Just starting it up provides a plethora of information about your system's resource usage. If you just need to know what may be slowing your system down, for example, it might be enough to run top and see if there's any process running at close to 100% of CPU time or using a little too much memory.

It is, however, possible to configure it in a variety of ways that change how it displays information. We'll cover some top options on two of the most popular UNIX variants, Mac OS X and Linux (which is technically an UNIX clone).

Mac OS X Top

Top in Mac OS X is somewhat more limited than its Linux (and traditional FreeBSD) counterpart, but can still be a fairly useful tool.

To get started, you can run top -h to see all of the available commands, and man top to see an explanation of each. We'll cover a few examples to help get you started.

Perhaps the first thing you might want it to do is display processes sorted by what you want to focus on monitoring. For instance, you might want to primarily monitor memory usage so the default sorting by CPU usage might not quite fit the bill. To sort by memory usage you would use the top -o mreg command.

The top -o command accepts a number of other key's like mreg including cpu for CPU usage, time for execution time, threads for number of threads running, user for sorting by process's username, and so on. The full list is available in the man page (the man top command).

You can also control how often the information shown is updated (the default is every second). If you want to set it to update every 10 seconds just run top -s 10.

To limit how many processes in total are shown use the top -n 10 if you want to show just the top 10 processes.

Top on Mac has four modes of counting events the default one being non-event mode (top -c n). The accumulative mode (top -a) counts events cumulatively since the launch of top. The delta mode (top -d) counts events relative to the previous value. Absolute mode (top -e) counts using absolute counters.

Multiple top commands can be combined to control what exactly you want to see. For example, if you want top to show you processes sorted by memory usage, in delta mode, updating every 5 seconds and displaying only top 5 results you simply combine all of the appropriate commands (mentioned above) and run "top -o mreg -d -s 10 -n 5".

Linux Top

Top can be found on pretty much any Linux distribution out there including popular ones such as Ubuntu, Fedora and OpenSUSE which are among the easiest to install and try out.

The commands to get help with top on Linux are the same as on Mac OS X, top -h for a condensed list of commands, and man top for a much more verbose explanation of all available options.

It has a powerful interactive mode which is active by default when you start top, and is probably going to be the primary way in which you operate top since it provides the most flexibility and ease of use. You can use a variety of commands in form of just letter key presses to manipulate what you are seeing. Here are a few examples.

To sort processes by memory usage simply press M (shift-m on the keyboard). To sort by CPU usage press P (shift-p). You can see a full list of fields by pressing f which will show the fields with their appropriate letter (which you can use to sort by that field).

With the f key you can also opt to add a new field to display by pressing f and then the letter representing the key. For example if you want to add a code size field (CODE) press f and then r (as shown in the field list).

You can set the delay time for updates by just pressing s, putting in a desired number of seconds, and pressing enter. It will then update in that number of seconds, but you can update any time you want yourself by pressing the space bar.

To change the number of processes shown just press n, put in the desired number and press enter.

You can even kill processes from within top if you have a rogue process or a program of some kind wont quit or some process is using too many resources. To do so press k, enter the PID (Process ID, which you can read in top) of that process and press enter.

Linux top also supports the cumulative mode which can be simply toggled by pressing S (shift-s). A full list of all available interactive commands is available in the top manual page (man top).

Of course, it is still possible to start top with some options already set. For example, top -d 5 will cause top to refresh its data every five seconds (equivalent to s and 5 in the interactive mode). The top -q will display information without any delay, and run it with highest priority if top is run as a superuser (or root).

Top can also be started to show only a few updates and then quit automatically. Just run top -n 10, for instance, to have top show 10 iterations of information before quitting.

Another interesting command line option is top -b which runs top in a batch mode suitable for recording into a text file. Instead of just refreshing information on screen it prints it out in batches every specified number of seconds until all iterations run out (set by -n as mentioned above) or until it is quit. To write it out into a text file called top.txt stored in a local directory just run top -b > top.txt.

Just as in Mac OS X, it is possible to combine multiple commands to configure top at its start. For example, run top -d 5 -n 10 to start top with a refresh rate of five seconds and have it update only 10 times before quitting.

To quit top manually, in both OSX and Linux, just press the q key.

How to Use vi Editor

2010-12-29T09:22:00.000-08:00

How to Use vi
The vi editor (visual editor) is one of the oldest and more popular text editors on computers running the Unix Operating System (OS). The vi editor can be used from any computer terminal interfacing with a computer running Unix, since the editor relies on the standard alphabet keys for specific commands. Since vi is not a WYSIWYG (What You See is What You Get) text editor, it does not provide the formatting capabilities word processors do for paragraph indentations, font, and line centering. New vi users need to learn the following: opening and closing a file, file editing, and moving around in a text file.

How to Start vi

Step 1 – Open an existing file by entering the following command at the terminal command line, then press the “return” key" vi myFileName

If the file is not in the current directory, the fully qualified file path must also be included.

Step 2 – Create a new file by entering the following command:
vi myNewFile
Enter Text in vi

When vi is first started, it loads in command board with the keyboard keys doing text deletion and cursor movement. In order to enter text, enter the “insert mode” by typing the letter “i”. No visual change will occur on the screen, but text can now be entered. Press “return” at the end of each line of text. The vi editor will not wrap text automatically at the end of a line on the screen. Instead, it will automatically break the line of text in mid word if the “return” key is not pressed prior to the end of line.
How to Move the Cursor in vi

One of the initial tasks that new users of the vi editor find challenging is moving the cursor to a new position in the document. In order to do so, place the vi editor in command mode by pressing the “Esc” key. If unsure about what mode the editor is in, press the key until a beep is heard. The following letters can move the cursor:

l – moves the cursor right one space
k – moves the cursor up one line
j – moves the cursor down one line
h – move the cursor left one space

Once the cursor is moved as far as possible in a given direction, the terminal will beep.
How to Edit a File in vi

In order to edit a file in vi, place the editor into command mode. The letters' meanings depend on whether they are typed in lower or upper case. Some commands can also be repeated a predefined number of times by including a number prior to the command.

Vi Editing Commands

Character deletion – x (with the cursor placed on the incorrect letter)

Delete the character prior to the cursor – X

Delete multiple characters – (number)x (will delete the character highlighted by the cursor and the next three

Delete words – dw (with the cursor on the first letter of the word)

Delete lines – dd (the cursor can be at any location on the line to be deleted)

Delete from the cursor to the end of the line – D

Replace characters – r (with the cursor placed on top of the character to be replaced).

Replace words – cw (with the cursor at the start of the word to be replaced).

Replace lines – C (after typing the command, enter the new text then press the “Esc” key).

Insert text – i (pressed after the cursor is positioned where the next text is to be inserted. The text is inserted prior to the cursor).

Append text – a (with the cursor placed on the final letter of the line to append the text).

Insert a blank line above the current line – O

Undo edits – u

Undo all edits on a line – U

Undoing
To undo your most recent edit, type
u
To undo all the edits on a single line, type
U (uppercase)

Useful Vi Commands to Move Around Files in Command Mode

“Control” “f” Scroll forward one screen in the editor
“Control” “b” Scroll backward one screen in the editor
“Control” “d” Scroll down one-half screen in the editor
“Control” “u” Scroll up one-half screen
w – Move forward one word at a time
b – Move backward a word at a time
$ – Move to the end of the line
0 – Move to the beginning of the line
H – move to the top line of the screen
M – Move to the middle of the screen
L – Move to the last line of the screen
G- Move to the last line of the file

ZZ – Exit and Save a file
:w – Save a file
:q! – Discard file changes and quit

How to Change an IP Address on Solaris

2010-12-29T09:18:00.001-08:00

How to Change an IP Address on Solaris
To change an IP address on a Solaris system immediately, use the `ifconfig` command.

The syntax for `ifconfig` is:

ifconfig

If you don't know the names of your network interfaces, use the `ifconfig -a` command to list all of the available network interfaces.

Permanently Change an IP Address on Solaris

To make this change permanent, you will need to edit one or more Solaris configuration files. If you do not, then your IP address will change back to the old address the next time you reboot the system.

You will need to edit the hosts entry in /etc/hosts.

If you have moved the system to a new network, you will need to change the default route in /etc/defaultrouter.

If you are using VLSM (Variable Length Subnet Masks), you may need to edit /etc/netmasks.

If you are using Solaris 9 or above, you may need to edit the IP address in /etc/inet/ipnodes.

You should then reboot the server to test your changes and ensure that they operate correctly.

How to Change a Hostname on Solaris

2010-12-29T09:13:00.000-08:00

How to Change a Hostname on Solaris
Solaris makes it unreasonably difficult to change the hostname of an installed server.

To change the hostname on a Solaris system, you should edit all of these files:

/etc/hosts
/etc/nodename
/etc/hostname.*
/etc/net/ticlts/hosts
/etc/net/ticots/hosts
/etc/net/ticotsord/hosts
/etc/inet/ipnodes
You should then reboot the server to test your changes and ensure that they operate correctly.

Exam prep

2010-12-08T19:07:00.000-08:00

If you consider to take solaris exam (two exam) you should think about
these books:

A new edition of this title is available, ISBN-10: 0789737906 ISBN-13: 9780789737908

The Solaris 10 System Administrator Certification Exam Prep 2 is the ideal book for both new and seasoned system administrators. This book will give you the insight you need into the newest certification exams for system administrators, the 310-200 and the 310-202. It offers classroom-style training by one of the best and well-known authors in the Solaris world, Bill Calkins. It will equip you with vital knowledge for success on exam day plus it acts a reference guide that will come in handy after the test. The content addresses all the new exam objectives in detail and will show you how to apply this knowledge to real-world scenarios.

The included CD features ExamGear's innovative test engine, which will be an effective tool for preparing for the Solaris 10 exam. It provides you with five different ways to test yourself, random questions and order of answers, detailed explanations of correct and incorrect answers, and it pays special attention to exam objectives. Also included on the CD is a PDF of the complete text of the book.
From the Back Cover
A new edition of this title is available, ISBN-10: 0789737906 ISBN-13: 9780789737908

The Solaris 10 System Administrator Certification Exam Prep 2 is the ideal book for both new and seasoned system administrators. This book will give you the insight you need into the newest certification exams for system administrators, the 310-200 and the 310-202. It offers classroom-style training by one of the best and well-known authors in the Solaris world, Bill Calkins. It will equip you with vital knowledge for success on exam day plus it acts a reference guide that will come in handy after the test. The content addresses all the new exam objectives in detail and will show you how to apply this knowledge to real-world scenarios.

The included CD features ExamGear's innovative test engine, which will be an effective tool for preparing for the Solaris 10 exam. It provides you with five different ways to test yourself, random questions and order of answers, detailed explanations of correct and incorrect answers, and it pays special attention to exam objectives. Also included on the CD is a PDF of the complete text of the book.

FTP SERVER

2010-08-27T06:19:00.000-07:00

Hello every one.

I installed it on my Linux machine and it's very

good to use.

Please note that:

This installation guide only support OS Solaris10.

1.> put these two files(vsftpd, vsftpd.conf) to the directory which you create mannually;

su - root

# cd /opt

# mkdir vsftpd-2.0.5

........ ------ put these two files(vsftpd, vsftpd.conf) to vsftpd-2.0.5 directory.

# cd /opt/vsftpd-2.0.5

# chmod u+x *

# ls -l

total 488

-rwxr--r-- 1 root root 109908 Jun 8 20:54 vsftpd

-rwxr--r-- 1 root root 3913 Jun 8 20:56 vsftpd.conf

2.> We need create ftp user and directory for it.

# mkdir /var/ftp/

# useradd -d /var/ftp ftp

# chown root:root /var/ftp

# chmod 755 /var/ftp

3.> vsftpd needs the (empty) directory /usr/share/empty in the defaultconfiguration.

Add this directory in case it does not already exist.

# mkdir /usr/share/empty/

4.> vsftpd can run standalone or via an inetd (such as inetd or xinetd). This case we run vsftpd without inetd.

So we need edit /etc/vsftpd.conf, and add below line at the bottom:

listen=YES

5.> Copy vsftpd.conf to /etc , and edit it.

# cp vsftpd.conf /etc

# cd /etc/

# vi vsftpd.conf

Please notice below items for vsftp 's normal running when you edit vsftpd.conf.

......

# Allow anonymous FTP? (Beware - allowed by default if you comment this out).

anonymous_enable=YES

#

# Uncomment this to allow local users to log in.

local_enable=YES

#

# Uncomment this to enable any form of FTP write command.

write_enable=YES

#

# Default umask for local users is 077. You may wish to change this to 022,

# if your users expect that (022 is used by most other ftpd's)

local_umask=022

......

listen=YES ------ this is the last line of vsftpd.conf

6.> Test without an inetd

# mkdir /opt/vsftpd-2.0.5/GSN ------ Create directory for gsn user,

we also can create directory for rnc user follow gsn's steps

# useradd -d /opt/vsftpd-2.0.5/GSN gsn

# chown gsn : other GSN

# passwd gsn

New Password:

Re-enter new Password:

passwd: password successfully changed for gsn

#

# ls -lrt

total 490

-rwxr--r-- 1 root root 109908 Jun 8 20:54 vsftpd

-rwxr--r-- 1 root root 3913 Jun 8 20:56 vsftpd.conf

drwxr-xr-x 2 gsn other 512 Jun 8 21:44 GSN

/opt/vsftpd-2.0.5

# nohup ./vsftpd & ---- root user

# ps -ef|grep vsftpd

root 1301 1246 0 21:42:11 pts/1 0:00 grep vsftpd

root 1300 1246 0 21:42:06 pts/1 0:00 ./vsftpd

From Client side, we can get below information during we use vsftpd first time.

root@serverP}/opt/GSN# ftp 10.40.106.200

Connected to 10.40.106.200.

220 (vsFTPd 2.0.5)

Name (10.40.106.200:root): gsn

331 Please specify the password.

Password:

230 Login successful.

Remote system type is UNIX.

Using binary mode to transfer files.

ftp> pwd

257 "/opt/vsftpd-2.0.5/GSN"

ftp> dir

200 PORT command successful. Consider using PASV.

150 Here comes the directory listing.

226 Directory send OK.

7.>Construction startup script

# vi /etc/rc3.d/S83vsftpd

#!/sbin/sh

case "$1" in

start)

/usr/local/bin/vsftpd &

;;

stop)

pkill vsftpd

;;

*)

echo "Usage: $0 { start | stop }"

exit 1

;;

esac

exit 0

Best Regards.

Solaris UNIX: How to Setup DNS Client configuration / name server

2010-07-25T23:40:00.000-07:00

Solaris UNIX: How to Setup DNS Client configuration name server

So how do you set DNS namserver under Sun Solaris UNIX system? The resolver is a set of routines in the C library that provide access to the Internet Domain Name System (DNS). The resolver configuration file contains information that is read by the resolver routines the first time they are invoked by a process. The file is designed to be human readable and contains a list of keywords with values that provide various types of resolver information.
Internet address (in dot notation) of a name server that the resolver should query. Up to MAXNS (currently 3, see ) name servers may be listed, one per keyword. If there are multiple servers, the resolver library queries them in the order listed. To configure Solaris nameserver edit or modify /etc/resolv.conf file.
DNS Client Setup
First Create the file called /etc/resolv.conf - which includes the primary and secondary DNS server IP address for Solaris system, it can be your own DNS server or your ISPs DNS server:

# touch /etc/resolv.confOpen /etc/resolv.conf using vi text editor:

# vi /etc/resolv.conf

Add the following lines to it:

search khalaf.in
nameserver 202.54.1.30
nameserver 202.54.1.18
Where,
nameserver IP : It is IP of first DNS server
search ahmedkhalaf.in : Default domain name to search.

For example, if you type command nslookup www, it will search it as http://www.ahmedkhalaf.in/
2) Enable the name resolving using DNS as follows:

# cp /etc/nsswitch.dns /etc/nsswitch.conf

3) Test new name server by running the nslookup command as follows:

# nslookup khalaf.in

# /usr/sfw/sbin/nslookup khalaf.inOutput: Server: gwbsd2vsnl.khalaf.in
Address: 192.168.1.202
Non-authoritative answer:
Name: khalaf.in
Address: 202.71.128.225

best regards..

remember do it many time until you be prof.

Kernel Recovery for Solaris INTEL 4.04.01

2010-07-19T22:45:00.000-07:00

Kernel Recovery for Solaris INTEL 4.04.01 description

Kernel Solaris Intel Data Recovery for Solaris INTEL is a unix data recovery tool recovers lost, deletetd or corrupted data from default solaris file system that is UFS File System created using Sun Solaris operating system on INTEL machine.

Solaris Data Recovery Software

recovers solaris operating system data, lost due to following reasons :

Group descriptor block corruption
Damaged super block or inode table
Partition structures are damaged or deleted
Volume Table of Contents (VTOC) corruption
FSCK failed to repair system data structures
Improper system shutdown

Main Screen of Kernel Recovery for Solaris INTEL

Recovery Screen of Kernel Recovery for Solaris INTEL

Found data listed in tree like structure by Kernel Recovery for Solaris INTEL

Download Demo Version of Kernel Solaris INTEL, Full-featured Evaluation Version. Once you are satisfied, simply purchase the Full version.

Mac theme for Solaris 100% works Good.

2010-07-19T02:11:00.000-07:00

Make your Solaris desktop look like a Mac,YES it can be here ...!!!!

Steps To Do:

Download these :

GTK2 Theme with metacity from MacOS-X Aqua Theme
http://shareit.yousomething.com/index.php?hash=3ef815416f775098fe977004015c6193

Icon theme from MacOS-X Aqua Theme
http://shareit.yousomething.com/index.php?hash=c9e1074f5b3f9fc8ea15d152add07294
Wallpaper for MacOS-X Aqua Theme
http://shareit.yousomething.com/index.php?hash=c7e1249ffc03eb9ded908c236bd1996d
Installation procedure:

[Part 1] GTK2 Theme
Step 1 : If you have got the old version before, then delete the old version.
rm -Rf ~/.themes/MacOS-X
if not, skip this step.
Step 2 : Unpack the downloaded file.
tar zxf 13548-Gnome_MacOS-X_Aqua_Theme_20040730.tar.gz
Step 3 : Move the entire folder named "MacOS-X" into ~/.themes
mv MacOS-X ~/.themes
[Part 2] Icon Theme
Step 1 : If you have got the old version before, then delete the old version.
rm -Rf ~/.icons/MacOS-X
if not, skip this step.
Step 2 : Unpack the downloaded file.
tar zxf Gnome_MacOS-X_Icon_Theme_20040730.tar.gz
Step 3 : Move the entire folder named "MacOS-X" into ~/.icons
mv MacOS-X ~/.icons
Have Fun.. ;)

______________________________________________________________________

That was the old one you may try the new theme that i installed on my solairs

from here you can download the theme and icons...which i didn't install cause of time :)

http://gnome-look.org/content/show.php?content=13548

Best Regards.

Access NTFS partition from Solaris

2010-07-19T02:04:00.000-07:00

How to Access NTFS partition,

Here is the steps:
1) Install the FSWpart package Download http://www.belenix.org/binfiles/FSWpart.tar.gz Uncompress: gunzip -c FSWpart.tar.gz | tar xvf - Install: pkgadd -d . FSWpart

2) Install the FSWfsmisc package Download http://www.belenix.org/binfiles/FSWfsmisc.tar.gz Uncompress: gunzip -c FSWfsmisc.tar.gz | tar xvf - Install: pkgadd -d . FSWfsmisc

3) prtpart /dev/rdisk/c0d0p0 -ldevs This will display all the partitions in this format ==> /dev/dsk/c0d0pN : FAT/NTFS NOTE : N means 0,1,2,3 etc.
4) Now to mount the particular NTFS partition Example :
mkdir /mnt/c mount -F ntfs /dev/dsk/c0d0p1 /mnt/c

if you have more than one partition, than make more directories in '/mnt/' and put the address (/dev/dsk/..)

Best Regards.

Solaris 10 10/08 : Free Download

2010-07-19T01:36:00.000-07:00

Solaris 10 description

Solaris Operating System

Solaris is a proprietary UNIX-like operating system, developed by Sun Microsystems. Early versions, based on BSD UNIX, were called SunOS. The shift to a System V code base in SunOS 5 was marked by changing the name to Solaris 2. Earlier versions were retroactively named Solaris 1.x. After version 2.6, Sun dropped the "2." from the name.

Solaris consists of the SunOS UNIX base operating system plus a graphical user environment. Solaris is written in a platform-independent manner and is available for SPARC and x86 processors (including x86_64). Historically, Solaris used to be a proprietary operating system, however, starting from version 10, its licence has changed and the product is now distributed free of charge for any system or purpose, while its source code is available from OpenSolaris.org under a license approved by Open Source Initiative (OSI).

What's New in This Release:

"

What's new in Solaris 10 10/08:

The new version builds on the core strengths of the Solaris 10 to help customers maximize asset usage and systems performance, manage datacenter complexity, preserve business continuity and reduce costs. Solaris 10 10/08 includes numerous product updates and enhancements, several of which were done through the OpenSolaris community. New features in Solaris 10 10/08: the ZFS file system has been enhanced with recent work from the OpenSolaris community; Solaris 10's virtualization technologies, such as Solaris Containers, have been enhanced with new features; Sun and Intel continue to collaborate to help ensure Solaris 10 will support Intel's latest Intel Xeon processor line.

"

Download page (registration required)

Building IPC Portlets for Sun Java System Portal Server 7 With Sun Java Studio Creator 2 part 1

2010-02-18T01:52:00.000-08:00

Building IPC Portlets for Sun Java System Portal Server 7 With Sun Java Studio Creator 2

With portlets that support Interportlet Communication (IPC), you can make them aware of each other's behavior and display content consistently. This article describes how to create an IPC portlet for Sun Java System Portal Server 7 (henceforth, Portal Server) with the Sun Java Studio Creator 2 IDE (henceforth, Java Studio Creator). The portlet can subscribe to all IPC events and display the events in a table.

An appendix at the end of this article shows you how to deploy an IPC portlet to Sun Java System Web Server 6.1 (henceforth, Web Server).

Contents:

- Installing Portal Server and Java Studio Creator - Displaying Sample IPC Portlets - Creating an IPC Portlet With Java Studio Creator - Deploying the Portlet - Appendix: Deploying on Sun Java SystemWeb Server 6.1 - References

Installing Portal Server and Java Studio Creator

First, install Portal Server and Java Studio Creator:

Download and install Portal Server 7.

Download and install Java Studio Creator.

Displaying Sample IPC Portlets

Portal Server includes sample IPC portlets that demonstrate the use of IPC techniques. To see those portlets in action:

Log in to the Portal Server desktop at http://hostname:portnumber/portal/dt.

A welcome page is displayed. See Figure 1.

Figure 1: Portal Server Welcome Page

Click Developer Sample under SAMPLES. At the login page, type developer in both the user name and password fields.

The developer sample portal is displayed. See Figure 2.

Figure 2: Developer Sample Portal

Click the Interportlet Communication tab.

All the IPC portlets in this sample are displayed. See Figure 3.

Figure 3: IPC Portlets in Developer Sample

Now try out the portlets and observe their behavior. For example, type 345 in the text field under PricePortlet and click OK. After the page refreshes, click OK in SearchPortlet to trigger IPC messaging events between the portlets. The portlets then display a desktop similar to that in Figure 4.

Figure 4: Desktop After Triggering of IPC Messaging Events

Install Sun Java System Portal Server 7.1

2010-02-18T01:42:00.000-08:00

To Install Sun Java System Portal Server 7.1

From the installation location, go to the OS-arch directory, where OS-arch can be Solaris_sparc, Solaris_x86, or Linux_x86.
Run ./installer to invoke the wizard to install the software.
In the Welcome screen, click Next.
In the Software License Agreement screen, read the agreement and click Yes, Accept License.
The Choose Software Components screen appears. Select Portal Server 7.1.
When this option this selected, the following components are selected by default:
- The Directory Preparation Tool
- Service Registry 3.1
- Access Manager 7.1 and related sub components of Identity Management and Policy Services
- Directory Server Enterprise Edition 6.0 including the Directory Server Core
- Java DB 10.2
Select the other software components that you want to install.
- To install Secure Remote Access (SRA) services, select Portal Server Secure Remote Access 7.1. When you select this option, the Gateway, Netlet Proxy, and the Rewriter Proxy are selected by default.
- To install Application Server, select Application Server Enterprise Edition 8.2 . When you select this option, the Domain Administration Server, Command Line Administration Tool, and Sample Applications for the Application Server are selected by default. The Application Server High Availability Session Store 4.4 and Sun Java System Message Queue 3.7 UR1 are also selected by default.
  
  Note –
  Select this option if you need EJB container for portal.
- To install Web Server, select the Sun Java System Web Server 7.0. When you select this option, the Web Server CLI, Web Server Core, and Web Server Samples are selected by default.
  
  Note –
  Select this option if you require only Web Applications.
- To install multilingual support for the selected Java ES components, select Install Multilingual Packages for Selected Component(s).
  
  Note –
  If J2SE-SDK or any shared components require upgrade, the installer displays the corresponding screens. By default, installer upgrade them with the latest version in the installer disk.
The Shared Component Upgrades Requires screen is displayed if any one of the shared components requires upgrading. Click Next to upgrade these shared components.
On the Specify Installation Directories page, specify the installation directory for the software. The following are the default locations. Use the Browse button to change the default location. Click Next.

Access Manager

/opt

Application Server

/opt/SUNWappserver

Application Server: Data and Configuration

/var/opt/SUNWappserver

Directory Server

/opt/SUNWdsee

Directory Preparation Tool

/opt/SUNWcomds

Web Server

/opt

Web Server Instance

/var/opt/SUNWwbsvr7

Service Registry

/opt

Portal Server

/opt

The Verify System Requirements screen is displayed. The installer verifies each of the listed system requirements and displays OK if the requirements are met. If the installer indicates that all the requirements are met, the System Ready for Installation message appears. Click Next to continue with the installation. In case any of the requirements are not met, a text indicating the same appears with the following options: View Reports and Check Again. The View Report option provides the details about the requirements that are not met. It is recommended that you address these issues. After the requirements are met, click the Check Again option to verify whether the requirements are met.
Click Next to continue the installation.
The Choose a Configuration Type screen is displayed.
Select Configure Now, and click Next.
The installer only supports adding one portal and one instance only. For any other configuration, the Configure Later option must be selected. If the Configure Now option is selected, after the packages are installed, the configuration starts immediately.
Select Configure Now, and click Next.
The Custom Configuration screen is displayed.
Service Registry 3.1 and Java DB are not configured during the installation. It can be configured after the installation. Click Next.
The Specify Administrator Account Preferences screen is displayed.
Enter the Administrator ID and password. Type the password, and click Next.
You are also provided with an option to select different administrator accounts for each product.
The Specify Common Server Settings screen is displayed.
Specify the following server settings:

Host Name, DNS Domain Name, and Host IP Address

Host name, domain, and IP address of the system. The installer automatically displays these values.

System User and Group

System user name and group ID. For Solaris 10 OS and Linux, the default is root for system user name and root for group ID. For Solaris 9 OS, the default is root for system user name and other for group ID.

Note –
Values you enter here appear as default values during the rest of the installation.
If you have selected Web Server as a component to install, the Choose Configuration Type screen is displayed. You have an option to configure administration instance as a server or as a node. By default, configure administration instance as server is selected. Click Next.
If you have selected Web Server as a component to install, the Web Server: Specify Administration Server Settings and Web Server: Specify Instance Settings screens are displayed. Provide the information for Web Server, and click Next.

Note –
Specify the Runtime Unix user ID as root.

You need to specify the following details for the Web Server: Specify Administration Server Settings screen:

Server Host

The default value is automatically created by joining the values that you provided for Host Name and DNS Domain Name under Common Server Settings. The value has the format hostname.domainname.

SSL Port

The default value is 8989.

HTTP Port

Port on which Web Server listens for HTTP connections. The default is 8800.

Runtime User ID

User ID that the default instance of Web Server uses to run on the system. The default is root.

You need to specify the following details for the Web Server: Specify Instance Settings screen:

Server Name

A host and domain value that resolves to the local host. The value has the format hostname.domainname.

HTTP Port

Port on which Web Server listens for HTTP connections. The default value is 80.

Runtime UNIX User ID

An existing non-root user. If you are installing Access Manager or Portal Server, set this value to root and set the Runtime Group to other. You can change these values after installation. For other servers, the Runtime User ID should be a non-root user. The default value is webservd.

Document Root Directory

Location where Web Server stores content documents. For Solaris OS, the default value is /var/opt/SUNWwbsvr7/docs. For Linux and HP-UX, the default value is /var/opt/sun/webserver7/docs.
The High Availability Session Store (HADB): Specify Configuration Data screen is displayed. The Installer displays the default values. This screen is displayed only if you have selected Application Server as a component to install. Click Next.

HADB Management Port

Port on which the HADB management listens. The default value is 1862.

HADB Resource Directory

Location where HADB stores resource contents. The default value is /var/opt.

HADB Administrator Group

The UNIX group (GID) in which the default instance of HADB runs as a user. The default value is other.

Automatically start HADB when system starts

Choose this option to direct the installer to configure HADB to start automatically when the system restarts. By default, this is selected.

Allow Group Management

Choose this option when you want HADB to be managed by the HADB Administration Group. If this parameter is set to yes, all members belonging to the group (HADB_DEFAULT_GROUP) can run and manage HADB. By default, it is set to No.

The Application Server: Domain Administration Server screen is displayed.
Provide or change values in the installer pages as needed and click Next.
The installer displays the default values. This screen is displayed only if you have selected Application Server as a component to install.

Admin Port

Port on which Application Servers administrative server listens for connections. By default, it is 4849.

JMX Port

The default is 8686.

HTTP Port

The default value is 8080. If the installer detects that the default port is used, an alternative value is suggested.

HTTPS Port

The default is 8181.

Master Password

SSL certificate database password, used for asadmin operations such as Domain Administration Server startup and Node Agent startup. The default value is the Administrator Password you provided under Common Server Settings.

The Application Server: Node Agent screen is displayed.
Specify the details and click Next.
This screen displays only if you have selected Application Server as a component to install.

Admin Host Name

Host name for administration server which the node agent can connect to.

Admin User Name

User ID of the Application Server admin user. The default value is the Administrator User ID you provided under Common Server Settings.
If you chose to use a single administrator account, this field is not present.

Password

Password for the Application Server admin user. There is no default value.
If you chose to use a single administrator account, this field is not present.

Master Password

SSL certificate database password, used for asadmin operations such as Domain Administration Server startup and Node Agent startup. There is no default value.

Admin Port

Port on which Application Servers node agent listens for connections. Provides access to the administration tools. The default value is 4849.

Node Agent Name

Name of the local node. The default value is the local host name

The Application Server: Configure Load Balancing Plugin screen is displayed.
Specify the details and click Next.
This screen displays only if you have selected Application Server as a component to install.
Web server that the load balancing plugin will use

You can select either Sun Java System Web Server or Apache Web Server. HP-UX does not support Apache Web Server.

Web server installation directory
Installation directory for Web Server or Apache HTTP Server.
The default value is:
- Solaris OS: /opt/SUNWwbsvr7
- Linux and HP-UX: /opt/sun/webserver7
Web Server instance directory
Installation directory for Web Server or Apache HTTP Server.
The default value is:
- Solaris OS: /var/opt/SUNWwbsvr7
- Linux and HP-UX: /var/opt/sun/webserver7
The Directory Server: Specify Instance Creation Information screen is displayed.
Specify the information for Directory Server instance creation and click Next.

Instance Directory

Location of new instance.

Directory Instance Port

The default value is 389.

Directory Instance SSL Port

The default value is 636.

Directory Manager DN

Distinguished Name (DN) of the user who has unrestricted access to Directory Server. The default value is cn=Directory Manager.

System User

The default value is root.

System Group

The default value is root.

Directory Manager Password

Password for the directory manager.

Suffix

Initial directory suffix managed by this instance. The default value is formed by the segments of the fully qualified domain name for the current host. For example, if you install on siroe.sub1.example.com, the default value is dc=sub1,dc=example,dc=com.

For more information, see Directory Server Configuration Information in Sun Java Enterprise System 5 Installation Reference for UNIX.
The Access Manager: Specify Configuration Information screen is displayed.
Specify the information for the Access Manager configuration and click Next.

Install type

Indicates the level of interoperability with other components. You have a choice of Realm mode (version 7 style) or Legacy mode (version 6 style). Default option is Legacy mode. You must use Legacy mode if you are installing Access Manager with Portal Server, Messaging Server, Calendar Server, Delegated Administrator, or Instant Messaging. The default value for Legacy mode is Enabled. The default for Realm mode is Disabled.

Note –
Portal Server supports Realm mode only if Sun Java System Directory Server is used as a user repository and Access Manager SDK is configured as the datastore plugin for the Realm mode. If you select the Configure Now option for the Realm mode, the installer does this by default.

Administrator User ID

Access Manager's top-level administrator. This user has unlimited access to all entries managed by Access Manager. The default name, amadmin, cannot be changed. This ensures that the Access Manager administrator role and its privileges are created and mapped properly in Directory Server, allowing you to log into Access Manager immediately after installation.

Administrator Password

Password of the amadmin user. The value must have at least eight characters.

LDAP User ID

Bind DN user for LDAP, Membership, and Policy services. This user has read and search access to all Directory Server entries. The default user name, amldapuser, cannot be changed.

LDAP Password

Password of the amldapuser user. This password must be different from the password of the amadmin user. It can be any valid Directory Service password.

Password Encryption Key

A string that Access Manager uses to encrypt user passwords. For security purposes, it is recommended that the password encryption key be 12 characters or longer.

Note –
amAdmin and amldapuser password should be different.

For more information, see the Access Manager Configuration Information in Sun Java Enterprise System 5 Installation Reference for UNIX.

Note –
Portal Server supports installing Access Manager in the Realm mode or in the Legacy mode.
The Access Manager: Choose Deployment Container screen is displayed.
You can select either Sun Java System Web Server or Sun Java System Application Server. Select the option, and click Next.
For more information about configuring Web Server, see the Web Server Configuration Information in Sun Java Enterprise System 5 Installation Reference for UNIX in Sun Java Enterprise System 5 Installation Reference for UNIX.
For more information about configuring Application Server, see the Sun Java Enterprise System 5 Installation Reference for UNIX
The Access Manager: Specify Sun Java System Application Server screen is displayed.
Specify the details and click Next.
This screen is displayed only if you have selected Sun Java System Application Server as the web container for Access Manager.

Secure Server Instance Port

Specify whether the value for Instance Port refers to a secure port. A secure port uses the HTTPS protocol. A non-secure port uses HTTP.

Secure Administration Server Port

Specify whether the value for Administrator Port is a secure port. A secure port uses the HTTPS protocol. A non-secure port uses HTTP.

The Access Manager: Specify Web Container for Running Access Manager Services screen is displayed.
Specify the details for Access Manager and click Next.

Host Name

Fully qualified domain name of the host on which you are installing.

Services Deployment URI

Uniform Resource Identifier (URI) prefix for accessing the HTML pages, classes, and Java Archive (JAR) files associated with the Identity Management and Policy Services Core subcomponent. The default value is amserver. Do not enter a leading slash.

Common Domain Deployment URI

URI prefix for accessing the common domain services on the web container. The default value is amcommon. Do not enter a leading slash.

Cookie Domain

The names of the trusted DNS domains that Access Manager returns to a browser when Access Manager grants a session ID to a user. A leading dot (.) is required for each domain in the list. The default value is the current domain, prefixed by a dot (.).

Password Deployment URI

URI that determines the mapping that the web container running Access Manager will use between a string you specify and a corresponding deployed application. The default value is ampassword. Do not enter a leading slash.

Console Protocol

Specify whether the console uses a secure or unsecure port. A secure port uses the HTTPS protocol. A non-secure port uses HTTP. The default is HTTP.

The Access Manager: Choose Access Manager Console screen is displayed.

Note –
This screen is displayed only if you select the Legacy mode to install Access Manager.
By default, Deploy New Console is selected. Click Next.

Administration Console

Choose Deploy new console to deploy the console into the web container of the host on which Access Manager is being installed. Choose Use existing console to use an existing console that is deployed on a remote host.

Console Deployment URI

URI prefix for accessing the HTML pages, classes, and JAR files associated with the Access Manager Administration Console subcomponent.The default value is amconsole.

Console Host Name

Fully qualified domain name for the server hosting the existing console. This value is not needed if you are deploying a new console. You can edit the field only if you are using an existing console.

Console Port

Port on which the existing console listens for connections. Permitted values are any valid and unused port number, in the range 0 (zero) through 65535.

The Access Manager: Choose Directory Server Instance screen is displayed.
Use the Directory Server Instance that you just created. Click Next.

Note –
If you choose to use an existing instance instead of the default, the alternate instance must already be configured.
The Access Manager: Specify Directory Server Data screen is displayed.
You can select Yes or No for the option: Is Directory Server is Provisioned with User Data. By default, No is selected. If you select Yes, you need to provide the related information. Click Next.
If you have selected Application Server as the deployment container for Access Manager, the Specify Sun Java System Application Server Information screen is displayed. Click Next.

Secure Server Instance Port

This protocol specifies whether the value for Server Instance port refers to a secure port. A secure port uses the HTTPS protocol. A non-secure port uses HTTP.

The Portal Server: Specify Web Container Deployment Information screen is displayed.
Specify the Web Container deployment information and click Next.

Portal Access URL

The default is host name:port/portal1.

Portal ID

The default is portal1.

Search ID

The default is search1.

Deployment URI

The default is /portal.

Portal Instance ID

The default is hostname-8080.

Select the Enable Secure Remote Access option, if you wish to enable Secure Remote Access. Select Developer Sample, Enterprise Sample, and Community Sample if you wish to configure samples.
The Portal Server: Secure Remote Access screen is displayed. The Portal Server: Secure Remote Access: Configure Gateway screen is displayed.
Enter the following information and click Next.

Gateway Protocol

It is https by default.

Portal Server Domain Name

Portal Server domain name.

Gateway Domain

Gateway domain.

Gateway Port

It is 443 by default.

Gateway Profile Name

It is default by default.

Log User Password

The user password
Specify the details and click Next.

Protocol

Protocol (HTTP or HTTPS) the gateway uses to communicate. In most cases the gateway should use HTTPS.

Host Name, Subdomain, and Domain

The name, subdomain, and domain name of the machine on which the Gateway proxy resides. By default, the system values are used.

Host IP Address and Access Port

The host IP address on which the Gateway Proxy resides. By default, the IP address is the IP address of the system and port is 443.

Gateway Profile Name

The gateway profile name. By default, the gateway profile name is default.

The Portal Server: Secure Remote Access: Configure Netlet Proxy screen is displayed.
Specify the following information for the Netlet Proxy.

Host Name, Subdomain, and Domain

The name, subdomain, and domain name of the machine on which the Netlet proxy resides. By default, the system values are used.

Host IP Address and Access Port

The host IP address on which the Netlet Proxy resides. By default, the IP address is the IP address of the system and port is 10555.

Gateway Profile Name

The gateway profile name. By default, the gateway profile name is default.

Click Next.
The Portal Server: Secure Remote Access: Configure Rewriter Proxy screen is displayed.
Specify the following information to install the Rewriter Proxy.

Host Name, Subdomain, and Domain

The host name, subdomain, and domain name of the machine on which the Rewriter Proxy resides. By default, the system values are used.

Host IP Address and Access Port

The Host IP address and access port of the machine on which the Rewriter Proxy resides. By default, the IP address is the IP address of the system and port is 10443.

Gateway Profile Name

The gateway profile name. By default, the gateway profile name is default.

Click Next.
The Portal Server: Secure Remote Access: Specify Certificate Information screen is displayed.
Specify the following certificate information for the Secure Remote Access.

Organization, Division, City/Locality, State/Province

The organization name, division, city, and state information.

Country Code

The country code in two character format.

Certificate Database Password

The certificate database password must be at least eight characters.

Click Next.
The Ready to Install screen is displayed. Specify whether you are ready to install by clicking Install.

Verifying the Portal Server 7.1 Installation

Verify the Portal Server installation by doing the following:

Accessing the samples.
Accessing the Portal Server administration console.
Verifying the Gateway port and running the Portal Server in secure mode.

To Verify Sun Java System Portal Server 7.1 Installation

Start Directory Server, web container, and gateway.
Access Portal Server. For example, type the URL in the browser.
http://host.domain-name:port/portal-URI
The welcome page appears. The page displays a short description of Portal server and links to sample portals that you selected for installation. Click on one of the links and access the anonymous portal desktop for the sample portal. If the sample portal desktop displays without exception, your Portal Server installation was successful.
Type http://host.domain-name:port/psconsole.
Verify whether Java DB process is running.
netsatat -an | grep 1527
If Java DB is not running, start Java DB. For more information, refer to To Start and Stop Java DB
Check whether the common agent container is running.
On the Solaris platform, type the following:
/usr/share/bin/cacaoadm status
On the Linux platform, type the following:
/opt/sun/cacao/bin/cacaoadm status
If the common agent container is not running, restart it.
On the Solaris platform, type the following:
/usr/share/bin/cacaoadm stop
/usr/share/bin/cacaoadm start
On the Linux platform, type the following:
/opt/sun/cacao/bin/cacaoadm stop
/opt/sun/cacao/bin/cacaoadm start
Note –
By default, common agent container creates a self-signed CA cert and uses it to sign the server cert of the Cacao agent. The subject DN of this server cert is CN=hostname_agent (or CN=hostname_default_agent on MS Windows). When this default server cert is to be replaced by another server cert signed by the CA of the user's choice, the subject DN of the new server cert must be kept the same as the original one for Portal Server administration to continue function without interruption.
Verify whether Directory Server is running using the following commands:
netstat -an | grep 389
If it is not running, start the Directory Server using the following command:
cd /opt/SUNWdsee/ds6/bin
./dsadm start /var/opt/SUNWdsee/dsins1
Verify whether the Application Server or Web Server is running using the following command:
For Web Server:
netstat -an | grep 80
For Application Server:
netstat -an | grep 8080
If it is not running, start the server using the following command:
For Application Server:
/ApplicationServer_base/Appserver/bin/asadmin
start-domain --user admin domain1
For Web Server:
/var/opt/SUNWwbsvr7/https-host.domain-name/bin/startserv
Run the following command to check if the gateway is running on the specified port (the default port is 443):
netstat -an | grep 443
If the gateway is not running, do the following:
PortalServer-base/bin/psadmin provision-sra -u amadmin -f amadmin-password-file --gateway-profile gateway-profile --enable
PortalServer-base/bin/psadmin start-sra-instance -u amadmin -f amadmin-password-file --instance-type gateway --instance-name gateway-instance-name
1. Create a file and add the amadmin password in plaint text.
2. Also view the log files. The log file name is picked up from the property called debug.com.sun.portal.handler.java.util.logging.FileHandler.pattern in the platform.conf file.
Run the Portal Server in secure mode by typing the gateway URL in your browser:
https://gateway-machine-name:443
If you chose a different port number other than the default port (443) during installation, you need not specify that port number.

____________________________________________________________________

now how to uninstall portal server if any problem or issue ...

Uninstalling Portal Server

Use the following procedure to uninstall Portal Server.

To Uninstall Portal Server

As a root user, log in to the machine where you installed Portal Server.
Change directories to:
- /var/sadm/prod/SUNWentsys5/ on Solaris.
- /var/sadm/prod/sun-entsys5/ on Linux.
Type ./uninstall to uninstall Portal Server.
The Sun Java Enterprise System Uninstall Wizard is displayed.
Select the components to uninstall and select Next.
If you are uninstalling the Secure Remote Access component, you are asked to provide the portal administrator, Access Manager administrator, and LDAP passwords.
Select Uninstall to uninstall the software.

step by step installation Sun Solaris Server

2010-02-18T00:49:00.001-08:00

Power Up and Media Boot

If you don't want to substitute your current operating system and instead you want to run Solaris as a guest OS or Virtual Machine, please download and install xVM VirtualBox for free from http://www.virtualbox.org.

The following procedure can be used to install Solaris 10 5/09 on a new or used system.

Power up the system and insert the first installation CD or DVD into the drive tray.
Restart the system.
If the system appears to be booting from the hard disk and the Solaris OS installer does not start, power cycle the system (power cycle is shutting down the power on the system and then restarting the system). As the system begins to boot, enter setup mode. Typically, the system displays a message indicating which key to press (such as "Enter F2 to enter setup", although the key to press varies by manufacturer; the ESC and F12 keys are other common options.) If you miss the message, simply restart the system a couple of times until you are able to view it.
Once in setup mode, specify the boot device for the system. This example specifies the CD or DVD drive as the boot device. To do so, find the list that describes boot order and re-order as needed to ensure the CD or DVD drive appears first on the list. The system should then boot from the CD or DVD drive to start the install process.

Installing the Solaris 10 5/09 Operating System

Identifying the Console

The next step in the installation process is to select the type of console for the hardware on which the Solaris OS is being installed. Use the arrow keys to select the version of the Solaris OS that matches the hardware configuration. For most x86 systems, use the default selection.

Press the ENTER key and boot the version of operating system selected. The highlighted entry boots in 60 seconds even if a key is not pressed.

Note: Prompts do not appear during the boot process. If a selection is not made, the screen times out and the system automatically boots the Solaris OS.

Selecting the Type of Installation

After the ENTER key is pressed or the counter times out, a series of dots will run on the screen and you will see the basic device configuration message along with a menu with six installation options.

Before this new counter times out, select option 3 to install Solaris 10 5/09 from the beginning using Solaris ZFS as the root file system. You can get more information on ZFS from http://www.sun.com/software/solaris/zfs.jsp.

Note: If you don't want to use ZFS as your root filesystem, you can use option 1. Please refer to the previous version of this "How To Guide."

Once option 3 is selected, you'll see the following screen with some information regarding your hardware. Keep in mind that the hardware information displayed (such as "nge0") may differ from the exact data displayed below and that each step can take up to a couple of minutes to complete:

After a few seconds, you are presented with the keyboard layout configuration in case you don't have a standard keyboard or if you have a localized keyboard. If you have a US keyboard, press the [F2] key; if not, select the right language using the arrow keys to move up or down, make your selection with the [space bar] and then press [F2] to continue.

Immediately, you'll see the following message. Press ENTER to continue.

System Configuration

A series of screens guides you through the Solaris OS configuration process.
Note: The graphical screens require a mouse to be rolled over the window in order to answer questions posed throughout the configuration process.

After you press ENTER, the system configuration process will start through a series of windows. Please roll the mouse over the window, click the mouse, then press ENTER to continue.
Select a language for the system.
A new window, the Solaris Install Console, appears in the bottom-right corner. This window is used to display pertinent installation messages. Another window appears in which the Solaris OS installation questions should be answered. Press [F2] to continue.
The system identification process begins. Press [F2] to continue:.
The Network Connectivity window appears. Use the default answer, (unless you don't have a network) and press [F2] to continue.
The DHCP selection appears. For most cases, just select DHCP for your network configuration using the arrow keys and the space bar to make the selection and then press [F2] to continue.
The IPv6 window appears. Just use the default and press [F2] to continue.
The Confirmation window appears. If you agree with your selections, press [F2] to continue; if not, press [F4] and the process will go back to step 5.
The Security Policy window appears. Use the default for No Kerberos configuration, then press [F2] to continue.
For confirmation of your policy selection, press [F2] and continue to the next screen.
The Name Service window appears. Select NONE using the arrow keys and pressing the space bar to select, then press [F2] to continue.
For confirmation of your selection, press [F2] and continue to the next screen.
The NFSv4 domain name window appears. Let the system use the default option and press [F2] to continue.
For confirmation of your selection, press [F2] to continue to the next screen.
The Time Zone window appears. Next, set the time zone for the system. This example sets the Americas time zone. Use the arrow keys and the space bar to make the selection, then press [F2] to continue.
Time Zone cont'd. Set the United States Country & Region, then press [F2] to continue.
Time Zone cont'd. Set the Pacific Time, then press [F2] to continue.
Set current date and time. Use arrow keys and keyboard to change the proposed date and time, then press [F2] to continue.
To confirm your selection, press [F2] to continue.
The Root Password window appears. Set the root password. Note the password typed remains invisible. Re-enter the password in the second box and press [F2] to continue.
The Network Services window appears. Click [F2] to continue.
The Remote Services window appears. In this window, you can choose a "Secure by default" Solaris installation, but afterwards individual services should be enabled. If you are unsure of your type of installation, follow the default "Yes" to enable all remote services and press [F2] to continue.
The Install Progress window appears. Wait for a few minutes while Solaris installs on your system. After the installation is completed, the system will reboot automatically and will start the Solaris OS. Remember that in some cases, you will have to eject the media manually.
The Eject CD/DVD window appears. Use the default. Press [F2] to continue; the system will automatically eject the media after installation.
The Reboot After Installation window appears. Use the default, press [F2] to continue.
The Confirmation window appears; press [F2] to continue. In some cases, the system will not be able to eject the media after installation. Be sure to eject it manually to avoid starting the installation process again; if after the installation your system didn't eject the media and the install process started again, you can simply reboot your system. During the boot process, eject the media and the system will boot from the hard disk using the freshly installed Solaris 10 image.
The License window appears. Please read the Solaris License Agreement, and if you agree, press [F2] to continue.
The Geographic Regions window appears. To add support for other regions, select the desired region; if not, press [F2] to continue.
The System Locale window appears. Press [F2] to continue.
The Selection of Additional Products window appears. Press [F2] to continue.
The Root File System selection window appears. Select ZFS and press [F2] to continue.
The Software Selection window appears. Use the default and press [F2] to continue.
The Disk Selection window appears. Use the default and press [F2] to continue.
The ZFS Configuration window appears. Use the default and press [F2] to continue.
The Remote Mounts window appears. Use the default and press [F2] to continue.
The Profile window appears. On this window, you can see a technical description of how Solaris will be installed on your system. Press [F2] to continue.
The Install Progress window appears. Wait for a few minutes while Solaris installs on your system. After the installation is completed, the system will reboot automatically and will start the Solaris OS. Remember that in some cases, you will have to eject the media manually.
Now you have successfully installed Solaris 10 5/09 on your system. Login using the root user and the password you assigned on step 19.

Best regards.

wait for your lovely comment : )

How to setup more than 255 virtual ethernets

2009-12-25T12:03:00.000-08:00

Introduction:

Solaris 8 can support up to 8192 virtual ethernets per card (HME, QFE or GE). On virtual interfaces greater than 255 and on Solaris 8, the following needs to be considered:

It will take over 1 hours to plumb and IP address all of the interfaces.
You will need to create an RC script to due the setup.
You should consider using RUN level 4 (init 4) for starting the interfaces.
You will need to run an NDD command to allow that many interfaces.
You will need to consider networking and routing issues (not covered by this FAQ)
FYI: Don't try creating 8192 files (hostname.hme:????). It won't work and it will take 2 hours for the system to boot with errors.

Step 1.

Modify /etc/init.d/inetinit

Add the following line to the bottom:

"/usr/sbin/ndd -set /dev/ip ip_addrs_per_if 8192" (8192 is the max number of interfaces)

Step 2.

Create a start/stop script in /etc/init.d/ and link to K & S scripts. This sample was orginally found in SUN Solve infodoc 16369 and was modified. When I have time I am going to re-write this as bourne shell and consider some methods for parallizing it.

script follows: (download just the script from here)

Name it like (/etc/init.d/virtual.if)

##!/bin/ksh
# Configuration Area
# set this value to the nuber of logical interfaces you want per physical IF
typeset -i N=500
#
#set these to the IP addrs you want to configure
typeset -i IP3=172
typeset -i IP2=16
typeset -i IP1=10
typeset -i IP0=0
typeset -i n=0
# What kind of interface (le, hme, qfe, ge)
PIF=hme0
# No Changes below this line
##################################################
while ((n Step 3:
Test the ndd and the script prior to linking the start/stop script.
Make the script executable (chmod +x /etc/init.d/virtual.if)

Step 4:

Link the scripts
(I recommend putting it in run level four and changing the inittab when you get everything working otherwise)
ln /etc/init.d/virtual.if /etc/rc2.d/K10virtual.interfaces
ln /etc/init.d/virtual.if /etc/rc3.d/S99virtual.interfaces

Caveats and issues:

1)Consider putting in a hostname into etc hosts.

2)Consider setting up IPMP in Solaris 8

3)Make sure that your application does not bind to all IPs unless you want it to.

4)Some software may have real issues (unnamed Database company specific version) with too many virtual interfaces. This is a warning for good trouble shooting.

5)Consider looking into this parameter "tcp_deferred_ack_interval=1" if you are going to be transferring lots of small files.

6)It takes a really long time to configure this many interfaces.. *HOURS*

Amazing Sun server in the hole world

2009-09-25T18:08:00.000-07:00

Now wounder why IBM Company did a lot of effort to expend and marketing them own product in towards put 1000$ U.S Dolor support of parts

here is the presentation on new super server.

AXIGEN Mail Server

2009-09-25T06:29:00.000-07:00

A perfect answer to the complex challenges and requirements of collaborative Enterprises, the AXIGEN Mail Server features Groupware, Personal Organizer, Public Folders, Account Classes and much more. Offering advanced security policies and efficient 24x7 technical support services, the Enterprise messaging solution targets businesses with elaborate hierarchies and managing one or more offices

Features:

• Shared folders & permissions with other (groups of) users
• Grant permissions on specific folders to a user group
• Permissions: backed-up & restored using FTP-Backup
• Personal Organizer: Calendar/Tasks/Journal/Notes & collaborative support available from WebMail & Outlook
• Active Directory Integration
• Outlook Rules Wizard
• Multiple AntiVirus & AntiSpam support
• Anti Impersonation policies
• Password Enforcement Policies
• SMTP Firewall
• Built-in Milter support
• Clustering support
• Delegated Administration
• Comprehensive charts & statistics
• SNMP support
• Single storage of emails sent to multiple recipients
• Automatic migration tools
• and many more...

Installation

Being accompanied by comprehensive documentation, the AXIGEN Mail Server installation is a pretty straightforward process and can be done by almost anybody, provided they have at least some base Linux terminal knowledge, as it needs su privileges. And knowing that this product is mainly for IT professionals, the command-line installation is as easy as it can be. Leaving that aside, it is also very fast and you will be ready to configure your settings in no more, probably less, than two minutes. After the install process is finished, the services won't start automatically, as you must do the initial configuration: setting the admin password, primary domain, SMTP and POP3 interfaces etc. Fast forward, and you are ready to start your mail server, but not before shutting down other web or mail services (Apache, Sendmail, Postfix, IMAPD, Dovecot) that could interfere with AXIGEN. That being done, simply run the following two commands "sudo /etc/init.d/axigen start" and "sudo /etc/init.d/axigenfilters start" and you have a working mail server ready to be further tweaked to your needs using the simple, clean and efficient web interface.

The Web Interface

After typing in the password, you enter the WebAdmin panel and everything is exactly where you would expect it to be. The left pane displays all the categories, the middle pane shows the settings for the selected subcategory, and on the right, Contextual Help is available for quick understanding of what's going on in that page. Also, in the upper-right hand corner of the interface, a "Home" icon will appear if you leave the first page. Near it, a useful "Contact Support" link will accompany you on every screen, facilitating a quick access to assistance.

The first category is "Global settings" in which you can view your Primary Domain and the SSL Random File. Under that, another panel will display license information like the numbers of machines and mailboxes that are managed, the Tech Support provider, currently installed addons and other details regarding the limitations of the license you bought.

The Services category is where you start, stop, restart and configure all of AXIGEN's mail services (POP3, IMAP, SMTP, etc.). The very thorough configuration subcategories allow you to customize your server to the finest details. A simple Log Level slider exists in almost all settings pages and will instruct AXIGEN to either log everything or only critical events. The Flow control will allow you to limit the number of simultaneous connections and the maximum connections per x seconds, minutes, hours or days. Error control will close sessions after a number of invalid commands received from clients or failed authentication attempts. This number can range from 0 to 100. There is also support for the StartTLS technology – a quality Encryption and Authentication method and Thread Management for normal or overload situations. You can even set the Greeting message for the POP3 and IMAP services. Another "safety net" provided by AXIGEN is Email Loop Protection that will reject emails that have more than "X" received headers.

The Domains & Accounts control panel is pretty self-explanatory, letting you manage your domains, accounts, groups, mailing lists, public folders and account classes. A nifty feature that you'll come across when adding a new account, group, mailing list or account class for multi-domain servers comes in the form of an autocomplete field that will filter domains while you type, saving precious time or just helping you through a memory lapse.

Security and Filtering

With huge amounts of spam, malware and viruses coming 24/7 from all over the world, the true power of a mail server solution might just stand in its ability to filter out these pests constantly while still allowing legit emails to get through. AXIGEN is able to work with several applications to address these issues. Support for SpamAssassin, AVG, AVAST, ClamAV, Commtouch, amavis is available, along with the more generic aximilter interface, which enables connecting to even more security or filtering products. All these solutions will attempt to clean infected emails and if that's not possible it's your choice what to do next. You can either still deliver them, move them to trash or just discard them. The same goes for emails marked as suspicious. The AntiSpam configuration features two 0-10 thresholds with 0 meaning not spam and 10 being spam. After receiving a score from SpamAssasin, the messages will either be sent to the SPAM folder or deleted, according to the readout on the threshold. For example, if you set the "move to spam" threshold at 5 and the "delete" threshold at 8, all messages that get a 5 or higher score will be moved to the spam folder and those with an 8 or higher score will automatically be deleted. Very, very helpful and so easy. Of course, you can always integrate your favorite AntiVirus solutions and create Whitelists and Blacklists for specific addresses. Other anti-spam methods include country filtering (in collaboration with MaxMind geolocation service), Sender Policy Framework, Domain Keys, DNS BlackLists and DNS Check.

Status and Monitoring

AXIGEN Mail Server offers a comprehensive reporting service and has the ability to create charts for an easy overview of the server's load and activity. You can enable SNMP (Simple Network Management Protocol) and add listeners for it, collect domain and domain object data (with the option of renewing samples at an interval ranging from 0 to 848 weeks) and set the logging level.

When creating a new chart, you are asked to name it and add it to an existing group, or create a new one. Next, set the start/end time and dates, choose the data you want to be used, play around with the colors if you don't like the default ones and that's it. It will start monitoring and you can, at any time, download the collected data summary either as a CSV or an XML file.

The storage chart will give you a quick look at how much space is being used, but you can also view a detailed version of it, which provides more in-depth information. Note that AXIGEN Mail Server will only use what it needs to use, with an auto-expanding storage size (of course, within the limits imposed by you).

In the logging subcategory you can decide whether you want to separate service logs or centralize them in a single file. You can also view saved logs (.txt extension) right from the interface.

Migration and Back-up

AXIGEN offers automatic and manual migration solutions through IMAP. All domains, accounts and mailboxes from any mail server platform can be migrated seamlessly; it will even copy the server's login credentials and create an exact replica of it. You simply cannot ask for a simpler tool.

The AXIGEN team also included a complete Back-up & Restore function (with flow, error and thread controls) facilitating full or partial restores and both offline and online backups. This service can also be accessed from more than one location, giving administrators the ability to set access rules for specific IPs. Advanced clustering support with multi-tier setups, LDAP authentication and routing, SMTP routing to back-end, POP3 & IMAP WebMail proxies and integration with the RH Cluster Suite are also available.

End-users are also sure to have a great experience using AXIGEN's email services with features like:

· Localized WebMail clients
· Mobile WebMail
· Personal organizer
· Address book
· Multiple skins
· Printer friendly emails
· Out-of-office messages and much more.

The Good

Fast installation and configuration, quick understanding of all the functions under a very clean and efficient Webadmin interface and a plethora of settings that can be tweaked are some of AXIGEN Mail Server's strong points. Add those to stability, almost unbeatable security and great overall performance and you get this high-class mail server solution.

The Bad

Newer Linux distributions are not fully supported. The AXIGEN mail server refused to start automatically at bootup on Ubuntu 8.10, which was released quite a while ago. But this is definitely not a huge problem and, knowing that Gecad updates the server quite often, I'm sure this bug will be addressed in no time.

The Truth

Whether you are an admin or an end-user, working with or under AXIGEN's mail server is bound to make you a lot more efficient and a lot less worried. Yet another great product from a company worthy of its reputation.

Download it:
here you can chose your suitable Operating System (redhat,ubuntu,solaris ...etc)

Step by Step installation Solaris 10

2009-09-16T15:03:00.000-07:00

Installation Assumptions

This guide makes several assumptions, including:

The system is an x86 system
The system is compatible with the Solaris 10 5/09 OS and is listed on the Solaris Hardware Compatibility List (HCL)
The system has a graphical interface

While this guide is most appropriate for a stand-alone system that doesn't connect to a network or connects to a network with automatic configuration, it can be used to install a system with a fixed IP address if the network configuration information is available.

If problems arise during the installation process that are not discussed in this guide, refer to the Solaris 10 OS Installation Guide: Basic Installations for more information. This guide is part of the Solaris 10 Release and Installation Collection located on the Sun Web site at http://docs.sun.com/app/docs/prod/solaris.10.

Check the Hardware Compatibility List

The first step before the installation process is to verify that the system to be installed is on the hardware compatibility list located at: http://www.sun.com/bigadmin/hcl/.
Note: The term "x86" refers to the family of 32-bit x86-compatible architecture and 64-bit AMD64 and Intel 64.

Basic System Requirements

Verify the computer system meets the following requirements.
NOTE: The requirements below are recommended minimums.

While it is possible to install the Solaris OS on a system with less disk capacity and CPU speed, it is not recommended.

Minimum 1024 MB of physical RAM
Minimum 10 GB of available hard drive space
Minimum 400 MHz CPU speed
DVD or CD-ROM drive
Attached monitor or integrated display

For more information on Solaris System requirements, visit http://www.sun.com/solaris/specs.jsp. For a catalog of the more than 5000 Solaris-ready applications and solutions, please visit http://sun.com/bigadmin/apps.

Obtaining Media for the x86 Platform

The Solaris 10 5/09 OS release is available via download from the Sun Web site.

Go to http://sun.com/solaris/ and click on the Solaris logo if you want to obtain information about the Solaris 10 5/09 OS; if not, proceed to step 2.
Go to http://sun.com/solaris/get.jsp to begin the download process.
Choose Solaris 10 on the list of available downloads.
Click on the appropriate media format (Solaris for x86 systems).
Register at the Sun Download Center, if you have not already done so.
Answer the short questionnaire.
Read and accept the license agreement.
Download and burn the CDs or DVDs.

See the Solaris 10 Self Help FAQs located at http://www.sun.com/solaris/self_help.jsp for additional guidance, instruction, and tips on downloading the Solaris 10 OS or burning installation CD and DVD media.

Power Up and Media Boot

The following procedure can be used to install Solaris 10 5/09 on a new or used system.

Power up the system and insert the first installation CD or DVD into the drive tray.
Restart the system.
If the system appears to be booting from the hard disk and the Solaris OS installer does not start, power cycle the system (power cycle is shutting down the power on the system and then restarting the system). As the system begins to boot, enter setup mode. Typically, the system displays a message indicating which key to press (such as "Enter F2 to enter setup", although the key to press varies by manufacturer; the ESC and F12 keys are other common options.) If you miss the message, simply restart the system a couple of times until you are able to view it.
Once in setup mode, specify the boot device for the system. This example specifies the CD or DVD drive as the boot device. To do so, find the list that describes boot order and re-order as needed to ensure the CD or DVD drive appears first on the list. The system should then boot from the CD or DVD drive to start the install process.

Installing the Solaris 10 5/09 Operating System

Identifying the Console

Press the ENTER key and boot the version of operating system selected. The highlighted entry boots in 60 seconds even if a key is not pressed.

Note: Prompts do not appear during the boot process. If a selection is not made, the screen times out and the system automatically boots the Solaris OS.

Selecting the Type of Installation

Note: If you don't want to use ZFS as your root filesystem, you can use option 1. Please refer to the previous version of this "How To Guide."

Immediately, you'll see the following message. Press ENTER to continue.

System Configuration

After you press ENTER, the system configuration process will start through a series of windows. Please roll the mouse over the window, click the mouse, then press ENTER to continue.
Select a language for the system.
A new window, the Solaris Install Console, appears in the bottom-right corner. This window is used to display pertinent installation messages. Another window appears in which the Solaris OS installation questions should be answered. Press [F2] to continue.
The system identification process begins. Press [F2] to continue:.
The Network Connectivity window appears. Use the default answer, (unless you don't have a network) and press [F2] to continue.
The DHCP selection appears. For most cases, just select DHCP for your network configuration using the arrow keys and the space bar to make the selection and then press [F2] to continue.
The IPv6 window appears. Just use the default and press [F2] to continue.
The Confirmation window appears. If you agree with your selections, press [F2] to continue; if not, press [F4] and the process will go back to step 5.
The Security Policy window appears. Use the default for No Kerberos configuration, then press [F2] to continue.
For confirmation of your policy selection, press [F2] and continue to the next screen.
The Name Service window appears. Select NONE using the arrow keys and pressing the space bar to select, then press [F2] to continue.
For confirmation of your selection, press [F2] and continue to the next screen.
The NFSv4 domain name window appears. Let the system use the default option and press [F2] to continue.
For confirmation of your selection, press [F2] to continue to the next screen.
The Time Zone window appears. Next, set the time zone for the system. This example sets the Americas time zone. Use the arrow keys and the space bar to make the selection, then press [F2] to continue.
Time Zone cont'd. Set the United States Country & Region, then press [F2] to continue.
Time Zone cont'd. Set the Pacific Time, then press [F2] to continue.
Set current date and time. Use arrow keys and keyboard to change the proposed date and time, then press [F2] to continue.
To confirm your selection, press [F2] to continue.
The Root Password window appears. Set the root password. Note the password typed remains invisible. Re-enter the password in the second box and press [F2] to continue.
The Network Services window appears. Click [F2] to continue.
The Remote Services window appears. In this window, you can choose a "Secure by default" Solaris installation, but afterwards individual services should be enabled. If you are unsure of your type of installation, follow the default "Yes" to enable all remote services and press [F2] to continue.
The Install Progress window appears. Wait for a few minutes while Solaris installs on your system. After the installation is completed, the system will reboot automatically and will start the Solaris OS. Remember that in some cases, you will have to eject the media manually.
The Eject CD/DVD window appears. Use the default. Press [F2] to continue; the system will automatically eject the media after installation.
The Reboot After Installation window appears. Use the default, press [F2] to continue.
The Confirmation window appears; press [F2] to continue. In some cases, the system will not be able to eject the media after installation. Be sure to eject it manually to avoid starting the installation process again; if after the installation your system didn't eject the media and the install process started again, you can simply reboot your system. During the boot process, eject the media and the system will boot from the hard disk using the freshly installed Solaris 10 image.
The License window appears. Please read the Solaris License Agreement, and if you agree, press [F2] to continue.
The Geographic Regions window appears. To add support for other regions, select the desired region; if not, press [F2] to continue.
The System Locale window appears. Press [F2] to continue.
The Selection of Additional Products window appears. Press [F2] to continue.
The Root File System selection window appears. Select ZFS and press [F2] to continue.
The Software Selection window appears. Use the default and press [F2] to continue.
The Disk Selection window appears. Use the default and press [F2] to continue.
The ZFS Configuration window appears. Use the default and press [F2] to continue.
The Remote Mounts window appears. Use the default and press [F2] to continue.
The Profile window appears. On this window, you can see a technical description of how Solaris will be installed on your system. Press [F2] to continue.
The Install Progress window appears. Wait for a few minutes while Solaris installs on your system. After the installation is completed, the system will reboot automatically and will start the Solaris OS. Remember that in some cases, you will have to eject the media manually.
Now you have successfully installed Solaris 10 5/09 on your system. Login using the root user and the password you assigned on step 19.

How to install Sun Java System Portal Server 7.1 Installation on Solaris 10

2009-09-12T08:15:00.000-07:00

This screencast provides the step-by-step procedure for installing Sun Java System Portal Server 7.1 on Solaris 10 SPARC machine

What's New in This Release

The following new features are available in Portal Server 7.2:

Desktop Design Tool
Delegated Administration
Enterprise Edition Installer
SharePoint Integrated Services
Advanced Encryption Standard (AES) Support for Secure Remote Access
CMS Portlet and CMS Framework
JSR 286 / Portlet Container 2.0 Support
WSRP 1.0 Reintegration
Portal Server 7.2 Samples Consolidation
Enhancements to Cluster Configuration
Google Gadgets Integration
Workflow API
JSF Portlet Bridge 1.2

to download it just click here

any questions or comment i really enjoy to read it.

how to install solaris 10

2009-09-07T06:57:00.000-07:00

this is a simple why to install the most powerful System in network administration
you need:
1.Machine with xp
2.Virtual box ( you can download it from here) which is very good and it's provide from Sun Micro Systems
3.Open Solaris Or Solaris (you can download it here)