why the oracle log was writed into pkg log?

[Rambo_1]

I found the / was 100% full.And the problem caused by the pkg.log . The oracle writed the log into the pkg.log interval a few minutes . So the pkg.log became bigger and bigger ,and finally chock up the / directory.
How to stop the behavior launched by oracle? can somebody tell me ?

Thanks & B.R
RAMBO

[Oviwan]

Hey

Check this thread:
http://forums.itrc.hp.com/service/forums/questionanswer.do?threadId=1030589

Regards

[Matti_Kurkela · Accepted solution]

It was probably the standard output of the oracle process.

ServiceGuard has this way of making you painfully aware of the fact that your packaged application is printing something to standard output and/or standard error.

The package control script is started with its standard output and standard error streams redirected to the package log file. Everything started from the control script inherits this property, unless you specify something else.

Redirect it into some suitable location in your oracle startup script (or package control script). If the real Oracle logfile does contain the same messages, you could redirect the standard output to /dev/null. Think carefully before redirecting standard error, though: usually that isn't nearly so verbose, and having the standard error output available might yield some vital clues at some later time when you're having problems.

You might also think about archiving the package logs periodically. Copying the log and then truncating the original might work.

If you're aiming for long uptimes and uninterrupted service, *anything* that grows without limit will need either a plan to handle the growth or a maintenance procedure to trim it back. If the growth is slow enough, the admins or the operators can do it manually if you have some sort of a system that sends a warning well before the disk is 100% full. But if the growth is fast or unpredictable, you may need to automate it.

MK