New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DBCA operation failed... not sure why, can't seem to view the log :( #16

Closed
s50600822 opened this Issue Jun 20, 2016 · 6 comments

Comments

Projects
None yet
6 participants
@s50600822
s5060@DESKTOP-8VTHH4M MINGW64 ~
$ docker run -d -p 8080:8080 -p 1521:1521 sath89/oracle-12c
09179912ff6e6e08226e9e571415994e2ed60fe7cdc58c0d6b52ee87f0b6fd33

s5060@DESKTOP-8VTHH4M MINGW64 ~
$ docker logs -f 09179912ff6e6e08226e9e571415994e2ed60fe7cdc58c0d6b52ee87f0b6fd33
ls: cannot access /u01/app/oracle/oradata: No such file or directory
Database not initialized. Initializing database.
Starting tnslsnr
Copying database files
1% complete
2% complete
4% complete
DBCA Operation failed.
Look at the log file "/u01/app/oracle/cfgtoollogs/dbca/xe/xe.log" for further details.

s5060@DESKTOP-8VTHH4M MINGW64 ~
$ less /u01/app/oracle/cfgtoollogs/dbca/xe/xe.log
/u01/app/oracle/cfgtoollogs/dbca/xe/xe.log: No such file or directory

s5060@DESKTOP-8VTHH4M MINGW64 ~
@ansgarkroger

This comment has been minimized.

Show comment
Hide comment
@ansgarkroger

ansgarkroger Jun 22, 2016

got the same issue.
copied the log file over using:
docker cp mydockercontainername:/u01/app/oracle/cfgtoollogs/dbca/xe/xe.log .

It shows:

 The specified shared pool size or SGA size "292MB" does not meet the recommended minimum size requirement "331MB". This will make database creation fail. Do you want to continue?

Unique database identifier check passed.

/u01/app/oracle/ has enough space. Required space is 6140 MB , available space is 53851 MB.
File Validations Successful.
Copying database files
DBCA_PROGRESS : 1%
DBCA_PROGRESS : 2%
ORA-00821: Specified value of sga_target 292M is too small, needs to be at least 364M
ORA-01078: failure in processing system parameters

DBCA_PROGRESS : 4%
ORA-01034: ORACLE not available

ORA-01034: ORACLE not available

DBCA_PROGRESS : DBCA Operation failed.

my problem is that I have difficulties investigating further. when I run
docker exec -it a70e80d41c5e sh
I get
rpc error: code = 2 desc = "oci runtime error: exec failed: exit status 1"

got the same issue.
copied the log file over using:
docker cp mydockercontainername:/u01/app/oracle/cfgtoollogs/dbca/xe/xe.log .

It shows:

 The specified shared pool size or SGA size "292MB" does not meet the recommended minimum size requirement "331MB". This will make database creation fail. Do you want to continue?

Unique database identifier check passed.

/u01/app/oracle/ has enough space. Required space is 6140 MB , available space is 53851 MB.
File Validations Successful.
Copying database files
DBCA_PROGRESS : 1%
DBCA_PROGRESS : 2%
ORA-00821: Specified value of sga_target 292M is too small, needs to be at least 364M
ORA-01078: failure in processing system parameters

DBCA_PROGRESS : 4%
ORA-01034: ORACLE not available

ORA-01034: ORACLE not available

DBCA_PROGRESS : DBCA Operation failed.

my problem is that I have difficulties investigating further. when I run
docker exec -it a70e80d41c5e sh
I get
rpc error: code = 2 desc = "oci runtime error: exec failed: exit status 1"

@MaksymBilenko

This comment has been minimized.

Show comment
Hide comment
@MaksymBilenko

MaksymBilenko Jul 7, 2016

Owner

It should be fixed already

Owner

MaksymBilenko commented Jul 7, 2016

It should be fixed already

@nouhouari

This comment has been minimized.

Show comment
Hide comment
@nouhouari

nouhouari Jul 18, 2016

Facing same issue today. What is the fix ?

$ more xe.log
The specified shared pool size or SGA size "297MB" does not meet the recommended minimum size requirement "331MB". This will make database creation fail. Do you want to continue?

Unique database identifier check passed.

/u01/app/oracle/ has enough space. Required space is 6140 MB , available space is 7955 MB.
File Validations Successful.
Copying database files
DBCA_PROGRESS : 1%
DBCA_PROGRESS : 2%
ORA-00821: Specified value of sga_target 300M is too small, needs to be at least 364M
ORA-01078: failure in processing system parameters

DBCA_PROGRESS : 4%
ORA-01034: ORACLE not available

ORA-01034: ORACLE not available

DBCA_PROGRESS : DBCA Operation failed.

****** UPDATE
docker run --shm-size=1024MB -p 1521:1521 -p 8080:8080 sath89/oracle-12c

nouhouari commented Jul 18, 2016

Facing same issue today. What is the fix ?

$ more xe.log
The specified shared pool size or SGA size "297MB" does not meet the recommended minimum size requirement "331MB". This will make database creation fail. Do you want to continue?

Unique database identifier check passed.

/u01/app/oracle/ has enough space. Required space is 6140 MB , available space is 7955 MB.
File Validations Successful.
Copying database files
DBCA_PROGRESS : 1%
DBCA_PROGRESS : 2%
ORA-00821: Specified value of sga_target 300M is too small, needs to be at least 364M
ORA-01078: failure in processing system parameters

DBCA_PROGRESS : 4%
ORA-01034: ORACLE not available

ORA-01034: ORACLE not available

DBCA_PROGRESS : DBCA Operation failed.

****** UPDATE
docker run --shm-size=1024MB -p 1521:1521 -p 8080:8080 sath89/oracle-12c

@ppapaj

This comment has been minimized.

Show comment
Hide comment
@ppapaj

ppapaj Jul 20, 2016

I solved the problem simply by adding RAM to Docker VM. I increased it from 1024M to 2048M.

ppapaj commented Jul 20, 2016

I solved the problem simply by adding RAM to Docker VM. I increased it from 1024M to 2048M.

@geeeeeeeeek

This comment has been minimized.

Show comment
Hide comment
@geeeeeeeeek

geeeeeeeeek Aug 22, 2016

@MaksymBilenko This is a common issue when building your image. @ppapaj 's answer is exactly to the point and I think you should put it into your README to highlight the issue.

Quick commands:

docker-machine stop
VBoxManage modifyvm default --memory 4096
docker-machine start

geeeeeeeeek commented Aug 22, 2016

@MaksymBilenko This is a common issue when building your image. @ppapaj 's answer is exactly to the point and I think you should put it into your README to highlight the issue.

Quick commands:

docker-machine stop
VBoxManage modifyvm default --memory 4096
docker-machine start
@MaksymBilenko

This comment has been minimized.

Show comment
Hide comment
@MaksymBilenko

MaksymBilenko Aug 22, 2016

Owner

Thank you guys,
I've added link to this issue at the README.md
Cheers

Owner

MaksymBilenko commented Aug 22, 2016

Thank you guys,
I've added link to this issue at the README.md
Cheers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment