rp e1perf rac

7/28/2019 Rp e1perf Rac

1/51

Oracle 10g R2 Real ApplicationCluster (RAC) with EnterpriseOne

An Oracle JD Edwards EnterpriseOne

Performance and Tuning Paper

July 2006


2/51

Oracle 10g R2 Real Application Cluster (RAC) with EnterpriseOne Page i

PURPOSE STATEMENT

This document provides considerations when reviewing system performance relative toyour JD Edwards EnterpriseOne system. Many factors can influence performance andyour results may differ depending on many different variables.

This document is intended for information purposes only, and may not be incorporatedinto any contract. It is not a commitment to deliver any material, code, or functionality,and should not be relied upon in making purchasing decisions. The development,

release, and timing of any features or functionality described for Oracles productsremains at the sole discretion of Oracle. Updates and enhancements are provided inaccordance with Oracles Technical Support Policies at:

www.oracle.com/support/collateral/oracle-technical-support-policies.pdf


3/51

Copyright Oracle. All rights reserved. Oracle 10g R2 Real Application Cluster (RAC) with EnterpriseOne Page ii

Oracle 10g R2 Real Application Cluster

Introduction........................................................................................................................................................1Test Objectives .............................................................................................................................................. 1Red Hat Linux Test Environment..............................................................................................................1

Requirements......................................................................................................................................................3Cluster Hardware Requirements .................................................................................................................3Cluster Software Requirements...................................................................................................................3Oracle Requirements.....................................................................................................................................4EnterpriseOne Requirements......................................................................................................................4

Steps used for Client Fail-Over Test...............................................................................................................5Procedural Steps............................................................................................................................................5Steps used for UBE Batch Fail-Over Test.....................................................................................................6Procedural Steps............................................................................................................................................6

Applications Tested within EnterpriseOne....................................................................................................7EnterpriseOne Fastpath Reference ............................................................................................................7

Load Balancing RAC Option...........................................................................................................................8Load Balancing Options...............................................................................................................................8Load Balancing Simulation ..........................................................................................................................8Load Balancing Observations......................................................................................................................8

Fail-Over RAC Option .....................................................................................................................................9Fail-Over Explanation..................................................................................................................................9Fail-Over Simulation.....................................................................................................................................9

Fail-Over Observations................................................................................................................................9

EnterpriseOne Enterprise Server Fail-Over Behavior........................................................................9Web Client Fail-Over Behavior .............................................................................................................. 9Fail-Over Behavior Summaries.............................................................................................................10

Preliminary Recommendations......................................................................................................................12Preliminary Recommendations .................................................................................................................12

EnterpriseOne Supported Versions..............................................................................................................14EnterpriseOne Supported Versions .........................................................................................................14

Related Reference Materials ...........................................................................................................................14General All Plaforms ..................................................................................................................................14Red Hat Linux (x86) ...................................................................................................................................14Microsoft Windows (x86) ..........................................................................................................................14Solaris (UltraSPARC)..................................................................................................................................15AIX (IBM pSeries) ......................................................................................................................................15HP-UX (PA-RISC) .....................................................................................................................................15

Reference Internet Sites ..................................................................................................................................15


4/51


5/51

Copyright Oracle. All rights reserved. Oracle 10g R2 Real Application Cluster (RAC) with EnterpriseOne Page 1

Oracle 10g R2 Real Application Cluster

INTRODUCTION

Oracle 10g R2 Real Application Cluster (RAC) is an option offered with the Oracle 10g R2 Database Enterprise

Edition (10.2.0.1). Following are the benefits of implementing the RAC option:

RAC is a shared cache architecture that overcomes the limitations of the traditional shared nothing and

shared disk cluster solutions.

RAC software is designed to provide a highly scalable and available database solution for business

applications.

RAC allows a large number of transactions to be separated onto many machines for fast parallel

execution.

RAC provides high throughput for large workloads and scales incrementally for growing user populations.

Test Objectives

The desired results of this test are to evaluate, document, and publish the information gathered that will address

how to install, implement, and configure Oracle 10g R2-RAC software with JD Edwards EnterpriseOne 8.96.

There are two main areas of functionality that will specifically be addressed: scalability and availability.

Scalability is addressed by determining EnterpriseOne softwares ability to use the load balancing features of

Oracle 10g R2-RAC. The load balancing specifics are outlined below.Availability is addressed by determining the ability of EnterpriseOne to use the fail-over features of Oracle 10g R2-

RAC. The fail-over specifics are outlined below.

Due to time and resource constraints, this project was completed using only Linux based environments for

database, application, and enterprise servers. The objective is to determine the interaction of EnterpriseOne with

Oracle RAC software. This test produced EnterpriseOne user experience information that we believe is relevant to

other operating systems and physical hardware platforms.

In the future, if additional testing is performed with Oracle RAC, a different operating system and set of hardware

will be used, and the results added to this document.

Red Hat Linux Test Environment

Testing was conducted using the following:

EnterpriseOne 8.96 GA with 8.11-SP-1


6/51


Oracle 10g R2 (version 10.2.0.1) database software with the Real Application Cluster (RAC) features

installed

Oracle Cluster File System

Oracle Cluster Ready Services

Oracle Application Server and Oracle Automatic Storage Management on HP Proliant with Red Hat

Linux 3.0 Update 6

Installation prerequisites, suggestions, and examples are shown to help implement the RAC environment. The

EnterpriseOne software functionality, behavior, and end user experience observed during test scenarios is

explained. This establishes the baseline for EnterpriseOne 8.96 GA configured with the Oracle RAC software.

Proper installation and configuration methods are identified to insure successful implementation of the Oracle

RAC option. We use common installation processes that mirror the steps you use to implement the software on

this platform.

This paper can be used by technical users, installers, system administrators, and programmers who implement,

maintain, or develop applications for your EnterpriseOne system. However, this paper does not address every

configuration variable that might be encountered in this process.

The information was gathered while testing the Oracle 10g R2 RAC environment. Not all possible hardware and

software combinations were tested. Your system may show different results.

When RAC is used with EnterpriseOne you should create a RAC environment using the Oracle 10.2.0.1 version of

Database Software. As newer versions are released, additional testing will be conducted and the results noted in an

updated version of this document.


7/51


REQUIREMENTS

Cluster Hardware Requirements

A cluster is a group of independent computers working together as a single computer. A cluster is composed of

two or more computers, called cluster members, which are connected using one or more physically independent

networks called cluster interconnects. Cluster members use one or more shared buses to access the shared storage

system.

Todays clustering technology is designed to keep server-based applications running, even when an individual

component fails.

Cluster Software Requirements

Cluster software (either running on Oracle or the operating system) links the cluster members together so they

function as a single computer. The shared bus storage is usually an external storage device that is used by the

