I realized that my /oracle/rdbms/log/ directory contains 30.000 *.trc files, produced by 4 instances running in the last 3 months. all these files seem to contain something like this:
---------------------------------------- Oracle9i Enterprise Edition Release 9.2.0.2.0 - 64bit Production With the Partitioning, OLAP and Oracle Data Mining options JServer Release 9.2.0.2.0 - Production ORACLE_HOME = /oracle System name: HP-UX Node name: dbsermm Release: B.11.22 Version: U Machine: ia64 Instance name: oa Redo thread mounted by this instance: 0 <none> Oracle process number: 0 7092
All these instances are working really well. What kind of trouble are these trace files trying to tell me?
Oracle 9.2.0.2, HP-UX 11.22, Itanium.
Thanks for yor help!
Claudio
Note: If you are the author of this question and wish to assign points to any of the answers, please login first.For more information on assigning points ,click
here
If you are using RAW disk partitions for you Database, The following from Administrator Reference Guide from Oracle ----------
The asynchronous I/O pseudo-driver on HP allows the Oracle server to perform I/O to raw disk partitions using an asynchronous method, resulting in less I/O overhead and higher throughput. You can use the asynchronous I/O pseudo-driver on both HP-UX 9000 servers and workstations.
MLOCK Privilege To allow Oracle9i to execute asynchronous I/O operations, the group that the Oracle software owner belongs to (dba) must have the MLOCK privilege. To give the dba group the MLOCK privilege:
As the root user, enter the following command:
# setprivgrp dba MLOCK
To retain the MLOCK privilege after rebooting, create the /etc/privgroup file, if it does not exist on your system, and add the following line to it:
dba MLOCK
-------------------------------------------------------------------------------- Note: If the Oracle software owner does not have the MLOCK privilege, Oracle9i on HP-UX generates trace files that include the following error:
hi, * According to metalink, to fix the problem, you'll need to grant oracle owner privileges to lock memory pages. This is done with the command: * # setprivgrp dba MLOCK * After this, no more trace files are generated. * Hope this helps! regards Yogeeraj
Printable version
