weird user_dump_dest issue

I've got kind of a weird issue with a 9.2.0.5 (64-bit) database on
HP-UX.  Basically, it seems to be forgetting the "user_dump_dest"
setting for some reason... it's putting trace files under 
$ORACLE_HOME/rdbms/log even though the parameter is properly set, and
"show parameter user_dump_dest" indicates the expected location.

I can reset it dynamically with no apparent trouble, but for some
reason it seems to revert back after writing the first tracefile (see
below).  The directory permissions seem to be OK (mode 750, owned by
oracle:dba), and the alert log doesn't show anything out of the
ordinary.

Anyone else run into this sort of behaviour?  Any suggestions on what
to look at?


$ pwd
/oracle/u01/admin/P1CTM1/udump

$ sqlplus "/ as sysdba"

SQL*Plus: Release 9.2.0.5.0 - Production on Mon Apr 11 11:40:15 2005
Copyright (c) 1982, 2002, Oracle Corporation.  All rights reserved.

Connected to:
Oracle9i Enterprise Edition Release 9.2.0.5.0 - 64bit Production
With the Partitioning option
JServer Release 9.2.0.5.0 - Production

SQL> show parameter user_dump_dest

NAME           TYPE   VALUE
-------------- ------ ------------------------------
user_dump_dest string /oracle/u01/admin/P1CTM1/udump

SQL> alter database backup controlfile to trace;

Database altered.

SQL> !ls -l
total 0

SQL> alter system set user_dump_dest='/oracle/u01/admin/P1CTM1/udump'
scope=both;

System altered.

SQL> alter database backup controlfile to trace;

Database altered.

SQL> !ls -l
total 15
-rw-r-----   1 oracle   dba         12272 Apr 11 11:41 p1ctm1_ora_12535.trc

SQL> /

Database altered.

SQL> !ls -l
total 15
-rw-r-----   1 oracle   dba         12272 Apr 11 11:41 p1ctm1_ora_12535.trc

SQL> exit
Disconnected from Oracle9i Enterprise Edition Release 9.2.0.5.0 -
64bit Production
With the Partitioning option
JServer Release 9.2.0.5.0 - Production

-- 
"I'm too sexy for my code." - Awk Sed Fred.
--
http://www.freelists.org/webpage/oracle-l

Other related posts: