After migrating a informix binaries to new server by os level cloning there was a warning when I execute the oninit -vy like could not open some chunks. then I ask system administrator link those missing chunks and again executed the oninit -vy again it prompt a warning with mentioning those chunks are bad chunks. what is the reason behind that. Is there any mistake happen when chunks re-configuring to new server
nwnhost@nwn$oninit -vy
Reading configuration file '/informix/strim/inf11/etc/onconfig'...succeeded
Creating /INFORMIXTMP/.infxdirs...succeeded
Checking config parameters...succeeded
Allocating and attaching to shared memory...succeeded
Creating resident pool 1629910 kbytes...succeeded
Allocating 6606044 kbytes for buffer pool of 2K page size...succeeded
Allocating 19267600 kbytes for buffer pool of 8K page size...succeeded
Creating infos file "/informix/strim/inf11/etc/.infos.ocs_test"...succeeded
Linking conf file "/informix/strim/inf11/etc/.conf.ocs_test"...succeeded
Initializing rhead structure...succeeded
Writing to infos file...succeeded
Initialization of Encryption...succeeded
Initializing ASF...succeeded
Initializing Dictionary Cache and SPL Routine Cache...succeeded
Bringing up ADM VP...succeeded
Creating VP classes...succeeded
Forking main_loop thread...succeeded
Initializing DR structures...succeeded
Forking 1 'soctcp' listener threads...succeeded
Starting tracing...succeeded
Initializing 128 flushers...succeeded
Initializing SDS Server network connections...succeeded
Initializing log/checkpoint information...succeeded
Initializing dbspaces...succeeded
Opening primary chunks...Bad Primary Chunk '/dev/chunk1186'.
Bad Primary Chunk '/dev/chunk1188'.
Bad Primary Chunk '/dev/chunk1265'.
Bad Primary Chunk '/dev/chunk1279'.
Bad Primary Chunk '/dev/chunk1317'.
Bad Primary Chunk '/dev/chunk1319'.
Bad Primary Chunk '/dev/chunk1320'.
succeeded
Validating chunks...succeeded
Initialize Async Log Flusher...succeeded
Starting B-tree Scanner...succeeded
Init ReadAhead Daemon...succeeded
Initializing DBSPACETEMP list...succeeded
Checking database partition index...succeeded
Initializing dataskip structure...succeeded
Checking for temporary tables to drop...succeeded
Updating Global Row Counter...succeeded
Forking onmode_mon thread...succeeded
Creating periodic thread...succeeded
Creating periodic thread...succeeded
Starting scheduling system...succeeded
Verbose output complete: mode = 5
here is the onstat -d output for those chunks
nwnhost@nwn$onstat -d | egrep 'chunk1188|chunk1186|chunk1265|chunk1279|chunk1317|chunk1319|chunk1320'
7be211028 1252 36 48 2097125 0 PD-B-- /dev/chunk1186
7be211428 1254 36 48 2097125 0 PD-B-- /dev/chunk1188
7be22d028 1331 37 48 2097139 0 PD-B-- /dev/chunk1265
7be22fc28 1345 38 48 2097000 0 PD-B-- /dev/chunk1279
7be241228 1383 48 48 2097139 0 PD-B-- /dev/chunk1317
7be241628 1385 38 48 2097139 0 PD-B-- /dev/chunk1319
7be241828 1386 37 48 2097000 0 PD-B-- /dev/chunk1320
nwnhost@nwn$
I could resolve above error by opening those chunks by below command.
onspaces -s [dbspace_name] -p [pathname] -o [offset] -O
eg :-
onspaces -s dbspace1 -p /dev/chunk1186 -o 96 -O