Longtx transaction log help
Posted in 2005
Topics: Storage & Space Management, Server Administration, Transactions, Locking & Isolation, Logging & Checkpoints
I am trying to move some data to a 9.4UC5 server and am stuck on the indexing
piece. I used myschema and dbcopy from Art to migrate the data. The dbcopy
went fine but when I apply the 2nd schema which has the indexes I keep getting a
long transaction error.
I have 195 transaction logs configured when I run onstat -l which all look like
below:
address number flags uniqid begin size used %used
7d743c78 193 U-B---- 1568 2:240053 1250 1250 100.00
7d743cc0 194 U-B---- 1569 2:241303 1250 1250 100.00
7d743d08 195 U-B---- 1570 2:242553 1250 1250 100.00
195 active, 195 total
onconfig:
# Root Dbspace Configuration
ROOTNAME rootdbs # Root dbspace nameROOTPATH /dev/informix/dbroot
ROOTOFFSET 0 # Offset of root dbspace into device (Kbytes)
ROOTSIZE 400000 # Size of root dbspace (Kbytes)
# Disk Mirroring Configuration Parameters
MIRROR 0 # Mirroring flag (Yes = 1, No = 0)
MIRRORPATH # Path for device containing mirrored root
MIRROROFFSET 0 # Offset into mirrored device (Kbytes)
# Physical Log Configuration
PHYSDBS dbplog # Location (dbspace) of physical log
PHYSFILE 400000 # Physical log file size (Kbytes)
# Logical Log Configuration
LOGFILES 195 # Number of logical log files
LOGSIZE 2500 # Logical log size (Kbytes)
onstat -d
IBM Informix Dynamic Server Version 9.40.UC5 -- On-Line -- Up 00:30:05 -- 1909760 Kbytes
Dbspaces
address number flags fchunk nchunks flags owner name
7d10e7d8 1 0x20001 1 1 N informix rootdbs
7d744c58 2 0x20001 2 1 N informix dblog
7d744da8 3 0x20001 3 1 N informix dbplog
7d630018 4 0x42001 4 1 N TB informix dbtmp
7d630168 5 0x60001 5 1 N B informix wmsnj
7d6302b8 6 0x60001 6 1 N B informix wmsmi
7d630408 7 0x60001 7 3 N B informix db1
7d630558 8 0x60001 10 1 N B informix dbtest
8 active, 2047 maximum
Chunks
address chunk/dbs offset size free bpages flags pathname
7d10e928 1 1 0 200000 197324 PO-- /dev/infor
mix/dbroot
7d743d50 2 2 0 400000 156197 PO-- /dev/infor
mix/dblog
7d744018 3 3 0 1000000 799947 PO-- /dev/infor
mix/dbplog
7d7441a0 4 4 0 4000000 3999397 PO-B /dev/infor
mix/dbtmp
7d744328 5 5 0 10000000 5702511 PO-B /dev/infor
mix/wmsnj
7d7444b0 6 6 0 10000000 9999947 PO-B /dev/infor
mix/wmsmi
7d744638 7 7 0 25000000 2071 PO-B /dev/infor
mix/db1
7d7447c0 8 7 0 25000000 593669 PO-B /dev/infor
mix/db2
7d744948 9 7 0 25000000 8356125 PO-B /dev/infor
mix/db3
7d744ad0 10 8 0 25000000 23841927 PO-B /dev/infor
mix/db4
10 active, 2047 maximum
On Fri, 22 Apr 2005 15:27:17 -0400, Gary Quiring <gquiring@msn.com> wrote: Ok the brain phart has been identified. I am moving data for a testing thing, I did the move a few weeks (with no logging) applied the indexes walked away and just assumed it finished and then turned on logging. We started testing and found that many indexes were missing. The 2nd part of the schema never finished due to a dup key error. Somehow my 40+ brain just never saw the light. Thanks for the help Gary Q