ORA-15260: permission denied on ASM disk group
ORA-15260 error pops up when you try to drop/create an ASM diskgroup while connecting as SYSDBA. Oracle 11g onward, oracle requires SYSASM privilege do CREATE or DROP an ASM diskgroup.
ORA-15260 error pops up when you try to drop/create an ASM diskgroup while connecting as SYSDBA. Oracle 11g onward, oracle requires SYSASM privilege do CREATE or DROP an ASM diskgroup.
I use Synology DS920+ in order to provision disks for Oracle ASM. Let’s start leveraging it: Login to DS920+ and click on “SAN Manager” app: This is how it looks in my test environment: Creating the iSCSI targets: We will create 6 target disks that will be managed by ASM:– TGT-ASM-MGMT1 => 50GB– TGT-ASM-DATA1 =>…
Most probably you did a shutdown abort in order to speed up the bounce process 🙂 so you can set your database into archivelog mode.Below, you can find an example of how one can reproduce this error: The solution is an easy one. All you have to do is to bring you database in OPEN…
Rolling upgrade with Transient Logical Standby is known as a MAA (Maximum Availability Architecture) technique, to minimize downtime during upgrade of Oracle database. Approaches: There are several methods which can be used: Manually from command line Manually using phsyru.sh script which is available since 11g (Doc ID 949322.1) Use DBMS_ROLLING package which is available since 12.1.0.1 (Doc ID 2086512.1) Note: for both manual…
I find that’s a good idea to have a different ORACLE_HOME when it comes to patching or maybe you want to have the same oracle home setup in a lower environment than PROD. The cloning comes in very handy rather doing the whole installation (including whatever patches have been deployed in the past) again. One…
I’ve found this very interesting, having my online VSCode accessible from any laptop / tablet within my network. Bellow I will describe the steps I took to make that possible: To install a VS Code server, we will use code-server by coder. To install it, run the following command: This is the output: The installation is very minimal…
After executing an upgrade exercise in a dataguard environment (19c), the broker was still showing the status: “ROLLING DATABASE MAINTENANCE IN PROGRESS” This is due to a bug: Bug 26921039 – INCORRECT DGMGRL SHOW CONFIGURATION STATUS AFTER POST ROLLING UPGRADE SWITCHOVER Solution is simple: Execute the following statement on PRIMARY database and bounce it: Let’s…
It’s not something new in 19c, however, this feature has been improved and covers all the steps that a DBA must do or was supposed to do in the past in order to recover a lagging standby. I will simulate it and this is my setup: I have created a dataguard environment using Vagrant. The…
I know is not the most optimized Vagrantfile written out there but, I’m going to post only the Vagrantfile for the moment and soon I will upload also the files used to create the databases and broker config: And the result would be something like this:
I know is not the most optimized Vagrantfile written out there but, I’m going to post only the Vagrantfile for the moment and soon I will upload also the files used to create the databases and broker config: And the result would be something like this: