© 2009 Oracle Corporation Proprietary and Confidential© 2009 Oracle Corporation –Proprietary and Confidential What happens to customizations when Upgrade/Alter by table Renames

© 2009 Oracle Corporation – Proprietary and Confidential


S317393 - PeopleSoft Integration of Oracle Database

TechnologiesJerry Zarate Oracle/PeopleTools Development

Darryl Presley Oracle Development: Database and Applications MAA / Exadata


The following is intended to outline our general

product direction. It is intended for information

purposes only, and may not be incorporated into 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 Oracle‟s

products remains at the sole discretion of Oracle.


<Insert Picture Here>

Agenda

• Review PeopleSoft enhancements

integrating Oracle features

• Review PeopleSoft functionality

in an MAA environment


PeopleSoft Oracle Feature

Integration Enhancements


Overview PeopleSoft –

Oracle Integration Enhancements

• Preserving Customized Storage Parameters

during Upgrades

• Partitioning support

• Advanced Compression support

• Active Data Guard (ADG)

• (Limited offload reporting support)

• Transparent Application Failure (TAF)

• (SELECT) support



Preserving Customized

Storage Parameters during

Upgrades


Overview

• What is customization of Storage

Parameters?

• What happens to these customizations

when Upgrade/Alter by table renames

are done ?

• How do we preserve storage parameter

customizations ?

• Examples


What is Customization in Storage

Parameters ?

• Storage parameters of Tables or Indexes created from PSIDE

are based on an RDBMS specific template we deliver in the

PSDDLMODEL table

CREATE TABLE [TBNAME] ([TBCOLLIST]) TABLESPACE [TBSPCNAME] STORAGE (INITIAL *INIT* NEXT *NEXT*

MAXEXTENTS *MAXEXT* PCTINCREASE *PCT) PCTFREE **PCTFREE* PCTUSED *PCTUSED*

CREATE [UNIQUE] *BITMAP* INDEX [IDXNAME] ON [TBNAME] ([IDXCOLLIST]) TABLESPACE *INDEXSPC* STORAGE

(INITIAL *INIT* NEXT *NEXT* MAXEXTENTS *MAXEXT* PCTINCREASE *PCT) PCTFREE **PCTFREE* PARALLEL

NOLOGGING;

• Any change in physical storage parameters of table/index done

outside of PSIDE is considered from an upgrade perspective a

customization (e.g. partitioning, compression, freelists, etc.)


What happens to customizations when

Upgrade/Alter by table Renames are done ?

• At the time of an upgrade, a customer‟s table/index

storage layout which they might have customized to

take the advantage of specific database features such

as partitioning, compression and other physical

storage parameters are lost when the table is dropped

and recreated (ALTER by TABLE RENAME) as a part

of the upgrade process.


How do we preserve storage parameter

customizations ?

• Beginning with PT8.51, Data Admin (PSIDE) has

improved functionality which preserves the

customization of any table/index storage parameters

• The DBMS_METADATA.GET_DDL PL/SQL package

is used to extract the storage parameter of table/index

being altered

• Data Admin (PSIDE) now uses the storage

parameters extracted by the PL/SQL package

DBMS_METADATA.GET_DDL instead of using the

storage parameters provided with the default template

(PSDDLMODEL)


Example:TEST_ALTER_STRG record was created with following fields.

(EMPLID, EMPLID_LAST_EMPL, EMPLOYEE, DATE_FROM, TIMEDOUT and DESCR).

CREATE TABLE PS_TEST_ALTER_STRG (EMPLID VARCHAR2(11) NOT NULL,

EMPLID_LAST_EMPL DECIMAL(10) NOT NULL,

EMPLOYEE VARCHAR2(1) NOT NULL,

DATE_FROM DATE,

TIMEDOUT SMALLINT NOT NULL,DESCR VARCHAR2(30) NOT NULL) TABLESPACE PTTBL STORAGE (INITIAL 40000 NEXT

100000 MAXEXTENTS UNLIMITED PCTINCREASE 0) PCTFREE 10 PCTUSED 80/

TABLE TEST_ALTER_STRG is subsequently customized using TABLE Partitioning by RANGE on the DATE_FROM column.

