SEO

Hi,

I am workind with Informix (IDS) 7.31 under Solaris 8. I have problems
to put an Informix Server Online. By showing the log messages it seems
that there are a lot of problems:

10:05:41 semctl: errno = 22

10:05:41 semctl: errno = 22
10:05:41 PANIC: Attempting to bring system down
10:05:41 mtex.c, line 471, thread 7, proc id 595, No Exception Handler.

10:05:34 See Also: /INFORMIXDUMP/af.3efe9b4, shmem.3efe9b4.0

10:05:27 listener-thread: err = -27002: oserr = 0: errstr = : No
connections are allowed in Dynamic Server quiescent mode.
10:05:27 (14) connection rejected - no calls allowed for sqlexec

10:05:12 listener-thread: err = -27002: oserr = 0: errstr = : No
connections are allowed in Dynamic Server quiescent mode.
10:05:12 (13) connection rejected - no calls allowed for sqlexec
10:04:53 Action: Please notify Informix Technical Support.
10:04:53 Results: Exception Caught. Type: MT_EX_OS, Context: mem
10:04:53 Who: Session(1, root@oami2, 0, 239157272)
Thread(7, main_loop(), e3ea018, 3)
File: mtex.c Line: 471
10:04:53 Informix Dynamic Server Version 7.31.UD7
10:04:53 Assert Failed: No Exception Handler
10:04:53 Cannot Open Primary Chunk '/disk_extern/prueba/plogicallog_2',
errno = 2
10:04:53 Cannot Open Primary Chunk '/disk_extern/prueba/pem_blob1_4',
errno = 2
10:04:53 Cannot Open Primary Chunk '/disk_extern/prueba/pem_blob1_3',
errno = 2
10:04:53 Cannot Open Primary Chunk '/disk_extern/prueba/plogicallog_2',
errno = 2
10:04:52 Cannot Open Primary Chunk '/disk_extern/prueba/pem_blob1_4',
errno = 2
10:04:52 Cannot Open Primary Chunk '/disk_extern/prueba/pem_blob1_3',
errno = 2
10:04:52 Cannot Open Primary Chunk '/disk_extern/prueba/pem_data4_2',
errno = 2
10:04:52 Cannot Open Primary Chunk '/disk_extern/prueba/pem_data3_2',
errno = 2
10:04:52 Cannot Open Primary Chunk '/disk_extern/prueba/pem_data2_2',
errno = 2
10:04:52 Informix Dynamic Server Version 7.31.UD7 Software Serial
Number AAB#J904945
10:04:52 Dynamically allocated new message shared memory segment (size
352KB)
10:04:52 Requested shared memory segment size rounded from 344KB to
352KB
10:04:52 Requested shared memory segment size rounded from 344KB to
352KB
10:04:51 DR: DRAUTO is 0 (Off)
10:04:47 Event alarms enabled. ALARMPROG = '/informix/etc/no_log.sh'


The chunks which is trying to open do not exist but still try to open
them. Anybody know what happens? I am absolutely lost.


For more information I give you the /etc/system files with the shared
memory configuration:

informix@BO:/$ more /etc/system
*ident "@(#)system 1.18 97/06/27 SMI" /* SVR4 1.5 */
*
* SYSTEM SPECIFICATION FILE
*

* moddir:
*
* Set the search path for modules. This has a format similar to
the
* csh path variable. If the module isn't found in the first
directory
* it tries the second and so on. The default is /kernel
/usr/kernel
*
* Example:
* moddir: /kernel /usr/kernel /other/modules



* root device and root filesystem configuration:
*
* The following may be used to override the defaults provided by
* the boot program:
*
* rootfs: Set the filesystem type of the root.
*
* rootdev: Set the root device. This should be a fully
* expanded physical pathname. The default is the
* physical pathname of the device where the boot
* program resides. The physical pathname is
* highly platform and configuration dependent.
*
* Example:
* rootfs:ufs
* rootdev:/sbus@1,f8000000/esp@0,800000/sd@3,0:a
*
* (Swap device configuration should be specified in /etc/vfstab.)



