Couple things, the DocID you mention talks about the problem only in relation to generic weblogic. This is clear also because the file they talk about is: setDomainEnv.sh and not the OAS file setStartupEnv.sh. If the thought is this doc is the most relevant to the issue we have to modify the idea of the document to fit how OAS does things.

If you open setDomainEnv.sh the first comments at the top of the file says:

WARNING: This file is created by the Configuration Wizard.
Any changes to this script may be lost when adding extensions to this configuration.

So is the file being overwritten? And are you sure the parameter would even be used if its not?

Regardless, you should probably use setStartupEnv.sh where we know the java_options will be applied if we set the parameters in the correct lines.

I dont think there is any risk in applying the parameter -Doracle.jdbc.fanEnabled=falseso you should ensure it gets added to both the AdminServer and bi_server1.

In setStartupEnv.sh find this section and add it at the end of the java_options line inside the quotes:

Then do the same for the BISUITE-MAN-SRV section:

If we need to use setDomainEnv.sh the format for modifying the JAVA_OPTIONS is like this always:

JAVA_OPTIONS="${JAVA_OPTIONS} ${JAVA_PROPERTIES}"
export JAVA_OPTIONS

Note that it always keeps the previous value and adds to it. So the way you have it:

export JAVA_OPTIONS="-Doracle.jdbc.fanEnabled=false <other-options>"

make sure you add back in whatever previously needs to be there like this:

export JAVA_OPTIONS="${JAVA_OPTIONS} -Doracle.jdbc.fanEnabled=false <other-options>"