Configuring the APEX workspacePosted: October 19, 2012
This is the third part of the puzzle to get APEX working in the AWS
If you got here directly have a look at Part 1 and 2
We now need to create a workspace so that we can start working.
When you configured your environment. This maybe different, so go with the ports you were given.
Enter the username and password!!!!!
I have installed Apex a few times now and it is always different. I spent 30 minutes trying to figure out what this password was. I eventually gave up and ran the apxchpwd.sql script again. I then noticed the user name.
Everywhere else it is admin, except here its ADMIN arrrrrgggghhhh!!!!!!!!!!!!!!!!!!!!!!!
You will be asked to change the password to match the new 11g complexity passwords.
You now should have a working APEX installation
You may have a working environment but you will not be able to do anything with it. You need to check a setting. Luckily mine was already set to 1000 but you need to check
Directly from one of the installation guides
"JOB_QUEUE_PROCESSES determine the maximum number of concurrently running jobs. In Oracle Application Express release 4.1, transactional support and SQL scripts require jobs.
JOB_QUEUE_PROCESSES is not enabled and working properly, you cannot successfully execute a script.”
To see how many JOB_QUEUE_PROCESSES there are, can be checked in three ways. The easiest is from the command line
sqlplus sys/ORACLE_PASSWORD@localhost as sysdba
SELECT VALUE FROM v$parameter WHERE NAME = ‘job_queue_processes’;
ALTER SYSTEM SET JOB_QUEUE_PROCESSES = <number>
You can now use Apex to your hearts content. Good luck and happy developing