* exclude:
*
* Modules appearing in the moddir path which are NOT to be
loaded,
* even if referenced. Note that `exclude' accepts either a module
name,
* or a filename which includes the directory.
*
* Examples:
* exclude: win
* exclude: sys/shmsys



* forceload:
*
* Cause these modules to be loaded at boot time, (just before
mounting
* the root filesystem) rather than at first reference. Note that
* forceload expects a filename which includes the directory. Also
* note that loading a module does not necessarily imply that it
will
* be installed.
*
* Example:
* forceload: drv/foo



* set:
*
* Set an integer variable in the kernel or a module to a new
value.
* This facility should be used with caution. See system(4).
*
* Examples:
*
* To set variables in 'unix':
*
* set nautopush=32
* set maxusers=40
*
* To set a variable named 'debug' in the module named
'test_module'
*
* set test_module:debug = 0x13
set shmsys:shminfo_shmmax=256000000
set shmsys:shminfo_shmmin=100
set shmsys:shminfo_shmmni=100
set shmsys:shminfo_shmseg=100

set semsys:seminfo_semmap=64
set semsys:seminfo_semmni=4096
set semsys:seminfo_semmns=4096
set semsys:seminfo_semmnu=4096
set semsys:seminfo_semume=64
set semsys:seminfo_semmsl=512

set msgsys:msginfo_msgmni=2048


#set semsys:seminfo_semmap=50
#set semsys:seminfo_semmni=2000
#set semsys:seminfo_semmns=2000
#set semsys:seminfo_semmnu=500
#set semsys:seminfo_semmsl=512
set semsys:seminfo_semopm=256
#set semsys:seminfo_semume=500
set semsys:seminfo_semvmx=32767
set semsys:seminfo_semaem=16384
#set shmsys:shminfo_shmmax=20971520
#set shmsys:shminfo_shmmin=0
#set shmsys:shminfo_shmmni=2000
#set shmsys:shminfo_shmseg=100
#set msgsys:msginfo_msgmni=2048
set max_nprocs=1000
set fnsod:sod_Debug=0
set rlim_fd_max=1024
set rlim_fd_cur=256

* vxvm_START (do not remove)
forceload: drv/vxdmp
forceload: drv/vxio
forceload: drv/vxspec
forceload: drv/dad
forceload: drv/pcipsy
forceload: drv/sd
forceload: drv/ssd
rootdev:/pseudo/vxio@0:0
set vxio:vol_rootdev_is_volume=1
*/dev/console 0666 /dev/console
* vxvm_END (do not remove)


Any ideas pelase?

Thanks.

Alan

10:04:53 Cannot Open Primary Chunk '/disk_extern/prueba/plogicallog_2',
> errno = 2

this means no such file or directory.
why are your devices for your not present???

do a ls -lL /disk_extern/prueba/plogicallog_2
this should read

-rw-rw--- informix informix...........

and CHECK all of them please.

Superboer.


Massoroto schreef:

> Hi,
>
> I am workind with Informix (IDS) 7.31 under Solaris 8. I have problems
> to put an Informix Server Online. By showing the log messages it seems
> that there are a lot of problems:
>
> 10:05:41 semctl: errno = 22
>
> 10:05:41 semctl: errno = 22
> 10:05:41 PANIC: Attempting to bring system down
> 10:05:41 mtex.c, line 471, thread 7, proc id 595, No Exception Handler.
>
> 10:05:34 See Also: /INFORMIXDUMP/af.3efe9b4, shmem.3efe9b4.0
>
> 10:05:27 listener-thread: err = -27002: oserr = 0: errstr = : No
> connections are allowed in Dynamic Server quiescent mode.
> 10:05:27 (14) connection rejected - no calls allowed for sqlexec
>
> 10:05:12 listener-thread: err = -27002: oserr = 0: errstr = : No
> connections are allowed in Dynamic Server quiescent mode.
> 10:05:12 (13) connection rejected - no calls allowed for sqlexec
> 10:04:53 Action: Please notify Informix Technical Support.
> 10:04:53 Results: Exception Caught. Type: MT_EX_OS, Context: mem
> 10:04:53 Who: Session(1, root@oami2, 0, 239157272)
> Thread(7, main_loop(), e3ea018, 3)
> File: mtex.c Line: 471
> 10:04:53 Informix Dynamic Server Version 7.31.UD7
> 10:04:53 Assert Failed: No Exception Handler
> 10:04:53 Cannot Open Primary Chunk '/disk_extern/prueba/plogicallog_2',
> errno = 2
> 10:04:53 Cannot Open Primary Chunk '/disk_extern/prueba/pem_blob1_4',
> errno = 2
> 10:04:53 Cannot Open Primary Chunk '/disk_extern/prueba/pem_blob1_3',
> errno = 2
> 10:04:53 Cannot Open Primary Chunk '/disk_extern/prueba/plogicallog_2',
> errno = 2
> 10:04:52 Cannot Open Primary Chunk '/disk_extern/prueba/pem_blob1_4',
> errno = 2
> 10:04:52 Cannot Open Primary Chunk '/disk_extern/prueba/pem_blob1_3',
> errno = 2
> 10:04:52 Cannot Open Primary Chunk '/disk_extern/prueba/pem_data4_2',
> errno = 2
> 10:04:52 Cannot Open Primary Chunk '/disk_extern/prueba/pem_data3_2',
> errno = 2
> 10:04:52 Cannot Open Primary Chunk '/disk_extern/prueba/pem_data2_2',
> errno = 2
> 10:04:52 Informix Dynamic Server Version 7.31.UD7 Software Serial
> Number AAB#J904945
> 10:04:52 Dynamically allocated new message shared memory segment (size
> 352KB)
> 10:04:52 Requested shared memory segment size rounded from 344KB to
> 352KB
> 10:04:52 Requested shared memory segment size rounded from 344KB to
> 352KB
> 10:04:51 DR: DRAUTO is 0 (Off)
> 10:04:47 Event alarms enabled. ALARMPROG = '/informix/etc/no_log.sh'
>
>
> The chunks which is trying to open do not exist but still try to open
> them. Anybody know what happens? I am absolutely lost.
>
>
> For more information I give you the /etc/system files with the shared
> memory configuration:
>
> informix@BO:/$ more /etc/system
> *ident "@(#)system 1.18 97/06/27 SMI" /* SVR4 1.5 */
> *
> * SYSTEM SPECIFICATION FILE
> *
>
> * moddir:
> *
> * Set the search path for modules. This has a format similar to
> the
> * csh path variable. If the module isn't found in the first
> directory
> * it tries the second and so on. The default is /kernel
> /usr/kernel
> *
> * Example:
> * moddir: /kernel /usr/kernel /other/modules
>
>
>
> * root device and root filesystem configuration:
> *
> * The following may be used to override the defaults provided by
> * the boot program:
> *
> * rootfs: Set the filesystem type of the root.
> *
> * rootdev: Set the root device. This should be a fully
> * expanded physical pathname. The default is the
> * physical pathname of the device where the boot
> * program resides. The physical pathname is
> * highly platform and configuration dependent.
> *
> * Example:
> * rootfs:ufs
> * rootdev:/sbus@1,f8000000/esp@0,800000/sd@3,0:a
> *
> * (Swap device configuration should be specified in /etc/vfstab.)
>
>
>
> * exclude:
> *
> * Modules appearing in the moddir path which are NOT to be
> loaded,
> * even if referenced. Note that `exclude' accepts either a module
> name,
> * or a filename which includes the directory.
> *
> * Examples:
> * exclude: win
> * exclude: sys/shmsys
>
>
>
> * forceload:
> *
> * Cause these modules to be loaded at boot time, (just before
> mounting
> * the root filesystem) rather than at first reference. Note that
> * forceload expects a filename which includes the directory. Also
> * note that loading a module does not necessarily imply that it
> will
> * be installed.
> *
> * Example:
> * forceload: drv/foo
>
>
>
> * set:
> *
> * Set an integer variable in the kernel or a module to a new
> value.
> * This facility should be used with caution. See system(4).
> *
> * Examples:
> *
> * To set variables in 'unix':
> *
> * set nautopush=32
> * set maxusers=40
> *
> * To set a variable named 'debug' in the module named
> 'test_module'
> *
> * set test_module:debug = 0x13
> set shmsys:shminfo_shmmax=256000000
> set shmsys:shminfo_shmmin=100
> set shmsys:shminfo_shmmni=100
> set shmsys:shminfo_shmseg=100
>
> set semsys:seminfo_semmap=64
> set semsys:seminfo_semmni=4096
> set semsys:seminfo_semmns=4096
> set semsys:seminfo_semmnu=4096
> set semsys:seminfo_semume=64
> set semsys:seminfo_semmsl=512
>
> set msgsys:msginfo_msgmni=2048
>
>
> #set semsys:seminfo_semmap=50
> #set semsys:seminfo_semmni=2000
> #set semsys:seminfo_semmns=2000
> #set semsys:seminfo_semmnu=500
> #set semsys:seminfo_semmsl=512
> set semsys:seminfo_semopm=256
> #set semsys:seminfo_semume=500
> set semsys:seminfo_semvmx=32767
> set semsys:seminfo_semaem=16384
> #set shmsys:shminfo_shmmax=20971520
> #set shmsys:shminfo_shmmin=0
> #set shmsys:shminfo_shmmni=2000
> #set shmsys:shminfo_shmseg=100
> #set msgsys:msginfo_msgmni=2048
> set max_nprocs=1000
> set fnsod:sod_Debug=0
> set rlim_fd_max=1024
> set rlim_fd_cur=256
>
> * vxvm_START (do not remove)
> forceload: drv/vxdmp
> forceload: drv/vxio
> forceload: drv/vxspec
> forceload: drv/dad
> forceload: drv/pcipsy
> forceload: drv/sd
> forceload: drv/ssd
> rootdev:/pseudo/vxio@0:0
> set vxio:vol_rootdev_is_volume=1
> */dev/console 0666 /dev/console
> * vxvm_END (do not remove)
>
>
> Any ideas pelase?
>
> Thanks.
>
> Alan

