Laurent Vaills wrote:

> 
> On Tue, 2002-02-05 at 08:45, Zabach, Elke wrote:
> > Corinne Laborde wrote:
> > 
> > > I did an update of the version 7.3.00.18 to the new version 
> > > 7.3.00.20. I 
> > > didn't have any errors.
> > > 
> > > Now I want to create a new database.
> > > 
> > > This is my error :
> > > 
> > > start communication server...
> > > stop and drop existing KASSA...
> > > create database KASSA...
> > > set parameters for KASSA...
> > > start KASSA...
> > > initializing KASSA...
> > > load system tables...
> > > load system tables failed: ERR
> > > -24964,ERR_EXECUTE: error in program execution
> > > 1792,/opt/sapdb/depend/bin/xload -S INTERNAL -n 
> > > localhost.localdomain -d 
> > > KASSA -u dba,* -b /opt/sapdb/depend/env/lsystab.ins en ENG domain
> > > Some SQL error has occured
> > > / S Error Summary      
> > > / S         1 x -7500    message not 
> > > available                                                     
> > >                                                               
> > >                                                               
> > >                                                  
> > > 
> > > / *
> > > / M STOP      20020204 00181559
> > > / *
> > > / M RC = 7    Some SQL error has occured
> > > / *
> > 
> > as I wrote 6 days ago and found in the archive again: 
> > recycled mail from the archive concerning error -7500:
> > 
> > some coding ( DDL Triggers, which serve to maintain some 
> catalog tables used
> > by SqlStudio ) are provided within the dynamic/shared library
> > "dbpinstall.dll" on WinNT or "dbpinstall.so" (.sl) on Unix.
> > This library has to be 'registered' using the 'xregcomp' 
> command before it
> > can be found by the SAP-DB kernel.
> > /usr/lib/userv/sapdb/bin/xregcomp
> > /usr/lib/userv/sapdb/lib/dbpinstall
> > ( please specify the complete path of the library without 
> using the file
> > extension .dll, .so or .sl )
> 
> I think when upgrading from the rpm packages, the 
> 'registration' of the
> library should be done by the rpm's script, shouldn't be ?
> 
> After discussing with Corinne outside of the list, it seems that the
> problem came from from the file Registry1.dcom . The group of the file
> was set to root instead of sapdb. Should the chmod has to be added in
> the rpm'script as well as the library's registration ?
> 
> Laurent

Mhm, the guy responsible for this script just told me that
being root the following is done:

[...]
_o=`$DBROOT/bin/xregcomp -c $DBROOT/lib/dbpinstall`
if [ -f /var/opt/sapdb/indep_data/config/Registry1.dcom ]; then
    chmod 664 /var/opt/sapdb/indep_data/config/Registry1.dcom
    chown root:sapdb /var/opt/sapdb/indep_data/config/Registry1.dcom
fi
[...]

and that therefore all users belonging to group sapdb should be able to
write.
He has too much work to further investigate in this problem (and I am not
familiar with this script). So: if someone sees the problem, please tell us.

Elke
SAP Labs Berlin

_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general

Reply via email to