Re: Cannot start 2 instances of OnLine 7.x
Posted in 1997
Topics: Backup & Restore, Installation, Setup & Upgrades, Server Administration, Migration, Import/Export & Data Conversion
June Tong wrote:
> Erik A. Widholm (ewidholm@moody.edu) wrote:
> : Until recently, we ran our test database on OL 7.x and our production
> : database on OL 5.x with no memory conflicts. Then I upgraded the 5.x to
> : 7.x (dbexport, dbimport, etc.), and got it running. During the upgrade,
> : I did not have the 7.x engine running, but I did have a level 0 archive
> : of it that had been successfully restored a couple of times.
>
> : Now that my production database is up, I cannot get my test engine to
> : come up. When I do an 'oninit', it returns to the command prompt OK,
> : but within seconds states: oninit: Fatal error in shared memory
> : initialization
>
> Most common reasons for this situation:
> - Non-unique SERVERNUMs (but this is not your problem, because you would
> get shmget[EEXIST] errors or something like that.
> - Shared memory kernel parameters not set high enough for two instances.
> - Non-unique servicenames or servernames. DSA creates files in /INFORMIXTMP
> for your shmem and tcp connections (I don't know about others), which are
> named by servicename (for tcp) and servername (for shmem). If these are not
> unique on the machine, one will overwrite the other.
>
> Hope that helps.
Production Test
========== ====
SERVERNUM 70 66 (tried 14, 96, 77, etc....)INFORMIXSERVER mbi mbit
service onlinecarsi onlinet
With the production server up:
*) I can start up the test engine with oninit -i, create a database in dbaccess,
create tables, etc. without any conflicts. I am also able to take it off-line and
bring it up again without any trouble.
*) When I do a ontape -r to restore from tape (from a backup I made just previous
to bringing the production engine on-line) and stop the restore somewhere in
midpoint (by accident today), I can access all loaded tables and run the engine
with no trouble.
!) When I allow ontape -r to go until completion, that is when I cannot bring up
the engine. This occurs with any of the four or so most recent backups I have (I
haven't gone any further back yet).
Any ideas? I'm still down......