Oracle Demantra customer, are you considering an upgrade to you Oracle Demantra software? There are three ciritical MOS notes that you may want to review.
- 12.2.1, 12.2.2, 12.2.3 and 12.2.4 Install Upgrade ADVISOR: Demantra (Doc ID 1664177.2)
- DEMANTRA WARNING Have you OR are you Planning to Upgrade to Release 12.2.2? Upgrade from 12.2.2 to 12.2.3 or 12.2.4 Collections EP Load is Failing ORA-20002, ORA-00001, ORA-06512 (Doc ID 1917715.1)
- Upgrading to Demantra 12.2.4? Here are current known issues from Demantra Development, Proactive Services and Oracle Support (Doc ID 1928367.1)
Upgrading a Customized Environment? There is help available!
Hello Demantra Customers! Are you upgrading a customized install? There is are new updates to a white paper that speaks about
using BAL to upgrade a customized environment. Check out Demantra Upgrade with Customizations using BAL (Doc ID 1458572.1).
Announcement: Oracle Demantra 12.2.3 Available
We are excited to announce Oracle Demantra 12.2.3 is now available for new and existing customers. All customers who are not incorporating Demantra with other VCP products are welcome to upgrade without any restrictions. Customers who are using Demantra in conjunction with VCP products will need to upgrade VCP to 12.2.3.
Demantra 12.2.3 encompasses the same functional scope as Demantra 12.2.2 with additional security and functional bug fixes.
Demantra 12.2.3 will work with JD Edwards EnterpriseOne 9.1 using the AIA 11.4 for the Value Chain Planning Base Integration Pack.
Demantra 12.2.3 will only work with VCP 12.2.3.
Demantra 12.2.3 and VCP 12.2.3 will work with EBS 12.1.3 or EBS 12.2.3.
Please review the release readme and all 12.2.3 documentation carefully to determine content details for this patch. You can also find documentation in the Demantra Documentation Library on My Oracle Support (note 443969.1).
The release is currently available on My Oracle Support (formerly known as Metalink) as Patch 17921238.
Release will be available from e-delivery in a few weeks.
It is recommended for all customers who are on 12.2.1 or 12.2.2 to upgrade to 12.2.3 at earliest convenience. Please do not upgrade to 12.2.2 and then 12.2.3.
Demantra 12.2.3 encompasses the same functional scope as Demantra 12.2.2 with additional security and functional bug fixes.
Demantra 12.2.3 will work with JD Edwards EnterpriseOne 9.1 using the AIA 11.4 for the Value Chain Planning Base Integration Pack.
Demantra 12.2.3 will only work with VCP 12.2.3.
Demantra 12.2.3 and VCP 12.2.3 will work with EBS 12.1.3 or EBS 12.2.3.
Please review the release readme and all 12.2.3 documentation carefully to determine content details for this patch. You can also find documentation in the Demantra Documentation Library on My Oracle Support (note 443969.1).
The release is currently available on My Oracle Support (formerly known as Metalink) as Patch 17921238.
Release will be available from e-delivery in a few weeks.
It is recommended for all customers who are on 12.2.1 or 12.2.2 to upgrade to 12.2.3 at earliest convenience. Please do not upgrade to 12.2.2 and then 12.2.3.
Upgrading to 12.2.2? Do you want extra speed? Use a logon trigger for parallelism
When upgrading your Demantra application from an older version directly to 12.2.2, you can minimize the upgrade time. You can force parallelism using a Logon trigger on the server.
Creation of new Indexes on sales data can take long time.
As part of the upgrade there is a script building a new set of indexes, one per engine profile, on each profile quantity_form expression.
The creation of the index can take a long time on big data tables.
- Remember to disable or drop that trigger when the upgrade has completed.
The following trigger was created as SYS database user and tested successfully by creating DEMANTRA database user and logging in with it:
CREATE OR REPLACE TRIGGER force_parallel_ddl_trg
Thanks
Srini
Creation of new Indexes on sales data can take long time.
As part of the upgrade there is a script building a new set of indexes, one per engine profile, on each profile quantity_form expression.
The creation of the index can take a long time on big data tables.
- Remember to disable or drop that trigger when the upgrade has completed.
The following trigger was created as SYS database user and tested successfully by creating DEMANTRA database user and logging in with it:
CREATE OR REPLACE TRIGGER force_parallel_ddl_trg
AFTER LOGON ON database
BEGIN
IF (USER='DEMANTRA') THEN
EXECUTE IMMEDIATE 'ALTER SESSION FORCE PARALLEL DDL';
END IF;
END force_parallel_ddl_trg;
/
Make sure to:
BEGIN
IF (USER='DEMANTRA') THEN
EXECUTE IMMEDIATE 'ALTER SESSION FORCE PARALLEL DDL';
END IF;
END force_parallel_ddl_trg;
/
Make sure to:
- Modify DEMANTRA to be the database schema name.
- drop it after it is not needed anymore using the foillowing:
Thanks
Srini
No comments:
Post a Comment
No one has ever become poor by giving