Oracle Practices and Standards

I am developing in Oracle 10gR2 database and I am trying to implement a Software and Database documenting standard for any new system, software, modification that the developers develop.
I would like to know, what is the best approach for documenting my database. Best Practices or methodologies to do this.
Is there any Oracle Method or Standard to Document my Software and Databases?

cnawrati wrote:
A customer complained about the following
Your company statements are not clear...
On your web page - http://www.oracle.com/security/critical-patch-update.html
Who is the "your" to which you are referring?
<snip>
Nowhere in that statement is the Patch Set Update even mentioned. If Oracle intends to recommend to all customers that Patch Set Updates are the recommended means of Patching for Security and Functionality then it should be stated so here!Um. OK
Please clarify!
Of whom are you asking for a clarification?
Where can I find the current information so that I can use to Official Oracle statement as a reference for my Enterprise Practices and Standards document? The individual patch package references you Who is the "you" to which you refer?
are giving me do not state Oracle recommended Best Practice, they only speak to the specific patch package they describe. These do not help me in making an Enterprise statement of Practices and Standards.
I need to close the process out to capture a window of availability for Practices and Standards approval.
Be our guest.
Do we What do you mean "we", Kemosabi?
have any Best Practice document about PSU patches available for customers?This is a very confusing posting, but overall it looks like you are under the impression that this forum is some kind of channel for communicating back to Oracle Crop anything that happens to be on your mind about their corporate web site and/or policies and practices. Please be advised that this forum is simply a platform provided BY Oracle Corp as a peer operated user support group. No one here is responsible for anything on any Oracle web site. No one here is responsible for any content anywhere in the oracle.com domain, outside of their own personal posting on this forum. In other words, you can complain all you want about Oracle's policy, practice, and support, but "there's no one here but us chickens."

Similar Messages

Oracle RAC and Standard Edition 11g R2

Hi,
Our application is tested with Oracle 11g r2 enterprise edition on RAC (inhouse).
A customer is asking whether he can use Oracle 11g r2 standard edition on RAC.
I need a gut feel on this, as our application does not use any of the enterprise edition features. Also our application has been successfully tested with oracle 11g r2 standard edition on single instance.
This is a big account and i need reliable answer.
Thanks in advance,
Krishna

Hello,
Yes, it is possible to have Oracle RAC with 11gR2 standard edition.
You can take a look at this http://docs.oracle.com/cd/E11882_01/license.112/e10594/editions.htm
Krishna Nazare
Newbie
Handle:      Krishna Nazare
Status Level:      Newbie
Registered:      Jul 11, 2011
Total Posts:      16
Total Questions:      8 (8 unresolved)
Name      Krishna
Location      Bangalore
Occupation      Software Architect Please follow the forum etiquette by marking your questions as answered by providing appropriate points if you feel that they have been answered. Please keep the forum clean !!

Oracle RAC and Standards

Does anyone know if Oracle RAC is part of any emerging Grid standards?

Hi Eric
Isn't RAC a middle to reach the grid computing goals ?
“A computational grid is a hardware and software infrastructure that provides dependable, consistent, pervasive, and inexpensive access to high-end computational capabilities.” by Carl Kesselman and Ian Foster in “The Grid: Blueprint for a New Computing Infrastructure,”

Difference between Enterprise Edition and Standard Edition for Oracle RAC

Hi,
In our current setup we have RAC on standard edition and client is now planning to go for Enterprise Edition but not yet decide because of cost.
Is there any difference between Grid Infrastructure 11gR3 Enterprise edition and Standard Edition ?
They told me to first install Enterprise Edition and then will move to Standard Edition if they can't get the EE license so in that case do i have to re-install Grid infrastructure for standard edition?
Regards,
Chirag

994551 wrote:
Hi,
In our current setup we have RAC on standard edition and client is now planning to go for Enterprise Edition but not yet decide because of cost.
Is there any difference between Grid Infrastructure 11gR3 Enterprise edition and Standard Edition ?
They told me to first install Enterprise Edition and then will move to Standard Edition if they can't get the EE license so in that case do i have to re-install Grid infrastructure for standard edition?Hi,
There is no "Grid Infrastructure 11gR3 Enterprise edition and Standard Edition", is only Grid Infrastructure 11gR2.
About Oracle Clusterware (Grid Infrastructure) licensing.
At least one of the servers in the cluster is licensed for Oracle Database (SE1, SE, or EE)
A cluster is defined to include all the machines that share the same Oracle Cluster Registry (OCR) and Voting Disk.
http://docs.oracle.com/cd/E11882_01/license.112/e10594/editions.htm#CJAHFHBJ
About Database licensing.
http://www.oracle.com/us/products/database/enterprise-edition/comparisons/index.html
Note : Oracle Real Application Clusters (Oracle RAC), is an option to Oracle Database 11g Enterprise Edition and included with Oracle Database 11g Standard Edition (on clusters with a maximum of 4 sockets).
If you move to Oracle EE you must purchase a separate licence to use RAC option
About Installation:
Nothing changes on your current setup of Grid Infrastructure 11.2
Just install a new fresh installation of Oracle Database (On current clusterware) chosing E.E during Install. Configure the database/services to start from this new ORACLE HOME. Nothing change on Database all previous backup and features used still unchanged. Using this new Oracle Home new features are enabled to be used by your databases.
About Downgrade:
Step by Step Procedure to Convert from Enterprise Edition to Standard Edition [ID 465189.1]

Implementing replication in Oracle 10&11 Standard Edition

I am implementing an oracle based application which will run under Linux/Oracle 10gr2 standard edition and which will soon be upgraded to Oracle 11g standard edition.
One of the requirements of the application is that a hot standby must be provided. To provide the hot standby, I must implement some sort of replication mechanism, but the nice replication features (data guard, streams, advanced replication, basic replication) are only available with Oracle enterprise edition.
Two questions:
1. It appears that I will be building a home-made replication mechanisms. I am planning on using insert/update/delete triggers and dblinks to trap database updates and propogate them to the standby server. (alternatively, may write them to files as SQL statements and have the second server load the files). Is their a better way to implement replication in Oracle SE. (esp. a feature of Oracle SE that I could be using to do this?).
2. Oracle Advanced and Basic Replication are not shown in the Oracle 11 Editions Description web page which lists the availability of features across the various oracle versions. I assume it is still supported in Oracle 11, but is Oracle Streams now the "best practice" for implementing replication (i.e. instead of advanced replication?)
Thanks in advance,
Werner

1) Having database triggers that use a database link is an exceptionally poor way of implementing a hot standby. If the database link goes down, or if the remote database is unavailable, the trigger will generate an exception and the parent transaction will be rolled back. Which means that the system is available only if both databases are available and the network between them is available, which is exactly the opposite of what a hot standby would be expected to provide.
2) You most likely want to set up a manual DataGuard-like setup. Clone the database from one machine to another, keep the standby database in managed recovery mode, and copy archived log files from the primary to the standby periodically. You'll have to script that, of course, but that shouldn't be insurmountable.
3) Basic replication (one-way materialized views) are available in the standard edition, but probably aren't the sort of thing you'd want to use to build a hot standby.
Justin

Oracle Spatial and Oracle Forms

Hi,
Does anyone have experience with Oracle Spatial and Oracle Forms?
I have generated a form, which is based on a view. The view uses the mdsys.sdo_relate operator. Somehow I am unable to get the form to perform (to get one record it takes over 20 minutes). While useing sql-navigator to process the same statement it seems no problem. The query that also uses the view, is then processed in 10 seconds.
I also noticed that when text-functions like ' lower' of ' upper' are used to query the view, the query is processed within 15 seconds. If I don't use ' lower' or ' upper' it takes a long time (> 20 minutes) to process the query. Is it possible that this causes the bad performance of the form?
On metalink I have found that forms and spatial do not cooperate because of the pl/sql version that
forms6 uses. There is no solution presented, does anyone know of a work around?
My configuration is:
Oracle 8.1.7 on WIN2K @ PIII-800Mhz 256 Mb memory.
Formsbuilder 6
If requested I can post the queries that I have made.
With regards,
Gerjan Walrecht
[email protected]
null

Hello Priya,
Look into the following.
1. Book - Pro Oracle Spatial for Oracle Database 11g by r. Kothuri, A. Godfrind, E. Beinat. This book provides a nice introduction on Oracle Spatial concepts and have examples.
2. Look at the Oracle Spatial & Graph User Guide
2. Book - Applying and Extending Oracle Spatial by S. Greener and S. Ravada. This book provides hands on information for advanced oracle spatial application developers. Practical guide on hands-on examples, Data models and develop cross-vendor database solutions.
3. This oracle spatial forum, once you understand these concepts.
In the future consider Certification on Oracle Spatial 11g Certified Implementation Specialist.
Best
Navaneet

ORACLE SERVER AND UNIX TP MONITOR-2

