How to Reset / Change ias_admin Password

Hi Everyone,

I came across the situation where i forget my ias_admin password of oracle Application server.
Below are the steps for reset/change ias_admin password.


You can reset/change ias_admin password in following ways

Step 1. Using Enterprise Manager (Application Server Control) Web Site:

–Login to Instance Home Page (ias-console)

–Click on Preferences on top right

–In new screen, click on “Change Password” on left menu

–Enter current password and New Password

.
2. Using Command line tool

we can also reset password of ias-console for oracle application server :

emctl set password <old_password> <new_password>

like

emctl set password oracle  oracle123(Here oracle is current ias_admin password and oracle123 is new password which you wish to reset)

If you don’t know current ias_admin password then change it in configuration file (And the last which i have faced problem)

.

3. Change ias_admin password directly in configuration file

–Backup /oracle/orainfra/sysman/j2ee/config/jazn-data.xml and /oracle/orabi/sysman/j2ee/config/jazn-data.xml

–Search for entry like below

  <user>
    <name>ias_admin</name>
      <credentials>{903}8QkQ/crno3lX0f3+67dj6WxW9KJMXaCu</credentials>
  </user>

and Update new password (oracle123 like )

  <user>
    <name>ias_admin</name>
      <credentials>!oracle123</credentials>
  </user>

Note ! (Exclamation Mark in front of password. This signifies that password is stored in clear text)

This helped me alot.. Hope it helps you too..

Enjoyy working with Middleware.

Regards,
Ajinkya Vichare


.

"OIMAuthenticationProvider is not specified" Error while Starting Managed Servers using Node manager in OIM 11g

Hi Everyone,


I have tried hands on OIM implementation in cluster mode but when i tried to start my Managed server, have receive following error while while Starting Managed Servers using Node manager in OIM 11g.
When attempting to start managed server using Node manager, having extended domain with Oracle Identity Manager the following error occurs.

Managed logs are given below :

<Jun 2, 2010 6:01:37 PM IST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Jun 2, 2010 6:01:37 PM IST> <Notice> <Log Management> <BEA-170019> <The server log file /oracle/app/admin/IDMDomain/mserver/IDMDomain/servers/wls_ods1/logs/wls_ods1.log is opened. All server side log events will be written to this file.>
<Jun 2, 2010 6:01:37 PM IST> <Warning> <NodeManager> <BEA-300043> <Node manager native library not found - server process id not saved.>
<Jun 2, 2010 6:01:37 PM IST> <Error> <Socket> <BEA-000438> <Unable to load performance pack. Using Java I/O instead. Please ensure that libmuxer library is in :'/tmp/OraInstall2010-10-10_02-35-47PM/jre/lib/amd64/server:/tmp/OraInstall2010-10-10_02-35-47PM/jre/lib/amd64:/tmp/OraInstall2010-10-10_02-35-47PM/jre/../lib/amd64:/oracle/app/product/fmw/idm/lib:/oracle/app/product/fmw/idm/lib:/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib:/oracle/app/product/fmw/idm/lib/:/oracle/app/product/fmw/idm/jdk/jre/lib/i386/:/oracle/app/product/fmw/wlserver_10.3/server/native/linux/i686:/oracle/app/product/fmw/idm/lib/'
>
Jun 2, 2010 6:01:42 PM oracle.security.jps.internal.policystore.util.PolicyStoreRefreshThread run
INFO: Policy store cleanup thread started.
<Jun 2, 2010 6:01:43 PM IST> <Error> <Security> <BEA-090870> <The realm "myrealm" failed to be loaded: weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: com.bea.common.engine.SecurityServiceRuntimeException: [Security:097533]SecurityProvider service class name for OIMAuthenticationProvider is not specified..
weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: com.bea.common.engine.SecurityServiceRuntimeException: [Security:097533]SecurityProvider service class name for OIMAuthenticationProvider is not specified.
at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(CSSWLSDelegateImpl.java:342)
This issues has occured due to missing OIMAuthenticator.jar and oimsignaturembean.jar in the classpath on affected machine node.

