Re: Oracle Application Server Admin

  • From: "Pedro Espinoza" <raindoctor@xxxxxxxxx>
  • To: Joel.Patterson@xxxxxxxxxxx
  • Date: Wed, 23 Jan 2008 16:22:57 -0500

Well, when you bring it under odl, the files appear like:

-rw-r-----   1 oracle   dba      4999510 Jan 17 02:46 log19.xml
-rw-r-----   1 oracle   dba      4999510 Jan 19 12:53 log20.xml
-rw-r-----   1 oracle   dba      4999510 Jan 21 23:00 log21.xml
-rw-r-----   1 oracle   dba      3535396 Jan 23 16:05 log.xml


So, afaik, you can't dictate the name of the odl logs (they are just
that: current log being log.xml, and other old xml logs). But you can
tell oc4j which directory you wanna put log.xml.

Oracle supplied config file has soemthing like this:  <file
path="../log/server.log" />

I can replace it with <odl path="../log/" max-file-size="5000"
max-directory-size="20000" />
In that case,  I would see log.xml files in
$OMS_HOME/j2ee/OC4J_EM/log/OC4J_EM_default_island_1/

ls -ltr $OMS_HOME/j2ee/OC4J_EM/log/OC4J_EM_default_island_1/ *.log

-rw-rw----   1 oracle   dba      150491416 Dec  2 02:32 server.log
-rw-rw----   1 oracle   dba         4666 Dec 17 17:15 jms.log
-rw-rw----   1 oracle   dba         9332 Dec 17 17:15 rmi.log
-rw-rw----   1 oracle   dba        17693 Dec 17 17:17 global-application.log
-rw-rw----   1 oracle   dba      4373299 Jan 23 09:29 em-application.log

if I bring the all of the above under ODL, and if I keep the old path
= "../log/", it wreaks havoc, because all these applications may try
to write the same file: log.xml

That's why, I didn't use ../log/server/ for every thing
$pwd
/home/oracle/product/10.2.0/oms10g/j2ee/OC4J_EM/config

$ grep odl *

application.xml:                  <odl
path="../log/global-application/" max-file-size="1000"
max-directory-size="10000"/>
default-web-site.xml:   <odl-access-log
path="../log/default-web-access/" max-file-size="5000"
max-directory-size="20000"  />
http-web-site.xml:      <odl-access-log path="../log/http-web-access"
max-file-size="1000" max-directory-size="10000"/>
jms.xml:        <odl path="../log/jms/" max-file-size="1000"
max-directory-size="10000"/>
rmi.xml:                <odl path="../log/rmi/" max-file-size="1000"
max-directory-size="10000"/>
server.xml:             <odl path="../log/server/"
max-file-size="5000" max-directory-size="20000" />









On Jan 23, 2008 3:36 PM,  <Joel.Patterson@xxxxxxxxxxx> wrote:
> I suspect I wasn't clear in the other thread when I asked what directory
> convention you used.
>
> I see you used ../log/server which creates a directory etc like all the
> others, but I was also considering including orion-application.xml's in
> the consideration.  For instance the two original xml files I have
> presently go to ./  and ../../log as shown below.
>
> Since I haven't changed them yet, I wondered if I would send ODL logging
> to the same place also, and of course then it creates a directory
> analogous to all the others...
>
> Anyway, I'm presently on my oc4j directory... and I believe this might
> be related...  Have SR on this, but sometimes they don't go in the
> direction you envision.
>
> IsWebCascheWorking:
> <log>
> <file path="application.log" />
> </log>
> Goes to:
> home/application-deployments/IsWebCacheWorking/home_default_island_1/app
> lication.log
>
> em:
> <log>
> <file path="../../log/em-application.log" />
> </log>
> Goes to: OC4J_EM/log/OC4J_EM_default_island_1/em-application.log
>
>
> Joel Patterson
> Database Administrator
> joel.patterson@xxxxxxxxxxx
> x72546
> 904  727-2546
>
> -----Original Message-----
> From: oracle-l-bounce@xxxxxxxxxxxxx
> [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Pedro Espinoza
> Sent: Wednesday, January 23, 2008 2:56 PM
> To: Stephens, Chris
> Cc: oracle-l@xxxxxxxxxxxxx
> Subject: Re: Oracle Application Server Admin
>
>
> It is oracle diagnostic logging facility.
>
> http://download.oracle.com/docs/cd/B32110_01/web.1013/b28950/logadmin.ht
> m#i1027867
>
> Here is my notes:
>
>  Use oracle diagnostic logging to administer log sizes, number of log
> files; the following have been changed.
>
>  Edit the following files
>
>  $OMS_HOME/j2ee/home/config/server.xml
>  $OMS_HOME/j2ee/OC4J_EM/config/server.xml
>  $OMS_HOME/j2ee/OC4J_EM/config/default-web-access.xml
>  $OMS_HOME/j2ee/OC4J_EMPROV/config/server.xml
>  $OMS_HOME/j2ee/OC4J_EMPROV/config/default-web-access.xml
>
>  Replace <file path="../log/server.log" />
>  with  <odl path="../log/server/" max-file-size="5000"
> max-directory-size="20000" />
>
> Then bounce all instances, using opmnctl stopall; opmnctl startall.
>
>
>
> On Jan 23, 2008 2:50 PM, Stephens, Chris <chris_stephens@xxxxxxxxxxxx>
> wrote:
> > What is this ODL you speak of?
> >
> > -----Original Message-----
> > From: oracle-l-bounce@xxxxxxxxxxxxx
> > [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Pedro Espinoza
> > Sent: Wednesday, January 23, 2008 1:49 PM
> > To: Brandon.Allen@xxxxxxxxxxx
> > Cc: Joel.Patterson@xxxxxxxxxxx; oracle-l@xxxxxxxxxxxxx
> > Subject: Re: Oracle Application Server Admin
> >
> >
> > We use piped logs in our lamp stacks. In our grid setup, I have
> > changed all logging to make use of ODL, so that we can set the max
> > size for that log directory.
> >
> >
> > On Jan 23, 2008 2:15 PM, Allen, Brandon <Brandon.Allen@xxxxxxxxxxx>
> > wrote:
> > >
> > >
> > > Have you tried using piped logs?  I don't have any experience with
> it,
> > but
> > > they mentioned in it at my OAS Admin class and it looks like it
> could
> > be
> > > helpful:
> > >
> > >
> >
> http://download-west.oracle.com/docs/cd/B14099_19/web.1012/q20201/logs.h
> > tml#piped
> > >
> > > Regards,
> > > Brandon
> > >
> > >  ________________________________
> > >  From: Joel.Patterson@xxxxxxxxxxx
> [mailto:Joel.Patterson@xxxxxxxxxxx]
> > >
> > >
> > >
> > --
> > http://www.freelists.org/webpage/oracle-l
> >
> >
> >
> >
> > CONFIDENTIALITY NOTICE:
> >         This message is intended for the use of the individual or
> entity to which it is addressed and may contain information that is
> privileged,
> > confidential and exempt from disclosure under applicable law.  If the
> reader of this message is not the intended recipient or the employee or
> agent responsible for delivering this message to the intended recipient,
> you are hereby notified that any dissemination, distribution or copying
> of this communication is strictly prohibited.  If you have received this
> > communication in error, please notify us immediately by email reply.
> >
> --
> http://www.freelists.org/webpage/oracle-l
>
>
>
--
http://www.freelists.org/webpage/oracle-l


Other related posts: