Monday, October 30, 2017

Reset the AdminServer Password in WebLogic 11g and 12c

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:

Wednesday, October 11, 2017

sqlplus "/as sysdba" ORA-01017: invalid username/password; logon denied

sqlplus /as sysdba

ORA-01017: invalid username/password; logon denied
[root@ORACLE ~]# su - oracle
[oracle@ORACLE ~]$ orapwd file=$ORACLE_HOME/dbs/orapw$ORACLE_SID password=oracle entries=10 force=y
[oracle@ORACLE ~]$ . oraenv
ORACLE_SID = [oracle] ? orcl
[oracle@ORACLE ~]$ sqlplus / as sysdba
SQL*Plus: Release 11.2.0.4.0 Production on Tue Dec 1 15:59:37 2015
Copyright (c) 1982, 2013, Oracle.  All rights reserved.
ERROR:
ORA-01017: invalid username/password; logon denied
Enter user-name:
ERROR:
ORA-01017: invalid username/password; logon denied
Enter user-name: sys / as sysdba
Enter password: (oracle)
Connected to an idle instance.
USER is "SYS"
SQL>

Friday, October 6, 2017

OPATCH_JAVA_ERROR=OPatch Exception: Patch "22288381" has a minimum OPatch version "11.1.0.9.0" greater than the current OPatch version. Please go to My Oracle Support and get latest OPatch.

Weblogic Patch Issue 22288381

 OPATCH_JAVA_ERROR=OPatch Exception: Patch "22288381" has a minimum OPatch version "11.1.0.9.0" 

greater than the current OPatch version.

 Please go to My Oracle Support and get latest OPatch.


Applying patch i got a error .

 Patch "22288381" has a minimum OPatch version "11.1.0.9.0" greater than the current OPatch version



It seems OPatch failed because of Inventory problem. Validate the OUI inventory with the following commands:
  
   $ opatch lsinventory  -jre $ORACLE_HOME/jdk/jre

Exit the session and try 

From the session where you are running opatch apply,

1) Did you export the ORACLE_HOME & the PATH.

ORACLE_HOME by default points to the 10.1.2 Home.

As this Patch is on top of FMW webtier. The Oracle Home for webtier should be exported.

Example:
Assuming my FMW Webtier is /u01/apps/fs1/FMW_Home/webtier

export ORACLE_HOME=/u01/apps/fs1/FMW_Home/webtier
export PATH=$ORACLE_HOME:$ORACLE_HOME/OPatch:$PATH:.
opatch  lsinventory  -jre $ORACLE_HOME/jdk/jre

Try above and check !!!
 opatch apply 22288381 

It worked for me opatch applied successfully 

Wednesday, October 4, 2017

ADOP PATCHING

ADOP PATCHING 


ADOP PHASES 
--------------------

prepare       : Prepare the instance for online patching.
apply         : Apply patch(es) to the Patch Edition.  
finalize      : Ready the instance for cutover.  
abort         : Abort the patching cycle.  
cutover       : Promote the Patch Edition to Run Edition.   
cleanup       : Drop obsolete objects and seed data from Old Editions.
actualize_all : Actualize all objects in the Patch Edition.   
cleanup_full  : Cleanup and drop Old Editions.   
abandon       : yes|no - Abandon failed patches.


ADOP PATCH LOG DIRECTORY
-----------------------

<INSTALL BASE>/fs_ne/EBSapps/log/adop
ADOP PATCH PROCESS CYCLE STEPS
------------------------------
Download any required technology patches and unzip the contents.
 The patch contents may be unzipped into  $NE_BASE/EBSapps/patch.

1. Prepare the system for patching. 

   source <EBS_ROOT>/EBSapps.env run

   $ adop phase=prepare 

2. Apply technology patches to the Oracle Home under the Patch f/s 
using the information below. 

   source <EBS_ROOT>/EBSapps.env patch 

3. Apply any Oracle E-Business Suite patches planned for this patching cycle 

   $ adop phase=apply patches=<patch_list> 

4. After all patches have been successfully applied, complete the patching cycle. 

   $ adop phase=finalize 
   $ adop phase=cutover 

Note: Below steps can be done when applications are up and running 

5. source <EBS_ROOT>/EBSapps.env run 
   
   $ adop phase=cleanup

6. To complete the process and synchronize the technology level between patch 
and run f/s. 

   $ adop phase=fs_clone

Adop hotpatch steps (we cannot abort hotpatch and abondon cannot be done):
Hotpatch which can apply directly on run fs

$ adop phase=apply patches=<patch_list> hotpatch=yes

After hotpatch please run phase=cleanup and phase=fs_clone 
to sync the run fs with patch fs to prepare for next patching cycle