This content has been marked as final. Show 30 replies
It looks to me like there's something in the @apex_epg_config11 script that screws up the XDB authentication.
I've tried building a completley new database (twice) and installing APEX V2.2.1 - this works fine - then V3.0 - broken.
Then I tried a second new database and installed V3.0 from scratch - this too displays the same fault.
It looks like V3.0 only works (not that I've seen yet) with Apache and Mod Pl/SQL
Big expectations - bad delivery - on the embedded PL/SQL gateway side.
Especially since the embedded gateway gets rid of the overhead of the external processes - it's really cool - IF IT WORKS!!
I'm trying other tactics and will update if I make any progress.
Thanks for the snappy reply.
I have the same feeling, but no matter what combination of "/" or "\" I include in the path to the images I can't get it working at all on a 10.2.0.x database.
However, the IDENTICAL path - pointed to a 10.1.x database works fine!
Is there a difference in the requirements for specifying the image path.
I had no trouble upgrading a 10.2.0.1 server from Apex version 2.2.1 to 3.0 using the HTTP server.
I gave up on my "10.2.0.3 or later" server for now.
It was previously running Apex 2.2.1 with the embedded PL/SQL gateway.
That had been set up by running the apex_epg_config script that came with 2.2.
After upgrading to 3.0 and running the apex_epg_config11 script, I am getting the same XDB messages you are.
The Apex team has earned a weekend off. I'm sure we'll get an answer in a couple days.
I just successfully upgraded from Apex 2.2.1 to 3.0 using the embedded PL/SQL gateway on a 10.2.0.3 instance (Windows XP).
I had the same problem with the missing images initially, but realized there is the extra step of uploading the images to the embedded PL/SQL gateway.
I did this as follows:
1. Copy the apex directory and all sub-directories to %ORACLE_HOME%.
2. Run apex_epg_config.sql, passing the %ORACLE_HOME% path as a parameter.
e.g. sql> @apex_epg_config.sql C:\oracle\product\10.2.0\db_1
Note: Do not run the the apex_epg_config11 script - I believe this is for 11g?
Note2: I originally set up the gateway using notes from the Amis website http://technology.amis.nl/blog/?p=1443.
Hope this helps - Mark
Those are the instructions I followed when I got it working with version 2.2.1.
The installation guide for 3.0 says specifically to use the apex_epg_config11 script.
(I can only say that I am using version "10.2.0.3 or later".)
It loaded the images successfully. I can see them.
It looks like there was some stuff about anonymous access removed from the apex_epg_config script since the 2.2.1 version.
Running it manually didn't help.
At this point I've probably made a mess of my XDB configuration.
After many hours of testing, I've come up with a workable solution of getting V3.0 loaded and working with the Embedded PlSQL Gateway (EPG).
Whichever database you use, run the apexins.sql as directed.
Set up your EPG outside of the Apex environment - if you're using XE - it's done for you - if a non-XE database see this wonderful link by Marco Gralike http://technology.amis.nl/blog/?p=1443
Whatever you do, don't use the apex_epg_config.sql or apex_epg_config11.sql at all.
I loaded the images using the FTP service defined in Marco's article referenced above. Images are stored in the database, and this virtual directory is exposed by the EPG.
I used CuteFTP but any FTP utility can be used.
I now have V3.0 working on XE 10.1.x and 10.2.x databases.
NOTE that on XE, you will loose the database administration functionality, but you'll get aworking Apex v3.0 on XE!!
Hope this helps.