Solaris setup

BigAdmin has patch info and howtos

Get software from www.sunfreeware.com

Solaris Admin and HOWTOs

Install:
  wget
  gnu tar
  lsof -> or use pfiles <pid>
  top -> or use prstat [-a]
  vim

For gnu tar:
gunzip libgcc package: gzip -d ...
pkgadd libgcc: pkgadd -d ...

Check install:
pkginfo | grep tar
Check details:
pkginfo -l SMCtar
to remove: pkgrm SMCtar

create link in /usr/local/bin for gtar
cd /usr/local/bin
ln -s /usr/sfw/bin/gtar gtar

Check patch level:
ls -l /var/sadm/patch
OR
showrev -p

uname -X (release, number of CPUs)
/usr/sbin/psrinfo [-v] (cpu status, type, and speed)
listusers (lists all users)
/etc/passwd file format
groupadd -g 400 develop (add group 'develop' with GID 400)
usermod -G develop existing_user (add existing_user to group develop)
grpck (check consistency of group file)
pwck (check consistency of passwd file)

useradd -d /export/home/username -m -s /usr/bin/bash -c "some comment" username

Recursive, change encountered Links, Prevent following links
chown -R -L -P <owner>:<group> <dir | file>
using * for chown for dir or file on Solaris 10 did not work, had to go up a dir and specify dir

Gathering system info

Run levels:

Run level
2 is multi-user mode one step beyond single-user
3 is normal user mode

Create links to start stop scripts:
/etc/rc#.d/S##<name> start process
/etc/rc#.d/K##<name> stops process

r#.d is run level
## provides script ordering

/etc/profile for default profile

common paths to utils
/usr/bin
/usr/sbin
/usr/local/bin
/usr/sfw/bin


Solaris tar is broken, it gets hung with the tar file growing forever until you kill tar
tar with exclude
create exclude file listing all the directories and files you don't want included
tar -cvpfX newTarFile.tar excludeFile whatToTar

gnu tar works
gtar -cvpf newTarFile.tar -X excludeFile dirToTar > tarFile.log

excludeFile contains list of dirs and/or files to exclude

Routing tables:

netstat -r

To see IP addresses:

netstat -rn

To find required patches:
Go to sunsolve.sun.com
Click on Patch Cluster & Patch Bundle Downloads
Under 'J2SE Patch Clusters'
Expand: J2SE Patch Clusters
Click on README and compare with output of showrev -p
You will need a support contract to download these.

Comments

Post a Comment

Popular posts from this blog

Sites, Newsletters, and Blogs

BLOGS Java.net Weblogs Martin Fowler's blog Paul Graham Ruminations of a Programmer Form Follows Function Newsletters Core Java Tech Tips Enterprise Java Tech Tips JavaSpecialists.EU TheServerSide.com Sites Java.net Today Hot Java Sites CSS Zen Garden Evernote Hacker News Pragmatic Programmer
Read more

Oracle JDBC ReadTimeout QueryTimeout

If a query exceeds the oracle.jdbc.ReadTimeout without receiving any data, an exception is thrown and the connection is terminated by the Oracle driver on the client. Unfortunately the session will still be queued on the database and continue to wait for locks, hold any current locks, and complete any DML/PL*SQL procedures that are pending on the server-side of the orphaned connection. If an application, on a another connection, due to ReadTimeout exception, retries DML/PL*SQL  which requires locks, those queries will queue behind the initial DML/PL*SQL. This will increase the workload exacerbating the situation. On applications with retries, this can be observed by querying the v$session table  or gv$session on RAC and noting new sessions started periodically based on the ReadTimeout interval. The sessions may often have the same SQL_ID and/or SQL_HASH_VALUE. If stmt.setQueryTimeout(Seconds) is issued and the statement exceeds the timeout, it will atte...
Read more

Locks held on Oracle for hours after sessions abnormally terminated by node failure

If a session holds db locks and is abnormally terminated (no fin/ack), the locks will persist until the db session is closed, typically around 2 hours and 12 minutes with default network tcp_keepalive settings. Abnormally terminated does not include CTRL C or kill -9. The ojdbc6 driver apparently has a shutdown hook thread that closes the connections in graceful shutdowns. The OS apparently closes the connections when processes are killed. Abnormally terminated might include power failure, firewall failures, Out Of Memory, OS/kernel crash, network connection failure, JBoss or other server node failure, etc. This was easily reproduced by creating a  process that connected to the db and updated a record but did not commit. While the first process was waiting, a second process with a contending update was started which blocked on the first update. The first clients network cable was then disconnected. The second clients transaction waited for approximately 2 hours until the databa...
Read more