on 05-20-2010 9:19 AM
Hi,
When installing ECC 5.0 IDES on Wins 2k3 x64 & MaxDB 7.5. At phase Database Instance Installation - sub-phase MaxDB Database Installation, I get error as following:
-
CJS-00030 Assertion failed: in
function InstallationScript_334() {
var installer = new Installer();
var kdb = new KeyDB();
var context = new Context();
var gui = new Gui();
-
Checking sapinst_dev.log:
SDB: ERROR EXECUTING PARAM CHECK! CHECK THE XCMDOUT.LOG!
Checking XCMDOUT.LOG:
-
> Subprocess starts at 20100521112002
Execute Command : d:\sapdb\programs\pgm\dbmcli.exe -n Bitexco -d GCS -u CONTROL,********
Execute Session Command : param_startsession
Execute Session Command : param_checkall
Execute Session Command : exit
> Subprocess stops at 20100521112003
OK
ERR
-24973,ERR_XPCHECK: param check failure/request
DATA_VOLUME_SIZE_0001 Constraint
20480000
-
It seems that data volume is too big, but I don't know how to change it.
Regards,
Toan Do
Hello,
Please post the output of the following commands, run them on the database server:
d:\sapdb\programs\pgm\dbmcli.exe -n Bitexco -d GCS -u CONTROL,<pwd>
<enter>
dbmcli on Bitexco>param_getvolsall
<enter>
dbmcli on Bitexco>param_directget VOLUMENO_BIT_COUNT
<enter>
dbmcli on Bitexco>param_getexplain VOLUMENO_BIT_COUNT
<enter>
dbmcli on Bitexco>param_directput DATA_VOLUME_SIZE_0001 16000000
<enter>
dbmcli on Bitexco>param_checkall
<enter>
dbmcli on Bitexco>exit
Thank you and best regards, Natalia Khlopina
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Here's outputs:
dbmcli.exe on Bitexco : GCS>param_getvolsall
OK
LOG_MIRRORED NO
MAXLOGVOLUMES 1
MAXDATAVOLUMES 1
LOG_VOLUME_NAME_001 128000 F D:\sapdb\GCS\saplog\DISKL001
DATA_VOLUME_NAME_0001 20480000 F D:\sapdb\GCS\sapdata\DISKD0001
dbmcli.exe on Bitexco : GCS>param_directget VOLUMENO_BIT_COUNT
OK
VOLUMENO_BIT_COUNT 8
dbmcli.exe on Bitexco : GCS>param_getexplain VOLUMENO_BIT_COUNT
OK
Number of bits in a four byte converter block address
reserved for the logical devive number which identifies
the data volumes. The rest of the four byte block
address is used for the device offset.
The greater the VOLUMENO_BIT_COUNT the more data volume
could be managed.
Note that this reduces the capacity of usable data volumes!
This value is not changeable within the lifetime of the data
base without making a recovery.
Example: If the PAGESIZE is set to 8 KB and VOLUMENO_BIT_COUNT
is set to the default value of 8 than the data base is able
to manage as far as 256 data volumes, whereby the maximum
capacity of one data volume is 128 GB.
If the VOLUMENO_BIT_COUNT is set to 6 the data base is able
to manage up to 64 data volumes, whereby the capacity of
one data volume is 512 GB.
The lower and upper limits are:
6 <= VOLUMENO_BIT_COUNT <= 12
dbmcli.exe on Bitexco : GCS>param_directput DATA_VOLUME_SIZE_0001 16000000
OK
dbmcli.exe on Bitexco : GCS>param_checkall
OK
Regards,
Yes, thanks.
Command "param_directput DATA_VOLUME_SIZE_0001 16000000" fixes the problem.
But I wonder why this happened though I had set 160000 MB (default) for data volume before. Then the installer said it is 20480000 & stopped. Then when setting it 16000000 makes the installer running again.
Regards,
Hello,
1. You posted question:
u201CIt seems that data volume is too big, but I don't know how to change it.u201D
I gave you answer in my last replay & you confirmed that you was able to continue the Installation.
2. Now you posted the issue:
u201CBut I wonder why this happened though I had set 160000 MB (default) for data volume before.
Then the installer said it is 20480000 & stopped.u201D
Please create the SAP message to the component u201CBC-DB-SDB-INSu201D, if you had set
160000 MB for data volume during the MAXDB database installation.
Thank you and best regards, Natalia Khlopina
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.