fmorais
24th March 2003, 21:33
Hi,

I was trying to export some components and I got an error 512 message.

Just in case checked the 000 tables using
"ttad4232m000 - Check tables".

Error 512 is returning for ttadv304, ttadv335 and ttadv364

My environment is
Windows2000/SQL2000/BIVc4 (pset6.1c.06.05)

We've not done anything special on the system lately.

Looking at other threads, already tried:
-Restoring an old porting set (6.1c.06.01)
-Create RDD for tools with "also dump dd"

Problem stil occurs.

Thought about trying to export/import tables using bdbpre/bdbpost, removing in between the tables and respective procedures in MSQL Enterprise Manager but,
Won't I get the same error 512 somewhere on the export or on the import?


Can someone give a hand? (I'm now on a dead end...)

I was trying to avoid restoring a backup because it's not clear since when the problem exists.

Thanks
Fred

fmorais
24th March 2003, 21:37
Hi,

Just tried bdbpre:

"bdbpre -N ttadv304 -C 000 > dump.pre"

and is also givig error 512.


Fred

patvdv
24th March 2003, 22:33
Mmm, aren't these the tables that hold binary data for forms and reports? Did you ever get a 'index out of dims error' on these tables?

fmorais
24th March 2003, 23:28
Hi Pat,

Answering your question,

Did not notice any problems until today. Been developing new sessions forms and reports with no problems.

Did not try it today, since I noticed the problem.

Can this be a mismatch between the table and the corresponding stored procedure in MSQL? If so, can I delete and recreate the stored procedure? How?

Thanks
Fred

patvdv
24th March 2003, 23:57
Fred,

Not sure about what you said regarding the stored procedure. I just know that these tables can be an awful hassle when one of your reports/forms get saved in a wrong NLS setting. That can corrupt the data in the table which leads to the error I have described before.

Can you actually call up the report/form layouts you developed recently?

fmorais
25th March 2003, 14:22
Hi all

First of all, thanks Pat for your prompt assistance.
I discovered what the problem was:

It was related with the recent removal of a parameter in db_resource:

msql_65_shema:1

Please find full details in:

http://www.baanboard.com/baanboard/newreply.php?s=&action=newreply&threadid=9300


Thanks
Fred