oopps it should read

crw-rw---- informix informix....

Superboer.

Hi Superboer,

I tried what you suggested:

informix@BO:/export/home/informix$ ls -lL
/disk_extern/prueba/plogicallog_2
/disk_extern/prueba/plogicallog_2: No such file or directory

and seems that this chunks does not exist.

Is it possible to drop this chunk by deleting it from the file
oncfg_prueba.4? Or it must be restored using ontape?

Thank you.

do you have any idea what data was in the chunk stored on there?

Personally I wouldn't tamper with oncfg_ files

I think you need to restore your archive, however the archive will
expect the file /disk_extern/prueba/plogicallog_2 to exist so you'll
need to recreate that device ot the archive won't restore.

As this sasy "disk_extern" is this a remote mounted disk and the
connection (cross mount) has been lost? If so, recreating that may
resolve the problem.


Massoroto wrote:
> Hi Superboer,
>
> I tried what you suggested:
>
> informix@BO:/export/home/informix$ ls -lL
> /disk_extern/prueba/plogicallog_2
> /disk_extern/prueba/plogicallog_2: No such file or directory
>
> and seems that this chunks does not exist.
>
> Is it possible to drop this chunk by deleting it from the file
> oncfg_prueba.4? Or it must be restored using ontape?
>
> Thank you.

