Note: FixedDataControlFile.ctl is kept in C:\app\sunita\product\12.1.0\dbhome_1\BIN.

Thank you.

If you are invoking sqlldr on the same system as the database server itself, there is NO need to include "@XE" after username/password.

BTW, SYS should only be used to do Oracle database upgrade & maintenance & NEVER for normal application processing!

post content of tnsnames.ora file

ora-12154ALWAYS only occurs on SQL Client & no SQL*Net packets ever leave client systemora-12154NEVER involves the listener, the database itself or anything on the DB Server.ora-12154occurs when client requests a connection to some DB server system using some connection string.TNS-03505 is thrown by tnsping & is same error as ora-12154thrown by sqlplus or others.The lookup operation fails because the name provided can NOT be resolved to any remote DB.The analogous operation would be when you wanted to call somebody, but could not find their name in any phonebook.The most frequent cause for the ora-12154error is when the connection alias can not be found in tnsnames.ora.The lookup operation of the alias can be impacted by the contents of the sqlnet.ora file; specifically DOMAIN entry.TROUBLESHOOTING GUIDE: ora-12154& TNS-12154 TNS:could not resolve service name [ID 114085.1]http://edstevensdba.wordpress.com/2011/02/26/ora-12154tns-03505/

That's not the incorrect password error, that's the first error you say which is saying that your connection string can't be found in your tnsnames file. Funny, because I'm sure you used that @pdborcl earlier just fine, what changed?

Additionally, I didn't even see any attempt for the lower case password.

Also, there's no indication that the password you've saved in sql developer is hr/HR and allows you to connect successfully.