Hari ini gue mendapatkan banyak error di mesin yang menurut gue paling canggih, paling banyak CPU (20), paling banyak Memory (143GB), boros disk (30 TB), pokoknya
serba paling.

tapi di hari ini dia juga mengumpulkan daftar error paling banyak, berikut error list hari ini.

List Error Hari ini
“lckpwdf: Lockf deadlock detection Cannot obtain lock for /etc/.pwd.lock”
“WARNING: Failed to lock file: /var/opt/ignite/recovery/mnr_lockfile: Lockf deadlock detection (errno = 45)”
“Oracle instance running on a system with low open file descriptor limit. Tune your system to increase this limit to avoid severe performance degradation”
“ORA-00313: open failed for members of log group 2 of thread 1″
“ORA-00312: online log 2 thread 1: ‘/rdbms/oracle/users/oracle_sid/log_oracle-sid.ora’”
“ORA-27086: skgfglk: unable to lock file - already in use”
“HP-UX Error: 46: No locks available”

Machine Detail

• Model: 9000/800/SD32A
• Main Memory: 143277 MB
• Processors: 20
• OS mode: 64 bit
• OS: HP-UX B.11.11 U 9000/800

Solving with tuning the kernel parameter below here..

• nflocks = 200 + sum of database files for all instance
• maxfiles = 25% x current value
• maxfiles_lim = 25% x current value
• maxusers = No of connection oracle + 64
• maxuprc = maxusers * 5

Yesterday i get error on my database

Errors in file /rdbms/oracle/admin/udump/prod_ora_685.trc: ORA-01114: IO error writing block to file 10004 (block # 503489) ORA-27072: skgfdisp: I/O error HP-UX Error: 28: No space left on device Additional information: 503489

Karena semua query di tampung di temporary tablespace,
so i go to that mount point, and you now what, the mount point was full
# bdf

Filesystem kbytes used avail %used Mounted on
/dev/vg12/lvol5 112656384 112656384 0 100% /rdbms/oracle/temp

so i extend the new datafile on temp tablespace to that mount point, the extend proses was to quickly than before,

so i use

# lvdisplay /dev/vg12/lvol5 and
# fstyp -v /dev/vg12/lvol5
to check the size and compare with bdf/sam command.

Think fast, I used another mount point to moving and recreate the temp tablespace..detail click here.

And blast..
the error was gone, the mount point was suspect corrupt, Use umount, lvremove, lvcreate and than newfs, mount and yes new mount point was added again.