Skip navigation.

APPS Blogs

Unprotecting URIs without using OAM Anonymous authentication

Online Apps DBA - Fri, 2014-02-21 00:00
I am pretty sure you might have had the requirement to unprotect certain URI context in an application URL using OAM. This is in regards to OAM 10.1.4.3. The usual procedure to unprotect an URI context is to define the resource in OAM Policy Domain. Create a separate policy for that URI and specify Anonymous [...]

This is a content summary only. Visit my website http://onlineAppsDBA.com for full links, other content, and more!
Categories: APPS Blogs

Product Restrictions during R12.2 online patching

Vikram Das - Thu, 2014-02-20 23:34
This information is from page 75 of Oracle® E-Business Suite Maintenance Guide Release 12.2 Part No. E22954-13, published in July 2013 available here  http://docs.oracle.com/cd/V39571_01/current/acrobat/122ebsmt.zip

For patches that have manual steps, the patch readme file instructs you to use Oracle Patch Application Assistant (PAA) to create customized instructions for your system. PAA consolidates and displays only the relevant manual steps for all the patches you want to apply, including steps that you have completed. It also automatically merges the contents of individual patch readme files for a merged patch.

Create Checklist of Product Functionality Disabled in Online Patching Cycle:
During an online patching cycle, the following product restrictions will apply. Before you commence patching, you should therefore ensure there will be no requirement for any these actions or features until the cycle is complete.
  • Payroll
    • Users will not be able to define Fast Formulas or use the Fast Formula Assistant.
    • Users will not be able to perform dynamic trigger maintenance.
    • Users will not be able to create, update, or delete US Cities.
    • Data Pump meta-mapper generator will be disabled.
    • The Japanese Balance Dimensions concurrent program will be deferred to after the cutover phase is complete.
    • Pension Calculation Setup cannot be used.
    • US localization earnings and deduction setup cannot be used.
    • Tax Withholding Rules Setup cannot be used.
    • Wage Attachment Earnings Rules Setup cannot be used.
    • Garnishment Rules Setup cannot be used.
    • Quick Paint Reports cannot be used.
    • Quantum Program Update Installer execution is unavailable.
  • Order Management:
    • Creation of a new Defaulting Condition in the Attribute Defaulting Rules form is disabled, unless the same seeded condition already exists for a given attribute.
  • Warehouse Management:
    • WMS Rule creation is restricted.
  • Inventory:
    • Concurrent program "Generate Stock Locator Flexfield Definition for Mobile Transactions" will be disabled.
  • Public Sector Financials International:
    • Users will not be able to run the following concurrent programs:
      • Subledger Security: Apply Security
      • Subledger Security: Import/Export Data Fix
  • Subledger Accounting:
    • Users will not be able to Validate the Application Accounting definitions.
  • Accounts Receivable:
    • Users will not be able to create new Transaction Sources.
  • Incentive Compensation:
    • Transaction collection process for new mappings will not be available and any changed mapping will continue to use previous mapping rules.
    • Users will not be able to run the "Synchronize Classification Rulesets" program.
    • Users will not be able to use the "Formula Generation" feature.
    • Users will not be able to specify new formulas or changes to compensation rules.
  • Oracle Demand Planning:
    • Demand plans will not be available for users.
Categories: APPS Blogs

Oracle E-Business Logging and Auditing, CMM and SIEM

Most Oracle E-Business Suite implementations do not fully take advantage of the auditing and logging features. These features are sophisticated and are able to satisfy most organization’s compliance and security requirements. 

The default Oracle E-Business Suite installation only provides a basic set of logging functionality.  In Integrigy’s experience, the implementation of database and application logging seldom exceeds meeting the needs of basic debugging.  Most organizations do not know where to start or how to leverage the built-in auditing and logging features to satisfy their compliance and security requirements.

Even organizations already using centralized logging or Security Incident and Event Management (SIEM) solutions, while being more advanced in the Common Maturity Model (CMM), in Integrigy’s experience are commonly challenged by the E-Business Suite’s auditing and logging features and functionality.

This guide presents Integrigy’s framework for auditing and logging in the Oracle E-Business Suite.  This framework is a direct result of Integrigy’s consulting experience and will be equally useful to both those wanting to improve their capabilities as well as those just starting to implement logging and auditing.  Our goal is to provide a clear explanation of the native auditing and logging features available, present an approach and strategy for using these features and a straight-forward configuration steps to implement the approach.

