Sponsored Content
Special Forums UNIX Desktop Questions & Answers oracle performance on solaris 8 Post 30809 by niasdad on Monday 28th of October 2002 09:29:02 AM
Old 10-28-2002
Thanks for that excellent interpetation of what's going on. I will change the settings back in etc/system as orascle recommends. I believe that disk i/o is the problem right now. Another question to you is. Is there a way to tune a ufs file system?
 

2 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Oracle-performance tuning

Sorry, This is out of scope of this group.But I require the clarification pretty urgently. My Oracle database is parallely enabled. Still,in a particular table queries do not work "parallely" always. How is this? (9 Replies)
Discussion started by: kthri
9 Replies

2. AIX

Oracle performance optimum vs. SGA memory allocation

Dear all experts, I have a p750 Power 7 3.3GHz server with 4 processors and 48GB Memory. This is a DB server which is using Oracle 9i. I have been told that Oracle 9i can only allocate 10GB as SGA Max to get the oracle optimum performance. Anything more will result in overflow of memory and will... (1 Reply)
Discussion started by: kwliew999
1 Replies
UFS_DISK_CLOSE(3)					   BSD Library Functions Manual 					 UFS_DISK_CLOSE(3)

NAME
ufs_disk_close, ufs_disk_fillout, ufs_disk_fillout_blank, ufs_disk_write -- open and close userland UFS disks LIBRARY
UFS File System Access Library (libufs, -lufs) SYNOPSIS
#include <sys/param.h> #include <sys/mount.h> #include <ufs/ufs/ufsmount.h> #include <ufs/ufs/dinode.h> #include <ufs/ffs/fs.h> #include <libufs.h> int ufs_disk_close(struct uufsd *disk); int ufs_disk_fillout(struct uufsd *disk, const char *name); int ufs_disk_fillout_blank(struct uufsd *disk, const char *name); int ufs_disk_write(struct uufsd *disk); DESCRIPTION
The ufs_disk_close() function closes a disk and frees internal memory related to it. It does not free the disk structure. The ufs_disk_fillout() and ufs_disk_fillout_blank() functions open a disk specified by name and populate the structure pointed to by disk. The disk is opened read-only. The specified name may be either a mountpoint, a device name or a filesystem image. The ufs_disk_fillout() function assumes there is a valid superblock and will fail if not, whereas the ufs_disk_fillout_blank() function makes no assumptions of that sort. The ufs_disk_write() function attempts to re-open a disk as writable if it is not currently. ERRORS
The function ufs_disk_close() has no failure points. The function ufs_disk_fillout() may fail for any of the reasons ufs_disk_fillout_blank() might, as well as for any reason sbread(3) might. The ufs_disk_fillout_blank() may fail and set errno for any of the errors specified for the library functions open(2), strdup(3). Addition- ally, it may follow the libufs(3) error methodologies in situations where no device could be found to open. The function ufs_disk_write() may fail and set errno for any of the errors specified for the library functions open(2) and stat(2). Namely, it will fail if the disk in question may not be written to. SEE ALSO
open(2), getfsfile(3), libufs(3), sbread(3) HISTORY
These functions first appeared as part of libufs(3) in FreeBSD 5.0. AUTHORS
Juli Mallett <jmallett@FreeBSD.org> BSD
June 4, 2003 BSD
All times are GMT -4. The time now is 08:05 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy