Last Year I discussed about Oracle Service Bus here, from Fusion Middleware SOA 11g, Oracle’s Enterprise Bus is renamed as Oracle Mediator and BEA’s AquaLogic Service Bus (ALSB) is now called as Oracle Service Bus.

This post covers high level Installation steps for Oracle Service Bus (OSB) 10.3.1 .  Oracle Service Bus 10.3.1 uses Oracle WebLogic Server so make sure you understand WebLogic concepts “Domain, Administration and Managed Server” more information here

.
Oracle Service Bus Installation Steps

A. Install OSB Software
B. Configure/create domain for OSB
C. Start WebLogic Server
D. Access OSB Console

A. Install OSB Software

1. Download Service Bus Software from here
2. Start Installation by running osb1031_wls103_[os].bin
3. Choose Installation Type
a) Typical- WebLogic Server, Workshop and Oracle Service Bus
b) Custom - individual components

.
4. Select Installation Directory for OSB

.

B. Create/Configure domain for OSB

1. Start domain creation by running $INSTALL_BASE/ wlserver_10.3/ common/ bin/config.sh
2. Select create a new WebLogic Domain

3. Select Generate a domain configured to automatically support Oracle Service Bus

4. Enter WebLogic Administrator Login details
5. You can choose customize installation (change listen port, server…) or select default installation

Default installation will create domain “base_domain” with Administration Server listening on port 7001

. 

C. Start WebLogic Server

$INSTALL_BASE/ user_projects/ domains/ [base_domain]/ startWebLogic.sh
 

D. Access Oracle Service Bus Console

Use URL  http://servername:7001/sbconsole

(weblogic/password) where weblogic/password are credential defined above (section B point 4)

.
.

Documentation

• Download Oracle Service Bus from here
• OSB Documentation Library here
• OSB installation Guide here

.

Oracle Service Bus High Availability Deployment (Active-Active) coming soon !!!

Share This

This post covers steps on how to troubleshoot “Unable to call fnd_ldap_wrapper . create_user / update_user” issues. This is similar to issue I discussed here in May 2009

.

Setup - E-Business Suite (11i/R12) integrated with OID/SSO
Issue- Error while creating/updating user in EBS 11i/R12 - Unable to call fnd_ldap_wrapper . create_user | update_user

.

This error could be because of many reasons , to name few
1) More Secure Password Policy in OID compared to E-Business Suite
2) User already exists in OID but missing in E-Business Suite
3)  apps user does not have privileges to access dbms_ldap package.
4) AppsDN password expired in OID (password expiry in OID)
5) OID or DIP server not running

To narrow down issue, enable debug in Apps and then search for issues around error message.

.

How to troubleshoot fnd_ldap_wrapper issues ?

Step 1 : Enable Profile Option Debug

System Administrator -> Profile -> System -> set profile option “FND: Debug Log Enabled” to Yes

.

Step 2 : Reproduce Issue

Step 3 : Check logs in FND_LOG_MESSAGES table

SQL> select module||’ ‘||message_text , timestamp from apps.fnd_log_messages where timestamp > (sysdate - 1) order by timestamp;

fnd.plsql.oid. fnd_ldap_user. create_user: ORA-31202:DBMS_LDAP: LDAP client/server error: UnKnown Error Encountered
. Server Plug-in OCI failure 12-Aug-09

Step 4 : Search for issue mentioned in message_text from apps.fnd_log_messages (In my case ORA-31202 - Server Plug-in OCI failure which was caused by custom plug-in OID for ldapadd event)

Share This

Concurrent –> Request –> Submit Request –> Gather Schema statistics (Paramerters “ALL”)The above request gathers statistics for all schemas , however it skips custom schemas registered in Oracle Applications.Explaination : Whenever Custom schemas are registerd in Oracle Applications , the entries are done in 2 tables

Share This

RCU - Repository Creation Utility (more information here ) is certified only on Windows and Linux , then how to create schema on database running on Solaris, AIX or HP-Unix ?

Download RCU on Linux/Windows machine and connect to database server (running on Solaris/HP-Unix) and load schema remotely (no client software required on Windows/Linux machine).

