Path: news.easynews.com!newsfeed1.easynews.com!easynews.com!easynews!c03.atl99!news.webusenet.com!telocity-west!DIRECTV!sn-xit-03!sn-xit-01!sn-post-02!sn-post-01!supernews.com!corp.supernews.com!not-for-mail From: "Peter van Rijn" Newsgroups: comp.databases.oracle.server Subject: Re: rotating listener.log Date: Thu, 12 Dec 2002 11:33:34 +0100 Organization: Posted via Supernews, http://www.supernews.com Message-ID: References: <3DF729E9.87FD56A7@artelecom.ru> X-Newsreader: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Complaints-To: abuse@supernews.com Lines: 21 Xref: newsfeed1.easynews.com comp.databases.oracle.server:169497 X-Received-Date: Thu, 12 Dec 2002 03:33:20 MST (news.easynews.com) > > Oracle has problems, if the logfile is deleted or renamed. No new file > will be created before you restart the listener or instance. With the > echo the content of the file will be deleted, not the file himself. > If you rename the file the listener will continue to write to the renamed file! After renaming the file it still has the same inode number, and that's why the file is still being written to. If you delete the file the listener still uses its file handle to the inode, but since the file has gone you will not be able to see it. If you do something like "echo >" or "cat /dev/null >" or similar actions the contents of the file are altered (i.e. made empty), but since it still has the same inode number the listener can still visibly write to this file. hth, Peter