Carlos,
The segments did grow somewhat since 3.4. They can be even bigger if you
have DRDA linked in. We do in ours to allow access from DB/2 Connect on
the Windows side. Our database machines are 32 meg in the directory. Here
are the values that we are using for DB/2 7.4 shared segments.
ORIGIN SYSNAME BEGPAG ENDPAG
2800000 740RMGR 02800 02A3F
D00000 740ISQL 00D00 00D5F
C00000 740SQLDS 00C00 00D7F
3000000 740XRDS 03000 033DF
Ed Zell
(309) 674-8255 x-107
[EMAIL PROTECTED]
________________________________
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of
Carlos Bodra
Sent: Monday, December 04, 2006 5:21 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject:
Hi!
We are installing DB2 V7.4 and have a -934 error during start up of server
machine unde a z/VM 4.4 Level 0501.
What sounds strange is that if we start server without saved segment support,
no problems occurs.
Our old data base is a SQL version 3.4, so saved segments grows a lot and we
don´t know if this problem is because wrong definition of saved segments (using
vmfsgmap exec)
Since SQL is running in production and these saved segments have original IBM
names, we did need to rename new ones. Bellow is where we put them:
DB2RMGR 01400-02300
DB2ISQL 00B00-00B60
DB2SQLDS 008B0-00A2F
DB2XRDS 01400-0237F
DB2SP03 008B0-0237F --> This is DB Space
Server machine has 128MB memory defined in directory.
Since we guess that DB2 program directory is not complete about how to
generated saved segments, we are trying to get some help and hints from VM-L
gurus.
Thanks a lot for help.
Carlos
São Paulo - Brazil
.
CONFIDENTIAL NOTICE: This communication, including any attachments, is
intended only for the use of the individual or entity to which it is addressed
and contains information which may be confidential. If you are not the
intended recipient, any distribution or copying of this communication is
strictly prohibited. If you have received this communication in error, notify
the sender immediately, delete the communication and destroy all copies. Thank
you for your compliance.
