Remove Dataguard Configuration From Primary Database
💡 If you wish to remove the dataguard/standby setup from primary database i.e to make the primary database as standalone database without any standby database, then follow below steps. 1.Put…
💡 If you wish to remove the dataguard/standby setup from primary database i.e to make the primary database as standalone database without any standby database, then follow below steps. 1.Put…
💡 Solve ORDS was unable to make a connection to the database Many Oracle APEX developers & users encountered ORDS 503 Service Unavailable problems like: ORDS was unable to make a connection…
Cause: The network between primary and standby must be broken ERROR: ORA-16664: unable to receive the result from a database DGM-17017: unable to determine configuration status SOLUTION: Check lại…
ORA-16714: the value of property ArchiveLagTarget is inconsistent with the database setting ORA-16714: the value of property LogArchiveMaxProcesses is inconsistent with the database setting ORA-16714: the value of property LogArchiveMinSucceedDest…
ERROR: CREATE CONFIGURATION my_dg_config AS PRIMARY DATABASE IS bvtb CONNECT IDENTIFIER IS bvtb; Error: ORA-16501: The Oracle Data Guard broker operation failed. Error: ORA-16625: cannot reach database “dktb” SOLUTION:…
Error in invoking target ‘client_sharedlib’ of makefile ‘/u01/app/oracle/product/12.1.0.2/db_1/rdbms/lib/ins_rdbms.mk’. See Chạy câu lệnh sau yum -y install gcc or yum -y install gcc-c++
I deleted the test database, and now I want to restore it back, when I try to recover the database I get this error. Everything I had at the database…
We have got this error while we begin the installation Of Oracle database 19c on Oracle Linux 8 Lỗi / Problem $ ./runInstaller -silent -responseFile install/response/db_install.rsp Launching Oracle Database Setup Wizard……
Lỗi khi startup database trên con standby SQL> startup ORACLE instance started. Total System Global Area 1912602624 bytes Fixed Size 2925792 bytes Variable Size 1191185184 bytes Database Buffers 704643072 bytes…
This was caused by reusing ASM disks from a previous installation of GI. Remedied this with the following commands: [root@redfern1 ~]# dd if=/dev/zero of=/dev/sda1 bs=32768 count=32768 conv=notrunc oflag=direct 32768+0 records…