This discussion is archived
1 2 Previous Next 20 Replies Latest reply: Aug 2, 2013 4:17 PM by 987840 RSS

After upgrading to OBIEE 11.1.1.7 BI Scheduler component does not start

D.Mozeli Newbie
Currently Being Moderated

Hi,

 

We are facing an issue after upgrading OBIEE 11.1.1.5 to OBIEE 11.1.1.7 Cluster environment. All other opmn services start with no issue. The BI Scheduler component stays a long time in "Init" status and after 5-10 minutes it changes to down. The problem is happening on both BI nodes. We have already tried to use opmn startall and opmnctl startproc ias-component=coreapplication_obisch1 but they both failed to start the BI Scheduler.

 

[oracle@agtbiapp01 bin]$ ./opmnctl status

 

Processes in Instance: OBI_instance1

---------------------------------+--------------------+---------+---------

ias-component                    | process-type       |     pid | status

---------------------------------+--------------------+---------+---------

coreapplication_obiccs1          | OracleBIClusterCo~ |    5027 | Alive

coreapplication_obisch1          | OracleBIScheduler~ |   10245 | Init

coreapplication_obijh1           | OracleBIJavaHostC~ |    5018 | Alive

coreapplication_obips1           | OracleBIPresentat~ |    5019 | Alive

coreapplication_obis1            | OracleBIServerCom~ |    5017 | Alive

 

Here is the the result of the nqscheduler.log:

 

[2013-07-25T09:19:49.000-05:00] [OracleBISchedulerComponent] [NOTIFICATION:1] [] [] [ecid: 004s_Qs0^gq5IfK5qVP5iY0001KV000003,0] [tid: 41e41940]  [16020] Metadata Database Type: Oracle 11g [[^M

Data Source Name: (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=xxxxxxtdb-scan.xxxxxxxx.com)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=WLTST)))

Data Source Type: Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64b^M

]]^M

[2013-07-25T12:38:29.000-05:00] [OracleBISchedulerComponent] [WARNING:1] [] [] [ecid: ] [tid: bf868700]  [67004] Configuration value iBots\NumGlobalRetries not set.^M

[2013-07-25T12:38:29.000-05:00] [OracleBISchedulerComponent] [WARNING:1] [] [] [ecid: ] [tid: bf868700]  [67004] Configuration value iBots\MinGlobalSleepSecs not set.^M

[2013-07-25T12:38:29.000-05:00] [OracleBISchedulerComponent] [WARNING:1] [] [] [ecid: ] [tid: bf868700]  [67004] Configuration value iBots\MaxGlobalSleepSecs not set.^M

[2013-07-25T12:38:29.000-05:00] [OracleBISchedulerComponent] [WARNING:1] [] [] [ecid: ] [tid: bf868700]  [67004] Configuration value iBots\NumRequestRetries not set.^M

[2013-07-25T12:38:29.000-05:00] [OracleBISchedulerComponent] [WARNING:1] [] [] [ecid: ] [tid: bf868700]  [67004] Configuration value iBots\MinRequestSleepSecs not set.^M

[2013-07-25T12:38:29.000-05:00] [OracleBISchedulerComponent] [WARNING:1] [] [] [ecid: ] [tid: bf868700]  [67004] Configuration value iBots\MaxRequestSleepSecs not set.^M

[2013-07-25T12:38:29.000-05:00] [OracleBISchedulerComponent] [WARNING:1] [] [] [ecid: ] [tid: bf868700]  [67004] Configuration value iBots\NumDeliveryRetries not set.^M

[2013-07-25T12:38:29.000-05:00] [OracleBISchedulerComponent] [WARNING:1] [] [] [ecid: ] [tid: bf868700]  [67004] Configuration value iBots\MinDeliverySleepSecs not set.^M

[2013-07-25T12:38:29.000-05:00] [OracleBISchedulerComponent] [WARNING:1] [] [] [ecid: ] [tid: bf868700]  [67004] Configuration value iBots\MaxDeliverySleepSecs not set.^M

[2013-07-25T12:38:29.000-05:00] [OracleBISchedulerComponent] [WARNING:1] [] [] [ecid: ] [tid: bf868700]  [67004] Configuration value iBots\Debug not set.^M

[2013-07-25T12:38:29.000-05:00] [OracleBISchedulerComponent] [WARNING:1] [] [] [ecid: ] [tid: bf868700]  [67004] Configuration value iBots\KeepErrorLogFiles not set.^M

[2013-07-25T12:38:29.000-05:00] [OracleBISchedulerComponent] [WARNING:1] [] [] [ecid: ] [tid: bf868700]  [67004] Configuration value iBots\LogMailContent not set.^M