cluster software to store files that are accessible to all cluster members. Storage can be either a set of unformatted

shared disk devices, also referred to as raw devices, or a shared file system, also referred to as a cluster file system.

Vendors usually supply a utility that can partition the external shared hard disks into multiple raw devices. Eachraw device can function as an Oracle data file and is available to all members in a cluster.

For this test, the Oracle Cluster File System and Oracle Cluster Ready Services were used as the cluster software to

interconnect the nodes. Oracle Automatic Storage Management was also implemented as the disk management

software.


8/51


Oracle Requirements

Oracle 10g R2 RAC is an option of Oracle 10g R2 that harnesses the processing power of multiple, interconnected

computers in a cluster. All software, including operating-system-specific cluster software that is required by Oracle

10g R2 RAC, must also be installed on each cluster member, except when using an Oracle cluster file system.

The main difference between Oracle 10g R2 and Oracle 10g R2 RAC is that RAC is a multi-Oracle-instance

environment that uses cluster software to communicate between different Oracle instances on cluster members.

Therefore, using multiple Oracle 10g R2 RAC instances can be functionally identical to using a single Oracle 10gR2 instance.

In a multi-Oracle10g R2-RAC instance environment, each Oracle instance must have its own:

Oracle System Identifier (SID)

Redo Log Groups

Private rollback segments for manual undo management, or private undo tablespace for automatic undo

management

Note: For automatic undo management, you do not need to create private rollback segments for each Oracle

instance.

EnterpriseOne Requirements

This test was conducted with EnterpriseOne 8.96 GA - refer to the EnterpriseOne Minimum Technical

Requirement documents to verify the specific platforms and versions that support Oracle RAC.

Shared Database for

Oracle

Instances 1 and 2

Operating System

Cluster Software

Oracle 10g R2 RAC

Instance 2

Cluster Member 2

Operating System

Cluster Software

Oracle 10g R2 RAC

Instance 1

Cluster Member 1

Cluster Interconnect

Shared

Access

Shared

Access


9/51


STEPS USED FOR CLIENT FAIL-OVER TEST

Procedural Steps

Database 1 node is running Database is started reported as Database Opened.

Database 2 node is not running Database is stopped.

Database 1 node Oracle Listener is running.


The Enterprise Server System is started, making the kernel connections to Database 1 node.

The Oracle Application Server is started.

The HTTP Server is started.

Begin an EnterpriseOne session web client.

Begin performing the work as outlined in Appendix A following the script steps.

Complete about 50% of the script, stopping in the middle of making the entries.

Start Database 2 node Once the Database reports Database Opened proceed.

Fail Database 1 node use command shutdown abort.

Proceed on following the script steps.

If possible, finish the script and check the results.

If the test is successful and the entered information is available, document the user experience.

If the test fails, document the user experience.

Reset the entire environment so every test begins with the same hardware and software configuration.


10/51


STEPS USED FOR UBE BATCH FAIL-OVER TEST

Procedural Steps

Database 1 node is running Database is started reported as Database Opened.

Database 2 node is not running Database is stopped.



The Enterprise Server System is started, making the kernel connections to Database 1 node.

The Oracle Application Server is started.

The HTTP Server is started.

Begin an EnterpriseOne session web client.

Begin performing the work as outlined in Appendix A following the script steps for Tests 2 and 12.

Complete the entries and submit the job to run.

Start Database 2 node Once the Database reports Database Opened proceed.

Fail Database 1 node use command shutdown abort.

Proceed to monitor the running job.

If the job reports DONE, verify the report and the work that was done.

If the job continues to run and not appear to finish, view all the appropriate logs and determine what is

happened.

If the job appears to be running but the logs indicate a connection can not be made, either let the job

continue to run and hope it finishes, or terminate the job, and determine why it failed and what else might

be tried. Re-test the failed job and observe the results. If the test is successful and the entered information is available, document the user experience.

If the test fails, document the user experience.

Reset the entire environment so every test begins with the same hardware and software configuration.


11/51


APPLICATIONS TESTED WITHIN ENTERPRISEONE

EnterpriseOne Fastpath Reference

The following applications were used for testing. These applications show how EnterpriseOne reacts with the

Oracle 10g R2-RAC software in different circumstances, and we observed that each application reacts in its own

way.

Not every application could be tested in this project. If you implement Oracle 10g R2-RAC, perform similar tests

using the applications specific to your companys. The specific test results should be documented before you

activate the Production environment.

Test 1 Address Book Entry fastpath 3/G01

Test 2 Address Book Report UBE Batch fastpath 3/G0121

Test 3 Sales Order Entry fastpath 3/G4211

Test 4 Standard Voucher Entry fastpath 3/G0411

Test 5 Supplier Ledger Inquiry fastpath 16/G0411

Test 6 Standard Receipts Entry fastpath 5/G03B12

Test 7 Journal Entry fastpath 2/G0911

Test 8 Trial Balance Ledger Comparison fastpath 22/G0912

Test 9 Inventory Adjustments fastpath 65/G4111

Test 10 Summary Availability fastpath 15/G41112

Test 11 Purchase Order Entry fastpath 3/G43A11

Test 12 Print Pick Slips UBE Batch fastpath 4/G4211


12/51


LOAD BALANCING RAC OPTION

Load Balancing Options

There are two types of load balancing: client based and server based. Client based load balancing is enabled by

setting load_balancing=on in the tnsnames.ora file. Client load balancing enables clients to randomize requests to

multiple listeners. This load balancing is connection based, and the connections are assigned to instances at

random.

If you don't set up load_balancing in the tnsnames.ora file, the default load_balancing is based on CPU utilization

and is called server based load_balancing.

Load Balancing Simulation

LoadRunner software was used to generate many JD Edwards EnterpriseOne user connections. The test suite of

scripts that are usually run for the benchmark test process were used to simulate the work performed by these

users.

Load Balancing Observations

For our test observations we used the Client load balancing method. This method made the process easier toobserve, and determine if the appropriate files were configured correctly.

The Oracle 10g R2-RAC Load Balancing feature worked very well. When the necessary EnterpriseOne kernel

database connections needed to be established, each of the database nodes were used. As additional users were

added to the test, additional connections were established across each of the database nodes. At no time during the

test was there an observed imbalance on either database node.


13/51


FAIL-OVER RAC OPTION

Fail-Over Explanation

Clients that connect to any instance of the database use the net service name entry for the database. This entry also

enables Oracle Enterprise Manager to discover a Real Application Clusters database.

A listener address is configured for each node that runs an instance of the database. The load_balance option

causes Oracle to choose the address randomly. If the chosen address fails, then the failover option causes the

connection request to fail over to the next address. Thus, if an instance fails, clients can still connect using another

instance.

Failover=on is set by default for a list of addresses. Thus, it isn't necessary to explicitly specify the failover=on

parameter.

Fail-Over Simulation

During our tests, we simulated database node failures by shutting down the database using the database command

shutdown abort. This test allowed a controlled shutdown of the database and was least destructive to hardware and

software. Also, by doing the failure simulation this way, we could simulate what happened when this database was

restarted.

Fail-Over Observations

The Oracle 10g R2-RAC Fail-Over option yielded different results depending on the application tested. When a

specific test was conducted, the results were documented and compiled into the behavior summaries in this

document. Although full use of the fail-over features provided within RAC can not be tested, there were some

applications within EnterpriseOne that work well.

To fully utilize the Oracle 10g R2-RAC Transparent Application Fail-over (TAF) features, EnterpriseOne must be

enhanced to include coding to specifically interact with the TAF features of Oracle-RAC.

EnterpriseOne Enterprise Server Fail-Over Behavior

The EnterpriseOne Enterprise Server was able to utilize the fail-over feature and was able to re-establish the

necessary database connections for the kernels immediately or upon request when needed. No observable delay

was visible to the user. At no time during any of the fail-over testing did the EnterpriseOne Enterprise Server need

to be stopped and restarted due to a database failure.

Web Client Fail-Over Behavior

Following is a high level explanation of the observed fail-over behavior when the Web client was tested. No

predictable behavior is observed from the client. The following results describe the user experience observed

during the testing.

The summary explanations below are each unique. There may not be substantial differences between them but the

user experience was different so a slightly different explanation is provided. The results indicate a success or

failure of an application to work with Oracle 10g R2-RAC database software features when a database node fails.

Note that all the tested EnterpriseOne applications function properly when running in an Oracle database RAC

environment. EnterpriseOne behaves exactly as if running on a single Oracle database instance. EnterpriseOne


14/51


only malfunctions when one of the RAC nodes fail. Any user or process accessing the failed node is affected by

the failure. This failure may or may not be a user friendly experience.

Each of the tests below is associated with the corresponding user experience.

Fail-Over Behavior Summaries

RESULT 1

Test 1. Address Book Entry - fastpath 3/G01

When the database was forced to fail, the user did not get any indication that the RAC node failed. The only visual

indication observed after the failure was that no address book number was shown on the screen when the OK

button was pressed. If the user did not notice this behavior, many entries might be made then later realize that

none of the entries is actually saved.

If users exit from the application but stay logged onto the same EnterpriseOne session, they can reopen the

application but it will not be able to function correctly. However, the application is restored when users exit the

application, log off EnterpriseOne, close the Explorer window, and then start a new EnterpriseOne session.

All entries made before the failure were saved in the database and had address book numbers assigned to them.

In summary, this application did not have a user friendly experience during a RAC node failure.

RESULT 2

Test 2. Address Book Report UBE fastpath 3/G0121

This UBE is a query type batch process that generates a report. During processing, when the database was forced

to fail, the runbatch process automatically re-established its connection with the remaining running RAC database

nodes and the UBE continued to process. The processing time was about twice as long, but the expected report

was produced in its entirety.

This operation did have a user friendly experience during a RAC node failure.

RESULT 3

Test 3. Sales Order Entry fastpath 3/G4211

Test 4. Standard Voucher Entry fastpath 3/G0411

Test 5. Supplier Ledger Inquiry fastpath 16/G0411

Test 8. Trial Balance Ledger Comparison fastpath 22/G0912

Test 10. Summary Availability fastpath 15/G41112

During this entry type process, when the database was forced to fail, the user did not get any indication that theRAC node failed. The input process continued after the failure without any interruption or abnormalities.

After exiting from the entry application, a query was performed, and EnterpriseOne reported every entry and line

as successfully completed. This included all entries made before the failure as well as all entries completed after

the failure.


15/51


Overall these applications gave a user friendly experience during a RAC node failure.

RESULT 4

Test 6. Standard Receipts Entry fastpath 5/G03B12

During this entry type process, when the database was forced to fail, EnterpriseOne displayed an error indicating

that the Next Number was not obtained. This occurred because a database connection could not be made to

assign the next number.

The EnterpriseOne session must be exited and a new session established for work to continue without errors. The

work performed before the failure was saved, but the current entry made during the failure was not saved.

This application failed to function correctly during the RAC node failure, but the user was notified of the problem,

although wasnt given details. This result was more user friendly and did not waste a lot of the users time.

RESULT 5

Test 7. Journal Entry fastpath 2/G0911

Test 9. Inventory Adjustments fastpath 65/G4111

During this entry process, when the database was forced to fail, the user did not get any indication that anything

was wrong. The input process continued after the failure and appeared to be working correctly. When the

operation was finalized, such as by pressing the OK button, an error window appeared and notified the user that

there was a problem with the entry.

When a search for the entered data was conducted, no data was found from before or after the database failure.

To continue without errors, the EnterpriseOne session must be exited and a new session established in order.

This was an undesirable user experience. The user was not aware of the failure until finalizing the entry, which

might occur after entering many lines. At this point, the user discovered that the inputted data was not accepted.

In addition to the loss of entered data, the users time was lost.

RESULT 6

Test 11. Purchase Order Entry fastpath 3/G43A11

During this entry process, the user did not receive any indication of error when the database was forced to fail.

The input process continued and it appeared that everything was working correctly.

When the operation finalized (such as by pressing the OK button), the process appeared to complete successfully.

No error window appeared and no interruption to the current session was encountered. There was no indication

that the RAC node failed.

When a search for the entered data was conducted, no data was found from before or after the failure.

To correct the problem, the EnterpriseOne session had to be exited and a new session started.


16/51


This user experience was the worst possible. The user was not alerted to the failure, and had no way to know that

data was not being entered into the database. The user could potentially lose a lot of time entering data before

discovering the problem. In addition to the loss of entered data, the users time was lost.

RESULT 7

Test 12. Print Pick Slips Batch UBE fastpath 4/G4211

During the processing of this type of batch query (which generates Pick Slips), the runbatch process automatically

re-established its connection with the remaining running RAC database node and the UBE continued to process.

The UBE appeared to continue running, and the job status did not change or indicate a problem. After 30

minutes, the job was terminated. No data was produced from the job that was running.

When investigated, we discovered that no database connection was made and the process could not connect to the

table and assign the next number.

Within the same session, the job was submitted again, which ran without end until the process was terminated.

To correct the problem, the EnterpriseOne session had to be exited and a new session established, then the job

had to be resubmitted.

This operation did have a user friendly experience during a RAC node failure.

PRELIMINARY RECOMMENDATIONS

Preliminary Recommendations

The following preliminary recommendations are based on the test results described in this document. Further

testing will be conducted and the results will be published.

Overall the EnterpriseOne Applications tested worked well with the Oracle 10g R2-RAC database software. It has

