Skip to main content

Posts

ORA-00093: pga_aggregate_limit must be between 10240M and 100000G

<<Back to DB Administration Main Page ORA-00093: pga_aggregate_limit must be between 10240M and 100000G SQL> startup ORA-00093: pga_aggregate_limit must be between 10240M and 100000G ORA-01078: failure in processing system parameters SQL> Disconnected Cause: pga_aggregate_limit  is less than double of pga_aggregate_target. Starting from oracle 18c pga_aggregate_limit must be twice or more than twice than pga_aggregate_target  Solution: set   pga_aggregate_limit twice or more the value of pga_aggregate_target. example SQL> show parameter pga NAME                                 TYPE        VALUE ------------------------------------ ----------- ------------------------------ pga_aggregate_limit     ...

Warning: ORA-16869: fast-start failover target not initialized

<<Back to Oracle DataGuard Main Page Warning: ORA-16869: fast-start failover target not initialized This is just a warning oracle is still enabling FSFO. Wait for few minutes and re-sun the show configuration command.  DGMGRL> enable fast_start failover Enabled. DGMGRL> show configuration; Configuration - DG_ORCLDB   Protection Mode: MaxAvailability   Members:   ORCLDBP - Primary database     Warning: ORA-16869: fast-start failover target not initialized     ORCLDBS - (*) Physical standby database Fast-Start Failover: ENABLED Configuration Status: WARNING   (status updated 22 seconds ago) DGMGRL>  show configuration; Configuration - DG_ORCLDB   Protection Mode: MaxAvailability   Members:   ORCLDBP - Primary database     ORCLDBS - (*) Physical standby database Fast-Start Failover: ENABLED Configuration Status: SUCCESS   (status updated 29 seconds ago) ...

How to Restrict the Number of Pluggable database in a Container Database

<<Back to DB Administration Main Page How to Restrict the Number of PDBs in a CDB As you may already know there is no parameter to restrict the number of PDBs for a CDB in 12.1. Which means if you intensely or accidental created more than 1 PDB in your CDB you bought licenses Multitenant option. You may also know that, you can create up to 252 user-defined pluggable databases in 12.1. To prevent the accidental creation of PDBs and avoid buying out the not required licenses oracle introduced MAX_PDBS  parameter from 12.2 onwards   MAX_PDBS <= MAX_PDBS specifies a limit on the number of pluggable databases (PDBs) that can be created in a CDB or under an application root. D efault value is 4098 Range of values 0 – 4098 In case of Oracle RAC, value must be same on all instances. This parameter can only be set while connected to the CDB root or the application root. Only user-created PDBs are counted. PDB$SEED, application seed, and application root clones are i...

Oracle Database tablespace Rename

<<Back to DB Administration Main Page How to rename a tablespace in oracle A tablespace in oracle can be renamed using alter tablespace rename command. To rename a tablespace TS1 to TS2 you run below command. SQL> alter tablespace TS1 rename to TS2; Tablespace altered. NOTE: SYSTEM and SYSAUX tablespace cannot be renamed. Lets rename the TEMP tablespace in oracle SQL> show pdbs     CON_ID CON_NAME                       OPEN MODE  RESTRICTED ---------- ------------------------------ ---------- ----------          2 PDB$SEED                       READ ONLY  NO          3 PDB01           ...

The Central Inventory is corrupted

<<Back to DB Administration Main Page The Central Inventory is corrupted The oraInst.loc file specified is not valid. ./opatch lsinventory Oracle Interim Patch Installer version 12.2.0.1.13 Copyright (c) 2019, Oracle Corporation.  All rights reserved. Oracle Home       : /u01/app/oracle/product/12.1.0.2/home_1 Central Inventory : /home/oracle/oraInventory    from           : /u01/app/oracle/product/12.1.0.2/home_1/oraInst.loc OPatch version    : 12.2.0.1.13 OUI version       : 12.1.0.2.0 Log file location : /u01/app/oracle/product/12.1.0.2/home_1/cfgtoollogs/opatch/opatch2019-10-09_10-12-49AM_1.log LsInventorySession failed: OPatch failed to locate Central Inventory. Possible causes are:     The Central Inventory is corrupted     The oraInst.loc file specified is not valid. OPatch failed with error ...

recovery catalog schema release xxxx is newer than RMAN release

<<Back to Oracle Backup & Recovery Main Page recovery catalog schema release 19.04.00.00. is newer than RMAN release CAUSE The catalog schema version is different from the rman executable version. Version of RMAN client (RMAN executable) displayed when you start RMAN Run the below command as rman catalog schema owner to find the catalog schema version SQL> SELECT * FROM rcver; SOLUTION This information message can be ignored. This is simply an informational message, no action is necessary.  There will be no problem while registering the target database to the recovery catalog, resyncing the recovery catalog, and/or performing backup or recovery.   

Datafiles are mutually inconsistent Oracle Physical Standby

<<Back to Oracle Backup & Recovery Main Page Datafiles are mutually inconsistent Oracle Physical Standby rman target / Recovery Manager: Release 12.1.0.2.0 - Production on Mon Sep 23 11:23:32 2019 Copyright (c) 1982, 2014, Oracle and/or its affiliates.  All rights reserved. connected to target database: ORCLTP (DBID=XXXXX) RMAN> list failure; using target database control file instead of recovery catalog Database Role: PHYSICAL STANDBY List of Database Failures ========================= Failure ID Priority Status    Time Detected Summary ---------- -------- --------- ------------- ------- 142322     HIGH     OPEN      21-SEP-19     Datafiles are mutually inconsistent RMAN>  advise failure; Database Role: PHYSICAL STANDBY List of Database Failures ========================= Failure ID Priority Status    Time Detected Summary -----...