제품 : ORACLE SERVER
작성날짜 : 1995-01-24
Subject: Oracle Server and UNIX Transaction Processing Monitors-2
Page(3/4)
This file contains commonly asked questions about Oracle7 Server and UNIX
Transaction Processing Monitors (TPMs). The topics covered in this article are
     o Oracle Parallel Server and TP Monitors
     o Oracle and DCE-based TP Monitors
     o Other commonly asked questions
The questions answered in part 3 provide additional detail to the information
provided in part 1.
Oracle Parallel Server and TP Monitors
======================================
How does Oracle Parallel Server (OPS) work with TP Monitors?
If you are using Oracle-managed transactions, there are no special
considerations. But if you are using TPM-managed transactions, and
thus need to use the XA interface, then Oracle requires release 7.1.3
or later and a special version of the Distributed Lock Manager, called
the session-based lock manager. This version of the DLM is not yet
available for all platforms. To understand this restriction, let's take
a look at one of the technical details of XA.
The XA specification requires that the Resource Manager be able to
move a transaction from one process to another, and even to be
able to commit in a separate process. In Oracle, transactions are
attached to sessions, so that means that we also have to be able to
move sessions. Therefore, the session/transaction can't have any state
which is tied to a particular process. The first generation distributed
lock managers were all built to use the process id as the lock owner,
which doesn't work for locks which need to move with the transaction.
Oracle and DCE-based TP Monitors
================================
How does Oracle interface to the Encina TP monitor? To CICS/6000? I've
heard that they require OSF DCE facilities in order to run?
Oracle interfaces to Encina and CICS/6000 just as it does to any other
TP Monitor. The TP Monitor issues XA commands to control transactions, and
Oracle executes the commands. Encina and CICS/6000 do use DCE features for
their own operation. However, this use is transparent to the Oracle Server.
What DCE facilities can Oracle products take advantage of when working with
a DCE-based TP Monitor?
The two most commonly mentioned DCE features which might be useful
to Oracle users are multi-threading and security. We look at these in
the subsequent questions in this section.
Encina documentation suggests that a Resource Manager such as Oracle can
be either single-threaded or multi-threaded? Which way is Oracle XA
implemented?
The Oracle XA implementation is single-threaded, as is any Oracle client.
Within a single process, at most one thread can access Oracle at a time.
Does that mean that only a single Encina application can access an instance
of Oracle transactionally at any given moment?
No. Oracle XA is only single-threaded within a single application server
process. Multiple applications can access Oracle simultaneously using XA
by using different application processes. Encina allows
(1) serial reuse of a single server by different clients. There are
two options for this. The server can use long term reservation
but be defined to be in shared or concurrent access mode, which
allows the server to be used by another client as soon as an RPC
completes. Alternatively, the server can use default reservation
and exclusive mode, which allows the server to be used by another
client as soon as the current transaction ends.
(2) concurrent execution by multiple servers, even if they are accessing
the same Oracle database. These may be executing the same or different
procedures.
These two features should let you get as much concurrency as you need.
Why isn't the Oracle XA library multi-threaded?
The XA specification specifically states that its use of the phrase
"thread of control" means a process. If an RM were to multi-thread its
XA, it would be in violation of the specification. This restriction
was put place in because at the time the specification was written,
there were numerous thread packages: if the TM used one, the application
another, and perhaps the RM yet a third, there's no way it could work.
As threads standards settle down, the later versions of XA will probably
relax this restriction.
Will Oracle change if the XA specification changes?
Very likely. The exact time frame will of course depend on the priority of
all work items at that time.
Does Oracle use DCE security via the TP Monitors?
The integrity of the connection between a DCE TP Monitor client and DCE
TP Monitor server is protected by the DCE security functionality.
Theoretically, the TP Monitor could make the DCE-protected client security
information available to Oracle. Unfortunately, there's no standard way
for a TP Monitor to pass security information information to a Resource
Manager such as Oracle. Oracle is leading an effort to extend the X/Open
model to allow use of the security information provided by the Monitor.
In the meantime, the basic DCE security features such as encryption are
useful within TP Monitors.
Effective use of DCE security would normally also mean that the security of
the TP Monitor client be passed through the TP Monitor, through the Oracle
client (application server), to the Oracle Server, and possibly on
to other Oracle Servers through database links. The ability to transfer
security information to other processes, called delegation, is missing
in DCE version 1.0. DCE version 1.1, expected to emerge in late 1994,
has some delegation features. Oracle is examining these features to see
how they might be used.
Are there any special considerations for CICS/6000?
There are two:
(1) It is inefficient to run without XA. CICS/6000 is designed to
use XA. It uses XA so that the CICS server can log on to Oracle
when it starts, after which it makes that Oracle connection available
to any transaction it executes. If you don't use XA, the CICS server
does not itself log on to Oracle so each transaction has to log on
and log off - a very expensive mode of operation. Also, it is very
un-cics-like in that the application does the log{on,off} and also
commits - in a mainframe CICS database program CICS would implicitly
do these operations. Oracle does not recommend this mode because of the
performance penalty.
(2) CICS servers are generic and dynamically load application modules.
In order for these modules to access the Oracle connection made by
CICS, the applications must be built with a shared object version of
the Oracle libraries. This is an installation option on platforms which
support CICS/6000 and other products using its architecture such as
CICS 9000.
Other commonly asked questions
==============================
What other Resource Managers can be included in an Oracle XA transaction?
Several other relational database vendors have an XA implementation
available or in progress. There is an XA C-ISAM product from
Gresham Telecomputing. There are also Resource Managers contained
within some of the TP Monitors which can be coordinated in the same
transaction. For example, CICS/6000 has VSAM files and other data
stores, Encina has its RQS queuing system, and Tuxedo has its /Q queuing
system.
What is Recoverable Queuing Service (RQS) and how does it interoperate with
Oracle7 and Encina? What about /Q?
Recoverable Queuing Service is a feature provided by Encina which allows
transactional, distributed queuing (enqueue/dequeue). Tuxedo has a similar
product called /Q. Because these products are themselves coordinated by the
TM component of the TP Monitor, their queue operations are atomically
coordinated with with operations on XA Resource Managers such as Oracle7
Server. That is, they can atomically put something on one of their queues
and commit an Oracle transaction, then at some later time dequeue an
entry atomically with doing some other Oracle transaction. The queue
system guarantees that the message will not be lost or transmitted twice.
Can I mix TP Monitor applications with standard Oracle7 Server applications?
Yes, you can have existing Oracle applications connected to the database
with alongside TPM applications against the same database. The TPM does
not manage the whole database, just those transactions which are started
by the TPM. The Oracle Server will properly handle concurrency control
between the transactions managed by itself and those managed by the TPM.
Is Oracle planning to change its tools to be more suitable for TP Monitors?
With Oracle Procedure Builder 1.5, to be available with CDE2,
Oracle will provide a foreign function interface that allows you to
dynamically set up PL/SQL calls that access C functions. In other
words, you can access C routines in Windows DLLs from within your
PL/SQL procedures. This will allow PL/SQL under Windows easy access to
TP Monitor APIs.
Does Oracle7 Server itself use XA-compliant TPMs as the interface to
foreign RMs?
No, for this purpose Oracle Server uses the SQL*Connect products or the new
Transparent and Procedural Gateway products.
Does Oracle7 Server use XA to coordinate Oracle7-only distributed
transactions?
No, it uses an internal mechanism.
Can database links be used with XA?
If an Oracle7 database is running under XA, it can access other Oracle7
databases through database links, with some restrictions. First, the
access to the other database must use SQL*Net V2 and be running MTS.
Second, it must currently be to another Oracle7 database. Assuming those
restrictions, the Oracle 7 database can do distributed update to another
Oracle 7 database by using a database link, whether it is started by an
Oracle application or a TP Monitor application. The TPM will see Oracle
as only a single RM, but Oracle7 will propagate all the transaction
commands to the other database, including the two-phase commit. If
the transaction is started by a TP Monitor application and is using XA,
it can also update non-Oracle resources managed by the TPM. If it
is started from an Oracle application, it can only include resources
managed by Oracle.
Here's a sample configuration:
| TPM | | TPM |
| client | | client |
| |
| |
| TPM |
| |
| |
| Oracle | Forms, Forms, | Oracle | | non-XA | | XA |
| client | Plus, Plus, | client | | TPM | | TPM |
--------- Pro, Pro, --------- | server | | server |
| Financials, Financials, | |(note 1)| ----------
| etc. etc. | ---------- |
| | | |
| SQL | SQL | SQL | XA
| commit | commit | commit | commit
| | | |
| Oracle | | Oracle | | Oracle | | Oracle |
| server | | server | | server | | server |
| | | |
| | | |
| | | |
| Database 1 | | Database 2 |
| | | |
| A | A
| | dblink to database 1 | |
| ------------------------------------ |
| |
dblink to database 2
Note 1: Oracle will work having both XA and non-XA servers but some TPMs
may have restrictions on this.
Are multiple direct connections possible from a Pro* program?
Using XA, you can not only specify multiple direct connections to Oracle7
databases, you can also update them both in the SAME transaction. The
way to do this is to use a precompiler feature called a named database.
When you use a named database, you qualify the SQL statement with the
database name. For example, you write EXEC SQL AT dbname UPDATE emp ....
We have a complementary feature in the xa open string to let the user
associate the name with a particular RM instance, called the DB clause.
You will also want to use the SqlNet clause in the open string so you
can give the two different SIDs. This clause does not require the use of
the SQL*Net product, it is just a naming convention. For more information,
see Oracle7 Server for UNIX Administrator's Reference Guide.
Some TP Monitors may not support having multiple Resource Mangers in the
same server; check with the TPM vendor.
Is there any collateral available for XA or TP Monitors?
Oracle At Work 52684.0692
Oracle7 Server for UNIX Administrator's #A10324-1
Reference Guide
Guide to Oracle's Products and Services #A10560
Oracle7 Server and CICS/6000               #A14200
Where can I get more information on the DTP model?
X/Open's address is
X/Open company Ltd (Publications)
P O Box 109
Penn
High Wycombe
Bucks HP10 8NP
Tel: +44 (0)494 813844
Fax: +44 (0)494 814989
Request
G307 Distributed Transaction Processing: Reference Model Version 2
X/Open Guide G307 ISBN 1-859120-19-9 28cm.44p.pbk.220g.11/93
Page(4/4)
This file contains commonly asked questions about Oracle Server and UNIX
Transaction Processing Monitors (TPMs). The topics covered in this article are
     o Performance with Oracle Server and TP monitors
     o Performance using Oracle's XA Library
