Best Of
Re: What Risk Analysis setting is considered when running it via recurring services?
Yes, this would be a challenge with the set up today. I think this is a good idea for an enhancement.
Re: Does Risk Import Template Support Risk code assignment?
Hi @Dave Hammal - Oracle Construction & Engineering-Oracle ,
At the moment one project and register. But I was curious on exploring the options for future.
I'll have a check on the API options as well
Thanks & Regards,
Ajay Dev N S
Re: Patch 30771422 : Error in the Read Me file
Hi
In XML, attributes must be clearly separated by whitespace. so this is a problem
I will contact DEV team for this to correct it. To set expectattion, possible to take some time till corrected, but it should be.
Thanks
Stefan
Announcing a new simplified Support Repository Update (SRU) schedule for Oracle Solaris 11.4 and ZFS
Currently, each month Oracle releases a new SRU for Oracle Solaris 11.4 and ZFS Storage Appliance software. The first SRU in the calendar quarter is called a Critical Patch Update (CPU) and focuses on security and bug fixes. This CPU aligns with the critical updates released for other Oracle products. The second SRU introduces new features as per our continuous release model [link], and the third delivers additional fixes. In the case of ZFS Storage Appliance software, SRUs are called Micro releases.
Oracle is adopting a simplified release cadence of two updates per calendar quarter, which will now consist of:
- A Critical Patch Update (CPU) (or Micro release) aligned with Oracle’s quarterly security release cycle, delivering security and bug fixes.
- A Support Repository Update (SRU) feature release (or Micro feature release) will be available approximately six weeks later, delivering new capabilities and enhancements.
This change provides customers with a clear and predictable release structure. By separating the quarterly security and maintenance update from the feature release, customers can more easily plan patching, validation, and production deployment while continuing to adopt innovation on a regular basis. The quarterly CPU remains the primary stability and security milestone, aligned with the broader Oracle portfolio. The SRU continues to deliver new functionality on a predictable schedule, with improved separation allowing evaluation and rollout planning.
This new cadence is intended to simplify lifecycle management while maintaining the quality, stability, and responsiveness that customers expect from Oracle Solaris and our ZFS Storage Appliance software. An interesting point is that, based on our statistics of SRU and Micro release adoption, an installation frequency of once or twice a quarter is already preferred by most customers.
As a reminder, every CPU, SRU and Micro release includes all previous enhancements and fixes. Oracle will also continue to provide Interim Diagnostic or Relief (IDR) updates for urgent customer specific issues between SRUs when needed, and those fixes also roll into subsequent updates as part of the standard release process.
For more information on Oracle Support policies please consult this document
Re: Getting "Cannot call getText() on a secret entry" error while migrating order version 21 to 25
@User_Z4K9S I'll save you a bit of trouble (hopefully)….
KB213246 | "Cannot call getText() on a secret entry" when trying to upgrade ORDS from 19.x or 20.x to 25.2 | Knowledge Article
That doc says to go to 24.3 or 25.1 as a step and then onto later version. I successfully used 25.1 to upgrade from 21.3. And then went to 25.4.
Ran into a couple of other issues along the way, and the following docs helped. I'll go ahead and post them here just in case it helps anyone… actually finding this stuff in the new MOS was a pain.
KB482040 | ORDS upgrade failed with error'ORA-04063: package body "ORDS_METADATA.ORDS_INTERNAL" has errors' | Knowledge Article
KB454982 | No Pools Configured Yet In Tomcat Log File After Upgrading ORDS 22.x | Knowledge Article
Re: Configuring Veritas Netbackup to create Tape copies of Protected Database backups
According to the official ZDLRA documentation, tape copies of protected database backups must be driven from the RA itself, not directly from the databases, which means Veritas NetBackup is used only as a third‑party media manager on the ZDLRA side and not as an RMAN target on the database hosts. This requires to install the NetBackup media manager library on the RA compute nodes, define an SBT library in the RA catalog that points to the NetBackup shared library, create one or more SBT attribute sets with the NetBackup‑specific parameters (such as media pool and any vendor‑specific options), and then configure and schedule RA copy‑to‑tape jobs (via DBMS_RA or Enterprise Manager) that stream virtual full/incremental backup pieces from ZDLRA to NetBackup.