[2013-07-25T12:38:29.000-05:00] [OracleBISchedulerComponent] [WARNING:1] [] [] [ecid: ] [tid: bf868700]  [67004] Configuration value iBots\MaxRowsTimesColumns not set.^M

[2013-07-25T12:38:29.000-05:00] [OracleBISchedulerComponent] [WARNING:1] [] [] [ecid: ] [tid: bf868700]  [67004] Configuration value iBots\Generate7BitPlainText not set.^M

[2013-07-25T12:38:29.000-05:00] [OracleBISchedulerComponent] [WARNING:1] [] [] [ecid: ] [tid: bf868700]  [67004] Configuration value iBots\ForceUTF8 not set.^M

[2013-07-25T12:38:29.000-05:00] [OracleBISchedulerComponent] [WARNING:1] [] [] [ecid: ] [tid: bf868700]  [67004] Configuration value Workflow\Server not set.^M

[2013-07-25T12:38:29.000-05:00] [OracleBISchedulerComponent] [WARNING:1] [] [] [ecid: ] [tid: bf868700]  [67004] Configuration value Workflow\System not set.^M

[2013-07-25T12:38:29.000-05:00] [OracleBISchedulerComponent] [WARNING:1] [] [] [ecid: ] [tid: bf868700]  [67004] Configuration value Workflow\Service not set.^M

[2013-07-25T12:38:29.000-05:00] [OracleBISchedulerComponent] [WARNING:1] [] [] [ecid: ] [tid: bf868700]  [67004] Configuration value Mail\SmtpCaCertificateFile not set.^M

[2013-07-25T12:38:29.000-05:00] [OracleBISchedulerComponent] [WARNING:1] [] [] [ecid: ] [tid: bf868700]  [67004] Configuration value Mail\SmtpCaCertificateDirectory not set.^M

[2013-07-25T12:38:29.000-05:00] [OracleBISchedulerComponent] [WARNING:1] [] [] [ecid: ] [tid: bf868700]  [67004] Configuration value Mail\SmtpCipherList not set.^M

[2013-07-25T12:38:29.000-05:00] [OracleBISchedulerComponent] [NOTIFICATION:1] [] [] [ecid: ] [tid: bf868700] Verifying Scheduler's backend database configuration [[^M

^M

]]^M

[2013-07-25T12:38:29.000-05:00] [OracleBISchedulerComponent] [NOTIFICATION:1] [] [] [ecid: 004s__yXgtR5IfK5qVP5iY0002W5000003,0] [tid: 4010d940]  [16020] Metadata Database Type: Oracle 11g [[^M

Data Source Name: (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=xxxxxtdb-scan.xxxxxx.com)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=WLTST)))

Data Source Type: Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64b^M

]]^M

[2013-07-25T12:38:29.000-05:00] [OracleBISchedulerComponent] [ERROR:1] [] [] [ecid: 004s__yXgtR5IfK5qVP5iY0002W5000003,0] [tid: 4010d940]  [nQSError: 46066] Operation cancelled. [[^M

PRIMARY_POOL RetrieveColumnInfo from table S_NQ_JOB Exchange^M

 

Both OBIEE and the metadata schemas (MDS and BIPLATFORM) have been upgraded sucessfully to OBIEE 11.1.1.7.


Since the current BI Scheduler component is not working, we've tried to create a new one using the command:


./opmnctl createcomponent -isRemoteLaunchCommand true -componentName coreapplication_obisch2 -componentType OracleBISchedulerComponent -instanceName OBI_instance1 -biApplicationName coreapplication -appServerAdminPort 9999 -appServerManagedPort 9999 -fmwConfigPath /u01/app/oracle/product/11.1.1/fmw/user_projects/domains/XXXXXXX_BI_domain/config/fmwconfig -autoCreateComponentPort true -portRangeStart 9700 -portRangeEnd 9810 -skipComponentProvisioning true


But it did not work either, so we delete the component:
./opmnctl deletecomponent -isRemoteLaunchCommand true -componentName coreapplication_obisch2 -componentType OracleBISchedulerComponent -instanceName OBI_instance1



Here is the BI Scheduler instanceconfig.xml file:


<?xml version="1.0" encoding="UTF-8" standalone="no"?>

<scheduler>

<ServerInstance>

        <!--This Configuration setting is managed by Oracle Business Intelligence Enterprise Manager--><!--This Configuration setting is managed by Oracle Enterprise Manager Fusion Middleware Control--><CLIType>12</CLIType>

        <!--This Configuration setting is managed by Oracle Business Intelligence Enterprise Manager--><!--This Configuration setting is managed by Oracle Enterprise Manager Fusion Middleware Control--><ClusterPort>9708</ClusterPort>

        <!--This Configuration setting is managed by Oracle Business Intelligence Enterprise Manager--><!--This Configuration setting is managed by Oracle Enterprise Manager Fusion Middleware Control--><DSN>(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=xxxdb-scan.xxxxxx.com)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=WLTST)))</DSN>

       

        <Java_Extension>

            <!--This Configuration setting is managed by Oracle Business Intelligence Enterprise Manager--><!--This Configuration setting is managed by Oracle Enterprise Manager Fusion Middleware Control--><Java_Host_Server>10.50.10.244:9810,10.50.10.245:9810</Java_Host_Server>

        </Java_Extension>

        <Mail>

        <!--

        NOTE:

        Values in this element may be automatically updated from the

        biee-domain.xml file.

        -->

            <!--This Configuration setting is managed by Oracle Business Intelligence Enterprise Manager--><!--This Configuration setting is managed by Oracle Enterprise Manager Fusion Middleware Control--><From>Agilum Business Intelligence</From>

            <!--This Configuration setting is managed by Oracle Business Intelligence Enterprise Manager--><!--This Configuration setting is managed by Oracle Enterprise Manager Fusion Middleware Control--><SMTP_Port>2525</SMTP_Port>

            <!--This Configuration setting is managed by Oracle Business Intelligence Enterprise Manager--><!--This Configuration setting is managed by Oracle Enterprise Manager Fusion Middleware Control--><SMTP_Server>exchange.postoffice.net</SMTP_Server>

            <!--This Configuration setting is managed by Oracle Business Intelligence Enterprise Manager--><!--This Configuration setting is managed by Oracle Enterprise Manager Fusion Middleware Control--><Sender>BI.Admin@xxxxxx.com</Sender>

 

 

        <!--This Configuration setting is managed by Oracle Business Intelligence Enterprise Manager--><!--This Configuration setting is managed by Oracle Enterprise Manager Fusion Middleware Control--><Try>1</Try>