• Download either windows or Linux version of RCU (from here - under “Required Additional Software“) on your windows or Linux machine .
• Ensure that Windows/Linux machine can connect to remote database server on database listener port. 
• Start rcu from windows/Linux machine and connect to your database on Solaris/AIX/HP-Ux machine remotely (database client software is NOT required on Windows/Linux machine)  steps here

.

Share This

Oracle Software (Database, OID, HTTP Server, Forms & Report, Discoverer …) installation issues are logged under oraInventory/logs/[filename].log (for more on oraInventory click here ) but how to identify oraInventory location on system ?

Oracle Inventory Pointer oraInst.loc (registry variable inst_loc for windows)  determines oraInventory location

• oraInventory location in windows : INST_LOC - “c:\program files\Oracle\Inventory“
• oraInventory default location in Linux, AIX : Directory mentioned in /etc/oraInst.loc
  
• oraInventory default location in Solaris: Directory mentioned in /var/opt/oracle / oraInst.loc
  
• oraInventory default location in HP OpenVMS: Directory under sys$login 

.

.

To find INST_LOC registry variable in windows : Start > Run > regedit > HKLM > Software > Oracle

.

Share This

.

When I run a Concurrent request I get Phase - Pending and the Status - Standby. What does pending standby means and how to fix it ?

When I run a request in GL,the status appears Inactive and phase as No Manager. Please tell me what the problem could be ?

These are some of common questions I receive in my mail box so I decided to dedicate a post on concurrent request life-cycle.

.

Concurrent Request Lifecycle

Concurrent Request/Program can be under one of four Phases . Each phase has different Status .

Phase : Pending, Running , Completed, Inactive

.

Status :

Pending - Normal, Standby, Schedules, Waiting
Running - Normal, Paused, Resuming, Terminating
Completed - Normal, Error, Warning, Cancelled, Terminated, Disabled
Inactive - Disabled , On Hold, No Manager

.

.

A. Pending Standby  - Phase Pending and Status Standby means Program to run request is incompatible with other program(s) currently running.

How to check Incompatible Program/Request for any Program/Request ?

• Login with Application Developer responsibility
• Click on Concurrent > Program
• Query Program
• Click on Incompatibilities button

.

B. Inactive - No Manager

i) No manager is defined to run the request
or
ii) All managers are locked by run-alone requests
or
iii) Concurrent Manager Service is down
or
iv) No concurrent manager process because of workshift

To check Work Shift for any Concurrent Manager From System Administrator responsibility > Concurrent > Manager > Define > Work Shifts > Processes

For Description of other Concurrent Request Phase/Status click here
.

.

References

• Oracle Applications R12 System Administrator’s Maintenence Guide [Page 22-24]
• Orace Applications 11i System Administrator’s Maintenance Guide - [Page 20-21]
• Concurrent Request Phase and Status

Share This

For daily checks ( Health Check on Admin/Concurrent Manager Node click on this link eBusiness 11i/R12 - Daily Checks (for Apps. DBA) - Admin Node

.

Related : For health check in 11i Click Here 

Share This

Here is short presentation on“introduction of Oracle Web Services Manager (OWSM) 11g R1″ from Vikas Jain

OWSM is tool to secure Web Services (+ more) and provides centralized management of policies (using OWSM Policy Manager).
OWSM agents are already embedded in WebLogic Server (for more information on WebLogic click here)

.
.
OWSM is completely re-architected in 11g Fusion Middleware , for changes in OWSM from 10g to 11g click here
.

Share This

This post covers overview of Oracle Directory Service Manager (ODSM) , new tool to manager Oracle Internet Directory (OID) and Oracle Virtual Directory (OVD)

JNDI - Java Naming and Directory Interface
LDAP - Lightweight Directory Access Protocol
ODM  - Oracle Directory Manager (10g OID)
ODSM- Oracle Directory Services Manager (11g OID)
OID  - Oracle Internet Directory
OVD  - Oracle Virtual Directory
WLST- WebLogic Scripting Tool

.
Oracle Directroy Service Manager  (ODSM) - is Java application (introduced in 11g OID/OVD) to manage OID and OVD. 
a)  ODSM is java application which runs on WebLogic Server (Managed Server - wls_ods1) 
b) Oracle Directory Manager (tool to manage OID in 10g) is now deprecated in 11g OID.
c) ODSM uses JNDI to connect to OID & OVD
d) You can install and configure ODSM with OID/OVD during installation or later

