dgielis_

Archive · 13 June 2006

APEX and Full Exp/Imp DB

Written 20 years ago. Oracle APEX has moved on a lot since; check the current Oracle APEX posts too.

Today I had to create a new database, exactly as an other one.
APEX was installed on that (source) database, so I was curious to see if it would work on the target as well… and yes it almost did work!

To reproduce what I did:
1. Take a full export of source database
2. Create new database and do a full import into that database
3. Recompile all invalid objects (in $ORACLE_HOME/rdbms/admin - SQL>@utlrp)
4. Test APEX (after changing/adding DAD if necessary)

My APEX didn’t work correctly… I saw that there were some invalidated packages.
To correct APEX, these are the grants the invalid packages needed (grant by sys):
>grant execute on SYS.DBMS_LOCK to flows_020000;
>grant execute on SYS.DBMS_FLASHBACK to flows_020000;
>grant execute on SYS.DBMS_SYS_SQL to flows_020000;

I also needed to change the password of my workspace users (admin, …) to be able to login again.
You can also create a new admin user by following script:
    alter user FLOWS_020000 account unlock; (as system)
    -> connect to the FLOWS_020000 user and run this procedure
    begin
    wwv_flow_api.set_security_group_id(p_security_group_id=>10);
    wwv_flow_fnd_user_api.create_fnd_user(
    p_user_name => ‘admin2’,
    p_email_address => ‘dimitri.gielis@telenet.be’,
    p_web_password => ‘admin2’) ;
    end;
    /
    commit;
    alter user FLOWS_020000 account lock; (as system)

Now everything is up-and-running again! APEX is great!

Originally published on Blogspot.

Comments

Comments appear after I've read them. Plain text; line breaks are kept. Privacy