Best Of

Re: Users not able to request access in new Cloud support portal and Admins cannot add them

Reading this with despair; we support multiple clients and require the ability to raise SRs for all our clients.

While some of us have had our CSI access ported over from old MOS, it's proving virtually impossible for our newer users to request access to clients as we're unable to determine what the CSI equivalent is for each client.

The client often has little / no experience of using Cloud Console and can't provide details. For other clients, some of us are user group admins but can't add colleagues access. User group names might be a string of numbers, a seemingly random string of letters and numbers, the client name, or a 4 character environment name (that includes those usergroups showing 'created for legacy CSI by Oracle Migration').

Documentation, such as that linked above, provides little assistance due to reliance on cloud admins. Many clients are unaware of who their cloud admin is; we can't help them here. We've been advised to 'log an SR' in this instance, when the issue is we can't log SRs for that client!

Reviewing knowledge doc MC11 refers to outdated Cloud Console pages and navigation which don't reflect new pages.

It's mind blowing how poor the user experience now is and how enormously frustrating and time-consuming new MOS has become.

Alastair Wood

1

Re: Can I run the post-install script once for multiple installations of Oracle database patches?

You can start datapatch for one database, let it begin, then start another one. Starting two at the exact same time has a high chance of one failing with failure to get lock on Central Inventory.

Wesley D-Oracle

2

Re: Patch 37102264 & Patch 37486199

@Mr. C Actually, when it comes to the world of Oracle Database on Windows, and how the database is patched on Windows, the OJVMRU has a requisite against the WINDBBP.

For example:
The 19.27 OJVMRU for Windows will only if the 19.27 WINDBBP is already in place.
The 19.27 WINDBBP will not apply if an older OJVMRU for Windows is already in the Oracle Home.
If there is already a 19.26 WINDBBP and 19.26 OJVMRU applied in the Oracle Home, you would first have to rollback the 19.26 OJVMRU just so that the 19.27 WINDBBP can apply. After the 19.27 WINDBBP is applied, then you can proceed to apply the 19.27 OJVMRU for Windows.

Yes, I know patching on Linux/Unix does not have this constraint. This is just now it is in Windows though, and one of the things that makes patching Oracle on Windows different than Linux/Unix.

Windows: Bundle Patch Conflicts with OJVM Patch (Doc ID 2022382.1)

—

With Oracle 21c and newer, there is no separate OJVMRU. It has been absorbed into the DBRU/WINDBBP.

Wesley D-Oracle

1

Re: Issues with OpenSearch Dashboard Aggregations

Wade,

You might need to look at when you are completing your full crawl, how much data are crawling for? All data or data based on a time period. Example - for some of our indexes like Suppliers we index the full data and supplement it by RTI, but for AR ITEMS we complete a full crawl for only 3 years and then each morning we complete an INCREMENTAL crawl to update for previous night's activity. If these don't help then sometimes, I have dig into how the connected query (generally) creates the index data and work out the differences between it (connect query) and my SQL that I am trying to reconcile to.

If this doesn't make sense, we can figure out a time to meet and chat.

Thank you

Janel

Janel L

1

Re: ODA BUI: "There was an error connecting to the agent."

Thanks Krisz, this did the trick!

Cheers, Uwe

Uwe Küchler

1

Re: retention for contents in recycle bin

No internal parameters, and as dp says, an object could remain in the recyclebin for seconds or years depending on the space requirements.

It is simple to create a job to regularly purge older objects. This could be run before space monitoring scripts to get a real situation.

set serveroutput on
declare
sql_stmt varchar2(50);
begin
dbms_output.enable(1000000);
for dt in (select object_name from user_recyclebin
             where to_date(droptime,'YYYY-MM-DD:HH24:MI:SS') < sysdate-2
             and type = 'TABLE') loop
    sql_stmt := 'purge table "'||dt.object_name||'"';
    dbms_output.put_line(sql_stmt);
    execute immediate sql_stmt;
end loop;
end;
/

will purge all tables dropped more than 2 days ago

BobB

BobBeattie

1

Re: Difference UDOs

Not sure what kind of difference you are looking for.

App version: They are just a record in F983051 with their own PO values. They have been around from very old releases. If you make any changes to the PO values, it will be immediately reflected for all other users in the same environment.

UDOs: User defined objects were something new introduced in 9.2 tools release. They have their own tables in central object data source with corresponding OL entries in F9860W and F9861W. You have to reserve the existing UDOs to make changes and then need to Share it to make the change available for all the users who have the view security.