CREATE TABLE PS_TEST_ALTER_STRG (EMPLID VARCHAR2(11) NOT NULL,



DATE_FROM DATE,

TIMEDOUT SMALLINT NOT NULL,DESCR VARCHAR2(30) NOT NULL) TABLESPACE PTTBL

PARTITION BY RANGE ("DATE_FROM")

(PARTITION "EMPLOYED_Q1_2006" VALUES LESS THAN

(TO_DATE(' 2006-04-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))

PCTFREE 10 PCTUSED 80 INITRANS 1 MAXTRANS 255 STORAGE(INITIAL 40960 NEXT 106496 MINEXTENTS 1 MAXEXTENTS 2147483645PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT) TABLESPACE "PTAUDIT" NOCOMPRESS ,

PARTITION "EMPLOYED_Q2_2006" VALUES LESS THAN (TO_DATE(' 2006-07-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS',

'NLS_CALENDAR=GREGORIAN')) PCTFREE 10 PCTUSED 80 INITRANS 1 MAXTRANS 255

STORAGE(INITIAL 40960 NEXT 106496 MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POO L DEFAULT) TABLESPACE "PTAUDIT" NOCOMPRESS,

PARTITION "EMPLOYED_Q3_2006" VALUES LESS THAN

(TO_DATE(' 2006-10-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN')) PCTFREE 10 PCTUSED 80 INITRANS 1 MAXTRANS 255 STORAGE(INITIAL 40960 NEXT 106496 MINEXTENTS 1 MAXEXTENTS 2147483645

PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT) TABLESPACE "PTAUDIT" NOCOMPRESS ,

PARTITION "EMPLOYED_Q4_2006" VALUES LESS THAN

(TO_DATE(' 2007-01-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN')) PCTFREE 10 PCTUSED 80 INITRANS 1 MAXTRANS 255

STORAGE(INITIAL 40960 NEXT 106496 MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOLDEFAULT) TABLESPACE "PTAUDIT" NOCOMPRESS )

/Contd…..


Example: Contd...If this TABLE was subsequently altered during an upgrade via PSIDE to drop the column DESCR, the customized partitioning

would have been lost in a pre PT8.51 release.

Note: The pre PT8.51 ALTER uses the DEFAULT Data Model DDL when generating the DDL for the altered table.

CREATE TABLE PSYTEST_ALTER_STRG (EMPLID VARCHAR2(11) NOT NULL,



DATE_FROM DATE,TIMEDOUT SMALLINT NOT NULL) TABLESPACE PTTBL STORAGE (INITIAL 40000

NEXT 100000 MAXEXTENTS UNLIMITED PCTINCREASE 0) PCTFREE 10 PCTUSED 80

/

INSERT INTO PSYTEST_ALTER_STRG (EMPLID,

EMPLID_LAST_EMPL,

EMPLOYEE,

DATE_FROM,

TIMEDOUT)SELECT

EMPLID,

EMPLID_LAST_EMPL,

EMPLOYEE,

DATE_FROM,TIMEDOUT

FROM PS_TEST_ALTER_STRG

/

DROP TABLE PS_TEST_ALTER_STRG

/RENAME PSYTEST_ALTER_STRG TO PS_TEST_ALTER_STRG

/

Contd…..


Example: Contd...ALTER script generated by Tools 8.51 Note: Partitioning customization is retained.

CREATE TABLE PSYTEST_ALTER_STRG (EMPLID VARCHAR2(11) NOT NULL,

EMPLID_LAST_EMPL DECIMAL(10) NOT NULL,EMPLOYEE VARCHAR2(1) NOT NULL,

DATE_FROM DATE, TIMEDOUT SMALLINT NOT NULL) PCTFREE 10 PCTUSED 80 INITRANS 1

MAXTRANS 255 NOCOMPRESS LOGGING STORAGE(INITIAL 40960 NEXT 106496 MINEXTENTS 1 MAXEXTENTS 2147483645

PCTINCREASE 0 BUFFER_POOL DEFAULT) TABLESPACE "PTTBL"

PARTITION BY RANGE ("DATE_FROM") (PARTITION "EMPLOYED_Q1_2006" VALUES LESS THAN


PCTFREE 10 PCTUSED 80 INITRANS 1 MAXTRANS 255 STORAGE(INITIAL 40960 NEXT 106496 MINEXTENTS 1 MAXEXTENTS 2147483645


PARTITION "EMPLOYED_Q2_2006" VALUES LESS THAN (TO_DATE(' 2006-07-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS','NLS_CALENDAR=GREGORIAN')) PCTFREE 10 PCTUSED 80 INITRANS 1 MAXTRANS 255 STORAGE(INITIAL 40960 NEXT 106496 MINEXTENTS 1

MAXEXTENTS 2147483645 PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT) TABLESPACE "PTAUDIT" NOCOMPRESS, PARTITION "EMPLOYED_Q3_2006" VALUES LESS THAN


PCTFREE 10 PCTUSED 80 INITRANS 1 MAXTRANS 255 STORAGE(INITIAL 40960 NEXT 106496 MINEXTENTS 1 MAXEXTENTS 2147483645


PARTITION "EMPLOYED_Q4_2006" VALUES LESS THAN(TO_DATE(' 2007-01-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN')) PCTFREE 10 PCTUSED 80 INITRANS 1 MAXTRANS 255

STORAGE(INITIAL 40960 NEXT 106496 MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOLDEFAULT) TABLESPACE "PTAUDIT" NOCOMPRESS )

/

INSERT INTO PSYTEST_ALTER_STRG (

EMPLID,

EMPLID_LAST_EMPL,EMPLOYEE,

DATE_FROM,

TIMEDOUT)

SELECT

EMPLID,EMPLID_LAST_EMPL,

EMPLOYEE,

DATE_FROM,

TIMEDOUT

FROM PS_TEST_ALTER_STRG/

DROP TABLE PS_TEST_ALTER_STRG

/

RENAME PSYTEST_ALTER_STRG TO PS_TEST_ALTER_STRG

/

© 2009 Oracle Corporation – Proprietary and Confidential© 2009 Oracle Corporation – Proprietary and Confidential

PeopleSoft and

Oracle Active Data Guard



PeopleSoft and ADG

• Overview of ADG

• PeopleSoft integration of ADG


Data Guard and Active Data Guard

• Data Guard

• Oracle Data Guard is an Oracle feature providing a comprehensive set of services that create, maintain, manage, and monitor one or more standby databases to enable production Oracle databases to survive disasters and data corruptions ensuring high availability, data protection, and disaster recovery for enterprise data.

• Data Guard maintains these standby databases as transactionally consistent copies of the production database. Then, if the production database becomes unavailable because of a planned or an unplanned outage, Data Guard can switch any standby database to the production role, minimizing the downtime associated with the outage. Data Guard can be used with traditional backup, restoration, and cluster techniques to provide a high level of data protection and data availability.

• PeopleSoft supports Physical or Logical standby databases. PeopleSoft does not utilize any special Oracle data types that would preclude Data Guards use

•

• Active Data Guard

• Introduced in 11g, Active Data Guard is an extension of Data Guard whereby the standby DB can be actively accessed in READ/ONLY mode.


• Data availability and data protection for the Oracle Database

• Up to thirty standby databases in a single configuration

• Standby database used for queries, reports, test, or backups

Active Data Guard

Standby Database

Primary

Database

Oracle Data Guard OverviewBest Data Protection

Sync / Async

Redo Transport

Data Guard Broker


• Switchover

• Planned role reversal, never any data loss

• No database reinstantiation required

• Used for database upgrades, tech refresh, data center moves, etc.

• Manually invoked via Grid Control, Broker, or SQL*Plus

• No need to shutdown or restart PeopleSoft

• Failover

• Unplanned failure of primary

• Flashback Database used to reinstate original primary

• Manually invoked via Grid Control, Broker, or SQL*Plus

• May also be done automatically: Fast-Start Failover

Data Guard Role TransitionSwitchover & Failover


Primary DB and Standby DB using Data Guard

Pre-11g

Primary DB

Dictionary

Cache

Log buffer

LCK0 LGWR DBW0

SMON PMON

LibraryCache

Global Resource Directory

LMS0

Buffer Cache

LMON LMD0 DIAG

Standby DB

Dictionary

Cache

Log buffer

LCK0 LGWR DBW0

SMON PMON

LibraryCache


LMS0

Buffer Cache

LMON LMD0 DIAG

Fully Accessible Non- Accessible

PeopleSoft PeopleSoft


Primary DB and multiple Standby DB‘s using

Data Guard 11g onward

Primary DB

Public Lan

Dictionary

Cache

Log buffer

LCK0 LGWR DBW0

SMON PMON

LibraryCache


LMS0

Buffer Cache

LMON LMD0 DIAG

Standby DB2

Public Lan

Dictionary

Cache

Log buffer

LCK0 LGWR DBW0

SMON PMON

LibraryCache


LMS0

Buffer Cache

LMON LMD0 DIAG

Fully Accessible Accessible R/O

Standby DB1

Public Lan

Dictionary

Cache

Log buffer

LCK0 LGWR DBW0

SMON PMON

LibraryCache


LMS0

Buffer Cache

LMON LMD0 DIAG

Accessible R/O



PeopleSoft integration with

Oracle ADG


• Beginning with PeopleTools 8.51, we‟ve provided the

infrastructure to off load units of work (UOWs) either PIA

components or Process Scheduler jobs to run on a

STANDBY DB

• This infrastructure is comprised of the following:

• Ability to configure a standby DB in the App server and Process

Scheduler configuration files

• A mechanism to mark components as R/O so that these

components get redirected to the STANDBY DB

• A mechanism to mark Process Scheduler processes as R/O so that

these components get redirected to the STANDBY DB

• Changes to App server and Process Scheduler to redirect a UOW

to the STANDBY DB if the UOW is attributed as R/O

• Documentation and scripts needed to configure PeopleSoft for ADG

Peoplesoft and ADG 11g


Configuring a Standby DB• With PT8.51 we‟ve provided an ability to specify an optional STANDBY database in addition to the

current PRIMARY database designation in the Application Server configuration file

• PT8.51 Application Server config file

• [Startup]

• ;=========================================================================• ; Database Signon settings• ;=========================================================================

• DBName=QE851PRI• DBType=ORACLE

• UserId=QEDMO• UserPswd=QEDMO• ConnectId=people

• ConnectPswd=peop1e• ServerName=

• StandbyDBName=QE851SBY• StandbyDBType=ORACLE• StandbyUserId=QEDMOSA

• StandbyUserPswd=QEDMOSA

• Note: New Standby DB entries


Standby DBAccessible R/O

PeopleTools 8.51 and ADG 11g

Primary DBFully Accessible

DBLINKs/ Remote Synonyms for every table

requiring non SELECT DML

Tables requiring SELECT only DML

require Local Synonyms from the

Secondary Accessid to

Primary AcccessId’s tables and views

Primary connection

using SYSADM1 via QEDMO

Application

Server(s) Detail

PSQRYSRVPSAPPSRV

Secondary connection using

SYSADM2 via QEDMOSA

PSPUBSRV PSSAMSRV PSQCKSRV


Configuring a Standby DB• With PT8.51 we‟ve provided an ability to specify an optional STANDBY database in addition to the

current PRIMARY database designation in the Process Scheduler configuration file

• PT8.51 Process Scheduler Server config file

• [Startup]

• ;=========================================================================• ; Database Signon settings• ;=========================================================================

• DBName=QE851PRI• DBType=ORACLE

• UserId=QEDMO• UserPswd=QEDMO• ConnectId=people

• ConnectPswd=peop1e• ServerName=

• StandbyDBName=QE851SBY• StandbyDBType=ORACLE• StandbyUserId=QEDMOSA

• StandbyUserPswd=QEDMOSA

• Note: New Standby DB entries


Standby DBAccessible R/O


Primary DBFully Accessible

DBLINKs/ Remote Synonyms for every table

requiring non SELECT DML

Tables requiring SELECT only DML

require Local Synonyms from the

Secondary Accessid to

Primary AcccessId’s tables and views

Process Scheduler

PSUNX

COBOL SQRPSAE

Connected to Primary DB using

SYSADM1 via QEDMO

PSAESRV

Primary connection

using SYSADM1 via QEDMO

Secondary connection using

SYSADM2 via QEDMOSA


• We now have the ability to configure a STANDBY DB in

addition to the PRIMARY DB we‟ve always been able to

configure.

• How can I redirect units of work (UOW‟s) either PIA

components or Process Scheduler jobs to run on the

STANDBY DB?

• A PIA component can be „marked‟ as READ-ONLY at Application

Design time via Application Designer (PSIDE)

• PSIDE -> Component -> Component Properties -> Use

• A Process Scheduler UOW can be „marked‟ as READ-ONLY at

Application Design time via

• PIA -> Process Scheduler -> Process Definition

Using Peoplesoft and ADG 11g


Marking a Component as Read Only


• Online components pre-determined to be able to utilize a

Standby DB

• PSQUERY Viewer

• Tree Viewer

• XMLP Viewer

• SES Feeds Generation

• FEEDS Reader



Marking a Process Definition as Read Only


• Batch Infrastructure and Batch Reporting Tool components able to utilize a Standby DB• Process Scheduler (Batch Server)

• Process Scheduler spawned components:

• PSAE processed via PSAESRV

• The following Process scheduler components cannot currently be redirected to a STANDBY DB:

• PSAE spawned Batch Processes

• Cobol Reports

• Cobol Batch Processes (ex. Payroll)

• SQR Reports

• SQR Batch Processes



• How does PeopleSoft distinguish between the Primary and Standby DB‟s?

• The primary DB will be accessed by the PeopleSoft schema owner or in PeopleSoft parlance the ACCESSID. The Standby DB will be accessed via an Alternate Oracle user Id or a secondary ACCESSID.

• The setup for using PeopleSoft with ADG 11g requires additional installation/configuration tasks, namely:

• Creation of an alternate Oracle User to be used while connected to the standby DB.

• This includes setting up a Secondary ACCESSID.

• Creation of local synonyms under the Alternate Oracle User which in effect access Primary tables locally on the standby DB via the Synonym mechanism for R/O operations.

• Creation of a „fixed User DB Link‟ on the Standby directed to Primary DB

• Creation of remote synonyms under the alternate Oracle User which in effect redirects the Read/Write access of a table locally on the Standby DB back to the Primary via the DBLink/Synonym mechanism.

• Additional documentation and SQL scripts to facilitate the installation setup included with PT8.51.



• The ideal use of this enhancement is where a given UOW is primarily READ-ONLY or Mostly READ/ONLY.

• We say Mostly READ/ONLY because there is no PeopleSoft process that is strictly read only. At a minimum, there are UPDATES/INSERTS/DELETES associated with the PeopleTools infrastructure to present a component or to run a process.

• We‟ve analyzed the PeopleTools infrastructure and accounted for the TABLES and VIEWS that need UPDATES/INSERTS/DELETES..

• The objective of this enhancement is to offload selected UOWs to the STANDBY DB.

• Note. Selecting the Read Only property on additional components or processes should only be done after detailed analysis. You need to make sure that the requests generated from the component or process perform operations like selecting and displaying lists, rather than inserting, updating, or deleting rows. If there are some DML operations that the component must make, the affected tables need to be identified, and a remote synonym needs to be created between the standby and primary databases.



References

• ADG Configuration Reference in PeopleBooks:• http://download.oracle.com/docs/cd/E18083_01/pt851pbr0/eng/psbooks/tadm/book.htm?File=tadm/htm/tadm13.htm#H4064


PeopleSoft Integration

with Oracle FAN and TAF



PeopleSoft integration with

Oracle FAN/TAF


PeopleSoft Architecture Overview

HTTPS

Database Storage

Web Client

Application

Servers

Process

Scheduler

Web Server

Cluster

App Developer

LDAP Directory

Jolt

Integration Broker

Tuxedo

SQL

SQL

SQL

PortalDatabase Server

SQL

HCM


PeopleSoft Architecture with RAC

HTTPS

Database Storage

Web Client

Application

Servers

Domains

Process

Scheduler

Web Server

Cluster

App Developer

LDAP Directory

Jolt

Integration Broker

Tuxedo

SQL

SQL SQL SQL

RAC Cluster Interconnect

PortalRAC Node1 RAC Node3RAC Node2

SQL

HCM



Transparent Application

Failover (TAF/FAN)


TAF Concept vs Feature

• Transparent Application Failover the „concept‟ refers to the ability of an application to seamlessly recover from a database node failure in a RAC environment

• Transparent Application Failover the „Oracle feature‟ refers to the automatic failover and re-establishment of application-to-db-service connections in the event of a a database node failure in a RAC environment

• In this case when an open connection to a database is lost, client applications can automatically reconnect to the database, and, optionally, resume a SELECT statement that was in progress.

• This reconnect happens automatically from within the Oracle Call Interface (OCI) library, with no intervention from the application program.



HTTPS

Database Storage

Web Client

Application

Servers

Process

Scheduler

Web Server

Cluster

App Developer

LDAP Directory

Jolt

Integration Broker

Tuxedo

SQL

SQL SQL SQL



SQL

HCM



HTTPS

Database Storage

Web Client

Application

Servers

Process

Scheduler

Web Server

Cluster

App Developer

LDAP Directory

Jolt

Integration Broker

Tuxedo

SQL

SQL SQL SQL



SQL

HCM



HTTPS

Database Storage

Web Client

Application

Servers

Process

Scheduler

Web Server

Cluster

App Developer

LDAP Directory

Jolt

Integration Broker

Tuxedo

SQL

SQL SQL SQL



SQL

HCM


What currently happens for PeopleSoft

components without TAF feature enabled

• NO Reconnects to the backup Instance or Alternate node

• Appserver and Process Scheduler will „retry‟ the connection and will

reconnect once the DB is available.

• PeopleSoft session is not re-established

• SELECT statement in progress is not automatically resumed

• User login is not-preserved

• Automatic re-initiation of AE JOBS will happen based on AE restart

parameter


What currently happens for PeopleSoft

components without TAF enabled (cont)

• What about Process Scheduler spawned jobs?

• Cobol attempting to connect or reconnect or execute sql

• SQR attempting to connect or reconnect or execute sql

• PSAE attempting to connect or reconnect or execute sql

• All of the processes mentioned above will just report these

loss of connection errors and terminate. No retry is

attempted.


Enabling TAF/FAN with PeopleSoft

• PeopleTools provides limited support for Oracle Transparent Application Failover (TAF)

• PeopleTools has been enhanced to listen for Oracle fast application notification (FAN) events to derive the failover behavior. Upon receipt of a FAN event, PeopleSoft servers break their existing TCP connections and initiate TAF, which references the TNSNAMES.ORA connect alias address list and establishes a connection to the surviving instance.

• PeopleSoft servers enhanced to support Fast Application Notification (FAN) to expedite application failover as of Peopletools 8.50.09

• PeopleSoft servers can be configured to transparently reconnect to a surviving RAC instance in the event of an instance failure with in a RAC cluster

• PeopleSoft servers can be configured to transparently fail over to an Oracle Database Data Guard standby when the primary database is lost

• Note. In most cases, other than a slight pause in the operation, the failover is transparent to the application end user.


PeopleSoft

Maximum Availability Architecture (MAA)



PeopleSoft with Integrated

MAA


PeopleSoft



PeopleSoft

Maximum Availability Architecture (MAA)• Integrated, Tested, Validated and Documented

PeopleSoft MAA Solution

• RAC scalability and HA failover

• No need for RAC instance affinity

• Supports Physical and logical standby

• Minutes of downtime for Rolling database upgrades

• Supports Transient Logical standby

• Online database patching

• Deliver RPO < 5 minutes, 0 if required

• PeopleSoft Application Server enhanced to support Fast

Application Notification (FAN) to expedite application failover

as of Peopletools 8.50.09

• Fast transaction error repair with Flashback technology


PeopleSoft


• PeopleTools 8.51 adds support of Active Data Guard

• Offload queries to Active Data Guard database with no

compromise for HA and DR

• Active Data Guard configured as “Secondary” database

service in PeopleTools application server configuration

• Auto-Block Repair is transparent to PeopleSoft with Active

Data Guard

• Single Client Access Name (SCAN) support as long

as PeopleSoft application server utilizes 11.2 Oracle

client

• Full application stack startup at DR site

• Example in white paper


• Overview & Benefit• Database services can be configured to be automatically active in specific database roles on

databases configured with Oracle Clusterware or Oracle Restart

• Data Guard Broker interacts with Oracle Clusterware or Oracle Restart to ensure appropriate services are active after a role transition: no need to write triggers on system startup events

• Example• Service “payroll” active in primary database role on the primary database London

• Service “reporting” active in physical standby database role on the standby database Boston

srvctl add service -d London -s payroll -l PRIMARY -q TRUE -e SELECT –m BASIC -w

10 -z 150

srvctl add service -d Boston -s reporting -l PHYSICAL_STANDBY -q TRUE –e SELECT -m

BASIC -w 10 -z 150

Oracle Database 11.2 EnhancementsRole Specific Services

Note:

1.For failover / switchover, Service “payroll” should also be configured on Boston in primary role and “reporting”

be configured on London in physical standby role

2.The “reporting” service must be explicitly created with DBMS_SERVICE.CREATE_SERVICE on primary

database to ensure information propagated via redo to physical standby

3.PeopleSoft will receive FAN events during the failover process


PeopleSoft on Exadata


• PeopleSoft Specific Failover Conditions for

Application Server clients

PeopleSoft Client Operation Behavior

Web client user is updating data and

submits or saves the updates during or just after the database failure.

Oracle reconnects and reconstructs

the database session on a surviving node and PeopleSoft resubmits the update.

Web client user is paging through

queried data when the database failure occurs.


the database session on a surviving node. Pages are rendered from pre-fetched result-set.

Web client user is issuing a new query

or switching screens just after the

database failure.


the database session on a surviving node.


PeopleSoft on Exadata


• PeopleSoft Specific Failover Conditions for Batch

Process Server clients

PeopleSoft Batch Operation Behavior

Process Scheduler Oracle reconnects and reconstructs the

process scheduler session on a surviving node successfully

Application Engine (AE) job submitted

just BEFORE primary failure

Oracle reconnects and reconstructs the

session on a surviving node but AE jobs may fail and show as “No Success”

Application Engine (AE) submitted

during or just AFTER primary instance failure

AE job completes successfully

COBOL jobs just BEFORE primary

instance failure

Programs with only SELECTs failover

successfully otherwise, restart required.

Crystal and SQR reports Same as COBOL programs

PSQUERY, Tree Viewer, XMLP Viewer These components will all failover

successfully


Active Data Guard–Data Protection, DR–Query Offload

GoldenGate–Active-active–Heterogeneous

Oracle Secure Backup–Backup to tape / cloud

Active Replica

Edition-based Redefinition,

Online Redefinition, Data Guard, GoldenGate– Minimal downtime maintenance, upgrades, migrations

RAC–Scalability–Server HA

Flashback–Human error

correction

Production Site

ASM–Volume Management

RMAN & Fast Recovery Area–On-disk backups

Oracle Maximum Availability ArchitectureLow cost, Integrated, Fully Active, High ROI


PeopleSoft Maximum Availability Architecture (MAA)

• Integrated, Tested, Validated full stack PeopleSoft

and Database MAA solution

• Incorporates PeopleSoft HA capabilities

• FAN and client failover support in PeopleTools 8.50.09

• Active Data Guard support in PeopleTools 8.51

• PeopleSoft MAA white paper at:

http://www.oracle.com/technetwork/database/features/availability/maa-

peoplesoft-bestpractices-134154.pdf

• Reducing PeopleSoft Downtime with Local Standby:http://www.oracle.com/technetwork/database/features/availability/maa-

peoplesoft-local-standby-128609.pdf

http://www.oracle.com/technetwork/database/features/availability/maa-peoplesoft-bestpractices-134154.pdf







http://www.oracle.com/technetwork/database/features/availability/maa-peoplesoft-local-standby-128609.pdf











Questions?


Follow us on PeopleSoft_Info

click icons for more information

Information PortalHosted & Mobile

PeopleBooks

Doc Home Pages and Enterprise Integration

Point Maps

Transfer of Information (TOIs)

Cumulative Feature Overview & Upgrade

Resource Report Tools

Business Process Maps & Entity Relationship

Diagrams

Learn MorePeopleSoft Information Development Resources

http://www.oracle.com/us/products/applications/054275.html

http://www.oracle.com/pls/psft/homepage

http://twitter.com/PeopleSoft_Info

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

http://oukc.oracle.com/static05/opn/customer_toi/psft_login.html

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=SYSTEMDOC&id=1117033.1


https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=REFERENCE&id=1061003.1


https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=REFERENCE&id=845867.1

http://download.oracle.com/docs/cd/E18171_01/EIPAPP91/index.html


Documents

© 2009 Oracle Corporation Proprietary and Confidential© 2009 Oracle Corporation –Proprietary and Confidential What happens to customizations when Upgrade/Alter by table Renames