Wednesday, November 28, 2012

OIM xelsysadm password reset

We had a request from customer to reset the xelsysadm password reset.I thought it would be a complex process using ladapmodify etc..but it was very simple.

1)You need to use the Administrator Console, edit the "System Administrator" user (user login "xelsysadm"), select the "Change Password At Next Login" check-box, logout and login again. Then you can change the xelsysadm password.

Tuesday, November 27, 2012

ORA-00001: unique constraint (PROD_SOAINFRA.AT_PK) violated

I was seeing a huge amount of errors pertaining to AT_PK table ,


####<Nov 27, 2012 3:01:57 AM CET> <Error> <EJB> <host> <WLS_SOA1> <orabpel.audit.pool-3.thread-4> <<anonymous>> <> <0000JfFsuuR6eLMaELq2US1G_pet000IDr> <1353981717680> <BEA-010026> <Exception occurred during commit of transaction Name=[EJB com.collaxa.cube.engine.ejb.impl.bpel.BPELAuditTrailBean.storeAuditBatch(com.collaxa.cube.engine.audit.BatchEvent,com.collaxa.cube.persistence.dto.AuditCounter)],Xid=BEA1-074BC784ED925837639D(810973762),Status=Rolled back. [Reason=Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.1.3.v20110304-r9073): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (PROD_SOAINFRA.AT_PK) violated

Error Code: 1
        bind => [305173755, 0, 39, 11816, 2012-11-27 03:01:51.677, 1891, 0, [B@30572981]

Solution as per: Doc ID 1338478.1

They suggest to apply the patch ,will apply this and see if issue gets fixed.

Saturday, November 24, 2012

IPM Web Support Server Logging

IPM 10g is a very old and stable product. Once you set it up, it goes very smoothly.But this customer wanted to enable logging ,i followed the below procedure.

To enable logging, perform the following steps:

   1. Login to IBPMExpress client (typical URL to log in to IBPMExpress: http://ServerName/ibpmexpress).
   2. Click on Administration (located in the left pane).
      Note: If you do not see Administration then the user you logged in as has not been given Web Administration Privileges through IPM Security Policies.
   3. Scroll down to the Diagnostics Section.
   4. Enter in a valid location for Real Time Log File Location.
   5. Checkbox the following options:
      a) Trace all available reporting points
      b) Trace all datasets
      c) Trace all outbound notifications
      d) Trace Key Points
      e) Use Realtime Logging
   6. Restart the Oracle Web Support Server service.

The above options can also be found in the WSSConfigEditor.exe tool which is located in the install directory.  (Example location: C:\Program Files\Stellent\WSS\WSSConfigEditor.exe)

Friday, November 23, 2012

Upgrade Oid Status Shows Invalid In dba_registry and app_registry tables

I usually don't work on 11g OID,but was helping out a team here.Issue comes on OID version to

OID showing as INVALID in dba_registry and app_registry tables.

select * from dba_registry where status='INVALID' and
select * from app_registry where status ='INVALID'

OID shows invalid.


OID showing as invalid in dba_registry and app_registry tables, however when viewing ODS objects -- all are valid
SQL> select owner,object_name,object_type from dba_objects where owner='ODS' and status='INVALID'; 

This could be caused due to possible problem with upgrade script (oidiugrd.sql).OID showing as invalid in dba_registry and app_registry tables, however when viewing ODS objects -- all are valid

Errors can be found in  $ORACLE_HOME/ldap/admin/LOGS/ldapupgrade.log

Check the ODS schema for invalid objects and correct as necessary

% sqlplus / as sysdba
SQL> select owner,object_name,object_type from dba_objects
2> where owner='ODS' and status='INVALID';

Cut the final validation portion of oidiugrd.sql and run it by itself:

alter session set current_schema = SYS;

rc integer;
rc := ods.ldapUpgUtls.validateODS();
if rc = 0 then
end if;


Register OHS 11g

Sometime after upgrade on fusion we get issues with ohs.ohs shows as down on em, despite being up.We have faced this many times, so we have included below steps after all fusion upgrades.

--------UNREGISTER OHS ---------------------------
-bash-3.2$ ./opmnctl unregisterinstance -instanceName ohs1 -adminHost host -adminPort port

Command requires login to weblogic admin server (host):
  Username: weblogic

Unregistering instance
Command succeeded.

--------REDEPLOY OHS ---------------------------
-bash-3.2$ ./opmnctl redeploy -adminHost host -adminPort port

Command requires login to weblogic admin server (host):
  Username: ohsadmin

Redeploying NonJ2EEManagement Application...weblogic.Deployer invoked with options:  -adminurl -username ohsadmin -name NonJ2EEManagement -source /test/fmw/product/111/ohs/opmn/applications/NonJ2EEManagement.ear -redeploy -upload -noexit
<Apr 24, 2012 3:25:01 PM CDT> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating redeploy operation for application, NonJ2EEManagement [archive: test/fmw/product/111/ohs/opmn/applications/NonJ2EEManagement.ear], to configured targets.>
Task 0 initiated: [Deployer:149026]deploy application NonJ2EEManagement [Version=11.1.1] on AdminServer.
Task 0 completed: [Deployer:149026]deploy application NonJ2EEManagement [Version=11.1.1] on AdminServer.
Target state: redeploy completed on Server AdminServer

Command succeeded.

--------REGISTER OHS ---------------------------
 ./opmnctl registerinstance -adminHost host -adminPort port

Command requires login to weblogic admin server (host):
  Username: weblogic

Registering instance
Command succeeded.

-adminHost is the weblogic admin server
-adminPort is the port for the admin server

Kill particular OS process

ps -ef |grep <Process> |awk '{print  $2}'|xargs kill -9

For example:
ps -ef |grep LOCAL=NO |awk '{print  $2}'|xargs kill -9

Disable 11g gather stats

I know this is very simple,but here it is,

 col JOB_NAME for a30
 col START_DATE for a30
 col LAST_START_DATE for a30
 col NEXT_RUN_DATE for a30

SELECT owner, job_name, job_class, enabled FROM dba_scheduler_jobs;

exec dbms_scheduler.disable('GATHER_SYS_STATS_JOB');

OIM Bundle patch

I was applying bundle patch on OIM as per,

+ opatch apply was failing.The logs are here,


Saw this error,
/test/fmw/product/111/iam_111/server/setup/deploy-files/setup.xml:337: Unable to delete directory --->I renamed the folder manually.

+ The script "sh"  looks for profile files.Need to update weblogic.profile as well.

+ Later got the error as in Doc ID 1441378.1 .Set the path as per the note.

Later it failed with errors like,

With errors like,
java.lang.RuntimeException: Can't find resource 'solrconfig.xml' in classpath or '${RBACX_HOME}/.indexes/cores/core01/conf/',

java.lang.RuntimeException: Can't find resource 'solrconfig.xml' in classpath or '${RBACX_HOME}/.indexes/cores/core08/conf/', cwd=/twrl2s/admin/user_projects/oia_domain

RBACX_HOME is set in .profile.But i added additionally in

JAVA_PROPERTIES="-Dplatform.home=${WL_HOME} -Dwls.home=${WLS_HOME} -Dweblogic.home=${WLS_HOME}  -DRBACX_HOME=/test/fmw/product/111/oia_111"

Hope this port will be helpful.Took me sometime to figure out

Portal 11g patch issue

While applying patch on portal came across this issue and was able to fix it.

Applying Portal Patch!!
Copying file /prod/fmw/patches/13985116/custom/scripts/ to /prod/fmw/product/111/portal/portal/patch/oneoffs/
CMD=./ptlpatch.csh  -z -s dev1_portal -p oracle -c host:port:SID

Return Code = 1
Command invocation returned Error... '', Return Code = 1
Execution of PRE script failed, with return value = 1

Do you want to proceed? [y|n]
User Responded with: Y

Patching component oracle.portal.midtier,
Copying file to "/prod/fmw/product/111/portal/portal/patch/oneoffs/13985116.txt"
ApplySession adding interim patch '13985116' to inventory

Verifying the update...
Inventory check OK: Patch ID 13985116 is registered in Oracle Home inventory with proper meta-data.
Files check OK: Files from Patch ID 13985116 are present in Oracle Home.
The following warnings have occurred during OPatch execution:
1) OUI-67133:Execution of PRE script failed, with return value = 1

+ ptlpatch.csh didnot have execute permission.Give it the 755 permission.
+ Added the tnsnames.ora in portal home ,it was unable to connect to database.
+ opatch apply /prod/fmw/patches/13985116 -pre -s dev1_portal -p oracle -c host:port:SID  -opatch_pre_end-->No quotes needed in syntax!