Back to top

Back to top

Back to top

Error page=167 item="P167_REGION" id="12754902714045613"
declare
*
ERROR at line 1:
ORA-06502: PL/SQL: numeric or value error
ORA-06512: at "SYS.OWA_UTIL", line 325
ORA-06512: at "SYS.HTP", line 1322
ORA-06512: at "SYS.HTP", line 1397
ORA-06512: at "SYS.HTP", line 1689
ORA-06512: at "FLOWS_020000.WWV_FLOW_API", line 3243
ORA-06502: PL/SQL: numeric or value error: character string buffer too small
ORA-06512: at "FLOWS_020000.WWV_BIU_STEP_ITEMS", line 63
ORA-04088: error during execution of trigger 'FLOWS_020000.WWV_BIU_STEP_ITEMS'
ORA-06512: at line 7

1. alter system set nls_length_semantics = BYTE scope = spfile;
2. shutdown the database
3. restart the database

Back to top

Back to top

Back to top

     drop user FLOWS_030100 cascade;
     drop user FLOWS_FILES cascade;

And to remove Oracle Application Express from the database execute the following command:

     @apxremov.sql 

For releases prior to Application Express 3.1 there are three steps required to completely uninstall Oracle Application Express from an instance of the Oracle Database. The first step is to drop the schemas associated with your Application Express installation. Two of those schemas are FLOWS_FILES and HTMLDB_PUBLIC_USER. Additionally, for each version of Application Express installed in your database, there will be a version-specific schema name similar to FLOWS_0XYYZZ. For Application Express 2.0 that schema name is FLOWS_020000. Application Express 1.5 uses FLOWS_010500, and the 1.6 version uses FLOWS_010600. Connect to the database as the SYSTEM user, and drop these schemas.

Next, you will need to drop the Application Express public synonyms. To do this, issue the following statement and run the resulting output:

     select 'drop public synonym ' || synonym_name || CHR(10) || '/' from sys.dba_synonyms
       where table_owner in ('FLOWS_010500','FLOWS_010600','FLOWS_020000','FLOWS_FILES');

Finally, if desired, remove the images directory that was associated with the Application Express install.

Back to top

Back to top

Back to top

First, make sure that you're using the Service Administration Login Page (http://somehost.com/pls/htmldb/htmldb_admin) If the screen you're seeing doesn't say something like "Welcome to Application Express Service Administration" then you're probably not properly attempting to log into the htmldb_admin interface. If you just installed Application Express, the password was specified as part of that install. The username will always be "admin" by default. If you still cannot remember the password, then you can use SQL*Plus to reset the password or create a new Administrator depending on which release of Oracle APplication Express you are using.

With release 3.0 and 3.1 to change the admin password start SQL*Plus and connect to the database where Oracle Application Express is installed as SYS. Then enter the following command followed by the new password:

     @apxxepwd.sql password

For Releases prior to 3.0 you will need to create a new Administrator. Using that newly created login, you should be able to log into the Service Administration Console and reset the original Admin user's password. To create the new admin user from SQL*Plus, customers connect to the database as sys or system and run this command:

     alter user FLOWS_020000 account unlock;

...and then 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 => 'myemail@mydomain.com',
          p_web_password => 'admin2') ;
     end;
     /

...which creates a new admin user with username "admin2" and password "admin2". Finally, execute a...

     alter user FLOWS_020000 account lock;

...from a schema like System after this process is completed.

Back to top

Back to top

1. Ensure that you do not have either of the TNS_ADMIN or ORACLE_HOME environment variables set.
2. If the failed attempt to log into the database shows an ORA-12545, please check the troubleshooting tips in support Note 12101.1
3. Some users have found that copying the "htmldb" tnsnames.ora entry from $ORACLE_APEX_HOME/network/admin/tnsnames.ora into the tnsnames.ora file used by their database has solved this issue for them.
4. On a windows machine, removing traces of your ORACLE_HOME environment variable *could* mean checking the registry as well (please check support Metalink Note 208256.1 for guidance in this delicate matter).

Back to top