For what reason background process SMCO falls at creation of a DB in 12.1.0.2?

Question

linux

the situation is like this. I'm using a Docker image (of Oracla).
Because db specific rewrote the dockerfile for itself, where the db is created by scripts using the init.ora file.
Previously, it had the MEMORY_TARGET=2200m setting and everything worked. Now we need to increase the memory. Increased to 5120m.

Piece of alertlog

Thu Jul 05 09:59:28 2018
Dump of system resources acquired for SHARED GLOBAL AREA (SGA) Thu

Jul 05
09:59:28
2018
soft) limit = 64K
Thu Jul 05 09:59:28 2018
Expected per process system memlock (soft) limit to lock
SHARED GLOBAL AREA (SGA) into memory: 5120M
Thu Jul 05 09:59:28 2018
Available system pagesizes:
4K, 2048K
Thu Jul 05 09:59:28 2018
Supported system pagesize(s):
Thu Jul 05 09:59:28 2018
PAGESIZE AVAILABLE_PAGES EXPECTED_PAGES ALLOCATED_PAGES ERROR(s)
Thu Jul 05 09:59:28 2018
4K Configured 1310727 1310727 NONE
Thu Jul 05 09:59:28 2018
Reason for not supporting certain system pagesizes:
Thu Jul 05 09:59:28 2018
2048K - Dynamic allocate and free memory regions
Thu Jul 05 09:59:28 2018
RECOMMENDATION:
Thu Jul 05 09:59:28 2018
1. Increase per process memlock (soft) limit to at least 5120MB
to lock 100% of SHARED GLOBAL AREA (SGA) pages into physical memory
Thu Jul 05 09:59:28 2018

inexplicably

Per process system memlock (soft) limit = 64K

After all, the oracle preinstall sets its values ​​in /etc/security/limits.d/oracle-rdbms-server-12cR1-preinstall.conf

oracle soft memlock 134217728

and ulimit -l issues under the oracle user

# ulimit -l
64

Oh well, it used to work anyway.

When creating the database, I get the following error:

SMON: enabling tx recovery
Starting background process SMCO
Process SMCO died, see its trace file
Thu Jul 05
10:00:38
2018 00443: background process "SMCO" did not start
Starting background process SMCO
Process SMCO died, see its trace file
Thu Jul 05 10:00:39 2018
Errors in file /u01/oracle/diag/rdbms/testdb/TESTDB/trace/TESTDB_smon_3038 .trc:
ORA-00443: background process "SMCO" did not start
Thu Jul 05 10:00:41 2018
Successfully created internal service SYS$BACKGROUND at open
Successfully created internal service SYS$USERS at open
Starting background process SMCO
Process SMCO died, see its trace file
Thu Jul 05 10:00:42 2018
Errors in file /u01/oracle/diag/rdbms/testdb/TESTDB/trace/TESTDB_ora_3053.trc:
ORA-00443: background process "SMCO" did not start
replication_dependency_tracking turned off (no async multimaster replication found)
Process m000 died, see its trace file
Starting background process AQPC
Process AQPC died, see its trace file
Thu Jul 05 10:00:44 2018
Errors in file /u01/oracle/diag/ rdbms/testdb/TESTDB/trace/TESTDB_ora_3053.trc:
ORA-00443: background process "AQPC" did not start
Thu Jul 05 10:00:44 2018
Errors in file /u01/oracle/diag/rdbms/testdb/TESTDB/trace /TESTDB_ora_3053.trc:
ORA-01501: CREATE DATABASE failed
ORA-00450: background process 'AQPC' did not start
ORA-00443: background process "AQPC" did not start
Error 450 happened during database creation, shutting down database
USER (ospid: 3053): terminating the instance due to error 450

in smco trace the following

-------------------------------------------------- -----------------------------
Trace Bucket Dump Begin: default bucket for process 17 (osid: 3038, SMON)
TIME(*= approx):SEQ:COMPONENT:[email protected]:FUNCTION:SECT/DUMP: [EVENT#:PID:SID] DATA
------------------------ -------------------------------------------------- -----
2018-07-05 10:00:37.187675 :8000C3FF:db_trace:[email protected]:ksbs1p_real(): [10254:17:395] KSBS1P: process SMON trying to start background SMCO
2018-07- 05 10:00:37.187689 :8000C400:db_trace:[email protected]:ksb_spawn_cleanup(): [10254:17:395] KSB_SPAWN_CLEANUP: Process (SMCO) prior PSO cleaned up
2018-07-05 10:00:38.184729 :8000C47 :db_trace:[email protected]:ksbs1p_real(): [10254:17:395] KSBS1P: out of loop: process did not start
-------------------------------------------------- -----------------------------
Trace Bucket Dump End: default bucket for process 17 (osid: 3038, SMON)
ORA-00443: background process "SMCO" did not start

*** 2018-07-05 10:00:39.214
----------------------------- --------------------------------------------------
Trace Bucket Dump Begin: default bucket for process 17 (osid: 3038, SMON)
TIME(*=approx):SEQ:COMPONENT:[email protected]:FUNCTION:SECT/DUMP: [EVENT#:PID:SID] DATA
--- -------------------------------------------------- --------------------------
2018-07-05 10:00:37.187675 :8000C3FF:db_trace:[email protected]:ksbs1p_real() : [10254:17:395] KSBS1P: process SMON trying to start background SMCO
2018-07-05 10:00:37.187689 :8000C400:db_trace:[email protected]:ksb_spawn_cleanup(): [10254:17:395] KSB_SPAWN_CLEANUP: Process (SMCO) prior PSO cleaned up
2018-07-05 10:00 :38.184729 :8000C467:db_trace:[email protected]:ksbs1p_real(): [10254:17:395] KSBS1P: out of loop: process did not start
2018-07-05 10:00:38.215303 :8000C469:db_trace:ksb [email protected]:ksbs1p_real(): [10254:17:395] KSBS1P: process SMON trying to start background SMCO
2018-07-05 10:00:38.215306 :8000C46A:db_trace:[email protected]:ksb_spawn_cleanup(): [10254:17:395] KSB_SPAWN_CLEANUP: Process (SMCO) prior PSO cleaned up
2018-07-05 10:00:39.214635 :8000C4D3:db_trace:[email protected]:ksbs1p_real(): [10254:17:395] KSBS1P : out of loop: process did not start
----------------------------------------- --------------------------------------
Trace Bucket Dump End: default bucket for process 17 (osid: 3038, SMON)
ORA-00443: background process "SMCO" did not start

Further, for the sake of interest, I changed the value in init.ora to the value from one of our test environments, although there are also production environments where the memtarget and sga parameters are much larger than 5GB

###########################################
# Miscellaneous
###########################################
compatible=12.1.0.2.0
diagnostic_dest=/u01/oracle
#memory_target=5296m
sga_target=3360m
pga_aggregate_target=1120m

ATTENTION!!!!! Everything is OK, the database is created without errors. So the question is, does anyone know what causes this behavior? Maybe somewhere there is a setting that is less than the memory_target value I set?

Thanks in advance.

Answer 1

I wonder if the issue was resolved in the end?
It is generally not recommended to use memory_target in combat. Including because of such jokes.
What df -h says | grep shm? It should fit memory_max_target
https://oracle-base.com/articles/11g/automatic-mem...