Database Administration (MOSC)

MOSC Banner

Problem with lsof of Oracle files on AWS

edited Dec 21, 2019 4:00AM in Database Administration (MOSC) 3 commentsAnswered

We are running Oracle 12.2 on Amazon AWS (RHEL) and in the past we've used the "lsof" command to find open oracle files, specifically log files.   Part of our log rotation scripts uses lsof to exclude everything that is open in the log directory, and process files and the alert.log usually show up as open.  However, this does not seem to the the case anymore, and the only thing that has changed is that we're running on AWS.    Anyone seen this behavior?   Is there something about 12.2 that leaves logfiles closed?   I can't imagine Oracle repeatedly opening the alert.log to

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center