How to drop a database using DBCA in silence mode
I have a 19c database which I would like to drop it using DBCA utility. If we cannot use GUI, we have this command instead: Let’s see how it goes on my side: Looks good 🙂
I have a 19c database which I would like to drop it using DBCA utility. If we cannot use GUI, we have this command instead: Let’s see how it goes on my side: Looks good 🙂
This is happening when one is trying to delete a database using DBCA utility. The reason for the failure is that there is no information about the database in /etc/oratab: Let’s reproduce it: Let’s add the information of the database into /etc/oratab file: Let’s try again to drop it: Happy ending 🙂
At the end of this post we should have a working Goldengate environment where we can replicate a dummy table. High level steps: Install an Oracle database (19c) Install Goldengate 21c (source and destination will be on the same machine in my case) (You can follow this post: ora-base.com/how-to-install-goldengate-21c-in-silent-mode Create the source and destination pluggable…
Let’s create the sample schema HR in a new PDB Step 1 ) Navigate to the DEMO folder Step 2 ) Connect to the PDB and execute the “hr_main.sql” This is going to create the HR user into the PDB Step 3 ) Let’s connect as HR and check the tables
Usually we do the installation using the graphical interface. Let’s try this time the silent mode: This is my environment: Download the software from: https://www.oracle.com/middleware/technologies/goldengate-downloads.html#license-lightbox Copy the file to a staging location on the server. In my case will be “/u01/software”: Step 1) Unzip the software Step 2) Create Response File This is my response…
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…