Re: Weirdness ??

Robertson Lee NTSE wrote: > All, > Two things..... > 1. In the log file on our test machine I am noticing the following error > message > Warning: Invalid dbspace 'temp_dbs' listed in DBSPACETEMP. > The environment variable is not set at the moment and the DBSPACETEMP > entry in the oncon file is set to > temp1_dbs:temp2_dbs:temp3_dbs:temp4_dbs. > Am I missing something here ?? Yes. The connection that generated that message came from another user, possible on another machine, with DBSPACETEMP set in its environment to "temp_dbs". > 2. We are attempting to back up our Logical logs with Onarchive > (continuous logging). This works fine on the production server but for > some reason is not working on the test machine. A Log file is backed up > and then the next one aborts and produces an error file in the tmp > directory, contents below > > 14:03:59 shmat: [22]: operating system error [SNIP] > The file pointed to (/tmp/sysfail.14455) has the following contents :- > Program has been aborted on 01-APR-1998:14:03:59. > An unexpected system error has occurred : code 11 > Please report this to Informix Technical Support. The shmat error and code 11 are the clues. Onarchive failed to create some shared memory segment, or to locate an existing one, and then tried to attach to the segment anyway (poor defensive programming that). The errno 11 is "resource temporarily unavailable" probably returned from shmget() and the errno 22 reported from shmat() is invalid argument to a system call, probably a bad shared memory handle since the shmget returns -1 on error. Looks like your test machine either does not have enough memory or the kernel was configured with not enough shared memory or shared memory handles to allow the onarchive to do what it wants to do. Art S. Kagel