Error start managed-server Access denied ("oracle.security.jps.JpsPermission" "idstore.config")

Symptoms:

When tried to start the managed-server, after a few seconds get FAILED_START status.

The managed-server log (manage-server_name.out) presents the error such as:

oracle.security.jps.JpsException: oracle.security.jps.service.idstore.IdentityStoreException: java.security.AccessControlException: access denied ("oracle.security.jps.JpsPermission" "idstore.config")

Cause:

This is probably an error - no privilege - to access the jar libraries that provide access to the keystores.

Solution:

Possibly that the error message and the reason might varies according to the configuration, but you might check the privileges at weblogic.policy.

Add the following directives to the file - $WLS_HOME/wlserver/server/lib/weblogic.policy

//begin

grant codeBase "file:/u01/ofm/12.2.1-Domain/WLS/oracle_common/modules/oracle.jps/jps-api.jar" {

               permission java.security.AllPermission;

             };

grant codeBase "file:/u01/ofm/12.2.1-Domain/WLS/oracle_common/modules/oracle.jps_11.1.1/jps-api.jar" {

               permission java.security.AllPermission;

             };

grant codeBase "file:/u01/ofm/12.2.1-Domain/WLS/oracle_common/modules/oracle.jps/jps-internal.jar" {

               permission java.security.AllPermission;

             };

grant codeBase "file:/u01/ofm/12.2.1-Domain/WLS/oracle_common/modules/com.oracle.webservices.fmw.wsserver-impl.jar" {

               permission java.security.AllPermission;

             };

grant codeBase "file:/u01/ofm/12.2.1-Domain/WLS/oracle_common/modules/oracle.wsm.common/wsm-agent-core.jar" {

               permission java.security.AllPermission;

             };

grant codeBase "file:/u01/ofm/12.2.1-Domain/WLS/oracle_common/modules/oracle.wsm.common/wsm-pap.jar" {

               permission java.security.AllPermission;

             };

grant codeBase "file:/u01/ofm/12.2.1-Domain/WLS/oracle_common/modules/*" {

               permission java.security.AllPermission;

             };

//end

Restart the Weblogic server and then try to start the managed-server.

Hope this help.

Start Weblogic managed-server with error The object identified by: '31' could not be found

Symptoms:
Starting the Weblogic managed-server via startManagedWebLogic.sh script get the error:
Caused by: java.rmi.NoSuchObjectException: The object identified by: '31' could not be found.  Either it was has not been exported or it has been collected by the distributed garbage collector.

Cause:
This error has several reasons, but if you search on the web or Oracle Support, the first results will be port misconfigured somewhere


Solution:
Option 1: Check the Weblogic admin server listener address if its empty: <listen-address></listen-address>
To fix:
1. Go to $DOMAIN_HOME/config/config.xml file
2. Edit config.xml and set valid listen-address for admin server.
<listen-address></listen-address>
3. Restart the server.

Option 2: The script or command to start the managed-server is wrong, it should be the Admin Server port, instead the managed-server.
Example:
$ startManagedWebLogic.sh your_managed_server t3://yourWLS:7010 &

Your AdminServer is running on port 7001 and you tried to launch on the managed-server port (7010), that's why the error.


It might have other solutions for the same message error, so if you know, let us know.

Hope this help.

Oracle Cloud changes /etc/hosts after reboot

Symptoms: 
You have your Linux /etc/hosts configured correctly and after a reboot, the Cloud removes the line where your hostname was set. So the questions is how to permanently change the hostname of an Oracle Cloud Infrastructure (OCI) compute instance?

Cause: 
If any aplication that looks for the physical hostname to start, an example is Weblogic, the start process will hang due to the missing entry on /etc/hosts

Solution:

As given on the MOS Doc ID 2325469.1, by design, changes made in the /etc/hosts and resolve.conf files revert to their original values, after an instance restart.

To stop reverting this changes, edit the oci configuration file for hostnames as given below to update the needed value to 2.

    vi /etc/oci-hostname.conf

    PRESERVE_HOSTINFO=2

Reboot the instance and check.

ORA-01017: invalid username/password; logon denied with sqlnet.authentication_services

Symptoms: 
When tyring to login on the db instance using sqlplus / as sysdba, gets ORA-01017: invalid username/password; logon denied.

Cause: 
Operating system authentication may have been deliberately disabled.


Solution:
Look at the sqlnet.ora file located at $ORACLE_HOME/network/admin and check the value of parameter sqlnet.authentication_services.

If you get the operating system authentication disabled, this parameter is set with the value:
#SQLNET.AUTHENTICATION_SERVICES = (NONE)

If you want to allow connection using operating system authentication, remove or comment out the line:
#SQLNET.AUTHENTICATION_SERVICES = (NONE)