<!--This Configuration setting is managed by Oracle Business Intelligence Enterprise Manager-->

<!--This Configuration setting is managed by Oracle Enterprise Manager Fusion Middleware Control--><MaxRecipients>0</MaxRecipients>

<!--This Configuration setting is managed by Oracle Business Intelligence Enterprise Manager-->

<!--This Configuration setting is managed by Oracle Enterprise Manager Fusion Middleware Control--><UseBcc>true</UseBcc>

<!--This Configuration setting is managed by Oracle Business Intelligence Enterprise Manager-->

<!--This Configuration setting is managed by Oracle Enterprise Manager Fusion Middleware Control--><UseSSL>false</UseSSL>

<!--This Configuration setting is managed by Oracle Business Intelligence Enterprise Manager-->

<!--This Configuration setting is managed by Oracle Enterprise Manager Fusion Middleware Control--><SmtpCaCertificateVerificationDepth>9</SmtpCaCertificateVerificationDepth>

<!--This Configuration setting is managed by Oracle Enterprise Manager Fusion Middleware Control--><UseStartTls>false</UseStartTls>

</Mail>

        <MaxExecThreads>100</MaxExecThreads>

        <MinExecThreads>1</MinExecThreads>

        <!--This Configuration setting is managed by Oracle Business Intelligence Enterprise Manager--><!--This Configuration setting is managed by Oracle Enterprise Manager Fusion Middleware Control--><PartOfCluster>True</PartOfCluster>

        <!--This Configuration setting is managed by Oracle Business Intelligence Enterprise Manager--><!--This Configuration setting is managed by Oracle Enterprise Manager Fusion Middleware Control--><PortString>10.50.10.244:9705</PortString>

       

        <ScriptEngine>

            <!--This Configuration setting is managed by Oracle Business Intelligence Enterprise Manager--><!--This Configuration setting is managed by Oracle Enterprise Manager Fusion Middleware Control--><ScriptRPCPort>9707</ScriptRPCPort>

        </ScriptEngine>

        <!--This Configuration setting is managed by Oracle Business Intelligence Enterprise Manager--><!--This Configuration setting is managed by Oracle Enterprise Manager Fusion Middleware Control--><TargetType>57</TargetType>

       

        <iBots>

            <Log_Dir>/u01/app/oracle/product/11.1.1/fmw/instances/OBI_instance1/diagnostics/logs/OracleBISchedulerComponent/coreapplication_obisch1</Log_Dir>

            <!--This Configuration setting is managed by Oracle Business Intelligence Enterprise Manager--><!--This Configuration setting is managed by Oracle Enterprise Manager Fusion Middleware Control--><Web_Server>10.50.10.244:9710,10.50.10.245:9710</Web_Server>

        </iBots>

       

       

        <Log>

            <Level>

                <!--This Configuration setting is managed by Oracle Business Intelligence Enterprise Manager--><!--This Configuration setting is managed by Oracle Enterprise Manager Fusion Middleware Control--><Error>1</Error>

                <!--This Configuration setting is managed by Oracle Business Intelligence Enterprise Manager--><!--This Configuration setting is managed by Oracle Enterprise Manager Fusion Middleware Control--><IncidentError>1</IncidentError>

                <!--This Configuration setting is managed by Oracle Business Intelligence Enterprise Manager--><!--This Configuration setting is managed by Oracle Enterprise Manager Fusion Middleware Control--><Trace>0</Trace>

                <!--This Configuration setting is managed by Oracle Business Intelligence Enterprise Manager--><!--This Configuration setting is managed by Oracle Enterprise Manager Fusion Middleware Control--><Warning>1</Warning>

                <!--This Configuration setting is managed by Oracle Business Intelligence Enterprise Manager--><!--This Configuration setting is managed by Oracle Enterprise Manager Fusion Middleware Control--><Notification>1</Notification>

            </Level>

            <!--This Configuration setting is managed by Oracle Business Intelligence Enterprise Manager--><!--This Configuration setting is managed by Oracle Enterprise Manager Fusion Middleware Control--><MaximumFileSizeKb>1000</MaximumFileSizeKb>

            <!--This Configuration setting is managed by Oracle Business Intelligence Enterprise Manager--><!--This Configuration setting is managed by Oracle Enterprise Manager Fusion Middleware Control--><MaximumLogAgeDay>10</MaximumLogAgeDay>

        </Log>

       

        <!--This Configuration setting is managed by Oracle Business Intelligence Enterprise Manager--><!--This Configuration setting is managed by Oracle Enterprise Manager Fusion Middleware Control--><FMWServicesURL>http://10.50.10.244:9704</FMWServicesURL>

