Skip to main content

Posts

OPMNCTL Missing after clone

Find the server timeout and increase the value in the context file grep s_adminservertimeout $CONTEXT_FILE ##Set to 4000 vi $CONTEXT_FILE /s_adminservertimeout adautocfg.sh Create the missing domain $FND_TOP/bin/txkrun.pl -script=ChkEBSDependecies -server=ALL_SERVERS cd $FND_TOP/patch/115/bin ps -uapplyes ## Make sure no processes are running echo $CONTEXT_FILE perl txkEBSDomainConfig.pl Remove node if its there from PROD clone sqlplus apps/$APPS_PASS select node_name from ADOP_VALID_NODES; dELETE FROM ADOP_VALID_NODES WHERE EXISTS ( select node_name from ADOP_VALID_NODES where node_name='prodserver' ); commit; exit; Run autoconfig and start the application tier adautocfg.sh adstrtal.sh apps/$APPS_PASS ## After R12.2.4 Upgrade Found OPMNCTL Missing While Starting Services (Doc ID 1953456.1)
Recent posts

JBO-29000 Excpetion

Users tried to log on to the development instance an after logging on they get the really helpful message:
You have encountered an unexpected error. Please contact your System Administrator for assistance.

Digging into the exception log I found this:
JBO-29000: Unexpected exception caught: java.lang.NoClassDefFoundError, msg=Could not initialize class oracle.apps.fnd.functionSecurity.User;

So I ran autoconfig after seeing a few things about mx paramter in the $CONTECT_FILE. I then started the services again and everything was working fine.Hope this helps anyone who might be scratching their heads about this.

Session Killer

I've been noticing lately that the database does not seem to be cleaning up after itself and the processes just keep climbing and climbing. Some sessions are more than two weeks old. I thought this was a bit weird and when our monitoring system started alerting to the number of sessions I realised there was a lot of dead session that are inactive but not being cleaned up. This is probably due to pooling and the way the DB is trying to save resources but in the EBS once a user closes a form they will not be using that session again. This sql give me the code to kill the session both in the DB as well as on the server itself:

select vp.SPID,vs.username, UPPER(vs.program) program, logon_time,         floor(vs.last_call_et / 60 ) min_inactive        ,floor(vs.last_call_et / 60 /60 ) hr_inactive, vs.status, vs.status        ,'alter system kill session '''||vs.sid||','||vs.serial#||''';'        ,'kill -9 '||vp.SPID from v$session vs, v$pro…

Failed to initialize the application 'EBSDataSource' due to error weblogic.application.ModuleException after FNDCPASS apps change

Started testing password changes in our clone environments. Weblogic seems to love throwing you curve balls and when I changes the apps password with the below:
FNDCPASS apps/$APPS_PASS 0 Y system/system SYSTEM APPLSYS $APPS_PASS
I was not able to start the weblogic managed servers. A look in the log an I found this:

weblogic.application.ModuleException:
        at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:327)
        at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
        at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517)
        at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
        at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
        at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45)
        at weblogic.application.internal.BaseDep…

adrci Tool

I found this neat little tool for digging into the alert log without having to actually open it up and start searching line by line. Produces a nice little summary and also generates a report if you need to upload something to MOS.
adrci> show problem
ADR Home = /u03/oratest/testdb/11.2.0.4/admin/TEST_oratest/diag/rdbms/test/TEST: ************************************************************************* PROBLEM_ID           PROBLEM_KEY                                                 LAST_INCIDENT        LASTINC_TIME                              -------------------- ----------------------------------------------------------- -------------------- ----------------------------------------  2                    ORA 600 [pfrdef1_get_tdo#145: pin failed]                   116801               2016-02-10 11:20:29.927000 +02:00        4                    ORA 7445 [kgmdtim()+85]                                     118161               2016-02-10 11:22:02.762000 +02:00        1              …