.
How to find ODSM URL ?

Option 1 - $Fusion_Middleware_Home/ Oracle_Identity_Management_domain/ servers/ wls_ods/ data/ nodemanager/ wls_ods1.url

Option 2 - Identify Managed Server (wls_ods1) port and use URL http://host:port/odsm
. 

How to access ODSM ?1. Start Managed Server wls_ods1 
startManagedWebLogic.sh wls_ods1

2. Access ODSM from URL - http://host:port/odsm  where default managed server (wls_ods1) port is 7005 (cn=orcladmin)

.

.
References

• ODSM Concept
• Use ODSM to Manage OID
• Troubleshooting Directory Services Manager 
• Installing and Configuring Oracle Directory Services Manager

Share This

Today’s post is from one of our Apps DBA training exercise (more information on our online Apps DBA training [699 USD] here   ) related to Concurrent Manager.

.

How to check if Concurrent Manager is Up and running ?

Login as user with System Administrator responsibility. Under Concurrent : Manager click on Administer (Actual should be equal to Target)

.

.

.

How to troubleshoot Concurrent Manager issue ?  

Check Concurrent Manager log $SID_[MMDD] where MMDD is Concurrent Manager start Month & Date

 1. $APPLCSF/$APPLLOG/$SID_[MMDD].mgr

Could NOT contact Service Manager FNDSM_INNOWAVE03_visr12. 
 
The TNS alias could NOT be located, the listener process onINNOWAVE03 could NOT be contacted, 
 
OR the listener failed TO spawn the Service Manager process. 
 
     Process monitor session started : 24-SEP-2009 20:31:07Could NOT contact Service Manager FNDSM_INNOWAVE03_visr12. 
 
The TNS alias could NOT be located, the listener process onINNOWAVE03 could NOT be contacted, 
 
OR the listener failed TO spawn the Service Manager process.

2. Error message is pointing towards “FNDSM_INNOWAVE03_visr12″ so run tnsping to check status of TNS alias like

[avisr12@innowave03 ~]$ tnsping FNDSM_INNOWAVE03_visr12

Output like

TNS Ping Utility for Linux: Version 10.1.0.5.0 - 
 
Production on 24-SEP-2009 20:36:12Copyright (c) 1997, 2003, Oracle.  
 
All rights reserved.Used parameter files:Used TNSNAMES adapter to resolve the alias 
 
Attempting to contact (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=innowave03.com)(PORT=1638)) (CONNECT_DATA=(SID=FNDSM))) 
 
TNS-12541: TNS:no listener

3. Check Apps Listener status like

[avisr12@innowave03 ~]$ lsnrctl status APPS_visr12

LSNRCTL for Linux: Version 10.1.0.5.0 - 
 
Production on 24-SEP-2009 20:37:36Copyright (c) 1991, 2004, Oracle.  
 
All rights reserved.Connecting to (ADDRESS=(PROTOCOL=TCP)(Host=innowave03.com)(Port=1638)) 
 
TNS-12541: TNS:no listener  
 
TNS-12560: TNS:protocol adapter error  
 
TNS-00511: No listener   
 
Linux Error: 111: Connection refused

4. Start Apps Listener

[avisr12@innowave03 scripts]$ ./adalnctl.sh start

output like

adalnctl.sh version 120.3 
 
Checking for FNDFS executable. 
 
Starting listener process APPS_visr12. 
 
adalnctl.sh: exiting with status 0adalnctl.sh: check the logfile /oracle/ apps/ r12/ visr12/ inst/ apps/ visr12_innowave03/ logs/ appl/ admin/ log/ adalnctl.txt formore information ... 

5. Try again tnsping again

[avisr12@innowave03 scripts]$ tnsping FNDSM_INNOWAVE03_visr12

output like

TNS Ping Utility for Linux: Version 10.1.0.5.0 - 
 
Production on 24-SEP-2009 20:39:09Copyright (c) 1997, 2003, Oracle.  
 
All rights reserved.Used parameter files:Used TNSNAMES adapter to resolve the aliasAttempting to contact (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=innowave03.com)(PORT=1638)) (CONNECT_DATA=(SID=FNDSM))) 
 
OK (0 msec)

6. Restart CM again

For further information on Concurrent Manager click on System Administrator Maintenance Guide here  [page 21-77]

Share This