I've created a portal-ext.properties and added:
jdbc.default.driverClassName=oracle.jdbc.driver.OracleDriver
jdbc.default.url=x
jdbc.default.username=y
jdbc.default.password=z
schema.run.enabled=true
schema.run.minimal=true
And I've added my ojdbc5.jar to lib/ext.
However when I run my startup.bat the database isn't being generated?
Does anyone know why this is occuring?
Check to make sure that the database is up and running. Can you log into Oracle using SQL*Plus or some other client using the credentials you've provided? If you can't, Liferay won't be able to either.
Can you try using lifery's Data Migration feature? You can start your server with default HSQL script and then try to migrate (which can automatically create tables as well).
Go to Control Panel->Server Administration.
- Enter the values in section Migrate from One DB to another and click execute.
Related
Attempting to view the a view or procedure:
from SQL Server Management Studio 17.4 in Azure SQL Datawarehouse notes the error:
I can however, delete and create any object that I want.
How can I work to ensure I can view the objects definition?
UPDATED
Concerning setting the options in SSMS to SQL Datawarehouse, there is not that option:
Please change this setting under Tools... Options. That should resolve the error. I wish we didn't have to change this but at lease we have a workaround.
In SSMS 17.5 there are a few more options. You can have it automatically detect what type of database you're connected to and script accordingly. Or you can force it to script for a particular database type like the following screenshot.
It appears there is a bug in certain versions of SSMS (such as 17.5) where if the DW user isn't also a user in the master database then scripting fails. The easy fix for this is having the server admin connect to the master database and run:
CREATE USER MyUserNameHere FROM LOGIN MyUserNameHere;
Sorry you're seeing this. I've been able to repro this on SSMS 17.4 and 17.5. We are looking at this now.
This seems to be a defect in the upgrade path for 17.5 as this should be supported without having to change the script settings. We are investigating this and will try to get an update out as soon as possible.
Liferay 6.1.1 CE GA2 works works fine-and-dandy on my local machine and my coworkers as well. When we deploy it to our main dev server, we find that we can't save any changes (i.e., create web content, change theme/schemes, etc).
Any idea why this is happening?
Cheers!
check the log output, this might give you hints on what's going wrong
If you get UI errors, this might help as well
check what database you're connecting with, make sure that the user account you use has write access to the database
In case you use hsql (don't do this unless on an unimportant demo server) make sure that the user your appserver runs as is able to write to the data directory and persist the database
If you're running on a cluster and the second machine doesn't pick up changes made through the first machine, you need to configure clustering properly. The Userguide at https://www.liferay.com/documentation/ has a chapter on this.
If nothing of this helps, please give more information
I am using liferay 6.1 and while configuring the database to mysql database in console it is giving error as innoDB is having row level logging enabled so unable to execute the query...etc..
But surprisingly I am not able to see these logs in any of the files.
I have checked {TOMCAT_HOME}/logs directory and {LIFERAY_HOME}/logs directory. But none of the files are containing the error logs.
If anybody can assist me on is there any other place to look for the logs, that will be really helpful.
Shruti
The blank database you have created might not have enough permission, you would need to give full permission i.e. to allow write / execute.
So that while you configure Liferay to point this blank database it will create table which requires write permission.
The issue is resolved now.
In mysql db the setting for binlog_format is "STATEMENT'
I changed it to ROW and it started running.
The syntax:
SET GLOBAL binlog_format = 'ROW';
Thanks ..
I'm using Broadleaf Commerce 2.2 and unable to update my database with new product entry which i did from admin console. I would like to know that why my changes which i made in admin is not reflecting in database?
I added couple of new product through admin console in Broadleaf database but when i check this under database table i won't find any product there. Is there any way which i need to consider or setup??? how can i add more product from admin and see those under database?
First migrate your database from hibernateSQl to Mysql.
then you have to made one change in development.resources after starting the jetty from
blPU.hibernate.hbm2ddl.auto=create-drop
to
blPU.hibernate.hbm2ddl.auto=update
if it doesnt works then you have to setup your whole demosite in tomcat server by just delpoying the .war file of your project in tomcat webapp folder.
and do the same changes in development.properties after starting the tomcat ..
It will surely work for you.
After doing a test install of Orchard 1.0, I've decided I want to use regular SQL Server instead of SQLCE. How do I change the provider? And, how do I re-run the database setup?
Best thing to do is to delete all files from under your App_Data folder in Orchard.Web, this way you can start fresh :)
Edit app_data\default\settings.txt.
You should change the settings.txt, located in App_Data\Sites\Default.
In this file, the connectionstring and provider is stored as plain text, like so:
Name: Default
DataProvider: SqlServer
DataConnectionString: Data Source=server;Initial Catalog=dbname;User Id=username;Password=password;
If you are using the SqlCe DataProvider, the connectionstring will be null.
Change it to the appropriate connectionstring and change the DataProvider to SqlServer. Once this is changed correctly, you'll be able to use the supplied SQL Server.
To migrate the data from SQL CE, I've used this VS2010 plugin as you can't connect to those DB's yet out of the box: http://visualstudiogallery.msdn.microsoft.com/0e313dfd-be80-4afb-b5e9-6e74d369f7a1/
Hope it'll be of any use to you as deleting the App_Data folder will give you a lot more work.