Re: [Info-Ingres] bad database name?
- From: martin.bowes@xxxxxxxxxxxxx
- Date: Thu, 26 Jul 2007 12:35:31 +0100
Hi Everyone, Me again...
I created a new database the other day, no problems with the createActually there were problems with loading data into the database. A
table which didn't load correctly was a btree with a hash partition,
6million rows and two of its columns were long varchar - in fact it
flagged a log full condition. The rollback clearly had some trouble as
every subsequent command in the copy.in was failed with
E_US087C You are already in a transaction, try a savepoint.
E_SC0206 An internal error prevents further processing of this query.
I have found that if I alter the copy.in to create the table with no
partitions, do the copy and then partition the table that the load is
successful and a ckpdb wil be okay.
Now that's just gott be a bug of some type...
Marty
--
Random Farscape Quote #3:
John - If this is part of some sick experiment, I'm going to bill them for
the therapy.
- Prev by Date: [Info-Ingres] bad database name?
- Next by Date: Visual DBA
- Previous by thread: [Info-Ingres] bad database name?
- Next by thread: Visual DBA
- Index(es):
Relevant Pages
|
|
