SQL> srtup pfile=init.ora ORACLE instance started.
Total System Global Area 3226043912 bytes Fixed Size 9172488 bytes Variable Size 2080374784 bytes Database Buffers 1006632960 bytes Redo Buffers 129863680 bytes ORA-01103: database name 'NEWDB' in control file is not 'SALMAN' |
RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of Duplicate Db command at 06/26/2024 05:32:00 RMAN-05501: aborting duplication of target database RMAN-06617: UNTIL TIME (20-JUN-24) is ahead of last NEXT TIME in archived logs (20-JUN-24) |
SQL> create tablespace testtbs blocksize 4k datafile '+DATA' size 2m; create tablespace testtbs blocksize 4k datafile '+DATA' size 2m * ERROR at line 1: ORA-29339: tablespace block size 4096 does not match configured block sizes |
SQL> alter database datafile '+DATA/MYDB/19AF24AD633634AEE0632502F50A727A/DATAFILE/testtbs.5971.1170569741' resize 6m; alter database datafile '+DATA/MYDB/19AF24AD633634AEE0632502F50A727A/DATAFILE/testtbs.5971.1170569741' resize 6m * ERROR at line 1: ORA-03214: File size specified is smaller than minimum required |
RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of Duplicate Db command at 06/26/2024 05:32:00 RMAN-05501: aborting duplication of target database RMAN-06617: UNTIL TIME (20-JUN-24) is ahead of last NEXT TIME in archived logs (20-JUN-24) |
This is a very critical error message that many applications started seeing since 12c. Prior to 12c, PGA of a server process could grow unabatedly. After the advent of PGA_AGGREGATE_LIMIT, PGA usage for all connected sessions could be limited to avoid enormous growth of PGA memory due to bad PL/SQL code (or due to an Oracle bug causing a process memory leak). Whenever total PGA usage by all sessions tries to go beyond the value set in this parameter, ORA-04036 is returned to the session and also logged in the alert log file (and trace file is also generated) . Alert log file could log error message similar to the following.
There could be other reasons for this message to appear while you are trying to execute something in a standby database (or perhaps on primary database), however, in my case, this message was returned when I was trying to create an SQL Tuning Advisor task and wanted to submit for advisor’s recommendations. While doing so, I did not realize that I was actually trying to execute this on physical standby database. Following is the entire error stack that was returned.
SQL> startup pfile=initaux.ora ORA-00371: not enough shared pool memory, should be at least 16341008384 bytes |
Whenever we start an oracle database instance, it requires memory to allocate some memory components of the SGA so that instance could serve the database and database sessions. If we do not specify size of memory components, we might face errors during instance startup. sga_target is the basing parameter to specify before we start an instance and other memory components like shared pool, buffer cache, or log buffer cache are allocated from the memory allocated to SGA.
SQL> alter system set sga_target=4257m; alter system set sga_target=4257m * ERROR at line 1: ORA-02097: parameter cannot be modified because specified value is invalid ORA-56747: invalid value 4463788032 for parameter sga_target; must be smaller than parameter sga_target of the root container |