The questions answered in part 4 provide additional detail to the information
provided in part 1.
Performance with Oracle Server and TP Monitors
==============================================
I have heard that Transaction Processing Monitors (TPMs) will increase
Oracle Server performance. Is this true?
Several hardware and TPM vendors have made the claim that TPMs
will increase RDBMS performance. This claim is based on TPC-A
benchmarks. The key point to understand about TPC-A is that it
requires, for every transaction-per-second, ten times that many
users to be connected. For example, to get 600 TPS, you need 6000
users. The next question will answer in more detail how the the
three-tier architecture addresses this requirement, but first let's
look more generally at what TP Monitors can and can't do to improve
performance.
TP Monitors can provide better performance:
(1) When there are more than several hundred users connected.
     This is because of the TP Monitor's role in the three-tier
     architecture, described in the next question. In this
     architecture, terminal handling is offloaded to one or more
     separate machines, freeing up those cycles to do database work.
     Note that this does NOT mean that Oracle itself runs faster,
     just that we've given it more CPU cycles to use.
(2) When, because of the high potential concurrency of requests,
     significant resource contention exists. Use of a TP Monitor can
     limit the degree of concurrency and thus reduce contention.
TP Monitors can not provide better performance:
(1) For existing applications. The applications must be designed
     to fit the TP Monitor architecture.
(2) For applications which are highly interactive in their use of
     the database. These applications put many messages
     through the transport system, and the TP Monitor is not as
     efficient as SQL*Net for point-to-point communication.
(3) For CPU intensive single-query decision support. When executing
     a single large command, Oracle query facilities work efficiently,
     especially with the use of Oracle Parallel Query, available in 7.1.
How does the three-tier solution help TPC-A, or other situations with
thousands of on-line users?
The TPC-A test calls for a large number of users to produce a given
result. In the high-end results we produced in June, 1992, for example,
6150 terminals were simulated to produce 618 TPC-A transactions.
Thus, terminal concentration accounts for a large portion of the total
processing time used.
First, let's look at how the Multi Threaded Server would work for
this benchmark. In this case, there are many client processes,
but only a few server processes, which handle client requests on a
first-come first serve basis. When they are done with a request,
they take another client's request.
ORACLE7 CLIENT/SERVER ARCHITECTURE WITH MULTI THREADED SERVER
| Client | | Server |
| __________ |______________|_____ _____________ _____________ |
| | Client | | SQL*Net | |_|Dispatcher | | | |
| | Process| | | ____| Process |___| | |
| |________| | | | __|___________| | | |
|____________| | | | | | | | |
| | | | | | Oracle7 | |
______________ | | | __|__|____ | Server | |
| Client | | | | __|_|_____ | | | |
| __________ | | | | | Shared | |____| | |
| | Client | | SQL*Net | | | | Server |_|____| | |
| | Process|_|______________|__| | | Process|_| | | |
| |________| | | | |________| |___________| |
|____________| | | |
| | |
______________ | | |
| Client | | | |
| __________ | | | |
| | Client | | SQL*Net | | |
| | Process|_|______________|____| |
| |________| | | |
|____________| | |
|_______________________________________|
Client processes = N Dispatcher processes >= 1
Shared server processes >= 1
If there are 500 clients in this environment, there will be one or more
dispatcher processes, dynamically tunable, and one or more shared
server processes, dynamically tunable, on the server. The reduction
in the total number of processes handled by the server system
results in more processing time available for RDBMS activity. Thus
higher RDBMS transaction throughput can be obtained on the
server system.
But the problem for the TPC-A, and for certain large customer
configurations, is not the only ability of the Oracle Server to
process transactions, but also the ability of the operating
system to handle huge numbers of incoming connections.
There is one incoming connection for each client. Most UNIX
operating systems have a limit on how many such connections they can
handle. Even if a particular operating system allows a large number of
connections, each takes some amount of overhead to manage.
In order to service all 6150 terminals, we selected a 3-tier hardware
environment where the middle tier, using a TPM, acted as a terminal
concentrator. The high-end TPC-A architecture looked like the following.
The Application Servers, which contain the Pro*C statements used to
perform the transaction also run on the terminal concentrator machine
in order to offload as much work from the database serve as possible.
They send the compiled SQL over SQL*Net to the Oracle7 Server processes.
ORACLE7 TPS-A CLIENT/SERVER ARCHITECTURE
| Client | | Terminal | | Server |
| ________ | | Concentrator | | |
| | Client | |TPM | | | |
| | Process|_|_____|__ _____ | | |
| |________| |Comm | | | | | | |
|____________| | | | | | | |
| |__| | | | |
____________ | | TPM | | | |
| Client | | ___| | _______ | | ________ _______ |
| ________ | | | | |_| |__|_______|__| Oracle | | | |
| | Client | |TPM | | | | |Appl. | |SQL*Net| | Server |__| | |
| | Process|_|_____|_| |_____| |Server | | | | Process| | | |
| |________| |Comm | |_______| | | |________| | | |
|____________| | | | | | |
|_______________________| | | | |
| | | |
____________ _______________________ | |Oracle7| |
| Client | | Terminal | | |Server | |
| ________ | | Concentrator | | | | |
| | Client | |TPM | | | | | |
| | Process|_|_____|__ _____ | | __________ | | |
| |________| |Comm | | | | _______ |SQL*Net| | Oracle | | | |
|____________| | | | |_| |__|_______|__| Server |__| | |
| |__| | |Appl. | | | | Process| | | |
____________ | | TPM | |Server | | | |________| |_______| |
| Client | | ___| | |_______| | | |
| ________ | | | | | | | |
| | Client | |TPM | | | | | | |
| | Process|_|_____|_| |_____| | | |
| |________| |Comm | | | |
|____________| | | | |
|_______________________| |________________________|
Clients = 6150 Terminal concentrators = 17
TP Monitor instances = 17
Application server processes Oracle Server processes
= 17*8 = 17*8
The TPM is the software component of the terminal concentrator. In this role
it offloads terminal handling from the the machine running Oracle Server.
Since more than one terminal concentrator can be configured, whereas the
database in this case had to run on a single machine, concentrator machines
can be added until the performance of the back-end machine was optimized.
This three-tier solution resulted in the outstanding transaction throughput
announced with Oracle7 Server. Even with Oracle Parallel Server, it may pay
to offload the terminal handling so that the cluster can be exclusively used
for database operations.
Can you summarize the performance discussion for me?
Depending on the number of users required, different architectures may be
used in a client/server environment to maximize performance:
1) For a small number of users, the traditional Oracle two-task
architecture can be used. In this case, there is a one-to-one
correspondence between client processes and server processes. It's
simple, straightforward, and efficient.
2) For a large number of users, Multi Threaded Server might be a better
approach. Although some tuning may be required, Multi Threaded Server
can handle a relatively large number of users for each machine size
compared to the traditional Oracle approach. Using this approach,
customers will be able to handle many hundreds of users on many
platforms. Furthermore, current Oracle applications can move to this
environment without change.
3) For a very large number of users, where transactions are simple and
terminal input concentration is the overriding performance issue, a
3-tier architecture incorporating a TPM may be useful. In this case,
terminal concentration is handled by the TPM in the middle tier. As
     you might expect, it is a more complex environment requiring more
     system management. For existing Oracle customers, significant Oracle
