Tuesday Aug 13, 2013

Do Not Run Multiple Branch Processes in Parallel

Query to show log:
------------------

select (select schema_name
        from  demantra.wf_schemas
        where schema_id = a.schema_id),
        to_char(a.record_created, 'DD-MON-YYYY HH24:MI:SS'),
        to_char(a.record_updated, 'DD-MON-YYYY HH24:MI:SS'),
        a.*
from    demantra.wf_process_log a
where process_id >= 922599
order by a.record_created desc


Does the above output indicate that you are running multiple batch processes in parallel?

Please review your environment and make sure you run processes in the correct order and
that the processes are not competing for hardware resources.

If you are trying to run processes that compete for same data in same tables you can try extending
your undo space and settings to be much larger, assuming your hardware can support this path.

However, running overlapping engines is not recommended.

* Attain the process ID from the OS for the most recently ran batch process 

Thursday Aug 08, 2013

7.3.0.1 or 7.3.1.4 Demantra with EBS 11i, ASCP VCP 11i?

Many customers are unwilling to upgrade their EBS due to customizations, users and overall effort required, but upgrading their VCP apps is easier and is supported.  You can leave your 11i system as is and install a separate VCP 12.1 instance which collects data from 11i10.

This is a fully supported configuration and allows you to connect Demantra 7.3.1.4 to EBS 11i10.

You do not even need to use any VCP apps other than Demantra.  The data flows through the 12.1 VCP instance into Demantra 7.3.1.4. 
This is the certified configuration for 11i and Demantra 7.3.1.4, so we advise considering this mix of tools.

The additional benefit you achieve is the ability to bring your VCP applications forward without impacting your EBS applications.

For 7.3.1.4 you would work with the following configuration.
    EBS 11.5.10  (11i)
    VCP 12.1.3.8
    Demantra 7.3.1.4

Worksheet Issues During or After Upgrade?

 Proactive action During/After an Upgrade may help.  Please review the following:

  1. Clean the Java cache by deleting the Java cache windows folder 
  2. Set the Java console debug mode to '5'
  3. Reproduced the issue
  4. Review the Client Java console
  5. Review the collaborator.log
  6. Produce an action plan
About

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

Search

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