Piotr Wrzosek
@pewu78.bsky.social
Dealing with Oracle products (mainly DB(A)) since 2000. POUG member. Interests/hobbies: playing guitar, electronics, home automation, 3D graphics.
Mike put up a blog post explaining all of it late yesterday, just not linked it yet here.
And again we have a release numbering change...
mikedietrichde.com/2025/10/14/o...
And again we have a release numbering change...
mikedietrichde.com/2025/10/14/o...
Oracle AI Database 26ai replaces Oracle Database 23ai
Larry Ellison announced Oracle AI Database 26ai today in his keynote at Oracle AI World conference in Las Vegas. And I am pretty certain you may want some clarification on what this means exactly.…
mikedietrichde.com
October 15, 2025 at 6:31 AM
Mike put up a blog post explaining all of it late yesterday, just not linked it yet here.
And again we have a release numbering change...
mikedietrichde.com/2025/10/14/o...
And again we have a release numbering change...
mikedietrichde.com/2025/10/14/o...
"Oracle AI Database 26ai Free Release 23.26.0.0.0"
October 14, 2025 at 4:14 PM
"Oracle AI Database 26ai Free Release 23.26.0.0.0"
"This section is not visible to customers"
Not really.
Not really.
October 8, 2025 at 11:39 AM
"This section is not visible to customers"
Not really.
Not really.
Reposted by Piotr Wrzosek
MOS AI assistant does that too:
bsky.app/profile/pewu...
bsky.app/profile/pewu...
Have you seen new AI assisted search on MOS?
I can see the potential here, but...
Why 21c?
Why fixed 280px answer area size? (increased it in console for the screenshot so you can see it all)
And who can first spot where it hmm... let it's imagination run wild and misleads us?
I can see the potential here, but...
Why 21c?
Why fixed 280px answer area size? (increased it in console for the screenshot so you can see it all)
And who can first spot where it hmm... let it's imagination run wild and misleads us?
August 13, 2025 at 5:04 PM
MOS AI assistant does that too:
bsky.app/profile/pewu...
bsky.app/profile/pewu...
I got "There has been a critical error on this website." message only for a long time when visiting your blog.
August 13, 2025 at 4:52 PM
I got "There has been a critical error on this website." message only for a long time when visiting your blog.
OK, looks like it's not mentioned directly in changelog.
July 30, 2025 at 9:19 AM
OK, looks like it's not mentioned directly in changelog.
What version of AU introduced that (and other home_settings options)?
July 30, 2025 at 6:46 AM
What version of AU introduced that (and other home_settings options)?
That's even more complicated, it changed in the past over the versions - it worked, then not without some workarounds, as of now it's fixed after my SR.
Full story here:
bsky.app/profile/pewu...
Full story here:
bsky.app/profile/pewu...
Finally, after 8 months of waiting the #SQLcl 25.2 release fixes this issue.
It took me great effort to fill the SR, deal with the clueless person handling it for several months, escalate, etc. to reach this goal. To just get back to where it was working in 24.1.
Should be happy but I'm more tired.
It took me great effort to fill the SR, deal with the clueless person handling it for several months, escalate, etc. to reach this goal. To just get back to where it was working in 24.1.
Should be happy but I'm more tired.
...and unfortunately that was the case with SQLcl 21.1 up to 24.1, but since 24.2 it is not working anymore and requires additional ?tns_admin= connection parameter ☹️
@thatjeffsmith.com @martindba.bsky.social - can anyone look at this regression?
@thatjeffsmith.com @martindba.bsky.social - can anyone look at this regression?
July 23, 2025 at 10:29 AM
That's even more complicated, it changed in the past over the versions - it worked, then not without some workarounds, as of now it's fixed after my SR.
Full story here:
bsky.app/profile/pewu...
Full story here:
bsky.app/profile/pewu...
Cannot open SQLcl from SQLDev due to this error, but I can connect successfully from the edit connection window as the password field is not checked for content there.
July 22, 2025 at 11:28 AM
Cannot open SQLcl from SQLDev due to this error, but I can connect successfully from the edit connection window as the password field is not checked for content there.
And turns out the connection to source CDB SID is redirected to the hostname of new CDB, but to the management name not VIP so not working properly too. But anyway why CDB when it's PDB that's being relocated?!?
Either way it screws up EM monitoring and backups.
It's all a mess.
Either way it screws up EM monitoring and backups.
It's all a mess.
July 8, 2025 at 3:03 PM
And turns out the connection to source CDB SID is redirected to the hostname of new CDB, but to the management name not VIP so not working properly too. But anyway why CDB when it's PDB that's being relocated?!?
Either way it screws up EM monitoring and backups.
It's all a mess.
Either way it screws up EM monitoring and backups.
It's all a mess.
PDB services are running, local listener reports them but scans not, so connections are refused with ORA-12514. LISTENER_NETWORKS is not updated, no chance of connection forwarding. On top of that ORA-00600 [krbbbdr_bad_guid] occurs during backup of tombstone PDB files supposedly due to Bug 36534336
July 8, 2025 at 9:30 AM
PDB services are running, local listener reports them but scans not, so connections are refused with ORA-12514. LISTENER_NETWORKS is not updated, no chance of connection forwarding. On top of that ORA-00600 [krbbbdr_bad_guid] occurs during backup of tombstone PDB files supposedly due to Bug 36534336
On a downside what hasn't changed is #SQLcl still defaults to thick connection on Windows, even with no client present in path/env, while on Linux it's opposite. Why? 🤷♂️
Reported it also in the same SR to no effect...
For reference this thread describes my initial findings: bsky.app/profile/pewu...
Reported it also in the same SR to no effect...
For reference this thread describes my initial findings: bsky.app/profile/pewu...
I dedicate my first tech post to my first follower :)
#SQLcl 24.3 brings new interesting feature for CI/CD - the 'project' command - which I'll definitely test, but for now I'm happy to see inclusion of 23 JDBC driver which finally aligns well with e.g. instant client 23.5 (no more version mismatch)
#SQLcl 24.3 brings new interesting feature for CI/CD - the 'project' command - which I'll definitely test, but for now I'm happy to see inclusion of 23 JDBC driver which finally aligns well with e.g. instant client 23.5 (no more version mismatch)
July 8, 2025 at 8:19 AM
On a downside what hasn't changed is #SQLcl still defaults to thick connection on Windows, even with no client present in path/env, while on Linux it's opposite. Why? 🤷♂️
Reported it also in the same SR to no effect...
For reference this thread describes my initial findings: bsky.app/profile/pewu...
Reported it also in the same SR to no effect...
For reference this thread describes my initial findings: bsky.app/profile/pewu...
Another thing worth to mention is #SQLcl now seems to be not so much dependant on JDBC driver version when using thick connection and works with any 23 client (tested IC 23.5-23.8) as long as it's in the path. I don't find the selected excerpt from release notes to be true, it doesn't work that way.
July 8, 2025 at 8:13 AM
Another thing worth to mention is #SQLcl now seems to be not so much dependant on JDBC driver version when using thick connection and works with any 23 client (tested IC 23.5-23.8) as long as it's in the path. I don't find the selected excerpt from release notes to be true, it doesn't work that way.