application modifications will be required.
Oracle provides all of these choices.
Performance using Oracle's XA Library
=====================================
Are there any performance implications to using the XA library (in other
words, to using TPM-managed transactions)?
(1) The XA library imposes some performance penalty. You should use
TPM-managed transactions only if you actually need them. Even if you
are getting the one-phase commit optimization, the code path is
longer because we need to map back and forth between external
formats and internal ones. Also, prior to 7.1, XA requires you
to release all cursors at the end of a transaction, which results
in extra parsing. Even with shared cursors, there is time spent
looking up the one you need and re-validating it. This has been
improved for 7.1.
(2) If you need to use two-phase commit, this will incur additional cost
since extra I/Os are required. If you do need 2PC, you need to account
for that when sizing the application.
(3) Although some TPMs allow parallel execution of services (such as Tuxedo's
"tpacall"), this will not normally enhance performance unless different
resource managers are being used. In fact, Oracle Server must serialize
accesses to the same transaction by the same Oracle instance, and the
block/resume code will in fact degrade performance in that case compared
to running the services sequentially.

hello,
the role is the same on all plattforms. the reports server takes requests for running reports, spawns an engine that executes the request. in addition to that, the server also provides scheduling services and security features for the reports environment.
regards,
the oracle reports team

Sample Response File for Oracle Database 12c Standard Edition on Oracle Linux 6.4 -- working

oracle@styles-and-artists-development-oracle database]$ cat response/db_install.rsp
## Copyright(c) Oracle Corporation 1998,2013. All rights reserved.##
## Specify values for the variables listed below to customize     ##
## your installation.                                             ##
## Each variable is associated with a comment. The comment        ##
## can help to populate the variables with the appropriate        ##
## values.                                                        ##
## IMPORTANT NOTE: This file contains plain text passwords and    ##
## should be secured to have read permission only by oracle user ##
## or db administrator who owns this installation.                ##
# Do not change the following system generated value.
oracle.install.responseFileVersion=/oracle/install/rspfmt_dbinstall_response_schema_v12.1.0
# Specify the installation option.
# It can be one of the following:
#   - INSTALL_DB_SWONLY
#   - INSTALL_DB_AND_CONFIG
#   - UPGRADE_DB
oracle.install.option=INSTALL_DB_AND_CONFIG
# Specify the hostname of the system as set during the install. It can be used
# to force the installation to use an alternative hostname rather than using the
# first hostname found on the system. (e.g., for systems with multiple hostnames
# and network interfaces)
ORACLE_HOSTNAME=styles-and-artists-development-oracle
# Specify the Unix group to be set for the inventory directory.
UNIX_GROUP_NAME=oracle
# Specify the location which holds the inventory files.
# This is an optional parameter if installing on
# Windows based Operating System.
INVENTORY_LOCATION=/home/oracle/oracleInventory
# Specify the languages in which the components will be installed.
# en   : English                  ja   : Japanese
# fr   : French                   ko   : Korean
# ar   : Arabic                   es   : Latin American Spanish
# bn   : Bengali                  lv   : Latvian
# pt_BR: Brazilian Portuguese     lt   : Lithuanian
# bg   : Bulgarian                ms   : Malay
# fr_CA: Canadian French          es_MX: Mexican Spanish
# ca   : Catalan                  no   : Norwegian
# hr   : Croatian                 pl   : Polish
# cs   : Czech                    pt   : Portuguese
# da   : Danish                   ro   : Romanian
# nl   : Dutch                    ru   : Russian
# ar_EG: Egyptian                 zh_CN: Simplified Chinese
# en_GB: English (Great Britain) sk   : Slovak
# et   : Estonian                 sl   : Slovenian
# fi   : Finnish                  es_ES: Spanish
# de   : German                   sv   : Swedish
# el   : Greek                    th   : Thai
# iw   : Hebrew                   zh_TW: Traditional Chinese
# hu   : Hungarian                tr   : Turkish
# is   : Icelandic                uk   : Ukrainian
# in   : Indonesian               vi   : Vietnamese
# it   : Italian
# all_langs   : All languages
# Specify value as the following to select any of the languages.
# Example : SELECTED_LANGUAGES=en,fr,ja
# Specify value as the following to select all the languages.
# Example : SELECTED_LANGUAGES=all_langs
SELECTED_LANGUAGES=en
# Specify the complete path of the Oracle Home.
ORACLE_HOME=/extended2/oracleBase/db12c1
# Specify the complete path of the Oracle Base.
ORACLE_BASE=/extended2/oracleBase
# Specify the installation edition of the component.
# The value should contain only one of these choices.
#   - EE     : Enterprise Edition
#   - SE     : Standard Edition
#   - SEONE : Standard Edition One
#   - PE     : Personal Edition (WINDOWS ONLY)
oracle.install.db.InstallEdition=SE
# PRIVILEGED OPERATING SYSTEM GROUPS                                          #
# Provide values for the OS groups to which OSDBA and OSOPER privileges       #
# needs to be granted. If the install is being performed as a member of the   #
# group "dba", then that will be used unless specified otherwise below.       #
# The value to be specified for OSDBA and OSOPER group is only for UNIX based #
# Operating System.                                                           #
# The DBA_GROUP is the OS group which is to be granted OSDBA privileges.
oracle.install.db.DBA_GROUP=osdba
# The OPER_GROUP is the OS group which is to be granted OSOPER privileges.
# The value to be specified for OSOPER group is optional.
oracle.install.db.OPER_GROUP=osoper
# The BACKUPDBA_GROUP is the OS group which is to be granted OSBACKUPDBA privileges.
oracle.install.db.BACKUPDBA_GROUP=bckdba
# The DGDBA_GROUP is the OS group which is to be granted OSDGDBA privileges.
oracle.install.db.DGDBA_GROUP=dbdba
# The KMDBA_GROUP is the OS group which is to be granted OSKMDBA privileges.
oracle.install.db.KMDBA_GROUP=kmdba
#                               Grid Options                                  #
# Specify the type of Real Application Cluster Database
#   - ADMIN_MANAGED: Admin-Managed
#   - POLICY_MANAGED: Policy-Managed
# If left unspecified, default will be ADMIN_MANAGED
oracle.install.db.rac.configurationType=
# Value is required only if RAC database type is ADMIN_MANAGED
# Specify the cluster node names selected during the installation.
# Leaving it blank will result in install on local server only (Single Instance)
# Example : oracle.install.db.CLUSTER_NODES=node1,node2
oracle.install.db.CLUSTER_NODES=
# This variable is used to enable or disable RAC One Node install.
#   - true : Value of RAC One Node service name is used.
#   - false : Value of RAC One Node service name is not used.
# If left blank, it will be assumed to be false.
oracle.install.db.isRACOneInstall=
# Value is required only if oracle.install.db.isRACOneInstall is true.
# Specify the name for RAC One Node Service
oracle.install.db.racOneServiceName=
# Value is required only if RAC database type is POLICY_MANAGED
# Specify a name for the new Server pool that will be configured
# Example : oracle.install.db.rac.serverpoolName=pool1
oracle.install.db.rac.serverpoolName=
# Value is required only if RAC database type is POLICY_MANAGED
# Specify a number as cardinality for the new Server pool that will be configured
# Example : oracle.install.db.rac.serverpoolCardinality=2
oracle.install.db.rac.serverpoolCardinality=
#                        Database Configuration Options                       #
# Specify the type of database to create.
# It can be one of the following:
#   - GENERAL_PURPOSE/TRANSACTION_PROCESSING
#   - DATA_WAREHOUSE
oracle.install.db.config.starterdb.type=GENERAL_PURPOSE
# Specify the Starter Database Global Database Name.
oracle.install.db.config.starterdb.globalDBName=cbd
# Specify the Starter Database SID.
oracle.install.db.config.starterdb.SID=cdb1
# Specify whether the database should be configured as a Container database.
oracle.install.db.ConfigureAsContainerDB=true
# Specify the Pluggable Database name for the pluggable database in Container Database.
oracle.install.db.config.PDBName=pdb1
# Specify the Starter Database character set.
# One of the following
# AL32UTF8, WE8ISO8859P15, WE8MSWIN1252, EE8ISO8859P2,
# EE8MSWIN1250, NE8ISO8859P10, NEE8ISO8859P4, BLT8MSWIN1257,
# BLT8ISO8859P13, CL8ISO8859P5, CL8MSWIN1251, AR8ISO8859P6,
# AR8MSWIN1256, EL8ISO8859P7, EL8MSWIN1253, IW8ISO8859P8,
# IW8MSWIN1255, JA16EUC, JA16EUCTILDE, JA16SJIS, JA16SJISTILDE,
# KO16MSWIN949, ZHS16GBK, TH8TISASCII, ZHT32EUC, ZHT16MSWIN950,
# ZHT16HKSCS, WE8ISO8859P9, TR8MSWIN1254, VN8MSWIN1258
oracle.install.db.config.starterdb.characterSet=AL32UTF8
# This variable should be set to true if Automatic Memory Management
# in Database is desired.
# If Automatic Memory Management is not desired, and memory allocation
# is to be done manually, then set it to false.
oracle.install.db.config.starterdb.memoryOption=true
# Specify the total memory allocation for the database. Value(in MB) should be
# at least 256 MB, and should not exceed the total physical memory available
# on the system.
# Example: oracle.install.db.config.starterdb.memoryLimit=512
oracle.install.db.config.starterdb.memoryLimit=512
# This variable controls whether to load Example Schemas onto
# the starter database or not.
oracle.install.db.config.starterdb.installExampleSchemas=true
# Passwords can be supplied for the following four schemas in the             #
# starter database:                                                           #
#   SYS                                                                       #
#   SYSTEM                                                                    #
#   DBSNMP (used by Enterprise Manager)                                       #
# Same password can be used for all accounts (not recommended)                #
# or different passwords for each account can be provided (recommended)       #
# This variable holds the password that is to be used for all schemas in the
# starter database.
oracle.install.db.config.starterdb.password.ALL=CDBadmin12345#
# Specify the SYS password for the starter database.
oracle.install.db.config.starterdb.password.SYS=CBDsys12345#
# Specify the SYSTEM password for the starter database.
oracle.install.db.config.starterdb.password.SYSTEM=PDBsys12345#
# Specify the DBSNMP password for the starter database.
oracle.install.db.config.starterdb.password.DBSNMP=DBsnmp12345#
# Specify the PDBADMIN password required for creation of Pluggable Database in the Container Database.
oracle.install.db.config.starterdb.password.PDBADMIN=PDBadmin12345#
# Specify the management option to use for managing the database.
# Options are:
# 1. CLOUD_CONTROL - If you want to manage your database with Enterprise Manager Cloud Control along with Database Express.
# 2. DEFAULT   -If you want to manage your database using the default Database Express option.
oracle.install.db.config.starterdb.managementOption=DEFAULT
# Specify the OMS host to connect to Cloud Control.
# Applicable only when oracle.install.db.config.starterdb.managementOption=CLOUD_CONTROL
oracle.install.db.config.starterdb.omsHost=
# Specify the OMS port to connect to Cloud Control.
# Applicable only when oracle.install.db.config.starterdb.managementOption=CLOUD_CONTROL
oracle.install.db.config.starterdb.omsPort=
# Specify the EM Admin user name to use to connect to Cloud Control.
# Applicable only when oracle.install.db.config.starterdb.managementOption=CLOUD_CONTROL
oracle.install.db.config.starterdb.emAdminUser=
# Specify the EM Admin password to use to connect to Cloud Control.
# Applicable only when oracle.install.db.config.starterdb.managementOption=CLOUD_CONTROL
oracle.install.db.config.starterdb.emAdminPassword=
# SPECIFY RECOVERY OPTIONS                                                    #
# Recovery options for the database can be mentioned using the entries below #
# This variable is to be set to false if database recovery is not required. Else
# this can be set to true.
oracle.install.db.config.starterdb.enableRecovery=true
# Specify the type of storage to use for the database.
# It can be one of the following:
#   - FILE_SYSTEM_STORAGE
#   - ASM_STORAGE
oracle.install.db.config.starterdb.storageType=FILE_SYSTEM_STORAGE
# Specify the database file location which is a directory for datafiles, control
# files, redo logs.
# Applicable only when oracle.install.db.config.starterdb.storage=FILE_SYSTEM_STORAGE
oracle.install.db.config.starterdb.fileSystemStorage.dataLocation=/extended1/db/data
# Specify the recovery location.
# Applicable only when oracle.install.db.config.starterdb.storage=FILE_SYSTEM_STORAGE
oracle.install.db.config.starterdb.fileSystemStorage.recoveryLocation=/extended1/db/recovery
# Specify the existing ASM disk groups to be used for storage.
# Applicable only when oracle.install.db.config.starterdb.storageType=ASM_STORAGE
oracle.install.db.config.asm.diskGroup=/dev/oracleasm
# Specify the password for ASMSNMP user of the ASM instance.
# Applicable only when oracle.install.db.config.starterdb.storage=ASM_STORAGE
oracle.install.db.config.asm.ASMSNMPPassword=ASMsnmp122345#
# Specify the My Oracle Support Account Username.
# Example   : [email protected]
MYORACLESUPPORT_USERNAME=
# Specify the My Oracle Support Account Username password.
# Example    : MYORACLESUPPORT_PASSWORD=password
MYORACLESUPPORT_PASSWORD=
# Specify whether to enable the user to set the password for
# My Oracle Support credentials. The value can be either true or false.
# If left blank it will be assumed to be false.
# Example    : SECURITY_UPDATES_VIA_MYORACLESUPPORT=true
SECURITY_UPDATES_VIA_MYORACLESUPPORT=false
# Specify whether user doesn't want to configure Security Updates.
# The value for this variable should be true if you don't want to configure
# Security Updates, false otherwise.
# The value can be either true or false. If left blank it will be assumed
# to be false.
# Example    : DECLINE_SECURITY_UPDATES=false
DECLINE_SECURITY_UPDATES=flase
# Specify the Proxy server name. Length should be greater than zero.
# Example    : PROXY_HOST=proxy.domain.com
PROXY_HOST=
# Specify the proxy port number. Should be Numeric and atleast 2 chars.
# Example    : PROXY_PORT=25
PROXY_PORT=
# Specify the proxy user name. Leave PROXY_USER and PROXY_PWD
# blank if your proxy server requires no authentication.
# Example    : PROXY_USER=username
PROXY_USER=
# Specify the proxy password. Leave PROXY_USER and PROXY_PWD
# blank if your proxy server requires no authentication.
# Example    : PROXY_PWD=password
PROXY_PWD=
# Specify the proxy realm.
# Example    : PROXY_REALM=metalink
PROXY_REALM=
# Specify the Oracle Support Hub URL.
# Example    : COLLECTOR_SUPPORTHUB_URL=https://orasupporthub.company.com:8080/
COLLECTOR_SUPPORTHUB_URL=
# Specify the auto-updates option. It can be one of the following:
#   - MYORACLESUPPORT_DOWNLOAD
#   - OFFLINE_UPDATES
#   - SKIP_UPDATES
oracle.installer.autoupdates.option=SKIP_UPDATES
# In case MYORACLESUPPORT_DOWNLOAD option is chosen, specify the location where
# the updates are to be downloaded.
# In case OFFLINE_UPDATES option is chosen, specify the location where the updates
# are present.
oracle.installer.autoupdates.downloadUpdatesLoc=
# Specify the My Oracle Support Account Username which has the patches download privileges
# to be used for software updates.
# Example   : [email protected]
AUTOUPDATES_MYORACLESUPPORT_USERNAME=
# Specify the My Oracle Support Account Username password which has the patches download privileges
# to be used for software updates.
# Example    : AUTOUPDATES_MYORACLESUPPORT_PASSWORD=password
AUTOUPDATES_MYORACLESUPPORT_PASSWORD=