Integrigy’s framework is also specifically designed to help clients meet compliance and security standards such as Sarbanes-Oxley (SOX), Payment Card Industry (PCI), FISMA, and HIPAA.  The foundation of the framework is PCI DSS requirement 10.2.

To make it easy for clients to implement, the framework has three maturity levels – which level a client starts at depends on the infrastructure and policies already in place.

The three levels are:

  • Level 1 – Enable baseline auditing and logging for application/database and implement security monitoring and auditing alerts
  • Level 2 – Send audit and log data to a centralized logging solution outside the Oracle Database and E-Business Suite
  • Level 3 – Extend logging to include functional logging and more complex alerting and monitoring

This blog series will be reviewing the Framework in detail. The full whitepaper is available for download – the link is referenced below.

If you have questions, please contact us at info@integrigy.com

 -Michael Miller, CISSP-ISSMP

References Tags: AuditingSecurity Strategy and StandardsComplianceOracle E-Business Suite
Categories: APPS Blogs, Security Blogs

WLST connecting to WebLogic Admin Server failed : Bootstrap to [IP:Port] failed. It is likely that the remote side declared peer gone on this JVM

Online Apps DBA - Tue, 2014-02-18 04:59
WebLogic Scripting Tool (WLST) is a command-line scripting environment that you can use to create, manage, and monitor WebLogic Server domains . I recently encountered issue while connecting to WebLogic Server from WLST command connect(‘user’,'password’,'adminserver’)) remotely. Issue: WLST connect from local machine (where WebLogic Server is running) is working fine where as connection from remote machine (WLST on remote...

This is a content summary only. Visit my website http://onlineAppsDBA.com for full links, other content, and more!
Categories: APPS Blogs

Oracle E-Business Suite PCI DSS Compliance, Requirement 3.4 and Decryption Risk

PCI requirement 3.4 requires PAN data to be unreadable anywhere it is stored unless it is protected. With Release 12 credit cardholder data can be decrypted at any time as easily as it is encrypted by simply running the request set “Decrypt Sensitive Data Request Set” or any of the individual programs.

Integrigy Corporation highly recommends removing the request set, as well as the concurrent programs within it, from all request groups and then disabling (end-date the request set and disable its concurrent programs.  If for any reason the programs need to be run at a later date, they can be enabled. This will help prevent accidental decryption along with nefarious attempts to access cardholder data.

It is also highly recommended by Integrigy Corporation to set up special monitoring for these Decrypt Sensitive Data concurrent programs in production (non-production instances cannot have live credit cardholder data per requirement 6.4.3). Oracle Alerts can be configured if other monitoring tools do not exist.  Whatever monitoring process is setup it needs to be monitored daily to ensure that these programs are not run.

When not in use remove from all request groups and disable:

Request set (end-date)

  • Decrypt Sensitive Data Request Set

Concurrent Programs (disable)

  • Decrypt Credit Card Data
  • Decrypt External Bank Account Data
  • Decrypt Transaction Extension Data
  • Decrypt Credit Card Transaction Data
  • Payments Scheduled Decryption
Further Information

For further information on PCI compliance, Corporate Cards and the E-Business Suite please refer to our whitepaper in the link below.

If you have questions, please contact us at info@integrigy.com

 -Michael Miller, CISSP-ISSMP

References Tags: EncryptionCompliancePCIOracle E-Business Suite
Categories: APPS Blogs, Security Blogs

Download JDK/JRE (older/current version) from Oracle

Online Apps DBA - Sun, 2014-02-16 18:18
  If you are looking for older (1.1, 1.2, 1.3, 1.4, 5, 6) or latest (7) version of JDK (Sun and now Oracle) then you can get it from Oracle Technology Network (OTN)     Previous in series Related Posts for JRockit #JRockit Mission Control (JRMC) : Software & Documentation Location#JRockit Mission Control Overview – [...]

This is a content summary only. Visit my website http://onlineAppsDBA.com for full links, other content, and more!
Categories: APPS Blogs

Weekday Online Oracle Weblogic Administrator Training

Online Apps DBA - Sat, 2014-02-15 02:42
This course trains system administrators and data center personnel on techniques for installing, configuring, deploying and securing distributed, clustered applications and systems deploy on Oracle WebLogic Server. This training focuses on techniques for building high availability, clustered configurations to ensure maximum application uptime. Method for hardening the implementation to provide reliable security are also emphasized. [...]

This is a content summary only. Visit my website http://onlineAppsDBA.com for full links, other content, and more!
Categories: APPS Blogs

Oracle Fusion Middleware 11g SOA Administrator Training

Online Apps DBA - Sat, 2014-02-15 02:37
This is a hands-on lab-intensive course conducted on weekends. Our instructor lead trainings are interactive with Practice and Q/A Sessions. We use industry leading Conferencing Software [with integrated VOIP] to provide trainings. We will provide the students with step-by-step Setup/Installation Guide including two node active Fusion Middleware Cluster (SOA). Batch Commencing on: 22 February 2014 [...]

This is a content summary only. Visit my website http://onlineAppsDBA.com for full links, other content, and more!
Categories: APPS Blogs

Online OBIEE Basic & Advance Administration Training

Online Apps DBA - Sat, 2014-02-15 02:35
This is a hands-on lab-intensive course conducted on weekends. Our instructor lead trainings are interactive with Practice and Q/A Sessions. We use industry leading Conferencing Software [with integrated VOIP] to provide trainings.  Commencement Date: 22 February 2014 Training Schedule: 22, 23 February, 01, 02 & 08 March 2014 Training Duration : 5 Days Timings: 12:00 [...]

This is a content summary only. Visit my website http://onlineAppsDBA.com for full links, other content, and more!
Categories: APPS Blogs

Online Informatica Administrator Training

Online Apps DBA - Sat, 2014-02-15 02:31
This four-day Informatica Training program will help you learn how to administer the Informatica PowerCenter 9 Platform. This Informatica Training Program provides the necessary skills to manage services on any authorized Informatica Platform.   After completing this program you should be able to: Install the Informatica 9 architecture platform, configure add and manage Informatica Data [...]

This is a content summary only. Visit my website http://onlineAppsDBA.com for full links, other content, and more!
Categories: APPS Blogs

Online Oracle RAC DBA Training

Online Apps DBA - Sat, 2014-02-15 02:26
This is an intensive 6-day, full time hands-on in Oracle Real Application Clusters (RAC) course. Unlike other Oracle RAC tuning classes, it will provide you step by step guidance to create RAC environment at your home PC using VMWARE a freeware software. The course focuses on RAC architecture, installation, patching, administration, backup and recovery and [...]

This is a content summary only. Visit my website http://onlineAppsDBA.com for full links, other content, and more!
Categories: APPS Blogs

Oracle E-Business Test and Development Databases and PCI Compliance

Creating clones and copies of production E-Business Suite databases is a regular occurrence. There are several PCI DSS requirements that apply to non-production instances of the Oracle E-Business Suite. 

No Production Cardholder Data

The most important PCI DSS requirement that applies to non-production instances is requirement 6.4.3 which forbids production cardholder data to be used for development, testing, training and/or any other reason or purpose other than supporting business transactions in production.  Production cardholder data cannot exist outside production. Non-production instances need to have production cardholder data either removed or scrambled.

Protect Production Encryption Keys

Requirement 3.5 governs the protection and management of encryption keys which when applied to non-production databases means that production encryption keys (specifically the Payment Wallet) cannot be copied to and/or exist in non-production instances. If, for whatever reason, the production wallet is copied to a non-production instance, the production encryption key MUST be rotated and the production wallet MUST be destroyed by a secure wipe (not just deleted from the file system). If the non-production instance is virtualized, depending on how memory is locked or shared to the guest, a secure wipe may be even more critical.

Building Non-Production Instances

The points below highlight the requirements to build non-production instances:

  • The production Payment Wallet will need to be rotated and securely wiped if copied from production.
  • The location of the Payment Wallet will need to be reset. Do not use SQL to update to table IBY_SYS_SECURITY_OPTIONS directly. The user interface must be used to update the file location.
  • Remove, purge and/or scramble production cardholder data. Depending on requirements there are several options for creating and sanitizing cardholder data. These options make use of the fact that cardholder data (the PAN and supplemental data) is separate and different from the related business transaction and that the cardholder data is centralized within the Secure Payment Repository.

For further information on PCI compliance, Corporate Cards and the E-Business Suite please refer to our whitepaper in the link below.

If you have questions, please contact us at info@integrigy.com

 -Michael Miller, CISSP-ISSMP

References

 

Tags: CompliancePCIOracle E-Business Suite
Categories: APPS Blogs, Security Blogs

Enabling Credit Card PCI Protection for the Oracle E-Business Suite

The real challenge for meeting PCI compliance is the secure management of all the components and parts of the Oracle E-Business Suite environment every day of year. While Release 12 of the Oracle E-Business Suite by default does not protect cardholder data, it can be enabled. The steps are rather straight forward and can easily be completed in a non-production instance for testing.  Future blog posts will review the daily, weekly, monthly and annual PCI requirements once these basic PCI setups have been completed.

Three Basic Steps

There are the three basic steps to enable PCI protection for a new Release 12 implementation are:

  1. Create Payment encryption wallet
  2. Set protection configuration options
  3. Encrypt existing cardholder data
  Step 1: Create the Payment Encryption Wallet

With Release 12, the most critical step in meeting PCI DSS is the creation and on-going protection and maintenance of the Payment encryption wallet. There are several decisions to be made before creating a Payment Wallet. Wallets can either be self-signed, where the certificate is the same as the subject, or use a third party certificate from a well-known Certificate Authority. Which type of wallet is created is dependent on your trust requirements and expected usage. Payment Wallets must also be backed up separately from the E-Business database.

Step 2: Set Protection Configuration Options

Setting the protection configuration options is done using the Funds Capture Setup Administrator or Payments Setup Administrator responsibility. The decisions regarding which options to use should be carefully reviewed with internal audit, security and counsel.

  • Wallet - Location of the wallet file, the name of the wallet and the wallet password. Another decision is the whether the system key will be system generated or user defined. Integrigy Corporation recommends using a system generated key unless specific requirements are identified.
  • Account Number - Yes or No to encrypt the credit card number - select ‘Yes’
  • Supplemental data - Yes or No whether card holder name and expiration date will also be encrypted. This is also referred to as partial encryption if set to ‘No’.
  • Type – Whether or not encryption will occur immediately prior to being written to the database or later at a scheduled time. The options are ‘Immediate’ or ‘Scheduled’.  If you select scheduled, data will be unencrypted until the request set ‘Encrypt Sensitive Data Request Set’ is run.  Oracle does not automatically schedule this and it will need to be manually scheduled.  Integrigy Corporation strongly recommends using ‘Immediate’ and not ‘Scheduled’.
  • Card Owner Verification – Requiring the ‘Security Code’ and/or ‘Require Statement Billing Address’ by setting to ‘Yes’ requires the entry of the credit card security code or card statement billing address. This information is passed to the payment system, which in turn, checks with the credit card issuer to confirm the credit card owner's security code and/or statement billing address.
  • Credit Card Masking - Allows for masking of all but the first or last x digits of a PAN, for which x is identified by the field ‘Number of Digits to Display.

Step 3: Encrypt Existing Cardholder data

Cardholder data created prior to setting the encryption configurations will not be automatically encrypted. To encrypt cardholder data that already exists run the request set ‘Encrypt Sensitive Data Request Set’.

Next Blog Posting

In the next blog posting we will review the PCI requirements for creating non-production instances from copies of production.

For further information on PCI compliance, Corporate Cards and the E-Business Suite please refer to our whitepaper in the link below.

If you have questions, please contact us at info@integrigy.com

 -Michael Miller, CISSP-ISSMP

References Tags: EncryptionCompliancePCIOracle E-Business Suite
Categories: APPS Blogs, Security Blogs

Upgrade Oracle IAM (OES) from 11gR2 (11.1.2.0/1) to 11gR2 PS2 (11.1.2.2) lessons learned

Online Apps DBA - Tue, 2014-02-11 16:17
I discussed about availability of IAM 11gR2 PS2 (11.1.2.2) here and installation changes in IAM 11gR2 PS2 (11.1.2.2) here. In this post I am going to cover steps to upgrade IAM (OES in specific) from 11gR2 (11.1.2.0/1) to 11gR2 PS2 (11.1.2.2) . Upgrade of other IAM component (OIM, OAM, OAAM & OPAM) to follow soon. For [...]

This is a content summary only. Visit my website http://onlineAppsDBA.com for full links, other content, and more!
Categories: APPS Blogs

Oracle E-Business Suite, PCI Compliance and the Secure Payments Repository

Continuing this blog series on PCI compliance and the Oracle E-Business Suite, this posting focuses on the Secure Payments Repository.  New with Release 12 of the E-Business Suite, credit card processing and data storage within Oracle Financials, for customer’s and vendor’s card data, is now done within the Secure Payment Data Repository within Oracle Payments.  It is through this new standard functionality built into the Secure Payment Data Repository that PCI DSS compliance can be met.

With Release 12, the Oracle E-Business Suite has eleven modules that use Oracle Payments for the processing and storage of cardholder data.  Only these eleven products can be configured to meet PCI DSS requirements through the PA DSS functionality provided by Oracle Payments.  From the release notes for the Oracle Payment Application Data Security Standard (PA DSS) Consolidated Patch Release 12.1.2 (Doc ID 981033.1), the following list of products now use the Secure Payment Repository –

Oracle Modules using the Secure Payment Repository

  • Oracle Advanced Collections
  • Oracle iExpenses
  • Oracle iReceivables
  • Oracle iStore
  • Oracle Order Capture
  • Oracle Order Management
  • Oracle Partner Management
  • Oracle Payables
  • Oracle Payments
  • Oracle Quoting
  • Oracle Service Contracts
Secure Payment Repository

With Release 12, the Trading Community Architecture (TCA) defines party information (e.g. suppliers and customers) and the Secure Payment Data repository stores the payment instruments (credit card and bank accounts) for the parties.  It is through this consolidation of payment instruments into the Secure Payment Repository that Oracle Payments offers its new functionality for the encryption and masking of payment instruments to meet the PA DSS requirements.

The key point to note is that only those products identified above make use of the Secure Payment Repository. More importantly, the PA DSS functionality provided by the Secure Payment Repository is NOT enabled by default.  The steps to enable it will be reviewed in the next blog posting

For further information on PCI compliance, Corporate Cards and the E-Business Suite please refer to our whitepaper in the link below.

If you have questions, please contact us at info@integrigy.com

 -Michael Miller, CISSP-ISSMP

References Tags: CompliancePCIOracle E-Business Suite
Categories: APPS Blogs, Security Blogs

Focusthread offers Oracle Golden Gate Training starts on 15 February 2014 @Lowest price ever!!!

Online Apps DBA - Sat, 2014-02-08 23:47
Get trained from the best instructor known to have trained novices as experts in this field. Commencement Date: 15 February 2014 Training Duration: 4 Days Training Schedule:- 15, 16, 22, 23 February 2014 Timing: 12:00 Noon GMT | 7:00AM EST | 4:00AM PST | 6:00AM CST | 5:00AM MST | 5:30PM IST Course Fee - USD 399   Course Content [...]

This is a content summary only. Visit my website http://onlineAppsDBA.com for full links, other content, and more!
Categories: APPS Blogs

R12.2 upgrade - icxr12pd.sql takes a very long time

Vikram Das - Sat, 2014-02-08 17:19
During an R12.2 upgrade, the worker icxr12pd.sql takes very long time.  This is document in My Oracle Support Article ICXR12PD.Sql Runs Slowly During Upgrade to 12.1.1 (Doc ID 864898.1)
 
Cause: The pre-upgrade steps for iProcurement were not implemented as documented in the upgrade guide
Though this article talks about R12.1.1, it also applies to R12.2.  If you read the 11i to R12.2 upgrade guide ( http://docs.oracle.com/cd/V39571_01/current/acrobat/122upg11i.pdf ). it has specifically mentioned on page 285:

iProcurement
Completing these tasks could substantially reduce the downtime required for your
upgrade.
The Catalog Data Pre-upgrade Process
This pre-upgrade process is strongly recommended if you are upgrading iProcurement
from 11.5.9 or 11.5.10 to Release 12. It pre-processes bulk-loaded content to reduce the
actual time required for the upgrade and to ensure the upgrade process runs smoothly.
You can run it multiple times. If exceptions are found, then make corrections and re-run
the program until no exceptions are noted. Running this program does not require users
to log off the system. Note: Exceptions noted and not fixed before the upgrade will not
be available in the iProcurement Catalog. Specifically, this program shortens the time it
takes to run these upgrade scripts:
• -icxiftug.sql: updates POR_TEMPLATE_INFO
• -icxr12in.sql: general setup upgrade script needed for iProcurement
• -poxujpoh.sql:updates PO_HEADERS_ALL (for example, create_language)
• -poxukpol.sql: updates PO_LINES_ALL (for example, ip_category_id)
• -poxukrt.sql: updates PO_REQEXPRESS_LINES_ALL (for example, ip_catetory_id)
• -icxr12ug.sql: migrates iProcurement data model to PO
• -icxr12rt.sql: populates the requisition templates in iProcurement intermedia index
tables
• -icxr12pd.sql: populates the Purchasing documents in iProcurement intermedia
index tables: blanket purchase agreements (BPAs), global blanket agreements
(GBPAs), and quotes
• -icxr12mi.sql: populates the master items in iProcurement intermedia index tables
• -poxukfi.sql: purchasing script to approve the GBPAs created during iProcurement
migration
• -poxukat.sql: purchasing script to update the attachments
• -icxr12fi.sql: final upgrade script, which upgrades favorite lists, purges the BPAs
and GBPAs that are not approved, and creates the intermedia index


Make sure that you complete the tasks described in the upgrade guide, during the pre-upgrade phase, much before actual cutover downtime starts.

If you haven't done this and proceed to upgrade, it is going to take a long time for all the workers which are going to run icxr12pd.sql.  Based on my analysis of v$sql_longops, this is the insert query most fired during this worker's execution:

INSERT INTO AP_INV_DISTS_TARGET T1 (BATCH_ID, INVOICE_ID, INVOICE_LINE_NUMBER,
INVOICE_DISTRIBUTION_ID, DISTRIBUTION_LINE_NUMBER, LINE_TYPE_LOOKUP_CODE,
DESCRIPTION, DIST_MATCH_TYPE, ORG_ID, DIST_CODE_COMBINATION_ID, ACCOUNTING_DATE,
PERIOD_NAME, ACCRUAL_POSTED_FLAG, CASH_POSTED_FLAG, AMOUNT_TO_POST,
BASE_AMOUNT_TO_POST, POSTED_FLAG, ACCOUNTING_EVENT_ID, SET_OF_BOOKS_ID, AMOUNT,
BASE_AMOUNT, EXCHANGE_DATE, ROUNDING_AMT, QUANTITY_VARIANCE, BASE_QUANTITY_VARIANCE,
MATCH_STATUS_FLAG, ENCUMBERED_FLAG, PACKET_ID, USSGL_TRANSACTION_CODE,
USSGL_TRX_CODE_CONTEXT, REVERSAL_FLAG, PARENT_REVERSAL_ID, CANCELLED_FLAG, INCOME_TAX_REGION,
TYPE_1099, STAT_AMOUNT, CHARGE_APPLICABLE_TO_DIST_ID, PREPAY_AMOUNT_REMAINING,
PREPAY_DISTRIBUTION_ID, PREPAY_TAX_PARENT_ID, PARENT_INVOICE_ID, CORRECTED_QUANTITY,
PO_DISTRIBUTION_ID, RCV_TRANSACTION_ID, UNIT_PRICE, MATCHED_UOM_LOOKUP_CODE, QUANTITY_INVOICED,
FINAL_MATCH_FLAG, RELATED_ID, ASSETS_ADDITION_FLAG, ASSETS_TRACKING_FLAG, PROJECT_ID, TASK_ID, EXPENDITURE_T

In our test environment, we have 25 million + rows in ap_inv_dists_target.  We have already waited for 8 hours for all the workers to complete.  Here's the status of the queries:

set pages 300 lines 300
col "Username" for a12
col "QC/Slave" for A8
col "Slaveset" for A8
col "Slave INST" for A9
col "QC SID" for A6
col "QC INST" for A6
col "operation_name" for A30
col "target" for A30

select
decode(px.qcinst_id,NULL,username,
' - '||lower(substr(pp.SERVER_NAME,
length(pp.SERVER_NAME)-4,4) ) )"Username",
decode(px.qcinst_id,NULL, 'QC', '(Slave)') "QC/Slave" ,
to_char( px.server_set) "SlaveSet",
to_char(px.inst_id) "Slave INST",
substr(opname,1,30) operation_name,
substr(target,1,30) target,
sofar,
totalwork,
units,
start_time,
timestamp,
decode(px.qcinst_id, NULL ,to_char(s.sid) ,px.qcsid) "QC SID",
to_char(px.qcinst_id) "QC INST"
from gv$px_session px,
gv$px_process pp,
gv$session_longops s
where px.sid=s.sid
and px.serial#=s.serial#
and px.inst_id = s.inst_id
and px.sid = pp.sid (+)
and px.serial#=pp.serial#(+)
order by
decode(px.QCINST_ID, NULL, px.INST_ID, px.QCINST_ID),
px.QCSID,
decode(px.SERVER_GROUP, NULL, 0, px.SERVER_GROUP),
px.SERVER_SET,
px.INST_ID
/

Username QC/Slave SlaveSet Slave INS OPERATION_NAME TARGET SOFAR TOTALWORK UNITS START_TIME TIMESTAMP QC SID QC INS
------------ -------- -------- --------- ------------------------------ ------------------------------ ---------- ---------- -------------------------------- --------------- --------------- ------ ------
APPS QC 1 Table Scan AP.AP_INVOICE_DISTRIBUTIONS_AL 1570329 1570329 Blocks 08-FEB-14 2335
APPS QC 1 Table Scan AP.AP_INVOICE_DISTRIBUTIONS_AL 1570329 1570329 Blocks 08-FEB-14 2335
APPS QC 1 Table Scan AP.AP_INVOICE_DISTRIBUTIONS_AL 1570329 1570329 Blocks 08-FEB-14 2335
APPS QC 1 Table Scan AP.AP_INVOICE_DISTRIBUTIONS_AL 1570329 1570329 Blocks 08-FEB-14 2335
APPS QC 1 Gather Table's Index Statistic 0 0 Indexes 08-FEB-14 2335
APPS QC 1 Table Scan AP.AP_INVOICE_DISTRIBUTIONS_AL 1570329 1570329 Blocks 08-FEB-14 2335
APPS QC 1 Table Scan AP.AP_INVOICE_DISTRIBUTIONS_AL 1570329 1570329 Blocks 08-FEB-14 2335

7 rows selected.
Categories: APPS Blogs

Security:090294 could not get connection javax. net. ssl. SSLKeyException FATAL Alert BAD_CERTIFICATE – A corrupt or unuseable certificate was received

Online Apps DBA - Fri, 2014-02-07 11:05
In today’s post I am going to discuss issue while integrating WebLogic Server with LDAP Server (OID/OVD) listening on SSL. To know more about adding OID as authentication provider in WebLogic click here If OID/OVD is configured to listen on SSL (for steps on how to configure OID/OVD in SSL click here and here ) then you select [...]

This is a content summary only. Visit my website http://onlineAppsDBA.com for full links, other content, and more!
Categories: APPS Blogs

Oracle E-Business Suite, PCI Compliance and External vs Internal Accounts

To help understand the Oracle E-Business Suite’s standard functionality to help meet PCI compliance, it is useful to know the difference between what Oracle deems as external and internal accounts.

Oracle defines “external accounts” as those accounts belonging to customers, suppliers, vendors, students, and external third parties.  These are the credit cards and bank account numbers customers and vendors use to conduct business with a company.  Oracle defines “internal accounts” as those accounts a company uses internally such as bank accounts defined within Accounts Payable or employee bank accounts defined within Oracle HR/Payroll for direct deposit. 

While it is highly recommended by Integrigy Corporation to appropriately protect the security of both external as well as internal accounts, PCI compliance requirements apply to only external accounts. 

For further information on PCI compliance and the E-Business Suite please refer to our whitepaper in the link below.

In the next blog posting we will review the Oracle E-Business Suite’s Secure Payments Repository and how it is used to help meet PCI compliance.

If you have questions, please contact us at info@integrigy.com

 -Michael Miller, CISSP

References Tags: CompliancePCIOracle E-Business Suite
Categories: APPS Blogs, Security Blogs

Oracle IAM 11.1.2.2 Certification Matrix – Supported JDK, WebLogic, OS

Online Apps DBA - Wed, 2014-02-05 16:54
If you are looking for certified O.S. , JDK, Database or Web Server version for Oracle Identity & Access Management then check Certification Matrix for Fusion Middleware Components here On Fusion Middleware Certification Matrix page, search for your Identity & Access Management version and click on XLS . For Certification Matrix for IAM version 11.1.2.2 click [...]

This is a content summary only. Visit my website http://onlineAppsDBA.com for full links, other content, and more!
Categories: APPS Blogs