Best Of
Re: New MOS Search Needs a Lot Of Improvement
I am amazed that oracle corp. released such an immature product (MOS) in Dec. 2025. If the the database software had been of similar poor quality in the past, oracle corp. would no longer exist today.
Re: What happened to My Oracle Support?
Oracle is not listening to customers! Very bad indeed! The new MOS compromises our ability to perform the work we need to do. It simply does not work at the high level that customers are paying for, there are still many issues with performance, search results, patch download, article formatting. All Oracle keeps saying via the new MOS is that they are working on improvements, but which improvements are those? It has been almost 12 months since the new MOS was rollout out. If Oracle thinks this will force us to move to the Oracle Cloud, big mistake, customers might just switch to another rdbms vendor, and/or go to a different cloud provider.
Re: PeopleTools Upgrade to 8.62.07 impacting master data
Hi Everyone,
Thank you for your input. My question is, how do we know specifically which configuration we need to check for any changes, if we do not know exactly what is in scope for change? This cannot be an unknown.
Does anyone have the list of tables where data might be changed by PeopleSoft?
Thanks & Regards
Leona
Leo_8888
Cycle Counting for items with Zero Quantity. (Inventory - Oracle EBS)
We are performing a Cycle Count for a selected group of inventory items.
(These inventory items belong to a sub-inventory and the 'Count Zero Quantities' in Auto Schedule section is selected when defining the cycle Count).
But Count requests won't get generated for the items with zero on-hand quantity. The items with zero quantities won't get selected to the Cycle Count Listing report as well.
Please advice how the count requests can be generated for the items with zero on-hand quantity.
Cheers,
Samindi
SKM
Simplified Development Client
Simplified Development Client
We are currently using simplified web development and this was all workin until recently. We have done no tools or UN upgrades.
Suddenly when anyone attempt to create a new log it is simply flashing and nothing happens. In the log we get the below message.
SMCSysFunctionRequests: getUserLogFilesList() fails with an exception, java.lang.IllegalArgumentException: URL contains invalid characters.
I can ma nually go to the URL without any issues - I am not sure where it is passing the URL to see if there are any special characters. I am on the latest planner and tools rollup ESU's.
The SMC configuration have not changed.
webProductLogInstance is assigned to the group in SMC.
Cleola
Re: Latest CSPU patch # 39952167 does it have a latest OJVM Release update matching the exact target CSP
I guess Oracle is working on it since we have raised an SR.
Would suggest you to raise an Oracle SR as well so that they know of the impact across various customers.
Re: Latest CSPU patch # 39952167 does it have a latest OJVM Release update matching the exact target CSP
I have an SR raised on this too. Awating update.
Re: Latest CSPU patch # 39952167 does it have a latest OJVM Release update matching the exact target CSP
Hello OP,
Has there been any resolution provided by Oracle yet?
I have an SR raised too but wondering if we should just wait for Oct CPU.
Re: Latest CSPU patch # 39952167 does it have a latest OJVM Release update matching the exact target CSP
O:\Ora64\product\19c\Patches\39952167\39952167>opatch prereq CheckConflictAgainstOHWithDetail -ph ./
Oracle Interim Patch Installer version 12.2.0.1.53
Copyright (c) 2026, Oracle Corporation. All rights reserved.
PREREQ session
Oracle Home : O:\Ora64\product\19c
Central Inventory : O:\Ora64\Inventory
from :
OPatch version : 12.2.0.1.53
OUI version : 12.2.0.7.0
Log file location : O:\Ora64\product\19c\cfgtoollogs\opatch\opatch2026-09-17_12-02-31PM_1.log
Invoking prereq "checkconflictagainstohwithdetail"
ZOP-40: The patch(es) has conflicts with other patches installed in the Oracle Home (or) among themselves.
Prereq "checkConflictAgainstOHWithDetail" failed.
Summary of Conflict Analysis:
Patches that can be applied now without any conflicts are :
39487170, 39761039, 39897693, 39996899
Following patches have conflicts. Please contact Oracle Support and get the merged patch of the patches :
39222882, 39996979
Following patches are not required, as they are subset of the patches in Oracle Home or subset of the patches in the given list :
39661089, 39750798, 39779336, 39854538
Conflicts/Supersets for each patch are:
Patch : 39661089
Identical duplicate of 39661089
Patch : 39750798
Identical duplicate of 39750798
Patch : 39779336
Identical duplicate of 39779336
Patch : 39854538
Identical duplicate of 39854538
Patch : 39996979
Conflict with 39222882
Conflict details:
O:\Ora64\product\19c\bin\oracle.exe
O:\Ora64\product\19c\rdbms\admin\oracle.sym
OPatch succeeded.
Re: What PeopleSoft Customers Need to Know for IRS 2026 Filings
There is a known issue in the current process where commas are not being stripped from the CSV file. This can cause the subsequent fields to shift. The issue is being addressed as part of the 2026 file changes.
Per the IRS CSV formatting guidelines:
- Business or Entity Name Lines 1 and 2: May contain letters, numbers, spaces, and only these special characters: hyphen (
-), pound sign (#), parentheses (()), ampersand (&), and apostrophe ('). - First and Last Names: Maximum 20 characters; may contain letters, spaces, and hyphens (
-) only. - Payer Address Lines: May contain alphanumeric characters, spaces, hyphens (
-), and slashes (/) only.
Any characters outside these allowed sets, including commas in business names and addresses, should be avoided until the updated process is available.