This is the simplest installation you can get, but if you want to do a fast response file based installation, there it is.

ORACLE SERVER AND UNIX TP MONITOR-1

제품 : ORACLE SERVER
작성날짜 : 2002-05-17
====================================================================
Subject: Oracle Server and UNIX Transaction Processing Monitors - 1
=====================================================================
PURPOSE
This file contains commonly asked questions about Oracle Server and UNIX
Transaction Processing Monitors (TPMs). The topics covered in this article are
     o What is a Transaction Processing Monitor (TPM)?
     o What is the X/Open Distributed Transaction Processing Model?
     o How does the Oracle Server works with TPMs?
     o How should I position TPMs with my customer?
     o What Oracle products must a customer purchase?
     o Where can my customer purchase a TPM?
     o Availability and packaging
Explanation & Example
What is a Transaction Processing Monitor?
=========================================
Under UNIX, a Transaction Processing Monitor (TPM) is a tool that coordinates
the flow of transaction requests between front-end client processes that issue
requests and back-end servers that process them. A TPM is used as
the "glue" to coordinate transactions that require the services of several
different types of back-end processes, such as application servers and
resource managers, possibly distributed over a network.
In a typical TPM environment, front-end client processes perform screen
handling and ask for services from back-end server processes via calls to the
TPM. The TPM then routes the requests to the appropriate back-end server
process or server processes, wherever they are located on the network. Through
configuration information, the TPM knows what services are available and where
they are located. Generally, the back-end server processes are specialized so
that each one handles one type of requested service. The TPM provides
location transparency as well and can send messages through the network
utilizing lower-level transport services such as TCP/IP or OSF DCE.
The back-end servers process the requests as necessary and
return the results back to the TP monitor. The TP monitor then routes
these results back to the original front-end client process.
A TPM is instrumental in the implementation of truly distributed processing.
Front-end clients and back-end processes have no knowledge of each
other. They operate as separate entities, and it is this concept that provides
flexibility in application development. Front-end and back-end processes are
developed in the UNIX client-server style, with each side optimized for its
particular task. Server functionality can be deployed in stages, which makes
it easy to add functionality as needed later in the product cycle. It also
makes it easy to distribute both the front-end and back-end processes
throughout the network on the most appropriate hardware for the job. In
addition, multiple back-end server processes of the same type might be
activated to handle increasing numbers of users.
What is the X/Open Distributed Transaction Processing Model?
============================================================
The X/Open Transaction Processing working group has been working
for several years to establish a standard architecture to implement
distributed transaction processing on open systems. In late 1991,
X/Open published the initial Distributed Transaction Processing (DTP)
model specification and defined the first of several interfaces that
exist between the components of the model. Subsequently, other publications
and a revised model specification have been published.
An important function of the TPM in the X/Open DTP model is the
synchronization of any commits and rollbacks that are required to complete
a distributed transaction request. The Transaction Manager (TM) portion
of the TPM is the entity responsible for ordering when distributed commits
and rollbacks will take place. Thus, if a distributed application program
is written to take advantage of the TM portion of the TPM, then it,
and not the DBMS, becomes responsible for enabling the two-phase commit
process. Article 2 has more detail on this model.
How does the Oracle Server work with TPMs?
==========================================
When a TPM is used without invoking an X/Open TM component to manage the
transactions, Oracle Server needs no special functionality. The transaction
will be managed by Oracle itself. However, when the TPM X/Open TM component
is used to manage the transaction, the Oracle Server, that is the Oracle DBMS,
acts as a Resource Manager--a type of back-end process. In the case of
TPM-managed transactions, the TM needs a way to tell the RMs about the stages
of the transaction. This is done by a standard, X/Open defined interface
called XA. Article 2 of of this document gives more information about both
the X/Open model and Oracle7's use of XA.
Because the XA interface provides a standard interface between the TM and the
resource manager, it follows that the TM can communicate with any XA-compliant
resource manager (e.g., RDBMS), and, conversely, that a resource manager can
communicate with any XA-compliant TM. Thus, the Oracle Server, beginning with
Oracle7, works with any XA-compliant TM.
How should I position TPMs with my customer?
============================================
There's been a great deal of confusion about the need for TPM technology. Some
software suppliers, most notably IBM, will assert that a TPM like CICS is a
necessary requirement for high volume OLTP. Other vendors will assert that
there is seldom a need for such technology. And yet others promote TPMs as
providers of higher transaction throughput.
From Oracle's standpoint, customers might choose TPM technology under any of
the following conditions:
1. For heterogeneous database access, especially for 2PC capability
     This means that a TPM can be used to coordinate 2PC between Oracle
     DBMS and any other XA-compliant database, such as Informix. This
     does NOT provide SQL heterogeneity - SQL calls to Oracle DBMS may be
     different than SQL calls to Informix. The TPM handles the routing,
     communication, and two-phase commit portion of the transaction, but
     does not translate one type of SQL call into another.
