Key Software Oracle Olr Cannot Be Opened.error 2

We provide Oracle administration support on GNU Linux Servers. One of our customers had us set up a new Oracle XE server for them on CentOS. We set up everything and had the system up and running fine. We had also tested everything on the server and verified connection status from clients. Two days after installation we got a call from the customer that he could not open the Oracle XE web administration interface and he was getting an access denied, page not found error on http://127.0.0.1:8080/apex


It may or may not be a database issue, well without debugging you cannot actually say, sometimes it may be a database issue because of some patches etc., well you need to debug how that scenario occurs, even if you raise a TAR with oracle too, they will also ask you the same questions.!! I am a new one who started to use Oracle Database and faced the problem during installation the last verstion of Oracle XE 11g x64 to the Microsoft Windows 7 x64 Enterprise.

We promptly looked into the issue and checked for any mistakes in configuration or the setup. We scourged the oracle technology forums for an answer to this problem. There were a few solutions that were mentioned on the site. We tried all of them that we found on OTN but could not figure out the problem. The oracle service was running fine but we could not connect to it through the web admin interface.
Opened.errorSome of the solutions mentioned on the site included
a) Reinstalling Oracle XE - we did not want to go this way as we would not learn anything by doing this
b) Reloading settings by running /etc/init.d/oracle-xe force-reload. We did this but didn't change anything
c) We tried the

Key Software Oracle Olr Cannot Be Opened.error 2 1

exec dbms_xdb.sethttpport(8080) strategy but it was throwing errors.Release
On checking lsnrctl status we were getting the following errors
We figured that the the listener was not able to start and bind to the port and had something to do with network settings. We checked out /etc/hostname and /etc/hosts and checked with the local ip. What had happened was that the local static IP was changed manually after the Oracle XE installation but the hosts file did not reflect this change. We corrected this error and did a /etc/init.d/oracle-xe force-reload and presto everything was working.
We were no longer getting the 'Could not connect to http://localhost:8080/apex, Page not found' error anymore. We verified that the listeners were running by running lsnrctl statusKey which gave us the correct response which should look like below

Key Software Oracle Olr Cannot Be Opened.error 2 Free


We also offer Readymade websites for individuals and businesses to generate unlimited revenue. An ideal solution to get your business to take off fast without waiting for website development delays. Make your business easily accessible to the billions of internet users that go online daily. If you have any query regarding this, to get in touch with us to know more.

Web-Development projects are one of the most widely available freelancing projects. Technical Solution Application Development Technologies Freelancing Leave a reply Your email address will not be published. Required fields are marked *

Key Software Oracle Olr Cannot Be Opened.error 2013

General Database Discussions


Listener suddenly looses connection to database reporting ORA-12518


Previous Page | General Database Discussions | HOME

Key Software Oracle Olr Cannot Be Opened.error 2

Related Links

Scripting question
How to setup Oracle Client SQLNet.ora trace on client side
Slow SQL--Plan looks fishy--any suggestion!!!
Reformation of table with columns values as Column names
how create data block corruption for test DBMS_REPAIR
Changing user passwords
Help Me Abt -> IMP-00009: abnormal end of export file
How to query database to find out what privileges have been granted
processing of oracle architecture
teamed NICs for RAC interconnect
ora-12801
Issue with reclaiming space
Column size suggestion..
Problem defining partition for storing value 0 with new data
best practices to generate archivelog
Recovery of data after ASM Disk fails