on 06-26-2015 6:10 PM
Hi Max DB gurus,
We have two Productive Instances of Max DB database ,version 7.7.04.28
which are used are repository for content server . There is a
performance
bottleneck that when we add a new data volume of it using Database
Studio(Database Manager 7.6) it takes quite long time. Even adding a
data
volume of 20GB takes more than an hour and it often fails and then we
have to readd it . Does this behaviour depend upon any kernel paramter
. Please suggest through which parameter change
it can be reduced.
The operating system version is Windows Server 2008 R2
Regards,
Bhupesh Shukla
This is rather an OS or disk related problem, but very unlikely caused by MaxDB.
When a Data Volume is added, MaxDB creates a file, writes some metadata into that Volume and fills the rest with hex(00) to ensure that the complete file can be written to.
If formatting is slow, then you need to check your IO system. More than an hour for just 20 GB is definitely too long and should be investigated.
If adding a a Volume aborts, then have a look into the MaxDB KnlMsg log file. There should be a MaxDB error code plus an OS error code if formatting stopped due to an OS error.
This is not related to your current problem, but please consider patching your MaxDB version 7.7.04.28 to the latest 7.7.07.xx release.
Thorsten
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Bhupesh,
How much hours it takes to add data volume?
By the way the adding data volume will cause the existing data to be re-dispatched, which takes time. However the mainly time cost will be IO.
Best regards,
James
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Bhupesh,
1) Do you face the same issue while adding a data volume by using the CLI command lines?
2) Have you tried to check the state of the x_cons for this host?
run the following command during the Data file creation:
x_cons <SID> show active
change <SID> for your database name.
It might give some background of what the server is doing.
3) Do you have the database analyzer data for this time? You can try to check whether there is a I/O bottleneck that is affecting your system. We would need this to determine whether the cause is hardware or some error in the MaxDB Kernel.
Regards,
Luis Darui
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
92 | |
11 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.