scottishpoet wrote:
> do you have any idea what data was in the chunk stored on there?
>
> Personally I wouldn't tamper with oncfg_ files

It's not too critical - IDS regenerates them from information in the
reserved pages, etc.

> I think you need to restore your archive, however the archive will
> expect the file /disk_extern/prueba/plogicallog_2 to exist so you'll
> need to recreate that device ot the archive won't restore.

Yes!

> As this sasy "disk_extern" is this a remote mounted disk and the
> connection (cross mount) has been lost? If so, recreating that may
> resolve the problem.

If it was remote mounted, then (a) performance was likely bad, and (b)
it is not clear that the configuration was ever supported. It depends a
bit on the nature of the remote mount - if it was a SAN/NAS type
appliance, then your chances are better than if it was a random NFS file
system on a random server.

Either way, until that system is brought back (or an equivalent
created), Massoroto is going to have a tough time.

> Massoroto wrote:
>
>>Hi Superboer,
>>
>>I tried what you suggested:
>>
>>informix@BO:/export/home/informix$ ls -lL
>>/disk_extern/prueba/plogicallog_2
>>/disk_extern/prueba/plogicallog_2: No such file or directory
>>
>>and seems that this chunks does not exist.
>>
>>Is it possible to drop this chunk by deleting it from the file
>>oncfg_prueba.4? Or it must be restored using ontape?
>>
>>Thank you.
>
>


--
Jonathan Leffler #include <disclaimer.h>
Email: jleffler@earthlink.net, jleffler@us.ibm.com
Guardian of DBD::Informix v2005.02 -- http://dbi.perl.org/