been proven that EnterpriseOne software will function equally well when used with the Oracle database RAC

option installed on multiple nodes, or on a single machine with a single instance of the Oracle database software.

An advantage of using the Oracle 10g R2-RAC database option is realized when evaluating the load balancing

feature. This option of the RAC software enables the database connections to automatically balance across each of

the database nodes. The load balancing method implemented may be a client-based or server-based load balancing

method. Either method works well; each individual site should evaluate the utilization of the RAC nodes and

implement the method that works best for them.

Specific performance results were not gathered in the scope of this project.

As described in the Fail-Over Behavior Summaries section of this paper, the user experience varied depending on

the application being tested. The RAC fail-over feature performed better than expected with some applications

but also provided a less than acceptable user experience with others. The RAC fail-over features are not expected

to work as well as the RAC load balancing feature due to the fact that EnterpriseOne software has not been

specifically written to take advantage of the RAC fail-over features. The load balancing feature does not require

any specially written code to function correctly.

The EnterpriseOne Services that run on the Enterprise Server are necessary to allow all aspects of EnterpriseOne

to function. These services establish database connections that allow users to utilize the EnterpriseOne software.


17/51


The user tasks can include log on security verification, interactive application navigation, and submitting batch

UBE jobs.

While performing the fail-over part of this project, the EnterpriseOne Services were able to maintain the necessary

database connections to allow EnterpriseOne to continue functioning. If the Services were connected to the failed

RAC node, their current connection was lost. When the Services were called upon by EnterpriseOne they would

re-establish a new connection to the surviving RAC node. As the RAC nodes were repeatedly forced to fail the

EnterpriseOne Services continued to re-establish database connections without any user interaction to manuallyrestart the services. This highlights how well EnterpriseOne Services work with the Oracle RAC fail-over feature.

EnterpriseOne interactive clients and batch processing UBEs produced various results that were not consistent

across the EnterpriseOne applications tested when the RAC node fail-over occurred. If Oracle 10g R2-RAC is

implemented, users must be aware of the normal EnterpriseOne application interactive behavior and be very

observant to visual differences that might indicate a node failure has occurred.

When the Oracle database RAC option is implemented a data verification process needs to be previously defined,

tested, and accepted as a reliable method to be able to check the integrity of the data that was being accessed when

the RAC node fail-over occurred. The methods implemented to perform this data integrity check may be an

automated job, a manual interactive user process or a combination of both that every company implementing RAC

must decide on how to best perform this check.

Administrators that implement the RAC option must have a method of monitoring the nodes so they can be

notified when a failure occurs. The Oracle Enterprise Manager does include a variety of methods to notify

administrators based on user defined values depending on what is important to each company. If the

administrator knows that a RAC node has caused a fail-over to occur and the reason why, the administrator can

then notify the users and tell them about the specific problem so the users will be able to check the data integrity.

In summary, Oracle 10g R2-RAC worked with EnterpriseOne 8.96 GA software. There are EnterpriseOne

improvements that have been noted, will be addressed, and possibly made available in future EnterpriseOne

releases to take full advantage of the Oracle Database RAC options offered.


18/51


ENTERPRISEONE SUPPORTED VERSIONS

EnterpriseOne Supported Versions

Oracle 10g R2 Real Application Clusters (RAC) version 10.2.0.1 is supported with EnterpriseOne 8.96 GA

RELATED REFERENCE MATERIALS

This paper is not intended to be the only source of information for implementing the Oracle RAC databasesoftware options. You should form a cross-functional team for this implementation. This team should be very

familiar with system administration, hardware and software clusters, database concepts, the Oracle Application

Server, and EnterpriseOne installation and operation.

EnterpriseOne installation and configuration documentation must be used in conjunction with the platform

specific guides for each of the corresponding software products installed.

General All Plaforms

ASMCMD - ASM Command Line Utility

Oracle Metalink Document ID: Note:332180.1

Red Hat Linux (x86)

Oracle Database Oracle Clusterware and Oracle Real Application Clusters Installation Guide 10g

Release 2 (10.2) for Linux

Part Number B14203-05

Oracle Database Installation Guide 10g Release 2 (10.2) for Linux x86


Step By Step 10gR2 RAC with ASM install on Linux(x86) Demo

Oracle Metalink Document ID: Note: 337937.1

Microsoft Windows (x86)


Release 2 (10.2) for Microsoft Windows


Oracle Database Installation Guide 10g Release 2 (10.2) for Microsoft Windows (32-Bit)


Step-By-Step Install of RAC with OCFS on Windows 2003

Oracle Metalink Document ID: Note:178882.1

How to setup ASM on Windows Oracle Metalink Document ID: Note:331796.1


19/51


Solaris (UltraSPARC)


Release 2 (10.2) for Solaris Operating System


Oracle Database Installation Guide 10g Release 2 (10.2) for Solaris Operating System (SPARC 64-Bit)


AIX (IBM pSeries)


Release 2 (10.2) for AIX


Oracle Database Installation Guide 10g Release 2 (10.2) for AIX 5L Based Systems (64-Bit)


HP-UX (PA-RISC)


Release 2 (10.2) for HP-UXPart Number B14202-04

Oracle Database Installation Guide 10g Release 2 (10.2) for hp-ux PA-RISC (64-Bit)


REFERENCE INTERNET SITES

Reference Internet Sites

http://www.oracle.com/technology/index.html

http://www.oracle.com/support/premier/global-support-resolution/metalink.html

http://www.oracle.com/technology/documentation/database10gr2.html

http://www.oracle.com/technology/products/database/asm/index.html

http://www.oracle.com/technology/community/oracle_ace/ace2.html

http://www.puschitz.com/

http://www.oracle.com/technology/pub/articles/tech_dba.html

http://oss.oracle.com/projects/ocfs/files/RedHat/RHEL3/

http://oss.oracle.com/projects/oracleasm/

http://oss.oracle.com/projects/oracleasm/documentation/

http://oss.oracle.com/projects/oracleasm/files/sources/


20/51


TECHNICAL SPECIFICATIONS AND DOCUMENTATION

Specific Environment Configuration System Diagrams

The following information indicates the hardware and software used during this test. This information does not

indicate the only supported configurations. Any configuration specified in the EnterpriseOne Tools 8.9x Minimum

Technical Requirements is supported. Note the specific versions of Operating Systems as well as the other

software that is compatible and certified for the RAC Environments.

Oracle Application Server 10.1.2.0.0

This system was tested with OAS 10.1.2.0.0 using a Linux based OAS server.

Equipment and Software

Red Hat Linux (x86)

EnterpriseOne 8.96 GA

Oracle 10.2.0.1 RAC

Oracle Application Server 10.2.0.0 Red Hat Linux 3.0 Update 6

denpro6 database server rac1 instance Linux

denpro7 database server rac2 instance Linux

denpro8 enterprise server Linux

denpro9 OAS server Linux

denpro1 windows client Windows 2003

denpro6 and denpro7 specific configuration:

Intel Xeon 2-cpu x 3.066Ghz ProLiant DL380 G3

5gb memory

2 1Gb lan interfaces

6 X 36gb Internal Drives

1 Fibre storage interface

both share three fibre storage arrays totaling 30 x 36gb using an MSA1000 Controller

both run Red Hat Linux 3.0 Update 6

denpro8 and denpro9 specific configuration:

Intel Xeon 2-cpu x 3.066Ghz ProLiant DL380 G3

5gb memory

1 1Gb lan interface


21/51


2 x 146gb Internal Drives

both are running Red Hat Linux 3.0 Update 6


22/51


ORACLE INFORMATION

Oracle Files and Settings

The files below are shown as examples only. The contents of each file depend upon your system configuration,

hardware, and operating system. The important settings in these files are those that are used to communicate with

and configure Oracle 10g R2-RAC.

Use these examples to reference the concepts of the installed RAC components. These concepts apply across

platforms and systems.

TNSNAMES.ORA

Database Node 1 denpro6 rac1

RAC =

(DESCRIPTION =

(ADDRESS = (PROTOCOL = TCP)(HOST = denpro6-vip)(PORT = 1521))


(LOAD_BALANCE = yes)

(CONNECT_DATA =

(SERVER = DEDICATED)

(SERVICE_NAME = rac)

)

)

LISTENERS_RAC =

(ADDRESS_LIST =



)

RAC2 =

(DESCRIPTION =


(CONNECT_DATA =



(INSTANCE_NAME = rac2)

)

)

RAC1 =

(DESCRIPTION =


(CONNECT_DATA =



23/51




)

)

EXTPROC_CONNECTION_DATA =

(DESCRIPTION =(ADDRESS_LIST =

(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))

)

(CONNECT_DATA =

(SID = PLSExtProc)

(PRESENTATION = RO)

)

)


RAC =

(DESCRIPTION =




(CONNECT_DATA =



)

)

LISTENERS_RAC =

(ADDRESS_LIST =



)

RAC2 =

(DESCRIPTION =

(ADDRESS = (PROTOCOL = TCP)(HOST = denpro7-vip)(PORT = 1521))(CONNECT_DATA =





24/51


)

)

RAC1 =

(DESCRIPTION =


(CONNECT_DATA =(SERVER = DEDICATED)



)

)

EXTPROC_CONNECTION_DATA =

(DESCRIPTION =

(ADDRESS_LIST =


)(CONNECT_DATA =

(SID = PLSExtProc)

(PRESENTATION = RO)

)

)

Windows Client denpro1

RAC =

(DESCRIPTION =

(ADDRESS = (PROTOCOL = TCP)(HOST = denpro6)(PORT = 1521))


(LOAD_BALANCE = YES)

(CONNECT_DATA =



)

)

Oracle Application Server (10.2.0.0) Server denpro9

rac =

(DESCRIPTION =




25/51



(CONNECT_DATA =



)

)

EnterpriseOne Enterprise Server denpro8

RAC =

(DESCRIPTION =




(CONNECT_DATA =



)

)

Deployment Server denpro5

RAC =

(DESCRIPTION =



(LOAD_BALANCE = YES)

(CONNECT_DATA =(SERVER = DEDICATED)


)

)

SQLNET.ORA

Database Nodes 1 and 2 denpro6 rac1 and denpro7 rac2

NAMES.DIRECTORY_PATH= (TNSNAMES, , EZCONNECT)

Oracle Application Server denpro9

NAMES.DIRECTORY_PATH= (LDAP, TNSNAMES, EZCONNECT, ONAMES, HOSTNAME)


26/51


Windows Client denpro1 and Deployment Server denpro5

SQLNET.AUTHENTICATION_SERVICES= (NTS)

NAMES.DIRECTORY_PATH= (TNSNAMES, EZCONNECT)

LISTENER.ORA


SID_LIST_LISTENER_DENPRO6 =

(SID_LIST =

(SID_DESC =

(SID_NAME = PLSExtProc)

(ORACLE_HOME = /u01/app/oracle/oracle/product/10.2.0/db_1)

(PROGRAM = extproc)

)

)

LISTENER_DENPRO6 =

(DESCRIPTION_LIST =

(DESCRIPTION =


(ADDRESS = (PROTOCOL = TCP)(HOST = denpro6-vip)(PORT = 1521)(IP = FIRST))

(ADDRESS = (PROTOCOL = TCP)(HOST = 10.139.195.41)(PORT = 1521)(IP = FIRST))

)

)


SID_LIST_LISTENER_DENPRO7 =

(SID_LIST =

(SID_DESC =

(SID_NAME = PLSExtProc)

(ORACLE_HOME = /u01/app/oracle/oracle/product/10.2.0/db_1)

(PROGRAM = extproc)

)

)

LISTENER_DENPRO7 =

(DESCRIPTION_LIST =

(DESCRIPTION =


27/51



(ADDRESS = (PROTOCOL = TCP)(HOST = denpro7-vip)(PORT = 1521)(IP = FIRST))

(ADDRESS = (PROTOCOL = TCP)(HOST = 10.139.195.42)(PORT = 1521)(IP = FIRST))

)

)

Listener Status

When the statement, lsnrctl status, is used, the following should appear:


LSNRCTL for Linux: Version 10.2.0.1.0 - Production on 15-JUN-2006 07:49:41

Copyright (c) 1991, 2005, Oracle. All rights reserved.

Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))

STATUS of the LISTENER

------------------------Alias LISTENER_DENPRO6

Version TNSLSNR for Linux: Version 10.2.0.1.0 - Production

Start Date 22-MAY-2006 07:39:32

Uptime 24 days 0 hr. 10 min. 8 sec

Trace Level off

Security ON: Local OS Authentication

SNMP ON

Listener Parameter File /u01/app/oracle/oracle/product/10.2.0/db_1/network/admin/listener.ora

Listener Log File /u01/app/oracle/oracle/product/10.2.0/db_1/network/log/listener_denpro6.log

Listening Endpoints Summary...

(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1)))(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=10.139.195.105)(PORT=1521)))

(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=10.139.195.41)(PORT=1521)))

Services Summary...

Service "+ASM" has 1 instance(s).

Instance "+ASM1", status BLOCKED, has 1 handler(s) for this service...

Service "+ASM_XPT" has 1 instance(s).


Service "PLSExtProc" has 1 instance(s).

Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...

Service "rac" has 2 instance(s).

Instance "rac1", status READY, has 2 handler(s) for this service...Instance "rac2", status READY, has 1 handler(s) for this service...

