Decrypt Oracle Weblogic password.

    Oracle WebLogic Server is a Java EE application server currently developed by Oracle Corporation. Oracle acquired WebLogic Server when it purchased BEA Systems in 2008. It is a chance that we may forget the WebLogic admin username and password. Following is the step-by-step guide to recovering the WebLogic admin user and password.

1. Set oms environment variables.

. oraenv <<< oms 

2. Changed directory to the GCDomain/bin

cd  /u01/app/oracle/gc_inst/user_projects/domains/GCDomain/bin/

ls -alh

3. The WebLogic settings are in the setDomainEnv.sh script file(setDomainEnv.cmd for Windows and setDomainEnv.sh for Linux). Execute the command below to set WebLogic environment variables.

./setDomainEnv.sh

4. The username and password are stored in encrypted format in the file boot.properties below. Search the file with the name. There may be multiple boot.properties files, but the required one is inside the security directory.

find /u01 -iname boot.properties

Choose the one with the security/boot.properties as in the screenshot below.

/u01/app/oracle/gc_inst/user_projects/domains/GCDomain/servers/EMGC_ADMINSERVER/security/boot.properties

5. WebLogic Scripting Tool (WLST) is a command-line scripting interface system administrators and operators use to monitor and manage WebLogic Server instances and domains. Execute wlst.sh inside the oracle_common/common/bin directory.

${ORACLE_HOME}/oracle_common/common/bin/wlst.sh

Type the following command to fetch the password.

Once you execute the wlst.sh the prompt will be like below. 

wls:/offline>

6. Execute the command one at a time. Make sure you replace the location of the boot.properties noted in the earlier step.

from weblogic.security.internal import BootProperties

BootProperties.load("<boot.properties location>", false)

prop = BootProperties.getBootProperties()

print "username: " + prop.getOneClient()

print "password: " + prop.getTwoClient()

The password was recovered successfully.

Read More

How to find Oracle Enterprise Manager startup time.

 

    Oracle Enterprise Manager(OEM) is an on-premises solution for a comprehensive monitoring and management solution for Oracle products such as Oracle Database and Engineered Systems. A lot of plugins, monitoring Templates, thresholds, and other features make OEM a great tool for monitoring.

    Few days ago, I was asked to find the Oracle Management Service(OMS) startup time. I googled a lot and search for a better way to present the startup time for the OEM process. Finally, after 2 hours of searching I found the solution to find the startup time of the OEM.

    Following is the step-by-step process to find the startup time of the OMS startup time.

1. Click on Setup >> Manage Cloud Control >> Management Servers.

2. Click on the Management Servers >> Monitoring >> Status History.

3. The time value in the Up Since provides the time the OMS server has been started.

4. At the top left side, there is a drop-down menu to check the Overall Availability Duration. We have the option to check availability during the last 24 hours, last 7 days, last 31 days, and custom.

Read More

How to change ASMSNMP user password in Oracle RAC Database.

        The ASMSNMP user is an Oracle ASM user with privileges to monitor Oracle ASM instances. The ASMSNMP user password is required to configure monitoring. Following are the steps by step guides to change asmsnmp password if you forgot.

        The ASMSNMP user password is required while creating an Oracle RAC database. If you forgot, then you can follow the below steps to reset asmsnmp user password.

        Log in as grid user or export to  ORACLE ASM-HOME and SID as ASM instance if configured both grid and oracle in one user.

Method 1: Use alter user command.

        The command requires the SYSASM privilege to run. A user logged in as SYSDBA cannot change their password using this command.

Connecting to the ASM instance and executing an alter user

. oraenv <<< +ASM1

$ sqlplus / as sysasm

SQL> select * from v$pwfile_users;

USERNAME                        SYSDB  SYSOP  SYSAS
------------------------------  -----  -----  -----
SYS                             TRUE   TRUE   TRUE
ASMSNMP                         TRUE   FALSE  FALSE

SQL> ALTER USER asmsnmp IDENTIFIED BY <new_password>;

SQL> exit

Method 2: Using orapwusr command. 

The orapwusr attempts to update passwords on all nodes in a cluster. 

Connect as grid user, and export ASM instance variables.

. oraenv <<< +ASM1
$ asmcmd
ASMCMD> lspwusr
Username  sysdba  sysoper  sysasm
     SYS    TRUE     TRUE    TRUE
 ASMSNMP    TRUE    FALSE   FALSE

ASMCMD> lspwusr
Username  sysdba  sysoper  sysasm
     SYS    TRUE     TRUE    TRUE
 ASMSNMP    TRUE    FALSE   FALSE

