Oracle Vs. DB2
From: comm onno oracle8@mailcity.com
Date: Tuesday, April 06, 1999 7:54 PM
Subject: Oracle Vs DB2
Hi Oracle gurus:
Could you please help me?
I have a discussion question on Oracle VS DB2.
Could you possibly point it out what is (are) the difference(s) between
these two
relational databases mainly in how they manage concurrency, security, query
optimisation, tuning, and database space management?
TIA
comm onno
Date: Wed, 7 Apr 1999 14:47:08 -0600
From: "Frank Dodgers" dodgers.eis@worldnet.att.net
Subject: Re: Oracle Vs DB2
Keep in mind there are 2 DB2s. DB2 for OS390 (aka MVS), and UDB which runs
on other platforms such as SUN, AS400, RS6000, SP2, and even NT.
DB2 is designed around the old school (surprise, surprise) thinking such as
large logical units of work, pessimistic locking, transaction serialization
(rather than data time-stamping), etc. Whereas UDB is much
like Oracle in these regards. As is always the case with IBM products, you
can make DB2 do whatever you want, just add time and money.
TPCC benchmarks show that UDB runs faster on SUN hardware than it does on
IBM RS6000 hardware.
Lock escalation was a serious problem in early versions of DB2 circa 1988.
Version 6 of DB2 has a real interesting backup feature (not sure on the name
but I think it is called hardware snapshot) where you can literally take an
image backup in an incredibly small amount of time. Of course this assumes
you have a ton of "big buck" IBM "big iron" on hand. Depending upon the
circumstances, execution plans still have to be manually rebound at times
with DB2.
The development center for UDB is in Toronto, Canada and for DB2 it is Santa
Theresa, California, USA.
Frank
Oracle Service
From: SRIVATHSAN N [mailto:nsrivaths@yahoo.com]
Sent: Sunday, April 11, 1999 3:07 AM
Subject: Oracle Service!
Hi All!
Could anyone tell me what Oracle service is?I am not able to
find good
material on the web about this.
Can Oracle Service be used for a leasing company?
We are primarily into leasing of heavy equipment and we
heard that
Oracle service provides a good fit!
Look forward to your replies
Thanks in advance
regards
srivathsan
Date: Wed, 31 Mar 1999 09:49:14 -0800
From: "David A. Vandenberg" dvandenb@us.oracle.com
Subject: Re: Oracle Service
Kathryn,
You might take a look at Oracle Service. Here is a short sales blurb:
Overview of Oracle Service
Oracle Service offers a critical extension to your supply chain by providing
support for products after you have sold them. By offering you
complete access to customer and product profiles, including current and past
service history, Oracle Service helps you strengthen your
customer relationships.
Oracle Service is an integrated customer service solution that provides
installed base management, support service tracking, service requests,
and depot repair. You can fully integrate your service organization with the
rest of your business by leveraging Oracle Service with Oracle
Order Entry, Oracle Receivables, Oracle Inventory, and Oracle Work in Process.
Oracle Service shares key data with these Oracle
Applications modules, such as customer and product masters, so you can spend
less time managing data and more time servicing your
customers.
Thanks,
Dave
Date: Mon, 12 Apr 1999 11:57:10 -0400
From: "Lakdawala, M" M_Lakdawala@csx.com
Subject: RE: Oracle Service!
You need to visit http://technet.oracle.com http://technet.oracle.com
(copy the address, don't click on it somehow it does not work). Their you
shall find enough material under oracle applications including release 11
manual.
Thanks & Regards
MUZAFFER LAKDAWALA
From: Scott L. Frost [SMTP:sfrost@noblestar.com]
Sent: Sunday, April 11, 1999 6:16 AM
Subject: Re: Oracle Service!
Oracle Service is the latest application from Oracle in the Front Office
arena. The other two primary applications are Oracle Sales & Marketing
(OSM) and Oralce Sales Compensation. Service is primarily used for
customer
service in a company. It is designed to improve the quality of customer
service operations. Oracle plans on incorporating other modules as well
as
splitting up some of the service module into separate modules.
The 3 primary functions of this application are:
1. managing the Install Base (those products that have been purchased, or
exist at your customer's sites)
2. Customer Service (handling customer calls and managing customer
support
regarding product defects/problems, warranty coverages)
3. Depot Repair (either retrieving products to be repaired, or
dispatching
service engineers to repair those products at client sites)
It integrates very tightly with Order Entry and Inventory as well as OSM,
HR, WIP, BOM, and Receivables.
It does sound like this module would be a fit for a leasing company. Your
leases are probably set up with specific terms and conditions which would
be
a service program that you can set up to maintain those customer products
that are being leased. If a customer has a broken piece of equipment, you
would more than likely use the depot repair piece to dispatch a repair
person, or else have that piece of equipment sent back. Just be sure you
examine the requirements of some of these other modules. especially OE,
there is A LOT of integration with OE in order to get some of the
automated
functions setup for use in service.
If you have more specific questions, I would be more than happy to answer
them: sfrost@noblestar.com
Hope this helps!
Scott
Default uppercase
Date: Thu, 1 Apr 1999 10:21:12 -0600
From: "MCAVOY, Brian J." bmcavoy@shl.com
Subject: Default uppercase
Hi, has anyone forced the system to default all characters to uppercase. If
so, how difficult was sit. My client is particularly looking for that
capability while entering suppliers and item descriptions.
Thanks.
Brian McAvoy
Consultant
MCI Systemhouse
pager 888-319-3433
bmcavoy@shl.com
Date: Thu, 1 Apr 1999 13:16:48 -0500
From: Steve Bradley sbradley@sprynet.com
Subject: RE: Default uppercase
I can tell you how NOT to do this.
I had a client who wanted to do the same thing with GL JE Batch names. A
bright consultant from a large database software company said the easiest
thing to do is apply a pre-insert database trigger to change the name to
uppercase. This worked for a while until someone tried to key an existing
batch name "sample batch name". The query to find if it existed found
nothing in the table. It probably saw "SAMPLE BATCH NAME" but that wasn't
the same as what was keyed in. So, the form permitted the user to key in
the 200 line JE. When they tried to save (insert) the data the user got an
error "Batch name already exists" and the screen locked up.
This can happen with vendor additions also but the pain won't be as severe
as losing an hour's work.
Best, least costly method that survives upgrades very well is "Proper User
Training". Get them in the habit of hitting that Caps Lock key after they
log in.
Respectfully,
Steve Bradley, CPA
OASIS Consulting Group, Inc.
Office 404-352-8387
Fax 404-609-9856
Pager 888-912-2569
Date: Thu, 01 Apr 1999 10:36:40 -0800
From: Lewis R Cunningham lcunning@popmail.lmu.edu
Subject: RE: Default uppercase
One word, Custom.pll. Or is that 2 words?
Anyway, trigger: when-new-form-instance, change all items to upper case.
You can even create a generic procedure to dynamically loop through every
item in a form, check if it's an editable text-item, and change the
property to uppercase.
Simple and very upgradeable.
Lewis
Date: Thu, 1 Apr 1999 14:09:47 -0500
From: Ken_Rosenbaum@lcc.com
Subject: RE: Default uppercase
If you are doing a new install, have you looked at setting the VALUE SET to
uppercase only for FORMAT VALIDATION?
Date: Thu, 1 Apr 1999 11:53:36 -0800
From: "Walker, Cary" Cary.Walker@fluke.com
To: "'oraapps-l@cpa.qc.ca'" oraapps-l@cpa.qc.ca
Subject: RE: Default uppercase
I agree with Lewis. One of the examples in the documentation on what to use
the custom.pll for is to enforce uppercase data.
Cary
Date: Fri, 2 Apr 1999 08:19:02 -0600
From: "Veach, L. Vincent" VeachLV@bvsg.com
Subject: RE: Default uppercase
Here's my 2 cents worth:
Please don't be afraid to implement your validation in a database
trigger
just because some programmer failed to implement the design correctly. All
that
you need to do is to convert the data first before checking for duplicate
records.
As for the Custom.pll, it is true that this would be a perfect
example of
when to use the custom library as long as the only way you can update the
field
in question is through a form. If you happen to have an interface that also
updates
the same field then you will need to make the same changes there and any
other
place that currently or in the future may update that field.
In the final analysis you are better off using a database trigger
that will
validate the field no matter what process is doing the insert or update,
assuming
that you code it correctly. :-)
Vincent Veach