A new problem importing data with loadercli

I have fixed the 25011 problem that I got when I tried to import data with import from loadercli. It was due to a table in the database that has a VARCHAR(4000) UNICODE column (the documentation says that this type of data support a length <= 4000) Now I get two different problems when I try to im

24994

Hi, I've spent the last two days trying to figure this out so I figure its time to ask... I upgraded the database using the rpms from the mysql site on a CentOS 4.2 machine. I started at 7.6.0.12 and upgraded to 7.6.0.16. I now receive the following error every time I try to start the dat

RE: How to add a LONG with default value to a table

Hi Michael, >ALTER TABLE "DBA"."A_PERSON" ADD ("COMMENT2"LONG ASCII DEFAULT '') ><<< > >the error > > >>> > Error --- >Auto Commit: On, SQL Mode: Internal, Isolation Level: Committed > General error;-7035 POS(32768) DEFAULT specification not allowed for >this

RE: Error starting syncservice

Hola Ignacio, It seems this is a known bug in the SyncManGUI. When the master unit is defined as an out-unit the password for the message server is not stored. As a workaround you can define the master unit as in/out. A scenario for a unidirectional replication will also work with an in/out maste

Error starting syncservice

Hello, I receive this error when I try to start syncservice: java.lang.Exception: capture handling: password not found And the service does not start. The syncservice has to run on Sun Solaris, at the same box of the message server and the master database. The password for the user dbservice (u

How to define 2 FK into 1 table

Hello I want to define folowing DB structure: CREATE TABLE "SYSUSER" ( "ID" Integer NOT NULL DEFAULT SERIAL, "TSTAMP" Timestamp NOT NULL DEFAULT TIMESTAMP, "NAME" Varchar(30) ASCII NOT NULL, "PASSWORD" Varchar(30) ASCII NOT NULL, PRIMARY KEY (

How to add a LONG with default value to a table

Hi group, the definition of a table with a field of type long with the default value '' such as >>> CREATE TABLE "DBA"."A_PERSON" ( "ID" IntegerNOT NULL, "NAME" Char (20) ASCII DEFAULT '', "COMMENT"Long ASCII DEFAULT '', PRIMARY KEY

Re: Problems with loadercli and export

Rosa, I got a very similar error while importing a user catalog and data that contained some BLOB columns. It was solved by: 1.- Setting the parameter COLUMN_COMPRESSION to false on both instances. Restart them. 2.- re-exporting and re-importing. Hope it helps. Martin -- Dinamica - RADical J2EE

RE: Error while create TST database. MaxDB 7.6.0.16. Fedora 4

Thank you for answer, Heinrich! The problem was really created by SELinux. Now necessary will to create politics for user sdb. Pavel Konovalov Nettlecom LLC -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe:http://lists.mysql.com/[EMAIL PROT

Problems checking database from database manager gui

I am trying to import my database in anoter machine this time using restoring from a backup I make a database backup without problems but when I try to restart the database to which I restored the backup it can not reach the online state nor the admin mode and I get the following error 24806 cann

Problems with loadercli and export

I still have problems using loadercli This time I try to export de data using expor like this --- loadercli>export db catalog outstream file 'bd4.catalog' ddl data outstream file 'bd4.data' records package outstream file 'bd4.package' OK -25010 SQL error -2003 = Output columns too long (error pos