Identity and Access Management, Identity Governance

yum install and groupinstall difference is explained below http://serverfault.com/questions/274279/whats-the-difference-of-group-install-vs-regular-install-in-linux groupinstall is for installing packages in a group without having to install each individual package which is done via yum install "package_name"

If orcladmin password is locked then use the oidpasswd utility provided in OID to unlock the password as below. oidpasswd connect=<database connection> unlock_su_acct=true ldapbind -h host -p 389 -D cn=orcladmin -w "password" gives following error if your password is locked ldapbind_bind: DSA is unwilling to perform ldapbind_bind: additional info: Password Policy Error: 9001 cn=orcladmin: Your account is locked. Contact your OID administrator Check following references https://community.oracle.com/thread/506036 http://onlineappsdba.com/index.php/2008/05/15/sso-how-to-deal-with-your-account-is-locked/ http://onlineappsdba.com/index.php/2010/08/04/osr-11g-account-management-failed-with-error-initialization-of-accounts-has-failed-contact-the-administrator-of-the-registry/

OID uninstall requires running deinstall for the ORACLE_HOME and Instance. First deinstall the Instance then oracle_home. Oracle Fusion Middleware link for OID uninstall http://docs.oracle.com/cd/E23943_01/install.1111/e12002/deinstall.htm#INOIM457 Link to Installation Guide http://docs.oracle.com/cd/E23943_01/install.1111/e10033/configone.htm#OIMQI1543

OAMOIM: OAM console access (oamconsole )

OAM console access <host>:port/oamconsole requires that OAM host have dns entry when accessed from remote host. This is required since there is a redirection to the 14101 port during authentication. If there is no dns entry for the host for the remote host it will not be able to continue to the host/port for authentication. After authentication is completed the page for <host:port>/oamconsole is available.

Error while installing package Desktop - yum groupinstall 'Desktop' Transaction Check Error:   file /etc/pki/rpm-gpg/RPM-GPG-KEY from install of rhn-client-tools-1.0.0.1-18.0.2.el6.noarch conflicts with file from package oraclelinux-release-6:6Server-5.0.2.x86_64 This can be fixed by installing below two packages oraclelinux-release and rhn-client-tools   (Refer Release notes http://docs.oracle.com/cd/E37670_01/E57668/E57668.pdf Link ) After installing above two packages, reboot and you are set to launch Desktop GUI startx will give issues if you are using su to another user The logon process assigns the console ownership to the user who logons. If you su user then ownership of the console ownership remains with user who logged on. To avoid this login as the user and then startx. Above fix is for Oracle Linux 6.5 Oracle Linux 6.5 installation  http://oracle-base.com/articles/linux/oracle-linux-6-installation.php   Link

RedHat 6 Server RedHat Documentation

How to fix error for X11 Forwarding on Oracle Linux 6.5 On connecting via ssh to Oracle Linux server (6.5) gave following error X11 forwarding request failed on channel 0 Solution:    Add following two lines to sshd_config file  /etc/ssh/sshd_config Forwarding yes X11 UseLocalhost no Now after making above changes to the sshd_config file, restart the sshd service Command to restart sshd service    service sshd restart Make sure you have xauth available SSH login works fine and /usr/bin/xauth: creating new authority file /root/.Xauthority Hope this helped you. I used below urls as reference when solving my issue. Feel free to provide your comments and if there any other issues you faced. https://www.centos.org/forums/viewtopic.php?t=17982 http://www.cyberciti.biz/faq/how-to-fix-x11-forwarding-request-failed-on-channel-0/X11

OAM 11gR2, Oracle Access Manager new installation creates boot.properties for Admin Server. However for Managed server you need to create boot.properties. If boot.properties is not there the weblogic server start will ask for credentials. So you create a new file boot.properties with just two lines as below. Managed server uses this boot.properties file to retrieve the username/password in order to start/authenticate the managed services. How to create boot.properties file First create new directory “security” and inside it create the boot.properties file. Enter below two lines (as shown below) username=weblogic password=yourpassword After first start of Managed server the contents of the file will be encrypted. So if you open the boot.properties file you will see two lines with some random text (which is actually encrypted version of the two lines). So if you forgot the password then by opening this file you will not be able to the see the password. In this case you wil

A new out of the box install of Oracle Identity Manager, OIM contains 4 default users (1)  XELSYSADM (2)  XELOPERATOR (3)  WEBLOGIC (4)  OIMINTERNAL You can check the USR table for the number of users as below select count(*) from usr; COUNT(*) -------------------                4 -------------------------------------------------------------------------------------------------------------------------- OIMINTERNAL user For OIMINTERNAL account, the guidance from Oracle is to never change the password of this account. This account is created during OIM install and is used internally by OIM. -------------------------------------------------------------------------------------------------------------------------- WEBLOGIC user Change the   WEBLOGIC password Here is the link that provides steps to change the weblogic password . (same as below) 15.15  Enabling Oracle Identity Manager to Connect to SOA Using the Administrative Users Provisioned in LDAP Or