This content has been marked as final. Show 2 replies
Is it possible that when I migrated the complete DB, I unwillingly took some DB objects created by the oldThis at least shouldn't be something to worry about. Apex objects get installed under a schema with the corresponding name. Your 3.2 objects would have been under APEX_030200 and your Apex 4.2 objects should be under APEX_040200.
APEX-version (on the old machine) with me that now clash when I try to use the new APEX version?
That said, I don't know what is causing your workspace issue. Ruling something out is useful, though. :)
as a possible workaround, set "Create demonstration objects in new workspaces" = No in Manage Instance -> Feature Configuration -> Application Development. This will prevent the installation of the Sample Application when a new workspace is created.
After you have done that and created a new workspace, can you login into that workspace and install the Sample Database Application and let us know which error you are getting?
Your problem might be related to the following thread Re: wwv_flow_lists_of_values$ where template applications had been installed on instance level ("Manage Instance -> Manage Shared Components -> Template Applications")
My Blog: http://www.inside-oracle-apex.com
APEX Plug-Ins: http://apex.oracle.com/plugins
Edited by: Patrick Wolf on Nov 7, 2012 12:39 PM