Presented at BLUEPRINT 4D
Session ID: 104600

Presented at BLUEPRINT 4D
Session ID: 100440

Presented at BLUEPRINT 4D
Session ID: 100510

Do you have your PeopleSoft or JD Edwards application environments in either on-premises, or on Exadata Cloud? How do you ensure your applications infrastructure is secure, have all vulnerabilities patched, and compliant with security policies?

Presented at BLUEPRINT 4D
Session ID: 104210

Accurate master data is the bedrock for system integrity. It guides users through the master data process to ensure the data is entered, approved, and finally loaded, via integrations, into JDE. It also utilizes system processes to reduce manual input for improved accuracy and efficiency.

With support ending or expiring for Oracle database versions before 19c, there’s likely an upgrade in your future. Unfortunately, the technical skills and procedures developed for earlier database versions are no longer supported. New requirements and features introduced in Oracle Database versions 19c and 23c completely change your upgrade workflows! There’s so much to consider that it’s easy to feel intimidated, even overwhelmed!

AutoUpgrade mitigates the risks and fears database administrators face. It offers unparalleled simplicity and control over all phases of the upgrade process, covering every imaginable upgrade and migration scenario. AutoUpgrade’s built-in error detection, correction, and self-healing capabilities protect the database at every step, offering peace of mind in any environment—including those running RAC, Data Guard, GoldenGate, encryption, and legacy and multi-tenant architectures.

In this session, I share practical advice based on my experience upgrading dozens of production databases with AutoUpgrade and working with Oracle’s AutoUpgrade team

Oracle SQL Plan Management (SPM) is often overlooked and underused. This feature started in version 11.1 and has been enhanced with each new release. As of 19c this should be your goto method to help maintain well performing SQL statements.

How many times have we heard of breaches due to compromised (guessed or brute forced) passwords?

So, can we get rid of passwords from the Oracle database? Are there more secure alternatives?

Well, there are a number of extremely low-risk easy changes and various other things we can do to remove passwords. Let’s discuss password weaknesses and some alternatives for authentication. And categorize, group and rank each suggestion based on implementation risk and complexity.

Keeping data private and secure is a major challenge, and we need proof of making those efforts. We managed to be compliant and safeguard databases by implementing various Oracle Security products and features. We implemented Transparent data encryption (TDE), Backup Encryption, Database Vault, Audit Vault, GoldenGate Encryption, Data Masking and several other security best practices. In this session, the attendees will have a revision of all available Oracle Advanced Security features and will get a brief idea what it takes to implement those.