2. For transaction monitoring and workload control
     The leading TPMs supply tools to actively manage the flow of
     transactions between clients and servers and to load balance the work
     load across all available processors on a network, not just on a
     single multi-processor system. Some TPMs also have the ability to
     dynamically bring up additional back-end services during peak work
     hours.
3. For more flexible application development and installation
     One of the key features of the DTP model is application modularity.
     Modularity, that is, the decomposition of a large program into small,
     easily defined, coded and maintained "mini-programs" makes it easy to
     add new functionality as needed. Modularity also makes it much easier
     to distribute the front-end and back-end processes and the resource
     managers across hardware throughout a network.
4. For isolating the client from details of the data model
By using the service oriented programming model, the client program
     is unaware of the data model. The service can be recoded to use a
     different one with no change to the client. To get this advantage,
     the application developer must explicitly code the server and client
     to fit the service model.
5. For connection of thousands of users
     TP Monitors, because of their three-tier architecture, can be used
     to connect users to an intermediate machine or machines, removing
     the overhead of handling terminal connections from the machine
     actually running the database. See Article 4 for more information.
There are also several cases where TPM technology is not the right answer.
These include:
1. If the customer is simply looking for a performance improvement
     The customer may have heard a theory that "higher performance
     is possible for large scale applications only if they use a
     TP monitor". First, no performance gain can be achieved for
     existing applications; in fact, they won't even run under a TP
     Monitor without recoding. Second, performance improvements have
     only been documented for large numbers of users, and "large"
     means many hundreds or thousands. Without a TP Monitor,
     Oracle Server can handle several hundred users with its normal
     two-task architecture and several times that using the Multi
     Threaded Server. For more on performance, see Article 4.
2. If the customer has made large investment in his existing Oracle
applications
     TP monitor applications must be designed from the ground up to take
     advantage of TP monitor technology. Current Oracle customers will find
     it difficult to "retrofit" a TP monitor to their existing applications.
     The Multi Threaded Server, on the other hand, allows the use of
     existing Oracle applications without change.
3. If the customer is committed to the Oracle tool set
     Currently, none of Oracle's front-end tools (Oracle Forms, etc.) is
     designed to work with TP monitors. It is possible to invoke a
     TP Monitor by using user exits. However, the fact that the TP
     Monitor model hides the data model from the client means that only
     the screen display parts of Forms can be used, not the automatic
     mapping from screen blocks to tables.
4. If the customer does not have a staff of experienced software engineers
     This is still very young technology for UNIX. There is not a lot of
knowledge in the industry on how to build TP monitor applications or
what techniques are most useful and which are not. Furthermore,
     integrating products from different vendors, even with the support
     of standard interfaces, is more complex than deploying an integrated
     all-Oracle solution. Because TP monitor technology is fairly
     complex, we recommend that you let the TP monitor supplier promote
     the virtues of their technology and differentiate themselves from
     their competitors.
What Oracle products must a customer purchase?
==============================================
If your customer is only interested in building Oracle-managed TP Monitor
transactions, the only Oracle products required are the Oracle Server
and the appropriate Oracle precompiler for whatever language the
application is being written in--most likely C or Cobol. If TPM-managed
transactions are required, the Oracle7 Server with the distributed option
is also required. SQL*Net is optional because the TPM takes care of the
network services. Article 2 describes when you would choose to have the TP
Monitor manage the transactions.
Where can my customer purchase a TPM?
=====================================
There are many vendors offering the UNIX TPM products. (Oracle does not
relicense TPMs.) Information on the most well known products is provided
below:
The following support XA:
Product & Vendor     FCS          Known OS/Platform Ports
"TUXEDO System/T"     1986          UNIX SVR4 & SVR3: Amdahl, AT&T,
UNIX System Laboratories          Bull, Compaq, Dell, Fujitsu, ICL,
190 River Road                    Motorola, Olivetti, Pyramid,Sequent,
Summit, NJ 07901               Sun, Toshiba, Unisys, NCR, Stratus
                         Other: IBM AIX, HP/UX, DEC Ultrix
"TOP END"      1992          UNIX SVR4: NCR
NCR Corporation
1334 S. Patterson Blvd.
Dayton, OH 45479
"ENCINA"          1992          IBM AIX, HP, Sun (SunOS and Solaris)
Transarc Corporation               Other: OS/2, DOS, HP-UX, STRATUS
707 Grant Street (Depends on DCE)
Pittsburgh, PA 15219
"CICS/6000" 1993          AIX: IBM
IBM Corporation                    (Depends on DCE)
"CICS 9000" 1994          HP-UX
HP
The following do not currently support XA:
Product & Vendor     FCS          Known OS/Platform Ports
"VIS/TP"          unknown          unknown
VISystems, Inc.
11910 Greenville Avenue
Dallas, TX 75243
"UniKix"          1990          UNIX: ARIX, AT&T, NCR, Pyramid,
UniKix                     Sequent, Sun, Unisys
"MicroFocus           1993          SCO Unix, AIX
Transaction System"
Micro Focus
26 West Street
Newbury RG13 1JT
UK
There are also several third parties who are reselling the products listed
above.
In addition, Groupe Bull, Digital, Siemens-Nixdorf, and several other hardware
vendors are planning to redesign their proprietary TPMs to be XA-compliant and
suitable for use on UNIX systems.
Availability and Packaging
==========================
On what platforms is the XA Library available?
Oracle provides the XA interface with Oracle7 Server on all platforms that
support an XA-compliant TPM. Support for XA is included as part of the
Oracle7 Server distributed option and has no extra charge in and of itself.
Which version of XA does Oracle Server support?
Oracle7 Server supports the Common Application Environment (CAE) version of
XA, based on the specification published by X/Open in late 1991. It will
require that the TM also be at that level. This means Tuxedo /T version 4.2,
for example.
Oracle Server supports all required XA functions. There are some optional
features Oracle Server does not support, such as asynchronous operation.
None of those options affect application programming.
Page (2/4)
This file contains commonly asked questions about Oracle Server and UNIX
Transaction Processing Monitors (TPMs). The topics covered in this article are
     o Oracle Server Working with UNIX TPMs
     o TPM Application Architecture
