Upgrade from v 1.3.1

[manu]

Like it

Up

0

Down

Drop it

::

Are you using the upgrade tool?

[yduma]

Like it

Up

0

Down

Drop it

::

yes.
I put migrate sql script and upgrade.php. When I run http://…./upgrade.php I get error.
After I try do next – mysql -u root -p pandora2 (I change name of pandora2 – copy of pandora db) < pandora_migrate_2.0.sql and get error –
ERROR 1091 (42000) at line 8: Can't DROP 'agent_type'; check that column/key exists

[Sancho]

Like it

Up

0

Down

Drop it

::

What version are you migrating from ?, the migration script is only for 1.3.1 version.

How do you make a copy of pandora db ?, using a full mysqldump ? (this is a good idea).

If you’re unsure about version, please put here dump for these SQL commands:

describe tagente;

select * from tconfig;

[yduma]

Like it

Up

0

Down

Drop it

::

I run migrate sql script for 1.3 to 1.3.1
after run migrate script for 1.3.1 to 2.0 and get error at line 33.

[manu]

Like it

Up

0

Down

Drop it

::

Ask nil’s question.

But it works for us, I have to say

[Sancho]

Like it

Up

0

Down

Drop it

::

Very odd….

Open a window with pandora_migrate_2.0.sql.

open another window with a mysql command line and enter line to line, the sql code from pandora_migrate_2.0.sql. Should work fine (i’ve tested in a lot of systems), if fail, say exactly what line and put it here.

[yduma]

Like it

Up

0

Down

Drop it

::

Running this script I receive
ERROR 1072 (42000) at line 33: Key column ‘disabled’ doesn’t exist in table
Same error when I was doing that line by line.

[yduma]

Like it

Up

0

Down

Drop it

::

Do somebody will read this discussions from administrators?

[raul]

Like it

Up

0

Down

Drop it

::

Yes, we are busy, but trying to identify the error

[yduma]

Like it

Up

0

Down

Drop it

::

Hi.

I think it is big problem when pandora user’s can’t upgrade it?!!!

I really need this.

THANKS!!!!!

[manu]

Like it

Up

0

Down

Drop it

::

It’s just you who can’t

[Sancho]

Like it

Up

0

Down

Drop it

::

Please, put here the results of

mysqldump –nodata -u root -p pandora

And we try to solve the migration problem.

[yduma]

Like it

Up

0

Down

Drop it

::

In atachement.

[yduma]

Like it

Up

0

Down

Drop it

::

I move database manually and get next:
1) pandora don’t see my modules.
2) If I create new module host alive – and after delete it, it start check my old module.