Platform service is unavailable

Question

Hello -
I am running OWB 10.2.0.1 on a Linux x86-64 platform and am unable to start the control center service. After ensuring the ORACLE_HOME is set correctly, as well as the ORACLE_SID, I go to the following directory:
cd $ORACLE_HOME/owb/bin/unixI then run the local_service_login.sh file via the following command:
./local_service_login.sh -startup $ORACLE_HOMEThe correct login screen pops up and I am able to enter in my credentials (the repository owner credentials). After hitting enter, it acts just as I think it should but when I attempt to enter the Control Center Manager from the Design Center, it pops up the error RTC-5301stating the Control Center Service is not currently available.
I have tried all sort of combinations of logging out of the Design Center and logging back in/starting up and stopping the control center service but the same error continues to plague me.
After peforming a little bit of research, I discovered that you could also start up the control center service via the start_service.sql file in the $ORACLE_HOME/owb/rtp/sql directory. So, I logged on as the repository owner, executed the start_service.sql file and received the following message:
Not available
Diagnostics:
service startup failure using command "/owb/bin/unix/run_service.sh -manual 1
OWB_REP_OWNER 192.168.0.7 1521 OWB" reason ORA-29532: Java call terminated by u
ncaught Java exception: java.io.IOException: can't exec: /owb/bin/unix/run_serv
ice.sh doesn't exist
I then ran the show_service.sql file and received the following message:
Not available
I then ran the service_doctor.sql file and received the following message:
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
There is a problem accessing the service startup script from the database server
Here is the detailed error message which contains the name of the start script file:-
Service startup file 'null/owb/bin/unix/run_service.sh' is not accessible from the database server on instance number 1
Please verify that the disk containing the file is visible to the database server
Please verify that the database server account has access rights on the fileConnection information stored within the repository is correct
I found it a little curious that the ORACLE_HOME was null in the above message, seeing as I have double checked millions of times via the 'env' command in Linux and verified that ORACLE_HOME is in fact populated correctly (perhaps this is not how ORACLE retrieves the ORACLE_HOME, however. In which case, how does ORACLE retrieve the ORACLE_HOME?). I have attempted to review the PL/SQL that OWB generates and uses in the start_service.sql file, but could not read it because the code is 'wrapped'.
Is this a bug that anyone else has dealt with, or am I just overlooking something. I have read other posts about this topic for previous releases and did not find a solution that has yet worked. Any help would be awesome,
Mark
P.S. I should also mention that I am running everything OWB related through a VNC client (because my machine is a Windows machine while my client has OWB loaded on a Linux machine). When I start the control center service from my Windows machine for my client's OWB instance, the control center service does become available and everything is hunky-dory. However, this will not be a great solution once I pass the knowledge on to them and they start running everything from that Linux box via a VNC client as well (their repository is not located on the same network that their developers currently develop on, and since OWB is very chatty, this is the solution we have chosen to implement).

Answer 1

As you stated in your first post, it is really odd having NULL in the error message:
Service startup file 'null/owb/bin/unix/run_service.sh' is not accessible from the database server on instance number 1At this point, I can only give you few suggestions of what I'd look for...
Check if there's OS restrictions acessing the file. Can you perform a "chmod 777 run_service.sh" and retry? Still, I don't really think this is the reason.
It seems like the Repository Assistant software, for some reason, does not recognize the ORACLE_HOME variable. I thought that could be due to having more than one Oracle Home, that this could cause conflicts, but i guess i was wrong.
Plus, check the UTL_FILE_DIR parameter, in the instance you are runing the sql script. Try to include the $OWB_HOME\owb\bin\unix directory in this. Not sure this is going to help.
Also, try to run run_service_local.sh instead of run_service.sh.
I know this sounds stupid, but, did you bounced your server? I had this same issue few years ago, but it was a different OWB and DB version. Restarting database used to work, but I can't assure this will help you. And I guess you don't want to restart it every single time the runtime platform service fails...
You may also look at this and see it helps you in any way:
Re: OWB execution error : ORA-20213: Unable to create standalone job record
Good luck.
Marcos