Re: Sybase to Oracle

hi,

    i have the same problem (dealing ~50% of my work time to get used to oracle, i.e. ~30 hours now). fortunatly my former collegues did some work in that area, so i could see what's up and how things are solved.

so, as far as i understand (and i might be very wrong here), you have the listener which takes the scheduling
(or should i say database-routing?) job and you have
a bunch of DB-server- and other background-processes for each individual database. the listener on each server (machine, not db-server) listens on a dedicated port (default 1521 or something) and therefore behaves like a sybase server
(or engine 0) in terms of connection management.

tnsnames.ora is what the sybase interfaces file is, listener.ora is needed on the db-server-side to make the dbs known to the listener (after changes: call the listener manager lsnctrl and excute a "reload" to read it again).

the biggest unanswered question to me is how storage is organized. if i got that right blocks and extents are both of variable size and the latter could be variable even in a single db. segments might be what device- fragments are in sybase, but i'm not sure yet. if so, tablespaces are what segments are in sybase.

hope this helps (and that someone corrects me if i'm wrong)! - tB! Received on Thu Jul 08 1999 - 11:02:25 CDT