Decrypting Weblogic Password

Sometimes we may forget the password we set for weblogic. At such times this method will be very much helpful.  

Below is the step by step process to decrypt the password for weblogic.

1. Take a backup of the boot.properties file
   
   
   
2. Note the value of encrypted password
   
   
   
3. Now invoke the WebLogic scripting tool                                                                                            sh wlst.sh
   
   
   
4. Pass the values for Domain, service, encryption and password                                                  wls:/offline> domain = "<Domain Value>"

   wls:/offline> service = weblogic.security.internal.SerializedSystemIni.getEncryptionService(domain)

   wls:/offline> encryption = weblogic.security.internal.encryption.ClearOrEncryptedService(service)

   wls:/offline> print encryption.decrypt("<Encrypted Password>")

   
   
   
5. Your password will be decrypted
6. Now you can use the decrypted password to start the Admin server
   
   
   

****************************நன்றி****************************

Oracle error -29548: ORA-29548: Java system class reported: release of Java system classes in the database does not match that of the oracle executable - USER ( APPS ) has been detected in FND_WEB_SEC.GET_OP_VALUE.

After completed cloning of EBS-12.2.4, working on the post clone activities. When tried to change the APPS and SYSADMIN passwords using FNDCPASS utility faced the below issue.

This is the first time I'm facing this issue. I can't understand why this issue has occurred as I didn't face any issues during cloning. Below is the step by step process to overcome this issue.

Create two scripts 'rmcorejvm.sql' & 'corejvminst.sql' and execute them on the DB Tier.

Content of rmcorejvm.sql

connect / as sysdba

set echo on

set serveroutput on

select * from v$instance;

select owner, status, count(*) from all_objects

where object_type like '%JAVA%' group by owner, status;

execute rmjvm.run(false);

shutdown immediate

set echo off

spool off

exit

Content of corejvminst.sql

set serveroutput on

set echo on

startup mount

alter system set "_system_trig_enabled" = false scope=memory;

alter database open;

select owner, status, count(*) from all_objects

where object_type like '%JAVA%' group by owner, status;

create or replace java system

/

shutdown immediate

set echo off

spool off

exit

Now run the scripts in the below mentioned order at DB Tier via sqlplus as sysdba user.

Now mount the database, change the parameter _system_trig_enabled to false and take a bounce on the DB.

Once the DB is started, check the below value and proceed to change the apps/sysadmin passowrds.

This time I could change the passwords without any issues.

****************************நன்றி****************************

Enabling EM Express Console in OCI Environment

By default EM Express Console is not enabled in 18.1.0.0, 12.2.0.1 and 12.1.0.2 databases.  Below is the step by step process to enable EM Express Console in Oracle Database.

In my environment, I had enabled the EM Console at PDB level.

Before enabling the console listener status would be

To enable the console and set its port

Now confirm the listener is listening on the port '5500'.

Now to open the port '5500' on DB system, follow the below steps

Once the DB port is opened, update your security list in OCI console. To do this on an existing security list, follow the below steps.

1. Open the navigation menu. Under Oracle Database, click (Bare Metal / VM / Exadata) ---> as per your environment

2. Choose your Compartment.

   A list of DB systems is displayed.

3. Locate the DB system in the list.
4. Note the DB system's Subnet name and click its Virtual Cloud Network.
5. Locate the subnet in the list, and then click its security list under Security Lists.

6. Click Edit All Rules and add an ingress rule with source type = CIDR, source CIDR=<source CIDR>, protocol=TCP, and port=<port number or port range>.

   The source CIDR should be the CIDR block that includes the ports you open for the client connection.

Known Issue:

You might get a "Secure Connection Failed" error message when tried to connect to the EM Express Console from your 1 node DB system because the correct permissions were not applied automatically. To overcome this issue follow the below steps.

Now copy the location of the wallet directory, navigate there and follow the below steps.

Ref: Monitoring a Database (oracle.com)

        Known Issues (oracle.com)

****************************நன்றி****************************