Service "racXDB" has 2 instance(s).

Instance "rac1", status READY, has 1 handler(s) for this service...



28/51


Service "rac_XPT" has 2 instance(s).



The command completed successfully


LSNRCTL for Linux: Version 10.2.0.1.0 - Production on 15-JUN-2006 07:51:47

Copyright (c) 1991, 2005, Oracle. All rights reserved.

Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))

STATUS of the LISTENER

------------------------

Alias LISTENER_DENPRO7

Version TNSLSNR for Linux: Version 10.2.0.1.0 - Production

Start Date 25-MAY-2006 13:57:22

Uptime 20 days 17 hr. 54 min. 25 sec

Trace Level off

Security ON: Local OS Authentication

SNMP ON

Listener Parameter File /u01/app/oracle/oracle/product/10.2.0/db_1/network/admin/listener.ora

Listener Log File /u01/app/oracle/oracle/product/10.2.0/db_1/network/log/listener_denpro7.log

Listening Endpoints Summary...

(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1)))



Services Summary...

Service "+ASM" has 1 instance(s).


Service "+ASM_XPT" has 1 instance(s).


Service "PLSExtProc" has 1 instance(s).

Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...

Service "rac" has 2 instance(s).



Service "racXDB" has 2 instance(s).



Service "rac_XPT" has 2 instance(s).



The command completed successfully


29/51


Initialization Parameter File

For this test, the Initialization Parameter File was used to easily make changes and track modifications to configure

and control the database. The SPFILE was created from the pfile and mutually shared between the two nodes.

The values in these files were used to perform our tests. Due to the scope of this test, there were no performance

configuration tests performed. The values used allowed our environment to function in conjunction with the

specific hardware used.

These settings will not be justified or defended as the perfect set of values for numbers in all environments. These

settings produced satisfactory results in our system, but may not be optimal for your system. These are the

settings used in this test to produce results that we were satisfied with at the conclusion of the test. Everyone must

configure their own systems to meet their own needs and equipment.

As with a single Oracle instance configuration, the values used in the initialization files are very dependant on the

hardware used, as well as the actual work performed with the EnterpriseOne system.

Database Node 1 & 2 Shared Pfile Entries

rac1.__db_cache_size=1023410176

rac2.__db_cache_size=889192448

rac1.__java_pool_size=16777216rac2.__java_pool_size=16777216

rac1.__large_pool_size=16777216

rac2.__large_pool_size=16777216

rac1.__shared_pool_size=318767104

rac2.__shared_pool_size=452984832

rac1.__streams_pool_size=117440512

rac2.__streams_pool_size=117440512

*._db_block_lru_latches=3

*._kgl_large_heap_warning_threshold=8388608

*.audit_file_dest='/u01/app/oracle/admin/rac/adump'

*.background_dump_dest='/u01/app/oracle/admin/rac/bdump'

*.cluster_database_instances=2

*.cluster_database=true

*.compatible='10.2.0.1.0'

*.control_files='+GRP1/rac/controlfile/current.260.583161227'

*.core_dump_dest='/u01/app/oracle/admin/rac/cdump'

*.cursor_space_for_time=TRUE

*.db_block_checking='FALSE'

*.db_block_checksum='FALSE'

*.db_block_size=8192

*.db_cache_size=0

*.db_create_file_dest='+GRP1'

*.db_domain=''

*.db_file_multiblock_read_count=128

*.db_name='rac'

*.db_writer_processes=3


30/51


*.disk_asynch_io=TRUE

*.dispatchers='(PROTOCOL=TCP) (SERVICE=racXDB)'

*.filesystemio_options='ASYNCH'

rac1.instance_number=1

rac2.instance_number=2

*.job_queue_processes=10

*.open_cursors=6000*.pga_aggregate_target=838860800

*.pre_page_sga=TRUE

*.processes=3000

*.remote_listener='LISTENERS_RAC'

*.remote_login_passwordfile='exclusive'

*.session_cached_cursors=1024

*.sga_max_size=1500000000

*.sga_target=1500000000

*.streams_pool_size=104857600

rac2.thread=2

rac1.thread=1*.undo_management='AUTO'

rac1.undo_tablespace='UNDO_RAC1_1'

rac2.undo_tablespace='UNDO_RAC2_1'

*.user_dump_dest='/u01/app/oracle/admin/rac/udump'

*.workarea_size_policy='AUTO'


31/51


Database Node 2 denpro7 Initialization Parameter Values

NAME TYPE VALUE

O7_DICTIONARY_ACCESSIBILITY boolean FALSE

_db_block_lru_latches integer 24

_kgl_large_heap_warning_threshold integer 8388608

active_instance_count integeraq_tm_processes integer 0

archive_lag_target integer 0

asm_diskgroups string

asm_diskstring string

asm_power_limit integer 1

audit_file_dest string /u01/app/oracle/admin/rac/adump

audit_sys_operations boolean FALSE

audit_syslog_level string

audit_trail string NONE

background_core_dump string partial

background_dump_dest string /u01/app/oracle/admin/rac/bdump

backup_tape_io_slaves boolean FALSE

bitmap_merge_area_size integer 1048576

blank_trimming boolean FALSE

buffer_pool_keep string

buffer_pool_recycle string

circuits integer

cluster_database boolean TRUE

cluster_database_instances integer 2

cluster_interconnects string

commit_point_strength integer 1

commit_write string

compatible string 10.2.0.1.0

control_file_record_keep_time integer 7

control_files string +GRP1/rac/controlfile/current.260.583161227

core_dump_dest string /u01/app/oracle/admin/rac/cdump

cpu_count integer 4

create_bitmap_area_size integer 8388608

create_stored_outlines string


32/51



NAME TYPE VALUE

cursor_sharing string EXACT

cursor_space_for_time boolean TRUE

db_16k_cache_size big integer 0

db_2k_cache_size big integer 0db_32k_cache_size big integer 0



db_block_buffers integer 0

db_block_checking string FALSE

db_block_checksum string FALSE

db_block_size integer 8192

db_cache_advice string ON

db_cache_size big integer 0

db_create_file_dest string +GRP1

db_create_online_log_dest_1 string





db_domain string

db_file_multiblock_read_count integer 128

db_file_name_convert string

db_files integer 200

db_flashback_retention_target integer 1440

db_keep_cache_size big integer 0

db_name string rac

db_recovery_file_dest string

db_recovery_file_dest_size big integer 0

db_recycle_cache_size big integer 0

db_unique_name string rac

db_writer_processes integer 3

dbwr_io_slaves integer 0

ddl_wait_for_locks boolean FALSE


33/51



NAME TYPE VALUE

dg_broker_config_file1 string /u01/app/oracle/oracle/product/10.2.0

/db_1/dbs/dr1rac.dat

