If the packages were first created on a different database system, their Oracle port very likely
does not take full advantage of Oracle??™s functional capabilities, such as sequences, triggers, and
methods. Tuning such a package to meet your needs may require modifying the source code.
If the package assumes that it has full DBA authority, it must not be stored in the same
database as any other critical database application. Most packages that require DBA authority do
so in order to add new users to the database. You should determine exactly which system-level
privileges the package administrator account actually requires (usually just CREATE SESSION and
CREATE USER). You can create a specialized system-level role to provide this limited set of system
privileges to the package administrator.
Packages that were first developed on non-Oracle databases may require the use of the same
account as another Oracle-ported package. For example, ownership of a database account called
SYSADM may be required by multiple applications. The only way to resolve this conflict with full
confidence is to create the two packages in separate databases.
Data Requirements
Any processing requirements that the packages have, particularly on the data-entry side, must be
clearly defined. These requirements are usually well documented in package documentation.
Version Requirements
Applications you support may have dependencies on specific versions and features of Oracle.
Pages:
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297