1. 

   shintoroi, Member

   I tried 1.3 and got the following just after i enter the mysql data info:
   Checking if myDBR reporting objects exist ToDo
   Running script failed with error
   MySQL error 1370: alter routine command denied to user 'XXXXXXXXXX'@'localhost' for routine XXXX_mydbr.sp_MyDBR_LicensesGet'

   DROP PROCEDURE IF EXISTS


   _

   I got the same error during an install with 1.22. I am on shared hosting on hostmonster using mysql 5,ioncube loaded, database user with full permissions. Read the docs till my eyes dried out. what am I missing. I also got the license for 1.22. I assumed it would be the same for 1.3but did not get to a part in the install where it asked for one.
2. 

   myDBR Team, Key Master

   myDBR is updating it's internal database, but is not able to drop and recreate a procedure in the database. Check what username has been used to create the object (sp_MyDBR_LicensesGet) in the database. It should match the admin username that you have specified in the myDBR connection info.

   To check the owner of the procedure issue a command:

   show create procedure sp_MyDBR_LicensesGet\G

   and look for the CREATE DEFINE value (form 'username@machine). Note that the different machine-part constitutes as a different user.

   To resolve the issue, use a username with more privileges or use the same username that you have used before.

   If myDBR's username matches the username that has been used to create the object ask for your hosting company to provide you the 'ALTER ROUTINE' privilege. if you have right to create routines, you should have right to drop them as well.

   To avoid this in future, always use same username when creating database objects.

   --
   myDBR Team
3. 

   shintoroi, Member

   Contacted my host and they told me I needed to use my main account to create the database object then I get this error:

   Checking if myDBR reporting objects exist ToDo
   Running script failed with error
   MySQL error 1267: Illegal mix of collations (utf8_general_ci,IMPLICIT) and (utf8_unicode_ci,IMPLICIT) for operation '='

   -- Fix tables and add admin user if it does not exist
   call sp_MyDBR_FixTables( database() )

   I am sorry if this seems trivial.
   MySQL client version: 5.0.81
4. 

   myDBR Team, Key Master

   myDBR uses UTF-8 as character set by default. UTF-8's default collation (rules how characters are compared to each other) is utf8_general_ci. For some reason you seem to have different collation used somewhere.

   To resolve the issue first check the collation used in mydbr tables:

   SELECT table_name, table_collation
   
   FROM information_schema.tables
   
   WHERE table_schema='mydbr';

   By default your tables should be utf8_general_ci.

   Probably the easiest way to resolve this is to dump the mydbr database (with routines) fix the incorrect collations and reload the database. You hosting provider may be able to help you.

   --
   myDBR Team
5. 

   bbaker@copesan.com, Member

   I am geting the following error when trying to install.

   DB error (1267): Illegal mix of collations (utf8_general_ci,IMPLICIT) and (utf8_unicode_ci,IMPLICIT) for operation '='

   I am installing on a produtcion Mysql server and I cannot change any of the setting. Can your code be changed to use unicode?
6. 

   myDBR Team, Key Master

   Hi,
   myDBR does use unicode (UTF8) in all operations. When myDBR creates the database it uses UTF8 charset and server default for the table collations (this is usually utf8_general_ci). Looks like your database is using differect collation (utf8_unicode_ci) therefore the mismatch.

   If your mismatch becomes from a comparision between myDBR's and your own database, you have few options:

   1) Change myDBR's default collation to utf8_unicode_ci
   2) Convert myDBR tables to use utf8_unicode_ci collation using ALTER TABLE
   3) Use COLLATE in queries

   See difference between utf8_general_ci and utf8_unicode_ci at http://dev.mysql.com/doc/refman/5.0/en/charset-unicode-sets.html

   --
   myDBR Team

Reply

You must log in to post.