Wednesday, June 16, 2010

java.sql.SQLException while registering Ebiz with SSO

Hi
Recently while trying to integrate an EBiz R12 instance with OID for Single Sign On functionality we hit an while running the following command:
$FND_TOP/bin/txkrun.pl -script=SetSSOReg -registersso=yes -appspass=apps
Fri Jun 11 03:47:39 PDT 2010 =========================================
Fri Jun 11 03:47:39 PDT 2010 OracleAS Single Sign-On Registration Tool
Fri Jun 11 03:47:39 PDT 2010 =========================================
Fri Jun 11 03:47:39 PDT 2010 Parameters passed to SSO registration tool :
param0:-oracle_home_path
param1:/cdv1001/apps/tech_st/10.1.3
param2:-site_name param
3:http://sord142.corp.com:8010
param4:-config_mod_osso param
5:true param6:-logout_url param7:http://sord142.corp.com:8010/OA_HTML/AppsLogoutSSO
param8:-home_url
param9:http://sord142.corp.com:8010
param10:-config_file param11:/cdv1001/inst/apps/cdv_sord142/ora/10.1.3/Apache/Apache/conf/osso/cdv_sord142_osso.conf param12:-update_mode
param13:CREATE
param14:-success_url
param15:http://sord142.corp.com:8010/osso_login_success
param16:-cancel_url
param17:http://sord142.corp.com:8010
Fri Jun 11 03:47:39 PDT 2010 -DinstallType=
Fri Jun 11 03:47:39 PDT 2010 -DoldOracleHome=Fri Jun 11 03:47:39 PDT 2010 -DoldOHSUser=root
Fri Jun 11 03:47:39 PDT 2010 SSO database is jdbc:oracle:thin:@ldap://ldap-imdvrdc.domain.com:3051/idmdvrdc,cn=oraclecontext
Fri Jun 11 03:47:40 PDT 2010 Exception while creating database connection :java.sql.SQLException: Io exception: The Network Adapter could not establish the connectionjava.sql.SQLException: Io exception: The Network Adapter could not establish the connection at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:125) at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:162) at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:274) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:328) at oracle.jdbc.driver.PhysicalConnection.(PhysicalConnection.java:361) at oracle.jdbc.driver.T4CConnection.(T4CConnection.java:151) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:595) at java.sql.DriverManager.getConnection(DriverManager.java:525) at java.sql.DriverManager.getConnection(DriverManager.java:171) at oracle.security.sso.SSORegistrar.main(SSORegistrar.java:327)Fri Jun 11 03:47:40 PDT 2010 Check if your database is up and running.

Fix:
The database was up and running and there were no issues. However, in this case, the ebiz server was in a different domain than that of our OID environment and we had opened specific ports between the environments to allow access to the OID servers. When we performed telnet test on database listener port, everything was fine. However, when trying to register the error was showing up.

Further investigation revealed that oraclecontext was was pointing to database name instead of databasename.domain.com. In our telnet tests we were using fully qualified hostname to test the access. To over come this issue, we put an entry in /etc/hosts of the web server of ebiz environment as follows:

123.45.67.89 dvdb.domain.com dvdb

In the above entry, first entry is the IP address of the database host of the OID and subsequent entries are the databasehost.domain.com and databasehost values.

This resolved the issue.

- Aravind Kamath Posral

Monday, June 14, 2010

FNDOPP24553.txt:usdsop: exec failed during spawn/apps/local/TS10EF/inst/apps/TS10EF_'uname -n'/admin/scripts/java.sh: No such file or directory

Hi,
we had just cloned an R12.1.1 apps instance. In the target instance, TS10EF, the Output Post Processor and Workflow Background Listener managers were not coming up. The log of the OPP manager had the following error:
FNDOPP24553.txt:usdsop: exec failed during spawn/apps/local/TS10EF/inst/apps/TS10EF_'uname -n'/admin/scripts/java.sh: No such file or directory

Fix:
The issue is caused by incorrect AFJVAPRG environment variable setting. It should point to $ADMIN_SCRIPTS_HOME/java.sh. However, in our case, there was 'uname -n' in the environment variable which was causing this issue. To fix this, make the change in xml file for AFJVAPRG environment variable to reflect the context name (TS10EF_istg03) and run autoconfig. If you dont wish to run autoconfig, you can make the change in xml and also change AFJVAPRG the follow env file:
/apps/ts10ef/apps/apps_st/appl/istg03.env
Once the fix is done, log out , log in, source the env and start the concurrent managers. This should resolve the issue. However, in our case, it did not. In
the administer concurrent managers screen, we were seeing the following error:
"System Hold, Fix Manager before resetting counters "

To over come this issue, shutdown concurrent managers, run cmclean.sql (or basically set the process codes right) and start the managers. The problem would be fixed.

- Aravind Kamath Posral