I am running Oracle 10g on a Sun V490/Solaris 10 platform. When I attempt to run sqlldr from the command line (see below for the top of the .ctl file) I get the following error;
SQL*Loader-941: Error during describe of table VD_CLAIM
ORA-04043: object VD_CLAIM does not exist
I am logging into sqlldr as SYS, connecting as sysdba since the owner of the schema/table gets booted out as "invalid user/password". This is odd in that the user can log into the Enterprise Manager and isqlplus interfaces and perform all appropriate actions.
I have looked up the error (04043) and it appears to be tied to privileges; but SYS has full privileges on the table VD_CLAIM.
INTO TABLE VD_CLAIM
thanks for any help,
you need to prefix the table with the schema name, how else would it know what schema it was in?
but I would fix your problem with the username / password as using sys should be discouraged, guess you are doing something wrong somewhere
whats the full sqlldr command you are issuing
here is the sqlldr login
Thank you. Below is the way I access sqlldr; this particular login works. However my other user MFAD cannot login as it gets the ora 04043 error "invalid user/password". This is very odd as this particular user can login into the enterprise manager and isqlplus interfaces.
>sqlldr \' sys/xxxxx AS SYSDBA \'
The system responds with
I enter the path/name of the control file and it begins to run and then ends with the following error;
SQL*Loader-941: Error during describe of table MFAD.VD_LOCKIN
ORA-04043: object MFAD.VD_LOCKIN does not exist
MFAD is the user/schema name that works everywhere but sqlldr.
Thanks for your assistance.
full sqlldr .ctl file
LOAD INFILE '/export/medic/tape4/vendor/utd_vd_lockin_2004_08.dat'
INTO TABLE MFAD.VD_LOCKIN
The ctl file explodes on the INTO TABLE line.
Check the BAD file for errors, as well see if the table has any non-portable data types. Since you are doing an INSERT are you sure the table is empty?
"What is past is PROLOGUE"
Check if you have that table in MFAD schema and grant insert permissions to sys and try it.
I just tried with sys user and works fine with other schema tables.
Click Here to Expand Forum to Full Width