I have tried to install the Bugzilla-5.0.4 version in my Windows 10 OS system.
Also, I have installed MySQL 8.0 version along to maintain the all Bug data assets. I have installed all plugin which were not install.
I have provided all database configuration in localconfig file.
But i am facing issue while running checksetup.pl command .
Few last lines taken from the CMD window while executing below command.
c:\Bugzilla>perl checksetup.pl
* This is Bugzilla 5.0.4 on perl 5.24.3
* Running on Win10 Build 17134
Checking perl modules...
.
.
.
.
.
Checking for DBD-mysql (v4.001) ok: found v4.033
Checking for MySQL (v5.0.15) ok: found v8.0.15
Adding new table groups...
DBD::mysql::db do failed: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'groups (
id mediumint auto_increment PRIMARY KEY NOT NULL,
name varchar(255) N' at line 1 [for Statement "CREATE TABLE groups (
id mediumint auto_increment PRIMARY KEY NOT NULL,
name varchar(255) NOT NULL,
description mediumtext NOT NULL,
isbuggroup tinyint NOT NULL,
userregexp tinytext DEFAULT '' NOT NULL,
isactive tinyint DEFAULT 1 NOT NULL,
icon_url tinytext
) ENGINE = InnoDB CHARACTER SET utf8"] at Bugzilla/DB.pm line 837.
Bugzilla::DB::_bz_add_table_raw(Bugzilla::DB::Mysql=HASH(0x913ec90), "groups", HASH(0x94cf7c8)) called at Bugzilla/DB.pm line 796
Bugzilla::DB::bz_add_table(Bugzilla::DB::Mysql=HASH(0x913ec90), "groups", HASH(0x94cf7c8)) called at Bugzilla/DB.pm line 509
Bugzilla::DB::bz_setup_database(Bugzilla::DB::Mysql=HASH(0x913ec90)) called at Bugzilla/DB/Mysql.pm line 558
Bugzilla::DB::Mysql::bz_setup_database(Bugzilla::DB::Mysql=HASH(0x913ec90)) called at checksetup.pl line 121
I really appreciate your help.
Thank you.
Resolved.
The issue is mainly with current BugZilla 5.0.4 version. The scripts to generate the tables and all relevant asset in MySql 8.0 doesn't support UTF-8.
Thus i am looking for downgrading the MySQL version to 5x versions.
Below are external links for your reference.
https://bugzilla.mozilla.org/show_bug.cgi?id=1424043
https://groups.google.com/forum/#!topic/mozilla.community.india/LRwxmGJ2yNQ
Related
Create a table statement as follows:
[omm#tpl-centos7 bin]$ ./gsql -ddev -Uomm -p26000 -f test.sql
gsql:test.sql:7: ERROR: column name “tid” conflicts with a system column name
total time: 0 ms
[omm#tpl-centos7 bin]$ cat test.sql
CREATE TABLE if not exists ax_quarantine_rcpt
(
“tid” varchar2(255) NOT NULL,
rcpt varchar2(255) NOT NULL,
org_id varchar2(60) NOT NULL,
PRIMARY KEY (“tid”,rcpt)
);
error:column name “tid” conflicts with a system column name
Looking at the documentation, it says reserved words must never be used as other identifiers, but tid is also not in the keyword
Referring to the Internet with double quotation marks does not work, solve
It may be a version problem. He described that the tid is occupied by the system view field. I can use the latest compiled version. It is recommended to use the latest version.
If you cannot compile it yourself, you can use the container version. https://hub.docker.com/repository/docker/enmotech/opengauss
I keep getting the "Invalid field size for datatype" error trying to BCP in several tables. This is despite the fact that I'm using Native (Unicode) mode and I am absolutely certain that the table definitions match because the target is created from a DACPAC of the source right before I attempt the import. Some tables work, but most fail with the error. I've tried using format files as well, and that didn't help either. I've read all the documentation and all the BCP-related questions I could find on SO. Any ideas?
Here's my export command. The $query_array is just a dictionary of "Select * From $tbl" mixed with "Select * From $tbl Where some date filter":
&bcp $query_array[$tbl] QueryOut "Data\$tbl.dat" -N -S $SqlAddress -d $SqlDB -T;
And here's the import:
&bcp $tgtTable in "Data\$tbl.dat" -N -S $SqlAddress -d $SqlDB -E -T -ErrorAction Stop;
One of the tables that fails looks like this:
CREATE TABLE [Foo].[Bar](
[Blah1] [numeric](38, 0) NOT NULL,
[Blah2] [numeric](38, 0) NULL,
[Blah3] [numeric](38, 0) NULL,
[Blah4] [numeric](38, 0) NULL,
[Blah5] [datetime2](7) NULL,
[Blah6] [varchar](30) NULL,
[Blah7] [datetime2](7) NULL,
CONSTRAINT [PK_Foo] PRIMARY KEY CLUSTERED
(
[Blah1] ASC
)
The overall procedure is pretty simple
Generate DACPAC from source
Export each table using BCP in Unicode Native to a dat file
Create target DB from DACPAC
Import each table using BCP in Unicode Native format from dat file
This is driving me crazy. It should just work. I'm guessing that there's a problem with the datetime2 fields, but I cant imagine what it is. TIA.
i am installing moodle (2.2 or 2.5) and modified the sql generator.php to have foreign keys and map the database for studies proposes and i get this allways, i am using 5.5.27 - MySQL Community Server by the way
Debug info: Table 'config' already exists CREATE TABLE config ( id
BIGINT(10) NOT NULL auto_increment, name VARCHAR(255) CHARACTER SET
utf8 COLLATE utf8_spanish_ci NOT NULL DEFAULT '', value LONGTEXT
CHARACTER SET utf8 COLLATE utf8_spanish_ci NOT NULL, CONSTRAINT
PRIMARY KEY (id) ) ENGINE = InnoDB DEFAULT CHARACTER SET utf8 DEFAULT
COLLATE = utf8_spanish_ci Error code: ddlexecuteerror Stack trace:
line 429 of \lib\dml\moodle_database.php: ddl_change_structure_exception thrown
line 842 of \lib\dml\mysqli_native_moodle_database.php: call to moodle_database->query_end()
line 88 of \lib\ddl\database_manager.php: call to mysqli_native_moodle_database->change_database_structure()
line 77 of \lib\ddl\database_manager.php: call to database_manager->execute_sql()
line 417 of \lib\ddl\database_manager.php: call to database_manager->execute_sql_arr()
line 369 of \lib\ddl\database_manager.php: call to database_manager->install_from_xmldb_structure()
line 1479 of \lib\upgradelib.php: call to database_manager->install_from_xmldb_file()
line 203 of \admin\index.php: call to install_core()
i found this is a minor bug at https://tracker.moodle.org/browse/MDL-20437 anyways its for the version 1.9 but this is not the version i try to install
i have searched so far and no solution!. did someone actually fix this
It seems, you are naming your table "config" which is a big NO-NO. You are supposed to prefix your table names by the name of your module. E.g. if your module is called "mymodule", it's config table name should be "mymodule_config". I hope, this fixes it for you.
See this Moodle dev wiki article for more information.
I can't solve my problem with my local Oracle database.
I'm tryong to connect to my local Oracle database (Oracle Database 11g Express Edition)
Later on I will use JNDI to another Oracle Database, but I think this should still work.
Driver: ojdbc6.jar in /lib
db.default.driver=oracle.jdbc.driver.OracleDriver
db.default.url="jdbc:oracle:thin:#localhost:1521:xe"
db.default.user="user"
db.default.pass="pass"
So I know I do connect to the database, but the error is that it says that the table does not exist. I'm not even creating or querying to a table (no model exists - but I've tried with having a model too, same error). Something seems to be wrong in the beginning and I don't know how to Debug this.
Error:
**java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist**
oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:457)
oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:400)
oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:926)
oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:476)
oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:200)
oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:543)
oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:197)
oracle.jdbc.driver.T4CStatement.executeForDescribe(T4CStatement.java:1213)
oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1492)
oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1710)
oracle.jdbc.driver.OracleStatement.executeQuery(OracleStatement.java:2006)
oracle.jdbc.driver.OracleStatementWrapper.executeQuery(OracleStatementWrapper.java:1709)
com.jolbox.bonecp.StatementHandle.executeQuery(StatementHandle.java:503)
play.api.db.evolutions.Evolutions$.executeQuery(Evolutions.scala:118)
play.api.db.evolutions.Evolutions$.databaseEvolutions(Evolutions.scala:334)
play.api.db.evolutions.Evolutions$.evolutionScript(Evolutions.scala:306)
play.api.db.evolutions.EvolutionsPlugin$$anonfun$onStart$1$$anonfun$apply$1.apply$mcV$sp(Evolutions.scala:435)
play.api.db.evolutions.EvolutionsPlugin.withLock(Evolutions.scala:478)
play.api.db.evolutions.EvolutionsPlugin$$anonfun$onStart$1.apply(Evolutions.scala:434)
play.api.db.evolutions.EvolutionsPlugin$$anonfun$onStart$1.apply(Evolutions.scala:432)
scala.collection.immutable.List.foreach(List.scala:309)
play.api.db.evolutions.EvolutionsPlugin.onStart(Evolutions.scala:432)
play.api.Play$$anonfun$start$1$$anonfun$apply$mcV$sp$1.apply(Play.scala:63)
play.api.Play$$anonfun$start$1$$anonfun$apply$mcV$sp$1.apply(Play.scala:63)
scala.collection.immutable.List.foreach(List.scala:309)
play.api.Play$$anonfun$start$1.apply$mcV$sp(Play.scala:63)
play.api.Play$$anonfun$start$1.apply(Play.scala:63)
play.api.Play$$anonfun$start$1.apply(Play.scala:63)
When reading about it I've only found that I might not have permission to some table, but the thing is that I use the same login in Oracle SQL Developer and it works.
As nico_ekito wrote, you need to create this table manually.
This one works for me:
CREATE TABLE play_evolutions
(
id Number(10,0) Not Null Enable,
hash VARCHAR2(255 Byte),
applied_at Timestamp Not Null,
apply_script clob,
revert_script clob,
state Varchar2(255),
last_problem clob,
CONSTRAINT play_evolutions_pk PRIMARY KEY (id)
);
Try to manually create a play_evolutions table with the following columns (by adapting the types to the ones used by Oracle):
id int not null primary key, hash varchar(255) not null,
applied_at timestamp not null,
apply_script text,
revert_script text,
state varchar(255),
last_problem text
In conf/application.conf
Un-comment the following line:
evolutionplugin=disabled
This is if you don't need Evolutions (to track schema changes).
Using Greenplum database version 3.2.3 on Solaris.
Step 1. Create a table.
CREATE TABLE ivdb.OPTION_PRICE (
SecurityID integer NOT NULL,
Date timestamp NOT NULL,
Root char(5) NOT NULL,
Suffix char(2) NOT NULL,
Strike integer NOT NULL,
Expiration timestamp NOT NULL,
CallPut char(1),
BestBid real NOT NULL,
BestOffer real NOT NULL,
LastTradeDate timestamp NULL,
Volume integer NOT NULL,
OpenInterest integer NOT NULL,
SpecialSettlement char(1) DEFAULT '0',
ImpliedVolatility real NOT NULL,
Delta real NOT NULL,
Gamma real NOT NULL,
Vega real NOT NULL,
Theta real NOT NULL,
OptionID integer NOT NULL,
Adjustmentfactor integer DEFAULT 1 NOT NULL,
CONSTRAINT PK_OPTION_PRICE PRIMARY KEY (Date, Root, Suffix))
PARTITION BY RANGE (Date) (
START (timestamp '01/01/1996') INCLUSIVE
END (timestamp '01/01/2020') EXCLUSIVE
EVERY (INTERVAL '1 month'));
Step 2: Insert data from another table. (This one is plain vanilla, not partitioned, no constraints. It has 564,392,723 rows.)
INSERT INTO OPTION_PRICE SELECT * FROM casey_option_price;
Results:
-- Executing query:
INSERT INTO OPTION_PRICE SELECT * FROM casey_option_price;
NOTICE: Releasing gangs to finish aborting the transaction.
ERROR: Segment connection failed: allocateWriterGang attempted to return a bad gang. (cdbgang.c:2591)
********** Error **********
ERROR: Segment connection failed: allocateWriterGang attempted to return a bad gang. (cdbgang.c:2591)
SQL state: XX000
The bad gang things brings the whole show to a halt, need to restart database to get things cleaned up again.
Haven't found much on the web, have a helpdesk ticket open with greenplum, thought I'd float it out here as well. Will come back with a solution if I get one before you do.
Sorry, not enough rep to tag with "greenplum".
This error was due to a hardware problem. A hard drive failed and for some reason the RAID didn't cover us correctly.
"bad gang" means "check your hardware" to me now.
A related (or maybe the real one) problem: Check your gp_vmem_protect_limit setting. Ours was too high, and I was using up all of the machine's swap space in my query.
The "gang was disconnected" is a symptom which indicates one or more primary segments' worker processes abort abnormally.
The possible causes vary. EG, max_connections are reached on one segment; primary segments down due to timeout; Postgresql Processes are killed;
segment server NIC issue; File system is full on segments; etc.
I suggest you open cases to GP support team with below info:
master logs
related segment logs
gp_segment_configuration output
select * from gp_configuration_history order by 1 desc;
/var/log/messages on related segment servers
df -h on segments
Any change you may think related.