Online DBA

<<Back to DB Administration Main Page How to Add the JVM Component to an Existing Oracle Database Followed oracle Doc ID 1461562.1 and installed oracle JVM component in multitenant database, the script installed JVM component in CDB$ROOT container only and the component was still missing in PDB$SEED and all pluggable database. Since the script and steps mentioned in Doc ID 1461562.1 did not install the component in PDB$SEED , all future PDBs create in the container also inherited the issue and eventually JVM  component was not installed in any of the PDBs. Scroll down to see how to install JVM component in a Multitenant Database environment using catcon.pl How to Verify if JVM component is installed or not select comp_name, version, status from dba_registry where comp_name like '%JAVA%' ; COMP_NAME                           ...

<<Back to Oracle Backup & Recovery Main Page Starting Control File and SPFILE Autobackup at 2020-01-28 20:45:29 RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03009: failure of Control File and SPFILE Autobackup command on ORA_SBT_TAPE_1 channel at 01/28/2020 20:45:32 ORA-00245: control file backup failed; in Oracle RAC, target might not be on shared storage Cause :  SNAPSHOT CONTROLFILE configuration not correct  Solution: Configure  SNAPSHOT CONTROLFILE parameter to shared location eg to ASM Diskgroup $rman target / RMAN> CONFIGURE SNAPSHOT CONTROLFILE NAME TO '+FRA/snapcf_orcl1p.f';

<<Back to Linux Main Page   How to Check if port to a remote server is open or not to check if the port XYZ to a remote server ABC is open or not you can use telnet telnet  ABC  XZY $telnet host1 1521 But many times we realize that the package telnet is not installed we can use curl in that case How to Check if port to a remote server is open or not without using telnet curl http://192.250.65.175:1521 curl: (7) Failed to connect to 192.250.65.175 port 1521: Connection refused

<<Back to Oracle DataGuard Main Page Error: ORA-16765: Redo Apply is running DGMGRL> show configuration; Configuration - DG_TST1T   Protection Mode: MaxAvailability   Databases:     TST1TS - Primary database     TST1TP - Physical standby database       Error: ORA-16765: Redo Apply is running Fast-Start Failover: DISABLED Configuration Status: ERROR CAUSE: Broker configuration out of sync with MPR running causes by using sqlplus to start and stop MRP instead of dgmgrl.  SQL> select dest_name,recovery_mode,database_mode,type,status from v$archive_dest_status where type like '%PHYSICAL%'; DEST_NAME                      RECOVERY_MODE           DATABASE_MODE   TYPE           STATUS ----...

<<Back to Oracle DATAPUMP Main Page expdp fails with ORA-01690: sort area size too small expdp As per Metalink note Doc ID 1911968.1 issue has been fixed in 12.1 and above however I had the issue in 12.1.0.2 version while performing full database export using expdp utility. Tried to increase the pga_aggregate_target from 2G to 10G but no luck.  Solution1: Recommended  Changed the parameter file to have schema based export instead of full. Before userid= system directory=dump dumpfile=dump_%U logfile=exp.log full=y parallel=3 flashback_scn=291638761 AFTER userid= system directory=dump dumpfile=dump_%U logfile=exp.log schemas=TEST1, TEST2 parallel=3 flashback_scn=291638761 Solution2: use traditional exp utility instead of expdp

<<Back to Oracle DataGuard Main Page Error: ORA-16647: could not start more than one observer Although observer is not started receiving the following error while starting the observer [W000 01/03 12:44:30.72] Failed to start the Observer. Error: ORA-16647: could not start more than one observer DGMGRL> show configuration verbose; .................................................................. .................................................................. Fast-Start Failover: DISABLED   Threshold:          300 seconds   Target:             ORCL1S   Observer:           host_observer   Lag Limit:          30 seconds (not in use)   Shutdown Primary:   TRUE   Auto-reinstate:     TRUE   Observer Recon...

<<Back to DB Administration Main Page  Oracle 12.1.0.2 Support Extended The Extended Support for Oracle 12.1.0.2 has been extended for another one year. It was ending by July 2021. Now you can purchase it until end of July 2022. For additional details have a look at  Doc ID 742060.1