Unable to login or run an application after applying APEX 4.1.1 patch set?

Posted on by

If you get the error Workspace “[workspace name]” is inactive. Contact your administrator. when you try to login into your workspace or when you run an application, then you should run the following script to fix the status of your workspaces.

  • Connect as SYS, SYSTEM, APEX_040100 or any user who has the APEX_ADMINISTRATOR_ROLE role
  • Run the following PL/SQL script: 
    begin
    for l_workspace in ( select short_name
                           from apex_040100.wwv_flow_companies
                          where account_status='AVAILABLE' )
    loop
        apex_040100.apex_instance_admin.enable_workspace(l_workspace.short_name);
    end loop;
    commit;
end;
/

Note: This problem only occurs for workspaces which have been created on the command line with the apex_instance_admin.add_workspace procedure. Workspaces which have been created through the UI should be fine.

The problem has been filed as bug# 13769526 and will get fixed in the next version of APEX. Thanks to Dimitri who notified us about the problem.

2 thoughts on “Unable to login or run an application after applying APEX 4.1.1 patch set?”

  1. Pingback: Unable to login or run an application after applying APEX 4.1.1 patch set? | Warp11 .::. Oracle Apex Knowledge Group

  2. Hello Patrick,

    I had this problem too, this afternoon after exporting a workspace from a APEX 4.1 and trying to import it to al OracleXE 11gR2 on my laptop.
    I had just finished applying the path from Apex 4.1 to 4.1.1.

    After importing I got the :”Worskpace is inactive..” error.

    Your fix did not instantly do the trick. I used Apex_040100 and that was still Locked and was not granted the APEX_ADMINISTRATOR_ROLE.

    The following statement gave the same output even after running your fix, (PLSQL sucessfully completed)

    Select Short_name, accountstatus from wwv_flowCompanies;
    resulted in:

    shortname account_status
    INHER AVAILABLE

    But I was still not able to open the workspace..

    Then I realised that the role was never granted to APEX_040100, at least not by me explicitly…

    After
    alter user Apex_040100 identified by ;
    alter user apex_040100 account unlocked;
    grant APEX_ADMINITRATOR_ROLE to apex_040100;

    and running your fix again

    Select Short_name, accountstatus from wwv_flowCompanies;

    resulted in:

    shortname account_status
    INHER ASSIGNED

    And then I was able to use the workspace again.

    If I only had read your instruction better the first time….
    Let everybody else be warned to check if the role has been granted…

    Thanks for the quick fix
    regards
    Wouter

Comments are closed.