Join IIUG
 for   
 

Informix News
18 Nov 13 - ZDNet - Top 20 mobile skills in demand... Read
09 Sep 13 - telecompaper - Shaspa and Tatung have shown a new smart home platform at Ifa in Berlin. Powered by the IBM Informix software... Read
06 Sep 13 - IBM data magazine - Mission Accomplished - Miami, Florida will be the backdrop for the 2014 IIUG Informix Conference... Read
01 Feb 13 - IBM Data Magazine - Are your database backups safe? Lester Knutsen (IBM Champion) writes about database back up safety using "archecker"... Read
14 Nov 12 - IBM - IBM's Big Data For Smart Grid Goes Live In Texas... Read
3 Oct 12 - The Financial - IBM and TransWorks Collaborate to Help Louisiana-Pacific Corporation Achieve Supply Chain Efficiency... Read
28 Aug 12 - techCLOUD9 - Splunk kicks up a SaaS Storm... Read
10 Aug 12 - businessCLOUD9 - Is this the other half of Cloud monitoring?... Read
3 Aug 12 - IBM data management - Supercharging the data warehouse while keeping costs down IBM Informix Warehouse Accelerator (IWA) delivers superior performance for in-memory analytics processing... Read
2 Aug 12 - channelbiz - Oninit Group launches Pay Per Pulse cloud-based service... Read
28 May 12 - Bloor - David Norfolk on the recent Informix benchmark "pretty impressive results"... Read
23 May 12 - DBTA - Informix Genero: A Way to Modernize Informix 4GL Applications... Read
9 Apr 12 - Mastering Data Management - Upping the Informix Ante: Advanced Data Tools... Read
22 Mar 12 - developerWorks - Optimizing Informix database access... Read
14 Mar 12 - BernieSpang.com - International Informix User Group set to meet in San Diego... Read
1 Mar 12 - IBM Data Management - IIUG Heads West for 2012 - Get ready for sun and sand in San Diego... Read
1 Mar 12 - IBM Data Management - Running Informix on Solid-State Drives.Speed Up Database Access... Read
26 Feb 12 - BernieSpan.com - Better results, lower cost for a broad set of new IBM clients and partners... Read
24 Feb 12 - developerWorks - Informix Warehouse Accelerator: Continuous Acceleration during Data Refresh... Read
6 Feb 12 - PRLOG - Informix port delivers unlimited database scalability for popular SaaS application ... Read
2 Feb 12 - developerWorks - Loading data with the IBM Informix TimeSeries Plug-in for Data Studio... Read
1 Feb 12 - developerWorks - 100 Tech Tips, #47: Log-in to Fix Central... Read
13 Jan 12 - MC Press online - Informix Dynamic Server Entices New Users with Free Production Edition ... Read
11 Jan 12 - Computerworld - Ecologic Analytics and Landis+Gyr -- Suitors Decide to Tie the Knot... Read
9 Jan 12 - planetIDS.com - DNS impact on Informix / Impacto do DNS no Informix... Read
8 Sep 11 - TMCnet.com - IBM Offers Database Solution to Enable Smart Meter Data Capture... Read
1 Aug 11 - IBM Data Management Magazine - IIUG user view: Happy 10th anniversary to IBM and Informix... Read
8 Jul 11 - Database Trends and Applications - Managing Time Series Data with Informix... Read
31 May 11 - Smart Grid - The meter data management pitfall utilities are overlooking... Read
27 May 11 - IBM Data Management Magazine - IIUG user view: Big data, big time ( Series data, warehouse acceleration, and 4GLs )... Read
16 May 11 - Business Wire - HiT Software Announces DBMoto for Enterprise Integration, Adds Informix. Log-based Change Data Capture... Read
21 Mar 11 - Yahoo! Finance - IBM and Cable&Wireless Worldwide Announce UK Smart Energy Cloud... Read
14 Mar 11 - MarketWatch - Fuzzy Logix and IBM Unveil In-Database Analytics for IBM Informix... Read
11 Mar 11 - InvestorPlace - It's Time to Give IBM Props: How many tech stocks are up 53% since the dot-com boom?... Read
9 Mar 11 - DBTA - Database Administration and the Goal of Diminishing Downtime... Read
2 Feb 11 - DBTAs - Informix 11.7 Flexible Grid Provides a Different Way of Looking at Database Servers... Read
27 Jan 11 - exactsolutions - Exact to Add Informix Support to Database Replay, SQL Monitoring Solutions... Read
25 Jan 11 - PR Newswire - Bank of China in the UK Works With IBM to Become a Smarter, Greener Bank... Read
12 Oct 10 - Database Trends and Applications - Informix 11.7: The Beginning of the Next Decade of IBM Informix... Read
20 Sep 10 - planetIDS.com - ITG analyst paper: Cost/Benefit case for IBM Informix as compared to Microsoft SQL Server... Read
20 Jul 10 - IBM Announcements - IBM Informix Choice Edition V11.50 helps deploy low-cost scalable and reliable solutions for Apple Macintosh and Microsoft Windows... Read
20 Jul 10 - IBM Announcements - Software withdrawal: Elite Support for Informix Ultimate-C Edition... Read
24 May 10 - eWeek Europe - IBM Supplies Database Tech For EU Smart Grid... Read
23 May 10 - SiliconIndia - IBM's smart metering system allows wise use of energy... Read
21 May 10 - CNET - IBM to help people monitor energy use... Read
20 May 10 - ebiz - IBM Teams With Hildebrand To Bring Smart Metering To Homes Across Britain... Read
19 May 10 - The New Blog Times - Misurare il consumo energetico: DEHEMS è pronto... Read
19 May 10 - ZDNet - IBM software in your home? Pact enables five-city smart meter pilot in Europe... Read
17 March 10 - ZDNet (blog) David Morgenstern - TCO: New research finds Macs in the enterprise easier, cheaper to manage than... Read
17 March 2010 - Virtualization Review - ...key components of Big Blue's platform to the commercial cloud such as its WebSphere suite of application ser vers and its DB2 and Informix databases... Read
10 February 2010 - The Wall Street Journal - International Business Machines is expanding an initiative to win over students and professors on its products. How do they lure the college crowd?... Read


