sgslufread: Hard error on read, OS error = 32 while starting OID

sgslufread: Hard error on read, OS error = 32


solution:

check your DB connection username/password.  database password might be expired.

moving datafile to ASM storage database 11.2.0.4

ORA-01157: cannot identify/lock data file 64 - see DBWR trace file
ORA-01110: data file 64: '/u01/app/oracle/product/11.2.0.4/dbhome_1/dbs/path_to_your_datafiles_foldername_of_df_you_want.dbf'
ORA-02002: error while writing to audit trail
ORA-00604: error occurred at recursive SQL level 1
ORA-01157: cannot identify/lock data file 64 - see DBWR trace file
ORA-01110: data file 64: '/u01/app/oracle/product/11.2.0.4/dbhome_1/dbs/path_to_your_datafiles_foldername_of_df_you_want.dbf'







file was created locally instead of ASM storage. corrective action is move the file using RMAN (use copy command /oroginal/location  to '+DATA/' )

alter database rename file in database so system will also look at ASM place

starting and stoping Managed server stack commands if you dont know the names of each managed server

If you do not know the names of the Managed Servers that should be started, you can view the contents of the following file on Linux or UNIX systems:

DOMAIN_HOME/startManagedWebLogic_readme.txt

On Windows systems:

DOMAIN_HOME\startManagedWebLogic_readme.txt

Or, you can access the Administration Server console at the following URL:

http://host:admin_server_port/console

Supply the user name and password that you specified on the Configure Administrator Username and Password Screen of the Configuration Wizard. Then, navigate to Environment > Servers to see the names of your Managed Servers.




To stop the stack components from the command line, perform the following steps:

1. Stop WebLogic managed components, such as Oracle Access Management, Oracle Identity Manager, and Oracle Adaptive Access Manager, by executing the following command:
   

   DOMAIN_HOME/bin/stopManagedWebLogic.sh \
   {SERVER_NAME} {ADMIN_URL} {USER_NAME} {PASSWORD}
   

2. Stop the Oracle WebLogic Administration Server by executing the following command:
   

   DOMAIN_HOME/bin/stopWebLogic.sh

3. If you want to stop the Node Manager, you can use the kill command:
   

   kill -9 PID
   

what is OAM, very good explanation

In today’s world with increase in number of applications (Business apps, mobile apps, Enterprise apps)

It is a challenge to provide seamless Single Sign On (SSO) experience across any application from any device. We cannot integrate every new application to the existing security solution. It leads to managing multiple identities.

OAM helps us to achieve seamless and secure access across all the channels, be it web, mobile etc.

Through OAM we set up the policies on application access at one place and that carries through no matter what channels or the way we access that application. In this way, it assures all polices are consistent across the system.

It helps the developer of the application to concentrate only on the function implementation and not worry about security implementation. Also for the security Administrators, it is easy to manage and troubleshoot as OAM provides a single console to administer and configure the policies.

OAM also provides auditing capabilities which is useful for compliance.

FEATURES OF OAM:

•       Authentication: Validating a user against an identity store.

•       Authorization: Once the user is authenticated, validating the authorization policies. Is the user authorized to access the resource?

•   Managing sessions and SSO for Web Tier: Maintaining session for users, like idle time out, session timeout, how many concurrent user sessions can be created?

1.1 About Oracle Access Manager

Oracle Access Manager (formerly known as Oblix NetPoint and Oracle COREid) provides a full range of identity administration and security functions, that include Web single sign-on; user self-service and self-registration; sophisticated workflow functionality; auditing and access reporting; policy management; dynamic group management; and delegated administration.

Oracle Access Manager offers a DMZ-type three-tier architecture to provide a highly secure deployment with maximum protection of data and applications that includes the following:

• Identity System: The industry's first and most mature enterprise identity management system. The Identity System (formerly known as NetPoint COREid) provides user management and self service, dynamic group management and organization management, privacy enforcement, delegated administration, and powerful workflow to secure additions and changes to any of these. The Identity System is used to manage hundreds of thousands to millions of users in some of the world's largest extranets and portals.
• Access System: The access-control system (formerly known as the NetPoint Access System). The Access System, Network Computing's 2003 Product of the Year, provides single sign-on across any Web application. It supports a variety of access policies, and is fully integrated with the Identity System so that changes in user profiles are instantly reflected in the Access System's policy enforcement.
• Integration Services: Extends Oracle Access Manager capabilities to all your applications. By providing integration points with systems and applications from other vendors, Oracle Access Manager enables out-of-the box integrations with most leading application servers, Web servers, directories, portal servers, system management products, and packaged applications.

opensaml::FatalProfileExceptionThe system encountered

Error Message:
opensaml::FatalProfileExceptionThe system encountered an error at Sat Oct 8 10:20:46 2016To report this problem, please contact the site administrator at . Please include the following message in any email:opensaml::FatalProfileException at ( )Assertion contains an unacceptable AudienceRestriction.

Solution:

we have solved this error by fixing prividerId in a URL. we was getting this error because of wrong provierId

sgslunlListen: Bind failed (port=389), OS error=(13)

error
sgslunlListen: Bind failed (port=389), OS error=(13)


Solution:
in my case database was not accepting connection. OID stores information in database and my database was having issues. fixing database issues resolved issues at OID level.

script to start weblogic server, OID , OVD servers

#!/bin/sh

export ORACLE_HOME=/home/oracle/app/oracle/product/11gR1ps1/Middleware/Oracle_IDM1

export MW_HOME=/home/oracle/app/oracle/product/11gR1ps1/Middleware
export WL_HOME=/home/oracle/app/oracle/product/11gR1ps1/Middleware/wlserver_10.3
export WLS_HOME=/home/oracle/app/oracle/product/11gR1ps1/Middleware/user_projects
export JAVA_HOME=/usr/java/default
export PATH=$JAVA_HOME/bin:$ORACLE_HOME/bin:$ORACLE_HOME/ldap/bin:$ORACLE_HOME/dcm/bin:$ORACLE_HOME/opmn/bin:$WLS_HOME/bin:$PATH
export LD_LIBRARY_PATH=$ORACLE_HOME/lib

export DOMAIN_HOME=$MW_HOME/user_projects/domains/base_domain


cd $DOMAIN_HOME
echo "*********************************"
echo "* Starting the WLS Admin Server *"
echo "*********************************"
date

nohup sh startWebLogic.sh >/dev/null 2>/dev/null &
sleep 1
while [ 1 -gt 0 ]; do
tail -100 AdminServer.log | grep 'Server started in RUNNING mode'
if [ $? -eq 0 ]; then
printf "Admin Server is RUNNING\n"
break
fi
printf "."
sleep 1
done


echo "******************************"
echo "* Starting OID / OVD Servers *"
echo "******************************"
date

cd $ORACLE_HOME/opmn/bin
./opmnctl startall
sleep 1
./opmnctl status


cd $DOMAIN_HOME/bin
echo "****************************************"
echo "* Starting the wls_ods1 Managed Server *"
echo "****************************************"
date
nohup sh startManagedWebLogic.sh wls_ods1 "http://localhost:7001" >/dev/null 2>/dev/null &