Importing from Development install to production "runtime only" installation [message #484784] |
Thu, 02 December 2010 14:08 |
chris32680
Messages: 92 Registered: January 2006 Location: Charlotte
|
Member |
|
|
Good afternoon all,
I've configured a development installation of apex 4.0, plus a production runtime only install. (actually, i created the production as full dev at first to create the workspace, and then converted it back to runtime only)
I attempted to export an application created in the development side and then import that into the production run time only (by executing the sql export as the apex schema owner).
It looks like the security ID that the development APEX assigns to the application has a problem with the security id expected in the production side.
Is there a way around this without manually editing every exported application we do?
Enter user-name: aeproduction
Enter password:
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> @f102.sql
APPLICATION 102 - aer_vendor_consignment
Set Credentials...
Illegal security group id value for this schema.
Check Compatibility...
API Last Extended:20100513
Your Current Version:20100513
This import is compatible with version: 20100513
COMPATIBLE (You should be able to run this import without issues.)
Set Application ID...
begin
*
ERROR at line 1:
ORA-20001: Package variable g_security_group_id must be set.
ORA-06512: at "APEX_040000.WWV_FLOW_API", line 51
ORA-06512: at "APEX_040000.WWV_FLOW_API", line 304
ORA-06512: at line 4
15:07:21 >select * from v$version
15:07:23 2 ;
BANNER
--------------------------------------------------------------------------------
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
PL/SQL Release 11.2.0.1.0 - Production
CORE 11.2.0.1.0 Production
TNS for Solaris: Version 11.2.0.1.0 - Production
NLSRTL Version 11.2.0.1.0 - Production
|
|
|
|
|
|
|
|
|
|