End of Support Dates

IIUG on Facebook IIUG on Twitter

[ View Thread ] [ Post Response ] [ Return to Index ] [ Read Prev Msg ] [ Read Next Msg ]

IDS Forum

Re: dbimport EXTREMELY slow

Posted By: Obnoxio The Clown
Date: Wednesday, 13 September 2006, at 9:32 p.m.

In Response To: dbimport EXTREMELY slow (Quman)

Quman said:
>
> I am doing dbimport with IDS 10UC5 on AIX 5.3.
>
> Watched,
>
> large number(100,000+) of dirty pages were SLOWLY written to disk.
>
> piece of online log,
>
> 20:08:47 Maximum server connections 0
> 20:08:47 On-Line Mode
> 20:15:15 Fuzzy Checkpoint Completed: duration was 56 seconds, 1
> buffers not flushed.
> 20:15:15 Checkpoint loguniq 12, logpos 0xcb7050, timestamp: 0x54d481b
>
> 20:15:15 Maximum server connections 1
> 21:00:24 Fuzzy Checkpoint Completed: duration was 2409 seconds, 7
> buffers not flushed.
> 21:00:24 Checkpoint loguniq 12, logpos 0xccb0b0, timestamp: 0x5eba28f
>
> 21:00:24 Maximum server connections 1
> 21:01:54 Checkpoint Completed: duration was 61 seconds.
> 21:01:54 Checkpoint loguniq 12, logpos 0xd21018, timestamp: 0x601652a
>
> 21:01:54 Maximum server connections 1
> 21:01:56 IBM Informix Dynamic Server Stopped.
>
> See the above LONG check point!
>
> config file attached.
>
> Any suggestions are deeply appreciated!

Run the dbimport with logging disabled.

Given the large number of pages you are flushing, why do you think the
checkpoint is long?

