Skip to Main Content

APEX

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Service Temporarily Unavailable

alexliznMay 30 2008 — edited Jun 23 2008
Hi, folks,
I installed APEX into a new oracle database. After HTTP Server configuration, I ran this:

http://tracy.mycompany.com:7777/pls/apex

and got to a error:
503 Service Temporarily Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.

I have no problem with:
http://tracy.mycompany.com:7777
which means the HTTP Server works fine.

Here is my environment:
APEX 3.1
Oracle 10.2 RAC (primary instance on server: truckee)
Oracle Application Server & HTTP Server on another server (server name: tracy)

APEX 3.1 installation into Oracle 10.2 was successful. I checked the DBA_REGISTRY:

SQL>
SQL> SELECT STATUS FROM DBA_REGISTRY
2 WHERE COMP_ID = 'APEX';

STATUS
--------------------------------------------
VALID

SQL>


In my HTTP Server configuration, dad.conf is like:

Alias /i/ "/usr/orasw/as1012/Apache/images/"
AddType text/xml xbl
AddType text/x-component htc

<Location /pls/apex>
Order deny,allow
PlsqlDocumentPath docs
AllowOverride None
PlsqlDocumentProcedure wwv_flow_file_mgr.process_downloadd
PlsqlDatabaseConnectString truckee:1521:mcqs1 ServiceNameFormat
PlsqlNLSLanguage AMERICAN_AMERICA.AL32UTF8
PlsqlAuthenticationMode Basic
SetHandler pls_handler
PlsqlDocumentTablename wwv_flow_file_objects$
PlsqlDatabaseUsername APEX_PUBLIC_USER
PlsqlDefaultPage apex
PlsqlDatabasePassword <<password removed>>
PlsqlRequestValidationFunction wwv_flow_epg_include_modules.authorize
Allow from all
</Location>

Listener Status on database server(not the HTTP Server)

[oracle@/home/oracle]
[oracle@/home/oracle]lsnrctl status

LSNRCTL for Linux: Version 10.2.0.3.0 - Production on 30-MAY-2008 10:12:56

Copyright (c) 1991, 2006, Oracle. All rights reserved.

Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
STATUS of the LISTENER
------------------------
Alias LISTENER_TRUCKEE
Version TNSLSNR for Linux: Version 10.2.0.3.0 - Production
Start Date 08-MAY-2008 06:37:14
Uptime 22 days 3 hr. 35 min. 42 sec
Trace Level off
Security ON: Local OS Authentication
SNMP ON
Listener Parameter File /usr/orasw/db102/network/admin/listener.ora
Listener Log File /usr/orasw/db102/network/log/listener_truckee.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=10.30.7.121)(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=10.30.7.120)(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=192.168.20.120)(PORT=1521)))
Services Summary...
Service "+ASM" has 1 instance(s).
Instance "+ASM1", status BLOCKED, has 1 handler(s) for this service...
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
.... some entries removed here ....
Service "mcqs.mycompany.com" has 1 instance(s).
Instance "mcqs1", status READY, has 2 handler(s) for this service...
The command completed successfully
[oracle@/home/oracle]
[oracle@/home/oracle]

The HTTP Server log:

[Fri May 30 09:03:43 2008] [error] [client 10.30.7.124] [ecid: 85909137699,1] mod_plsql: /pls/apex/apex HTTP-503 ORA-12514 ORA-12514: TNS:listener does not currently know of service requested in connect descriptor\n



apex_public_user account was unlocked, password was also changed.
There is no Listener on HTTP Server. Only tnsname.ora exists on this server. From this HTTP server, I can connect to the database with service name mcqs which is from tnsname like:

SQL> conn apex_public_user/pass@mcqs

but on this HTTP Server, I can't connect to the database this way:

SQL> conn apex_public_user/pass@truckee:1521/mcqs1

The problem is obvious: HTTP server can't talk to database with this dad.conf setting:

PlsqlDatabaseConnectString truckee:1521:mcqs1 ServiceNameFormat

I think the above setting should enable HTTP server to talk to database directly--it has host name, port and sid and it has all it needs--it may get away without Listener and tnsname. Am I right?

Does the HTTP Server have to have a Listener in it? I don't think so, what do you say?
If not, how can I make the HTTP server talk to the database.

Any input will be appreciated!
Alex

null
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Jul 21 2008
Added on May 30 2008
4 comments
6,297 views