
Copyright © 2001, 2015, Oracle and/or its affiliates. All rights reserved.
It is recommended that, in an Oracle Transportation Management production database, following
objects be pinned in the SGA:
Package:
VPD
PARTIT
PKG_PURGE
RRL
USER_EXIT_HELPER
RPT_GENERAL
Database Space Monitoring
A DBA should periodically monitor Oracle Transportation Management database(s) space usage. There
are several tables containing a column with data type of CLOB. These columns can have great amount
of data. Some of the CLOB tables can be loaded quite often. One example is I_TRANSMISSION and
I_TRANSACTION table. These tables contain transmission/transaction’s XMLs. If there are inbound
/outbound transmissions in and out of system frequently, the disk space usage of these two tables can
grow very quickly.
Scheduled Jobs
Oracle Transportation Management database uses Oracle Database scheduled job to perform certain
activities inside the database. Some of the jobs are set up automatically after the database is
installed. The others are optional and can be implemented by a DBA. An Oracle Transportation
Management database DBA should monitor these jobs regularly.
Length Semantics
Oracle Transportation Management uses character semantics for new string columns and all of the
PL/SQL objects to support multi-byte character encoding scheme. It is highly recommended to use
character semantics during customization of Oracle Transportation Management database schemas.
Change NLS_LENGTH_SEMANTICS parameter at session level before adding new column or compiling
PL/SQL object during customization as shown below.
alter session set NLS_LENGTH_SEMANTICS=CHAR;
For further information about NLS_LENGTH_SEMANTICS, please refer to Oracle Database Globalization
Support Guide.
Optimizing Application-Database Round Trips
When querying or updating a group of records, an Oracle Transportation Management application
server can be configured to retrieve or send batches of records at a time. This can significantly
increase perceived query performance by reducing the network round trips.
For queries, the following properties controls the SQL fetch size
glog.sql.query.fetch.on = true
glog.sql.query.fetch.default = 10
glog.sql.query.fetch.maximum = 250
The on property specifies whether the application should use the default JDBC fetch size. If set to
true, queries will explicitly set their fetch size based on the use case. The default property specifies
the default fetch size for application queries. Many use cases in Oracle Transportation Management,
however, set a fetch size based on criteria such as page size (see the User Interface section below).
In these cases, the fetch size is often controlled by implementation details and can degrade
Comentarios a estos manuales