Customer with web_user.id of 563579 was created yesterday, 11-MAR-01, and the Join app allowed what appears to be a single character wide space to be entered as in the web_user_personal_info.last_name field. This breaks things very badly, so the form validation should disallow any character that is actually a just a space in any of the required fields (first name, last name, address, city, state, zip, phone). I update this web user's last name to be '.', and this allowed the Oracle import processes to continue.
Another example: web_user.id = 571196 In this case the web_user_personal_info.last_name appears to be a 6 character wide null: LENGTH(LAST_NAME) ----------------- 6
New symptom: web_user_site_info.address1 is a 14 character wide null: select length(ADDRESS1) from WEB_USER_SITE_INFO where id = 1556680 LENGTH(ADDRESS1) ---------------- 14 Major problems here. Why would the Join process transform characters into nulls?
Another example of the problem: web_user_site_info.id = 1603348 web_user.id = 595136 ADDRESS1 and CITY were both null. Already fixed these two since they were holding up the mirror process. Is this the Join process or the RHN reg client?
Two more examples from today: WEB_USER_PERSONAL_INFO.ID = 595233 FIRST_NAMES and LAST_NAME are ' ' -- WEB_USER_SITE_INFO.ID 987736 and 987737 both have ' ' in ADDRESS1.
Are we any closer to knowing what is causing this? Marty have you seen any more examples of this happening on the site?
I send an email to Adrian and Cristian regarding this problem back in March. Subject: Re: [Bug 31557] Changed - Join processes allowing some sort of NULL? Date: Mon, 19 Mar 2001 17:58:18 -0800 From: Eric Chen <echen> To: "adrian" <adrian>, Cristian Gafton <gafton>, "mmesser" <mmesser> References: 1 Adrian, I finally traced the problem to rhn_register and was able to create an account empty last name from my desktop, can you take a look at this.
Jay, webdev isn't CC'ing to itself anymore. I just saw this. I have no new reports of this.
Closing out this issue.