Re: Migration from Informix to Oracle 7.3.3

On 7 Jan 1998 14:03:23 -0500, nigelg@ppsl.com (Nigel Gall) wrote: > >Just out of curiosity, if Oracle gave you all these problems, why was it >decided to migrate to Oracle instead of upgrade to Informix ODS 7.2x? > >Please note, I have no experience in using Oracle, so I cannot confirm what >you're saying; I'm taking your word for it, though I find it hard to >believe that Oracle only allows one database per instance. Don't they >follow standard SQL? > Yes, they do only allow 1 DB per instance, and I was just wondering where in the SQL standard does it say you have to allow more than 1? Neither Informix nor Oracle is truly "standard" whatever that means. This is a good thing though, as some of the sql extensions are best part of both products. >At 01:31 PM 1/6/98 EDT, you wrote: >} >} >}We are currently running Informix-5, with a setup as follows: >} >} Single DB server running version 5 of informix. >} Multiple (60+) databases served >} Lots of Infomaker clients using password authentication >} Several unix client workstations using .rhosts/hosts.equiv >} authentication. >} >}From the looks of things after installing 7.3.3, (well, starting to >}install it anyway.) It seems that oracle can only serve a single database >}per instance. This means we would have to run 60+ instances of oracle on >}the DB server, does it not? Many of the databases have identical tables >}and are archive versions of the main database. I.e. the Fall Semester >}1996 student database. >} >}Oracle does not seem to support .rhosts/hosts.equiv authentication, so it >}looks like we'll have to move to embedding the passwords in the perl >}scripts that connect to the database server (or in a local file or similar). >} >}Does anyone have any pointers or tips for going about this migration >}process. At the moment, I am still struggling with just getting Oracle up >}and running to where I can connect to it remotely. >} [snip] I can't solve all of your problems, but you could put all 60 databases inside the single Oracle DB, using different user ID's to create the tables. This is essentially a namespace problem, so you can use the user ID and permissions to isolate each 'database' from the others. I don't know if this will work with the applications that are hitting the DB, but take a look at it. Installing SQL*Net makes I-Net/I-Connect look like a user friendly, well written, error free program huh? -- ej You can reach me at the above id at pcslink.com, unless you are just sending spam. I get enough now as it is.