2.4.07

APEX 3.0 on XE part 2

On 29 Februari 2008 Oracle released Application Express 3.1 . With this release you can upgrade the Application Express within Oracle XE to 3.1. For more information on this topic see Oracle Database XE and Application Express 3.1 and APEX 3.1 on XE .

If you followed the guidelines of APEX 3.0 on XE, you have a working APEX 3.0 interface. However the administrative interface of APEX is not installed on XE by default. Using this interface you can manage all aspects of the service including creating, removing, and managing workspaces. Barney Mattox discovered a workaround to install this interface as well.

In order to install the administrative interface perform the following steps:

  1. Start SQL*Plus. Make sure your working folder is the APEX installation folder (where apexins.sql is located).

  2. Connect as user SYS.

  3. ALTER SESSION SET CURRENT_SCHEMA = FLOWS_030000
    /

  4. The following command imports the administrative interface: @script\f4050.sql

  5. The following command imports the request for workspace interface: @script\f4700.sql

  6. Change the password for the ADMIN user in order to login in the administrative interface: @apxxepwd.sql

  7. Use the following URL to access the administrative interface http://server:port/apex/f?p=4550:10 i.e. http://127.0.0.1:8080/apex/f?p=4550:10 .

Additonal notes:

  • Issue a spool install.log after logging in to SQL* Plus. If there occurs an error SQL*Plus will exit. You can use the logfile to find out what went wrong.

  • I experienced problems with step 3: Illegal security group id value for this schema. A workaround is to login as FLOWS_030000 and run the scripts. First you need to unlock user FLOWS_030000:
    ALTER USER FLOWS_030000 IDENTIFIED BY password ACCOUNT UNLOCK
    /

12 comments:

pzn said...

HI,

i tested the apex 3.0 installation, on XE, if i modify the coreins.sql as mentioned in the script it could'nt install APEX correctly, but if i do the standard installation, all works fine.

Setfpport to upload all images,
stop and start xe db,
apxxepwd.sql to set admin password.

Regards

Philippe

Anonymous said...

Hello,

Tested your workaround to install Apex 3.0 on XE and experienced some difficulties.

1. Did not succeed to run the scripts to install "the administrative interface" (4050) and "the request for workspace interface" (4700) in sqlplus via cmd.exe
There was no problem to run these scripts in toad with user FLOWS_030000 (after unlocking)

2. Scripts where renamed?
- @script\4050.sql => @builder\f4050.sql
- @script\4700.sql => @builder\f4700.sql


Regards,
Philip

Jornica said...

Philip,

Thanks for the feedback, concering item 1 I don't have any clue. And item 2 is corrected.

Thanks,

Jornica

SeBasTiaan said...

Hello,

I was wondering where the tablespace (Usage) monitor is hidden in APEX 3.0.
In Oracle Database Express, you have this easy Storage administrator, where you have an overview of the Tablespaces and Datafiles used.

Thanks.

Sebastian

Anonymous said...

I followed the procedure, but on running the script, I got the error:

g_security_group_id must be set.

I altered the session as described. I saw in the previous post you had encountered this - did you just end up starting from scratch at that point?

Thanks.

--Ted

Anonymous said...

Trying to figure out how to find that security ID

select security_group_id from wwv_flows
/

Doesn't work...even after I've altered the session

ALTER SESSION SET CURRENT_SCHEMA = FLOWS_030000

Carlos said...

Hi,

I installed APEX 3 in Oracle Express Edition with success (applications 4050 and 4700 too), using the information in your posts (thx ;)).

I'm having a problem now with application 4700. I'm creating a new workspace, and in the last step, is asked for me to put the verification code (generated images). The problem is that the 5 images doesn't appear... is necessary to complete another step on the installation to become complete?

Anyone can help, please
Thx in advance :)

Carlos V.

Jornica said...

Ted,

Yes, run the scripts f4700.sql f4050.sql again and login as FLOWS_030000 and execute
wwv_flow_api.set_security_group_id(p_security_group_id=>10);
ins SQL+

And have a look for the comments in the scripts.

With kind regards,

Jornica

Jornica said...

Carlos,

I tried to reproduce your problem, but I don't see any verification code at all (version 3.0.0.00.17).

With kind regards,

Jornica

Carlos said...

Jornica,

Thanks for your post... i'm using version 3.0.0.00.20. Maybe this verification code is a change comparing to 3.0.0.00.17 that you mentioned.

Well, if you try one day this version, and understand why this problem occurs, let us know here in the blog :)

Best regards
Carlos V.

Anonymous said...

Jornica,

Thanks for your suggestion.

I did as you proposed and keep getting the same problems. In fact, the scripts never "run", in that they get kicked out from the g_security_group_id must be set error.

I executed this:

exec wwv_flow_api.set_security_group_id(p_security_group_id=>10);

commit;

and it worked.

I didn't know what this means:

"ins SQL+"

Anyway, the above two lines executed successfully, then I ran the two scripts and got the same error.

Anything else you can think of that might be causing this?

Thanks again.



And have a look for the comments in the scripts.

With kind regards,

Jornica

21:50

Anonymous said...

Log on using the user FLOWS_030000 rather than setting the current_schema. It worked for me.