1. How To Install Sun Explorer In Solaris 11 Commands Windows 10
2. How To Install Sun Explorer In Solaris 11 Commands Pdf
3. How To Install Sun Explorer In Solaris 11 Commands Command
4. How To Install Sun Explorer In Solaris 11 Commands Download

Minimal Memory: 256 MB
Minimal Swap Space: Twice the amount of the RAM

Here I am just sharing few tips to find the server serial number from Oracle Solaris. Download the STB (Sun explorer) bundle from oracle website and install it by just executing the script. After installing STB bundle,by default SNEEP utility also will be installed on the server. You can find the sneep utilities in the below mentioned location. To upgrade the non-IPS format of Explorer to a higher version, use the commands pkgrm SUNWexplo and pkgrm SUNWexplu to remove the currently installed Oracle Explorer packages before attempting to install a new version as superuser. Also refer to the upgrade instructions found on the SunSolve web site. Question: Is there a way to install one copy of Oracle Explorer and share it among all my. How to Quickly Install the Solaris 10 OS on x86 Systems. This How-to Guide instructs users unfamiliar with Solaris 10 Operating System installation on how to install the Solaris 10 OS on a Sun-supported x86 system (including the family of 32-bit x86 systems as well as 64-bit AMD64 and Intel 64 systems). Oracle Explorer must be installed in the global zone if you are installing it on the Solaris 10 Operating System (Solaris OS). If a version of Oracle Explorer is installed on the host, remove the SUNWexplo and SUNWexplu (if found any) packages before installing the new Oracle Explorer package.

To determine the amount of RAM memory installed on your system, enter the following command.

$ /usr/sbin/prtconf

To determine the amount of SWAP installed on your system, enter the following command and multiply the BLOCKS column by 512.

$ swap -l

