oninit fails w/ 10uc5

oninit fails w/ 10uc5

Post by Mike Bada » Sat, 07 Oct 2006 03:05:13


Solaris 9

When I attempt to initialize the engine, it proceeds until the following
message is displayed:

Initializing 1 flushers...succeeded

After the above message is displayed, oninit stops, the prompt is
returned, no errors are reported and the engine fails to initialize.
Has anyone experienced this behavior from "oninit -iv" running 10uc5?
The full output from "oninit -iv" is listed below.

Thanks in advance for your help.

Mike Badar
ESRI Professional Services
1 International Court
Broomfield, CO 80021-3200

informix@am:/am1/software/db/informix/ids10.00.UC5> oninit -iv

This action will initialize IBM Informix Dynamic Server;
any existing IBM Informix Dynamic Server databases will NOT be
accessible -
Do you wish to continue (y/n)? y
Checking group membership to determine server run mode...succeeded
Reading configuration file
Creating /INFORMIXTMP/.infxdirs...succeeded
Creating infos file
Linking conf file
Writing to infos file...succeeded
Checking config parameters...succeeded
Allocating and attaching to shared memory...succeeded
Creating resident pool 1402 kbytes...succeeded
Allocating 10016 kbytes for buffer pool of 2K page size...succeeded
Initializing rhead structure...succeeded
Initializing ASF...succeeded
Initializing Dictionary Cache and SPL Routine Cache...succeeded
Bringing up ADM VP...succeeded
Creating VP classes...succeeded
Onlining 0 additional cpu vps...succeeded
Onlining 2 IO vps...succeeded
Initialization of Encryption...succeeded
Forking main_loop thread...succeeded
Initializing DR structures...succeeded
Forking 1 'tlitcp' listener threads...succeeded
Starting tracing...succeeded
Initializing 1 flushers...succeeded

oninit fails w/ 10uc5

Post by Quma » Sat, 07 Oct 2006 05:03:27

What is in online log?


oninit fails w/ 10uc5

Post by Mike Bada » Sat, 07 Oct 2006 07:19:36

hank you Quman. After looking in the online.log (note to self: always
look in the online.log) I discovered IDS could not bind to the port
number defined in /etc/services. One of the failed "oninit -iv"'s must
not have released the port. I killed the "oninit" process and as I look
over my shoulder, the engine is on-line.