<DefaultScriptPath>/u01/app/oracle/product/11.1.1/fmw/instances/OBI_instance1/bifoundation/OracleBISchedulerComponent/coreapplication_obisch1/scripts/common</DefaultScriptPath>

      <SchedulerScriptPath>/u01/app/oracle/product/11.1.1/fmw/instances/OBI_instance1/bifoundation/OracleBISchedulerComponent/coreapplication_obisch1/scripts/scheduler</SchedulerScriptPath>

      <TempPath>/u01/app/oracle/product/11.1.1/fmw/instances/OBI_instance1/tmp/OracleBISchedulerComponent/coreapplication_obisch1</TempPath>

      <SSL>

         <CACertificateDir>/u01/app/oracle/product/11.1.1/fmw/instances/OBI_instance1/config/OracleBISchedulerComponent/coreapplication_obisch1</CACertificateDir>

         <CertPrivateKeyFileName>/u01/app/oracle/product/11.1.1/fmw/instances/OBI_instance1/config/OracleBISchedulerComponent/coreapplication_obisch1/private.pem</CertPrivateKeyFileName>

         <CertificateFileName>/u01/app/oracle/product/11.1.1/fmw/instances/OBI_instance1/config/OracleBISchedulerComponent/coreapplication_obisch1/public.pem</CertificateFileName>

         <PassphraseFileName>/u01/app/oracle/product/11.1.1/fmw/instances/OBI_instance1/config/OracleBISchedulerComponent/coreapplication_obisch1/passphrase</PassphraseFileName>

      <!--This Configuration setting is managed by Oracle Business Intelligence Enterprise Manager--><!--This Configuration setting is managed by Oracle Enterprise Manager Fusion Middleware Control--><UseSSL>false</UseSSL>

</SSL>

      <!--This Configuration setting is managed by Oracle Business Intelligence Enterprise Manager--><!--This Configuration setting is managed by Oracle Enterprise Manager Fusion Middleware Control--><OC4JActionExecutionPort>http://10.50.10.244:9704/analytics/actions/ActionExecutionService</OC4JActionExecutionPort>

   </ServerInstance>

</scheduler>


We are now in the OBIEE 11.1.1.7.1 release and it still not working as the previous OBIEE 11.1.1.7.


Someone have any idea on what's happening?


Rgds,


