The rename of the T140A to T140 helped but did not completely solve the issue. We need to go back to the latest backup and roll forward until just before I tired to import the forms. I'm going to need to take a closer look at the field definitions between the two servers. I thought that the fields that were giving me issues were the same. Dave
________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Shellman, David Sent: Wednesday, May 30, 2007 8:31 AM To: [email protected] Subject: Re: ORA-00942: table or view does not exist ** Nope. The field is in the table. It's a display only field. When I would delete this field, the error would move to the next field in the sequence. Dave ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Sean Garrison Sent: Wednesday, May 30, 2007 8:27 AM To: [email protected] Subject: Re: ORA-00942: table or view does not exist ** It looks like one of 2 things are going on .... 1you removed a field with id of 536870914 but it still exists in the view or 2 the view is referencing field 536870914 but does not exist in the underlying table. Either one true? Thanks, Sean "Shellman, David" <[EMAIL PROTECTED]> Sent by: "Action Request System discussion list(ARSList)" <[email protected]> 05/30/2007 07:16 AM Please respond to [email protected] To [email protected] cc Subject ORA-00942: table or view does not exist ** I was updating a table last night with a def file. I ran into problems with some of the fields. Odd errors that didn't make sense like ORA-00904: "C536870914": invalid identifier. Being a good admin, I exported the forms before I made the update. I'm still getting the invalid identifier errors but I'm also getting the ORA-00942 errors. It looks like with the update, the table was renamed to 140A as I would have expected but we ran out of temp space and the process didn't complete. We're stuck and can't update the form because it sort of doesn't exist from the admin tool perspective. I can see the form. I can open it. I can add or delete a field but the saves error because the view doesn't exist. Anyone run across this situation before? I think I understand what we need to do but It's been a long night so I need folks to look over my shoulder while support is pouring over the arerror and sql log files. Here's what I think we need to do: Shut down the app server. Back up the database. Rename the 140A table to 140. Reapply the definition files to back out the failed changes. Lack of sleep has made my brain fuzzy but does this sound like what needs to be done? Dave Dave Shellman Phone: (717) 810-3687 Fax: (717) 810-2124 email: [EMAIL PROTECTED] tyco/Electronics A tyco International LTD Company MS 161-043 PO Box 3608 Harrisburg, PA 17105-3607 __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
