This content has been marked as final. Show 5 replies
Dear Paul M.
Thank you very much for answering. I posted the same question on the application express forum. Also posted on the Books forum as well as looked for the error code up in google. Nada.
Please note that I am migrating from MS Access and am knew to oracle. Can you please detail the instructions. I know it's a lot to ask but i am stuck in the beggining of the book for 3 days now.
Thansk in advance.
This is realy getting frustating. I get the same error. I just want to learn and go through the book. Following are the steps that i followed.
1 - Installed Oracle Database Express Edition (XE) Release on my local PC with Windows XP Professional SP 3 supplying the password for SYS and SYSTEM as per the video at
2 - Upgraded the Oracle Application Express to 3.2 as per the video at
2 - Now I log in as
WORKSPACE : SYSTEM
USER NAME : SYSTEM
PASSWORD : ********
3 - Go to Utilities > Data Load/Unload > Load > Loadspreadsheet Data >
Change the Load from to upload file (comma seperated or tab delimited) NEXT
Browse for the file which is 'ORDERS', NEXT
Change the table name to 'ORDERS'
Change the primirary key column to ORDERS_ID - LOAD DATA
And than i get
"ORA-20001: create_table error: ORA-20001: Excel load run ddl error: ORA-01003: no statement parsed"
As i said I am totally new to this and migrating from MS Access. However I am quite familiar with all the RDBMS concepts (Theory and academic).
I tried as per your instructions
SQL> conn / as sysdba
grant create table to SYSTEM;
Maybe some thing to do with the workspace SYSTEM, the Schema SYSTEM and user name SYSTEM.
I am not much familiar with the Oracle Architect. The book named 'Begning Oracle Application Express' uses a hosted account and therefore the approach will be slightly different. But how different, I do not know. Just a simple start to go along the book.
If there is any thing that can be done about it, please state so.
Maybe some thing to do with the workspace SYSTEM, the Schema SYSTEM and user name SYSTEM.I don't know, but surely it's not a good idea using SYSTEM user for application things, system is a dba, and should only be used for that purpose.
You should create a new user (if you don't already have one) and use that one for your applications. An example follows (using SQL command line as sysdba) :
change names as per your needs.
SQL> create user new_user identified by new_user 2 default tablespace users 3 quota unlimited on users; User created. SQL> grant create session,create table to new_user; Grant succeeded. SQL>
Create a new workspace, assign it to this user, and retry your loading.
If this works, you may need to grant other privileges to the user.
P.S. The above worked perfectly to me.