Whenever I try to import a Workspace from an dos export file I get the following error. Any ideas?
Application Express 4.2.2.00.11
Oracle Database EE 22.214.171.124
Execution of the statement was unsuccessful. ORA-06550: line 3, column 4: PLS-00201: identifier
'WWV_FLOW_API#G_ID_OFFSET' must be declared ORA-06550: line 3, column 4: PL/SQL: Statement ignored
wwv_flow_api#g_id_offset := 0;
wwv_flow_hint.g_schema := 'MYUSER';
ORA-06550: line 3, column 4: PLS-00201: identifier 'WWV_FLOW_API#G_ID_OFFSET' must be declared ORA-06550: line 3, column 4: PL/SQL: Statement ignored
I'm having the same problem... trying to export a workspace from 10g into 11g, same version of APEX (4.2.2.00.11). Did you find a solution yet? Is this some kind of bug?
UPDATE: I managed to import the workspace by executing the sql script with SQL*Plus, so not by using the APEX web interface... All looks well!
thanks for updating your thread, as that's the suggestion I was about to make to you - to use the command line import option. Yourself and Jeff have hit an issue we're aware of, and something that will be resolved in our next patch release, 4.2.3. With the inclusion of RESTful Services-related API calls in a workspace export file, there are a number of new API calls that hadn't been previously included. Some underlying import logic needed to be updated to take into account these new API calls, but unfortunately WWV_FLOW_API.G_ID_OFFSET was missed. In the meantime, as you've already found out, and as confirmed by my colleague, Christian, you'll need to use the command line option for importing your workspace.
I'm not able to find the bug back in My Oracle Support (by searching on the bug number 16846844). Is this hidden for some reason or does it need some time for the bug to appear in the search results?
UPDATE: I found the bug back when I search under "Patches & Updates". Apparently, there's already a patch out which fixes this and another issue related to workspace imports. The patch ID is 16781538.
You're spot on! APEX 4.2.2 PSE 16781538 has been made available on MOS, which addresses the bug I previously mentioned plus a separate, 16781538, relating to an integrity constraint violation during a workspace import. I wasn't aware that the two issues had been combined into the one PSE, otherwise I'd have mentioned this PSE before now, so apologies for that. The PSE is available for download via the 'Patches & Updates' tab in MOS. Just search for # 16781538.
Is there a certain user that the script needs to be run as. When I just ran the script as SYS I get the following error:
Creating workspace STOREPAGE...
ERROR at line 3:
ORA-06550: line 3, column 1:
PLS-00201: identifier 'WWV_FLOW_TEAM_API.CHECK_VERSION' must be declared
ORA-06550: line 3, column 1:
PL/SQL: Statement ignored
Disconnected from Oracle Database 11g Enterprise Edition Release 126.96.36.199.0 - 64
With the Partitioning option
You need to run the script as the APEX schema owner - for APEX 4.2.2, this will be APEX_040200.
It could be that the account is locked, so you will have to unlock it first then.
Could also work if you use "ALTER SESSION SET CURRENT_SCHEMA = APEX_040200;" when connected as SYS.