This is a discussion on RE: informix begginer on xp within the Informix forums, part of the Database Server Software category; --> Art, Is the rootsize big enough?.... Doing the basics... 51.2MB - 2 MB physlog = 49.2MB - 12MB logs ...
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Art, Is the rootsize big enough?.... Doing the basics... 51.2MB - 2 MB physlog = 49.2MB - 12MB logs = 37.2 MB. I think that's big enough in the olden days for a tiny engine on unix, but I know nothing of windows installs, and I think it was stated this is a 9.4 engine. Will informix on windows be ok with the truncated pathnames such as: > MSGPATH C:\PROGRA~1\Informix\ika.log # System message log file path > CONSOLE C:\PROGRA~1\Informix\conika.log # System console message path > BAR_ACT_LOG C:\PROGRA~1\Informix\bar_ika.log #Path of log file for Is the shmbase from the default ok? (SHMBASE 0xC000000L) [keyy@punkass.com]Iksatongafin, Check the machine notes for informix. They are in in your install dir... What's your XP system event viewer telling you when you try starting the DB? Check your system messages and such, maybe your XP machine is complaining. > MSGPATH C:\PROGRA~1\Informix\ika.log # System message log file path > CONSOLE C:\PROGRA~1\Informix\conika.log # System console message path If the DB is talking to you.... It'll probably be there, unless the "progra~1" truncations is confusing it. Art, Speaking of the truncated names..... Would this instance perhaps need DELIMIDENT set before startup... . Maybe, like unix, the tilde (~) is not understood without delimident and quotes? .....2 cents... Norma Jean -----Original Message----- From: owner-informix-list@iiug.org [mailto On Behalf Of Art S. Kagel Sent: Wednesday, November 10, 2004 5:52 PM To: informix-list@iiug.org Subject: Re: informix begginer on xp On Wed, 10 Nov 2004 13:43:05 -0500, iksatongafin wrote: Does the ROOTPATH file (C:\IFMXDATA\ika\rootdbs_dat.000) exist? Is it the full 51.2MB? If not, you killed the oninit too soon, the time spent was in creating and padding the initial chunk. It's one problem with using COOKED files for IDS chunks. Art S. Kagel > onconfig.ika > ---------------------- > #************************************************* ******************** > ***** > # > # INFORMIX SOFTWARE, INC. > # > # Title: onconfig.std > # Description: Informix Dynamic Server Configuration Parameters # > #************************************************* ******************** > ***** > > # Root Dbspace Configuration > > ROOTNAME rootdbs # Root dbspace name > ROOTPATH C:\IFMXDATA\ika\rootdbs_dat.000 # Path for device containing > ROOTOFFSET 0 # Offset of root dbspace into device ROOTSIZE 51200 # Size of root dbspace (Kbytes) > > # Disk Mirroring Configuration Parameters > > MIRROR 0 # Mirroring flag (Yes = 1, No = 0) MIRRORPATH # Path for MIRROROFFSET 0 # Offset into mirrored > > # Physical Log Configuration > > PHYSDBS rootdbs # Location (dbspace) of physical log > PHYSFILE 2000 # (Kbytes) > > # Logical Log Configuration > > LOGFILES 6 # Number of logical log files LOGSIZE 2000 # (Kbytes) LOG_BACKUP_MODE MANUAL > > # Diagnostics > > MSGPATH C:\PROGRA~1\Informix\ika.log > CONSOLE C:\PROGRA~1\Informix\conika.log > > # BACKUPLOGS=Y ALARMPROGRAM C:\PROGRA~1\Informix\etc\alarmprogram.bat > TBLSPACE_STATS 1 > > # SYSALARMPROGRAM - Full path of ... > > # System Archive Tape Device > TAPEDEV \\.\TAPE0 # Tape device path > TAPEBLK 16 # Tape block size (Kbytes) TAPESIZE 10240 # Maximum (Kbytes) > > # Log Archive Tape Device > LTAPEDEV NUL # Log tape device path > LTAPEBLK 16 # Log tape block size (Kbytes) LTAPESIZE 10240 # Max (Kbytes) > > # Optical > STAGEBLOB # Optical staging area > OPTICAL_LIB_PATH # ptical Subsystem driver DLL > > # System Configuration > SERVERNUM 0 DBSERVERNAME ika DBSERVERALIASES # List of alternate NETTYPE onsoctcp,1,,NET # Override sqlhosts nettype DEADLOCK_TIMEOUT 60 # Max time to wait of lock in RESIDENT 0 # Forced residency flag (Yes = 1, No = 0) > > MULTIPROCESSOR 0 > NUMCPUVPS 1 # Number of user (cpu) vps SINGLE_CPU_VP 0 > NOAGE 0 # Process aging > AFF_SPROC 0 # Affinity start processor AFF_NPROCS 0 # Affinity > > # Shared Memory Parameters > > LOCKS 2000 # Maximum number of locks > BUFFERS 2000 NUMAIOVPS # Number IO vps > PHYSBUFF 32 LOGBUFF 32 CLEANERS 1 SHMBASE 0xC000000L SHMVIRTSIZE 8192 SHMADD 8192 SHMTOTAL 0 > CKPTINTVL 300 LRUS 8 # > LRU_MAX_DIRTY 60 > LRU_MIN_DIRTY 50 TXTIMEOUT 300 > 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. > > DYNAMIC_LOGS 2 > LTXHWM 70 > LTXEHWM 80 > > # 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 > DRINTERVAL 30 # DR max time between DR buffer flushes (in sec) > DRTIMEOUT 30 # DR network timeout (in sec) DRLOSTFOUND \tmp # DR > lost+found file path > > # CDR Variables > CDR_EVALTHREADS 1,2 # evaluator threads (per-cpu-vp,additional) > CDR_DSLOCKWAIT 5 # DS lockwait timeout (seconds) CDR_QUEUEMEM 4096 # > Maximum memory for any CDR queue (Kbytes) CDR_QHDR_DBSPACE # CDR > queue dbspace (default same as catalog) CDR_QDATA_SBSPACE # CDR queue > smart blob space CDR_QDATA_SBFLAGS 2 # Log/no-log (default no log) > CDR_NIFCOMPRESS 0 # Link level compression (-1 never, 0 none, 9 max) > > # Backup/Restore variables > BAR_ACT_LOG C:\PROGRA~1\Informix\bar_ika.log #Path of log file for > onbar.exe BAR_MAX_BACKUP 0 BAR_RETRY 1 BAR_NB_XPORT_COUNT 10 > BAR_XFER_BUF_SIZE 15 BAR_BSALIB_PATH C:\ISM\2.20\bin\libbsa.dll # > Location of ISM XBSA DLL > > RESTARTABLE_RESTORE ON #To support restartable restore..values on/off > > # 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: > # Dynamic Server equivalent of DBTEMP for SE. This is the list of > dbspaces # that the Dynamic Server SQL Engine will use to create temp > tables etc. # If specified it must be a colon separated list of > dbspaces that exist # when the Dynamic Server 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 Dynamic Server operations. > # For DUMPSHMEM, DUMPGCORE and DUMPCORE 1 means Yes, 0 means No. > > DUMPDIR C:\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 Dynamic > Server) > DUMPCNT 1 # Number of shared memory or gcore dumps for > # a single user's session > > FILLFACTOR 90 # Fill factor for building indexes > > # method for Dynamic Server 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 32 # > Maximum number of decision support queries DS_TOTAL_MEMORY 4096 # Decision > support memory (Kbytes) DS_MAX_SCANS 1048576 # Maximum number of decision > support scans 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 2 # 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 sbspace # Default sbspace > > BLOCKTIMEOUT 3600 # Default timeout for system block > > # 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) > SYSSBSPACENAME sbspace # Default System sbspace > > # > # The following are default settings for enabling Java in the > database. # > > #VPCLASS jvp,num=1 # Number of JVPs to start with > > JVPJAVAHOME C:\PROGRA~1\Informix\extend\krakatoa\jre # JDK > installation root directory JVPHOME > C:\PROGRA~1\Informix\extend\krakatoa # Krakatoa installation directory > > JVPLOGFILE C:\PROGRA~1\Informix\extend\krakatoa\ika_jvp.log # VP log > file JVPPROPFILE C:\PROGRA~1\Informix\extend\krakatoa\.jvpprops_ika # > JVP property file > > JDKVERSION 1.3 # JDK version supported by this server > > # The path to the JRE libraries relative to JVPJAVAHOME JVPJAVALIB > \bin\ > > JVPJAVAVM hpi;server;verify;java;net;zip;jpeg > > # Classpath to use upon Java VM start-up (use _g version for > debugging) JVPCLASSPATH > C:\PROGRA~1\Informix\extend\krakatoa\krakatoa.jar; C:\PROGRA~1\Informix > \exten > d\krakatoa\jdbc.jar -----Original Message----- From: owner-informix-list@iiug.org [mailto On Behalf Of iksatongafin Sent: Monday, November 08, 2004 6:22 AM To: informix-list@iiug.org Subject: informix begginer on xp hi im learning on my college how to use databases, so i installed informix 9.4 from iugg site on my xp machine but the problem is when it start to initialize it just does that for a veery long time i left it for half hour and it wasn't finished so i though i should install probably some more things on my computer before installing informix can you tell me what to do?? thanx and if you can please tell me how to connect to that same database server with avg studio (also on iugg site) thanx again ----------------------------------------- ================================================== ========== The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any reproduction, dissemination or distribution of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Tellabs ================================================== ========== sending to informix-list |