Scribd Logo
Upload

Welcome to Scribd!

  • 144 views

    Performance Script

    Uploaded by

    ptnaidu2
    The document provides a list of 30 steps to identify performance problems in databases (DB) and applications (APPS). For DB issues, the steps check for process resource usage, stale mounts, disk space, I/O wait status, blocking sessions, network packet loss, and database bottlenecks. For APPS, the steps check configuration files, process resource usage, stale mounts, network connectivity, database locks, log file usage, workflow queues and purges, memory size, and debug settings.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOC, PDF, TXT or read online from Scribd
    Flag for inappropriate content

    You might also like

    Performance Script

    Uploaded by

    ptnaidu2
    144 views2 pages
    The document provides a list of 30 steps to identify performance problems in databases (DB) and applications (APPS). For DB issues, the steps check for process resource usage, stale mounts, disk space, I/O wait status, blocking sessions, network packet loss, and database bottlenecks. For APPS, the steps check configuration files, process resource usage, stale mounts, network connectivity, database locks, log file usage, workflow queues and purges, memory size, and debug settings.

    Original Description:

    Copyright

    © Attribution Non-Commercial (BY-NC)

    Available Formats

    DOC, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    The document provides a list of 30 steps to identify performance problems in databases (DB) and applications (APPS). For DB issues, the steps check for process resource usage, stale mounts, disk space, I/O wait status, blocking sessions, network packet loss, and database bottlenecks. For APPS, the steps check configuration files, process resource usage, stale mounts, network connectivity, database locks, log file usage, workflow queues and purges, memory size, and debug settings.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOC, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as doc, pdf, or txt
    144 views2 pages

    Performance Script

    Uploaded by

    ptnaidu2
    The document provides a list of 30 steps to identify performance problems in databases (DB) and applications (APPS). For DB issues, the steps check for process resource usage, stale mounts, disk space, I/O wait status, blocking sessions, network packet loss, and database bottlenecks. For APPS, the steps check configuration files, process resource usage, stale mounts, network connectivity, database locks, log file usage, workflow queues and purges, memory size, and debug settings.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOC, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as doc, pdf, or txt
    of 2

    Performance Problem Identification Script:

    DB:

    1. Check huge page settings

    2. Check top resource consuming processes

    3. Check runaway processes, defunct processes, defunct processes blocking any specific ports.

    4. Check archiver hung issues, max sessions reached issues

    5. Check for stale mount points (df –k), disk space full

    6. Using sar command to check the iowait status of the server.

    7. Check DB blocking sessions, long running LOCAL=NO processes, DB listener status, deadlocks,
    tablespace space full etc.

    8. Check CRS status in case of RAC DB nodes.

    9. DB Account locks.

    10. Perform a tracert for the server and check where there is packet loss.

    11. Check v$session_longops for long running jobs

    12. Run AWR report for identifying database bottlenecs.

    APPS:

    13. Check if any important configuration files modified recently?


    httpd.conf, jesrv.properties, appsweb.cfg, init.ora etc.

    14. jar file check "find $OA_JAVA/oracle/apps -name "*.jar" -mtime -3 –ls"

    15. Check top resource consuming processes

    16. Check runaway processes, defunct processes, defunct processes blocking any specific ports.

    17. Check for stale mount points (df –k), disk space full

    18. Ping the failing node.

    19. Perform a tracert for the server and check where there is packet loss.

    20. Check whether Big IP mapping and DNS entries are present.

    21. Inactive JDBC connections

    22. DB Account locks.


    23. Check $APPLCSF/log & out directories full and number of files.

    24. Workflow Mailer Queue build up issue: Check and reduced the sleep time

    25. Verify the status of purge concurrent requests, Workflow tables and purge

    26. Verify WF mailer sleep time

    27. Verify JVM memory size

    28. Check Private URLs accessibility

    29. =============================================
    The following debug options need looked at to see if some or most can be turned off.
    APPL|Receivables|AR: Enable Debug Message Output|Y
    SITE|SITE|CLN: Debug Level|4
    SITE|SITE|EAM: Activity API Debug Option|2
    SITE|SITE|EAM: Debug PM Scheduling|2
    SITE|SITE|FND: Debug Log Level|5
    USER|AMEZA|FND: Debug Log Level|1
    SITE|SITE|FND: Debug Log Mode|2
    SITE|SITE|FND_DEBUG_RULE_THRESHOLD|100
    SITE|SITE|IEX: Debug Level|20
    SITE|SITE|JTM: Debug level|1
    SITE|SITE|MSC: Enable Java Debug|Y
    SITE|SITE|OE: Debug Level|3
    USER|GFIMP_ORODRIGUEZ|OM: Debug Level|10
    SITE|SITE|PJI: Debug Level|5
    USER|GFIMP_ORODRIGUEZ|PO: Set Debug Concurrent ON|Y
    USER|GFIMP_ORODRIGUEZ|PO: Set Debug Workflow ON|Y
    USER|GMANRIQUE|PO:Enable Sql Trace for Receiving Processor|Y
    USER|GFIMP_ORODRIGUEZ|POA: Debug Mode|Y
    SITE|SITE|POR: Set Debug Catalog Loader ON|2
    SITE|SITE|SLA: Trace Level|100
    SITE|SITE|SLA: Trace Timeout|600
    SITE|SITE|TP:Release Debug|01110

    You might also like