PROBLEM: Getting an ORA-22288: file or LOB operation FILEOPEN failed, The system cannot find the path specified. ORA-06512: at "SYS.XMLTYPE" error during the upgrade process.
I am a relative newbie to Oracle and Oracle XE, so the following may seem like a novice problem to you, but there are many internet questions about why they are getting the above error during 5.1.4 setup. The problem arises from poorly worded guidance in the upgrade instructions. The upgrade process referred to is located at (Upgrading Oracle Application Express in Oracle Database Express Edition). I have copied the relevant steps below. The specific error occurs in Step 5, when they run @apex_epg_config.sql APEX_HOME.
CORRECT ANSWER: When installing the 5.1.4, you must use the .\APEX folder, inside the path you extracted to. So, in my example during Step 1, where I extracted the files to C:\APEX\MEDIA\APEX.5.1.4 the correct command line is: @apex_epg_config.sql C:\APEX\MEDIA\APEX.5.1.4\APEX which folder contains the .\Images folder. Or, in generic terms, the correct command line for Step 5 is: @apex_epg_config.sql [YOUR EXTRACTION PATH]\APEX
UPDATE: I had to create a 5.1.0 environment today to test the upgrade procedure. In this case, I had to use the extracted folder, as the NOTE suggests. Whereas in 5.1.4, the command was: @apex_epg_config.sql [YOUR EXTRACTION PATH]\APEX, the 5.1.0 install required @apex_epg_config.sql [YOUR EXTRACTION PATH] without the \APEX folder included. If anyone can confirm this, please post a reply.
DISCUSSION: As an Oracle newbie, let me say that I have 15+ years is Access, SQL Server and Visual Studio development under my belt, so I am not a novice. With this said, I ran this command line (as others online have suggested they did) in an "as is" manner. The APEX_HOME was not italicized or otherwise indicated that it was a parameter. The instructions need to clarify the distinction. Moreover, they need to be corrected. Here is what did not work:
INCORRECT INSTRUCTIONS:
1. In the note in Step 5, it said "APEX_HOME is the directory you specified when unzipping the file" which could have been "for information" or meant as guidance. If one assumes that this is some type of system variable that was defined when Oracle XE was installed, then it could easily be interpreted as FYI and you could easily run it without editing. Again, I was not alone is thinking this, if internet inquiries are any indication. In any case, the @apex_epg_config.sql APEX_HOME command does not work.
2. Alternatively, in various on-line forums, the NOTE was interpreted as the "drive" containing the extraction folder. That is, if you extracted your files to C:\APEX, then you use C:\ as your APEX_HOME whereas if you use D:\APEX you would use D:\. Again, failure. In this case, the @apex_epg_config.sql C:\ command does not work. Again, I was not alone, if internet inquiries are any indication.
3. Finally, if you assume that "APEX_HOME is the directory you specified when unzipping the file" and use that, its still fails. In my example, I used a path other than that specified in Step 1. I extracted my files to C:\APEX\MEDIA\APEX.5.1.4. So, according to the note, I should have used this folder. 2. Alternatively, in various on-line forums, the NOTE was interpreted as the "drive" containing the extraction folder. That is, if you extracted your files to C:\APEX, then you use C:\ as your APEX_HOME whereas if you use D:\APEX you would use D:\. Again, failure. In this case, the @apex_epg_config.sql C:\APEX\MEDIA\APEX.5.1. command does not work. Once again, this was incorrect.
How to Upgrade
To install the latest version of Oracle Application Express in your Oracle Database XE, first download the latest version of Application Express from the Oracle Technology Network.
1. Unzip the downloadloaded zip file:
- Linux: Unzip <filename>.zip
- Windows: Double click <filename>.zip in Windows Explorer
- [Note: You should keep the directory tree where you unzip the files short and not under directories that contain spaces. For example, within Windows unzip to C:\_apex.]
5. Log back into SQL*Plus (as above) and configure the Embedded PL/SQL Gateway (EPG):