User reported that large log files were being created on the web server. On investigation we found that web services were down as that the datasource was unable to connect to the database and gave errors in the logs suggesting a password had expired. This caused the log files to grow quite large very quickly and the SOA_INRA server to be shown as down in the Weblogic console.
The datasource was unable to connect to the database as the oracle user accounts used by the weblogic server for its repository had expired. When implementing a password expiration policy for everyday users, the following user accounts should be given separate user profiles which do not expire as the passwords must remain the same. I.E Create a separate user profile with password_life_time set to unlimited and grant this profile to the following users so their passwords do not expire:TMAWS<soa_schema_name>_MDS (I.E. where <soa_schema_name> is the schema prefix defined on deployment for the components, such as LIVE_MDS)<soa_schema_name>_ORASDPM<soa_schema_name>_SOAINFRA
In order to stop your log files growing to an excessively large size you can also implement a log file rotation policy. To do this please see:
Product TechNotes and FAQs
Bentley Technical Support KnowledgeBase
Bentley LEARN Server
Bentley's Technical Support Group requests that you please confine any comments you have on this Wiki entry to this "Comments or Corrections?" section. THANK YOU!