Dear IFS community, 

did you came accross trace files summing up large amounts of gigabytes during installations?
Of course I’m available of a workaround increasing the storage :) 

The operational monitoring recognized the fully running trace directory and expanded the file system several times yesterday - in total, the file system was expanded from an initial 21 GB to currently 115 GB (!!).

 
Is there any chance we can disable / limit / define trace creation path on our own for remote customers?

Example error message looks like:
11:46:19 2024:  CHPHPRD(3):Non critical error ORA-48181 caught while writing to trace metadata file (.trm)

11:46:19 2024:  Trace file name: "/oracle/CHPH4/oratrace/diag/rdbms/chph4/CHPH4/trace/CHPH4_ora_66060760.trc"

11:46:19 2024:  Error message: IBM AIX RISC System/6000 Error: 28: No space left on device

11:46:19 2024:  Error message: 

19 11:46:19 2024:  Writing to the above trace file is disabled for now…


Interestingly it is not disabled and continues:

11:46:41 2024:  CHPHPRD(3):Non critical error ORA-48113 caught while writing to trace file "/oracle/CHPH4/oratrace/diag/rdbms/chph4/CHPH4/trace/CHPH4_ora_540.trc"

11:46:41 2024:  Error message: 

11:46:41 2024:  Writing to the above trace file is disabled for now...

….