MQSeries.net :: View topic - Managed by DB using raw device

MQSeries.net

Tech Exchange

Education

Certifications

Library

Info Center

SupportPacs

FAQÂ Â

Usergroups

RSS Feed - WebSphere MQ Support

RSS Feed - Message Broker Support

MQSeries.net Forum Index » Workflow Engines - IBM MQ Workflow & Business Process Choreographer » Managed by DB using raw device

Managed by DB using raw device

« View previous topic :: View next topic »

Author

Message

vennela

Posted: Mon Nov 15, 2004 2:06 pm Post subject: Managed by DB using raw device

Jedi Knight

Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India

I am trying to configure workflow server on an AIX machine.
WMQ 5.3 CSD 6
WMQWF 3.5 SP2
DB2 8.1 FP 6

I can create the server by selecting the DB to be
Managed by system (option r in colum 22 of the Installation Guide manual Chapter

Managed by DB (option b in colum 22 of the Installation Guide manual Chapter

But it is giving me an error while selecting th option r.

This is the error that I am getting.

Quote:

FMC33148E DB2 CLI call 'SQLExecDirect(CREATE TEMPORARY TABLESPACE TMP32 PAGESIZE 32 K MANAGED BY DATABASE USING (DEVICE '/dev/rTMP32' 500) BUFFERPOOL FMCBP32)' ended with error: '[IBM][CLI Driver][DB2/6000] SQL0970N The system attempted to write to a read-only file'.
FMC33148E DB2 CLI call 'SQLExecDirect(CREATE TEMPORARY TABLESPACE TMP32 PAGESIZE 32 K MANAGED BY DATABASE USING (DEVICE '/dev/rTMP32' 500) BUFFERPOOL FMCBP32)' ended with error: '[IBM][CLI Driver][DB2/6000] SQL0970N The system attempted to write to a read-only file'.

Anybody configured a RT DB using raw devices?

dsbailey

Posted: Fri Nov 19, 2004 2:17 pm Post subject: Managed by DB using raw device

Novice

Joined: 20 May 2002
Posts: 24

I found some information regarding MQWF runtime dabase and raw devices. This was based off MQWF 3.3.2 and DB2 7.2.1....

how to configure a Workflow database using raw devices:
1. Determine the tablespaces that should be placed on a raw device.
2. Create a volume group containing the devices you intend to use.
3. Create a logical volume for each tablespace you want to be on a raw device. The volume name must be the same as the tablespace, for example for the tablespace ADTTRAIL create a logical volume "ADTTRAIL". This results in a new entry in /dev named rADTTRAIL.
4. Change the ownership of the device /dev/rADTTRAIL to db2inst1:db2iadm1 (or the db admin user/group you are using).
5. Start fmczutil as root user to create a new config.
6. Select 'i' to create the new database.
7. On the prompt "DB2 database layout file" specify a file that does not exist. Then the file will be created and you can modify it later.
8. On the prompt "DB2 database location" enter a valid location (on the database host) for the remaining database files (the ones not stored on raw devices)
9. On the prompt "DB2 container location" accept the default. This will be ignored for all raw devices, but is used for other containers.
10. On the prompt "DB2 log files location" enter a valid location (on the database host) for the log files.
11. On the prompt "Select space management ...: " select "r" for using raw devices.
12. Proceed with the following prompts as needed for your setup.
13. At least select "c ... Create configuration profile for 'XXXX' now"
14. Answer the question "- FMC33502I Do you want to create the Runtime database now?" with N. (NO)
15. Exit fmczutil.

The above creates a layout file (see example below) where the tablespaces are flagged as 'raw device'.

Modify the layout file as follows:

For each tablespace you do not want to be on a raw device you may change the key "ManagedBy=Database" to System or the key "RawDevice=1" to 0.

Using "RawDevice=0" and "ManagedBy=Database" the tablespace will be created in the file <ContainerPath>/<TablespaceName>.
For Example, the following section DEFINITION will create the files below:
/fmcdb/RAWDEV/LIST
/fmcdb/RAWDEV/MODEL
/fmcdb/RAWDEV/STAFF
/fmcdb/RAWDEV/TEMPLATE
/fmcdb/RAWDEV/TOPOLOGY

;*** Tablespace group DEFINITION
[DEFINITION]
ContainerPath=/fmcdb/RAWDEV
ManagedBy=Database
;RawDevice=1 is only valid for ManagedBy=Database
RawDevice=0
;Sizes for tablespaces
LIST=2000
MODEL=5000
STAFF=7000
TEMPLATE=5000
TOPOLOGY=5000

Using "ManagedBy=System" will store the tablespace in the directory specified by "ContainerPath". The RawDevice Key will be ignored.

After you finished your modifications you must ensure that the db2 admin user can read the fmczdblay.ini file.
Now logon with the fmc user or the db2 administrator. (a user id having db2 admin permissions)
Start fmczutil.
Select your perviously configured configuration.
Select 'r' to enter the Runtime Database Commands Menu
Select 'c' to create the database.

----------
I have not tested this.... but maybe it will give you some further direction.

Display posts from previous:

Page 1 of 1

MQSeries.net Forum Index » Workflow Engines - IBM MQ Workflow & Business Process Choreographer » Managed by DB using raw device

Jump to:

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

Protected by Anti-Spam ACP