The questions answered in part 2 provide additional detail to the information
provided in part 1.
Oracle Server Working with UNIX TP Monitors
===========================================
Do I need XA to use Oracle Server with TPMs? If I don't use it, what are
the consequences?
There are a number of real applications running today with Oracle Server and
TPMs but not using XA. To use a TPM with Oracle without using XA, the user
would write an "application server" program which could handle one or more
"services". For example, a server program might handle a service called
"debit_credit". The key requirement is that the entire transaction,
including the "commit work", must be executed within a single service. This
is the restriction which XA will remove, as we'll see later. Each
server process can serially handle requests on behalf of different clients.
Because a server process can handle many client processes, this can
reduce the total number of active processes on the server system,
thereby reducing resource requirements and possibly increasing overall
throughput.
When Oracle is used with a TPM in this mode, we call it an Oracle-managed
transaction since the transaction commit or rollback is done with a SQL
statement.
What is XA? How does XA help Oracle7 work with UNIX TPMs?
XA is an industry standard interface between a Transaction Manager and a
Resource Manager. A Resource Manager (RM) is an agent which
controls a shared, recoverable resource; such a resource can be
returned to a consistent state after a failure. For example, Oracle7 Server
is an RM and uses its redo log and undo segments to be able to do this.
A Transaction Manager (TM) manages a transaction including the
commitment protocol and, when necessary, the recovery after a failure.
Normally, Oracle Server acts as its own TM and manages its own commitment
and recovery. However, using a standards-based TM allows Oracle7 to
cooperate with other heterogeneous RMs in a single transaction.
The commonly used TPMs include a TM component for this purpose. In order to
use the TM capability of the TPM rather than Oracle7's own transaction
management, the application uses a transaction demarcation API (called TX)
provided by the TPM rather than the SQL transaction control statements (e.g.
"commit work"). For each TX call, the TM then instructs all RMs, by the
appropriate XA commands, to follow the two-phase commit protocol. We
call this a TPM-managed transaction.
The following picture shows these interfaces within a monolithic application
program model. This is the model most commonly described in the
DTP literature. We'll see later what the picture looks like when we add
Oracle7 and when we switch to a modularized client-server application
program model.
          | |
          | |
          | Application Program (AP) |
          | |
          | |
               | | |                    |
Resource Manager API | | | |
(e.g. SQL) -----|--|------------- | TX API
          | | v |          |
          --------|-------------     |          |
          | v | | v
     ---------------------- | | --------------------
     | | | | | |
     | Resource | | |<----->| Transaction |
     | Managers | |--- | Manager |
     | (RMs) | |<-------->| (TM) |
     | |--- | |
     | |<----------->| |
     ---------------------- XA --------------------
                    Interface
The XA interface is an interface between two system components, not
an application program interface; the application program does
not write XA calls nor need to know the details of this interface.
The TM cannot do transaction coordination without the assistance of
the RM; the XA interface is used to get that assistance.
How does the DTP Model support client-server?
The above picture was actually simplified to make it easier to explain
the role of XA. In a true distributed transaction architecture, there
are multiple applications, each with an Application Program, a Resource
Manager, and a Transaction Manager. The applications communicate by
using a Communication Resource Manager. The CRM is generally provided
as a component of the TPM. It includes the transaction information when
it sends messages between applications, so that both applications can
act of behalf of the same transaction. The following picture
illustrates this:
Client Application
| AP |
||| | |
SQL ||| | TX | CRM
||V V | API
-||-- ----- |
| |V | | | V
--|-- |<---| | -----
| V || | | | |
----- |<----| TM |<-->| CRM |
| || | |XA+ | |
| RMs |<-----| | -----
| | XA | | A
----- ----- | Server Application
| -----------------------------
| | AP |
| -----------------------------
| ||| | |
| SQL ||| | TX | CRM
| ||V V | API
| -||-- ----- |
| | |V | | | V
| --|-- |<---| | -----
| | V || | | | |
| ----- |<----| TM |<-->| CRM |
| | || | |XA+ | |
| | RMs |<-----| | -----
| | | XA | | A
| ----- ----- |
| |
| |
-------- |
/ |
/ |
/ |
Most TP Monitor products include both a TM and a CRM, and also provide
additional functions such as task scheduling and workload monitoring.
What is XA+? What does Oracle need to do to comply with it?
XA+ is an interface that lets the X/Open model actually be distributed
because it allows a communication resource manager to tell a TM on the
server that a message from a client just came in for a particular
transaction. Oracle is not currently planning to provide an X/Open
communication resource manager, so we don't have any plans right now
to do XA+. Version 2 of the DTP model paper from X/Open describes it.
The status of the current XA+ specification is "snapshot".
When would I choose an Oracle-managed transaction vs a TPM-managed
transaction?
Oracle Server is very efficient at managing its own transactions. If
the TPM manages the transaction, in general some additional overhead
will be incurred.
The two main reasons a customer might prefer to use a TPM-managed
transaction are as follows:
(1) He may need to update RMs from different vendors. Experience so far
has been that the most common case is wanting to update both Oracle and
a TP Monitor managed resource such as a transactional queuing service
in the same transaction (see Article 3).
(2) He may want to use the model of having several different services in
a transaction, even to the same database. For example, the
"debit_credit" service could be split into a "debit" service and a
"credit" service. This is a very attractive model, but this type of
modularity does exact a performance penalty (see Article 4).
Can I get a version of XA to run on Oracle Server version 6?
No, the XA functionality uses two underlying mechanisms in the Oracle
Server which are not available in version 6: two-phase commit and
session switching. The upi calls for these functions do not not exist
in version 6.
When would I use XA vs Oracle7 to coordinate all-Oracle distributed
transactions?
Generally speaking, Oracle Server should be used to coordinate all-Oracle
distributed transactions. The main reason for using XA to coordinate
transactions would be that you want to use the TP Monitor service-oriented
architecture. That is, you would like to construct an application built of
services and service requests in order to benefit from the modularity and
workload control such an environment provides.
TP Monitor Application Architecture
===================================
What might a TP Monitor application look like?
Most TPM applications will consist of two more more programs, where
there are front-end client programs which request services and back-end
server programs which provide services. In this case, the TPM supplies an
additional capability which is transactional communication. The client
describes the boundaries of the transaction, through the use of the TX API,
and the TPM relays that transaction information to each requested service.
The overall application structure generally looks like the following in the
client-server model. The "TP Monitor Services" box is not necessarily a
process. It could be one or more processes, or just libraries coordinating
through shared memory. Each client process and server process could be on
a different machine. Normally, the application server processes would be
connected to their Oracle Server processes using the IPC driver; the TPM
would be used to deliver messages between application client processes on
one machine and application server processes on another. However, the
application server processes could also be connected with the standard
Oracle SQL*Net to shadow processes on different machines. This might be
useful if one of the databases was on a machine which did not support TPMs.
|Application| |Application| |Application|
| Client 1 | | Client 2 | | Client 3 |
| | | | | |
\ TPM API | TPM API / TPM API
| |
| TP Monitor Services |
| |
     | --------------------- |
| | Transaction Manager | |
---------------|---------------|---------------------
TPM API | | XA | XA | TPM API
| | inter- | inter- |
          | | face | face |
          | | | |
