Recently I loaded some localisation patches and followed the normal procedure. We have BaaN 4c4 (in3) on Windows NT and SQL server 7.0

On reconfiguring tables I found 2 tables not loaded properly and the requisite R.dump was created for them.

When I tried the command bdbreconfig -N tdput901100+ -nm I got error 520 ie error during buffered updates.

On checking the event viewer I got the following message
"Event Type: Error
Event Source: Baan
Event Category: Msql7_srv
Event ID: 1000
Date: 29/09/2004
Time: 2:02:00 PM
User: VMLGROUP\baan
Computer: VMPL
Description:
Env Bse (c:\Baan)
Prog msql7_srv file \db\servers\MSQL\msql_lev1.c # 945
Keyword Date out of range
Username baan type S language 2
Process 0x28f
Lasterror 203 (The system could not find the environmentoption that was entered.)
Errno 0
bdberrno 0
Message
dbs_errno = 205 Error 205 occurred:
bshell date 11371136/11369161/0001 (538976288 days) is not supported. The valid supported range of dates are from 02/01/1753 (639907 days) to 31/12/9999 (3652059 days) [dd/mm/yyyy].
DBMS Input: Data out of range for R_INS on dbo.ttdpur901100.
Flushed at \db\servers\MSQL\msql_row.c : #264."

IF in the R.dump the date is out of range - Can I do something to restore this table from this dump?

Yeah I know what you are thinking but unfortunately I do not have the current backup of the table ...

Thanks in advance

That sort of thing happens when your DD/Domain doesn't match with
the dump.. [i.e., random out of range errors... ]

You need the original table def and domainfiles used when you created
the R file.. since you were doing a convert/create to runtime, it moved the .new files in palce..

You're on windows / sql so that's a little bit more complicated ( have to make sure A) stored procedure is dropped and B) table DD/domain aren't in shared memory).

One thing you could try first though would be to send the -Z or -R options to bdbreconfig
bdbreconfig -Z -N<table>+ -C<company>
bdbreconfig -R -N<table>+ -C<company>

-Z is supposed to roll back and -R is supposed to roll forward
but it seems these change a lot..

Anyway, this is a difficult one to walk through in a forum, if you've got a support contract give 'em a call.

Dave

Hi Dave,

just out of curiosity: In SQL Server there is a stored procedure involved, when you do CRDD?

What is it doing?

Regards

markus

Hi Markus,

the stored procedures handle inserts and updates in tables, so when a table is created, a stored procedure gets created with it.. I think its for performance or something..

But the problem is that the stored procedures don't always get dropped properly after/during a reconfig, so they end up having the wrong/old picture of the table in them..

Dave

What happens with the bdbreconfig + - option is, that instead the dd.old was used the normal dd was used, then matched against the R.-file (and then afterwards reconfigured due to a dd.new-file). The 205 error occur during the matching-stage. So the dd.old points us all to a wrong thinking.

How to solve it is easy now. Example is table tcmcs003100(means comp. 100 - belongs to Packagecombiantion b40ocdev).

Under /baanerp/dict/ddb50ocdev and then in directory dtcmcs you have the original situation for the dd´s:

dtcmcs003 x bytes
dtcmcs003.old y bytes

I have copied:
cp dtcmcs003 dtcmcs003.new
cp dtcmcs003.old dtcmcs003

and then works in $BSE/tmp the bdbreconfig6.2 -Ntcmcs003100+ perfect