dg_broker_config_file2 string /u01/app/oracle/oracle/product/10.2.0

/db_1/dbs/dr2rac.datdg_broker_start boolean FALSE

disk_asynch_io boolean TRUE

dispatchers string (PROTOCOL=TCP) (SERVICE=racXDB)

distributed_lock_timeout integer 60

dml_locks integer 14540

drs_start boolean FALSE

event string

fal_client string

fal_server string

fast_start_io_target integer 0

fast_start_mttr_target integer 0

fast_start_parallel_rollback string LOW

file_mapping boolean FALSE

fileio_network_adapters string

filesystemio_options string ASYNCH

fixed_date string

gc_files_to_locks string

gcs_server_processes integer 2

global_context_pool_size string

global_names boolean FALSE

hash_area_size integer 131072

hi_shared_memory_address integer 0

hs_autoregister boolean TRUE

ifile file

instance_groups string

instance_name string rac2

instance_number integer 2

instance_type string RDBMS

java_max_sessionspace_size integer 0


34/51



NAME TYPE VALUE

java_pool_size big integer 0

java_soft_sessionspace_limit integer 0

job_queue_processes integer 10

large_pool_size big integer 0ldap_directory_access string NONE

license_max_sessions integer 0

license_max_users integer 0

license_sessions_warning integer 0

local_listener string

lock_name_space string

lock_sga boolean FALSE

log_archive_config string

log_archive_dest string

log_archive_dest_1 string










log_archive_dest_state_1 string enable











35/51



NAME TYPE VALUE

log_archive_duplex_dest string

log_archive_format string %t_%s_%r.dbf

log_archive_local_first boolean TRUE

log_archive_max_processes nteger 2log_archive_min_succeed_dest integer 1

log_archive_start boolean FALSE

log_archive_trace integer 0

log_buffer integer 15316992

log_checkpoint_interval integer 0

log_checkpoint_timeout integer 1800

log_checkpoints_to_alert boolean FALSE

log_file_name_convert string

logmnr_max_persistent_sessions integer 1

max_commit_propagation_delay integer 0

max_dispatchers integer

max_dump_file_size string UNLIMITED

max_enabled_roles integer 150

max_shared_servers integer

nls_calendar string

nls_comp string

nls_currency string

nls_date_format string

nls_date_language string

nls_dual_currency string

nls_iso_currency string

nls_language string AMERICAN

nls_length_semantics string BYTE

nls_nchar_conv_excp string FALSE

nls_numeric_characters string

nls_sort string

nls_territory string AMERICA

nls_time_format string

nls_time_tz_format string


36/51



NAME TYPE VALUE

nls_timestamp_format string

nls_timestamp_tz_format string

object_cache_max_size_percent integer 10

object_cache_optimal_size integer 102400olap_page_pool_size big integer 0

open_cursors integer 6000

open_links integer 4

open_links_per_instance integer 4

optimizer_dynamic_sampling integer 2

optimizer_features_enable string 10.2.0.1

optimizer_index_caching integer 0

optimizer_index_cost_adj integer 100

optimizer_mode string ALL_ROWS

optimizer_secure_view_merging boolean TRUE

os_authent_prefix string ops$

os_roles boolean FALSE

parallel_adaptive_multi_user boolean TRUE

parallel_automatic_tuning boolean FALSE

parallel_execution_message_size integer 2148

parallel_instance_group string

parallel_max_servers integer 80

parallel_min_percent integer 0

parallel_min_servers integer 0

parallel_server boolean TRUE

parallel_server_instances integer 2

parallel_threads_per_cpu integer 2

pga_aggregate_target big integer 800M

plsql_ccflags string

plsql_code_type string INTERPRETED

plsql_compiler_flags string INTERPRETED, NON_DEBUG

plsql_debug boolean FALSE

plsql_native_library_dir string

plsql_native_library_subdir_count integer 0


37/51



NAME TYPE VALUE

plsql_optimize_level integer 2

plsql_v2_compatibility boolean FALSE

plsql_warnings string DISABLE:ALL

pre_page_sga boolean TRUEprocesses integer 3000

query_rewrite_enabled string TRUE

query_rewrite_integrity string enforced

rdbms_server_dn string

read_only_open_delayed boolean FALSE

recovery_parallelism integer 0

recyclebin string on

remote_archive_enable string true

remote_dependencies_mode string TIMESTAMP

remote_listener string LISTENERS_RAC

remote_login_passwordfile string EXCLUSIVE

remote_os_authent boolean FALSE

remote_os_roles boolean FALSE

replication_dependency_tracking boolean TRUE

resource_limit boolean FALSE

resource_manager_plan string

resumable_timeout integer 0

rollback_segments string

serial_reuse string disable

service_names string rac

session_cached_cursors integer 1024

session_max_open_files integer 10

sessions integer 3305

sga_max_size big integer 1440M

sga_target big integer 1440M

shadow_core_dump string partial

shared_memory_address integer 0

shared_pool_reserved_size big integer 22649241

shared_pool_size big integer 0


38/51



NAME TYPE VALUE

shared_server_sessions integer

shared_servers integer 1

skip_unusable_indexes boolean TRUE

smtp_out_server stringsort_area_retained_size integer 0

sort_area_size integer 65536

spfile string +GRP1/rac/spfilerac.ora

sql92_security boolean FALSE

sql_trace boolean FALSE

sql_version string NATIVE

sqltune_category string DEFAULT

standby_archive_dest string ?/dbs/arch

standby_file_management string MANUAL

star_transformation_enabled string FALSE

statistics_level string TYPICAL

streams_pool_size big integer 112M

tape_asynch_io boolean TRUE

thread integer 2

timed_os_statistics integer 0

timed_statistics boolean TRUE

trace_enabled boolean TRUE

tracefile_identifier string

transactions integer 3635

transactions_per_rollback_segment integer 5

undo_management string AUTO

undo_retention integer 900

undo_tablespace string UNDO_RAC2_1

use_indirect_data_buffers boolean FALSE

user_dump_dest string /u01/app/oracle/admin/rac/udump

utl_file_dir string

workarea_size_policy string AUTO


39/51


APPENDIX A SPECIFIC TESTING STEPS

Testing Steps

Test 1

Address Book Entry 3/G01

Form Title Action Test Value

Master Directory Enter Fast path 3/G01

Work With Addresses Press ADD Button

Enter Address Book Revision Information Enter Alpha Name Abtest1

Enter Search Type E

Press OK button

Supplier Master Revision Press OK button

Press OK button


Enter Search Type E

Press OK button


Press OK button


Enter Search Type E

Press OK button


Press OK button

Press Cancel button

Work With Addresses Enter Alpha Name Abtest*

Enter Search Type E

Press Find button


40/51


Test 2

