This content has been marked as final. Show 12 replies
Yes. Many times.
anybody else ran into this before?
Perhaps the installer has not completed all its tasks, the database is not up, and/or the listener are not running. If the installer doesn't quite get your host particulars correct, Apex pages will not work.
Is the listener running? If its not running the Apex pages have no chance of working. In a command box, try:
If Apex is running you will see the presentation http entry for 8080 under the Endpoints. If that is not present, the "home page" is not going to work.
Step Two, is the database running, same thing, if the database is down there is no chance the Apex pages will work.
... password ...
Most likely installer didn't get to finish creating and starting up the database.
And usually installer won't give much indication when it does. There is a log file for the installer, but finding useful information in the installer log can be frustratingly difficult.
Try a startup in a command box:
connect /as sysdba;
... connected to idle instance ...
... -- will probably fail, usually it reports a controlfile problem ...
Try the uninstall steps at http://docs.oracle.com/cd/E17781_01/install.112/e18803/toc.htm#CIHDDHJD then give it another go.
And verify your NIC configuration. If you have a wireless adapter, VPN interface, virtual box network device, or other interfaces besides your "main" IP address in the Networks applet, disable them until after the installer completes.
When I did the startup command, this is what it gave me:
ORA-01078: failure in processing system parameters
ORA-01565: error in identifying file 'C:\oraclexe\app\oracle\product\10.2.0\serv
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
I'm going to try to uninstall and reinstall today. The computer may very well have a wireless adapter - it's sitting in the spare bedroom at my lead developer's house, and I'm remoting into it. So if it fails a second time I may just have to let him handle it. :)
I'll let you know what happens - thanks for your assistance so far.
Like it states in the documentation, "You must be part of the Administrators group on Windows to install Oracle Database XE." see http://docs.oracle.com/cd/E17781_01/install.112/e18803/toc.htm#BABIHEJC in the "Permission Requirement ..." section.
Check the local Administrators group, in Start/Run lusrmgr.msc the Local Users and Groups applet. The user running the installer has to be an admin, to set up the services and other tasks. If that requirement isn't satisfied the installer experience will be ... very unsatisfactory.
If you didn't get an ora-12560 protocol error with a connect /as sysdba; the windows database service was running. As far as the extra NIC adaptor, that can cause glitches for Apex but the database install and setup has to work first.
Apparently I was not a network administrator - I was just a standard user with administrative links. So I changed myself to a network administrator (apparently one of my links gave me the authority to do that :) ) So then I uninstalled Oracle and re-installed it and... no luck - same issue.
It was an ORA-12560 error.
Guideline here, what does one do with the PDC and the backup DCs? Ensure they are Up. And Nothing Else.
is also a domain controller
The server admins ought to be rather upset at non-DC software installs on the DCs. Outside of ensuring the domain services stuff is running, nothing else should be happening to a DC. Yes, it would be good to find a different host for trying out XE (or any other software) ...
I agree it would be a very dumb idea in any normal company, but we're very small - 3 guys. The domain controller is also the web server as well as test bed server. It's the latter usage where Oracle comes in. The user's are wanting to remote to the machine and run our app against Oracle in a test setting.
OK. Got it working. I looked at this link:
Re: 10g Express Edition on Windows 2008 Enterprise R2 x64 with Active Directory
I followed the tip for changing the compatibility for the installer and that seems to have done the trick.
But thanks so much for your time, my friend. I'll make sure I give you some points for effort. ;)