All The Administration Console permits the creation of Work Manager configurations that are not supported and do not function as intended.Incorrect Work Manager configurations may result in a number of exceptions being recorded in the server logs, most commonly exceptions while parsing deployment descriptors.Workaround Navigate to a configuration page for a different deployment, then navigate back to the original deployment again.All The Oracle OCI driver is no longer explicitly listed as a preconfigured driver type in the Administration Console.Workaround Use either of the following workarounds to bypass the new password restrictions.message on the Enterprise Manager (EM) console when the maximum number of file descriptors configured for the Administration Server is less than 65535.Remove the variable and variable-assignment clauses as needed to revert back to the descriptor settings you had before the you created the override via the Administration Console.All After a page flow completes in the Administration Console, it forwards to a different page, typically a table.
Correcting the Work Manager configurations to match the documented constraints resolves these issues.
Pressing the browser Back button at this point results in an attempt to load the last JSP file in the completed assistant.
At this point, all of the context for this assistant is discarded.
Workaround The Oracle OCI driver remains a supported driver for application data connectivity, consistent with prior releases of Oracle Web Logic Server.
However, users must now specify all required configuration properties manually, including the data base username.
Workaround Oracle recommends that you do not use the browser Back button to step back into an assistant once changes are cancelled or finished, and that you do not go back to a previous step in an assistant.