Hi list, Have a look at this:
dbmcli on mgmsys>db_enum -s OK .USRLOCA /usr/local/sapdb/depend 7.4.3.30 fast offline .USRLOCA /usr/local/sapdb/depend 7.4.3.30 slow offline .USRLOCA /usr/local/sapdb/depend 0.0.0.0 test unknown .USRLOCA /usr/local/sapdb/depend 7.4.3.30 quick offline MGMSYS /usr/local/sapdb/depend 7.4.3.30 fast running MGMSYS /usr/local/sapdb/depend 7.4.3.30 slow offline MGMSYS /usr/local/sapdb/depend 0.0.0.0 test unknown MGMSYS /usr/local/sapdb/depend 7.4.3.30 quick offline --- dbmcli on mgmsys> This is my database instance on a linux server after being created with dbmgui from a windows box. This looks somehow weird compared to dbmcli>db_enum -s OK MGMSYS C:\PROGRAMME\SAPDB\DEPEND 7.4.3.0 fast running .CPROGRA C:\PROGRAMME\SAPDB\DEPEND 7.4.3.0 fast offline --- dbmcli> on a windows machine. It looks like it somehow registered all kernels with this database instance. When I try to manually unregister one of the kernels, it unregisters all of them and when I want to re-register one kernel it produces above output again. Functionality doesn't seem to be affected although I'm not 100% sure. Uli -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
