Hi,
Daniel Dittmar said i should suggest you to scan the mailing list for that, but
maybe you may find this answer more helpfull...
$ dbmcli -R $INSTROOT db_create xyz dbm,dbm
OK
$ dbmcli -d xyz -u dbm,dbm
dbmcli on xyz>param_startsession
OK
CAREFUL param_init only needed once!!!!!!
---
dbmcli on xyz>param_init
OK
CAREFUL param_init only needed once!!!!!!
---
dbmcli on xyz>param_put MAXBACKUPDEVS 10
OK
---
dbmcli on xyz>param_checkall
OK
---
dbmcli on xyz>param_commitsession
OK
---
dbmcli on xyz>quit
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>><
If you forget 'param_init'
$ dbmcli -R $INSTROOT db_create xyz dbm,dbm
OK
$ dbmcli -d xyz -u dbm,dbm
dbmcli on xyz>param_startsession
OK
---
dbmcli on xyz>param_put MAXBACKUPDEVS 10
OK
---
dbmcli on xyz>param_checkall
ERR -24973,ERR_XPCHECK: param check failure/request
CONTROLUSERID Mandatory
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>><
If you forget 'param_checkall'
$ dbmcli -R $INSTROOT db_create xyz dbm,dbm
OK
$ dbmcli -d xyz -u dbm,dbm
dbmcli on xyz>param_startsession
OK
---
dbmcli on xyz>param_put MAXBACKUPDEVS 10
OK
---
dbmcli on xyz>param_commitsession
ERR
-24973,ERR_XPCHECK: param check failure/request
KERNELVERSION Unknown
'param_checkall' writes the content of the new parameter file. If it is forgotten, the
param_commitsession reads an empty file missing the 'KERNELVERSION' which is expected
as first parameter.
As Uwe mentioned, the parameter file is valid with the next start of the database.
CU
jrg
> -----Original Message-----
> From: Krishna, Tupurani Ravi (STSD) [mailto:[EMAIL PROTECTED]
> Sent: Montag, 17. Mai 2004 16:06
> To: Mensing, Joerg
> Subject: RE: problem in bringing up an instance to admin state
>
>
>
> Hi George,
>
>
> The following below is the error I got when used
> param_commitsession....
>
>
> ./dbmcli on xyz>param_commitsession
> ERR
> -24973,ERR_XPCHECK: param check failure/request
> KERNELVERSION Unknown
> KERNEL 7.4.3 BUILD 032-121-068-842
>
>
> ---
>
> Ravi
>
>
> -----Original Message-----
> From: Mensing, Joerg [mailto:[EMAIL PROTECTED]
> Sent: Monday, May 17, 2004 7:32 PM
> To: Krishna, Tupurani Ravi (STSD)
> Subject: RE: problem in bringing up an instance to admin state
>
>
> Hi,
>
> you asked this one week ago. And you were asked by
> Jean-Michel Oltra to
> use param_commitsession
> Did you use it? Why not / what happened then?
> CU
> jrg
>
>
> > -----Original Message-----
> > From: Krishna, Tupurani Ravi (STSD) [mailto:[EMAIL PROTECTED]
> > Sent: Montag, 17. Mai 2004 15:52
> > To: Mensing, Joerg
> > Subject: RE: problem in bringing up an instance to admin state
> >
> >
> >
> >
> > Hi Mensing,
> >
> > How're u? I have a small problem with sapdb. I'm
> mailing u
> > with a hope that I can find a solution to this. I'm trying
> to set the
> > parameter value of MAXBACKUPDEVS. The current value is 2. I want to
> > set it to 10. when I have given the command
> >
> > ./dbmcli on xyz>param_startsession
> > OK
> >
> > ---
> > ./dbmcli on xyz>param_put MAXBACKUPDEVS 10
> > OK
> >
> > ---
> >
> > It is changing successfully but unable to commit it
> once I exit
>
> > and login to the database instance. So please let me know
> what to do
> > to commit the value to the parameter MAXBACKUPDEVS. Please
> do let me
> > know if u need any more information....
> >
> >
> > Regards
> > Ravi
> >
> > -----Original Message-----
> > From: Mensing, Joerg [mailto:[EMAIL PROTECTED]
> > Sent: Tuesday, May 04, 2004 4:46 PM
> > To: Krishna, Tupurani Ravi (STSD); [EMAIL PROTECTED]
> > Subject: RE: problem in bringing up an instance to admin state
> >
> >
> > Hi,
> >
> > > -----Original Message-----
> > > From: Krishna, Tupurani Ravi (STSD) [mailto:[EMAIL PROTECTED]
> > > Sent: Dienstag, 4. Mai 2004 12:37
> > > To: [EMAIL PROTECTED]
> > > Subject: problem in bringing up an instance to admin state
> > >
> > >
> > >
> > >
> > >
> > > Hi,
> > >
> > > I have installed SAPDB 64 bit
> > > (sapdb-all-hpux-64bit-hppa-7_4_3_31) on HPUX 11.11 64 bit
> > version. I
> > > have started the x_server. After that i have given the following
> > > commands to create an instance test
> > >
> > > # ./dbmcli db_create -s test dbm,dbm root,data*pr0
> > > OK
> >
> > i would try a different user. Database under 'root' account are
> > problematic ...
> >
> > >
> > > # ./dbmcli -d test -u dbm,dbm
> > > ./dbmcli on test>param_startsession
> > > OK
> > >
> > > ---
> > > ./dbmcli on test>param_init
> > > OK
> > >
> > > ---
> > > ./dbmcli on test>param_put MAXUSERTASKS 20
> > > OK
> > >
> > > ---
> > > ./dbmcli on test>param_checkall
> > > OK
> > >
> > > ---
> > > ./dbmcli on test>param_commitsession
> > > OK
> > >
> > > ---
> > > ./dbmcli on test>param_adddevspace 1 LOG logfile F 10000
> > > OK
> > >
> > > ---
> > > ./dbmcli on test>param_adddevspace 1 DATA datafile F 20000 OK
> > >
> > > ---
> > > ./dbmcli on test>db_cold
> > > ERR
> > > -24994,ERR_RTE: runtime environment error
> > > 1,Check knldiag! Kernel exited with '47' before reaching
> ADMIN state
> > >
> > > ---
> > >
> > > The problem is, that when i am trying to say
> db_cold it
>
> > > is ending giving the above error.
> > >
> > > Here's that i am sending u the snapshot of the
> > > kernldiag.err file of 'test' directory, (which is under
> > > '/var/opt/sapdb/indep_data/wrk/test') which u can find as an
> > > attachment.
> > > Please have a look at it.
> > >
> >
> > hmmmm... no attachment found. Either you want to make a good
> > joke or you
> > forgot to add it. But it would be better anyhow not to add
> > knldiag.err,
> > but the last written information found in knldiag. The
> > knldiag.err only
> > shows the 'ERR'or messages, while knldiag also includes warnings and
> > information
> > messages: Later ones make it much easier to identify what has
> > happened...
> >
> > >
> > > Guess i have provided u with enough details. If at all u
> > > require any further information, please do mail back so that i can
> > > send u at the
> > > earliest.
> > >
> > > Hope u will certainly turn up soon with some
> > > solution...............
> > >
> > >
> > >
> > > Thanks & Regards
> > > Ravi
> > >
> > CU
> > jrg
> >
> >
> >
> > --
> > MaxDB Discussion Mailing List
> > For list archives: http://lists.mysql.com/maxdb
> > To unsubscribe:
> > http://lists.mysql.com/[EMAIL PROTECTED]
> >
>
--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