Address Book Report UBE 3/G0121



Work with Batch Versions Available

Versions

Select Check Box XJDE0001

Press Select button

Version Prompting Select Check Box Data Selection

Select Form Menu

Select Advanced

Press Check Box Override Location

Press OK Button

Version Prompting Press Submit Button

JDE Data Sources Select Enterprise Server radio

buttonPress Select

Data Selection Select Left Operand Address Number (F0101) (AN8) [BC]

Select Comparison Is less than

Select Right Operand Literal Value

Select Literal Value Enter Literal Value 5000

Press OK Button

Data Selection Press OK Button

Printer Selection Press OK Button

Work With Batch Version AvailableVersion

Select Form Menu

Select Submitted Jobs

Submitted Job Search Find the job you justsubmitted. When theDescription field shows Done.Look at the PDF anddetermine the success.


41/51


Test 3

Sales Order Entry 3/G4211



Customer Service Inquiry Press ADD button

Sales Order Detail Revisions Enter Document Type SO

Enter Branch/Plant M30A

Enter Sold To 26403

Enter Ship 26411

Enter Order Date Todays Date + 1 week

Line 1 - Enter Quantity Ordered 1

Line 1 - Enter Item Number 702141

Line 1 - Enter Unit of Measurement EA























42/51


Test 3

Sales Order Entry 3/G4211







Press OK button

Test 4

Standard Voucher Entry 3/G0411


Master Directory Enter Fast path 3/G0411Supplier Ledger Inquiry Press ADD button

Enter Voucher Payment Information Enter Company 00050

Enter Supplier Number 4010

Enter GL Date 06/01/2000

Press On Gross Amount Field

Enter Gross Amount 500

Press OK button

Enter Voucher G/L Distribution Line 1 Enter Account M30.1510.A1

Line 1 Enter Amount 100

Line 2 Enter Account M30.1511.A1







Line 5 Enter Amount 100Press OK button


43/51


Test 5

Supplier Ledger Inquiry 16/G0411



Supplier Ledger Inquiry Focus on Supplier Number andhit CTRL-S

Address Book Long Number Search Enter Name Search BAABRP

Enter Search Type V

Press FIND button

Select 1st row in grid

Press SELECT button

Supplier Ledger Inquiry Press OPEN radio button

Press FIND button

Test 6

Standard Receipts Entry 5/G03B12


Master Directory Enter Fast path 5/G03B12

Press Add

Receipt Entry Enter Company 00200 or 00001

Enter Payor 39950

Enter Customer 39950

Enter Receipt Number 123ABC

Enter GL Date 6/1/2000

Enter Receipt Amount 1

Press Menu OptionFORM/SELECT

Press Find

Select Invoices Enter QBE Document Number 149332

Press FIND

Select 1st row in grid

Press Menu Option

ROW/SELECT

Press CLOSE

Receipt Entry Press OK button


44/51


Test 7

Journal Entry 2/G0911



Press Add

Journal Entry Enter Document Type JE

Enter Company 00050

Enter G/L Date 6/01/2000

Enter Explanation Explanation

Enter Ledger Type AA

Click on First Grid Line

Line 1 - Enter Account Number M30.5010.

Line 1 Enter positive Amount 1


Line 2 Enter negative Amount -1

















Press OK button


45/51


Test 8

Trial Balance Ledger Comparison 22/G0912



Trial Balance/Ledger Comparison Enter Skip to Account 1

Select/Skip To Account Uncheck

Enter Thru Date 1 02/28/99

Enter Thru Date 2 12/31/99

Press FIND button

Trial Balance/Ledger Comparison Enter LOD 5

Press FIND button


46/51


Test 9

Inventory Adjustments 65/G4111



Inventory Adjustments Enter Document Type IA

Enter G/L Date 06/01/2000

Enter Branch/Plant M30

Enter Explanation Explanation


Line 1 - Enter Quantity 1



















Press OK button


47/51


Test 10

Summary Availability 15/G41112



Work With Item Availability Enter Item Number 708412


Check Omit Zero Quantities check box

Press FIND button

Select first grid row

Press Menu Option Row/Detail Avail

Detail Availability Press CANCEL button


48/51


Test 11

Purchase Order Entry 3/G43A11


Master Directory Enter Fast path 3/G43A11

Press Add

Order Detail Enter Document Type OP

Enter Supplier 3480


Enter Order Date Todays Date


Line 1 Enter Quantity 1


Line 2- Enter Quantity 2

















Press OK button


49/51


Test 12

Print Pick Slips Batch 4/G4211



Work with Batch Versions Available Versions

Select Check Box XJDE0001

Press Select button

Version Prompting Select Check Box Data Selection

Select Form Menu

Select Advanced

Press Check Box Override Location

Press OK Button

Version Prompting Press Submit Button

JDE Data Sources Select Enterprise Server radio button

Press Select

Data Selection Select Left Operand Document (Order NO, Invoice, etc.)(F4211) (DOCO) [BC]

Select Comparison Is equal to

Select Right Operand Literal Value

Select Literal Value Select Range of Values Tab

Literal Value From: 10000

Literal value To: 11000

Press OK Button

Data Selection Press OK Button

Processing Options 1. Next Status From 520

2. Next Status Thru 999

Press OK Button

Printer Selection Press OK Button

Work With Batch Version Available Version

Select Form Menu

Select Submitted Jobs

Submitted Job Search Find the job you just submitted. When

the Description field shows Done. Lookat the PDF and determine the success.

APPENDIX B VALIDATION AND FEEDBACK

This section documents that real-world validation that this Red Paper has received.


50/51


Customer Validation

Oracle is working with Oracle customers to get feedback and validation on this document. Lessons learned from

these customer experiences will be posted here.

Field Validation

Oracle Consulting has provided feedback and validation on this document. Additional lessons learned from field

experience will be posted here.


51/51

Oracle Corporation

World Headquarters

500 Oracle Parkway

Redwood Shores, CA 94065

U.S.A.

Worldwide Inquiries:

Phone: +1.650.506.7000

Fax: +1.650.506.7200

oracle.com

Copyright 2006, Oracle. All rights reserved.

This document is provided for information purposes only and the

contents hereof are subject to change without notice.

This document is not warranted to be error-free, nor subject to any

other warranties or conditions, whether expressed orally or implied

in law, including implied warranties and conditions of merchantability

or fitness for a particular purpose. We specifically disclaim any

liability with respect to this document and no contractual obligations

are formed either directly or indirectly by this document. This document

may not be reproduced or transmitted in any form or by any means,

electronic or mechanical, for any purpose, without our prior written permission.

Oracle, JD Edwards, PeopleSoft, and Retek are registered trademarks of

Oracle Corporation and/or its affiliates. Other names may be trademarks

of their respective owners.

rp e1perf rac

Documents