To overcome this problem, you can follow the steps given below :

Solution :

Step 1) Copy OIMAuthenticator.jar and oimsignaturembean.jar from \Oracle\Middleware\Oracle_IDM1\server\loginmodule\wls\ location to affected machines location \Oracle\Middleware\wlserver_10.3\server\lib\mbeantypes on the affected machine.

2) Also add the location of these jar files into ALT_TYPES_DIR in the setDomainEnv.sh.

3) After copying jars, servers needs to be restarted for this to take effect.

[ Reference  : metalink note : 1271932.1 ]

Thanks to Oracle metalink..Will post OIM clustering very soon.....!

And enjoy working with Middleware technologies :).

Regards,
Ajinkya Vichare

Restarting the Application Server After a Crash - OID Failure

Dear All,

While working with oracle application server many of the people come accross the sevirity 1 issues for OID crash issues.

I also face the same many times, so today we will discuss about possible solutions for OID crash issue.

The Oracle Application Server 10g is a group of interdependent components.  Many times the application server will not restart after a crash or improper shutdown. The culprit is almost always the Oracle Internet Directory or OID.

If you get the error "1 of 4 Components Started" when running opmnctl startall, the problem is that OID is not being started.  The only infrastructure component not dependent on OID is the Oracle HTTP Server or  OHS.  No matter how many times you reboot the server, the application server will not start correctly without OID.

This problem happens in  9iAS and AS 10g

OID is started, stopped and monitored by a process called oidmon.  Oidmon will periodically check a database table called ods.ods_process to determine if an OID process needs to be started, stopped or restarted. It is the row in the ods_process table that usually causes the problem.  If the application server
crashed or was improperly shutdown, oidmon may not have been able to update the ods_process table.  When the application server restarts, oidmon will find the row in the table identifying a running OID process and so will not start OID. The fix is to remove the row in the ods_process tables.

There are two possible fixes.

First shutdown the application server, but not the metadata repository database.

On windows make sure that all the services set to automatic are started.  

On UNIX/Linux ensure the oidmon is running.

# ps -ef |grep oid

oracle 3331 3318 0 Mar30 ? 00:00:02     /oracle/orainfra/bin/oidmon

If OID is running you will get two other process called oidldap.  If you have all three processes, then starting OID is not your issue so this solution will not solve you problem.

oidmon must be running to start OID.  If oidmon is not running, start it with the command below:

ORACLE_HOME=C:\oracle\orainfra

$ORACLE_HOME/bin/oidmon start

On windows oidmon is a service, insure the Oracle<Infra>InternetDirectory_iasdb services is started.

Solution 1.  Using Windows -UNIX/Linux

Set the environment:

For windows Environment :

c:\> set ORACLE_HOME=c:\oracle\orainfra
c:\> set ORACLE_SID=iasdb

For Unix Environment :

Login with oracle user :

export ORACLE_HOME=/oracle/orainfra

export ORACLE_SID=iasdb

Log onto the database :

c:\> SQLPLUS "/ as sysdba"

SQL> select * from ods.ods_process;

Should get one line returned. If not go to solution 2.

SQL> deleted from ods.ods_process;
one line deleted

SQL> commit;
commit complete

SQL> exit

Now reboot the server to bring up the appsvr normally.

Solution 2;

If there is no entry in the ods.ods_process table then oidmon was never told to start OID. Here we need to tell oidmon to start OID.

for windows :

c:\oracle\orainfra\bin>oidctl server=oidldapd configset=0 instance=1 start

for Unix platform :

/oracle/orainfra/bin>./oidctl server=oidldapd configset=0 instance=1 start

Now restart the application server instances using opmnctl startall.

Once the Oracle Internet Directory is running, the other components should start normally

I hope it will help you while solving OID crash issues...

Enjoy working with Middleware Technologies...

Regards,
Ajinkya