ORA-01017: invalid username/password logon denied

When we are trying to connect database as

$sqlplus / as sysdba

Error:

ORA-01017: invalid username/password; logon denied

SP2-0157: unable to CONNECT to ORACLE after 3 attempts, exiting SQL*Plus

Solution:

We need to change the password file

Connect to oracle user and change directory to

$cd $ORACLE_HOME/dbs

$orapwd file=$ORACLE_HOME/dbs/oraSID password=xyz force=y

Here you have to enter your password instead of xyz and your DB name instead of SID.

Posted by: Anil Bandi

Oracle Apps DBA

How to Increase the Number of Concurrent Request Processes

Login to the application

Switch to System Administrator responsibility

Go to Concurrent Manager Define

Query “Standard Manager”  and click on workshifts

Increase the number (as per your requirement) in the Processes column

Posted by: Anil Bandi

Oracle Apps DBA

Encountered unrecognized patch ID

“Encountered unrecognized patch ID” Failures when trying to apply WLS Patch using bsu Smart Update

Applies to: Oracle Weblogic Server – Version 9.0 to 10.3.6

Information in this document applies to any platform.

Symptoms: When attempting to remove a patch currently  applied or apply a newly downloaded patch using the Smart Update tool in command line, the following error occurs:

Encountered unrecognized patch ID: XYZ  (OR)  Unable to locate the specified product directory [/wlserver_10.3]

Cause: This error may cause due to the wrong version  patch you are trying to apply

Solution:

1.Recheck the patch version of weblogic server you are using.

Choose the right version and unzip the patch recommended while running checkMTpatch.sh. Then unzip the patch in the PATCH_TOP dir.

2.Check the permissions for the patches and move the patches into $FMW_HOME/utils/bsu/cache_dir

After moving the patch we have to smart update the patch by running bsu.

$bsu.sh –install –patch download_dir=$FMW_HOME/utils/bsu/cache_dir  -patchlist=DN1F –prod_dir=$FMW_HOME/wlserver_10.3

If it throws any error like Unable to locate the specified product directory [/wlserver_10.3]

3. Give the full path instead of $FMW_HOME and try again.

Once all are set properly it will check for conflicts …

Checking for conflicts......

Conflict(s) detected - resolve conflict condition and execute patch installation again

Conflict condition details follow:

Patch DN1F is mutually exclusive and cannot coexist with patch(es): CIH8

Exception in thread "main" java.lang.OutOfMemoryError: GC overhead limit exceeded

        at java.util.HashMap.inflateTable(HashMap.java:316)

        at java.util.HashMap.put(HashMap.java:488)

        at com.bea.cie.common.dao.xbean.XBeanDataHandler.loadPropertyMap(XBeanDataHandler.java:778)

        at com.bea.cie.common.dao.xbean.XBeanDataHandler.<init>(XBeanDataHandler.java:99)

        at com.bea.cie.common.dao.xbean.XBeanDataHandler.createDataHandler(XBeanDataHandler.java:559)

        at com.bea.cie.common.dao.xbean.XBeanDataHandler.getComplexValue(XBeanDataHandler.java:455)

        at com.bea.plateng.patch.dao.cat.PatchCatalogHelper.getPatchDependencies(PatchCatalogHelper.java:442)

        at com.bea.plateng.patch.dao.cat.PatchCatalogHelper.getPatchDependencies(PatchCatalogHelper.java:464)

        at com.bea.plateng.patch.dao.cat.PatchCatalog.getPatchDependencies(PatchCatalog.java:56)

        at com.bea.plateng.patch.dao.cat.PatchCatalogHelper.getInvalidatedPatchMap(PatchCatalogHelper.java:1621)

        at com.bea.plateng.patch.PatchSystem.updatePatchCatalog(PatchSystem.java:436)

        at com.bea.plateng.patch.PatchSystem.refresh(PatchSystem.java:130)

        at com.bea.plateng.patch.PatchSystem.setCacheDir(PatchSystem.java:201)

        at com.bea.plateng.patch.Patch.main(Patch.java:306)

If any conflicts occurs it recommends to remove the existing patch. In the above case it is suggesting to Remove CIH8 patch. Once we remove the conflict patch, then only it allows us to apply new patch Smart Update.

To remove the conflicted patches run the below command.

$bsu.sh –remove –patchlist=CIH8 –prod_dir=$FMW_HOME/wlserver_10.3

It will take time to remove. Once the conflicted patch is removed we can apply the recommended patch.

Posted by: Anil Bandi

Oracle Apps DBA

      Oracle EBS 12.2 Opatch Utility error

  OPATCH lsinventory : bash : Command not found

Applies to: Oracle Apps DBA

Symptoms:

E-Business suite 12.2, DB patching opatch related issues

When you are applying a patch ensure that you verify the Oracle Inventory because OPatch accesses it to install the patches. To verify the inventory, you have to run the following command.

$ opatch lsinventory

bash: opatch: command not found...

Similar command is: 'patch'

Solution:

You have to export the path

export PATH=$PATH:$ORACLE_HOME/OPatch:$ORACLE_HOME/bin

Posted by: Anil Bandi

Apps DBA

How to kill processes run by a User on Linux

     If you are a DBA, there are situations where you want to kill all processes belonging to a specific user, for example because the user is being removed or the user is forking malicious processes. It will take long time to kill individual processes of the user one by one manually. In this post I will show you how to kill all the process IDs at a time launched by a user.

     Here I use a command that kills all the processes owned by Linux user say "applfprd".

      To generate the process IDs, we use ps command

$ ps -ef | grep applfprd | awk {'print $2'}

Now we have to kill the process IDs which are generated above

$ ps -ef | grep applfprd | awk {'print $2'} | xargs kill -9

                                          (or)

$ sudo pkill -u applfprd

             

                                          (or)

$ pgrep -u applfprd | sudo xargs kill -9

                                           (or) 

$ sudo killall -u applfprd

Posted by: Anil Bandi

 Oracle Apps DBA