- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Oracle failed to start dure to no space for the lo...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-20-2003 03:16 AM
тАО11-20-2003 03:16 AM
Afer stopping the database and running the cold backup. the oracle failed to start.
Checked server and found the free space for mount point "/var" is very low (99% used).
After purging a couple log files. there were 80M aviable for "/var" and succeed to start the oracle database.
I purged
1.) /var/adm/syslog/syslog.log
2.) /var/adm/syslog/mail.log
3.) /var/spool/mqueue/syslog
4.) /var/mail/root
I wonder to which log file the UX will write when it start a process. and why the oracle failed to start dure to the low space on the "/var".
Thank you for your answer
Cazxd
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-20-2003 03:23 AM
тАО11-20-2003 03:23 AM
Re: Oracle failed to start dure to no space for the log to grow.
JL
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-20-2003 03:24 AM
тАО11-20-2003 03:24 AM
Re: Oracle failed to start dure to no space for the log to grow.
backup them to the /tmp first if you need to keep them or from an old ignite tape...
cleanup -p -c 2 ##to check what are avail to remove.. .then do
cleanup -c 2
IF you need more space do:
cleanup -c 1 to remove those superceeded only once...
This should give you much more space.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-20-2003 03:24 AM
тАО11-20-2003 03:24 AM
Re: Oracle failed to start dure to no space for the log to grow.
It's location is defined by the background_dump_dest parameter in your init.ora file. (or from "sqlplus / as sysdba" use "show parameter back")
Maybe your setup is doing stuff on /var, but it would be better not to.
-- Graham
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-20-2003 03:37 AM
тАО11-20-2003 03:37 AM
Re: Oracle failed to start dure to no space for the log to grow.
These files are critical for security and need to be there.
sam has a log trim facility under routine tasks that will trim one or all of the dozens of logs on your systems.
print spoolers store output in /var and you sholld make sure your print spoolers are periodically purged of old print jobs./
IF you still are tight on space you can extend /var with online JFS or if not, you can extend it in single user mode.
Let us know if you wish to extend the /var filesystem.
Oracle might be putting alert logs on /var. Check your init.ora files for where files are written.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-20-2003 03:43 AM
тАО11-20-2003 03:43 AM
Re: Oracle failed to start dure to no space for the log to grow.
IF your /var/tmp is not linked to /tmp, I would strongly recommend doing so. Oracle uses /var/tmp for some storage of data.
All mine are linked to /tmp and I increased my /tmp to 8gb on all boxes where I have databases. Also on my web tier, where users can max out a 2gb /tmp with one bad query.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-20-2003 03:46 AM
тАО11-20-2003 03:46 AM
Re: Oracle failed to start dure to no space for the log to grow.
deleting files, which are in use, wont do you any good. The space still keeps occupied. Check, that tmp does not point to /var.
greetings,
Michael
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-21-2003 04:36 AM
тАО11-21-2003 04:36 AM
Re: Oracle failed to start dure to no space for the log to grow.
John Garrott
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-21-2003 07:07 AM
тАО11-21-2003 07:07 AM
Re: Oracle failed to start dure to no space for the log to grow.
du -kx /var | sort -rn | head -20
You should see something like this:
454104 /var
427568 /var/adm
427288 /var/adm/sw
336792 /var/adm/sw/save
In this case, /var/adm/sw/save is the big area that needs trimming. Since thes are rollback patches (needed to remove an old patch), you can run the cleanup command to commit patches (no rollback). You can decide how far back to go, perhaps keeping the previous patch and maybe the one before that. See the man page for cleanup.
But notice that the /save directory is 336 megs! That's a lot so you concentrate on that directory. DO NOT remove files in the sw directory! Instead use cleanup and swmodify (to commit patches). If you remove files with rm, you may never be able to patch or load any software ever again.
Now if insteaad you see /var/tmp or /var/mail or /var/spool as being very large, then you have to deal with each directory based on it's usage. /var/mail is email and if it is large, somone (or something) has sent far too much mail to a user. Use this command:
ll /var/mail | sort -rnk5 | head
to find the largest mailboxes. Then look in the biggest mailbox to find why the file is so large. In short, find the directories that have the largest amount of data and fix them first. syslog.log and mail.log were probably fairly small. And make sure /var is big enough. 200 megs is way to small, and even 1000 megs may not be large enough. But you'll need a cron job customized for your environment to keep the temp files and other files under control.
Bill Hassell, sysadmin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-23-2003 09:46 PM
тАО11-23-2003 09:46 PM
Re: Oracle failed to start dure to no space for the log to grow.
are you still with us?
greetings,
Michael