Database Administrator

Reset the AdminServer Password in WebLogic 11g and 12c

If you forget the AdminServer password for your WebLogic 11g domain, you can reset it from the command line using the following process.

Set up the following environment variables. They are not necessary for the process itself, but will help you navigate. In this case my domain is called "ClassicDomain". Remember to change the value to match your domain.
```
export MW_HOME=/u01/app/oracle/middleware
export DOMAIN_HOME=$MW_HOME/user_projects/domains/ClassicDomain
```
Shut down the WebLogic domain.
```
$ $DOMAIN_HOME/bin/stopWebLogic.sh
```

Rename the data folder.

$ mv $DOMAIN_HOME/servers/AdminServer/data $DOMAIN_HOME/servers/AdminServer/data-old

Set the environment variables.
```
$ . $DOMAIN_HOME/bin/setDomainEnv.sh
```
Reset the password using the following command. Remember to substitute the appropriate username and password.
```
$ cd $DOMAIN_HOME/security
$ java weblogic.security.utils.AdminAccount <username> <password> .
```
Update the "$DOMAIN_HOME/servers/AdminServer/security/boot.properties" file with the new username and password. The file format is shown below.
```
username=<username>
password=<password>
```
Start the WebLogic domain.
```
$ $DOMAIN_HOME/bin/startWebLogic.sh
```

For more information see:

How to Change the WebLogic Server Administrator Password [ID 1082299.1]

Determining the amount of memory installed from the ESXi command line (2005821)

Purpose

This article provides a command to determine the amount of memory installed on an ESXi host.

Resolution

To determine the amount of memory installed on an ESXi host, run this command on the host ESXi host through an SSH session:

cim-diagnostic.sh > mem.out

Where mem.out is the file in which the command output is stored.

After you have determined the amount of memory installed on the host, run this command to determine how much memory each slot of physical RAM is reporting.

less -i mem.out
To jump to the memory specific output, run this command from within the less session:

/CIM_Mem
The output appears similar to:

Dumping instances of CIM_Memory
Dumping instances of CIM_PhysicalMemory

OMC_PhysicalMemory.CreationClassName="OMC_PhysicalMemory",Tag="32.0"
Tag = 32.0
CreationClassName = OMC_PhysicalMemory
MaxMemorySpeed = (NULL)
IsSpeedInMhz = false
InterleavePosition = 255
PositionInRow = 255
TotalWidth = 32
Speed = (NULL)
SerialNumber = (NULL)
RemovalConditions = (NULL)
PartNumber = (NULL)
OperationalStatus = { 0, }
MemoryType = 2
Manufacturer = (NULL)
HealthState = (NULL)
FormFactor = 8
ElementName = RAM slot #0
Description = RAM slot #0
DataWidth = 32
Caption = RAM slot #0
Capacity = 2147483648
Note: The capacity of the RAM is in bytes.

Alternate:

#cim-diagnostic.sh | grep -i capacity will return capacity.

Basic Enterprise Manager Troubleshooting

The web-based Enterprise Manager tool was introduced in Oracle 10g and has significant functionality improvements over previous versions. Even so, it seems there is not a day goes by without someone asking how to solve an Enterprise Manager configuration issue, so this article explains the first things you should look at. It's not meant to be an all encompassing guide. Just a first shot.
Make sure the "/etc/hosts" file contains at least the loopback address and preferably the machine definition also.

127.0.0.1       localhost.localdomain  localhost
192.168.0.181   myserver.localdomain   myserver

If you are using 11g, make sure the ORACLE_HOSTNAME and ORACLE_UNQNAME environment variables are set correctly.

ORACLE_HOSTNAME=myserver.localdomain; export ORACLE_HOSTNAME
ORACLE_UNQNAME=DB11G; export ORACLE_UNQNAME

Check the listener is running correctly.

lsnrctl status

Manual Upgrades

Backup the database before starting the upgrade process. In the event of a failure, you will need this backup to allow you to recreate your starting point.
To run the new Pre-Upgrade Information Tool, copy the "preupgrd.sql" and "utluppkg.sql" scripts from the 12c home to a location accessible by the database that needs upgrading. In this example I used a directory under "/tmp".

$ mkdir -p /tmp/upgrade
$ cp /u01/app/oracle/product/12.1.0.1/db_1/rdbms/admin/preupgrd.sql /tmp/upgrade
$ cp /u01/app/oracle/product/12.1.0.1/db_1/rdbms/admin/utluppkg.sql /tmp/upgrade

Make sure the ORACLE_BASE is set and run the "preupgrd.sql" script from SQL*Plus.

$ export ORACLE_SID=orcl
$ ORAENV_ASK=NO
$ . oraenv
$ ORAENV_ASK=YES
$ cd /tmp/upgrade
$ sqlplus / as sysdba

SQL> @preupgrd.sql
Loading Pre-Upgrade Package...
Executing Pre-Upgrade Checks...
Pre-Upgrade Checks Complete.
      ************************************************************

Supported Upgrade Paths

Direct upgrades to 12c are possible from existing databases with versions 10.2.0.5+, 11.1.0.7+, or release 11.2.0.2+. Upgrades from other versions are supported only via intermediate upgrades to a supported upgrade version.
When you are using the DBUA or performing a manual upgrade, you will need both versions of the database present to complete the operation. Typically, you will be installing Oracle 12c into a new ORACLE_HOME on the existing server.

Database Upgrade Assistant (DBUA)

The preferred upgrade method is to use the Database Upgrade Assistant (DBUA), a GUI tool that performs all necessary prerequisite checks and operations before upgrading the specified instances. The DBUA can be started directly from the Oracle Universal Installer (OUI) during installation, or separately after the software installation is complete.
Make sure the database is started and run the database upgrade assistant.

$ export ORACLE_HOME=/u01/app/oracle/product/12.1.0.1/db_1
$ export PATH=$ORACLE_HOME/bin:$PATH
$ dbua

Select the "Upgrade Oracle Database" option, then click the "Next" button.
Select Operation