Tuesday Dec 15, 2015

Demantra Upgrading 7.3.1.4 to 12.2.5.1 Ideas, Roadmap, Procedures

Hello!  Thank you for your query via the Demantra BLOG!

We have no direct dialogue specifically regarding upgrading from 7.3.1.4 to 12.2.5.1, we do have the following My Oracle Support (MOS) notes that will
help you navigate the upgrade process.  These will help you create your upgrade procedures.  After reviewing the following, and any additional information that you find, please feel free to submit your plan for review.   We would be glad to review and comment as required.  Not knowing your specific scenario, here is a list that will help.  The proper approach is to review each item.  This will help you develop a solid upgrade plan:

  • Demantra Solutions Advisor Webcast Calendar And Archive (Doc ID 800030.1)
    • January 13, 2016, Setup/Run/Troubleshoot The NEW 12.2.5.1 Demantra Engine
    • September 9, 2015, Oracle Demantra Release 12.2.5.1, Part 1
    • October 14, 2015, Oracle Demantra Release 12.2.5.1, Part 2
    • November 11, 2015, The Demantra Engine - Setup, Run and Common Issues
  • Installing Demantra 12.2.5.1 (Doc ID 2069281.1)
  • 12.2.5.1 Engine Deployment Guide (Doc ID 2069139.1)
  • Demantra Demand Planning 12.2.5.1 Known Issues and Workarounds (Doc ID 2068316.1)
  • Demantra 12.2.5.1 Now Available. See Patch 21951481 [Document 2068456.1]
  • Demantra Demand Management Release 12.2.5.1. There is a mandatory Patch Required 21959406 [Document 2068458.1] 
  • Demantra Platform or Application Upgrading - Program Manager Recommendations, Demand Management DM SOP PTP TPO SPF CTO IMCDP [Document 1609763.1]
  • List Of Demantra Versions And Corresponding Java Versions [Document 1346197.1]
  • Oracle Demantra Demand Management Release Notes for Release 12.2.5 (Doc ID 2059390.1)

 

For a Better Understanding:

  • Oracle Demantra and RDBMS Edition Based Redefinition (EBR) EBS schema - Processing and Hot Patching [Document 1932210.1]
  • Customer RecommendedUpgrading from Demantra 7.3.1.x to 12.2.x? This can produce duplicate rows. There are two ways to solve. See patch 21089579 and the details in this note. (Doc ID 2025954.1)
  • Demantra Performance and Setup Analyzer Script and Monitoring Tool (7.3.1 and Above) (Doc ID 1618885.1)
  • Demantra, DM, Weblogic, Engine Related Files and Paths [Document 2072591.1] 
  • Demantra TABLE_REORG procedure. Did you know that TABLE_REORG has replace REBUILD_SCHEMA mad REBUILD_TABLES? [Document 2005086.1]
  • Demantra Development Suggested Performance Advice Plus Reference Docs [Document 1157173.1] 
  • Demantra Upgrade with Customizations using BAL [Document 1458572.1]
  • Oracle Demantra Customizations BAL White Paper [Document 1627590.1] 
  • Demantra Workbench Access Over The Web For External Vendors (Doc ID 2080717.1)
  • Demantra Worksheet Personalization Does Not Show Worksheet Full Name (Doc ID 1962297.1)
  • Unsupported Java Version When Running createDSInEngineRoot.sh (Doc ID 2007452.1)
  • Demantra Upgrade Fails - ORA-01400: cannot insert NULL into (""DEMANTRA"".""INIT_PARAMS_217"".""PER_NODE"") Error in PROCEDURE (Doc ID 2086982.1)

Wednesday Jun 06, 2012

Need a Quick Sure Method to Produce a Formatted Explain Plan? This will help!

Please use the following on the production machine to get formatted explain
plan and sql trace using the SLOW sql (e.g. 'T_COMB_LIST.COMB_ID = 216') or
any other value that takes longer:

-- Open new session is SQL*Plus */
-- Make sure you are using updated PLAN_TABLE
-- This can be done by dropping it and recreate it by running:
-- SQL> @?/rdbms/admin/utlxplan.sql)

set lines 1000
set pages 1000
spool xplan_1.txt
EXPLAIN PLAN FOR
<<<<Replace this line with exactly the same query you used above. Force hard
parse by modifying the case of a character>>>>
@?/rdbms/admin/utlxplp
spool off
EXIT

--Open a second session is SQL*Plus
ALTER SESSION SET max_dump_file_size = unlimited;
ALTER SESSION SET tracefile_identifier = '10046';
ALTER SESSION SET statistics_level = ALL;
ALTER SESSION SET events '10046 trace name context forever, level 12';
<<<<Replace this line with exactly the same query you used above. Force hard
parse by modifying the case of a character>>>>
select 'verify cursor closed' from dual;
ALTER SYSTEM SET EVENTS '10046 trace name context off';
EXIT

Make sure spooled file is formatted properly and that the 10046 trace has relevant explain plan in it.  Please Upload both files (10046 trace is generated in udump).

Need instructions to find udump?  

sqlplus "/ as sysdba"
show parameters dump_dest

This will show you bdump, cdump and udump locations.

About

This blog delivers the latest information regarding performance and install/upgrade. Comments welcome

Search

Archives
« May 2016
SunMonTueWedThuFriSat
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
18
19
20
21
22
23
24
25
26
27
28
29
30
31
    
       
Today