das_k_tushar
18th December 2003, 15:06
We are facing one major problem,

When we access itemmaster by record by record, when the system found junk/multi byte character in the itemcode, the session terminates and send a message "Process 8- Fatal Error :Error 305 (Wrong row returned ) on SELECT, Can not continue.

We have able to locate the error. the records are combination of english and arabic character in the item code. we want to delete this records. even through GTM we are unable to access this records.

Looking for help.

Regards
Tushar

k_paga
19th December 2003, 08:11
Hi,
What BaaN help says is,
The table index could be corrupt for this error message.

If it is just selecting particular records from Item master,
maintain a signal code in Item master for the records you have identified as junk and give the condition in your select statement in the session to deselect the junk records.

It mite work if the index is not corrupted.

Else you can do a Reconfigure table before proceeding with the session.
NOTE:
1 Contact your system administrator befor eproceeding on this reconfigure
2 Mandatorily Reconfigure in single user mode(when no users logged into system).

Revert back if you have any queries before proceeding.
Have reconfigure as your last option.

Hitesh Shah
19th December 2003, 08:32
The tcitem domain is string and will never allow multibyte characters. So if there are multibyte characters in it , it will throw error 305.

Now u may do following in consultation with Baan support.

1. Export table using exchange (standard export may not work)
2. Import the clean data after dropping the table.

This should be done when nobody is working in Baan. Further also check about references.

das_k_tushar
21st December 2003, 15:26
Dear Hitesh,
Thanks for the help. We are also planning to take dump and reload. few clarification needed.

We will upload the data without referential integrity. if we do that it will take long time since we have more than 1.5 lacs itemcode. if we do that, is there any problem in future?

Regards
Tushar

Hitesh Shah
22nd December 2003, 10:09
u definitely need to repair reference counter and check referential integrity in ttaad4225m000 before users start using the system.