Unable to Provide Read Access to WebLogic Server Logs using UMask Setting in Start Scripts (Doc ID 2204236.1)

Last updated on AUGUST 24, 2023

Applies to:

Oracle WebLogic Server - Version 12.2.1.1.0 to 12.2.1.2.0 [Release 12c]
Information in this document applies to any platform.

Default logs are set at 027, but desiring to give read access to WebLogic server_name.log

Updated the startNodeManager.sh and startWebLogic.sh with umask 022, but still the logs are generated with umask 027.

	To view full details, sign in with your My Oracle Support account.
	Don't have a My Oracle Support account? Click to get started!

In this Document

Symptoms

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.