> Thanks
> Quman
>
> # Root Dbspace Configuration
>
> ROOTNAME rootdbs # Root dbspace name
> ROOTPATH /usr/informix/dev-links/int1/DBROOT_INT1 # Path for
> device containing root dbspace
> ROOTOFFSET 4 # Offset of root dbspace into device (Kbytes)
> ROOTSIZE 512000 # Size of root dbspace (Kbytes)
>
> # Disk Mirroring Configuration Parameters
>
> MIRROR 1 # Mirroring flag (Yes = 1, No = 0)
> MIRRORPATH /usr/informix/dev-links/int1/MDBROOT_INT1 # Path
> for device containing mirrored root
> MIRROROFFSET 4 # Offset into mirrored device (Kbytes)
>
> # Physical Log Configuration
>
> PHYSDBS dbphylog # Location (dbspace) of physical log
> PHYSFILE 890000 # Physical log file size (Kbytes)
> #PHYSDBS rootdbs # Location (dbspace) of physical log
> #PHYSFILE 20000 # Physical log file size (Kbytes)
>
> # Logical Log Configuration
>
> LOGFILES 140 # Number of logical log files
> #LOGSIZE 20000 # Logical log size (Kbytes)
> LOGSIZE 160000 # Logical log size (Kbytes)
> LOG_BACKUP_MODE MANUAL # Logical log backup mode (MANUAL, CONT)
>
> # Tablespace Tablespace Configuration in Root Dbspace
>
> TBLTBLFIRST 0 # First extent size (Kbytes) (0 = default)
> TBLTBLNEXT 0 # Next extent size (Kbytes) (0 = default)
>
> # Security
> # DBCREATE_PERMISSION:
> # By default any user can create a database. Uncomment DBCREATE_PERMISSON
> to
> # limit database creation to a specific user. Add a new
> DBCREATE_PERMISSION
> # line for each permitted user.
>
> DBCREATE_PERMISSION informix
>
> # DB_LIBRARY_PATH:
> # When loading a (C or C++) shared object (for a UDR or UDT), IDS checks
> that
> # the user-specified path starts with one of the directory prefixes listed
> in
> # the comma-separated list of prefixes in DB_LIBRARY_PATH. The string
> # "$INFORMIXDIR/extend" must be included in DB_LIBRARY_PATH in order for
> # extensibility and IBM supplied blades to work correctly.
>
> DB_LIBRARY_PATH $INFORMIXDIR/extend
>
> # IFX_EXTEND_ROLE:
> # 0 (or off) => Disable use of EXTEND role to control who can register
> # external routines.
> # 1 (or on) => Enable use of EXTEND role to control who can register
> # external routines. This is the default behaviour.
> #
> IFX_EXTEND_ROLE 1 # To control the usage of EXTEND role.
>
> # Diagnostics
>
> MSGPATH /dbbackup/online_log/online_int1.log # System message
> log file path
> CONSOLE /dbbackup/online_log/console # System console message path
>
> # To automatically backup logical logs, edit alarmprogram.sh and set
> # BACKUPLOGS=Y
> ALARMPROGRAM /usr/informix/etc/alarmprogram.sh # Alarm program path
> ALRM_ALL_EVENTS 0 # Triggers ALARMPROGRAM for any event occur
> TBLSPACE_STATS 1 # Maintain tblspace statistics
>
> # System Archive Tape Device
>
> TAPEDEV /dbbackup/ontape/ontape_int1 # Tape device path
> TAPEBLK 32 # Tape block size (Kbytes)
> #TAPESIZE 10240 # Maximum amount of data to put on tape (Kbytes)
> TAPESIZE 0 # Maximum amount of data to put on tape (Kbytes)
>
> # Log Archive Tape Device
>
> LTAPEDEV /dev/null # Log tape device path
> #LTAPEDEV /dbbackup/logbackup/logbackup_int1 # Log tape device path
> LTAPEBLK 32 # Log tape block size (Kbytes)
> #LTAPESIZE 10240 # Max amount of data to put on log tape (Kbytes)
> LTAPESIZE 0 # Max amount of data to put on log tape (Kbytes)
>
> # Optical
>
> STAGEBLOB # Informix Dynamic Server staging area
>
> # System Configuration
>
> SERVERNUM 10 # Unique id corresponding to a OnLine instance
> DBSERVERNAME osdint1_tcp # Name of default database server
> DBSERVERALIASES osdint1 # List of alternate dbservernames
> #NETTYPE # Configure poll thread(s) for nettype
> NETTYPE ipcshm,1,50,CPU # Configure poll thread(s) for nettype
> NETTYPE soctcp,2,100,NET # Configure poll thread(s) for nettype
> DEADLOCK_TIMEOUT 60 # Max time to wait of lock in distributed env.
> RESIDENT 0 # Forced residency flag (Yes = 1, No = 0)
>
> MULTIPROCESSOR 1 # 0 for single-processor, 1 for multi-processor
> SINGLE_CPU_VP 0 # If non-zero, limit number of cpu vps to one
>
> # Shared Memory Parameters
>
> LOCKS 200000 # Maximum number of locks
> PHYSBUFF 32 # Physical log buffer size (Kbytes)
> LOGBUFF 32 # Logical log buffer size (Kbytes)
> CLEANERS 32 # Number of buffer cleaner processes
> SHMBASE 0x40000000L # Shared memory base address
> SHMVIRTSIZE 307200 # initial virtual shared memory segment size
> SHMADD 32768 # Size of new shared memory segments (Kbytes)
> EXTSHMADD 8192 # Size of new extension shared memory
> segments (Kbytes)
> SHMTOTAL 0 # Total shared memory (Kbytes). 0=>unlimited
> CKPTINTVL 300 # Check point interval (in sec)
> TXTIMEOUT 300 # Transaction timeout (in sec)
> STACKSIZE 64
>
> # Dynamic Logging
> # DYNAMIC_LOGS:
> # 2 : server automatically add a new logical log when necessary. (ON)
> # 1 : notify DBA to add new logical logs when necessary. (ON)
> # 0 : cannot add logical log on the fly. (OFF)
> #
> # When dynamic logging is on, we can have higher values for
> LTXHWM/LTXEHWM,
> # because the server can add new logical logs during long transaction
> rollback.
> # However, to limit the number of new logical logs being added,
> LTXHWM/LTXEHWM
> # can be set to smaller values.
> #
> # If dynamic logging is off, LTXHWM/LTXEHWM need to be set to smaller
> values
> # to avoid long transaction rollback hanging the server due to lack of
> logical
> # log space, i.e. 50/60 or lower.
> #
> # In case of system configured with CDR, the difference between LTXHWM and
> # LTXEHWM should be atleast 30% so that we could minimize log overrun
> issue.
>
> DYNAMIC_LOGS 2
> LTXHWM 30
> LTXEHWM 60
>
> # System Page Size
> # BUFFSIZE - OnLine no longer supports this configuration parameter.
> # To determine the page size used by OnLine on your platform
> # see the last line of output from the command, 'onstat -b'.
>
> # Recovery Variables
> # OFF_RECVRY_THREADS:
> # Number of parallel worker threads during fast recovery or an offline
> restore.
> # ON_RECVRY_THREADS:
> # Number of parallel worker threads during an online restore.
>
> OFF_RECVRY_THREADS 10 # Default number of offline worker threads
> ON_RECVRY_THREADS 1 # Default number of online worker threads
>
> # Data Replication Variables
> # DRAUTO: 0 manual, 1 retain type, 2 reverse type
> DRAUTO 0 # DR automatic switchover
> DRINTERVAL 30 # DR max time between DR buffer flushes (in sec)
> DRTIMEOUT 30 # DR network timeout (in sec)
> DRLOSTFOUND /usr/informix/etc/dr.lostfound # DR lost+found file path
> DRIDXAUTO 0 # DR automatic index repair. 0=off, 1=on
>
> # CDR Variables
> CDR_EVALTHREADS 1,2 # evaluator threads (per-cpu-vp,additional)
> CDR_DSLOCKWAIT 5 # DS lockwait timeout (seconds)
> CDR_QUEUEMEM 4096 # Maximum amount of memory for any CDR queue (Kbytes)
> CDR_NIFCOMPRESS 0 # Link level compression (-1 never, 0 none, 9 max)
> CDR_SERIAL 10,1 # Serial Column Sequence
> CDR_DBSPACE # dbspace for syscdr database
> CDR_QHDR_DBSPACE dberdata # CDR queue dbspace (default
> same as catalog)
> CDR_QDATA_SBSPACE dbersbdata # List of CDR queue smart blob spaces
>
> # CDR_MAX_DYNAMIC_LOGS
> # -1 => unlimited
> # 0 => disable dynamic log addition
> # >0 => limit the no. of dynamic log additions with the specified value.
> # Max dynamic log requests that CDR can make within one server session.
>
> CDR_MAX_DYNAMIC_LOGS 0 # Dynamic log addition disabled by default
>
> # Backup/Restore variables
> BAR_ACT_LOG /usr/informix/bar_act.log # ON-Bar Log file - not in /tmp
> please
> BAR_DEBUG_LOG /usr/informix/bar_dbug.log # ON-Bar Debug Log - not in /tmp
> please
> BAR_MAX_BACKUP 0
> BAR_RETRY 1
> BAR_NB_XPORT_COUNT 20
> BAR_XFER_BUF_SIZE 31
> RESTARTABLE_RESTORE ON
> BAR_PROGRESS_FREQ 0
>
> # Informix Storage Manager variables
> ISM_DATA_POOL ISMData
> ISM_LOG_POOL ISMLogs
>
> # Read Ahead Variables
> RA_PAGES # Number of pages to attempt to read ahead
> RA_THRESHOLD # Number of pages left before next group
>
> # DBSPACETEMP:
> # OnLine equivalent of DBTEMP for SE. This is the list of dbspaces
> # that the OnLine SQL Engine will use to create temp tables etc.
> # If specified it must be a colon separated list of dbspaces that exist
> # when the OnLine system is brought online. If not specified, or if
> # all dbspaces specified are invalid, various ad hoc queries will create
> # temporary files in /tmp instead.
>
> DBSPACETEMP # Default temp dbspaces
>
> # DUMP*:
> # The following parameters control the type of diagnostics information
> which
> # is preserved when an unanticipated error condition (assertion failure)
> occurs
> # during OnLine operations.
> # For DUMPSHMEM, DUMPGCORE and DUMPCORE 1 means Yes, 0 means No.
>
> #DUMPDIR /usr/informix/tmp # Preserve diagnostics in this directory
> DUMPDIR /tmp # Preserve diagnostics in this directory
> DUMPSHMEM 1 # Dump a copy of shared memory
> DUMPGCORE 0 # Dump a core image using 'gcore'
> DUMPCORE 0 # Dump a core image (Warning:this aborts OnLine)
> DUMPCNT 1 # Number of shared memory or gcore dumps for
>
> # a single user's session
>
> FILLFACTOR 90 # Fill factor for building indexes
>
> # method for OnLine to use when determining current time
> USEOSTIME 0 # 0: use internal time(fast), 1: get time from OS(slow)
>
> # Parallel Database Queries (pdq)
> MAX_PDQPRIORITY 100 # Maximum allowed pdqpriority
> DS_MAX_QUERIES # Maximum number of decision support queries
> DS_TOTAL_MEMORY # Decision support memory (Kbytes)
> DS_MAX_SCANS 1048576 # Maximum number of decision support scans
> DS_NONPDQ_QUERY_MEM 128 # Non PDQ query memory (Kbytes)
> DATASKIP # List of dbspaces to skip
>
> # OPTCOMPIND
> # 0 => Nested loop joins will be preferred (where
> # possible) over sortmerge joins and hash joins.
> # 1 => If the transaction isolation mode is not
> # "repeatable read", optimizer behaves as in (2)
> # below. Otherwise it behaves as in (0) above.
> # 2 => Use costs regardless of the transaction isolation
> # mode. Nested loop joins are not necessarily
> # preferred. Optimizer bases its decision purely
> # on costs.
> OPTCOMPIND 0 # To hint the optimizer
>
> DIRECTIVES 1 # Optimizer DIRECTIVES ON (1/Default) or OFF (0)
>
> ONDBSPACEDOWN 2 # Dbspace down option: 0 = CONTINUE, 1 = ABORT, 2 = WAIT
> OPCACHEMAX 0 # Maximum optical cache size (Kbytes)
>
> # HETERO_COMMIT (Gateway participation in distributed transactions)
> # 1 => Heterogeneous Commit is enabled
> # 0 (or any other value) => Heterogeneous Commit is disabled
> HETERO_COMMIT 0
>
> SBSPACENAME dbsbdata00 # Default smartblob space name - this
> is where blobs
>
> # go if no sbspace is specified when the smartblob is
>
> # created. It is also used by some datablades as
>
> # the location to put their smartblobs.
> SYSSBSPACENAME dbsbdata01 # Default smartblob space for use by
> the Informix
>
> # Server. This is used primarily for Informix Server
>
> # system statistics collection.
>
> BLOCKTIMEOUT 3600 # Default timeout for system block
> SYSALARMPROGRAM /usr/informix/etc/evidence.sh # System Alarm program path
>
> # Optimization goal: -1 = ALL_ROWS(Default), 0 = FIRST_ROWS
> OPT_GOAL -1
>
> ALLOW_NEWLINE 0 # embedded newlines(Yes = 1, No = 0 or anything but 1)
>
> #Create Index Online Shared Memory usage limitation
> ONLIDX_MAXMEM 5120 # Per pool per index (Kbytes)
>
> #Timeout for client connection request
> LISTEN_TIMEOUT 10 # Timeout (in Seconds)
>
> #Following are the deprecated configuration parameters, instead of these
> #use BUFFERPOOL configuration parameter
> #BUFFERS, LRUS, LRU_MIN_DIRTY, LRU_MAX_DIRTY
>
> IFX_FOLDVIEW 0 # fold multiple tables or union all view with ansi joins
> #
> # The following are default settings for enabling Java in the database.
> # Replace all occurrences of /usr/informix with the value of $INFORMIXDIR.
>
> #VPCLASS jvp,num=1 # Number of JVPs to start with
> #VPCLASS cpu,num=6,aff=1-6 # CPUVPs configuration
> VPCLASS cpu,num=4 # CPUVPs configuration
> VPCLASS aio,num=2 # AIOVPs configuration , it only used
> by cooked chunk
>
> JVPJAVAHOME $INFORMIXDIR/extend/krakatoa/jre # JRE
> installation root directory
> JVPHOME $INFORMIXDIR/extend/krakatoa # Krakatoa installation directory
>
> JVPPROPFILE $INFORMIXDIR/extend/krakatoa/.jvpprops # JVP property file
> JVPLOGFILE $INFORMIXDIR/jvp.log # JVP log file.
>
> JDKVERSION 1.3 # JDK version supported by this server
>
> # The path to the JRE libraries relative to JVPJAVAHOME
> JVPJAVALIB /bin
>
> # The JRE libraries to use for the Java VM
>
> JVPJAVAVM hpi:jvm:java:net:zip:jpeg
>
> # use JVPARGS to change Java VM configuration
> #To display jni call
> #JVPARGS -verbose:jni
>
> # Classpath to use upon Java VM start-up (use _g version for debugging)
>
> #JVPCLASSPATH
> /usr/informix/extend/krakatoa/krakatoa_g.jar:/usr/informix/extend/krakatoa/jdbc_g.jar
> JVPCLASSPATH
> $INFORMIXDIR/extend/krakatoa/krakatoa.jar:/usr/informix/extend/krakatoa/jdbc.jar
>
> # The following parameters are related to the buffer pool
> BUFFERPOOL
> default,buffers=400000,lrus=64,lru_min_dirty=20.000000,lru_max_dirty=40.000000
> BUFFERPOOL
> size=4K,buffers=400000,lrus=64,lru_min_dirty=20.000000,lru_max_dirty=40.000000
>
>
> *******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
> --
> This message has been scanned for viruses and
> dangerous content by OpenProtect(http://www.openprotect.com), and is
> believed to be clean.
>

--
Bye now,
Obnoxio

"... no bill is required as no value was provided."
-- Christine Normile

--
This message has been scanned for viruses and
dangerous content by OpenProtect(http://www.openprotect.com), and is
believed to be clean.

Messages In This Thread

  • dbimport EXTREMELY slow
    Quman -- Wednesday, 13 September 2006, at 5:03 p.m.
    • Re: dbimport EXTREMELY slow
      ART KAGEL, BLOOMBERG/ 731 LEXIN -- Wednesday, 13 September 2006, at 5:16 p.m.
    • Re: dbimport EXTREMELY slow
      Obnoxio The Clown -- Wednesday, 13 September 2006, at 9:32 p.m.

[ View Thread ] [ Post Response ] [ Return to Index ] [ Read Prev Msg ] [ Read Next Msg ]

IDS Forum is maintained by Administrator with WebBBS 5.12.