A DBA question

Question

Hi,
This is a database question.
I am using JDeveloper 10.1.3.4 and got an error when entering a WHERE clause in the definition of a view object:
SQL Query Error Message: ORA-00904: "LDAPUID": invalid identifierI figure the cause of this problem lies in the database tables because I can connect to the database schema from the Connection Navigator, and can see the table descriptions of all the three tables in the Structure tab, but can not see any rows in any of the three tables on the Data tab. (I can query the tables and get expected returns in sqlplus, though).
I have three tables in the schema, with foreign key constraints. When inserting rows into the empty tables, I use saved scripts that contain the INSERT command lines, such as
INSERT INTO BILL VALUES ('LDAP_UID', 'FIRST_NAME', 'LAST_NAME', ....);The saved scripts contain up to more than 20,000 lines. When these scripts are run (such as SQL> @fill_bill.sql), in addition to the "1 row created" lines, I also saw long lines flashing by on the screen. These must be some error messages. But they flashed by too fast I could not catch any of them.
Is there any way to capture the messages in a log file so I can examine them afterwards. Or somehow have the execution of the sql script halted automatically upon encountering a culprit INSERT statement in the script so that I can see which line has what problem?
Thanks a lot!
Newman

Answer 1

Hi, Shay:
The column name in the table is LDAP_UID. In the entity object the name of the attribute for the column is LdapUid. The WHERE clause I used is: LdapUid=lower(:TheCurrentUser). I clicked Test button to test the WHERE clause. When the error pops up, I clicked the Help button and the explanation is:
View Object SQL Query Statement
    This area displays the view object SQL, to the line where the error occurred. For view objects,
    this is the view object's query. For view links, it is the destination view object's query, as
    modified by the view link's WHERE clause. In either case, null is passed in for all parameters
    (such as WHERE clause parameters in a view object or source attributes in a view link). This explanation made me think that the test query did not receive any return.
Again, is there a way to capture the errors in a log file when executing the sql INSERT statements?
Thanks!
Newman