The username is case-sensitive while using orapwusr command, use ASMSNMP in upper case.
ASMCMD> orapwusr
usage: orapwusr { { { --add | --modify [--password] }[--privilege {sysasm|sysdba|sysoper} ] } | --delete } user
help:  help orapwusr
ASMCMD> orapwusr --modify --password ASMSNMP
Enter password: *******



-- 12c and above.

[oracle@host19c +ASM1]$ asmcmd 
ASMCMD> lspwusr 
       Username sysdba sysoper sysasm  
            SYS   TRUE    TRUE   TRUE  
CRSUSER__ASM_001   TRUE   FALSE   TRUE  
        ASMSNMP   TRUE   FALSE  FALSE  

ASMCMD> help orapwusr 
usage: orapwusr {--add | --modify | --delete | --grant {sysasm|sysdba|sysoper} | --revoke {sysasm|sysdba|sysoper} } <user> 
 ASMCMD> orapwusr --modify ASMSNMP 
Enter password: ******** 
ASMCMD> 

Read More

Install Oracle Database using docker in Mac M1

 

   

    The new Mac with Apple Silicon is ARM 64-bit architecture and does not directly support x86_64 or AMD 64-bit applications. There are multiple ways to make an x86_64 bit application run with the arm processor. There is no easy and straightforward way to install Oracle Database using docker in mac with M1/M2 chip. Following is the step-by-step guide to install the Oracle database using docker in a mac M1 processor.

Install Homebrew and other required packages.

    Homebrew is a package manager for macOS. It is one of the first tools that need to install on your mac to install docker for x86_64 containers. It is used to install (and remove) software programs for the terminal, or CLI. Almost every useful open-source package is available through Homebrew. Installing Homebrew is pretty easy. Execute the command below in the terminal window to install Homebrew.

/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

    Set environment variables to include brew binary in the PATH environment variable. Execute the following command in the terminal

export PATH=/opt/homebrew/bin:$PATH

    Uninstalled any docker package installed by App Store or using dmg files. It will avoid any crossover with the software. Install the following brew packages. Here, Docker is an open platform for developing, shipping, and running applications using Docker containers. Similarly, Docker Compose is a tool that was developed to help define and share multi-container applications. Colima is a container runtime on MacOS (and Linux) with minimal setup. Colima is almost a drop-in replacement for Docker Desktop. Colima directly supports the ARM chip and it can start up the VM that will run the x86_64 containers. Qemu is an emulator for x86 and arm chips.

$ brew install colima
$ brew reinstall qemu
$ brew install docker
$ brew install docker-compose

    Start a VM to run an x86_64 docker container.  Execute command in the terminal. The command below starts a VM that uses 4 CPUs, and 12G of memory, and supports the x86_64 architecture. This should allow me to download and run an x86_64 container.

colima start -c 4 -m 12 -a x86_64

Validate the status of the VM that was started.

colima list

Once docker everything is ready, export a running docker x86_64 container with the Oracle database running. I tried to install the Oracle database using Oracle's official docker repo but encountered some java related issues. The second time, I installed OEL 7.9 and tried to install Oracle database software and Oracle database but it failed again with the Java issue. I will troubleshoot the issue later but for this post, I am saving my running Intel-based x86_64 docker container image to a file and loading a file to the docker with an M1 chip.

    Due to a license issue, I cannot share my Oracle Database docker Image file. I am assuming ora19c.gz is a file where I have loaded Oracle docker Image.

Syntax to load the docker image to a file.

docker save oracle/database:19.3.0-ee | gzip  > ora19c.gz

    Once the docker image is saved to the file with the name ora19c.gz. Ship the file to the Mac book Maching with M1 chip. Load the image file copy with the command below.

docker load < ora19c.gz

Create and run a new container from an image oracle.

docker run -d -t -i --privileged --name=oracle19c --hostname=oracle19c -p 1522:1521 -v /Users/raj:/mnt ora19c oracle/database:19.3.0-ee

Verify docker container is running.

docker ps 

Execute /bin/bash command in a running docker container.

docker exec -it -u oracle oracle19c /bin/bash

Starting Oracle Database container later.

Verify if colima is started, if not start with the command below.

/opt/homebrew/bin/colima list
/opt/homebrew/bin/colima start

Start Oracle Database container.

docker start oracle19c

Execute /bin/bash in the running oracle database container.

docker exec -it -u oracle oracle19c /bin/bash

Read More