Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Fred Prose — — source: Usenet: comp.databases.informix
We have run into similar problems, and not just with this release. In
our case we had Stored Procedures that would not export our and import
back in due to special characters.
We learned a trick that can save you hours of watching a dbimport work
only to see it fail like you did.
We run a 'test fire'. Before you do the real import you do a simple
create database (in the dbspace you planned on putting it) and then
run the .SQL file as a script through dbaccess. This process takes
seconds or a few minutes and will check everything for syntax.
↪ replying to Fred Prose
Hari Gupta — — source: Usenet: comp.databases.informix
Sound an excellent trick. I will certainly try this.
Hari
"Fred Prose" <fprose@hotmail.com> wrote in message
news:195a4770.0310081229.153fe1e8@posting.google.com...
> We have run into similar problems, and not just with this release. In
> our case we had Stored Procedures that would not export our and import
> back in due to special characters.
>
> We learned a trick that can save you hours of watching a dbimport work
> only to see it fail like you did.
>
> We run a 'test fire'. Before you do the real import you do a simple
> create database (in the dbspace you planned on putting it) and then
> run the .SQL file as a script through dbaccess. This process takes
> seconds or a few minutes and will check everything for syntax.
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.