• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar
Techgoeasy

Techgoeasy

Learn Oracle, PHP, HTML,CSS,Perl,UNIX shell scripts

  • Home
  • Oracle
    • Oracle database
    • Oracle Ebusiness Suite
    • Oracle weblogic
    • Oracle Performance Tuning
    • Oracle Hyperion
    • Oracle Cloud Tutorials
  • SQL
  • interview questions
  • Linux
  • PHP and HTML
  • Downloads
  • General
Home » Oracle » Handling of seed data in R12.2 online patching

Handling of seed data in R12.2 online patching

August 10, 2015 by techgoeasy 2 Comments

We are trying to explain here the Handling of seed data in R12.2 online patching

What is seed data?

1)Seed data is data stored in database tables that affects the behavior of the application and is patched by EBS development
2) Patches cannot be allowed to modify the seed data seen by the running application otherwise it will impact the running application
3) seed tables are stored in APPS_TS_SEED tablespace

Changes done in seed data in R12.2
1)An additional column ZD_EDITION_NAME is populated in the seed tables.
2)Seed Data is filtered using the ZD_EDITION_NAME by a Virtual Private Database (VPD) Policy

How is seed data changes are handled

Online patches are prevented from modifying runtime seed data by the use of editioned data storage. This involves creation of a (patch) copy of the seed data, which is stored in the same table. The patches that are applied interact only with this copy, while the run edition only interacts with a private copy (which is eventually deleted as part of the cleanup phase).

The running application uses the run edition copy of seed data, while patches may update the patch edition copy of seed data in isolation. The two copies are isolated, except that seed data changes made by the running application are synchronized to the patch edition copy.

Run edition Patch edition
Always operates on a private copy of the seed data Runs the seed data loader
It is  never modified by patch application Prepares the relevant table for patching
it does not see the data modified by patch edition Copies all table rows and Loads seed data changes into the (patch) copy

Updates to  edition are automatically propagated to the patch edition by the use of cross-edition triggers.

Filed Under: Oracle, Oracle Ebuisness Suite Tagged With: R12.2, seed data

Reader Interactions

Comments

  1. Dan says

    November 8, 2022 at 8:11 pm

    Hi,

    I’m currently running a query under a database user named STGUSER

    select * from apps.FND_FLEX_VALUES_VL where flex_value_set_id=108673

    and flex_value_id=30883

    and I’m getting the same record twice, one as set1 and the other one as set2, the same is happening if I use this view FND_FLEX_VALUE_CHILDREN_V, but if I run the same query under XXDP or APPS, I’m getting only 1, would you know how to force the STGUSER to read these views/tables similar to APPS or XXDP?

    Thanks

    Daniel

    Reply
    • techgoeasy says

      November 21, 2022 at 4:06 pm

      R12.2 uses VPD( Virtual Private data) to filter edition data . I believe you need to register schema in R12.2 and then you should see single user

      Reply

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Primary Sidebar



Subscribe to our mailing list

Enter your email address to subscribe to this blog and receive notifications of new posts by email

Recent Posts

  • How to use sed replace string in file
  • Password Version in oracle
  • How to login as user without changing the password in Oracle database(alter user identified by values)
  • How to check encrypted tablespace in the Database
  • How To Export -Import TDE Master Encryption Key

Copyright © 2023 : TechGoEasy

  • Hire me
  • Privacy Policy
  • Contact Us
  • New? Start Here
  • About Us