----------- | | -----------
|Application| | | |Application|
| Server 1 |--- ---| Server 2 |
| (Pro*C) | | | | (Pro*C) |
| SQL | SQL
| | | |
| Resource ----------- ----------- |
| Manager | | | | |
| | Oracle7 | | Oracle7 | |
| | Server | | Server | |
| | Process | | Process | |
| | | | | |
| ----------- ----------- |
| | | |
| ----------------------------------------------------- |
| | | |
| | SGA | |
| | | |
| ----------------------------------------------------- |
| |
Application client programs might be written in C and be linked with
TPM libraries. Alternatively, they could use a screen painter product.
Application server programs would be written in Pro*C or Pro*COBOL and
be linked with TPM libraries, the normal Oracle7 user-side libraries
and libxa.a. The Oracle7 Server process is the regular Oracle7 executable.
More complicated application architectures can also be constructed. Most of
the TPMs allow a server to become a client of another service, so you can
involve additional servers.
Could I use Oracle7's Multi Threaded Server as the SQL*Net connection in the
previous picture?
Yes, but that will not be needed in many cases. For example, both
application server processes in the previous picture could talk to a
single Oracle7 Server process through the Multi Threaded Server in the
previous picture. However, since the TPM architecture typically reduces
the number of server processes, the reduction in processes using Multi
Threaded Server may be less significant than in an architecture without
TPMs. If the application will use database links, however, then MTS will
be required.
How do I write an Oracle TP Monitor application?
The actual API used to talk to the TPM varies between vendors, so you need
to get the documentation from the vendor. However, all have a way to
indicate where a transaction begins and ends and a way to send a request
and receive a response from a client to a server. Some use an RPC model,
some use a pseudo-RPC model, and some use a send/receive model. The TX API
described earlier is a subset of the TPM API as defined by each of
the TPM providers.
The client program and server program might look something like the
following examples. We h (such as Tuxedo's
"tpacall
Reference Ducumment
---------------------

hello,
the role is the same on all plattforms. the reports server takes requests for running reports, spawns an engine that executes the request. in addition to that, the server also provides scheduling services and security features for the reports environment.
regards,
the oracle reports team

Problem installing Oracle forms and report in windows 7

I have a problem while installing Oracle forms and reports in windows 7 64 bit
The error is : [as] [ERROR] [] [oracle.as.provisioning] [tid: 20] [ecid: 0000IY5_e_EApIRMyYAhMG1BuDGr00000B,0] [[
oracle.as.provisioning.exception.ASProvWorkflowException: Error Executing workflow.
at oracle.as.provisioning.engine.WorkFlowExecutor._createDomain(WorkFlowExecutor.java:688)
at oracle.as.provisioning.engine.WorkFlowExecutor.executeWLSWorkFlow(WorkFlowExecutor.java:393)
at oracle.as.provisioning.engine.Config.executeConfigWorkflow_WLS(Config.java:866)
at oracle.as.install.classic.ca.standard.StandardWorkFlowExecutor.execute(StandardWorkFlowExecutor.java:65)
at oracle.as.install.classic.ca.standard.AbstractProvisioningTask.execute(AbstractProvisioningTask.java:26)
at oracle.as.install.classic.ca.standard.StandardProvisionTaskList.execute(StandardProvisionTaskList.java:61)
at oracle.as.install.classic.ca.ClassicConfigMain.doExecute(ClassicConfigMain.java:124)
at oracle.as.install.engine.modules.configuration.client.ConfigAction.execute(ConfigAction.java:335)
at oracle.as.install.engine.modules.configuration.action.TaskPerformer.run(TaskPerformer.java:87)
at oracle.as.install.engine.modules.configuration.action.TaskPerformer.startConfigAction(TaskPerformer.java:104)
at oracle.as.install.engine.modules.configuration.action.ActionRequest.perform(ActionRequest.java:15)
at oracle.as.install.engine.modules.configuration.action.RequestQueue.perform(RequestQueue.java:63)
at oracle.as.install.engine.modules.configuration.standard.StandardConfigActionManager.start(StandardConfigActionManager.java:158)
at oracle.as.install.engine.modules.configuration.boot.ConfigurationExtension.kickstart(ConfigurationExtension.java:81)
at oracle.as.install.engine.modules.configuration.ConfigurationModule.run(ConfigurationModule.java:83)
at java.lang.Thread.run(Thread.java:619)
So I Google for it and found that this is version mismatch (May be I am wrong) and it tells that I have to install WLS - 10.3.2 with ofm_pfrd_win_11.1.1.2.0_64 (1 to 4)
But I am unable to get wls version 10.3.2.
For better understanding I am listing my installers :
(I) Windows 7 Ultimate 64 Bit
(II) (Oracle 11g) win64_11gR2_database (1 & 2)
(III) ofm_pfrd_win_11.1.1.2.0_64 (1 to 4)
(IV)wls1033_generic.jar , wls1033p_generic.jar , wls1035_generic.jar
(V)accessbridge-2_0_2-fcs-bin-b06
(VI)ofm_rcu_win32_11.1.1.2.1_disk1_1of1,ofm_rcu_win_11.1.1.3.1_disk1_1of1
(VII) ofm_wc_generic_11.1.1.5.0_disk1_1of1
(VIII)jdk-6u38-nb-7_2_1-windows-i586-ml , jdk-6u38-windows-x64
(IX) oepe-wls-indigo-installer-11.1.1.8.0.201110211138-10.3.6-win32
(X)wls1033_oepe111150_win32.exe
(XI)wls1035_win32.exe
(XII)wls1035_oepe111172_win64
(XIII)oepe-indigo-installer-12.1.1.0.1.201203120349-12.1.1-win64
After the installation while configure the forms reports, I am stuck while creating domain.
steps I follow is :
(i) Install Windows 7 Ultimate 64 Bit
(ii) (Oracle 11g) win64_11gR2_database (1 & 2)
(iii) wls1033_generic.jar
(iv) accessbridge-2_0_2-fcs-bin-b06
(v)ofm_rcu_win32_11.1.1.2.1_disk1_1of1
(vi) ofm_pfrd_win_11.1.1.2.0_64 (1 to 4)
Please any body help, for the installation of oracle forms and reports.
I have a formatted Windows 7 Ultimate
Where I have installed Adobe Acrobat Reader
IIS server from windows installer
Now I want to know the exact procedure so that i can run the forms and report in my machine.
This is my first installation of Oracle forms & Reports, so please do not pre assume about my understanding (Like "to install this he surely did this environment settings" )
Please specify all the steps
Furthermore if Another software I have to download then please tell me.
And I will be grateful if you specify the mistakes in my side.
Looking forward with anticipation.

Solved, Thank you

How to Read Statspack Report in Oracle 11.2g Standard Edition

Dear All,
I am using Oracle 11.2g Standard Edition in Lab.
For the performance tuning, How can i read the Statspack Report ?
Please Note- I can't use the Oracle AWR feature due to License Limitation. As well as if i will generate AWR report with Oracle Standard Edition, it will be not proper and print error " DB time is zero for any interval Report.
-sumit
Bangalore,India

Hi Summit,
In oracle 11g you will be finding the spcreate.sql script in the same directory as hemant said just run that script
@@$ORACLE_HOME/rdbms/admin/spcreate.sql
And follow the normal procedure which you do for creating the statspack report using the perfstat user
can you please refer to below link for more details:
stack pack report in oracle 11g
Also see the link given by Aman sir.
Hi Aman sir its good to see you after long time.
Best regards,
Rafi.
http://rafioracledba.blogspot.com/

Differences in NLS_LANGWE8ISO8859 between Oracle 8i and Oracle 9i or higher

Are there any differences in NLS_LANG WE8ISO8859P1between Oracle 8i and Oracle 9i or higher?
please, there is a document that explains what.
thank you very much.

Ok,
I want to know whether there was any difference when using this NLS_LANG between 8 and oracle 9.
I read many documet about unicode, but i want to know this question.
If NLS_LANG is a standard there isn´t changes between the to versions.

Choice between UPK in-application help and standard EBS help

Hi,
We are on a EBS 11.5.10 project, implementing UPK.
We got UPK in-application help working; changed custom.pll, set the profile option, everything fine.
Now we would like the users to have the choice between UPK help (default) and standard EBS help.
Therefore we opened the In-Application Support Player Configuration, and created a new Tab:
Type: Oracle E-Business Suite help
Tab Text: EBS help
URL: ?
Whatever we put in the URL, it won’t display the standard EBS context sensitive help. We can see the ‘EBS help’ tab when selecting ‘window help’ in the application but the page is blank or shows an error message.
Do you have any tips on how to get this working?
Thanks,
Abe de Beer
EBS Financials consultant
Oracle Belgium

Hi,
I have the exact same requirtment, Could you please give the step what you have done so that it would be helpfull. Also after publishing the content on the i am not seeing the "Application Option" i am seeing the smart help. do we need to configure on "Application Option" or on smart help. Where ever is see the doc it says configure oracle_gateway.html but i dont see oracle/hemi folder at all. do know if there is a set up that has to be done to get this option (UPK 11.10.1)
Thanks

Expense report and Standard Invoice in ap.

hi
Difference b/w Expense report and Standard Invoice in ap. plz give me example
thks

Hi,
AFAIK Oracle EBS does not keep that sort of info. When looking for the payment you may know that both documents were included in that payment. But when looking at the the invoice or at the DR/CR Memo you will not see any cross reference between them.
Octavio

External table in Oracle 10g and Windows server 2003 problem

I'm having a problem accessing an external table in an Oracle 10g and Windows 2003 server environment. The disk is remote (mapped) to the server. It's the usual access errors, kup-04001 or kup-04063.
I have the [seemingly] exact same setup in an Oracle 9i and Windows 2000 server environment which works perfectly. Services run as local SYSTEM and SYSTEM has full permissions on the disk. Directories exist and so do the permissions to the directories.
In the Oracle 10g and Windows 2003 environment, services run as local SYSTEM and SYSTEM has full permissions on the mapped disk. Directories exist and so do the permissions to the directories.
This obviously effects mappings, deployments, etc.
Does anyone know if something changed in either the db or the os?
Thank you,
Michael

Thank you for your reply.
Your proposal is the standard solution. As a matter of fact, that's how it is on my "old" system. Server "A" Oracle services are started by SYSTEM. Server "B" Oracle services are started by SYSTEM and is where the flat files reside. SYSTEM has full permissions on a disk local to Server "B". Database directoriies defined on Server "A" point to Server "B" remote disk. External Tables on Server "A" are defined with directories that point to Server "B" remote (mapped) disk. I have no problems with this configuration.
I'm having a problem acheiving the same configuration with Oracle 10g and Windows 2003. I guess I'm baffled over the fact it isn't working the same way as my "old" environment. Why shouldn't it? Oracle (and you) want me to start services as a specific user. It shouldn't have to be that way unless something changed in the way the database makes calls to the os or if Microsoft slipped something in with one of it's numerous security patches.

Oracle Practices and Standards

Similar Messages

Maybe you are looking for