Danilo

  • 1. Re: After upgrading to OBIEE 11.1.1.7 BI Scheduler component does not start
    SunilSharma Expert
    Currently Being Moderated

    Did you try from the backup you have for this instanceconfig.xml file?

  • 2. Re: After upgrading to OBIEE 11.1.1.7 BI Scheduler component does not start
    D.Mozeli Newbie
    Currently Being Moderated

    I've compared both files (old and new) and found there are differences related to the upgrade from 11.1.1.5 to 11.1.1.7 (new parameters). It does not seem to have any parameter setup wrongly on the new instanceconfig.xml. Also, We have setup the Fusion Middleware Deploy > Scheduler and it's using a valid and unlocked BIPLATFORM schema.

  • 3. Re: After upgrading to OBIEE 11.1.1.7 BI Scheduler component does not start
    SunilSharma Expert
    Currently Being Moderated

    can you try starting the individual component and see how it goes

  • 4. Re: After upgrading to OBIEE 11.1.1.7 BI Scheduler component does not start
    Sasi Nagireddy Expert
    Currently Being Moderated

    Can u check dev_biplatform schema status in DB,Sometimes it may be the problem for scheduler service to start.

     

    SELECT USENAME,CREATED FROM DBA_USERS WHERE USERNAME LIKE '%PLATFORM%';

  • 5. Re: After upgrading to OBIEE 11.1.1.7 BI Scheduler component does not start
    D.Mozeli Newbie
    Currently Being Moderated

    I've tried to start individual components and it did not work either. I noticed the opmnctl is taking a long time to start the BI Scheduler and it's probably raising a timeout issue. Can you let me know where I can increase the timeout parameter to 10 or 15 minutes?

     

    Thanks.

  • 6. Re: After upgrading to OBIEE 11.1.1.7 BI Scheduler component does not start
    D.Mozeli Newbie
    Currently Being Moderated

    I've run the command and here are the results:

     

    SELECT USERNAME,CREATED,ACCOUNT_STATUS FROM DBA_USERS WHERE USERNAME LIKE '%PLATFORM%';

     

    USERNAME                       CREATED                   ACCOUNT_STATUS                  

    ------------------------------ ------------------------- --------------------------------

    TST_BIPLATFORM                 23-DEC-12                 OPEN                            

  • 7. Re: After upgrading to OBIEE 11.1.1.7 BI Scheduler component does not start
    D.Mozeli Newbie
    Currently Being Moderated

    We've tried to start the opmn BI Scheduler ias-component using a 200 sec timeout. After, 33 minutes we received the error:

     

    [oracle@agtbiapp02 bin]$ ./opmnctl startproc ias-component=coreapplication_obisch1 timeout=2000

    opmnctl startproc: starting opmn managed processes...

     

     

    ================================================================================

    opmn id=agtbiapp02.agilum.com:9501

    Response: 0 of 1 processes started.

     

     

    ias-instance id=OBI_instance2

    ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

    --------------------------------------------------------------------------------

    ias-component/process-type/process-set:

      coreapplication_obisch1/OracleBISchedulerComponent/coreapplication_obisch1/

     

     

    Error

    --> Process (index=1,uid=600657675,pid=26969)

      time out while waiting for a managed process to start

      Log:

      /u01/app/oracle/product/11.1.1/fmw/instances/OBI_instance1/diagnostics/logs/OracleBISchedulerComponent/coreapplication_obisch1/console~coreapplication_obisch1~1.log

     

    And the bi scheduler shows "Stop" status:

     

    [oracle@agtbiapp02 OBI_instance1]$ ./bin/opmnctl status

     

     

    Processes in Instance: OBI_instance2

    ---------------------------------+--------------------+---------+---------

    ias-component                    | process-type       |     pid | status

    ---------------------------------+--------------------+---------+---------

    coreapplication_obisch1          | OracleBIScheduler~ |   26969 | Stop

    coreapplication_obiccs1          | OracleBIClusterCo~ |   21160 | Alive

    coreapplication_obips1           | OracleBIPresentat~ |   21157 | Alive

    coreapplication_obijh1           | OracleBIJavaHostC~ |   21159 | Alive

    coreapplication_obis1            | OracleBIServerCom~ |   21156 | Alive

  • 8. Re: After upgrading to OBIEE 11.1.1.7 BI Scheduler component does not start
    SunilSharma Expert
    Currently Being Moderated

    Does it start on primary machine? compare the files with primary machine related to config changes. looks like some issue with config files

  • 9. Re: After upgrading to OBIEE 11.1.1.7 BI Scheduler component does not start
    D.Mozeli Newbie
    Currently Being Moderated

    I've run a comparison and both files are the identical, except for the hostnames and ips.

     

    I run the startproc on BI Scheduler again and the BI Scheduler on the primary machine started but  I can't explain why it did not start previously. See below:

     

    [oracle@agtbiapp01 bin]$ ./opmnctl status

     

    Processes in Instance: OBI_instance1

    ---------------------------------+--------------------+---------+---------

    ias-component                    | process-type       |     pid | status

    ---------------------------------+--------------------+---------+---------

    coreapplication_obiccs1          | OracleBIClusterCo~ |   10914 | Alive

    coreapplication_obisch1          | OracleBIScheduler~ |   10915 | Alive

    coreapplication_obijh1           | OracleBIJavaHostC~ |   10913 | Alive

    coreapplication_obips1           | OracleBIPresentat~ |   10911 | Alive

    coreapplication_obis1            | OracleBIServerCom~ |   10912 | Alive

     

     

     

    Just to make sure it would start again. I stopped the service:

     

    [oracle@agtbiapp01 bin]$ ./opmnctl stopproc ias-component=coreapplication_obisch1

    opmnctl stopproc: stopping opmn managed processes...

     

    And tried to start it again:

     

    [oracle@agtbiapp01 bin]$ ./opmnctl startproc ias-component=coreapplication_obisch1

    opmnctl startproc: starting opmn managed processes...

    ================================================================================

    opmn id=agtbiapp01.xxxxxxxx.com:9501

    Response: 0 of 1 processes started.

     

     

    ias-instance id=OBI_instance1

    ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

    --------------------------------------------------------------------------------

    ias-component/process-type/process-set:

      coreapplication_obisch1/OracleBISchedulerComponent/coreapplication_obisch1/

     

     

    Error

    --> Process (index=1,uid=896171300,pid=15270)

      time out while waiting for a managed process to start

      Log:

      /u01/app/oracle/product/11.1.1/fmw/instances/OBI_instance1/diagnostics/logs/OracleBISchedulerComponent/coreapplication_obisch1/console~coreapplication_obisch1~1.log

     

     

    [oracle@agtbiapp01 bin]$

     

    It took a long time on "Init" status and raised the opmn timeout issue again. So, it was not started.


    Here is the result of the nqscheduler.log on Node1. As you can see, it could start once but could not start it again.


    [2013-07-25T13:09:42.000-05:00] [OracleBISchedulerComponent] [NOTIFICATION:1] [] [] [ecid: 004s_biBpbT5IfK5qVP5iY0002eZ000002,0] [tid: 410df940]  [16020] Metadata Database Type: Oracle 11g [[^M

    Data Source Name: (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=agtdb-scan.xxxxxx.com)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=WLTST)))

    Data Source Type: Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64b^M

    ]]^M

    [2013-07-25T13:09:44.000-05:00] [OracleBISchedulerComponent] [NOTIFICATION:1] [] [] [ecid: ] [tid: dc065700]  [68013] Scheduler service started.^M

    [2013-07-25T13:09:44.000-05:00] [OracleBISchedulerComponent] [NOTIFICATION:1] [] [] [ecid: ] [tid: dc065700]  [68030] Scheduler subsystem started: Job scheduler.^M

    [2013-07-25T13:09:44.000-05:00] [OracleBISchedulerComponent] [NOTIFICATION:1] [] [] [ecid: ] [tid: dc065700]  [71076] Oracle BI Scheduler agtbiapp01:9705 has been changed to an Inactive state.^M

    [2013-07-25T13:09:47.000-05:00] [OracleBISchedulerComponent] [NOTIFICATION:1] [] [] [ecid: 004s_biSkCl5IfK5qVP5iY0002eZ00000H,0] [tid: 41320940]  [43071] A connection with Cluster Controller agtbiapp01.xxxxx.com:9706 was established.^M

    [2013-07-25T13:09:47.000-05:00] [OracleBISchedulerComponent] [NOTIFICATION:1] [] [] [ecid: 004s_biSkCl5IfK5qVP5iY0002eZ00000H,0] [tid: 41320940]  [71075] Oracle BI Scheduler agtbiapp01:9705 has been changed to an Active state.^M

    [2013-07-25T14:58:19.000-05:00] [OracleBISchedulerComponent] [NOTIFICATION:1] [] [] [ecid: ] [tid: dc065700]  [68025] Scheduler subsystem stopped: NQCmd engine.^M

    [2013-07-25T14:58:19.000-05:00] [OracleBISchedulerComponent] [NOTIFICATION:1] [] [] [ecid: ] [tid: dc065700]  [68027] Scheduler subsystem stopped: Agent chain engine.^M

    [2013-07-25T14:58:19.000-05:00] [OracleBISchedulerComponent] [NOTIFICATION:1] [] [] [ecid: ] [tid: dc065700]  [68028] Scheduler subsystem stopped: Java engine.^M

    [2013-07-25T14:58:21.000-05:00] [OracleBISchedulerComponent] [NOTIFICATION:1] [] [] [ecid: ] [tid: dc065700]  [68029] Scheduler subsystem stopped: Scripting engine.^M

    [2013-07-25T14:58:21.000-05:00] [OracleBISchedulerComponent] [NOTIFICATION:1] [] [] [ecid: ] [tid: dc065700]  [68026] Scheduler subsystem stopped: Job engine.^M

    [2013-07-25T14:58:21.000-05:00] [OracleBISchedulerComponent] [NOTIFICATION:1] [] [] [ecid: ] [tid: dc065700]  [68024] Scheduler subsystem stopped: Purge.^M

    [2013-07-25T14:58:21.000-05:00] [OracleBISchedulerComponent] [NOTIFICATION:1] [] [] [ecid: ] [tid: dc065700]  [68023] Scheduler subsystem stopped: Job scheduler.^M

    [2013-07-25T14:58:22.000-05:00] [OracleBISchedulerComponent] [NOTIFICATION:1] [] [] [ecid: 004s_biSkCl5IfK5qVP5iY0002eZ00000H,0] [tid: 41320940]  [71075] Oracle BI Scheduler agtbiapp01:9705 has been changed to an Active state.^M

    [2013-07-25T14:58:22.000-05:00] [OracleBISchedulerComponent] [ERROR:1] [] [] [ecid: 004s_biGniG5IfK5qVP5iY0002eZ00000G,0] [tid: 411e0940]  [nQSError: 46066] Operation cancelled.^M

    [2013-07-25T14:58:22.000-05:00] [OracleBISchedulerComponent] [ERROR:1] [] [] [ecid: 004s_biSkCl5IfK5qVP5iY0002eZ00000H,0] [tid: 41320940]  [nQSError: 46066] Operation cancelled.^M

    [2013-07-25T14:58:24.000-05:00] [OracleBISchedulerComponent] [NOTIFICATION:1] [] [] [ecid: ] [tid: dc065700]  [68015] Scheduler service stopped.^M

    [2013-07-25T14:58:38.000-05:00] [OracleBISchedulerComponent] [WARNING:1] [] [] [ecid: ] [tid: f74d4700]  [67004] Configuration value iBots\NumGlobalRetries not set.^M

    [2013-07-25T14:58:38.000-05:00] [OracleBISchedulerComponent] [WARNING:1] [] [] [ecid: ] [tid: f74d4700]  [67004] Configuration value iBots\MinGlobalSleepSecs not set.^M

    [2013-07-25T14:58:38.000-05:00] [OracleBISchedulerComponent] [WARNING:1] [] [] [ecid: ] [tid: f74d4700]  [67004] Configuration value iBots\MaxGlobalSleepSecs not set.^M

    [2013-07-25T14:58:38.000-05:00] [OracleBISchedulerComponent] [WARNING:1] [] [] [ecid: ] [tid: f74d4700]  [67004] Configuration value iBots\NumRequestRetries not set.^M

    [2013-07-25T14:58:38.000-05:00] [OracleBISchedulerComponent] [WARNING:1] [] [] [ecid: ] [tid: f74d4700]  [67004] Configuration value iBots\MinRequestSleepSecs not set.^M

    [2013-07-25T14:58:38.000-05:00] [OracleBISchedulerComponent] [WARNING:1] [] [] [ecid: ] [tid: f74d4700]  [67004] Configuration value iBots\MaxRequestSleepSecs not set.^M

    [2013-07-25T14:58:38.000-05:00] [OracleBISchedulerComponent] [WARNING:1] [] [] [ecid: ] [tid: f74d4700]  [67004] Configuration value iBots\NumDeliveryRetries not set.^M

    [2013-07-25T14:58:38.000-05:00] [OracleBISchedulerComponent] [WARNING:1] [] [] [ecid: ] [tid: f74d4700]  [67004] Configuration value iBots\MinDeliverySleepSecs not set.^M

    [2013-07-25T14:58:38.000-05:00] [OracleBISchedulerComponent] [WARNING:1] [] [] [ecid: ] [tid: f74d4700]  [67004] Configuration value iBots\MaxDeliverySleepSecs not set.^M

    [2013-07-25T14:58:38.000-05:00] [OracleBISchedulerComponent] [WARNING:1] [] [] [ecid: ] [tid: f74d4700]  [67004] Configuration value iBots\Debug not set.^M

    [2013-07-25T14:58:38.000-05:00] [OracleBISchedulerComponent] [WARNING:1] [] [] [ecid: ] [tid: f74d4700]  [67004] Configuration value iBots\KeepErrorLogFiles not set.^M

    [2013-07-25T14:58:38.000-05:00] [OracleBISchedulerComponent] [WARNING:1] [] [] [ecid: ] [tid: f74d4700]  [67004] Configuration value iBots\LogMailContent not set.^M

    [2013-07-25T14:58:38.000-05:00] [OracleBISchedulerComponent] [WARNING:1] [] [] [ecid: ] [tid: f74d4700]  [67004] Configuration value iBots\MaxRowsTimesColumns not set.^M

    [2013-07-25T14:58:38.000-05:00] [OracleBISchedulerComponent] [WARNING:1] [] [] [ecid: ] [tid: f74d4700]  [67004] Configuration value iBots\Generate7BitPlainText not set.^M

    [2013-07-25T14:58:38.000-05:00] [OracleBISchedulerComponent] [WARNING:1] [] [] [ecid: ] [tid: f74d4700]  [67004] Configuration value iBots\ForceUTF8 not set.^M

    [2013-07-25T14:58:38.000-05:00] [OracleBISchedulerComponent] [WARNING:1] [] [] [ecid: ] [tid: f74d4700]  [67004] Configuration value Workflow\Server not set.^M

    [2013-07-25T14:58:38.000-05:00] [OracleBISchedulerComponent] [WARNING:1] [] [] [ecid: ] [tid: f74d4700]  [67004] Configuration value Workflow\System not set.^M

    [2013-07-25T14:58:38.000-05:00] [OracleBISchedulerComponent] [WARNING:1] [] [] [ecid: ] [tid: f74d4700]  [67004] Configuration value Workflow\Service not set.^M

    [2013-07-25T14:58:38.000-05:00] [OracleBISchedulerComponent] [WARNING:1] [] [] [ecid: ] [tid: f74d4700]  [67004] Configuration value Mail\SmtpCaCertificateFile not set.^M

    [2013-07-25T14:58:38.000-05:00] [OracleBISchedulerComponent] [WARNING:1] [] [] [ecid: ] [tid: f74d4700]  [67004] Configuration value Mail\SmtpCaCertificateDirectory not set.^M

    [2013-07-25T14:58:38.000-05:00] [OracleBISchedulerComponent] [WARNING:1] [] [] [ecid: ] [tid: f74d4700]  [67004] Configuration value Mail\SmtpCipherList not set.^M

    [2013-07-25T14:58:38.000-05:00] [OracleBISchedulerComponent] [NOTIFICATION:1] [] [] [ecid: ] [tid: f74d4700] Verifying Scheduler's backend database configuration [[^M

    ^M

    ]]^M

    [2013-07-25T14:58:38.000-05:00] [OracleBISchedulerComponent] [NOTIFICATION:1] [] [] [ecid: 004s_hnjnMN5IfK5qVP5iY0003ia000003,0] [tid: 41bce940]  [16020] Metadata Database Type: Oracle 11g [[^M

    Data Source Name: (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=agtdb-scan.xxxxxx.com)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=WLTST)))

    Data Source Type: Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64b^M

    ]]^M

     

     

    Any help?


    Thanks,


    Danilo


    For some reason, opmn was able to start the BI Scheduler only on Node1 once but it's unable to do it again or to start on Node2.


    Right now, both BI Schedulers are stopped and I can't start them.



  • 10. Re: After upgrading to OBIEE 11.1.1.7 BI Scheduler component does not start
    SunilSharma Expert
    Currently Being Moderated

    looks like some ^M characters  are there. try restarting the scheduler from EM or else try restarting all services from command line including admin and managed server and then opmnctl

  • 11. Re: After upgrading to OBIEE 11.1.1.7 BI Scheduler component does not start
    D.Mozeli Newbie
    Currently Being Moderated

    Hi,

     

    The ^M character is just a line break on log files, it does not seem to be related to the problem. I've tried to restart all services from the command line (including admin and managed server) and after that the opmn but they did not work.

     

    Something is wrong with the configuration files or the internal bi authentication that is preventing the BI Scheduler to start.

     

    Do you have any idea?

     

    Thanks

  • 12. Re: After upgrading to OBIEE 11.1.1.7 BI Scheduler component does not start
    SunilSharma Expert
    Currently Being Moderated

    ya looks like the problem with config files, try to apply the patch 11.1.1.7.1 and start the services it should start all of them without any issues as it will fix them.

     

    mark if it helps

  • 13. Re: After upgrading to OBIEE 11.1.1.7 BI Scheduler component does not start
    D.Mozeli Newbie
    Currently Being Moderated

    Yes, I've applied the OBIEE 11.1.1.7.1 patch last week and it did not work either. Is there anything else I can do to troubleshoot it? Is there a trace log or something we can enable to capture all the events that are happening during the opmn start.

  • 14. Re: After upgrading to OBIEE 11.1.1.7 BI Scheduler component does not start
    SunilSharma Expert
    Currently Being Moderated

    yes log in to EM and click on core application ->diagnostics ->log configuration ->change the scheudler log level to highest and then restrat the services and see what it has to say.

1 2 Previous Next

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points