abhisbyk
commented
2 years ago @KentTwilio
I see that the Failed to get D-Bus connection: Operation not permitted error is not responsible for subsequent failures. When I built the image on my dev-machine this message was there in the build log, but did not cause any issues after that.
Further, I followed the steps you executed, but was not able to replicate the error you got. My database setup was successful. My terminal output is as follows:
[oracle@3614e5f7ea19 ~]$ /opt/oracle/runOracle.sh
ORACLE EDITION: ENTERPRISE
LSNRCTL for Linux: Version 19.0.0.0.0 - Production on 02-MAR-2022 04:53:47
Copyright (c) 1991, 2019, Oracle. All rights reserved.
Starting /opt/oracle/product/19c/dbhome_1/bin/tnslsnr: please wait...
TNSLSNR for Linux: Version 19.0.0.0.0 - Production
System parameter file is /opt/oracle/product/19c/dbhome_1/network/admin/listener.ora
Log messages written to /opt/oracle/diag/tnslsnr/3614e5f7ea19/listener/alert/log.xml
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1)))
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=0.0.0.0)(PORT=1521)))
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1)))
STATUS of the LISTENER
------------------------
Alias LISTENER
Version TNSLSNR for Linux: Version 19.0.0.0.0 - Production
Start Date 02-MAR-2022 04:53:48
Uptime 0 days 0 hr. 0 min. 0 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /opt/oracle/product/19c/dbhome_1/network/admin/listener.ora
Listener Log File /opt/oracle/diag/tnslsnr/3614e5f7ea19/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=0.0.0.0)(PORT=1521)))
The listener supports no services
The command completed successfully
Prepare for db operation
8% complete
Copying database files
31% complete
Creating and starting Oracle instance
32% complete
36% complete
40% complete
43% complete
46% complete
Completing Database Creation
51% complete
54% complete
Creating Pluggable Databases
58% complete
77% complete
Executing Post Configuration Actions
100% complete
Database creation complete. For details check the logfiles at:
/opt/oracle/cfgtoollogs/dbca/ORCLCDB.
Database Information:
Global Database Name:ORCLCDB
System Identifier(SID):ORCLCDB
Look at the log file "/opt/oracle/cfgtoollogs/dbca/ORCLCDB/ORCLCDB.log" for further details.
SQL*Plus: Release 19.0.0.0.0 - Production on Wed Mar 2 05:13:38 2022
Version 19.3.0.0.0
Copyright (c) 1982, 2019, Oracle. All rights reserved.
Connected to:
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.3.0.0.0
SQL>
System altered.
SQL>
System altered.
SQL>
Pluggable database altered.
SQL>
PL/SQL procedure successfully completed.
SQL> SQL>
Session altered.
SQL>
User created.
SQL>
Grant succeeded.
SQL>
Grant succeeded.
SQL>
Grant succeeded.
SQL>
User altered.
SQL> SQL> Disconnected from Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.3.0.0.0
The Oracle base remains unchanged with value /opt/oracle
Executing user defined scripts
/opt/oracle/runUserScripts.sh: running /opt/oracle/scripts/extensions/setup/savePatchSummary.sh
/opt/oracle/runUserScripts.sh: running /opt/oracle/scripts/extensions/setup/swapLocks.sh
[2022:03:02 05:13:44]: Acquiring lock .ORCLCDB.exist_lck with heartbeat 30 secs
[2022:03:02 05:13:44]: Lock acquired
[2022:03:02 05:13:44]: Starting heartbeat
[2022:03:02 05:13:44]: Lock held .ORCLCDB.exist_lck
DONE: Executing user defined scripts
The Oracle base remains unchanged with value /opt/oracle
#########################
DATABASE IS READY TO USE!
#########################
Executing user defined scripts
/opt/oracle/runUserScripts.sh: running /opt/oracle/scripts/extensions/startup/runDatapatch.sh
Datafiles are already patched. Skipping datapatch run.I am not sure what is causing the DB to fail. The command to build the image is also fine. So, for further debugging, can you do the following things:
- Run the container with
runOracle.shscript running automatically and see if the same error persists or not (Is there any specific reason why you want to bypass this and run it manually ?). - Try to use the named volume option of docker. For eg.
docker run -d -t -v vol1:/opt/oracle/oradata <image>and see if the error persists. - If the error is still there, please attach dbca logs from the container. The location of the logs will be in the directory
/opt/oracle/cfgtoollogs/dbca/ORCLCDB. Please zip the contents of this directory and attach.
Also, please note that there is no need to run the following commands explicitly inside the container as root user
1. /opt/oracle/oraInventory/orainstRoot.sh
2. /opt/oracle/product/19c/dbhome_1/root.shThese commands are executed in an intermediate container while building the image itself.
Thanks
segkent
balaji-krishnan
1aal
scscgit
I am trying to build an Oracle 19c image but I continually get the same error which may or may not be related to a subsequent failure of the container to create a database and start.
I am running this command-line to build the image.
./buildContainerImage.sh -v 19.3.0 -t oracle19c-ee:latest -e -o '--build-arg SLIMMING=false'During the build process I see this error occur. It always occurs in the same place. I have tried building the image in an Ubuntu 20 VM and in OSX against Docker Desktop.
The image otherwise seems to be created perfectly normally.
I then run the container with the following to prevent the auto-run
runOracle.sh:docker run -d --rm --name oracle19ee oracle19ee:latest bash -c "sleep infinity"I get a terminal into the container as root with:
docker exec -it -u root oracle19ee bashAnd run these commands as instructed by the build process:
Then I exit the bash terminal and execute this to get back in as user
oracle:docker exec -it oracle19ee bashAnd run
/opt/oracle/runOracle.sh.That runs for about 7 minutes and then spits this out:
No database is ever created and the container remains in an unhealthy state.
I've run these commands dozens of times trying various permutations over the past few days and I get the same results every time.
I also try setting the following env variables to various values with the same results.
Am I doing something wrong here or is there a problem with the image build process?