Adding portlet on one instance removed it from another

[user1 liferay, modificado 7 Anos atrás.]

Hello All,

This morning i encountered something really weird with liferay.

We have two instances that are running liferay(test and production) , both connect o a single backend oracle database.

We were surprisingly missing a portlet on the welcome screen on test and local machines yesterday but the production environment was fine.
This morning, we added the missing portlet to our welcome page. And immediately this caused the portlet to be removed from the production instance.
Any ideas as to what might have caused this?
Also, i cannot add the portlet on the production instance itself, because it can only be added once and therefore blurred out in the add applications window


One other issue we found recently,
We changed a permission on a page in local usually this propogates to test and production but recently it did not.
So i had to login to the production as admin and change the permissions on the page again.
Hoping this might give certain hints as to what might have caused this issue.

Since this is directly now affecting our production module, any inputs/help would be appreciated.

[user1 liferay, modificado 7 Anos atrás.]

Any ideas?

[Pankaj Kathiriya, modificado 7 Anos atrás.]

Your question is bit confusing.
Any reason you are using same database schema for test and production?

[user1 liferay, modificado 7 Anos atrás.]

Well, in a way, test server is there only to mirror the production environment.
Just to make sure there won't be any issues with that particular environment.

Why should using the same schema cause issues?
If anything any changes(good/bad) should reflect on both test and production in the exact same way right?

[Pankaj Kathiriya, modificado 7 Anos atrás.]

Can you explain in detail why same database schema is used for different environment.?
I don't think its good design at all. I am assuming your data in tables is getting mixed between environment which is causing issue.

[user1 liferay, modificado 7 Anos atrás.]

As i mentioned, the whole point of having test server instance to use the same schema, was it to mirror everything that production s/m was going to use and see including the data.
We have used this in this way for some time now, Any idea how different schema's might be seeing different values on one portlet?
We could use a different schema for the test but we also need to figure out what might be causing this issue.

[Jaydip Lakhatariya, modificado 7 Anos atrás.]

Hi,

I agree with Pankaj, It is really bad design to use same database schema for both of the server. This way it will cause lot of issues in several situations. If you want to mirror both the environment then its better to make it manually rather than using the same database schema.

Regards,
Jaydip