Use the latest kernel patch from Sun Microsystems (http://sunsolve.sun.com)

Use the latest kernel patch from Sun Microsystems.

- Download the Patch from: http://sunsolve.sun.com
- Read the README File included in the Patch
- Usually the only thing you have to do is:

$ cd <patch cluster directory>
$ ./install_custer
$ cat /var/sadm/install_data/<luster name>_log
$ showrev -p

- Reboot the system

To determine your current operating system information:

$ uname -a

To determine which operating system patches are installed:

$ showrev -p

To determine which operating system packages are installed:

$ pkginfo -i [package_name]

To determine if your X-windows system is working properly on your local system, but you can redirect the X-windows output to another system.

$ xclock

To determine if you are using the correct system executables:

$ /usr/bin/which make
$ /usr/bin/which ar
$ /usr/bin/which ld
$ /usr/bin/which nm

Each of the four commands above should point to the /usr/ccs/bin directory. If not, add /usr/ccs/bin to the beginning of the PATH environment variable in the current shell.

The JRE shipped with Oracle9i is used by Oracle Java applications such as the Oracle Universal Installer is the only one supported. You should not modify this JRE, unless it is done through a patch provided by Oracle Support Services. The inventory can contain multiple versions of the JRE, each of which can be used by one or more products or releases. The Installer creates the oraInventory directory the first time it is run to keep an inventory of products that it installs on your system as well as other installation information. The location of oraInventory is defined in /var/opt/oracle/oraInst.loc. Products in an ORACLE_HOME access the JRE through a symbolic link in $ORACLE_HOME/JRE to the actual location of a JRE within the inventory. You should not modify the symbolic link.

Oracle9i includes native support for files greater than 2 GB. Check your shell to determine whether it will impose a limit.

To check current soft shell limits, enter the following command:

$ ulimit -Sa

To check maximum hard limits, enter the following command:

$ ulimit -Ha

The file (blocks) value should be multiplied by 512 to obtain the maximum file size imposed by the shell. A value of unlimited is the operating system default and is the maximum value of 1 TB.

Set to the sum of the PROCESSES parameter for each Oracle database, adding the largest one twice, then add an additional 10 for each database. For example, consider a system that has three Oracle instances with the PROCESSES parameter in their initSID.ora files set to the following values:

ORACLE_SID=TYP1, PROCESSES=100
ORACLE_SID=TYP2, PROCESSES=100
ORACLE_SID=TYP3, PROCESSES=200

The value of SEMMNS is calculated as follows:

SEMMNS = [(A=100) + (B=100)] + [(C=200) * 2] + [(# of instances=3) * 10] = 630

Setting parameters too high for the operating system can prevent the machine from booting up. Refer to Sun Microsystems Sun SPARC Solaris system administration documentation for parameter limits.

*
* Kernel Parameters on our SUN Enterprise with 640MB for Oracle 9
*
set shmsys:shminfo_shmmax=4294967295
set shmsys:shminfo_shmmin=1
set shmsys:shminfo_shmmni=100
set shmsys:shminfo_shmseg=10
set semsys:seminfo_semmni=100
set semsys:seminfo_semmsl=100
set semsys:seminfo_semmns=2500
set semsys:seminfo_semopm=100
set semsys:seminfo_semvmx=32767

$ groupadd -g 400 dba
$ groupdel dba

$ useradd -u 400 -c 'Oracle Owner' -d /export/home/oracle
-g 'dba' -m -s /bin/ksh oracle

# Setup ORACLE environment
ORACLE_HOME=/opt/oracle/product/9.2.0; export ORACLE_HOME
ORACLE_SID=TYP2; export ORACLE_SID
ORACLE_TERM=xterm; export ORACLE_TERM
TNS_ADMIN=/export/home/oracle/config/9.2.0; export TNS_ADMIN
NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1; export NLS_LANG
ORA_NLS33=$ORACLE_HOME/ocommon/nls/admin/data; export ORA_NLS33
LD_LIBRARY_PATH=$ORACLE_HOME/lib:/lib:/usr/lib:/usr/openwin/lib
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/dt/lib:/usr/ucblib:/usr/local/lib
export LD_LIBRARY_PATH
# Set up the search paths:
PATH=/bin:/usr/bin:/usr/sbin:/opt/bin:/usr/ccs/bin:/opt/local/GNU/bin
PATH=$PATH:/opt/local/bin:/opt/NSCPnav/bin:$ORACLE_HOME/bin
PATH=$PATH:/usr/local/samba/bin:/usr/ucb:.
export PATH
# CLASSPATH must include the following JRE location(s):
CLASSPATH=$ORACLE_HOME/JRE:$ORACLE_HOME/jlib:$ORACLE_HOME/rdbms/jlib
CLASSPATH=$CLASSPATH:$ORACLE_HOME/network/jlib

Usually the CD-ROM will be mounted automatically by the Solaris Volume Manager, if not, do it as follows as user root.

$ su root
$ mkdir /cdrom
$ mount -r -F hsfs /dev/.... /cdrom

exit or CTRL-D

If you downloaded database installation files from Oracle site (901solaris_disk1.cpio.gz, 901solaris_disk2.cpio.gz and 901solaris_disk3.cpio.gz) gunzip them somewhere and you'll get three .cpio files. The best way to download the huge files is to use the tool GetRight ( http://www.getright.com/ )

$ cd <somewhere>
$ mkdir Disk1 Disk2 Disk3
$ cd Disk1
$ gunzip 901solaris_disk1.cpio.gz
$ cat 901solaris_disk1.cpio | cpio -icd

This will extract all the files for Disk1, repeat steps for Disk2 and Disk3. Now you should have three directories (Disk1, Disk2 and Disk3) containing installation files.

Check oraInst.loc File

If you used Oracle before on your system, then you must edit the Oracle Inventory File, usually located in:
/var/opt/oracle/oraInst.loc

inventory_loc=/opt/oracle/product/oraInventory

Install Oracle 9i with Oracle Installer

$ cd /Disk1
$ DISPLAY=<Any X-Window Host>:0.0
$ export DISPLAY
$ ./runInstaller

Answer the questions in the Installer, we use the following install directories

Inventory Location: /opt/oracle/product/oraInventory
Oracle Universal Installer in: /opt/oracle/product/oui
Java Runtime Environment in: /opt/oracle/product/jre/1.1.8

Edit the Database Startup Script /var/opt/oracle/oratab

TYP2:/opt/oracle/product/9.2.0:Y

Edit and save the CREATE DATABASE File initTYP2.sql in $ORACLE_HOME/dbs, or create a symbolic-Link from $ORACLE_HOME/dbs to your Location.

$ cd $ORACLE_HOME/dbs
$ ln -s /export/home/oracle/config/9.2.0/initTYP2.ora initTYP2.ora
$ ls -l

initTYP2.ora -> /export/home/oracle/config/9.2.0/initTYP2.ora

First start the Instance, just to test your initTYP2.ora file for correct syntax and system resources.

$ cd /export/home/oracle/config/9.2.0/
$ sqlplus /nolog
SQL> connect / as sysdba
SQL> startup nomount
SQL> shutdown immediate

Now you can create the database

SQL> @initTYP2.sql
SQL> @shutdown immediate
SQL> startup

Check the Logfile: initTYP2.log

$ lsnrctl start LSNRTYP2

To start the Database automatically on Boot-Time, create or use our Startup Scripts dbora and lsnrora (included in ora_config_sol_920.tar.gz), which must be installed in /etc/init.d. Create symbolic Links from the Startup Directories.

lrwxrwxrwx 1 root root S99dbora -> ../init.d/dbora*
lrwxrwxrwx 1 root root S99lsnrora -> ../init.d/lsnrora*

You may want to install the following Options:

• Oracle JVM
• Orcale XML
• Oracle Spatial
• Oracle Ultra Search
• Oracle OLAP
• Oracle Data Mining
• Example Schemas

Run the following script install_options.sh to enable this options in the database. Before running this scripts adjust the initSID.ora paramaters as follows for the build process. After this, you can reset the paramters to smaller values.

parallel_automatic_tuning = false
shared_pool_size = 200000000
java_pool_size = 100000000

$ ./install_options.sh

These Scripts can be used as Templates. Please note, that some Parameters like ORACLE_HOME, ORACLE_SID and PATH must be adjusted on your own Environment. Besides this, you should check the initSID.ora Parameters for your Database (Size, Archivelog, ...)

Click here for the download (ora_config_sol_920.tar.gz)

How To Install Sun Explorer In Solaris 11 Commands Windows 10

If your system is a SunFire midframe server (38x0, 48x0, or 68x0 model), use this command to include data from the system console:
# /opt/SUNWexplo/bin/explorer -q -e -w default,scextended
If your system uses an alom (advanced lights out manager), some additional data can be collected. Systems that use that include:
Sun Fire V210,V240,V250,V245,V440,V440R,V445 Server Netra 240,440 (AC) Server
Use this command:
# /opt/SUNWexplo/bin/explorer -q -e -w default,alomextended
If your system uses T1 processors (system type starts with T, and uname -a command will say architecture is sun4v), use this command:
# /opt/SUNWexplo/bin/explorer -q -e -w default,Tx000

For any other model of Sun system, use this command:
# /opt/SUNWexplo/bin/explorer -q -e
The -q option suppresses printing of error messages during the run.
The -e option prevents explorer from automatically sending email.
The -w scextended option collects data from the system console (sc).
If you cannot run explorer for some reason, here are the most important things to collect:
/var/adm/messages or messages.# file for the time when the crash was taken. Be sure to include any messages that occurred just before panic.
/etc/system file
output of the showrev -p command, for a list of patches on system

How To Install Sun Explorer In Solaris 11 Commands Pdf

Detailed hardware configuration of the system. To determine which command to use, issue the command uname -m to find the system architecture type.
If it is sun4u, send the output of this command:
/usr/platform/sun4u/sbin/prtdiag -v
If it is sun4v, send the output of this command:
/usr/platform/sun4v/sbin/prtdiag -v
Output of this command:

How To Install Sun Explorer In Solaris 11 Commands Command

prtconf -vp
If your system is a SunFire midframe server (38x0, 48x0, or 68x0 model), include the output of these commands to collect data from the system console:

How To Install Sun Explorer In Solaris 11 Commands Download

showlogs -v
showlogs -d showboards -v showplatform -v showenvironment -v showsc -v