I'm running the script as root with the root password for the SQL database. I can give myself whatever permissions needed. Am I missing that step? I though root had unlimited privilege to the DB.
-----Original Message----- From: Kenneth Crocker [mailto:[EMAIL PROTECTED] Sent: Monday, April 21, 2008 2:28 PM To: Trenton Taylor Cc: rt-users@lists.bestpractical.com Subject: Re: [rt-users] error upgrading from 3.4.5 to 3.6.4 (via etc/upgrade/3.5.1 script) Trenton, Yep. Access to DataBases for the purpose of altering them is always limited. I had to have the permissions changed so I could run those scripts, then change them back to whatever. I suggest you speak to your DBA and Unix technicians about this. Kenn LBNL On 4/21/2008 1:45 PM, Trenton Taylor wrote: > Well now you nailed down exactly what my issue is. I don't have the "My > Tickets" or "Unowned Tickets" in the options. When I try to run the 3 > upgrade scripts, I get the following: > > 1. [EMAIL PROTECTED] ~]# /opt/rt3.6/sbin/rt-setup-database --dba root > --prompt-for-dba-password --action schema > In order to create or update your RT database,this script needs to > connect to your mysql instance on localhost as root. > Please specify that user's database password below. If the user has no > database > password, just press return. > > Password: > Creating database schema. > Problem with statement: > > > CREATE TABLE Attachments ( > id INTEGER NOT NULL AUTO_INCREMENT, > TransactionId integer NOT NULL , > Parent integer NOT NULL DEFAULT 0 , > MessageId varchar(160) NULL , > Subject varchar(255) NULL , > Filename varchar(255) NULL , > ContentType varchar(80) NULL , > ContentEncoding varchar(80) NULL , > Content LONGTEXT NULL , > Headers LONGTEXT NULL , > Creator integer NOT NULL DEFAULT 0 , > Created DATETIME NULL , > PRIMARY KEY (id) > ) TYPE=InnoDB > Table 'Attachments' already exists at /opt/rt3.6/sbin/rt-setup-database > line 220, <SCHEMA> line 464. > > 2. [EMAIL PROTECTED] ~]# /opt/rt3.6/sbin/rt-setup-database --dba root > --prompt-for-dba-password --action acl > In order to create or update your RT database,this script needs to > connect to your mysql instance on localhost as root. > Please specify that user's database password below. If the user has no > database > password, just press return. > > Password: > Done setting up database ACLs. > > 3. [EMAIL PROTECTED] ~]# /opt/rt3.6/sbin/rt-setup-database --dba root > --prompt-for-dba-password --action insert > In order to create or update your RT database,this script needs to > connect to your mysql instance on localhost as root. > Please specify that user's database password below. If the user has no > database > password, just press return. > > Password: > Use of uninitialized value in concatenation (.) or string at > /opt/rt3.6/sbin/rt-setup-database line 164, <STDIN> line 1. > [Mon Apr 21 20:12:58 2008] [crit]: Can't locate /content in @INC (@INC > contains: /opt/rt3/lib /opt/rt3/local/lib > /usr/lib/perl5/site_perl/5.8.6/i386-linux-thread-multi > /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi > /usr/lib/perl5/site_perl/5.8.4/i386-linux-thread-multi > /usr/lib/perl5/site_perl/5.8.3/i386-linux-thread-multi > /usr/lib/perl5/site_perl/5.8.6 /usr/lib/perl5/site_perl/5.8.5 > /usr/lib/perl5/site_perl/5.8.4 /usr/lib/perl5/site_perl/5.8.3 > /usr/lib/perl5/site_perl > /usr/lib/perl5/vendor_perl/5.8.6/i386-linux-thread-multi > /usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi > /usr/lib/perl5/vendor_perl/5.8.4/i386-linux-thread-multi > /usr/lib/perl5/vendor_perl/5.8.3/i386-linux-thread-multi > /usr/lib/perl5/vendor_perl/5.8.6 /usr/lib/perl5/vendor_perl/5.8.5 > /usr/lib/perl5/vendor_perl/5.8.4 /usr/lib/perl5/vendor_perl/5.8.3 > /usr/lib/perl5/vendor_perl /usr/lib/perl5/5.8.6/i386-linux-thread-multi > /usr/lib/perl5/5.8.6 .) at /opt/rt3.6/sbin/rt-setup-database line 464, > <STDIN> line 1. > (/opt/rt3/lib/RT.pm:295) > > > > I obviously need to get through these scripts successfully in order to > have those options. > > Any ideas? > > Trent > > > > > > -----Original Message----- > From: Kenneth Crocker [mailto:[EMAIL PROTECTED] > Sent: Monday, April 21, 2008 1:05 PM > To: Trenton Taylor > Cc: rt-users@lists.bestpractical.com > Subject: Re: [rt-users] error upgrading from 3.4.5 to 3.6.4 (via > etc/upgrade/3.5.1 script) > > Trenton, > > > By webpage, do you mean the Homepage? In 3.6.4, the first time > any user > signs on it will be blank. that's because the homepage settings (click > "Edit" on the right of the "RT at a glance" tool bar (blue). Select what > > you want to see and then click "home". After that, the homepage will > come up with your selections every time. As to the DB upgrade, I'd > advise to run all three commands anyway, can't hurt. > > > Kenn > LBNL > > On 4/21/2008 12:49 PM, Trenton Taylor wrote: >> I tried running my old database (the one that installs with 3.4.5) and >> the webpage is blank after a user logs in. >> >> If I skip the Schema and run the Insert, I get: >> >> Use of uninitialized value in concatenation (.) or string at >> /opt/rt3.6/sbin/rt-setup-database line 164, <STDIN> line 1. >> [Mon Apr 21 19:45:31 2008] [crit]: Can't locate /content in @INC (@INC >> contains: /opt/rt3/lib /opt/rt3/local/lib >> /usr/lib/perl5/site_perl/5.8.6/i386-linux-thread-multi >> /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi >> /usr/lib/perl5/site_perl/5.8.4/i386-linux-thread-multi >> /usr/lib/perl5/site_perl/5.8.3/i386-linux-thread-multi >> /usr/lib/perl5/site_perl/5.8.6 /usr/lib/perl5/site_perl/5.8.5 >> /usr/lib/perl5/site_perl/5.8.4 /usr/lib/perl5/site_perl/5.8.3 >> /usr/lib/perl5/site_perl >> /usr/lib/perl5/vendor_perl/5.8.6/i386-linux-thread-multi >> /usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi >> /usr/lib/perl5/vendor_perl/5.8.4/i386-linux-thread-multi >> /usr/lib/perl5/vendor_perl/5.8.3/i386-linux-thread-multi >> /usr/lib/perl5/vendor_perl/5.8.6 /usr/lib/perl5/vendor_perl/5.8.5 >> /usr/lib/perl5/vendor_perl/5.8.4 /usr/lib/perl5/vendor_perl/5.8.3 >> /usr/lib/perl5/vendor_perl > /usr/lib/perl5/5.8.6/i386-linux-thread-multi >> /usr/lib/perl5/5.8.6 .) at /opt/rt3.6/sbin/rt-setup-database line 464, >> <STDIN> line 1. >> (/opt/rt3/lib/RT.pm:295) >> >> >> >> Thanks for the help ... Any more ideas? >> >> >> >> -----Original Message----- >> From: Kenneth Crocker [mailto:[EMAIL PROTECTED] >> Sent: Monday, April 21, 2008 12:38 PM >> To: Trenton Taylor >> Cc: rt-users@lists.bestpractical.com >> Subject: Re: [rt-users] error upgrading from 3.4.5 to 3.6.4 (via >> etc/upgrade/3.5.1 script) >> >> Trenton, >> >> >> >> What I found was that I didn't need to BUILD the schema, just >> upgrade >> it. In fact, there are 3 DB upgrade executions we did (due to 3.5.1), >> which were: >> >> 1) action schema >> 2) action acl >> 3) action insert >> >> Turns out, the only one that did anything was action insert. The >> DB >> changes due to 3.5.1 do not really change any schema design or major >> stuff like that, it merely adds two new queries (10 unowned & my >> tickets) as default and updates the privileges so they can be used. I >> actually upgraded and forgot to run the DB upgrade part and RT worked >> fine, except those two queries were NOT listed or available. I ran the > >> three actions and those two queries were available for home page >> selection. I'm not familiar with how MySQL works as a database (in > terms >> of schema changes) so perhaps it requires a rebuild. Here's what I > used >> as my commands: >> >> 1) Typed >> "/tools/bin/perl/apps/rt/rt-[3.6.4]/sbin/rt-setup-database >> -dba rtadm -prompt-for-dba-password -action schema -datadir >> etc/upgrade/[3.5.1]" <enter> as one line. >> 2) Typed >> "/tools/bin/perl/apps/rt/rt-[3.6.4]/sbin/rt-setup-database >> -dba rtadm -prompt-for-dba-password -action acl -datadir >> etc/upgrade/[3.5.1]" <enter> as one line. >> 3) Typed >> "/tools/bin/perl/apps/rt/rt-[3.6.4]/sbin/rt-setup-database >> -dba rtadm -prompt-for-dba-password -action insert -datadir >> etc/upgrade/[3.5.1]" <enter> as one line. >> >> Hope this helps. >> >> Kenn >> LBNL >> >> On 4/21/2008 12:10 PM, Trenton Taylor wrote: >>> Nope ... >>> >>> Still no upgraded DB. We use Mysql. >>> >>> I am basically running a new instance of RT and an additional archive >> DB >>> now. We don't have many tickets on the new DB so I could easily > delete >>> them if someone could explain to me what is going wrong with the >> upgrade >>> script. >>> >>> Kenn ... what did your upgrade command look like? Anything different >>> than mine? (/opt/rt3.6/sbin/rt-setup-database --action schema \ >>> --datadir etc/upgrade/3.5.1 --dba root --prompt-for-dba-password) >>> >>> Thanks in advance to anyone who helps out ... >>> >>> Trent >>> >>> -----Original Message----- >>> From: Kenneth Crocker [mailto:[EMAIL PROTECTED] >>> Sent: Monday, April 21, 2008 12:02 PM >>> To: Trenton Taylor >>> Cc: rt-users@lists.bestpractical.com >>> Subject: Re: [rt-users] error upgrading from 3.4.5 to 3.6.4 (via >>> etc/upgrade/3.5.1 script) >>> >>> Trenton, >>> >>> >>> Did you get an answer to this? I just finished the same upgrade. >>> We use >>> Oracle. >>> >>> Kenn >>> LBNL >>> >>> On 4/17/2008 8:30 AM, Trenton Taylor wrote: >>>> I'm trying to upgrade my RT system from 3.4.5 to 3.6.4 via: >>>> >>>> >>>> >>>> # command: >>>> >>>> /opt/rt3.6/sbin/rt-setup-database --action schema \ --datadir >>>> etc/upgrade/3.5.1 --dba root --prompt-for-dba-password >>>> >>>> >>>> >>>> But I am getting this error: >>>> >>>> >>>> >>>> #: >>>> >>>> Creating database schema. >>>> >>>> Problem with statement: >>>> >>>> >>>> >>>> >>>> >>>> CREATE TABLE Attachments ( >>>> >>>> id INTEGER NOT NULL AUTO_INCREMENT, >>>> >>>> TransactionId integer NOT NULL , >>>> >>>> Parent integer NOT NULL DEFAULT 0 , >>>> >>>> MessageId varchar(160) NULL , >>>> >>>> Subject varchar(255) NULL , >>>> >>>> Filename varchar(255) NULL , >>>> >>>> ContentType varchar(80) NULL , >>>> >>>> ContentEncoding varchar(80) NULL , >>>> >>>> Content LONGTEXT NULL , >>>> >>>> Headers LONGTEXT NULL , >>>> >>>> Creator integer NOT NULL DEFAULT 0 , >>>> >>>> Created DATETIME NULL , >>>> >>>> PRIMARY KEY (id) >>>> >>>> ) TYPE=InnoDB >>>> >>>> Table 'Attachments' already exists at >>> /opt/rt3.6/sbin/rt-setup-database >>>> line 220, <SCHEMA> line 464. >>>> >>>> >>>> >>>> >>>> >>>> Thanks in advance - >>>> >>>> Trent >>>> >>>> >>>> >>>> >>>> Important: The information contained in this e-mail message is >>>> confidential and is intended only for the named addressee(s). If the > >>>> reader of this e-mail message is not an intended recipient (or the >>>> individual responsible for the delivery of this e-mail message to an > >>>> intended recipient), please be advised that any re-use, >> dissemination, >>>> distribution or copying of this e-mail message is prohibited. If you > >>>> have received this e-mail message in error, please reply to the >> sender >>>> that you have received the message in error and then delete it. > Thank >>> you. > ------------------------------------------------------------------------ >>>> _______________________________________________ >>>> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users >>>> >>>> Community help: http://wiki.bestpractical.com >>>> Commercial support: [EMAIL PROTECTED] >>>> >>>> >>>> Discover RT's hidden secrets with RT Essentials from O'Reilly Media. > >>>> Buy a copy at http://rtbook.bestpractical.com >>> >>> Important: The information contained in this e-mail message is >> confidential and is intended only for the named addressee(s). If the >> reader of this e-mail message is not an intended recipient (or the >> individual responsible for the delivery of this e-mail message to an >> intended recipient), please be advised that any re-use, dissemination, >> distribution or copying of this e-mail message is prohibited. If you >> have received this e-mail message in error, please reply to the sender >> that you have received the message in error and then delete it. Thank >> you. >> >> >> Important: The information contained in this e-mail message is > confidential and is intended only for the named addressee(s). If the > reader of this e-mail message is not an intended recipient (or the > individual responsible for the delivery of this e-mail message to an > intended recipient), please be advised that any re-use, dissemination, > distribution or copying of this e-mail message is prohibited. If you > have received this e-mail message in error, please reply to the sender > that you have received the message in error and then delete it. Thank > you. >> > > > > Important: The information contained in this e-mail message is confidential and is intended only for the named addressee(s). If the reader of this e-mail message is not an intended recipient (or the individual responsible for the delivery of this e-mail message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this e-mail message is prohibited. If you have received this e-mail message in error, please reply to the sender that you have received the message in error and then delete it. Thank you. > > Important: The information contained in this e-mail message is confidential and is intended only for the named addressee(s). If the reader of this e-mail message is not an intended recipient (or the individual responsible for the delivery of this e-mail message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this e-mail message is prohibited. If you have received this e-mail message in error, please reply to the sender that you have received the message in error and then delete it. Thank you. _______________________________________________ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com