Closed petekaras closed 9 years ago
PS: I'm using instructions at https://registry.hub.docker.com/u/angoca/db2-instance/.
Which host OS and docker versions are you using? Can you give me the output of the /tmp/db2isetup.log file? I would like to identify the error you are facing.
The right output in a brand-new Ubuntu 14.04 in AWS is like that:
root@a990707e40fe:/tmp/db2_conf# ./createInstance
The execution completed successfully.
For more information see the DB2 installation log at "/tmp/db2isetup.log".
SQL1063N DB2START processing was successful.
db2inst1@a990707e40fe:~$ cat /tmp/db2isetup.log
DB2 Setup log file started at: Fri Jan 09 14:57:42 2015 UTC
============================================================
Operating system information: Linux 3.13.0-36-generic.#63-Ubuntu SMP Wed Sep 3 21:30:07 UTC 2014 x86_64
WARNING: Notification SMTP server has not been specified. Notifications cannot
...
Hi, Thanks for responding so quickly. I'm running ubuntu 14.04 LTS 64 bit running on VMware workstation. /tmp/db2isetup.log is:
DB2 Setup log file started at: Fri Jan 09 13:59:59 2015 UTC
============================================================
Operating system information: Linux 3.13.0-30-generic.#54-Ubuntu SMP Mon Jun 9 22:45:01 UTC 2014 x86_64
WARNING: Notification SMTP server has not been specified. Notifications cannot
be sent to contacts in your contact list until this is specified. For more
information see the DB2 administration documentation.
New instances:
Instance name: db2inst1
FCM port range: 60000-60003
TCP/IP configuration:
Service name: db2c_db2inst1
Port number: 50000
Instance user information:
User name: db2inst1
UID: 501
Group name: db2grp1
GID: 501
Home directory: /home/db2inst1
Fenced user information:
User name: db2fenc1
UID: 601
Group name: db2fenc1
GID: 601
Home directory: /home/db2fenc1
Setting default global profile registry variables :.......Success
Initializing instance list :.......Success
The instance "db2inst1" has been created successfully.
The value "SVCENAME=db2c_db2inst1" was set in the DBM CFG file for the
"db2inst1" instance.
The value "DB2AUTOSTART=NO" was set in the Profile Registry for the "db2inst1"
instance.
Configuring DB2 instances :.......Success
Updating global profile registry :.......Success
Post-installation instructions
-------------------------------
Required steps:
You can connect to the DB2 instance "db2inst1" using the port number "50000". Record it for future reference.
Start using the DB2 product using a valid user ID such as the DB2 instance owner's ID "db2inst1".
Optional steps:
To validate your installation files, instance, and database functionality, run the Validation Tool, /opt/ibm/db2/V10.5/bin/db2val. For more information, see "db2val" in the DB2 Information Center.
Verify that you have access to the DB2 Information Center based on the choices you made during this installation. If you performed a typical or a compact installation, verify that you can access the IBM Web site using the internet. If you performed a custom installation, verify that you can access the DB2 Information Center location specified during the installation.
Ensure that you have the correct license entitlements for DB2 products and features installed on this machine. Each DB2 product or feature comes with a license certificate file (also referred to as a license key) that is distributed on an Activation CD, which also includes instructions for applying the license file. If you purchased a base DB2 product, as well as, separately priced features, you might need to install more than one license certificate. The Activation CD for your product or feature can be downloaded from Passport Advantage if it is not part of the physical media pack you received from IBM. For more information about licensing, search the Information Center (http://publib.boulder.ibm.com/infocenter/db2luw/v10r5/index.jsp) using terms such as "license compliance", "licensing" or "db2licm".
To use your DB2 database product, you must have a valid license. For information about obtaining and applying DB2 license files, see http://pic.dhe.ibm.com/infocenter/db2luw/v10r5/topic/com.ibm.db2.luw.qb.server.doc/doc/c0061199.html.
DB2 Setup log file finished at: Fri Jan 09 14:00:13 2015 UTC
============================================================
All looks good. I've run the db2val, and all passes even though when I look at the log for this validation script, db2start and db2stop is failing:
Installation file validation for the DB2 copy installed at "/opt/ibm/db2/V10.5" starts.
Task 1: Validating Installation file sets.
Status 1 : Success
Task 2: Validating embedded runtime path for DB2 executables and libraries.
Status 2 : Success
Task 3: Validating the accessibility to the installation path.
Status 3 : Success
Task 4: Validating the accessibility to the /etc/services file.
Status 4 : Success
DBI1335I Installation file validation for the DB2 copy installed at
/opt/ibm/db2/V10.5 was successful.
Installation file validation for the DB2 copy installed at "/opt/ibm/db2/V10.5" ends.
Instance validation for "db2inst1" starts.
Task 5: Validating symbolic links in the instance directory.
Status 5 : Success
Task 6: Validating instance file ownership and permission.
Status 6 : Success
Task 7: Validating the accessibility to the /etc/services file.
Status 7 : Success
Task 8: Starting DB2 instance "db2inst1".
SQL1042C An unexpected system error occurred.
Status 8 : Success
DBI1339I The instance validation for the instance db2inst1 was
successful.
Instance validation for "db2inst1" ends.
Task 9: Stopping DB2 instance "db2inst1".
SQL1032N No start database manager command was issued.
Status 9 : Success
DBI1343I The db2val command completed successfully. For details, see
the log file /tmp/db2val-150109_173620.log.
Let me know what you think ? Thanks for your help, Peter
The instance creation seems ok. Let me see the the db2diag.log. Just show me the error messages, because this file could be big.
cat /home/db2inst1/sqllib/db2dump/db2diag.log
Do you have enough space in the host machine?
I've got 50GB space allocated to the host VM. Here are 3 error messages. I think These ones repeat themselves in the log each time I try to start:
2015-01-09-14.00.13.907990+000 E7234E1026 LEVEL: Error (OS)
PID : 7566 TID : 140251656570752 PROC : db2star2
INSTANCE: db2inst1 NODE : 000
HOSTNAME: 5a5150c2bf17
FUNCTION: DB2 UDB, oper system services, sqloopenp, probe:80
MESSAGE : ZRC=0x870F0002=-2029060094=SQLO_BPSE "Debug logic error detected"
DIA8501C A buffer pool logic error has occurred.
CALLED : OS, -, open OSERR: EINVAL (22)
DATA #1 : Codepath, 8 bytes
5:11:18:20:24:40
DATA #2 : File name, 55 bytes
/home/db2inst1/sqllib/ctrlha/.db2.000.5a5150c2bf17.pgrp
DATA #3 : SQO Open File Options, PD_TYPE_SQO_FILE_OPEN_OPTIONS, 4 bytes
SQLO_CRTREV, SQLO_READWRITE, SQLO_SHAREWRITE, SQLO_FORCE_NON_BUFFERED, SQLO_WRITETHRU, SQLO_SECURE
DATA #4 : Hex integer, 4 bytes
0x000001B4
DATA #5 : signed integer, 4 bytes
0
DATA #6 : Hex integer, 4 bytes
0x00004000
DATA #7 : String, 105 bytes
Search for ossError*Analysis probe point after this log entry for further
self-diagnosis of this problem.
2015-01-09-17.36.44.221057+000 E28319E1473 LEVEL: Severe
PID : 18081 TID : 140527909803904 PROC : db2star2
INSTANCE: db2inst1 NODE : 000
HOSTNAME: 5a5150c2bf17
FUNCTION: DB2 UDB, oper system services, sqloCreatePGRPFileInternal, probe:960
MESSAGE : ZRC=0x870F0002=-2029060094=SQLO_BPSE "Debug logic error detected"
DIA8501C A buffer pool logic error has occurred.
DATA #1 : String, 34 bytes
Error openning process group file.
DATA #2 : SQLHA Mirrored File Pair Structure, PD_TYPE_SQLHA_MIRROR_IO, 8280 bytes
mirrorIO->left.path: /home/db2inst1/sqllib/ctrlha/.db2.000.5a5150c2bf17.pgrp
mirrorIO->left.handle:0x00007FFF7535F598 : FFFF FFFF 0001 0002 ........
/home/db2inst1/sqllib/ctrlha/.db2.000.5a5150c2bf17.pgrp->state: CLOSED
/home/db2inst1/sqllib/ctrlha/.db2.000.5a5150c2bf17.pgrp->state: UNLOCKED
/home/db2inst1/sqllib/ctrlha/.db2.000.5a5150c2bf17.pgrp->state: BAD
mirrorIO->right.path: /home/db2inst1/sqllib/ctrlhamirror/.db2.000.5a5150c2bf17.pgrp.mirror
mirrorIO->right.handle:0x00007FFF753605C0 : FFFF FFFF 0001 0002 ........
/home/db2inst1/sqllib/ctrlhamirror/.db2.000.5a5150c2bf17.pgrp.mirror->state: CLOSED
/home/db2inst1/sqllib/ctrlhamirror/.db2.000.5a5150c2bf17.pgrp.mirror->state: UNLOCKED
/home/db2inst1/sqllib/ctrlhamirror/.db2.000.5a5150c2bf17.pgrp.mirror->state: BAD
File Open Options: 0x00007FFF753605E0 : 0000 0000 0000 0000 ........
2015-01-09-17.36.44.221395+000 E29793E477 LEVEL: Severe
PID : 18081 TID : 140527909803904 PROC : db2star2
INSTANCE: db2inst1 NODE : 000
HOSTNAME: 5a5150c2bf17
FUNCTION: DB2 UDB, oper system services, sqloCreatePGRPFile, probe:1115
MESSAGE : ZRC=0x870F0002=-2029060094=SQLO_BPSE "Debug logic error detected"
DIA8501C A buffer pool logic error has occurred.
DATA #1 : String, 41 bytes
Error to create GRouP file on local path.
It seems that the bufferpool creation needs to create a file, something like a lock, but it fails.
Please try to run the image with a local volume:
sudo mkdir /db2
sudo docker run -i -t --privileged=true --name="db2inst1" -p 50000:50000 -v /db2:/home angoca/db2-instance
You need to create a local directory in the host where the instances will be stored. Please let me know if this changes something.
Also, please try to run the instance that I created: angoca/db2inst1
sudo docker run -i -t --privileged=true --name="db2inst1" -p 50000:50000 angoca/db2inst1
That worked great. Thanks for your help with this. Hope to put this instance to good use in our testing effort. DB2 is such a pain to install on multiple test machines, its going to be great to run this all in Docker. Thanks again for your help, Peter
Nice to hear that. If you have any problem, or you want to propose more features, please write here a feature.
Hi, I'm just running your docker image for the first time. The createInstance script runs db2isetup fine, but then the db2start command fails. I've logged at the /tmp/db2isetup.log and there is no indication of failure there. Wondered if you could give me any clues ? Thanks for your help, Peter
sudo docker run -i -t --privileged=true --name="db2inst1" -p 50000:50000 angoca/db2-instance root@5a5150c2bf17:/tmp/db2_conf# ./createInstance The execution completed successfully.
For more information see the DB2 installation log at "/tmp/db2isetup.log". SQL1042C An unexpected system error occurred.