Unable to connect to the OWB Control Center

May 3rd, 2007 by Jon Mead

I am currently doing some OWB 10gR2 training in Iceland, some of the examples I am using are on a Virtual Machine running on my laptop, halfway through the day I tried to connect to the Control Center and I got the following error:

RTC-5260: Failed to connect to Control Center, Please check you have provided the correct Host, user, password and Service Name.
RTC-5301: The Control Center Service is not currently available

This is not the first time I have seen this in my time of using OWB, so I thought I would connect to the database as the repository owner and check the service doctor.

SQL> @service_doctor
>>>>>> There are errors in one or more PL/SQL packages and functions
Platform properties have been loaded correctly
Platform location has been seeded correctly
NLS messages have been loaded correctly
>>>>>> The platform service is not available
Service script is accessible to the database server
Connection information stored within the repository is correct

The next step was to check which packages were invalid.

select OBJECT_NAME, OBJECT_TYPE from ALL_OBJECTS where status='INVALID' and owner='OWBREP';

OBJECT_NAME                   
OBJECT_TYPE
—————————— ——————-
SNAPSHOT                       PACKAGE BODY
WB_RTI_WORKFLOW_UTIL           PACKAGE BODY
OWB_UPROP_TUNE                
PACKAGE BODY

alter package SNAPSHOT compile;
alter package SNAPSHOT compile body;

alter package WB_RTI_WORKFLOW_UTIL compile;
alter package WB_RTI_WORKFLOW_UTIL compile body;

alter package OWB_UPROP_TUNE compile;
alter package OWB_UPROP_TUNE compile body;

SQL> select OBJECT_NAME, OBJECT_TYPE from ALL_OBJECTS where
status=’INVALID’ and owner=’OWBREP’;

More packages and package bodies were invalid after this so I thought I would recompile the whole schema.

EXEC DBMS_UTILITY.compile_schema(schema => 'OWBREP');

SQL> select OBJECT_NAME, OBJECT_TYPE from ALL_OBJECTS where status=’INVALID’ and owner=’OWBREP’;

no rows selected

SQL> @service_doctor
All PL/SQL packages and functions are valid
Platform properties have been loaded correctly
Platform location has been seeded correctly
NLS messages have been loaded correctly
>>>>>> The platform service is not available
Service script is accessible to the database server
>>>>>> There is a problem with the repository connection information used to
start the service
>>>>>>   Here is the detailed error message which contains the connection
information passed to the service:-
>>>>>>     Cannot access the repository owner password from within the database
server
>>>>>>   Please verify that this information is accurate
>>>>>>   If this information is correct, then please use the
’set_repository_password.sql’ script to reset the stored password

PL/SQL procedure successfully completed.

SQL> @set_repository_password.sql
Enter value for 1: owbrep
declare
*
ERROR at line 1:
ORA-29532: Java call terminated by uncaught Java exception:
oracle.jdbc.driver.OracleSQLException: ORA-04061: existing state of  has been
invalidated
ORA-04061: existing state of package “OWBREP.WB_RT_SERVICE_CONTROL” has
been
invalidated
ORA-04065: not executed, altered or dropped package
“OWBREP.WB_RT_SERVICE_CONTROL”
ORA-06508: PL/SQL: could not find program unit being called:
“OWBREP.WB_RT_SERVICE_CONTROL”
ORA-06512: at line 1
ORA-06512: at “OWBREP.WB_RTI_UTIL”, line 40
ORA-06512: at line 5

This type of error is usually caused by packages being in inconsistent states, so it looked like it was time to restart the database.
 After the restart things looked better.

SQL> select OBJECT_NAME, OBJECT_TYPE from ALL_OBJECTS where status=’INVALID’ and owner=’OWBREP’;
no rows selected

SQL> @service_doctor
All PL/SQL packages and functions are valid
Platform properties have been loaded correctly
Platform location has been seeded correctly
NLS messages have been loaded correctly
>>>>>> The platform service is not available
Service script is accessible to the database server
Connection information stored within the repository is correct

SQL> @start_service
Not available
Diagnostics:
service startup failure using command “/opt/oracle/product/OWB10.2.0.1/owb/bin/
unix/run_service.sh -automatic 1 /opt/oracle/product/OWB10.2.0.1 OWBREP TIGNES.
RITTMANMEAD.COM 1521 ORCL.RITTMANMEAD.COM” reason ORA-29532: Java call terminat
ed by uncaught Java exception: java.io.IOException: service startup timeout: er
r= : out=2007/05/03-03:12:39-BST [2BB514] Thin driver connection time - 708 mil
lisecond(s)

OK, things may have looked better, but still not able to start the service.  Next step, check this is not a result of the
ORACLE_HOME being set to the database home, not the OWB home.

[oracle@tignes sql]$ echo $ORACLE_HOME
/opt/oracle/product/10.2.0.1.0
[oracle@tignes sql]$ export ORACLE_HOME=/opt/oracle/product/OWB10.2.0.1/
[oracle@tignes sql]$ echo $ORACLE_HOME
/opt/oracle/product/OWB10.2.0.1/

[oracle@tignes sql]$ sqlplus owbrep/owbrep@orcl

SQL> @service_doctor
All PL/SQL packages and functions are valid
Platform properties have been loaded correctly
Platform location has been seeded correctly
NLS messages have been loaded correctly
>>>>>> The platform service is not available
Service script is accessible to the database server
Connection information stored within the repository is correct

I checked the log files to see if there were any clues there, but nothing, so gave it another go….

SQL> @start_service
Not available
Diagnostics:
service startup failure using command “/opt/oracle/product/OWB10.2.0.1/owb/bin/
unix/run_service.sh -manual 1 /opt/oracle/product/OWB10.2.0.1 OWBREP TIGNES.RIT
TMANMEAD.COM 1521 ORCL.RITTMANMEAD.COM” reason ORA-29532: Java call terminated
by uncaught Java exception: java.io.IOException: service startup timeout: err=
: out=2007/05/03-03:14:23-BST [2BB514] Thin driver connection time - 635 millis
econd(s)

… still no joy, try and execute it from the command line:

/opt/oracle/product/OWB10.2.0.1/owb/bin/unix/run_service.sh
-manual 1 /opt/oracle/product/OWB10.2.0.1 OWBREP TIGNES.RITTMANMEAD.COM
1521 ORCL.RITTMANMEAD.COM

Returned to command prompt, so I re-tried the service doctor and got the same error message.

By this point I was getting fairly frustrated, and trying even more obscure searches on Google, then something struck me, Google searches were being returned in Icelandic, it was redirecting me to www.google.is, could my problem be related to this? Could I have some sort of character set or internationization problem?  The Virtual Machine was running is shared network mode.  I shut down the database, and then the Virtual Machine, pulled out the network cable and re-started everything.

Initially the service doctor reported the service as down, but when I executed @start_service it started immediately. nbsp;Success.
 Can’t say that I can understand why - if anyone can shed any light on this I would be very grateful.  I have added a few more useful diagnostic queries below.

Check the service name:

select service_name from WB_RT_SERVICE_NODES;

Check current jobs:

select job, what from USER_JOBS;

Get command to start service:

select * from WB_RT_SERVICE_JOB_LOGS;

Posted in Oracle Warehouse Builder |

Comments

  1. David Says:

    May 15th, 2007 at 6:42 pm

    Was there any information in the OWB runtime log (under owb/log in OWB ORACLE home), may be a timezone not found… did the timezone automatically change or something odd when plugged into network?

    There are some problems with certain timezones (and db versions) that cause the runtime to fail startup. It can be resolved by editing the run_service to set the timezone using numeric rather than tokens taken from the environment.

  2. Jon Mead Says:

    May 16th, 2007 at 9:47 pm

    The only output in the log files was:

    2007/05/03-03:38:15-BST [2BB514] Error creating the temp directory /opt/oracle/product/OWB10.2.0.1/owb/temp

    This was repeated quite a few times. This directory existed and I tried changing the permissions etc, but still got the log error message, wasn’t sure if it was a red herring.

    Didn’t think about the timezone (I will have a go next time I am there), however I didn’t have Icelandic installed as a runtime repository language, so wondered if that would have had something to do with it - again if something got automatically by plugging into the network.

  3. Sourabh Says:

    May 17th, 2007 at 8:39 am

    Hi,

    I was getting the following error

    service startup failure using command “/data3/u01/app/oracle/product/owb10g/owb
    /bin/unix/run_service.sh -manual 1 /data3/u01/app/oracle/product/owb10g OWB_RT
    172.16.227.225 1521 ERSSP7AT” reason ORA-29532: Java call terminated by uncaugh
    t Java exception: java.io.IOException: service early exit: code=255 : err= : ou
    t=2007/05/17-11:45:32-IST [D2906A] Thin driver connection time - 496 millisecon
    d(s)
    2007/05/17-11:45:32-IST [D2906A] Connection Manager - property user.timezo
    ne value is Asia/Calcutta
    2007/05/17-11:45:32-IST [D2906A] Connection Manager -
    connection.timezone not set. Defaulting to value SERVICE
    2007/05/17-11:45:32-I
    ST [D2906A] Connection Manager - using service timezone Asia/Calcutta
    200

    On the same server i had 2 databases . One of the database had repository on 10.2.0.2 and other had its repository on 10.2.0.1.
    I was using the same oracle software binaries for both the database.So finally i uplifted the repository on 10.2.0.1 to 10.2.0.2 and eveything is working fine now

    Regards

  4. ravi Says:

    May 24th, 2007 at 7:51 am

    Ok finally found what’s happening. Enabled sqlnet trace and found owb runtime service was trying to connect to (host=please_ignore) Oracle Tech support confirmed it’s bug and work around it to add alias in /etc/hosts please_ignore
    Now my etc/hosts looks like this

    192.158.56.10 myserver.myco.com myserver please_ignore

    and runtime service starts immediately.
    Hope this will help.

  5. Jon Mead Says:

    May 25th, 2007 at 11:01 pm

    Thanks Ravi, useful to know,

    Jon

  6. Prabhu Kasinathan Says:

    October 12th, 2007 at 10:34 am

    Hi All,

    Me too got the same error. i had done the following procedure and activated the control service platform.

    For your information, please find the following procedure to up the control service platform.

    Error:
    RTC – 5301: The control service is not currently available.

    Solution:

    1. Go to the path, where your OWB 10g R2 installed and open the below batch file in notepad or textpad.

    \owb\bin\win32\run_service.bat

    2. In that text file, please change the below line

    Original Script:
    %JAVAPATH%\jre\bin\javaw.exe %JVM_OPTIONS% -DORACLE_HOME=”%RTHOME%” -DOCM_HOME=”%RTHOME%” -DOCM_ORACLE_HOME=”%RTHOME%” -classpath %RTHOME%\owb\bin\admin\;%RTHOME%\owb\bin\admin\launcher.jar -DOWB_HOME=%OWB_HOME% -DJDK_HOME=%JDK_HOME% -DORA_HOME=%ORA_HOME% -DOEM_HOME=%OEM_HOME% -DIAS_HOME=%IAS_HOME% Launcher %RTHOME%\owb\bin\admin\owb.classpath oracle.wh.runtime.platform.service.Service %STARTUP_TYPE% %NODEID% %RTUSER% %HOST% %PORT% %SERVICE%

    Add this text -Duser.timezone=”+02:00″ as shown below:

    %JAVAPATH%\jre\bin\javaw.exe %JVM_OPTIONS% -DORACLE_HOME=”%RTHOME%” -Duser.timezone=”+02:00″ -DOCM_HOME=”%RTHOME%” -DOCM_ORACLE_HOME=”%RTHOME%” -classpath %RTHOME%\owb\bin\admin\;%RTHOME%\owb\bin\admin\launcher.jar -DOWB_HOME=%OWB_HOME% -DJDK_HOME=%JDK_HOME% -DORA_HOME=%ORA_HOME% -DOEM_HOME=%OEM_HOME% -DIAS_HOME=%IAS_HOME% Launcher %RTHOME%\owb\bin\admin\owb.classpath oracle.wh.runtime.platform.service.Service %STARTUP_TYPE% %NODEID% %RTUSER% %HOST% %PORT% %SERVICE%

    (In the above line, please mention space, double quotes and other things carefully)

    3. Save the file run_service.bat.
    4. Open the sqlplus and login using OWB repository OWNER name and password (not user name / password).
    5. Then, execute the below scripts

    SQL> @\owb\rtp\sql\stop_service.sql

    SQL> @\owb\rtp\sql\start_service.sql

    Now, you successfully enabled the control service platform.

    Now, go to OWB and deploy the objects.

    Thanks,
    Prabhu Kasinathan.
    Cognizant.

  7. V Foster Says:

    December 18th, 2007 at 6:31 pm

    This is what worked for me:
    (1) bounced my repository database :DEVOWB
    (2) updated the wb_rt_nodes_services host column from an IP to the fully qualified name

    THEN the control center service started. My env is 11g OWB client connected to a 10g database repository, target in on 9.2.0.8

  8. Benni Says:

    January 15th, 2008 at 2:40 pm

    Hi Mark. Being Icelandic I suspect that this relates to a known bug only affecting Icelanders (it has nothing to do with booze). The domain suffix .is has caused us innumerable problems through time and this keeps popping up again and again with i.e. db links and gloabl name etc. Oracle has fixed this a number of times but it keeps creeping back in. Since this “is” is a reserved word it simply causes incomprehensible errors from time to time in various circumstances. You may never refer to .is, but perhaps somewhere a name is resolved in such a way that .is gets in the way. This might explain why pulling the network cable fixed the issue. Just a thought.

    Benni

  9. appi Says:

    February 20th, 2008 at 9:40 am

    Hi all,
    on our side the change of the value “localhost” to the fully qualified hostname in table WB_RT_SERVICE_NODES.
    After this change the service starts withou the “Uncaught Java Exception”
    regards
    Uwe

  10. Joshna Says:

    March 1st, 2008 at 10:57 am

    I’m facing same problem. My DBA suggested me to start the control center manually from start->programs->owb->admnistration->start control center…This is working fine normally.But, when I schedule jobs, they are not running fine. As soon as I shut down the client it is control center is losing connection with the repository and not able to execute the jobs at scheduled time, Now, when I start the control center manually, it is saying as scheduled job aborted…Help me ..How to resolve…