RE: Case of the Missing Rows

[Weiss, Rick]

Title: Message

Nope, .BAD file is empty, I have been experimenting this morning with cloning the table as suggested earlier, but every DDL statement against the table drops the rows (#'s 70-1417) of the ID PK Column. Still working on that angle   Rick Weiss -----Original Message----- From: Ruth Gramolini [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 28, 2003 8:55 AM To: Multiple recipients of list ORACLE-L Subject: Re: Case of the Missing Rows Could they be in the .bad file?  I have had stuff go there if a column was too long or something.   Ruth ----- Original Message ----- From: Tim Gorman To: Multiple recipients of list ORACLE-L Sent: Monday, January 27, 2003 7:43 PM Subject: Re: Case of the Missing Rows My guess is that SQL*Loader didn't really load 88,640 rows, but rejected or discarded about 1400 of them?   ----- Original Message ----- From: Weiss, Rick To: Multiple recipients of list ORACLE-L Sent: Monday, January 27, 2003 4:53 PM Subject: Case of the Missing Rows I have a recurring, repeatable problem I was wondering about its cause. Oracle 9.2.0.1 on W2K Professional (SP2) Dell Optiplex workstation Pentium 4 Step 1 - I do an SQLLDR process that loads 88640 rows to a table Step 2 - SQL*Plus session - SELEC COUNT(*) from the table returns 88640 rows Step 3 - Do an EXP on the table (to allow fall back to this point) - only exports 87257 rows Step 4 - SQL*Plus session again - SELEC COUNT(*) from the table returns 87257 rows No one else has access to the database.  There are no unusual entries in the alert log. There is nothing I have found in the UDUMP or BDUMP directories that would help. Has anyone else experienced this?? Thanks Rick Weiss